The European Single Procurement Document

Technical Handbook

1. UBL Based and distribution package

Semantic assets have been defined by ISA as "a collection of highly reusable metadata (e.g. xml schemata, generic data models) and reference data (e.g. code lists, taxonomies, dictionaries, vocabularies) which are used for e-Government system development".

1.1. ESPD Distribution package

All the semantic assets needed to implement ESPD electronic documents are organised in a distribution package. The content of this folder is organised as follows:

Distribution package

Figure 5. Distribution package

  1. ESPDTeam: contains files for ESPD Team internal use in maintenance tasks of the ESPD-EDM;

  2. codelists: contains the different code lists used in ESPD in Genericode format and the criterion structure definition.

  3. conceptual-model: contains the UML conceptual model of the ESPD in .eap, .xmi and HTML format.

  4. java-library: contains the XML schemas used to generate the JAXB annotated Java classes.

  5. ubl-2.3: contains a redistribution package from UBL 2.3.

  6. validation: contains business rules validation files for Schematron and Testbed.

  7. xml-examples: contains default ESPDRequest and ESPDResponse xml samples and the criterion xml schema.

1.2. Adoption of UBL-2.3

UBL, developed by the Organization for the Advancement of Structured Information Standards, is a royalty-free library of standard electronic Extensible Markup Language (XML) business documents. It is designed to plug directly into existing business, legal, auditing, and records management practices, and to operate within a standard business framework such as ISO 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing Electronic Data Interchange (EDI) systems to businesses of all sizes.

UBL is also included in the ICT Standards for Procurement (ICT Standards for Procurement): the rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement.

UBL is a specific used in some Member States and by the EU institutions, namely the European Commision. UBL is also referred to in the Commission implementing decision of 31 October 2014 on the identification of Universal Business Language version 2.1 for referencing in public procurement (COM Decision 2014/771/EU).

Technical resources and tools are freely available for its use and repurpose by the Member States, Service Providers, EC and any other stakeholders. Especially interesting and largely used are the open source tools and artefacts referred by the OASIS UBL-TC, such as Genericode , ISO Schematron and Crane Softwright.

The adoption of the new UBL version (UBL 2.3) is related to the alignment between ESPD and eForms, which will ensure and improve the interoperability between models.

1.3. UBL-2.3 Documents and libraries

UBL-2.3 defines thousands of different information components and dozens of documents. This guide describes and illustrates only those elements from UBL-2.3 that are actually used by the eESPD. Thus the ESPD-EDM reuses only a small set of those components and only 2 documents: QualificationApplicationRequest (for the ESPD Request) and QualificationApplicationResponse (for the ESPD Response).

UBL-2.3 distributes two sets of XSD schemas: see folders xsd and xsdrt of the UBL distribution package. The xsd folder contains the schemata fully documented (with dictionary entry names, definitions, examples, etc.); whilst the xsdrt schemata are not likewise documented and are frequently used in production environments (rt stands for "run-time").

The previous ESPD-EDM versions used its own libraries where Criterion and Evidence-related aggregate and components were defined (components prefixed with cac-ccv:, cac-cev, cbc-ccv and cbc-cev).

This new version uses components exclusively defined by UBL-2.3 in two main libraries: Common Aggregate Components (file UBL-CommonAggregateComponents-2.3.xsd.xsd) and Common Basic Components (UBL-CommonBasicComponents-2.3.xsd.xsd).

The usual prefix used to identify Common Aggregate Components is cac:. The prefix for Common Basic Components is cbc:.

All the materials developed by UBL-2.3 Technical Committee can be accessed here: here.

1.4. UBL-2.3 and TOOP Requirements

During the development of ESPD-EDM some requirements arose from TOOP related to the Evidence class. The aforementioned requirements that can be found in the following GitHub issue, are fully mappable to the UBL 2.3 Schema.

To check the mapping, please access to these TOOPRequirements_UBL_2.3.xlsx or TOOPRequirements_UBL_2.3.ods.

1.5. Codes and Identifiers

A code is a shortened way (a number or a short abbreviated text), leading to the definition of a 'concept'. The code represents the concept and is used by software applications to retrieve the definition of the concept or make automatic decisions.

An Identifier, in turn, can be defined as "a value (represented as a short text, a number or a combination of both) used to establish the identity of, and distinguish uniquely, one occurrence of an object following a pattern".

The essential distinctive features between identifiers and codes are:

  1. Identifiers point at specific occurrences of objects (instances); codes replace concepts;

  2. Identifiers are virtually limitless while codes are finite. In other words, identifier lists are "open" (the lists may grow) and code list are "closed" (practically never updated, once consolidated). Hence codes are maintained in 'Codelists' whilst identifiers are usually kept in databases.

  3. Identifiers are in principle maintained in the business domain, e.g. buyer identifiers, economic operator identifiers, exclusion or selection criteria identifiers, etc.

  4. Codes may belong to three different domains:

    1. they can be somehow 'business-agnostic' and be used cross-domain (e.g. country codes, currency codes, language codes, etc.);

    2. business-specific domain (i.e. procurement specific, like codes representing contract types, procurement procedure types, criteria types, etc.); and

    3. business process-specific, i.e. ESPD-specific, such as the data type expected in the response to a criterion, or the type of a criterion property, etc.

Codes and code lists

The ESPD Exchange Data Model tries to reuse as much as possible the codes that are already used for e-Procurement. In any project, like the ESPD-EDM, there are at least three types (or layers) of codes:

  1. Cross-sector, common, codes, like the ones defined and maintained by the ISO for currencies, languages, countries, etc.; or the ones defined by the European Commission that can be used in multiple business domains, e.g. the NUTS defined by EUROSTAT; the ones defined by BACH (Banque de France), etc.;

  2. Business domain-related, maintained by international or European authorities, e.g. the ones defined by UNECE (as unit codes), or by the Publications Office of the European Union (OP), e.g. types of procurement procedures (based on the EU Directives);

  3. Project-specific (or application-specific), i.e. those codes that are particular of the project. Types (taxonomy) of exclusion and selection criteria, types of evaluation method, etc. in the case of the ESPD-EDM.

Moreover, the ESPD will reuse code list from EU Vocabularies. This is due to the alignment between both models, ESPD and eForms to ensure the maximum interoperability. With this purpose ESPD will align the use of certain code lists.

Codes are normally maintained in "code lists". The ESPD-EDM keeps and distributes these code lists in Genericode 1.0 (GC) files (one *.gc file per code list).

However, it is worth to note that those code list that are reused from EU Vocabularies in alignment with eForms are not completely shown in excel and ods files. Instead, the metadata and the location of them in EU Vocabularies is provided.

For the genericodes is different, in this version ESPD will provide the gc files from EU Vocabularies to ensure its use and the validation. In future versions of the ESPD, only will be provided these GC of the code list purely used and maintained by ESPD.

ESPD-EDM Code list contain the following elements:

  • Metadata: information about the code list, e.g. its identifier, the identifier and name of the agency responsible for defining and maintaining the list, the version of the list, etc.

  • Code identifier: the literal (a label composed of characters, numbers and symbols like '_');

  • Concept description: the definition of the concept represented by the code;

  • Multilingual descriptions: the translations of the English definitions.

The figure below illustrate how these elements are organised in the code lists maintained in spread-sheets:

Elements and metadata of an ESPD code list

Figure 6. Elements and metadata of an ESPD code list

The Annex I of this document lists all the code lists used by the ESPD and in which context or element it is used.

Compulsory attributes

Table 1. ESPD Requirement regarding codes

REQUIREMENT:

For codes, this ESPD specification requires always three mandatory attributes: listID, listAgencyID, and listVersionID.

Table 2. ESPD Requirement regarding identifiers

REQUIREMENT:

For identifiers, this ESPD specification requires at least (and always) the mandatory attribute schemeAgencyID. When identifying parties, like the Economic Operator, the Buyer, etc., the attribute schemeID SHOULD also be used (for this use the code list EOIDType).

In UBL Codes and identifiers are based on ebXML Core components (UBL conforms to ebXML CCTS ISO/TS 15000-5:2005 currently maintained by UN/CEFACT).

One convenient characteristic of these two CCT elements (Codes and Identifiers) is that they use a rich set of attributes that allow to identify their pattern, the name of the list, the URI from where to obtain the list, the Agency that maintains the list, the version of the list, and other.

UBL-2.3 CCT are defined in the file CCTS_CCT_SchemaModule-2.3.xsd (see folders xsd/common or xsdrt/common in the distribution package).

The figure below shows the complete list of attributes for the CCT CodeType component.

Code attributes

Figure 7. Code attributes

And its corresponding definitions, as provided by OASIS UBL (ISO/IEC 19845):

Table 3. UBL attributes for codes

Attribute

Definition

listID

The identification of a list of codes (MANDATORY in this version of ESPD).

listAgencyID

An agency that maintains one or more lists of codes (MANDATORY in this version of ESPD).

listAgencyName

The name of the agency that maintains the list of codes.

listName

The name of a list of codes.

listVersionID

The version of the list of codes (MANDATORY in this version of ESPD).

name

The textual equivalent of the code content component.

languageID

The identifier of the language used in the code name.

listURI

The Uniform Resource Identifier that identifies where the code list is located.

listSchemeURI

The Uniform Resource Identifier that identifies where the code list scheme is located.

This other figure shows the attributes for the CCT `IdentifierType`component.

Identifier attributes

Figure 8. Identifier attributes

Table 4. UBL attributes for identifiers

Attribute

Definition

schemeID

The identification of the identification scheme.

schemeName

The name of the identification scheme.

schemeAgencyID

The identification of the agency that maintains the identification scheme (MANDATORY in this version of ESPD).

schemeAgencyName

The name of the agency that maintains the identification scheme.

schemeVersionID

The version of the identification scheme.

schemeDataURI

The Uniform Resource Identifier that identifies where the identification scheme data is located.

schemeURI

The Uniform Resource Identifier that identifies where the identification scheme is located.

And its corresponding definitions, as provided by OASIS UBL (ISO/IEC 19845):

XML Example

This fragment of XML shows how the compulsory attributes are used for the some of the root elements of an ESPD Request document.

<cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.3</cbc:UBLVersionID>

<cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>

<cbc:UUID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="4">0fddbf2d-1e33-4267-b04f-52b59b72ccb6</cbc:UUID>

<cbc:ContractFolderID schemeAgencyID="DGPE">PP.20170419.1024-9</cbc:ContractFolderID>

<cbc:VersionID schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1.0</cbc:VersionID>
  1. The Agency responsible for the maintenance of the UBL versioning is the OASIS UBL Technical Committee

  2. The identifier for this document was issued by the a Spanish Central Government Directorate identified as 'DGPE'

  3. The UUID follows the ISO/IEC Scheme 9834-8:2008 Version 4 and was generated by the European Commission’s Directorate General GROWTH (DG GROW)

  4. The reference number used to identify to which procurement procedure this ESPD document belongs (PP.20170419.1024-9) has been supplied by the Spanish Directorate DGPE

  5. Generic information, such as the content version ID, use always by default the "EU-COM-GROW" Agnecy ID. Notice that the other additional attributes may be also used, as in this example.

  6. Beware that the codes may be numbers, text or combinations of both. These code labels are the ones that are specified in the codelist spreadsheets and XML Genericode files distributed jointly with this specification (in the folder /codelists of the distribution package.

Code list that IS NOT used for CODE values

Code lists contain the code identifiers that are expected as "values" for a data element of type CODE (i.e. a UBL-2.3. cbc:CodeType element). This is case of code lists such as eo-role-type, or docref-content-type, etc.

However, this ESP-EDM specification also uses the code list EOIDType with a different purpose, "the identification of the type of scheme used to identify parties, namely Economic Operators" (but should also used to identify the schemes used to identify Buyers, Service Providers, etc.).

The figure below shows the possible values of this code list. These codes are to be used as values of the schemeID attribute (attribute of the UBL-2.3 element cbc:Identifier):

Values of the schemeID for Party Identifiers

Figure 9. Values of the schemeID for Party Identifiers

The next fragment of XML shows how this is used in the particular case of the Criterion "Relied on entities" ("Does the economic operator rely on the capacities of other entities in order to meet the selection criteria…​?").:

TenderingCriterionProperty (a QUESTION) asking for the identifier of the Economic Operator

...

<cac:TenderingCriterionProperty>

<cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1fa05728-308f-43b0-b547-c903ffb0a8af</cbc:ID>

<cbc:Description>ID of the economic operator</cbc:Description>

<cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>

<cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>

</cac:TenderingCriterionProperty>

...
  1. The identifier of the property will be used in the response to map link the response to this QUESTION.

  2. The ECONOMIC_OPERATOR_IDENTIFIER is mapped to an element cbc:ResponseID in the response (which is based on the UBL-2.3. element cbc:Identifier).

TenderingCriterionResponse (the answer to the previous QUESTION)

...
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">acb58f0e-0fe4-4372-aa08-60d0c36bfcfe</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1fa05728-308f-43b0-b547-c903ffb0a8af</cbc:ValidatedCriterionPropertyID>
<cbc:ResponseID schemeID="VAT" schemeAgencyID="ES-AEAT">B82387770</cbc:ResponseID>
</cac:TenderingCriterionResponse>
...
  1. Notice that this UUID is identical to the QUESTION UUID, which is the mechanism used in UBL to link the answer to the very specific QUESTION it is responding.

  2. The element cbc:ResponseID is of type Identifier(as defined in the Core Component Type Specification library). The value ''VAT'' assigned to the attribute schemeID, taken from the code list EOIDType, is used to indicate that the type of identifier used is the Value Added Tax identifier issued by the Spanish Tax Agency (ES-AEAT).

2. The ESPD Request Document

2.1. ESPD Request Business Requirements

The ESPD-EDM models the business and information requirements in alignment with the works developed by e-Sens, which uses the identifier Trdm070 to refer to the business requirements regarding the ESPD Request transaction. See formal information requirements related to the ESPD Request transaction in the document Business Requirements: ESPD request transaction (Trdm070), by e-Sens.

2.2. ESPD Request XSD Schema

The ESPD-EDM uses the UBL-2.3 document named QualificationApplicationRequest.xsd XSD Schema. This schema can be found under the folder ubl-2.3/xsdrt/maindoc (or the equivalent documented xsd folder).

The figure below shows the XSD Schema defined by UBL-2.3 for the document "Qualification Application Request". This schema replaces the previous scheme form UBL 2.2.

The figure below shows a diagram representing the UBL-2.3 XSD Schema. Only the first level components of the schema are shown. The inner sub-elements and sub-classes are covered in detail in the following sub-sections of this document.

QualificationApplicationRequest-2.3

Figure 11: QualificationApplicationRequest-2.3 main elements.

2.3. ESPD Request cardinalities

As you can see the UBL-2.3 Schema is quite flexible as, except for a few cases practically all the elements are optional.

The ESPD-EDM model, however, adds a few more restrictions regarding the cardinalities of some elements. These can be seen in the diagram below, which presents the ESPD-EDM structure for the ESPD Request with its own cardinality restrictions.

QualificationApplicationRequest'

Figure 12. ESPD-EDM 'QualificationApplicationRequest', UML diagram

If you compare both figures you will observe that:

  1. The cardinalities of the root common basic components, such as cbc:ID, cbc:UUID, are different for the ESPD than for UBL-2.3;

  2. Similarly, the cardinalities of aggregate components like cac:ContractingParty and cac:TenderingCriterion are different to the UBL-2.3 ones.

The cardinality constraints added by the ESPD are not defined in the XSD Schema. In order to control these constraints the ESPD-EDM uses ISO Schematron assertions. The ESPD-EDM distribution package provides Schematron schemata and CVA files for the validation of the XML instances (folder /validation).

2.4. Root elements

The table below lists the elements that are expected in the ESPD Request and provides details on the cardinalities and usage of those elements.

A note about the Business Rules identifiers

From this point on in the document, the tables defining classes and its properties refer frequently to business rules. As stated in the e-Sens BIS document, "[..] 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".

Information requirement:

Beware that all theses documents do share the same business rule identifiers (e.g. tbrxx-yyy for Business Requirement Identifiers in ESPDInt, and BR-Type-Id#n for the Test Cases technical rules).

Table 5. Class QualificationApplicationRequest, components required by the ESPD-EDM

Document name:

QualificationApplicationRequest

Definition 1:

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

Document provided by a buyer defining the exclusion and selection criteria for a given procurement procedure.

Business rule(s):

None

File:

/ubl-2.3/xsd/maindoc/UBL-QualificationApplicationRequest-2.3.xsd

Components Type Card Description Requirements

cbc:UBLVersionID

Identifier

1

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.

Information Requirement: tbr070-002.

Rule: Use the value "2.3". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.

Rule scope: Common (BR-OTH-05, 2.BR-OTH-02)

cbc:CustomizationID

Identifier

1

Identifies a user-defined customization of UBL for a specific use. tbr070-001.

Information Requirement:

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.

Rule scope: Common (BR-OTH-02, BR-OTH-06)

cbc:ProfileID

Identifier

0..1

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.

Information Requirement: tbr070-002.

Rule: Use the value "41". Use also "CEN-BII" for the scheme AgencyID attribute.

Rule scope: Common (BR-OTH-07, BR-OTH-02)

cbc:ProfileExecutionID

Identifier

1

The identification and version of the ESPD Exchange Data Model used to create the XML instance. The identification may include the exact version of the specification.

Information Requirement: tbr070-002.

Rule: Compulsory use of the CodeList ProfileExecutionID. Use the value "EU-COM-GROW" for th SchemeAgencyID attribute.

Rule scope: Common (BR-OTH-01, BR-OTH-01#13, BR-OTH-03)

cbc:ID

Identifier

1

An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, e.g. a buyer, or the supplier, e.g. an economic operator). An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, e.g. a buyer, or the supplier, e.g. an economic operator). The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Information Requirement: tbr070-002.

Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document.

Rule scope: Common (BR-OTH-02)

cbc:CopyIndicator

Indicator

0..1

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

Information Requirement: tbr070-002.

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

cbc:UUID

Identifier

1

A universally unique identifier that can be used to reference this ESPD document instance.

Information Requirement: tbr070-002.

Rule: This UUID will be used to link the ESPD Response to its corresponding ESPD Request (thus its compulsoriness). Copies of a document must be identified with a different UUID. Compulsory use of schemeAgencyID attribute.

Rule scope: BR-OTH-02

cbc:ContractFolderID

Identifier

1

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

Information Requirement: tbr070-007.

Rule: Try always to use the reference number issued by the buyer. This information will be provided in eForms using the same cbc:ContractFolderID, therefore the ESPD should include the same identifier in order to link both models, and shall be globally unique.

This number in combination with a registered buyer ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.

Rule scope: BR-SC-10

cbc:IssueDate

Date

1

Date when the document was issued by the buyer.

Information Requirement: tbr070-002.

Rule: Format "YYYY-MM-DD".

cbc:IssueTime

Time

0..1

Time when the document was issued by the buyer.

Information Requirement: tbr070-002.

Rule: Format "hh:mm:ss".

cbc:VersionID

Identifier

0..1

The version identifying the content of this document.

Information Requirement: tbr070-014.

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

cbc:PreviousVersionID

Identifier

0..1

The version identifying the previous modification of the content of this document.

Information Requirement: tbr070-014.

Rule: None

cbc:ProcedureCode

Code

1

The type of the procurement administrative procedure according to the EU Directives.

Information Requirement: tbr070-007.

Rule: For the ESPD, this information will be linked to eForms. And ESPD should include the same procedure code as the one stated in eForms notices.

cac:ContractingParty

Associated class

1

The buyer 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).

Information Requirement: tbr070-01.

Rule: UBL-2.3 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.

In ESPD the contracting party information will come from eForms. Which also uses cac:ContractingParty to specify the information about buyer.

cac:ProcurementProject/cbc:Description

Text

1

Text describing this procurement project.

This element is required in the ESPD, however it should be identical to that provided in eForms. In general the corresponding eForm should feed the corresponding ESPD with the corresponding data.

cac:TenderingCriterion

Associated class

1..n

A tendering criterion describes a rule 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 candidates to the award decision.

Information Requirement: tbr70-003, tbr70-009.

Rule: (see examples further below in this document)

cac:TenderingCriterion/cac:ProcurementProjectLotReference/cbc:ID

Identifier

0..n

One or more of the procurement project lots Identifier to which this criterion can be related to.

Information Requirement: (see section Lot Management)

Rule: This element is mandatory for all Selection Criteria with cardinality 1..n because different Selection Criteria can be associated with different procurement lots. This element is not necessary for exclusion grounds because exclusion grounds are applied to all procurements.

cac:AdditionalDocumentReference

Associated class

0..n

A reference to an additional document associated with this document.

Information Requirement: tbr70-007.

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

2.5. Lot Management

The ESPD includes a change regarding how lots are managed. This is the outcome of the alignment with eForms.

In this new version the ESPD will have the following logic:

There will be 1 ESPD request stating the Exclusion Criteria and the Selection Criteria, but with differences respect version 2.1.1. The figure below shows the logic:

Overview of new lot management approach.

Figure 13. Overview of new lot management approach.

The ESPD request include exclusion grounds that are general for all the Lots in which the procedure is divided in. However, for Selection Criteria is different since in the procedure is possible to have Lots with different selection criteria. Therefore, in the ESPD request the different Selection Criteria will have to include the reference to the lots which applies. It will be done using the UBL 2.3 cac:ProcurementProjectLotReference that includes cbc:TenderingCriterion.

The following XML example shows how it is done:

<!--- Root elements eliminated for the sake of brevity -->

<cac:TenderingCriterion>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">499efc97-2ac1-4af2-9e84-323c2ca67747</cbc:ID>
<cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">gen-year-to</cbc:CriterionTypeCode>
<cbc:Name>General yearly turnover</cbc:Name>
<cbc:Description>Its general yearly turnover for the number of financial years required in the relevant notice, the in the ESPD, the relevant notice or the ESPD is as follows:</cbc:Description>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
</cac:ProcurementProjectLotReference>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
</cac:ProcurementProjectLotReference>
<cac:SubTenderingCriterion>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
<cbc:Name>[Name of the National Criterion]</cbc:Name>
<cbc:Description>[Description of the National Criterion ]</cbc:Description>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
<cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ed2a13ed-cf3d-478e-888d-cb9b89f55020</cbc:ID>
<cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
<cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b21ab072-e5b6-495c-ad6e-4ead6993ede5</cbc:ID>
<cbc:Description>Your Answer</cbc:Description>
<cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
</cac:SubTenderingCriterion>
<cac:Legislation>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">635a537c-57bf-4beb-8b69-d97d49382e1f</cbc:ID>
<cbc:Title>[Legislation title]</cbc:Title>
<cbc:Description>[Legislation description]</cbc:Description>
<cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
<cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
<cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
<cac:Language>
<cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
<cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">42824f1f-3574-4e53-80ca-501d22e85ef8</cbc:ID>
<cbc:Description>Minimum requirement</cbc:Description>
<cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
<!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
<cbc:ExpectedAmount currencyID="EUR">100000</cbc:ExpectedAmount>
</cac:TenderingCriterionProperty>

<!--- Rest of the elements of the criterion have been eliminated for the sake of brevity -->

In Economic Operator’s side it is different, as can be read in the image above there will be as many ESPD Response as Lots or Group of Lots the EO wishes to tender for. If the EO wants to participate in three Lots, the EO will need to fill in 3 ESPD Response. For more details on this, please see section ESPD Response.

Lots identifiers:

This version of the ESPD changes the form to identify the Lots and Group of Lots taking the eForms format. This changes is done towards the interoperability of both models.

Until version 2.1.1, the lots have been identified with the following structure "Lot1, Lot2, Lot3". With the new approach (eForms) the Lots identifiers will be as follows: (eForms) the Lots identifiers will be as follows:

Lot Identifiers according to eForms schema

Figure 14: Lot Identifiers according to eForms schema

2.6. EU and notice publications

REQUIREMENT tbr070-007

The Buyer must be able to provide information about official journals or gazettes where the procurement procedure is announced. For procurement projects above the threshold it is compulsory to refer to the Contract Notice published in TED.

ESPD conformant software applications will have to provide the means for the user to supply references to EU and notice publications about the procurement procedure, and notably about the Notices to which the ESPD is related.

Mock-up

The Figure below is a mock-up representation of how to collect the data expected to reference publications on official gazettes or journals. This mechanism can also be used for contracts below the threshold, obviously.

Publications mock-up

Figure 14. Publications, mock-up

XSD Schema

The ESPD EDM uses the UBL component cac:AdditionalDocumentReference to allow the inclusion of references to documents that they might consider relevant, and amongst them the reference to the Contract Notice on the TED (for above-the-threshold contracts) and to possible Notices on national journals and boards.

The class used for this, cac:AdditionalDocumentReference ''is a'' cac:DocumentReference class defined in the UBL-2.3 Common Aggregate Components library).

cac:DocumentReference

Figure 15. cac:DocumentReference, XSD diagram

The class cac:AdditionalDocumentReference aggregates a subclass cac:Attachment that is used by ESPD to place the URI, name of the document and descriptions.

Associated class cac:ExternalReference XSD diagram

Figure 16. Associated class cac:ExternalReference, XSD diagram

Expected elements

As you can see from the XSD Schema the cac:DocumentReference class has a rich data structure. However, to refer to publications such as the TED and national publications, the ESPD most expects at most the following data:

Table 6. Reference to additional documents, expected elements

Class name:

cac:AdditionalDocumentReference

Definition:

A reference to an additional document associated with this document.

Business rule(s):

Common (BR-COM-10)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:AdditionalDocumentReference

Context of Use:

In this case this reference points at a document published on the Supplement of the European Official Journal or on a national journal.

Components Type Card Description Requirements

cbc:ID

Identifier

1

The identifier for the referenced document, generally issued by the entity responsible for the document.

Information Requirement: tbr070-007.

Rule: 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). 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.

Rule scope: Common (BR-COM-10#1, BR-OTH-02)

cbc:UUID

Identifier

0..1

A universally unique identifier that can be used to reference this ESPD document instance.

Information Requirement: tbr92-013.

Rule: If the referenced document has a UUID to identify its particular instance refer to that UUID here.

cbc:DocumentTypeCode

Code

1

The type of document being referenced, expressed as a code.

Information Requirement: tbr070-007.

Rule: For the ESDP-EDM it is compulsory use of the Code List "docref-content-type". See example below on how to specify the OJS Contract Notice. If, for other documents, the type of document is not available in this list, provide the code "Other" and describe the content in the element DocumentType.

Rule scope: Common (BR-OTH-01, BR-OTH-01#3, BR-OTH-03)

cbc:DocumentType

Text

0..1

The type of document being referenced, expressed as text.

Information Requirement: tbr070-007.

Rule: Optionally use the attribute languageID to indicate the language of the text. Use the Code List "Language" for the value of the languageID attribute.

Rule scope: Common (BR-OTH-01, BR-OTH-01#4, BR-OTH-03)

cbc:IssueDate

Date

0..1

Date when the document was issued by the buyer.

Information Requirement: tbr92-013.

Rule: Format "YYYY-MM-DD". If available in the referenced document place here the data of publication by the buyer.

cbc:IssueTime

Time

0..1

Time when the document was issued by the buyer.

Information Requirement: tbr92-013.

Rule: If available in the referenced document place here the time of publication by the buyer.

Beware that the ESPD document do not embed the content of referenced documents but instead make a reference to its source. Thus the class 'DocumentReference' aggregates a 'cac:Attachment' class that allows for embedding the content or making reference to an external source of the content, which is the preferred way in ESPD (see XSD schema above):

Table 7. External Reference

Component name:

cac:ExternalReference

Definition:

A reference to the authentic source of content of this document.

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference

Components Type Card Description Requirements

cbc:URI

Identifier

0..1

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

Information Requirement: tbr070-007.

Rule: None.

cbc:FileName

Text

0..1

The title of the document.

Information Requirement: tbr070-007.

Rule: Originally this field is the placeholder for the name of the file (e.g. PLACE-ContractNotice-2017-12452.xml. However, as the UBL component does not have a placeholder for a name or title, the ESPD documents use it for a short descriptive title of the document being referenced.

cbc:Description

Text

0..n

Short description of the document.

Information Requirement: tbr070-007.

Rule: If 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. See example and comments below.

Rule scope: Common (BR-COM-10#2, BR-COM-10-S10, BR-COM-10-S20, BR-COM-10-S30)

XML Example

The XML snippet below illustrates how to use the cac:AdditionalDocumentReference in the ESPDRequest XML document to refer to a Contract Notice published in TED and on a national procurement board:

<!--- Root elements eliminated for the sake of brevity -->

<!-- Reference to the Contract Notice published on TED -->

<cac:AdditionalDocumentReference>

<cbc:ID schemeAgencyID="EU-COM-OP">2017/S 142-293520</cbc:ID>

<cbc:DocumentTypeCode listID="docrefcontent-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">TED_CN</cbc:DocumentTypeCode>

<cac:Attachment>

<cac:ExternalReference>

<!-- Beware XML URI fields may require encoded URLs -->

<cbc:URI schemeAgencyID="EU-COM-OP">http://ted.europa.eu/udl?uri%3DTED:NOTICE:293520-2017:TEXT:EN:HTML%026src%3D0</cbc:URI>

<cbc:FileName>Spain-Zamora: Repair and maintenance services</cbc:FileName>

<cbc:Description>Repair and maintenance services. Real estate services.</cbc:Description>

<cbc:Description>293520-2017</cbc:Description>

</cac:ExternalReference>

</cac:Attachment>

</cac:AdditionalDocumentReference>

<!-- Reference to the Contract Notice published on the Spanish Central Government eTendering Platform -->

<cac:AdditionalDocumentReference>

<!-- Contract Notice publishied on the Spanish Central eTendering Platform "PLACE" Plataforma de Contratación del Sector Público -->

<cbc:ID schemeAgencyID="PLACE">3.17/20830.0160</cbc:ID>

<!-- Contract Notice (CN) published on a National Government Official Journal -->

<cbc:DocumentTypeCode listID="docrefcontent-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NOJCN</cbc:DocumentTypeCode>

<cac:Attachment>

<cac:ExternalReference>

<!-- Beware XML URI fields may require encoded URLs -->

<cbc:URI schemeAgencyID="PLACE">https://contrataciondelestado.es/wps/portal/!ut/p/b1/pY_LDoIwEEW_hQ8wM5S2wJKH5REUVEDbjenCGI3Axvj9gmFrMXF2Nzkncy8okDahHD2XMAYnUL1-3a76eRt6_Ziy4me6LqNIpAS9gxMjKeKm4ekUyQhIA5AQo5-w2WdORNu8rfghSxCzVMRFY7NR57_5-OUC_K-_t9j_CMqMkBkwTfwAhg3bdOguIEfMPQfthedkvoNluB8f5dWmrhJiI3KoQYbhEkYnLA-hUw8hhJ_dqV7pwLLeHJySpA!!/</cbc:URI>

<cbc:FileName>Suministro y transporte de balasto</cbc:FileName>

<cbc:Description>Suministro y transporte de balasto para el tramo Zamora — Pedralba de la Línea de Alta Velocidad Olmedo — Lubián — Ourense. Subtramo 8.</cbc:Description>

</cac:ExternalReference>

</cac:Attachment>

</cac:AdditionalDocumentReference>

</QualificationApplicationRequest>
  1. For TED Notices you must use the Publications Office Official Journal Supplement number in its original format [][][][]/S [][][]-[][][][][][], e.g. 2017/S 142-293520. Notice that the schemeAgencyID is EU-COM-OP (OP standing for 'Publications Office').

  2. The jurisdiction scope of this document is typified in the Code List docref-content-type (see file /codelists/gc/DocRefContentType.gc in the distribution package). Beware that the name and content of this Code List has changed from the previous ESPD-EDM version 2.1.1.

  3. The ESPD documents never embed the actual content. Rather the content is always referenced from its original source (alignment to the Once-Only-Principle).

  4. The title of the CN has to be placed in the FileName field of the attachment. UBL does not provide a placeholder fo the title of the document.

  5. In the case of publication on the TED, at ESPD Request preparation time, the procurer does not have yet the OJS number, but can receive a temporary CN identifier (Received Notice Number). To save this number in the DocumentReference component create two cbc:Description elements and use the second one to place this Received Notice Number. If you do not have a description for the CN then use a 'dummy' content for the first description, e.g. <cbc:Description>_</cbc:/Description>.

  6. Notice how the schemeAgencyID is used in this example to specify that the national Agency that created this reference to the national publication (e.g. "PLACE" to refer to the ID of the national electronic board where the CN was published). The pattern of the ID is the one created by the Spanish buyer.

  7. In this case the code NOJCN means 'Contract Notice (CN) published on a National Government Official Journal' (see file /codelists/gc/DocRefContentType.gc in the distribution package).

2.7. Contracting Body

See formal requirements related to the contracting authorities in the e-Sens site: tbr070-001*

Mock-up

In principle, the ESPD-EDM asks for a few data about the procurer (i.e. the buyer, body or entity). The essential (compulsory) data for the contracting body are namely the one aimed to identify it, i.e. its official name and the country. The figure below represents a possible GUI interface for these two data. However the UBL specification provides many other data elements some of which may be interesting to include in the ESPD, notably data about the means to contact the contracting body (see below the list of elements possible in the ESPD).

Therefore software applications may take leverage of the richness of UBL-2.3 to collect also data about the buyer contact, end-point, and other data possible in the ESPD.

Procurer identification

Figure 17. Data about the procurer, mock-up

XSD Schema

The UBL-2.3 model provides a component that fits the purpose of holding data about the procurer: the common aggregate component cac:ContractingParty.

cac:ContractingParty XSD Schema

Figure 18. cac:ContractingParty XSD Schema, global vision

The cac:ContractingParty class is a specialisation of cac:Party. Hence, the main data about the procurer is in this associated cac:Party component:

cac:Party XSD Schema

Figure 19. cac:Party XSD Schema, global vision

The cac:Party class in turn associates a very rich class that holds the data about the Party address, including the country (see the UBL-2.3 specification for the complete list of fields):

cac:PostalAddress

Figure 20. cac:PostalAddress, XSD Schema

Notice also that the class associated to cac:Party to place the data about how to contact the contracting body:

cac:Contact

Figure 21. cac:Contact, XSD Schema

Expected elements

Table 8. Contracting body, expected elements

Class name:

cac:ContractingParty

Definition:

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

Business rule(s):

Common (BR-REQ-20#1)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:ContractingParty

Components Type Card Description Requirements

cbc:BuyerProfileURI

Identifier

0..1

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

Information Requirement: tbr070-006.

Rule: 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).

Table 9. Contracting body party, expected elements

Class name:

cac:Party

Definition:

Main data placeholder structure for, in this case, the contracting body.

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:ContractingParty/cac:Party

Components Type Card Description Requirements

cac:PartyIdentification/cbc:ID

Identifier

1

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

Information Requirement: tbr070-001.

Rule: When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system). When not possible a different identifier may be used. The code list EOIDType may be used to indicate the type of identifier used as a value of the schemeID attribute, e.g. schemeID="VAT").

Rule scope: Common (BR-REQ-20#4, BR-OTH-02)

cbc:WebsiteURI

Identifier

0..1

The website of the contracting body.

Information Requirement: tbr070-006.

Rule: For online services (e.g. Web Services, REST services, etc. use the component cac:EndPointID.

cbc:EndPointID

Identifier

0..1

Electronic address of the contracting body.

Information Requirement: tbr070-001.

Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the cac:Party/cbc:WebsiteURI). An end-point identifier MUST have a scheme identifier attribute (e.g.eSENSParty Identifier Scheme). Should be considered for all actors (buyer, service provider, economic operator) as an eDeliveryID.

cac:PartyName/cbc:Name

Text

1

The name of the contracting body as it is registered.

Information Requirement: tbr070-001.

Rule: Mandatory. Use the official name of the contracting body. The PartyName class has an associated basic element "cbc:Name". See XML example below.

Rule scope: Common (BR-REQ-20#2)

Table 10. Contracting body postal address, expected elements

Class name:

cac:PostalAddress

Definition:

Contractinng body address information.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:ContractingParty/cac:Party/cac:PostalAddress

Components Type Card Description Requirements

cbc:StreetName

Text

0..1

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

Information Requirement: tbr070-006.

Rule: None.

cbc:CityName

Text

0..1

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

Information Requirement: tbr070-006.

Rule: None.

cbc:PostalZone

Text

0..1

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

Information Requirement: tbr070-006.

Rule: None.

cac:Country/cbc:IdentificationCode

Code

1

A code that identifies the country.

Information Requirement: tbr070-006.

Rule: The country of the contracting body must always be specified. Compulsory use of the code list Country from EU Vocabularies).

Rule scope: Common (BR-REQ-20#3, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

cac:Country/cbc:Name

Text

0..1

The name of the country.

Information Requirement: tbr070-006.

Rule: None.

Table 11. Contact of the contracting body, expected elements

Class name:

cac:Contact

Definition:

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

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:ContractingParty/cac:Party/cac:Contact

Components Type Card Description Requirements

cbc:Name

Text

0..1

The name of the contact point.

Information Requirement: tbr070-006.

Rule: None.

cbc:Telephone

Text

0..1

A phone number for the contact point.

Information Requirement: tbr070-006.

Rule: None.

cbc:Telefax

Text

0..1

A fax number for the contact point.

Information Requirement: tbr070-006.

Rule: None.

cbc:ElectronicMail

Text

0..1

An e-mail address for the contact point.

Information Requirement: tbr070-006.

Rule: None.

2.8. Service Provider

REQUIREMENT tbr070-011

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

Service providers are officially recognised organisations that can supply ESPD Request documents (on behalf of the contracting body) with pre-filled information about the contracting body and additional information (e.g. liability statements, see tbr070-012)

The ESPD allows the provision of data about the service provider who produced the ESPD Request document (and equally for the ESPD Response document, on behalf of the economic operator).

Since the 2.1.1 does not include the cac:ServiceProvider as a 'document root component'. Instead, it uses the UBL-2.3 cac:ContractingParty/cac:Party associated class cac:ServiceProviderParty.

XSD Schema

cac:ServiceProvider XSD Schema

Figure 22. cac:ServiceProvider XSD Schema

Notice that:

  1. The cac:Party class aggregates the class cac:ServiceProviderParty; and

  2. The cac:ServiceProviderParty class 'is a' Party. Hence it aggregates a cac:Party class too, and uses it to place the main data about the service provider (like name, address, end-point, etc.).

cac:ServiceProvider

Figure 22. cac:ServiceProvider

service provider’s 'Party' elements

Figure 23. cac:ServiceProvider/cac:Party elements expected for the service provider

Expected elements

Table 12. Service provider, expected elements

Class name:

cac:Party

Definition:

Main information about the service provider.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:ContractingParty/cac:Party/cac:ServiceProviderParty/cac:Party

Components Type Card Description Requirements

cbc:WebsiteURI

Identifier

0..1

The website of the service provider.

Information Requirement: tbr070-011.

Rule: Use it for the official web site of the service provider. Reserve the EndPointID for online services (e.g. web, REST, ftp services, etc.)

cbc:EndpointID

Identifier

0..1

Electronic address of the service provider.

Information Requirement: tbr070-011.

Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the cac:Party/cbc:WebsiteURI). An end-point identifier MUST have a scheme identifier attribute (e.g.eSENSParty Identifier Scheme). Should be considered for all actors (buyer, service provider, economic operator) as an eDeliveryID.

cac:PartyIdentification/cbc:ID

Identifier

1

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

Information Requirement: tbr070-011.

Rule: An identifier for the service provider must always be provided. Compulsory 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). See XML example below. The code list EOIDType may be used to indicate the type of identifier used as a value of the schemeID attribute, e.g. schemeID="VAT").

Rule scope: Common (BR-REQ-20#5, BR-OTH-02")

cac:PartyName/cbc:Name

Text

1

The name of the service provider.

Information Requirement: tbr070-011.

Rule: The name of the service provider must always be specified. Supply the official registered name of the service provider.

Rule scope: Common (BR-REQ-20#6)

cac:PostalAddress/cac:Country/cbc:IdentificationCode

Code

1

The code that identifies the country of the service provider.

Information Requirement: tbr070-011.

Rule: The country of the service provider must always be specified. Compulsory use of the code list "Country" from EU Vocabulary, which includes 3-character codes and it is based on ISO.

Rule scope: BR-REQ-20#7, BR-OTH-01, BR-OTH-01#5, BR-OTH-03

XML example

The XML snippet below shows how an example of how to supply the expected data for the service provider.

...

_<!--- Root elements eliminated for the sake of brevity -->_

<cac:ContractingParty>

<cac:Party>

<cac:PartyIdentification><cbc:ID schemeAgencyID="VIES">B82387770</cbc:ID> </cac:PartyIdentification>

<cac:PartyName><cbc:Name>Ministerio de Defensa</cbc:Name></cac:PartyName>

<cac:PostalAddress><cac:Country><cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">ES</cbc:IdentificationCode></cac:Country></cac:PostalAddress>

<cac:ServiceProviderParty>

<cac:Party>

<cbc:WebsiteURI>http://www.minhafp.gob.es/es-ES/Areas%20Tematicas/Patrimonio%20del%20Estado/Contratacion%20del%20Sector%20Publico/Paginas/ROLECE.aspx</cbc:WebsiteURI>

<cbc:EndpointID>http://www.minhafp.gob.es/ESPD/endpoint</cbc:EndpointID>

<cac:PartyIdentification>

<cbc:ID schemeAgencyID="AEAT">B36699932</cbc:ID>

</cac:PartyIdentification>

<cac:PartyName>

<cbc:Name>Registro Oficial de Licitadores y Empresas Clasificadas (ROLECE)</cbc:Name></cac:PartyName>

<cac:PostalAddress>

<cac:Country><cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">ESP</cbc:IdentificationCode></cac:Country>

</cac:PostalAddress>

</cac:Party>

</cac:ServiceProviderParty>

</cac:Party>

</cac:ContractingParty>

...
  1. ContractingParty non-compulsory elements have been omitted for the sake of brevity.

  2. The service provider VAT number. The issuer Agency is the Spanish Tax Agency (AEAT). You can use the VIES platform to verify that the VAT number exists and is correct for Spain.

  3. The registered name of the service provider is mandatory.

  4. The country code of the service provider (ESP) is compulsory. You will need to use this code (ESP) to verify the VAT number in the VIES service.

3. Common aspects for criteria

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

The ESPD-EDM defined a flexible structure to express data about criteria. Based on this structure UBL-2.3 defined in turn the component cac:TenderingCriterion, which is used in ESPD-EDM to implement the XML objects for exclusion and selection criteria.

The UML diagram below provides a graphic view of the QualificationApplicationRequest document with the complete structure for the cac:TenderingCriterion component (cf. section on the ESPD Response, further on this guide, to understand how the QualificationApplicationResponse deals with Criteria).

Criterion - UML diagram

Figure 33. Criterion - UML diagram

3.1. General behavior

Notice that:

  1. One criterion may have descendent 'sub-criteria'. This is very useful to, for example, define national exclusion criteria that specialise the EU criteria defined in the Directive;

  2. One criterion may refer to one or several pieces of legislation (EU, national, other);

  3. One criterion must always contain at least one group of 'properties'. Properties may be informative captions; general requirements issued by the Member State or procedure-specific requirements specified by the buyer; and questions addressed to the economic operator;

  4. One group of properties must always specify at least one 'property';

  5. One group of properties may contain one or several 'sub-groups' of properties.

XSD Schema

This XSD Schema diagram shows a global view of the UBL 2.3 cac:TenderingCriterion component:

cac:TenderingCriterion - XSD Schema

Figure 34. cac:TenderingCriterion - XSD Schema, global view

Expected elements

Table 20. Criterion, expected elements

Class name:

cac:TenderingCriterion

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.

Business rule(s):

BR-LOT-20, BR-LOT-30, BR-LOT-30-S20, Common (BR-TC-01)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-Components-2.3.xsd.xsd

Path:

/QualificationApplicationRequest/cac:TenderingCriterion

Components Type Card Description Requirements

cbc:ID

Identifier

1

A language-independent token, e.g., a number, that allows to identify a criterion uniquely as well as allows to reference the criterion in other documents.

Information Requirement: tbr070-010.

Rule: Each Criterion is defined in e-Certis and must use the UUID supplied by e-Certis. See also the spreadsheets ESPD-criterion.

Rule scope: Common (BR-TC-02, BR-TC-12, BR-TC-13, BR-OTH-02)

cbc:CriterionTypeCode

Code

1

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

Information Requirement: tbr070-013

Rule: Compulsory use of codes coming from e-Certis, which are also used in the spreadsheets ESPD-criterion, e.g. crime-org, corruption, chain-manage)

Rule scope: 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)

cbc:Name

Text

1

A short and descriptive name for a criterion.

Information Requirement: tbr70-010

Rule: The name should match the one from e-Certis, which should be the same as in the in the spreadsheets ESPD-criterion], e.g. 'Convictions', 'Corruption', 'Fraud', 'Financial ratio', 'Subcontracting proportion’etc.).

Rule scope: Common (BR-TC-05)

cbc:Description

Text

1..n

An extended description of the criterion.

Information Requirement: tbr70-010

Rule: The description should match the one from e-Certis, which should be the same as in the in the spreadsheets ESPD-criterion], e.g. 'Has the economic operator itself or any person who is a member of its administrative, management or supervisory body or has powers of representation, decision or control therein been the subject of a conviction by final judgment for participation in a criminal organisation, by a conviction rendered at the most five years ago or in which an exclusion period set out directly in the conviction continues to be applicable? As defined in Article 2 of Council Framework Decision 2008/841/JHA of 24 October 2008 on the fight against organised crime (OJ L 300, 11.11.2008, p. 42).'.

Rule scope: Common (BR-TC-06, BR-TC-19)

Note: The UBL specification allows always multiple lines of text for the component cbc:Description. This feature can be used to split long descriptions into multiple lines, especially when the description contains enumerations (see the criterion "Misinterpretation" for an example).

cac:ProcurementProjectLotReference

Class

0..n

One or more of the procurement project lots to which this criterion can be related to.

Information Requirement: (see section Lot Management)

Rule: This element is mandatory for all Selection Criteria with cardinality 1..n because different Selection Criteria can be associated with different procurement lots. This element is not necessary for exclusion grounds because exclusion grounds are applied to all procurements.

cbc:SubTenderingCriterion

Class

0..n

One or more descendant criteria used namely to define a national exclusion criterion that specialises a more generic criterion like a EU exclusion criterion defined in the Directive.

Information Requirement: tbr70-013

Rule: None. Beware that a sub-criterion 'is a' criterion, therefore no need to list these elements at new. See XML examples in the section about exclusion criteria about how to define a sub-criterion.

cac:Legislation

Class

0..n

A reference to the legislation related to the Criterion.

Information Requirement: tbr070-013

Rule: None. See table below with the elements of this class.

cac:TenderingCriterionPropertyGroup

Class

1..n

The first level group of properties and sub-groups of properties in the structure of a criterion.

Information Requirement: tbr070-013

Rule: None. Beware that in previous versions of the ESPD-EDM this was termed "RequirementGroup".

XML Examples

See XML examples in the sections about exclusion and selection criteria.

3.2. Legislation

The XSD schema below shows, in blue, the elements of the component cac:Legislation used to point at the legislation related to the criterion.

cac:Legislation XSD Schema

Figure 35. cac:Legislation. XSD Schema

Expected elements

Table 21. Legislation, expected elements

Class name:

cac:Legislation

Definition:

A class to make reference to the legislation related to the criterion.

Business rule(s):

Common (BR-TC-08, 2. BR-OTH-01, BR-OTH-01#9, BR-OTH-03)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:TenderingCriterion/cac:Legislation

Components Type Card Description Requirements

cbc:ID

Identifier

0..1

An identifier to refer to the legislation.

Information Requirement:

Rule: Rule scope:

cbc:Title

Text

1..n

Title of the legislation.

Information Requirement: tbr070-013.

Rule: The complete title of the legislation provided as in the original legal text. At a later stage it might be provided by e-CERTIS (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).

Rule scope: Common (BR-TC-09)

cbc:Description

Text

0..n

Textual short description of the legislation.

Information Requirement: tbr070-013

Rule: The description of the legislation provided in the original legal text SHOULD be provided. At a later stage they might be provided by e-CERTIS. Can be provided in several languages, but if LanguageID not specified it defaults to en (English).

Rule scope: Common (BR-TC-10)

cbc:JurisdictionLevel

Text

0..n

Jurisdictional level of a particular legislation.

Information Requirement: tbr070-013

Rule: Although this is a text. Can be provided in several languages, but if LanguageID not specified it defaults to en (English).

cbc:Article

Text

0..n

Textual description of the article of the legislation.

Information Requirement: tbr070-013

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

Rule scope: Common (BR-TC-11)

cbc:URI

Identifier

0..1

URI that points to a legislation related to this criterion.

Information Requirement: tbr070-013

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

XML Examples

See examples in sections about exclusion and selection criteria.

XML Example

Snippet of XML to illustrate how to use the cac:Legislation component inside a criterion:

<cac:TenderingCriterion>

_<!-- ... elements omitted for brevity -->_

<cac:Legislation>

<cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4ea7a10a-643e-4022-b67e-e06573b28ff5</cbc:ID>

<cbc:Title>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</cbc:Title>

<cbc:Description>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</cbc:Description>

<cbc:JurisdictionLevel languageID="en">EU Directive</cbc:JurisdictionLevel>

<cbc:Article>57(1)</cbc:Article>

<cbc:URI>http://eur-lex.europa.eu/legal-content/ES/TXT/?uri=celex%3A32014L0024</cbc:URI>

</cac:Legislation>

_<!-- ... elements omitted for brevity -->_

</cac:TenderingCriterion>
  1. Use the UUID provided by GROW.

  2. The official long title of the legislation is expected in the Title.

  3. The short name that is commonly used to refer to the legislation is expected in the Description.

3.3. Groups of properties

This XSD diagram shows the sub-components of a group of criteria:

cac:TenderingCriterionPropertyGroup - XSD Schema global view

Figure 36. cac:TenderingCriterionPropertyGroup - XSD Schema, global view

One group of properties may include one or more 'sub-groups' of properties (class cac:SubsidiaryTenderingCriterionGroup).

Notice that: One sub-group of properties 'is a' group of criteria:

cac:SubsidiaryTenderingCriterionGroup- XSD Schema

Figure 37. cac:SubsidiaryTenderingCriterionGroup- XSD Schema

Expected elements

Table 22. Groups of properties, expected elements

Class name:

cac:TenderingCriterionPropertyGroup

Definition:

The first level group of properties and sub-groups of properties in the structure of a criterion.

Business rule(s):

Common (BR-TC-07, BR-TC-16)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup

Components Type Card Description Requirements

cbc:ID

Identifier

1

Identifies a group of requirements uniquely.

Information Requirement: tbr070-013.

Rule: Compulsory use of the UUIDs supplied by e-Certis.

See also the spreadsheet ESPD-criterion.

Rule scope: Common (BR-TC-12, BR-OTH-02, BR-OTH-02#01)

cbc:PropertyGroupTypeCode

Code

1

Code addressed to control the behavior of the group of criteria.

Information Requirement: tbr070-013.

Rule: Compulsory use of the Code List PropertyGroupType. See sections below about the 'criteria data structures' and the XML examples on exclusion and selection criteria to understand the use of this code. 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. See also the sub-section The ONTRUE/ONFALSE codes for GROUP and SUBGROUP control

Rule scope: Common (BR-TC-14, BR-TC-15, BR-OTH-01, BR-OTH-01#11, BR-OTH-03)

cac:TenderingCriterionProperty

Class

1..n

Caption (i.e. a 'label'), specific MS or buyer requirement (e.g. 'Number of references expected: 5' or a question addressed to the economic operator (e.g. 'Your average yearly turnover for the past three years?'.

Information Requirement: tbr070-013.

Rule: See the rules for the class in the tables below to see the rules related to criterion properties. See also the XML examples provided in sections about exclusion and selection criteria.

cac:SubsidiaryTenderingCriterionPropertyGroup

Class

0..n

A second, third or n-level group inside a first level group of properties.

Information Requirement: tbr070-013.

Rule: subsidiary property groups 'are' property groups (i.e. it is the same component but qualified as 'subsidary'). Therefore all the rules applicable to property groups are also applicable to sub-groups: Compulsory use of the Code List PropertyGroupType. See sections below about the 'criteria data structures' and the XML examples on exclusion and selection criteria to understand the use of this code. 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.

XML Examples

  1. See examples in sections about exclusion and selection criteria. Study:

    • How GROUPS (cac:TenderingCriterionPropertyGroup) and SUB-GROUPs (cac:cac:SubsidiaryTenderingCriterionPropertyGroup) are organised, and

    • How the codes ON*, ONTRUE and ONFALSE are used.

  2. You will notice in the examples that the elements cbc:Name and cbc:Description of groups and subgroups of properties are never used. As a common practice the ESPD documents use instead a first cac:TenderingCriterionProperty of type CAPTION (i.e. an informative property that act as a 'label').

3.4. Properties

REQUIREMENT

The buyer needs to be able to specify the type of the value it expects from the economic operator in a response; e.g. DESCRIPTION, INDICATOR, QUANTITY, URL, etc.). The economic operator must provide a value for the response that is consistent with the type specified by the buyer.

This other XSD diagram shows the elements of the properties of a criterion:

cac:TenderingCriterionProperty - XSD Schema

Figure 38. cac:TenderingCriterionProperty - XSD Schema

Notice that: One sub-criterion 'is a' criterion:

cac:SubTenderingCriterion- XSD Schema

Figure 39. cac:SubTenderingCriterion- XSD Schema

Expected elements

The following table lists the elements of a criterion property. Beware that the majority of the elements are the possible types of responses that the buyer can specify. The economic operator, in the ESPDResponse, must provide values that are consistent with the type specified by the buyer.

Table 23. Properties, expected elements

Class name:

cac:TenderingCriterionProperty

Definition:

Caption (i.e. a 'label'), specific MS or buyer requirement (e.g. 'Number of references expected: 5' or a question addressed to the economic operator (e.g. 'Your average yearly turnover for the past three years?'.

Information Requirement: tbr070-013

Business rule(s):

BR-SC-20

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:TenderingCriterion/cac:TenderingCriterionProperty

Components Type Card Description Requirements

cbc:ID

Identifier

1

Identifies one specific property.

Information Requirement: tbr070-013.

Rule: Property 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. See the section about the ESPD Response for examples.

Rule scope: Common (BR-TC-18, BR-OTH-02)

cbc:Description

Text

1

The text of the caption, requirement or question.

Information Requirement: tbr070-013.

Rule: None.

Rule scope: Common (BR-TC-19)

cbc:TypeCode

Code

1

The type of property. Used to verify that structure of the property is correct.

Information Requirement: tbr070-013.

Rule: Compulsory use of the 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 ResponseDataType

Rule scope: BR-TC-20, BR-OTH-01, BR-OTH-01#14, BR-OTH-03

cbc:ValueDataTypeCode

Code

1

The type of answer expected by the buyer in the case of a property of type QUESTION.

Information Requirement: tbr070-013.

Rule: Compulsory use of the Code List "ResponseDataType". Verify that the value is different to NONE for properties of type QUESTION.

Rule scope: Common (BR-TC-21, BR-OTH-01, BR-OTH-03, BR-OTH-01#12, BR-OTH-03)

cbc:ValueUnitCode

Code

0..1

The unit of measure of the numeric value as a quantity or measure in the expected response from the economic operator.

Information Requirement: tbr070-013.

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

Rule scope: BR-OTH-01

cbc:ValueCurrencyCode

Code

0..1

The currency of the numeric value as an amount in the expected response from the economic operator.

Information Requirement: tbr070-013.

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

Rule scope: BR-OTH-01

cbc:ExpectedAmount

Amount

0..1

The amount in the expected response from the economic operator.

Information Requirement: tbr070-013.

cbc:ExpectedID

Identifier

0..1

The expected identifier that the economic operator has to provide in the criterion response.

Information Requirement: tbr070-013.

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

Rule scope: (BR-LOT-40)

cbc:ExpectedCode

Code

0..1

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

Information Requirement: tbr070-013.

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

Rule scope:(BR-OTH-01)

cbc:ExpectedValueNumeric

Numeric

0..1

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

Information Requirement: tbr070-013.

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

cbc:ExpectedDescription

Text

0..1

The description of the expected evidence that the economic operator has to provide in the Criterion response.

Information Requirement: tbr070-013.

Rule:

cbc:MaximumValueNumeric

Numeric

0..1

The maximum value the response must have.

Information Requirement: tbr070-013.

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

cbc:MinimumValueNumeric

Numeric

0..1

The minimum value the response must have.

Information Requirement: tbr070-013.

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

cbc:CertificationLevelDescription

Text

0..1

The description of the level of the expected certification.

Information Requirement: tbr070-013.

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

cac:ApplicablePeriod

Class

0..1

The period to which this criterion property shall apply.

Information Requirement: tbr070-013.

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

cac:TemplateEvidence

Class

0..n

A pointer to one or more evidences that support the veracity of this criterion.

Information Requirement: tbr070-013.

Rule: None.

XML Examples

  1. See examples in sections about exclusion and selection criteria.

  2. You will notice in the examples that the element cbc:Name is never used. Instead the cac:Description is sufficient for all the ESPD purposes.

3.5. Mock-ups

Chapters 4 Exclusion Criteria and 5. Selection Criteria describe in detail the different types of exclusion and selection criteria defined and used in the ESPD-EDM. By type of criterion we refer to criteria that share common characteristics, namely how they are structured. Each type of criterion is presented from three perspectives:

  1. Layout and functional: Mock-ups are provided to explain which data are expected and, to some extent, how software applications should behave (what to show/hide, validate or process depending on variables like 'what the user answers' or 'which is the role of the user'). Mock-ups are provided for both the buyer and economic operator perspectives;

  2. Structural: a spread-sheet books is provided with this document aimed to explain how each type of criterion is organised (the book contains different sheets (tabs). Each 'tab' shows the structure of one type of criterion (e.g. 'EG-Convictions', 'EG-Contributions', …​, 'SC-Suitability', 'SC_References', etc.; where 'EG' stands for 'Exclusion Grounds', and 'SC' stands for 'Selection Criteria').

    • ESPD-Criterion where the structures of the ESPD criteria are defined

  3. XML Implementation: Each mock-up (or pair of Buyer + EO mock-ups) represent the structure represented in the data structure spread-sheet and in the supplied XML example. Whilst the mock-up and XML example are quite self-explanatory, to understand the value of the data structure spread-sheet needs to be explained; which is the mission of this very next sub-section below.

3.6. Data Structures

The ESPD-EDM 'criterion' entity is a very flexible and business-agnostic structure. This flexibility provides a convenient way to represent any type of criteria. The counterpart is that the semantics of the criteria needs to be delimited based on codes, identifiers and design rules.

Hence this document proposes a way of representing the criteria following a regular method and providing concrete codes to specify types of criterion properties, and identifiers to distinguish the different criteria and reusable groups of properties (when studying these data groups you will observe that sub-groups of properties are reused in different criteria have identical identifiers and structures).

The following figures below illustrates the data structure sheets for one simple exclusion criterion (EG-Contributions). Compare them with the UBL-2.3 cac:TenderingCriterion XSD element.

The columns of the tables are to be interpreted as follows:

  • Column 1: an ordinal number to sort sequentially the criteria

  • Column 2: contains always the opening and closing tag for Criterion

  • Columns 3 to 17: reserved for the opening and closing tags defining the data structure (see the tag codes in code list CriterionElementType).

  • Column 18: Name, a short descriptive text to identify the criterion withouth having to read the description

  • Column 19: Description, the text describing the criterion as kept in e-Certis

  • Column 20: Value a possible value or description of the value used by the transformation artefacts to produce example XML instances

  • Column 21: Cardinality, indicates whether the element is mandatory or optional and its multiplicity

  • Column 22: PropertyDataType, the type of data expected according to the types defined in the code list ResponseDataType

  • Column 23: ElementUUID, The Universal Unique Identifier assigned to identify unambiguously a criterion, group or subgroup. These UUID are kept in e-Certis, except for those that have to be generated dynamically (e.g. UUIDs for Questions, Captions and Requirements). See also the special note "Criteria Taxonomy/Data Structures and the use of UUIDS" below

  • Column 24: Element Code; in the case of Criterion it contains the code that categorises the criterion in the taxonomy of exclusion and selection criteria (it maps to the taxonomy drawn in the online documentation and in the spread-sheet files "ESPD-criterion" in folder /codelists). For the rest of elements there are three types of codes

    • ON*, meaning "process always" (e.g. show always or read and extract data always")

    • ONTRUE, meaning "process this group only if the previous parent question (always an INDICATOR) has been answered affirmatively"

    • ONFALSE, meaning "process this group only if the previous parent question (always an INDICATOR) has been answered negatively"

Contributions' criterion data structure

Figure 41. 'Contributions' criterion data structure

We could say that the 'data structures' represented in the spread-sheets define a kind of 'meta-language' (or 'controlled vocabulary') that helps 'map' the structure of an ESPD-EDM criterion and the UBL-2.3 criterion data structure. The table below 'maps' both vocabularies. Please compare any of the data structures provided in this document with both the UBL-2.3 XSD Schemas and the XML examples provided herein.

Table 24. Mapping between the ESPD-EDM criterion data structure spread-sheets and the UBL-2.3 vocabulary

ESDP-EDM Spread-sheet vocabulary

UBL-2.3 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

The ESPD-EDM data structures vocabulary is defined in the Code List "CriterionElementType". Her you have the definitions provided therein:

  • CRITERION: A criterion (in the case of the the ESPD an Exclusion or Selection criterion); maps to a UBL-2.3 cac:TenderingCriterion class

  • SUBCRITERION: Used to define national sub-criteria; maps to a UBL-2.3 cac:SubTenderingCriterion class

  • REQUIREMENT_GROUP: Group of requirements or remarks issued by a MS or a CA; maps to a UBL-2.3 cac:TenderingCriterionPropertyGroup

  • REQUIREMENT_SUBGROUP: A subgroup of requirements or remarks inside a group or subgroup of requirements; maps to a UBL-2.3 cac:SubsidiaryTenderingCriterionPropertyGroup

  • REQUIREMENT: Requirement, remark, rule, restriction or additional information to which the EO needs to conform or comply with; maps to a cac:TenderingCriterionProperty class (one data type must be specified for the value supplied by the buyer; see see codes in the Code List "ResponseDataType")

  • QUESTION_GROUP: Group of questions, each question requiring a datum as an answer from the EO; maps to a cac:TenderingCriterionPropertyGroup class

  • QUESTION_SUBGROUP: A subgroup of questions inside a group or a subgroup of questions; maps to a cac:SubsidiaryTenderingCriterionPropertyGroup

  • QUESTION: A question that requires an answer (a specific datum) from the EO; maps to a cac:TenderingCriterionProperty class (one, and only one, data type is expected; see codes in the Code List "ResponseDataType" )

  • CAPTION: A text label (no requirement nor answer is expected); maps to a cac:TenderingCriterionProperty class (the expected response data type is NONE)

  • ADDITIONAL_DESCRIPTION_LINE: Additional line in a description (for descriptions that can be split in several lines); maps to a cbc:Description element (namely in cac:TenderingCriterion)

  • LEGISLATION: An instance of a Legislation class; maps to a cac:Legislation class

The main differences between REQUIREMENT, CAPTION and QUESTION are:

  1. A REQUIREMENT is a condition, restriction or rule established by the Member State (in e-Certis, for all procurement procedures) or the buyer (for the specific procurement procedure). REQUIREMENT(s) are not intended to be responded by the economic operator; but the economic operator must conform to (comply with) it. Examples of REQUIREMENT(s): 'Provide at least three references to similar works', 'The expected lowest general yearly turnover is 1,000,000 €', etc. (see mock-ups);

  2. A CAPTION is a label normally used to introduce a group of REQUIREMENT(s) or QUESTION(s); e.g. 'Lots the EO tenders to' (which is followed by a list of Lots identifiers provided by the EO);

  3. A QUESTION is a direct request for a specific datum by the MS or the Buyer addressed to the EO. The EO has to respond this QUESTION with a value of the expected type of data.

If you examine any of the XML examples provided in this document you will observe that:

  • SUBCRITERION is currently used to specify national criteria.;

  • The reason for having 'groups' and 'sub-groups' of properties is because UBL-2.3 defined the 'TenderingCriterionPropertyGroup' and 'SubsidiaryTenderingCriterionPropertyGroup';

  • The following rules apply in a regular way:

    • When the member state (MS) or the buyer needs to specify REQUIREMENT(s), the outer group of the data structure is always a REQUIREMENT_GROUP (e.g. 'EG-Contributions', 'SC-Suitability', or practically all selection criteria). Otherwise the outer group is always a QUESTION_GROUP (e.g. 'EG-Convictions', 'EG-Environ-Social-Labour_Law', 'EG-Business', etc.);

    • A REQUIREMENT_GROUP always contain a first element CAPTION or REQUIREMENT. This is because in the UBL-2.3 XSD schema the first mandatory element is always a cac:TenderingCriterionProperty element;

    • A REQUIREMENT_GROUP or REQUIREMENT-SUBGROUP may contain either REQUIREMENT_SUBGROUPS and/or QUESTION_SUBGROUPS;

    • The only possibility in the UBL-2.3 model to distinguish whether a group or a subgroup of criterion properties contains REQUIREMENT(s) or QUESTION(s) is to look into the value of the cac:TenderingCriterionProperty/cbc:TypeCode. The list of possible codes are the ones of the above mentioned Code List "CriterionElementType".

3.7. XML examples and tools

The fact of presenting the data structures as a spread-sheet book had an additional reason: to use the spread-sheet as an elementary prototype tool to generate the XML instances of the criteria for the ESPD Request and ESDP Response documents.

Thus the folder xml-examples/__xslt__/ODS-Data-Structures-to-ESPD-XML contains four XSL style-sheets that facilitate the generation of the complete set of criteria required in an ESDP Request or in an ESDP Response XML file.

For this, you can use the following method: Rename the .ods files as .ods.zip and extract the file 'content.xml'; use an XML editor to load the 'content.xml' file and the XSL-T file. Associate (or reference) the XSLT file to the XML. Launch the transformation from the XML Editor. Save the output file.

Beware that this solution is a simple prototype aimed at generating the complete list of criteria that may occur in an ESDP Request and the responses (but not the the criteria properties) in an ESPD Response.

The following features are implemented in the first set of transformation XSL-T style-sheet (ESPDRequest-Annotated.xslt):

  • All the root elements are created and commented;

  • An empty buyer is created in the ESPD Request and ESPD Response (no data about any buyeris supplied); just the necessary for the XML to be validated against the XSD schema;

  • An empty economic operator is created in the ESPD Response (no data about any EO is supplied); just the necessary for the XML to be validated against the XSD schema;

  • All the exclusion and selection criteria in the spread-sheets are created;

  • Per each criterion a complete Legislation object is instantiated with 'dummy' values.

The following features are NOT implemented in the first set of transformation XSL-T style-sheet (ESPDRequest-Annotated.xslt):

  • The publications and document references requested in the business requirements are not generated; but the XML examples provided in the distribution do contain examples of TED and national publications (for the ESPDRequest.xml and ESPDResponse.xml, in the xml-examples folder.

  • The response value and cardinality are shown for informative purposes. No functionality is currently implemented based on them, but could be used in future improved versions of the prototype;

The following features are implemented in the second set of transformation XSL-T style-sheet (From-REQUEST-to-RESPONSE.xslt):

  • All the root elements are created and commented;

  • An empty buyer is created (no data about any buyeris supplied); just the necessary for the XML to be validated against the XSD schema;

  • An empty economic operator is created (no data about any EO is supplied); just the necessary for the XML to be validated against the XSD schema;

  • A cac:TenderingCriterionResponse per cac:TenderingCriterionProperty in the ESPD Request document is created with 'dummy' values. The cac:ResponseValue elements are of the data type expected as specified in the ESPD Request cac:TenderingCriterionProperty/cac:ValueDataTypeCode element.

The following feature is NOT implemented in the first set of transformation XSL-T style-sheet (ESPDRequest-Annotated.xslt):

  • The Criteria from the ESPD Request are not copied in the ESPD Response document. But the XML examples in the xml-examples folder.

3.8. GUI control elements

The ESPD-EDM specification includes two sets of data elements (codes) that help software applications control how to show the Graphic User Interfaces (GUI) dealing with ESPD Documents. These elements can be seen as ''processing instructions''.

ONTRUE/ONFALSE codes for GROUP and SUBGROUP control

Three codes concerning the GROUPS or SUBGROUPS of REQUIREMENT(s) and QUESTION(s) are defined in the code list PropertyGroupType:

  1. ON*, meaning that the GROUP or SUBGROUP has to be processed always;

  2. ONTRUE, meaning that the GROUP or SUBGROUP has to be processed, and announcing that a GROUP or SUBGROUP is coming next which must not be processed if the value of the closer QUESTION of type INDICATOR is true;

  3. ONFALSE, meaning that the GROUP or SUBGROUP must be processed if the value of the closer QUESTION of type INDICATOR is false;

These codes are used for a software application modules to know whether it has to process a concrete GROUP or SUBGROUP. If the objective of the module is, for example, to build dynamically the Graphic User Interface (GUI) - based on the ESPD-Request or an ESPD-Response XML instance-, then a GROUP or SUBGROUP marked as ONTRUE implies that the GROUP or SUBGROUP content is to be shown, whilst the one marked as ONFALSE needs to be hidden. GROUPS and SUBGROUPS marked as ON* imply that has to be always shown. You can see this mechanism as a way of implementing ''choices'' or ''switch/cases'' inside a Criterion Data Structure.

The figure below illustrates how the ONTRUE and ONFALSE SUBGROUPS of a Criterion of type "Contributions (exclusion grounds)" relate to each of its ''closer QUESTION'' of type INDICATOR (see boxes and lines coloured in blue):

ONTRUE/ONFALSE choice control

Figure 42. GROUP and SUBGROUP control via the ONTRUE/ONFALSE codes

The screen-captures below illustrate how the European Commission’s ESPD Service processed the GUI for the Exclusion Criterion ''Contributions'' based on this mechanism. Note that these are examples on how the GUI is processed and its behaviour taking into account the PropertyGroupType, the actual content can be outdated:

Case 1: When the first QUESTION ''Your Answer?'' is set to false:

Figure 43. Case 1: When the first QUESTION ''Your Answer?'' is set to false:

Case 2: When the first QUESTION ''Your Answer?'' is set to true

Figure 44. Case 2: When the first QUESTION ''Your Answer?'' is set to true:

Case 3: When the first QUESTION ''Your Answer?'' and the option "Has this breach of obligations been established …​" are both set to true:

Figure 45. Case 3: When the first QUESTION ''Your Answer?'' and the option "Has this breach of obligations been established …​" are both set to true:

Case 4: When all the QUESTION(s) that are INDICATORS are set to true

Figure 46. Case 4: When all the QUESTION(s) that are INDICATORS are set to true

Radio-Button and Check-box controls

In version 2.1.0 a new code list named BooleanGUIControlType was added to help software application process REQUIREMENT(s) issued by the buyer when drafting ESPD documents. For the time being this need is only present in one Criterion of ESPD: 'Other economic or financial requirements' (finan-requ). The figure below shows the data structure for that Criterion:

Use of the code list BooleanGUIControlType

Figure 47. Use of the code list BooleanGUIControlType

Notice that:

  1. The property data type used is BOOLEAN_CODE. This is a new type that has been added to the code list ResponseDataType to make obvious that the code is specifically used to identify a three state indicator (true, false or not checked). In the case of this particular Criterion it is used specify the type of value that will be provided by the buyer for this specific REQUIREMENT (see the XML example below);

  2. The possible values for this property data type are defined in the code list BooleanGUIControlType, which are: RADIO_BUTTON_TRUE, RADIO_BUTTON_FALSE, RADIO_BUTTON_UNSELECTED, CHECK_BOX_TRUE, CHECK_BOX_FALSE and CHECK_BOX_UNCHECKED;

  3. When the value of the CODE_BOOLEAN is RADIO_BUTTON_TRUE (true) the SUBGROUPs of REQUIREMENT(s) (UUID 26ece6a2-b360-46c1-890d-8338913b8719 ) and QUESTION(s) (UUID 9b3a04ff-e36d-4d4f-b47c-82ad402b9b02) are processed (e.g. shown by the GUI). Otherwise the software application processes the alternative SUBGROUPs of REQUIREMENT(s) (UUID cc96aa19-a0be-4409-af58-ff3f3812741b) and QUESTION(s) (UUID 5fe93344-ed91-4f97-bcab-b6720a131798).

The following fragment of XML code shows how this is expressed:

_Use of semantised boolean codes for REQUIREMENT processing control_

_<!-- lines with '...' refer to elements that have been removed for brevity. See complete sample in folder xml-examples of this distribution -->_

<cac:TenderingCriterionPropertyGroup>

<cac:TenderingCriterionProperty>

_<!--...-->_

<Description>Lots the requirement applies to</Description>

_<!--...-->_

</cac:TenderingCriterionProperty>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

_<!--...-->_

<cac:TenderingCriterionProperty>

_<!--...-->_

<Description>Lot ID</Description>

_<!--...-->_

</cac:TenderingCriterionProperty>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

<ID schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">26ece6a2-b360-46c1-890d-8338913b8719</ID>

<PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</PropertyGroupTypeCode>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">9c62f2c7-0c51-451d-8730-427f92ed618c</ID>

<Description>Select the type of requirement</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CODE_BOOLEAN</ValueDataTypeCode>

<ExpectedCode listID="BooleanGUIControlType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">RADIO_BUTTON_TRUE</ExpectedCode>

</cac:TenderingCriterionProperty>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

_<!--...-->_

<PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</PropertyGroupTypeCode>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">13728a54-21e3-4c84-8b11-48666c3d260f</ID>

<Description>Specify the total invoiced amount, taxes included.</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</ValueDataTypeCode>

<ExpectedDescription>__FinReqsDescription</ExpectedDescription>

</cac:TenderingCriterionProperty>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">48c7b3bf-8d1c-4497-a915-78d53ba68089</ID>

<Description>Minimum amount</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</ValueDataTypeCode>

<MinimumAmount currencyID="EUR">100006</MinimumAmount>

</cac:TenderingCriterionProperty>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">8b4ae4f0-2849-49ea-a64b-7bb20c60bde4</ID>

<Description>Start date; End date</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</ValueDataTypeCode>

<cac:ApplicablePeriod>

<StartDate>2000-10-10</StartDate>

<EndDate>2000-10-10</EndDate>

</cac:ApplicablePeriod>

</cac:TenderingCriterionProperty>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

<ID schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9b3a04ff-e36d-4d4f-b47c-82ad402b9b02</ID>

<PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1"></PropertyGroupTypeCode>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">1d89c188-58d2-461e-a4f6-a17f689d87f4</ID>

<Description>Amount</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</ValueDataTypeCode>

</cac:TenderingCriterionProperty>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

<ID schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cc96aa19-a0be-4409-af58-ff3f3812741b</ID>

<PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</PropertyGroupTypeCode>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">57d4160f-20b4-4b43-967b-76b038a2fa6b</ID>

<Description>Minimum rating</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</ValueDataTypeCode>

</cac:TenderingCriterionProperty>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">f07b5174-93ae-46dd-aa26-7f451d97f6a8</ID>

<Description>Rating scheme</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</ValueDataTypeCode>

<ExpectedDescription></ExpectedDescription>

</cac:TenderingCriterionProperty>

<cac:SubsidiaryTenderingCriterionPropertyGroup>

<ID schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5fe93344-ed91-4f97-bcab-b6720a131798</ID>

<PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1"></PropertyGroupTypeCode>

<cac:TenderingCriterionProperty>

<ID schemeID="criterion" schemeAgencyID="EU-COM-OP" schemeVersionID="3.0.1">3bd1913b-c461-41eb-87c4-84e003785a56</ID>

<Description>Rating</Description>

<TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</TypeCode>

<ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</ValueDataTypeCode>

</cac:TenderingCriterionProperty>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

</cac:SubsidiaryTenderingCriterionPropertyGroup>

<!--...-->

</cac:TenderingCriterionPropertyGroup>

</cac:TenderingCriterion>
  1. This property (cac:TenderingCriterionProperty) can be used by the software application to help the buyer select the type of REQUIREMENT it wants to be shown to the economic operator, either an Amount limited by a threshold and a period of time or rating constrained by a threshold and a rating scheme. The expected value will be a code expressing a three-state indicator (a boolean semantised as CODE_BOOLEAN).

  2. In this example, the buyer has specified the value RADIO_BUTTON_TRUE.

  3. As the value of the element cbc:ExpectedCode, inside the REQUIREMENT (cac:TenderingCriterionProperty) ''Select the type of requirement'', is RADIO_BUTTON_TRUE the economic operator will see the first SUBGROUP of REQUIREMENT(s) (UUID 26ece6a2-b360-46c1-890d-8338913b8719) and will have to respond the QUESTION with the text "Amount".

  4. The buyer is specifying that an amount above 100006 Euros is expected.

  5. This is the QUESTION that the economic operator needs to respond (the "Amount" corresponding to the economic of financial requirement (in this example: "Specify the total invoiced amount, taxes included" (cac:TenderingCriterionProperty UUID 13728a54-21e3-4c84-8b11-48666c3d260f).

  6. The economic operator (EO) will have to respond using an element of type cbc:Amount, see the next fragment of XML below for the response of the EO. The validation mechanism checks that the type of data specified by the buyer in the ESPD-Request (AMOUNT) and the type of data provided in the ESPD-Response (cbc:ReponseAmount) are coherent.

  7. This SUBGROUP is never processed (e.g. shown to the economic operator) as it contains the SUBGROUP of REQUIREMENT(s) and QUESTION in case the buyer had specified RADIO_BUTTON_FALSE as an answer to the field "Select the type of requirement".

  8. The QUESTION that the economic operator would have had to respond in case the buyer had selected the second SUBGROUP of REQUIREMENT(s), which is not the case in this example.

Response of the economic operator to the REQUIREMENT "Amount"

_<!-- ... -->_

<cac:TenderingCriterionResponse>

<ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">76085d25-05ad-4cb3-b1e0-675558e3f43e</ID>

<ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1d89c188-58d2-461e-a4f6-a17f689d87f4</ValidatedCriterionPropertyID>

<cac:ResponseValue>

<ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">42245674-d305-40bf-8b58-87ba51313345</ID>

<ResponseAmount currencyID="EUR">10025</ResponseAmount>

</cac:ResponseValue>

</cac:TenderingCriterionResponse>
  1. This UUID is identical to the UUID of the cac:TenderingCriterionProperty selected by the buyer for the QUESTION "Amount:" (see XML above).

  2. The element cbc:ResponseAmount is of type "AMOUNT", as expected by the validation mechanisms.

  3. The value of the amount meets the REQUIREMENT, as the amount is required to be above 10006 Euros (see XML above, notice the currencyID type value, too).

  4. Beware that, contrary to other numeric types of data, AMOUNT is not semantised and mapped to cbc:ResponseMinimumAmount nor cbc:ResponseMaximumAmount`, as in the current ESPD-EDM specification all monetary thresholds are always "minimum" (and similarly for QUANTITY or QUANTITY_INTEGER, e.g. see the REQUIREMENT ''Minimum number of years'' in criterion #49 (tab SC-Abilities_5 (Staff) in the ESPD-criterion spread-sheet).

Use of CAPTION

As explained in section 3.6 Data Structures (see from ''Table 25. Mapping between the ESPD-EDM criterion data structure spread-sheets and the UBL-2.3 vocabulary ESDP-EDM Spread-sheet vocabulary'' on, the term CAPTION is used in the Criteria data structures to inform software applications about the presence of a text label. Applications could use it to label boxes containing groups of REQUIREMENT(s) or of QUESTION(s). But in general software applications should know how to present the contents of the XML instances without having to recur to such resources (see the ''Note for the future: eBusiness Documents should not convey Process Instructions'' just below).

A CAPTION is mapped to the UBL element cbc:TenderingCriterionProperty. This is the reason why the ESPD-EDM had to introduce an element that, in the end, is quite ''dummy'': the UBL-2.3 specification requires that the first element of a GROUP or SUBGROUP is has always to be a criterion property (an element cac:TenderingCriterionProperty).

For software applications, the implication can be reduced to a very simple rule: when encountering a cac:TenderingCriterionProperty which cbc:TypeCode* value equals CAPTION just skip it!*

Business data and GUI decoupling

The business domain semantics should be decoupled from its management processes. Thus eBusiness Documents should not contain processing instructions but just data about the business domain. One counter-example for this statement are those cases when the XML instances contain processing instructions for a software GUI solution to manage how the layout must behave or how the data must be presented.

For the time being, the ESPD-EDM does not conform 100% to this rule: the purpose of the code lists PropertyGroupType and BooleanGUIControlType and of the CAPTION tag aim precisely to the opposite. They are not part of the Business Domain Data Model.

One reason that led to include these kind of "processing instructions" in the ESPD-Exchange Data Model is the high level of abstraction of the ISA2 Core Criterion and Evidence Vocabulary (CCEV) (the UBL-2.3 cac:TenderingCriterion is a specialisation of this vocabulary). As GROUPs and SUBGROUPS of REQUIREMENT(s) and of QUESTION(s) may be freely and unlimitedly nested, the software applications may have a hard time to detect whether a GROUP or SUBGROUP contains REQUIREMENT(s) and QUESTION(s) or just QUESTION(s) (which is usual in the ESP-EDM specification). Or vice-versa, if a GROUP or SUBGROUP comes first with QUESTION(s) followed by REQUIREMENT(s) (something that never happens in the ESPD-EDM specification).

One way for the ESPD-EDM to help software applications understand that a nested data structure is a GROUP of REQUIREMENT(s) or just of QUESTION(s) would have been codifying it as "REQUIREMENT_GROUP" or "QUESTION_GROUP", using for that purpose the element cbc:PropertyGroupTypeCode element (similarly to what is done with the cbc:TypeCode element inside the cac:TenderingCriterionProperty). However for backwards compatibility reasons with the MS software applications the decision was made to reserve the cbc:PropertyGroupTypeCode to control the GUI behaviour by means of the values defined in the code list PropertyGroupType (codes ON*, ONTRUE and ONFALSE).

The way currently used by software applications to detect whether a GROUP (or SUBGROUP) carries REQUIREMENT(s) or not is to look at the type of the first criterion property: if the first cac:TenderingCriterionProperty is of cbc:TypeCode value REQUIREMENT then it is a REQUIREMENT_GROUP, if it is of value QUESTION then the GROUP (or SUBGROUP) contains only QUESTION(s).

In future versions, the ESPD-EDM should get rid of these codes and mechanisms that couple the eProcurement Data Model to the dynamic building-up of the Graphic User Interfaces (GUIs) or to other processing needs. One possible solution could be to separate the particular software applications needs from the business data model by means of ''annotations'' that can be linked to each data element that needs it, at integration data time (i.e. when acquiring the data; e.g. just after the reception of an eBusiness Document from another system).

For this, imagine that each element of the Criteria Taxonomy data structures could contain (or be preceded by) one or more instructions addressed to the software application for one particular purpose, as illustrated in the figure below (elements starting with an @ symbol):

Annotation with processing instructions of one Criterion Data Structures

Figure 48. Annotation with processing instructions of one Criterion Data Structures

4. Exclusion criteria

REQUIREMENT tbr092-015, 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.

REQUIREMENT 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. These should be retrieved from e-Certis.

As suggested in section "Criteria Data Structures" criteria may be grouped in several different categories. The figure below is intended to identify and list these categories for the Exclusion criteria (branches in text boxes), and specific subgroups within each category (leaves in text without boxes).

Each branch in this 'criteria classification' corresponds to one data structure that is identical for all the leaves under that branch.

Exclusion criteria clasification

Figure 49. Exclusion criteria clasification

4.1. Convictions

Information requirement

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

The label ''Convictions'' groups all the criteria with identical data structures classified as:

''participation in a criminal organisation'', ''corruption'', ''fraud'', ''terrorist offences linked to terrorist activities'', ''money laundering or terrorist financing'', ''child labour and other forms of trafficking in human beings''.

Note about the ESPD Service

In an initial phase, the European Commission provided an ESPD service to support the ESPD’s uptake. As announced in 2018, on 2 May 2019, the Commission’s ESPD service has been turned off. To reap the full benefit of an electronic ESPD, the integration with national eProcurement services and national databases is necessary. This will enable data reusability, default form pre-filling and data interexchange among different databases. In turn, buyers and suppliers will benefit from the automatism, making the application of the ESPD much easier and decreasing the data errors rates.

Data structure

Convictions data structure

Figure 52. Data Structure for all 'Conviction' exclusion grounds

XML Example

The fragment of XML code below illustrates how a 'Convictions' criterion looks like in ESPD Request. See comments beneath the example.

'Participation in a criminal organisation' conviction

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Participation in a criminal organisation -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">005eb9ed-1347-4ca3-bb29-9bc0db64e1ab</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">crime-org</cbc:CriterionTypeCode>
                <cbc:Name>Participation in a criminal organisation</cbc:Name>
                <cbc:Description>Has the economic operator itself or any person who is a member of its administrative, management or supervisory body or has powers of representation, decision or control therein been the subject of a conviction by final judgment for participation in a criminal organisation, by a conviction rendered at the most five years ago or in which an exclusion period set out directly in the conviction continues to be applicable? As defined in Article 2 of Council Framework Decision 2008/841/JHA of 24 October 2008 on the fight against organised crime (OJ L 300, 11.11.2008, p. 42).</cbc:Description>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ae5e864a-f3ba-489b-ba17-b87af8b10138</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a8d55a62-425a-4284-b450-b5b34622a4fa</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4bd07682-ee14-4744-b7de-96c8c8adb6f3</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c31b6447-bf88-4172-901a-f9b105205391</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f5276600-a2b6-4ff6-a90e-b31fe19dae41</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a1534624-95cf-4519-bdaa-856d5acf59b6</cbc:ID>
                                        <cbc:Description>Date of conviction</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f36ee1fb-210b-4786-b351-e0194ba2df89</cbc:ID>
                                        <cbc:Description>Reason</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">05bd1155-a780-4eef-9526-09d90b1b5359</cbc:ID>
                                        <cbc:Description>Who has been convicted</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5969410e-0884-41c6-ae13-e7f4666b2e81</cbc:ID>
                                        <cbc:Description>Length of the period of exclusion</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">108399ae-0332-4c14-bd3b-69d5035a2c53</cbc:ID>
                                                <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f59271bd-8049-41cc-a4d7-06a4f0762d09</cbc:ID>
                                                  <cbc:Description>Please describe them</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e33c4da3-fbd4-4b84-b716-def041300c12</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5b633586-4ef3-454b-ba76-74db49b1844d</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->
  1. Date of conviction. Mandatory format 'YYYY-MM-DD'

  2. The reason of convictions. A descriptive text.

  3. The natural person or legal entity convicted. A text.

  4. Length of the period of exclusion. A cac:Period will be used in the response by the economic operator. The EO may specify a starting date and an end-date or, alternatively, a text to commenting the length. See XML example in the ESPD Response section.

  5. If the answer is No the QUESTION 'Please describe them' should not be shown.

  6. Text box to describe the measures to demonstrate the economic operator’s reliability.

  7. A whole group related to one conviction can be repeated multiple times (or deleted).

  8. If answered as No the group of QUESTION(s) relating the online evidence should not be shown. Beware that the ESPD Response behaves totally differently as far as evidences are concerned. The data concerning the evidence in the ESPDRequest document is placed in the ESPD Response document in a component cac:Evidence in a different manner. See the section ESPD Response for more details on this. See also the XML examples.

  9. The URL where to access the evidence. Will be placed in an element of the object cac:Evidence. See chapter "6.8 Evidences".

  10. By specifying that the value of the expected data type is an evidence identifier (code EVIDENCE_IDENTIFIER of the Code List ResponseDataType`) the Response will have to contain an evidence supplied in an element of the object cac:Evidence, at the end of the XML Instance. See chapter "6.8 Evidences".

  11. The issuer party of this evidence (e.g. a base registry). Will be placed in the element cac:Evidence/cac:DocumentReference/cac:Attachment/cac:IssuerParty. Some countries use verification codes associated to evidences. To specify these verification codes you can use the Evidence ID, as in the end the code identifies uniquely the Evidence in the issuer system (see this XML example, look for 'Verification code' inside the example, bullet number 6).

  12. National criterion defined by the MS in e-Certis (this example corresponds to Finland) related to the EU criterion on this conviction.

  13. An additional specification for this national criterion, in this case related to the evidence that will be required by this Member State.

  14. UUID supplied by e-Certis. See also the criterion spread-sheet.

  15. Exclusion criteria taxonomy code defined in the criterion spread-sheet.

  16. Compulsory name and description for the criterion as defined in e-Certis. See also ESPD-criterion spreadsheet. Beware that UBL-2.3 allows '0..n' description lines!

  17. This property is a caption, a mere 'label'. See Code List CriterionElementType for the complete list of possible options. Beware that when a property is of type CAPTION the cbc:ValueDataType must be set to NONE.

  18. As the property is a CAPTION no response is expected from the economic operator. See Code List 'ResponseDataType' for the complete list of possible options.

  19. Notice that in the ESPD Request the criterion properties never use its element cbc:Name.

  20. EU legislation data related to this criterion. Notice that all the textual fields have multiple cardinality and may specify the language (attribute languageID. This can be used to express the same content in different languages. No language specified defaults to en (English).

  21. The complete title as published in Eurlex or in a national official electronic bulletin board is expected for this field.

  22. A quick reference name to refer to the legislation is expected for this field.

  23. The jurisdiction level (or scope) covered by this legislation.

  24. One or more articles from this legislation where the criterion is defined and referred to. Beware that the cardinality of this field is multiple.

  25. Groups codified as ON* must be processed always (e.g. all its elements shown on a GUI or automatically parsed and saved, etc.).

  26. Pay attention to this type of QUESTION(s). It is intended to act as a decision point. If answered with yes (INDICATOR value = true) some additional questions will be asked to the economic operator. Thus the value of the code of the next sub-group (set to ONTRUE).

  27. This property is a QUESTION, therefore a specific type of value will be expected from the economic operator in the ESPD Response (an INDICATOR, i.e. a 'boolean' value true/false, in this case).

  28. The cbc:ValueDataType indicates the type of value that the buyer requires for this QUESTION. Therefore, in its answer (inside the ESPD Request document) the economic operator will have to use also an INDICATOR value (true/false). Otherwise the mechanism used to validate the ESPD Response should consider the XML instance as invalid (should be treated as a FATAL error).

  29. Data structures defined by GROW are re-usable. This is specially the case (but not uniquelly) of the structure 'Is this information available electronically?' Notice that the UUID that identifies this structure is always the same in all the criteria that include it. Similarly structures that are reused in different criteria do have the same UUID (as they are the same). Beware that the group of properties (URI, Reference/Code, Issuer) will only be shown if the answer is 'Yes', thus the sub-group code ONTRUE.

Note for the future: Cross-border/cross-sector codes

Some relevant trans-European initiatives like ECRIS, BRIS, EESSI, and other, have defined Code Lists and other reference data that could be used in e-Procurement, and specifically by the ESPD. This would enhance the cross-border and cross-sector semantic and technical interoperability. Thus, in the case of Convictions, a new requirement could be introduced in G1 (see figures above) asking for the ECRIS Code corresponding to the offence that will be specified in the Response in case the Economic Operator answered ''yes'' to the first Requirement. The ECRIS Codes can be consulted in the Annex to the COUNCIL DECISION 2009/316/JHA of 6 April 2009 on the establishment of the European Criminal Records Information System (ECRIS) in application of Article 11 of Framework Decision 2009/315/JHA.

4.2. Contributions

Related information requirements

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

REQUIREMENT

The buyer needs to be able to specify national exclusion criteria linked to one EU criterion as well as criteria particular for the procurement procedure. The economic operator, in the ESPD Response document, will have to responde "Yes" or "No" to each national criterion thus confirming that it in breach of the Law.

See also the REQUIREMENT tbr070-015 about economic thresholds regarding unpaid taxes or social security obligations.

Mock-ups - buyer perspective

This other screen-capture below represents a possible mock-up, from the buyer perspective, for the edition of requirements in 'Contributions' criterion (Payment of Taxes).

Payment of Taxes

Figure 58. 'Payment of Taxes', REQUIREMENT edition (Buyer Perspective)

Mock-ups - economic operator perspective

This other mock-up illustrates what the economic operator sees.

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Payment of Taxes

Figure 59. 'Payment of Taxes', (EO perspective)

Data structure

Contributions

Figure 60. 'Contributions' criterion data structure

XML Example

Payment of Taxes (PoT)

<!... header elements removed for brevity -->

<!-- Criterion:Payment of taxes -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b61bbeb7-690e-4a40-bc68-d6d4ecfaa3d4</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">tax-pay</cbc:CriterionTypeCode>
                <cbc:Name>Payment of taxes</cbc:Name>
                <cbc:Description>Has the economic operator breached its obligations relating to the payment of taxes, both in the country in which it is established and in Member State of the contracting authority or contracting entity if other than the country of establishment?</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">61f8dd3d-5ec6-4718-be92-4e58df6d0343</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">364f5ed8-2861-4eb3-bffc-b81732325ea8</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cf127b09-2ca6-4365-bade-e8c90b8e8528</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">610f01af-b5c6-486b-9b5e-8ea35c80beeb</cbc:ID>
                                <cbc:Description>Threshold</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedAmount currencyID="EUR">500000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f89b64e0-db7e-4ec9-9657-17755521b7ab</cbc:ID>
                                <cbc:Description>Additional Information</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>[Additional information provided by the CA]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">098fd3cc-466e-4233-af1a-affe09471bce</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e51f555a-48ec-4f06-853c-a162dce98668</cbc:ID>
                                        <cbc:Description>Your answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f8499787-f9f8-4355-95e2-9784426f4d7b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">280e5b46-66b3-40c4-bb7a-0dcbbbea519b</cbc:ID>
                                                <cbc:Description>Country or member state concerned</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CODE_COUNTRY</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cd469ace-ae87-4203-b182-10186f8d7d8b</cbc:ID>
                                                <cbc:Description>Amount concerned</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7c2aec9f-4876-4c33-89e6-2ab6d6cf5d02</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">08a4c9e3-5d00-4058-977d-27886783ab75</cbc:ID>
                                                  <cbc:Description>Has this breach of obligations been established by means other than a judicial or administrative decision?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3cb7abf1-662a-4756-b61c-7bc716c1fafc</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e03fdd7b-ab5b-4413-9d4c-1841bff6ac4d</cbc:ID>
                                                  <cbc:Description>Please describe which means were used</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fc57e473-d63e-4a04-b589-dcf81cab8052</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f6402f3e-3e4f-482f-abc3-d754815809cc</cbc:ID>
                                                  <cbc:Description>Has the economic operator fulfilled its obligations by paying or entering into a binding arrangement with a view to paying the taxes contributions due, including, where applicable, any interest accrued or fines?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6c3609e1-9add-4fa9-9409-62ce72ae4548</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">04b9b95c-13f4-4fd1-993f-5e0b3a766cdb</cbc:ID>
                                                  <cbc:Description>Please describe them</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c882afa4-6971-4b00-8970-0c283eb122cc</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d2e558b1-53b0-42d6-bd8b-52ca95f86b1e</cbc:ID>
                                                  <cbc:Description>If this breach of obligations was established through a judicial or administrative decision, was this decision final and binding?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">815422d6-f8a1-418a-8bf0-3524f7c8f721</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">228aa0c1-43a1-4c52-a8a6-587df8838d75</cbc:ID>
                                                  <cbc:Description>Please indicate the date of conviction or decision</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fd161583-cd57-4033-b387-60c76f878c26</cbc:ID>
                                                  <cbc:Description>In case of a conviction insofar as established directly therein, the length of the period of exclusion</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f99c2b68-bd5e-4cf8-b51a-ed906defe9e9</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d13ad29a-f24a-4e01-b716-7f61006d083f</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>
  1. The MS defined this national 'Payment of Taxes' criterion in e-Certis.

  2. Reference to the EU Legislation. This reusable structure is identical for all the exclusion criteria.

  3. For this ESPD Request Payment of Taxes criterion, the Member State defined in e-Certis a national REQUIREMENT consisting in the specification of the 'threshold amount of debt that an economic operator have with the national Tax Agency' (50 Euros in this example).

  4. Notice that type of property used is REQUIREMENT. This entails that: a cbc:ValueDataType will be present indicating the type of value the buyer uses for this REQUIREMENT (e.g. AMOUNT, INDICATOR, DESCRIPTION, etc.; see the Code List ResponseDataType, the values are the same for buyers REQUIREMENT(s) than for economic operator response values).

  5. Beware that No answer is expected here from the economic operator (do not get confused by the presence of the cbc:ValueDataType, as said it is used by both the Buyer and the EO.

  6. The value supplied by the buyer for this requirement (50 Euros, in this example). Notice that the currency is specified in the attibute currencyID of the cbc:Amount component.

  7. The MS also allows the buyer the possibility of adding multiple additional textual requirements (in this case the Buyer uses this to explain that ''Beware that the national Tax Agency won’t permit the existence of a debt, even if minimial, for two consecutive years'').

  8. Again, no answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer.

4.3. Environment, Social, Labour Law

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), more specifically tbr070-009, tbr070-004, tbr070-013.

Category ''Social'' encompasses criteria with identical data structures, classified as:

''breaching of obligations in the fields of environmental law'', ''breaching of obligations in the fields of social law'' and ''breaching of obligations in the fields of labour law''.

Mock-ups - buyer perspective

Environmental Law

Figure 61. 'Environmental Law' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Environmental Law

Figure 62. 'Environmental Law' criterion mock-up - EO perspective

Data structure

Environmental Law

Figure 64. 'Environmental Law' criterion data structure

XML Example

'Environmental Law'

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Breaching of obligations in the fields of environmental law -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a80ddb62-d25b-4e4e-ae22-3968460dc0a9</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">envir-law</cbc:CriterionTypeCode>
                <cbc:Name>Breaching of obligations in the fields of environmental law</cbc:Name>
                <cbc:Description>Has the economic operator, to its knowledge, breached its obligations in the fields of environmental law? As referred to for the purposes of this procurement in national law, in the ESPD, the relevant notice or the in the ESPD, the relevant notice or , in Article 18(2) of Directive 2014/24/EU or in the ESPD.</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0be59e53-a54b-4d55-919f-27c43ddf0a7a</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">926641b9-c06b-400a-965b-bfebf0b37265</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c1201af-033e-46a4-8128-74ec1cc8dec0</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">976b5acb-c00f-46ca-8f83-5ce6abfdfe43</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">823a071e-8a30-4746-a49d-819beba42d2a</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">64a2102c-4af1-4ecb-97b3-0c41907ec0f6</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2c555ed7-b410-42f5-8349-aeffdb71a5cc</cbc:ID>
                                        <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c0bc6c22-d74c-47c9-ad3e-9966aefcf7f0</cbc:ID>
                                                <cbc:Description>Please describe them</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">98c3450f-f8cd-466f-acfe-2c6dc940c6f0</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">eeeb0915-bff0-4b54-94e6-7974ef4d2090</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

4.4. Business

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

Mock-ups - buyer perspective

Bankruptcy

Figure 65. 'Bankruptcy' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Bankruptcy

Figure 66. 'Bankruptcy' criterion mock-up - economic operator perspective

Data structure

Bankruptcy

Figure 68. 'Bankruptcy' criterion data structure

XML Example

'Bankruptcy'

_<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->_

<!-- Criterion:Bankruptcy -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d3732c09-7d62-4edc-a172-241da6636e7c</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">bankruptcy</cbc:CriterionTypeCode>
                <cbc:Name>Bankruptcy</cbc:Name>
                <cbc:Description>Is the economic operator bankrupt? This information needs not be given if exclusion of economic operators in this case has been made mandatory under the applicable national law without any possibility of derogation where the economic operator is nevertheless able to perform the contract.</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a5429140-3b97-4ea4-a394-f6925bcaa2c1</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9726bad-0a49-4283-841d-02d5c9e17166</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8be235a5-28ce-4eb7-9346-5081e078e8a2</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ce25a3f9-9441-45f1-9119-305aa810226c</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7bb7076c-25d6-4d01-a5a5-cb6ffce52519</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">84897200-d392-49f4-a30a-24f0839e4b11</cbc:ID>
                                        <cbc:Description>Indicate reasons for being nevertheless to perform the contract</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">762b11f1-f868-45df-beaa-1558a3120ade</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5677d83e-aa4c-44e5-9882-4b4fe946905a</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

_<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->_

4.5. Misconduct

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

Mock-ups - buyer perspective

Professional misconduct

Figure 69. 'Professional misconduct' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Professional misconduct

Figure 70. 'Professional misconduct' criterion mock-up - economic operator perspective

Data structure

Professional misconduct

Figure 72. 'Professional misconduct' criterion data structure

XML Example

'Professional Misconduct'

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Guilty of grave professional misconduct -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">514d3fde-1e3e-4dcd-b02a-9f984d5bbda3</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">prof-misconduct</cbc:CriterionTypeCode>
                <cbc:Name>Guilty of grave professional misconduct</cbc:Name>
                <cbc:Description>Is the economic operator guilty of grave professional misconduct? Where applicable, see definitions in national law, the relevant notice or the procurement documents.</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">96cd710b-436e-4ff5-a141-3aac6ee43789</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0004587c-4eb3-417d-8fd6-97752da5d1ce</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">125db323-d942-4efe-a48b-7f114206dda3</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">06009017-4cae-4938-8a38-604e565c1c7b</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2cbcf978-765c-40aa-996b-b1d082485cef</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8cb8ac3a-652a-4b96-8969-ccbbfad27198</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">535ffa7d-8639-49f5-99cb-dc49ed860624</cbc:ID>
                                                <cbc:Description>Have you taken measures to demonstrate your reliability</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b8deb91b-af02-4f67-bab0-14db098838ad</cbc:ID>
                                                  <cbc:Description>Please describe them</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">721b7270-c602-49fc-bb3f-f97128641300</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b2894bb0-0130-4aa6-a0f2-f411e127b78f</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

4.6. Conflict of interest

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

We have divided the conflict of interest criteria in two groups, this first group is composed of two criteria with the same structure:

  • partic-confl: Conflict of interest due to ''direct or indirect involvement in the preparation of this procurement procedure'';

  • prep-confl: Conflict of interest due to ''participation in the procurement procedure''.

The second group, named ''Early termination'', is explained in a different section. See section "Early termination).

Mock-ups - buyer perspective

Conflict of interest

Figure 73. 'Conflict of interest' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Conflict of interest

Figure 74. 'Conflict of interest' criterion mock-up - economic operator perspective

Data structure

Conflict of interest

Figure 76. 'Conflict of interest' criterion data structure

XML Example

'Participation in the procurement procedure' conflict of interest

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Conflict of interest due to its participation in the procurement procedure -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b1b5ac18-f393-4280-9659-1367943c1a2e</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">partic-confl</cbc:CriterionTypeCode>
                <cbc:Name>Conflict of interest due to its participation in the procurement procedure</cbc:Name>
                <cbc:Description>Is the economic operator aware of any conflict of interest, as indicated in national law, the relevant notice or in the ESPD, the relevant notice or due to its participation in the procurement procedure?</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">48e12b79-7f31-4f3d-a009-314307122380</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3530028b-4bb9-4631-9be7-3354a6addd15</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d1c5244c-4fec-4b38-9f35-b356bef1548a</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f37bb3b5-caa9-4669-940e-c049720c23d9</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e582fd07-a464-4cdb-8b03-89980059f5e0</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">63abbc31-22ee-4b47-ada8-96eb02de7e7b</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3041829d-4042-43ad-a42a-303028280086</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

4.7. Early termination

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), more specifically tbr070-009, tbr070-004, tbr070-013.

Mock-ups - buyer perspective

Early termination

Figure 77. 'Early termination' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Early termination

Figure 78. 'Early termination' criterion mock-up - economic operator perspective

Data structure

Early termination

Figure 80. 'Early termination' criterion data structure

XML Example

Early termination conflict of interest

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Early termination, damages or other comparable sanctions -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3293e92b-7f3e-42f1-bee6-a7641bb04251</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">sanction</cbc:CriterionTypeCode>
                <cbc:Name>Early termination, damages or other comparable sanctions</cbc:Name>
                <cbc:Description>Has the economic operator experienced that a prior public contract, a prior contract with a contracting entity or a prior concession contract was terminated early, or that damages or other comparable sanctions were imposed in connection with that prior contract?</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1887885e-9783-4563-a44f-9c3fec26f3c7</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">849a83f3-d4f8-4b67-8124-2c8133137b42</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bc28f42c-999f-41ec-8280-751e9dfc672c</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">70f55a26-19ca-4b3a-9ce4-d6e6394e08ea</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5934f108-1682-472e-be9c-8717c51bca3b</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">55207fdf-803e-46ef-a096-1c8ea17911cd</cbc:ID>
                                                <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1556d05c-84b8-4a23-91dc-6d0ddb09aa2b</cbc:ID>
                                                  <cbc:Description>Please describe them</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">dcb433c0-8de4-40ad-b70e-1daaea91bcc8</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d7977bf6-67d2-4fb1-8d1e-bc19a3943fc3</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

4.8. Misinterpretation

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

Mock-ups - buyer perspective

Misinterpretation

Figure 81. 'Misinterpretation' criterion mock-up - buyer perspective

Mock-ups - economic operator perspective

Beware that this mock-up is not showing the national criteria. For this mock-up it is presumed that by answering 'Yes' to the general EU criterion all the national criteria QUESTION 'Your answer' will be also set to 'Yes'.

Misinterpretation

Figure 82. 'Misinterpretation' criterion mock-up - economic operator perspective

The UBL specification allows always multiple lines of text for the component cbc:Description. This feature can be used to split long descriptions into multiple lines, specially when the description contains enumerations.

The data structure for the criterion "Guilty of misinterpretation […​]" below uses the feature to divide four possible cases into different lines. Software and transformation solutions can also use it to generate an XML instance where the enumeration is split in multiple cbc:Description lines. See screen-captures below representing the data structures of this criterion for the model.

Data structure

Misinterpretation

Figure 84. 'Misinterpretation' criterion data structure

XML Example

'Misinterpretation' conflict of interest

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Guilty of misinterpretation, withheld information, unable to provide required documents and obtained confidential information of this procedure -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">696a75b2-6107-428f-8b74-82affb67e184</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">misinterpr</cbc:CriterionTypeCode>
                <cbc:Name>Guilty of misinterpretation, withheld information, unable to provide required documents and obtained confidential information of this procedure</cbc:Name>
                <cbc:Description>Can the economic operator confirm that:</cbc:Description>

                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8661b1db-b160-4e56-ab0b-498a1d7996a3</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">429d2255-0c9b-4e15-a3ba-76163c9b102f</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6a590e19-8815-4b95-875b-1b58c1fc9476</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f3a6836d-2de2-4cd1-81ca-fb06178d05c5</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">68d5af5e-ca71-47ab-afb7-d3299f12d8e6</cbc:ID>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3fdeb1ea-e207-43d1-b4a2-89cde7e1483e</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d1fa6189-b8f0-467d-b64d-ab740a4756c5</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

_<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->_

4.9. Purely national criteria

See formal requirements related to exclusion grounds in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically tbr070-009, tbr070-004, tbr070-013.

Other requirements related specifically to purely national criteria are:

REQUIREMENT

The Member State must be able to specify in e-Certis individual national criteria, and the economic operator must be able to answer to each individual purely national exclusion grounds criterion.

REQUIREMENT

For the purely national exclusion grounds that have evidences related in e-Certis, the required evidences should be displayed. When the criterion has no related evidences, the text "No evidence required for this criterion" should be displayed. Per each national criterion the EO needs to be able to provide one or more evidences.

The ESPD-EDM V2.1.1 Extended ESPD introduced and important feature: the MS can specify and save in the XML individual national criteria. The mock-ups, data structure and XML example below show how. In the ESPD-EDM, it is kept as the only version of the ESPD is the equivalent to the EXTENDED that was introduced in V2.1.1.

Mock-up - economic operator perspective

The figure below shows a fragment of a list of national criteria that a software application has captured from e-Certis. Per each criterion the economic operator has to specify whether it fulfills the Criterion or not and eventually provide references to online evidences.

Purely national criteria

Figure 88. 'Purely natural criteria' - economic operator perspective

Data structure

Purely national criteria

Figure 89. 'Purely national criteria' data structure

XML Example

'Purely national criteria'

<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

<!-- Criterion:Purely national exclusion grounds -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">63adb07d-db1b-4ef0-a14e-a99785cf8cf6</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">nati-ground</cbc:CriterionTypeCode>
                <cbc:Name>Purely national exclusion grounds</cbc:Name>
                <cbc:Description>Other exclusion grounds that may be foreseen in the national legislation of the contracting authority's or contracting entity's Member State. Has the economic operator breached its obligations relating to the purely national grounds of exclusion, which are specified in the relevant notice or in the procurement documents?</cbc:Description>

                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">45d43642-e515-486f-b189-d0ed67f05037</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8d79d5f7-dc21-45e9-b188-e02008b854e0</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">491b1c19-a1db-4ff9-9cb4-a1232eed82ef</cbc:ID>
                                <cbc:Description/>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4f5088db-ae29-46fb-b642-30240aa2248a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fb9be63d-9b0c-4a4a-8745-299c3a4433e6</cbc:ID>
                                        <cbc:Description>[Text describing the national criterion]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3007d3ed-045b-4740-81f4-f79166ff7f97</cbc:ID>
                                        <cbc:Description>[Type of evidence from e-Certis]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">73786eb6-db0e-418b-8be2-16a1bb8399de</cbc:ID>
                                        <cbc:Description>Your answer?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a4483120-627b-418d-8933-9536aba247f6</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">30315ebf-0f7b-4e4c-8f8f-de09b1134316</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

_<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->_

5. Selection criteria

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

This chapter on selection criteria provides details on how to implement the formal requirements set in the eSens ESPD BIS 41 - Single European Document (Version 2.0.0) document. See specifically these global requirements related to selection criteria: br41-002, tbr070-010, tbr070-013, tbr070-018.

As for the exclusion criteria (and following requirement tbr070-013) we have grouped the selection criteria under different categories. The figure below is intended to identify and list these categories for the selection criteria (branches in text boxes), and specific subgroups within each category.

Each branch in this 'criteria classification' corresponds to one data structure that is identical for all the leaves under that branch (e.g. compare the names of the boxes with the tabs and ElementType column of the spreadsheets containing ESPD-criterion data structures).

Selection criteria classification

Figure 90. Selection criteria classification

5.1. Lot Management approach for Selection Criteria

As already explained in previous sections (see ESPD Request chapter) the Lot Management logic has been adapted to be ensure the alignment with eForms.

The buyer may specify the Lots that each selection criteria apply by using the element cac:TenderingCriterion that includes cac:ProcurementProjectLotReference. The image below shows the UBL-2.3 schema for TenderingCriterion:

cac:TenderingCriterion/cac:ProcurementProjectLotReference

Figure 91. cac:TenderingCriterion/cac:ProcurementProjectLotReference

5.2. Initial question for the EO to fulfil or not the criteria

In this version of ESPD, a new data structure has been added to the selection criteria to get more information about the EO and the fulfilment of the selection criteria. The UUID identifying the group is 0e50931d-4d39-4f1d-9fdc-b2cf16c0807a. It is a common structured reused over selection criteria.

Data structure

The following image shows an example of how it represented in the spread-sheets (see ESPD-Criterion)

Does the EO fulfil the criteria by itself? Data structure

Figure 92. 'Does the EO fulfil the criteria by itself? Data structure and UUID.

Mockup

Does the EO fulfil the criteria by itself? Mock up

Figure 92. 'Does the EO fulfil the criteria by itself? Mock up from the EO perspective.

The figure above is an example of how this information should be displayed. There, the Economic Operators must provide an answer to whether is going to fulfil the criteria by itself or relying on other entity.

5.3. Suitability

See formal requirements related to 'Suitability' criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically the requirement tbr070-003

Suitability (enrolments)

For each criteria regarding suitability, the buyer should be able to provide: the register type (Occupations code list, see ESPD-CodeLists.xlsx) in case of criterion "Enrolement in a relevant professional register", and the name and its URL and for other criteria related to registries.

Data Structure

Few details regarding data structure for Suitability selection criteria

  1. It allows the definition of multiple national sub-criteria (to be retrieved from e-Certis): cardinality "0..n" of the SUBCRITERION group;

  2. It also allows the buyer to speciy multiple groups of REQUIREMENT(s) (in this case to specify which registers the economic operator should be registered in).

  3. Regarding the groups of questions, notice that the main question is addressed to get the confirmation from the economic operator that it fulfills the criterion (if "Yes" the economic operator is registered). In case of answering "No" a sub-group of one QUESTION must be shown (the one asking the economic operator to provide the reason why it is not registered in the register specified by the buyer).

(The figure below is defined in the the tab "Suitability-I of the ESPD-criterion spread-sheet).

SC Suitability enrolement

Figure 100. 'Suitability' criterion data structure (enrolments)

XML Example

The following XML example illustrates how the ESPD would look like when the Lots are specified.

'Enrolment in a relevant professional register' suitability criterion

<!... header elements removed for brevity -->

<!-- Criterion:Enrolment in a relevant professional register -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6ee55a59-6adb-4c3a-b89f-e62a7ad7be7f</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">prof-regist</cbc:CriterionTypeCode>
                <cbc:Name>Enrolment in a relevant professional register</cbc:Name>
                <cbc:Description>It is enrolled in relevant professional registers kept in the Member State of its establishment as described in Annex XI of Directive 2014/24/EU; economic operators from certain Member States may have to comply with other requirements set out in that Annex.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b6ab1c8b-08d5-43f9-b34b-5031ea517514</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">16b75711-02e3-43ce-87a4-4a428bc11d5a</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9a14e990-8280-4122-bfcd-d4a0694ec2c4</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b01d8f8f-ceac-4b47-b7aa-88cdeb630465</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">53fe9bf5-38c9-4281-b8a9-7250b75a9407</cbc:ID>
                                <cbc:Description>occupation</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CODE</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedCode listID="PleaseSelectTheCorrectOne" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">[occupation Code]</cbc:ExpectedCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1d497f55-150a-4b96-b8c3-300e63401a02</cbc:ID>
                                <cbc:Description>Other Register</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>[Other Register Type]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e8a82f06-6267-4125-a262-afeb987b4981</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">27109f66-df32-4f7b-afd3-98d3079cf358</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6c9a9066-c027-4b38-ad23-968612769d94</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">877d221b-e528-4762-8a25-11554562bbe6</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6cce6b8e-c53d-4598-8150-ac49aba3b9c7</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">68cd0cdb-2975-4aa4-a6d3-fc4d24fb2f7c</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">70d5bbcf-0581-4d0f-b5c7-8b604a791972</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">31a9173f-f72e-49fc-9f5c-d7e90ccc7e02</cbc:ID>
                                                <cbc:Description>Registration number</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3a4a5421-81cc-468e-b69f-b86bf8c7932d</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7468215a-299e-480d-acd6-e7ef393cf4c3</cbc:ID>
                                                <cbc:Description>Reasons why your are not registered</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2826f86e-afc7-4826-9ac6-37b961125fb4</cbc:ID>
                                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">39618b2c-ed5c-4b4d-b77b-b0fa735ec3df</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->

The code list 'occupation' is used to determine the area to which the EO should be registered in. It comes from the ESCO classification, in case the Buyer do not find the appropiate code to define the type of professional enrolement it can select code '0000.0' which stands for other. Then would be able to include the type using a text box.

Suitability (service contracts)

Data Structure (service contracts)

(The figure below is defined in the the tab "Suitability-II" of the ESPD-criterion spread-sheet).

Suitability criterion data structure (service contracts)

Figure 102. 'Suitability' criterion data structure (service contracts)

XML Example (service contracts)

Example of suitability criterion

<!--... header elements removed for brevity... -->

<!-- Criterion:For service contracts: authorisation of particular organisation needed -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9eeb6d5c-0eb8-48e8-a4c5-5087a7c095a4</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">autorisation</cbc:CriterionTypeCode>
                <cbc:Name>For service contracts: authorisation of particular organisation needed</cbc:Name>
                <cbc:Description>Is a particular authorisation of a particular organisation needed in order to be able to perform the service in question in the country of establishment of the economic operator?</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">73570c2d-8e88-41ae-9750-ed72076aaaf0</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">02143118-7c75-4ed7-9e3c-bd8ccc84fd9a</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7696fb3f-9722-43b8-9b91-ad59bb4b8ad2</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3d13038a-fd4e-4d07-ab43-14d4bd2f4e0f</cbc:ID>
                                                <cbc:Description>If yes, please describe them</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f7901626-2f5f-4977-8038-b197a51dd333</cbc:ID>
                                                <cbc:Description>Indicate whether the economic operator has it</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">39b36171-7033-462a-b493-8648a902d9f3</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a53561d5-6614-4dbe-987e-b96f35387f46</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7fbb14cb-dd63-4f77-aa3d-13baa7e78e38</cbc:ID>
                                <cbc:Description>Register name</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>[Register Name]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a24a37df-6a98-48a0-80c7-6e3837c45bd5</cbc:ID>
                                <cbc:Description>URL</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">URL</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b76e24b8-279f-4c86-b1c6-792b8b24f73d</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">67f22f88-4fc4-416c-9287-be8ea5b610d0</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">78238b9e-31f6-4b5e-a092-2776b2ec89dc</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4dff1e8c-823f-4fc3-af83-368c8c53b482</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6cce6b8e-c53d-4598-8150-ac49aba3b9c7</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b376d27f-3898-420f-adbb-7d0869fa0d47</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">70d5bbcf-0581-4d0f-b5c7-8b604a791972</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5a4e1115-7191-4711-8d8b-868bc923c9cb</cbc:ID>
                                                <cbc:Description>Registration number</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3a4a5421-81cc-468e-b69f-b86bf8c7932d</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ab1de04c-0c85-4d0e-8039-300ea95a2b3a</cbc:ID>
                                                <cbc:Description>Reasons why your are not registered</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">04d77b77-f3b8-47cf-adc8-d799e1a801f4</cbc:ID>
                                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a6a1b3fe-dec5-488b-a81f-cbf78d0aa814</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->
  1. A CAPTION, software applications can use it to document the GUI.

  2. As a CAPTION no value is expected to be provided by the buyer (thus the absence of a cbc:Expected…​ element) nor by the Economic Operator (thus the value NONE`for the element `cac:ValueDataTypeCode)

  3. The name of the organisation issuing the authorisation: the Spanish food safety agency.

  4. Notice the use of the attribute languageID meaning, in this example, that the name is expressed in Spanish.

  5. A "choice" structure is coming now: A true/false QUESTION is asked ("Your answer" to the question contained in the Criterion "Is a particular membership of a particular organisation needed in order to be able to perform the service …​". If the user (the EO) answers "Yes" (true) then it has to provide the registration number of the authorisation. Otherwise the EO will have to provide a justification about why the authorisation is not registered.

  6. If yes…​ provide the registration number for the authorisation.

  7. If no…​ provide a justification for not having this authorisation issued by the required organisation.

5.4. Turnovers

See formal requirements related to 'Turnover' criteria ESPD in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically the requirement tbr070-008

Differences between 'general and specific' and 'yearly and average' turnovers
  1. General turnover refers to the general turnover of the economic operator in a period of years and regardless of the nature of the contract, normally the last three or five years (as required in the contract documents or the ESPD).

  2. Specific turnovers refer to the turnover of the economic operator resulting from the activity of the economic operator in the business area covered by the contract;

  3. As far as the data structures are concerned, they can be classified in two groups 'yearly' and 'average':

    • For general and specific yearly turnovers the economic operator specifies a turnover amount (and currency) per year, e.g. one amount for 2016, one amount for 2015, one amount for 2014, etc.

    • For general and specific average turnovers, given the n last years (specified in the ESPD, notices or procurement documents) the economic operator adds all the yearly turnovers of those n years, divides the sum by n and provides the resulting amount.

    • The classification codes for the different turnovers are:

      • (Yearly)

        1. gen-year-to

        2. aver-year-to

      • (Average)

        1. spec-aver-to

        2. spec-year-to

For the general yearly turnover the buyer can specify the number of the past recent years for which it will require Turnovers, and also the minimum amount it expects from the economic operator. The economic operator should only see the same number of groups of fields 'amount + period' than the number of minimum amounts the buyer required.

For the average yearly turnover the buyer can specify the number of fiscal years * ("QUANTITY_YEAR") encompassing the yearly turnovers for which the average is to be calculated; the *minimum amount for which the EO’s average yearly turnover must equal or be greater; and the currency.

For the specific yearly turnover the buyer can specify the number of fiscal years for which the EO will have to provide turnovers (e.g. last 5 years); the Minimum amount expected from the EO, for which each specific yearly turnover must equal or be greater; and the currency.

For the specific average turnover the buyer can specify the number of the past recent fiscal years for which the EO will need to provide the Average Turnover; e.g. last 3 years; the minimum amount expected from the EO, for which the EO’s average yearly turnover must equal or be greater; and the currency.

General turnover

The contracting can specify the number of the past recent years for which it will require turnovers, but also the minimum amount it expects from the economic operator.

Mock-up - buyer perspective

Notice that the buyer can add and remove as many groups of minimum required amounts as needed (in the example below the software application limits the number to five, see tool-tip next to the button "Add"). These requirements are, of course, particular to this procurement procedure and were not defined by the Member State in e-Certis.

General Yearly Turnovers buyer mock-up for common threshold

Figure 106. 'General Yearly Turnovers' buyer mock-up for a a common threshold for all years requested.

General Yearly Turnovers buyer mock-up for a a common threshold for all years requested

Figure 107. 'General Yearly Turnovers' Buyer mock-up when applaying different turnover per year requested.

Mock-up - economic operator perspective

General and Specific Yearly Turnovers

Figure 107. 'General Yearly Turnovers' EO mock-up

Data Structure

In this this figure what it is being shown is that the buyer required three general yearly turnovers, for which it defined minimum amounts in one REQUIREMENT(s) group. Next, three groups of QUESTION(s) are provided, each one of them corresponding to the past three years. Remember that the spreadsheet used in this guide to represent the criteria data structure is also used to generate sample XML instances. So by including three groups of QUESTION(s) in the spread-sheet, the tool generating sample XML instances will automatically generate three sub-groups of properties each one with distinct UUIDs.

General Yearly Turnovers

Figure 108. 'General Yearly Turnovers' criterion data structure

XML Example

General yearly turnover

<!--... header elements removed for brevity... -->
<!-- Criterion:General yearly turnover -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">499efc97-2ac1-4af2-9e84-323c2ca67747</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">gen-year-to</cbc:CriterionTypeCode>
                <cbc:Name>General yearly turnover</cbc:Name>
                <cbc:Description>Its general yearly turnover for the number of financial years required in the relevant notice, the in the ESPD, the relevant notice or the ESPD is as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ed2a13ed-cf3d-478e-888d-cb9b89f55020</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b21ab072-e5b6-495c-ad6e-4ead6993ede5</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">635a537c-57bf-4beb-8b69-d97d49382e1f</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">42824f1f-3574-4e53-80ca-501d22e85ef8</cbc:ID>
                                <cbc:Description>Minimum requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedAmount currencyID="EUR">100000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e3401597-fe8a-4be4-9086-ae16015b1b13</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">514ce671-73b6-4df0-aee5-79e30c9f7e11</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c256fd6d-937d-467a-8446-945d43257ae1</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">496d7f3c-11d4-4b6f-9de4-269b2fe05815</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">275dfaeb-0155-4ad5-a39f-1dd7ca890700</cbc:ID>
                                        <cbc:Description>Amount</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7d0e5eb2-4ce6-42cb-825b-5b402f911197</cbc:ID>
                                        <cbc:Description>Start date; End date</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c69914fe-3fa8-4ac6-a1b3-66cb8088d8b7</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cb4d7604-70dd-4601-9379-7885dd027688</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">37df94d6-2c14-47ea-b71b-75d8c03f70a9</cbc:ID>
                                        <cbc:Description>In case the information concerning turnover (general or specific) is not available for the entire period required, please state the date on which the economic operator was set up or started trading:</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">aecaafbd-2612-433e-8abb-f4542bcec6d7</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1094ee3b-d353-4337-9d79-f0313a7c5e30</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- rest of elements removed for brevity -->

Average yearly turnover

Mock-up - buyer perspective

For criteria of type "average yearly turnover", the following fields can be specified by the buyer:

  1. The number of fiscal years encompassing the yearly turnovers for which the average is to be provided by the economic operator (EO);

  2. The minimum amount for which the EO’s average yearly turnover must be equal or greater;

  3. The currency;

Notice that as for the rest of criteria, the Member State may specify national sub-criteria in e-Certis for this criterion.

average yearly turnover

Figure 112. 'Average yearly turnover' Buyer mock-up

Mock-up - economic operator perspective

In turn, the economic operator:

  1. Will have to provide the average amount and currency for the required period; and

  2. May provide some additional information in a free-text field.

Average yearly turnover

Figure 113. 'Average yearly turnover' EO mock-up

Data Structure

Average yearly turnover

Figure 114. 'Average yearly turnover' criterion data structure

XML Example

Average yearly turnover

<!--... header elements removed for brevity... -->

<!-- Criterion:Average yearly turnover -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b16cb9fc-6cb7-4585-9302-9533b415cf48</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">aver-year-to</cbc:CriterionTypeCode>
                <cbc:Name>Average yearly turnover</cbc:Name>
                <cbc:Description>Its average yearly turnover for the number of years required in the relevant notice, the procurement documents or the ESPD is as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">be471b6b-4093-4ed1-a3a6-16fab9e86ed1</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9be2dab-481e-4183-b574-9fd76e29b90d</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">32f66226-56f3-48e1-87c0-3d8917957fea</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">53882893-f4a8-40ae-99dc-cad7b0748790</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0b8950cc-a073-4b29-baca-1d6125fcfc82</cbc:ID>
                                <cbc:Description>Number of fiscal years</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c03f7fe0-36ce-43a1-b53f-5de455a65f6f</cbc:ID>
                                <cbc:Description>Minimum requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedAmount currencyID="EUR">120000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e8222e1f-0827-4cce-b5b3-2efeb694c5bb</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bf547b11-360d-412e-b51a-ff32a841c7aa</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2db05699-6ba3-48b0-9d0a-5a8f6173cb40</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9e9b7af-11d9-4f98-9118-f0b064b8020f</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e1886054-ada4-473c-9afc-2fde82c24cf4</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fd447188-12a5-42ab-aa66-2c4f12e43025</cbc:ID>
                                        <cbc:Description>Average for the required period</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">57a9382b-45fc-4235-a071-fe8b20cffa55</cbc:ID>
                                        <cbc:Description>Additional information</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fff57e2f-e845-48ac-95bb-1be3109beb41</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">19584299-847b-44b9-98e4-b9ba728b5a3b</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0db6624e-934c-4add-8d11-f53d8c16ca21</cbc:ID>
                                        <cbc:Description>In case the information concerning turnover (general or specific) is not available for the entire period required, please state the date on which the economic operator was set up or started trading:</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ea3d7499-d619-4c72-a1c5-b74fea37c177</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6944be10-5bae-4ec9-bd92-2d4b7b586def</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->

Specific yearly turnover

One characteristic of the "specific" turnovers is that the buyer requires to know which is the economic operator’s turnover for a concrete business domain. The only way of responding that requirement is either by describing the domain in a free-text field (DESCRIPTION ResponseDataType) in Data structures.

Notice that in the Mock-ups and the Data Structures, below, both options are available to the economic operator.

Mock-up - buyer perspective

For specific yearly turnover criterion the following fields can be required by the buyer (CA):

  1. The number of fiscal years for which the economic operator (EO) will have to provide turnovers; e.g. last 5 years;

  2. The minimum amount expected from the EO, for which each specific yearly turnover must equal or be greater;

  3. The currency.

specific yearly turnover' buyer mock-up_

Figure 118. 'specific yearly turnover' Buyer mock-up

Mock-up - economic operator perspective

Notice that in this example:

  1. The buyer required specific yearly turnovers for the past five years;

  2. The minimum amount required by the buyer, and the currency for that amount (the EO should be able to express an identical or greater economic value in a different currency);

  3. The software application has produced up to five groups of properties for each of the last five Fiscal Years (FY1 to FY5);

  4. The economic operator has provided answers for all the properties of each Fiscal Year.

specific yearly turnover

Figure 119. 'specific yearly turnover' EO mock-up

Data Structure

Notice that:

  1. The criterion may have one or more linked national sub-criteria downloaded from e-Certis (SUBCRITERON structure, cardinality 0..n);

  2. The buyer is able to specify the number of fiscal years (REQUIREMENT 'Number of fiscal years');

  3. The description of the business area is a text-field;

  4. The buyer does also specifies the minimum amount required for this specific turnover.

  5. The rest of the criterion are the questions for the economic operator to answer: period and amount (and currency in the amount attribute @currencyID).

Specific yearly turnover

Figure 120. 'Specific yearly turnover' criterion data structure

XML Example

Specific yearly turnover

<!--... header elements removed for brevity... -->

<!-- Criterion:Specific yearly turnover -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">074f6031-55f9-4e99-b9a4-c4363e8bc315</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">spec-year-to</cbc:CriterionTypeCode>
                <cbc:Name>Specific yearly turnover</cbc:Name>
                <cbc:Description>Its specific yearly turnover in the business area covered by the contract for the number of financial years required in the relevant notice, the in the ESPD, the relevant notice or or the ESPD is as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1ab48993-53aa-4782-88f9-7025477a4df6</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a8f1e01c-5ef7-461c-9b21-2df9d7fec60b</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">34b31d0c-5fe7-4f36-874f-a68f3184d919</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">19a68e37-d307-4a28-9061-c22cd767be58</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8d23f156-be4f-4fc7-ae87-c4b2bde59366</cbc:ID>
                                <cbc:Description>Number of fiscal years</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7bbcbc42-e81d-49e5-9570-81563416b1bd</cbc:ID>
                                <cbc:Description>Business domain description</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>IT consulting / development of semantic interoperability solutions</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bf8a8e1d-ad69-4bb9-a023-81b924cb9049</cbc:ID>
                                <cbc:Description>Minimum requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedAmount currencyID="EUR">1000000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4ca9d5c0-28e8-4929-b65f-438fd50c0ee3</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b94a10bc-da55-46ab-936d-06978576849b</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5e778df3-c065-41aa-9867-3df1926efd1a</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">77fe87b5-cbfe-416a-84ed-3afc9cd4a349</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1eb80667-ff73-44b4-b867-c5d1248b723a</cbc:ID>
                                        <cbc:Description>Start date; End date</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">33ded15b-4e7a-4d0d-b9b1-41dd0f756238</cbc:ID>
                                        <cbc:Description>Amount</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4152909d-891b-49cd-aef7-ff8f69108757</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b6c705d0-2c7b-4d5e-9235-2fac283ae23e</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c8a7a9ed-0503-4b0a-bdd6-6e4961dc1b14</cbc:ID>
                                        <cbc:Description>In case the information concerning turnover (general or specific) is not available for the entire period required, please state the date on which the economic operator was set up or started trading:</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4efe3d08-2deb-440a-b3b4-29b0c6fab3c6</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">163f44f9-53b5-414d-95d0-5b1d99b6ea63</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->

Specific average turnover

As for the specific yearly turnover, in the specific average turnover the buyer is interested in knowning the turnover for a concrete business domain. Hence the fields business domain description in the mock-ups and data structures.

Mock-up - buyer perspective

Specific average turnover

Figure 124. 'Specific average turnover' Buyer mock-up

Mock-up - economic operator perspective

Specific average turnover

Figure 125. 'Specific average turnover' EO mock-up

Data Structure

Notice that this specific average turnover structure is 'practically identical' to the data structure of the specific yearly turnover criterion. The only difference is that the cardinality of the amount is 1 (instead of 1..n).

Specific average turnover' criterion data structure

Figure 126. Specific average turnover' criterion data structure

XML Example

Specific average turnover

<!--... header elements removed for brevity... -->

<!-- Criterion:Specific average turnover -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d3dfb714-f558-4512-bbc5-e456fa2339de</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">spec-aver-to</cbc:CriterionTypeCode>
                <cbc:Name>Specific average turnover</cbc:Name>
                <cbc:Description>Its specific average yearly turnover in the business area covered by the contract for the number of years required in the relevant notice, the in the ESPD, the relevant notice or or the ESPD is as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8b592e5b-628c-4d4c-898e-331caaf91807</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">47fc8823-5261-4068-afbf-addcb135844d</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">13545b12-7b5a-4e7b-897b-10724ec2fac5</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6cff132b-8d15-4f79-ae37-2f9295432381</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9203d764-a7d0-4f9e-acea-b23088f97886</cbc:ID>
                                <cbc:Description>Number of fiscal years</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority -->
                                <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">06b53773-3e55-42cb-be93-3e2e1b1bbc08</cbc:ID>
                                <cbc:Description>Business domain description</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority -->
                                <cbc:ExpectedDescription>e.g. "IT consulting / development of semantic interoperability solutions"</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5691a269-085a-47f7-8581-4a5021ed4800</cbc:ID>
                                <cbc:Description>Minimum requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority -->
                                <cbc:ExpectedAmount currencyID="EUR">1000000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ce4ee424-ec04-42b7-9592-e5651c502cbe</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">eaffc968-dae3-4faa-837b-381f827208e2</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">aa7c166e-eb10-4a3a-8d62-e8c557139d5e</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">32e0f960-7886-4ccc-bc27-eb688138343d</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5ecb6e8e-e493-499b-a827-7fe5193b6886</cbc:ID>
                                        <cbc:Description>Start date; End date</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c13e60a7-8b48-48c8-8061-4b4b03346066</cbc:ID>
                                        <cbc:Description>Amount</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5a980465-09db-4d0b-8c7a-31fb16a4feab</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">61fa383a-c290-48fa-b288-649a22ddf722</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fd5e5e16-2073-46a8-8733-9902bb9834ce</cbc:ID>
                                        <cbc:Description>In case the information concerning turnover (general or specific) is not available for the entire period required, please state the date on which the economic operator was set up or started trading:</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9bd18524-59a6-4c45-82c6-4ad4e2437d45</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">53dac1dd-495d-40b3-b4cb-43a3686f279b</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->

5.5. Financial ratios

See formal requirements related to 'Turnover' criteria ESPD in the BIS 41 - European Single Procurement Document (Version 2.0.0), and more specifically the requirement tbr070-013

REQUIREMENT

The buyer must use the BACH Banque France Code List for the specification of financial ratios.

Mock-ups - buyer perspective

'Financial ratio' buyer mock-up

The buyer has selected the financial ratio as one of the selection criteria that will go into the ESPD Request document:

Financial ratio

In ESPD the buyer specifies procurement procedure-specific requirements, see data structure below.

Mock-up - economic operator perspective

The economic operator does only have to provide the numeric value for the financial ratio (which should be greater than the minimum requirement specified by the buyer ):

Financial ratio

Figure 135. 'Financial ratio' EO mock-up

Data Structure

REQUIREMENT(s) specified by the buyers can be place outside a group of QUESTION(s) (see any other previous criteria) or inside a group of QUESTION(s), which is the case for financial ratios, as you can see in the data structure for this criterion, below.

Notice how the spreadsheet has been used to specify the three different financial ratios of the above mock-up example: the XML example below was produced using a XSL-T transformation ESPDRequest-Annotated that takes the ESPD-criterion and produced the ESPD-Request.

Financial ratio

Figure 136. 'Financial ratio' criterion data structure

XML Example

Financial Ratio

<!--... header elements removed for brevity... -->

<!-- Criterion:Financial ratio -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e4d37adc-08cd-4f4d-a8d8-32b62b0a1f46</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">finan-rat</cbc:CriterionTypeCode>
                <cbc:Name>Financial ratio</cbc:Name>
                <cbc:Description>Concerning the financial ratios specified in the relevant notice, the in the ESPD, the relevant notice or or the ESPD, the economic operator declares that the actual values for the required ratios are as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">387118be-f732-49f2-982a-5bdb4d9e52ff</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cc1da737-6c4e-4f4e-821d-c260029058f6</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">889620da-979a-4ce9-b4a7-aaa8aef09066</cbc:ID>
                                <cbc:Description>Select the periods applicable for all ratios</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cac:ApplicablePeriod>
                                        <cbc:StartDate>2016-01-01</cbc:StartDate>
                                        <cbc:EndDate>2016-01-01</cbc:EndDate>
                                </cac:ApplicablePeriod>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ee486082-93fa-4c17-8920-fdf01b890bd1</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">96df5f9f-f458-40cf-818f-a2beade58b1a</cbc:ID>
                                        <cbc:Description>Ratio Type</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CODE</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedCode listID="PleaseSelectTheCorrectOne" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">Assets to equity ratio</cbc:ExpectedCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1649c3aa-db0b-40cc-adb0-561f13531cf5</cbc:ID>
                                        <cbc:Description>Definition</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedDescription>Total balance sheet/Total equity</cbc:ExpectedDescription>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b5d47ff0-f82b-4818-9e2e-88d2c133544d</cbc:ID>
                                        <cbc:Description>Minimum requirement</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedValueNumeric>0.5</cbc:ExpectedValueNumeric>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6234d4cc-1936-4e1c-9d87-0bcd7f01cd7c</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f1aec98d-5991-4119-9ffd-a95486a7ce68</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">99a61ff5-addf-41b3-9e89-55b576e1b35d</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">104cc794-cb50-4387-bbad-b64c0d5d3c26</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a8c29eb0-9a60-4e7f-9685-41195e02fc99</cbc:ID>
                                        <cbc:Description>Please provide your ratio</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8d06c2c6-8353-499a-8390-e676771008c0</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">77cbefd5-6683-41da-8c25-19bfbf2b5f4b</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->
  1. The period applicable for all the ratios required by the buyer . This applies to the three ratios required in the example (see mock-up above).

  2. First financial ratio block: the particular ratio required by the buyer is expressed as a code defined by BACH (See CodeList "FinancialRatioType").

  3. First financial ratio block: the description of the ratio is the one provided by BACH and should be captured from the CodeList "FinancialRatioType", which in turn is should be directly form the BACH web-site.

  4. First financial ratio block: a threshold established by the buyer as minimum requirement; the ratio provided by the economic operator shall be greater or equal to this minimum numeric value.

  5. Second financial ratio block: type code required by the buyer according to the example illustrated in the mock-up above (the buyer may require several financial ratios; notice that the cardinality of this sub-group in the data structure and the mock-up is 1..n). The content of this block, and of the following one, have been removed for brevity, but they are similar to the first block, except that the value of the code, description and minimum requirement shall be different.

  6. Second financial ratio block: ratio definition.

  7. Second financial ratio block: minimum requirement.

  8. Third financial ratio block: ratio type required by the buyer according to the example illustrated in the mock-up above.

  9. Third financial ratio block: ratio definition.

  10. Third financial ratio block: minimum requirement.

  11. First financial ratio block: the Criterion Property used to refer to the response by the economic operator. In the ESPD Response document, the ID of this Criterion Property will be used by the element cac:ValidatedCriterionPropertyID as the means to link the response to the question. See section "Answering Questions" (under ESPD Response) for more details on this.

  12. Block "Is this information available electronically". This block is constant for all criteria. It has been removed from the example for brevity. See other XML examples.

5.6. Risk indemnity insurance

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

The only criterion defined under this data structure is classified with the code:

  • indem-ins

Mock-ups - buyer perspective

The buyer has selected the option professional risk indemnity insurance for its inclusion in the ESPD Request. Additionally the buyer can specify REQUIREMENT(s) specific to the procurement procedure. There are two situations that need to be distinguished here, when the procurement procedure is divided into Lots and when it is not.

For both situations (Lots and Lot): The buyer can require data from the economic operator in relation to up to four types of insurances. Software applications should control that: no more groups of amount an currency data are presented to the economic operator; and that there are not two amounts referring to the same type of insurance;

Risk indemnity insurance

Figure 140. 'Risk indemnity insurance' Buyer REQUIREMENT(s) edition (Procedure with no lots, which actually means 1 Lot)

When the procedure is divided into Lots: The buyer can specify the Lots one particular insurance applies to.

Risk indemnity insurance' Buyer REQUIREMENT(s) edition (Procedure with more than one Lot)

Figure 141. 'Risk indemnity insurance' Buyer REQUIREMENT(s) edition (Procedure with more than one Lot).

Mock-up - economic operator perspective

The only data the economic operator needs to provide is the amount covered by the insurance and the currency for that amount:

Economic operator indemnity insurance

Figure 142. 'Economic operator indemnity insurance' EO mock-up

Note that the EO should provide an answer (ESPD Response) for every Lot that tenders. Meaning that if the Selection Criteria applies to different Lots (as can be read in the mockup), the EO should sumbit the data for the number of lots that apply.

Data Structure

This structure is quite particular. Notice that:

  1. Multiple national sub-criteria can be defined (as for the rest of criteria); and additionally

  2. Multiple groups of REQUIREMENT(s) and QUESTION(s) can be defined by the buyer :

    • An additional sub-group for the type of insurance and the minimum amount required by the CA.

    • A sub-group of three QUESTION(s) for the economic operator to answer (amount, and two questions to be answered as "Yes" or "No"; and

    • The possibility of attaching an evidence per each insurance.

The XML example below illustrates all this. The values used in the example are the same as the ones in the spread-sheet.

risk indemnity insurance' criterion data structure

Figure 143. 'risk indemnity insurance' criterion data structure

XML Example

'Risk indemnity insurance' criterion (Procedure with Lots)

<!... header elements removed for brevity -->

 <!-- Criterion:Professional risk indemnity insurance -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7604bd40-4462-4086-8763-a50da51a869c</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">indem-insu</cbc:CriterionTypeCode>
                <cbc:Name>Professional risk indemnity insurance</cbc:Name>
                <cbc:Description>The insured amount in its professional risk indemnity insurance is the following:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7c7c04a7-6975-4de2-872c-90b303745eaa</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4b299dd0-02f0-4360-bb44-c4457a3a859e</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d8d5b26e-239e-4cc2-9ac7-244dea49397b</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">83e3dcc4-c9b3-47e5-9fb8-ffd8386679f1</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c6b76697-ef10-401a-8707-b5e00d288bd7</cbc:ID>
                                <cbc:Description>Type of insurance</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>[Description of the type of insurance]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a1155e6d-3e8f-4fe4-803a-f754b56dfde7</cbc:ID>
                                <cbc:Description>Minimum amount</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedAmount currencyID="EUR">50000</cbc:ExpectedAmount>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9ec9f970-67b3-4bff-9f3b-c1fc5f7bcd4b</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">dbb1d777-035b-4416-a44d-8784f24f0f4a</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">87f5c345-0da9-4b69-9b08-d0f944ef5be8</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fcf81003-4f49-4ac4-96c1-b168803e0ced</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">42dc8062-974d-4201-91ba-7f2ea90338fd</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e39f4a01-e593-49a0-b771-d6a5dbd6e2f2</cbc:ID>
                                        <cbc:Description>Amount</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e2610238-0ced-470d-9f8d-90cc5ab62bf1</cbc:ID>
                                        <cbc:Description>As an EO I will commit to obtain the minimum amount required</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">095f0646-cd60-4833-b8ee-3df16daa66c3</cbc:ID>
                                        <cbc:Description>I am exempt</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">96c40e5c-c969-4776-8176-98bb76e70f2e</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d2713efc-f0a6-4a7c-909e-8782a98ad7c2</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!--... rest of elements removed for brevity... -->

5.7. Other economic or financial requirements

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

The only criterion defined is classified with the code:

  • finan-requ

Buyer perspective

The buyer has selected the option other economic or financial requirements for its inclusion in the ESPD Request.

Additionally the buyer can specify REQUIREMENT(s) specific to the procurement procedure. There are two situations that need to be distinguished here, when the procurement procedure is divided into Lots and when it is not.

Thus, for this criterion the buyer will be able to:

  1. Either add multiple requirements. For each requirement, the Buyer will need to provide the description of the requirement, the minimum amount and currency and the start and end date; or it will need to provide the minimum rating and the rating schema.

  2. In the ESPDResponse, the EO will be required to provide, for each requirement, the amount and currency.

  3. When the procedure includes more than one Lot: The buyer can specify the Lots the criteria applies to.

Notice that in the mock-up below the first requirement is about an economic of financial requirement whilst the second requirement is about a rating requirement. See data structure and XML example for more details on this distiction.

Mock-up - economic operator perspective

The economic operator, in its view, sees all the requirements defined by the buyer and responds to this requirements with an amount and currency. See XML example below to identify where these data are placed in the XML instance.

Other economic or financial requirements

Figure 148. 'Other economic or financial requirements' EO mock-up

Note that the EO should provide an answer (ESPD Response) for every Lot that tenders. Meaning that if the Selection Criteria applies to different Lots (as can be read in the mockup), the EO should sumbit the data for the number of lots that apply.

Data Structure

Notice the following aspects from the 'other economic or financial requirements':

  1. It allows for capturing multiple national criteria;

  2. It specifies the Legislation component for the EU parent criterion. So far so good, no differences until now;

  3. There’s a group of REQUIREMENT(s) and QUESTION(s).

  4. The group of REQUIREMENT(s) defines a caption that is kep empty (no name, no description, no value. You will have noticed this also in other criteria. The reason for having this dummy CAPTION is that the UBL-2.3 model requires always at least one cac:TenderingCriterionProperty element instance inside a group or sub-group of properties;

  5. The most important part comes now: You have a kind of choice here: one of the two subgroups the data will be shown (or not) depending on the answer of the buyer * to the REQUIREMENT: *Select the type of requirement. If the CA’s answer was economic or financial requirement the application takes it as a true; otherwise it is considered false:

    • On true (see the group code on the right side of the data structure) three REQUIREMENT(s) will be shown to the economic operator: description, minimum amount and period. For this REQUIREMENT the economic operator will see all these requirements and will have to provide an amount.

    • On false (see the group code on the right side of the data structure) three REQUIREMENT(s) will be shown to the economic operator: minimum rating and rating scheme. For this REQUIREMENT the economic operator will see all these requirements and will have to provide a rating.

Other economic or financial requirements

Figure 149. 'Other economic or financial requirements' criterion data structure

XML Example

'Other economic or financial requirements' criterion

<!-- ... header elements removed for brevity ... -->

<!-- Criterion:Other economic or financial requirements -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ab0e7f2e-6418-40e2-8870-6713123e41ad</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">finan-requ</cbc:CriterionTypeCode>
                <cbc:Name>Other economic or financial requirements</cbc:Name>
                <cbc:Description>Concerning the other economic or financial requirements, if any, that may have been specified in the relevant notice or in the ESPD, the economic operator declares that:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">183ffa32-4222-4aee-8d56-f94a4e88c09b</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe442288-267f-4151-a8fe-c3582ba8723f</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0eb7f3ad-0f05-49c7-9dc7-51def9444679</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4ddccd16-91e4-4b72-ae0f-78f2f1ab9490</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">77b68ed2-4c20-4b0d-9e06-e09baf8ca5f7</cbc:ID>
                                <cbc:Description/>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">26ece6a2-b360-46c1-890d-8338913b8719</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">977149e9-9a91-4aa6-acb6-6928a0dd6609</cbc:ID>
                                        <cbc:Description>Select the type of requirement</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CODE_BOOLEAN</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedCode listID="BooleanGUIControlType" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">RADIO_BUTTON_TRUE</cbc:ExpectedCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ca15c15f-110e-4a10-8d6e-5e41cf5f9098</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4d879427-f3e8-431b-a516-1c0f22edd56a</cbc:ID>
                                                <cbc:Description>Description of the economic or financial requirement</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cbc:ExpectedDescription>[Description]</cbc:ExpectedDescription>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">dc0e4df7-166d-49c0-b2bf-461c870a0f30</cbc:ID>
                                                <cbc:Description>Minimum amount</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cbc:ExpectedAmount currencyID="EUR"
                                                  >100000</cbc:ExpectedAmount>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">77094dbc-28ea-43ce-b984-2bc1fd0e0484</cbc:ID>
                                                <cbc:Description>Start date; End date</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cac:ApplicablePeriod>
                                                  <cbc:StartDate>2016-01-01</cbc:StartDate>
                                                  <cbc:EndDate>2016-01-01</cbc:EndDate>
                                                </cac:ApplicablePeriod>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9b3a04ff-e36d-4d4f-b47c-82ad402b9b02</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">01e45356-eaea-48ab-9cfa-e580ce9d00b0</cbc:ID>
                                                  <cbc:Description>Amount</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cc96aa19-a0be-4409-af58-ff3f3812741b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d996223a-3f54-4803-bf05-39019c843e94</cbc:ID>
                                                <cbc:Description>Minimum rating</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cbc:ExpectedValueNumeric>0.33</cbc:ExpectedValueNumeric>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">864e1a59-d53f-4810-b8f5-ab701b90972f</cbc:ID>
                                                <cbc:Description>Rating scheme</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cbc:ExpectedDescription>n/10, where n&lt;=10</cbc:ExpectedDescription>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5fe93344-ed91-4f97-bcab-b6720a131798</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d40e05a3-5a2b-4743-8cbf-935176fbeff4</cbc:ID>
                                                  <cbc:Description>Rating</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">106705b8-e981-45c1-9fb9-f6014fd6fedb</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fb63482a-83ae-42bb-9730-ec2874f06604</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... rest of elements removed for brevity ... -->

5.8. References on similar works, deliveries or services

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

There are three criteria with the same data structure (works, supplies and services references):

  • qa-certif-inst

  • qu-certif-indep

  • envir-certif-indep

Difference between 'total amount' and 'specific amount' in a reference

The total amount refers to the amount of the contract, the specific refers to the amount of the contract a concrete reference is linked to. Two examples could be:

  1. A contract for the acquisition of printers (Lot1) and the maintenance of the printers (Lot2). Your reference is about the maintenance only. Total amount: 1,000,000 € (Lot1 + Lot 2). Specific amount: 700,000.00 (Lot2, maintenance).

  2. Building of a bridge. Total amount: 20,000,000 €. The reference is only about the asphalt provided for the bridge: specific amount 1,351,145.89 €.

Mock-ups - buyer perspective

As in the previous example, in this example about the references the buyer requires references for the contract, the nature of which is also about works.

For the ESPD, the buyer can specify these REQUIREMENT(s):

  1. The minimum number of references expected;

  2. One or more specific requirements in the form of free-texts (notice the buttons to add or remove the requirements.

References' buyer REQUIREMENT(s) edition mock-up

Figure 153. 'References' buyer REQUIREMENT(s) edition mock-up

Mock-ups - economic operator perspective

  1. In this view for the economic operator (EO) can see the lots and requirements specified by the buyer (CA), lower left side of the mock-up.

  2. The EO can also list those Lots it tenders to that apply to the particular reference it is providing. Software applications should validate that the Lots supplied by the EO for a reference are in the range of those specified by the buyer.

  3. The EO can provide a description for the reference, the total amount of the contract in which the reference was included, the amount for the specific works referenced, the period of execution and one or more groups of data about the recipients (name/description, contact person name and contact e-mail).

  4. The EO can also state that one reference is confidential, in which case the reference will only be accessible to the evaluation team.

References' EO mock-up

Figure 154. 'References' EO mock-up

Non-validation of text content

NOTICE that the EO has made a mistake and for a "Works contracts: performance of works for the specified type" it is describing a Service. The Schematron-based validation solution cannot validate this situation as the description is a textual value.

For details on the Schematron-based validation solution see section 7. Validation.

Data Structure

The data structure for references caters for:

  1. The definition of multiple national criteria associated to the EU criterion specified in e-Certis;

  2. The creation of the Legislation component associated to the EU criterion;

  3. One group of REQUIREMENT(s) for the buyer to specify the general requirements for this criterion (e.g. Lots the references apply to, minimun number of references);

  4. Multiple groups (cardinality 1..n) of questions for the economic operator to answer; which in this case are multiple references to works about which the EO has to provide information and the lots the EO tenders to related to the references.

References

Figure 155.'References' criterion data structure

XML Example

'References for a works contract' criterion

<!--... header elements removed for brevity... -->

<!-- Criterion:For supply contracts: performance of deliveries of the specified type -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3a18a175-1863-4b1d-baef-588ce61960ca</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">supply-perform</cbc:CriterionTypeCode>
                <cbc:Name>For supply contracts: performance of deliveries of the specified type</cbc:Name>
                <cbc:Description>For public supply contracts only: During the reference period, the economic operator has delivered the following principal deliveries of the type specified. Contracting authorities may require up to three years and allow experience dating from more than three years.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b2a38518-42cb-48a3-a4b8-3cae396fbb24</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f770c131-6aeb-4a72-bbb5-2ea29592d707</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9c3887a4-a6d8-49e1-bc97-97b3fc8f1dff</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">381bea15-9460-49f7-a6d0-15d13059de29</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f29df27e-85ea-4da1-b9f5-c48b997a3b67</cbc:ID>
                                <cbc:Description>Minimum number of references</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6a9db029-0bdd-44dd-96dc-8f30b2203bf1</cbc:ID>
                                        <cbc:Description/>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d663aca5-5f3c-4980-b825-81e1bd7db381</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8d818131-465c-4c51-a6f3-4bd295549983</cbc:ID>
                                                <cbc:Description>Requirement</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                                <cbc:ExpectedDescription>The references provided need to refer to good supplied in more than one EU Member States.</cbc:ExpectedDescription>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a44e24e9-f878-4651-9ead-e0b1387dae09</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">71a8b493-0a70-4823-a043-b5f245b89af5</cbc:ID>
                                        <cbc:Description/>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c8ec5c30-2c17-4936-abbb-392523d873e5</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">60084d4a-33ab-43c2-850b-cb975995da4f</cbc:ID>
                                                <cbc:Description>Reference description</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1ea03e22-d51d-4224-aaf7-c8e673f49dbf</cbc:ID>
                                                <cbc:Description>Total amount</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c11d9ccf-97e2-4ddd-8961-840794c4bc8b</cbc:ID>
                                                <cbc:Description>Activity of the economic operator</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">25c464f5-17e9-488e-9820-81213e20845c</cbc:ID>
                                                <cbc:Description>Specific amount</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">AMOUNT</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d337a41c-2030-4126-b194-296ebffa6eeb</cbc:ID>
                                                <cbc:Description>Period (Start and End dates)</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">PERIOD</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">73b1b8e2-164e-4656-9791-1f76ba7e325e</cbc:ID>
                                                <cbc:Description>Confidential</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6afa7569-e4c4-4538-be89-84a82b2a301b</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3e72b656-00dc-4135-91e6-792bdc33debd</cbc:ID>
                                                  <cbc:Description>Recipient name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9576259a-f5bf-423f-9642-4fb4fda03ea3</cbc:ID>
                                                  <cbc:Description>Contact person name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bc804c82-f03a-4f21-8e19-3788f809e1e0</cbc:ID>
                                                  <cbc:Description>Contact email</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f8ca97d2-7053-47c8-811c-8d20f1620e62</cbc:ID>
                                                  <cbc:Description>Contact telephone</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a2ed0e66-9056-42dc-9047-799f9806f241</cbc:ID>
                                                  <cbc:Description>Is this information available online?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4b18ffc5-fb9d-428c-aa25-823486de5269</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

The following elements can be read in the example:

  1. The description of the Criterion.

  2. The minimum number of references expected by the buyer (minimum one, in this example).

  3. Additional REQUIREMENT expressed by the buyer that apply for the affected Lots: Specific amount greater than a certain amount.

  4. Additional REQUIREMENT expressed by the buyer that apply for the affected Lots: Executed recently.

  5. The Lots for which the Reference makes sense. Notice that the response of the EO is consistent, as the procedure is divided into 2 Lots.

  6. The description of the work executed.

  7. The Total Amount of the Reference, including the amounts that were specific to (share of) other EOs participating in the execution of the work. Notice that the attribute currencyID is set to "EUR".

  8. The activity of this economic operator in this work.

  9. The amount specific to the contribution of this EO in this Reference. Notice that the specific and the total amounts are identical. The EO proabably executed the work alone, as a sole contractor.

  10. Duration of the execution of the work.

  11. The level of confidentiality of the information regarding this Reference. Confidential references provided by the EO cannot be made accessible by the buyer to third parties.

  12. The name of the recipient of the work.

  13. Name of the contact point, a person in this case.

  14. Contact e-mail of the recipient of the work.

5.9. Abilities

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

The ESPD, supplies data structures facilitating a greater semantic interoperability:

  • One data structure to define two ability criteria related to technicians:

    • Technicians or technical bodies for quality control (qual-cont-tech)

    • For works contracts: technicians or technical bodies to carry out the work (work-tech)

  • One data structure to define a miscellania of five criteria that can share the same data structure:

    • Technical facilities and measures for ensuring quality (qual-facil)

    • Study and research facilities (research-fac)

    • Supply chain management (chain-manage)

    • Environmental management measures (envir-measure)

    • Tools, plant or technical equipment (tech-equip)

  • One data structure to define abilities related to the education and professional qualifications of the contractor or service provider:

    • Educational and professional qualifications (qualification)

And one more data structure to define the allowance of checks: * Special requierements check (spec-req-check)

  • One data structure to define two abilities related to the contractor’s staff:

    • Number of managerial staff (manage-staff)

    • Average annual manpower (year-manpower)

Abilities (I) - Persons

Note that in this version of ESPD there are not weights to keep the model as simple as possible.

Mock-ups - buyer perspective

Abilities (I)

Figure 165. 'Abilities (I)' buyer REQUIREMENT edition mock-up

Mock-ups - economic operator perspective

As you see from the mock-up below the economic operator can add and remove technicians and bodies associated to one CA’s REQUIREMENT. In this case the REQUIREMENT specified by the buyer is the type of technical assistance the EO’s teams must provide.

Abilities (I)

Figure 166. 'Abilities (I)' EO mock-up

Data Structure

(The figure below is defined in the the tab ''SC-Abilities_1 (Persons)'' of the ESPD-criterion spread-sheet).

Abilities (I)(Persons)

Figure 169. 'Abilities (I)(Persons)' criterion data structure

XML Example

The XML example below shows the REQUIREMENT(s) and QUESTION(s).

<!-- Criterion:Technicians or technical bodies for quality control -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3aaca389-4a7b-406b-a4b9-080845d127e7</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">qual-cont-tech</cbc:CriterionTypeCode>
                <cbc:Name>Technicians or technical bodies for quality control</cbc:Name>
                <cbc:Description>It can call upon the following technicians or technical bodies, especially those responsible for quality control. For technicians or technical bodies not belonging directly to the economic operator's undertaking but on whose capacities the economic operator relies as set out under Part II, Section C, separate ESPD forms must be filled in.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5b38f9d4-d1b5-4f36-b63b-833de7099cc0</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a87e1684-0612-48d6-9b38-a98e264a8d62</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e49b982a-549b-4830-abf8-df9986a924f9</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b2c35259-1991-43df-99e4-71f3517e66a8</cbc:ID>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0fe56fac-ad7e-4eb6-ba99-3eb3c19387c9</cbc:ID>
                                        <cbc:Description>Requirement</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedDescription>Technical User Support Group</cbc:ExpectedDescription>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d0771d9b-8190-4eef-84dd-4e0fa4e333e4</cbc:ID>
                                                <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">422cb36d-bbad-4140-9b60-c5e949752c7a</cbc:ID>
                                                  <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">47d18d32-940c-43dd-8331-347991f3e370</cbc:ID>
                                                  <cbc:Description>Name of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fb74c664-ad0f-448f-acde-3e856cf8e6ed</cbc:ID>
                                                  <cbc:Description>ID of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
										</cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">609cc954-64be-4b4f-800a-f17589deb936</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1e673510-a513-4294-80cd-718286205ca6</cbc:ID>
                                                <cbc:Description/>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7b896077-8997-4c4c-92f8-dd1a02fafe8f</cbc:ID>
                                                  <cbc:Description>First name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">25d62956-ec36-4d48-b7cb-3abfddb10033</cbc:ID>
                                                  <cbc:Description>Last name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5d48d39d-adc1-40ba-8eb7-8a2223d238c0</cbc:ID>
                                                  <cbc:Description>Profession</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">49d2f8d7-4108-4b97-9763-7d38ae86d2b0</cbc:ID>
                                                  <cbc:Description>Experience</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d6aa0ae2-09d1-429a-b415-0b3beccfad57</cbc:ID>
                                                  <cbc:Description>Other information</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6ba019e7-3d0a-4556-90a5-1e2975a9775b</cbc:ID>
                                                  <cbc:Description>How long with EO</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c5ed5aba-2cf0-498a-9c01-6a497520feca</cbc:ID>
                                                  <cbc:Description>Is this information available online?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bb8e1767-c951-43ea-b307-6665e59eb414</cbc:ID>
                                                  <cbc:Description>Evidence supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">45a67f48-d146-4faf-8239-dd6977dffe29</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">13c87b8b-9c5c-48c7-a6c9-02556c693400</cbc:ID>
                                                <cbc:Description/>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">97002d8c-a92e-4a4e-a9ea-765e41de8923</cbc:ID>
                                                  <cbc:Description>Name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e0a6c75d-1188-459a-9584-4c558e9cf9aa</cbc:ID>
                                                  <cbc:Description>Experience area</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">985ebee5-f6d7-470d-a6ee-1c4d855d4494</cbc:ID>
                                                  <cbc:Description>Other information</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">225c7eff-319d-48af-b716-0cc56eac5f93</cbc:ID>
                                                  <cbc:Description>Is this information available online?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f67b87ad-e832-48d3-bc69-347ac0d8ff1b</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

Abilities (II) - Facilities

Data Structure

(The figure below is defined in the the tab ''SC_Abilities_2 (Facilities,…​)'' of the ESPD-criterion spread-sheet).

Abilities (II) (Facilities, …​.)

Figure 170. 'Abilities (II) (Facilities, …​.)' criterion data structure

XML Example

Criterion "Technical facilities and measures for ensuring quality" (ESPD-Request)

<!-- Header elements removed for brevity -->

<!--This criterion illustrates how to prepare a selection criterion about ''abilities'', more specifically the criterion ''Technical facilities and measures for ensuring quality''.-->

<!-- Criterion:Technical facilities and measures for ensuring quality -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4bf996d9-439c-40c6-9ab9-980a48cb55a1</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">qual-facil</cbc:CriterionTypeCode>
                <cbc:Name>Technical facilities and measures for ensuring quality</cbc:Name>
                <cbc:Description>It uses the following technical facilities and measures for ensuring quality and its study and research facilities are as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0710de58-4a89-4101-a178-912e44b075c5</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">72f660ff-8fc2-49e3-875e-d5b981d869de</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bbd08f12-e686-4695-bfef-85ebf731f424</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">dde661c3-007f-4931-b830-541a3086f864</cbc:ID>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3015f927-7654-48a2-8e8c-686d4d4c8e4f</cbc:ID>
                                        <cbc:Description>Requirement</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedDescription>[Requirement text]</cbc:ExpectedDescription>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d4611288-307a-452c-803f-4668ab69e045</cbc:ID>
                                                <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c93e53e7-5557-470c-99e6-f2ee9cf5cb41</cbc:ID>
                                                  <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3f406bba-d2d1-41f5-b37d-7cf1f2d0a734</cbc:ID>
                                                  <cbc:Description>Name of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">07a334f3-e4e5-47ba-b7a8-182cb0fec6e8</cbc:ID>
                                                  <cbc:Description>ID of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
										</cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">488ca189-bcdb-4bf4-80c7-3ad507fd89fb</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cb4afaf5-4c8c-407d-811b-d5c1894efa94</cbc:ID>
                                                <cbc:Description>Please describe them</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cf928f06-c558-49e5-bee0-a9be3ac77edb</cbc:ID>
                                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9698606c-b31e-444f-b9a5-e863343dd500</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- Rest of elements removed for brevity -->

Abilities (III) - Education

Data Structure

(The figure below is defined in the the tab ''SC_Abilities_3 (Education)'' of the ESPD-criterion spread-sheet).

Abilities (III) (Education)' criterion data structure

Figure 171. 'Abilities (III) (Education)' criterion data structure

Use of the EC’s ESCO Taxonomy for Skills, Competences and Occupations (and Qualifications)

Notice that in the Data Structure above there is the field ''If possible please indicate the ESCO identifier for this qualification'', and that the expected type of data is 'URL'.

ESCO is a multilingual classification that identifies and categorises skills, competences, qualifications and occupations relevant for the EU labour market and education. It is being developed (maintained) by the European Commission since 2010. The taxonomy can be downloaded from this link.

The reason why the expected type of data is a URL is because in ESCO taxonomy each concept is identified with a URI (A Uniform Resource Identifier, and URI can be used as locators, i.e. URL are URIs).

ESCO is legally supported by the REGULATION (EU) 2016/589 of 13 April 2016 (the EURES Regulation) and two Implementing Decisions:

  • Commission Implementing Decision No 2018/1020 establishes the list of skills, competences and occupations of the European classification (ESCO) to be used for the operation of the EURES common IT platform as provided for in Article 19 of Regulation (EU) 2016/589 and lays down the procedures to update and review this list.

  • Commission Implementing Decision No 2018/1021 lays down the technical standards and formats necessary for the operation of the automated matching through the common IT platform using the European classification (ESCO) and the interoperability between national systems and the European classification.

XML Example

Criterion "Educational and professional qualifications" ESPD-Request)

<!-- This criterion illustrates how to prepare a selection criterion about ''abilities'', more specifically the criterion ''Educational and professional qualifications'' -->

<!-- The rest of criteria above and below this criterion have been removed for brevity. -->

<!-- Criterion:Educational and professional qualifications -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">07301031-2270-41af-8e7e-66fe0c777107</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">qualification</cbc:CriterionTypeCode>
                <cbc:Name>Educational and professional qualifications</cbc:Name>
                <cbc:Description>The following educational and professional qualifications are held by the service provider or the contractor itself, and/or (depending on the requirements set out in the relevant notice or the in the ESPD, the relevant notice or by its managerial staff.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">de86ae93-3693-4271-bb7f-903b68785dba</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d627cbd0-857d-4e71-bfe2-37aa3a192690</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f7205b02-54b1-4df8-86ae-33c1797a7025</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d2cadc29-07e0-46b2-a74a-a0dc4bd2e5c2</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bce9cda1-9041-4d7d-91ca-3ebe907583bd</cbc:ID>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1be6421a-0360-449e-ae7c-ce7fad73c2c2</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">81272bf3-615d-4327-be36-39777540f67a</cbc:ID>
                                        <cbc:Description>Requirement</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                        <cbc:ExpectedDescription/>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b899ae90-d94b-41c0-a1ea-e4754dd769e3</cbc:ID>
                                                <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">b7f2eeab-5185-4da6-a332-3879aa291d5c</cbc:ID>
                                                  <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bca69988-1b3a-4359-84e0-f5f5046ff591</cbc:ID>
                                                  <cbc:Description>Name of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">33949ea8-4a29-484f-8c1a-d35ef7a8b77c</cbc:ID>
                                                  <cbc:Description>ID of the entity</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
										</cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5df40500-a9b7-4c15-8325-a9762224a3c9</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">87466874-a4f7-4593-a910-5d45bfdcc92c</cbc:ID>
                                                <cbc:Description/>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5476ec64-de1e-45d2-aaf1-a40a463ab7a9</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a1fcac6e-cfcf-4562-86a8-7947221a0690</cbc:ID>
                                                  <cbc:Description>First name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ee554b00-8adf-4d44-8b8a-867374b48e3a</cbc:ID>
                                                  <cbc:Description>Last name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a80fc83a-97e9-4044-82f1-1612a64481f4</cbc:ID>
                                                  <cbc:Description>Please describe the educational or professional qualification</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">12bb0e91-ea89-4938-8a45-c6a758c06abf</cbc:ID>
                                                  <cbc:Description>If possible please indicate the ESCO identifier for this qualification</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">URL</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c9ff2a1d-493c-4e21-a361-b9e659459ed9</cbc:ID>
                                                  <cbc:Description>If possible please describe the ESCO qualification</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">34169879-f479-4b8f-b449-d7696631805b</cbc:ID>
                                                  <cbc:Description>Qualification name</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">766a57ce-3e96-4fda-a03a-135b97310326</cbc:ID>
                                                  <cbc:Description>Qualification number</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUAL_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3227540b-9d5f-4625-92cc-2d0979f0c020</cbc:ID>
                                                  <cbc:Description>Qualification issuing date</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DATE</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">65f0d094-f627-4bc0-8ee5-35c8781e9ab8</cbc:ID>
                                                  <cbc:Description>Qualification issuing body</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">758c9614-b909-4e7e-b41a-75d8a7341982</cbc:ID>
                                                  <cbc:Description>Is this information available online?</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                                                  <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                  <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4fed6953-5ee8-4ac7-b963-9475cbf48738</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                  </cac:TenderingCriterionProperty>
                                                  </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

Abilities (IV) - Checks

Mock-ups - buyer perspective

The buyer has selected the 'allowance of checks' (in ESPD-criterion will be shown as "Special requierements check", spec-req-check) option in a ESPD Request builder software application GUI. This software application will create a criterion of this in the ESPD Request XML instance with zero, one or more REQUIREMENT(s) by the EO.

The buyer (CA) can specify none, one or several REQUIREMENT(s). In this case a REQUIREMENT is a descriptive text provided by the buyer where the criterion is better explained or where certain conditions relating to the criterion. In this example the buyer is specifying which type of premises it wants to check and for which reasons.

Checks

Figure 172. Special requierements check buyer REQUIREMENT edition mock-up

Mock-ups - economic operator perspective

The EO should see as many boxes (groups) of REQUIREMENT + QUESTION as REQUIREMENT(s) specified by the CA. In this case the economic operator (EO) sees one REQUIREMENT associated to one QUESTION. The expected answer is Yes or No.

Special requierements check' EO mock-up

Figure 173. 'Special requierements check' EO mock-up

Data Structure

The data structure below shows how this criterion is organised. Notice the following:

  1. The Member State can associate one or more national criteria to this EU criterion (element sub-criterion, cardinality 0..n).

  2. The criterion can be associated to one or more pieces of legislation (this spread-sheet does not focus on the edition of the legislation element; the transformation style-sheet will generate dummy values for this element).

  3. At least one REQUIREMENT group will always be created. If the buyer specified more than one REQUIREMENT(s), more groups of REQUIREMENT + QUESTION would be added to the ESPD Request XML instance.

  4. If not specific REQUIREMENT is issued by the CA, the REQUIREMENT group should equally be created and the REQUIREMENT value should be replaced with a literal (e.g. 'No specific requirements').

(Some columns have been hidden to enhance the readability of the image).

(The figure below is defined in the the tab 'SC_Abilities_4 (Checks)' of the ESPD-criterion spread-sheet).

Abilities (IV) (Checks)

Figure 174. 'Abilities (IV) (Checks)' criterion data structure

XML Example

Allowance of checks criterion /Special requierements check

<!-- header elements removed for brevity -->

<!-- Criterion:Special requierements check -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c8809aa1-29b6-4f27-ae2f-27e612e394db</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">spec-req-check</cbc:CriterionTypeCode>
                <cbc:Name>Special requierements check</cbc:Name>
                <cbc:Description>For complex products or services to be supplied or, exceptionally, for products or services which are required for a special purpose: The economic operator will allow checks to be conducted on the production capacities or the technical capacity of the economic operator and, where necessary, on the means of study and research which are available to it and on the quality control measures? The check is to be performed by the contracting authority or, in case the latter consents to this, on its behalf by a competent official body of the country in which the supplier or service provider is established.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">008b9830-d292-46e4-8af2-284aa5c7f5ff</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">52a23c13-140b-4671-be70-65bd8e259291</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">dfc636dc-a817-43a7-8323-07680aba508e</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">10822ddd-9ba6-42d5-9339-de0845aeafc9</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7a446738-40b8-4d81-8f3c-d0dfa1241c71</cbc:ID>
                                <cbc:Description>Requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>The EO will allow the CA to visit the premises where the development is performed(upon pre-agreed calendar) in order to check the security measures undertaken by the EO.</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8f0509c0-b088-42a6-9128-13e46a1903cd</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a4973c79-051c-4b63-be27-5d46a6c09908</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f8dd0715-e1d8-4c6d-bbe4-f1ab25b9bcb1</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">abe5d8e2-a3a0-4a39-a550-bb64d514e552</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a3410620-8ed3-47f9-ab90-b5b1aeeff6a5</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">261caf7d-dd8f-4991-96ef-60297b9a4eb7</cbc:ID>
                                                <cbc:Description>Do you allow checks?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ee58f80a-dc0f-4288-88c1-e746264ca667</cbc:ID>
                                                <cbc:Description>Is this information available online?</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                  <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">adc13707-9729-4dfb-a026-bf276b0a75db</cbc:ID>
                                                  <cbc:Description>Evidence Supplied</cbc:Description>
                                                  <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                  <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- rest of elements removed for brevity -->

Abilities (V) - Staff

Data Structure

(The figure below is defined in the the tab ''SC_Abilities_5 (Staff)'' of the ESPD-criterion spread-sheet).

Abilities (V) (Staff)

Figure 175. 'Abilities (V) (Staff)' criterion data structure

XML Example

Criterion SC-Abilities (Staff) ESPD-Request

<!-- Header elements removed for brevity. -->

<!--This criterion illustrates how to prepare a selection criterion about ''abilities'', more specifically the criterion ''Number of managerial staff''-->

<!-- The rest of criteria above and below this criterion have been removed for brevity. -->

<!-- Criterion:Number of managerial staff -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6346959b-e097-4ea1-89cd-d1b4c131ea4d</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">manage-staff</cbc:CriterionTypeCode>
                <cbc:Name>Number of managerial staff</cbc:Name>
                <cbc:Description>The economic operator's number of managerial staff for the last three years were as follows:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">259b2cb7-b98b-4305-baae-1f6c521f0994</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">97b10c6b-d62c-4a68-b95a-1783a8a93c1d</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">98a87a09-39a3-429f-8ef8-a8b29339fa6e</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7f7949a8-dbe6-496c-a9f6-6f05b8648bad</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">15988699-0661-42dd-870d-47556c76bd52</cbc:ID>
                                <cbc:Description>Minum number of years</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6745965c-a3f7-4a72-8462-e87869b56e94</cbc:ID>
                                <cbc:Description>Additional information</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the buyer. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the buyer -->
                                <cbc:ExpectedDescription>[Additional information]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">32fc4b5e-0e6f-4d67-94c4-9877cb835dd6</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">eb2491ad-18e7-4c79-b596-20d939e822fd</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4b706b48-86de-480d-8459-6db8e71ea690</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d0509138-112c-437a-ae82-5a390944c01c</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5dc1ccd9-29c5-4038-a8f0-62db758842ba</cbc:ID>
                                        <cbc:Description>Year</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c88be4ba-b53c-4874-a4a8-d9e38e432a79</cbc:ID>
                                        <cbc:Description>Number</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">839f57de-d717-4c41-a9da-ac7cb2e1d9b0</cbc:ID>
                                        <cbc:Description>Is this information available online?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d476d19c-de20-4177-a926-77fdfa7d6daf</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- Rest of elements until the end of the Request documentn removed for brevity. -->

5.10. Subcontracting proportion

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

There is only one criterion with a simple data structure, classified as:

  • suncont-port

Mock-ups - buyer perspective

The buyer selects the criterion to be included in the ESPD Request:

Subcontracting proportion

Figure 176. 'Subcontracting proportion' buyer mock-up

Mock-ups - economic operator perspective

The economic operator has to provide a descriptive response in a free-text field:

Subcontracting proportion

Figure 177. 'Subcontracting proportion' EO mock-up

Data Structure

(Some columns have been hidden to enhance the readability of the image).

Subcontracting proportion' criterion data structure

Figure 179. 'Subcontracting proportion' criterion data structure

XML Example

'Subcontracting proportion' criterion

<!-- header elements removed for brevity -->

<!-- Criterion:Subcontracting proportion -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">612a1625-118d-4ea4-a6db-413184e7c0a8</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">suncont-port</cbc:CriterionTypeCode>
                <cbc:Name>Subcontracting proportion</cbc:Name>
                <cbc:Description>The economic operator intends possibly to subcontract the following proportion (i.e. percentage) of the contract. Please note that if the economic operator has decided to subcontract a part of the contract and relies on the subcontractor's capacities to perform that part, then please fill in a separate ESPD for such subcontractors, see Part II, Section C above.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4843ec84-031c-4abd-a78c-671c4dad4400</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">c9142feb-8776-4962-9a0e-aa963a6425b5</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0599bfbe-dba5-4b4d-a78a-ceeaf0787ce5</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e14dcaea-8363-477d-8654-5c8ddbc5cb5d</cbc:ID>
                                <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fff67658-7990-4173-a28a-9b51c3bb2cc2</cbc:ID>
                                        <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1800c69a-6d26-4261-ad57-5eb5a38e1ef2</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">19e18f28-ce30-4dea-8f57-80073e0e0135</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">575f7550-8a2d-4bad-b9d8-be07ab570076</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">be87a31c-9e0a-44e1-b4cb-5a96e15f8f89</cbc:ID>
                                <cbc:Description>Please specify</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3a3152ea-eb4f-475d-ba13-5939e1fbb77b</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">29c61f5a-eb77-4c85-bd8d-24f150f32195</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- rest of elements removed for brevity -->

5.11. Samples and certificates

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

There are two criteria that share the same data structure, classified as:

  • wo-autent

  • w-autent

Mock-ups - buyer perspective

The buyer selects the criteria that have to be included in the ESPD Request, e.g.:

Samples and certificates

Figure 180. 'Samples and certificates' buyer mock-up

Mock-ups - economic operator perspective

The economic operator only has to answer Yes or No. The GUI does not react in any way either the EO clicks one or the other (which is not the case for other criteria, see for example the behaviour of the criteria about 'quality assurance' below in further sections).

Samples and certificates

Figure 181. 'Samples and certificates' EO mock-up

Data Structure

(Some columns have been hidden to enhance the readability of the image).

Samples and certificates criteria data structure

Figure 183. 'Samples and certificates' criteria data structure

XML Example

'Samples and certificates' criterion

<!-- header elements removed for brevity -->

<!-- Criterion:For supply contracts: samples, descriptions or photographs without certification of authenticity -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">bdf0601d-2480-4250-b870-658d0ee95be6</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">wo-autent</cbc:CriterionTypeCode>
                <cbc:Name>For supply contracts: samples, descriptions or photographs without certification of authenticity</cbc:Name>
                <cbc:Description>For public supply contracts: The economic operator will supply the required samples, descriptions or photographs of the products to be supplied, which do not need to be accompanied by certifications of authenticity.</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e615882b-5327-40a5-9e95-46f8bc47d593</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fc811b82-bd59-4959-a62d-24cce243e180</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e51cbd1c-1bae-49cb-b854-c86d59a70824</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">60c3ee45-5930-4666-b68d-67ce1dfd1dea</cbc:ID>
                                <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">6b001a15-76a3-43df-bff5-4a95db63ed8b</cbc:ID>
                                        <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ONTRUE</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1"/>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">5b0ee75b-c238-445b-a696-c82550f58369</cbc:ID>
                                        <cbc:Name>Name of the entity</cbc:Name>
                                        <cbc:Description>[Name]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7a6aa002-d216-4a71-b72a-b991b9667a68</cbc:ID>
                                        <cbc:Name>ID of the entity</cbc:Name>
                                        <cbc:Description>[ID]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
						</cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">cb73544d-e8bb-4cc6-819b-b8e04f1e240e</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">9ee3d7cc-adb1-48e0-9f65-190567a05d14</cbc:ID>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">3ca57783-159f-47cb-b9d0-a0ec24ea270b</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8f46b28f-7e77-4a1a-9c3e-6e7acb0da069</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

5.12. Quality assurance

See formal requirements related to selection criteria in the BIS 41 - European Single Procurement Document (Version 2.0.0).

Mock-ups - buyer perspective

In ESPD the buyer can specify a REQUIREMENT. In this example it provides the name of the ISO it expects the economic operator to be conformant to.

Quality Assurance schemes and environmental management standards

Figure 187. 'Quality Assurance schemes and environmental management standards' buyer mock-up

Mock-ups - economic operator perspective

Notice that, as for the ESPD the economic operator (EO) has to answer Yes or No. In the case the EO answers No the box with the text "If not, please explain why and specify which other means …​" is shown. This box is not shown for the Yes answer. This behaviour can be controlled with the ONFALSE code of the sub-group of QUESTION(s) (see data structure and XML example below, too).

When the EO answers Yes it will be asked whether online evidences are available online or not. This is controlled by the code ONTRUE assigned to the sub-group of QUESTION(s) about the evidence (see data structure and XML example).

Quality Assurance schemes and environmental management standards' EO mock-up

Figure 188.'Quality Assurance schemes and environmental management standards' EO mock-up

Data Structure

Notice the following:

  1. In principle the buyer has to provide at least one REQUIREMENT. But it might decide not to provide any requirement at all. In this case do not to alter the data structure (e.g. not to remove the REQUIREMENT_GROUP) and to provide a text for REQUIREMENT such as, for example, 'No specific requirements'.

  2. The ONFALSE code for the sub-group containing the sentence thats starts with 'If not, please explain why…​' means: if the answer to the previous question was No then this sub-group must be shown/processed.

  3. If ONTRUE (answer to previous QUESTION = Yes) then the question about the online evidences is shown/processed.

(Some columns have been hidden to enhance the readability of the image).

Quality Assurance schemes and environmental management standards

Figure 189. 'Quality Assurance schemes and environmental management standards' criteria data structure

XML Example

'Certificates by quality control institutes' criterion

<!-- header elements removed for brevity -->

<!-- Criterion:For supply contracts: certificates by quality control institutes -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">a7669d7d-9297-43e1-9d10-691a1660187c</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">qa-certif-inst</cbc:CriterionTypeCode>
                <cbc:Name>For supply contracts: certificates by quality control institutes</cbc:Name>
                <cbc:Description>Can the economic operator provide the required certificates drawn up by official quality control institutes or agencies of recognised competence attesting the conformity of products clearly identified by references to the technical specifications or standards, which are set out in the relevant notice or the in the ESPD, the relevant notice or ?</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                        <cbc:Name>[Name of the National Criterion]</cbc:Name>
                        <cbc:Description>[Description of the National Criterion ]</cbc:Description>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d1b09540-bd2a-4962-bbcd-bb3e33c64694</cbc:ID>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2d776e97-ef4d-4220-83b6-a70332f242a2</cbc:ID>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">d6a38bde-89a1-4bc1-8124-b77cf7e1bf4b</cbc:ID>
                        <cbc:Title>[Legislation title]</cbc:Title>
                        <cbc:Description>[Legislation description]</cbc:Description>
                        <cbc:JurisdictionLevel>EU</cbc:JurisdictionLevel>
                        <cbc:Article>[Article, e.g. Article 2.I.a]</cbc:Article>
                        <cbc:URI>http://eur-lex.europa.eu/</cbc:URI>
                        <cac:Language>
                                <cbc:LocaleCode listID="language" listAgencyName="OP" listVersionID="20211208-0">ENG</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">612d99eb-ea3b-4275-ac06-0db05e039c8c</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">2bad2db0-bca7-42e3-b01b-19aa3afaded7</cbc:ID>
                                <cbc:Description>Requirement</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                <!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority -->
                                <cbc:ExpectedDescription>ISO 9001</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">0e50931d-4d39-4f1d-9fdc-b2cf16c0807a</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">634f10ad-7656-4800-af83-5e82bcb9f242</cbc:ID>
                                        <cbc:Description>Does the EO fulfil the criteria by itself?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe557ed0-2387-478f-a9be-d0f3457c088e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">1daa45dc-2247-4d4c-a726-8a887fff42ca</cbc:ID>
                                                <cbc:Description>In the case of no - Relied upon or not</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e296a1cc-83d3-48ac-b4e4-7e7d0ae0af25</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4cae2348-e917-4257-ad76-93d02736aaf5</cbc:ID>
                                                <cbc:Description>Name of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">facb663a-5f85-4c8e-8c84-dd2ae27b91b8</cbc:ID>
                                                <cbc:Description>ID of the entity</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
								</cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4887c3d7-05fc-4e3e-b066-f338910f0c4c</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f88b78fd-b7b1-48e4-9a41-7a5fcc67bcc0</cbc:ID>
                                        <cbc:Description>Your answer?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">83f2f79e-0455-4918-89ff-d7829e8bf758</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">e469b83b-43f4-4109-9567-788505cbb2fe</cbc:ID>
                                                <cbc:Description>If not, please explain why and state which other means of proof can be provided:</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">43ae65f6-4734-4065-bc33-27a7d49110ea</cbc:ID>
                                        <cbc:Description>Is this information available online?</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">4b207cf8-3852-4ac8-9762-9f22ca0d4fd9</cbc:ID>
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- rest of elements removed for brevity -->

5.13. Other aspects of participation and selection

Reduction of candidates

In restricted procedures, competitive procedures with negotiation, competitive dialogue procedures and innovation partnerships, buyers may limit the number of candidates meeting the selection criteria that they will invite to tender or to conduct a dialogue.

To cover this possibility, the ESPD Regulation introduces a section named "Reduction of the number of qualified candidates" with one criterion that reads as follows:

"The economic operator declares that it meets the objective and non-discriminatory criteria or rules to be applied in order to limit the number of candidates in the following way:".

This ESPD-EDM specification provides a specific data structure that allows the buyer to specify these objective and non-discriminatory criteria and for the economic operator to declare that it meets them.

However, in this version of the ESPD-EDM he behaviour of this criterion is linked to eForms instantiation of the aim of using the reduction of candidates. Meaning that if in eForms CN this is not stated, it will not be part of the ESPD-Request nor Response.

Data structure

The figure below shows the data elements required to the economic operator for this criterion in the ESPD-Request:

Reduction of candidates

Figure 190. 'Reduction of candidates' data structure

XML example (ESPD-Request)

The XML snippet below shows how an instance of this criterion looks like in the ESPD-Request.

Reduction of Candidates - (QUESTION(s) in the ESPD-Request)

<!-- ... beginning of document removed for brevity -->

<!-- Criterion:Reduction of the number of qualified candidates -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">51c39ba9-0444-4967-afe9-36f753b30175</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">staff-red</cbc:CriterionTypeCode>
                <cbc:Name>Reduction of the number of qualified candidates</cbc:Name>
                <cbc:Description>The economic operator declares that It meets the objective and non discriminatory criteria or rules to be applied in order to limit the number of candidates in the following way:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ecc69670-f428-4446-908f-689568ca0d0d</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">de82e45f-a0f6-43a6-9761-bfae3385fd1d</cbc:ID>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f13754df-7e15-4155-aaa6-7ca6407baa47</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ffc141f8-5ffe-4492-9066-7ff5dd633583</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">01a08984-328f-4bc8-88d9-56634e66ca3c</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe61b9a7-9e60-45eb-98c9-cd7102a86013</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

<!-- ... rest of document removed for brevity -->

6. The ESPD Response Document

6.1. Business requirements specification

The ESPD-EDM models the business and information requirements in alignment with the works developed by e-Sens, which uses the identifier Trdm092 to refer to the business requirements regarding the ESPD Response transaction. See formal information requirements related to the ESPD Response transaction in the document BIS 41 - European Single Procurement Document (Version 2.0.0), by e-Sens.

BUSINESS REQUIREMENT

The ESPD Response document must include all the criteria that are present in the ESPD Request. For certain *selection criteria the economic operator can add additional properties to the criteria so it can include in the ESPD Response more responses than the minimum required by the buyer.

This last requirement has a technical reason: each response of an economic operator needs to be linked to one, and only one, property of a criterion (this is explained and illustrated in the sections below). Therefore for those cases when the buyer requires a minimum number of data but gives the flexibility to the economic operator for adding more the economic operator (the software it uses) will have to add properties to the criterion.

Examples: the buyer requires a minimum of 3 references to works similar to the ones being procured, but the EO decides to add 5. The ESPD REquest will contain a criterion "For works contracts: performance of works of the specified type" with the structure prepared for three references. The ESPD Response will add two more structures to contain the additional references to that criterion. The ESPD will add (at the end of the file) five responses related to the same criterion, each response will point at five different properties of the criterion. This is described and illustrated in more detail in the section "Providing additional responses" below.

6.2. ESPD Response XSD Schema

For the ESPD Response, the ESPD-EDM uses the UBL-2.3 document named QualificationApplicationResponse.xsd XSD Schema. This schema can be found under the folder ubl-2.3/xsdrt/maindoc (or the equivalent documented xsd folder).

The figure below shows the XSD Schema defined by UBL-2.3 for this document, which replaces the Schema UBL 2.2. Only the first level components of the schema are shown. The inner sub-elements and sub-classes are covered in detail in the following sub-sections of this document. The ESPD Response share many elements with the ESPD Request. For those elements that have already been described in the ESPD Request please see the sections above in this document where those elements were explained.

Notice that, in the UBL-2.3 Schema there are only four mandatory elements: cbc:IssueDate, ContractFolderID, cac:ContractingParty (the buyer) and cac:EconomicOperatorParty (the economic operator).

This section about the ESPD Response does not cover those information elements that were already described in the ESPD Request, unless a characteristic related to the ESPD Response needs to be clarified. Thus for details about elements like cac:ContractingParty, cac:ProcurementProject and cac:AdditionalDocumentReference refer to the section 2. The ESPD Request.

QualificationApplicationResponse XSD Schema

Figure 191. QualificationApplicationResponse XSD Schema, global view

6.3. ESPD Response cardinalities

As you can see the UBL-2.3 Schema is quite flexible as, except for a few cases practically all the elements are optional.

The ESPD-EDM model, however, adds a few more restrictions regarding the cardinalities. These can be seen in the diagram below, which presents the ESPD-EDM structure for the ESPD Response with its own cardinality restrictions. Notice that ESPD-EDM does not change anything else from the UBL-2.3 Schema.

Qualification Application Response UML Diagram

Figure 193. ESPD-EDM 'QualificationApplicationResponse', UML diagram

If you compare both figures you will observe that:

  1. The cardinalities of the root common basic components, such as cbc:ID, cbc:UUID, cbc:TendererRole, and other are different for the ESPD than for UBL-2.3;

  2. Similarly, the cardinalities of aggregate components like cac:ContractingParty, cac:ProcurementProjectLot and cac:TenderingCriterion are different to the UBL-2.3 ones.

The cardinality constraints added by the ESPD are not defined in the XSD Schema. In order to control these constraints the ESPD-EDM uses ISO Schematron assertions. The ESPD-EDM distribution package provides Schematron schemata and CVA files for the validation of the XML instances (folder /validation).

The European Commission (EC) ISA2 Programme provides an Interoperability Testbed where Stakeholders can freely test these validation artefacts.

6.4. Root elements

The table below lists the elements that are expected in the ESPD Response and provides details on the cardinalities and usage of those elements.

Table 26. Class QualificationApplicationResponse, components required by the ESPD-EDM

Document name:

QualificationApplicationResponse

Definition:

"A structured electronic business document for providing qualification information in a simplified way through an ESPD when responding to a Call for Tender." (source: ESPD Response transaction (Trdm092)).

Preliminary evidence certificates in the form of a self-declaration submitted by the economic operator during the tendering phase. On awarding, the winning party has to supply the real attestations and certificates.

Business rule(s):

None

File:

ubl-2.3/xsdrt/maindoc/UBL-QualificationApplicationResponse-2.3.xsd

Components Type Card Description Requirements

cbc:UBLVersionID

Identifier

1

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.

Information Requirement: tbr92-020.

Rule: Use the value "2.3". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute.

Rule scope: Common (BR-OTH-05, 2.BR-OTH-02)

cbc:CustomizationID

Identifier

1

Identifies a user-defined customization of UBL for a specific use.

Information Requirement: tbr92-019.

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.

Rule scope: Common (BR-OTH-02, BR-OTH-06)

cbc:ProfileID

Identifier

0..1

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.

Information Requirement: tbr92-019.

Rule: Use the value "41". Use also "CEN-BII" for the scheme AgencyID attribute.

Rule scope: Common (BR-OTH-07, BR-OTH-02)

cbc:ProfileExecutionID

Identifier

1

The identification and version of the ESPD Exchange Data Model used to create the XML instance. The identification may include the exact version of the specification.

Information Requirement: tbr070-002.

Rule: Compulsory use of the CodeList ProfileExecutionID. Use the value "EU-COM-GROW" for th SchemeAgencyID attribute.

Rule scope: Common (BR-OTH-01, BR-OTH-01#13, BR-OTH-03)

cbc:ID

Identifier

1

An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, or the supplier, e.g. an economic operator). The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Information Requirement: tbr92-019.

Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document.

Rule scope: Common (BR-OTH-02)

cbc:CopyIndicator

Indicator

0..1

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

Information Requirement: tbr92-019.

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

cbc:UUID

Identifier

1

A universally unique identifier that can be used to reference this ESPD document instance.

Information Requirement: tbr92-019.

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

cbc:ContractFolderID

Identifier

1

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

Information Requirement: tbr92-013.

Rule: Try always to use the reference number issued by the buyer. This number in combination with a registered buyer ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.

Rule scope: (BR-SC-30)

cbc:IssueDate

Date

1

Date when the document was issued by the buyer.

Information Requirement: tbr92-019.

Rule: Format "YYYY-MM-DD".

cbc:IssueTime

Time

0..1

Time when the document was issued by the buyer.

Information Requirement: tbr92-019.

Rule: Format "hh:mm:ss".

cbc:EconomicOperatorGroupName

Text

0..1

The name of the group that presents a tender to which this economic operator belongs (e.g. the name of a consortium, a joint venture, etc.).

Information Requirement: tbr92-008.

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

Rule scope: (BR-LEAD-10-S10)

cbc:VersionID

Identifier

0..1

The version identifying the content of this document.

Information Requirement: tbr92-020.

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

cbc:PreviousVersionID

Identifier

0..1

The version identifying the previous modification of the content of this document.

Information Requirement: tbr92-020.

Rule: None

cbc:ProcedureCode

Code

1

The type of the procurement administrative procedure according to the EU Directives.

Information Requirement: tbr070-007.

Rule: For the ESPD, this information will be linked to eForms. And ESPD should include the same procedure code as the one stated in eForms notices.

cac:ContractingParty

Associated class

1

The buyer 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). See section Contracting Body for more specification details.

Information Requirement: tbr92-011.

Rule: UBL-2.3 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.

cac:EconomicOperatorParty

Associated class

1

Any natural or legal person or public entity 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.

Information Requirement: tbr92-001.

Rule: The ESPD Response only refers to one, and only one, economic operator.

Rule scope: Common (BR-RESP-10)

cac:ProcurementProject/cbc:Description

Text

1

Text describing this procurement project.

This element is required in the ESPD, however it should be identical to that provided in eForms. In general the corresponding eForm should feed the corresponding ESPD with the corresponding data. Information Requirement: tbr92-013.

Rule: Use this component to identify and describe the procurement administrative procedure.

cac:ProcurementProjectLot

Associated class

1

The procurement project lot or group of lots this ESPD Response tenders to.

Information Requirementtbr92-014.

Rule: The economic operator has to specify the Procurement Project Lot the ESPD refers to.

Rule scope: (BR-LOT-30)

cac:TenderingCriterion

Associated class

1..n

A tendering criterion describes a rule 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 candidates to the award decision.

Information Requirement: tbr92-015,tbr92-016.

Rule: (see examples further below in this document)

cac:TenderingCriterionResponse

Associated class

1..n

Response of the economic operator to the requirements and questions issued by the buyer in the ESPD Request.

Information Requirement: br92-018, tbr92-007, tbr92-005, tbr92-006.

Rule: (see examples further below in this document)

cac:AdditionalDocumentReference

Associated class

0..n

A reference to an additional document associated with this document.

Information Requirement: tbr92-013.

Rules: At least two instances of the AdditionalDocumentReference are expected:

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

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

Rule scope: Common (BR-COM-10)

cac:Evidence

Associated class

0..n

A reference to an online document available for free in a national or EU database.

Information Requirement: tbr92-017, tbr92-007, tbr92-006.

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

XML example

The XML snippet below shows how the beginning of an ESPD Response XML instance looks like. For a complete instance of an ESPD Response XML document see the the example files in the dist/xml folder: or ESPD-Response.xml.

<QualificationApplicationResponse

xmlns="urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationResponse-2"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"

xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions"

xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"

xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"

xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"

xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0" xmlns:util="java:java.util.UUID"

xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationResponse-2 ../xsdrt/maindoc/UBL-QualificationApplicationResponse-2.3.xsd">

<!-- The ESPD-EDM is entirely based on OASIS UBL-2.3 -->

<cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.3</cbc:UBLVersionID>

<!-- How ESPD-EDM uses the UBL-2.3 schemas whilst keeping conformance -->

<cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm092:ver3.0</cbc:CustomizationID>

<!-- The transactional profile where the ESPD is used. ESPD-EDM refers to the CEN profile -->

<cbc:ProfileID schemeAgencyID="CEN-BII" schemeVersionID="2.0">4.1</cbc:ProfileID>

<!-- The identifier of this document generally generated by the systems that creates the ESPD -->

<cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-bb99b1c34e</cbc:ID>

<!-- Indicates whether this document is an original or a copy. In this case the document is the original -->

<cbc:CopyIndicator>false</cbc:CopyIndicator>

<!-- The unique identifier for this instance of the document. Copies of this document should have different UUIDs -->

<cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">43afa3db-fbed-4565-9ef7-cd7089698836</cbc:UUID>

<!-- The reference number the buyer assigns to this procurement procedure -->

<cbc:ContractFolderID schemeAgencyID="DGPE">PP.20170419.1024-9</cbc:ContractFolderID>

<cbc:IssueDate>2021-02-11+01:00</cbc:IssueDate>

<cbc:IssueTime>16:27:06.248+01:00</cbc:IssueTime>

<!-- The version of the content of this document. If the document is modified the element cbc:PreviousVersionID should be instantiated -->

<cbc:VersionID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">1.0</cbc:VersionID>

<!-- The type of the procurement procedure; this information is provided by eForms and the concret notice per procedure. e.g. open = In open procedures any interested economic operator may submit a tender in response to a call for competition.-->

<cbc:ProcedureCode listID="procurement-procedure-type" listAgencyID="" listVersionID="">open</cbc:ProcedureCode>

_<!-- ... rest of document removed for brevity -->_

6.5. Reference to publications and to the ESPD Request

REQUIREMENT

The economic operator must include int its ESPD Response document the information from the ESPD Request about the official journals or gazettes where the procurement procedure is announced. For procurement projects above the threshold it is compulsory to refer to the Contract Notice published in TED by the buyer.

For EU and notice publications that need to be included in the ESPD Response. See the section "2.6 EU and notice publications" where this information is presented in detail and illustrated with examples.

REQUIREMENT

The economic operator must include in its ESPD Response document a reference to the ESPD Request. For this, the values of the two identifiers cbc:ID and cbc:UUID of the ESPD Request must be used as the values for the cbc:ID and cbc:UUID* in the ESPD Response cac:AdditionalDocumentReference (to refer to that ESDP Request).*

Thus the ESPD Response must also make reference to the ESPD Request that is being responded by the economic operator. The XSD diagram below shows (in blue) which elements are expected for this reference. See also the list of expected elements (and rules) and the XML example beneath the XSD diagram.

Reference to ESPD Request

Figure 195. Elements expected to reference the ESPD Request from the ESPD Response

If the buyer publishes the ESPD Request on a public journal, the economic operator must specify the URI from where the ESPD Response was downloaded to draft its ESPD Response (see for instance how this is done for the publications on the TED or national journals; and see also the XML example below).

This URI should be specified in the field cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference/cbc:URI:

URI_Reference to ESPD Request

Figure 196. URI of the ESPD Request

In the ESPD Response you may also add references to:

  • Evidences that are global for the whole Response. This is not recommended though. Evidences should be as much particular of the Criterion as possible.

  • Other documents, e.g. maps, diagrams, or descriptive documents to complement the references about works, supplies or services.

Expected elements

Table 27. Reference to the ESPD Request, expected elements

Class name:

cac:AdditionalDocumentReference

Definition:

A reference to an additional document associated with this document.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3xsd

Path:

/QualificationApplicationResponse/cac:AdditionalDocumentReference

Context of Use:

In this case this reference points at the ESPD Request XML instance that was used to produce the ESPD Response XML document.

Components Type Card Description Requirements

cbc:ID

Identifier

1

The identifier for the referenced document, generally issued by the entity responsible for the document.

Information Requirement: tbr92-013.

Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:ID.

Rule scope: Common (BR-OTH-02)

cbc:UUID

Identifier

1

A universally unique identifier that can be used to reference this ESPD document instance.

Information Requirement: tbr92-013.

Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:UUID.

Rule scope: (BR-OTH-02)

cbc:DocumentTypeCode

Code

1

The type of document being referenced, expressed as a code.

Information Requirement: tbr92-013.

Rule: For the ESDP-EDM it is compulsory use of the value ESPD_REQUEST from the Code List docref-content-type. See also the XML example below on how to specify the ESPD Request.

Rule scope: Common (BR-OTH-01, BR-COM-10#3, BR-OTH-01#3, BR-OTH-03)

cbc:DocumentType

Text

0..1

The type of document being referenced, expressed as text.

Information Requirement: tbr92-013.

Rule: Optionally use the attribute languageID to indicate the language of the text. Use the Code List Language for the value of the languageID attribute.

Rule scope: Common (BR-OTH-01, BR-OTH-01#4, BR-OTH-03)

cbc:IssueDate

Date

0..1

Date when the document was issued by the buyer.

Information Requirement: tbr92-013.

Rule: Format "YYYY-MM-DD". If available in the referenced document place here the data of publication by the buyer.

cbc:IssueTime

Time

0..1

Time when the document was issued by the buyer.

Information Requirement: tbr92-013. Rule: If available in the referenced document place here the time of publication by the buyer.

cbc:DocumentDescription

Text

0..1

Text describing the referenced document.

Information Requirement: tbr92-013. Rule: Use the attribute languageID to indicate the language of the text. Use the Code List LanguageCodeEU for the value of the languageID attribute.

Rule scope: Common (BR-OTH-01, BR-OTH-01#4, BR-OTH-03)

Beware that the ESPD document does not embed the content of referenced documents but instead make a reference to its source. Thus the class DocumentReference aggregates a `cac:Attachment`class that allows for making reference to an external source of the content, which is the preferred way in the ESPD-EDM (see XSD schema above).

In the case of the reference to the ESPD Request from the ESPD Response, the only data expected here is the URI where the ESPD Request XML instance was published:

Table 28. External Reference

Component name:

cac:ExternalReference

Definition:

A reference to the authentic source of content of this document.

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:AdditionalDocumentReference/cac:Attachment/cac:ExternalReference

Context of use:

Reference to the URI location where the ESPD Request XML instance can be downloaded from.

Components Type Card Description Requirements

cbc:URI

Identifier

0..1

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

Information Requirement: tbr92-013.

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

cbc:FileName

Text

0..1

The title of the document.

Information Requirement: tbr070-007.

Rule: Originally this field is the placeholder for the name of the file (e.g. PLACE-ContractNotice-2017-12452.xml. However, as the UBL component does not have a placeholder for a name or title, the ESPD documents use it for a short descriptive title of the document being referenced.

cbc:Description

Text

0..n

Short description of the document.

Information Requirement: tbr070-007.

Rule: If 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. See example and comments below.

Rule scope: Common (BR-COM-10#2, BR-COM-10-S10, BR-COM-10-S20, BR-COM-10-S30)

6.6. Economic Operator

See formal requirements related to the economic operators in the e-Sens site: (tbr092-001, _tbr092-008).

Table 29. Information requirement about the ESPD Response and the economic operators

REQUIREMENT

One ESPD Response per economic operator. The ESPD-EDM, as all the previous versions of the ESPD, requires that every economic operator that participates in one tender provide its own ESDP Response document. This affects sole traders that rely on other entities for the execution of the contract (e.g. subcontractors) and groups of economic operators, e.g. a Joint Venture or a Consortium, and all the sub-contractors on which each economic operator of the group relies on to meet the selection criteria.

Moreover, each EO should submit an ESPD Response per lot or group of Lots which tenders to.

Table 30. Information requirement about the identifiers of the economic operators

REQUIREMENT

For the identification of the economic operators the UBL-2.3 element cac:PartyIdentification/cbc:ID must be used. The following two attributes of the cbc:ID element (CCT IdentifierType element) must be used: (1) @schemeID, a code from the Code List EOIDType must be used; (2) @schemeAgencyID, the default value "EU-COM-GROW" must be used; (3) Optionally, the attribute @schemeName can be used to place the 'Name' of the code (see the column 'Name' in the above mentioned Code List). For the ESPD-EDM the preferred type code for the @schemID is VAT.

Table 31. Information requirement about the groups of economic operators

REQUIREMENT

All economic operators belonging to a group (e.g. a Joint Venture, a Consortium, etc.) must specify the name of the group exactly with the same spelling (and respecting capital and lower cases, punctuation, and symbols) in each of their ESPD Responses.

| a| About the definition of economic operator

Beware that this ESPD-EDM specification defines economic operator based on the one provided by the 2014 Directives, where an economic operator is "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".

According to this definition one group of suppliers associated in a Joint Venture or in a Consortium, or any other type of undertaking is also an economic operator.

However, due to the previous requirement establishing that each company participating in a tender must prepare its own ESPD Response document, the ESPD-EDM specification never uses the term "economic operator" to refer to a group of persons and/or companies but only to refer to each natural or legal person or public entity that participates in a tender.

Therefore, in the context of the ESPD the definition of economic operator has been rephrased as "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".

A couple of examples. According to the previous requirements:

  • One tender submitted by a sole trader that relies on two sub-contractors will have to include three ESPD Requests, one for the sole trader and one per each of the sub-contracted entity.

  • One tender submitted by a Consortium composed of three economic operators, two of which rely on two sub-contracted entities and the third one relies on five sub-contracted entities, will have to include 3 + 2 + 5 (ten) ESPD Requests.

  • Note that both examples are made to represent who should provide an ESPD Response. But it is also worth to note that all the participants have to provide an ESPD per Lot to which tender.

The information that the economic operator (EO) has to provide is relatively abundant, especially if the EO is the lead entity of a group. UBL does provide a class cac:EconomicOperatorParty with sufficient data elements to identify the economic operator, its role, its representatives, physical location, officially registered address and other.

As the whole ESDP-EDM is based entirely on the UBL-2.3 XSD (W3C) Schemas, these schemas are to be used for ESPD.

Nonetheless some data requested in the ESPD are not modeled in UBL-2.3, namely those aiming at purposes going beyond the identification of the economic operator; e.g. data with statistical purposes; or to ensure the transparency of the procurement procedure; other.

Therefore in the ESPD-EDM, the information about the economic operator is spread in two different places:

  1. The UBL-2.3 cac:EconomicOperatorParty component; and

  2. In criteria data structures: following the solution adopted for Version ESPD-EDM, the ESPD-EDM defines several criteria classified as CRITERION.OTHER.EO_DATA.* (where the * refers to different branches and leaves of a different structures about the economic operator (e.g. SHELTERED_WORKSHOP, TOGETHER_WITH_OTHERS, etc.). The XML instances use criteria components (UBL-2.3 cac:TenderingCriterion) to structure these data. The sub-sections below cover both.

XSD Schemas

cac:EconomicOperatorParty

The UBL-2.3 cac:EconomicOperatorParty has three common aggregate components, the XSD Schema looks like this:

EconomicOperator overview

Figure 197. cac:EconomicOperatorParty XSD, global view

  1. cac:QualifyingParty: is used to place data about the economic operator that is available from an official list, tenderer register or (pre)qualification system, such as official classification schemes, certificates, the number of employees, references used for the classification, etc.;

  2. cac:EconomicOperatorRole: use to place the role of the economic operator;

  3. cac:Party: used to place the data to identify the EO and its contact.

cac:QualifyingParty

The diagram below shows the XSD element that will hold the data required by the ESPD (see mock-up 1/7, too). Beware that:

  • Identification of the economic operator: The Identifier assigned by the register or (pre)qualification system to the economic operator is placed in the element /cac:EconomicOperatorParty/cac:QualifyingParty/cac:Party/cac:PartyIdentification (more details on this below and in the XML example);

  • (Pre)qualification system: The Identifier and name of the (pre)qualification system is captured from e-Certis. The only datum that is necessary to keep in the XML is the identifier of the system provided by e-Certis. This identifier will be used as the value for the attribute schemeAgencyID (always compulsory) of the element /cac:EconomicOperatorParty/cac:QualifyingParty/cac:Party/cac:PartyIdentification. This way:

    • The (pre)qualification system is perfectly identified (and trusted, as it is registered in eCertis); and

    • The economic operator, identified with the number used in that (pre)qualification system, is linked inequivocally to that (pre)qualification system.

  • References and classification: The references linked to the classification of the EO are place in the component cac:QualifyingParty/cac:CompletedTask.

    • For this version of the ESPD the only expected data about the reference is a short description identifying the task as described in the (pre)qualification system. However if you take a look at this common aggregate component you will observe that it caters for other relevant data.

    • Similarly, this version of the ESPD-EDM, does not expect a complex representation of possible (optional) classification schemes. However the component cac:BusinessClassificationScheme, associated to cac:QualifyingParty allows complex hierarchical classifications.

  • SME and number of employees: The number of employees determine the classification of the company as Micro, Small, Medium or Large company. The cac:QualifyingParty component provides two place-holders that are used by this ESPD-EDM (see also mock-ups above) :

    • cac:QualifyingParty/cbc:EmployeeQuantity, for the number of employees; and

    • cac:QualifyingParty/cac:Party/cbc:IndustryClassificationCode to indicate whether the EO is a micro, small, medium or large company (or simply an SME). This code is defined in the Code List economic-operator-size. See also sections "Expected Elements" and "XML example" for more details.

  • Turnover: For statistical purposes the ESPD-EDM asks this datum to reflect the financial capability of the economic operator (see mock-ups above). This datum is to be placed in cac:QualifyingParty/cac:FinancialCapability/ValueAmount.

Qualifying Party

Figure 198. cac:QualifyingParty element, XSD

cac:EconomicOperatorRole

The UBL-2.3 element for the role of the economic operator is quite straightforward and typical in UBL: it provides a pair code + description (see Code List eo-role-type for the codes and descriptions; see also the XML example below).

Role of the economic operator

Figure 199. Role of the economic operator

cac:Party

The XSD diagram below shows (in blue) the elements for which data are expected in the ESPD Response for the cac:Party element of the economic operator.

The Party of the economic party

Figure 200. The Party of the economic party

The figures below show the cac:QualifyingParty sub-components cac:BusinessClassificationScheme and FinancialCapability, and cac:CompletedTask in a bit more of detail. At present, the ESPD-EDM only uses one field, cbc:Description for the references and classifications and `cbc:Amount`for the Turnover.

UBL-2.3 'Classification Scheme'

Figure 201. The rich structure of a UBL-2.3 'Classification Scheme' for the representation of taxonomies

UBL-2.3 'Capability'

Figure 202. The structure of UBL-2.3 'Capability'

UBL-2.3 Completed Task (used for references)

Figure 203. The structure of the UBL-2.3 Completed Task (used for references)

UBL-2.3 provides a component to hold very specifically the data to identify the economic operator as it officially registered in a Business Register. This XSD diagram below shows the elements of this component cac:LegalEntityParty. This ESPD-EDM specification recommends to use it as an alternative (or supplementary) way to identify the economic party.

UBL-2.3 Legal Entity Party

Figure 204. The UBL-2.3 Legal Entity Party

Expected elements

Please, remember that the elements cac:ContractingAuthority, cac:ProcurementProject, cac:ProcurementProjectLot and cac:AdditionalDocumentReference are expected in the ESPD Request, too. However, for the sake of brevity, and as they are taken from the ESPD Request and 'copied' in the ESPD Response, they have not been re-explained in this section about the ESPD Response. Therefore for details on those elements please refer to the section 2. The ESPD Request document.

Remember that if the economic operator belongs to a group (i.e. it is not a sole contractor), the element /cac:QualificationApplicationResponse/cbc:EconomicOperatorGroupName becomes compulsory and that the spelling of the name must be identical for lead entity, all the members of the group and all the entities that participate in the procedure.

Table 32. Economic operator, expected elements

Class name:

cac:EconomicOperatorParty

Definition:

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.

Business rule(s):

Common (BR-RESP-10)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:EconomicOperatorParty

Context of use:

The ESPD Response document.

Components Type Card Description Requirements

cac:QualifyingParty

Associated class

1

The distinctive features or characteristics qualifying an economic operator to be a party in a tendering process (e.g., number of employees, number of operating units, type of business, technical and financial capabilities, completed projects).

Information Requirement: tbr92-001

Rule: This element is compulsory in the ESPD-EDM as it is the natural placeholder for several relevant data about the Economic Operator.

Rule scope: BR-RESP-10-01

cac:EconomicOperatorRole

Associated class

1

The function of the economic operator when bidding from a consortium (Sole tenderer, member of a group, etc.).

Information Requirement:

Rule: This element is compulsory in the ESPD-EDM because depending on it different sets of data will be required or not, shown or hidden, processed or skipped.

cac:Party

Associated class

1

Main set of data used to identify and contact the economic operator, such as official identifiers, name, address, contact person, representatives, etc.

Information Requirement:

Rule: (See expected elements and rules below in the table about this Party).

Table 33. Qualifying Party, expected elements

Class name:

cac:QualifyingParty

Definition:

The distinctive features or characteristics qualifying an economic operator to be a party in a tendering process (e.g., number of employees, number of operating units, type of business, technical and financial capabilities, completed projects).

Business rule(s):

(BR-RESP-10-01)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:EconomicOperatorParty/cac:QualifyingParty

Context of use:

Economic Operator in the ESPD Response document.

Components Type Card Description Requirements

cbc:EmployeeQuantity

Quantity

0..1

The number of people employed by the economic operator participating in the tender.

Information Requirement: tbr92-001

Rule: Integer value expected.

cac:BusinessClassificationScheme/cbc:Description

Text

0..n

The text describing one official classification assigned by an official list or (pre)qualification system to the economic operator.

Information Requirement: tbr92-001

Rule: Only the 'Description' is expected, but the component cac:ClassificationScheme offers other rich possibilities (see the UBL-2.3 model in the distribution package or in the original source for more details).

Rule: Integer value expected.

cac:FinancialCapability/cbc:ValueAmount

Amount

0..1

A monetary amount as a measure of this capability.

Information Requirement: tbr92-001

Rule: 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 currency.

Rule scope: (BR-OTH-01#16, BR-OTH-03)

cac:CompletedTask/cbc:Description

Text

0..1

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

Information Requirement: tbr92-001

Rule: Use it to place here the references that were used in the (pre)qualification system to get the specific classification related to those references.

cac:Party/cac:PartyIdentification/cbc:ID

Identifier

1

The identifier of the economic operator in an official list, register or (pre)qualification system.

Information Requirement: tbr92-001

Rule: 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:QualifyingParty/​cac:Party/​cac:PartyIdentification/​cbc:ID for the value of the identifier. Additionally you can use the data structure "registered" to specify an alternative or additional name, identifier and description. The code list EOIDType should be used to indicate the type of identifier used as a value of the schemeID attribute, e.g. schemeID="VAT").

Rule scope: (BR-RESP-80-S10, BR-RESP-80-S20), Common (BR-RESP-50, BR-OTH-02)

Table 34. Economic operator role, expected elements

Class name:

cac:EconomicOperatorRole

Definition:

The function of the economic operator when bidding from a consortium (Sole tenderer, group leader, member of a group, etc.).

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationRequest/cac:EconomicOperatorParty/cac:EconomicOperatorRole

Context of use:

Economic Operator in the ESPD Response document.

Components Type Card Description Requirements

cbc:RoleCode

Code

1

Identifies the role of the economic operator in the bid.

Information Requirement: tbr92-008 Rule: Compulsory use of the Code List eo-role-type.

Rule scope: (BR-RESP-10-03, BR-OTH-01, BR-OTH-01#15, BR-OTH-03)

cbc:RoleDescription

Text

0..1

The text describing the role of the economic operator in the bid.

Information Requirement: tbr92-008

Rule: Software applications should retrieve and reuse the description from the Code List eo-role-type.

Rule scope: Common (BR-RESP-10-02)

Table 35. (Qualifying) economic operator party, expected elements

Class name:

cac:Party

Definition:

Main set of data used to identify and contact the economic operator, such as official identifiers, name, address, contact person, representatives, etc.

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party

Components Type Card Description Requirements

cac:PartyIdentification/cbc:ID

Identifier

1

An identifier that identifies the economic operator, such as the VAT number, the company registration number in a Business Register, other.

Information Requirement: tbr92-001.

Rule: When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system). When not possible a different identifier may be used. For a very complete way of identification of the Party it is highly recommended to, additionally to the cac:Party/cac:Identification/cbc:ID, use the UBL-2.3 component cac:PartyLegalEntity: this element is the perfect placeholder for the data officially registered in a Business Register (see UBL-2.3 model, and XSD diagram above).

Rule scope: Common (BR-OTH-02)

cbc:EndPointID

Identifier

0..1

Electronic address of the contracting body.

Information Requirement: tbr92-001.

Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the cac:Party/cbc:WebsiteURI). An end-point identifier MUST have a scheme identifier attribute (e.g.eSENSParty Identifier Scheme). Should be considered for all actors (buyer, service provider, economic operator) as an eDeliveryID.

Rule scope: Common (BR-RESP-10-08)

cac:PartyName/cbc:Name

Text

1

The name of the economic operator.

Information Requirement: tbr92-001.

Rule: Use the official name of the Party as officially registered. Be accurate in its spelling.

cbc:IndustryClassificationCode

Code

1

Used to indicate whether the company is a micro, small, medium or large enterprise.

Information Requirement: tbr92-004.

Rule: Used only for statistical purposes. Compulsory use of code list economic-operator-size, to determine EO’s company is micro, small, medium or large.

cbc:WebsiteURI

Identifier

0..1

The website of the economic operator.

Information Requirement: tbr92-012.

Rule: Use it for the official web site of the service provider.

Table 36. Economic operator postal address, expected elements

Class name:

cac:PostalAddress

Definition:

Postal address information.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/​cac:EconomicOperatorParty/​cac:Party/​cac:PostalAddress

Components Type Card Description Requirements

cac:AddressLine/cbc:Line

Text

0..1

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

Information Requirement: tbr92-012.

Rule: None.

cbc:CityName

Text

0..1

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

Information Requirement: tbr92-012.

Rule: None.

cbc:PostalZone

Text

0..1

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

Information Requirement: tbr92-012.

Rule: None.

cac:Country/cbc:IdentificationCode

Code

1

A code that identifies the country.

Information Requirement: tbr92-012.

Rule: The country of the contracting body must always be specified. Compulsory use of the Code List Country.

Rule scope: Common (BR-RESP-10-07, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

cac:Country/cbc:Name

Text

0..1

The name of the country.

Information Requirement: tbr92-012.

Rule: None.

Table 37. Contact of the economic operator, expected elements

Class name:

cac:Contact

Definition:

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

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:Contact

Components Type Card Description Requirements

cbc:Name

Text

0..1

The name of the contact point.

Information Requirement: tbr92-012.

Rule: None.

cbc:Telephone

Text

0..1

A phone number for the contact point.

Information Requirement: tbr92-012.

Rule: None.

cbc:Telefax

Text

0..1

A fax number for the contact point.

Information Requirement: tbr92-012.

Rule: None.

cbc:ElectronicMail

Text

0..1

An e-mail address for the contact point.

Information Requirement: tbr92-012.

Rule: None.

Table 38. Service provider, expected elements

Class name:

cac:ServiceProviderParty/cac:Party

Definition:

Main information about the service provider.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:ServiceProviderParty/cac:Party

Components Type Card Description Requirements

cbc:WebsiteURI

Identifier

0..1

The website of the service provider.

Information Requirement: tbr070-021.

Rule: Use it for the official web site of the service provider. Reserve the EndPointID for online services (e.g. web, REST, ftp services, etc.)

cbc:EndpointID

Identifier

0..1

Electronic address of the service provider.

Information Requirement: tbr070-021.

Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the cac:Party/cbc:WebsiteURI). An end-point identifier MUST have a scheme identifier attribute (e.g.eSENSParty Identifier Scheme). Should be considered for all actors (buyer, service provider, economic operator) as an eDeliveryID.

Rule scope: Common (BR-RESP-10-08)

cac:PartyIdentification/cbc:ID

Identifier

1

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

Information Requirement: tbr070-021.

Rule: An identifier for the service provider must always be provided. Compulsory 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). See XML example below.

Rule scope: Common (BR-RESP-10-11, BR-OTH-02)

cac:PartyName/cbc:Name

Text

1

The name of the service provider.

Information Requirement: tbr070-021.

Rule: The name of the service provider must always be specified. Supply the official registered name of the service provider.

Rule scope: Common (BR-RESP-10-09)

cac:PostalAddress/cac:Country/cbc:IdentificationCode

Code

1

The code that identifies the country of the service provider.

Information Requirement: tbr070-021.

Rule: The country of the service provider must always be specified. Compulsory use of the Code List Country.

Rule scope: (BR-RESP-10-10, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

  1. The value expected for the EO identifier is of type Identifier. For the identifier of the EO it is also required to specify the type of identifier, and a closed list of possible types is proposed. EOs must use one of the available values, but the preferred one is the VAT number. Beware that the data structure does not keep the type of the identifier. This is because the this type code is placed in the attribute @schemeID of the cac:ResponseValue/cbc:ResponseID element (and the @schemeAgencyID attribute must be set to the default EU-COM-GROW). See the information requirement about the identifiers of the economic operators at the beginning of the section. See also next sections about the responses, XSD schemas and XML example.

As you will see next, the information required about the economic operators varies depending on several factors:

  1. Is the economic operator a sole trader or does it belong to a group?

  2. If it belongs to a group, is the economic operator the leader of the group, a member or another entity (see the different types of 'roles' below);

  3. Does the economic operator rely on other entities to fulfill the selection criteria?

  4. Is the procurement procedure divided into lots?

One relevant aspect is the Role of the economic operator. The ESPD-EDM defines five different roles for the EO. The information to be provided by each role varies depending on whether the EO is:

  1. Sole tenderer / Group Leader: Sole entity or, in case of Consortium, Joint Venture or other types of groups, the leader of the group. In this case:

    • The sole contractor or leader will have to produce a complete ESDP;

    • The sole contractor or leader will also have to identify the rest of the procurers (in the case of a group);

    • The sole contractor or leader will have to identify the entities upon which it relies (and about those on which the entities it relies on rely).

    • The sole contractor or leader will have to identify the entities upon which it does not relies.

    • The sole contractor or leader will have to specify the subcontracted proportion of the group (in the selection criteria "Subcontracted Proportion" of the ESPD).

  2. Group member: Member (not leader) of the Consortium, Joint Venture or other type of group. In this case:

    • The member of the group will have to produce a complete ESPD;

    • The member of the group does not have to identify the rest of the procurers or entities.

  3. Other entity (relied upon): Entity on which the main contractor, the group or another subcontractor relies in order to meet the selection criteria. In this case:

    • The entity will have to produce an ESPD;

    • The entity will not have have to identify the rest of the procurers or entities. Beware that an entity could have again another entity which it relies on or a a sub-contractor: in this case those entities and sub-contractors will have also to produce their own ESPD Response.

  4. Subcontractor: Entity on which the main contractor, the group or another subcontractor does not rely in order to meet the selection criteria. In this case:

    • The entity will have to produce an ESPD, too;

    • The entity does not have to provide information about the selection criteria;

    • The entity does not have to provide information about the reduction of the number of qualified candidates.

The simplest case

The simplest case is when:

  • The economic operator (EO) is a sole tenderer

  • The EO does not rely on other entities

  • The EO has to provide an ESPD Response per Lot that wishes to tender

Notice the following:

  1. Sole contractor. We know that the EO is a sole contractor when:

    • The role specified is 'Sole contractor'; and

    • The EO states that it does not participate together with others; and

    • The EO states that it does not participate in a group;

  2. Not an SME. . The definition of what is an SME is provided in the EU recommendation 2003/361. Notice that ESPD asks for the number of employees and turnover. This can be used by the software applications to validate the consistency of the data provided by the EO with the definition. By the way, these data are all placed in the cac:QualifyingParty element. See the XSD diagrams above the and the XML example below for details on the use of the cac:QualifyingParty and sub-components.

Sheltered workshop

If the economic operator answers Yes the fields about the 'percentage of disabled/disadvantaged workers and the category of handicap to which they belong to should shown, validated or processed.

Data structure for a sheltered workshop or social business in case of reserved procurement:

Sheltered workshop or social business

Figure 222. Sheltered workshop or social business - data structure

EO registered in a (Pre)Qualification System (PQS)

One of the questions asked is whether the economic operator is registered on an official list (e.g. on a national Pre-Qualification System). In the case the EO answers Yes, the software application should ask the EO for this other data about which the evaluators may be interested in

Beware that the (pre)qualification system the EO is registered on must be know by the software application. One proposal is that each (pre)qualification systems is perfectly identified and registered in e-Certis so the applications can use it and trust it (and even download certificates from it). Note that This is part of the schema envisioned in the Once Only Principle. However if this were not possible (because e-Certis does not implement this timely, for example), the data structure for the PQS provides an alternative field to keep the name of the (pre)qualification system; see data structure below.

In case the EO is registered on several pre-qualification systems, the EO will need to choose the one that applies to this particular procurement procedure. The EO will also be required to provide the identification of the EO in the selected pre-qualification system.

Data structure for the (pre)qualification of the economic operator by an official list or similar:

  • The identifier assigned by the (pre)qualification system to the economic operator is required. This value however is placed in the element cac:QualifyingParty/cac:Party/cac:PartyIdentification/cbc:ID and therefore is not required in the data structure.

  • The name of an alternative or additional (pre)qualification system (PQS) can also be provided by the EO. In principle this is not necessary as the PQS identifier is the value of the attribute @schemeAgencyID of the element cbc:ID.

Pre-qualification-related data structure

Figure 223. Pre-qualification-related data structure

Data structure to identify the rest of the EOs that are members of the group:

In the ESPD the Group leader must identify the rest of economic operators that participate in the group. See the rest of the mock-ups and data structure below to see how, additionally, it also identifies other entities (e.g. sub-contractors).

Notice that:

  1. The values expected for the name and activity are texts.

  2. The value expected for the EO identifier is of type Identifier. For the identifier of the EO it is also required to specify the type of identifier, and a closed list of possible types is proposed (see Code List EOIDType. EOs must use one of the available codes, but the preferred one is the VAT number. Beware that the data structure does not keep the type of the identifier. This is because this type code is placed in the attribute @schemeName of the cac:ResponseValue/cbc:ResponseID element (and the @schemeAgencyID attribute must be set to the default EU-COM-GROW). See information requirements at the beginning of the section. See also next sections about the responses, XSD schemas and XML example.

Group of EO

Figure 226. Group of EO, data structure

Certificates about contributions to the Tax Agency and/or Social Security

Data structure for the certificates about contributions to the Tax Agency and/or Social Security:

Contributions certificates - data structure

Figure 227. Contributions certificates

Mock-up: Information about reliance on the capacities of the other entities

As explained above, the Sole tenderer or the Leader of a group will have to provide information about the entities it relies on in order to meet the selection criteria. The mock-up below shows the set of data the ESPD-EDM expects from this role. Remember that this information does not need to be supplied by the members of a group or other entities.

EO Roles-entities relied on

Figure 228. EO Roles-entities relied on, mock-up

Data structure for the entities upon which the EO relies on:

Relied on entities - data structure

Figure 229. Relied on entities - data structure

Mock-up: Information about third parties on which the EO does not rely on

The Sole contractor or the Leader of a group will have also to provide information about subcontractors on whose capacity the economic operator does not rely. Remember that this information does not need to be supplied by the members of a group or other entities.

EO Roles-entities not relied on

Figure 230. EO Roles-entities not relied on, mock-up

Data structure for the entities upon which the EO does not relies on:

Not relied on entities - data structure

Figure 231. Not relied on entities - data structure

XML Example

This example contains all the data about an economic operator. Beware that the basic identification data is placed into the cac:EconomicOperatorParty component, whilst the rest of the data (namely for statististical purposes) is structured in the data structures described above.

Economic operator data - XML example

<!-- The group of the name is at the root of the document -->

<!-- The name of the group (Consortium, Joint Venture, etc.) if the tenderer is not a sole contractor -->

<cbc:EconomicOperatorGroupName>ACME-Consortium</cbc:EconomicOperatorGroupName>

<!-- Root elements removed for the sake of brevity -->

<!-- Economic Operator Data -->

<cac:EconomicOperatorParty>

<cac:QualifyingParty>

<cbc:EmployeeQuantity>12167</cbc:EmployeeQuantity>

<cac:FinancialCapability>

<cbc:ValueAmount currencyID="EUR">1203000000</cbc:ValueAmount>

</cac:FinancialCapability>

<cac:Party>

<!-- This EO company is NOT an SME -->

<cbc:IndustryClassificationCode listID="economic-operator-size" listAgencyID="OP" listVersionID="20210317-0">LARGE</cbc:IndustryClassificationCode>

<!-- Notice that the ID and Name of the Pre-Qualification System is in the attributes. They would be captured from e-Certis. -->

<cac:PartyIdentification>

<cbc:ID schemeID="VAT" schemeAgencyID="ROLECE" schemeAgencyName="Registro Oficial de Licitadores y Empresas Clasificadas del Estado">B82387770</cbc:ID>

</cac:PartyIdentification>

</cac:Party>

</cac:QualifyingParty>

<cac:EconomicOperatorRole>

<cbc:RoleCode listID="http://publications.europa.eu/resource/authority/eo-role-type" listAgencyID="OP" listVersionID="20211208-0">group-lead</cbc:RoleCode>

<cbc:RoleDescription>Sole entity or, in case of Consortium, Joint Venture or other types of groups, the leader of the group.</cbc:RoleDescription>

</cac:EconomicOperatorRole>

<cac:Party>

<!--Additional Identifier not provided -->

<cbc:WebsiteURI>https://everis.com/global/en</cbc:WebsiteURI>

<cac:PartyIdentification>

<cbc:ID schemeAgencyID="VAT" schemeAgencyName="EU-COM-GROW" schemeID="VIES" schemeURI="link:http://ec.europa.eu/taxation_customs/vies/vieshome.do?locale=es" schemeName="VAT number">B82387770</cbc:ID>

</cac:PartyIdentification>

<cac:PartyName><cbc:Name>Everis, Spain, S.L.U.</cbc:Name></cac:PartyName>

<cac:PostalAddress>

<cbc:CityName>Madrid</cbc:CityName>

<cbc:PostalZone>28050</cbc:PostalZone>

<cac:AddressLine>

<cbc:Line>Manoteras, 52</cbc:Line>

</cac:AddressLine>

<cac:Country>

<cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">ES</cbc:IdentificationCode>

<cbc:Name>Spain</cbc:Name>

</cac:Country>

</cac:PostalAddress>

<cac:Contact>

<cbc:Name>Xavi Ker; Ruth Gomis; Miguel Verde</cbc:Name>

<cbc:Telephone>+34 91 749 00 00</cbc:Telephone>

<cbc:ElectronicMail>Spain.Proposals.Office@everis.com</cbc:ElectronicMail>

</cac:Contact>

</cac:Party>

</cac:EconomicOperatorParty>

<!-- EO DATA ENDS HERE -->

<!-- EXCLUSION CRITERIA START HERE -->

<!-- Exclusion and selection Criteria, Responses and Evidences removed for the sake of brevity -->
  1. Role of the economic operator. The values are defined in the Code List eo-role-type. The selection of the value Sole Tenderer or Group Leader determines whether the data about the relied-on and not-relied-on entities is instantiated in this XML.

  2. Name of the economic operator. A text field.

  3. Street and number of the economic operator. Notice that the cac:AddressLine element is used instead of cbc:StreetnName and cbc:BuildingNumber. This is because name and number are not split in two fields.

  4. Postcode (zip code) of the EO. A text field. Either the GUI and/or an external Schematron rule could be implemented to control the pattern of this text.

  5. City, the name of the town of the EO. Applications could check whether the town exists in the country.

  6. Country, only the country code identifier is needed. In this example the description is also used, but is redundant. Software applications should be able to, based on the language of the user, retrieve the name of the country based on the country code.

  7. E-mail address of the EO. A text field. Either the GUI and/or an external Schematron rule could be implemented to control the pattern of this text.

  8. Telephone of the EO. A text field. Either the GUI and/or an external Schematron rule could be implemented to control the pattern of this text.

  9. A coma separated list of persons of contact.

  10. The VAT number of the EO. Notice how the attributes of the cbc:ID element are used: they respect the information requirements established for the identification of the EO (see requirements at the beginning of the section).

  11. Additional identifier. In this example it is not used, thus the absence of the element.

  12. Internet address, normally the official web-site of the EO.

  13. Code to identify the type of the company (micro, small, medium, SME, Large). Notice the use of the Code List economic-operator-size (for statistical purposes).

  14. Number of employees of the EO’s company. Do not use separators. The software application should take care of the formatting (for statistical purposes).

  15. Indicative turnover of the EO’s company (for statistical purposes).

Economic operator representatives

See formal requirements related to the representatives of the economic operator in the e-Sens site: tbr92-021.

Notice that the economic operator may specify more than one representative.

Mock-up

In this example of mock-up the economic operator is specifying two representatives:

EO representatives - mock-up

Figure 233. EO representatives, mock-up

XSD Schema

In the The ESPD-EDM all the data regarding the representative of the economic operators is placed in the UBL-2.3 component cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney. In principle the elements expected by the ESPD-EDM are very few, only the ones represented in the mock-up above. However this UBL element provides other possibilities that may be used in the future or for other purposes (or as a national extension of the ESPD).

Thus, additionally to the expected elements, the cac:PowerOfAttorney component caters also for, at least, two other data could be required at some point (e.g. cac:MandateDocumentReference, see figure below):

  • The place of registration of the representative. The logic first element to look at is the place of birth (this is one of the expected elements). But other elements could be used complementarily: (i) cac:Person/cac:IdentityDocumentReference (A reference to a document that can precisely identify this person (e.g., a residence certificate), (ii) cac:Person/cbc:NationalityID, and/or cac:Person/cbc:CitizenshipCountry.

  • Official documentation demonstrating that the person representing has an authentic mandate (e.g. a reference to a register where this mandate is located). For this the element cac:/PowerOfAttorney/cac:MandateDocumentReference should be used.

EO representatives Power of Attorney

Figure 234. EO representatives Power of Attorney, XSD Schema

Notice that the largest part of the data is held in the component cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney/cac:AgentParty/cac:Person. The figure below shows (in blue) the expected elements. See the table "Expecte Elements" and the XML example below for the details (e.g. how to use the cac:Person/cac:Contact element to contact the representative.

EO representatives - element Person

Figure 235. EO representatives - element Person, XSD Schema

Contact elements, such as telephone and e-mail are in the cac:Contact associated to the the cac:Person information element:

EO representatives - element Contact

Figure 236. EO representatives - element Contact, inside Person, XSD Schema

Expected Elements

Table 39. Representatives of the economic operator, expected elements

Class name:

cac:PowerOfAttorney

Definition:

Official or legal mandate issued by an authority (e.g. an attorney or a notary) to represent the economic operator as a representative of the economic operator in public procurement procedures.

Business rule(s):

Common (BR-RESP-20)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party/cac:PowerOfAttorney

Context of use:

The economic operator in the ESPD Response document. Use this element to refer to the natural persons that represent the economic operator. See requirement tbr92-018.

Components Type Card Description Requirements

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:FirstName

Text

1

Name of the natural person.

Information Requirement: tbr92-009 Rule: Name of the natural person is mandatory.

Rule scope: Common (BR-RESP-20-01)

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:FamilyName

Text

1

Family Name of the natural person.

Information Requirement: tbr92-009

Rule: Family Name of the natural person is mandatory.

Rule scope: Common (BR-RESP-20-02)

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:BirthDate

Date

0..1

Date of birth of the natural person.

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:BirthplaceName

Text

0..1

Place of birth of the natural person.

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cac:AddressLine

Text

0..1

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

Information Requirement: tbr92-009

Rule: Use it to specify the street name and number of the building of the representative natural person in one line. Beware that specifying the address of a natural person might enter in conflict with the current Data Protection rules.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cbc:PostalZone

Text

0..1

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

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cbc:CityName

Text

0..1

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

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/ cac:Country/cbc:IdentificationCode

Code

1

A code that identifies the country.

Information Requirement: tbr92-009

Rule: Compulsory use of the Code List Country.

Rule scope: Common (BR-RESP-20-03, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/ cac:Country/cbc:Name

Text

0..1

The name of the country.

Information Requirement: tbr92-009

Rule: Try to use the name provided in the Code List Country and in the language of the user.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:Contact/cbc:ElectronicMail

Text

0..1

An e-mail address for the contact point.

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:Contact/cbc:Telephone

Text

0..1

A phone number for the contact point.

Information Requirement: tbr92-009

Rule: None.

cac:PowerOfAttorney/cbc:Description

Text

0..n

The short description for the role of the economic operstors representative and other detailed information on the representation.

Information Requirement: tbr92-010

Rule: Use line 1 of the description to describe the role of the representative. Use line 2 to provide detailed information on the representation (its forms, extent, purpose, etc.)

Data Structure

None, all the data is placed in the UBL-2.3 component cac:PowerOfAttorney

XML Example

Notice that this XML example contains two representatives, as in the mock-up.

Economic operator’s representatives

<!-- Economic Operator Data -->

<cac:EconomicOperatorParty>

<cac:QualifyingParty>

<cbc:EmployeeQuantity>12167</cbc:EmployeeQuantity>

<cac:FinancialCapability><cbc:ValueAmount currencyID="EUR">1203000000</cbc:ValueAmount></cac:FinancialCapability>

<cac:Party>

<!-- This EO company is NOT an SME -->

<cbc:IndustryClassificationCode listID="economic-operator-size" listAgencyID="OP" listVersionID="20210317-0">large</cbc:IndustryClassificationCode>

<!-- Notice that the ID and Name of the Pre-Qualification System is in the attributes. They would be captured from e-Certis. -->

<cac:PartyIdentification>

<cbc:ID schemeID="VAT" schemeAgencyID="ROLECE" schemeAgencyName="Registro Oficial de Licitadores y Empresas Clasificadas del Estado">B82387770</cbc:ID>

</cac:PartyIdentification>

</cac:Party>

</cac:QualifyingParty>

<cac:EconomicOperatorRole>

<cbc:RoleCode listID="http://publications.europa.eu/resource/authority/eo-role-type" listAgencyID="OP" listVersionID="20211208-0">sole-tenderer</cbc:RoleCode>

<cbc:RoleDescription>Sole entity or, in case of Consortium, Joint Venture or other types of groups, the leader of the group.</cbc:RoleDescription>

</cac:EconomicOperatorRole>

<cac:Party>

<cbc:WebsiteURI>https://everis.com/global/en</cbc:WebsiteURI>

<cac:PartyIdentification>

<cbc:ID schemeAgencyID="VAT" schemeAgencyName="EU-COM-GROW" schemeID="VIES" schemeURI="link:http://ec.europa.eu/taxation_customs/vies/vieshome.do?locale=es" schemeName="VAT number">B82387770</cbc:ID>

</cac:PartyIdentification>

<cac:PartyName><cbc:Name>Everis, Spain, S.L.U.</cbc:Name></cac:PartyName>

<cac:PostalAddress>

<cbc:CityName>Madrid</cbc:CityName>

<cbc:PostalZone>28050</cbc:PostalZone>

<cac:AddressLine>

<cbc:Line>Manoteras, 52</cbc:Line>

</cac:AddressLine>

<cac:Country>

<cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">ESP</cbc:IdentificationCode>

<cbc:Name>Spain</cbc:Name>

</cac:Country>

</cac:PostalAddress>

<cac:Contact>

<cbc:Name>Xavi Ker; Ruth Gomis; Miguel Verde</cbc:Name>

<cbc:Telephone>+34 91 749 00 00</cbc:Telephone>

<cbc:ElectronicMail>Spain.Proposals.Office@everis.com</cbc:ElectronicMail>

</cac:Contact>

<!-- REPRESENTATIVES of the Economic Operator -->

<!-- Representative 1 -->

<cac:PowerOfAttorney>

<cbc:Description>Total powers to make decisions on behalf of the company.</cbc:Description>

<cbc:Description>Main legal representative with power to make decisions about any aspect related to public procurement contracts with public administrations.</cbc:Description>

<cac:AgentParty>

<cac:Person>

<cbc:FirstName>Mary A.</cbc:FirstName>

<cbc:FamilyName>Smith</cbc:FamilyName>

<cbc:BirthDate>1980-07-17</cbc:BirthDate>

<!-- No element for "street and number" present. The user decided not to provide it -->

<cbc:BirthplaceName>Brussels</cbc:BirthplaceName>

<cac:Contact>

<cbc:Telephone>+322124522</cbc:Telephone>

<cbc:ElectronicMail>masmith@everis.com</cbc:ElectronicMail>

</cac:Contact>

<cac:ResidenceAddress>

<cbc:CityName>Brussels</cbc:CityName>

<cbc:PostalZone>1000</cbc:PostalZone>

<cac:Country>

<cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">BEL</cbc:IdentificationCode>

<cbc:Name languageID="en">Belgium</cbc:Name>

</cac:Country>

</cac:ResidenceAddress>

</cac:Person>

</cac:AgentParty>

</cac:PowerOfAttorney>

<!-- Representative 2 -->

<cac:PowerOfAttorney>

<cbc:Description>Public Sector Responsible Manager</cbc:Description>

<cbc:Description>Can sign contracts with the buyer on behalf of the Consortium.</cbc:Description>

<cac:AgentParty>

<cac:Person>

<cbc:FirstName>Sergi</cbc:FirstName>

<cbc:FamilyName>Mallol</cbc:FamilyName>

<cbc:BirthDate>1960-06-21</cbc:BirthDate>

<cbc:BirthplaceName>Barcelona</cbc:BirthplaceName>

<cac:Contact>

<cbc:Telephone>+34934947700</cbc:Telephone>

<cbc:ElectronicMail>sergi.mallol@everis.com</cbc:ElectronicMail>

</cac:Contact>

<cac:ResidenceAddress>

<cbc:CityName>Barcelona</cbc:CityName>

<cbc:PostalZone>08020</cbc:PostalZone>

<cac:Country>

<cbc:IdentificationCode listID="http://publications.europa.eu/resource/authority/country" listAgencyID="OP" listVersionID="20211208-0">>ESP</cbc:IdentificationCode>

<cbc:Name languageID="en">Spain</cbc:Name>

</cac:Country>

</cac:ResidenceAddress>

</cac:Person>

</cac:AgentParty>

</cac:PowerOfAttorney>

</cac:Party>

</cac:EconomicOperatorParty>

<!-- Exclusion and selection Criteria, Responses and Evidences removed for the sake of brevity -->
  1. First Name of the natural person that represents the economic operator.

  2. Data of birth of the natural person that represents the economic operator.

  3. Notice that no street name and building number or postbox was provided. Hence the element cac:AddressLine has not been instantiated in this XML document.

  4. Postal or zip code in the city where the natural person lives.

  5. Name of the city where the natural person lives.

  6. Code representing the country where the natural person lives.

  7. Second line of the cac:Description element reserved to hold the additional information providing detailed information about the representation (such as the extent of the representation, its forms, purposes, etc.).

  8. The family name of the natural person that represents the economic operator.

  9. Name of the place where the natural person representing the EO was born. This can be used to further identify the natural person.

  10. Electronic mail of the natural person.

  11. Telephone number of the natural person.

  12. Firts line of the cac:Description element reserved to hold the 'representation' role the natural person plays for this economic operator.

6.7. Answering QUESTIONs

REQUIREMENT

The ESPD Response must include one criterion response (one answer), and only one, linked to one, and only one, criterion property (one QUESTION) copied from the ESPD Request into the ESPD Response document; and to each criterion property added by the economic operator to the ESDP Response.

One criterion response, though, may contain a list of response values of the same type.

REQUIREMENT

If the response to a criterion property is marked as confidential the evidences linked to this criterion property must also be treated as confidential.

The section Data Structures established a mapping between each data structure elements 'label' and the corresponding UBL-2.3 XML element of the cac:TenderingCriterion component. Thus:

  • REQUIREMENT_GROUP and QUESTION_GROUP are mapped to cac:TenderingCriterionPropertyGroup;

  • REQUIREMENT_SUBGROUP and QUESTION_SUBGROUP are mapped to cac:SubsidiaryTenderingCriterionPropertyGroup; and

  • REQUIREMENT and QUESTION are mapped to cac:TenderingCriterionProperty.

If you have a look at the data structure tables (the fragments of spread-sheets in previous chapters), you will observe that all groups and subgroups have a UUID associated. These UUID are generated by e-Certis and identify the structure inside the group or subgroup.

In the same data structures REQUIREMENT(s) and QUESTION(s) do not have a UUID assigned. This is because the UUID for each cac:TenderingCriterionProperty element has to be generated dynamically: each criterion property needs a unique identifier. The reasons are:

  1. In the UBL-2.3 model the answers are separated from inside the criterion. This differs from the previous models of the ESPD-EDM. The motivation for this separation was to allow drafting QualificationApplicationResponse documents without having to copy every criterion from the QualificationApplicationRequest, having in mind other scenarios different to the European Single Procurement Document. This could be used, perhaps, by public administrations that would like to use the UBL-2.3 XSDs for "under-the-threshold contract" ESPDs. Even in that situation the QualificationApplicationResponse would need to refer to the specific QualificationApplicationRequest instance (so the UUIDs are exactly the ones that were automatically generated for that instance). Remember that this is not possible in the ESPD-EDM, as there is a specific requirement asking to copy every criterion from the QualificationApplicationRequest into the QualificationApplicationResponse; see this business requirement at the beginning of the section.

  2. If the UUID of cac:TenderingCriterionProperty was 'fixed' (as are the groups and subgroups) one answer could refer to more than one REQUIREMENT or QUESTION; and this is not permissible (see business requirement above, one criterion property → one answer, one answer → one criterion property).

XSD Schema

To answer a QUESTION the ESPD-EDM uses the UBL-2.3 component cac:TenderingCriterionResponse. The expected elements are highlighted in blue in the figure below:

cac:TenderingCriterionResponse XSD element

Figure 237. cac:TenderingCriterionResponse XSD element

To answer one QUESTION one of the different possible types of values from the cac:ResponseValue element (inside the cac:TenderingCriterionResponse) must be selected. In other words, the types of elements inside the cac:ResponseValue are all disjoint amongst themselves.

If the need is to build a list of values, a sequence of cac:ResponseValues shall be instantiated. See XML examples below.

cac:ResponseValue XSD element

Figure 238. cac:ResponseValue XSD element

The cac:ApplicablePeriod is used to hold the start date and the end-date provided by the economic operator to a QUESTION for which the expected data is of type 'PERIOD'. (See expected types in the Code List ResponseDataType).

Note for the future

Future versions of UBL could consider moving this element inside the element cac:ResponseValue and rename it appropriately (or come up with a design approach different to the current one).

cac:ApplicablePeriod XSD element

Figure 239. cac:ApplicablePeriod XSD element

One answer to one QUESTION may be linked to multiple evidences. The XSD diagram below shows that to make this link possible the element cac:TenderingCriterionResponse element associates a class cac:EvidenceSupplied. This class contains only one basic information element, a cbc:ID. In UBL, except for cbc:Description, basic information elements (typically prefixed as cbc:) cannot be of multiple cardinality, but associated classes can. Thus the need to place the cbc:ID inside a class. This ID points at an instance of cac:Evidence present in the XML.

This design is an interesting feature as, by separating the evidence object instances from inside the response, one evidence may be used for different criteria. See the component cac:Evidence below in the section "8. Evidences". See also XML examples.

cac:EvidenceSupplied XSD element

Figure 240. cac:EvidenceSupplied XSD element

Mock-ups and data structures

The answers to QUESTION(s) are provided in the example mock-ups of the previous sections about how the buyer specify REQUIREMENT(s) and QUESTION(s), and how the economic operator adds or removes instances of elements (such as data on the economic operator, references to similar works and services, etc. Please refer to those mock-ups and compare the values shown in the fields reserved for the EO to answer and compare those values with the ones in the example XML snippets below.

Responses are not associated to ESPD custom data structures. All the values regarding an answer are always placed in one instance of the UBL-2.3 data element cac:TenderingCriterionResponse.

Expected Elements

Table 40. Elements expected in an answer to a criterion property

Class name:

cac:TenderingCriterionResponse

Definition:

A class to describe a response to a criterion property.

Business rule(s):

BR-RESP-80, BR-RESP-80-S10, BR-RESP-80-S20, Common (BR-LEAD-10)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:TenderingCriterionResponse

Context of use:

The economic operator uses it in the ESPD Response document to answer a QUESTION. tbr92-018, tbr92-007, tbr92-005, tbr92-006.

Components Type Card Description Requirements

cbc:ID

Identifier

0..1

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.

Rule: This ID SHOULD be provided by the EO or the service provider that instantiates the ESPDResponse XML document.

Rule scope: Common (BR-TCR-05, BR-OTH-02)

cbc:ValidatedCriterionPropertyID

Identifier

1

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

Rule: This ID MUST point at one of the TenderingCriterionProperty/cbc:ID that were included in the Request document.

Rule scope: 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)

cbc:ConfidentialityLevelCode

Code

0..1

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

Rule: If the value is true, all the evidences associated to this response becomes also confidential.

Rule scope: BR-TCR-02, BR-OTH-01, BR-OTH-01#19, BR-OTH-03

cac:ResponseValue

Associated class

0..n

A class to describe the criterion property response value.

Information Requirement: tbr92-018

Rule: This class contains the main disjoint elements used to provide the actual answer. The UBL-2.3 model provides cardinality 0..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. Beware that the cardinality is flexible (0..whatever) because some responses are not simple values, like the ones but complex ones, e.g. cac:ApplicablePeriod and cac:EvidenceSupplied).

Rule scope: Common (BR-TCR-08, BR-TCR-04)

cac:ApplicablePeriod

Associated class

0..1

A class for the economic operator to specify the start date and the end-date when the expected answer to a criterion property is a lapse of time.

Information Requirement: tbr92-018

Rule: The ESPD-EDM does only expect start date and end date. Software applications may take leverage of the richness of this class though for other purposes beyond the scope of this specification.

cac:EvidenceSupplied

Associated class

0..1

A reference to the evidence supporting this criterion property response.

Information Requirement: tbr92-017

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

| a| Disjointness of the elements inside cac:ResponseValue

Beware that one 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).

Thus, for example, if in the ESPD Request the expected type is DESCRIPTION the cac:ResponseValue must use the element cbc:Description, if INDICATOR cbc:ResponseIndicator, if IDENTIFIER cbc:ResponseID, etc.

See the codes used for cac:ValueDataTypeCode in the Code List ResponseDataType. For the different possible values in the response see the XSD diagrams above and the list of the expected elements in cac:ResponseValue in the table below.

This disjointness rule applies to the type of the value, but not to the values of the same type. Thus, for lists of values that constitute the actual answer (e.g. the list of LotIDs the economic operator tenders to, or a list of CPV codes to describe with granularity an activity), a sequence of cac:ResponseValues shall be instantiated in the XML. See the XML examples below.

Table 41. Elements expected in the 'cac:ApplicablePeriod' class

Class name:

cac:Period

Definition:

A class to describe a period of time.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:TenderingCriterionResponse/cac:ApplicablePeriod

Context of use:

A class for the economic operator to specify the start date and the end-date when the expected answer to a criterion property is a lapse of time; tbr92-018.

Components Type Card Description Requirements

cbc:StartDate

Date

0..1

The date on which this period begins.

Information Requirement: tbr92-018

Rule: Expected format 'YYYY-MM-DD'.

cbc:EndDate

Date

0..1

The date on which this period ends.

Information Requirement: tbr92-018

Rule: Expected format 'YYYY-MM-DD'.

Table 42. Elements expected in the 'cac:EvidenceSupplied' class

Class name:

cac:EvidenceSupplied

Definition:

A reference to the evidence supporting this criterion property response.

Business rule(s):

None

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:TenderingCriterionResponse/cac:EvidenceSupplied

Context of use:

Used to refer to one ore more evidences that are present in the QualificationApplicationResponse XML instance; tbr92-017.

Components Type Card Description Requirements

cbc:ID

Identifier

1

The identifier of the referenced evidence.

Information Requirement: tbr92-018

Rule: The expected identifier must match the value of a cac:Evidence/cbc:ID present in the XML document.

Rule scope: Common (BR-TCR-09, BR-OTH-0)

The table below lists the elements expected in the sub-class cac:ResponseValue. Remember that the elements of distinct types are all disjoint amongst themselves: i.e. you cannot associate one amount AND one indicator to the same cac:TenderingCriterionProperty element (but several values for elements of one type may be used to build up lists, e.g. lists of Lots and lists of CPV codes).

Table 43. Elements expected in the 'cac:ResponseValue' class

Class name:

cac:ResponseValue

Definition:

A class to describe the criterion property response value.

Business rule(s):

Common (BR-TCR-08, BR-TCR-04)

File:

ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd

Path:

/QualificationApplicationResponse/cac:TenderingCriterionResponse/cac:ResponseValue

Context of use:

Used to specify one value or a collection of values (in the case of a list) as a response to one, and only one, cac:TenderingCriterionProperty that is typified as a QUESTION.

Components Type Card Description Requirements

cbc:ID

Identifier

0..1

An identifier to refer to this criterion response value.

Information Requirement: tbr92-018

Rule: Recommendation: use a UUDI-version 4 number.

Rule scope: BR-TCR-05

cbc:Description

Text

0..n

A description used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: The ESPD-EDM uses this element to place a response that is a string. UBL-2.3 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.

cbc:ResponseAmount

Amount

0..1

An amount used as a reply to the criterion property.

Information Requirement: tbr92-018

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

Rule scope: Common (BR-OTH-01, BR-OTH-01#17, BR-OTH-03)

cbc:ResponseCode

Code

0..1

A code used as a reply to the criterion property.

Information Requirement: tbr92-018

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

Rule scope: Common (BR-OTH-01)

cbc:ResponseDate

Date

0..1

A date used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: Format 'YYYY-MM-DD'.

cbc:ResponseTime

Time

0..1

A time used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: Format 'HH:MM:SS'.

cbc:ResponseID

Identifier

0..1

An identifier used as a reply to the criterion property.

Information Requirement: tbr92-018

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

cbc:ResponseIndicator

Indicator

0..1

An indicator used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: The only possible values are False and True.

Rule scope: Common (BR-TCR-06, BR-TCR-07)

cbc:ResponseMeasure

Measure

0..1

A measure used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: None.

cbc:ResponseNumeric

Numeric

0..1

A number used as a reply to the criterion property.

Information Requirement: tbr92-018

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

cbc:ResponseQuantity

Quantity

0..1

A quantity used as a reply to the criterion property.

Information Requirement: tbr92-018

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

cbc:ResponseURI

URI

0..1

A URI used as a reply to the criterion property.

Information Requirement: tbr92-018

Rule: None.

Request/Response XML Example

To start with a simple example let us re-take the last case presented in section Reduction of candidates.

The first thing to take into account is that the responses go at the end of the document, just after the last set of REQUIREMENT(s) and QUESTION(s) that were copied from the ESPD-Request into the ESPD-Response, and before the evidences.

The second important thing is to keep in mind is that each response is linked to one, and only one, QUESTION via the identifier of that QUESTION.

Having said this, imagine that the following snippet of XML code is the last criterion from the ESPD-Request that has been instantiated in your ESPD-Response (pay attention to the bullets and comments under the example).

Reduction of Candidates - (QUESTION(s) in the ESPD-Request)

<!-- ... beginning of document removed for brevity -->

<!-- Criterion:Reduction of the number of qualified candidates -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">51c39ba9-0444-4967-afe9-36f753b30175</cbc:ID>
                <cbc:CriterionTypeCode listID="http://publications.europa.eu/resource/authority/criterion" listAgencyID="OP" listVersionID="20210616-0">staff-red</cbc:CriterionTypeCode>
                <cbc:Name>Reduction of the number of qualified candidates</cbc:Name>
                <cbc:Description>The economic operator declares that It meets the objective and non discriminatory criteria or rules to be applied in order to limit the number of candidates in the following way:</cbc:Description>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00000</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:ProcurementProjectLotReference>
                        <cbc:ID schemeID="Criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">LOT-00001</cbc:ID>
                </cac:ProcurementProjectLotReference>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ecc69670-f428-4446-908f-689568ca0d0d</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">de82e45f-a0f6-43a6-9761-bfae3385fd1d</cbc:ID>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">f13754df-7e15-4155-aaa6-7ca6407baa47</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">ffc141f8-5ffe-4492-9066-7ff5dd633583</cbc:ID>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">01a08984-328f-4bc8-88d9-56634e66ca3c</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="property-group-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="criterion" schemeAgencyID="EU-COM-GROW" schemeVersionID="3.0.1">fe61b9a7-9e60-45eb-98c9-cd7102a86013</cbc:ID>
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="criterion-element-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="response-data-type" listAgencyID="EU-COM-GROW" listVersionID="3.0.1">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>