PEPPOL T006 - Tender Reception Notification 1.2

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.

Statement of copyright

This PEPPOL Business Interoperability Specification (BIS) document is based on the CEN CWA prepared by the BII workshop specified in the introduction below. The original CEN CWA document contains the following copyright notice which still applies:

The CEN CWA documents and profiles prepared by the BII workshop are not specific to a business area. Subject to agreement with CEN, customizations have been made by PEPPOL to establish the PEPPOL BIS, detailing and adding further guidance on the use of BII profiles.

OpenPEPPOL AISBL holds the copyright in the customizations made to the original document. The customizations appear from the corresponding conformance statement which is attached to this document. For the purpose of national implementations, customizations covered by the conformance statement may be further refined and detailed by PEPPOL Authorities and/or other entities authorized by OpenPEPPOL AISBL, provided that interoperability with PEPPOL BIS is ensured. This PEPPOL BIS document may not be modified, re-distributed, sold or repackaged in any other way without the prior consent of CEN and/or OpenPEPPOL AISBL.

1. Principle and prerequisites

1.1. Scope

This guide aims to provide insight into transaction details for the transaction model T006 - Tender Reception Notification 1.2. 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

Table 1. parties
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

Table 2. roles
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 "T006 - Tender Reception Notification 1.2", it inherits from CEN WS/BII 3 "Trdm045 Tender Reception Notification"(CWA 17027-205).

Table 3. Transaction business requirements of T006
ID	Requirement
tbr45-001	The Tender Reception Notification shall have its own ID, date and time (and timezone) of issue and name or identification of its sender and receiver.
tbr45-005	The Tender Reception Notification shall refer to the Tender documents that were received and to the procurement project.
tbr45-002	The Tender Reception Notification shall state the date and time 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-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

3. Data model: Syntax mapping and XML example

3.1. Data model and syntax mapping

The data model and syntax mapping for Tender Reception Notification can be found at Syntax mapping for T006 - Tender Reception Notification 1.2. The data model and syntax mapping explains how to use the UBL (or an underlying syntax) to support the Tender Reception Notification information transaction requirements. It provides the syntax mappings from each UBL (or syntax) element to the Tender Reception Notification information elements of this transaction.

3.2. XML example

The following XML example illustrates the structure of an instance of T006 - Tender Reception Notification 1.2.

Link to example file

Example

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TenderReceipt xmlns="urn:oasis:names:specification:ubl:schema:xsd:TenderReceipt-2"
    xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
    xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
    >
        <cbc:UBLVersionID>2.2</cbc:UBLVersionID>
        <cbc:CustomizationID>urn:fdc:peppol.eu:prac:trns:t006:1.2</cbc:CustomizationID>
        <cbc:ProfileID>urn:fdc:peppol.eu:prac:bis:p003:1.2</cbc:ProfileID>
        <cbc:ID schemeURI="urn:uuid">49af1fe0-c0af-4a98-8ffa-309408f9cfac</cbc:ID>
        <cbc:ContractFolderID>765a9937-16d5-4513-92b4-cc9800925951</cbc:ContractFolderID>
        <cbc:IssueDate>2017-12-07</cbc:IssueDate>
        <cbc:IssueTime>14:44:33+01:00</cbc:IssueTime>
        <cbc:RegisteredDate>2017-12-07</cbc:RegisteredDate>
        <cbc:RegisteredTime>14:44:22+01:00</cbc:RegisteredTime>
        <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="9930">DE122268496</cbc:EndpointID>
                </cac:IssuerParty>
        </cac:TenderDocumentReference>
        <cac:TenderDocumentReference>
                <cbc:ID schemeURI="urn:uuid">243A177F-E4E9-4FC8-B97E-BB1A950DD8F8</cbc:ID> (2)
                <cbc:DocumentTypeCode listID="UNCL1001">310</cbc:DocumentTypeCode> (3)
                <cac:Attachment>
                        <cac:ExternalReference>
                                <cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash> (4)
                                <cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod> (5)
                        </cac:ExternalReference>
                </cac:Attachment>
                <cac:IssuerParty>
                        <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (6)
                </cac:IssuerParty>
        </cac:TenderDocumentReference>
        <cac:SenderParty>
                <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID>
                <cac:PartyIdentification>
                        <cbc:ID schemeID="0204">991-1234512345-06</cbc:ID>
                </cac:PartyIdentification>
                <cac:PartyName>
                        <cbc:Name>Beschaffungsamt des Bundesministerium des Innern (BeschA)</cbc:Name>
                </cac:PartyName>
        </cac:SenderParty>
        <cac:ReceiverParty>
                <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID>
                <cac:PartyIdentification>
                        <cbc:ID schemeID="0088">7300010000001</cbc:ID>
                </cac:PartyIdentification>
        </cac:ReceiverParty>
</TenderReceipt>

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 Reception Notification: Syntax mapping for T006 - Tender Reception Notification 1.2

The following code lists for coded elements and identifier schemes are used by the transaction.

4.1. Code list for elements

4.1.1. DocumentTypeCode

Qualifier	`UNCL1001` (listID)
Document location	`cac:DocumentReference/cbc:DocumentTypeCode`
Source codelist	UNCL 1001

Qualifier

UNCL1001 (listID)

Document location

cac:DocumentReference/cbc:DocumentTypeCode

Source codelist

UNCL 1001

4.2. Code list for identifier schemes

Table 4. 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:TendererParty/cbc:EndpointID/@schemeID
Contracting body electronic address identifier	schemeID attribute is mandatory and must use values from EAS codes	cac:ContractingParty/cac:Party/cbc:EndpointID/@schemeID
Economic operator identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:TendererParty/cac:PartyIdentification/cbc:ID/@schemeID
Contracting body identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:ContractingParty/cac:Party/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.

Examples of usage in cac:PartyIdentification

<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.

Examples of usage in cbc:EndpointID

<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:

Examples of usage in PartyIdentification and EndpointID

<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 Reception Notification - Syntax mapping for T006 - Tender Reception Notification 1.2 - 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.

Table 5. Customization ID to be used for this transaction.
TransactionID	Transaction name	Short Description	`cbc:CustomizationID`
T006	TenderReceipt	CA receives the tender and sends acknowledgement to EO	urn:fdc:peppol.eu:prac:trns:t006:1.2

6. Descriptions of selected parts of the transaction

6.1. Parties

6.1.1. Economic operator

The economic operator is the party submitting the tender and the recipient of the tender 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.

Economic operator is represented in UBL 2.2 using ReceiverParty

<cac:ReceiverParty>
        <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID>
        <cac:PartyIdentification>
                <cbc:ID schemeID="0088">7300010000001</cbc:ID>
        </cac:PartyIdentification>
</cac:ReceiverParty>

6.1.2. Contracting Body

The contracting body is the contracting authority or contracting entity who is buying supplies, services or tendering works.

The contracting body is represented in UBL 2.2 using the SenderParty:

<cac:SenderParty>
        <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID>
        <cac:PartyIdentification>
                <cbc:ID schemeID="0204">991-1234512345-06</cbc:ID>
        </cac:PartyIdentification>
        <cac:PartyName>
                <cbc:Name>Beschaffungsamt des Bundesministerium des Innern (BeschA)</cbc:Name>
        </cac:PartyName>
</cac:SenderParty>

6.2. Document references

6.2.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.

DocumentReference Identifier for a Call for Tender Reference must be expressed in a UUID syntax (RFC 4122).

Document hash algorithm must be SHA-256.

Tender document reference (REM Evidence)

<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="9930">DE122268496</cbc:EndpointID>
        </cac:IssuerParty>
</cac:TenderDocumentReference>

Tender document reference (Tender)

<cac:TenderDocumentReference>
        <cbc:ID schemeURI="urn:uuid">243A177F-E4E9-4FC8-B97E-BB1A950DD8F8</cbc:ID> (1)
        <cbc:DocumentTypeCode listID="UNCL1001">310</cbc:DocumentTypeCode> (2)
        <cac:Attachment>
                <cac:ExternalReference>
                        <cbc:DocumentHash>72182B98A9DAB9A553CCF161EA049D41337E51DFDF74DDC8AB7B68E7CFFB7D1B</cbc:DocumentHash> (3)
                        <cbc:HashAlgorithmMethod>http://www.w3.org/2001/04/xmlenc#sha256</cbc:HashAlgorithmMethod> (4)
                </cac:ExternalReference>
        </cac:Attachment>
        <cac:IssuerParty>
                <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (5)
        </cac:IssuerParty>
</cac:TenderDocumentReference>

6.2.2. Document Type Code (REM Evidence)

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 UNCL 1001. The code used to reference the REM-Evidence regarding the time of arrival of a tender is 13 (Post receipt)

Document Type Code

<cbc:DocumentTypeCode listID="UNCL1001">13</cbc:DocumentTypeCode> (1)

Issuer Party

Party, which issued the REM Evidence, usually the receiving access point which is not always the final receiving party of the message.

<cac:IssuerParty>
        <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID>
</cac:IssuerParty>

6.2.3. Document Type Code (Tender)

The tender document received 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 UNCL 1001. The code used to reference a tender is 310 (Offer / quotation)

Document Type Code

<cbc:DocumentTypeCode listID="UNCL1001">310</cbc:DocumentTypeCode> (1)

Issuer Party

Identifier of the economic operator which issued the tender.

<cac:IssuerParty>
        <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (1)
</cac:IssuerParty>

6.3. 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 where the tender was actually received and its delivery was registered while the issue date and time refer to the issuance of the tender receipt notification.

The issue time and registered time must specify the time zone.

Example of Issue date/time and Registered date/time

<cbc:IssueDate>2017-12-07</cbc:IssueDate>
<cbc:IssueTime>14:44:33+01:00</cbc:IssueTime>

<cbc:RegisteredDate>2017-12-07</cbc:RegisteredDate>
<cbc:RegisteredTime>14:44:22+01:00</cbc:RegisteredTime>