The PEPPOL Business Interoperability Specification, “BIS” from here on after, has been developed by the OpenPEPPOL AISBL Pre Award Coordinating Community and is published as part of the PEPPOL specifications.
1. Principle and prerequisites
1.1. Scope
This guide aims to provide insight into transaction details for the transaction model T014 - Tender Withdrawal Reception Notification 1.1. The transaction description is meant to be a standalone description to be used as a part of one or more procurement profiles. It describes syntax mappings, requirements, rules and example.
The transactions, specified in this document are intended to be exchanged between the tendering systems of economic operators and contracting bodies. This means that it is expected that the parties have connected their systems to the internet, and that they have middleware in place to enable them to send and receive the transactions in a secure way, using an agreed syntax.
The content model of the transactions can also be used in procurement platforms or notification platforms, so that these platforms as well as procurement systems of economic operators and contracting bodies are based on the same information and process models, which makes them more interoperable. Even if platforms are not technically interoperable, the content model facilitates understanding the tendering documents and to participate in the tendering process.
1.2. Parties and roles
The following parties participate as business partners in this transaction, acting in the roles as defined below
Party | Description | Example of roles |
---|---|---|
Customer |
The customer is the legal person or organization who is in demand of a product, service or works. |
Buyer, consignee, debtor, contracting body |
Supplier |
The supplier is the legal person or organization who provides a product, service or works. |
Seller, consignor, creditor, economic operator |
Role | Description |
---|---|
Contracting body |
The contracting authority or contracting entity who is buying supplies, services or tendering works. |
Economic operator |
Party participating with a bid in a procurement process to sell goods, services or works. |
2. Transaction business and information requirements
The following tables describe the transaction business and information requirements of "T014 - Tender Withdrawal Reception Notification 1.1", it inherits from CEN WS/BII 3 "Trdm045 Tender Reception Notification transaction".
The transaction "T014 - Tender Withdrawal Reception Notification 1.1" must be sent to the economic operator when an existing tender is withdrawn. The "T014 - Tender Withdrawal Reception Notification 1.1" acknowledges the reception of a tender withdrawal document and noting the date and time of reception.
ID | Requirement |
---|---|
tbr45-001 |
The Tender Reception Notification shall name the business process, specification, versions and have its own ID, date and time (and timezone) of issue and name or identification of its sender and receiver. |
tbr45-002 |
The Tender Reception Notification shall state the date and time (and timezone) the tender was received. |
tbr45-003 |
The Tender Reception Notification shall NOT give an assessment on completeness or validity of the tender. |
tbr45-004 |
In case the tender document was submitted simultaneously with the Qualification documents and/or the pre-award Catalogue document, the Tender Reception Notification shall notify the reception of those documents as well. |
tbr45-005 |
The Tender Reception Notification shall refer to the Tender documents that were received and to the procurement project. |
tbr45-006 |
The Tender Reception Notification may state the object of the tendered contract. |
tbr45-007 |
It shall be possible to check the integrity of the received document(s), e.g. by quoting the hash values. |
tbr45-008 |
It shall be possible to check the integrity of the Tender Reception Notification |
tbr45-009 |
The message may contain a reference to the related call for tender questions. |
3. Data model: Syntax mapping and XML example
3.1. Data model and syntax mapping
The data model and syntax mapping for Tender Withdrawal Reception Notification can be found at Syntax mapping for T014 - Tender Withdrawal Reception Notification 1.1. The data model and syntax mapping explains how to use the UBL (or an underlying syntax) to support the Tender Withdrawal Reception Notification information transaction requirements. It provides the syntax mappings from each UBL (or syntax) element to the Tender Withdrawal Reception Notification information elements of this transaction.
4. Code lists
Any element with the semantic data type = code, can mandate the use of a specific code list (or a fixed value). The applicable code lists can be found in the Code list section. In this section, you can find the valid codes, their names and description, and also links to where the same code list is used elsewhere in the transaction, or in other PEPPOL BIS transactions.
Information elements that are ruled by codelists in this transaction are also described in the Syntax mapping for Tender Withdrawal Reception Notification: Syntax mapping for T014 - Tender Withdrawal Reception Notification 1.1 |
The following code lists for coded elements and identifier schemes are used by the transaction.
4.1. Code list for identifier schemes
Business Term | Allowed Scheme | Applicable Xpath |
---|---|---|
Economic operator electronic address identifier |
schemeID attribute is mandatory and must use values from EAS codes |
cac:RequestorParty/cbc:EndpointID/@schemeID |
Contracting body electronic address identifier |
schemeID attribute is mandatory and must use values from EAS codes |
cac:ResponderParty/cbc:EndpointID/@schemeID |
Economic operator identifier |
schemeID attribute is mandatory and must use values from ICD codes |
cac:RequestorParty/cac:PartyIdentification/cbc:ID/@schemeID |
Contracting body identifier |
schemeID attribute is mandatory and must use values from ICD codes |
cac:ResponderParty/cac:PartyIdentification/cbc:ID/@schemeID |
5. PEPPOL Identifiers
PEPPOL has defined a Policy for use of Identifiers that specifies how to use identifiers in both its transport infrastructure and within the documents exchanged across that infrastructure. It also introduces principles for any identifiers used in the PEPPOL environment. The e-Tendering pilot adopts and extends the PEPPOL Policy in the following ways:
5.1. Party Identifiers used in business (UBL) documents
All party identifiers (cac:PartyIdentification/cbc:ID) have an optional scheme identifier attribute '@schemeID'. If used, the value shall be chosen from the code list ICD codes.
<cac:PartyIdentification>
<cbc:ID schemeID="0088">5790000435968</cbc:ID> (1)
</cac:PartyIdentification>
1 | schemeID attribute is optional, but when used, the codes must be from ICD codes |
5.2. Electronic address identifier used in business (UBL) documents
All electronic address identifiers (cbc:EndpointID/@schemeID) use the Electronic Address Scheme code list (EAS), maintained by CEF (CEF Code lists).
Valid values are found here: EAS codes.
<cbc:EndpointID schemeID="0184">DK87654321</cbc:EndpointID> (1)
1 | schemeID attribute is mandatory and must use values from EAS codes |
5.3. Document Identifiers used in business (UBL) documents
5.3.1. UBL Version ID
This transaction model is using the UBL 2.2 syntax. The namespace of the XML-message does only communicate the major version number. Since it is important for the receiver to also know what minor version of the syntax that is used, the element UBLVersionID must be stated with the value 2.2:
<cbc:UBLVersionID>2.2</cbc:UBLVersionID>
5.3.2. Profile ID
ProfileID identifies what business process a given message is part of, and are connected to one business process, and may contain multiple document types.
Valid profile identifiers are described in the Syntax mapping for Tender Withdrawal Reception Notification - Syntax mapping for T014 - Tender Withdrawal Reception Notification 1.1 - and the corresponding BIS document, see Main documentation site.
5.3.3. Customization ID
The PEPPOL Customization ID identifies the specification of content and rules that apply to the transaction. Profiles are connected to one business process (ProfileID), and may contain multiple transactions. Valid document instances shall contain corresponding ProfileID and CustomizationID.
CustomizationID is a string without spaces. Which customization identification should be used, is based on which transaction is sent. |
For implementers, please note that the process identifiers in the document instance MUST correspond to the SMP process identifier. |
TransactionID | Transaction name | Short Description | cbc:CustomizationID |
---|---|---|---|
T014 |
Tender Withdrawal Reception Notification |
The CA sends the Tender Withdrawal Reception Notification to the EO. |
urn:fdc:peppol.eu:prac:trns:t014:1.1 |
6. Description of selected parts of the transaction
The transaction including business terms, business rules and code lists are based upon the definitions of "Trdm045 Tender Reception Notification transaction" described in "Profile 53 — Tender Withdrawal" (CWA 17027-118:2016).
6.1. Process control
6.1.1. Specification identification
Identifier for the set of rules and transactions for the Tender Withdrawal Reception Notification.
<cbc:CustomizationID>urn:fdc:peppol.eu:prac:trns:t014:1.1</cbc:CustomizationID> (1)
1 | The value for the specification identification is always "urn:fdc:peppol.eu:prac:trns:t014:1.1". |
6.1.2. Business Process Type Identifier
Identifier for the business process context of the Tender Withdrawal Reception Notification.
<cbc:ProfileID>urn:fdc:peppol.eu:prac:bis:p007:1.1</cbc:ProfileID> (1)
1 | The value for the business process type identifier is always "urn:fdc:peppol.eu:prac:bis:p007:1.1". |
6.3. Reference Number
An identifier that is specified by the buyer and used as a reference number for all documents in the procurement process. It is also known as procurement project identifier, procurement reference number or contract folder identifier. In UBL the reference number is represented by the ContractFolder ID.
<cbc:ContractFolderID>CA2B5B8C-61A5-4797-8E27-47D7D22EAC29</cbc:ContractFolderID> (1)
1 | The Reference Number must be expressed in a UUID syntax (RFC 4122). |
6.3.1. Tender Document Reference
The tender reception notification contains the reference to the tender document sent by the economic operator. The contracting authority should refer to the tender by using the document hash and the hash algorithm method used.
Tender document reference ID
<cac:TenderDocumentReference>
<cbc:ID schemeURI="urn:uuid">243A177F-E4E9-4FC8-B97E-BB1A950DD8F8</cbc:ID> (1)
1 | DocumentReference Identifier for a Call for Tender Reference must be expressed in a UUID syntax (RFC 4122). |
Document Type Code
The type of business document must also be included in the document reference element. Document Type Code is coded according to code list 1001 issued by UN/CEFACT. For a complete list of all the document types, see UNECE 1001.
<cbc:DocumentTypeCode listID="UNCL1001">310</cbc:DocumentTypeCode> (1)
1 | The code "310" for status information has to be put into the tag. The listID is always UNCL1001. |
Document hash algorithm
<cac:Attachment>
<cac:ExternalReference>
<cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash> (1)
<cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod> (2)
</cac:ExternalReference>
</cac:Attachment>
1 | In this tag goes the digest of the document. Used as a reference to the tender document to be withdrawn. |
2 | Document hash algorithm must be "http://www.w3.org/2001/04/xmlenc#sha256". |
6.3.2. Use of REM Evidence
In case of the usage of a REM evidence in the tender document, it should be referred to in an additional document reference. Apart from the different values that suggest the use of the REM evidence the document type code has to be 13 to match a REM evidence. See the example for further details.
<cac:TenderDocumentReference>
<cbc:ID schemeURI="urn:uuid">4946060c-f428-475f-9d81-39409bdf32bd</cbc:ID>
<cbc:DocumentTypeCode listID="UNCL1001">13</cbc:DocumentTypeCode> (1)
<cac:Attachment>
<cac:ExternalReference>
<cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash>
<cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod>
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<cbc:EndpointID schemeID="9944">30058019</cbc:EndpointID>
</cac:IssuerParty>
</cac:TenderDocumentReference>
1 | Use of document type code 13 from the UNCL1001. For a REM evidence reference the document type code HAS to be 13. |
6.4. Parties
6.4.1. Issuer Party
Party, which issued the reception, not always the final receiving party of the message.
<cac:IssuerParty>
<cbc:EndpointID schemeID="9930">30058019</cbc:EndpointID> (1)
</cac:IssuerParty>
1 | The EndpointID with its schemeID is mandatory and has to be clarified. The schemeID is an attribute of the EndpointID and has to be chosen according to the EndpointID. |
6.4.2. Economic operator
The economic operator is the party submitting the tender and the recipient of the tender withdrawal reception notification, and is any natural or legal person or public entity or group of such persons and/or entities, including any temporary association of undertakings, which offers the execution of works and/or a work, the supply of products, or the provision of services on the market.
<cac:ReceiverParty> (1)
<cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (2)
<cac:PartyIdentification> (3)
<cbc:ID schemeID="0088">7300010000001</cbc:ID> (4)
</cac:PartyIdentification>
<cac:PartyName> (5)
<cbc:Name>Aankoopbureau</cbc:Name>
</cac:PartyName>
</cac:ReceiverParty>
1 | As stated above, in UBL the Economic Operator is represented by the Receiver Party. |
2 | At first the EndpointID with its schemeID has to be clarified. The schemeID is an attribute of the EndpointID and has to be chosen according to the EndpointID. |
3 | Following the EndpointID the Identification of the Party has to be given in the same manner. |
4 | The same value as in the EndpointID also the EndpointID has to be given into the ID and the corresponding attribute for the schemeID. |
5 | At last the Name of the Economic Operator has to filled into the Name tag of the tag PartyName. |
6.4.3. Contracting Body
The contracting body is the contracting authority or contracting entity who is buying supplies, services or tendering works.
<cac:SenderParty> (1)
<cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID> (2)
<cac:PartyIdentification> (3)
<cbc:ID schemeID="0204">991-1234512345-06</cbc:ID> (4)
</cac:PartyIdentification>
<cac:PartyName> (5)
<cbc:Name>Beschaffungsamt des BMI</cbc:Name>
</cac:PartyName>
</cac:SenderParty>
1 | As stated above, in UBL the Contracting Body is represented by the Sender Party. |
2 | At first the EndpointID with its schemeID has to be clarified. The schemeID is an attribute of the EndpointID and has to be chosen according to the EndpointID. |
3 | Following the EndpointID the Identification of the Party has to be given in the same manner. |
4 | The same value as in the EndpointID also the EndpointID has to be given into the ID and the corresponding attribute for the schemeID. |
5 | At last the Name of the Contracting Body has to filled into the Name tag of the tag PartyName. |
6.5. Date and time
Issue date/time, and the registered date/time must be sent.
Issue date and received date are both xs:date data type, and the date is specified as "YYYY-MM-DD" where:
-
YYYY - four digit year
-
MM - two digit month (01 to 12)
-
DD - two digit day (0)
Issue time and received time are both xs:time data type, and the time is specified as "hh:mm:ss" where:
-
hh - two digits of hour (00 to 23) (am/pm NOT allowed).
-
mm - two digits of minute (00 to 59)
-
ss - two digits of second (00 to 59)
-
TZD - time zone designator (Z or +hh:mm or -hh:mm)
The registered date and time are the times when the registered tender withdrawal was received and its delivery was registered while the issue date and time refer to the issuance of the tender withdrawal receipt notification. For a more detailed insight, take a look at the four-corner-model.
The issue time and registered time must specify the time zone. |
<cbc:IssueDate>2021-02-15</cbc:IssueDate> (1)
<cbc:IssueTime>00:00:00Z</cbc:IssueTime> (2)
<cbc:RegisteredDate>2021-02-14</cbc:RegisteredDate> (3)
<cbc:RegisteredTime>00:00:00Z</cbc:RegisteredTime> (4)
1 | Date when the tender withdrawal reception notification was issued. |
2 | Time when the tender withdrawal reception notification was issued, granular to seconds and timezone. |
3 | Date when the tender withdrawal was received. |
4 | Time when the tender withdrawal document was received, granular to seconds and timezone. |