[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-214) Dealing with Contract Modification
Yves Jordan created UBL-214: ------------------------------- Summary: Dealing with Contract Modification Key: UBL-214 URL: https://issues.oasis-open.org/browse/UBL-214 Project: OASIS Universal Business Language (UBL) TC Issue Type: Improvement Components: Documents and business objects Environment: UBL - 2.2 Pre-Award Reporter: Yves Jordan Assignee: Cecile Guasch This may follow a similar approach as for Notice Changes (UBL-212) Some elements are common (or quite close) to ones for changes * *Modification Previous Section Identifier (Identifier):* An identifier of one or more sections within a previous notice within the procedure. The information in the modification section refers to this section or these sections. * *Modification Description (Text):* The summary of the contract modification(s). * *Modification Reason Code (Code):* The main reason for modifying the contract. * *Modification Reason Description (Text):* The description of the main reason for modifying the contract. SomeÂmore âContract Modificationâ specific information is also expected ("Overall price" before & after modification, "inflation rate") when this applies. Publication of a whole CAN, with updated values, would ensure other requirements (cf. annex V Part G, 2014/24/UE) are met while reusing existing document type and reducing the learning curve effect that the introduction of any new type of document could induce. The highlight of changes has also been requested; does anything exist that could help highlight âchangesâ or should this have a purely technical solution? -- This message was sent by Atlassian JIRA (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]