PEPPOL T017 - Awarding Notification 1.1

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 T017 - Awarding 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

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 "T017 - Awarding Notification 1.1", it inherits from the profiles

BII Profile 58 - Notify Awarding (CWA 17026-104:2016)

created by CEN WS/BII 3.

Table 3. Transaction business requirements of T017 - Awarding Notification 1.1
ID	Requirement
tbr94-001	The contracting body shall be identified.
tbr94-002	The economic operator shall be identified.
tbr94-003	The creation date and time of the message shall be specified.
tbr94-004	Each message shall have a message ID and may refer to the ID of the corresponding tender.
tbr94-005	The CEN/BII profile and transaction names and versions shall be identified.
tbr94-006	The message shall contain the Procurement Reference number.
tbr94-007	The message may contain the Lot ID’s.
tbr94-008	The message may contain the following information about the award of the contract: Award ID Award date and time Economic operator name(s) Registration number(s) in the professional registry Economic operator registration country code(s) Economic operator awarding rank
tbr94-009	The message may contain the reason for not awarding the bid.
tbr94-010	The message may contain the grounds for awarding.
tbr94-011	The message may contain the end date of the stand still period.
tbr94-012	The message may contain the draft contract as an attachment.

3. Data model: Syntax mapping and XML example

3.1. Data model and syntax mapping

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

3.2. Data model diagram

The following transaction data model illustrates the classes and information elements of T017 - Awarding Notification 1.1.

3.3. XML example

The following XML example illustrates the structure of an instance of T017 - Awarding Notification 1.1.

Link to example file

Example file for T017 - Awarding Notification 1.1

<?xml version="1.0" encoding="UTF-8"?>
<AwardedNotification
        xmlns="urn:oasis:names:specification:ubl:schema:xsd:AwardedNotification-2"
        xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
        xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="
                urn:oasis:names:specification:ubl:schema:xsd:AwardedNotification-2
                http://docs.oasis-open.org/ubl/os-UBL-2.2/xsdrt/common/UBL-AwardedNotification-2.2.xsd
                urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2
                http://docs.oasis-open.org/ubl/os-UBL-2.2/xsdrt/common/UBL-CommonBasicComponents-2.2.xsd
                urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2
                http://docs.oasis-open.org/ubl/os-UBL-2.2/xsdrt/common/UBL-CommonAggregateComponents-2.2.xsd">
    <cbc:UBLVersionID>2.2</cbc:UBLVersionID> (1)
    <cbc:CustomizationID>urn:fdc:peppol.eu:prac:trns:t017:1.1</cbc:CustomizationID> (2)
    <cbc:ProfileID>urn:fdc:peppol.eu:prac:bis:p009:1.1</cbc:ProfileID> (3)
    <cbc:ID schemeURI="urn:uuid">191C084F-5CC0-4719-BE32-234DEF813B44</cbc:ID> (4)
    <cbc:ContractFolderID>765a9937-16d5-4513-92b4-cc9800925951</cbc:ContractFolderID> (5)
    <cbc:IssueDate>2021-02-15</cbc:IssueDate> (6)
    <cbc:IssueTime>00:00:00Z</cbc:IssueTime> (7)
    <cbc:Note>price too high</cbc:Note> (8)
    <cac:SenderParty>
        <cbc:EndpointID schemeID="9930">DE122268496</cbc:EndpointID> (9)
        <cac:PartyIdentification>
            <cbc:ID schemeID="0204">991-1234512345-06</cbc:ID> (10)
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>Beschaffungsamt des Bundesministerium des Innern (BeschA)</cbc:Name> (11)
        </cac:PartyName>
    </cac:SenderParty>
    <cac:ReceiverParty>
        <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (12)
        <cac:PartyIdentification>
            <cbc:ID schemeID="0088">7300010000001</cbc:ID> (13)
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>Dutch Tulips Ltd</cbc:Name> (14)
        </cac:PartyName>
    </cac:ReceiverParty>
    <cac:MinutesDocumentReference>
        <cbc:ID>4d53c26e-68cf-4bd0-952f-8e312e4deb76</cbc:ID> (15)
        <cbc:DocumentStatusCode listID="awardCode">unaward</cbc:DocumentStatusCode> (16)
    </cac:MinutesDocumentReference>
    <cac:TenderResult>
        <cbc:TenderResultCode listID="http://publications.europa.eu/resource/authority/winner-selection-status">selec-w</cbc:TenderResultCode> (17)
        <cbc:AwardDate>2021-01-15</cbc:AwardDate> (18)
        <cbc:AwardTime>14:44:33+01:00</cbc:AwardTime> (19)
        <cbc:StartDate>2020-12-15</cbc:StartDate> (20)
        <cac:Contract>
            <cac:ContractDocumentReference>
                <cbc:ID>123Contractref</cbc:ID> (21)
                <cac:Attachment>
                    <cac:ExternalReference>
                        <cbc:URI>cid:contractref.pdf</cbc:URI>
                        <cbc:MimeCode>text/pdf/</cbc:MimeCode>
                        <cbc:FileName>ContractDraft</cbc:FileName>
                    </cac:ExternalReference> (22)
                </cac:Attachment>
            </cac:ContractDocumentReference>
        </cac:Contract>
        <cac:AwardedTenderedProject>
            <cac:ProcurementProjectLot>
                <cbc:ID>LOT-0001</cbc:ID> (23)
            </cac:ProcurementProjectLot>
        </cac:AwardedTenderedProject>
        <cac:WinningParty>
            <cbc:Rank>1</cbc:Rank> (24)
            <cac:Party>
                <cac:PartyName>
                    <cbc:Name>Company1</cbc:Name> (25)
                </cac:PartyName>
                <cac:PartyLegalEntity>
                    <cac:RegistrationAddress>
                        <cac:Country>
                            <cbc:IdentificationCode listID="ISO3166-1:Alpha2">DE</cbc:IdentificationCode> (26)
                        </cac:Country>
                    </cac:RegistrationAddress>
                </cac:PartyLegalEntity>
            </cac:Party>
        </cac:WinningParty>
    </cac:TenderResult>
</AwardedNotification>

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 Awarding Notification: Syntax mapping for T017 - Awarding 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

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:SenderParty/cbc:EndpointID/@schemeID
Contracting body electronic address identifier	schemeID attribute is mandatory and must use values from EAS codes	cac:ReceiverParty/cbc:EndpointID/@schemeID
Economic operator identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:SenderParty/cac:PartyIdentification/cbc:ID/@schemeID
Contracting body identifier	schemeID attribute is mandatory and must use values from ICD codes	cac:ReceiverParty/cac:PartyIdentification/cbc:ID/@schemeID
Tender Reference	listID attribute is mandatory and must use values form awardCodeList	cac:MinutesDocumentReference/cbc:DocumentStatusCode/@listID
Tender Result Code	listID attribute is mandatory and must use values form Winner Selection Status	cac:TenderResult/cbc:TenderResultCode/@listID
Country Code	listID attribute is mandatory and must use values from Country Codes (ISO 3166-1:Alpha2)	cac:TenderResult/cac:WinningParty/cac:Party/cac:PartyLegalEntity/cac:RegistrationAddress/cac:Country/cbc:IdentificationCode/@listID

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 Awarding Notification - Syntax mapping for T017 - Awarding 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.

Table 5. Customization ID to be used for this transaction.
TransactionID	Transaction name	Short Description	`cbc:CustomizationID`
T017	Notify Awarding	The CA sends the awarding notification to all EO that have tendered.	urn:fdc:peppol.eu:prac:trns:t017: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 "Trdm094 Awarding Notification" described in BII Profile 58 - Notify Awarding (CWA 17026-104:2016).

6.1. Identifier

6.1.1. UBL Version Identifier

Requires UBL version 2.2.

Example of UBL Version Identifier

<cbc:UBLVersionID>2.2</cbc:UBLVersionID> (1)

1	Has to be 2.2, to correspondent to the used UBL version

6.1.2. Document Identifier

The identifier enables positive referencing the transaction instance for various purposes including referencing between transactions that are part of the same process. Must be expressed as a UUID.

Example of document identifier

<cbc:ID schemeURI="urn:uuid">191C084F-5CC0-4719-BE32-234DEF813B44</cbc:ID> (1)

1	A transaction instance must contain an identifier, being a number expressed in uuid syntax

6.1.3. Contract Folder ID

The identifier specified by the buyer 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 this element is mapped to the cbc:ContractFolderID class.

Example of document identifier

<cbc:ContractFolderID>765a9937-16d5-4513-92b4-cc9800925951</cbc:ContractFolderID> (1)

1	A reference number expressed in uuid syntax

6.2. Document Issue date and time

Document issue date/time must be sent.

Document issue date is a xsi:date data type and is specified as "YYYY-MM-DD" where:

YYYY - four digit year
MM - two digit month (01 to 12)
DD - two digit day (0)

Document issue time is a xsi:time data type and 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 document issue date and time refer to the date when of the issuance notification for awarding.

The document issue time must specify the time zone.

Example of document issue date and time

<cbc:IssueDate>2021-02-15</cbc:IssueDate> (1)
<cbc:IssueTime>00:00:00Z</cbc:IssueTime> (2)

1	Format for the date has to be yyyy-mm-dd
2	Format for the time has to be hh:mm:ssTZD, granularity down to seconds and timezone

6.3. Party identification

6.3.1. Contracting Body

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

Example of sender party

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

1	Identifies the contracting party’s electronic address and the scheme identifier for the electronic address
2	The national identifier of a contracting body as it is legally registered (e.g. VAT identification, such as KBO)
3	The name of the contracting body as it is registered

6.3.2. Economic Operator

The party who is supposed to process the Notification of Awarding.

Example of receiver party

<cac:ReceiverParty>
    <cbc:EndpointID schemeID="9946">500820007</cbc:EndpointID> (1)
    <cac:PartyIdentification>
        <cbc:ID schemeID="0088">7300010000001</cbc:ID> (2)
    </cac:PartyIdentification>
    <cac:PartyName>
        <cbc:Name>Dutch Tulips Ltd</cbc:Name> (3)
    </cac:PartyName>
</cac:ReceiverParty>

1	Identifies the receivers party’s electronic address and the scheme identifier for the electronic address
2	Can be the registration number in the professional registry. An identifier that identifies the economic operator, such as a legal registration identifier.
3	The name of the economic operator

6.4. Reason of non award/ Grounds for awarding

Textual description of the reason for not awarding the tender or the grounds for awarding an specific contract or a framework agreement. For reasons of non award the following code list may be helpful: Non award justification

Example of reason of non award

<cbc:Note>price too high</cbc:Note> (1)

1	Text field for the reason of awarding/non awarding

6.5. Tender Document Reference and awarding result

Machine readable code to easily identify the result of the tendering procedure for the corresponding document.

Example of tender document reference

<cac:MinutesDocumentReference>
    <cbc:ID>4d53c26e-68cf-4bd0-952f-8e312e4deb76</cbc:ID> (1)
    <cbc:DocumentStatusCode listID="awardCode">unaward</cbc:DocumentStatusCode> (2)
</cac:MinutesDocumentReference>

1	ID for the referenced tender document
2	Code for the result of the tendering procedure, listID must be "awardCode"

6.6. Tender Result

This sections contains all the information about the outcome of the tender, containing the date of the award, the date of the stand still period, the winning party and the resulting contract.

The tender result wraps all the subsections below into one xml tag.

6.6.1. Tender Result Code

The tender result code indicates weather the tendering procedure was successful and a winner was chosen, or if the tender was not awarded at all.

Example of tender result code

<cbc:TenderResultCode listID="http://publications.europa.eu/resource/authority/winner-selection-status">selec-w</cbc:TenderResultCode> (1)

1	Code for the result of the tendering procedure, listID has to be "http://publications.europa.eu/resource/authority/winner-selection-status"

6.6.2. Awarded Date and Time

The date and time on which the contract has been awarded. For the specification on how to use the date and time fields see the section above for the issue date and time.

Example of awarded date and time

<cbc:AwardDate>2021-01-15</cbc:AwardDate> (1)
<cbc:AwardTime>14:44:33+01:00</cbc:AwardTime> (2)

1	Format for the date has to be yyyy-mm-dd
2	Format for the time has to be hh:mm:ssTZD, granularity down to seconds and timezone

6.6.3. Start Date

Final date for the stand still period. For optional use in the transaction.

Example of start date

<cbc:StartDate>2020-12-15</cbc:StartDate> (1)

1	Format for the date has to be yyyy-mm-dd

6.6.4. Contract

Optional information about the contract, which is bound to the award.

Example of contract reference

<cac:Contract>
    <cac:ContractDocumentReference>
        <cbc:ID>123Contractref</cbc:ID> (1)
        <cac:Attachment>
            <cac:ExternalReference>
                <cbc:URI>cid:contractref.pdf</cbc:URI>
                <cbc:MimeCode>text/pdf/</cbc:MimeCode>
                <cbc:FileName>ContractDraft</cbc:FileName>
            </cac:ExternalReference> (2)
        </cac:Attachment>
    </cac:ContractDocumentReference>
</cac:Contract>

1	An identifier that can be used to reference the attached document, such as an unique identifier.
2	The External Reference to the ASICC Container, should consist of the file name, type (Mime Code) and the URI

6.6.5. Awarded Tendered Project

Optional reference to the specific lot which the notification is about. Only to be used if there were lots to be awarded differently.

Example of awarded tendered project

<cac:AwardedTenderedProject>
    <cac:ProcurementProjectLot>
        <cbc:ID>LOT-0001</cbc:ID> (1)
    </cac:ProcurementProjectLot>
</cac:AwardedTenderedProject>

1	An identifier for the lot

6.6.6. Winning Party

Information about all the winning parties. This tag can be used multiple times, but doesn’t have to be included. It should be used to add more detailed information about the winning economic operators of the tendering procedure.

Example of Winning Party

<cac:WinningParty>
    <cbc:Rank>1</cbc:Rank> (1)
    <cac:Party>
        <cac:PartyName>
            <cbc:Name>Company1</cbc:Name> (2)
        </cac:PartyName>
        <cac:PartyLegalEntity>
            <cac:RegistrationAddress>
                <cac:Country>
                    <cbc:IdentificationCode listID="ISO3166-1:Alpha2">DE</cbc:IdentificationCode> (3)
                </cac:Country>
            </cac:RegistrationAddress>
        </cac:PartyLegalEntity>
    </cac:Party>
</cac:WinningParty>

1	The rank of the economic operator
2	The name of the economic operator
3	The registration country code of the economic operator, listID attribute is mandatory and must use values from Country Codes (ISO 3166-1:Alpha2)