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:

© 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members.

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.

Introduction to openPEPPOL and BIS

This Peppol BIS provides a set of specifications for implementing a Peppol business process. The document is concerned with clarifying requirements for ensuring interoperability of pan-European Public eProcurement and provides guidelines for the support and implementation of these requirements. This document is based on work done by the e-SENS pilot project as well as work done by CEN WS/BII 3.

BII relationship
Figure 1. Relationship between BII profiles and PEPPOL BIS

The Profile P008 - "Publish Notice" 1.2 describes a process providing electronic messaging support for the business process to publish a prior information notice, a contract notice or a contract award notice. The profile is executed between a contracting body or his representative and a publication body to announce business opportunities and contract awards in public procurement procedures. The key aspects covered by this BIS are:

  • The electronic message exchange from the contracting body or his representative to publish a notice at the services provided by a publisher.

  • The association of a notice to the message following the syntax provided by the UBL document schemas: Prior Information Notice Schema, Contract Notice Schema, Contract Award Notice Schema.

  • The formatting of that notice according the rules described in eForms Specifications maintained by the Publication Office.

  • The possibility for the publisher to validate the notice, to request/suggest corrections to the notice, to approve its publication and to announce its publication date.

  • The association of notice metadata to facilitate PEPPOL eTendering processes such as P001 - Procurement Procedure Subscription.

The purpose of this document is to facilitate an efficient implementation and increased use of electronic collaboration regarding the notification and tendering process based on these formats.

Audience

The audience for this document is organizations wishing to be PEPPOL enabled for exchanging electronic pre-award tendering messages, and/or their ICT-suppliers. These organizations may be:

  • Service providers

  • Contracting Authorities (CA)

  • Economic Operators (EO)

  • Software Developers

More specifically, roles addressed are the following:

  • ICT Architects

  • ICT Developers

  • Business Experts

For further information on PEPPOL/OpenPEPPOL, please see Peppol

1. Principles and prerequisites

This chapter describes the principles and assumptions that underlie the use of Peppol Pre-award. It is based on the CEN WS/BII 3 and the work done upon eForms:

• eForms Specifications
• BII Profile 14 - Prior Information Notice (CWA 17026-102:2016)
• BII Profile 10 - Contract Notice (CWA 17026-202:2016)
• BII Profile 43 - Contract Award Notice (CWA 17026-103:2016)

The BII Profile 10, BII Profile 14, BII Profile 43 profile documents are available from your national standardization body.

The intended scope for this profile includes public procurement, but the profile may also be used in Business to Business (B2B) relations.

This profile is intended to support transmission of electronic documents for processing in (semi-)automated processes. The legal requirements that were taken into account are requirements from European legislation, in particular the Directive 2014/23/EU, Directive 2014/24/EU and Directive 2014/25/EU

1.1. Associated notification and tendering procedures

This section provides a brief overview about the notification and tendering procedures and their associated Peppol BIS and transactions. The illustration thereby points to the relevant Peppol BISs that depict a particular business process. Additionally, the guideline references the underlying CEN WS/BII 3 Workshop Agreement. The CEN BII3 workshop is a standardisation initiative within CEN (European Committee for Standardisation). It provides a framework for interoperability in pan-European electronic transactions expressed as a set of technical specifications ("Profiles") .

The profiles provided by CEN BII3 and Peppol are designed to facilitate effective public e-procurement based on a modular approach for implementation, with a focus on global interoperability. Thereby, BII profiles can be seen as “agreements” on message contents and business processes and are the baseline for many Peppol BISs which add specific technical implementation perspectives that are further illustrated in section 6. Thus, the CEN profile descriptions rather focus on the core information elements that typically cater to the majority of user requirements applicable across Europe and lower the need for detailed bilateral agreements between the trading partners whereas Peppol provides a framework for their implementation and adaption.

1.1.1. Notification procedures

Official notification through publishing bodies is part of many procurement procedures. Many pre-award opportunities first become visible to the economic operators in the form of notices describing upcoming or current procurement procedures (prior information notices or contract notices). At the end of a procedure, a contract award notice about the result of the procedure is published.

eNotification covers the transfer of electronic procurement notices for publication and dissemination with the ultimate aim of opening business opportunities. eNotification profiles are addressed to all those who exchange procurement notices for publication and further information processing. eNotification is therefore generally addressed to eTendering Plattform Providers, Contracting Bodies, publishers, print shops, information brokers or monitoring or statistical services. eNotification can be carried out at various levels and between different levels (regional, state, European etc). The legal obligation of publishing notices at the correct level is the responsibility of the contracting bodies.

The content model of procurement notices in Europe is based on Commission Implementing Regulation (EU) 2019/1780 and upon Directive 2014/23/EU, Directive 2014/24/EU and Directive 2014/25/EU and their annexes, particularly the annex describing the standard forms to be used for the publication of procurement notices. eForms are at the core of the digital transformation of public procurement in the EU. Through the use of a common standard and terminology, they can significantly improve the quality and analysis of data. Well-implemented eForms increase the ability of businesses and other organisations to find opportunities. They will also reduce the administrative burden for buyers, increase the ability of governments to make data-driven decisions about public spending, and make public procurement more transparent.

eNotification covers the electronic transfer of electronic notices for publication and dissemination services. The publication of notices is executed between a contracting body or his representative and a publisher. CEN WS/BII 3 profiles BII14 Prior Information Notice (CWA 17026-102), BII10 Contract Notice (CWA 17026-101) and BII43 Contract Award Notice (CWA 17026-103) describe the exchange of notices between a contracting body or his representative and a publisher. In Peppol, these profiles are covered by the Peppol BIS P008 Publish Notice which provides electronic messaging support to publish a prior information notice, a contract notice or a contract award notice. Thus, Peppol BIS P008 Publish Notice helps contracting bodies to announce business opportunities and contract awards in public procurement procedures.

In the EU, eForms are used to publish notices above threshold on Tenders Electronic Daily (TED)—an online portal for public procurement notices from across the EU. On the national level public procurement decision makers can benefit from eForms through tailoring and defining a national approach to the various aspects of eForms, e.g. using them for contracts below thresholds, considering different policies and requirements.

The Peppol BIS P006 Search Notice supports a process by which a notification platform can be queried along a set of parameters to find relevant notices and related metadata required by other PEPPOL BISs. The profile is based on CEN WS/BII 3 Profile BII45 Search Notice (CWA 17026-104:2016). The transactions, specified in BIS P006 Search Notice are intended to be exchanged between eTendering systems and Publication Bodies but they can be adopted by many other actors. Since the P006 Search Notice provides access to Open Data, it also provides possibilities for the establishment of new business models that allow monitoring, the provision of statistical information or easy access for economic operators to business opportunities in different countries across different eTendering and eNotification platforms.

In order to execute the Peppol BIS P008 Publish Notice and Peppol BIS P006 Search Notice, it is necessary that the parties have Peppol eDelivery in place to enable them to send and receive the transactions in a secure way. Implementers must also support eForms Specifications content model because the transactions are based on the EU-wide eForms standard.

1.1.2. Tendering procedures

For the purpose of initiating electronic tendering via Peppol, the Peppol BIS P006 Search Notice plays a significant role. When the contracting body has published a notice, the interested economic operators who finds it may want to subscribe to this procedure by using PEPPOL P001 Procurement procedure subscription based on BII46 Subscribe to Procedure. Thereby, the Profile P006 Search Notice delivers necessary organisational and technical information to identify the procedure and contracting authority. This information is required because the request for procurement procedure subscription must be directed to the entity responsible for the procurement procedure.

eTendering can be put in place using different procedures, depending on the value and the type of the contract to be awarded, on the legal nature of the contracting body and on specific member state national legislation (Directive 2014/24/EU art. 26). Article 26 to 32 from Directive 2014/24/EU and article 43 to 50 from Directive 2014/25/EU describe the different tendering procedures that can be used by contracting bodies. For the purpose of electronic tendering, some of these procedures have been described in CEN WS/BII 3 BII37 Open Procedure (CWA 17027-106) and CEN WS/BII 3 BII39 Restricted Procedure (CWA 17027-108).

In open procedures, any economic operator can access the tender documents (including the call for tenders) and submit a tender before the time expires, without any previous assessment of their capabilities. In restricted and negotiated procedures and in a competitive dialogue the interested economic operators must submit a request to participate in order to be invited in the tendering process by the contracting body. When the contracting body has published a notice, the interested economic operators may subscribe (unscubsribe) to obtain (not obtain) tendering information using profile CEN WS/BII 3 BII46 Subscribe to Procedure (CWA 17027-111) covered by Peppol BIS P001 Procurement procedure subscription. Restricted and negotiated procedures require sending the invitation to tender (profile CEN WS/BII 3 BII52 Invitation to Tender (CWA 17027-117) to the identified candidates.

Once the interested economic operator has subscribed to an open procedure, the contracting authority provides the procurement documents by using Peppol BIS P002 Procurement document access. The BIS P002 is based on CEN WS/BII 3 BII60 Tender Status Inquiry (CWA 17027-123) and CEN WS/BII 3 BII47 Call for Tenders (CWA 17027-112) and provides the call for tender documents. It can be repeated at any time until the tender submission deadline to receive the latest version of the procurement documents. Additionally, contracting authorities must push updates to the economic operators that subscribed to a procedure.

Within the call for tenders, contracting authorities must inform economic operators how to qualify for the procedure. This may be done by an European Single Procurement Document (ESPD) defined by the Commission Implementing Regulation (EU) 2016/7 for which Peppol develops the BIS ESPD 3.0 based on the ESPD Exchange Data Model version 3.0. Additionally, call for tenders may include pre-award catalogue information to describe products and services in a common format allowing economic operators to send offers in a structured way and contracting authorities to evaluate products and services automatically through their tendering tools. The Peppol BIS pre-award catalogue can be used for this purpose and was defined according to the CEN WS/BII 3 Profile BII35 Advanced Tendering with Pre-award Catalogue.

Restricted and negotiated procedures require a previous qualification using profile CEN WS/BII 3 BII 49 Qualification (CWA 17027-114) covered by PEPPOL BIS P011 Qualification before submitting a tender. In restricted and negotiated procedures the contracting authority will send an invitation to tender using profile CEN WS/BII 3 BII52 Invitation to Tender (CWA 17027-117) to the identified candidates which have been selected to submit a tender. In contrast, those economic operators whose qualifications are being rejected are informed using profile CEN WS/BII 3 BII 51 Qualification Rejection (CWA 17027-116).

Once the economic operator has received the call for tenders or invitation to tender, it can use the Peppol BIS P004 Call for Tenders Questions and Answers for the business process of answering questions about a call for tenders. The BIS P004 is based upon CEN WS/BII3 profile BII48 Call for Tenders Questions and Answers (CWA 17027-113) and supports economic operators asking questions about call for tenders. Answers of the contracting authority then have to be sent to all economic operators that subscribed to the procedure and additionally the call for tenders should be updated and pushed to the subscribers of the procedure.

In case the economic operator decides to submit a tender, he can use the Peppol BIS P003 Tender Submission. After the submission of a tender, the contracting body notifies the economic operator of having received the tender. The BIS P003 is based upon CEN WS/BII3 profile BII54 Tendering (CWA 17027-119). On the contrary, economic operators can decide to withdraw a tender that was previously submitted by using the Peppol BIS P007 Tender Withdrawal. The BIS P007 was derived from CEN WS/BII3 profile BII53 Tender Withdrawal (CWA 17027-118) and provides electronic messaging support for the economic operator to withdraw a tender. The contracting body notifies the economic operator of having received the tender withdrawal. After the tender withdrawal, an economic operator may submit a new offer at any time before the tender submission deadline.

On the opening date, the contracting authority gathers and opens all received tenders. The opening board members can now evaluate the received tenders. If questions about specific offers arise during the course of the evaluation, they can be answered through the Peppol BIS P005 Tender Clarification. The BIS P005 supports the contracting authority to clarify questions on a tender which has been submitted. The BIS P005 was defined according to the requirements gathered by the CEN WS/BII3 profile BII50 Tender Clarification (CWA 17027-115).

At the end of the evaluation process, the contracting authority needs to inform the participating economic operators upon the results of the tender evaluation. For this purpose, contracting authorities can use the Peppol BIS P009 Notify Awarding which provides electronic messaging support to inform the bidders that a contract has been awarded to a particular economic operator. The BIS P009 is based upon the CEN WS/BII3 profile BII58 Notify Awarding (CWA 17027-121). The contracting authority can use BIS P009 to inform the winner(s) at the same time as they inform the unsuccessful tenderers and they must individually declare the reasons why they failed. The notification of the awarding decision imitated by BIS P009 shall also start the standstill period clock. After the stand still period, the contracting authority can finalize the contract with the winning supplier and also send a contract award notice using BIS Peppol BIS P008 Publish Notice.

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
Business Partner Description

Governmental or private organization

Any organisation.

Governmental organization

A body governed by public law, meaning bodies:

(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character;

(b) having legal personality; and

(c) financed, for the most part, by the State, regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities, or by other bodies governed by public law.
Table 2. roles
Role Description

Publication Body

A Pan-European, national or regional organisation that publishes procurement notices of a contracting body. While the basic role of the publisher may apply to any newspaper, other roles and functions are often restricted to official gazettes. These gazettes are also often responsible to ensure a formal verification of the notices in respect of legislative or other requirements in vigour. Official gazettes may also have the role to receive information exempted from publication (e.g. due to confidential content) used for notification to a supervising authority. I.e. eNotification also covers notification of authorities in the context of public procurement notices, e.g. for transparency and control reasons.

Contracting Body

The State, regional or local authorities, bodies governed by public law, associations formed by one or several of such authorities or one or more such bodies governed by public law, contracting Economic Operators for supply of goods, services or works. This term has a narrower scope than the term “Customer” and is in BII treated as a customer role.
usecasePN

1.3. Key examples

The following examples show use cases illustrating how the Profile P008 - "Publish Notice" 1.2 can be used.

1.3.1. Prior Information Notice

Example 1

A contracting body sends a request to publish a prior information notice, the notice concerns the delivery of one hundred personal computer and the installation of administrative software. The notice contains also details about the project such as the place of performance, the duration and the estimated value of the procurement. All information about the contracting body are included in the notice. If the reducing time limit indicator is checked, the contracting body indicates that a call for tender with a reduced delay for submitting bids will be published. The economic operator will see from the notice the estimated date of publication of the contract notice.

Example 2

A contracting body has a procurement project and publishes a prior information notice to inform economic operators about a business opportunity. The notice presents details about the project (text description, NUTS codes for location, CPV code for procurement items). If the call for competition indicator is checked, interested operators may inform the contracting authority about their interest in the contract.

1.3.2. Contract Notice

Example 3

A contracting body sends a request to publish a contract notice to the publication body. The publication body validates the notice. The notice concerns the delivery of one hundred personal computers and the installation of software. The notice contains also details about the project such as the place of performance, the duration and the estimated value of the procurement. All information about the contracting body are included in the notice. The publication body publishes the contract notice. Economic operators can see in the published notice, the address to access more information about the procurement project and the address to submit tenders or request to participate.

Example 4

A contracting body has a procurement project and publishes a contract notice to inform economic operators about the call for tenders. The notices present details about the project (text description, NUTS codes for location, CPV code for procurement items) and the procurement procedures (delay, award criterion, technical or financial capacities), so that economic operators can evaluate their interest in this business opportunity.

1.3.3. Contract Award Notice

Example 5

A contracting body has awarded a contract and publishes a contract award notice to inform economic operators about the winner of the call for tender. The notice presents details about the procurement procedures (delay, award criterion, number of candidates) and the awarded contract.

Example 6

A Dutch contracting body received several bids from different European countries. After having evaluated the tenders, he informs all tenderers (successful and non-successful) of the award decisions giving reasons for this decision. As the last step in the procedure the contracting body publishes the contract award notice on the Dutch procurement platform and Tenders Electronic Daily (TED).

1.4. Non-functional requirements

For the Peppol BIS all Peppol non-functional requirements are applicable as documented in CEN WS/BII 3

• BII Profile 14 - Prior Information Notice (CWA 17026-102:2016)
• BII Profile 10 - Contract Notice (CWA 17026-202:2016)
• BII Profile 43 - Contract Award Notice (CWA 17026-103:2016).

Implementers must comply to these requirements.

Req. ID Requirement statement

br10-001
br14-001
br43-001

A contracting body may directly or indirectly via another submitter request the publication or an appropriate processing of some notice in an information medium, operated by a publication body.

br10-004
br14-004
br43-004

The publication body may request the contracting body to correct the notice if it does not comply with regulations or rules that apply.

br10-005
br14-005
br43-005

The publication body may itself correct small (e.g. typographic) errors.

br10-006
br14-006
br43-006

The contracting body requires the publication body to inform him of the status of his notice.

br10-007
br14-007
br43-007

The publication body may provide publication status information to the contracting body.

br10-010
br14-010
br43-010

The publication body treats the modification or cancellation as a separate publication request.

1.5. Interoperability

The PEPPOL eTendering BIS structure is based on the European Interoperability Framework.

It applies the Framework as follows:

  1. Legal Interoperability

  2. Organizational interoperability

    • Organization (Organization/Business):

    • Organization (Process):

      • PEPPOL eTendering BIS support a set of “common business processes” that are assumed to be supported by most enterprises whether public or private. These are processes that are used widely or understood as being relevant for most companies.

      • The current scope of the PEPPOL eTendering BIS and guidelines include processes that support the main flow of open procedures such publication of notices, search of notices, calls for tenders, tenders and awarding notifications. During these processes additional support processes may be executed between contracting bodies and economic operators, such as procurement procedure subscription, call for tenders’ questions and answers, tender withdrawal or tender clarifications.

      • The BIS Pre-Award Guide for Notification and Open Procedure describes the choreography to execute open procedures using Peppol. Thus, the Notification & Open Procedure Guideline is a procedural specification. The guideline does not define individual transactions but it refers to Peppol several BISs and underlying standards, in which the transactions and the transaction information requirements are listed and defined. Even though the guideline is based on a set of PEPPOL BISs, its contents are derived from the agreement BII37 Open Procedure of the CEN Workshop on Business Interoperability Interfaces for Public Procurement in Europe .

  3. Technical interoperability

2. Business process

The BPMN diagram shows the choreography of the business process implemented by the Profile P008 - "Publish Notice" 1.2. The choreography of business collaborations defines the sequence of interactions when the profile is run within its context.

processPN

The process starts with the contracting body issuing a new publication notice. At first, they have to choose the appropriate UBL document schema of the underlying notice (PIN, CN or CAN) which needs to be formatted according to the eForms Specifications. After that, the publication request will be prepared and send to the publication body. Transaction 'T015 - Publish Notice' is used for the message to the publication body. The publication request can either be made with the intention to publish the notice or it can be sent to the publication body for validation purposes only.

Upon receipt of the publication request, the publication body validates the received T015 message. In case of negative validation results with critical errors, the publication body sends back a negative notice publication response to the contracting body and informs it of the underlying validation errors. Transaction 'T016 - Notice Publication Response' is used for the negative response message to the contracting body. In this case, the contracting body may decide to correct the errors and submit a new publication request.

In case of validation without critical errors, the publication body returns a positive notice publication response to the contracting body. In the reply to the notice, the publication authority differentiates between notices without warnings (status = 'accepted') and notices with warnings (status = conditionally accepted). The underlying warnings are in turn flagged in the response. Transaction 'T016 - Notice Publication Response' is used for the positive response message to the contracting body. If the contracting body has only requested the validation of a notice, the process stops at this point. The contracting body may decide to review eventual warnings and/or re-submit the notice with the intention to publish it.

If the contracting body has requested the publication of a notice, the publication body will, in the case of a positive validation result (status = 'accepted' or 'conditionally accepted'), inform the contracting body about the planned publication date of the notice. Transaction 'T016 - Notice Publication Response' is used for the positive message to the contracting body announcing a publication date. A change of the notice can then only be made by resubmitting the notice with a new version number.

At the time of publication of a notice, the publication body sends a confirmation to the contracting body containing the actual status 'published' and its publication date. Again 'T016 - Notice Publication Response' is used for the response message to announce the effective publication date and status.

Table 3. Business process
Category Description

Description

A contracting body requests a publication body to publish or test the validity of a prior information/ contract notice/ contract award notice. The publication body assesses the request and may ask for corrections. When the notice to be published meets the criteria, the publication body may indicate a planned publication date. The publication body affirms the publication date at the time of publication.

Pre-conditions

The contracting body prepared a prior information notice / contract notice / contract award notice according to eForms Specifications.

Post-conditions

The prior information notice / contract notice / contract award notice is published or tested.
Table 4. Role description
Activity Role involved Description

Prepare publication request

Contracting body

The contracting body prepares a publication request

Send publication request

Contracting body

The contracting body sends the request to publish the notice to the publication body

Receive publication request

Publication body

The publication body receives the publication request

Assess publication request

Publication body

The publication body assesses the validity of the publication request

Send publication request rejection notification

Publication body

If the request is not valid, the publication body rejects it and suggest corrections of the request to the contracting body.

Receive publication request rejection notification

Contracting body

The contracting body may receive a publication request correction.

Prepare publication request correction

Contracting body

The contracting body may prepare a new (corrected) request.

Send publication request acceptance notification

Publication body

If the request is valid, the publication body sends an acceptance confirmation that may indicate the planned publication date and remaining warnings.

Receive publication request acceptance notification

Contracting body

The contracting body receives an acceptance confirmation that may indicate the planned publication date and remaining warnings.

Publish notice

Publication body

If the request was accepted and a publication was requested by the contracting body, the notice is published

Send publication request publication notification

Publication body

The publication body sends an publication confirmation that indicates the effective publication date.

Receive publication request publication notification

Contracting body

The contracting body receives an publication confirmation that indicates the effective publication date.

3. Implementation guidelines

Profile P008 - "Publish Notice" 1.2 is based on work done by CEN WS/BII 3 and eForms. Business terms, Business rules and code lists used are inherited from eForms Specifications, OASIS ebXML RegRep Version 4.0 (RegRep), UBL 2.2 and UBL 2.3 documents and the following CEN WS/BII 3 specifications:

• BII Profile 14 - Prior Information Notice (CWA 17026-102:2016)
• BII Profile 10 - Contract Notice (CWA 17026-202:2016)
• BII Profile 43 - Contract Award Notice (CWA 17026-103:2016)

The namespaces used in the Profile P008 - "Publish Notice" 1.2 are:

  • urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0

  • urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0

  • urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2

The namespaces used in the eForms schemas are:

  • urn:oasis:names:specification:ubl:schema:xsd:PriorInformationNotice-2

  • urn:oasis:names:specification:ubl:schema:xsd:ContractNotice-2

  • urn:oasis:names:specification:ubl:schema:xsd:ContractAwardNotice-2

The T015 - Publish Notice transaction is based on Registry Information Model (ebRIM) and adapted according to the SubmitObjects Protocol of Services and Protocols (ebRS) for ebXML RegRep. The package consists of notice and notice metadata defined along business terms described by eForms Specifications and BII Profile 10, BII Profile 14, BII Profile 43. A local reference in the notice metadata points to the actual XML notice contained within the ASiC-E Container as defined by BIS eDocuments guide for pre-award. Notices must be defined in XML format along the following standards:

The T016 - Notice Publication Response is based on UBL Application Response Schema and the response message described in BII Profile 10, BII Profile 14, BII Profile 43.

The business processes includes 2 transaction:

4. PEPPOL identifiers

PEPPOL has defined a Policy for Using 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.

4.1. Profile identification

All transactions within this profile uses the following profile identifier

The value of the Element cbc:ProfileID for all transactions of this profile must be urn:fdc:peppol.eu:prac:bis:p008:1.2

4.2. Specification identification

In the table below you will find the values to be used as the specification identifier (Element cbc:CustomizationID) for the different transactions of this profile.

Table 5. Specification identifiers for the transactions
TransactionID Transaction name Short Description Element cbc:CustomizationID

T015

Publish Notice

The requester sends a Publish Notice Request to the publisher.

urn:fdc:peppol.eu:prac:trns:t015:1.2

T016

Notice Publication Response

The publisher sends a Notice Publication Response to the requester.

urn:fdc:peppol.eu:prac:trns:t016:1.2
For implementers, please note that the process identifiers in the document instance MUST correspond to the SMP process identifier.

5. Revision history

Version Date Author Organization Description

0.1

2021-05-12

Felicia Tsakonas

adesso SE

First draft

0.2

2021-06-14

Felicia Tsakonas

adesso SE

Gathered information from given profiles

0.3

2021-06-24

Ansgar Mondorf

University of Koblenz-Landau

Final Review of Profile, Inclusion of Process descriptions, Description of Implementation Guideline

0.4

2021-07-21

Felicia Tsakonas

adesso SE

Creation of Transactions and Syntax Mapping for T015 and T016

0.5

2021-07-23

Ansgar Mondorf

University of Koblenz-Landau

Final Review of Transactions and Syntax Mapping for T015 and T016

0.6

01-03-2023

Ansgar Mondorf

Mondorf IT

Final editorial review for March Release 2023: Update Version information, links & examples, editorial improvements, change of transaction structure

6. Contributors

Country Name Organization

DE

Ansgar Mondorf

Mondorf IT / University of Koblenz-Landau

DE

Rolf Kewitz

Beschaffungsamt des BMI

DE

Felicia Tsakonas

adesso SE