Adds a communication object to the tender and lot objects, to describe the modalities of communication about key events.
If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
In the European Union, this extension's fields correspond to eForms BT-124, BT-127, BT-631, BT-632 and BT-738.For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
An example of a planning notice from which a competition notice will follow.
{
"tender": {
"communication": {
"atypicalToolName": "ACertainTool",
"atypicalToolUrl": "https://ecomm-procurement.example.net",
"futureNoticeDate": "2020-06-17T00:00:00+01:00",
"noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
"documentAvailabilityPeriod": {
"startDate": "2020-06-15T00:00:00+01:00",
"endDate": "2020-07-10T00:00:00+01:00"
}
}
}
}An example of a planning notice that is used as a call for competition and that is divided into lots.
{
"tender": {
"lots": [
{
"id": "LOT-0001",
"communication": {
"atypicalToolName": "ACertainTool",
"atypicalToolUrl": "https://ecomm-procurement.example.net",
"noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
"documentAvailabilityPeriod": {
"startDate": "2020-06-15T00:00:00+01:00",
"endDate": "2020-07-10T00:00:00+01:00"
},
"invitationToConfirmInterestDispatchDate": "2020-11-15T09:00:00+01:00"
}
}
]
}
}Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
- Add fields:
Communication.atypicalToolNameCommunication.invitationToConfirmInterestDispatchDateCommunication.noticePreferredPublicationDateLot.communication
- Add
tender.communication.documentAvailabilityPeriodfield
- Add
minProperties,minItemsand/orminLengthproperties.
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.