UBL PR - Comment - Document changes: ÂWhat and ÂWhy (UBL-212)

["Mr. Yves Jordan" <yves.jordan@ext.publications.europa.eu>]

Hi,

Any Pre-Award notice may be subject to changes. Any change should specify:
- the original notice, 
- the background reason for the change (code and description),
- the modification/addition/deletion (concerned notice section, change description and/or values)

Proposal to have an optional repeatable Change ASBIE for any document type that may require describing changes. This currently concerns PIN, CN, CAN documents. A sample fragment is reported below.

NB: This solution is also suitable for ÂContracts Modifications with the single introduction of a ÂContractModification ASBIE of type Change

Thanks,
Yves

cac:Change

- ProcurementDocumentsChangeIndicator
- ProcurementDocumentsChangeDate

- cbc:ChangedNoticeIdentifier

- cac:Reason
-- cbc:ChangeReasonCode
-- cbc:ChangeReasonDescription

- cac:Element
-- cbc:ChangedSectionIdentifier
-- cbc:ChangeDescription
-- cbc:ElementOldValue
-- cbc:ElementNewValue

<cac:Change>
    <cbc:ChangedNoticeIdentifier>123
<!-- identifier of the changed notice -->
    </cbc:ChangedNoticeIdentifier>
    <cac:Reason>

	<cbc:ChangeReasonCode>ABC
<!-- from codelist -->
    </cbc:ChangeReasonCode>
	    <cbc:ChangeReasonDescription>Provision of additional information
<!-- Main reason for the change. -->
    </cbc:ChangeReasonDescription>
	</cac:Reason>
	<cac:Element>
	    <cbc:ChangedSectionIdentifier>IV.2.2)
<!-- to specify the section as numbered in the user friendly format -->
    </cbc:ChangedSectionIdentifier>
	    <cbc:ChangeDescription>Specification of the time-limit in local time of the tender submission deadline
    	<!-- Useful for changes not reflected in user friendly formats and for changes applied to multiple elements of a same section -->
    </cbc:ChangeDescription>
	    <!-- Old and new values help identify individual applied changes; they may also be used to mark deleted (Old only) or added (New only) information-->
	    <cbc:ElementNewValue>15:00</cbc:ElementNewValue>
    	</cac:Element>
    </cac:Change>
    <cac:Change>
    	<cbc:ChangedNoticeIdentifier>123
    <!-- identifier of the changed notice -->
    	</cbc:ChangedNoticeIdentifier>
       <cac:Reason>
	    <cbc:ChangeReasonCode>GHI<!-- from codelist --></cbc:ChangeReasonCode>
	    <cbc:ChangeReasonDescription>Information update
    	<!-- Main reason for the change. -->
    </cbc:ChangeReasonDescription>
    	</cac:Reason>
    	<cac:Element>
	    <cbc:ChangedSectionIdentifier>I.3)
      	<!-- to specify the section as numbered in the user friendly format -->
    </cbc:ChangedSectionIdentifier>
	    <cbc:ChangeDescription>Submission URL update
    	<!-- Useful for changes not reflected in user friendly formats and for changes applied to multiple elements of a same section -->
    </cbc:ChangeDescription>
	    <!-- Old and new values help identify individual applied changes; they may also be used to mark deleted (Old only) or added (New only) information-->
    <cbc:ElementOldValue>https://yourSubmissionPortalv1.0</cbc:ElementOldValue>
    <cbc:ElementNewValue>https://ourSubmissionPortalv1.2</cbc:ElementNewValue>
    	</cac:Element>
    </cac:Change>
    <cac:Change>
    	<cbc:ProcurmentDocumentsChangeIndicator>True
    <!-- To indicate whether the Procurement Documents have changed (True) or not (False) -->
    	</cbc:ProcurmentDocumentsChangeIndicator>
    	<cbc:ProcurementDocumentsChangeDate>23-08-2019
    <!-- Date and time the Procurement Documents were changed -->
    	</cbc:ProcurementDocumentsChangeDate>
    	<cac:Reason>
	    <cbc:ChangeReasonCode>DEF<!-- from codelist --></cbc:ChangeReasonCode>
	    <cbc:ChangeReasonDescription>Procurement Documents have been updated
    	<!-- Main reason for the change. -->
    </cbc:ChangeReasonDescription>
           	</cac:Reason>
    </cac:Change>