Abstract

BIS 41 - European Single Procurement Document was developed on the basis of the CEN BII Profile 41 and the ESPD EDM specifications of DG GROW. This document is concerned with the ESPD version 2.1.0 and  provides a set of specifications for implementing an ESPD and VCDThe document is concerned with clarifying requirements for ensuring interoperability of the qualification process in pan-European Public eProcurement and provides guidelines for supporting these requirements and how to implement. The purpose of this document is to describe a common format for the message exchange of electronic qualifications and to facilitate an efficient implementation. The document is accompanied by the ESPD EDM v202 Domain Vocabulary (TO BE UPDATED) which structures ESPD/VCD concepts and provide support for developers that are implementing ESPD and VCD services. The BIS 41 for ESPD version 1.0.2 which was developed in the eSENS project can be found hereThe BIS 41 for previous ESPD versions developed in the ESPDint project are available for versions 2.0.0, 2.0.1 and 2.0.2.

Statement of Copyright

This 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 projects like eSENS and ESPDint to establish this BIS, detailing and adding further guidance on the use of BII profiles. 
ESPDint customizations have been made according to version 2.1.0 of the ESPD Exchange Data Model and the ESPD Response XML Instantiation Guide (TO BE UPDATED) published by DG Grow. Corresponding conformance with the ESPD XML Instantiation Guide is and explicit goal enabling for the purpose of national implementations of this BIS. This BIS document may not be modified, re-distributed, sold or repackaged in any other way without the prior consent of ESPDint, CEN and DG Grow.


Table of Contents

Introduction to the ESPD BIS

This BIS is a result of work within ESPDint collaborating with actors like CEN and DG Grow. The ESPD BIS 41 provides a business oriented perspective on version 2.1.0 of the ESPD Exchange Data Model and provides a set of specifications for implementing an ESPD or VCD. The document is concerned with clarifying requirements for ensuring interoperability in electronic qualification transactions like the ESPD and the VCD. It provides guidelines on how to support these requirements and how to implement the ESPD and VCD in accordance with CEN BII profile 41 and the ESPD specifications version 2.1.0 of DG Grow. Both specifications are the underlying bases for this work. The purpose of the BIS 41 is to have an aggregated list of all concepts that occur in the domain of the ESPD and VCD and to provide a syntax bindings for the ESPD request and ESPD resonse transactions. The BIS 41 contains all the information elements of the electronic business transactions exchanged in the qualification domain by pointing to a given semantic data model for each of the business transactions. A syntax binding of the semantic data model to the corresponding UBL 2.2. syntaxes (QualificationApplicationRequest and QualificationApplicationRequest) used for the EDM v2.1.0 is given. Additionally, the BIS 41 also lists the business rules (including the use of code lists and identifiers) that govern and constrain the execution of business process(es) and its business transactions. Hence, it shall serve the need for documenting the ESPD/VCD concepts and provide support for developers that are implementing ESPD/VCD software to decide how to represent and collect values for a concept. This BIS 41 is accompanied by the ESPD EDM v201 Domain Vocabulary (TO BE UPDATED) reflecting the same contents of this document in a spread sheet format. Additionally, the ESPD and VCD Domain Vocabulary contains a mapping between the concepts used in ESPD EDM v1.0.2 and those used in ESPD EDM v2.1.0 transactions. 

Scope

BIS 41 - European Single Procurement Document (ESPD) describes a process providing electronic messaging support for requesting and providing an ESPD and VCD. As stated in Art. 59 of the directive 2014/24/EU of the European Parliament and of the Council, the ESPD is a self-declaration of a company’s formal status, financial status, abilities and suitability aimed to streamline and structure online interaction between Contracting Authorities (CA) and Economic Operators (EO). Economic Operators no longer have to provide full documentary evidence and different forms to prove that they fulfil the exclusion and selection criteria of a tender. Now, companies are able to self-declare these criteria with a single ESPD form. The actual documents will only have to be provided by the winner of the tender using the Virtual Company Dossier (VCD).  Both, ESPD and VCD allow buyers and suppliers to handle the entire qualification processes in public tenders electronically. 

This BIS principally supports the implementation of both, the ESPD and the VCD. The ESPD and VCD refer to the same elements and data models for the request and response transactions. Differences between the ESPD and VCD are not found on the conceptual level but on the process level. While the ESPD is a self-declaration by economic operators providing preliminary evidence, the VCD is a means to deliver the certificates and evidentiary documents issued by public authorities or third parties. Thus, the ESPD is used in the business process of tendering in a pre-awarding phase while the VCD is used along the awarding phase as well as in post-award procedures where the contracting body requires the economic operator to renew the proof of qualification. The difference in how to implement the VCD relates to the arrangement of certificates and evidences. The VCD therefore uses an additional eSENS Architecture Building Block (ABB) for Document Packaging. The ABB for Document Packaging is used to arrange and sign the different evidences (e.g. pdf, xml, jpg, vsd, etc.) which are associated to a VCD business document. The ABB for Document Packaging is implemented using an ASIC Container based on ETSI TS 102 918 V1.1.1. The use of it is further described in the eDelivery Guideline. From these differences the following differences on the data can be summarized:

  • The ESPD is used in the pre-awarding phase
  • The VCD is used along the awarding phase as well as in post-award procedures
  • The ESPD uses self-declarations or references to documents on a remote location
  • The VCD uses references to data objects which are physically allocated in an ASIC Container (TO BE UPDATED - use of ZIP instead of ASiC).

In the further course of this document no explicit differentiation between the ESPD and VCD will be made. The BIS 41 soley references to the ESPD and its transactions even though it can be used to implement the VCD transactions as well. The previous version of this BIS (which was based on the ESPD EDM v1.0.2) formally distinguished between the ESPD (BIS 41) and a VCD (BIS 56). Since the new ESPD EDM versions 2.0.0, 2.0.2 and 2.1.0 cater for all requirements needed by the VCD, a generalised qualification profile may be established in the future. However, this decision is not made yet and should be discussed in the corresponding standardization organizations maintaining the structure of eProcurement transactions. The ESPD/VCD transaction are not used in isolution but should refer to other eProcurement transactions like the call for tenders or submit tender. In case a Member State has established a legal prequalification procedure, the ESPD and VCD may additionally refer to the legal prequalification requirements. According to these assumptions, the profile may be used by:

  • Contracting bodies to create an ESPD/VCD request that is issued together with a call for tender. 
  • Contracting bodies to request an ESPD/VCD response of an economic operator. Likewise, an economic operator or subcontractor within a consortium may be requested by its main contractor to provide an ESPD/VCD response. 
  • Economic operators to request from a service provider (e.g. prequalification agency) to assemble an ESPD/VCD response (e.g. for a given ESPD/VCD request or prequalification procedure).
  • Economic operators to qualify with an ESPD/VCD response for call for tenders exectured in open or restricted procedure. 
  • Contracting bodies to evaluate the qualifications of economic operators using retrieved ESPD/VCD responses.   

The open procedure is described in profile BII37, the restricted procedure in profile BII39.
This profile is identified in the transactions by the ProfileID urn:www.cenbii.eu:profile:bii41:ver3.0

Goals

The main business benefits to be gained by implementing this profile are:

ID

Description

G41-001

The ESPD allows the contracting body to install a systematic qualification process, with considerable simplification for the benefit of both contracting authorities and economic operators.

G41-002

Economic operators can automatically generate an ESPD with the support of an ESPD service according to the criteria set out in a call for tender.

G41-003

Main contractors can easily request subcontractors or partner contractors in consortia to provide their ESPDs.

G41-004

The ESPD allows for a semi-automated and simple process to prove qualification of economic operators in tendering procedures through self-declarations.

Table 1: Goals

Business environment

Introduction

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 EU directives, mentioned in section 5 of this profile.
The transactions, specified in this profile 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 portals, 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.

Tendering procedures

Individual pre-award processes 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). 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 subscribing for interest and 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 to obtain tendering information using profile BII46. Negotiated procedures require sending the invitation to tender (profile BII52) to identified candidates.
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 BII profiles BII37 (open procedure) and BII39 (restricted procedure). These profiles are included in CWA 3456 parts 106 and 108.
Official notification through publishing bodies is part of many procedures. eNotification covers the electronic transfer of electronic notices for publication and dissemination services with the ultimate aim of opening market opportunities. Profiles BII14 Prior Information Notice, BII10 Contract Notice and BII43 Contract Award Notice describe the exchange of a notice between a contracting body or his representative and a publisher. Profile BII61 describes the exchange of notices between publishers. The process by which notices can be searched for on a given platform are described in profiles BII62 Exchange of Notice Metadata and BII45 Search Notices. These profiles are included in CWA 2345.

Requirements

High Level Business Requirements

Req. ID

Requirement statement

Ref. to goal

br41-001

The ESPD must be linked to a tendering process in order for the contracting body to be able to handle the ESPD and to evaluate the qualification of the economic operator.

G41-001

br41-002

The contracting body shall provide the exclusion grounds and selection criteria for its tendering process as structured information – via ESPD template or structured list of criteria set out in a call for tender.

G41-001
G41-002

br41-003

The contracting body requests from the economic operator or a set of economic operators along a tendering process to submit the ESPD.

G41-001

br41-004

An ESPD must enable identifying the candidate as one economic operator or a set of economic operators and their roles

G41-001

br41-005

The economic operator shall generate the ESPD (semi)automatically and provide it to the contracting authority as structured information using this profile. Along this, the economic operator may be able to reuse as much information from the ESPD template or call for tender qualification information as possible when elaborating the ESPD. This requirement very much relies on the alignment of call for tenders and ESPD data models.

G41-001
G41-002

br41-006

The economic operator shall provide the ESPD as structured information to enable the contracting body to automatically check the non-existence of exclusion grounds and fulfilment of qualitative selection criteria.

G41-001
G41-004

br41-006

An economic operator shall be able to ask its contractors in a consortium or subcontractors to provide their ESPD to her/him using this profile

G41-003

br41-007

The ESPD shall contain an URL and relevant access credentials to a national database, from where the evidentiary documents along the ESPD can be retrieved by the contracting body.

G41-004
G41-002

Table 2: High Level Business Requirements

Key Examples

Example 1

A contracting body from Germany using the eTendering platform e-Vergabe starts to prepare a tendering procedure, because it wants to buy goods from any European supplier. First, it starts to prepare the relevant documents in particular the tender notice and call for tender in any local format (e.g. x-Vergabe9. As part of this process, the contracting body specifies the qualification criteria in the form of a structured ESPD Template, according to pre-defined codes, which need to be proven by economic operators applying for the contract. The contracting body adds the standardised qualification criteria to the tender notice and/or call for tender, or it includes the ESPD Template as an attachment to the previous.
After having searched for interesting call for tenders across Europe, having received an invitation to the call for tender, or having received a notification from a platform where the economic operator is subscribed to (e.g. TED), an economic operator from the Netherlands subscribed interest (using TenderNed as his or her tendering platform to prepare the bid) and received the tender documents, including qualification criteria. In this ESPD profile, the most relevant document received is the call for tender including the list ofqualification criteria (as part of the call for tender itself or as attached ESPD Template). The list of qualification criteria is received in a standardized, structured format. Besides preparing the content of the tender in the tendering platform (e.g. TenderNed), the economic operator opens the ESPD Template received and creates the standardized form confirming that he/she fulfils all qualification criteria. The economic operator inserts the finalized ESPD in the Tender Offer and submits it together with the offer to e-Vergabe (using TenderNed as his/her client). The contracting body receives the offer in e-Vergabe, including the ESPD.

Example 2

Along the procedure described in Example 1, the economic operator is not a single tenderer. He / she bids in a consortium and has a subcontractor him- or herself. Hence, the economic operator as main contractor sends a request from his TenderNed client to the German subcontractor to provide the ESPD for the tender. The German subcontractor receives the request via DE-Mail. Furthermore, the economic operator sends a request from his TenderNed client to the Austrian, Italian and Greek partner contractors via eDelivery channels to provide their ESPDs for the tender. 
The German subcontractor, being located in Berlin, logs in to the ESPD service provider portal of Auftragsberatungsstelle Brandenburg e.V. He uploads the ESPD template received, fills and signs the ESPD using the ESPD service there, and retrieves the filled and signed ESPD from the portal via download. Afterwards, he sends the ESPD to the main contractor's tendering client (TenderNed) via DE-Mail. 
The Austrian partner contractor contacts ANKÖ to generate the ESPD. He uploads the ESPD template received, fills and signs the ESPD using the ANKÖ ESPD service, and sends from ANKÖ's portal the ESPD to the TenderNed client of the main contractor.
The Italian economic operator uses the ESPD service of the European Commission (DG-GROW) to generate the ESPD. He uploads the ESPD template to the portal and fills the data. Then he retrieves the filled ESPD and sends it via eDelivery to the Dutch main contractor.
The Greek economic operator uses the Greek ESPD service which works similar to the German one as described before. To deliver the ESPD to the Dutch economic operator, he uses the eSens eDelivery service.
Finally, the Dutch economic operator adds all received ESPDs to the bid in the bidder client of TenderNed and submits the bid using eSubmission profiles of BII, where the ESPDs of all consortium members and subcontractors are included as attachment.

Example 3

The scope of the scenario is a combination of example 1 and example 2. However, the contracting body uses a two-stage procedure. The contracting body makes the same preparations as described in 3.2.1, except that the procedure is different. 
The economic operator, as in example 1, subscribes to the procedure and receives the ESPD template. As it is a two-stage procedure, only the submission of the ESPD is required. Accordingly, he requests ESPDs of his consortium partners and subcontractors, and uses TenderNed to fill in his own ESPD – see the details described in example 2. Finally, the economic operator as main contractor submits the package of ESPDs from his TenderNed client via eDelivery to e-Vergabe.

Profile detailed description

Business processes in scope

Procurement is a complex domain with several key processes, some of which are illustrated in the following figure. 

Figure 2— Procurement 
The ESPD profile is realizing the ESPD process, as highlighted in the above figure. The ESPD process is part of the qualification process in the pre-awarding process area.

Parties and roles involved

The following parties participate as business partners in this profile, acting in the roles as defined below.

Party

Description

Governmental or private organisation

Any organisation

Table 3: Parties

Role

Description

ESPD requester

An organisation that requests the ESPD of an economic operator or of a service provider.

ESPD provider

An economic operator or a service provider providing an ESPD.

Table 4: Roles

Figure 3 — ESPD process

ESPD Process

The following diagram shows the choreography of the business process implemented by the profile. The choreography of business collaborations defines the sequence of interactions when the profile is run within its context. 

Figure 4 — ESPD business process


Category

Description

Description

The ESPD requester requests an ESPD from the ESPD provider. The ESPD provider prepares the ESPD and sends it to the ESPD requester.

Pre-conditions

The ESPD requester needs an ESPD.

Post-conditions

The ESPD has been provided to the ESPD requester.

Table 5: ESPD business process

Activity

Role involved

Description

Send ESPD template

ESPD requester

The ESPD requester requests an ESPD from the ESPD provider. The request includes a template with a specification of the information that needs to be present in the ESPD.

Prepare ESPD

ESPD provider

The ESPD provider prepares the ESPD, based on the template.

Send ESPD

ESPD provider

The ESPD provider sends the ESPD to the ESPD requester.

Table 6: ESPD Activites

ESPD Request transaction (Trdm070) 

Overview: ESPD request transaction (Trdm070)

Categories

Description and Values

Identifier

Trdm070

CustomizationID

urn:www.cenbii.eu:transaction:biitrdm070:ver3.0

Description

A structured electronic business document for requesting qualification information through an European Single Procurement Document (ESPD) (conform to an ESPD request). Directive 2014/24/EU, Art. 59.

Partner Types

Customer
Supplier

Authorized Roles

Contracting body
Economic operator

Initial Event

The contracting body publishes the ESPD request as part of the Call for Tender documents.

Terminal event

The economic operator receives and processes the ESPD request.

Scope

Open and restricted tendering procedures, with a focus on implementing the simplification in tendering procedures above threshold according to directives 2014/24/EU and 2014/25/EU.

Boundary

Trdm070

Table 7: Overview ESPD request transaction (Trdm 070)

Business Requirements: ESPD request transaction (Trdm070)

General

ID

Requirement

tbr070-002

The ESPD request shall be identified and dated. The time of issue should be stated and it should be indicated whether the document is a copy. The UBL version and the ESPD version, the ESPD specification and the transaction should be identified as well.


Contracting body

ID

Requirement

tbr070-001

The contracting body must be identified, hence information about the party is required, such as party name, identification, endpoint id-, buyer profile  and country- .

tbr070-006

The qualification document should contain contact information of the contracting body: Postal address, telephone number, fax number, e-mail address, contact person(s).

tbr070-005

The contracting authority must be able to provide the CPV codes in the ESPD request.


Call for tenders

ID

Requirement

tbr070-007

The ESPD request must contain the object of the contract, its name, a despription, the type of procedure, the type of procurement project and the applied CPV codes as well as a reference to the call for tenders, i.e. the procurement project ID or notice ID (PIN, CN, and CAN), which defines the requirements (i.e. criteria) for which this document is created and submitted by the economic operator. It must be possible to maintain this information in order to keep track of the connection between ESPD request and call for tenders/notices.


Procurement lots

ID

Requirement

tbr070-008

The ESPD request may contain information about the procurement lots defined in a call for tender and indicate for each tendering criterion what lots are related to it. The contracting body shall also set the minimum yearly turnover that economic operators are required to have if they tender for more than one lot. In this case, the contracting body shall provide a reference to the group of lots of the call for tender, to which the minimum turnover applies (art. 58 of 2014/24/EU).


List of Criteria

ID

Requirement

tbr070-003
The contracting authority must be able to define the particular requirements that apply to selection criteria regarding Suitability.

tbr070-009

The ESPD request must contain information about the criteria that set the exclusion grounds as stated in directive 2014/24/EU Art. 57 and referred to in directive 2014/25/EU Art. 80 and/or according to national legislation.

tbr070-010

The ESPD request must contain information about qualitative selection criteria as stated in directive 2014/24/EU Art. 58 and 2014/25/EU Art. 80 and/or according to national legislation.

tbr070-004

The contracting body must be able to indicate, which criteria for exclusion grounds and qualitative selection specific types of economic operators (e.g. subcontractors or partners in consortia) need to declare.

tbr070-013

The ESPD request shall provide criteria of exclusion grounds and of qualitative selection in a structured way, i.e. grouping the criteria along the criteria groups as put forward in the directive 2014/24/EU. Additional information for each criterion may be provided such as: Legal reference (EU level, contracting body national level, economic operator national level), type of criterion (e.g. technical capability, financial standing, etc.) or specific requirements for natural persons as settled in Art. 67-69 of directive 2014/24/EU. This information is provided by the contracting body, who includes the information from the call for tenders or it is automatically/directly imported from the call for tenders.

tbr070-015

The ESPD must provide information about thresholds regarding unpaid taxes or social security obligations.

tbr070-016

The contracting authority must be able to provide information about weighted criteria.

tbr070-017

Information about weighted criteria provided by the contracting authority must be displayed to the economic operator.

tbr070-018

Several selection criteria must be displayed only for a particular type of contract.

tbr070-019

The contracting authority must be able to provide information about the applicable periods for qualification criteria


ESPD service provider

ID

Requirement

tbr070-011

The ESPD request may contain information of identification regarding an ESPD service provider: Name, Party Identification, Endpoint ID, Website, Country.


Additional documentation

ID

Requirement

tbr070-012

The ESPD service provider may be able to provide complementary information such as liability statements.


Versioning

ID

Requirement

tbr070-014

The ESPD should allow to include a Version ID and a Previous Version ID to the ESPD. Both help to identify the status of subsystems that have supported the creation of the ESPD. The Previous version ID is needed to trace changes that have occurred.

Data Model for regulated ESPD: ESPD request transaction (Trdm070)


Figure 5: ESPD request data model (regulated ESPD)

Data Model for self contained ESPD: ESPD request transaction (Trdm070)

Figure 6: ESPD request data model (self-contained ESPD)

Implementation Guideline: ESPD request transaction (Trdm070)

This guideline explains how to use the UBL 2.2 syntax or the QualificationApplicationRequest to implement ESPD-EDM version 2.1.0 to support the CEN BII information transaction requirements. It provides the syntax mappings from the UBL syntax to the ESPD request transaction (Trdm070). It also provides specific details for each class and information element and provides guidelines, rules and examples on how to produce conformant XML documents. Additionally, the difference between Regulated and Self-Contained ESPD version is description in the column "Used in Reg". The tables can be also downloaded here as excel files as part of the ESPD EDM v202 Domain Vocabulary (TO BE UPDATED).

InfReqID

Used in Reg

Card

Business term

Description

Data Type

BusReqID

Syntax Binding (UBL Path)

Vocabulary term

Implementation Guideline

Business Rule IDs

 


 

ESPD Request

A structured electronic business document for requesting qualification information through an ESPD (conform to an ESPD template). Directive 2014/24/EU, Art. 59.

 

 

QualificationApplicationResquest

Qualification Application Request. Details



tir070-001

x

1..1

Document identifier

Identifier of the document assigned by the sender

Identifier

tbr70-002

cbc:ID

Qualification Application Request. Identifier

Rule: An identifier for this document, assigned by the sender. Compulsoriness inherited from UBL-2.2. Do not forget to specify the schemeAgencyID attribute to identify the organisation responsible for the document.Reg: -
SC: -
Common:
BR-OTH-02

tir070-002

x

1..1

Document issue date

Date when the referred document was issued.

Date

tbr70-002

cbc: IssueDate

Qualification Application Request. Issue Date. Date

Comment: compulsoriness inherited from UBL-2.1.
Is set at the compilation time. Use XSD Date (format "YYYY-MM-DD")

tir070-003

x

0..1

Document issue time

Time when the document was issued.

Time

tbr70-002

cbc: IssueTime

Qualification Application Request. Issue Time. Time

Comment: Is set at the compilation time. Use XSD time (format "hh:mm:ss")

tir070-004

 

0..1

Document version identifier

The version identifying the content of this document

Identifier

tbr70-014

cbc: VersionID

Qualification Application Request. Version. Identifier

Changes in content should entail the modification of the version identifier and a reference to the previous version.


tir070-526 0..1Previous document version identifierThe version identifying the previous modification of the content of this document.Identifiertbr70-014cbc:PreviousVersionIDQualification Application Request. PreviousVersionID. Identifier

tir070-527 0..1Procedure codeThe type of the procurement administrative procedure according to the EU Directives.Codetbr070-007cbc:ProcedureCodeQualification Application Request. ProcedureCode. CodeRule: Compulsory use of the code list ProcedureType (values: Open, Restricted, Accelerated, Competitive dialogue, etc.). Do not confound with the object of the procurement project (code list ProjectType: Works, Supplies, Services). Compulsory use of attributes listID, listAgencyName and listVersionID.Reg: -
SC: BR-SC-10#2, BR-OTH-03, BR-OTH-01, BR-OTH-01#1
Common: 

tir70-005

x

1..1

Reference number

An identifier that is specified by the buyer and used as a reference number for all documents in the procurement project. It is also known as procurement procedure identifier, procurement reference number or contract folder identifier. A reference to the procurement project to which this Qualification document is delivered as a response.

Identifier

tbr70-007

cbc: ContractFolderID

Qualification Application Request. Contract Folder Identifier. Identifier

Rule: This is a mandatory data provided by the Contracting Authority or the sender, for the process file (i.e., record) to which this document belongs. Try always to use the reference number issued by the contracting authority. This number in combination with a registered contracting authority ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.Reg: BR-REG-10
SC: BR-SC-10
Common: - 

tir70-500

 

1..1

Document universally unique identifier

A universally unique identifier for an instance of this document.

Identifier

tbr70-002

cbc:UUID

Qualification Application Request. UUID. Identifier

Rule: A universally unique identifier for an instance of this document. Use UUID version 4.Copies of a document should be identified with a different UUID. Compulsory use of schemeAgencyID attribute.Reg: -
SC: BR-OTH-02
Common: 

tir70-501

 

1

ESPD request type code

A code specifying the type of ESPD

Code

tbr70-002

cbc: QualificationApplicationTypeCode

Qualification Application Request. QualificationApplicationTypeCode. Code

Rule: Compulsory use of the codelist QualificationApplicationType (Regulated, Self-contained). Compulsory use of attributes listID, listAgencyName and listVersionID Reg: -
SC: BR-OTH-01, BR-OTH-01#2, BR-OTH-03
Common: 
tir070-322
0..nWeight scoring methodologyFree-form text to describing information about Weight Scoring MethodologyTexttbr070-016cbc:WeightScoringMethodologyNoteWeightScoringMethodologyNote. TextRule: Used for transparency motives. Provide a text explaining clearly the method that will be used to select those selection criteria that will be weighted.Reg:
SC: BR-2P-10
Common:
tir070-323
0..1Weighting type codeA code specifying the type of the Weighting.Codetbr070-016cbc:WeightingTypeCodeWeightingTypeCode. CodeRule: Compulsory use of the code list `WeightingType`. If this element it is not instantiated and one or more selection criteria are weighted the type defaults to `NUMERIC`.Reg:
SC: BR-2P-10
Common:

tir070-301

x

0..1

Copy indicator

Indicates whether this document is a copy (true) or not (false)

Indicator

tbr70-002

cbc: CopyIndicator

Qualification Application Request. Copy_ Indicator. Indicator

Comment: It is a good practice to use the CopyIndicator component if the same document is forwarded several times to the same or to different destinations. Use it in combination with the UUID identifier: copies of an ESPD document should be identified with distinct UUIDs.

 


1..1

Process control

A group of business terms providing information on the business process and rules applicable to the document.

 

 

 

 

 


tir070-006

x

1..1

Business process type identifier

Identifies a user-defined customization of UBL for a specific use. ESPD use the current version of the ESP-EDM 2.0.0

Identifier

tbr70-002

cbc: CustomizationID

Qualification Application Request. Customization Identifier. Identifier

Rule: For the ESPD we use the value “urn:www.cenbii.eu:transaction:biitrdm070:ver3.0”. Compulsory use of the value "CEN-BII" for the schemeAgencyID attribute.Reg: -
SC: -
Common:
BR-OTH-02
BR-OTH-06

tir070-007

x

1..1

Specification identification

An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. The identification may include the version of the specification as well as any customizations applied.

Identifier

tbr70-002

cbc: ProfileID

Qualification Application Request. Profile Identifier. Identifier

Rule: Applied BII Profile: Use the value "41" for ESPD. Use also "CEN-BII" for the scheme AgencyID attributeReg: -
SC: -
Common: BR-OTH-07, BR-OTH-02
tir070-299x1..1ESPD version identifer

Identifies the specific ESPD-EDM version (e.g.: ESPD-EDMv1.0.2; ESPD-EDMv2.0.0; ESPD-EDMv2.0.1 or ESPD-EDMv2.0.2)

Identifertbr70-002cbc:ProfileExecutionIDQualification Application Request. ProfileExecutionID. IdentifierRule: Compulsory use of the Code List "ProfileExecutionID".Reg: -
SC: -
Common: BR-OTH-01, BR-OTH-01#13, BR-OTH-03

tir070-302

x

0..1

UBL version identifier

Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance.

Identifier

tbr70-002

cbc:  UBLversionID

Qualification Application Request. UBL Version Identifier. Identifier

Rule: Use the value "2.2". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.Reg: -
SC: -
Common: BR-OTH-05, 2.BR-OTH-02

 


0..1

Notice Number

For procurement projects above the threshold it is compulsory to specify the following data about the Contract Notice published in TeD

 

 

cac: AdditionalDocumentReference

Document Reference. Details

 

Req:
SC:
Common: BR-COM-10

tir070-303

x

0..1

Notice identifer

The identifier of the Contract Notice published in TeD (the OJEU S number)

Identifier

tbr70-007

AdditionalDocumentReference /cbc:ID

Document Reference. Identifier

Rule: All ESPDResponse XML instances (and the ESPDRequest instances, too, for that matter) MUST always include an Additional Document Reference indicating the TeD reference number of the Contract Notice the ESPDResponse is related to.  If the document referenced is a Contract Notice published on TED the ID must follow the scheme defined by the Publications Office: [][][][]/S [][][]-[][][][][][] (e.g. 2015/S 252-461137).Reg: -
SC: -
Common: BR-COM-10#1, BR-OTH-02

tir070-304

x

0..1

Notice type code

The Type Code of the Contract Notice

Code

tbr70-007

AdditionalDocumentReference /cbc:DocumentTypeCode

Document Reference. Document Type Code. Code

Rule: For the ESDP-EDM it is compulsory use of the Code List “DocRefContentType”. See example in "AdditionalDocumentReference/cbc:ID" on how to specify the OJEU CN. If the type of document is not available in this list, provide the code “Other” and describe the content in the element “DocumentType”.Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#3, BR-OTH-03

tir070-304

x

0..1

Notice type description

The type of document being referenced, expressed as text.

Code

tbr70-007

AdditionalDocumentReference /cbc:DocumentType

Document Reference. Document Type. Text

Rule: Use the attribute languageID to indicate the language of the text. Use the Code List LanguageCodeEUfor the value of the languageID attribute.Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#4, BR-OTH-03

tir070-305

x

0..1

Notice URI

The Uniform Resource Identifier (URI) that identifies where the notice  is located.

Identifier

tbr70-007

AdditionalDocumentReference /Attachment /ExternalReference /cbc:URI

External Reference. URI. Identifier

Comment: If the document exists at a remote location, then the value should be the URL pointing to the document. 

tir070-306

x

0..1

Notice name

Title of the Contract Notice

Text

tbr70-007

AdditionalDocumentReference /Attachment /ExternalReference/cbc:FileName

External Reference. File Name. Name

Comment: The ESPD documents use this element for a short descriptive title of the document being referenced.

tir070-307

x

0..1

Notice description

The description of the procurement project used in the Notice

Text

tbr70-007

AdditionalDocumentReference /Attachment /ExternalReference/cbc:Description

External Reference. Description. Text

Rule: A description of the content. If the document being referenced is a Notice being published on TED, use two description lines. Use the first description line to describe the requested services and the second description line to place therein the temporary number received from TED.Reg: -
SC: -
Common: BR-COM-10#2, BR-COM-10-S10, BR-COM-10-S20, BR-COM-10-S30

 


1..1

Contracting body

The contracting authority or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU).

 

 

cac: ContractingParty

Contracting Party. Details

Rule: UBL-2.2 defines multiple cardinality ContractingParties presumably to allow joint procurements. However the ESPD only expects data about one buyer. The decision was made that in case of joint procurement the data collected in the ESPD would be about the leader of the joint procurement procedure.Reg: -
SC: -
Common: BR-REQ-20#1
tir070-528 0..1Contracting body buyer profileURL of the web section, in the contracting body web site, that contains information about the contracting body, the norms it applies when contracting, published calls for tenders, Prior Information Notices and Contract Notices as well as the related procurement documents, contract award notices, etc.Identifiertbr70-006ContractingParty/cbc:BuyerProfileURIContracting Party. Buyer Profile_ URI. Identifier

tir70-026

x

1..1

Contracting body name

The name of the contracting body as it is registered.

Text

tbr70-001

ContractingParty /Party /PartyName /cbc:Name

Party. Party Name

Rule:  Use the official name of the contracting body. Reg: -
SC: -
Common: BR-REQ-20#2

tir70-028

x

0..1

Contracting body identifier

The national identifier of a contracting body as it is legally registered (e.g. VAT identification, such as KBO)

Identifier

tbr70-001

ContractingParty /Party /PartyIdentification /cbc:ID

Party Identification. Identifier

Rule: An ID for the Contracting authority may be provided (e.g. in case of subdivisions/regional codes of the agency). Make use of the attribute SchemeAgencyID. When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system).Reg: -
SC: -
Common: BR-REQ-20#4, BR-OTH-02

tir70-039

x

0..1

Contracting body electronic address identifier

Electronic address of the contracting body.

Identifier

tbr70-001

ContractingParty /Party /cbc:EndpointID

Party. Endpoint Identifier. Identifier

Comment: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.) 

tir070-314

x

0..1

Contracting body website 

The website of the contracting body.

Identifier

tbr70-006

ContractingParty /Party /cbc:WebsiteURI

Party. Website_ URI. Identifier



 


1..1

Postal Address

Address information.

 

 

ContractingParty /Party /cac:PostalAddress

Address. Details

 


tir70-029

x

0..1

Address line 1

The main address line in an address. Usually the street name and number or post office box.

Text

tbr70-006

ContractingParty /Party /PostalAddress /cbc:StreetName

Address. Street Name. Name



tir70-031

x

0..1

City

The common name of a city where the address is located.

Text

tbr70-006

ContractingParty /Party /PostalAddress /cbc:CityName

Address. City Name. Name



tir70-032

x

0..1

Post code

The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code.

Text

tbr70-006

ContractingParty /Party /PostalAddress /cbc:PostalZone

Address. Postal_ Zone. Text



tir70-034

x

1..1

Country code

A code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.

Code

tbr70-006

ContractingParty /Party /PostalAddress /Country/cbc:IdentificationCode

Country. Identification Code. Code

Rule: The country of the contracting body MUST always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006)Reg: -
SC: -
Common: BR-REQ-20#3, BR-OTH-01, BR-OTH-01#5,  BR-OTH-03
tir70-502x0..1Country nameThe name of the countryTexttbr70-001cac:ContractingParty/cac:Party/cac:PostalAddress/cac:Country/cbc:NameCountry. Name. Text

 


0..1

Contacting details

Used to provide contacting information for a party in general or a person.

 

 

ContractingParty /Party /cac:Contact

Contact. Details

 


tir70-035

x

0..1

Contact point

The name of the contact point.

Text

tbr70-006

ContractingParty /Party /Contact /cbc:Name

Contact. Name



tir70-036

x

0..1

Contact telephone number

A phone number for the contact point.

Text

tbr70-006

ContractingParty /Party /Contact /cbc:Telephone

Contact. Telephone. Text



tir70-037

x

0..1

Contact fax number


A fax number for the contact point.

Text

tbr70-006

ContractingParty /Party /Contact /cbc:Telefax

Contact. Telefax. Text



tir70-038

x

0..1

Contact email address

An e-mail address for the contact point.

Text

tbr70-006

ContractingParty /Party/Contact /cbc:ElectronicMail

Contact. Electronic_ Mail. Text



 


0..1

Service provider

 

 

 

ContractingParty /Party /cac:ServiceProviderParty

Service Provider Party. Details

 


tir070-040

x1..1

Service provider name

The name of the service provider.

Text

tbr70-011

ContractingParty /Party /ServiceProviderParty /Party /PartyName /cbc:Name

Party Name. Name

Rule:  Use the official name of the service provider. Reg: -
SC: -
Common: BR-REQ-20#6

tir070-041

x1..1

Service provider identifier

The national identifier of a service provider as it is legally registered (e.g. VAT identification, such as KBO)

Identifier

tbr70-011

ContractingParty /Party /ServiceProviderParty /Party /PartyIdentification /cbc:ID

Party Identification. Identifier

Rule: Provide an ID for the Service Provider. Make use of the attribute SchemeAgencyID. When possible use the VAT identification of the service provider (see the VIES platform for a EU cross-border national VAT number verification system).Reg:
SC:
Common: BR-REQ-20#5, BR-OTH-02"

tir070-042

x

0..1

Service provider electronic address identifier

Electronic address of the service provider.

Identifier

tbr70-011

ContractingParty /Party /ServiceProviderParty /Party /cbc:EndpointID

Party. Endpoint Identifier. Identifier

Comment: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.) 

tir070-315

x

0..1

Service provider website 

The website of the service provider.

Identifier

tbr70-011

ContractingParty /Party /ServiceProviderParty /Party /cbc:WebsiteURI

Party. Website_ URI. Identifier

  
tir70-034 1..1Country codeA code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.Codetbr70-011cac:ContractingParty/cac:Party/cac:ServiceProviderParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCodeCountry. Identification Code. CodeRule: The country of the contracting body MUST always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006)Reg:
SC: BR-REQ-20#7, BR-OTH-01, BR-OTH-01#5,  BR-OTH-03
Common: 

 


0..1

ProcurementProject

Used to identify the procurement procedure.

 

 

cac:ProcurementProject

 

Comment: Use this component to identify and describe the procurement administrative procedure. If the procurement procedure is divided into lots use the ProcurementProjectLot component to provide details specific to the lot and reserve the ProcurementProject component to describe the global characteristics of the procedure.Reg:
SC: BR-SC-10
Common:

tir070-503

x

0..1

ProcurementProjectName

Procurement project name

Text

tbr70-007

cac:ProcurementProject /cbc:Name

Procurement Project. Name

Rule: Use the same name that will be used for the Contract Notice.Reg:
SC: BR-SC-10#1
Common:

tir070-504

x

0..1

ProcurementProjectDescription

Procurement project description

Text

tbr70-007

cac:ProcurementProject /cbc:Description

Procurement Project. Description. Text

Comment: Use the same description that will be used for the Contract Notice. 
tir070-528 0..1Procurement project type codeProcurement project type codeCodetbr70-007cac:ProcurementProject/cbc:ProcurementTypeCodeProcurement Project. Procurement_ Type Code. CodeRule: Compulsory use of the Code List ProjectType.Reg:
SC: BR-OTH-01, BR-OTH-01#6,  BR-OTH-03
Common: 
tir070-530
0..1Procurement sub type codeA code signifying the subcategory of the type of work for this project (e.g., land surveying, IT consulting).Codetbr70-007cac:ProcurementProject/cbc:ProcurementSubTypeCodeProcurement Project. Procurement Sub_ Type Code. CodeRule: Compulsory use of the code list ServicesProjectSubType.Reg:
SC: BR-OTH-01#22
Common: 
tir070-529
0..nCPV Classification CodeElement to specify the CPV code for works and services. Codetbr70-007cac:ProcurementProject/cac:MainCommodityClassification/cbc:ItemClassificationCodeCommodity Classification. Item Classification Code. CodeRule: The Self-contained ESPD adds the possibility for the contracting authority to specify a few more data relevant at evaluation time and for the economic operator:
• The CPV (Common Procurement Vocabulary) codes for the procurement procedure.
• The 'Object of the contract'.
Reg:
SC: BR-SC-10#1, BR-OTH-01,
Common: 

 


0..n

Procurement Project Lot

If there is a single procurement project lot, the ESPD refers to a project without lots.

 

 

cac:ProcurementProjectLot

Procurement Project Lot. Details

Rule: If there is only one single procurement project lot specified, the ESPD refers then to a procurement procedure without lots.Reg:
SC: BR-LOT-30
Common: 

tir070-052

x

1..1

Lot reference

A reference to one or more lots the economic operator is applying for. The original lot definition is part of the call for tender document. The Qualification instance only references the corresponding IDs in order to establish the connection to the call for tender information.

Identifier

tbr70-008

ProcurementProjectLot /cbc:ID

Procurement Project Lot. Identifier

Rule: Used to identify the lots into which a procurement procedure is divided into. Typical examples of lot identifiers are Lot1, Lot2, Lot3, etc. If only no Lot is specified its ID has to be set to '0' thus indicating that the procurement procedure is not divided into Lots. Use the schemeAgencyID attribute where necessary.Reg:
SC: BR-LOT-10, BR-LOT-30-S10, BR-OTH-02
Common: 

 


1..n

Criterion

A tendering criterion describes a fact or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidate tenderers to the award decision

 

tbr70-003
tbr70-009

cac:TenderingCriterion

Tendering Criterion. Details

Rule: “Tendering Criterion” with a new definition "A tendering criterion describes a fact or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidate tenderers to the award decision"
Rule: At least one TenderingCriterion is expected.
Reg:
SC: BR-LOT-20, BR-LOT-30, BR-LOT-30-S20
Common: BR-TC-01

tir070-060

x

1..1

Criterion identifier

A language-independent token, e.g., a number,thatallowstoidentifyacriterionuniquelyaswellasallowstoreferencethecriterionin other documents. A criterion describes a fact that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used in the award decision.

Identifier

tbr70-010
tbr70-009

TenderingCriterion /cbc:ID

Tendering Criterion. Identifier

Rule: An identifier to refer to the Criterion requirement.  Compulsory use of the IDs defined in the list “ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods”. E-Certis uses the same IDs. Criteria which are added manually should also use UUID version 4.Reg:
SC:
Common: BR-TC-02, BR-TC-12, BR-TC-13, BR-OTH-02

tir070-061

x

1..n

Criterion type code

A classification code defined by the ESPD-EDM to represent the criterion in the ESPD taxonomy of criteria

Code

tbr70-013

TenderingCriterion /cbc:CriterionTypeCode

Tendering Criterion. Criterion Type Code. Code

Rule: A code signifying the type of Criterion coming from e-Certis. Compulsory use of the Code List “CriteriaType” which are described in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods", e.g. CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION, CRITERION.EXCLUSION.SOCIAL.ENVIRONMENTAL_LAW, CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, etc.).Reg:
SC:
Common: BR-REQ-30, BR-REQ-30-S10,  BR-REQ-30-S20, BR-REQ-40, BR-TC-03, BR-TC-04, BR-OTH-01, BR-OTH-01#7, BR-OTH-03

tir070-062

x

0..1

Criterion name

A short and descriptive name for a criterion. A criterion describes a fact that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used in the award decision or to assess the eligibility of an economic operator.

Text

tbr70-010
tbr70-009

TenderingCriterion /cbc:Name

Tendering Criterion. Name

Rule: The name should be the same as in the in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods", e.g. 'Convictions', 'Corruption', 'Fraud', 'Financial ratio', 'Subcontracting proportion', 'Allowance of checks', etc. At a later stage they might be provided by eCERTIS in dependence of Criterion.Reg:
SC:
Common: BR-TC-05

tir070-063

x

0..1

Criterion description

An extended description of the criterion.

Text

tbr70-010
tbr70-009

TenderingCriterion /cbc:Description

Tendering Criterion. Description. Text

Rule: The description should be the same as in the in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods”, e.g. 'Has the economic operator entered into agreements with other economic operators aimed at distorting competition?'. At a later stage they might be provided by eCERTIS in dependence of Criterion.Reg:
SC:
Common: BR-TC-06, BR-TC-19

tir070-505


0..1

Criterion weight

A weighting to provide for automatic scoring of the Criterion.

Text

tbr70-016

TenderingCriterion /cbc:WeightNumeric

Tendering Criterion. Weight Numeric. Numeric

Rule: Used only in Self-contained ESPDs namely for ability and professional selection criteria in procedures organised in two stages.Reg:
SC: BR-2P-10-S10, BR-2P-10-S10#1, BR-2P-10-S20#1
Common:

tir070-506


0..1

Criterion evaluation method type

A code signifying the type of Evaluation. ESPD: Compulsory use of the Code List “EvaluationMethodType”

Code

tbr70-016

TenderingCriterion /EvaluationMethodTypeCode

Tendering Criterion. Evaluation Method Type Code. Code

Rule: Compulsory use of the Code List “EvaluationMethodType”.Reg:
SC: BR-2P-10-S10#2, BR-2P-10-S20, BR-OTH-01, BR-OTH-03, BR-OTH-01#8, BR-OTH-03
Common:

tir070-507


0..1

Evaluation method description

The textual description of the applied weighting and evaluation method

Text

tbr70-016

TenderingCriterion /cbc:WeightingConsiderationDescription

Tendering Criterion. Weighting Consideration Description. Text

Comment: Used only in Self-contained ESPDs namely for ability and professional selection criteria in procedures organised in two stages. 

 


0..n

Criterion

 

 

 

TenderingCriterion /cac:SubTenderingCriterion

SubTenderingCriterion.Details

 


 


0..n

Criterion legislation

 

 

 

TenderingCriterion /cac:Legislation

Legislation. Details

Rule: for "LangID" - if not specified defaults to `en (English)`Reg:
SC:
Common: BR-TC-08, 2. BR-OTH-01, BR-OTH-01#9, BR-OTH-03

tir070-508

 

0..1

Legislation identifier

An identifier to refer to the legislation. ESPD: If a DOI (Digital Object Identifier) exists for this legislation please use it here.

Identifier

tbr70-013

TenderingCriterion /Legislation /cbc:ID

Legislation. Identifier

Rule: The ID which identifies one specific property is mandatory. And it must use UUID numbers (version 4) automatically generated.Reg:
SC: BR-OTH-02
Common: 

tir070-064

x

1..1

Legislation title

Title of the legislation.

Text

tbr70-013

TenderingCriterion /Legislation /cbc:Title

Legislation. Title. Text

Rule: The complete title of the legislation provided in the original legal text MUST be provided. At a later stage they might be provided by eCERTIS in dependence of Criterion. (e.g.'DIRECTIVE 2014/24/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 26 February 2014 on public procurement and repealing Directive 2004/18/EC'). Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-09

tir070-065

x

0..1

Legislation description

Textual description of the legislation.

Text

tbr70-013

TenderingCriterion /Legislation /cbc:Description

Legislation. Description. Text

Rule: The description of the legislation provided in the original legal text SHOULD be provided. At a later stage they might be provided by eCERTIS in dependence of Criterion. Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-10

tir070-066

x

0..1

Jurisdiction level

Jurisdictional level of a particular legislation.

Text

tbr70-013

TenderingCriterion /Legislation /cbc:JurisdictionLevel

Legislation. Jurisdiction Level. Text

Rule: Compulsory use of the description in Code List "LegislationType". Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-OTH-03, BR-OTH-01#10, BR-OTH-03

tir070-067

x

0..1

Legislation article

Textual description of the article of the legislation.

Text

tbr70-013

TenderingCriterion /Legislation /cbc:Article

Legislation. Article. Text

Rule: Other articles where the Criterion is referred to SHOULD also be provided. At a later stage they might be provided by eCERTIS. Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-11

tir070-068

x

0..1

Legislation URI

URI that points to a particular legislation

Identifier

tbr70-013

TenderingCriterion /Legislation /cbc:URI

Legislation. URI. Identifier

Rule: In the case of European legislation, the URL MUST point at the multilingual EUR-LEX web-page; e.g. Directive 2014/24/EU 

 


0..n

Criterion requirement group

 

 

 

TenderingCriterion /cac:TenderingCriterionPropertyGroup

TenderingCriterionPropertyGroup. Details

Rule: This attribute is defined in the ESPDRequest. This element is used to specify how the elements within the group should be processed.Reg:
SC:
Common: BR-TC-07, BR-TC-16

tir070-320

x

1..1

Criterion requirement group identifier

Anidentifierthatallowstoidentifyagroupofrequirements uniquely.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /cbc:ID

TenderingCriterionPropertyGroup. Identifier

Rule: Compulsory use of the UUIDs in the in the spreadsheets “ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00”.  At a later stage they might be provided by eCERTIS. Groups which are added manually (e.g. national criteria) should also use UUID version 4. Reg:
SC:
Common: BR-TC-12, BR-OTH-02, BR-OTH-02#01

tir070-509


0..1

Criterion requirement group type code

Code specifying the type of the group.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /cbc:CriteriaGroupTypeCode

Tendering Criterion Property Group. Criteria Group Type Code. Code

Rule: Compulsory use of the Code List "PropertyGroupType". Beware that the first element inside a group of properties (after the group ID) is always a cac:TenderingCriterionProperty. In some occasions this might entail the use of an empty CAPTION element, for instance, to produce groups of subgroups where no property does really makes sense in the first group.Reg:
SC:
Common: BR-TC-14, BR-TC-15, BR-OTH-01, BR-OTH-01#11, BR-OTH-03

 


0..n

Criterion requirement group

 

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /cac:SubsidiaryTenderingCriterionPropertyGroup

SubTenderingCriterion.Details

Rule: Used to add susidiary tendering criteria groups. A second, third or n-level group inside a first level group of properties.Reg:
SC:
Common: BR-TC-17

 


1..n

Criterion requirement

Requirement to fulfill an specific criterion.

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /cac:TenderingCriterionProperty

TenderingCriterionProperty. Details

Comment: The CA specifies the criterion requirement and expected responses to be given by the economic operator. The request for data is answered by the Economic Operator in the Qualification Application Response document this information as a basis. Reg:
SC: BR-SC-20
Common:

tir070-080

x

1..1

Criterion requirement identifier

Identifier of the requirement that fulfills an specific criterion.

Identifier

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty/cbc:ID

TenderingCriterionProperty. Identifier

Rule: Requirement identifiers must use UUID numbers (version 4) automatically generated. The responses of the economic operator (in the ESPD Response document) will refer to this UUID to link the response with one, and only one, criterion property. Requirements which are added manually should also use UUID version 4. Reg:
SC:
Common: BR-TC-18, BR-OTH-02

tir070-510

 

0..1

Criterion requirement name

The name of the Criterion requirement

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:Name

TenderingCriterionProperty. Name

Comment: Compulsory use of the Requirement names from the table  "ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00". 

tir070-081

x

1..1

Criterion requirement description

Description of the requirement that fulfills an specific criterion.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:Description

TenderingCriterionProperty. Description. Text

Rule: Compulsory use of the Requirement descriptions from the table  "ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00"Reg:
SC:
Common: BR-TC-19
tir070-601 1..1Criterion requirement typeThe type of criterion requirement. Used to verify that structure of the criterion requirement is correct.Codetbr70-013
tbr70-004
TenderingCriterion/TenderingCriterionPropertyGroup/TenderingCriterionProperty/cbc:TypeCodeTenderingCriterionProperty. Type Code. CodeRule: Compulsory use of the Code List 'CriterionElementType'. Possible types are 'CAPTION, REQUIREMENT and QUESTION'. If the type is CAPTION or REQUIREMENT no answer is expected from the economic operator and therefore the cbc:ValueDataTypeCode must be set to NONE. Otherwise this value must be set to one of the values defined in the Code List 'ResponseDataType'Reg:
SC: BR-TC-20, BR-OTH-01, BR-OTH-01#14, BR-OTH-03
Common: 

tir070-510

x

1..1

Expected response data type

The data type of the numeric value and any constraints on the data type metadata. ESPD: The expected type of the data. Compulsory use of the Code List “ResponseDataType”.

Code

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueDataTypeCode

Tendering Criterion Property. Value Data Type Code. Code

Rule: Compulsory use of the Code List “ResponseDataType”. Verify that the value is different to NONE for properties of type QUESTION.Reg:
SC:
Common: BR-TC-21, BR-OTH-01, BR-OTH-03, BR-OTH-01#12, BR-OTH-03

tir070-511


0..1

Expected resonse value unit

The unit of measure of the numeric value as a quantity or measure.

Code

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueUnitCode

Tendering Criterion Property. Value Unit Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC: BR-OTH-01
Common: 

tir070-512


0..1

Expected response currency

The currency of the numeric value as an amount.

Code

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueCurrencyCode

Tendering Criterion Property. Value Currency Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC: BR-OTH-01
Common: 

tir070-513


0..1

Expected identifier

The expected identifier that the responder has to provide in the Criterion response.

Identifier

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedID

Tendering Criterion Property. Expected_ Identifier. Identifier

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC: BR-LOT-40
Common: 

tir070-514


0..1

Expected response code

The expected code that the responder has to provide in the Criterion response.

Code

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedCode

Tendering Criterion Property. Expected_ Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

For the the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, a "Response Value. Response Code. Code" MUST use the same code from the list "Ratio Type" that is described in the "Tendering Criterion Property. Expected_ Code. Code"
For the the Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION , a "Response Value. Response Code. Code" MUST use the same code from the list "BidType" that is described in the "Tendering Criterion Property. Expected_ Code. Code"

Reg:
SC: BR-OTH-01; BR-OTH-01#23, BR-OTH-01#24
Common: 

tir070-515


0..1

Expected response value

The expected value that the responder has to provide in the Criterion response.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedValueNumeric

Tendering Criterion Property. Expected_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir070-516


0..1

Expected maximum response value

The maximum value the response must have.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup/TenderingCriterionProperty /cbc:MaximumValueNumeric

Tendering Criterion Property. Maximum_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir070-517


0..1

Expected minimum response value

The minimum value the response must have.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:MinimumValueNumeric

Tendering Criterion Property. Minimum_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir070-518


0..1

Expected response certification level

The description of the level of the expected certification.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:CertificationLevelDescription

Tendering Criterion Property. Certification Level Description. Text

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

 


0..1

Criterion fulfillment time period

 

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod

 

Rule: The ESPD-EDM does only expect start date and end date. 
tir070-519

0..1

Period start date

The date when the period starts. The date is the first day of the period.

Date

tbr070-019

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:StartDate

Period. Start Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD")
tir070-521

0..1

Period end date

The date on which the period ends. The date is the last day of the period.

Date

tbr070-019

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:EndDate

Period. End Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD")

Table 8: Implementation Guideline ESPD request transaction (Trdm070)

ESPD Response transaction (Trdm092) 

Overview: ESPD response transaction (Trdm092)

Categories

Description and Values

Identifier

Trdm092

CustomizationID

urn:www.cenbii.eu:transaction:biitrdm092:ver3.0

Description

A structured electronic business document for providing qualification information in a simplified way through an ESPD when responding to a Call for Tender.

Partner Types

Customer
Supplier

Authorized Roles

Economic operator
Contracting body

Initial Event

The economic operator receives an ESPD request and prepares and sends the qualification document (ESPD).

Terminal event

The contracting body receives and processes the qualification document (ESPD).

Scope

Open and restricted tendering procedures, with a focus on implementing the simplification in tendering procedures above threshold according to directives 2014/24/EU and 2014/25/EU.

Boundary

Trdm092

Table 9: Overview ESPD response transaction (Trdm092)

Business Requirements: ESPD response transaction (Trdm092)

Economic Operator

ID

Requirement

tbr092-001

The economic operator shall be able to include all information necessary for identification: Party Name, Party Identification, endpoint id.

tbr092-002

The economic operator shall be able to include contact information: Postal address, telephone number, fax number, e-mail address, contact person(s), Internet address.

tbr092-003

The economic operator shall be able to define his country of registration. The country of registration is needed to identify relevant evidences and the legal domain of evidence provision.

tbr092-004

The economic operator shall be able to indicate the distinctive features or characteristics qualifying an economic operator to be a party in a tendering process (e.g. number of employees, whether he is a micro, a small or a medium-sized enterprise (SME), number of operating units, type of business, technical and financial capabilities, completed projects)

tbr092-006

If the economic operator is registered on an official list of approved economic operators or is in possession of an equivalent certificate (e.g. under a national (pre)qualification system), he shall be able to provide
a) the relevant registration or certification number,
b) in case the certificate is available electronically: the web address, issuing body, and precise reference of the documentation;
c) the references on which the registration or certification is based, as well as the classification obtained in the official list;
d) whether the registration or certification covers all the required exclusion grounds and selection criteria.

tbr092-007

If the call for tender demands a certificate with regard to the payment of social security contributions and taxes, the economic operator shall be able to indicate if he can provide such a certificate. And if so, in the case the certificate can be retrieved free of charge electronically: the web address, issuing body, and precise reference of the documentation.

tbr092-008

The economic operator shall be able to indicate if he is participating together with others (e.g. with subcontractors or with other partners). If so, he shall be able to provide
a) the role of the economic operator in the group (leader, responsible for specific tasks, etc.);
b) the identification of the other economic operators participating in the procurement procedure;
c) (where applicable) name of the participating group.


Representative of the economic operator

ID

Requirement

tbr092-009

The economic operator shall be able to name a natural person that is acting as the representative of the economic operator and to include the personal information necessary for identifying this natural person (e.g. Identifier, name, nationality, address, place of birth, date of birth, email, telephone)

tbr092-010

The economic operator shall also be able to specify the position (acting capacity) the natural person takes in the company in the qualification/tendering phase. If needed, the economic operator shall be able to provide detailed information on the representation (its forms, extent, purpose, etc.)


Contracting authority

ID

Requirement

tbr092-011

The contracting authority shall be identified, hence information about the party are required, such as party name, identification, endpoint id- buyer profile and country- .

tbr092-012

The ESPD should contain contact information of the contracting authority: Postal address, telephone number, fax number, e-mail address, contact person(s).


Call for tender reference

ID

Requirement

tbr092-013

The ESPD shall contain the object of the contract, the type of procedure and the type of procurement project (R90) as well as a reference to the call for tenders, i.e. the procurement project ID or notice ID (PIN, CN, and CAN), which defines the requirements (i.e. criteria) for which this document is created and submitted by the economic operator. It must be possible to maintain this information in order to keep track of the connection between ESPD response and the EPSD request, respectively the call for tenders/notices.



Procurement lots

ID

Requirement

tbr092-014

Where the call for tender is divided into lots, the economic operator shall be able to indicate, which lot he is tendering.


List of Criteria

ID

Requirement

tbr092-015

The ESPD shall contain corresponding information about the (non)existence of exclusion grounds as set out in the call for tender or ESPD request (cf. tbr70-009). The information shall contain a legal reference (EU level, contracting authority national level, economic operator national level). Furthermore it shall contain the name of criterion and criterion group to which it belongs (according to names of Art. 57 of 2014/24/EC and referred to in Art. 80 of 2014/25/EC) as well as indications of (non)existence of each single exclusion ground contained and details and explanations as requested according to Art. 57 of directive 2014/25/EU and the ESPD form agreed among the Member State.
Where demanded and if available electronically, the ESPD shall provide the following information to relevant documentation: the web address, issuing body, and precise reference of the documentation.
The ESPD shall also accommodate information of self-cleaning measures and reliability explanations in cases, where an exclusion ground exists.

tbr092-016

The ESPD shall contain corresponding information about the fulfilment of selection criteria as set out in the call for tender or ESPD request (cf. tbr70-010). The information shall contain a legal reference (EU level, contracting authority national level, economic operator national level). Furthermore it shall contain the name of criterion and criterion group to which it belongs (according to names of Art. 58 of 2014/24/EC and referred to in Art. 80 of 2014/25/EC) as well as indications of fulfilment of selection criteria contained as well as details and explanations as requested according to Art. 58 of directive 2014/25/EU and the ESPD form agreed among the Member State.
Where demanded and if available electronically, the ESPD shall provide the following information to relevant documentation: the web address, issuing body, and precise reference of the documentation.


Evidences

ID

Requirement

tbr092-017

The economic operator shall be able to add evidence or the internet address of a national database (including any identification data and, where applicable, the necessary declaration of consent cf. Art. 59 of 2014/24/EC) from which a contracting authority can directly retrieve any evidence documents and certificates or supporting documents which prove the EO's compliance to the requested criteria defined in the call for tender and stated in the ESPD. The description of the evidence shall include web address, verification code, issuing body, and precise reference of the documentation.


Evaluation of criteria

ID

Requirement

tbr092-018

The ESPD shall contain structured information about fulfillment of selection criteria and non-existence of exclusion grounds specified by Contracting Authority. This is essential for automatic evaluation of criteria.


Issuing date and time

ID

Requirement

tbr092-019

The ESPD shall be identified and dated. The time of issue should be stated and it should be indicated whether the document is a copy. The UBL version and the ESPD version, the ESPD specification and the transaction should be identified as well.


Versioning

ID

Requirement

tbr092-020

The ESPD should allow to include a Version ID and a Previous Version ID to the ESPD. Both help to identify the status of subsystems that have supported the creation of the ESPD. The Previous version ID is needed to trace changes that have occurred.


ESPD service provider

ID

Requirement

tbr092-021

The ESPD may reflect information about the issuing service of the CA and EO that was used to create the ESPD request and respectively the ESPD response itself.


Additional documentation

ID

Requirement

tbr092-022

The economic operator should be able to include any additional documents that are not classified as evidentiary information that prove specific exclusion grounds or selection criteria.


Date, place of issuance of evidence

ID

Requirement

tbr092-023

The economic operator shall be able to indicate date where an evidence has been issued.


Response

ID

Requirement

tbr092-024

In the ESPD response the economic operator must be able to provide information regarding the following selection criteria:

  • Financial Ratios
  • Professional risk indemnity insurance
  • Other economic or financial requirements
  • References on similar works, deliveries or services
  • Technicians or technical bodies
  • Technical, Study, Research and Development facilities/resources
  • Supply chain management
  • Allowance of checks
  • Educational and professional qualifications and Environmental management measures
  • Tools, plant or technical equipment
  • Supply contracts
  • Quality assurance schemes and environmental management standards
  • Financial Ratios

tbr092-025

The economic operator must be able to identify parts of the information provided in the ESPD response as Confidential.


Data Model for regulated ESPD: ESPD response transaction (Trdm092)


Figure 7: ESPD response data model (regulated ESPD)

Data Model for self-contained ESPD: ESPD response transaction (Trdm092)

Figure 8: ESPD response data model (self-contained ESPD)

Implementation Guideline: ESPD response transaction (Trdm092)

This guideline explains how to use the UBL 2.2 syntax or the QualificationApplicationResponse to implement ESPD-EDM version 2.1.0 to support the CEN BII information transaction requirements. It provides the syntax mappings from the UBL syntax to the ESPD request transaction (Trdm092). It also provides specific details for each class and information element and provides guidelines, rules and examples on how to produce conformant XML documents. Additionally, the difference between Regulated and Self-Contained ESPD version is description in the column "Used in Reg". The tables can be also downloaded here as excel files as part of the  ESPD EDM v202 Domain Vocabulary (TO BE UPDATED)

InfReqID

Used in Reg

Card

Business term

Description

Data Type

BusReqID

Syntax Binding (UBL Path)

Vocabulary term

Implementation Guideline

Business Rule IDs

 


 

ESPD Request

A structured electronic business document for requesting qualification information through an ESPD (conform to an ESPD request). Directive 2014/24/EU, Art. 59.

 

 

QualificationApplicationResponse

Qualification Application Response. Details

A document issued by a procurement organization to notify an Economic Operator whether it has been admitted to or excluded from the tendering process


tir92-001

x

1..1

Document identifier

Identifier of a document An transaction instance must contain an identifier. The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Identifier

tbr92-019

cbc:ID

Qualification Application Response. Identifier

Rule: An identifier for this document, assigned by the sender. Compulsoriness inherited from UBL-2.2.
Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document.
by COM)
Reg: -
SC: -
Common:
BR-OTH-02

tir92-002

x

1..1

Document issue date

Date when the referred document was issued.

Date

tbr92-019

cbc: IssueDate

Qualification Application Response. Issue Date. Date

Comment: Is set at the compilation time. Use XSD Date (format "YYYY-MM-DD") 

tir92-003

x

0..1

Document issue time

Time when the document was issued.

Time

tbr92-019

cbc: IssueTime

Qualification Application Response. Issue Time. Time

Comment: Is set at the compilation time. Use XSD time (format "hh:mm:ss") 

tir92-005


0..1

Document version identifier

The version identifying the content of this document

Identifier

tbr92-020

cbc: VersionID

Qualification Application Response. Version. Identifier

Comment: Changes in content should entail the modification of the version identifier and a reference to the previous version. 
tir92-541
0..1Previous document version identifierThe version identifying the previous modification of the content of this document.Identifiertbr92-020cbc:PreviousVersionIDQualification Application Response. PreviousVersionID. Identifier
 
tir92-542
0..1Procedure codeThe type of the procurement administrative procedure according to the EU Directives.Codetbr92-013cbc:ProcedureCodeQualification Application Response. ProcedureCode. CodeRule: Compulsory use of the code list ProcedureType (values: Open, Restricted, Accelerated, Competitive dialogue, etc.). Do not confound with the object of the procurement project (code list ProjectType: Works, Supplies, Services). Compulsory use of attributes listID, listAgencyName and listVersionID. Reg: -
SC: BR-OTH-01, BR-OTH-01#1, BR-OTH-03
Common: 

tir92-013

x

1..1

Reference number

An identifier that is specified by the buyer and used as a reference number for all documents in the procurement project. It is also known as procurement procedure identifier, procurement reference number or contract folder identifier. A reference to the procurement project to which this Qualification document is delivered as a response.

Identifier

tbr92-013

cbc: ContractFolderID

Qualification Application Response. Contract Folder Identifier. Identifier

Rule: This is a mandatory data provided by the Contracting Authority or the sender, for the process file (i.e., record) to which this document belongs.
Rule: Try always to use the reference number issued by the contracting authority. This number in combination with a registered contracting authority ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.
Reg: BR-REG-20
SC: BR-SC-30
Common: 

tir92-500


1..1

Document universally unique identifier

A universally unique identifier for an instance of this document.

Identifier

tbr92-019

cbc:UUID

Qualification Application Response. UUID. Identifier

Comment: Other documents, e.g. the tender, might refer to the ESPD Response using this identifier (thus its compulsoriness). Copies of a document must be identified with a different UUID. Compulsory use of schemeAgencyID attribute. 

tir92-501


1

ESPD request type code

A code specifying the type of ESPD

Code

tbr92-019

cbc:QualificationApplicationTypeCode

Qualification Application Response. QualificationApplicationTypeCode. Code

Rule: Compulsory use of the codelist QualificationApplicationType (values 'REGULATED`, SELFCONTAINED). Compulsory use of attributes listID, listAgencyName and listVersionID.Reg:
SC: BR-OTH-01, BR-OTH-01#2, BR-OTH-03
Common:

tir92-301

x

0..1

Copy indicator

Indicates whether this document is a copy (true) or not (false)

Indicator

tbr92-019

cbc: CopyIndicator

Qualification Application Response. Copy_ Indicator. Indicator

Comment: It is a good practice to use the CopyIndicator component if the same document is forwarded several times to the same or to different destinations. Use it in combination with the UUID identifier: copies of an ESPD document should be identified with distinct UUIDs. 
tir070-322
0..nWeight scoring methodologyFree-form text to describing information about Weight Scoring MethodologyTexttbr092-018cbc:WeightScoringMethodologyNoteWeightScoringMethodologyNote. TextRule: Used for transparency motives. Provide a text explaining clearly the method that will be used to select those selection criteria that will be weighted.

Reg:
SC: BR-2P-10
Common:

tir070-323
0..1Weighting type codeA code specifying the type of the Weighting.Codetbr092-018cbc:WeightingTypeCodeWeightingTypeCode. CodeRule: Compulsory use of the code list `WeightingType`. If this element it is not instantiated and one or more selection criteria are weighted the type defaults to `NUMERIC`.Reg:
SC: BR-2P-10
Common:

tir92-006

 

0..1

Consortium Name

A name of the consortium of economic operators that are bidding together in a tendering process.

Text

tbr92-008

cbc:EconomicOperatorGroupName

Qualification Application Response. Economic Operator Group Name. Name

Rule: Economic Operator Group Name associated with this Qualification.The leader of the group must take care of ensuring that the name of the group is identical in all the ESPDs of the tender.Reg:
SC:BR-LEAD-10-S10
Common: 

 


1..1

Process control

A group of business terms providing information on the business process and rules applicable to the document.

 

 

 

 

 Reg:
SC:
Common: 

tir92-007

x

1..1

Business process type identifier

Identifies a user-defined customization of UBL for a specific use. ESPD use the current version of the ESP-EDM 2.0.0

Identifier

tbr92-019

cbc: CustomizationID

Qualification Application Response. Customization Identifier. Identifier

Rule: For the ESPD we use the value “urn:www.cenbii.eu:transaction:biitrdm092:ver3.0”. Compulsory use of the value "CEN-BII" for the schemeAgencyID attribute.Reg: -
SC: -
Common:
BR-OTH-02
BR-OTH-06

tir92-008

x

1..1

Specification identification

An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. The identification may include the version of the specification as well as any customizations applied.

Identifier

tbr92-019

cbc:  ProfileID

Qualification Application Response. Profile Identifier. Identifier

Rule: Applied BII Profile: Use the value "41" for ESPD. Use also "CEN-BII" for the scheme AgencyID attributeReg: -
SC: -
Common: BR-OTH-07, BR-OTH-02
tir92-299x1..1ESPD version identiferIdentifies the specific ESPD-EDM version (e.g.: ESPD-EDMv1.0.2; ESPD-EDMv2.0.0; ESPD-EDMv2.0.1 or ESPD-EDMv2.0.2)Identifertbr92-019cbc: ProfileExecutionIDQualification Application Response. ProfileExecutionID. IdentifierRule: Compulsory use of the Code List "ProfileExecutionID".Reg: -
SC: -
Common: BR-OTH-01, BR-OTH-01#13, BR-OTH-03

tir92-302

x

0..1

UBL version identifier

Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance.

Identifier

tbr92-019

cbc:  UBLversionID

Qualification Application Response. UBL Version Identifier. Identifier

Rule: Use the value "2.2". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.Reg: -
SC: -
Common: BR-OTH-05, 2.BR-OTH-02

 


0..n

Notice Number

For procurement projects above the threshold it is compulsory to specify the following data about the Contract Notice published in TeD

 

 

cac: AdditionalDocumentReference

Document Reference. Details

Comment: This class is adapted from the ESPD request. For procurement procedures above the threshold it is compulsory to make reference to the Contract Notice of the procedure published in TED*. See section "Reference to the Contract Notice" for a complete example.  Req:
SC:
Common: BR-COM-10

tir92-303

x

0..1

Notice identifer

The identifier of the Contract Notice published in TeD (the OJEU S number)

Identifier

tbr92-013

AdditionalDocumentReference/cbc:ID

Document Reference. Identifier

Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cac:AdditionalDocumentReference.  All ESPDResponse XML instances (and the ESPDRequest instances, too, for that matter) MUST always include an Additional Document Reference indicating the TeD reference number of the Contract Notice the ESPDResponse is related to.
 If the document referenced is a Contract Notice published on TED the ID must follow the scheme defined by the Publications Office: [][][][]/S [][][]-[][][][][][] (e.g. 2015/S 252-461137).
Reg: -
SC: -
Common: BR-COM-10#1, BR-OTH-02

tir92-304

x

0..1

Notice type code

The Type Code of the Contract Notice

Code

tbr92-013

AdditionalDocumentReference /cbc:DocumentTypeCode

Document Reference. Document Type Code. Code

Rule: For the ESDP-EDM it is compulsory use of the Code List “DocRefContentType”. See example in "AdditionalDocumentReference/cbc:ID" on how to specify the OJEU CN. If the type of document is not available in this list, provide the code “Other” and describe the content in the element “DocumentType”.Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#3, BR-OTH-03

tir92-304

x

0..1

Notice type description

The type of document being referenced, expressed as text.

Code

tbr92-013

AdditionalDocumentReference /cbc:DocumentType

Document Reference. Document Type. Text

Rule: Optionally use the attribute languageID to indicate the language of the text. Use the Code List LanguageCodeEU for the value of the languageID attribute.Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#4, BR-OTH-03

tir92-305

x

0..1

Notice URI

The Uniform Resource Identifier (URI) that identifies where the notice  is located.

Identifier

tbr92-013

AdditionalDocumentReference /Attachment /ExternalReference /cbc:URI

External Reference. URI. Identifier

Comment: If the document exists at a remote location, then the value should be the URL pointing to the document.  

tir92-306

x

0..1

Notice name

Title of the Contract Notice

Text

tbr92-013

AdditionalDocumentReference /Attachment /ExternalReference /cbc:FileName

External Reference. File Name. Name

Comment: The ESPD documents use this element for a short descriptive title of the document being referenced. 

tir92-307

x

0..1

Notice description

The description of the procurement project used in the Notice

Text

tbr92-013

AdditionalDocumentReference /Attachment /ExternalReference /cbc:Description

External Reference. Description. Text

Rule: A description of the content. If the document being referenced is a Notice being published on TED, use two description lines. Use the first description line to describe the requested services and the second description line to place therein the temporary number received from TED.Reg: -
SC: -
Common: BR-COM-10#2, BR-COM-10-S10, BR-COM-10-S20, BR-COM-10-S30

 


0..n

ESPD Request

A reference to the ESPD Request

 

 

cac: AdditionalDocumentReference

 

Rule: In the ESPD Response it is also compulsory to make reference to the ESPD Request document. 

tir92-308

x

0..1

ESPD request identifier

The identifier of the ESPD Request issued by the entity responsible for the document

Identifier

tbr92-013

AdditionalDocumentReference /cbc:ID

Document Reference. Identifier

Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:ID.Reg:
SC:
Common: BR-OTH-02
tir92-543
1..1ESPD request universally unique identifier A universally unique identifier that can be used to reference this ESPD document instance.Identifiertbr92-013AdditionalDocumentReference/cbc:UUIDDocument Reference. UUID. IdentifierRule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:UUID.Reg:
SC:BR-OTH-02
Common: 

tir92-309

x

0..1

ESPD request type code

The Type Code of the ESPD Request

Code

tbr92-013

AdditionalDocumentReference /cbc:DocumentTypeCode

Document Reference. Document Type Code. Code

Rule: This value is set by the system using the data from the ESPD Request:cac:QualificationApplicationRequest/cbc:QualificationApplicationTypeCode  from the Code List "DocRefContentType".Reg:
SC:
Common: BR-OTH-01, BR-COM-10#3, BR-OTH-01#3, BR-OTH-03
tir92-544x0..1ESPD request document descriptionThe type of document being referenced, expressed as text.Texttbr92-013AdditionalDocumentReference/cbc:DocumentDescriptionDocument Reference. Document Type. TextRule: Use the attribute languageID to indicate the language of the text. Use the Code List LanguageCodeEU for the value of the languageID attribute.Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#4, BR-OTH-03

tir92-310

x

0..1

ESPD request issue date

The issue date of the ESPD Request

Date

tbr92-013

AdditionalDocumentReference /cbc:IssueDate

Document Reference. Issue Date. Date

Comment: This value is set by the system using the data from the ESPD Request: cac:QualificationApplicationRequest/cbc:IssueDate
Rule: Use XSD date (format "YYYY-MM-DD"). 
 

tir92-311

x

0..1

ESPD request issue time

The issue time of the ESPD Request

Time

tbr92-013

AdditionalDocumentReference /cbc:IssueTime

Document Reference. Issue Time. Time

Comment (TRDM092-18): This value is set by the system using the data from the ESPD Request: cac:QualificationApplicationRequest/cbc:IssueTime
Rule: Use XSD time (format "hh:mm:ss")
 

 


1..1

Contracting body

The contracting authority or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU).

 

 

cac: ContractingParty

Contracting Party. Details

 


tir92-545
0..1Contracting body buyer profileURL of the web section, in the contracting body web site, that contains information about the contracting body, the norms it applies when contracting, published calls for tenders, Prior Information Notices and Contract Notices as well as the related procurement documents, contract award notices, etc.Identifiertbr92-011ContractingParty/cbc:BuyerProfileURIContracting Party. Buyer Profile_ URI. IdentifierComment: Notices published at national level shall not contain information other than that contained in the notices dispatched to the Publications Office of the European Union or published on a buyer profile, but shall indicate the date of dispatch of the notice to the Publications Office of the European Union or its publication on the buyer profile (Directive 2014/24/EU, Art. 52.2). 

tir92-009

x

1..1

Contracting body name

The name of the contracting body as it is registered.

Text

tbr92-011

ContractingParty/ Party/PartyName/cbc:Name

Party. Party Name


 

tir92-010

x

0..1

Contracting body identifier

The national identifier of a contracting body as it is legally registered (e.g. VAT identification, such as KBO)

Identifier

tbr92-011

ContractingParty/Party/PartyIdentification/cbc:ID

Party Identification. Identifier


 

tir92-011

x

0..1

Contracting body electronic address identifier

Electronic address of the contracting body.

Identifier

tbr92-011

ContractingParty/Party/cbc:EndpointID

Party. Endpoint Identifier. Identifier

Rule: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.)Reg:
SC:
Common: BR-RESP-10-08

tir92-314

x

0..1

Contracting body website 

The website of the contracting body.

Identifier

tbr92-012

ContractingParty/Party/cbc:WebsiteURI

Party. Website_ URI. Identifier

Comment: Use it for the official web site of the contracting body. 

 


1..1

Postal Address

Address information.

 

 

ContractingParty/Party/cac:PostalAddress

Address. Details

 


tir92-012

x

0..1

Address line 1

The main address line in an address. Usually the street name and number or post office box.

Text

tbr92-012

ContractingParty/Party/PostalAddress/cbc:StreetName

Address. Street Name. Name



tir92-013

x

0..1

City

The common name of a city where the address is located.

Text

tbr92-012

ContractingParty/Party/PostalAddress/cbc:CityName

Address. City Name. Name



tir92-014

x

0..1

Post code

The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code.

Text

tbr92-012

ContractingParty/Party/PostalAddress/cbc:PostalZone

Address. Postal_ Zone. Text



tir92-016

x

1..1

Country code

A code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.

Code

tbr92-011

ContractingParty /Party/PostalAddress /Country /cbc:IdentificationCode

Country. Identification Code. Code

Rule: The country of the contracting body MUST always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006)Reg: -
SC: -
Common: BR-OTH-01, BR-OTH-01#5, BR-OTH-03

tir92-503

 0..1

Country name

The name of the country

Text

tbr70-001cac:ContractingParty/cac:Party/cac:PostalAddress/cac:Country/cbc:Name

Country. Name. Text



 


0..1

Contacting details

Used to provide contacting information for a party in general or a person.

 

 

ContractingParty /Party /cac:Contact

Contact. Details

 


tir92-017

x

0..1

Contact point

The name of the contact point.

Text

tbr92-012

ContractingParty /Party /Contact /cbc:Name

Contact. Name



tir92-018

x

0..1

Contact telephone number

A phone number for the contact point.

Text

tbr92-012

ContractingParty /Party /Contact /cbc:Telephone

Contact. Telephone. Text



tir92-019

x

0..1


Contact fax number

A fax number for the contact point.

Text

tbr92-012

ContractingParty /Party /Contact /cbc:Telefax

Contact. Telefax. Text



tir92-020

x

0..1

Contact email address

An e-mail address for the contact point.

Text

tbr92-012

ContractingParty /Party /Contact /cbc:ElectronicMail

Contact. Electronic_ Mail. Text



 


0..1

Service provider

 

 

 

ContractingParty /Party /cac:ServiceProviderParty

Service Provider Party. Details

 


tir92-021

x

0..1

Service provider name

The name of the service provider. Issuer body of the ESPD.

Text

tbr92-021

ContractingParty /Party /ServiceProviderParty /Party /PartyName /cbc:Name

Party Name. Name

Comment:  Use the official name of the service provider.  

tir92-022

x

0..1

Service provider identifier

The national identifier of a service provider as it is legally registered (e.g. VAT identification, such as KBO) Issuer body of the ESPD.

Identifier

tbr92-021

ContractingParty/Party /ServiceProviderParty /Party /PartyIdentification /cbc:ID

Party Identification. Identifier

Rule: Provide an ID for the Service Provider. Make use of the attribute SchemeAgencyID. When possible use the VAT identification of the service provider (see the VIES platform for a EU cross-border national VAT number verification system).Reg:
SC:
Common: BR-OTH-02

tir92-023

x

0..1

Service provider electronic address identifier

Electronic address of the service provider. Issuer body of the ESPD.

Identifier

tbr92-021

ContractingParty /Party /ServiceProviderParty /Party /cbc:EndpointID

Party. Endpoint Identifier. Identifier

Rule: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.)Reg:
SC:
Common: BR-RESP-10-08

tir92-315

x

0..1

Service provider website 

The website of the service provider.

Identifier

tbr92-021

ContractingParty /Party /ServiceProviderParty /Party /cbc:WebsiteURI

Party. Website_ URI. Identifier

Comment: Use it for the official web site of the service provider. 
tir92-546 1..1Country codeA code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.Codetbr92-021cac:ContractingParty/cac:Party/cac:ServiceProviderParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCodeCountry. Identification Code. CodeRule: The country of the service provider must always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006).Reg:
SC:BR-OTH-01, BR-OTH-01#5, BR-OTH-03
Common: 

 


0..1

Economic operator

Any natural or legal person or public entity, 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. Information about the party submitting the qualification.

 

 

cac:EconomicOperatorParty

Economic Operator Party. Details

Rule: The ESPD Response only refers to one, and only one, economic operator. Reg:
SC:
Common: BR-RESP-10

tir92-030

x

1..1

Economic operator identifier

An identifier that identifies the economic operator, such as a legal registration identifier.

Identifier

tbr92-001

EconomicOperatorParty /Party /PartyIdentification /cbc:ID

Party Identification. Identifier

Rule: Compulsory use of the attribute schemeAgencyID and highly recommended the use of the attribute schemeAgencyID. The preferred identifier is the national VAT number.  More than one identifier can be specified. Mandatory use of the  "EOIDType" Code list for the @schemeID.

Reg:
SC:
Common: BR-RESP-10-04, BR-OTH-02; BR-OTH-01#21

tir92-031

x

0..1

Economic operator electronic address identifier

Electronic address of the economic operator.

Identifier

tbr92-001

EconomicOperatorParty /Party /cbc:EndPointID

Party. Endpoint Identifier. Identifier

Rule: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.)Reg:
SC:
Common: BR-RESP-10-08

tir92-033

x

1..1

Economic operator name

The name of the economic operator.

Text

tbr92-001

EconomicOperatorParty /Party /PartyName /cbc:Name

Party Name. Name

Rule: Use the official name of the Party as officially registered.Reg:
SC:
Common: BR-RESP-10-05

tir92-034

x0..n

Economic operator role code

The role of the economic operator when bidding from a consortium. (main contractor,subcontractor ,additional)

Code

tbr92-008

EconomicOperatorParty /EconomnicOperatorRole /cbc:RoleCode

Economic Operator Role. Role Code. Code

Rule: A code specifying the role of the party. Compulsory use of the Code List EORoleType.Reg:
SC: BR-RESP-10-03, BR-OTH-01, BR-OTH-01#15, BR-OTH-03
Common: 

tir92-036


0..1

Economic operator role description

The role of the economic operator when bidding from a consortium. (main contractor,subcontractor ,additional)

Text

tbr92-008

EconomicOperatorParty /EconomnicOperatorRole /cbc:RoleDescription

Economic Operator Role. Role Description. Text

Rule: A textual description of the party role. Software applications should retrieve and reuse the description from the Code List EORoleType. Reg:
SC:
Common: BR-RESP-10-02

tir92-035

x

0..1

SME indicator

Used to indicate whether the company is a micro, small, medium or large enterprise. According to the EC, SME are enterprises with less than 250 employees, a turnover less than EUR 50 m and a balance sheet total less than EUR 43 m.

Indicator

tbr92-004

EconomicOperatorParty /Party /cbc:IndustryClassificationCode

Party. Industry Classification Code. Code

Rule: Compulsory use of the Code List EOIndustryClassificationCode. Used only for statistical purposes. Use the parameters established by the EU Recommendation 2003/361 to determine whether the EO’s company is micro, small, medium or large. Beware that these parameters may change in the future. Reg:
SC:
Common: BR-RESP-10-06, BR-OTH-01, BR-OTH-01#20, BR-OTH-03

tir92-316

x

0..1

Economic operator website 

The website of the economic operator.

Identifier

tbr041-002

EconomicOperatorParty /Party /cbc:WebsiteURI

Party. Website_ URI. Identifier

Comment: Use it for the official web site of the economic operator. 


1..1Qualifying Party


cac:EconomicOperatorParty/cac:QualifyingParty
 Reg:
SC: BR-RESP-10-01
Common: 
tir92-547x0..1Qualifying agency identifierThe identifier of the economic operator in an official list, register or (pre)qualification system.Identifiertbr092-004cac:Party/cac:PartyIdentification/cbc:IDParty. Party IdentificationRule: The attribute schemeAgencyID must hold the value retrieved from eCertis that identifies unequivocally the (pre)qualification system. If, for any reason, that value is not available use the default schemeAgencyID "EU-COM-GROW" and the cac:EconomicOperatorParty/cac:PartyIdentificaton/cbc:ID for the value of the identifier. Additionally you can use the data structure CRITERION.OTHER.EO_DATA.REGISTERED_IN_OFFICIAL_LIST to specify an alternative or additional name, identifier and description.Reg:
SC: BR-RESP-80-S10, BR-RESP-80-S20,
Common: BR-RESP-50, BR-OTH-02
tir92-548
0..1EmployeeQuantityThe number of people employed by the economic operator participating in the tender.Quantitytbr092-004cac:EconomicOperatorParty/cac:QualifyingParty/cbc:EmployeeQuantityQualifying Party. Employee. QuantityComment: Integer value expected. 
tir92-549
0..nBusiness classification schemeThe text describing the official business classification assigned by an official list or (pre)qualification system for which the economic operator is qualified.Texttbr092-004cac:EconomicOperatorParty/cac:QualifyingParty/cac:BusinessClassificationScheme/cbc:DescriptionClassification Scheme. Description. TextComment: Only the 'Description' is expected 
tir92-550
0..nGeneral turnoverA monetary amount as a measure of this capability.Amounttbr092-004cac:EconomicOperatorParty/cac:QualifyingParty/cac:FinancialCapability/cbc:ValueAmountCapability. Value. AmountComment: Use it to place here the general Turnover of the EO (for statistical purposes). Compulsory assignment of a value to the attribute currency. The default value should be set to 'EUR'. Compulsory use of the Code List CurrencyCode.Reg:
SC: BR-OTH-01#16, BR-OTH-03
Common: 
tir92-551
0..nCompleted taskText describing the works, supplies or services executed, delivered or performed in a procurement project (normally used as a reference for the classification of the economic operator.Texttbr092-004cac:EconomicOperatorParty/cac:QualifyingParty/cac:CompletedTask/cbc:DescriptionCompleted Task. Description. TextComment: Use it to place here the references that were used in the (pre)qualification system to get the specific classification related to those references. 

 


1..1

Postal address

Address information.

 

 

cac:EconomicOperatorParty /Party /cac:PostalAddress

Address. Details

 


tir92-041

x

0..1

Address line

The main address line in an address. Usually the street name and number or post office box.

Text

tbr92-002

EconomicOperatorParty/Party/PostalAddress/cac:AddressLine/cbc:LineAddress Line. Line. Text



tir92-043

x

0..1

City

The common name of a city where the address is located.

Text

tbr92-002

EconomicOperatorParty /Party /PostalAddress /cbc:CityName

Address. City Name. Name



tir92-044

x

0..1

Post code

The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code.

Text

tbr92-002

EconomicOperatorParty /Party /PostalAddress /cbc:PostalZone

Address. Postal_ Zone. Text



tir92-046

x

1..1

Country code

A code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.

Code

tbr92-003

EconomicOperatorParty /Party /PostalAddress /Country /cbc:IdentificationCode

Country. Identification Code. Code

Rule: The country of the economic operator MUST always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006)Reg:
SC:
Common: BR-RESP-10-07, BR-OTH-01, BR-OTH-01#5, BR-OTH-03

tir92-504

 

0..1

Country name

The name of the country

Text

tbr92-003

EconomicOperatorParty /Party /cac:PostalAddress /cac:Country /cbc:Name

Country. Name. Text



 


0..1

Contacting details

Used to provide contacting information for a party in general or a person.

 

 

EconomicOperatorParty /Party /cac:Contact

Contact. Details

 


tir92-047

x

0..1

Contact name

The name of the contact point.

Text

tbr92-002

EconomicOperatorParty /Party /Contact /cbc:Name

Contact. Name



tir92-048

x

0..1

Contact telephone number

A phone number for the contact point.

Text

tbr92-002

ContractingParty /Party /Contact /cbc:Telephone

Contact. Telephone. Text



tir92-049

x

0..1

Contact fax number

A fax number for the contact point.

Text

tbr92-002

EconomicOperatorParty /Party /Contact /cbc:Telefax

Contact. Telefax. Text



tir92-050

x

0..1

Contact email address

An e-mail address for the contact point.

Text

tbr92-002

EconomicOperatorParty /Party /Contact /cbc:ElectronicMail

Contact. Electronic_ Mail. Text



 


0..1

Service provider

 

 

 

EconomicOperatorParty /Party /cac:ServiceProviderParty

Service Provider Party. Details

 


tir92-021

x

0..1

Service provider name

The name of the service provider. Issuer body of the ESPD.

Text

tbr92-021

EconomicOperatorParty /Party /ServiceProviderParty /Party /PartyName /cbc:Name

Party Name. Name

Comment:  Use the official name of the service provider. Reg:
SC:
Common: BR-RESP-10-09

tir92-022

x

0..1

Service provider identifier

The national identifier of a service provider as it is legally registered (e.g. VAT identification, such as KBO) Issuer body of the ESPD.

Identifier

tbr92-021

EconomicOperatorParty /Party /ServiceProviderParty /Party /PartyIdentification /cbc:ID

Party Identification. Identifier

Rule: Provide an ID for the Service Provider. Make use of the attribute SchemeAgencyID. When possible use the VAT identification of the service provider (see the VIES platform for a EU cross-border national VAT number verification system).Reg:
SC:
Common: BR-RESP-10-11, BR-OTH-02

tir92-023

x

0..1

Service provider electronic address identifier

Electronic address of the service provider. Issuer body of the ESPD.

Identifier

tbr92-021

EconomicOperatorParty /Party /ServiceProviderParty /Party /cbc:EndpointID

Party. Endpoint Identifier. Identifier

Rule: An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.)Reg:
SC:
Common: BR-RESP-10-08

tir92-315

x

0..1

Service provider website 

The website of the service provider.

Identifier

tbr92-021

EconomicOperatorParty /Party /ServiceProviderParty /Party /cbc:WebsiteURI

Party. Website_ URI. Identifier

Comment: Use it for the official web site of the service provider. 
tir92-552 1..1Country codeA code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.Codetbr92-021cac:ContractingParty/cac:Party/cac:ServiceProviderParty/cac:Party/cac:PostalAddress/cac:Country/cbc:IdentificationCodeCountry. Identification Code. CodeRule: The country of the service provider must always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006).Reg:
SC: BR-RESP-10-10, BR-OTH-01, BR-OTH-01#5, BR-OTH-03
Common: 

 


0..n

Representative natural person

Official or legal mandate issued by an authority (e.g. an attorney or a notary) to represent the economic operator 

 

tbr92-018

EconomicOperatorParty/Party/PowerOfAttorney/AgentParty/cac:Person

Person. Details

Rule: Information about representatives of the economic operator CAN be providedReg:
SC:
Common: BR-RESP-20

tir92-055

x

1..1

Representative natural person first name

Name of the natural person.

Text

tbr92-009

EconomicOperatorParty /PowerOfAttorney /AgentParty /Person /cbc:FirstName

Person. First_ Name. Name

Rule: Name of the natural person is mandatoryReg:
SC:
Common: BR-RESP-20-01

tir92-055

x

1..1

Representative natural person family name

Family Name of the natural person.

Text

tbr92-009

EconomicOperatorParty /PowerOfAttorney/AgentParty /Person /cbc:FamilyName

Person. Family_ Name. Name

Rule: Family Name of the natural person is mandatoryReg:
SC:
Common: BR-RESP-20-02

tir92-065

x

0..1

Representative natural person role description

The short description for the role of the economic operstors representative .

Text

tbr92-010

EconomicOperatorParty /PowerOfAttorney /cbc:Description

Power Of Attorney. Description. Text



tir92-065

x

0..1

Representative natural person birth place

Place of birth of the natural person.

Text

tbr92-009

EconomicOperatorParty /PowerOfAttorney /AgentParty /Person /cbc:BirthplaceName

Person. Birthplace Name. Text



tir92-066

x

0..1

Representative natural person birth date

Date of birth of the natural person.

Date

tbr92-009

EconomicOperatorParty /PowerOfAttorney /AgentParty /Person /cbc:BirthDate

Person. Birth Date. Date



tir92-553
0..1Representative email addressAn e-mail address of the natural person.Texttbr92-009/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:Contact/cbc:ElectronicMailContact. Electronic_ Mail. Text

tir92-554
0..1Representative telephone numberA phone number of the natural person.Texttbr92-009/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:Contact/cbc:TelephoneContact. Telephone. Text
 

 


1..1

Postal address

Address information.

 

 

cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/

Address. Details

 


tir92-058

x

0..1

Address line

The main address line in an address. Usually the street name and number or post office box.

Text

tbr92-009

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/cac:AddressLine/cbc:LineAddress Line. Line. Text



tir92-060

x

0..1

City

The common name of a city where the address is located.

Text

tbr92-009

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/cbc:CityName

Address. City Name. Name



tir92-061

x

0..1

Post code

The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code.

Text

tbr92-009

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/cbc:PostalZone

Address. Postal_ Zone. Text



tir92-533


0..1

Country name

The name of the country

Text

tbr92-003

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/Country/cbc:Name

Country. Name. Text



tir92-063

x

1..1

Country code

A code that identifies the country. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.

Code

tbr92-009

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person/cac:ResidenceAddress/Country/cbc:IdentificationCode

Country. Identification Code. Code

Rule: The country of the representative national person  MUST always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006)Reg:
SC:
Common: BR-RESP-20-03, BR-OTH-01, BR-OTH-01#5, BR-OTH-03

 


0..1

ProcurementProject

Used to identify the procurement procedure.

 

 

cac:ProcurementProject

 

Comment: Use this component to identify and describe the procurement administrative procedure. If the procurement procedure is divided into lots use the ProcurementProjectLot component to provide details specific to the lot and reserve the ProcurementProject component to describe the global characteristics of the procedure.Reg:
SC: BR-SC-10
Common:

tir92-505

x

0..1

Procurement project name

The name of the procurement procedure.

Text

tbr92-013

cac:ProcurementProject /cbc:Name

Procurement Project. Name

Comment: Use the same name that will be used for the Contract Notice. 

tir92-506

x

0..1

Procurement project description

Text describing the procurement procedure.

Text

tbr92-013

cac:ProcurementProject /cbc:Description

Procurement Project. Description. Text

Comment: Use the same description that will be used for the Contract Notice. 
tir92-555
0..1Procurement project type codeA code to describe the object of the project (e.g. works, supplies, services, public work concessions, service concessions, other).Codetbr92-013cac:ProcurementProject/cbc:ProcurementTypeCodeProcurement Project. Procurement_ Type Code. CodeRule: Self Contained ESPD: Compulsory use of the Code List ProjectType.Reg:
SC: BR-OTH-01, BR-OTH-01#6, BR-OTH-03
Common: 
tir92-555
0..1Procurement sub type codeA code signifying the subcategory of the type of work for this project (e.g., land surveying, IT consulting).Codetbr92-013cac:ProcurementProject/cbc:ProcurementSubTypeCodeProcurement Project. Procurement Sub_ Type Code. CodeRule: Compulsory use of the code list ServicesProjectSubType.Reg:
SC: : BR-OTH-01#22
Common
tir92-556
0..nCPV Classification CodeElement to specify the CPV code for works and services. Codetbr92-013cac:ProcurementProject/cac:MainCommodityClassification/cbc: ItemClassificationCodeCommodity Classification. Item Classification Code. CodeComment: Comment: Beware that the cardinality of the basic element is 0..1 but the cardinality of the class is 0..n, Reg:
SC: BR-SC-10#1, BR-OTH-01,
Common: 

 


0..1

Procurement Project Lot

 

 

 

cac:ProcurementProjectLot.

Procurement Project Lot. Details

Rule: If there is only one single procurement project lot specified, the ESPD refers then to a procurement procedure without lots.Reg:
SC: BR-LOT-30
Common: 

tir92-130

x1..1

Lot reference

An identifier for the lot adapted from the call for tender document.

Identifier

tbr92-014

ProcurementProjectLot /cbc:ID

Procurement Project Lot. Identifier

Rule: Used to identify the lots into which a procurement procedure is divided into. Typical examples of lot identifiers are Lot1, Lot2, Lot3, etc. If only no Lot is specified its ID has to be set to '0' thus indicating that the procurement procedure is not divided into Lots. Use the schemeAgencyID attribute where necessary.Reg:
SC: BR-LOT-10, BR-LOT-30-S10, BR-OTH-02
Common: 

 


1..n

Criterion

A tendering criterion describes a fact or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidate tenderers to the award decision

 

 

cac:TenderingCriterion

Tendering Criterion. Details

 Reg:
SC: BR-LOT-20, BR-LOT-30, BR-LOT-30-S20
Common: BR-TC-01

tir92-070

x

1..1

Criterion identifier

A language-independent token, e.g., a number, thatallowstoidentifyacriterion uniquely as well as allows to reference the criterion in other documents. A criterion describes a fact that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used in the award decision.

Identifier

tbr92-015
tbr92-016

TenderingCriterion /cbc:ID

Tendering Criterion. Identifier

Rule: An identifier to refer to the Criterion requirement.  Compulsory use of the IDs defined in the list "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods". E-Certis uses the same IDs. Criteria which are added manually should also use UUID version 4.Reg:
SC:
Common: BR-TC-02, BR-TC-12, BR-TC-13, BR-OTH-02

tir92-071

x

1..n

Criterion type code

A classification code defined by the ESPD-EDM to represent the criterion in the ESPD taxonomy of criteria

Code

tbr92-015
tbr92-016

TenderingCriterion /cbc:CriterionTypeCode

Tendering Criterion. Criterion Type Code. Code

Rule: A code signifying the type of Criterion coming from e-Certis. Compulsory use of the Code List “CriteriaType” which are described in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods", e.g. CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION, CRITERION.EXCLUSION.SOCIAL.ENVIRONMENTAL_LAW, CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, etc.).Reg:
SC:
Common: BR-TC-03, BR-TC-04, BR-OTH-01, BR-OTH-01#7, BR-OTH-03

tir92-072

x

0..1

Criterion name

A short and descriptive name for a criterion. A criterion describes a fact that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used in the award decision or to assess the eligibility of an economic operator.

Text

tbr92-015
tbr92-016

TenderingCriterion /cbc:Name

Tendering Criterion. Name

Rule: The name should be the same as in the in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods", e.g. 'Convictions', 'Corruption', 'Fraud', 'Financial ratio', 'Subcontracting proportion', 'Allowance of checks', etc. At a later stage they might be provided by eCERTIS in dependence of Criterion.Reg:
SC:
Common: BR-TC-05

tir92-073

x

0..1

Criterion description

An extended description of the criterion.

Text

tbr92-015
tbr92-016

TenderingCriterion /cbc:Description

Tendering Criterion. Description. Text

Rule (TRDM092-35): The description should be the same as in the in the spreadsheets "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods", e.g. 'Has the economic operator entered into agreements with other economic operators aimed at distorting competition?'. At a later stage they might be provided by eCERTIS in dependence of Criterion.Reg:
SC:
Common: BR-TC-06, BR-TC-19

tir92-507


0..1

Criterion weight

A weighting to provide for automatic scoring of the Criterion.

Text

tbr92-015
tbr92-016

TenderingCriterion /cbc:WeightNumeric

Tendering Criterion. Weight Numeric. Numeric

Rule: Used only in Self-contained ESPDs namely for ability and professional selection criteria in procedures organised in two stages.Reg:
SC:BR-2P-10-S10, BR-2P-10-S10#1, BR-2P-10-S20#1
Common:

tir92-508


0..1

Criterion evaluation method type

A code signifying the type of Evaluation. ESPD: Compulsory use of the Code List “EvaluationMethodType”

Code

tbr92-015
tbr92-016

TenderingCriterion /EvaluationMethodTypeCode

Tendering Criterion. Evaluation Method Type Code. Code

Rule: Compulsory use of the Code List “EvaluationMethodType”.Reg:
SC: BR-2P-10-S10#2, BR-2P-10-S20, BR-OTH-01, BR-OTH-03, BR-OTH-01#8, BR-OTH-03
Common:

tir92-509


0..1

Evaluation method description

The textual description of the applied weighting and evaluation method

Text

tbr92-015
tbr92-016

TenderingCriterion /cbc:WeightingConsiderationDescription

Tendering Criterion. Weighting Consideration Description. Text

Comment: Used only in Self-contained ESPDs namely for ability and professional selection criteria in procedures organised in two stages. 

 


0..n

Criterion

Subsidiary criteria

 

 

TenderingCriterion /cac:SubTenderingCriterion

SubTenderingCriterion.Details

Used to add susidiary tendering criteria  

 


0..n

Criterion legislation

 

 

 

TenderingCriterion /cac:Legislation

Legislation. Details

Rule: Comment for "LangID" - If not specified defaults to `en (English)`Reg:
SC:
Common: BR-TC-08, 2. BR-OTH-01, BR-OTH-01#9, BR-OTH-03

tir92-510


0..1

Legislation identifier

An identifier to refer to the legislation. ESPD: If a DOI (Digital Object Identifier) exists for this legislation please use it here.

Identifier

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:ID

Legislation. Identifier

Rule: An identifier to refer to the legislation. ESPD: If a DOI (Digital Object Identifier) exists for this legislation please use it here.Reg:
SC: BR-OTH-02
Common: 

tir92-130

x

1..1

Legislation title

Title of the legislation.

Text

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:Title

Legislation. Title. Text

Rule: The complete title of the legislation provided in the original legal text MUST be provided. At a later stage they might be provided by eCERTIS in dependence of Criterion. (e.g.'DIRECTIVE 2014/24/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 26 February 2014 on public procurement and repealing Directive 2004/18/EC'). Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-09

tir92-131

x

0..1

Legislation description

Textual description of the legislation.

Text

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:Description

Legislation. Description. Text

Rule: The description of the legislation provided in the original legal text SHOULD be provided. At a later stage they might be provided by eCERTIS in dependence of Criterion. Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-10

tir92-132

x

0..1

Jurisdiction level

Jurisdictional level of a particular legislation.

Text

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:JurisdictionLevel

Legislation. Jurisdiction Level. Text

Rule: Compulsory use of the description in Code List "LegislationType". Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-OTH-03, BR-OTH-01#10, BR-OTH-03

tir92-133

x

0..1

Legislation article

Textual description of the article of the legislation.

Text

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:Article

Legislation. Article. Text

Rule Other articles where the Criterion is referred to SHOULD also be provided. At a later stage they might be provided by eCERTIS. Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).Reg:
SC:
Common: BR-TC-11

tir92-134

x

0..1

Legislation URI

URI that points to a particular legislation

Identifier

tbr92-015
tbr92-016

TenderingCriterion /Legislation /cbc:URI

Legislation. URI. Identifier

Comment: In the case of European legislation, the URL MUST point at the multilingual EUR-LEX web-page; e.g. Directive 2014/24/EU 

 


0..n

Criterion requirement group

 

 

 

TenderingCriterion /cac:TenderingCriterionPropertyGroup

TenderingCriterionPropertyGroup. Details

Rule: This attribute is defined in the ESPDRequest. In the case of the RequirementGroup element the ESPD Service uses this attribute to specify how the elements within the group should be processed. Reg:
SC:
Common: BR-TC-07, BR-TC-16

tir92-320

x

0..1

Criterion requirement group identifier

An identifier thatallowstoidentifyagroup of requirements uniquely.

Text

tbr92-015
tbr92-016

TenderingCriterion /TenderingCriterionPropertyGroup /cbc:ID

Tendering Criterion Property Group. Identifier

Rule: Compulsory use of the UUIDs in the in the spreadsheets “ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00”.  At a later stage they might be provided by eCERTIS. Groups which are added manually (e.g. national criteria) should also use UUID version 4. Reg:
SC:
Common: BR-TC-12, BR-OTH-02,  BR-OTH-02#01

tir92-526


0..1

Criterion requirement group type code

Code specifying the type of the group.

Text

tbr70-013
tbr70-004

TenderingCriterion /TenderingCriterionPropertyGroup /cbc:CriteriaGroupTypeCode

Tendering Criterion Property Group. Criteria Group Type Code. Code

Rule: Compulsory use of the Code List "PropertyGroupType". Beware that the first element inside a group of properties (after the group ID) is always a cac:TenderingCriterionProperty. In some occasions this might entail the use of an empty CAPTION element, for instance, to produce groups of subgroups where no property does really makes sense in the first group.Reg:
SC:
Common: BR-TC-14, BR-TC-15, BR-OTH-01, BR-OTH-01#11, BR-OTH-03

 


0..n

Criterion requirement group

Subsidiary requirement groups

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /cac:SubsidiaryTenderingCriterionPropertyGroup

SubsidiaryTenderingCriterionPropertyGroup. Details

Rule: Used to add susidiary tendering criteria groups. A second, third or n-level group inside a first level group of properties.Reg:
SC:
Common: BR-TC-17

 


1..n

Criterion requirement

 

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /cac:TenderingCriterionProperty

TenderingCriterionProperty. Details

Comment: The CA specifies the criterion requirement and expected responses to be given by the economic operator. The request for data is answered by the Economic Operator in the Qualification Application Response document this information as a basis.

Reg:
SC: BR-SC-20
Common:

 

tir92-135

x

1..1

Criterion requirement identifier

Identifier of the requirement that fulfills an specific criterion.

Identifier

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ID

TenderingCriterionProperty. Identifier

Rule: Requirement identifiers must use UUID numbers (version 4) automatically generated. The responses of the economic operator (in the ESPD Response document) will refer to this UUID to link the response with one, and only one, criterion property. Requirements which are added manually should also use UUID version 4. Reg:
SC:
Common: BR-TC-18, BR-OTH-02

tir92-511


0..1

Criterion requirement name

The name of the Criterion requirement

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:Name

TenderingCriterionProperty. Name


 

tir92-136

x

1..1

Criterion requirement description

Description of the requirement that fulfils a specific criterion.

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:Description

TenderingCriterionProperty. Description. Text

Rule: The text of the caption, requirement or question is mandatory.Reg:
SC:
Common: BR-TC-19
tir92-601
1..1Criterion requirement typeThe type of criterion requirement. Used to verify that structure of the criterion requirement is correct.Codetbr92-015
tbr92-016
tbr92-018
TenderingCriterion/TenderingCriterionPropertyGroup/TenderingCriterionProperty/cbc:TypeCodeTenderingCriterionProperty. Type Code. CodeRule: Compulsory use of the Code List 'CriterionElementType'. Possible types are 'CAPTION, REQUIREMENT and QUESTION'. If the type is CAPTION or REQUIREMENT no answer is expected from the economic operator and therefore the cbc:ValueDataTypeCode must be set to NONE. Otherwise this value must be set to one of the values defined in the Code List 'ResponseDataType'Reg:
SC: BR-TC-20, BR-OTH-01, BR-OTH-01#14, BR-OTH-03
Common: 

tir92-512

x

1..1

Expected response data type

The data type of the numeric value and any constraints on the data type metadata. ESPD: The expected type of the data. Compulsory use of the Code List “ResponseDataType”.

Code

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueDataTypeCode

Tendering Criterion Property. Value Data Type Code. Code

Rule: Compulsory use of the Code List “ResponseDataType”. Verify that the value is different to NONE for properties of type QUESTION.Reg:
SC:
Common: BR-TC-21, BR-OTH-01, BR-OTH-03, BR-OTH-01#12, BR-OTH-03

tir92-513


0..1

Expected response value unit

The unit of measure of the numeric value as a quantity or measure.

Code

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueUnitCode

Tendering Criterion Property. Value Unit Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC: BR-OTH-01
Common: 

tir92-514


0..1

Expected response currency

The currency of the numeric value as an amount.

Code

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ValueCurrencyCode

Tendering Criterion Property. Value Currency Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC:
Common: BR-OTH-01

tir92-515


0..1

Expected identifier

The expected identifier that the responder has to provide in the Criterion response.

Identifier

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedID

Tendering Criterion Property. Expected_ Identifier. Identifier

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.Reg:
SC: BR-LOT-40
Common: 

tir92-516


0..1

Expected response code

The expected code that the responder has to provide in the Criterion response.

Code

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedCode

Tendering Criterion Property. Expected_ Code. Code

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

For the the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, a "Response Value. Response Code. Code" MUST use the same code from the list "Ratio Type" that is described in the "Tendering Criterion Property. Expected_ Code. Code"
For the the Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION , a "Response Value. Response Code. Code" MUST use the same code from the list "BidType" that is described in the "Tendering Criterion Property. Expected_ Code. Code"

Reg:
SC: BR-OTH-01, BR-OTH-01#23, BR-OTH-01#24
Common: 

tir92-517


0..1

Expected response value

The expected value that the responder has to provide in the Criterion response.

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:ExpectedValueNumeric

Tendering Criterion Property. Expected_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir92-518


0..1

Expected maximum response value

The maximum value the response must have.

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:MaximumValueNumeric

Tendering Criterion Property. Maximum_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir92-519


0..1

Expected minimum response value

The minimum value the response must have.

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:MinimumValueNumeric

Tendering Criterion Property. Minimum_ Value. Numeric

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

tir92-520


0..1

Expected response certification level

The description of the level of the expected certification.

Text

tbr92-015
tbr92-016
tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cbc:CertificationLevelDescription

Tendering Criterion Property. Certification Level Description. Text

Rule: Verify that the value of cac:TypeCode is set to QUESTION and that the `cac:ValueTypeCode`is different to NONE.

 


0..1

Criterion fulfillment time period

 

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod

 

Comment: The ESPD-EDM does only expect start date and end date.  

tir92-171


0..1

Period start date

The date when the period starts. The date is the first day of the period.

Date

tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:StartDate

Period. Start Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD") 

tir92-173


0..1

Period end date

The date on which the period ends. The date is the last day of the period.

Date

tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:EndDate

Period. End Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD") 

 


1..n

Criterion requirement response

 

 

 

cac:TenderingCriterionResponse

Tendering Criterion Response. Details

Rule: A class to describe a response to a criterion property.Reg:
SC: BR-RESP-80, BR-RESP-80-S10, BR-RESP-80-S20
Common: BR-LEAD-10

tir92-158

x

0..1

Criterion response identifier

A language-independent token, e.g., a number, that allows to identify a criterion response uniquely as well as allows to reference the criterion response in other documents. A criterion response describes how an economic operators fulfills an specific criterion.

Identifier

tbr92-018
tbr92-007
tbr92-005
tbr92-006

TenderingCriterionResponse /cbc:ID

Tendering Criterion Response. Identifier

Rule: An identifier for this criterion requirement response. This id SHOULD be provided by the EO or the service provider that instantiates the ESPDResponse XML document.Reg:
SC:
Common: BR-TCR-05, BR-OTH-02, 

tir92-524

x

1..1

Validated criterion requirement identifier

A cross-reference to the criterion requirements which is validated thorugh this response expressed as an identifier.

Identifier

tbr92-018
tbr92-007
tbr92-005
tbr92-006

TenderingCriterionResponse /cbc:ValidatedCriterionPropertyID

Tendering Criterion Response. Validated Criterion Property Identifier. Identifier

Rule: This ID MUST point at one of the TenderingCriterionProperty/cbc:ID that were included in the Request document.Reg:
SC:
Common: BR-RESP-30, BR-RESP-40, BR-RESP-60, BR-RESP-60-S10, BR-RESP-60-S20, BR-TCR-01, BR-TCR-03, BR-LEAD-10-S20, BR-LEAD-10-S30

tir92-525


0..1

Response confidentiality level code

A code specifying the confidentiality level of the given response for this criterion.

Code

tbr92-018
tbr92-007
tbr92-005
tbr92-006

TenderingCriterionResponse /cbc:ConfidentialityLevelCode

Tendering Criterion Response. Confidentiality Level Code. Code

Rule: Compulsory use of the Code List ConfidentialityLevel.
Comment: If the value is "confidential", all the evidences associated to this response become also confidential.
Reg:
SC: BR-TCR-02, BR-OTH-01, BR-OTH-01#19, BR-OTH-03
Common: 

tir92-526

x

0..1

Evidence identifier

The identifier of the referenced evidence.

Identifier

tbr92-018
tbr92-007
tbr92-005
tbr92-006

/QualificationApplicationResponse /cac:TenderingCriterionResponse /cac:EvidenceSupplied /cbc:ID

Evidence Supplied. Identifier

Rule (TRDM092-46): The identifier of the referenced evidence using UUID version 4.This ID MUST point at one of the cac:Evidence/cbc:ID.Reg:
SC:
Common: BR-TCR-09, BR-OTH-02

 


0..n

Declaration fulfilment

 

 

 

TenderingCriterionResponse /ResponseValue/

Tendering Criterion Response. Details

Rule: This class contains the main disjoint elements used to provide the actual answer. The UBL-2.2 model provides cardinality 1..n, this allows for building up lists of, namely, identifier and code values that are all "packaged" into one cac:TenderingCriterionResponse that in turn is linked to one cac:TenderingCriterionProperty.Reg:
SC:
Common: BR-TCR-08, BR-TCR-04

tir92-527


0..1

Criterion fulfillment identifier

An identifier to refer to the criterion requirement response value.

Identifier

tbr92-018

TenderingCriterionResponse /ResponseValue/cbc:ID

Response Value. IdentifierRule: use a UUDI-version 4 number on Response value identifier.Reg:
SC: BR-TCR-05
Common: 

tir92-165

x

0..n

Criterion fulfillment description

Textual description of the fulfilment of this criterion.

Text

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:Description

Response Value. Description. Text

Comment: The ESPD-EDM uses this element to place a response that is a string. UBL-2.2 instead uses cbc:Response, for this. This is something that needs to be reviewed and agreed between ESPD-EDM and future versions of the UBL. See the XML provided in this ESPD-EDM specifications for details on its usage. 

tir92-162

x

0..1

Criterion fulfillment amount

Declared amount that fulfills this criterion.

Amount

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseAmount

Response Value. Response Amount. Amount

Rule: The currencyID attribute is MANDATORY (e.g. "EUR"). Compulsory use of the code list "ISO 4217 3A:2015". BEWARE that amounts can use decimal separators (e.g. 14134,95 but not hundred or thousand separators)Reg:
SC:
Common: BR-OTH-01, BR-OTH-01#17, BR-OTH-03

tir92-167

x

0..1

Criterion fulfillment code

Event declared to fulfil this criterion, expressed as a code.

Code

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseCode

Response Value. Response Code. Code

Rule: Compulsory use of the attributes mentioned in the section "II.4 Codes and Identifiers" for codes.

For the the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, a "Response Value. Response Code. Code" MUST use the same code from the list "Ratio Type" that is described in the "Tendering Criterion Property. Expected_ Code. Code"
For the the Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION , a "Response Value. Response Code. Code" MUST use the same code from the list "BidType" that is described in the "Tendering Criterion Property. Expected_ Code. Code"

Reg:
SC: BR-OTH-01; BR-OTH-01#23, BR-OTH-01#24
Common:

tir92-166

x

0..1

Criterion fulfillment date

Declared date where  this criterion was fulfilled.

Date

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseDate

Response Value. Response Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD") 

tir92-530


0..1

Criterion fulfillment response identifier

An identifier used as a reply to the criterion requirement response.

Identifier

tbr92-018

TenderingCriterionResponse/ResponseValue/cbc:ResponseIDResponse Value. Response Identifier. IdentifierComment: Compulsory use of the attributes mentioned in the section "II.4 Codes and Identifiers" for codes. Several identifiers may be linked to one criterion property thus building a list of identifiers. See XML examples (e.g. in Self-contained references ESPD Response, 'Lots tendered the EO tenders to'). 

tir92-160

x

0..1

Criterion fulfillment indicator

Indicates whether the economic operator states that he fulfills the specific criterion (true) or not (false).

Indicator

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseIndicator

Response Value. Response Indicator. IndicatorRule: The only possible values are False and TrueReg:
SC:
Common: BR-TCR-06, BR-TCR-07

tir92-531


0..1

Criterion fulfillment measure

A measure used as a reply to the criterion requirement.

Measure

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseMeasure

Response Value. Response Measure. Measure
 
tir92-557x

0..1

Criterion fulfillment numeric

A number, rate or percent used as a reply to the criterion requirement.

Numeric

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseNumeric

Response Value. Response Numeric. Numeric

Rule: do not format the percentage with the "%" symbol, just provide a float value like in the example (e.g. 0.4) 

tir92-163

x

0..1

Criterion fulfillment quantity

UOM shouldbestated byusingrecommendation 20 v10 Declared quantity that fulfills this criterion.

Quantity

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseQuantity

Response Value. Response Quantity. Quantity

Comment: BEWARE that different types of Quantities can be required, some of them with a special attribute. Up to three different types of Quantities can be specified: (1) QUANTITY_INTEGER, a number representing a quantity in a specific unit of measure. The unit has to be specified (e.g. number of workers); (2) QUANTITY_YEAR, a non-negative integer (i.e. a natural number) representing a year. The unit has to be specified as YEAR, and (3) QUANTITY, a number representing a generic quantity with no unit specified (e.g. a ratio). Beware that in the case of QUANTITY_INTEGER and QUANTITY_YEAR the attribute unitCode MUST be always specified  

tir92-532


0..1

Criterion fulfillment time

A time used as a reply to the criterion requirement.

Time

tbr92-018

TenderingCriterionResponse /ResponseValue /cbc:ResponseTime

Response Value. Response Time. TimeRule: Use XSD time (format "hh:mm:ss") 
tir92-558
0..1Criterion fulfillment URIA URI used as a reply to the criterion property.URItbr92-018TenderingCriterionResponse/ResponseValue/cbc:ResponseURIResponse Value. Response URI. Identifier

 


0..1

Response fulfillment time period

 

 

 

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod

Period. DetailsRule: The ESPD-EDM does only expect start date and end date. 

tir92-171


0..1

Period start date

The date when the period starts. The date is the first day of the period.

Date

tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:StartDate

Period. Start Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD") 

tir92-173


0..1

Period end date

The date on which the period ends. The date is the last day of the period.

Date

tbr92-018

TenderingCriterion /TenderingCriterionPropertyGroup /TenderingCriterionProperty /cac:ApplicablePeriod /cbc:EndDate

Period. End Date. Date

Rule: Use XSD Date (format "YYYY-MM-DD") 

 


0..n

Evidence

 

 

 

cac:Evidence

EvidenceSupplied. Details

Used to point at an instance of the cac:Evidence.. 

tir92-137

x

1..1

Evidence identifier

Identifier for an evidence.

Identifier

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:ID

Evidence. Identifier

Rule: The Evidence ID MUST be unique in the ESPD Response XML instance (i.e. two evidences cannot have the same ID value). It is recommended to use always a UUID UUID of version 4 (random generated UUID).Reg:
SC:
Common: BR-TCR-09, BR-OTH-02, BR-TCR-05

tir92-138


0..1

Evidence type code

Type code for an evidence.

Code

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:EvidenceTypeCode

Evidence. Evidence Type Code. Code

Rule: A code signifying the type of evidence. Could be used in the future in alignment to e-Certis.Reg:
SC: BR-OTH-01
Common: 

tir92-139


0..1

Evidence name

The name of an evidence.

Text

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:Name

Evidence. Name

Comment:  Could be used in the future in alignment to e-Certis.

tir92-524


0..1

Candiate Statement

Information about a candidate statement that the contracting authority accepts as a sufficient response.

Text

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:CandidateStatement

Evidence. Candidate_ Statement. Text


 

tir92-141


0..1

Evidence description

A textual description of the evidence.

Text

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:Description

Evidence. Description. Text


 

tir92-142


0..1

Response confidentiality level code

A code specifying the confidentiality level of the evidence provided for this criterion.

Identifier

tbr92-017
tbr92-007
tbr92-006

/QualificationApplicationResponse /cac:Evidence /cbc:ConfidentialityLevelCode

Evidence. Confidentiality Level Code. CodeRule: Compulsory use of the Code List ConfidentialityLevel. Software application should set this code to CONFIDENTIAL automatically when the confidentiality level code of at least one criterion to which this evidence is associated is set to CONFIDENTIAL.Reg:
SC: BR-TCR-02, BR-OTH-01, BR-OTH-01#18, BR-OTH-03
Common: 

 


0..1

Evidence issuer party

 

 

 

cac:Evidence/cac:DocumentReference/cac/IssuerParty/Party. Details

tir92-143


0..1

Evidence issuer party identifier

The identifier of the party issuer of the evidence.

Identifier

tbr92-017
tbr92-007
tbr92-006

cac:Evidence/cac:DocumentReference/cac:IssuerParty/cac:PartyIdentification/cbc:ID

Party Identification. Identifier

Rule: Provide an ID for the issuing party. Make use of the attribute SchemeAgencyID. When possible use the VAT identification of the issuing party (see the VIES platform for a EU cross-border national VAT number verification system).Reg:
SC: BR-OTH-02
Common: 

tir92-144


0..1

Evidence issuer party name

The name of the party issuer of the evidence.

Text

tbr92-017
tbr92-007
tbr92-006

cac:Evidence/cac:DocumentReference/cac:IssuerParty/cac:PartyName/cbc:Name

Party Name. Name

Comment: ESPD-EDM uses this element to keep the name of the evidence issuer in the ESPD Response XML instance.
tir92-559

0..1

Evidence issuer website

The website of the party issuer of the evidence.

Identifier

tbr92-017
tbr92-007
tbr92-006

cac:Evidence/cac:DocumentReference/cac:IssuerParty/cbc:WebsiteURI

Party. Website_ URI. Identifier


 

 


0..n

Evidence document

 

 

 

cac:Evidence/cac:DocumentReferenceDocument Reference. Details  
tir92-560
0..1Verification CodeAn verification code needed to access the referenced document.Identifiertbr92-017
tbr92-007
tbr92-006
cac:Evidence/cac:DocumentReference/cbc:IDDocument Reference. IdentifierRule: If the reference or verification code is provided for the evidence use this element to place it. This 'code' is used in some countries (e.g. Spain) to check that the document is authentic. If a verification code is supplied you can use an official 'end-point' to retrieve an image (or a PDF) of the document and check that the evidence is authentic.Reg:
SC: BR-OTH-02
Common:

tir92-151

x

0..1

External document URI

The Uniform Resource Identifier (URI) that identifies where the external document is located.

Identifier

tbr92-017
tbr92-007
tbr92-006
cac:Evidence/cac:DocumentReference/Attachment/ExternalReference/cbc:URI

External Reference. URI. Identifier

Comment: If the document exists at a remote location (e.g. in a prequalification agency), then the value should be the URL pointing to the document.  

Code Lists

A number of information elements values are constrained (or should be constrained) to be those in a list of codes known as Code Lists; the specific Code Lists used in business transactions must be common between business partners in order to achieve interoperability. The following table lists the code lists identified by eSENS to be used in this eSENS BIS. The dictionary entry name identifies the name of the element which needs to consider the codes according to this BIS and the ESPD-VCD domain vocabulary (excel file (TO BE UPDATED)). For each code list a corresponding issuer agency is identified including a hyperlink to the source. While the listId uniquely identifies the code list, the genericode files can be used for the implementation.


Vocabulary TermIssuer AgencyFile Name (TO BE UPDATED)
ListID
Tendering Criterion Property. Expected_ Code. Code
Response Value. Response Code. Code
(See Data structure and XML examples for Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION of the SELF-CONTAINED ESPD Request)
Publications Office of the EUBidType-CodeList.gcBidType
Evidence. Confidentiality Level Code. CodeDG GROW (European Commission)ConfidentialityLevel-CodeList.gcConfidentialityLevel
Country. Identification CodeDG GROW (European Commission)CountryCodeIdentifier-CodeList.gcCountryCodeIdentifier
Tendering Criterion. Criterion Type Code. CodeDG GROW (European Commission)ESPD-CriteriaTaxonomy_V2.0.2.gcCriteriaType
TenderingCriterionProperty. Type CodeDG GROW (European Commission)CriterionElementType-CodeList.gcCriterionElementType
CurrencyIDPublications Office of the EUCurrencyCode-CodeList.gcCurrencyCode
Document Reference. Document Type Code. CodeDG GROW (European Commission)DocRefContentType-CodeList.gcDocRefContentType
Party Identification. Identifier @schemeIDDG GROW (European Commission)EOIDType-CodeList.gcEOIDType
Party. Industry Classification Code. CodeDG GROW (European Commission)EOIndustryClassificationCode-CodeList.gcEOIndustryClassificationCode
Economic Operator Role. Role Code. CodeDG GROW (European Commission)EORoleType-CodeList.gcEORoleType
Tendering Criterion. Evaluation Method Type Code. CodeDG GROW (European Commission)EvaluationMethodType-CodeList.gcEvaluationMethodType
Tendering Criterion Property. Expected_ Code. Code
Response Value. Response Code. Code
(Used in the REQUIREMENT "Ratio Type" of the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_ STANDING.FINANCIAL_RATIO . See data structure for this criterion in the SELF-CONTAINED ESPD Request spread-sheet.)
BACH Banque de FranceFinancialRatioType-CodeList.gcFinancialRatioType
“LangID“ attribute of “Legislation. Details”DG GROW (European Commission)EULanguageCode-CodeList.gcLanguageCodeEU
Legislation. Jurisdiction Level. TextDG GROW (European Commission)LegislationType-CodeList.gcLegislationType
ProcedureCode. CodePublications Office of the EUProcedureType-CodeList.gcProcedureType
ProfileExecutionID. IdentifierDG GROW (European Commission)ProfileExecutionID-CodeList.gcProfileExecutionID
Procurement Project. Procurement_ Type Code. CodePublications Office of the EUProjectType-CodeList.gcProjectType
Tendering Criterion Property Group. PropertyGroupTypeCode. CodeDG GROW (European Commission)PropertyGroupType-CodeList.gcPropertyGroupType
QualificationApplicationTypeCode. CodeDG GROW (European Commission)QualificationApplicationType-CodeList.gcQualificationApplicationType
Tendering Criterion Property. Value Data Type Code. CodeDG GROW (European Commission)ResponseDataType-CodeList.gcResponseDataType
Procurement Project. Procurement Sub_ Type Code. CodePublications Office of the EUServicesProjectSubType-CodeList.gcServicesProjectSubType
Tendering Criterion. Weight Numeric. Numeric (optional)DG GROW (European Commission)WeightingType-CodeList.gcWeightingType

Table 11: Code lists

Identifiers

eSENS has to define a policy for the use of identifiers that describes the specific case for Party Identifiers and principles that should be followed cases when eSENS transport infrastructures is used. As the ESPD not necessarily needs to apply these rules the policy for the use of identifiers is not mandatory but an optional element for the ESPD implementation. About the specific use of identifiers this BIS states as follows.


IdentifierConstraints
Qualification Application Request. Identifier


Compulsory use of schemeAgencyID attribute

Qualification Application Response. Identifier
Qualification Application Request. Profile Identifier. Identifier


Use the value "41" for ESPD and "CEN-BII" for the scheme AgencyID attribute

Qualification Application Response. Profile Identifier. Identifier
Qualification Application Request. Version. Identifier


Compulsory use of schemeAgencyID attribute. Changes in content should entail the modification of the version identifier and a reference to the previous version.

Qualification Application Response. Version. Identifier
Qualification Application Request. Contract Folder Identifier. Identifier


Compulsory use of schemeAgencyID attribute. No other constraints (provided by contracting authority)

Qualification Application Response. Contract Folder Identifier. Identifier
Qualification Application Request. UBL Version Identifier. Identifier


Use the value "2.2". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.

Qualification Application Response. UBL Version Identifier. Identifier
Qualification Application Request. UUID. Identifier


Use UUID version 4. Copies of a document should be identified with a different UUID. Compulsory use of schemeAgencyID attribute.

Qualification Application Response. UUID. Identifier
Tendering Criterion Property Group. IdentifierCompulsory use of schemeAgencyID attribute. Compulsory use of the UUIDs in the in the spreadsheets “ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00” (TO BE UPDATED?)
Legislation. IdentifierCompulsory use of schemeAgencyID attribute. If a DOI (Digital Object Identifier) exists for this legislation please use it here.
TenderingCriterionProperty. IdentifierRequirement identifiers must use UUID numbers (version 4) automatically generated. The responses of the economic operator (in the ESPD Response document) will refer to this UUID to link the response with one, and only one, criterion property. Requirements which are added manually should also use UUID version 4.  Compulsory use of schemeAgencyID attribute
Document Reference. Identifier (Evidence)If the reference or verification code is provided for the evidence use this element to place it. This 'code' is used in some countries (e.g. Spain) to check that the document is authentic. If a verification code is supplied you can use an official 'end-point' to retrieve an image (or a PDF) of the document and check that the evidence is authentic. Compulsory use of schemeAgencyID attribute
Procurement Project Lot. IdentifierCompulsory use of schemeAgencyID attribute. Use the value "0" to indicate that this procurement project has no lots.
Document Reference. IdentifierReference number of the Contract Notice in TeD MUST be specified using the follow scheme defined by the Publications Office: [][][][]/S [][][]-[][][][][][] (e.g. 2015/S 252-461137). Compulsory use of schemeAgencyID attribute
Party. Endpoint Identifier. IdentifierCompulsory use of schemeAgencyID attribute. An endpoint identifier may have a scheme identifier attribute (e.g. eSENS Party Identifier Scheme) for eDelivery. Otherwise, use it for online services (e.g. Web Services, REST services, ftp, etc.)
Party Identification. IdentifierMore than one identifier can be specified. Compulsory use of the attribute schemeAgencyID and highly recommended the use of the attribute schemeAgencyID. The preferred identifier is the national VAT number.  
Service Provider Party. Party Identification. IdentifierCompulsory use of schemeAgencyID attribute. In many countries this ID is the VAT number, but in the future it could be the European Unique ID provided by the Business Registers Interconnection System (BRIS).
Qualification Application Request. Customization IdentifierCompulsory use of the value “urn:www.cenbii.eu:transaction:biitrdm070:ver3.0” and the value “CEN-BII " for the “schemeAgencyID”
Qualification Application Response. Customization Identifier

Compulsory use of value “urn:www.cenbii.eu:transaction:biitrdm092:ver3.0” and the value “CEN-BII " for the “schemeAgencyID”

Table 12: Identifiers

Business Rules

In order to facilitate interoperability in cross border trade, sets of business rules should been defined.
The business rules are sets of rules that clarify the content of instances by stating mandatory fields, fixed values (like code lists), dependency between fields in the same object and dependency between different objects. The business rules are grouped into two main sections depending on their scope :

  • rules working on a single object (i.e.: an ESPD Request XML document or an ESPD XML document);
    • check mandatory fields, fixed values and dependencies between fields;
    • check the use of mandatory set of values on specific fields (code lists);
  • rules working on more than one object (e.g. a VCD XML document and an ASIC Container):
    • check information constraints (e.g. file reference checks) including " Multidimensional" checks crossing the barrier between different objects, i.e. metadata versus physical object instances, or "Cross-referencing" checks between the content value (e.g. a VCD that is referenced in an ASIC Container by its UUID must exist).

Each rule has an error level that can be stated as:

  • warning: offering recommendations to improve the quality of the instance or regain full validity
  • fatal: the rule point to a major issue of consistency or data correctness.

The table below collects a set of business rules coming affecting the creation of instances. The terms used in the business rules refer to the corresponding schema elements. The list is an indicative list and will be extended and approved in future versions of this document. MUST rules correspond to an error level that can be stated as fatal, while SHOULD rules correspond to an error level that can be stated as warning.

Common Business Rules

The Common Business Rules are designed for both ESPD Request and Response and reflect the general rules applied to the creation and processing of any ESPD document. 


RuleIDXSD ReferenceTypeFlagDescription (TO BE UPDATED)
BR-TC-01/cac:TenderingCriterion RuleFatalAt least one TenderingCriterion is expected.
BR-TC-02/cac:TenderingCriterion/cbc:IDRuleFatalEach Criterion is defined in e-Certis and must use the UUID supplied by e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].
BR-TC-03/cac:TenderingCriterion /cbc:CriterionTypeCodeRuleFatalClassification code defined by the ESPD-EDM to represent the criterion in the ESPD taxonomy of criteria is mandatory.
BR-TC-04/cac:TenderingCriterion /cbc:CriterionTypeCode RuleFatalCompulsory use of codes coming from e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].
BR-TC-05/cac:TenderingCriterion/cbc:Name RuleWarningThe name should match the one from e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].
BR-TC-06/cac:TenderingCriterion/cbc:Description RuleWarning
The description should match the one from e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods"].
BR-TC-07/cac:TenderingCriterion /cac:TenderingCriterionPropertyGroup RuleFatal
The first level group of properties and sub-groups of properties in the structure of a criterion must match the number of QUESTION_GROUP from ["ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods"].
BR-TC-08/cac:TenderingCriterion/cac:LegislationReferenceInformationInformation The reference to the legislation related to the Criterion is optional.
BR-TC-09/cac:Legislation /cbc:TitleRuleWarningTitle of the legislation is mandatory. 
BR-TC-10/cac:Legislation /cbc:DescriptionRuleWarningThe description of the legislation provided in the original legal text SHOULD be provided.
BR-TC-11/cac:Legislation/cbc:Article RuleWarningOther articles where the Criterion is referred to SHOULD also be provided.
BR-TC-12../cbc:ID RuleFatalThe ID which identifies one specific property is mandatory.
BR-TC-13/cac:TenderingCriterion/../cbc:ID RuleFatalEach Criterion is defined in e-Certis and must use the UUID supplied by e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods"]
BR-TC-14/cbc:PropertyGroupTypeCodeRuleFatalThe code addressed to control the behaviour of the group of criteria is mandatory.
BR-TC-15/cbc:PropertyGroupTypeCodeRuleFatalCompulsory use of the group of criteria supplied by e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods"].
BR-TC-16/cac:TenderingCriterionPropertyGroupRuleFatalProperties related to the tendering criterion must be the ones supplied by e-Certis [see "ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods” and “ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.0.2.ods"].
BR-TC-17/cac:SubsidiaryTenderingCriterionPropertyGroupRuleWarningA second, third or n-level group inside a first level group of properties.
BR-TC-18../cbc:ID RuleFatalThe ID which identifies one specific property is mandatory. And it must use UUID numbers (version 4) automatically generated.
BR-TC-19../cbc:Description RuleFatalThe text of the caption, requirement or question is mandatory.
BR-TC-20..TenderingCriterionProperty/cbc:TypeCode RuleFatalThe type of property is mandatory and it should match the one from e-Certis.
BR-TC-21../cbc:ValueDataTypeCode RuleFatalThe type of answer expected by the contracting authority in the case of a property of type QUESTION, is mandatory and it should match the one from e-Certis.
BR-COM-10/cac:AdditionalDocumentReference/cbc:IDGroup
Information about publication CAN be provided
BR-COM-10#1/cac:AdditionalDocumentReference /cbc:ID RuleFatalIf the document referenced is a Contract Notice published on TED the ID must follow the scheme defined by the Publications Office: [][][][]/S [][][]-[][][][][][] (e.g. 2015/S 252-461137). If at the time of drafting the ESPD document the Publication Office has not published yet the Contract Notice the value 0000/S 000-000000 value must be used to indicate that a temporary identifier is being used
BR-COM-10#2/cac:AdditionalReferenceDocument /cac:Attachment /cac:ExternalReference/ cbc:Description RuleWarningIf the document being referenced is a Notice being published on TED, use two description lines. Use the second description line to place therein the temporary number received from TED.
BR-COM-10#3/cac:AdditionalDocumentReference /cbc:DocumentTypeCode RuleFatalThe type of document being referenced, expressed as a code is mandatory.
BR-COM-10-S10/cac:AdditionalReferenceDocument /cac:Attachment /cac:ExternalReference/ cbc:DescriptionInformation (no schematron rule)
Above the threshold, information about the publication of the contract notice in TED MUST be provided.
BR-COM-10-S20/cac:AdditionalReferenceDocument /cac:Attachment /cac:ExternalReference/ cbc:DescriptionInformation (no schematron rule)
Below the threshold, information about the publication of the contract notice in TED MIGHT be provided.
BR-COM-10-S30/cac:AdditionalReferenceDocument /cac:Attachment /cac:ExternalReference/ cbc:DescriptionInformation (no schematron rule)
Information about the publication of the contract notice in other official gazettes or journals MIGHT be provided.
BR-OTH-01/cbc:…CodeRuleFatalFor codes, this ESPD V2.0.2 specification requires always three mandatory attributes: listID, listAgencyID, and listVersionID.
BR-OTH-01#1../cbc: ProcedureCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “ProcedureCode. Code” MUST have the listID “ PROC / PR_PROC / SECTION IV.1.1”, a listAgencyName and listVersionID.
BR-OTH-01#2../cbc: QualificationApplicationTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “QualificationApplicationTypeCode. Code” MUST  have the listID “ QualificationApplicationType”, a listAgencyName and listVersionID
BR-OTH-01#3../cbc: DocumentTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “Document Type Code. Code” MUST use the Code List ”DocRefContentType”.
BR-OTH-01#4../@ languageIDRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)WarningThe “languageID”  SHOULD be defined in the attribute "LanguageID" using listID "LanguageCodeEU"
BR-OTH-01#5../cac:Country/cbc:IdentificationCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A ”Country. Identification Code” MUST have a list identifier from the code list “CountryCodeIdentifier” (ISO 3166-1 2A:2006)
BR-OTH-01#6/cac:ProcurementProject/cbc:ProcurementTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “Procurement Project. Procurement_ Type Code. Code” MUST use the Code List “ProjectType”.
BR-OTH-01#7../cbc: CriterionTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “Tendering Criterion. Criterion Type Code. Code” MUST use the list identifier attribute "CriteriaType"
BR-OTH-01#8/cac:TenderingCriterion /cbc:EvaluationMethodTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal The “Tendering Criterion. Evaluation Method Type Code. Code” MUST  use the Code List “EvaluationMethodType”
BR-OTH-01#9../cbc:Legislation/@LangIDRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)WarningThe “LangID “attribute of “Legislation. Details” SHOULD be defined in the attribute "LanguageID" using listID "LanguageCodeEU"
BR-OTH-01#10/cac:Legislation/cbc: JurisdictionLevelRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)WarningA ”Legislation. Jurisdiction Level. Text” SHOULD use the description from the Code List “LegislationType”
BR-OTH-01#11/cac:TenderingCriterionPropertyGroup/cbc: Criteria Group Type Code. CodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “ Tendering Criterion Property Group. Criteria Group Type Code. Code”  MUST use of the Code List “PropertyGroupType”.
BR-OTH-01#12/cac:TenderingCriterionProperty/cbc: ValueDataTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A ”Tendering Criterion Property. Value Data Type Code. Code” MUST always use the Code List “ResponseDataType”
BR-OTH-01#13../cbc: ProfileExecutionIDRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A "ProfileExecutionID. Identifier" MUST use the code list "ProfileExecutionID"
BR-OTH-01#14/cac:TenderingCriterionProperty/cbc: TypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A "TenderingCriterionProperty. Type Code. Code" MUST use of the Code List 'CriterionElementType'. Possible types are 'CAPTION, REQUIREMENT and QUESTION'. If the type is CAPTION or REQUIREMENT no answer is expected from the economic operator and therefore the Tendering "Criterion Property. Value Data Type Code. Code" MUST be set to NONE. Otherwise the "Tendering Criterion Property. Value Data Type Code. Code" must be set to one of the values defined in the Code List 'ResponseDataType'
BR-OTH-01#15/cac:Economic Operator Role/cbc:RoleCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal An “Economic Operator Role. Role Code. Code” MUST use the Code List “EORoleType”.
BR-OTH-01#16/cac:FinancialCapability/cbc:ValueAmountRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)WarningThe “FinancialCapability. ValueAmount”  MUST use the code list "ISO 4217 3A:2015" to specify the “currencyID”
BR-OTH-01#17/cac:ResponseValue/cbc:ResponseAmountRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A “Response Value. Response Amount. Amount”  MUST use the code list "ISO 4217 3A:2015" to specify the “currencyID” 
BR-OTH-01#18cac:Evindence/cbc:ConfidentialityLevelCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)WarningA “Confidentiality Level Code. Code” SHOULD use the code list “ConfidentialityLevel”
BR-OTH-01#19/cac:Tendering Criterion Response/cbc:ConfidentialityLevelCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A "Tendering Criterion Response. Confidentiality Level Code. Code" MUST use the Code List "ConfidentialityLevel".  If the value is "confidential", all the "EvidenceSupplied. Details" to this response become also confidential.
BR-OTH-01#20../cbc:IndustryClassificationCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)Fatal A "IndustryClassificationCode" MUST use the Code List EOIndustryClassificationCode.
BR-OTH-01#21cac:EconomicOperatorParty/cac:Party/ cac:PartyIdentification/cbc:ID@schemeIDRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)FatalA "Party Identification. Identifier @schemeID" of the cac:/EconomicOperatorParty class MUST use the "EOIDType" Code list.
BR-OTH-01#22cac:ProcurementProject /cbc:ProcurementSubTypeCodeRule (covered by schematron rules BR-OTH-01 and BR-OTH-03)FatalA "Procurement Project. Procurement Sub_ Type Code. Code" MUST use the "ServicesProjectSubType" Code list.
BR-OTH-01#23

cac:TenderingCriterion /cac:TenderingCriterionPropertyGroup/ cac:TenderingCriterionProperty/cbc:ExpectedCode

cac:TenderingCriterionResponse/ cac:ResponseValue/cbc:ResponseCode

Rule (covered by schematron rules BR-OTH-01 and BR-OTH-03)FatalFor the the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, a "Response Value. Response Code. Code" MUST use the same code from the list "Ratio Type" that is described in the "Tendering Criterion Property. Expected_ Code. Code" 
BR-OTH-01#24

cac:TenderingCriterion /cac:TenderingCriterionPropertyGroup/ cac:TenderingCriterionProperty/cbc:ExpectedCode

cac:TenderingCriterionResponse/ cac:ResponseValue/cbc:ResponseCode

Rule (covered by schematron rules BR-OTH-01 and BR-OTH-03)FatalFor the the Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION , a "Response Value. Response Code. Code" MUST use the same code from the list "BidType" that is described in the "Tendering Criterion Property. Expected_ Code. Code" 
BR-OTH-02../cbc:ID RuleFatalFor identifiers, this ESPD V2.0.2 specification requires at least (and always) the mandatory attribute schemeAgencyID.
BR-OTH-02#01/cac:TenderingCriterion/ cac:TenderingCriterionPropertyGroup/cbc:ID. IdentifierRuleFatal A “TenderingCriterionPropertyGroup. Identifier”  MUST use of the UUIDs in the spreadsheets “ESPDRequest-CriteriaTaxonomy-SELFCONTAINED-V02.00.00”. TenderingCriterionProperties  are added manually MUST  be expressed in a UUID syntax (RFC 4122)
BR-OTH-03../cbc:…CodeRuleFatalCompulsory use of the code list identified within the document [ESPD-CodeLists-V2.0.2.xlsx].
BR-OTH-04see “19 Annex II: Compulsory XSD’s elements"RuleFatalThere are cardinality constraints added by the ESPD which are not defined in the XSD Schema. The elements listed within “19 Annex II: Compulsory XSD’s elements" MUST be used.
BR-OTH-05/cbc:UBLVersionIDRuleFatalIdentifies the earliest version of the UBL 2 schema.
Use the value "2.2". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.
BR-OTH-06/cbc:CustomizationID RuleFatalIdentifies a user-defined customization of UBL for a specific use.
For the ESPDRequest we use the value “urn:www.cenbii.eu:transaction:biitrdm070:ver3.0”. And ESPDResponse we use “urn:www.cenbii.eu:transaction:biitrdm092:ver3.0”.
Compulsory use of the value "CEN-BII" for the schemeAgencyID attribute.
BR-OTH-07/cbc:ProfileID RuleFatalIdentification of the specification.
Use the value "41". Use also "CEN-BII" for the schemeAgencyID attribute.

Table 13: Common Business Rules

Business Rules for ESPD request (Trdm070)

RuleIDXSD ReferenceTypeFlagDescription (TO BE UPDATED)
RegulatedSelf-ContainedCommon
BR-REQ-20/cac:ContractingParty/cac:PartyGroupFatalInformation about the procurer MUST be provided

x
BR-REQ-20#1/cac:ContractingPartyRuleFatalThe ESPD only expects data about one buyer

x
BR-REQ-20#2/cac:ContractingParty/cac:Party /cac:PartyName/cbc:NameRuleFatalUse the official name of the contracting body is mandatory.

x
BR-REQ-20#3/cac:ContractingParty/cac:Party /cac:PostalAddress/cac:Country /cbc:IdentificationCodeRuleFatalThe country of the contracting body must always be specified

x
BR-REQ-20#4/cac:ContractingParty/cac:Party /cac:PartyIdentification/cbc:ID RuleWarningMore than one identifier can be specified

x
BR-REQ-20#5/cac:ContractingParty/cac:Party /cac:ServiceProviderParty /cac:Party /cac:PartyIdentification/cbc:ID RuleFatalAn identifier for the service provider must always be provided

x
BR-REQ-20#6/cac:ContractingParty/cac:Party /cac:ServiceProviderParty /cac:Party/cac:PartyName /cbc:NameRuleFatalThe name of the service provider must always be specified

x
BR-REQ-20#7/cac:ContractingParty/cac:Party /cac:ServiceProviderParty /cac:Party/cac:PostalAddress /cac:Country /cbc:IdentificationCodeRuleFatalThe country of the service provider must always be specified

x
BR-REQ-30/cac:TenderingCriterion/cbc:CriterionTypeCodeRuleFatalExclusion grounds MUST be retrieved from e-Certis ["ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].

x
BR-REQ-30-S10/cac:TenderingCriterion/cbc:CriterionTypeCodeInformation
Information for common exclusion grounds (sections A, B and C) MUST be retrieved from e-Certis ["ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].

x
BR-REQ-30-S20/cac:TenderingCriterion/cbc:CriterionTypeCodeInformation
Information for national exclusion grounds (section D) MUST be retrieved from e-Certis ["ESPD-CriteriaTaxonomy-REGULATED-V2.0.2.ods”].

x
BR-REQ-40/cac:TenderingCriterion/cbc:CriterionTypeCode GroupWarningSelection criteria CAN be provided.

x
BR-REG-10/cac:ProcurementProject/cbc:ContractFolderIDInformation
Information about the procurement procedure MUST be providedx

BR-SC-10/cac:ProcurementProject;
/cbc:ContractFolderID
GroupFatalInformation about the procurement procedure MUST be provided
x
BR-SC-10#1/cac:ProcurementProject /cbc:MainCommodityClassification;  /cac:ProcurementProject /cbc:NameInformation
The Self-contained ESPD adds the possibility for the contracting authority to specify a few more data relevant at evaluation time and for the economic operator:
• The CPV (Common Procurement Vocabulary) codes for the procurement procedure.
• The 'Object of the contract'.

x
BR-SC-10#2/cbc:ProcedureCodeRuleFatal• The ‘type of the procurement’ administrative procedure according to the EU Directives.
x
BR-SC-20cac:TenderingCriterion /cac:TenderingCriterionPropertyGroup/ cac:TenderingCriterionPropertyInformation
When selection criteria is provided, specific requirements for each criteria CAN be provided.
x
BR-2P-10/cbc:WeightScoringMethodologyDescription /cbc:WeightingTypeGroupFatalInformation about weighting MUST be provided
x
BR-2P-10-S10/cac:TenderingCriterion /cbc:EvaluationMethodTypeCode
/cac:TenderingCriterion/cbc:WeightNumeric
RuleFatalFor two-phased procedure with weighted criteria the information about weighting for each criteria within “Technical and professional ability” MUST be provided
x
BR-2P-10-S10#1/cac:TenderingCriterion /cbc:WeightNumericRuleWarningFor two stage procedures it should be possible to weight the "Technical and professional ability". Weighting can be done either using percentage or points for one procedure. The CA should have a free text where they can describe the scoring methodology.
x
BR-2P-10-S10#2/cac:TenderingCriterion /cbc:EvaluationMethodTypeCodeRuleWarningThe rest of selection criteria should be always PASS/FAIL.
x
BR-2P-10-S20/cac:TenderingCriterion /cbc:EvaluationMethodTypeCodeRuleWarningFor two-phased procedure without weighted criteria, additional information regarding weighting IS NOT required
x
BR-2P-10-S20#1/cac:TenderingCriterion/cbc:WeightNumericRuleWarningIf evaluation method is pass/fail, weighting is not required.
x
BR-LOT-30• /cac:ProcurementProjectLot
• /cac:TenderingCriterion
GroupFatalInformation about lots MUST be provided
x
BR-LOT-30-S10/cac:ProcurementProjectLot /cbc:ID RuleFatalThe number of lots into which the procurement procedure is divided MUST be provided.
x
BR-LOT-30-S20/cac:TenderingCriterionInformation
Additional information regarding lots CAN be provided.
x
BR-LOT-40/cac:TenderingCriterionPropertyGroup/ cac:TenderingCriterionProperty/ cbc:ExpectedIDRuleFatalWhen selection criteria is provided, the lots each criteria applies to MUST be provided.
x
BR-LOT-20 /cac:TenderingCriterion[0..n], CRITERION.OTHER.CA_DATA.LOTS_SUBMISSIONRuleFatalThe set of lots that apply to the information provided in response to the requirements for each selection criterion MUST be provided.
x


Table 14: Business Rules for ESPD request (Trdm070)

Business Rules for ESPD response (Trdm092)


RuleIDXSD ReferenceTypeFlagDescription (TO BE UPDATED)
RegulatedSelf-ContainedCommon
BR-SC-10/cac:ProcurementProject /cbc:ContractFolderIDRuleFatalInformation about the procurement procedure MUST be provided
x
BR-SC-20cac:TenderingCriterion /cac:TenderingCriterionPropertyGroup /cac:TenderingCriterionPropertyInformation
When selection criteria is provided, specific requirements for each criteria CAN be provided.

x
BR-RESP-10/cac:EconomicOperatorPartyGroupFatalInformation about the economic operator MUST be provided

x
BR-RESP-10-01/cac:EconomicOperatorParty /cac:QualifyingPartyRuleFatal Qualifying party / Party identifier: The attribute schemeAgencyID must hold the value retrieved from eCertis that identifies unequivocally the (pre)qualification system. If, for any reason, that value is not available use the default schemeAgencyID "EU-COM-GROW" and the cac:EconomicOperatorParty /cac:PartyIdentificaton /cbc:ID for the value of the identifier. Additionally you can use the data structure CRITERION.OTHER.EO_DATA.REGISTERED_ IN_OFFICIAL_LIST to specify an alternative or additional name, identifier and description.
x
BR-RESP-10-02/cac:EconomicOperatorParty /cac:EconomicOperatorRole/cbc:Role DescriptionRuleFatalThis element is compulsory in the ESPD-EDM V2.0.2 because depending on it different sets of data will be required or not, shown or hidden, processed or skipped.

x
BR-RESP-10-03/cac:EconomicOperatorParty /cac:EconomicOperatorRole /cbc:RoleCodeRuleFatalIdentifies the role of the economic operator in the bid.
x
BR-RESP-10-04/cac:EconomicOperatorParty /cac:Pary/cac:PartyIdentification/cbc:IDRuleFatalAn identifier that identifies the economic operator is mandatory.

x
BR-RESP-10-05/cac:EconomicOperatorParty/cac:Pary /cac:PartyName/cbc:NameRuleFatalThe name of the economic operator is mandatory.

x
BR-RESP-10-06cac:EconomicOperatorParty/cac:Party /cbc:IndustryClassificationCodeRuleFatalIndustrial classification: Compulsory use of the element.

x
BR-RESP-10-07/cac:EconomicOperatorParty /cac:Party/cac:PostalAddress /cac:Country /cbc:IdentificationCodeRuleFatalThe country of the contracting body must always be specified.

x
BR-RESP-10-08/cbc:EndpointID/@schemeIDRuleFatalAn end-point identifier MUST have a scheme identifier attribute.

x
BR-RESP-10-09../cac:ServiceProviderParty /cac:Party/cac:PartyName/cbc:NameRuleFatalThe name of the service provider must always be specified.

x
BR-RESP-10-10../cac:ServiceProviderParty /cac:Party/cac:PostalAddress/cac:Country /cbc:IdentificationCodeRuleFatalThe country of the service provider must always be specified.
x
BR-RESP-10-11.. /cac:ServiceProviderParty /cac:Party/cac:PartyIdentification/cbc:IDRuleFatalAn identifier for the service provider must always be provided.

x
BR-RESP-20/cac:EconomicOperatorParty/cac:Party /cac:PowerOfAttorney/AgentParty/cac:PersonGroupWarningInformation about representatives of the economic operator CAN be provided

x
BR-RESP-20-01cac:EconomicOperatorParty/cac:PowerOfAttorney /cac:AgentParty/cac:Person/cbc:FirstNameRuleFatalName of the natural person is mandatory

x
BR-RESP-20-02cac:EconomicOperatorParty/cac:PowerOfAttorney/ cac:AgentParty/cac:Person /cbc:FamilyNameRuleFatalFamily Name of the natural person is mandatory

x
BR-RESP-20-03cac:EconomicOperatorParty /cac:PowerOfAttorney/ cac:AgentParty/cac:Person /cac:ResidenceAddress/cac:Country /cbc:IdentificationCodeRuleFatalA code that identifies the country is mandatory

x
BR-RESP-30/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDRuleFatalInformation about compliance of exclusion grounds MUST be provided if no pre-qualification system is used.

x
BR-RESP-40/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDRuleFatalInformation about compliance of selection criteria MUST be provided; and, Response to the specific requirements related to selection criteria of the ESPDRequest MUST be provided if no pre-qualification system is used.

x
BR-RESP-50/cac:EconomicOperatorParty /cac:QualifyingParty/cac:Party /cac:PartyIdentification/cbc:ID
 

/cac:TenderingCriterionResponse
RuleFatalInformation about the pre-qualification system the EO is registered on MUST be provided

x
BR-RESP-60/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDRuleWarningInformation about compliance of exclusion grounds CAN be provided if a pre-qualification system is used. 

x
BR-RESP-60-S10/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDInformation
When the pre-qualification system the EO is registered on does not cover all the exclusion criteria, information about compliance of exclusion grounds MUST be provided

x
BR-RESP-60-S20/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDInformation
When the pre-qualification system the EO is registered on covers all the exclusion criteria, information about compliance of exclusion grounds IS NOT required.

x
BR-RESP-80/cac:TenderingCriterionResponseGroupWarningResponse to the specific requirements related to selection criteria of the ESPDRequest CAN be provided
x
BR-RESP-80-S10/cac:EconomicOperatorParty /cac:QualifyingParty/cac:Party /cac:PartyIdentification/cbc:ID; /cac:TenderingCriterionResponseRuleFatalWhen the pre-qualification system the EO is registered on does not cover all the selection criteria, information about compliance of selection criteria MUST be provided.
x
BR-RESP-80-S20/cac:EconomicOperatorParty /cac:QualifyingParty/cac:Party /cac:PartyIdentification/cbc:ID; /cac:TenderingCriterionResponseRuleWarningWhen the pre-qualification system the EO is registered on covers all the selection criteria, information about compliance of selection criteria IS NOT required.
x
BR-LOT-10/cac:ProcurementProjectLot /cbc:IDRuleFatalThe list of lots the EO tenders for MUST be provided.
x
BR-LEAD-10/cac:TenderingCriterionResponseRule/GroupFatalWhen the EO is participating in the procurement procedure together with others, information about the other participants MUST be provided

x
BR-LEAD-10-S10/cbc:EconomicOperatorGroupNameRuleFatalWhen the EO is participating in the procurement procedure in a group (Consortium, Joint Venture or others), information about the group MUST be provided

x
BR-LEAD-10-S20/cac:TenderingCriterionResponse/ cbc:ValidatedCriterionPropertyIDRuleFatalWhen the EO (or any other EO participating in the procurement procedure) relies on the capacities of other entities in order to meet the selection criteria, information about all the entities the EO relies on MUST be provided

x
BR-LEAD-10-S30/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDRuleFatalWhen the EO (or any other EO participating in the procurement procedure) intends to subcontract a share of the contract to third parties, information about all subcontractors MUST be provided

x
BR-TCR-01/cac:TenderingCriterionResponse /cbc:ValidatedCriterionPropertyIDRuleFatalValidated Criterion Property ID MUST point at one of the TenderingCriterionProperty /cbc:ID that were included in the Request document.

x
BR-TCR-02/cac:TenderingCriterionResponse/ cbc:ConfidentialityLevelCodeInformation
If Confidentiality value is true, all the evidences associated to this response becomes also confidential.

x
BR-TCR-03/cac:TenderingCriterionResponse/ cbc:ValidatedCriterionPropertyID RuleWarningThe current structure for the response allows responding values inside the cac:ResponseValue element or in other elements of the cac:TenderingCriterionResponse, like cac:ApplicablePeriod or cac:EvidenceSupplied

x
BR-TCR-04cac:TenderingCriterionResponse /cac:ResponseValue/RuleFatalOne cac:ResponseValue element contains the complete list of possible values for one answer to a criterion property. Only one type of element can be used to answer a criterion property, and that element MUST be of the same type as the one specified as expected in the ESPD Request (element cac:TenderingCriterionProperty /cac:ValueDataTypeCode).

x
BR-TCR-05../cbc:ID/@schemeIDInformation
Recommendation: use a UUDI-version 4 number on Response value identifier.

x
BR-TCR-06/cac:TenderingCriterionResponse /cac:ResponseValue /cbc:ResponseIndicator RuleFatalGroups codified as ONTRUE must be processed if response is True

x
BR-TCR-07/cac:TenderingCriterionResponse /cac:ResponseValue /cbc:ResponseIndicator RuleFatalGroups codified as ONFALSE must be processed if response is False

x
BR-TCR-08/cac:TenderingCriterionResponse /cac:ResponseValue/InformationFatalThe table defined for BR-TCR-08 in the document ESPD_TestCases_mapping_v10.docx lists the relationship between data type and response data type

x
BR-TCR-09/cac:TenderingCriterionResponse /cac:EvidenceSupplied/cbc:IDRuleFatalThe expected Evidence identifier must match the value of a cac:Evidence/cbc:ID present in the XML document.

x

Table 15: Business Rules for ESPD response (Trdm092)

Criteria Data Structures

The contracting body shall provide the exclusion grounds and selection criteria for its tendering process as structured information.The ESPD-EDM which is based on UBL 2.2 defines a flexible structure to express data about criteria and possible responses. The data elements provided by UBL-2.2  can be used to implement XML documents with different criteria structures. Such nesting of criteria, groups of requirements and requirements can end up in complex XML instances which are a barrier for the (semantic) interoperability between systems. Hence, the need of establishing of a minimum set of rules about how to build up such criteria data structures is required.  Version 2.1.0 of the ESPD establishes fixed criteria data structures which are based on the requirements expressed in the Annex to the Regulation 2016/7. The required criteria structures are therefore outlined in sections "IV. Criteria, common aspects" and "V. Exclusion criteria" and "VI. Selection criteria" of the ESPD XML Implementation Guide v2.0.2 (TO BE UPDATED)

The answering of questions related to these criteria structures is further explained in section "VII.7 Answering QUESTIONs". 

An comprehensive specification of the used criteria data structures is additionally provided in the ESPD Data Structure spreadsheets. Among other things, the spreadsheet was used as a prototype tool to generate the XML instances of the criteria data structures used in the ESPD Request and ESDP Response documentsThe meta concepts used in the ESDP-EDM Spreadsheet vocabulary therefore had to be mapped to the UBL-2.2 vocabulary. The table below shows the mapping between both vocabularies and therewith provides an inital understanding for how to implement valid criteria data structures. 


ESDP-EDM Spreadsheet vocabulary

UBL-2.2 vocabulary

CRITERION

cac:TenderingCriterion

SUBCRITERION

cac:SubTenderingCriterion

REQUIREMENT_GROUP

cac:TenderingCriterionPropertyGroup

QUESTION_GROUP

cac:TenderingCriterionPropertyGroup

REQUIREMENT_SUBGROUP

cac:SubsidiaryTenderingCriterionPropertyGroup

QUESTION_SUBGROUP

cac:SubsidiaryTenderingCriterionPropertyGroup

CAPTION

cac:TenderingCriterionProperty

REQUIREMENT

cac:TenderingCriterionProperty

QUESTION

cac:TenderingCriterionProperty

ADDITIONAL_DESCRIPTION_LINE

cbc:Description (namely in cac:TenderingCriterion)

LEGISLATION

cac:Legislation

Table 15: Mapping between the ESPD-EDM criterion data structure (spreadsheet) and the UBL-2.2 vocabulary

Note: This fixed criteria data structure outlined above imposes limitations to the maintainability and evolution of the ESPD and VCD. A dynamic approach where the criteria data structures can be retrieved through an interface based on the data available in e-Certis is currently being addressed by the European Commission in order to overcome these limitations. As long as there is no reliable e-Certis system available which establishes these rules for criteria data structures, this BIS is therefore referencing to the specifications described above.

References (TO BE UPDATED)




[CEN_BII3] http://www.cenbii.eu
[ESDP Exchange Data Model] https://github.com/ESPD/ESPD-EDM/tree/2.1.0
[ESPD XML Implementation Guide] https://espd.github.io/ESPD-EDM/v2.0.0/xml_guide.html
[UBL 2.2] https://www.oasis-open.org/committees/document.php?document_id=60554
[eSENS EIA] http://wiki.ds.unipi.gr/display/ESENS/eSENS+Generic+Architecture+Repository
[eCertis] https://ec.europa.eu/growth/tools-databases/ecertis/
[Directive 2014/24/EU] http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.094.01.0065.01.ENG
[Directive 2014/25/EU] http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:32014L0025
[ETSI ASiC-E] www.etsi.org/deliver/etsi_ts/.../01.../ts_102918v010101p.pdf



Revision History (TO BE UPDATED)

VersionDateAuthorOrganizationDescription
0.107.05.2018

Ansgar Mondorf

Tevriz Iusupova

Ulf Lotzmann

University of Koblenz

Implementation of the changes described in the release notes

Final editing


Release Notes (TO BE UPDATED)

The following changes were applied in this BIS - ESPD (Version 2.0.2) in relation to the BIS - ESPD (Version 2.0.1). All the changes are also reflected in the corresponding Domain Vocabulary for version 2.0.2:

Nr.Description
1.Column "Business Rule IDs" added to the tables in Implementation Guidelines (Trdm070/Trdm092). Tab "Implementation Guideline" updated
2.Code List tables updated.
3.Identifier tables updated.
4.Section Common Business Rules added according to XML validation framework..
5. Business Rules for ESPD Request changed according to XML validation framework.
6. Business Rules for ESPD Request changed according to XML validation framework.
7.Adding the elements EconomicOperatorRoleCode and Qualifiying Agency Identifier to the ESPD Response regulated.
8.Corresponding update of the ESPD v202 domain vocabulary.xls


Contributors

Country

Name

Organization

DE

Ansgar Mondorf

University of Koblenz

DE

Maria Wimmer

University of Koblenz

DE

Ulf Lotzmann

University of Koblenz

DE

Tevriz Iusupova

University of Koblenz

DERoman SokolovUniversity of Koblenz

GR

Jerry Dimitriou

University of Piraeus

GR

Lefteris Leontaridis

University of Piraeus

GR

Andriana Prentza

University of Piraeus

  • No labels