The European Single Procurement Document

XML Implementation Guide v2.1.0

I. Introduction

I.1 Objectives and scope

I.1.1 The Directive

Article 59 of the new Public Procurement Directive 2014/24/EC (henceforth 'the Directive') introduced a new concept, the European Single Procurement Document (ESPD) which is a self-declaration document intended for preliminary evidence in a public procurement procedure. By mapping out equivalent certificates between MS, the ESPD replaces certificates issued by public authorities or a third party involved in a procedure. It is thus a valuable facilitator for cross-border participation of a greater number of potential operators in public procurement procedures and a valuable tool for integrating the European Single Market.

The European Commission (EC) has developed a data model and 'semantic assets' for the exchange of the ESPD between any Procurement stakeholder’s system. This document illustrates in detail how to use the model and assets in compliance with the Directive.

The model, named ESPD-EDM (standing for European Single Procurement Document - Exchange Data Model) defines two electronic (XML) documents:

The ESPD Request, a document providing information about the contracting authority, the procurement procedure and the exclusion and selection criteria established for the procurement procedure.

The ESPD Response, the document that is filled-in by the Economic Operators stating whether they fulfill or not the criteria required in the ESPDRequest, and providing the sources where evidences can be obtained to prove that the criteria are met.

This guide is intended to facilitate the understanding of the model underlying the implementation of the ESPD Request and ESPD Response XML documents. With that objective in mind the reader is provided with examples and rules relating to how the content of ESPD XML document should look like and be processed.

The content of the guide is mainly addressed to the development teams from the Member States, economic operators, information providers or any other party interested in understanding how the ESPD Exchange Data Model works and how to use it to produce XML instances of ESPD Request and ESPD Response documents.

I.1.2 Contracts above the threshold and below the threshold

The Directive (namely Article 4) regulates in detail those public procurement procedures which values of contract exceed certain amounts. These amounts, also known as 'thresholds', vary depending on the type of the contract and of the administration level of the contracting authority.

Those contracts that fall under this article 4 of the Directive are called contracts 'above the threshold', and the rest are known as contracts 'below the threshold'.

The ESPD-EDM is rich and flexible enough so as to allow ESPD instances for contracts above and below the threshold. However this document is oriented exclusively to illustrate how to create ESPD electronic documents for contracts above the threshold.

I.2 ESPD conformant solutions

The main objective of the ESPD documents is to reduce the administrative burden and lead to considerable simplification of participation in public procurement procedures for buyers and suppliers. In order to make full use of the ESPD concept, Member States (MS) and private sector companies (service providers) are developing software and on-line services to help contracting authorities and economic operators draft interoperable ESPD electronic documents. These solutions will reduce that burden by removing the need to produce a substantial number of certificates and documentation related to exclusion and selection criteria. This will answer to obstacles reported by many suppliers and especially SMEs.

For these software solutions to be interoperable they will have to conform to the indications set in this guide.

The ESPD International Knowledge Base (ESPDint) is a consortium formed by Member States, Universities and private organisations the objectives of which are to develop (i) a formal specification for the CEN BII profile 56 and ESPD requirements by DG GROW; and (ii) a software solution for the edition and exchange of ESPD electronic documents.The software solutions provided by the ESPDInt initiative refers to this XML instantiation guide. In turn, this ESPD-EDM XML implementation guide is aligned with the specification produced by the ESPDint initiative. Thus:

Formal requirements introduced in this guide are taken from (and point at) the requirements specified in the document BIS 41 - European Single Procurement Document; whereas
Formal definitions are taken from the ESPD-VCD Domain Vocabulary.

I.3 The ESPD Profile

The ESPD profile realises the ESPD process, which is is part of the qualification process in the pre-awarding process area. This is represented in the diagram below:

Figure 1. ESPD Business Process (source ESPDint)

The roles that participate as business partners in this process are mainly:

The Buyer (or ESDP requester) normally a governmental organisation like a contracting authority who prepares the procurement procedure requirements in a ESPD Request (electronic document QualificationApplicationRequest); and
The Supplier (i.e. economic operators), or ESPD Providers acting on behalf of them, who answer in an ESPD Response (electronic document QualificationApplicationResponse).

Figure 2. Actors in the ESPD business process (source ESPDint)

This other figure below shows the choreography of the business process implemented by the profile. The choreography of business collaborations defines the sequence of interactions when the profile is run within its context.

Figure 3. ESPD business process coreography (source ESPDint)

I.4 Regulated and Self-contained ESPDs

REQUIREMENT

The CA must be able to select the type of ESPD (regulated or self-contained)

This new version of the eESPD makes the difference between “regulated” and “self-contained” ESPD.

Regulated ESPDs are those XML document instances the structure and content of which are strictly adjusted to the terms expressed in the Annex 2 of the Commission Implementing Regulation (EU) 2016/7: Standard form for the European Single Procurement document (ESPD).

A Regulated ESPD usually refers to documents and information that are external; i.e. it uses sentences like "mentioned in the Contract Notice published or the Contract Documents". The criteria of a Regulated ESPD are all defined in eCertis and their structure never changes.

In a Self-contained ESPD all the information needed for an ESPD Request is either contained in other parts of the document or the document refers to the authentic online source from where to obtain it. Thus the criteria and requirements that are particular to the MS or to the contracting authority, generic to all Procurement Procedures or particular of the Procurement Procedure, are explicitly mentioned or defined in the ESPD Request document.

Additionally, in a Self-contained ESPD the Member State and the contracting authority are able to introduce requirements that are particular to the national legislation or the procurement procedure. Self-contained eESPDs confer the contracting authorities a greater flexibility when preparing their eESPD Request documents.

Thus, in the case of exclusion grounds, the Member States can define in eCertis national exclusion criteria and link them to the corresponding European criteria defined in the Directives.

In the case of selection criteria, the contracting authority may introduce requirements for certain requirements (e.g. regarding turnovers, financial ratios, or references) to specify expected minimum amounts, specific types of ratios, minimum number of references, or other requirements).

This document provides descriptions about some of these situations, mock-ups and XML examples to illustrate the differences between Regulated and Self-contained ESPDs and to clarify when and how to use them.

See also section "III. The ESPD Request document" for details on how to specify the type of ESPD in an XML instance of an ESPD Request document.

Mock-up

Software applications need to be aware of this new feature introduced by the V2.1.0 of the ESPD-EDM. Depending on whether the ESPD Request document that is being prepared is regulated or self-contained, a software application should behave in different ways; e.g. for Self-contained ESPD documents, the application should allow the contracting body to define requirements for some selection criteria that are specific to the procurement procedure.

One suggestion for a Graphical User Interface (GUI) aimed at editing ESPD Request documents is to facilitate the contracting body the selection of the type of ESPD Request in an initial page:

Figure 4. Regulated or Self-contained ESPD, mock-up

II. The ESPD Semantic Assets

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

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

Figure 5. Distribution (dist) package

art: contains graphical resources used to document the distribution;
cl: reference data (codelists) used by the XML instances. It also contains a spread-sheet with all the ESPD criteria structured. This spread-sheet can be used to automatically generate ESPD XML instances.
doc: contains this document (and other documents to support developers);
mod: UBL-2.2 model specified in spread-sheets;
val: validation artefacts (eg. ISO Schematron and OASIS Genericode CVA files);
xml: samples of ESPD XML instances for illustrative and testing purposes;
xsd: the UBL-2.2 XSD Schemas, documented (annotated) version;
xsdrt: the UBL-2.2 XSD Schemas, runtime version;
xslt: transformation stylesheets used to generate basic sample XML instances from the criteria defined in spreadsheets REGULATED ESPD data structures and SELF-CONTAINED ESPD data structures (see folder dist/cl).

II.2 Adoption of UBL-2.2

One important difference of this new version in respect of the previous versions of the ESPD-EDM is that the XSD Schemas used for the XML implementation of the Request and Response documents have been developed by OASIS UBL (ISO/IEC 19845) in close collaboration with the European Commission (EC).

The results of such collaboration have been included in the version 2.2 of UBL which is actually under revision and is to be formally adopted by the end of 2017.s

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 European Catalogue (EUcat): 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.

II.3 UBL-2.2 Documents and libraries

UBL-2.2 defines thousands of different information components and dozens of documents. This guide describes and illustrates only those elements from UBL-2.2 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.2 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.2 in two main libraries: Common Aggregate Components (file UBL-CommonAggregateComponents-Pre-award.xsd) and Common Basic Components (UBL-CommonBasicComponents-Pre-award.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.2 Technical Committee can be accessed here: https://www.oasis-open.org/committees/document.php?document_id=60554.

Beware also that the UBL-2.2 namespaces used for the two main documents in ESPD (and for the rest of UBL-2.2 XSD schemas are now final, since June 2018. Thus:

The ESPD-EDM v2.1.0 XSD Schemas use the namespace urn:oasis:names:specification:ubl:schema:xsd:*, whilst
The previous ESPD-EDM versions 2.0.* used the namespace urn:X-test:UBL:Pre-award:*.

II.4 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 epresents 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:

Identifiers point at specific occurrences of objects (instances); codes replace concepts;
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.
Identifiers are in principle maintained in the business domain, e.g. buyer identifiers, economic operator identifiers, exclusion or selection criteria identifiers, etc.
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:

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

Codes are normally maintained in "code lists". The ESPD-EDM keeps and distributes these code lists in three different formats:

In an Office Open XML (XLSX) file,
In an Open Office Document (ODS) file,
Genericode 1.0 (GC) files (one *.gc file per code list).

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:

Figure 6. Elements and metadata of an ESPD code list

The Annex II 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 V2.1.0 specification requires always three mandatory attributes: `listID`, `listAgencyID`, and `listVersionID`.

Table 2. ESPD Requirement regarding identifiers
REQUIREMENT:	For identifiers, this ESPD V2.1.0 specification requires at least (and always) the mandatory attribute `schemeAgencyID`. When identifying parties, like the Economic Operator, the Contracting Authority, 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.2 CCT are defined in the file CCTS_CCT_SchemaModule-2.2.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.

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 ESPD V2.1.0).
listAgencyID	An agency that maintains one or more lists of codes.
listAgencyName	The name of the agency that maintains the list of codes (MANDATORY in ESPD V2.1.0).
listName	The name of a list of codes.
listVersionID	The version of the list of codes (MANDATORY in ESPD V2.1.0).
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.

Figure 8. Identifier attributes

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

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 ESPD V2.1.0).
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.

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.2</cbc:UBLVersionID> (1)

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

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

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

<cbc:VersionID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1.0</cbc:VersionID> (5)

<cbc:ProcedureCode listID="ProcedureType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">OPEN</cbc:ProcedureCode> (6)

<cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode> (7)

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	Notice that for Codes, the three compulsory attributes are specified. For these codes. In this example the attributes are specifying that the code is maintained by DG GROW in a list named `ProcedureType` and that the version that has been used is version `2.1.0`which is distributed jointly with this ESPD-EDM V2.1.0 specification (in the distribution package).
7	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 `dist/cl` 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.2. cbc:CodeType element). This is case of code lists such as CurrencyCode, CountryCodeIdentifier, ProjectType, EORoleType, 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 Contracting Authorities, 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.2 element cbc:Identifier):

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…?"). See also section XML Example (SELF-CONTAINED economic operator) for a more complete example on this Criterion:

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

...

<cac:TenderingCriterionProperty>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1fa05728-308f-43b0-b547-c903ffb0a8af</cbc:ID>(1)
    <cbc:Description>ID of the economic operator</cbc:Description>
    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>(2)
</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.2. 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="2.0.2">acb58f0e-0fe4-4372-aa08-60d0c36bfcfe</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1fa05728-308f-43b0-b547-c903ffb0a8af</cbc:ValidatedCriterionPropertyID>(1)
    <cbc:ResponseID schemeID="VAT" schemeAgencyID="ES-AEAT">B82387770</cbc:ResponseID> (2)
 </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).

III. The ESPD Request document

III.1 ESPD Request Business Requirements

The ESPD-EDM V2.1.0 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.

III.2 ESPD Request XSD Schema

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

The figure below shows the XSD Schema defined by UBL-2.2 for the document “Qualification Application Request”. This schema replaces the Schema for the “ESPD Request” document used in the previous versions of the ESPD-EDM.

The figure below shows a diagram representing the UBL-2.2 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.

Figure 10. QualificationApplicationRequest XSD Schema, global view

LEGEND: The figure below enumerates the four different types of optionality and cardinality for the elements of the UBL-2.2 Schema:

Figure 11. Legend: QualificationApplicationRequest XSD Schema, possible cardinalities of the Schema elements

III.3 ESPD Request cardinalities

As you can see the UBL-2.2 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 V2.1.0 structure for the ESPD Request with its own cardinality restrictions. Notice that ESPD-EDM does not change anything else from the UBL-2.2 Schema.

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

If you compare both figures you will observe that:

The cardinalities of the root common basic components, such as cbc:ID, cbc:UUID, ProcedureCode, and cbc:QualificationApplicationTypeCode are different for the ESPD than for UBL-2.2;
Similarly, the cardinalities of aggregate components like cac:ContractingParty, cac:ProcurementProjectLot and cac:TenderingCriterion are different to the UBL-2.2 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 V2.1.0 distribution package provides Schematron schemata and CVA files ^[1] for the validation of the XML instances (folder dist/val).

III.4 Root elements

The table below lists the elements that are expected in the ESPD Response V2.1.0 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".

If you need to well understand where the business rules come from and how they are implemented and executed you should read the following content in the order indicated:

The ESPDint BIS document, Chapter Business Rules, where the rules are described in a narrative way, from the business perspective;
The ESPD Test Cases, where the ESPDint BIS rules are connected to each class and data element of the XML implementation Guide and "Test Cases" are defined as a previous step towards the specification of machine-readable rules (based on ISO-Schematron, see Annex I: XML Validation;
The ESPD Test Cases Mapping, where every business rule (previously identified and describe in the other two documents) is mapped to specific elements of the ESPD XSD Schemas, the severity of the error is indicate, the text of the validation-result message for the validation report, etc.; |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 V2.1.0
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:	dist/xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd

Components Type Card Description Requirements

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.2". 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: tbr070-001. 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 to 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 contracting authority, 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 contracting authority, 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: SELF-CONTAINED (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 contracting authority. This number in combination with a registered contracting authority ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure. Rule scope: REGULATED (BR-REG-10), SELF-CONTAINED (BR-SC-10)
cbc:IssueDate	Date	1	Date when the document was issued by the contracting authority.	Information Requirement: tbr070-002. Rule: Format "YYYY-MM-DD".
cbc:IssueTime	Time	0..1	Time when the document was issued by the contracting authority.	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	0..1	The type of the procurement administrative procedure according to the EU Directives.	Information Requirement: tbr070-007. Rule: Rule: Compulsory use of attributes listID, listAgencyName and listVersionID. Compulsory use of the code list ProcedureType (values: `Open`, `Restricted`, `Accelerated`, `Competitive dialogue`, etc.). Do not confound with the object of the procurement project (code list `ProjectType`: Works, Supplies, Services). Rule scope: SELF-CONTAINED (BR-SC-10#2, BR-OTH-03, BR-OTH-01, BR-OTH-01#1)
cbc:QualificationApplicationTypeCode	Code	1	The type of European Single Procurement Document (ESPD).	Information Requirement: tbr070-02. Rule: Compulsory use of the code list `QualificationApplicationType`. Compulsory use of attributes listID, listAgencyName and listVersionID. Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#2, BR-OTH-03)
cbc:WeightScoringMethodologyNote	Text	0..n	Free-form text to describing information about Weight Scoring Methodology.	Information Requirement: tbr070-016 Rule: Used for transparency motives. Provide a text explaining clearly the method that will be used to select those selection criteria that will be weighted. Rule scope: Common (BR-2P-10)
cbc:WeightingTypeCode	Code	0..1	A code specifying the type of the Weighting.	Information Requirement: tbr070-016 Rule: Compulsory use of the code list `WeightingType`. If this element it is not instantiated and one or more selection criteria are weighted the type defaults to `NUMERIC`. Rule scope: Common (BR-2P-10)
cac:ContractingParty	Associated class	1	The contracting authority or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU).	Information Requirement: tbr070-01. Rule: UBL-2.2 defines multiple cardinality ContractingParties presumably to allow joint procurements. However the ESPD only expects data about one buyer. The decision was made that in case of joint procurement the data collected in the ESPD would be about the leader of the joint procurement procedure.
cac:ProcurementProject	Associated class	0..1	An overall definition of the procurement procedure.	Information Requirement: tbr70-002. Rules: Use this component to identify and describe the procurement administrative procedure. The REGULATED version should not contain a `cac:ProcurementProject` in order to ensure the back-wards compatibility with the version 1.0.2. Use this component in case the ESPD is SELF-CONTAINED and the procedure is divided into lots. In this case use the `ProcurementProjectLot` component to provide details specific to the lot and reserve the `ProcurementProject` component to describe the global characteristics of the procedure.
cac:ProcurementProjectLot	Associated class	0..1	One of the procurement project lots into which this contract can be divided.	Information Requirement: tbr70-008. Rule: If there is only one single procurement project lot specified, the ESPD refers then to a procurement procedure without lots.
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: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.

cbc:UBLVersionID

Identifier

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

Information Requirement: tbr070-002.

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

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

cbc:CustomizationID

Identifier

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

Information Requirement: tbr070-001.

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

The identification and version of the ESPD Exchange Data Model used to create the to 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

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 contracting authority, 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 contracting authority, 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

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: SELF-CONTAINED (BR-OTH-02)

cbc:ContractFolderID

Identifier

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 contracting authority. This number in combination with a registered contracting authority ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.

Rule scope: REGULATED (BR-REG-10), SELF-CONTAINED (BR-SC-10)

cbc:IssueDate

Date

Date when the document was issued by the contracting authority.

Information Requirement: tbr070-002.

Rule: Format "YYYY-MM-DD".

cbc:IssueTime

Time

0..1

Time when the document was issued by the contracting authority.

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

0..1

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

Information Requirement: tbr070-007.

Rule: Rule: Compulsory use of attributes listID, listAgencyName and listVersionID. Compulsory use of the code list ProcedureType (values: Open, Restricted, Accelerated, Competitive dialogue, etc.). Do not confound with the object of the procurement project (code list ProjectType: Works, Supplies, Services).

Rule scope: SELF-CONTAINED (BR-SC-10#2, BR-OTH-03, BR-OTH-01, BR-OTH-01#1)

cbc:QualificationApplicationTypeCode

Code

The type of European Single Procurement Document (ESPD).

Information Requirement: tbr070-02.

Rule: Compulsory use of the code list QualificationApplicationType. Compulsory use of attributes listID, listAgencyName and listVersionID.

Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#2, BR-OTH-03)

cbc:WeightScoringMethodologyNote

Text

0..n

Free-form text to describing information about Weight Scoring Methodology.

Information Requirement: tbr070-016

Rule: Used for transparency motives. Provide a text explaining clearly the method that will be used to select those selection criteria that will be weighted.

Rule scope: Common (BR-2P-10)

cbc:WeightingTypeCode

Code

0..1

A code specifying the type of the Weighting.

Information Requirement: tbr070-016

Rule: Compulsory use of the code list WeightingType. If this element it is not instantiated and one or more selection criteria are weighted the type defaults to NUMERIC.

Rule scope: Common (BR-2P-10)

cac:ContractingParty

Associated class

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

Information Requirement: tbr070-01.

Rule: UBL-2.2 defines multiple cardinality ContractingParties presumably to allow joint procurements. However the ESPD only expects data about one buyer. The decision was made that in case of joint procurement the data collected in the ESPD would be about the leader of the joint procurement procedure.

cac:ProcurementProject

Associated class

0..1

An overall definition of the procurement procedure.

Information Requirement: tbr70-002.

Rules: Use this component to identify and describe the procurement administrative procedure. The REGULATED version should not contain a cac:ProcurementProject in order to ensure the back-wards compatibility with the version 1.0.2.

Use this component in case the ESPD is SELF-CONTAINED and the procedure is divided into lots. In this case use the ProcurementProjectLot component to provide details specific to the lot and reserve the ProcurementProject component to describe the global characteristics of the procedure.

cac:ProcurementProjectLot

Associated class

0..1

One of the procurement project lots into which this contract can be divided.

Information Requirement: tbr70-008.

Rule: If there is only one single procurement project lot specified, the ESPD refers then to a procurement procedure without lots.

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

The figure below shows a global view of an ESPD Request XML instance (all nodes have been 'collapsed' to simplify the view):

Figure 13. An ESPD Request XML instance (global view)

XML example

The XML snippet below shows how the beginning of an ESPD Request XML instance looks like

<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationRequest xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationRequest" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationRequest ../xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd">
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm070:ver3.0</cbc:CustomizationID>
        <!-- The transactional profile where the ESPD is used. ESPD-EDM-V2.1.0 refers to the CEN profile -->
        <cbc:ProfileID schemeAgencyID="CEN-BII">41</cbc:ProfileID>
        <!-- The identifier of this document provided by the contracing authority system -->
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>
        <!-- Indicator of whether this document is an original or a copy. In this case the document is the original -->
        <cbc:CopyIndicator>false</cbc:CopyIndicator>
        <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:IssueDate>2017-12-31</cbc:IssueDate>
        <cbc:IssueTime>19:09:11</cbc:IssueTime>
        <cbc:VersionID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1.0</cbc:VersionID>
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">OPEN</cbc:ProcedureCode>
        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>

...

III.5 EU and national publications

REQUIREMENT tbr070-007

The CA 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 national 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.

Figure 14. Publications, mock-up

XSD Schema

The ESPD EDM uses the UBL component cac:AdditionalReferenceDocument 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.2 Common Aggregate Components library).

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.

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:AdditionalReferenceDocument
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

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 `DocRefContentType`. 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 `LanguageCodeEU` 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 contracting authority.	Information Requirement: tbr92-013. Rule: Format "YYYY-MM-DD". If available in the referenced document place here the data of publication by the contracting authority.
cbc:IssueTime	Time	0..1	Time when the document was issued by the contracting authority.	Information Requirement: tbr92-013. Rule: If available in the referenced document place here the time of publication by the contracting authority.

cbc:ID

Identifier

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

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 DocRefContentType. 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 LanguageCodeEU 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 contracting authority.

Information Requirement: tbr92-013.

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

cbc:IssueTime

Time

0..1

Time when the document was issued by the contracting authority.

Information Requirement: tbr92-013. Rule: If available in the referenced document place here the time of publication by the contracting authority.

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:AdditionalReferenceDocument/cac:Attachment/cac:ExternalReference

Components Type Card Description Requirements

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)

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> (1)
                <cbc:DocumentTypeCode listID="DocRefContentType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">TED_CN</cbc:DocumentTypeCode> (2)
                <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> (3)
                        <cbc:FileName>Spain-Zamora: Repair and maintenance services</cbc:FileName>
                        <cbc:Description>Repair and maintenance services. Real estate services.</cbc:Description> (4)
                        <cbc:Description>293520-2017</cbc:Description>        (5)
                        </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> (6)
                <!-- Contract Notice (CN) published on a National Government Official Journal -->
                <cbc:DocumentTypeCode listID="DocRefContentType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NOJCN</cbc:DocumentTypeCode> (7)
                <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 `DocRefContentType` (see file `dist/cl/CodeLists-V2.1.0` in the distribution package). Beware that the name and content of this Code List has changed from the previous ESPD-EDM version 1.0.2. The code `TED_CEN`means 'Contract Notice published in TeD (Official Journal of the European Publications Office)'.
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 contracting authority.
7	In this case the code `NOJCN` means 'Contract Notice (CN) published on a National Government Official Journal' (see file CodeLists-V2.1.0) in the distribution package.

III.6 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 contracting authority, 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.2 to collect also data about the contracting authority contact, end-point, and other data possible in the ESPD.

Figure 17. Data about the procurer, mock-up

XSD Schema

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

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:

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.2 specification for the complete list of fields):

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:

Figure 21. cac:Contact, XSD Schema

Expected elements

Table 8. Contracting body, expected elements
Class name:	cac:ContractParty
Definition:	The contracting authority 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:
dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd	Path:

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

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:ContractingParty/cac:Party

Components Type Card Description Requirements

Components	Type	Card	Description	Requirements
cac:PartyIdentification/cbc:Identifier	Identifier	0..1	The national identifier of a contracting body as it is legally registered (e.g. VAT identification).	Information Requirement: tbr070-001. Rule: More than one identifier can be specified. When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system). 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 (contracting authority, 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)

cac:PartyIdentification/cbc:Identifier

Identifier

0..1

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

Information Requirement: tbr070-001.

Rule: More than one identifier can be specified. When possible use the VAT identification of the contracting body (see the VIES platform for a EU cross-border national VAT number verification system). 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 (contracting authority, service provider, economic operator) as an eDeliveryID.

cac:PartyName/cbc:Name

Text

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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. The lists of valid countries are registered with the ISO 3166-1 Maintenance agency, "Codes for the representation of names of countries and their subdivisions". It is recommended to use the Country Code ISO 3166-1 2A:2006 representation.	Information Requirement: tbr070-006. Rule: The country of the contracting body must always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006). 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.

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

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

Information Requirement: tbr070-006.

Rule: The country of the contracting body must always be specified. Compulsory use of the code list CountryCodeIdentifier (ISO 3166-1 2A:2006).

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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.

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.

XML example

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

...
<!--- Root elements eliminated for the sake of brevity -->
<cac:ContractingParty>
        <cac:Party>
                <cbc:WebsiteURI>www.defensa.gob.es</cbc:WebsiteURI>
                <cbc:EndpointID>www.defensa.gob.es/?p=3404</cbc:EndpointID>
                <cac:PartyIdentification>
                        <cbc:ID schemeAgencyID="VIES-AEAT">B82387770</cbc:ID> (1)
                </cac:PartyIdentification>
                <cac:PartyName>
                        <cbc:Name>Ministerio de Defensa</cbc:Name> (2)
                </cac:PartyName>
                <cac:PostalAddress>
                        <cbc:StreetName>Paseo de la Castellana, 109</cbc:StreetName>
                        <cbc:CityName>Madrid</cbc:CityName>
                        <cbc:PostalZone>28071</cbc:PostalZone>
                        <cac:Country><cbc:IdentificationCode listID="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ES</cbc:IdentificationCode></cac:Country> (3)
                </cac:PostalAddress>
                <cac:Contact>
                        <cbc:Name>Responsable de la compra pública</cbc:Name> (4)
                        <cbc:Telephone>913955000</cbc:Telephone>
                        <cbc:ElectronicMail>comprapublica@defensa.gob.es</cbc:ElectronicMail>
                </cac:Contact>
        </cac:Party>
</cac:ContractingParty>
...

1	The contracting body 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.
2	In the ESPD the official name of the contracting body is mandatory.
3	In the ESPD the country code (ES, in this example) is compulsory. You will need to use this code (ES) to verify the VAT number in the VIES service.
4	In this example the contracting body specifies a role, instead of the name of a person.

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

Differently to the previous version 1.0.2, the ESPD-EDM version 2.1.0 does not include the cac:ServiceProvider as a 'document root component'. Instead, it uses the UBL-2.2 cac:ContractingParty/cac:Party associated class cac:ServiceProviderParty.

XSD Schema

Figure 22. cac:ServiceProvider XSD Schema

Notice that:

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

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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:ContractingParty/cac:Party/cac:ServiceProviderParty/cac:Party

Components Type Card Description Requirements

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 (contracting authority, 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	Identifier	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 CountryCodeIdentifier (ISO 3166-1 2A:2006). Rule scope: SELF-CONTAINED (BR-REQ-20#7, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

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.

cac:PartyIdentification/cbc:ID

Identifier

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

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

Identifier

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 CountryCodeIdentifier (ISO 3166-1 2A:2006).

Rule scope: SELF-CONTAINED (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> (1)
                <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="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="2.1.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> (2)
                                        <cbc:ID schemeAgencyID="AEAT">B36699932</cbc:ID>
                                </cac:PartyIdentification>
                                <cac:PartyName> (3)
                                        <cbc:Name>Registro Oficial de Licitadores y Empresas Clasificadas (ROLECE)</cbc:Name></cac:PartyName>
                                <cac:PostalAddress> (4)
                                        <cac:Country><cbc:IdentificationCode listID="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ES</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 (ES, in this example) is compulsory. You will need to use this code (ES) to verify the VAT number in the VIES service.

III.8 Procurement Procedure: Regulated ESPD

REQUIREMENT

The contracting authority must be able to provide basic data about the Procurement Procedure

There are some important differences between the data collected for a Regulated ESPD Request and the data that can be required in a Self-contained ESPD Request.

Mock-up

For the Regulated ESDP REquest only three basic data are required: the title, a short description and the file (i.e. case) reference number attributed by the Contracting Authority to the procurement procedure.

The mock-up below shows a possible way of collecting this data:

Procurement Procedure in a Regulated ESPD

Figure 24. Procurement Procedure, data collected in a Regulated ESPD

XSD Schema

The figure below is a fragment of the QualificationApplicationRequest XSD Schema. The placeholders for the data expected in the Regulated ESPD Request have been highlighted (cbc:ContractFolderID and cac:ProcuementProject).

Figure 25. Procurement Procedure (Regulated ESPD). XSD Schema

Figure 26. Class cac:ProcurementProject (elements used in the Regulated ESPD). XSD Schema

Expected elements

As already explained when describing the root elements of the QualificationApplicationRequest document, the identification of the procurement procedure is compulsory for the ESPD documents. This is done by specifying the reference number that the contracting authority assigned to the procedure in the element cbc:ContracFolderID.

Table 13. Regulated ESPD Request: Procurement Procedure reference number
Class name:	QualificationApplicationRequest
Definition:	"A structured electronic business document for requesting qualification information through an ESPD (conform to an ESPD template). Directive 2014/24/EU, Art. 59." (ESPD Request transaction (Trdm070))
Business rule(s):	None
File:	dist/main/xsdrt/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd

Components

Type

Card

Description

Requirements

cbc:ContractFolderID

Identifier

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 this Qualification document is delivered as a response.

Information Requirement: tbr070-007.

Rule: Compulsory use of schemeAgencyID attribute. Although not mandatory, it is a good practice to identify the document wiht a UUID. Copies of a document should be identified with a different UUID.

Rule scope: REGULATED (BR-REG-10), SELF-CONTAINED (BR-SC-10)

The rest of the data related to the Regulated ESPD Request go in the cac:ProcurementProject class:

Table 14. Regulated ESPD Request: Procurement Procedure-related data
Class name:	cac:ProcurementProject
Definition:	An overall description of the procurement procedure.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd

Components	Type	Card	Description	Requirements
cbc:Name	Text	0..1	A title for the procurement procedure.	Information Requirement: tbr070-007. Rule: Use the same name that will be used for the Contract Notice. Rule scope: SELF-CONTAINED (BR-SC-10#1)
cbc:Description	Text	0..1	A descriptive text for the procurement procedure.	Information Requirement: tbr070-007. Rule: Use the same description that will be used for the Contract Notice.

Components

Type

Card

Description

Requirements

cbc:Name

Text

0..1

A title for the procurement procedure.

Information Requirement: tbr070-007.

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

Rule scope: SELF-CONTAINED (BR-SC-10#1)

cbc:Description

Text

0..1

A descriptive text for the procurement procedure.

Information Requirement: tbr070-007.

Rule: Use the same description that will be used for the Contract Notice.

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:Party></cac:ContractingParty>
        <cac:ProcurementProject>
                <cbc:Name>Spain-Aljaraque: Repair and maintenance services</cbc:Name>
                <cbc:Description>Repair and maintenance services. Real estate services.</cbc:Description>
</cac:ProcurementProject>
...

III.9 Procurement Procedure: Self-contained ESPD

REQUIREMENT

The CA must be able to provide the CPV codes to which the Procurement Procedure relates in the ESPDRequest

REQUIREMENT

The CA must be able to provide the object of the contract and the type of procedure

The Self-contained ESPD adds the possibility for the contracting authority to specify a few more data relevant at evaluation time and for the economic operator:

The CPV (Common Procurement Vocabulary) codes for the procurement procedure so the contracting authority can assess the classification of the economic operator; and for the economic operator to confirm that the procedure falls under its competences, skills or experience.
The 'Object of the contract' (i.e. the type of procurement project: execution of works, supply of products, provision of services). Software applications may use this information to, in a dynamic way, show or hide certain objects from the GUI; or to control the coherence of the XML content. Thus for example, if the object of the contract is 'works' it does not make sense to ask for references related to supplies of goods or services.
The 'Type of procedure' (e.g. Open procedure, Restricted procedure, Competitive procedure with negotiation, Competitive dialogue, Innovation partnership). The type of procedure can be used to control how to treat certain selection criteria. Thus for example, the weighting of technical and professional ability criteria is only used in two stages procedures.

Mock-up

The mock-up below show how this could be implemented in an GUI. Notice that more than one CPV code can be supplied by the contracting authority.

Procurement Procedure in a Self-contained ESPD

Figure 27. Procurement Procedure, data collected in a Regulated ESPD

XSD Schema

For the Self-contained ESPD Request, the 'Object of the contract' needs to be expressed as a code. This code is located in the cac:ProcurementProject class. As a matter of fact, the class provides two codes that allow to further refine the object of the contract: the cbc:ProcurementTypeCode and the cbc:ProcurementSubTypeCode. Thus you can specify things like 'Services' and 'Maintenance and repair services, or Land transport services, including armoured car services, and courier services, except transport of mail, or other', for example (see Code List ServicesProjectSubType in the Code Lists file).

The figure below shows the elements that can be used in a Self-contained ESPD. In blue those elements that are expected. See the UBL-2.2 XSD Schema for more elements in the cac:ProcurementProject class (e.g. the cac:AdditionalCommodityClassification class for other classifications beyond the CPV).

Figure 28. Procurement Procedure, elements used in a Self-contained ESPD

Expected elements

Table 15. Self-contained ESPD Request
Class name:	QualificationApplicationRequest
Definition:	"A structured electronic business document for requesting qualification information through an ESPD (conform to an ESPD template). Directive 2014/24/EU, Art. 59." (ESPD Request transaction (Trdm070))
Business rule(s):	None
File:	dist/main/xsdrt/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd

Components Type Card Description Requirements

Components	Type	Card	Description	Requirements
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 this Qualification document is delivered as a response.	Information Requirement: tbr070-007. Rule: Compulsory use of schemeAgencyID attribute. Although not mandatory, it is a good practice to identify the document with a UUID. Copies of a document should be identified with a different UUID. Rule scope: REGULATED (BR-REG-10), SELF-CONTAINED (BR-SC-10)
cbc:ProcedureCode	Identifier	1	The type of the procurement administrative procedure according to the EU Directives.	Information Requirement: tbr070-007. Rule: Compulsory use of the Code List `ProcedureType` (open procedure, restricted procedure, accelerated restricted procedure, competitive dialogue, negotiated procedure, etc.). Rule scope: SELF-CONTAINED (BR-SC-10#2, BR-OTH-03, BR-OTH-01, BR-OTH-01#1)

cbc:ContractFolderID

Identifier

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 this Qualification document is delivered as a response.

Information Requirement: tbr070-007.

Rule: Compulsory use of schemeAgencyID attribute. Although not mandatory, it is a good practice to identify the document with a UUID. Copies of a document should be identified with a different UUID.

Rule scope: REGULATED (BR-REG-10), SELF-CONTAINED (BR-SC-10)

cbc:ProcedureCode

Identifier

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

Information Requirement: tbr070-007.

Rule: Compulsory use of the Code List ProcedureType (open procedure, restricted procedure, accelerated restricted procedure, competitive dialogue, negotiated procedure, etc.).

Rule scope: SELF-CONTAINED (BR-SC-10#2, BR-OTH-03, BR-OTH-01, BR-OTH-01#1)

The rest of the data related to the Self-contained ESPD Request go in the cac:ProcurementProject class:

Table 16. Self-contained ESPD Request: Procurement Procedure-related data
Class name:	cac:ProcurementProject
Definition:	An overall description of the procurement procedure.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd

Components Type Card Description Requirements

Components	Type	Card	Description	Requirements
cbc:Name	Text	0..1	A title for the procurement procedure.	Information Requirement: tbr070-007. Rule: Use the same name that will be used for the Contract Notice. Rule scope: SELF-CONTAINED (BR-SC-10#1)
cbc:Description	Text	0..1	A descriptive text for the procurement procedure.	Information Requirement: tbr070-007. Rule: Use the same description that will be used for the Contract Notice.
cbc:ProcurementTypeCode	Code	0..1	A code to describe the object of the project (e.g. works, supplies, services, public work concessions, service concessions, other).	Information Requirement: tbr070-007. Rule: Compulsory use of the Code List `ProjectType`. Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#6, BR-OTH-03)
cbc:MainCommodityClassification	Class	0..n	A class to classify the works, services or supplies. The Self-contained ESPD uses it to assign CPV codes to works and services.	Information Requirement: tbr070-007. Rule: Use the element `cbc:ItemClassificationCode` for the specification of the CPV code. Beware that the cardinality of the basic element is 0..1 but the cardinality of the class is 0..n, thus allowing for multiple CPVs. Rule scope: SELF-CONTAINED (BR-SC-10#1, BR-OTH-01)

cbc:Name

Text

0..1

A title for the procurement procedure.

Information Requirement: tbr070-007.

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

Rule scope: SELF-CONTAINED (BR-SC-10#1)

cbc:Description

Text

0..1

A descriptive text for the procurement procedure.

Information Requirement: tbr070-007.

Rule: Use the same description that will be used for the Contract Notice.

cbc:ProcurementTypeCode

Code

0..1

A code to describe the object of the project (e.g. works, supplies, services, public work concessions, service concessions, other).

Information Requirement: tbr070-007.

Rule: Compulsory use of the Code List ProjectType.

Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#6, BR-OTH-03)

cbc:MainCommodityClassification

Class

0..n

A class to classify the works, services or supplies. The Self-contained ESPD uses it to assign CPV codes to works and services.

Information Requirement: tbr070-007.

Rule: Use the element cbc:ItemClassificationCode for the specification of the CPV code. Beware that the cardinality of the basic element is 0..1 but the cardinality of the class is 0..n, thus allowing for multiple CPVs.

Rule scope: SELF-CONTAINED (BR-SC-10#1, BR-OTH-01)

XML example

This fragment of XML shows how to supply data in a Self-contained ESPD Request XML document describing the procurement procedure.

<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationRequest xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationRequest" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationRequest ../xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd">
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm070:ver3.0</cbc:CustomizationID>
        <cbc:ProfileID schemeAgencyID="CEN-BII">41</cbc:ProfileID>
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>
        <cbc:CopyIndicator>false</cbc:CopyIndicator>
        <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:IssueDate>2017-12-31</cbc:IssueDate>

        <!-- The type of procedure: 1 stands for Open Procedure. See Code List 'ProcedureType' -->
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">1</cbc:ProcedureCode> (1)

        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>

        <!-- Contracting body data left empty for the sake of brevity -->
        <cac:ContractingParty><cac:Party/>        </cac:ContractingParty>

        <!-- Self-contained ESPD Request. Data about the procurement procedure -->
        <cac:ProcurementProject>
                <cbc:Name>Spain-Aljaraque: Repair and maintenance services</cbc:Name> (2)
                <cbc:Description>Repair and maintenance services. Real estate services.</cbc:Description> (3)
                <cbc:ProcurementTypeCode listID="ProjectType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">Services</cbc:ProcurementTypeCode> (4)

                <!-- CPV for 'Repair and maintenance services'. -->
                <cac:MainCommodityClassification><cbc:ItemClassificationCode>50000000</cbc:ItemClassificationCode></cac:MainCommodityClassification> (5)
                <!-- CPV for 'Real estate services'. -->
                <cac:MainCommodityClassification><cbc:ItemClassificationCode>70000000</cbc:ItemClassificationCode></cac:MainCommodityClassification> (6)
        </cac:ProcurementProject>
</QualificationApplicationRequest>

1	Use of the root element `cbc:ProcedureCode` to indicate that this is an 'Open procurement procedure'. The code is '1' according to the GROW’s Code List `ProcedureType`.
2	Compulsory element `cbc:Name`, used to specify the title of the procurement procedure. Use the same title as for the Contract Notice.
3	Compulsory element `cbc:Description` used to describe shortly the procedure. Use the same description as for the Contract Notice.
4	The procurement is of type 'Services'. See GROW’s Code List `ProjectType`. No sub-type of services is specified. The contracting authority possibly decided that the 2nd. CPV was enough for that matter.
5	First main CPV code '50000000' standing for 'Repair and maintenance services'.
6	Additional CPV code '70000000' standing for 'Real estate services'.

III.10 Lots - Regulated ESPD

Table 17. Requirement regarding Lots in the ESPD-REGULATED Request
REQUIREMENT	At least one Lot must be always instantiated in the Regulated ESPD XML document. If the procurement procedure is not divided into Lots the only lot present in the Regulated ESPD XML document represents the procedure, and its Identifier value must be '0'.

If the procedure is divided into Lots you can create multiple instances of the element ProcurementProjectLot and use it to identify and describe the Lots.

XSD Schema

Figure 29. cac:ProcurementProjectLot. XSD Schema

Expected elements

Table 18. Regulated ESPD Request: Lots
Class name:	cac:ProcurementProjectLot
Definition:	A sub-project into which a procurement procedure can be divided. A procurement project lot has its specific characteristics (e.g. different objectives and different selection criteria) and usually generates its own contract. tbr070-008
Business rule(s):	SELF-CONTAINED (BR-LOT-30)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:ProcurementProjectLot

Components Type Card Description Requirements

Components	Type	Card	Description	Requirements
cbc:ID	Identifier	1	A reference to one or more lots the economic operator is applying for. The original lot definition is part of the call for tender document. The Qualification instance only references the corresponding IDs in order to establish the connection to the call for tender information.	Information Requirement: tbr070-008. Rule: Compulsory use of schemeAgencyID attribute. Check that the type of the `cbc:QualificationApplicationRequest` element is set to `REGULATED`. If more than one lot is present in the XML instance a non-fatal warning should be thrown. Rule scope: SELF-CONTAINED (BR-LOT-10, BR-LOT-30-S10, BR-OTH-02)

cbc:ID

Identifier

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

Information Requirement: tbr070-008.

Rule: Compulsory use of schemeAgencyID attribute. Check that the type of the cbc:QualificationApplicationRequest element is set to REGULATED. If more than one lot is present in the XML instance a non-fatal warning should be thrown.

Rule scope: SELF-CONTAINED (BR-LOT-10, BR-LOT-30-S10, BR-OTH-02)

XML Example

In the example below the contracting authority has selected "No Lots", hence the Lot '0'.

Lots (REGULATED ESPD)

<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationRequest xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationRequest" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationRequest ../xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd">
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm070:ver3.0</cbc:CustomizationID>
        <cbc:ProfileID schemeAgencyID="CEN-BII">41</cbc:ProfileID>
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>
        <cbc:CopyIndicator>false</cbc:CopyIndicator>
        <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:IssueDate>2017-12-31</cbc:IssueDate>
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">1</cbc:ProcedureCode>
        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">REGULATED</cbc:QualificationApplicationTypeCode> (1)
        <!-- Contracting body data left empty for the sake of brevity -->
        <cac:ContractingParty> <cbc:BuyerProfileURI>http://www.defensa.gob.es/isfas/perfilcontr/</cbc:BuyerProfileURI>
                <cac:Party/>
        </cac:ContractingParty>

        <!-- Mandatory Lot of a Regulated ESPD -->
        <cac:ProcurementProjectLot>
                <cbc:ID schemeAgencyID="EU-COM-GROW">0</cbc:ID> (2)
        </cac:ProcurementProjectLot>
</QualificationApplicationRequest>

1	The type of ESPD is "REGULATED". If SELFCONTAINED was specified the presence of more than one lot should be checked and a non-fatal warning should be thrown.
2	The Regulated ESPD requires the presence of one Lot, identified with a '0' to indicate that the procedure is not divided into Lots. Additional Lots may be specified, in which case each Lot needs to be identified differently.

III.11 Lots - Self-contained ESPD

REQUIREMENT

The contracting authority needs to be able to specify the following information: (i) The Lots into which the procedure is divided; (ii) To which lots the tenders may be submitted (all lots, maximum number of lots, only one lot); and (iii) The maximum number of lots that may be awarded to one tenderer.

Mock-up

This mock-up shows how this could be implemented:

Figure 30. Lots (Selfcontained ESPD), mock-up

XSD Schema

REGULATED and SELF-CONTAINED ESPD documents share the same UBL-2.2 XSD Schemas (there are not two different sets of XSD Schemas). Thus, for the identification of the Lots, the Self-contained ESPD uses the same component than for the Regulated ESPD:

Figure 31. cac:ProcurementProjectLot. XSD Schema

The rest of information about the lots (“tenders must be submitted for…”, “maximum number of lots”, “maximum number of lots that may be awarded”) is treated as the elements (or properties) of a “Criterion” (component cac:TenderingCriterion) named “Additional information about the Lots”.

As you will see in section IV.4 Mock-ups, data structures, XML examples and tools and further on, this guide uses a spread-sheet-based method to represent the structures of the criteria (and to generate XML template instances of the criteria). The figure below shows the structure that "generates" the XML instance. One important thing to observe in this structure and in the XML example is the use of the Publications Office Code List "BidType" to specify to which Lots the economic operator may bid.

Figure 32. Requirements about Lots issued by the CA (Selfcontained ESPD), data structure

Expected elements

Table 19. Regulated ESPD Request: Lots
Class name:	cac:ProcurementProjectLot
Definition:	A sub-project into which a procurement procedure can be divided. A procurement project lot has its specific characteristics (e.g. different objectives and different selection criteria) and usually generates its own contract. tbr070-008
Business rule(s):	SELF-CONTAINED (BR-LOT-30)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:ProcurementProjectLot

Components Type Card Description Requirements

Components	Type	Card	Description	Requirements
cbc:ID	Identifier	1	A reference to one or more lots the economic operator is applying for. The original lot definition is part of the call for tender document. The Qualification instance only references the corresponding IDs in order to establish the connection to the call for tender information.	Information Requirement: tbr070-008. Rule: Compulsory use of schemeAgencyID attribute. If several lots are present check that the type of the `cbc:QualificationApplicationResponse` element is set to `SELFCONTAINED`; otherwise a fatal exception should be thrown. As for the Regulated version, if only one Lot is specified its ID has to be set to '0' thus indicating that the procurement procedure is not divided into Lots. Rule scope: SELF-CONTAINED (BR-LOT-10, BR-LOT-30-S10, BR-OTH-02)

cbc:ID

Identifier

Information Requirement: tbr070-008.

Rule: Compulsory use of schemeAgencyID attribute. If several lots are present check that the type of the cbc:QualificationApplicationResponse element is set to SELFCONTAINED; otherwise a fatal exception should be thrown. As for the Regulated version, if only one Lot is specified its ID has to be set to '0' thus indicating that the procurement procedure is not divided into Lots.

Rule scope: SELF-CONTAINED (BR-LOT-10, BR-LOT-30-S10, BR-OTH-02)

The rest of the data related to the Self-contained ESPD Request go in a cac:TenderingCriterion object. See the XML example below and read sections about exclusion and selection criteria for more details on this class.

XML Example

In the example below the contracting authority has specified seven Lots, hence the seven instances of ProcurementProjectLot component.

Convention: Lots should always be identified with a sequential number, as in the examples: Lot1, Lot2, … Lot7.

Lots (SEL-CONTAINED ESPD)

<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationRequest xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationRequest" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationRequest ../xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd">
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm070:ver3.0</cbc:CustomizationID>
        <cbc:ProfileID schemeAgencyID="CEN-BII">41</cbc:ProfileID>
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>
        <cbc:CopyIndicator>false</cbc:CopyIndicator>
        <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:IssueDate>2017-12-31</cbc:IssueDate>
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">1</cbc:ProcedureCode>
        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>
        <!-- Contracting body data left empty for the sake of brevity -->
        <cac:ContractingParty> <cac:Party/></cac:ContractingParty>
        (1)
        <!--- This procurement procedure is divided into 7 Lots -->
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot6</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot7</cbc:ID></cac:ProcurementProjectLot>

(2)
<!-- Additional information about the Lots supplied by the contracting authority -->
        <!-- Criterion:CA Lots -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6a21c421-5c1e-46f4-9762-116fbcd33097</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION</cbc:CriterionTypeCode>
                <cbc:Name>CA Lots</cbc:Name>
                <cbc:Description>Please take into account the following requirements regarding the lots of this procurement procedure:</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">03cff8d1-4d22-4435-82fa-d6361af84be6</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">847829aa-e70a-45e1-b4d3-e11c3ffaf7a0</cbc:ID>
                                <cbc:Description>Tenders may be submitted for</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</cbc:ValueDataTypeCode>(3)
                                <!-- Compulsory use of the Publications Office Code List BidType -->
                                <cbc:ExpectedCode listID="BidType" listAgencyID="EU-COM-OP" listVersionID="1.0">LOT_ALL</cbc:ExpectedCode> (4)
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dceddc28-0ac8-471b-b954-c376a862ea30</cbc:ID>
                                <cbc:Description>Maximum number of lots</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                <cbc:ExpectedValueNumeric>5</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4b710530-abea-4ed0-b3fb-f324919c2d62</cbc:ID>
                                <cbc:Description>Maximum number of lots that may be awarded to one tenderer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                <cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>
</QualificationApplicationRequest>

1	This procedure is divided into 7 lots. Hence their automatic identification from Lot1 to Lot7.
2	this Criterion has one group of properties containing a sub-group where the three requirements about the lots are actually specified: (i)The tenderers may submit tenders for the maximum number of lots; (ii) The Contracting Authority specifies a maximum number of 5 lots; and (iii) one tenderer can not win more than one lot. Notice that each element inside a criterion has a Universally Unique Identifier (UUID): these UUIDs are 'constant', meaning that they are maintained by DG GROW and need to be used compulsory as they were issued by DG GROW.
3	A code has to be provided to specify whether the economic operator is allowed to submit a tender covering one lot only, more than one but not all, or all of them.
4	The value for the expected code (see bullet number 3) needs to be chosen amongst the values of the Code List `BidType`.

Expected elements

Table 20. Regulated ESPD Request: Lots
Class name:	cac:ProcurementProjectLot
Definition:	A sub-project into which a procurement procedure can be divided. A procurement project lot has its specific characteristics (e.g. different objectives and different selection criteria) and usually generates its own contract. tbr070-008
Business rule(s):	SELF-CONTAINED (BR-LOT-30)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:ProcurementProjectLot

Components Type Card Description Requirements

cbc:ID

Identifier

Information Requirement: tbr070-008.

Rule scope: SELF-CONTAINED (BR-LOT-10, BR-LOT-30-S10, BR-OTH-02)

XML Example

In the example below the contracting authority has specified seven Lots, hence the seven instances of ProcurementProjectLot component.

Convention: Lots should always be identified with a sequential number, as in the examples: Lot1, Lot2, … Lot7.

Lots (SEL-CONTAINED ESPD)

<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationRequest xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationRequest" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationRequest ../xsdrt/maindoc/UBL-QualificationApplicationRequest-2.2-Pre-award.xsd">
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm070:ver3.0</cbc:CustomizationID>
        <cbc:ProfileID schemeAgencyID="CEN-BII">41</cbc:ProfileID>
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-3b5755dfb8</cbc:ID>
        <cbc:CopyIndicator>false</cbc:CopyIndicator>
        <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:IssueDate>2017-12-31</cbc:IssueDate>
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">1</cbc:ProcedureCode>
        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>
        <!-- Contracting body data left empty for the sake of brevity -->
        <cac:ContractingParty> <cac:Party/></cac:ContractingParty>
        (1)
        <!--- This procurement procedure is divided into 7 Lots -->
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot6</cbc:ID></cac:ProcurementProjectLot>
        <cac:ProcurementProjectLot><cbc:ID schemeAgencyID="EU-COM-GROW">Lot7</cbc:ID></cac:ProcurementProjectLot>

(2)
<!-- Additional information about the Lots supplied by the contracting authority -->
        <!-- Criterion:CA Lots -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6a21c421-5c1e-46f4-9762-116fbcd33097</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION</cbc:CriterionTypeCode>
                <cbc:Name>CA Lots</cbc:Name>
                <cbc:Description>Please take into account the following requirements regarding the lots of this procurement procedure:</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">03cff8d1-4d22-4435-82fa-d6361af84be6</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">847829aa-e70a-45e1-b4d3-e11c3ffaf7a0</cbc:ID>
                                <cbc:Description>Tenders may be submitted for</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</cbc:ValueDataTypeCode>(3)
                                <!-- Compulsory use of the Publications Office Code List BidType -->
                                <cbc:ExpectedCode listID="BidType" listAgencyID="EU-COM-OP" listVersionID="1.0">LOT_ALL</cbc:ExpectedCode> (4)
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dceddc28-0ac8-471b-b954-c376a862ea30</cbc:ID>
                                <cbc:Description>Maximum number of lots</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                <cbc:ExpectedValueNumeric>5</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4b710530-abea-4ed0-b3fb-f324919c2d62</cbc:ID>
                                <cbc:Description>Maximum number of lots that may be awarded to one tenderer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                <cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>
</QualificationApplicationRequest>

1	This procedure is divided into 7 lots. Hence their automatic identification from Lot1 to Lot7.
2	this Criterion has one group of properties containing a sub-group where the three requirements about the lots are actually specified: (i)The tenderers may submit tenders for the maximum number of lots; (ii) The Contracting Authority specifies a maximum number of 5 lots; and (iii) one tenderer can not win more than one lot. Notice that each element inside a criterion has a Universally Unique Identifier (UUID): these UUIDs are 'constant', meaning that they are maintained by DG GROW and need to be used compulsory as they were issued by DG GROW.
3	A code has to be provided to specify whether the economic operator is allowed to submit a tender covering one lot only, more than one but not all, or all of them.
4	The value for the expected code (see bullet number 3) needs to be chosen amongst the values of the Code List `BidType`.

IV. Criteria, common aspects

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.2 defined in turn the component cac:TenderingCriterion, which is used in ESPD-EDM V2.1.0 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, furhter on this guide, to understand how the QualificationApplicationResponse deals with Criteria).

Figure 33. Criterion - UML diagram

IV.1 General behavior

Notice that:

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;
One criterion may refer to one or several pieces of legislation (EU, national, other);
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 contracting authority; and questions addressed to the economic operator;
One group of properties must always specify at least one 'property';
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.2 cac:TenderingCriterion component:

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

Expected elements

Table 21. 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. tbr070-009
Business rule(s):	SELF-CONTAINED (BR-LOT-20, BR-LOT-30, BR-LOT-30-S20), Common (BR-TC-01)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:TenderingCriterion

Components Type Card Description Requirements

cbc:ID

Identifier

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 Criteria Taxonomy (Regulated ESPD) and Criteria Taxonomy (Self-contained ESPD).

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

cbc:CriterionTypeCode

Code

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 Criteria Taxonomy (Regulated ESPD) and Criteria Taxonomy (Self-contained ESPD), e.g. CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION, CRITERION.EXCLUSION.SOCIAL.ENVIRONMENTAL_LAW, CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO, etc.).

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

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 Criteria Taxonomy (Regulated ESPD) and Criteria Taxonomy (Self-contained ESPD), e.g. 'Convictions', 'Corruption', 'Fraud', 'Financial ratio', 'Subcontracting proportion', 'Allowance of checks', 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 Criteria Taxonomy (Regulated ESPD) and Criteria Taxonomy (Self-contained ESPD), 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, specially when the description contains enumerations (see the criterion "Misinterpretation" for an example).

cbc:WeightNumeric

Numeric

0..1

A weighting to provide for automatic scoring of the Criterion (normally a percentage, e.g. 0.1, 0.5)

Information Requirement: tbr70-016

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

Rule scope: SELF-CONTAINED (BR-2P-10, BR-2P-10-S10, BR-2P-10-S10#1, BR-2P-10-S20#1)

cbc:EvaluationMethodTypeCode

Code

0..1

A code to inform about the type of Evaluation, namely for transparency purposes (e.g. PASSFAIL, WEIGHTED)

Information Requirement: tbr70-016

Rule: Compulsory use of the Code List “EvaluationMethodType”.

Rule scope: SELF-CONTAINED (BR-2P-10-S10#2, BR-2P-10-S20, BR-OTH-01, BR-OTH-03, BR-OTH-01#8, BR-OTH-03)

cbc:WeightingConsiderationDescription

Numeric

0..n

Additional information, comments or considerations about the weighting and the evaluation method, namely for transparency purposes; e.g. '0 Points 0 IT specialists, 30 Points 1 IT specialists, 60 Points 2 IT specialists'. See section about Selection Criteria and sub-section on 'Weighting', for more details.

Information Requirement: tbr70-016

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

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.

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

cbc: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 exmamples in the sections about exclusion and selection criteria.

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

Figure 35. cac:Legislation. XSD Schema

Expected elements

Table 22. Legislation, expected elements
Class name:	cac:Legislation
Definition:	A class to make reference to the legislation related to the criterion. tbr070-013
Business rule(s):	Common (BR-TC-08, 2. BR-OTH-01, BR-OTH-01#9, BR-OTH-03)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:TenderingCriterion/cac:Legislation

Components Type Card Description Requirements

cbc:LegislationTitle

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

Code

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, use the description in Code List LegislationType. Can be provided in several languages, but if LanguageID`not specified it defaults to `en (English).

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

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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4ea7a10a-643e-4022-b67e-e06573b28ff5</cbc:ID>(1)
                <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> (2)
                <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> (3)
                <cbc:JurisdictionLevel languageID="en">EU Directive</cbc:JurisdictionLevel> (4)
                <cbc:Article>57(1)</cbc:Article> (5)
                <cbc:URI>http://eur-lex.europa.eu/legal-content/ES/TXT/?uri=celex%3A32014L0024</cbc:URI> (6)
                </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.
4	Use the textual values (descriptions) listed in the Code List `LegislationType` ESPD-CodeLists-V2.1.0.ods

IV.3 Groups of properties

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

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:

Figure 37. cac:SubsidiaryTenderingCriterionGroup- XSD Schema

Expected elements

Table 23. 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. tbr070-013
Business rule(s):	Common (BR-TC-07, BR-TC-16)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup

Components Type Card Description Requirements

cbc:ID

Identifier

Identifies a group of requirements uniquely.

Information Requirement: tbr070-013.

Rule: Compulsory use of the UUIDs supplied by e-Certis. See also the spreadsheets Criteria Taxonomy (Regulated ESPD) and Criteria Taxonomy (Self-contained ESPD).

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

cbc:PropertyGroupTypeCode

Code

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 contracting authority 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

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. For a better understanding of the use of these codes see also the sub-section The ONTRUE/ONFALSE codes for GROUP and SUBGROUP control
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').

IV.4 Properties

REQUIREMENT

The contracting authority 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 contracting authority.

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

Figure 38. cac:TenderingCriterionProperty - XSD Schema

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

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 contracting authority can specify. The economic operator, in the ESPDResponse, must provide values that are consistent with the type specified by the contracting authority.

Table 24. Properties, expected elements
Class name:	cac:TenderingCriterionProperty
Definition:	Caption (i.e. a 'label'), specific MS or contracting authority 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):	SELF-CONTAINED (BR-SC-20)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationRequest/cac:TenderingCriterion/cac:TenderingCriterionProperty

Components Type Card Description Requirements

cbc:ID

Identifier

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

The text of the caption, requirement or question.

Information Requirement: tbr070-013.

Rule: None.

Rule scope: Common (BR-TC-19)

cbc:TypeCode

Code

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

Information Requirement: tbr070-013.

Rule: Compulsory use of the Code List 'CriterionElementType'. Possible types are 'CAPTION, REQUIREMENT and QUESTION'. If the type is CAPTION or REQUIREMENT no answer is expected from the economic operator and therefore the cbc:ValueDataTypeCode must be set to NONE. Otherwise this value must be set to one of the values defined in the Code List 'ResponseDataType'

Rule scope: SELF-CONTAINED (BR-TC-20, BR-OTH-01, BR-OTH-01#14, BR-OTH-03)

cbc:ValueDataTypeCode

Code

The type of answer expected by the contracting authority in the case of a poperty 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: SELF-CONTAINED (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: SELF-CONTAINED (BR-OTH-01)

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: SELF-CONTAINED (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: SELF-CONTAINED (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: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

See examples in sections about exclusion and selection criteria.
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.

IV.5 Mock-ups

Chapters V. Exclusion Criteria and VI. 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:

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 contracting authority and economic operator perspectives;
Structural: two spread-sheet books (two files) are provided with this document aimed to explain how each type of criterion is organised (each 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-CriteriaTaxonomy-REGULATED-V2.1.0.xlsx, where the structures of the REGULATED ESPD criteria are defined;
- ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.1.0.xlsx, where the structures of the SELF-CONTAINE ESPD criteria are defined;
XML Implementation:

Each mock-up (or pair of CA + 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.

IV.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 two figures below illustrate the data structure sheets for one simple exclusion criterion (EG-Contributions) from both versions of the ESPD, REGULATED and SELF-CONTAINED. Compare them with the UBL-2.2 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-CriteriaTaxonomy*" in folder dist/cl). For the rest of elements there are three types of codes (see also section:
- 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"
Column 25: Code List; it indicates which is the name of code list containing the possible values that must be used for this field. This value is most cases a code however beware that in this ESPD-EDM specification at least one code list contains codes that are not intended to be used as values of codes. See the section titled #code-lists-that-strong-are-not-strong-used-for-code-values(under section Codes and code lists.

REGULATED

Figure 40. Regulated 'Contributions' criterion data structure

SELF-CONTAINED

Figure 41. Self-contained '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.2 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.2 XSD Schemas and the XML examples provided herein.

Table 25. Mapping between the ESPD-EDM criterion data structure spread-sheets and the UBL-2.2 vocabulary
ESDP-EDM Spread-sheet vocabulary	UBL-2.2 vocabulary
CRITERION	cac:TenderingCriterion
SUBCRITERION	cac:SubTenderingCriterion
REQUIREMENT_GROUP	cac:TenderingCriterionPropertyGroup
QUESTION_GROUP	cac:TenderingCriterionPropertyGroup
REQUIREMENT_SUBGROUP	cac:SubsidiaryTenderingCriterionPropertyGroup
QUESTION_SUBGROUP	cac:SubsidiaryTenderingCriterionPropertyGroup
CAPTION	cac:TenderingCriterionProperty
REQUIREMENT	cac:TenderingCriterionProperty
QUESTION	cac:TenderingCriterionProperty
ADDITIONAL_DESCRIPTION_LINE	cbc:Description (namely in cac:TenderingCriterion)
LEGISLATION	cac:Legislation

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.2 cac:TenderingCriterion class
SUBCRITERION: Used to define national sub-criteria; maps to a UBL-2.2 cac:SubTenderingCriterion class
REQUIREMENT_GROUP: Group of requirements or remarks issued by a MS or a CA; maps to a UBL-2.2 cac:TenderingCriterionPropertyGroup
REQUIREMENT_SUBGROUP: A subgroup of requirements or remarks inside a group or subgroup of requirements; maps to a UBL-2.2 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 contracting authority (CA); 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:

A REQUIREMENT is a condition, restriction or rule established by the Member State (in e-Certis, for all procurement procedures) or the contracting authority (CA, 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).
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);
A QUESTION is a direct request for a specific datum by the MS or the CA 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 Regulated ESPD documents do not specify SUBCRITERIA. The SELF-CONTAINED version does;
The Regulated ESPD documents do not specify REQUIREMENT(s), only QUESTION(s). The SELF-CONTAINED version does;
The reason for having 'groups' and 'sub-groups' of properties is because UBL-2.2 defined the 'TenderingCriterionPropertyGroup' and 'SubsidiaryTenderingCriterionPropertyGroup';
In the SELF-CONTAINED version the following rules apply in a regular way:
- When the member state (MS) or the contracting authority (CA) 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.2 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.2 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".

IV.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 dist/xslt 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 two different methods:

Automatic method: Use the script file "Transformer.bat" to generate an ESPD Request or ESPD Response. The expected syntax is the following:

To generate the REGULATED ESPD Request criteria (without the responses, only criteria groups and properties):

c:\dist\xslt>Transformer.bat [ods_file_filePathName] [XSL-T_filePathName] 	[Output_XML_filePathName]

Example: c:\dist\xslt>Transformer.bat 	..\cl\ods\ESPD-CriteriaTaxonomy-REGULATED-V2.1.0.ods .\REGULATED-ESPDRequest-Annotated-V2.1.0.xslt ..\xml\MyREGULATED_ESPDRequestCriteria.xml

To generate the REGULATED ESDP Response criteria (generates only the answers to the QUESTION(s)):

c:\dist\xslt>Transformer.bat [ESPD_Request_filePathName] [XSL-T_filePathName] 	[Output_XML_filePathName]

Example: c:\dist\xslt>Transformer.bat ..\xml\MyREGULATED_ESPDRequestCriteria.xml .\From-REGULATED-REQUEST_to_RESPONSE.xslt ..\xml\MyREGULATED_ESPDResponseCriteriaAnswers.xml

To generate the SELF-CONTAINED_ESPD Request criteria:

c:\dist\xslt>Transformer.bat [ods_file_filePathName] [XSL-T_filePathName] Output_XML_filePathName]

Example: c:\dist\xslt>Transformer.bat ..\cl\ods\ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.1.0.ods	.\SELFCONTAINED-ESPDRequest-Annotated-V2.1.0.xslt ..\xml\MySELFCONTAINED_ESPDRequestCriteria.xml

To generate the SELF-CONTAINED ESDP Response criteria (generates only the answers to the QUESTION(s)):

c:\dist\xslt>Transformer.bat [ESPD_Request_filePathName] [XSL-T_filePathName] 	[Output_XML_filePathName]

Example: c:\dist\xslt>Transformer.bat ..\xml\MySELFCONTAINED_ESPDRequestCriteria.xml .\From-SELFCONTAINED-REQUEST_to_RESPONSE.xslt ..\xml\MySELFCONTAINED_ESPDResponseCriteriaAnswers.xml

Manual 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 (REGULATED-ESPDRequest-Annotated-V2.1.0.xslt and SELFCONTAINED-ESPDRequest-Annotated-V2.1.0.xslt):

All the root elements are created and commented;
An empty contracting authority is created in the ESPD Request and ESPD Response (no data about any CA is 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 (REGULATED-ESPDRequest-Annotated-V2.1.0.xslt and SELFCONTAINED-ESPDRequest-Annotated-V2.1.0.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 (both for the ESPD Request and ESPD Response examples. See files REGULATED-ESPDRequest-2.1.0.xml, REGULATED-ESPDResponse-2.1.0.xml, SELFCONTAINED-ESPDRequest-2.1.0.xml and SELFCONTAINED-ESPDResponse-2.1.0.xml, in the xml 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-REGULATED-REQUEST_to_RESPONSE.xslt and From-SELFCONTAINED-REQUEST_to_RESPONSE.xslt files):

All the root elements are created and commented;
An empty contracting authority is created (no data about any CA is 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 features is NOT implemented in the first set of transformation XSL-T style-sheet (REGULATED-ESPDRequest-Annotated-V2.1.0.xslt and SELFCONTAINED-ESPDRequest-Annotated-V2.1.0.xslt):

The Criteria from the ESPD Request are not copied in the ESPD Response document. but the XML examples in the xml folder do.

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

ON*, meaning that the GROUP or SUBGROUP has to be processed always;
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;
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):

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

The screen-captures below illustrate how the European Commission’s ESP Service processed the GUI for the Exclusion Criterion ''Contributions'' based on this mechanism:

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

Figure 44. Case 2: When the first QUESTION ''Your Answer?'' is 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:

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 has been added to help software application process REQUIREMENT(s) issued by the contracting authority when drafting SELF-CONTAINED ESPD documents. For the time being this need is only present in one Criterion of the SELF-CONTAINED ESPD: 'Other economic or financial requirements' (CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.OTHER_REQUIREMENT(s)). The figure below shows the data structure for that Criterion:

Figure 47. Use of the code list BooleanGUIControlType

Notice that:

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 contracting authority for this specific REQUIREMENT (see the XML example below);
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 ^[2];
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 dist/xml 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="2.0.2">26ece6a2-b360-46c1-890d-8338913b8719</ID>
                <PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9c62f2c7-0c51-451d-8730-427f92ed618c</ID>
                    <Description>Select the type of requirement</Description>
                    <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                    <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CODE_BOOLEAN</ValueDataTypeCode>(1)
                    <ExpectedCode listID="BooleanGUIControlType" listAgencyID="EU-COM-OP" listVersionID="1.0">RADIO_BUTTON_TRUE</ExpectedCode>(2)
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <!--...-->
                    <PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</PropertyGroupTypeCode>(3)
                    <cac:TenderingCriterionProperty>
                        <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">13728a54-21e3-4c84-8b11-48666c3d260f</ID>
                        <Description>Specify the total invoiced amount, taxes included.</Description>
                        <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                        <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</ValueDataTypeCode>
                        <ExpectedDescription>__FinReqsDescription</ExpectedDescription>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">48c7b3bf-8d1c-4497-a915-78d53ba68089</ID>
                        <Description>Minimum amount</Description>
                        <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                        <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</ValueDataTypeCode>
                        <MinimumAmount currencyID="EUR">100006</MinimumAmount>(4)
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8b4ae4f0-2849-49ea-a64b-7bb20c60bde4</ID>
                        <Description>Start date; End date</Description>
                        <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                        <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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="2.0.2">9b3a04ff-e36d-4d4f-b47c-82ad402b9b02</ID>
                        <PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"></PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1d89c188-58d2-461e-a4f6-a17f689d87f4</ID>
                            <Description>Amount</Description>
                            <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</TypeCode>(5)
                            <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</ValueDataTypeCode>(6)
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cc96aa19-a0be-4409-af58-ff3f3812741b</ID>
                    <PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONFALSE</PropertyGroupTypeCode>(7)
                    <cac:TenderingCriterionProperty>
                        <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">57d4160f-20b4-4b43-967b-76b038a2fa6b</ID>
                        <Description>Minimum rating</Description>
                        <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                        <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUANTITY</ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f07b5174-93ae-46dd-aa26-7f451d97f6a8</ID>
                        <Description>Rating scheme</Description>
                        <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</TypeCode>
                        <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</ValueDataTypeCode>
                        <ExpectedDescription></ExpectedDescription>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5fe93344-ed91-4f97-bcab-b6720a131798</ID>
                        <PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"></PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3bd1913b-c461-41eb-87c4-84e003785a56</ID>
                            <Description>Rating</Description>
                            <TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</TypeCode>(8)
                            <ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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 contracting authority 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 contracting authority 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 contracting authority 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 contracting authority 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 contracting authority 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 contracting authority 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="2.0.2">76085d25-05ad-4cb3-b1e0-675558e3f43e</ID>
        <ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1d89c188-58d2-461e-a4f6-a17f689d87f4</ValidatedCriterionPropertyID>(1)
        <cac:ResponseValue>
            <ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">42245674-d305-40bf-8b58-87ba51313345</ID>
            <ResponseAmount currencyID="EUR">10025</ResponseAmount>(2) (3) (4)
        </cac:ResponseValue>
    </cac:TenderingCriterionResponse>

1	This UUID is identical to the UUID of the cac:TenderingCriterionProperty selected by the contracting authority 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-SELF-CONTAINED Criteria Taxonomy spread-sheet).

Use of CAPTION

As explained in section IV.6 Data Structures (see from ''Table 25. Mapping between the ESPD-EDM criterion data structure spread-sheets and the UBL-2.2 vocabulary ESDP-EDM Spread-sheet vocabulary'' on, the term CAPTION is used in the Criteria Taxonomy 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.2 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 ^[3] 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.2 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):

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

The fragment of XML code below illustrates how a mediation service, after reception and storage ^[4], could enrich the XML instance containing the business data with processing instruction annotations, based on the annotated data structure shown above (the complete example can be found in the folder Annotations Proposal

Use of annotations to decouple the business data payload from the software application processing needs

<!-- Criterion:Enrolment in a relevant professional register -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
schemeVersionID="2.1.0">6ee55a59-6adb-4c3a-b89f-e62a7ad7be7f</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW"
listVersionID="2.1.0"
>CRITERION.SELECTION.SUITABILITY.PROFESSIONAL_REGISTER_ENROLMENT</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:TenderingCriterionPropertyGroup>
<xs:annotation>(1)
        <xs:documentation>This is a root GROUP OF REQUIREMENT(s) INSIDE A CRITERION.</xs:documentation>(2)
        <xs:documentation>This group must be processed (e.g. shown) ALWAYS.</xs:documentation>
        <espd:groupVisibilityDependencyType>ON*</espd:groupVisibilityDependencyType>(3)
</xs:annotation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
        schemeVersionID="2.1.0"
        >a53561d5-6614-4dbe-987e-b96f35387f46</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType"
        listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
        >CRITERION_REQUIREMENT_GROUP</cbc:PropertyGroupTypeCode>(4)
<cac:TenderingCriterionProperty>
        <xs:annotation> (5)
                <xs:documentation>This is a DUMMY PROPERTY: the XSD schema makes its presence compulsory (cardinality 1). It can be used, though, to label a GUI frame to ecompasse the group of properties below.</xs:documentation>
        </xs:annotation>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                schemeVersionID="2.1.0"
                >9d5da9ce-fa74-405b-a0ce-2c8f6842b71f</cbc:ID>
        <cbc:Description>Lots the requirement apply to</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType"
                listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                >CAPTION</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType"
                listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                >NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                schemeVersionID="2.1.0"
                >3be88342-5d6e-4160-a37d-e1dd9fc1e92e</cbc:ID>
        <cbc:Description>LotIDs</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType"
                listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                >REQUIREMENT</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType"
                listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                >IDENTIFIER</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:ExpectedID schemeAgencyID="EU-COM-GROW">[List of
                Lots]</cbc:ExpectedID>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
         <xs:annotation>(6)
                <xs:documentation> This is a SUBGROUP OF REQUIREMENT(s) INSIDE A GROUP OF REQUIREMENT(s).</xs:documentation>
                <xs:documentation>This group must be processed (e.g. shown) ALWAYS.</xs:documentation>
                <espd:groupVisibilityDependencyType>CRITERION_REQUIREMENT_SUBGROUP</espd:groupVisibilityDependencyType>
        </xs:annotation>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                schemeVersionID="2.1.0"
                >3aacb82e-afba-440c-b64e-1834007965a2</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType"
                listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                >CRITERION_REQUIREMENT_SUBGROUP</cbc:PropertyGroupTypeCode>
        <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy"
                        schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"
                        >04a713af-549c-4443-84a8-2bd43f6728bd</cbc:ID>
                <cbc:Description>Register name</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType"
                        listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                        >REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType"
                        listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                        >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>[Register
                        Name]</cbc:ExpectedDescription>
        </cac:TenderingCriterionProperty>

<!-- ... etc. -->

1	Block of annotations applied to an element.
2	Human-addressed description of what processing needs to be applied to the next data element. The description can be split in multiple lines.
3	Instructs the software application that it must show this GROUP in any case.
4	Tells the software application what type of GROUP this is (in this case it is a GROUP of REQUIREMENT(s)).
5	Note about the "dumminess" of this element.
6	Next group of annotations, etc…

V. Exclusion criteria

REQUIREMENT br41-002

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.

Differences between Regulated and Self-contained exclusion criteria

As far as the data structures of exclusion criteria are concerned there are practically not differences between a Regulated ESPD and a Self-contained ESPD.

The only two differences lie in:

The way the criteria are worded; e.g. the description of a conviction criterion reads like this in the two cases:
- Regulated ESPD Request: Has the economic operator, to its knowledge, breached its obligations in the field of environmental law? As referred to for the purposes of this procurement in national law, in the relevant notice or the procurement documents or in Article 18(2) of Directive 2014/24/EU.
- Self-contained ESPD Request: Has the economic operator, to its knowledge, breached its obligations in the field of environmental law? As referred to for the purposes of this procurement in this ESPD document and in the national law, in the relevant notice or the procurement documents or in Article 18(2) of Directive 2014/24/EU.
The criterion 'Contributions' (i.e. Payment of Taxes and Social Security Contributions) adds a national REQUIREMENT to set the minimum threshold of debt for taxes or social security that is allowed in the Member State.

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 taxonomy' 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 of the spreadsheets containing the Regulated and Self-contained taxonomies).

Figure 49. Exclusion criteria taxonomy

V.1 Convictions

Information requirement

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

Differences between Regulated and Self-contained

The only difference between REGULATED and SELF-CONTAINED concerning conviction criteria is that the SELF-CONTAINED version allow Member States to link national sub-criteria to the EU conviction criterion. Thus:
- For REGULATED ESPDs the XML file will not contain the national criteria specified in e-Certis. See the figure showing the data structure for Regulated ESPDs.
- For SELF-CONTAINED ESPDs the XML will contain the national criteria and also the QUESTION for the economic operator to answer whether it fulfills the national criterion or not. See the figure showing the data structure for Self-contained ESPDs below.
The label ''Convictions'' groups all the criteria with identical data structures classified as:
- CRITERION.EXCLUSION.CONVICTIONS.*: ''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

If you are using the ESPD Service developed by the European Commission you will observe the label 'More information >>' on the left side of the mock-up. If you click on it the national criteria defined by the MS in the e-Certis will be shown. However you must be warned that, as the EC ESPD Service does only implement the Regulated ESPD V1.0.2 the national criterion will not be saved into the exported XML instance.

Mock-ups - economic operator perspective

The figure below shows the GUI presented by the ESPD Service. Beware that the XML example we provide in this guide is based on the ESPD Request V2.1.0, which does allow the possibility of saving the national criteria, contrary to the ESPD V1.0.2.

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

Figure 50. Conviction 'Participation in criminal organisation', mock-up (EO perspective)

Data structure - Regulated

Notice that the only difference between the Regulated and the Self-contained structures is that the Regulated one does not contain a 'national sub-criterion'.

Figure 51. Data Structure for all 'Regulated Conviction' exclusion grounds criteria

Data structure - Self-contained

Figure 52. Data Structure for all 'Self-contained Conviction' exclusion grounds criteria

XML Example - Self-contained

The fragment of XML code below illustrates how a 'Convictions' criterion looks like in a Self-contained 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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">005eb9ed-1347-4ca3-bb29-9bc0db64e1ab</cbc:ID>
        (14)
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION</cbc:CriterionTypeCode> (15)

        <cbc:Name>Participation in a criminal organisation</cbc:Name> (16)
        <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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                <cbc:Name>Participation in the activity of an organized criminal group ( The Criminal Code of Finland 39/1889 Chapter 17 Section 1)</cbc:Name>
                (12)
                <cbc:Description>Participation in the activity of an organized criminal group an accordance with the criminal code Chapter 17 Section 1</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">070e776e-6a83-44f2-8233-5ac8b39d3f62</cbc:ID>
                                <cbc:Name/>
                                (13)
                                <cbc:Description>Extract from the Criminal Records</cbc:Description>
                                <cbc:Description>Issued By: Legal Register Centre</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode> (17)
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode> (18)
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8591244c-5a6f-4dea-92d4-bba1fc7a7d00</cbc:ID>
                                <cbc:Description>Your Answer</cbc:Description> (19)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <!-- EU legislation data related to this criterion -->
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4ea7a10a-643e-4022-b67e-e06573b28ff5</cbc:ID>
                (20)
                <cbc:Title languageID="en">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 languageID="en">Directive 2014/24/EU</cbc:Description> (21)
                <cbc:JurisdictionLevel languageID="en">EU Directive</cbc:JurisdictionLevel> (22)
                <cbc:Article languageID="en">Article 57(1)</cbc:Article> (23)
                <cbc:URI>http://eur-lex.europa.eu/legal-content/ES/TXT/?uri=celex%3A32014L0024</cbc:URI>
        </cac:Legislation>

        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode> (24)
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7ee6d863-8897-4e18-8a88-75b2503cc286</cbc:ID>
                        <cbc:Description>Your answer</cbc:Description> (25)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode> (26)
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode> (27)
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup> (28)
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">75f31476-677c-4fa6-b48a-2e4d4f09ce82</cbc:ID>
                                <cbc:Description>Date of conviction</cbc:Description> (1)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7ea2ecf8-94a5-44bf-96ab-c8a430365811</cbc:ID>
                                <cbc:Description>Reason</cbc:Description> (2)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">579f5614-d114-4b73-b2ff-3b7d15d19e25</cbc:ID>
                                <cbc:Description>Who has been convicted</cbc:Description> (3)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ef9e3534-00bd-41ef-8f07-85efe6f44d1d</cbc:ID>
                                <cbc:Description>Length of the period of exclusion</cbc:Description> (4)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c048c1bc-b280-4409-9480-1663a2fdfd13</cbc:ID>
                                        <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description> (5)
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">db33b5ae-2290-4671-aeae-fd361d6f6958</cbc:ID>
                                                <cbc:Description>Please describe them</cbc:Description> (6) (7)
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>

                <!-- CONSTANT STRUCTURE: Is this information available online --> (29)
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">643ed2c5-1be5-4b4d-8103-63dcec7f5fe0</cbc:ID>
                        <cbc:Description>Is this information available electronically?</cbc:Description>(8)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f0651bc9-41b9-49b2-9401-ed23ed6aa12d</cbc:ID>
                                <cbc:Description>Evidence supplied</cbc:Description>(9)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>  (10) (11)
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

1	Date of conviction, see mock-up. Mandatory format 'YYYY-MM-DD'
2	The reason of convictions, see mock-up. 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 "IX. 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 "VIII.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 criteria taxonomy spread-sheet.
15	Exclusion criteria taxonomy code defined in the criteria taxonomy spread-sheet.
16	Compulsory name and description for the criterion as defined in e-Certis. See also criteria taxonomy spread-sheet. Beware that UBL-2.2 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. You must use the text of the description supplied by the Code List `LegislationType`.
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 contracting authority 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 ^[5].

V.2 Contributions

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
In the SELF-CONTAINED version the contracting authority can specify the minimum debt an economic operator can maintain related to unpaid taxes or social security contributions.
For both REGULATED and SELF-CONTAINED, the category ''Contributions'' encompasses two criteria with identical data structures:
- CRITERION.EXCLUSION.CONTRIBUTIONS.*: ''payment of taxes'' and ''social security contributions''.

V.2.1 Regulated Contributions

Mock-ups - contracting authority perspective

For a better understanding of the behavior of the Regulated 'Contributions' have a look to the two figures below. They show two different options offered by the ESPD Service GUI perspective for the economic operator:

The figure below represents a possible mockup for the contracting authority perspective of the Conviction criterion 'Payment of Taxes' as retrieved from e-Certis:

Regulated 'Payment of Taxes' (ESPD Service, CA perspective)

Figure 53. Regulated 'Conviction' Payment of Taxes (ESPD Service, EO perspective) - OPTION 1 (YES)

Mock-ups - economic operator perspective

The next mock-up shows the view of the economic operator when it answers "Yes" to the question "Has this breach of obligations been established by other means….?". See the next mock-up for the negative answer. See also the section IV.8 GUI control elements/ONTRUE/ONFALSE codes for GROUP and SUBGROUP control.

Regulated 'Payment of Taxes' (ESPD Service, EO perspective)

Figure 54. Regulated 'Conviction' Payment of Taxes (ESPD Service, EO perspective) - OPTION 1 (YES)

This other mock-up shows the view of the economic operator when it answers "No" to the question "Has this breach of obligations been established by other means….?".

Figure 55. Regulated 'Conviction' Payment of Taxes (ESPD Service, EO perspective) - OPTION 2 (NO)

Data Structure - Regulated

Figure 56. Regulated 'Contributions' criterion data structure

XML Example - Regulated

Regulated Payment of Taxes (PoT)

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

<!-- Criterion:Payment of taxes -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b61bbeb7-690e-4a40-bc68-d6d4ecfaa3d4</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONTRIBUTIONS.PAYMENT_OF_TAXES</cbc:CriterionTypeCode>

        <cbc:Name>Payment of taxes</cbc:Name> (1)
        <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>

        <!-- Reference to the EU Directive where 'Payment of Taxes' are covered -->
        <cac:Legislation>        (11)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4ea7a10a-643e-4022-b67e-e06573b28ff5</cbc:ID>
                <cbc:Title languageID="en">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 languageID="en">Directive 2014/24/EU</cbc:Description>
                <cbc:JurisdictionLevel languageID="en">EU Directive</cbc:JurisdictionLevel>
                <cbc:Article>Article 57(2)</cbc:Article>
                <cbc:URI>http://eur-lex.europa.eu/legal-content/ES/TXT/?uri=celex%3A32014L0024</cbc:URI>
        </cac:Legislation>


                <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">098fd3cc-466e-4233-af1a-affe09471bce</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0810157d-82d8-4a31-9814-b41de9ca0f7a</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Your answer</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f8499787-f9f8-4355-95e2-9784426f4d7b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">789302e2-acbe-4bee-b2a0-d0312207ef3d</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Country or member state concerned</cbc:Description> (2)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE_COUNTRY</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ea565b14-4b91-4730-840f-aae117a84a0c</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Amount concerned</cbc:Description> (3)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7c2aec9f-4876-4c33-89e6-2ab6d6cf5d02</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5773c0da-bccd-4378-89f3-1356f7bd2824</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Has this breach of obligations been established by means other than a judicial or administrative decision?</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">80633323-a7b6-4206-9728-e4534eaad8b2</cbc:ID>

                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">115b8c74-1f17-4e26-a10a-f35198978b16</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Please describe which means were used</cbc:Description> (4)
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a49e6e25-0059-47da-9397-72c2db5fd5b1 </cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6e00a5f4-e832-40aa-b399-2d33f5657c04</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Has the economic operator fulfilled its obligations by paying or entering into a binding arrangement with a view to paying the taxes or social security contributions due, including, where applicable, any interest accrued or fines?</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">42a44eb9-b8c9-4a67-8776-e77fc5356efe</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c5b50839-e117-4415-b5b9-fba95d76c443</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Please describe them</cbc:Description> (5)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">536417dc-8130-4981-85c5-fceba5541c58</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode> (12)
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">75545f09-5a13-40f3-af8b-6a4a131659fc</cbc:ID>
                                                <cbc:Name/>
                                                <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="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8aaac22d-1b59-442e-9210-a6e70ec05962</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">63cb3683-44ce-4549-aefc-843204884011</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Please indicate the date of conviction or decision</cbc:Description> (9)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">505a8da4-d7db-4870-8c3a-4229148a40e2</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>In case of a conviction insofar as established directly therein, the length of the period of exclusion</cbc:Description> (10)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dd5919af-59eb-4295-b27b-5dfd73466ba4</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">849d935c-7ef8-4e00-b075-9b6094464367</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplied</cbc:Description>(6)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode> (7) (8)
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

1	EU Payment of Taxes (PoT) criterion according to the Directive.
2	Country or Member State concerned by the conviction. This field is only shown if the the answer to the previous QUESTION was Yes.
3	Amount concerned and currency for the amount concerned. The economic operator may change the currency. Notice that the currency is specified in the `cac:Amount` attribute `@currencyID`. To see how this looks like in an XML instance open an XM example file corresponding to an ESPDResponse and search for `currencyID`. The default currency is EUR, but the economic operator may specify it in the currency of its country.
4	Placeholder for the "[…] means used to" establish the obligation (See mock-up above). Beware that this sub-structure is only processed (e.g. showed in a GUI, preserved in the XML instance, other) if the answer to the previous QUESTION is Yes (INDICATOR value = true). Compare with the ESPD Service screen-capture above (EO perspective) when the answer is yes.
5	Placeholder for the "Please describe them" field. This sub-group of one QUESTION is only shown if the previous QUESTION was answered with a Yes, thus the ONTRUE code for the sub-group.
6	URL from where to download the evidence. Will be placed in an element of the object `cac:Evidence`. See chapter "IX. Evidences".
7	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 "VIII.8 Evidences".
8	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).
9	Placeholder for the "Please indicate the date of conviction or decision". Beware that this sub-structure is only processed (e.g. showed in a GUI, preserved in the XML instance, other) if the answer to the previous QUESTION is Yes (INDICATOR value = true). Compare with the ESPD Service screen-capture above (EO perspective) when the answer is Yes. Notice also that this XML example contains the possible answers. This was done on purpose to show you how both branches are instantiated in the XML file. However in a real file (e.g. not in an example) it would not make sense have both XML branches, but only one: either the one corresponding to the Yes answer or the one for the No answer; which is the normal expected behaviour of a `choice` structure (this behavior is similar to the an XML `choice` structure, however UBL Naming and Design Rules (NDR) disavow the use of `choices`).
10	Placeholder for the "In case of a conviction, insofar as established…". It goes in the same sub-group than the previous QUESTION about the date of conviction.
11	Notice that the structure and elements for legislation are always the same for all exclusion criteria. Also the UUID identifying the structure is the same in all the exclusion criteria, as this is a highly reusable structure.
12	Beware that this sub-structure is only processed if the answer to the QUESTION was No (INDICATOR value = false). Compare with the mock-up. Compare with the ESPD Service screen-capture above (EO perspective) when the answer is No.

V.2.2 Self-contained Contributions

REQUIREMENT

The contracting authority 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 - contracting authority perspective

The screen-capture below represents a possible mock-up for a contracting authority perspective of the Self-contained 'Contributions' criterion (Payment of Taxes).

Figure 57. Regulated 'Payment of Taxes' (ESPD Service, CA perspective)

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

Figure 58. Self-contained 'Payment of Taxes', REQUIREMENT edition (CA Perspective)

The differences with the Regulated Contribution version are:

The criteria specified by the Member State in e-Certis will be save in the ESPD Request XML instance;
The contracting authority has specified a pair of REQUIREMENT(s) for this procedure (threshold and additional information). If the REQUIREMENT is applicable to all procurement procedure (because it is in the national Law, for example) this would be defined as a national criterion in e-Certis.

Mock-ups - economic operator perspective

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

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

Data structure - Self-contained

The figure for the general data structure below is not reflecting the fact that, for this particular example (about Finland), the national sub-criterion will be repeated four times (the sub-criterion structure has cardinality 0..n). Hence the circles 2 to 5 in this figure meaning that the sub-criterion structure will be repeated for the national criteria 2 to 5. Verify that in the XML example there are four cac:SubTenderingCriterion elements)

Figure 60. Self-contained 'Contributions' criterion data structure

XML Example - Self-contained

Self-contained Payment of Taxes (PoT)

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

<!-- Criterion:Payment of taxes -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b61bbeb7-690e-4a40-bc68-d6d4ecfaa3d4</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONTRIBUTIONS.PAYMENT_OF_TAXES</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> (1)

        <!-- Finland, in e-Certis, defines up to four different types of national exclusion ground for payment of taxes. Each one is instantiated in different national sub-criteria elements -->
        <cac:SubTenderingCriterion> (2)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                <!-- Mandatory: name and description -->
                <cbc:Name>I. Payment of taxes ( Act on public procurement 1397/2016 81 Section 1 )</cbc:Name>
                <cbc:Description>The contracting entity may decide to exclude from competitive tendering a candidate or tenderer that the contracting entity can prove, otherwise than by legally final decision or judgement, to have defaulted on a duty to pay the taxes or social security contributions of Finland or of its country of establishment;</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>

                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cde9df2e-1b89-443c-8946-c047f45c8935</cbc:ID>
                                <cbc:Description>1. Extract from Tax Debt Register</cbc:Description>
                                <cbc:Description>Issued By: Finnish Tax Administration</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52bcfe2c-53a5-4c57-986e-957dba43ce7e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>

        <!-- National criterion 2 --> (3)
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                <cbc:Name>II. Payment of taxes ( Act on public procurement 1397/2016 80 Section 4 )</cbc:Name>
                <cbc:Description>The contracting entity shall also exclude from competitive tendering a candidate or tenderer that has been found by a legally final decision or judgement to have defaulted on a duty to pay the taxes or social security contributions of Finland or of its country of establishment.</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cde9df2e-1b89-443c-8946-c047f45c8935</cbc:ID>
                                <cbc:Description>1. Extract from the Criminal Records</cbc:Description>
                                <cbc:Description>Issued By: Legal Register Centre</cbc:Description>
                                <cbc:Description>2. Extract from Tax Debt Register</cbc:Description>
                                <cbc:Description>Issued By: Finnish Tax Administration</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52bcfe2c-53a5-4c57-986e-957dba43ce7e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <!-- National criterion 3 --> (4)
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                <cbc:Name>III. Aggravated tax fraud ( The Criminal Code of Finland 39/1889 Chapter 29 Section 2 )</cbc:Name>
                <cbc:Description>If in the tax fraud (1) considerable financial benefit is sought or (2) the offence is committed in a particularly methodical manner and the tax fraud is aggravated also when assessed as a whole, the offender shall be sentenced for aggravated tax fraud to imprisonment for at least four months and at most four years.</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cde9df2e-1b89-443c-8946-c047f45c8935</cbc:ID>
                                <cbc:Description>1. Extract from the Criminal Records</cbc:Description>
                                <cbc:Description>Issued By: Legal Register Centre</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52bcfe2c-53a5-4c57-986e-957dba43ce7e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <!-- National criterion 4 --> (5)
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b21867-95b5-4549-8180-f4673219b179</cbc:ID>
                <cbc:Name>IV. Tax fraud ( The Criminal Code of Finland 39/1889 Chapter 29 Section 1 )</cbc:Name>
                <cbc:Description>A person who (1) gives a taxation authority false information on a fact that influences the assessment of tax, (2) files a tax return concealing a fact that influences the assessment of tax, (3) for the purpose of avoiding tax, fails to observe a statutory duty pertaining to taxation that is of significance in the assessment of tax, or (4) otherwise acts fraudulently, and thereby causes or attempts to cause a tax not to be assessed, a tax to be assessed too low or a tax to be unduly refunded, shall be sentenced for tax fraud to a fine or to imprisonment for at most two years.</cbc:Description>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cde9df2e-1b89-443c-8946-c047f45c8935</cbc:ID>
                                <cbc:Description>1. Extract from the Criminal Records</cbc:Description>
                                <cbc:Description>Issued By: Legal Register Centre</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52bcfe2c-53a5-4c57-986e-957dba43ce7e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>

        <!-- Reference to the EU Directive where 'Payment of Taxes' are covered -->
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4ea7a10a-643e-4022-b67e-e06573b28ff5</cbc:ID>
                <cbc:Title languageID="en">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 languageID="en">Directive 2014/24/EU</cbc:Description>
                <cbc:JurisdictionLevel languageID="en">EU Directive</cbc:JurisdictionLevel>
                <cbc:Article>Article 57(2)</cbc:Article>
                <cbc:URI>http://eur-lex.europa.eu/legal-content/ES/TXT/?uri=celex%3A32014L0024</cbc:URI>
        </cac:Legislation>

        <!-- Member State and contracting authority REQUIREMENT(s). In this case the MS allows a maximum debt of 50 EUR, and additional information is provided for clarification purposes -->
        <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a764b129-26e7-4047-9d58-752ebd59af28</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Threshold</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">50</cbc:ExpectedAmount> (6) (7)
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c4421575-0f45-430e-a3d9-9f9967eafdee</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Additional Information</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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>In case of debt please fulfill your obligation before tendering.</cbc:ExpectedDescription> (8)
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>

                (9)
                <!-- The rest of the criterion is identical than for the Regulated version -->

                <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">098fd3cc-466e-4233-af1a-affe09471bce</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0810157d-82d8-4a31-9814-b41de9ca0f7a</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Your answer</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f8499787-f9f8-4355-95e2-9784426f4d7b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">789302e2-acbe-4bee-b2a0-d0312207ef3d</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Country or member state concerned</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE_COUNTRY</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ea565b14-4b91-4730-840f-aae117a84a0c</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Amount concerned</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7c2aec9f-4876-4c33-89e6-2ab6d6cf5d02</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5773c0da-bccd-4378-89f3-1356f7bd2824</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Has this breach of obligations been established by means other than a judicial or administrative decision?</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">80633323-a7b6-4206-9728-e4534eaad8b2</cbc:ID>

                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">115b8c74-1f17-4e26-a10a-f35198978b16</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Please describe which means were used</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a49e6e25-0059-47da-9397-72c2db5fd5b1 </cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6e00a5f4-e832-40aa-b399-2d33f5657c04</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Has the economic operator fulfilled its obligations by paying or entering into a binding arrangement with a view to paying the taxes or social security contributions due, including, where applicable, any interest accrued or fines?</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">42a44eb9-b8c9-4a67-8776-e77fc5356efe</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c5b50839-e117-4415-b5b9-fba95d76c443</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Please describe them</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">536417dc-8130-4981-85c5-fceba5541c58</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">75545f09-5a13-40f3-af8b-6a4a131659fc</cbc:ID>
                                                <cbc:Name/>
                                                <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="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8aaac22d-1b59-442e-9210-a6e70ec05962</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">63cb3683-44ce-4549-aefc-843204884011</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Please indicate the date of conviction or decision</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">505a8da4-d7db-4870-8c3a-4229148a40e2</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>In case of a conviction insofar as established directly therein, the length of the period of exclusion</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dd5919af-59eb-4295-b27b-5dfd73466ba4</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">849d935c-7ef8-4e00-b075-9b6094464367</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

1	The MS defined this national 'Payment of Taxes' criterion in e-Certis. See also previous example for the REGULATED Payment of taxes (the behavior is identical for all exclusion criteria).
2	Reference to the EU Legislation. This reusable structure is identical for all the exclusion criteria.
3	For this SELFCONTAINED 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: (i) the ESPDRequest is of type SELFCONTAINED (REGULATED ESPDs does not work with REQUIREMENT(s)); (ii) a `cbc:ValueDataType` will be present indicating the type of value the contracting authority uses for this REQUIREMENT (e.g. AMOUNT, INDICATOR, DESCRIPTION, etc.; see the Code List `ResponseDataType`, the values are the same for contracting authorities 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 CA and the EO.
6	The value supplied by the contracting authority 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 contracting authority the possibility of adding multiple additional textual requirements (in this case the CA 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 contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority.
9	Except for the national sub-criteria and the REQUIREMENT(s), the rest is identical to the Regulated version.

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
For both REGULATED and SELF-CONTAINED, the category ''Social'' encompasses criteria with identical data structures, classified as:
- CRITERION.EXCLUSION.SOCIAL.*: ''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 - contracting authority perspective

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

Mock-ups - economic operator perspective

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

Data structure - Regulated

Figure 63. 'Environmental Law' criterion data structure

Data structure - Self-contained

Figure 64. 'Environmental Law' criterion data structure

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

'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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a80ddb62-d25b-4e4e-ae22-3968460dc0a9</cbc:ID>
                        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.SOCIAL.ENVIRONMENTAL_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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5f614675-9db7-4ec6-9567-0673b758c1e2</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f0a20829-ea70-44e5-8310-91808e7b957a</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Your Answer</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:TenderingCriterionPropertyGroup>
                        </cac:SubTenderingCriterion>
                        <cac:Legislation>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">22746727-298b-4abb-b580-52b5ea482d7c</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                                </cac:Language>
                        </cac:Legislation>
                        <cac:TenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">976b5acb-c00f-46ca-8f83-5ce6abfdfe43</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">95dad7ae-1aba-4ad6-9760-5a7ed15cb039</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Your answer</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">64a2102c-4af1-4ecb-97b3-0c41907ec0f6</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ea48e234-7ad2-4235-b375-4f72c9877693</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Please describe them</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a345842-1aee-4bba-b9a6-64343ba91809</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                        <cac:TenderingCriterionProperty>
                                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">304ef89a-477e-4b60-8b9b-9ea15d10a3a0</cbc:ID>
                                                                <cbc:Name/>
                                                                <cbc:Description>Please describe them</cbc:Description>
                                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                        </cac:TenderingCriterionProperty>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:TenderingCriterion>

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

V.4 Business

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
For both REGULATED and SELF-CONTAINED, the category ''Business'' encompasses the following group of criteria with the same data structures and classified as:
- CRITERION.EXCLUSION.BUSINESS.*: breaching of obligations for ''bankruptcy'', ''insolvency'', ''winding-up'', ''arrangement with creditors'', ''analogous situation like bankruptcy under national law'', ''assets being administered by liquidator'' and ''business activities suspended''.

Mock-ups - contracting authority perspective

'Bankruptcy' criterion mock-up - CA perspective

Figure 65. 'Bankruptcy' criterion mock-up - contracting authority perspective

Mock-ups - economic operator perspective

'Bankruptcy' criterion mock-up - EO perspective

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

Data structure - Regulated

Figure 67. 'Bankruptcy' criterion data structure - Regulated

Data structure - Self-contained

Figure 68. 'Bankruptcy' criterion data structure - Self-contained

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

'Bankruptcy'

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

        <!-- Criterion:Bankruptcy -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d3732c09-7d62-4edc-a172-241da6636e7c</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.BUSINESS.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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8ab473f2-653a-4465-a7dd-61e0df984c27</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9420733c-be4d-459e-b782-0e6cd6a7c199</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f92fe55b-e6fd-4317-b2d1-ae0e6a4aaf04</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2074f13b-4adb-4550-9814-6b971904c5b3</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">645b5933-30c3-482e-b7d4-6c6b29b3db72</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">36ccd47b-b021-4ccb-b614-6a3b671817c9</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Indicate reasons for being nevertheless to perform the contract</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c64b6686-acf9-4cb0-b3d7-ae8260cf75e6</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">771f8e03-abc5-4a08-b095-dc40efdd3f79</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterion>
<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

V.5 Misconduct

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
For both REGULATED and SELF-CONTAINED, the category ''Misconduct'' encompasses two criteria that share the same structure as the one used for the ''social'' group of criteria (see sub-section ''How to specify ''social'' related criteria, above).
- CRITERION.EXCLUSION.MISCONDUCT.*: ''guilty of grave professional misconduct''; and ''agreements with other economic operators aimed at distorting competition''.

All these criteria are specified based on the same data structure:

Mock-ups - contracting authority perspective

'Professional misconduct' criterion mock-up - CA perspective

Figure 69. 'Professional misconduct' criterion mock-up - contracting authority perspective

Mock-ups - economic operator perspective

'Professional misconduct' criterion mock-up - EO perspective

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

Data structure - Regulated

Figure 71. 'Professional misconduct' criterion data structure - Regulated

Data structure - Self-contained

Professional misconduct Professional misconduct

Figure 72. 'Professional misconduct' criterion data structure - Self-contained

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

'Professional Misconduct'

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

        <!-- Criterion:Guilty of grave professional misconduct -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">514d3fde-1e3e-4dcd-b02a-9f984d5bbda3</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.MISCONDUCT.MC_PROFESSIONAL</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 in the ESPD, the relevant notice or .</cbc:Description>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e988261e-93ae-4e62-9d71-ce1f548b1347</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3df8f3d8-d074-460d-85c9-969b8a947554</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cb8d4d15-7fd7-4d94-9a98-a4733d7268be</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e78aa682-1ad8-4b4c-b8aa-ea4f8f5cc88d</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2cbcf978-765c-40aa-996b-b1d082485cef</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">61ea71a3-28e4-401c-850d-0817c6bf4f4d</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1688b9f9-6d2d-422b-8ce3-6315a617fe88</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Have you taken measures to demonstrate your reliability</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c5210554-19a9-4b37-90f1-041bab348d58</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Please describe them</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

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

V.6 Conflict of interest

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
For both REGULATED and SELF-CONTAINED, the category ''Conflicts of Interest'' encompasses different exclusion criteria which are more heterogeneous than the ones described until now.

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

CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.PROCEDURE_PREPARATION: Conflict of interest due to ''direct or indirect involvement in the preparation of this procurement procedure'';
CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.PROCEDURE_PARTICIPATION: 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 - contracting authority perspective (REGULATED and SELF-CONTAINED)

This mock-up could be used for both versions, Regulated and Self-contained:

'Conflict of interest' criterion mock-up - CA perspective

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

Mock-ups - economic operator perspective (REGULATED and SELF-CONTAINED)

This mock-up could be used for both versions, Regulated and Self-contained:

'Conflict of interest' criterion mock-up - EO perspective

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

Data structure - Regulated

Figure 75. 'Conflict of interest' criterion data structure - Regulated

Data structure - Self-contained

Figure 76. 'Conflict of interest' criterion data structure - Self-contained

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

'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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b1b5ac18-f393-4280-9659-1367943c1a2e</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.MISCONDUCT.MC_PROFESSIONAL</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 the in the ESPD, the relevant notice or due to its participation in the procurement procedure?</cbc:Description>
                <cac:SubTenderingCriterion>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c4b7f5ce-bf0b-464f-b1b3-5db603c00c6f</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">621a3591-8ef5-469a-80d5-29130683ee5e</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fb5adf8c-1ffc-427c-95d0-9cfa0a8ef5cc</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">567e5857-978f-4115-95be-dc5145ea950a</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d2aaed34-443f-4fc7-9f8c-72c9e21d8f26</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

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

V.7 Early termination

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;

For both REGULATED and SELF-CONTAINED, the category 'Early termination' refers to only one criterion with a specific (simple) data structure classified as:
- CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.EARLY_TERMINATION: Conflict of interest due to ''early termination, damages or other comparable sanctions''.

Mock-ups - contracting authority perspective

'Early termination' criterion mock-up - CA perspective

Figure 77. 'Early termination' criterion mock-up - contracting authority perspective

Mock-ups - economic operator perspective

'Early termination' criterion mock-up - EO perspective

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

Data structure - Regulated

Figure 79. 'Early termination' criterion data structure - Regulated

Data structure - Self-contained

Figure 80. 'Early termination' criterion data structure - Self-contained

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3293e92b-7f3e-42f1-bee6-a7641bb04251</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.EARLY_TERMINATION</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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">82dd3b06-72fc-4dbe-ab09-e2726b621382</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6f8f4018-b255-4aaf-ac6f-dbd26a03e189</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Your Answer</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:TenderingCriterionPropertyGroup>
                </cac:SubTenderingCriterion>
                <cac:Legislation>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">339b347e-e301-4547-9128-c766d99d6237</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fed2e6a3-a1da-4a36-a638-b2f7a29ad243</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7495abce-b711-4acb-994c-fb180ec8827e</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Please describe them</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">20c5361b-7599-4ee6-b030-7f8323174d1e</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6edfb05b-c93c-4518-9f25-175a3f08e34c</cbc:ID>
                                                <cbc:Name/>
                                                <cbc:Description>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1154b341-7237-4712-9d4d-7f0656ffd947</cbc:ID>
                                                        <cbc:Name/>
                                                        <cbc:Description>Please describe them</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

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

V.8 Misinterpretation

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

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
For both REGULATED and SELF-CONTAINED, the category 'Misinterpreation', another type of 'Conflict of Interest', share the same data structure, and is classified as:
- CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.MISINTERPRETATION

Mock-ups - contracting authority perspective

'Misinterpretation' criterion mock-up - CA perspective

Figure 81. 'Misinterpretation' criterion mock-up - contracting authority perspective

Mock-ups - economic operator perspective

'Misinterpretation' criterion mock-up - EO perspective

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 REGULATED and SELF-CONTAINED versions.

Data structure - Regulated

Figure 83. 'Misinterpretation' criterion data structure - Regulated

Data structure - Self-contained

Figure 84. 'Misinterpretation' criterion data structure - Self-contained

XML Example - Self-contained

Notice that the Regulated and Self-contained XML instances are identical, except for the fact that the Regulated version does not contain national sub-criteria.

'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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">696a75b2-6107-428f-8b74-82affb67e184</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.MISINTERPRETATION</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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0934d941-9680-447c-b2ca-af1f0fce53fd</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7dfc567f-1429-4ed3-a299-39f2451e69c2</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e26648ec-ba40-46d4-a4d0-79833b7da551</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f3a6836d-2de2-4cd1-81ca-fb06178d05c5</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f838769c-5869-4f55-b9cb-089d9331bbf5</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Your answer</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

V.9 Purely national criteria

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

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

These two requirements are introduced by the new Self-contained ESPD-EDM V2.1.0. Therefore you will see that there is an essential difference between the Regulated and the Self-contained ESPDs.

Differences between Regulated and Self-contained

The SELF-CONTAINED version the XML instances can keep the national sub-criteria defined by the MS in e-Certis;
The data structure for the SELF-CONTAINED versions is quite different from the REGULATED due to the new information requirements requested by the Membere States. See the sub-sections below on Regulated purely national and Self-contained purely national criteria below for details on the differences. The classification code fore this criterion is:
- CRITERION.EXCLUSION.NATIONAL.OTHER

V.9.1 Regulated Purely national criteria

In the Regulated ESPD, software applications may download from e-Certis all the purely national criteria specified by the Member States in e-Certis. However the economic operator has not the possibility of answering the criteria individually, it has to respond 'Yes' or 'No' to all of them.

Beware that for Regulated ESPDs the XML file will not contain the national criteria specified in e-Certis.

Note about the ESPD Service

If you are using the ESPD Service developed by the European Commission you will observe the GUI shows the list of national criteria defined by the Member State in e-Certis. However you must be warned that, as the EC ESPD Service does only implement the Regulated ESPD V1.0.2 the list of national criteria will not be saved into the exported XML instance.

Mock-ups - contracting authority perspective (REGULATED)

The mock-up below shows how the contracting authority views the criteria purely national defined in e-Certis.

'Purely national criteria' mock-up - CA perspective

Figure 85. 'Purely national criteria' mock-up - contracting authority perspective

Mock-ups - economic operator perspective (REGULATED)

The figure below shows a fragment of a list of national criteria that a software application has captured from e-Certis. The economic operator does have to confirm that it fulfills all the criteria purely national.

'Purely national criteria' mock-up - EO perspective

Figure 86. 'Purely national criteria' mock-up - economic operator perspective

Data structure - Regulated

Figure 87. 'Purely national criteria' data structure

XML Example - Regulated

'Purely national criteria' (Regulated)

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

<!-- Criterion:Purely national exclusion grounds -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">63adb07d-db1b-4ef0-a14e-a99785cf8cf6</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.NATIONAL.OTHER</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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6df6d577-c593-4349-8a89-f785c97d830d</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"/>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fddf4a1a-744d-4fe0-ba1b-54f9dfc051ba</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41748296-9179-48b3-983f-964fb6127d46</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">13cd212b-24ba-471f-bd2e-9539c680ab23</cbc:ID>
                                <cbc:Name>Have you taken measures to demonstrate your reliability (Self-Cleaning)?</cbc:Name>
                                <cbc:Description/>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3fa51985-630a-4f73-a1d6-032a36cba292</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fa52a1af-798e-4b91-a490-8204519b17d2</cbc:ID>
                                        <cbc:Name>Please describe them</cbc:Name>
                                        <cbc:Description/>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">07e6adb0-fae2-47be-8fad-e98f60c55b37</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6c4442a6-0c88-4e3e-b23c-b9fa8e92d7bc</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- ... the rest of elements in the QualificationApplicationRequest document omitted for brevity -->

V.9.2 Self-contained Purely national criteria

The ESPD-EDM V2.1.0 Self-contained ESPD introduces 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.

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.

Figure 88. 'Purely natural criteria' - economic operator perspective (Self-contained)

Data structure - Self-contained

Figure 89. 'Purely national criteria' data structure - Regulated

XML Example - Self-contained

'Purely national criteria' (Self-contained)

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

<!-- Criterion:Purely national exclusion grounds -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">63adb07d-db1b-4ef0-a14e-a99785cf8cf6</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.NATIONAL.OTHER</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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3a26fe31-6441-454e-9831-a4b1418b3d97</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"/>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">70d6dbf1-7b58-4660-9249-ed93e7273dd8</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description/>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"/>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f2ec28aa-9202-4c4f-abc9-8287cda43175</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Text describing the national criterion]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4d9bd997-8aa0-4134-816d-b0b58471bfee</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Type of evidence from e-Certis]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7f06f77c-29e5-4af6-8eb1-0d7f1505f382</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bef25782-3d4e-4d31-b6c2-b9bcdbf112c4</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d1bcea91-26df-496a-bcdd-f04de6de32c4</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI. 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-016, and tbr070-018.

Differences between Regulated and Self-contained exclusion criteria

The ESPD-EDM V2.1.0 introduces important changes regarding the selection criteria. It provides the contracting authority with much more flexibility to define requirements specific to the procurement procedure. These new features affect specifically the following aspects:

Suitability, including enrolment in a relevant professional register, enrolment in a trade register, authorisation and membership of particular organisation needed for service contracts;
Turnovers (general and specific);
References to similar works and services, including confidentiality about the references;
Quality assurance schemes and environmental management standards;
Professional ris indemnity insurance;
Other economic or financial requirements;
Technicians or technical bodies;
Supply chain management;
Allowance of checks;
Educational and professional qualifications and Environmental management measures;
Tools, plant or technical equipment;
Criteria for a particular type of contract;
Technical, study, research, and development facilities resources;
Financial ratios;
Other: Lots management, weighting, EO Roles.

This section covers exhaustively each of these aspects and provides examples of XML implementation for each one of them. They will examined criterion by criterion, taking as a starting the point the requirement expressed in 'BIS 41 - European Single Procurement Document (Version 2.0.0)'.

ABOUT the compatibility between Regulated and Self-contained ESPDs:

Not all the selection criteria have modified their structures between versions 1.0.2 and 2.1.0.
The changes introduced by the Self-contained ESPD are basically 'additions'.

Therefore the compatibility from a Regulated ESPD towards a Self-contained ESPD should be possible to a large extent.

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 (leaves in text without boxes).

Figure 90. Selection criteria taxonomy

VI.1 Alpha criterion

The criterion 'Global indication for all selection criteria' (a.k.a. 'Alpha Criterion') is a special feature only possible in the REGULATED ESPD. It is intended to avoid that the economic operator specifies a long list of selection criteria.

The code used in the ESPD-REGULATED Criteria Taxonomy to identify this criterion is:

CRITERION.SELECTION.ALL (UUID f4dc58dd-af45-4602-a4c8-3dca30fac082)

The use of the Alpha Criterion implies that the economic operator states that it fulfills all the selection criteria. Fulfilling an ESPD-Response document like this is close to the idea of the ESPD used as a self-declaration.

If this selection criterion is used then no other selection criterion can occur in the XML instance of an ESPD-REGULATED document. Otherwise the validation mechanisms should reject the document.

The use of the Alpha Criterion is not recommended as it does not promote the transparency and hinders the interoperability: no data about the selection criteria are exchanged. These are the two main reasons why the Alpha Criterion is not used in the SELF-CONTAINED ESPD.

Mock-ups (CA perspective)

The two figures below show how the EC’s transitional ESPD-Service behaves when the 'Alpha Criterion' is used by the Contracting Authority (CA) to specify that there is no need for the Economic Operator (EO) to specify each criterion (first figure: no A to D sets of criteria), and when the CA requires the EO to specify each criterion (second figure: blocks of criteria A to D are to be answered).

Alpha Criterion selected- (CA perspective)'

image::AlphaCriterion_CA_mockup.PNG['Alpha Criterion selected' (CA perspective), alt="Alpha Criterion selected (CA perspective)", align="center"]

Alpha Criterion unselected (CA perspective)'

image::AlphaCriterion_CA_mockup_unselected.PNG['Alpha Criterion unselected' (CA perspective), alt="Alpha Criterion unselected(CA perspective)", align="center"]

Mock-ups (EO perspective)

The two figures below show how the EC’s transitional ESPD-Service behaves when the 'Alpha Criterion' is used by the Economic Operator (EO).

Figure 91. The Alpha Criterion selected (EO perspective)'

Figure 92. The Alpha Criterion unselected (EO perspective)'

Data Structure (ONLY REGULATED-ESPD)

(The figure below is defined in the the tab "ALPHA-CRITERION of the ESPD-CriteriaTaxonomy spread-sheet).

Figure 93. The Alpha Criterion in the Regulated ESPD

XML Example - (only for the Regulated ESPD)

In this example, the CA creates an ESPD-Request document which contains one, and only one, selection Criterion (see the first fragment of XML code below).

The System of the Economic Operator will import the ESPD-Request document ans will answer with a simple true or false value in the its ESPD-Response document (see the second fragment of XML code below):

Alpha Selection Criterion specified by the CA in the REGULATED ESPD-Request

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

<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
            schemeVersionID="2.0.2">f4dc58dd-af45-4602-a4c8-3dca30fac082</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW"
            listVersionID="2.0.2"
            >CRITERION.SELECTION.ALL</cbc:CriterionTypeCode>
    <cbc:Name>Global indication for all selection criteria</cbc:Name>
    <cbc:Description>Concerning the selection criteria the economic operator declares that It satisfies all the required selection criteria indicated in the relevant notice or in the procurement documents referred to in the notice.</cbc:Description>
    <cac:TenderingCriterionPropertyGroup>
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                    schemeVersionID="2.0.2"
                    >8684a40f-f0ac-43ed-8571-caf9e25dd934</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType"
                    listAgencyID="EU-COM-GROW" listVersionID="2.0.2"
                    >ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                            schemeVersionID="2.0.2"
                            >743cf1cf-d203-4df2-b84b-33f208957650</cbc:ID>
                    <cbc:Description>Your answer</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType"
                            listAgencyID="EU-COM-GROW" listVersionID="2.0.2"
                            >QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType"
                            listAgencyID="EU-COM-GROW" listVersionID="2.0.2"
                            >INDICATOR</cbc:ValueDataTypeCode>(1)
            </cac:TenderingCriterionProperty>
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

1	The type of data expected by the CA, a simple `true` or false value. See the example about the EO response below.

Alpha Selection Criterion, the response provided by the EO in the REGULATED ESPD-Response

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

 <cac:TenderingCriterionResponse>
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">acb58f0e-0fe4-4372-aa08-60d0c36bfcfe</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8684a40f-f0ac-43ed-8571-caf9e25dd934</cbc:ValidatedCriterionPropertyID>(1)
    <cbc:ResponseIndicator >true</cbc:ResponseID> (2)
 </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:ResponseIndicator` contains the value `true`, i.e. the EO states formally (declares) that it satisfies all the required selection criteria indicated in the relevant notice or in the procurement documents referred to in the notice.

VI.2 Suitability

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

Differences between Regulated and Self-contained

In the REGULATED, the CA is able to check the selection criteria regarding Suitability that apply to a particular procurement procedure, but cannot provide the particular information required to the EO for each criteria.
In the SELF-CONTAINED, the CA is able to specify the name of the register or the organisation the EO must be part of, and the URL. Additionally, the CA can specify Lots.
For both versions (REGULATED and SELF-CONTAINED), the category ''Suitability'' is split into covers two groups of different data structures with these classification codes:
- One data structure for two types of ''enrolments''(''Enrolment in a relevant professional register'' and ''Enrolment in a trade register''), and
- Another data structure for two suitabilities related to ''service contracts'' (''For service contracts: authorisation of particular organisation needed'' and ''For service contracts: membership of particular organisation needed'').

VI.2.1 Regulated suitability (enrolments)

Mock-ups - contracting authority perspective

Figure 94. Regulated 'Suitability' criterion (CA perspective)'

Mock-ups - economic operator perspective

Notice that, as for the exclusion criteria, for the selection criteria the MS can specify general national sub-criteria in e-Certis. Software applications can download these sub-criteria from e-Certis and shown them in their GUI. For each national sub-criteria, the economic operator will have to respond "Yes" or "No" to confirm that it fulfills them.

Figure 95. Regulated 'Suitability' criterion (EO perspective)'

Data Structure (Enrolments)- Regulated

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

Figure 96. Regulated 'Suitability' criterion data structure (for ''enrolments'')

XML Example (Enrolment)- Regulated

Regulated '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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6ee55a59-6adb-4c3a-b89f-e62a7ad7be7f</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.SUITABILITY.PROFESSIONAL_REGISTER_ENROLMENT</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:Legislation><!-- eliminated for brevity --></cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1768de86-a6c8-48e4-bd8e-de2f2f7424d0</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0b0e0f5c-af55-4bc9-b1d9-4a6a152e9e17</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a99c28d8-c3e0-40c9-993e-793c6f5358af</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b2f0f738-b50a-4a1e-af47-bff423626e9e</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

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

VI.2.2 Self-contained suitability (enrolments)

Mock-ups - contracting authority perspective

For each criteria regarding suitability, the CA should be able to provide: the register name, its URL and the Lots to which each requirement apply.

The mock-up below represents the requirements the CA should be able to specify for a suitability criterion in a procedure procurement that is not divided into lots:

Self-contained 'Suitability' criterion (CA perspective)

Figure 97. Self-contained 'Suitability' criterion without Lots (CA perspective)'

This other mock-up represents the same situation when the procurement procedure is divided into lots.

The contracting authority (CA) may request that the economic operator is registered in one or multiple registers. Per each register the CA specifies to which Lots this make sense. This behaviour of “one set of lots per group of properties is regular for all those selection criteria where the allocation of lots to a set of 'criterion properties' make sense (e.g. see the section "References").

Figure 98. Self-contained 'Suitability' criterion with Lots (CA perspective)'

Mock-ups - economic operator perspective

Notice that:

The Lots and registers specified by the contracting authority are presented to the economic operator (on the left side of the mock-up, circles 1 to 6);
The expected answer is "Yes", meaning that the economic operator fulfills the criterion;
In case of answering "No" the economic operator will have to provide the reasons why it is not registered.

Figure 99. Self-contained 'Suitability' criterion (EO perspective)'

Data Structure (Enrolments) - Self-contained

This data structure is quite different from the Regulated ESPD:

It allows the definition of multiple national sub-criteria (to be retrieved from e-Certis): cardinality "0..n" of the SUBCRITERION group;
It also allows the contracting authority to speciy multiple groups of REQUIREMENT(s) (in this case to specify which registers the economic operator should be registered in).
The number of Lots is also multiple (notice the cardinality "1..n" of the LotID REQUIREMENT, thus making possible to build lists of LotsIDs.
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 contracting authority).

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

Figure 100. Self-contained 'Suitability' criterion data structure (enrolments)

XML Example - Self-contained (with Lots)

The following XML example illustrates how to solve the more complex situation, when the Lots are specified. If the procurement procedure is not divided into Lots, the XML would be identical, except that all the elements related to Lots would not be present.

For detailed comments on how Lots are used in this case, visit the section IX.2 All about lots, sub-section Example 1: Suitability.

Self-contained '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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6ee55a59-6adb-4c3a-b89f-e62a7ad7be7f</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.SUITABILITY.PROFESSIONAL_REGISTER_ENROLMENT</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:SubTenderingCriterion> <!-- ... ELEMENTS REMOVED FOR BREVITY --> </cac:SubTenderingCriterion>
        <cac:Legislation><!-- ... ELEMENTS REMOVED FOR BREVITY --> </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a53561d5-6614-4dbe-987e-b96f35387f46</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f99ee126-23b8-4d83-8a62-6df4056a77cb</cbc:ID>
                        <cbc:Description>Lots the requirement apply to</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">aca46197-141d-4c96-8d97-6ed08d653e22</cbc:ID>
                        <cbc:Description>LotIDs</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">IDENTIFIER</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:ExpectedID>[List of Lots]</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3aacb82e-afba-440c-b64e-1834007965a2</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a72759b-cdff-4132-803f-d5d8955a5059</cbc:ID>
                                <cbc:Description>Register name</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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>[Register Name]</cbc:ExpectedDescription>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b420be09-d85b-45df-ab09-a43eef0b5635</cbc:ID>
                                <cbc:Description>URL</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">URL</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 -->
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6cce6b8e-c53d-4598-8150-ac49aba3b9c7</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d35eff44-9405-44f3-82c9-ca30bd98e589</cbc:ID>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">70d5bbcf-0581-4d0f-b5c7-8b604a791972</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8fa5ec56-385c-44ec-ba97-ff25e95a3287</cbc:ID>
                                        <cbc:Description>Registration number</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3a4a5421-81cc-468e-b69f-b86bf8c7932d</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">093d3723-461b-4782-a1a0-6cc5203b1ce3</cbc:ID>
                                        <cbc:Description>Reasons why your are not registered</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">53029e73-1cfe-45dd-ae91-36e2f9c4e610</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">012c8f70-2ba4-4273-aeec-5f8e404b75f2</cbc:ID>
                                                <cbc:Description>Evidence supplied</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!... rest of elements removed for brevity -->

VI.2.3 Regulated suitability (service contracts)

Data Structure (Service Contracts)- Regulated

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

Figure 101. Regulated 'Suitability' criterion data structure (for ''service contracts'')

XML Example (Service Contracts)- Regulated

Example of Regulated suitability criterion

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

<!-- Criterion:For service contracts: authorisation of particular organisation needed -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9eeb6d5c-0eb8-48e8-a4c5-5087a7c095a4</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.SUITABILITY.AUTHORISATION</cbc:CriterionTypeCode>
        <cbc:Name>For service contracts: authorisation of particular organisation needed</cbc:Name>
        <cbc:Description>Is a particular membership 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>
        <!-- Legislation removed for brevity -->
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a109e144-f65e-469d-bcda-220f1af34b6c</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">69ff9310-58c0-4407-a579-7e72cb9f38ff</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7696fb3f-9722-43b8-9b91-ad59bb4b8ad2</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">797e0a57-7c63-488b-9e2d-6de58f4d008b</cbc:ID>
                                <cbc:Description>Please describe them</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9089e9d5-3633-4b04-8e9e-bc9daa623f06</cbc:ID>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a69cb7c-f594-4738-a5a1-2b76fc8ab021</cbc:ID>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.2.4 Self-contained suitability (service contracts)

Data Structure (service contracts) - Self-contained

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

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

XML Example (service contracts) - Self-contained

Example of Self-contained suitability criterion

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

<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9eeb6d5c-0eb8-48e8-a4c5-5087a7c095a4</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.SUITABILITY.AUTHORISATION</cbc:CriterionTypeCode>
        <cbc:Name>For service contracts: authorisation of particular organisation needed</cbc:Name>
        <cbc:Description>Is a particular membership 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:Legislation> <!-- data elements removed for brevity -->
        </cac:Legislation>
        <!-- Main group containing everything REQUIREMENTs and QUESTIONs -->
        <cac:TenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a53561d5-6614-4dbe-987e-b96f35387f46</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- CAPTION announcing that a list of Lot IDs is coming. Addressed to software applications for GUI documentation purposes. -->
            <cac:TenderingCriterionProperty>(1)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d37f2545-fc73-49f6-a77c-80f099dbf6db</cbc:ID>
                <cbc:Description>Lots the requirement apply to</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>(2)
            </cac:TenderingCriterionProperty>
            <!-- The list of Lot IDs starts here. -->
            <cac:TenderingCriterionProperty>(3)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cfbc1c7f-9bc7-4af0-9d95-ba9f761e9ebd</cbc:ID>
                <cbc:Description>LotID</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <cac:TenderingCriterionProperty>(3)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cfbc1c7f-9bc7-4af0-9d95-ba9f761e9ebd</cbc:ID>
                <cbc:Description>LotID</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <cac:TenderingCriterionProperty>(3)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cfbc1c7f-9bc7-4af0-9d95-ba9f761e9ebd</cbc:ID>
                <cbc:Description>LotID</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <cac:TenderingCriterionProperty>(3)
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">85835a9f-0a1a-495a-bd78-2e5af121bdbb</cbc:ID>
                            <cbc:Description>LotID</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                            <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ExpectedID>
                        </cac:TenderingCriterionProperty>
            <!-- The list of Lot IDs ends here. -->
            <!-- The REQUIREMENTs by the CA related to this criterion start here. In this case, the REQUIREMENT is that the EO has to provide authorisations
                that are issued by the specific organisation cited by the CA in this REQUIREMENT.-->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>(4)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3aacb82e-afba-440c-b64e-1834007965a2</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <!-- The name of the organisation issuing the authorisation: the Spanish food safety agency. -->
                <cac:TenderingCriterionProperty>(5)
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6d80364e-4084-429f-94e0-bd2cbeac489a</cbc:ID>
                    <cbc:Description>Register name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    <cbc:ExpectedDescription languageID="es">Agencia española para el control alimentario</cbc:ExpectedDescription>(6)
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e0fb6013-1711-46f0-8597-7ee3a2fdccb1</cbc:ID>
                    <cbc:Description>URL</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">URL</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeID="URI" schemeAgencyID="EU-COM-GROW">http://datos.gob/aeca.es/autorizaciones</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <!-- The QUESTIONs associated to the REQUIREMENT and Lots above start here. -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>(7)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6cce6b8e-c53d-4598-8150-ac49aba3b9c7</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <!-- 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. -->
                <cac:TenderingCriterionProperty>(8)
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c4ad642-d057-4fee-a73a-3623f9689677</cbc:ID>
                    <cbc:Description>Your Answer</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- If yes... provide the registration number for the authorisation. -->
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">70d5bbcf-0581-4d0f-b5c7-8b604a791972</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>(9)
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a371db35-35ea-4f1f-9499-1426cf69d7d3</cbc:ID>
                        <cbc:Description>Registration number</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <!-- If no... provide a justification for not having this authorisation issued by the required organisation.-->
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3a4a5421-81cc-468e-b69f-b86bf8c7932d</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>(10)
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">62b65cc3-136a-4715-83b5-c09eb6c70619</cbc:ID>
                        <cbc:Description>Reasons why your are not registered</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <!-- Evidences, e.g. supporting the justification about why the authorisation is not registered in the required organisation could be provided. -->
                <cac:SubsidiaryTenderingCriterionPropertyGroup><!-- data elements removed for brevity. --></cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
    </cac:TenderingCriterion>

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

1	This is a CAPTION, software applications can use it to document the GUI.
2	As this is a CAPTION no value is expected to be provided by the Contracting Authority (thus the absence of a `cbc:Expected…` element) nor by the Economic Operator (thus the value NONE`for the element `cac:ValueDataTypeCode).
3	A sequence of REQUIREMENTs related to Lots start here. In this case, this element `cac:TenderingCriterionProperty` is the first of a list of a series of Lots for which the following REQUIREMENTS inside the parent group (group with UUUID `a53561d5-….`) apply. In this example, the list of Lots are `Lot1`, `Lot2`, `Lot4` and `Lot5`.
4	The REQUIREMENTs by the CA related to this criterion start here.
5	The name of the organisation issuing the authorisation: the Spanish food safety agency.
6	Notice the use of the attribute `languageID` meaning, in this example, that the name is expressed in Spanish.
7	The QUESTIONs associated to the REQUIREMENT and Lots above start here.
8	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.
9	If yes… provide the registration number for the authorisation.
10	If no… provide a justification for not having this authorisation issued by the required organisation.

VI.3 Turnovers

See formal requirements related to 'Turnover' criteria for the Self-contained 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

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).
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;
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) CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.GENERAL_YEARLY, CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_YEARLY;
  - (Average) CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.AVERAGE_YEARLY, CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_YEARLY

Differences between Regulated and Self-contained turnovers

The REGULATED version expects a constant amount of groups of properties made of Amount, Start Date, End Date. The ESPD Service, for instance, expects general or specific yearly turnovers for the five past years. Thus, being the current year 2017, the ESPD Service generates a view for the economic operator with fields for 2016, 2015, 2014, 2013 and 2012. See mock-up below for the Regulated version of the general and specific yearly turnovers.
In the new SELF-CONTAINED:
- For the general yearly turnover the contracting authority 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 contracting authority required.
- For the average yearly turnover the contracting authority can specify the period (“Start Date” and “End Date”) 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 contracting authority can specify the number of fiscal years for which the EO will have to provide turnovers (e.g. last 5 years); the CPVs, with one or several Common Procurement Vocabulary codes to indicate the activities that were developed during those fiscal years for that Turnover. The CA could be able to select the CPV codes from a pop-up window with the whole CPV structure. Both the CPV code and the “Business domain description” could be displayed, both in the pop-up window (in order to facilitate the selection of the codes to be included in the ESPD) and in the ESPDResponse; 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 contracting authority 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 CPVs, with one or several Common Procurement Vocabulary codes to indicate the activities that were developed during those fiscal years for that Turnover; the minimum amount expected from the EO, for which the EO’s average yearly turnover must equal or be greater; and the currency.

VI.3.1 Regulated general turnover

Mock-up - contracting authority perspective

The mock-up below shows the perspective of the contracting authority (CA) when preparing a new ESPD Request. Notice that the CA may select the type of turnover. The economic operator, while preparing the ESPD Response, should only see these turnovers, and not the unselected ones.

In this case the contracting authority (CA) requires only a general average turnover. You will notice that this case is identical to the Regulated specific average turnover. The only difference between both is the wording of the criterion. In this "general" case the CA asks for the average in general, regardless of the business area covered by the contract.

Figure 103. Regulated 'general yearly turnover' CA mock-up

Mock-up - economic operator perspective

The economic operator has to provide turnovers for all the years required by the contracting authority. For all of them it can also provide one evidence.

Figure 104. Regulated 'general yearly turnover' EO mock-up

Data Structure - Regulated

Regulated 'yearly turnover' criterion data structure

Figure 105. Regulated 'general yearly turnover' criterion data structure

XML Example - Regulated

Regulated 'general yearly turnover'

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

<!-- Criterion:General yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">499efc97-2ac1-4af2-9e84-323c2ca67747</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.GENERAL_YEARLY</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 or the ESPD is as follows:</cbc:Description>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0fe1a87a-2147-4af3-b3c9-b72cf92f2afe</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">954bc8eb-5c54-4743-9b73-323ce69a9dd6</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6c24be1c-f941-4e0b-af0f-2f6520dd3d62</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">70b936fd-c1e6-46a7-a1a9-14a5952be7d5</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b2792cd0-7c34-43c0-b872-4a3faae5114f</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e6b1f517-db48-40b6-b4c6-92fdb97d7d60</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c2741306-171e-44da-a9a7-9f23ff5df900</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">abc4f7c1-e6ec-4b9d-bb38-2fc62ae73a59</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bbe1f8bc-0dab-43cd-9029-eb44ae46bd6e</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">179cf46a-5c03-4523-bbe2-b5a8db427842</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f2d3c4af-98a1-4249-8cc3-857b9bf59ecb</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.2 Self-contained general turnover

In the new Self-contained version 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 - contracting authority perspective

Notice that the contracting authority 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.

Self-contained 'General and Specific Yearly Turnovers' CA mock-up

Figure 106. Self-contained 'General Yearly Turnovers' CA mock-up

Mock-up - economic operator perspective

Self-contained 'General and Specific Yearly Turnovers' EO mock-up_EO

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

Data Structure - Self-contained

In this this figure what it is being shown is that the contracting authority 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.

Figure 108. Self-contained 'General Yearly Turnovers' criterion data structure

XML Example - Self-contained

Self-contained general yearly turnover

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

<!-- Criterion:General yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">499efc97-2ac1-4af2-9e84-323c2ca67747</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.GENERAL_YEARLY</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 or the ESPD is as follows:</cbc:Description>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">91b9fce0-b813-4776-ab8e-7bec8800fb10</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">31e65051-2fa5-411b-8871-1486b7cbf0ad</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e4a5e2de-ec78-48ba-b78c-b5f4378be4a5</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b7b4a2e6-07c9-490b-b219-6899ce9a3184</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">100000</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">146d60a8-ee60-43f7-af3c-4d35679fe134</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">120000</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1875b9d4-9746-4d2a-bec7-1916036a5eaf</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">130000</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">724ba593-e19a-46fc-a2ea-94b1ca9d5d37</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c1af79e2-2328-4c27-b6ad-22ccc0f2deed</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">961a0dd6-d167-4751-8a72-bff18e33d8c3</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ee145623-127f-404a-baef-dc1f9c5267a4</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9bd6b906-c05c-4c7e-a0d1-76d200eaca50</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a514207f-da5e-4ef0-909d-788485e2d661</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">89c413f6-5be4-446e-90e7-0bcff1c03989</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fdcba069-3d40-480a-8e1f-f7f272e2d921</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b0dfbbbb-b8e3-4797-ae40-85715745532a</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.3 Regulated average yearly turnover

You will notice that the case of the Regulated average yearly turnover is identical to the Regulated specific average turnover.

Mock-up - contracting authority perspective

In this case the contracting authority, while preparing a new ESPD Request, has selected to require only an average yearly turnover. The economic operator will have to specify the number of years for which it provides the average turnover.

Figure 109. Regulated 'average yearly turnover' CA mock-up

Mock-up - economic operator perspective

Notice that, in the REGULATED mode it is the economic operator who specifies the number of years for the average turnover. Additional it also must provide the amount corresponding to the average and the currency for that amount.

Figure 110. Regulated 'average yearly turnover' EO mock-up

Data Structure - Regulated

Figure 111. Regulated 'average yearly turnover' criterion data structure

XML Example - Regulated

Regulated 'average yearly turnover'

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

<!-- Criterion:Average yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b16cb9fc-6cb7-4585-9302-9533b415cf48</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.AVERAGE_YEARLY</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 in the ESPD, the relevant notice or or the ESPD is as follows:</cbc:Description>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">57e8b7f1-1329-4d3e-86d9-9bcbdeb4279f</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e1886054-ada4-473c-9afc-2fde82c24cf4</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0d0a059d-c984-465c-8baa-416c766b8a11</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Number of years</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dbb840c8-b6af-4cfd-a9b8-bb53ac0406ec</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Average turnover</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3d1b7a9d-5ab0-4d5d-a34e-773a6fa09b59</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7474ed7c-a850-444a-9716-7ce800073571</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.4 Self-contained average yearly turnover

Mock-up - contracting authority perspective

For criteria of type “average yearly turnover”, the following fields can be specified by the contracting authority:

The period (“Start Date” and “End Date”) encompassing the yearly turnovers for which the average is to be provided by the economic operator (EO);
The minimum amount for which the EO’s average yearly turnover must be equal or greater;
The currency;

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

Figure 112. Self-contained 'average yearly turnover' CA mock-up

Mock-up - economic operator perspective

In turn, the economic operator:

Will have to provide the average amount and currency for the required period; and
May provide some additional information in a free-text field.

Self-contained 'average yearly turnover' EO mock-up_EO

Figure 113. Self-contained 'average yearly turnover' EO mock-up

Data Structure - Self-contained

Figure 114. Self-contained 'average yearly turnover' criterion data structure

XML Example - Self-contained

Self-contained average yearly turnover

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

<!-- Criterion:Average yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b16cb9fc-6cb7-4585-9302-9533b415cf48</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.AVERAGE_YEARLY</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 in the ESPD, the relevant notice or or the ESPD is as follows:</cbc:Description>
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">550c3b95-77a6-4e94-9f62-e97c34215ad8</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a360ae89-2625-4d7b-bd28-a6f0397ef08f</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a994d3b-1493-48bd-9468-bba0caa4d902</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">87194ddb-eab7-4b80-9f56-cb5c81ee2c6c</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start date; End date;</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</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 -->
                        <cac:ApplicablePeriod>
                                <cbc:StartDate>2016-01-01</cbc:StartDate>
                                <cbc:EndDate>2016-01-01</cbc:EndDate>
                        </cac:ApplicablePeriod>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ba3a72f0-25b8-47fc-a8a1-733249d748d7</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">120000</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e1886054-ada4-473c-9afc-2fde82c24cf4</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8f62195-feff-40f1-8b0e-20e38fa42acf</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Average for the required period</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9d48092f-7fdc-4a71-8583-dc057b148656</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Additional information</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>


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

VI.3.5 Regulated specific yearly turnover

Mock-up - contracting authority perspective

In this case the contracting authority (CA) requires only a specific average turnover. You will notice that this case is identical to the Regulated general average turnover. The only difference between both is the wording of the criterion. The difference between "general" and "specific" lies in the fact that for the second one the CA specifies that the turnover must relate to the specific business area covered by the contract.

Figure 115. Regulated 'specific yearly turnover' CA mock-up

Mock-up - economic operator perspective

Notice that in the Regulated ESPD the MS defined up to five groups of turnovers for the past recent 5 years. This is also visible in the data structure below. The Self-contained ESPD allows the CA to specify the number of turnovers for the procurement document.

Figure 116. Regulated 'specific yearly turnover' EO mock-up

Data Structure - Regulated

The figure below how the structure of the five groups of turnovers specified by the MS are organised:

Regulated 'specific yearly ' criterion data structure

Figure 117. Regulated 'specific yearly turnover' criterion data structure

XML Example - Regulated

Regulated 'specific yearly turnover'

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

<!-- Criterion:Specific yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">074f6031-55f9-4e99-b9a4-c4363e8bc315</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_YEARLY</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">869f2572-9738-484e-97e0-1edeec929dc7</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">49c44bbb-071c-4ee6-ab50-e8fedeab0d49</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b4da0891-57f7-4fbd-a23a-db291cb81d52</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e3f45c47-d2e1-4e8e-a8e6-22d66dc75817</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4d2428bd-5f88-455e-80f2-0f5b42267abb</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">02e4183d-1a96-4369-afda-4e3f4b14738d</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d3855af4-c0d5-47e3-b6e7-79b48d7a276b</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d5b14e2c-6fe5-437c-bf1b-98dd5b84a093</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a4705528-cb31-4687-968c-7731acd4bdee</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e57fc2ae-9782-46df-b39e-4106e872e6cc</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2680b6c0-005b-41cf-9d85-95d13f432f26</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.6 Self-contained specific yearly turnover

One characteristic of the "specific" turnovers is that the contracting authority 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 or to use the Common Procurement Vocabulary (CPV) codes to narrow as much as possible the business domain.

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

See also section about the SELF-CONTAINED specific average turnover.

Mock-up - contracting authority perspective

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

The number of fiscal years for which the economic operator (EO) will have to provide turnovers; e.g. last 5 years;
The CPVs, with one or several Common Procurement Vocabulary codes to indicate the activities that were developed during those fiscal years for that Turnover. The CA could be able to select the CPV codes from a pop-up window with the whole CPV structure. Both the CPV code and the “Business domain description” could be displayed, both in the pop-up window (in order to facilitate the selection of the codes to be included in the ESPD) and in the ESPDResponse;
The minimum amount expected from the EO, for which each specific yearly turnover must equal or be greater;
The currency.

Figure 118. Self-contained 'specific yearly turnover' CA mock-up

Mock-up - economic operator perspective

Notice that in this example:

The contracting authority required specific yearly turnovers for the past five years (circle numbered as 1);
The area covered by the contract is classified via three CPV codes. The software application may retrieve the descriptions of the CPV taxonomy (probably from the EU Publications Office SIMAP or MDR services) and show them in the next to the caption "Business domain description". The contracting authority may change those descriptions manually;
The minimum amount required by the contracting authority, and the currency for that amount (the EO should be able to express an identical or greater economic value in a different currency);
The software application has produced up to five groups of properties for each of the last five Fiscal Years (FY1 to FY5);
The economic operator has provided answers for all the properties of each Fiscal Year.

Self-contained 'specific yearly turnover' EO mock-up_EO

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

Data Structure - Self-contained

Notice that:

The criterion may have one or more linked national sub-criteria downloaded from e-Certis (SUBCRITERON structure, cardinality 0..n);
The contracting authority is able to specify the number of fiscal years (REQUIREMENT 'Number of fiscal years');
The contracting authority can specify one or more CPV to delimit the area covered by the contract (the REQUIREMENT 'CPV Code' has cardinality 1..n);
The description of the business area could be pre-filled with the descriptions coming from the CPV taxonomy or manually introduced;
The contracting authority does also specifies the minimum amount required for this specific turnover.
The rest of the criterion are the questions for the economic operator to answer: period and amount (and currency in the amount attribute @currencyID).

Figure 120. Self-contained 'specific yearly turnover' criterion data structure

XML Example - Self-contained

Self-contained specific yearly turnover

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

<!-- Criterion:Specific yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">074f6031-55f9-4e99-b9a4-c4363e8bc315</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_YEARLY</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:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3050f9bb-1541-4c4d-afd3-62d6755f0f4e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e380ff85-e749-4a54-89e4-25d32e01951a</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cad272a6-69f9-4be5-bcba-9215d0bf7182</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ce103845-a9b3-4651-b24b-17d2b1917ba9</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Number of fiscal years</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">3</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6d87673d-af3f-4c39-b0e4-fbef046bd435</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c4a6643-225f-4db9-b2d3-3f1af2d94629</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>CPVs:</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d343c5b1-1e3d-4468-814e-e84a32681c54</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>CPV Code</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</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:ExpectedCode>70000000-5</cbc:ExpectedCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5665ed79-c3d6-4402-9e6c-56799bd2cdb0</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Business domain description</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</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:ExpectedCode>IT consulting / development of semantic interoperability solutions</cbc:ExpectedCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">14f56765-a7ae-495b-b1be-6b0855b51257</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2eecaf23-845a-4d6a-9ab7-e54b86ebc8f3</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start date; End date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">df26966f-5201-4e9c-87df-4ad0dcaf5451</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.7 Regulated specific average turnover

You will notice that the case of the Regulated specific average turnover is identical to the Regulated general average turnover.

Mock-up - contracting authority perspective

For this case, the contracting authority has selected "Specific average turnover'. The economic operator should not see the rest of turnovers.

Figure 121. Regulated 'specific average turnover' CA mock-up

Mock-up - economic operator perspective

Figure 122. Regulated 'specific average turnover' EO mock-up

Data Structure - Regulated

Figure 123. Regulated 'specific average turnover' criterion data structure

XML Example - Regulated

Regulated 'specific average turnover'

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

<!-- Criterion:Specific yearly turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">074f6031-55f9-4e99-b9a4-c4363e8bc315</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_YEARLY</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">823a152a-7083-4e8d-8e8d-71c516ba118f</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">23fa4f99-e862-49e9-b061-6875d636e41e</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c17eb4db-f7a7-44bf-9342-00df6d19c5a2</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">69a4c8e9-773b-4fad-ba61-46aa102c3bd2</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41db6792-3a55-48dd-9906-1857e41be1ac</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e52e9ee3-f540-4f95-b308-f8e62353a5b5</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">acc71220-ec14-45a9-b111-5503df42bbcd</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0c4f2265-b7a4-4ec4-9aed-1722a52bd89f</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">153c8509-39b0-48e2-91f3-273bb95bcb94</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0cd9c1c-e90a-4ff9-bce3-ac0fe31abf16</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7dbaf4b2-ddc3-4cf2-93e7-d4c4ba397734</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a809495c-8f34-4773-9257-d7f768a1e009</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start Date; End Date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.3.8 Self-contained specific average turnover

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

Mock-up - contracting authority perspective

Self-contained 'specific average turnover' CA mock-up_EO

Figure 124. Self-contained 'specific average turnover' CA mock-up

Mock-up - economic operator perspective

Self-contained 'specific average turnover' EO mock-up_EO

Figure 125. Self-contained 'specific average turnover' EO mock-up

Data Structure - Self-contained

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

Figure 126. Self-contained 'specific average turnover' criterion data structure

XML Example - Self-contained

Self-contained specific average turnover

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

<!-- Criterion:Specific average turnover -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d3dfb714-f558-4512-bbc5-e456fa2339de</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SPECIFIC_AVERAGE</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:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">51fd8d2d-3d0d-4754-80ca-93b87771f905</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3108c889-9480-4c47-bd1c-0b5772d21c58</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7efd988d-562a-4d42-ae31-9ea921ace7df</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5ca58d66-3ef1-4145-957c-45d5b18a837f</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8939dbc-8f09-4fce-9692-96e6e8fd2c57</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start date; End date;</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</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 -->
                        <cac:ApplicablePeriod>
                                <cbc:StartDate>2016-01-01</cbc:StartDate>
                                <cbc:EndDate>2016-01-01</cbc:EndDate>
                        </cac:ApplicablePeriod>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">dc506cc2-2a39-4567-b2ee-bbffd0968d08</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Minimum requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">120000</cbc:ExpectedAmount>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e1886054-ada4-473c-9afc-2fde82c24cf4</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d3b63b1a-76fc-4c09-b6af-4b943968a683</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Average for the required period</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a6e7b107-9697-4f35-86b9-34b8366eff9b</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Additional information</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>


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

VI.4 EO setup

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

Differences between Regulated and Self-contained

For both versions, REGULATED and SELF-CONTAINED, the structure of the QUESTION criterion is identical and very simple. It only asks for a year: in the criterion description the Contracting Authority is requiring that in case the information concerning turnover (general or specific) is not available for the entire period required, the Economic Operator states the date on which it was set up or started trading. Thus the only criterion defined under this data structure is classified with the code:
- CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SET_UP
The SELF-CONTAINED is able to keep in the XML documents the national sub-criteria defined by the MS in e-Certis.

Mock-up - contracting authority perspective

In this case the contracting authority has selected the option Set up of economic operator just in case the other specific average turnover is not available:

Figure 127. 'Economic operator setup’CA mock-up

Mock-up - economic operator perspective

And in case the economic operator could not provide the specific average turnover will have to specify a date as a response to the QUESTION:

Figure 128. 'Economic operator setup’EO mock-up

Data Structure - Regulated

'Economic operator setup' criterion data structure

Figure 129. 'Economic operator setup' criterion (REGULATED) data structure

Data Structure - Self-contained

The data structure for the SELF-CONTAINED version is identical to the one in the REGULATED version, except for the fact that the XML instance is able to keep the national sub-criteria defined by the Member State in e-Certis.

Figure 130. 'Economic operator setup' criterion (SELF-CONTAINED) data structure

XML Example - Self-contained

'Economic operator setup' criterion

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

<!-- Criterion:Set up of economic operator -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">77f481ce-ffb6-483f-8e2b-c78db5e68292</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.TURNOVER.SET_UP</cbc:CriterionTypeCode>
        <cbc:Name>Set up of economic operator</cbc:Name>
        <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>
        <cac:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8cb78467-9d4c-4990-a41f-0131dc639cd8</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b97a9061-409c-4fb7-977e-33e64c1db6a2</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c753a2c5-59e6-4970-b6eb-27224e96bf76</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">23c7e5bb-8ef6-4119-a1e9-183debf7b9c3</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Please specify</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.5 Financial ratios

Differences between Regulated and Self-contained

The REGULATED version expects the economic operator to introduce a numeric value for the ratio (e.g. 0.7, 1.2, etc.) and a description explaining the meaning (the type of ratio) of this numeric value;
In the REGULATED version the possibility of adding more than one ratio is given to the economic operator;
In the SELF-CONTAINED version the possibility of adding more than one ratio is given to the contracting authority;
The SELF-CONTAINED version instead allows the contracting authority:
- To specify the number of the past recent years for which it will require Ratios;
- To specify one of the codes defined by BACH to specify the type of the ratio (see BACH Banque France, and FinancialRatioType);
- May specify a minimum requirement (the economic operator must provide a ratio above this minimum requirement).
The SELF-CONTAINED version expects the economic operator to introduce only the value of the ratio, which must be equal or greater than the minimum requirement specified by the contracting authority (if any was specified).
The data structures of REGULATED and SELF-CONTAINED are different. See the sub-sections below about the Regulated financial ratio and the Self-contained financial ratio for details. There is only one criterion under the category "financial ratio" and it is classified with the code:
- CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO
The SELF-CONTAINED is able to keep in the XML documents the national sub-criteria defined by the MS in e-Certis regarding this criterion.

VI.5.1 Regulated financial ratios

Mock-up - contracting authority perspective

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

Figure 131. Regulated 'financial ratio' CA mock-up

Mock-up - economic operator perspective

The economic operator has to respond with the numeric value corresponding to the financial ratio and with a description to identify the type of ratio:

Figure 132. Regulated 'financial ratio' EO mock-up

Data Structure - Regulated

Figure 133. Regulated 'financial ratio' criterion data structure

XML Example - Regulated

Regulated Regulated 'financial ratio' criterion

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

<!-- Criterion:Financial ratio -->
        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e4d37adc-08cd-4f4d-a8d8-32b62b0a1f46</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO</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:Legislation>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7a182b9e-4c3f-4087-a3ae-9a3791ecd713</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                        </cac:Language>
                </cac:Legislation>
                <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">83e3dcc4-c9b3-47e5-9fb8-ffd8386679f1</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a749f03a-abde-4e95-b999-fed640ff96e4</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Please provide your ratios</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

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

VI.5.2 Self-contained financial ratios

REQUIREMENT

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

Mock-ups - contracting authority perspective

Self-contained 'financial ratio' CA mock-up

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

In the Self-contained version the contracting authority specifies procurement procedure-specific requirements:

Self-contained 'financial ratio' CA REQUIREMENT(s) mock-up

Figure 134. Self-contained 'financial ratio' CA mock-up REQUIREMENT(s) edition

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 contracting authority):

Figure 135. Self-contained 'financial ratio' EO mock-up

Data Structure - Self-contained

REQUIREMENT(s) specified by the contracting authorities 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 style-sheet that takes the spreadsheet (file content.xml ^[6]) and produced the XML instance.

Figure 136. Self-contained 'financial ratio' criterion data structure

XML Example - Self-contained

Self-contained Financial Ratio

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

  <!-- Criterion:Financial ratio -->
         <cac:TenderingCriterion>
                 <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                         schemeVersionID="2.1.0">e4d37adc-08cd-4f4d-a8d8-32b62b0a1f46</cbc:ID>
                 <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW"
                         listVersionID="2.1.0"
                         >CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO</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:Legislation>
                         <!-- removed for brevity. See other XML examples for details on this element. -->
                 </cac:Legislation>
                 <cac:TenderingCriterionPropertyGroup>
                         <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                                 schemeVersionID="2.1.0"
                                 >cc1da737-6c4e-4f4e-821d-c260029058f6</cbc:ID>
                         <cbc:PropertyGroupTypeCode listID="PropertyGroupType"
                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                 >ON*</cbc:PropertyGroupTypeCode>
                         <cac:TenderingCriterionProperty> (1)
                                 <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                                         schemeVersionID="2.1.0"
                                         >79ae87bd-19bf-441e-9a6e-a61a315fa0c2</cbc:ID>
                                 <cbc:Description>Select the period applicable for all ratios</cbc:Description>
                                 <cbc:TypeCode listID="CriterionElementType"
                                         listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                         >REQUIREMENT</cbc:TypeCode>
                                 <cbc:ValueDataTypeCode listID="ResponseDataType"
                                         listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                         >PERIOD</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 -->
                                 <cac:ApplicablePeriod>
                                         <cbc:StartDate>2016-01-01</cbc:StartDate>
                                         <cbc:EndDate>2017-01-01</cbc:EndDate>
                                 </cac:ApplicablePeriod>
                         </cac:TenderingCriterionProperty>
                         <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                 <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                                         schemeVersionID="2.1.0"
                                         >ee486082-93fa-4c17-8920-fdf01b890bd1</cbc:ID>
                                 <cbc:PropertyGroupTypeCode listID="PropertyGroupType"
                                         listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                         >ON*</cbc:PropertyGroupTypeCode>
                                 <cac:TenderingCriterionProperty>
                                         <cbc:ID schemeID="CriteriaTaxonomy"
                                                 schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"
                                                 >8ba2d74f-2d1d-47d2-b713-27c03f87cafa</cbc:ID>
                                         <cbc:Description>Ratio Type</cbc:Description>
                                         <cbc:TypeCode listID="CriterionElementType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                         <cbc:ValueDataTypeCode listID="ResponseDataType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >CODE</cbc:ValueDataTypeCode>
                                         <cbc:ExpectedCode listID="FinancialRatio" listAgencyID="BACH" listVersionID="1.0">R11</cbc:ExpectedCode>(2)
                                 </cac:TenderingCriterionProperty>
                                 <cac:TenderingCriterionProperty>
                                         <cbc:ID schemeID="CriteriaTaxonomy"
                                                 schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"
                                                 >47d71610-4921-4a7c-aed5-1f95149837ef</cbc:ID>
                                         <cbc:Description>Definition</cbc:Description>(3)
                                         <cbc:TypeCode listID="CriterionElementType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >REQUIREMENT</cbc:TypeCode>
                                         <cbc:ValueDataTypeCode listID="ResponseDataType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >DESCRIPTION</cbc:ValueDataTypeCode>
                                         <cbc:ExpectedDescription>Total balance sheet/Total
                                                 equity</cbc:ExpectedDescription>
                                 </cac:TenderingCriterionProperty>
                                 <cac:TenderingCriterionProperty>
                                         <cbc:ID schemeID="CriteriaTaxonomy"
                                                 schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"
                                                 >575681d5-8ffc-40c0-883c-14de01193096</cbc:ID>
                                         <cbc:Description>Minimum requirement</cbc:Description>(4)
                                         <cbc:TypeCode listID="CriterionElementType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >REQUIREMENT</cbc:TypeCode>
                                         <cbc:ValueDataTypeCode listID="ResponseDataType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >QUANTITY</cbc:ValueDataTypeCode>
                                         <cbc:ExpectedValueNumeric>0.5</cbc:ExpectedValueNumeric>
                                 </cac:TenderingCriterionProperty>
                         </cac:SubsidiaryTenderingCriterionPropertyGroup>
                         <cac:SubsidiaryTenderingCriterionPropertyGroup>(11)
                                 <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW"
                                         schemeVersionID="2.1.0"
                                         >e9aa7763-c167-4352-8060-1a3d7d3e2662</cbc:ID>
                                 <cbc:PropertyGroupTypeCode listID="PropertyGroupType"
                                         listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                         >ON*</cbc:PropertyGroupTypeCode>
                                 <cac:TenderingCriterionProperty>
                                         <cbc:ID schemeID="CriteriaTaxonomy"
                                                 schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"
                                                 >705c99d0-01f1-4554-a789-776bc1c7681a</cbc:ID>
                                         <cbc:Description>Please provide your ratio</cbc:Description>
                                         <cbc:TypeCode listID="CriterionElementType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >QUESTION</cbc:TypeCode>
                                         <cbc:ValueDataTypeCode listID="ResponseDataType"
                                                 listAgencyID="EU-COM-GROW" listVersionID="2.1.0"
                                                 >QUANTITY</cbc:ValueDataTypeCode>
                                 </cac:TenderingCriterionProperty>
                         </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                 <cac:SubsidiaryTenderingCriterionPropertyGroup>(5) (6) (7)
                                                                 <!--  Multiple types of ratios can be required by the contracting authority for this particular procurement procedure. See mock-up above. This subgroup would contain the second ratio, but has been removed for brevity. -->
                                                 </cac:SubsidiaryTenderingCriterionPropertyGroup
                                                 <cac:SubsidiaryTenderingCriterionPropertyGroup>(8) (9) (10)
                                                                 <!--  Multiple types of ratios can be required by the contracting authority for this particular procurement procedure. See mock-up above. This subgroup would contain the second ratio, but has been removed for brevity. -->
                                                 </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                 <cac:SubsidiaryTenderingCriterionPropertyGroup>(12)
                                                                 <!-- Structure "Is this information available electronically would follow next. Removed for brevity. See other examples in other sections. -->
                                                 </cac:SubsidiaryTenderingCriterionPropertyGroup
                                                 <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                                 <!-- Structure "Is this information available electronically would follow next. Removed for brevity. See other examples in other sections. -->
                                                 </cac:SubsidiaryTenderingCriterionPropertyGroup
                 </cac:TenderingCriterionPropertyGroup>
         </cac:TenderingCriterion>
<!... rest of elements removed for brevity -->

1	The period applicable for all the ratios required by the Contracting Authority. 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 Contracting Authority 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 contracting authority 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 contracting authority according to the example illustraded in the mock-up above (the contracting authority 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 contracting authority according to the example illustraded 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 VIII.7 Answering Questions 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.

VI.6 Risk indemnity insurance

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

Other requirements:

REQUIREMENT

Compulsory use of the code list InsuranceType for the SELF-CONTAINED version of the ESPD.

Differences between Regulated and Self-contained

In the REGULATED version it is the economic operator who provides data about one risk indemnity insurance;
In the SELF-CONTAINED version the contracting authority can require one minimum amount for multiple insurances, each one of a different type (see the code list InsuranceType);
In the SELF-CONTAINED version when the amount specified by the economic operator (EO) is lower than the minimum required, the EO will be able to indicate that the EO commits to obtain the minimum amount required (though it doesn’t have it now).
In the SELF-CONTAINED version, for the type of insurance "Employers (Compulsory) Liability Insurance" (and only for this type), the EO will also be able to indicate whether it is exempt or not.
The SELF-CONTAINED is able to keep in the XML documents the national sub-criteria defined by the MS in e-Certis.
For both versions, REGULATED and SELF-CONTAINED The only criterion defined under this data structure is classified with the code:
- CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.RISK_INDEMNITY_INSURANCE

VI.6.1 Regulated risk indemnity insurance

Mock-up - contracting authority perspective

The contracting authority has selected the option Professional risk indemnity insurance for its inclusion in the ESPD Request. Notice that the Member State (Finland) defined in e-Certis a specific national criterion related to the risk indemnity insurance. This national criterion will not be saved into the exported XML instance, as this is a REGULATED version of the ESPD.

Figure 137. 'Regulated risk indemnity insurance’CA mock-up

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:

'Regulated 'risk indemnity insurance' EO mock-up

Figure 138. Regulated 'risk indemnity insurance' criterion data structure

Data Structure - Regulated

Figure 139. Regulated 'risk indemnity insurance' criterion data structure

XML Example - Regulated

Regulated 'risk indemnity insurance' criterion

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

<!-- Criterion:Professional risk indemnity insurance -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7604bd40-4462-4086-8763-a50da51a869c</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.RISK_INDEMNITY_INSURANCE</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4004e7e2-9107-4bf1-867c-2f384e4198cf</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">42dc8062-974d-4201-91ba-7f2ea90338fd</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7e1a7918-3f66-42e6-b0fb-26be48aabeb5</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a5846245-81da-4651-82db-97f1796c4488</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2cd3ff94-b65f-4579-a4ed-c76371e16760</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplier</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!... rest of elements removed for brevity -->

VI.6.2 Self-contained risk indemnity insurance

Mock-ups - contracting authority perspective

The contracting authority has selected the option professional risk indemnity insurance for its inclusion in the ESPD Request. Additionally the contracting authority 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 not Lots): The contracting authority 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;

Self-contained 'risk indemnity insurance' CA mock-up

Figure 140. 'Self-contained risk indemnity insurance' CA REQUIREMENT(s) edition (Procedure without Lots)

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

Figure 141. 'Self-contained risk indemnity insurance' CA REQUIREMENT(s) edition (Procedure divided into Lots).

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:

'Self-contained 'risk indemnity insurance' EO mock-up

Figure 142. 'Economic operator setup’EO mock-up

Data Structure - Self-contained

This structure is quite particular. Notice that:

Multiple national sub-criteria can be defined (as for the rest of criteria); and additionally
Multiple groups of REQUIREMENT(s) and QUESTION(s) can be defined by the contracting authority (CA):
- One group asking optionally for Lots: observe that the cardinality of the Lot IDs is 1..n and have their own sub-group, so a list of LotIDs can be built up; and
- 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.

Figure 143. Self-contained 'risk indemnity insurance' criterion data structure

XML Example - Self-contained

Self-contained 'risk indemnity insurance' criterion (Procedure with Lots)

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

<!-- Criterion:Professional risk indemnity insurance -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7604bd40-4462-4086-8763-a50da51a869c</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.RISK_INDEMNITY_INSURANCE</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:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">86fdb3ce-c54f-4ac0-9649-e204e209ee48</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">02282771-709d-48d6-b43a-a754e0ab6192</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2df5ec1a-462c-4064-8bc5-d9c1feefe505</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">83e3dcc4-c9b3-47e5-9fb8-ffd8386679f1</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f6d006ca-a598-4df5-954e-d926a79aa6bc</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description/>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cc1da737-6c4e-4f4e-821d-c260029058f6</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4b293826-9125-45cf-bbca-bee4fd4ba3fb</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Lots the requirement applies to</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cc1da737-6c4e-4f4e-821d-c260029058f6</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">792b4dfd-adea-45b3-a35d-99f714c736f9</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Lot ID</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0"/>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3b35ff7b-ac33-45e9-ae4c-b628a076f1f1</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Type of insurance</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</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:ExpectedCode>Professional risk indemnity insurance</cbc:ExpectedCode>
                                </cac:TenderingCriterionProperty>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">85241259-6316-40e7-b510-9ab16812ac0a</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Minimum amount</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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">50000</cbc:ExpectedAmount>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">42dc8062-974d-4201-91ba-7f2ea90338fd</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">35f573e9-1ce1-4ba4-a2da-e1635864b9fe</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Amount</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3c2c194b-9854-4354-b87c-9952dfb7c9bb</cbc:ID>
                                <cbc:Name>As an EO I will commit to obtain the minimum amount required</cbc:Name>
                                <cbc:Description>true</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b6dc43a6-edf0-49e5-a21a-6f58cdc0d39d</cbc:ID>
                                <cbc:Name>I am exempt</cbc:Name>
                                <cbc:Description>true</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c235b5fb-f512-416a-b264-7fe7a4241524</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">66ff5c5a-e801-46ab-b976-625e5b464969</cbc:ID>
                                        <cbc:Name/>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

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

Differences between Regulated and Self-contained

In the REGULATED version it is the economic operator who declares other economic and financial information.
In the SELF-CONTAINED version the contracting authority can specify the description of the economic or financial requirement; the minimum amount required and the currency; the period to which the amount relates to; a minimum rating and the rating schema.
In the SELF-CONTAINED the contracting authority can also specify the Lots to which the economic or financial requirement applies. This is not possible in the REGULATED version.
The SELF-CONTAINED is able to keep in the XML documents the national sub-criteria defined by the MS in e-Certis.
For both versions, REGULATED and SELF-CONTAINED, the only criterion defined is classified with the code:
- CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.OTHER_REQUIREMENT(s)

VI.7.1 Regulated other economic or financial requirements

Mock-up - contracting authority perspective

The contracting authority has selected the other economic or financial requirements to be included in the ESPD Request document:

Figure 144. Regulated 'other economic or financial requirements' CA mock-up

Mock-up - economic operator perspective

The only data expected from the economic operator is a textual description:

Figure 145. Regulated 'other economic or financial requirements' EO mock-up

Data Structure - Regulated

The data structure for this criterion is very simple:

Figure 146. Regulated 'other economic or financial requirements' data structure

XML Example - Regulated

Regulated 'other economic or financial requirements' criterion

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

<!-- Criterion:Other economic or financial requirements -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ab0e7f2e-6418-40e2-8870-6713123e41ad</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.OTHER_REQUIREMENT(s)</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">43da675b-f815-49f6-8b40-4ddb659ab317</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">488ca189-bcdb-4bf4-80c7-3ad507fd89fb</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">36a23054-433c-4e48-acc0-436ec5d66677</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Please describe them</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.7.2 Self-contained other economic or financial requirements

Mock-ups - contracting authority perspective

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

Additionally the contracting authority 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 contracting authority will be able to:

Either add multiple requirements. For each requirement, the CA 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.
In the ESPDResponse, the EO will be required to provide, for each requirement, the amount and currency.
When the procedure is divided into Lots: The contracting authority can specify the Lots one particular requirement 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.

Self-contained 'other economic or financial requirements' CA mock-up

Figure 147. Self-contained 'other economic or financial requirements' CA REQUIREMENT(s) edition (Procedure divided into Lots).

Mock-up - economic operator perspective

The economic operator, in its view, sees all the requirements defined by the contracting authority 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.

Figure 148. Self-contained 'other economic or financial requirements' EO mock-up

Data Structure - Self-contained

The structure of this criterion 'other economic or financial requirements' for the SELF-CONTAINED version is also very particular (distinct from the rest of criteria data structures). Notice the following aspects:

It allows for capturing multiple national criteria;
It specifies the Legislation component for the EU parent criterion. So far so good, no differences until now;
There’s a group of REQUIREMENT(s) and QUESTION(s).
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.2 model requires always at least one cac:TenderingCriterionProperty element instance inside a group or sub-group of properties;
Then you have the group for collecting Lots specified by the CA. This spreadsheet would generate only one Lot, unless you add more LotIDs into this sub-group. Observe that the cardinality of the REQUIREMENT (LotID) is multiple, 1..n.
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 contracting authority 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.

Figure 149. Self-contained 'other economic or financial requirements' criterion data structure

XML Example - Self-contained

Self-contained 'other economic or financial requirements' criterion (Procedure with Lots)

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

    <cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ab0e7f2e-6418-40e2-8870-6713123e41ad</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.OTHER_REQUIREMENTS</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:Legislation>
            <cbc:Title>Public Procurement Directive 2014/24/EU</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>eu</cbc:JurisdictionLevel>
            <cbc:Article>Article 58(3)</cbc:Article>
            <cbc:URI>http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.094.01.0065.01.ENG</cbc:URI>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4ddccd16-91e4-4b72-ae0f-78f2f1ab9490</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">df814480-6e5e-4c77-af81-faf76ea01d54</cbc:ID>
                <cbc:Description>Lots the requirement applies to</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cc1da737-6c4e-4f4e-821d-c260029058f6</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ae3a0f6a-942f-45c4-8e99-a9c2001bcc24</cbc:ID>
                    <cbc:Description>Lot ID</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ae3a0f6a-942f-45c4-8e99-a9c2001bcc24</cbc:ID>
                    <cbc:Description>Lot ID</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ae3a0f6a-942f-45c4-8e99-a9c2001bcc24</cbc:ID>
                    <cbc:Description>Lot ID</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">26ece6a2-b360-46c1-890d-8338913b8719</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c62f2c7-0c51-451d-8730-427f92ed618c</cbc:ID>
                    <cbc:Description>Select the type of requirement</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE_BOOLEAN</cbc:ValueDataTypeCode>
                    <cbc:ExpectedCode listID="BooleanGUIControlType" listAgencyID="EU-COM-OP" listVersionID="1.0">RADIO_BUTTON_TRUE</cbc:ExpectedCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ca15c15f-110e-4a10-8d6e-5e41cf5f9098</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">13728a54-21e3-4c84-8b11-48666c3d260f</cbc:ID>
                        <cbc:Description>Description of the economic or financial requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        <cbc:ExpectedDescription>__FinReqsDescription</cbc:ExpectedDescription>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">48c7b3bf-8d1c-4497-a915-78d53ba68089</cbc:ID>
                        <cbc:Description>Minimum amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                        <cbc:MinimumAmount currencyID="EUR">100006</cbc:MinimumAmount>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8b4ae4f0-2849-49ea-a64b-7bb20c60bde4</cbc:ID>
                        <cbc:Description>Start date; End date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                        <cac:ApplicablePeriod>
                            <cbc:StartDate>2000-10-10</cbc:StartDate>
                            <cbc:EndDate>2000-10-10</cbc:EndDate>
                        </cac:ApplicablePeriod>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9b3a04ff-e36d-4d4f-b47c-82ad402b9b02</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"></cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1d89c188-58d2-461e-a4f6-a17f689d87f4</cbc:ID>
                            <cbc:Description>Amount</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cc96aa19-a0be-4409-af58-ff3f3812741b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">57d4160f-20b4-4b43-967b-76b038a2fa6b</cbc:ID>
                        <cbc:Description>Minimum rating</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f07b5174-93ae-46dd-aa26-7f451d97f6a8</cbc:ID>
                        <cbc:Description>Rating scheme</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        <cbc:ExpectedDescription></cbc:ExpectedDescription>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5fe93344-ed91-4f97-bcab-b6720a131798</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"></cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3bd1913b-c461-41eb-87c4-84e003785a56</cbc:ID>
                            <cbc:Description>Rating</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0dbc3bcb-03c9-42de-a26e-9b55e529e847</cbc:ID>
                    <cbc:Description>Is this information available electronically?</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7ca215e9-4f2c-4894-968b-d3f71fe88da0</cbc:ID>
                        <cbc:Description>Evidence supplied</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
    </cac:TenderingCriterion>

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

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

Differences between Regulated and Self-contained

For both versions, REGULATED and SELF-CONTAINED the contracting authority can require references for the type of project (or nature of the contract: works, supplies and services). Software applications should take care of not including those types of contract that were not selected by the contracting authority.
In the REGULATED version the economic operator supplies its references for one of those types of contract.
In the REGULATED version the economic operator provides a description for the reference, the amount of the contract, the period of execution and who where the recipients of its works, supplies or services. 'Amount' here must be interpreted as the amount specific to this reference. See difference between total and specific amounts below.
In the SELF-CONTAINED version the contracting authority can specify the minimum number of references required for the evaluation; an an unlimited number of free-text “requirements”, so the CA can provide requirements very specific to the procurement procedure.
In the SELF-CONTAINED version, and per each reference, the economic operator (EO) can specify more information than for the REGULATED version; e.g. the Lots to which the reference applies; the 'total amount' and the 'specific amount', the 'activity' of the economic operator in this reference, the period of time the execution or performance took, whether this reference must be treated as confidential or not, and the 'receipients' of this reference.
The SELF-CONTAINED is able to keep in the XML documents the national sub-criteria defined by the MS in e-Certis.
For both versions, REGULATED and SELF-CONTAINED, there are three criteria with the same data structure (works, supplies and services references):
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.REFERENCES.WORKS_PERFORMANCE
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.REFERENCES.SUPPLIES_DELIVERY_PERFORMANCE
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.REFERENCES.SERVICES_DELIVERY_PERFORMANCE

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:

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

VI.8.1 Regulated references

Mock-ups - contracting authority perspective

In this example the contracting authority requires references for the contract, the nature of which is about works. Notice that in this case the Member State (Finland in this example) did not define any national criterion linked to the performance of works.

Figure 150. Regulated 'References' CA mock-up

Mock-ups - economic operator perspective

The economic operator can add or remove as many references as needed (buttons '+' and 'paper-bin'). For each reference it will have to provide a description of the reference, the amount of the contract of that referenced work, the period of execution and who where the recipients of the work.

Figure 151. Regulated 'References' CA mock-up' EO mock-up

Data Structure - Regulated

The data structure is quite straight-forward, it is composed of multiple groups (cardinality 1..n) of description, amount, period and recipients:

Figure 152. Regulated 'References' criterion data structure

XML Example - Regulated

Regulated 'Works contracts references' criterion

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

<!-- Criterion:For works contracts: performance of works of the specified type -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cdd3bb3e-34a5-43d5-b668-2aab86a73822</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.REFERENCES.WORKS_PERFORMANCE</cbc:CriterionTypeCode>
        <cbc:Name>For works contracts: performance of works of the specified type</cbc:Name>
        <cbc:Description>For public works contracts only: During the reference period, the economic operator has performed the following works of the specified type. Contracting authorities may require up to five years and allow experience dating from more than five years.</cbc:Description>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8a8db847-1e66-4361-b4fa-be9b8b9f5d2a</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">381bea15-9460-49f7-a6d0-15d13059de29</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0f38723e-33af-414c-876e-1dade0d9b887</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Description</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a9eaf466-506c-49e4-a76a-be6cab45c421</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Amount</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">413643b4-402d-4ec2-b4bf-64fb1954d20f</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Start date; End date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">493e0832-f12f-4ca7-ba10-2a9110b159b4</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Recipients</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b0149663-69ba-4087-9086-3d0f4be4b20c</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">94888c61-19b6-4980-a9b7-2a6f6afa164e</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence suppleid</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">aa36e2f0-a458-46c3-a1f6-361fb434906f</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Verification code</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">252c1469-d170-4a92-a627-59390beac4fb</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Issuer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.8.2 Self-contained references

Mock-ups - contracting authority perspective

As in the previous example, in this example about the self-contained references the contracting authority requires references for the contract, the nature of which is also about works.

For the SELF-CONTAINED version, the contracting authority can specify these REQUIREMENT(s):

The Lots to which all the requirements it will issue must apply;
The minimum number of references expected;
One or more specific requirements in the form of free-texts (notice the buttons to add or remove the requirements.

Figure 153. Self-contained 'References' CA REQUIREMENT(s) edition mock-up

Mock-ups - economic operator perspective

In this SELF-CONTAINED view for the economic operator (EO) can see the lots and requirements specified by the contracting authority (CA), lower left side of the mock-up.
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 contracting authority.
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).
The EO can also state that one reference is confidential, in which case the reference will only be accessible to the evaluation team.

Figure 154. Self-contained '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 Annex I: XML Validation.

Data Structure - Self-contained

The data structure for references caters for:

The definition of multiple national criteria associated to the EU criterion specified in e-Certis;
The creation of the Legislation component associated to the EU criterion;
One group of REQUIREMENT(s) for the contracting authority to specify the general requirements for this criterion (e.g. Lots the references apply to, minimun number of references);
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.

Figure 155. Self-contained 'References' criterion data structure

XML Example - Self-contained (REQUIREMENTs and QUESTIONs)

Self-contained 'References for a works contract' criterion

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

<!-- Criterion:For works contracts: performance of works of the specified type -->
<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cdd3bb3e-34a5-43d5-b668-2aab86a73822</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.REFERENCES.WORKS_PERFORMANCE</cbc:CriterionTypeCode>
    <cbc:Name>For works contracts: performance of works of the specified type</cbc:Name>
    <cbc:Description>For public works contracts only: During the reference period, the economic operator has performed the following works of the specified type. Contracting authorities may require up to five years and allow experience dating from more than five years.</cbc:Description>(1)
    <cac:Legislation>
        <cbc:Title>Public Procurement Directive 2014/24/EU</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>eu</cbc:JurisdictionLevel>
        <cbc:Article>Article 58(4)</cbc:Article>
        <cbc:URI>http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.094.01.0065.01.ENG</cbc:URI>
    </cac:Legislation>
    <cac:TenderingCriterionPropertyGroup>
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">381bea15-9460-49f7-a6d0-15d13059de29</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>

        <!-- CA's REQUIREMENT: minimum number of references expected -->

        <cac:TenderingCriterionProperty>(3)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">02ce3b09-71d0-4b3b-a504-ddfc14d3ef73</cbc:ID>
            <cbc:Description>Minimum number of references</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
            <cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>(3)
        </cac:TenderingCriterionProperty>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- The next property element is imposed by the cardinality in the UBL-2.2 XSD Schema -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3f601c12-10b9-43b9-aec4-0ba43330cdd1</cbc:ID>
                <cbc:Description> </cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>

            <!-- other REQUIREMENTs affecting Lot1, Lot2, Lot4 and Lot5 -->

            <cac:SubsidiaryTenderingCriterionPropertyGroup>(4) (5)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d663aca5-5f3c-4980-b825-81e1bd7db381</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>(4)
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7337b561-13b4-4368-a681-c3cd019f0360</cbc:ID>
                    <cbc:Description>Requirement</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    <cbc:ExpectedDescription>Specific amount greater than 1,000,000 €.</cbc:ExpectedDescription>(4)
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>(5)
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6496b5fb-b7f8-48cb-97f6-ea3663f35636</cbc:ID>
                    <cbc:Description>Requirement</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    <cbc:ExpectedDescription>Exeuted recently, after 2013 in any case.</cbc:ExpectedDescription>(5)
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>

            <!-- Lots affected by this REQUIREMENT. -->

            <cac:SubsidiaryTenderingCriterionPropertyGroup> (2)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">167ab253-4fb7-4e45-81be-b049fba44b3a</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0234b3d-29cb-45b3-b61c-c5080e9384b9</cbc:ID>
                    <cbc:Description>The following requirements apply to lots</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0234b3d-29cb-45b3-b61c-c5080e9384b9</cbc:ID>
                    <cbc:Description>The following requirements apply to lots</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0234b3d-29cb-45b3-b61c-c5080e9384b9</cbc:ID>
                    <cbc:Description>The following requirements apply to lots</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c0234b3d-29cb-45b3-b61c-c5080e9384b9</cbc:ID>
                    <cbc:Description>The following requirements apply to lots</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>

        <!-- QUESTIONs ADDRESSED TO THE EO START HERE. -->

        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a44e24e9-f878-4651-9ead-e0b1387dae09</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>

            <!-- CAPTION imposed by the UBL-2.2 XSD cardinality constraint. -->

            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a4eadb87-4612-4c04-aa45-92ced08c4746</cbc:ID>
                <cbc:Description>Lots these references apply to</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>

            <!--
                The Lots for which the Reference provided by the EO makes sense. For the EO answer see the Responses at the end of the document.
                The EO will answer with the LOT_IDENTIFIERs Lot1 and Lot2. See Response with the UUID 'c6eb0a5a-0d22-4123-8599-1be0e1d38697' in
                the element `cbc:ValidatedCriterionPropertyID`.
            -->

            <cac:SubsidiaryTenderingCriterionPropertyGroup>(6)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b9ac8ecf-5902-408e-a9a6-604568b35e1e</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c6eb0a5a-0d22-4123-8599-1be0e1d38697</cbc:ID>
                    <cbc:Description>Lot ID</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>

            <!--
                The following sub-group of properties are intended for the EO provide information about one Reference. See the Responses at the end of the
                document, where each Response is linked to one and only one of the following QUESTIONs through the UUID of the QUESTION, which in the Response
                is held in the element `cbc:ValidatedCriterionPropertyID`.
            -->

            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8ec5c30-2c17-4936-abbb-392523d873e5</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <!-- QUESTION: Description of the Reference by the EO. See Response at the end of the file. -->(7)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">72b19420-a904-4e4b-8465-a922dcec06b6</cbc:ID>
                    <cbc:Description>Reference description</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: The Total Amount of the Reference, including the amounts that were specific to (share of) other EOs participating in the execution of the work. See Response at the end of the file. -->(8)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c2556c58-72aa-42a6-ad45-568ef9ba1988</cbc:ID>
                    <cbc:Description>Total amount</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: The activity of this economic operator in this work. -->(9)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8886ec57-02d9-461d-932b-25c1bb494c7f</cbc:ID>
                    <cbc:Description>Activity of the economic operator</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: 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)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c78e1d6-1bdf-4129-b86c-89da335c8918</cbc:ID>
                    <cbc:Description>Specific amount</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: Duration of the execution of the work. -->(11)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4cdf40b6-a1dd-461b-81b1-a9669304302f</cbc:ID>
                    <cbc:Description>Period (Start and End dates)</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: The level of confidentiality of the information regarding this Reference. Confidential references provided by the EO cannot be made accessible by the CA to third parties. -->(12)
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">90da53d3-2e8f-47be-9b72-1393e6200e16</cbc:ID>
                    <cbc:Description>Confidential</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- QUESTION: The name of the recipient of the work. -->(13)
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6afa7569-e4c4-4538-be89-84a82b2a301b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bdfb2116-0c4e-4d2c-ae5e-a2b95d767078</cbc:ID>
                        <cbc:Description>Recipient name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION: Name of the contact point, a person in this case. -->(14)
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">95994e82-e650-4567-beab-ba4672d27008</cbc:ID>
                        <cbc:Description>Contact person name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION: Contact e-mail of the recipient of the work.. -->(15)
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6d9355c0-129b-4f70-85f0-36f2ffa6fcb8</cbc:ID>
                        <cbc:Description>Contact email</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">01112025-23d7-41cb-89fe-90a521515742</cbc:ID>
                        <cbc:Description>Contact telephone</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8768d6ff-a82b-49e3-a462-f53a1948d9ab</cbc:ID>
                        <cbc:Description>Is this information available online?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bda20df6-4a52-4487-b32c-480caccefdc1</cbc:ID>
                            <cbc:Description>Evidence Supplied</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a44e24e9-f878-4651-9ead-e0b1387dae09</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">865bd217-ad93-1002-98e7-cf130f727934</cbc:ID>
                <cbc:Description>Lots these references apply to</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b9ac8ecf-5902-408e-a9a6-604568b35e1e</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">849f9eb1-25ad-b69d-01ff-f78765477fad</cbc:ID>
                    <cbc:Description>Lots IDs</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8ec5c30-2c17-4936-abbb-392523d873e5</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6fdc82f1-84b3-d133-2a65-415d47c41ec1</cbc:ID>
                    <cbc:Description>Reference description</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a6096bee-df0e-334f-5b0f-2bdfb59777ce</cbc:ID>
                    <cbc:Description>Total amount</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">145c2bf7-1819-7735-4648-f9614b5e0b2b</cbc:ID>
                    <cbc:Description>Activity of the economic operator</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3c85e650-76af-20b8-b149-344b8fcc4954</cbc:ID>
                    <cbc:Description>Specific amount</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">AMOUNT</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b150493c-d407-bf74-1104-ad6d8eb171ff</cbc:ID>
                    <cbc:Description>Period (Start and End dates)</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERIOD</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c19e2b01-87a0-c4e1-4c75-2be6bc658890</cbc:ID>
                    <cbc:Description>Confidential</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6afa7569-e4c4-4538-be89-84a82b2a301b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c180d321-b2bc-0aae-22c9-fab05c1e6b52</cbc:ID>
                        <cbc:Description>Recipient name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">54365a34-6615-8f29-d421-7c80152c4975</cbc:ID>
                        <cbc:Description>Contact person name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9b064689-ed95-8db7-f176-f13e503626ba</cbc:ID>
                        <cbc:Description>Contact email</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cda27dd6-f108-4978-6122-50a8ec29c3d6</cbc:ID>
                        <cbc:Description>Contact telephone</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">69f0f61b-f03e-1df5-68f4-21ab7e4dfeb7</cbc:ID>
                        <cbc:Description>Is this information available online?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">233c7119-7050-bf30-482b-b344a89a023f</cbc:ID>
                            <cbc:Description>Evidence Supplied</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
 <!-- Rest of elements removed for brevity -->

1	The description of the Criterion.
2	The Lots to which the CA’s REQUIREMENTs apply to (Lot1, Lot2, Lot4 and Lot5, in this example).
3	The minimum number of references expected by the CA (minimum one, in this example).
4	Additional REQUIREMENT expressed by the CA that apply for the affected Lots: Specific amount greater than a certain amount.
5	Additional REQUIREMENT expressed by the CA that apply for the affected Lots: Executed recently.
6	The Lots for which the Reference makes sense. Notice that the response of the EO is consistent, as the procedure is divided into 7 Lots.
7	The description of the work executed.
8	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".
9	The activity of this economic operator in this work.
10	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.
11	Duration of the execution of the work.
12	The level of confidentiality of the information regarding this Reference. Confidential references provided by the EO cannot be made accessible by the CA to third parties.
13	The name of the recipient of the work.
14	Name of the contact point, a person in this case.
15	Contact e-mail of the recipient of the work.

The fragment of XML code below shows the responses to the QUESTIONs for the Criterion above. For details on how an ESPD-Response document specifies responses and links them to each particular QUESTION see section VIII.7 Answering QUESTIONs

XML Example - Self-contained (REQUIREMENTs and QUESTIONs)

Self-contained 'References for a works contract' criterion

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

<!--
    E.g. The responses coming next are the answers to the Criterion above "References". For complete "dummy" responses to all criteria (exclusion and selection), see
    the rest of examples in the folder dist/xml.
-->

<!--
    Responses to the QUESTIONs in Criterion "References" above.
    NOTICE that the EO has made a mistake and for a "Works contracts: performance of works for the specified type" it is describring a Service.
    The Schematron-based validation solution cannot validate this situation as the description is a textual value.
-->(1) (2) (3) (4) (5)

<!--
    Lots for which the Reference(s) provided by the EO make sense.
    *BEWARE* that this is a 'collection' of values of the same data type that are linked to one QUESTION.
-->

<cac:TenderingCriterionResponse>(6)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3d7d8db3-5e90-49fb-b96d-6fd53b950649</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c6eb0a5a-0d22-4123-8599-1be0e1d38697</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">daa25cac-b8c5-405d-abaa-18d29e2d5c59</cbc:ID>
        <cbc:ResponseID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ResponseID>(6)
    </cac:ResponseValue>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96995244-1cff-4b1c-8a4d-788e2cc604aa</cbc:ID>
        <cbc:ResponseID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ResponseID>(6)
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- The Reference Description -->
<cac:TenderingCriterionResponse>(7)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">afb8c2dd-4dfa-4182-83e1-719cc996b1e5</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">72b19420-a904-4e4b-8465-a922dcec06b6</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3ebe542b-e220-4a08-a488-ddca5eb7d2cd</cbc:ID>
        <cbc:Description>Implementation of the Interoperability Platform of Electronic State Sevices of the State which facilitates the exchange of information between
        different public institutions of the Government. This platform is aimed at allowing -in this first phase- the exchange of information between 5 public
        institutions, seeking the automation of 37 steps throught 30 information services</cbc:Description>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- The Total Amount of the Reference, including the amounts taht were specific to (share of) other EOs participating in the execution of the work. -->
<cac:TenderingCriterionResponse>(8)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c8ebc58-5d0b-454c-8fe9-6c16690400c5</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c2556c58-72aa-42a6-ad45-568ef9ba1988</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9cdcb2e6-f162-4f9f-8260-2cb5a47c8690</cbc:ID>
        <cbc:ResponseAmount currencyID="EUR">2479914.00</cbc:ResponseAmount>(8)
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- The activity of this economic operator in this work. -->
<cac:TenderingCriterionResponse>(9)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bdf6bdb0-e3c7-4d5b-8ee1-726434c983c6</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8886ec57-02d9-461d-932b-25c1bb494c7f</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">07e0e41b-235c-4d95-a9c7-15aa8eaf0215</cbc:ID>
        <cbc:Description>The project involved the design, development and implementation of the Interoperability Platform for Electronic Services of the State. This project
        integrated all Government Institutions, making a much more efficient and centralized information process possible.</cbc:Description>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- 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. -->
<cac:TenderingCriterionResponse>(10)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">31379d51-4b1c-40a1-b0bf-38cc85bf559d</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c78e1d6-1bdf-4129-b86c-89da335c8918</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a5762219-d77f-486c-8a6f-dae1b5efabe5</cbc:ID>
        <cbc:ResponseAmount currencyID="EUR">2479914.00</cbc:ResponseAmount>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Duration of the execution of the work. -->
<cac:TenderingCriterionResponse>(11)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fc669b60-f1b4-452e-9331-1fce9d3809b4</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4cdf40b6-a1dd-461b-81b1-a9669304302f</cbc:ValidatedCriterionPropertyID>
    <cac:ApplicablePeriod>
        <cbc:StartDate>2017-02-01</cbc:StartDate>
        <cbc:EndDate>2017-02-06</cbc:EndDate>
    </cac:ApplicablePeriod>
</cac:TenderingCriterionResponse>
<!-- The level of confidentiality of the information regarding this Reference. Confidential references provided by the EO cannot be made accessible by the CA to third parties. -->
<cac:TenderingCriterionResponse>(12)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">964bdaef-a00c-4c5a-b34b-333fa9cde699</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">90da53d3-2e8f-47be-9b72-1393e6200e16</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">31bdb55b-ebdf-4cab-a5cb-2a5e73c17191</cbc:ID>
        <cbc:ResponseIndicator>true</cbc:ResponseIndicator>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Sequence of data about the recepient of the work follows. -->
<!-- The name of the recipient of the work. -->
<cac:TenderingCriterionResponse>(13)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1137d708-eafe-4077-bfb1-dea6cdb63de5</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bdfb2116-0c4e-4d2c-ae5e-a2b95d767078</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d1bd1d8a-278f-40de-885c-f2cdecf28c80</cbc:ID>
        <cbc:Description>Economics Department, Government of Spain</cbc:Description>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Name of the contact point, a person in this case -->
<cac:TenderingCriterionResponse>(14)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">11ba592f-0c0d-4632-a110-4191a04d9b4f</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">95994e82-e650-4567-beab-ba4672d27008</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4e9008d5-059f-4bc4-a654-099f29db38a3</cbc:ID>
        <cbc:Description>Juan Rodriguez</cbc:Description>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- The email for contacting the recipient of the work executed by the EO.  -->
<cac:TenderingCriterionResponse>(15)
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">482ae348-b3d8-4efa-a827-3aba6aa9e2b6</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6d9355c0-129b-4f70-85f0-36f2ffa6fcb8</cbc:ValidatedCriterionPropertyID>
    <cac:ResponseValue>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f6478bc5-31bc-4724-825c-0bb6446eb76e</cbc:ID>
        <cbc:Description>Juan.rodriguez@mail.com</cbc:Description>
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>

<!-- Evidences would follow next. See other files in the dist/xml folder for complete examples. -->

1	Not part of the responses (see XML example above)
2	Not part of the responses (see XML example above)
3	Not part of the responses (see XML example above)
4	Not part of the responses (see XML example above)
5	Not part of the responses (see XML example above)
6	The Lots for which the Reference makes sense. Notice that the response of the EO is consistent, as the procedure is divided into 7 Lots.
7	The description of the work executed.
8	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".
9	The activity of this economic operator in this work.
10	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.
11	Duration of the execution of the work.
12	The level of confidentiality of the information regarding this Reference. Confidential references provided by the EO cannot be made accessible by the CA to third parties.
13	The name of the recipient of the work.
14	Name of the contact point, a person in this case.
15	Contact e-mail of the recipient of the work.

VI.9 Abilities

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

Table 26. Weighting
REQUIREMENT	In an open procedure the CA has to consider all tenders that pass the selection criteria. The contract is awarded based on award criteria. For two stage procedures it should be possible to weight the "Technical and professional ability" (the rest of selection criteria should be always PASS/FAIL). Weighting can be done either using percentage or points for one procedure. The CA should have a free text where they can describe the scoring methodology.

Differences between Regulated and Self-contained

In the REGULATED the contracting authority cannot specify any REQUIREMENT. It is the economic operator that provides descriptive information (free-text field) about the technicians or bodies.
In the SELF-CONTAINED the contracting authority can provide a specific REQUIREMENT. For this example the CA expects the economic operator to provide information about the group of technicians that will supply support to the users. The CA can add and remove as many requirements as needed.
In the SELF-CONTAINED the economic operator (EO) sees the REQUIREMENT(s) specified by the CA and can provide different groups of information (which are not disjoint).
For procurement procedures organised in two stages the SELF-CONTAINED version allows the weighting of the technical and professional abilities.
The SELF-CONTAINED is able to keep in the XML documents national sub-criteria defined by the MS in e-Certis.
The REGULATED ESPD defines two different data structures:
- One data structure to define up to eight Criteria (sharing the same data structure):
  - Technicians or technical bodies for quality control (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_QUALITY_CONTROL)
  - For works contracts: technicians or technical bodies to carry out the work (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_CARRYING_WORKS)
  - Technical facilities and measures for ensuring quality (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.FACILITIES_FOR_QUALITY_ENSURING)
  - Study and research facilities (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.FACILITIES_FOR_STUDY_RESEARCH)
  - Supply chain management (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.SUPPLY_CHAIN_MANAGEMENT)
  - Educational and professional qualifications (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.PROFESSIONAL_QUALIFICATIONS)
  - Environmental management measures (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.ENVIRONMENTAL_MANAGEMENT_MEASURES)
  - Tools, plant or technical equipment (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.EQUIPMENT)
- One data structure to define the Allowance of Checks:
  - Allowance of checks (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.CHECKS.ALLOWANCE_OF_CHECKS)
- One more data structure to define criteria related to the contractor’s staff:
  - Number of managerial staff (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.MANAGERIAL_STAFF)
  - Average annual manpower (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.AVERAGE_ANNUAL_MANPOWER)
The SELF-CONTAINED ESPD, in turn, supplies a richer set of (five) data structures thus facilitating a greater semantic interoperability:
- One data structure to define two ability criteria related to technicians:
  - Technicians or technical bodies for quality control (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_QUALITY_CONTROL)
  - For works contracts: technicians or technical bodies to carry out the work (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_CARRYING_WORKS)
- One data structure to define a miscellania of five criteria that can share the same data structure:
  - Technical facilities and measures for ensuring quality (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.FACILITIES_FOR_QUALITY_ENSURING)
  - Study and research facilities (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.FACILITIES_FOR_STUDY_RESEARCH)
  - Supply chain management (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.SUPPLY_CHAIN_MANAGEMENT)
  - Environmental management measures (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.ENVIRONMENTAL_MANAGEMENT_MEASURES)
  - Tools, plant or technical equipment (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.EQUIPMENT)
- One data structure to define abilities related to the education and professional qualifications of the contractor or service provider:
  - Educational and professional qualifications (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.PROFESSIONAL_QUALIFICATIONS)
- And one more data structure to define the allowance of checks:
  - Allowance of checks (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.CHECKS.ALLOWANCE_OF_CHECKS)
- One data structure to define two abilities related to the contractor’s staff:
  - Number of managerial staff (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.MANAGERIAL_STAFF)
  - Average annual manpower (CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.AVERAGE_ANNUAL_MANPOWER)

VI.9.1 Regulated Abilities (I) (Technicians, …)

Mock-ups - contracting authority perspective (PASS/FAIL, i.e. 'non-weighted')

Figure 156. Regulated 'Abilities (I)' CA mock-up

Mock-ups - economic operator perspective

Figure 157. Regulated 'Abilities (I)' EO mock-up

Data Structure - Regulated

Figure 158. Regulated 'Abilities (I)' criterion data structure

XML Example - Regulated

Regulated XX

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

<!-- Criterion:Technicians or technical bodies for quality control -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3aaca389-4a7b-406b-a4b9-080845d127e7</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_QUALITY_CONTROL</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5e6827e1-64ca-4375-989a-6a6948d5a0d3</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">488ca189-bcdb-4bf4-80c7-3ad507fd89fb</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b5207ccc-3207-4a51-a2a5-d2d2cb528e06</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Please describe them</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4e20e385-e48f-4e7b-981e-08b0e2fb8c92</cbc:ID>
                        <cbc:Name/>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d43276ac-7e9f-4870-8d04-c8bd9e959e2c</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">67ea2cfc-f8a5-44bd-b333-a73186dcd4fa</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Verification code</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ef2b8cc7-c8a8-4c9f-9b4c-e9961d6ba46a</cbc:ID>
                                <cbc:Name/>
                                <cbc:Description>Issuer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.9.2 Regulated Abilities (II) - Checks

Mock-ups - contracting authority perspective

The contracting authority has selected the 'allowance of checks' option in a ESPD Request builder software application GUI. This criterion will be included in the ESDP Request XML instance.

Figure 159. Regulated 'checks' CA mock-up

Mock-ups - economic operator perspective

The economic operator has only to answer Yes or No in response.

Figure 160. Regulated 'checks' EO mock-up

Data Structure - Regulated

The data structure for this criterion is quite straightforward, it only contains a group of one QUESTION which has to be answered with Yes or No, thus the expected property data type INDICATOR.

(Some columns have been hidden to enhance the readability of the image).

Regulated 'checks' criterion data structure criterion data structure

Figure 161. Regulated 'checks' criterion data structure

XML Example - Regulated

Regulated 'checks' XML example

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

<!-- Criterion:Allowance of checks -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8809aa1-29b6-4f27-ae2f-27e612e394db</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.CHECKS.ALLOWANCE_OF_CHECKS</cbc:CriterionTypeCode>
        <cbc:Name>Allowance of checks</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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3905a69e-4893-4d52-9650-c144d405ecba</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d7721546-9106-43a7-8d31-2fe08a862b00</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6250e2c6-9309-42ea-a969-d2599c0159be</cbc:ID>
                        <cbc:Description>Do you allow checks?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.9.3 Regulated abilities (III) (Staff)

Mock-ups - contracting authority perspective

Figure 162. Regulated 'Abilities (III)' CA mock-up

Mock-ups - economic operator perspective

Figure 163. Regulated 'Abilities (III)' EO mock-up

Data Structure - Regulated

(Some columns have been hidden to enhance the readability of the image).

Figure 164. Regulated 'Abilities (III)' criterion data structure

XML Example - Regulated

Regulated 'number of managerial staff' (Abilities III) criterion

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

<!-- Criterion:Number of managerial staff -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6346959b-e097-4ea1-89cd-d1b4c131ea4d</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.MANAGERIAL_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:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2ba5bf04-b2c3-4e3a-8e4d-c275663ef590</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">931ee8aa-8907-492c-acdb-2600d3360be0</cbc:ID>
                        <cbc:Description>Year</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8e3925ea-45c1-4db7-9c50-6de2196d4b63</cbc:ID>
                        <cbc:Description>Number</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0fb34dc6-78ba-4542-b78d-ff709bc4b905</cbc:ID>
                        <cbc:Description>Year</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0dacd810-70f1-43d6-9367-c3b474515b47</cbc:ID>
                        <cbc:Description>Number</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e30fcf9b-e656-41d3-9de9-0973cc9d0a12</cbc:ID>
                        <cbc:Description>Year</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">66869a93-8224-407c-8cd7-ef51cba5c416</cbc:ID>
                        <cbc:Description>Number</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.9.4 Self-contained Abilities (I) - Persons

Mock-ups - contracting authority perspective (PASS/FAIL, non-weighted)

Self-contained 'Abilities (I)' CA REQUIREMENT mock-up

Figure 165. Self-contained 'Abilities (I)' CA REQUIREMENT edition mock-up

Mock-ups - economic operator perspective (PASS/FAIL, non-weighted)

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 CA is the type of technical assistance the EO’s teams must provide.

Figure 166. Self-contained 'Abilities (I)' EO mock-up

Mock-ups - contracting authority perspective (WEIGHTED)

In two-stages procedures the contracting authority may like to score EOs in the evaluation phase and would like to inform the EO in a transparent way how it will weight them. The mock-up below shows a possible GUI for the CA to set this information and other additional requirements related to the weighting:

Figure 167. Self-contained 'Abilities (I)' WEIGHTED CA REQUIREMENT edition mock-up

Mock-ups - economic operator perspective (WEIGHTED)

Figure 168. Self-contained 'Abilities (I)' WEIGHTED EO mock-up

Data Structure - Self-contained

(The figure below is defined in the the tab ''SC-Abilities_1 (Persons)'' of the ESPD-CriteriaTaxonomy spread-sheet).

In this data structure the first REQUIREMENT set by the contracting authority is whether the criterion is to be WEIGHTED or not (the opposito to WEIGHTED is PASS/FAIL, see the Code List EvaluationMethodType).

Either if it is weighted or not one important aspect here is that the sub-groups of QUESTION(s), the one for the technicians and the one for the technical bodies, can be repeated several times, one time per each technician or body the economic operator decides to add (thus the cardinalities 0..n for both sub-groups).

Figure 169. Self-contained 'Abilities (I)(Persons)' criterion data structure

XML Example - Self-contained (WEIGHTED)

The XML example below shows the REQUIREMENT(s) and QUESTION(s). See the section "VIII.3. XML Example 3: Weighting" for this same example followed by the responses.

Notice that the data is distributed in three places:

Some root elements (directly under the root element of the /QualificationApplicationResponse. Observe that in the case of elements cbc:Description UBL-2.2 does always specify a multiple cardinality. This allows for separating the lines of the text thus facilitating its presentation for layout purposes.
The criterion itself; see circled numbers and comments beneath the XML code;
The data structure (see the SELF-CONTAINED spread-sheet tab SC-Abilities_1).

Criterion "Technicians or technical bodies for quality control" (SELF-CONTAINED and WEIHGTED)

<!-- root elements that are global for all weighted criteria -->
<cbc:WeightScoringMethodologyDescription>For weighted criteria, evaluators will allocate a score between 0 and 100 to each question reponse in accordance with the scoring guidance below:</cbc:WeightScoringMethodologyDescription>(3)
<cbc:WeightScoringMethodologyDescription>0 Unnaceptable</cbc:WeightScoringMethodologyDescription>
<cbc:WeightScoringMethodologyDescription>25 Poor</cbc:WeightScoringMethodologyDescription>
<cbc:WeightScoringMethodologyDescription>50 Acceptable</cbc:WeightScoringMethodologyDescription>
<cbc:WeightScoringMethodologyDescription>50 Acceptable</cbc:WeightScoringMethodologyDescription>
<cbc:WeightScoringMethodologyDescription>100 Excellent</cbc:WeightScoringMethodologyDescription>
<cbc:WeightScoringMethodologyDescription>Suppliers must pass all of the pass/fail (Yes/No) questions and score a minimum of 75 overall in this section to proceed to the next stage. This will allows us to get a short list of suppliers to take through to the next stage. The final score for a criterion (or "Weighted Question Score") results from the product of the Score obtained and the weight allocated by the Contracting Authority to the criterion.</cbc:WeightScoringMethodologyDescription>
<cbc:WeightingType listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERCENTAGE</cbc:WeightingType>(2)

<!-- Criterion:Technicians or technical bodies for quality control -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3aaca389-4a7b-406b-a4b9-080845d127e7</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_QUALITY_CONTROL</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>
        <cbc:WeightNumeric>0.1</cbc:WeightNumeric>(5)
        <cbc:EvaluationMethodTypeCode listID="EvaluationMethodType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHTED</cbc:EvaluationMethodTypeCode>(4)
                <cbc:WeightingConsiderationDescription>0 technicians -> 0 points</cbc:WeightingConsiderationDescription>(6)
                <cbc:WeightingConsiderationDescription>1 technician -> 30 points</cbc:WeightingConsiderationDescription>(6)
                <cbc:WeightingConsiderationDescription>2 technicians -> 60 points</cbc:WeightingConsiderationDescription>(6)
                <cbc:WeightingConsiderationDescription>3 technicians -> 75 points</cbc:WeightingConsiderationDescription>(6)
                <cbc:WeightingConsiderationDescription>4 technicians -> 100 points</cbc:WeightingConsiderationDescription>(6)
                <cbc:WeightingConsiderationDescription>Minimum acceptable: 2 technicians</cbc:WeightingConsiderationDescription>(6)
        <cac:SubTenderingCriterion>
                <!-- ... elements removed for brevity ... -->
        </cac:SubTenderingCriterion>
        <cac:Legislation><!-- ... elements removed for brevity ... --></cac:Legislation>
                        <cac:TenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9cf2aa13-19ac-4767-a06b-da3b6c8c9c27</cbc:ID>
                                <cbc:Description>Is this criterion weighted?</cbc:Description>(1)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</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 -->
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bbe06b1d-bb21-4588-a489-4bce6a51364f</cbc:ID>
                                        <cbc:Description>Requirement</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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>Technical User Support Group</cbc:ExpectedDescription>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">609cc954-64be-4b4f-800a-f17589deb936</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96cc5c65-2395-4750-b9c7-b60dc58fcf24</cbc:ID>
                                                <cbc:Description/>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b986d088-ec14-4eca-ac99-a7119aae4f43</cbc:ID>
                                                        <cbc:Description>Technician</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a2662683-efc5-4e81-be28-57dfa78b4834</cbc:ID>
                                                        <cbc:Description>First name</cbc:Description>(7)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bc0d0694-d47f-4b1c-9770-843fe177360c</cbc:ID>
                                                        <cbc:Description>Last name</cbc:Description>(8)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9a7344fa-fc73-4e73-a440-531e90b61231</cbc:ID>
                                                        <cbc:Description>Profession</cbc:Description>(9)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">845f376f-fedb-4710-a1b8-5514c5439c1b</cbc:ID>
                                                        <cbc:Description>Experience</cbc:Description>(10)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7e9f0030-3fe9-4407-888f-f7cfe39f9df2</cbc:ID>
                                                        <cbc:Description>Other information</cbc:Description>(11)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b848f9ea-281b-4895-96c1-705d678bf125</cbc:ID>
                                                        <cbc:Description>How long with EO</cbc:Description>(12)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                                        <cac:TenderingCriterionProperty>
                                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">94b53be3-b838-4538-8b43-b6b1f05fc158</cbc:ID>
                                                                <cbc:Description>Is this information available online?</cbc:Description>(13)
                                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                                        </cac:TenderingCriterionProperty>
                                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                                <cac:TenderingCriterionProperty>
                                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">91ee7ffe-07b5-4e87-87e5-9b1063e9d487</cbc:ID>
                                                                        <cbc:Description>Evidence supplied</cbc:Description>
                                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                                </cac:TenderingCriterionProperty>
                                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">45a67f48-d146-4faf-8239-dd6977dffe29</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">99fe0af5-0a47-4930-b1e8-8acbc614964b</cbc:ID>
                                                <cbc:Description/>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">aab9aa41-87a0-4f71-89d4-3dfdb94fc025</cbc:ID>
                                                        <cbc:Description>Technical body</cbc:Description>
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b8b76588-cc5c-4d6f-acf9-0447ab1047f4</cbc:ID>
                                                        <cbc:Description>Name</cbc:Description>(14)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3044bc5a-eb95-4639-a0b5-4c1d79da9873</cbc:ID>
                                                        <cbc:Description>Experience area</cbc:Description>(15)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <cac:TenderingCriterionProperty>
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">165d6fad-8915-4b20-8c75-1a661a27e2f4</cbc:ID>
                                                        <cbc:Description>Other information</cbc:Description>(16)
                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                                </cac:TenderingCriterionProperty>
                                                <!-- Evidence associated to the criterion -->
                                                <cac:SubsidiaryTenderingCriterionPropertyGroup> (17)
                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                                                        <cac:TenderingCriterionProperty>
                                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b9b7e484-829f-47b9-8d83-545ed3ff43cf</cbc:ID>
                                                                <cbc:Description>Is this information available online?</cbc:Description>
                                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                                        </cac:TenderingCriterionProperty>
                                                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                                                <cac:TenderingCriterionProperty>
                                                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5549921f-8000-45e9-8fbc-3c7bab4ba6d4</cbc:ID>
                                                                        <cbc:Description>Evidence supplied</cbc:Description>
                                                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                                                </cac:TenderingCriterionProperty>
                                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

1	The contracting authority (CA) selects that some criteria shall will be weighted.
2	The CA decides that the weights will be expressed as percentages.
3	The CA describes the general method used to score and evaluated the weighted criteria. As this, and the previous (#2 and #3) are global these data go in two XML document root elements.
4	This criterion is weighted (default is set to PASS/FAIL).
5	The weight assigned to this criterion by the CA is 10%.
6	The CA provides additional information related to the evaluation of this specific criterion. The expected data value is 'DESCRIPTION' → `cbc:Description`. As in UBL-2.2 descriptions are always multiple cardinality elements this is used to distribute the information in multiple description lines.
7	First Name of the technician (data about one technician starts here (circled numbers #7 to #13). Multiple technicians can be added/removed by the economic operator).
8	Family name of the technician.
9	Profession of the technician.
10	Experience of the technician.
11	Additional information about the technician.
12	Months the technician has worked for the economic operator.
13	Available online evidence related to this technician, his experience, etc.
14	Name of a technical body (data about technical bodies starts here, circled numbers #14 to #17). Multiple bodies can be added/removed by the economic operator.
15	Area of experience of the technical body.
16	Additional information related to the technical body.
17	Available online evidence related to this technical body.

VI.9.5 Self-contained Abilities (II) - Facilities

Data Structure - Self-contained

(The figure below is defined in the the tab ''SC_Abilities_2 (Facilities,…)'' of the ESPD-CriteriaTaxonomy spread-sheet).

Figure 170. Self-contained 'Abilities (II) (Facilities, ….)' criterion data structure

XML Example - Self-contained

Criterion "Technical facilities and measures for ensuring quality" (Self-contained 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''.
-->
<!-- The rest of criteria above and below this criterion have been removed for brevity. -->

<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4bf996d9-439c-40c6-9ab9-980a48cb55a1</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.FACILITIES_FOR_QUALITY_ENSURING</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>
    <!-- This criterion will be used in a second or subsequent evaluation stage. Its relative weight, assigned by the CA, is in this case 5%. -->
    <cbc:WeightNumeric>0.05</cbc:WeightNumeric>(1)
    <!-- The fact that the criterion is weighted is announced here. -->
    <cbc:EvaluationMethodTypeCode listID="EvaluationMethodType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHTED</cbc:EvaluationMethodTypeCode>(2)
    <!-- Additional information to help EOs improve their offer, and used also for transparency. See also chapter "Putting things together" and the XML
        example in that chapter for details on this. -->
    <cbc:WeightingConsiderationDescription>Facilities and quality measures aligned to standards will score better, especially if those standards are European.</cbc:WeightingConsiderationDescription>(3)
    <cac:Legislation><!-- data elements removed for brevity --></cac:Legislation>
    <!-- The main group of REQUIREMENTs and QUESTIONs start here. -->
    <cac:TenderingCriterionPropertyGroup>(4)
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
        <!-- The following property announces that the criterion will be weigthed. It principle it had a two-fold goal: 1) to make know the EO
            about the fact that it will be used in a second (or subsequent) stage of the evaluation for its ranking; and 2) for the evaluator (or
            system proposing automated evaluation results, to use it during the evaluation phase. However it is, in fact, superfluous or redundant,
            as this information is also indicated in the `cbc:EvaluationMethodTypeCode` (type WEIGHTED) and of the relative weight value assigned to
            the element `cbc:WeightNumeric`(5% in this example). -->
        <cac:TenderingCriterionProperty>(5)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e5ca83df-73d3-4774-8621-81a7914d228c</cbc:ID>
            <cbc:Description>This criterion will be weighted</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHT_INDICATOR</cbc:ValueDataTypeCode>
        </cac:TenderingCriterionProperty>
        <!-- Notice that multiple subgroups of REQUIREMENT + QUESTION can be used to specify multiple requirements -->
        <!-- This is the 1st. Subgroup of REQUIREMENT and QUESTION: Subgroup specifically used for facilities -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(6)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- Requirement specifically aimed to ask for details about the facility security measures. -->
            <cac:TenderingCriterionProperty>(7)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a8b8f85e-63f3-4364-a7fa-8e8e3004d3e3</cbc:ID>
                <cbc:Description>Requirement</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                <cbc:ExpectedDescription>Describe with as much detail as possible the facilities where the EO is developed, and namely these ones:
                    1) square meters of each storey; 2) quantity of exit gates per storey; 3) number of fire extinguishers per storey; 4) diagram with
                    the location of the exit doors and of the fire-extinguishers.</cbc:ExpectedDescription>
            </cac:TenderingCriterionProperty>
            <!-- The following subgroup contains the QUESTION that will be used in the Response as a reference for the Response
                of the EO to theREQUIREMENT in the previous subgroup. -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>(8)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">488ca189-bcdb-4bf4-80c7-3ad507fd89fb</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <!-- The UUID of this QUESTION will be used in the Response providing the text that will be used by the evaluators. -->
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4b0ddbd4-6c8e-42f1-9b39-d372d3ad878c</cbc:ID>(9)
                    <cbc:Description>Please describe them</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <!-- The EO can use this subgroup of evidences to, in the response to it (in the ESPD-Response), make the information required available online. The URL should be in the domain of the EO -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>(10)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ef6e3621-1098-4b68-b793-787963afe844</cbc:ID>
                    <cbc:Description>Is this information available electronically?</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0d25f520-02dc-4252-a565-86e4f0879fe5</cbc:ID>
                        <cbc:Description>Evidence supplied</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Notice that multiple subgroups of REQUIREMENT + QUESTION can be used to specify multiple requirements -->
        <!-- This is the 2nd. Subgroup of REQUIREMENT and QUESTION: Subgroup specifically used for quality measures -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(11)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3a901515-2bf3-435a-922d-8b42acbc61d8</cbc:ID>
                <cbc:Description>Requirement</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                <cbc:ExpectedDescription>Describe in detail how much your facilities are aligned with the ISO 9000. Where not aligned justify profusely.
                    If your explanations are lengthy, make them available online and specify the URL from where to access them freely or make them
                    available as additional document references or as part of the tender.</cbc:ExpectedDescription>
            </cac:TenderingCriterionProperty>
            <!-- The following subgroup contains the QUESTION that will be used in the Response as a reference for the Response
                of the EO to theREQUIREMENT in the previous subgroup. -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">488ca189-bcdb-4bf4-80c7-3ad507fd89fb</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <!-- The UUID of this QUESTION will be used in the Response providing the text that will be used by the evaluators. -->
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c7169ea8-cce8-4d1a-83de-a862ba9d4121</cbc:ID>
                    <cbc:Description>Please describe them</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
            <!-- The EO can use this subgroup of evidences to, in the response to it (in the ESPD-Response),
                make the information required available online. The URL should be in the domain of the EO. -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4d79fcb6-7b36-4208-984b-5c511d1257fa</cbc:ID>
                    <cbc:Description>Is this information available electronically?</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e9b9ff43-4397-46a2-a19c-37e109da5407</cbc:ID>
                        <cbc:Description>Evidence supplied</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

1	The fact that the criterion is weighted implies that the procedure will go throught at least of stages of the evaluation, the first one is used to exclude and select EOs, the second or other subsequent evaluation stages will be used to short-list and rank the best tenders based on the relative weights of the selected criteria that are weighted. See section "IX Putting all pieces together/IX.2 All about weights" for more details. In this example, the relative weight assigned by the CA to this criterion is 5%.
2	The fact that the criterion is weighted is also announce wiht the code WEIGHTED, in the element `cac:EvaluationMethodTypeCode`. This can be used by automated techniques (e.g. DPS, eAuction, other) to apply automated evaluation processes.
3	Additional information used for clarifications and transparency purposes.
4	Main group of REQUIREMENTs and QUESTIONs.
5	The following property announces that the criterion will be weigthed. It principle it had a two-fold goal: 1) to make know the EO about the fact that it will be used in a second (or subsequent) stage of the evaluation for its ranking; and 2) for the evaluator (or system proposing automated evaluation results, to use it during the evaluation phase. However it is, in fact, superfluous or redundant, as this information is also indicated in the `cbc:EvaluationMethodTypeCode` (type WEIGHTED) and of the relative weight value assigned to the element `cbc:WeightNumeric`(5% in this example).
6	Notice that multiple subgroups of REQUIREMENT + QUESTION can be used to specify multiple requirements. The 1st. Subgroup of REQUIREMENT and QUESTION: Subgroup specifically used for facilities starts here.
7	Requirement specifically aimed to ask for details about the facility security measures. The second subgroup of REQUIREMENT + QUESTION will ask about other aspects: the degree of alignement to an ISO.
8	Sub-subgroup containing the QUESTION that will be used in the Response as a reference for the Response of the EO to theREQUIREMENT in the previous subgroup.
9	This UUID will be used in the Response providing the text that will be used by the evaluators. Beware that the UUID is not illustrated in the spread-sheet data structure because it is generated automatically.
10	Subgroup for evidences. The EO can use it to, in the response to it (in the ESPD-Response), make the information required available online. The URL should be in the domain of the EO.
11	The 2nd. Subgroup of REQUIREMENT + QUESTION starts here, in this case to ask about for other specificic quality measures (e.g. alignment to the ISO 9000).

VI.9.6 Self-contained Abilities (III) - Education

Data Structure - Self-contained (Education)

(The figure below is defined in the the tab ''SC_Abilities_3 (Education)'' of the ESPD-CriteriaTaxonomy spread-sheet).

Figure 171. Self-contained '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 - Self-contained (Education)

Criterion "Educational and professional qualifications" (Self-contained 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. -->
<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">07301031-2270-41af-8e7e-66fe0c777107</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.PROFESSIONAL_QUALIFICATIONS</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>
    <!-- This criterion will be used in a second or subsequent evaluation stage. Its relative weight, assigned by the CA, is in this case 5%. -->
    <cbc:WeightNumeric>0.05</cbc:WeightNumeric>(1)
    <!-- The fact that the criterion is weighted is announced here. -->
    <cbc:EvaluationMethodTypeCode listID="EvaluationMethodType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHTED</cbc:EvaluationMethodTypeCode>(2)
    <!-- Additional information to help EOs improve their offer, and used also for transparency. See also chapter "Putting things together" and the XML
        example in that chapter for details on this. -->
    <cbc:WeightingConsiderationDescription>At least three qualifications are expected be provided, but the weight will not change if more than three qualifications are provided.</cbc:WeightingConsiderationDescription>(4)
    <cac:Legislation><!-- data elements removed for brevity --></cac:Legislation>
    <!-- The main group of REQUIREMENTs and QUESTIONs start here. -->
    <cac:TenderingCriterionPropertyGroup>(5)
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d2cadc29-07e0-46b2-a74a-a0dc4bd2e5c2</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
        <!-- The following property announces that the criterion will be weigthed. It principle it had a two-fold goal: 1) to make know the EO
            about the fact that it will be used in a second (or subsequent) stage of the evaluation for its ranking; and 2) for the evaluator (or
            system proposing automated evaluation results, to use it during the evaluation phase. However it is, in fact, superfluous or redundant,
            as this information is also indicated in the `cbc:EvaluationMethodTypeCode` (type WEIGHTED) and of the relative weight value assigned to
            the element `cbc:WeightNumeric`(5% in this example). Future versions of the ESPD-EDM may deprecate this REQUIREMENT. -->
        <cac:TenderingCriterionProperty>(6)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2fe1c4be-ed09-4241-a531-366e73b33436</cbc:ID>
            <cbc:Description>This criterion will be weighted</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHT_INDICATOR</cbc:ValueDataTypeCode>
        </cac:TenderingCriterionProperty>
        <!-- This subgroup may occur multiple times. In this example it is instantiated once. -->
        <!-- Subgroup specifically used to require that the qualifications must not be older than 3 years. -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(7)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1be6421a-0360-449e-ae7c-ce7fad73c2c2</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- The CA's REQUIREMENT: qualifications not older than 3 years. If no REQUIREMENT was necessary it could be replace with a CAPTION. Its
                 occurrence here is compulsory because of the cardinality imposed by the UBL-2.2 XSD Schema. -->
            <cac:TenderingCriterionProperty>(8)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">25c19a70-e4d1-42cf-aa33-20aad4faacbc</cbc:ID>
                <cbc:Description>Requirement</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                <cbc:ExpectedDescription>The qualifications provided by the economic operator must the most recent possible, in any case not older than three years.</cbc:ExpectedDescription>
            </cac:TenderingCriterionProperty>
            <!-- The next is a "dummy" property, a CAPTION used to overcome the compulsory cardinality of the UBL-2.2 XSD Schema. -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>(9)
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5df40500-a9b7-4c15-8325-a9762224a3c9</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a65e32e3-410c-4017-b7c8-d3bd395f732b</cbc:ID>
                    <cbc:Description> </cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <!-- The group of QUESTIONs addressed to the CA start here. -->
                <cac:SubsidiaryTenderingCriterionPropertyGroup>(10)
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5476ec64-de1e-45d2-aaf1-a40a463ab7a9</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <!-- QUESTION 1. -->
                    <cac:TenderingCriterionProperty>(11)
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e8dbdda7-f4d3-4a79-800c-3cbe89a7785e</cbc:ID>
                        <cbc:Description>First name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 2. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7671b0c6-9441-4294-a10f-e122533014e8</cbc:ID>
                        <cbc:Description>Last name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 3. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fd1cc8a2-7b71-490e-b97f-8efa2feffbf8</cbc:ID>
                        <cbc:Description>Please describe the educational or professional qualification</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 4. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">244adb88-1a49-4907-90ff-19f8aed4d5db</cbc:ID>
                        <cbc:Description>If possible please indicate the ESCO identifier for this qualification</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">URL</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 5. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b7fbe574-67b2-4f6e-afe1-8431f826b1b2</cbc:ID>
                        <cbc:Description>If possible please describe the ESCO qualification</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 6. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f006fd88-54c1-43d5-88d1-8dd144b1b7af</cbc:ID>
                        <cbc:Description>Qualification name</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 7. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e2fe06d0-9612-4aff-9a60-93083703db49</cbc:ID>
                        <cbc:Description>Qualification number</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">IDENTIFIER</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 8. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bfaacca0-ac68-4964-a071-2e8519e32697</cbc:ID>
                        <cbc:Description>Qualification issuing date</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DATE</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <!-- QUESTION 9. -->
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">056e7d4e-715e-40bc-ad9a-ea0ddc089e75</cbc:ID>
                        <cbc:Description>Qualification issuing body</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">48e9b90f-8158-4141-805a-941ad5d9b8a2</cbc:ID>
                            <cbc:Description>Is this information available online?</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <!-- Possible evidences related to this criterion -->
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                            <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">36bb4865-b0f4-421a-8e45-c34976698203</cbc:ID>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                            </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>

        <!-- 2nd. 3rd. etc. subgroups of REQUIREMENTs and QUESTIONs can be added here to ask for more qualifications subject to different specific REQUIREMENTs. -->

    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

VI.9.7 Self-contained Abilities (IV) - Checks

Mock-ups - contracting authority perspective

The contracting authority has selected the 'allowance of checks' 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 contracting authority (CA) can specify none, one or several REQUIREMENT(s). In this case a REQUIREMENT is a descriptive text provided by the CA where the criterion is better explained or where certain conditions relating to the criterion. In this example the CA is specifying which type of premises it wants to check and for which reasons.

Self-contained 'Checks' CA REQUIREMENT mock-up

Figure 172. Self-contained 'allowance of checks' CA 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.

Figure 173. Self-contained 'allowance of checks' EO mock-up

Data Structure - Self-contained

The data structure below shows how this criterion is organised. Notice the following:

The Member State can associate one or more national criteria to this EU criterion (element sub-criterion, cardinality 0..n).
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).
At least one REQUIREMENT group will always be created. If the CA specified more than one REQUIREMENT(s), more groups of REQUIREMENT + QUESTION would be added to the ESPD Request XML instance.
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-CriteriaTaxonomy spread-sheet).

Figure 174. Self-contained 'Abilities (IV) (Checks)' criterion data structure

XML Example - Self-contained

Self-contained allowance of checks criterion

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

<!-- Criterion:Allowance of checks -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c8809aa1-29b6-4f27-ae2f-27e612e394db</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.CHECKS.ALLOWANCE_OF_CHECKS</cbc:CriterionTypeCode>
        <cbc:Name>Allowance of checks</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:SubTenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8c39b505-8abe-44fa-a3e0-f2d78b9d8224</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9f7e914c-6abc-495e-9f97-3770635237f7</cbc:ID>
                                <cbc:Description>[Additional information; e.g. no evidences online]</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ef9f4d52-17ea-4dca-8863-a74b7ded2fc3</cbc:ID>
                                <cbc:Description>Your Answer</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:TenderingCriterionPropertyGroup>
        </cac:SubTenderingCriterion>
        <cac:Legislation> <!-- Elements removed for brevity. -->
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">10822ddd-9ba6-42d5-9339-de0845aeafc9</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>(1)
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">570c19ca-80f2-4477-a4c2-7d9b6781c31c</cbc:ID>
                        <cbc:Description>Requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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>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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a3410620-8ed3-47f9-ab90-b5b1aeeff6a5</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f20fee9c-f374-4dc7-b88f-8428cec5a4b3</cbc:ID>
                                <cbc:Description>Do you allow checks?</cbc:Description>(2)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <!-- Evidences block would follow. Removed for brevity. See it in other examples. -->
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.9.8 Self-contained Abilities (V) - Staff

Data Structure - Self-contained (Staff)

(The figure below is defined in the the tab ''SC_Abilities_5 (Staff)'' of the ESPD-CriteriaTaxonomy spread-sheet).

Figure 175. Self-contained 'Abilities (V) (Staff)' criterion data structure

XML Example - Self-contained

Criterion SC-Abilities (Staff) Self-contained 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. -->

<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6346959b-e097-4ea1-89cd-d1b4c131ea4d</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.MANAGERIAL_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:Legislation><!-- Data elements removed for brevity. --></cac:Legislation>
    <!-- This criterion will not be weigthed. -->
    <!-- The main group of REQUIREMENTs and QUESTIONs starts here. -->
    <cac:TenderingCriterionPropertyGroup>(1) (2)
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7f7949a8-dbe6-496c-a9f6-6f05b8648bad</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
        <!-- Two REQUIREMENTs are issued, minimum number of years and additional information. Beware that in the ESP all the thresholds imposed
            with a REQUIREMENT are at present *minimum* quantities. -->
        <!--
            REQUIREMENT #1: Minimum number of times (3) for which the economic must provide the number
            of managerial staff, three times in this example. -->
        <cac:TenderingCriterionProperty>(3) (4)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2416716f-1d55-4a5a-8580-f8b5a33ca2c9</cbc:ID>
            <cbc:Description>Minum number of years</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
            <!-- The number provided by the contracting authority. -->
            <cbc:ExpectedValueNumeric>3</cbc:ExpectedValueNumeric>
        </cac:TenderingCriterionProperty>
        <!-- Additional information in a narrative way. -->
        <cac:TenderingCriterionProperty>(5)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">da6558a0-0878-4662-99fd-a7040b139e02</cbc:ID>
            <cbc:Description>Additional information</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
            <cbc:ExpectedDescription>Provide a sufficient description of the managerial team.</cbc:ExpectedDescription>
        </cac:TenderingCriterionProperty>
        <!-- Subgroup 1/3 (for year 1 out of 3). -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(6)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- QUESTION asking the first year. -->
            <cac:TenderingCriterionProperty>(7)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bd677a81-a394-44de-b7d2-8bf3be5991d8</cbc:ID>
                <cbc:Description>Year</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <!-- QUESTION asking the number of the staff for the first year, e.g. the EO would respond with a value like: 12 (meaning a team of twelve people). -->
            <cac:TenderingCriterionProperty>(8)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">102375b8-881f-4bac-85d7-15f78e7a7895</cbc:ID>
                <cbc:Description>Number</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Placeholder for evidences related to the first year. -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(9)
            <!-- Data elements removed for brevity. -->
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Subgroup 2/3 (for year 2 out of 3) -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(10)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- QUESTION asking the second year -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0dcb85d0-9c7a-4dc3-b966-48dd8d00a4e4</cbc:ID>
                <cbc:Description>Year</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <!-- QUESTION asking the number of the staff for the second year. -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3995be99-c599-4049-a8e4-78d96a787fb1</cbc:ID>
                <cbc:Description>Number</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Placeholder for evidences related to the second year. -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <!-- Data elements removed for brevity. -->
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Subgroup 3/3 (for year 3 out of 3) -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(11)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">96defecc-7d32-4957-82e9-aad5f3c5b736</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <!-- QUESTION asking the third year -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">783bb2c3-b354-45e4-a75e-0547393ce05a</cbc:ID>
                <cbc:Description>Year</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_YEAR</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <!-- QUESTION asking the number of the staff for the third year. -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d9cd4ee1-c0f1-441a-8057-07ecba179266</cbc:ID>
                <cbc:Description>Number</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <!-- Placeholder for evidences related to the third year. -->
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <!-- Data elements removed for brevity. -->
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

<!-- Rest of elements until the end of the Request documentn removed for brevity. -->

1	Notice that this criterion does not specify any weight. The default evaluation method is PASS_FAIL. Most probably this is an Open Procurement Procedure.
2	The main group of REQUIREMENTs and QUESTIONs starts here.
3	Two REQUIREMENTs are issued, minimum number of years and additional information. Beware that in the ESP all the thresholds imposed with a REQUIREMENT are at present minimum quantities.
4	REQUIREMENT #1: Minimum number of times (3) for which the economic must provide the number of managerial staff, three times in this example.
5	Additional information in a narrative way.
6	Subgroup 1/3 (for year 1 out of 3).
7	QUESTION asking the first year, e.g. the EO, in its response would provide an integer value like: 2016.
8	QUESTION asking the number of the staff for the first year, e.g. the EO would respond with a value like: 12 (meaning a team of twelve people).
9	Subgroup for evidences related to this first REQUIREMENT. The data elements inhere have been removed for the sake of brevity. See XML examples in dist/xml for the complete Criterion.
10	Subgroup 2 or REQUIREMENTs and QUESTIONs.
11	Subgroup 3 or REQUIREMENTs and QUESTIONs.

VI.10 Subcontracting proportion

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

Differences between Regulated and Self-contained

For this criterion, the only difference between the REGULATED and SELF-CONTAINED versions lies in the fact that the SELF-CONTAINED XML instance is able to keep national sub-criteria defined by the Member State in e-Certis.
For both versions, REGULATED and SELF-CONTAINED, there is only one criterion with a simple data structure, classified as:
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.SUBCONTRACTING_PROPORTION

Mock-ups - contracting authority perspective (REGULATED and SELF-CONTAINED)

The contracting authority selects the criterion to be included in the ESPD Request:

Figure 176. 'Subcontracting proportion' CA mock-up (REGULATED and SELF-CONTAINED)

Mock-ups - economic operator perspective (REGULATED and SELF-CONTAINED)

The economic operator has to provide a descriptive response in a free-text field:

Figure 177. 'Subcontracting proportion' EO mock-up (REGULATED and SELF-CONTAINED)

Data Structure - Regulated

The data structure is very simple, it only defines a group with one QUESTION:

(Some columns have been hidden to enhance the readability of the image).

Regulated 'Subcontracting proportion' criterion data structure

Figure 178. 'Subcontracting proportion' criterion data structure (REGULATED)

Data Structure - Self-contained

The difference with the Regulated version is that the Self-contained is able to define and keep in the XML instance the national sub-criteria. But, as sub-criteria are optional, if the MS did not defined any national sub-criterion then the data structure would enn up being the same than for both cases.

(Some columns have been hidden to enhance the readability of the image).

Self-contained 'Subcontracting proportion' criterion data structure

Figure 179. 'Subcontracting proportion' criterion data structure (SELF-CONTAINED)

XML Example - (REGULATED and SELF-CONTAINED)

As in this case the MS (Finland, in this example), did not defined any national criterion associated to the EU criterion, the resulting XML instance is identical for both versions of the ESPD Request (Regulated and Self-contained).

'Subcontracting proportion' criterion

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

<!-- Criterion:Subcontracting proportion -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">612a1625-118d-4ea4-a6db-413184e7c0a8</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.SUBCONTRACTING_PROPORTION</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:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">575f7550-8a2d-4bad-b9d8-be07ab570076</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">48d527b0-ba49-4fbc-bfd3-3db487c47baf</cbc:ID>
                        <cbc:Description>Please specify</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VI.11 Samples and certificates

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

Differences between Regulated and Self-contained

For this criteria, the only difference between the REGULATED and SELF-CONTAINED versions lies in the fact that the SELF-CONTAINED XML instance is able to keep national sub-criteria defined by the Member State in e-Certis.
For both versions, REGULATED and SELF-CONTAINED, there are two criteria that share the same data structure, classified as:
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.ARTEFACTS.NO_AUTHENTICATED_ARTEFACTS
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.ARTEFACTS.AUTHENTICATED_ARTEFACTS

Mock-ups - contracting authority perspective (REGULATED and SELF-CONTAINED)

The contracting authority selects the criteria that have to be included in the ESPD Request, e.g.:

Figure 180. 'Samples and certificates' CA mock-up (REGULATED and SELF-CONTAINED)

Mock-ups - economic operator perspective (REGULATED and SELF-CONTAINED)

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

Figure 181. 'Samples and certificates' EO mock-up (REGULATED and SELF-CONTAINED)

Data Structure - Regulated

(Some columns have been hidden to enhance the readability of the image).

Regulated 'Samples and certificates' criteria data structure

Figure 182. 'Samples and certificates' criteria data structure (REGULATED)

Data Structure - Self-contained

The with the Regulated version is that the Self-contained is able to define and keep in the XML instance the national sub-criteria. But, as sub-criteria are optional, if the MS did not defined any national sub-criterion then the data structure would actually end up being the same for both cases.

(Some columns have been hidden to enhance the readability of the image).

Self-contained 'Samples and certificates' criterion data structure

Figure 183. 'Samples and certificates' criteria data structure (SELF-CONTAINED)

XML Example - (REGULATED and SELF-CONTAINED)

As in this case the MS did not defined any national criterion associated to the EU criterion, the resulting XML instance is identical for both versions of the ESPD Request (Regulated and Self-contained).

'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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">bdf0601d-2480-4250-b870-658d0ee95be6</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.MANAGEMENT.ARTEFACTS.NO_AUTHENTICATED_ARTEFACTS</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:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cb73544d-e8bb-4cc6-819b-b8e04f1e240e</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d86645aa-a97f-43c2-a9fd-3dc0278c1027</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d6c6dd34-91a8-4b3f-a2a1-5d27c3adff58</cbc:ID>
                        <cbc:Description>Is this information available electronically?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cfd7bf8d-0919-43d6-90b0-c8fafcbda85e</cbc:ID>
                                <cbc:Description>Evidence supplied</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- rest of elements removed for brevity -->

VI.12 Quality assurance

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

Differences between Regulated and Self-contained

In the REGULATED version the contracting authority (CA) cannot specify REQUIREMENT(s).
For both versions, REGULATED and SELF-CONTAINED, the economic operator is expected to answer Yes or No.
- If the EO answers Yes the EO will be asked whether there are evidences available online.
- In the case the EO answers NO it will have to provide additional explanations.
In the SELF-CONTAINED version the contracting authority can provide as many REQUIREMENT(s) as needed in a textual field, normally the type of standard it expects the EO conforms to, e.g. 'ISO 9001', 'EMAS', etc. (but it could issue any other type of REQUIREMENT as a text).
The SELF-CONTAINED is able to keep in the XML documents national sub-criteria defined by the MS in e-Certis.
For both versions, REGULATED and SELF-CONTAINED, there are three criteria that share the same data structure, classified as:
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.CERTIFICATES.QUALITY_ASSURANCE.QA_INSTITUTES_CERTIFICATE
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.CERTIFICATES.QUALITY_ASSURANCE.QA_INDEPENDENT_CERTIFICATE
- CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.CERTIFICATES.ENVIRONMENTAL_MANAGEMENT.ENV_INDEPENDENT_CERTIFICATE

VI.12.1 Regulated Quality Assurance schemes and environmental management standards

Mock-ups - contracting authority perspective

Figure 184. Regulated 'Quality Assurance schemes and environmental management standards' CA mock-up

Mock-ups - economic operator perspective

Notice that in the case where the economic operator 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).

Figure 185. Regulated 'Quality Assurance schemes and environmental management standards' EO mock-up

Data Structure - Regulated

Notice the ONFALSE code for the sub-group containing the sentence thats starts with 'If not, please explain why…'. The code means: if the answer to the previous question was No then this sub-group must be shown/processed.

(Some columns have been hidden to enhance the readability of the image).

Figure 186. Regulated 'Quality Assurance schemes and environmental management standards' criteria data structure

XML Example - Regulated

Regulated 'certificates by independent bodies about quality assurance standards' criterion

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

<!-- Criterion:Certificates by independent bodies about quality assurance standards -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d726bac9-e153-4e75-bfca-c5385587766d</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.CERTIFICATES.QUALITY_ASSURANCE.QA_INDEPENDENT_CERTIFICATE</cbc:CriterionTypeCode>
        <cbc:Name>Certificates by independent bodies about quality assurance standards</cbc:Name>
        <cbc:Description>Will the economic operator be able to produce certificates drawn up by independent bodies attesting that the economic operator complies with the required quality assurance standards, including accessibility for disabled persons?</cbc:Description>
        <cac:Legislation>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b4585532-0e0b-4ed1-a72d-208030547060</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="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">EN</cbc:LocaleCode>
                </cac:Language>
        </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4887c3d7-05fc-4e3e-b066-f338910f0c4c</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e11eba0e-66fd-4735-9aaa-614b006662fc</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41e950d1-47fd-4db6-be18-cbe82e779391</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c33cf7bb-85f0-4f85-990d-0e056c869b5b</cbc:ID>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">83f2f79e-0455-4918-89ff-d7829e8bf758</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d14b8965-e439-4d5c-8959-860b44ad38cb</cbc:ID>
                                <cbc:Description>If not, please explain why and state which other means of proof can be provided:</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- rest of elements removed for brevity -->

VI.12.2 Self-contained Quality Assurance schemes and environmental management standards

Mock-ups - contracting authority perspective

In the Self-contained version the contracting authority can specify a REQUIREMENT. In this example it provides the name of the ISO it expects the economic operator to be conformant to.

Figure 187. Self-contained 'Quality Assurance schemes and environmental management standards' CA mock-up

Mock-ups - economic operator perspective

Notice that, as for the Regulated version 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).

Figure 188. Self-contained 'Quality Assurance schemes and environmental management standards' EO mock-up

Data Structure - Self-contained

Notice the following:

In principle the contracting authority (CA) has to provide at least one REQUIREMENT. But it might decide not to provide any requirement at all, in which case the behaviour of the GUI would be similar to the one for the Regulated version. 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'.
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.
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).

Figure 189. Self-contained 'Quality Assurance schemes and environmental management standards' criteria data structure

XML Example - Self-contained

Self-contained '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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a7669d7d-9297-43e1-9d10-691a1660187c</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.CERTIFICATES.QUALITY_ASSURANCE.QA_INSTITUTES_CERTIFICATE</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>
        <!--Legislation eliminated for brevity -->
        <!--National sub-criterion eliminated for brevity -->
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">612d99eb-ea3b-4275-ac06-0db05e039c8c</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">348a935d-5418-467c-ab57-d5aaf1d1b614</cbc:ID>
                        <cbc:Description>Requirement</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">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="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">4887c3d7-05fc-4e3e-b066-f338910f0c4c</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">32ddd941-7efe-4333-aa4d-77d8d585f2bc</cbc:ID>
                                <cbc:Description>Your answer?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9c7e3e3f-8bdf-4e36-a171-3ea55a515a1b</cbc:ID>
                                        <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6947b635-dfdb-4581-b41b-9b543b765369</cbc:ID>
                                                <cbc:Description>Evidence supplied</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_Identifier</cbc:ValueDataTypeCode>
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">83f2f79e-0455-4918-89ff-d7829e8bf758</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONFALSE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0bc3265c-3d6a-4ff1-ba52-c0a2007f8fa9</cbc:ID>
                                        <cbc:Description>If not, please explain why and state which other means of proof can be provided:</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VII. Other aspects of participation and selection

VII.1 Reduction of candidates

In restricted procedures, competitive procedures with negotiation, competitive dialogue procedures and innovation partnerships, contracting authorities may limit the number of candidates meeting the selection criteria that they will invite to tender or to conduct a dialogue ^[7].

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 contracting authority to specify these objective and non-discriminatory criteria and for the economic operator to declare that it meets them.

Differences between Regulated and Self-contained

The data structure for this criterion is identical for both the REGULATED and the SELF-CONTAINED flavours.

Data structure (Regulated and Self-contained)

The figure below shows the data elements required to the economic operator for this criterion in the ESPD-Request:

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.

This example is extensively commented in section Request/Response XML example (both the Request and the Response). Please consult this section for further details.

Reduction of Candidates - (QUESTION(s) in the ESPD-Request)

<!-- ... beginning of document removed for brevity -->

<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">51c39ba9-0444-4967-afe9-36f753b30175</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.REDUCTION_OF_CANDIDATES</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:TenderingCriterionPropertyGroup>
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ecc69670-f428-4446-908f-689568ca0d0d</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
        <cac:TenderingCriterionProperty>
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c110177c-aa9a-4acd-809a-79a2353a41ef</cbc:ID>
            <cbc:Description>Your answer?</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
        </cac:TenderingCriterionProperty>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f13754df-7e15-4155-aaa6-7ca6407baa47</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e437cac1-3a89-4f36-bcc7-3219dda49d30</cbc:ID>
                <cbc:Description>Please describe them</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
    <cac:TenderingCriterionPropertyGroup>
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
        <cac:TenderingCriterionProperty>
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cfe146f7-8d5e-4e9a-a5e1-26a132e8f3c1</cbc:ID>
            <cbc:Description>Is this information available electronically?</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
        </cac:TenderingCriterionProperty>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">36c95410-2261-4987-b989-d75e1f877d0d</cbc:ID>
                <cbc:Description>Evidence supplied</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

VIII. The ESPD Response document

VIII.1 Business requirements specification

The ESPD-EDM V2.1.0 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 contracting authority.

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 contracting authority 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 CA 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.

VIII.2 ESPD Request XSD Schema

For the ESPD Response, the ESPD-EDM V2.1.0 uses the UBL-2.2 document named QualificationApplicationResponse.xsd XSD Schema. This schema can be found under the folder dist/xsdrt/maindoc (or the equivalent documented xsd folder).

The figure below shows the XSD Schema defined by UBL-2.2 for this document, which replaces the Schema for the “ESPD Request” document used in the previous versions of the ESPD-EDM. The figure below shows a diagram representing the UBL-2.2 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. 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.2 Schema there are only four mandatory elements: cbc:IssueDate, ContractFolderID, cac:ContractingParty (the contracting authority) 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:ContractingAuthorityParty, ProcurementProject, ProcurementProjectLot and AdditionalDocumentReference refer to the section III. The ESPD Request document.

Figure 191. QualificationApplicationResponse XSD Schema, global view

LEGEND: The figure below enumerates the four different types of optionality and cardinality for the elements of the UBL-2.2 Schema:

Figure 192. Legend: QualificationApplicationRequest XSD Schema, possible cardinalities of the Schema elements

VIII.3 ESPD Response cardinalities

As you can see the UBL-2.2 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 V2.1.0 structure for the ESPD Response with its own cardinality restrictions. Notice that ESPD-EDM does not change anything else from the UBL-2.2 Schema.

Figure 193. ESPD-EDM 'QualificationApplicationResponse', UML diagram

If you compare both figures you will observe that:

The cardinalities of the root common basic components, such as cbc:ID, cbc:UUID, cbc:TendererRole, cbc:QualificationApplicationTypeCode, ProcedureCode, and other are different for the ESPD than for UBL-2.2;
Similarly, the cardinalities of aggregate components like cac:ContractingParty, cac:ProcurementProjectLot and cac:TenderingCriterion are different to the UBL-2.2 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 V2.1.0 distribution package provides Schematron schemata and CVA files ^[8] for the validation of the XML instances (folder dist/val).

The European Commission (EC) ISA2 Programme provides an Interoperability Testbed where Stakeholders can freely test these validation artefacts.

VIII.4 Root elements

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

Table 27. Class QualificationApplicationResponse, components required by the ESPD-EDM V2.1.0
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:	dist/xsdrt/maindoc/UBL-QualificationApplicationResponse-2.2-Pre-award.xsd

Components Type Card Description Requirements

cbc:UBLVersionID

Identifier

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

Information Requirement: tbr92-020.

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

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

cbc:CustomizationID

Identifier

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

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

Identifier

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.

cbc:UUID

Identifier

0..1

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

Information Requirement:http://wiki.ds.unipi.gr/display/ESPDInt/BIS+41+-+ESPD+V2.1.0#BIS41-ESPDV2.1-tbr92-019[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

Information Requirement: tbr92-013.

Rule scope: REGULATED (BR-REG-20), SELF-CONTAINED (BR-SC-30)

cbc:IssueDate

Date

Date when the document was issued by the contracting authority.

Information Requirement: tbr92-019.

Rule: Format "YYYY-MM-DD".

cbc:IssueTime

Time

0..1

Time when the document was issued by the contracting authority.

Information Requirement: tbr92-019.

Rule: Format "hh:mm:ss".

cbc:EconomicOperatorGroupName

Code

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: SELF-CONTAINED (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

Identifier

0..1

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

Information Requirement:

Rule: Compulsory use of attributes listID, listAgencyName and listVersionID. Compulsory use of the code list ProcedureType (values: Open, Restricted, Accelerated, Competitive dialogue, etc.). Do not confound with the object of the procurement project (code list ProjectType: Works, Supplies, Services).

Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#1, BR-OTH-03)

cbc:QualificationApplicationTypeCode

Code

The type of European Single Procurement Document (ESPD).

Information Requirement: tbr92-019.

Rule: Compulsory use of the codelist QualificationApplicationType (values 'REGULATED`, SELFCONTAINED). Compulsory use of attributes listID, listAgencyName and listVersionID.

Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#2, BR-OTH-03)

cbc:WeightScoringMethodologyNote

Text

0..n

Free-form text to describing information about Weight Scoring Methodology.

Information Requirement: tbr070-016

Rule: Used for transparency motives. Provide a text explaining clearly the method that will be used to select those selection criteria that will be weighted.

Rule scope: Common (BR-2P-10)

cbc:WeightingTypeCode

Code

0..1

A code specifying the type of the Weighting.

Information Requirement: tbr070-016

Rule: Compulsory use of the code list WeightingType. If this element it is not instantiated and one or more selection criteria are weighted the type defaults to NUMERIC.

Rule scope: Common (BR-2P-10)

cac:ContractingParty

Associated class

Information Requirement: tbr92-011.

cac:EconomicOperator

Associated class

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

Associated class

0..1

An overall definition of the procurement procedure.

Information Requirement: tbr92-013.

Rule: Use this component to identify and describe the procurement administrative procedure. If the procurement procedure is divided into lots use the ProcurementProjectLot component to provide details specific to the lot and reserve the ProcurementProject component to describe the global characteristics of the procedure.

cac:ProcurementProjectLot

Associated class

0..1

One of the procurement project lots into which this contract can be divided.

Information Requirement: tbr92-014.

Rule: If there is only one single procurement project lot specified, the ESPD refers then to a procurement procedure without lots.

Rule scope: SELF-CONTAINED (BR-LOT-30)

cac:TenderingCriterion

Associated class

1..n

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

The figure below shows a global view of an ESPD Response XML instance (all nodes have been 'collapsed' to simplify the view):

Figure 194. An ESPD Response XML instance (global view)

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: REGULATED-ESPDResponse-2.1.0.xml or SELFCONTAINED-ESPDResponse-2.1.0.xml.

<QualificationApplicationResponse xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationResponse" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:espd="urn:com:grow:espd:2.1.0" 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" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:X-test:UBL:Pre-award:QualificationApplicationResponse ../xsdrt/maindoc/UBL-QualificationApplicationResponse-2.2-Pre-award.xsd">
<?xml version="1.0" encoding="UTF-8"?>
        <!-- The ESPD-EDM-V2.1.0 is entirely based on OASIS UBL-2.2 -->
        <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
        <!-- How ESPD-EDM-V2.1.0 uses the UBL-2.2 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-V2.1.0 refers to the CEN profile -->
        <cbc:ProfileID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">41</cbc:ProfileID>
        <!-- The identifier of this document provided by the contracting authority system -->
        <cbc:ID schemeAgencyID="DGPE">ESPDREQ-DGPE-46be0fdd00</cbc:ID>
        <!-- Indicator of 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">901afdb9-8f7d-4c43-823b-725eeda3208d</cbc:UUID>
        <!-- The reference number the contracting authority assigns to this procurement procedure -->
        <cbc:ContractFolderID schemeAgencyID="DGPE">PP.20170419.1024-9</cbc:ContractFolderID>
        <cbc:IssueDate>2017-04-13</cbc:IssueDate>
        <cbc:IssueTime>19:09:11</cbc:IssueTime>
        <!-- The name of the group (Consortium, Joint Venture, etc.) if the tenderer is not a sole contractor -->
        <cbc:EconomicOperatorGroupName>ACME-Consortium</cbc:EconomicOperatorGroupName>
        <!-- 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; e.g. V = Award of contract without prior publication of a contract notice -->
        <cbc:ProcedureCode listID="ProcedureType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">OPEN</cbc:ProcedureCode>
        <!-- The type of the ESPD (REGULATED or SELFCONTAINED) -->
        <cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>

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

VIII.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 contracting authority.

For EU and national publications that need to be included in the ESPD Response sSee the section "III.4 EU and national 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.

Figure 195. Elements expected to reference the ESPD Request from the ESPD Response

If the contracting authority 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:ExternalRefernce/cbc:URI:

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 28. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:AdditionalReferenceDocument
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

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

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: SELF-CONTAINED (BR-OTH-02)

cbc:DocumentTypeCode

Code

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 DocRefContentType. 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 LanguageCodeEU 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 contracting authority.

Information Requirement: tbr92-013.

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

cbc:IssueTime

Time

0..1

Time when the document was issued by the contracting authority.

Information Requirement: tbr92-013. Rule: If available in the referenced document place here the time of publication by the contracting authority.

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 29. External Reference
Component name:	cac:ExternalReference
Definition:	A reference to the authentic source of content of this document.
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:AdditionalReferenceDocument/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.

VIII.6 Economic Operator

See formal requirements related to the economic operators in the e-Sens site: (tbr092-001, _tbr092-008).

Table 30. Information requirement about the ESPD Response and the economic operators
REQUIREMENT	One ESPD Response per economic operator. The ESPD-EDM-2.1.0, 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.

Table 31. Information requirement about the identifiers of the economic operators
REQUIREMENT	For the identification of the economic operators the UBL-2.2 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 32. 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.

About the definition of economic operator

Beware that this ESPD-EDM V2.1.0 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.

Differences between Regulated and Self-contained

Both, REGULATED and SELF-CONTAINED versions use the same elements from the UBL-2.2 XSD Schema. Differently to version 1.0.2.
The REGULATED version expects the role as a text.The SELF-CONTAINED version allows for the specification of the role of the economic operator as a code. Depending on the role code the software applications can decide which sets of data show or hide in the GUI, validate or not, process or not.
The REGULATED version expects the identification of members of a group as a text. In the SELF-CONTAINED version the members of the group are identified separately (name, ID and type of ID, and activity in the procedure).
In the SELF-CONTAINED version the information required about the entities upon which the economic operator relies on or not is richer and more structured than in the REGULATED version.
The treatment of the data about the (pre)qualification of the economic operator varies; in the SELF-CONTAINED versions is more structured and aims at making possible the implementation of the Once-Only-Principle, based on the premise that all the trusted (pre)qualification systems will be registered in e-Certis.
When specifying the Lots to which the Economic Operator wishes to tender, the REGULATED ESPD expects a DESCRIPTION, whilst the SELF-CONTAINED expects a LOT_IDENTIFIER.

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:EconomicOperator 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 V2.1.0 is based entirely on the UBL-2.2 XSD (W3C) Schemas, these schemas are to be used for both the Regulated and the Self-contained versions of the ESPD.

Remember that the backwards compatibility between ESPD-EDM V2.1.0 and ESDP-EDM V1.0.2 is only ensured for the Regulated version.

Nonetheless some data requested in the ESPD are not modeled in UBL-2.2, 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-2.1.0, and for both the REGULATED and the SELF-CONTAINED versions, the information about the economic operator is spread in two different places:

The UBL-2.2 cac:EconomicOperatorParty component; and
In criteria data structures: following the solution adopted for Version 1.0.2 of the ESPD-EDM, the ESPD-EDM V2.1.0 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.2 cac:TenderingCriterion) to structure these data. The sub-sections below cover both.

XSD Schemas

cac:EconomicOperatorParty

The UBL-2.2 cac:EconomicOperatorParty has three common aggregate components, the XSD Schema looks like this:

Figure 197. cac:EconomicOperatorParty XSD, global view

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. (circle #13);
cac:EconomicOperatorRole: use to place the role of the economic operator (circle #1);
cac:Party: used to place the data to identify the EO and its contact (circles #2 to #12).

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 V2.1.0 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 V2.1.0 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) ^[9]; see also footnote #6:
- 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 EOIndustryClassificationCode. 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.

Figure 198. cac:QualifyingParty element, XSD

cac:EconomicOperatorRole

The UBL-2.2 element for the role of the economic operator is quite straightforward and typical in UBL: it provides a pair code + description (see Code List EORoleType for the codes and descriptions; see also the XML example below).

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.

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.

Figure 201. The rich structure of a UBL-2.2 'Classification Scheme' for the representation of taxonomies

Figure 202. The structure of UBL-2.2 'Capability'

Figure 203. The structure of the UBL-2.2 Completed Task (used for references)

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

Figure 204. The UBL-2.2 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 III. 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 bid.

Table 33. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:EconomicOperatorParty
Context of use:	The ESPD Response document.

Components

Type

Card

Description

Requirements

cac:QualifyingParty

Associated class

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 V2.1.0 as it is the natural placeholder for several relevant data about the Economic Operator.

Rule scope: SELF-CONTAINED (BR-RESP-10-01)

cac:EconomnicOperatorRole

Associated class

The function of the economic operator when bidding from a consortium (Sole contractor / Lead entity, member of a group, etc.).

Information Requirement:

Rule: This element is compulsory in the ESPD-EDM V2.1.0 because depending on it different sets of data will be required or not, shown or hidden, processed or skipped.

cac:Party

Associated class

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 34. 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):	SELF-CONTAINED (BR-RESP-10-01)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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.2 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 CurrencyCode.

Rule scope: SELF-CONTAINED (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:PartyIdentifier/cbc:ID

Identifier

0..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:PartyIdentificaton/cbc:ID for the value of the identifier. Additionally you can use the data structure CRITERION.OTHER.EO_DATA.REGISTERED_IN_OFFICIAL_LIST to specify an alternative or additional name, identifier and description. 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: SELF-CONTAINED ( BR-RESP-80-S10, BR-RESP-80-S20), Common (BR-RESP-50, BR-OTH-02)

Table 35. Economic operator role, expected elements
Class name:	cac:EconomicOperatorRole
Definition:	The function of the economic operator when bidding from a consortium (Sole contractor / Lead entity, member of a group, etc.).
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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

Identifies the role of the economic operator in the bid.

Information Requirement: tbr92-008 Rule: Compulsory use of the Code List EORoleType.

Rule scope: SELF-CONTAINED (BR-RESP-10-03, BR-OTH-01, BR-OTH-01#15, BR-OTH-03)

cbc:RoleDescription

Text

0..n

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

Rule scope: Common (BR-RESP-10-02)

Table 36. (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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:EconomicOperatorParty/cac:Party

Components Type Card Description Requirements

cac:PartyIdentification/cbc:Identifier

Identifier

An identifier that identifies the economic operator, such as a the VAT number, the company registration number in a Business Register, other.

Information Requirement: tbr92-001.

Rule: More than one identifier can be specified. Compulsory use of the attribute schemeAgencyID and highly recommended the use of the attribute schemeAgencyID. The preferred identifier is the national VAT number. Additional identifiers 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.2 component cac:PartyLegalEntity: this element is the perfect placeholder for the data officially registered in a Business Register (see UBL-2.2 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 scope: Common (BR-RESP-10-08)

cac:PartyName/cbc:Name

Text

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

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 parameters established by the EU Recommendation 2003/361 to determine whether the EO’s company is micro, small, medium or large. Beware that these parameters may change in the future.

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 37. Economic operator postal address, expected elements
Class name:	cac:PostalAddress
Definition:	Postal address information.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:EconomicOperator/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

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 CountryCodeIdentifier (ISO 3166-1 2A:2006).

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 38. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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.

Please see also the section III.6 Service Provider (for the ESPD Request) for other details and comparison with the previous version 1.0.2 of the ESPD-EDM.

Table 39. Service provider, expected elements
Class name:	cac:ServiceProviderParty/cac:Party
Definition:	Main information about the service provider.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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 scope: Common (BR-RESP-10-08)

cac:PartyIdentification/cbc:ID

Identifier

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

Information Requirement: tbr070-021.

Rule scope: Common (BR-RESP-10-11, BR-OTH-02)

cac:PartyName/cbc:Name

Text

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

Identifier

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 CountryCodeIdentifier (ISO 3166-1 2A:2006).

Rule scope: SELF-CONTAINED (BR-RESP-10-10, BR-OTH-01, BR-OTH-01#5, BR-OTH-03)

VIII.6.1 Regulated economic operator party

Mock-ups and data structures

The mock-up below shows the set of data required about the economic operator for the Regulated version of the ESPD:

Mock-up (1/8): Basic identification data:

Figure 205. Regulated economic operator, mock-up

The following figures below show the data aimed at other purposes (namely statistical), that is structured using the UBL-2.2 cac:TenderingCriterion. See the XML example below to check how both, the cac:EconomicOperatorParty and these data structures are used.

Mockup (2/8): Sheltered workshop or social business in case of reserved procurement:

Figure 206. Sheltered workshop or social business - mock-up

Data structure for a sheltered workshop or social business in case of reserved procurement:

Figure 207. Sheltered workshop or social business - data structure

Mockup (3/8): Registration on an official list, tenderer register or (pre)qualification system:

Figure 208. EO registration on a (pre)qualified system, mock-up

Data structure for the (pre)qualification of the economic operator by an official list or similar:

Figure 209. Prequalification-related data structure

Mock-up (4/8): Role and other members of the group:

Figure 210. Role and other members of the group, mock-up

Data structure for the role and members of the group (when bidding as a Consortium, Joint Venture, etc.) Beware that the name of the group has its own placeholder in the UBL-2.2 data model: /QualificationApplicationResponse/cbc:EconomicOperatorGroupName

Figure 211. EO Role and group-related data

Mock-up: (5/8): Lots to which the economic operator tenders:

Figure 212. Lots to which the EO tenders, mock-up

Data structure for the Lots to which the economic operator tenders to:

Figure 213. Lots tendered, data structure

Mock-up(6/8): Certificates about contributions to the Tax Agency and/or Social Security:

Figure 214. Contributions certificates

Data structure for the certificates about contributions to the Tax Agency and/or Social Security:

Contributions certificates - data structure

Figure 215. Contributions certificates

Mock-up (7/8): Entities on which the economic operator relies on to meet the selection criteria. Notice only a *Yes or No answer is expected:

Figure 216. Entities upon which the EO relies on, mock-up

Data structure for the entities the EO relies on:

Figure 217. Entities relied on - data structure

Mock-up: (8/8): Entities on which the economic operator does not rely on to meet the selection criteria. Notice only a *Yes or No answer is expected, plus a sequence of entity names as a text:

Figure 218. Entities upon which the EO does not rely on, mock-up

Data structure for the subcontractor upon which the EO does not relied to meet the selection criteria:

Figure 219. Entities not relied on - data structure

XML Example (REGULATED economic operator)

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.

Compare with the XML example about the economic operator for the SELF-CONTAINED ESPD Response. You will notice some differences, e.g. the Role of the economic operator, number of employees, and other.

The figure below shows how the data about the economic operator looks like in a 'collapsed' SELF-CONTAINED ESPD XML instance (notice that in this example the EO belongs to a group named 'AIAPU', element /cac:EconomicOperatorGroupName; beware that the group name is a data element located at the root of the document).

Figure 220. Vision of the data about the EO in a 'collapsed' Regulated ESPD

This fragment of XML does not include the responses to the QUESTION(s) in the data structures, yet. This is because the Responses have to be associated to a criterion property. The fragment below shows how these criterion properties are prepared and a 'dynamic' UUID is associated to each criterion property. Later on the response values will use these UUID to link the actual response to each QUESTION (i.e. with each cac:TenderingCriterionProperty element). Therefore the example does not include the data about the the EO yet. To see how the EO provides these data please see the sections below about the Response. There you will see that each element cac:ResponseValue is associated to a the UUID of the corresponding cac:TenderingCriterionProperty. For an example of a complete REGULATED ESPD Response XML document you can also see the file REGULATED-ESPDResponse-2.1.0.xml.

Economic operator data - XML example

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

<!-- Economic Operator Data -->
<cac:EconomicOperatorParty>
        <cac:QualifyingParty>
                <cac:Party>
                        <!-- This EO company is NOT an SME -->
                        <cbc:IndustryClassificationCode listID="EOIndustryClassificationCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LARGE</cbc:IndustryClassificationCode>
                </cac:Party>
        </cac:QualifyingParty>
        <cac:Party>
                <cbc:WebsiteURI>http://everis.com/global/en</cbc:WebsiteURI>
                <cac:PartyIdentification>
                        <cbc:ID schemeAgencyID="ES-VAT" schemeAgencyName="Spanish Tax Agency" schemeID="VIES" schemeURI="http://ec.europa.eu/taxation_customs/vies/vieshome.do?locale=es" schemeName="ES Value Added Tax 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="CountryCodeIdentifier" listName="ISO-1-ALPHA-2" listAgencyID="ISO" listVersionID="1.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>
<!-- OTHER DATA ABOUT THE ECONOMIC OPERATOR THAT IS MODELLED AS CRITERIA -->
<!-- Criterion:EO is a sheltered workshop -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2043338f-a38a-490b-b3ec-2607cb25a017</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.SHELTERED_WORKSHOP</cbc:CriterionTypeCode>
        <cbc:Name>EO is a sheltered workshop</cbc:Name>
        <cbc:Description>Only in case the procurement is reserved: is the economic operator a sheltered workshop, a 'social business' or will it provide for the performance of the contract in the context of sheltered employment programmes?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6febbe4a-e715-427c-a2b1-19cfabadaef0</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">97402ce3-b321-469e-9fa2-d3c3e3e09ca9</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a5e33369-e2b5-45f7-9969-ddb1c3ae17c8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">57dc3ba0-eda3-48cb-8e58-c065f12ad7a8</cbc:ID>
                                <cbc:Description>What is the corresponding percentage of disabled or disadvantaged workers?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERCENTAGE</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f536b7eb-d393-483f-bbe8-67161e7552a2</cbc:ID>
                                <cbc:Description>If required, please provide details on whether the employees concerned belong to a specific category of disabled or disadvantaged workers?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:EO registered in a PQS -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.REGISTERED_IN_OFFICIAL_LIST</cbc:CriterionTypeCode>
        <cbc:Name>EO registered in a PQS</cbc:Name>
        <cbc:Description>If applicable, is the economic operator registered on an official list of approved economic operators or does it have an equivalent certificate (e.g. under a national (pre)qualification system)?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">64162276-7014-408f-a9af-080426bfe1fd</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3f5959b0-6367-4f0e-96c2-a44635bbf84e</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a1e91ee8-30d3-43bc-886c-c72fb2fc173b</cbc:ID>
                                <cbc:Description>a) Please provide the name of the list or certificate and the relevant registration or certification number, if applicable</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c49b62b7-fc29-48ba-b55e-71071e26b967</cbc:ID>
                                <cbc:Description>b) If the certificate of registration or certification is available electronically, please state where</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">URL</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ebc94ce3-7344-4300-8b63-770b8dcf0f94</cbc:ID>
                                <cbc:Description>c) Please state the references on which the registration or certification is based, and, where applicable, the classification obtained in the official list</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5d901b56-a49d-4f2f-b7d5-e91f8480e230</cbc:ID>
                                <cbc:Description>d) Does the registration or certification cover all of the required selection criteria?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:EO together with others -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ee51100f-8e3e-40c9-8f8b-57d5a15be1f2</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.TOGETHER_WITH_OTHERS</cbc:CriterionTypeCode>
        <cbc:Name>EO together with others</cbc:Name>
        <cbc:Description>Is the economic operator participating in the procurement procedure together with others?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d939f2c6-ba25-4dc4-889c-11d1853add19</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">843676a4-303f-4ffa-bd0b-3531dcc3b731</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f5663c5a-d311-4ae4-be14-1575754be5f2</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e0f36b44-1c60-419c-b4bd-e33049612f6d</cbc:ID>
                                <cbc:Description>a) Please indicate the role of the economic operator in the group (leader, responsible for specific tasks...)</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">cfea21b1-e431-4aeb-a535-1f8e2e27324b</cbc:ID>
                                <cbc:Description>b) Please identify the other economic operators participating in the procurement procedure together</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Lots the EO tenders to -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.LOTS_TENDERED</cbc:CriterionTypeCode>
        <cbc:Name>Lots the EO tenders to</cbc:Name>
        <cbc:Description>Where applicable, indication of the lot(s) for which the economic operator wishes to tender</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">b98984d5-95fa-45cd-a6d1-c017a6aeb62e</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Contributions certificates -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.CONTRIBUTIONS_CERTIFICATES</cbc:CriterionTypeCode>
        <cbc:Name>Contributions certificates</cbc:Name>
        <cbc:Description>Will the economic operator be able to provide a certificate with regard to the payment of social security contributions and taxes or provide information enabling the contracting authority or contracting entity to obtaining it directly by accessing a national database in any Member State that is available free of charge?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2021715e-2579-4e0b-bc94-14427f49879a</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5b5d1bcd-5a6c-4e1f-8948-62be4bda6211</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">68d0a722-b1f1-4127-af27-7ef59b478805</cbc:ID>
                                        <cbc:Description>URL</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Relied on entities -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0d62c6ed-f074-4fcf-8e9f-f691351d52ad</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.RELIES_ON_OTHER_CAPACITIES</cbc:CriterionTypeCode>
        <cbc:Name>Relied on entities</cbc:Name>
        <cbc:Description>Does the economic operator rely on the capacities of other entities in order to meet the selection criteria set out under Part IV and the criteria and rules (if any) set out under Part V below?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">de11ac14-c2d2-4af6-a08e-e6a848f5ff77</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Not relied on entities -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">72c0c4b1-ca50-4667-9487-461f3eed4ed7</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.SUBCONTRACTS_WITH_THIRD_PARTIES</cbc:CriterionTypeCode>
        <cbc:Name>Not relied on entities</cbc:Name>
        <cbc:Description>Does the economic operator intend to subcontract any share of the contract to third parties?</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d5fe5a71-7fd3-4910-b6f4-5cd2a4d23524</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">63857106-8b44-44af-8ab4-1e3e92bbcc2c</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7f18c64e-ae09-4646-9400-f3666d50af51</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c983c80a-e826-4a88-93a5-46509e98cbcb</cbc:ID>
                                <cbc:Description>If yes and in so far as known, please list the proposed subcontractors</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- EO DATA ENDS HERE -->

<!-- Exclusion and selection Criteria, Responses and Evidences removed for the sake of brevity -->

VIII.6.2 Self-contained economic operator party

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.

Mock-up (SELFCONTAINED economic operator)

The figure below shows a possible mock-up with the information required related to the economic operator in the case of the SELF-CONTAINED ESPD Response.

Figure 221. Economic operator - mock-up (SELF-CONTAINED)

As you will see next, the information required about the economic operators varies depending on several factors:

Is the economic operator a sole trader or does it belong to a group?
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);
Does the economic operator rely on other entities to fulfill the selection criteria?
Is the procurement procedure divided into lots?

One relevant aspect is the Role of the economic operator. The ESPD-EDM V2.1.0 defines four different roles for the EO. The information to be provided by each role varies depending on whether the EO is:

Sole contractor / Lead entity: 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).
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.
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.
Other entity (not relied upon): 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 ^[10].

The simplest case

The simplest case is when:

The economic operator (EO) is a sole contractor
The EO does not rely on other entities
The procurement procedure is not divided into lots

Notice the following:

Sole contractor. We know that the EO is a sole contractor when:
- The role specified is 'Sole contractor / Lead entity' (first field of the mock-up); and (circle #1)
- The EO states that it does not participate together with others; and (circle #24)
- The EO states that it does not participate in a group (last field of the mock-up); (circle #25)
Not an SME. The EO is a large company (circles #13-#15). The definition of what is an SME is provided in the EU recommendation 2003/361^[11]. Notice that, differently to the REGULATED version, the SELF-CONTAINED version 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.
No lots. The software application GUI should not show any information about Lots if the procurement procedure is not divided into Lots. This information is available in the ESPD Request.

Sheltered workshop

For this case the SELF-CONTAINED version works identically as the REGULATED version. 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 (see mock-up for the REGULATED version in section VIII.5.1 Regulated economic operator party. For this purpose the REGULATED and the SELF-CONTAINED data structures are identical:

Data structure for a sheltered workshop or social business in case of reserved procurement:

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 (see mock-up, circles #17-#21).

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) ^[12]. 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 elements in the data structure for this SELF-CONTAINED version are different to the REGULATED one. Notice that int the SELF-CONTAINED version:

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.
The rest of the data are the same as for the REGULATED version: references, classifications and the scope of the registration in respect of the selection criteria of the procurement procedure.

Figure 223. Pre-qualification-related data structure

Lots (contracting authority perspective)

The economic operator should be able to specify to which Lots it tenders. Thus, if the procurement procedure is divided into Lots, the software application should show the list with all the Lots the contracted authority (CA) specified for the economic operator select one or more Lots. See the section III.10 Lots - Self-contained ESPD for details on how the CA specifies Lots. The mock-up below shows the requirements established by the contracting authorities about the Lots of the procurement procedure.

Figure 224. Selection of Lots by the CA, mock-up

Lots (economic operator perspective)

The economic operator should then be able to select the Lots it will tender to. However the software application should control that the requirements established by the contracting authority (CA) are respected. Thus, for example, if the CA established that the economic operator can only tender to one lot the application should block the economic operator from selecting more than one lot.

Data structure for the Lots to which the economic operator tenders to:

Observe that the difference with the REGULATED version is that in the SELF-CONTAINED the Lots are a list of multiple identifiers (cardinality 1..n) instead of a free-text field.

Figure 225. Lots tendered, data structure

Roles of the economic operator

Depending on its role the data that the economic operator (EO) will have to provide is different. In this example (see mock-up):

The EO is the Leader of a Consortium it also had to select Yes to the question on whether it participates in a group. To this the software application reacts displaying a new field for the EO to provide the name of the Consortium (the rest of the members and entities related to this Consortium will have also to provide exactly the same name in their ESPDs).
As it is the Leader this EO will have to identify the rest of procurers and entities. The rest of members and entities participating in the tender shall not be requested to provide this information.
The Leader will also have to identify the entities it relies on and on those it does not rely on (this would also the case for the Sole Contractor). See the two next mock-ups below for the data to be provided on these two entities.

Data structure to identify the rest of the EOs that are members of the group:

In the SELF-CONTAINED version the Lead entity of a group 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:

The data required here is different from the data required in the REGULATED version: name, identifier and activity of the EO.
The values expected for the name and activity are texts.
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.

Figure 226. Lots tendered, data structure

Data structure for the certificates about contributions to the Tax Agency and/or Social Security:

This data structure is identical to the REGULATED version, see circles #22 and #23 in the mock-up above).

Figure 227. Contributions certificates

Mock-up: Information about reliance on the capacities of the other entities

As explained above, the Sole contractor 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 V2.1.0 expects from this role. Remember that this information does not need to be supplied by the members of a group or other entities.

Figure 228. EO Roles-entities relied on, mock-up

Data structure for the entities upon which the EO relies on:

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.

Figure 230. EO Roles-entities not relied on, mock-up

Data structure for the entities upon which the EO does not relies on:

Figure 231. Not relied on entities - data structure

XML Example (SELF-CONTAINED economic operator)

Compare with the XML example about the economic operator for the REGULATED ESPD Response. You will notice some differences, e.g. the Role of the economic operator, number of employees, and other.

Figure 232. Vision of the data about the EO in a 'collapsed' Self-contained ESPD

This fragment of XML does not include the responses to the QUESTION(s) in the data structures, yet. This is because the Responses have to be associated to a criterion property. The fragment below shows how these criterion properties are prepared and a 'dynamic' UUID is associated to each criterion property. Later on the response values will use these UUID to link the actual response to each QUESTION (i.e. with each cac:TenderingCriterionProperty element). Therefore the example does not include the data about the the EO yet. To see how the EO provides these data please see the sections below about the Response. There you will see that each element cac:ResponseValue is associated to the UUID of the corresponding cac:TenderingCriterionProperty via the element cbc:ValidatedCriterionPropertyID. For an example of a complete SELF-CONTAINED ESPD Response XML document you can also see the file SELFCONTAINED-ESPDResponse-2.1.0.xml.

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>(25) (26)

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

<!-- Economic Operator Data -->
<cac:EconomicOperatorParty>
        <cac:QualifyingParty>
                <cbc:EmployeeQuantity>12167</cbc:EmployeeQuantity>(14)
                <cac:FinancialCapability>
                        <cbc:ValueAmount currencyID="EUR">1203000000</cbc:ValueAmount>
                </cac:FinancialCapability>(15)
                <cac:Party>
                        <!-- This EO company is NOT an SME -->
                        <cbc:IndustryClassificationCode listID="EOIndustryClassificationCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LARGE</cbc:IndustryClassificationCode> (13)
                <!-- 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>(19)
                </cac:Party>
        </cac:QualifyingParty>
        <cac:EconomicOperatorRole>
                <cbc:RoleCode listID="EORoleType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">SCLE</cbc:RoleCode>
(1)
                <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 --> (11)
                <cbc:WebsiteURI>http://everis.com/global/en</cbc:WebsiteURI> (12)
                <cac:PartyIdentification>
                        <cbc:ID schemeAgencyID="VAT" schemeAgencyName="EU-COM-GROW" schemeID="VIES" schemeURI="http://ec.europa.eu/taxation_customs/vies/vieshome.do?locale=es" schemeName="VAT number">B82387770</cbc:ID>(10)
                </cac:PartyIdentification>
                <cac:PartyName><cbc:Name>Everis, Spain, S.L.U.</cbc:Name></cac:PartyName>(2)
                <cac:PostalAddress>
                <cbc:CityName>Madrid</cbc:CityName>(5)
                        <cbc:PostalZone>28050</cbc:PostalZone>(4)
                        <cac:AddressLine>
                                <cbc:Line>Manoteras, 52</cbc:Line>(3)
                </cac:AddressLine>
                <cac:Country>
                        <cbc:IdentificationCode listID="CountryCodeIdentifier" listName="ISO-1-ALPHA-2" listAgencyID="ISO" listVersionID="1.0">ES</cbc:IdentificationCode>(6)
                        <cbc:Name>Spain</cbc:Name> (6)
                </cac:Country>
                </cac:PostalAddress>
                <cac:Contact>
                        <cbc:Name>Xavi Ker; Ruth Gomis; Miguel Verde</cbc:Name>(9)
                        <cbc:Telephone>+34 91 749 00 00</cbc:Telephone>(8)
                        <cbc:ElectronicMail>Spain.Proposals.Office@everis.com</cbc:ElectronicMail> (7)
                </cac:Contact>
        </cac:Party>
</cac:EconomicOperatorParty>

<!-- OTHER DATA ABOUT THE ECONOMIC OPERATOR THAT IS MODELLED AS CRITERIA -->

<!-- Criterion:EO is a sheltered workshop -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2043338f-a38a-490b-b3ec-2607cb25a017</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.SHELTERED_WORKSHOP</cbc:CriterionTypeCode>
        <cbc:Name>EO is a sheltered workshop</cbc:Name>
        <cbc:Description>Only in case the procurement is reserved: is the economic operator a sheltered workshop, a 'social business' or will it provide for the performance of the contract in the context of sheltered employment programmes?</cbc:Description> (16)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6febbe4a-e715-427c-a2b1-19cfabadaef0</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8d47e12d-2346-41d8-82fe-afb22ebbd791</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a5e33369-e2b5-45f7-9969-ddb1c3ae17c8</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">031953ad-2f92-4fca-a482-7b8efb7035a7</cbc:ID>
                                <cbc:Description>What is the corresponding percentage of disabled or disadvantaged workers?</cbc:Description> (16)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERCENTAGE</cbc:ValueDataTypeCode>(16)
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6e2f7c96-61ac-443b-9039-c45fa3a3e595</cbc:ID>
                                <cbc:Description>If required, please provide details on whether the employees concerned belong to a specific category of disabled or disadvantaged workers?</cbc:Description>(16)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:EO registered in a PQS -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.REGISTERED_IN_OFFICIAL_LIST</cbc:CriterionTypeCode>
        <cbc:Name>EO registered in a PQS</cbc:Name>
        <cbc:Description>If applicable, is the economic operator registered on an official list of approved economic operators or does it have an equivalent certificate (e.g. under a national (pre)qualification system)?</cbc:Description>(17)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">64162276-7014-408f-a9af-080426bfe1fd</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">343b5c92-2a5f-4ef7-9d8a-41c8e7b70aa7</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9f5528c1-6f7f-41e0-9287-054a0bef2f9f</cbc:ID>
                                <cbc:Description>a)Alternative or additional name of the (pre)qualifiction system</cbc:Description>(18)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3eb9b248-21de-47fa-9aa2-e34d0bf1d32c</cbc:ID>
                                <cbc:Description>c) Please state the references on which the registration or certification is based, and, where applicable, the classification obtained in the official list</cbc:Description>(20)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f6109977-1e25-4926-85f5-813db5c113d5</cbc:ID>
                                <cbc:Description>d) Does the registration or certification cover all of the required selection criteria?</cbc:Description> (21)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:EO together with others -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ee51100f-8e3e-40c9-8f8b-57d5a15be1f2</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.TOGETHER_WITH_OTHERS</cbc:CriterionTypeCode>
        <cbc:Name>EO together with others</cbc:Name>
        <cbc:Description>Is the economic operator participating in the procurement procedure together with others?</cbc:Description>(24)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d939f2c6-ba25-4dc4-889c-11d1853add19</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">89f59f77-2dff-4463-8eef-269fdf455ae9</cbc:ID>
                        <cbc:Description>Name of the economic operator in the group</cbc:Description>(28)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1fa05728-308f-43b0-b547-c903ffb0a8af</cbc:ID>
                        <cbc:Description>ID of the economic operator</cbc:Description>(29)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ECONOMIC_OPERATOR_IDENTIFIER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8b7e09d3-f537-43ec-85dc-32d6ad9bccd8</cbc:ID>
                        <cbc:Description>Activity of the economic operator (for this specific procedure)</cbc:Description>(30)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Lots the EO tenders to -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.LOTS_TENDERED</cbc:CriterionTypeCode>
        <cbc:Name>Lots the EO tenders to</cbc:Name>
        <cbc:Description>Lots selected by the economic operator</cbc:Description>(27)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ca0e6adb-a8a3-40f0-9ffa-f9f0b3d95e31</cbc:ID>
                        <cbc:Description>Lot ID</cbc:Description> (27)
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">IDENTIFIER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Contributions certificates -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.CONTRIBUTIONS_CERTIFICATES</cbc:CriterionTypeCode>
        <cbc:Name>Contributions certificates</cbc:Name>
        <cbc:Description>Will the economic operator be able to provide a certificate with regard to the payment of social security contributions and taxes or provide information enabling the contracting authority or contracting entity to obtaining it directly by accessing a national database in any Member State that is available free of charge?</cbc:Description>(22)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c4f182c7-5c47-4a82-9a0c-8f71f84c35a0</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">fb15e5ec-b67f-4fea-8422-c55347078b25</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>(23)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ID>
                                        <cbc:Description>Evidence supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Relied on entities -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0d62c6ed-f074-4fcf-8e9f-f691351d52ad</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.RELIES_ON_OTHER_CAPACITIES</cbc:CriterionTypeCode>
        <cbc:Name>Relied on entities</cbc:Name>
        <cbc:Description>Does the economic operator rely on the capacities of other entities in order to meet the selection criteria set out under Part IV and the criteria and rules (if any) set out under Part V below?</cbc:Description>(31)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">66dd1394-b278-4ee7-b589-e6d750024d16</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">50e9a74e-969e-4d79-8e19-8af71cb7c54a</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1f24933d-6b65-439a-98a7-f235a46ee895</cbc:ID>
                                <cbc:Description>Name of the entity</cbc:Description>(32)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">55b05d39-56b4-4d1f-8af5-9340a071b1bc</cbc:ID>
                                <cbc:Description>ID of the entity</cbc:Description>(33)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">024a5f37-6c39-4c20-8dc0-be55b736f310</cbc:ID>
                                <cbc:Description>Activity of the entity (for this specific procedure)</cbc:Description>(34)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Not relied on entities -->
<cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">72c0c4b1-ca50-4667-9487-461f3eed4ed7</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.SUBCONTRACTS_WITH_THIRD_PARTIES</cbc:CriterionTypeCode>
        <cbc:Name>Not relied on entities</cbc:Name>
        <cbc:Description>Does the economic operator intend to subcontract any share of the contract to third parties?</cbc:Description>(35)
        <cac:TenderingCriterionPropertyGroup>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2f7f9459-c020-4b89-8b27-4e52f25242ce</cbc:ID>
                        <cbc:Description>Your answer?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">50e9a74e-969e-4d79-8e19-8af71cb7c54a</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3fb6d7cc-f605-4eda-80f0-045dcb2c540a</cbc:ID>
                                <cbc:Description>Name of the subcontractor</cbc:Description>(36)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c186fefa-1923-4dbd-85a7-8a007bb75e2c</cbc:ID>
                                <cbc:Description>ID of the subcontractor</cbc:Description> (37)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">98e3401b-4024-4a60-98d2-9e9ad0ba2814</cbc:ID>
                                <cbc:Description>Activity of the entity (for this specific procedure)</cbc:Description>(38)
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0"/>
                        </cac:TenderingCriterionProperty>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

<!-- 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 EORoleType. The selection of the value `SCLE` determines whether the data about the relied-on and not-relied-on entities is instantiated in this XML. In this case, as the value is `SCLE` these data is present in the XML document.
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 EOIndustryClassificationCode (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).
16	Set of data about a sheltered workshop.
17	Set of data about a (pre)qualification system (PQS) where the EO is registered.
18	Alternative name of the PQS.
19	The ID and name of the PQS are in principle to be captured from e-Certis and set in the attributes. If they are not available use the alternative name of the PQS (see previous note <18> and circle #18 in the mock-up).
20	References used to get a classification in the PQS.
21	Statement by the EO kept taken as a self-declaration: scope of the registration or certification in/by a PQS.
22	Statement by the EO kept taken as a self-declaration: engagement to supply a certificate with regard to its social contributions (taxes and social security).
23	Online location of the certificate, if available. A text field. Either the GUI and/or an external Schematron rule could be implemented to control the pattern of this text.
24	Statement by the EO kept taken as a self-declaration: procurement procedure together with others.
25	Statement by the EO kept taken as a self-declaration: part of a group.
26	If the previous question (note <25> and circle #25 of the mock-up) is answered with a Yes the name of the group is placed in the element `cbc:EconomicOperatorGroupName`. Beware that all the members and entities belonging to the group must provide in their respective ESPD Response exactly the same name. Special attention must be paid to the spelling so to ensure that the name of the group can be used as an identifier to link all the members and entities of the group.
27	Lots the EO tenders to. See the responses in the next section to see how this list of Lots is constructed.
28	Name of one member of the group. This EO is the Lead entity and therefore has to identify all the members of the group (ACME-Consortium, in this example). The EO will have to introduce as many groups of name, ID, and activity data as members has the group (except itself).
29	Identifier of the member. The ESPD-EDM preferred option is the VAT number. Notice in the response (in further sections) that the type of identifier goes to the attribute `schemeID` (see values in the Code List EOIDType.
30	Activity of the EO. Free-text field.
31	Group of data about the relied-on entities. As this EO is the Lead entity it has to provide this data. Thus the instance of this data structure in this XML example.
32	Name of an entity. A free-text field.
33	ID of the entity. The ESPD-EDM preferred option is the VAT number. Notice in the response (in further sections) that the type of identifier goes to the attribute `schemeID` (see values in the Code List EOIDType.
34	Activity of the entity. Free-text field.
35	Group of data about the entities upon which the EO does not rely on. As this EO is the Lead entity it has to provide this data. Thus the instance of this data structure in this XML example.
36	Name of a subcontractor. A free-text field.
37	ID of a subcontractor. The ESPD-EDM preferred option is the VAT number. Notice in the response (in further sections) that the type of identifier goes to the attribute `schemeID` (see values in the Code List EOIDType.
38	Activity of the subcontractor. Free-text field.

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

Differences between the Regulated and Self-contained versions

There are no differences between the REGULATED and SELF-CONTAINED versions as far as the economic operator representatives are concerned. Thus, the mock-up, data structure and XML example proposed below are applicable to both cases.

Mock-up (REGULATED and SELF-CONTAINED)

In this example of mock-up the economic operator is specifying two representatives:.

Figure 233. EO representatives, mock-up

XSD Schema (REGULATED and SELF-CONTAINED)

In the The ESPD-EDM V2.1.0 all the data regarding the representative of the economic operators is placed in the UBL-2.2 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.

Figure 234. EO representatives, 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.

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 - Contac - XSD Schema

Figure 236. EO representatives - element Contact, inside Person, XSD Schema

Expected Elements (REGULATED and SELF-CONTAINED)

Table 40. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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

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

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

A code that identifies the country.

Information Requirement: tbr92-009

Rule: Compulsory use of the Code List CountryCodeIdentifier.

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 CountryCodeIdentifier 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 (REGULATED or SELF-CONTAINED)

None, all the data is placed in the UBL-2.2 component cac:PowerOfAttorney

XML Example (REGULATED and SELF-CONTAINED)

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="EOIndustryClassificationCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.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="EORoleType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">SCLE</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>http://everis.com/global/en</cbc:WebsiteURI>
                <cac:PartyIdentification>
                        <cbc:ID schemeAgencyID="VAT" schemeAgencyName="EU-COM-GROW" schemeID="VIES" schemeURI="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="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="1.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>

                <!-- REPRESENTATIVES of the Economic Operator -->
                <!-- Representative 1 -->
                <cac:PowerOfAttorney>
                <cbc:Description>Total powers to make decisions on behalf of the company.</cbc:Description>(12)
                <cbc:Description>Main legal representative with power to make decisions about any aspect related to public procurement contracts with public administrations.</cbc:Description>(7)
                <cac:AgentParty>
                        <cac:Person>
                                <cbc:FirstName>Mary A.</cbc:FirstName>(1)
                                <cbc:FamilyName>Smith</cbc:FamilyName>(8)
                                <cbc:BirthDate>1980-07-17</cbc:BirthDate>(2)
                                <!-- No element for "street and number" present. The user decided not to provide it -->(3)
                                <cbc:BirthplaceName>Brussels</cbc:BirthplaceName>(9)
                                <cac:Contact>
                                        <cbc:Telephone>+322124522</cbc:Telephone>(11)
                                        <cbc:ElectronicMail>masmith@everis.com</cbc:ElectronicMail>(10)
                                </cac:Contact>
                                <cac:ResidenceAddress>
                                        <cbc:CityName>Brussels</cbc:CityName>(5)
                                        <cbc:PostalZone>1000</cbc:PostalZone>(4)
                                        <cac:Country>
                                                <cbc:IdentificationCode listID="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">>BE</cbc:IdentificationCode>(6)
                                                <cbc:Name languageID="en">Belgium</cbc:Name>(6)
                                        </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="CountryCodeIdentifier" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">>ES</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.

VIII.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.2 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:

In the UBL-2.2 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.2 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.
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).

Differences between the Regulated and Self-contained versions

There are no differences between the REGULATED and SELF-CONTAINED versions as far as the answers to the QUESTION(s) are concerned.

XSD Schema (REGULATED and SELF-CONTAINED)

To answer a QUESTION the ESPD-EDM V2.1.0 uses the UBL-2.2 component cac:TenderingCriterionResponse. The expected elements are highlighted in blue in the figure below:

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, e.g. the list of Common Procurement Vocabulary codes (CPV) corresponding to an activity, or a the list of Lot identifiers the EO tenders to, a sequence of cac:ResponseValues shall be instantiated. See XML examples below.

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

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 "IX. Evidences". See also XML examples.

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 contracting authority 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.2 data element cac:TenderingCriterionResponse.

Expected Elements (REGULATED and SELF-CONTAINED)

Table 41. 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):	SELF-CONTAINED (BR-RESP-80, BR-RESP-80-S10, BR-RESP-80-S20), Common (BR-LEAD-10)
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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.

Information Requirement: tbr92-018, tbr92-007, tbr92-005, tbr92-006

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

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

Information Requirement: tbr92-018, tbr92-007, tbr92-005, tbr92-006

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.

Information Requirement: tbr92-018, tbr92-007, tbr92-005, tbr92-006

Rule: If the value is true, all the evidences associated to this response becomes also confidential.

Rule scope: SELF-CONTAINED (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.2 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.

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 42. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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 43. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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

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 44. 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:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.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: SELF-CONTAINED (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.2 instead uses cbc:Response, for this. This is something that needs to be reviewed and agreed between ESPD-EDM and future versions of the UBL. See the XML provided in this ESPD-EDM specifications for details on its usage.

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 "II.4 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 "II.4 Codes and Identifiers" for codes. Several identifiers may be linked to one criterion property thus building a list of identifiers. See XML examples (e.g. in Self-contained references ESPD Response, 'Lots tendered the EO tenders to').

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

<cac:TenderingCriterion>
    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">51c39ba9-0444-4967-afe9-36f753b30175</cbc:ID>
    <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.REDUCTION_OF_CANDIDATES</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:TenderingCriterionPropertyGroup>
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ecc69670-f428-4446-908f-689568ca0d0d</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
        <cac:TenderingCriterionProperty> (1)
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c110177c-aa9a-4acd-809a-79a2353a41ef</cbc:ID>
            <cbc:Description>Your answer?</cbc:Description> (2)
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>(3)
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>(4)
        </cac:TenderingCriterionProperty>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>(5)
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f13754df-7e15-4155-aaa6-7ca6407baa47</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>(6)
            <cac:TenderingCriterionProperty>(7)
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e437cac1-3a89-4f36-bcc7-3219dda49d30</cbc:ID>
                <cbc:Description>Please describe them</cbc:Description>(8)
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>(8)
            </cac:TenderingCriterionProperty>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:TenderingCriterionPropertyGroup>
    <cac:TenderingCriterionPropertyGroup>
        <!-- Block requesting evidences: removed for the sake of brevity and clarity -->
    </cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>

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

1	Here starts the first QUESTION (a criterion property of type QUESTION, the type follows below).
2	Here the contracting authority (CA) is requesting to the economic Operator that it states whether it meets the ''objective and non-discriminatory criteria or rules [..]".
3	The type of the criterion property: QUESTION.
4	The type of data that the economic operator (EO) will have to provide in the response (`true` or `false)`.
5	The next QUESTION is enclose in a SUBGROUP because the processing instruction `ONTRUE` can be used only by GROUPs or SUBGROUPs of REQUIREMENTs and QUESTIONs.
6	If the previous QUESTION is answered with a `true` the EO will be presented with a new demand expressed in th next QUESTION.
7	The QUESTION ''Please describe them'', presented if the EO answered `true` to the previous QUESTION (''Your answer'').
8	The type of data expected here is a free text bythe EO (for the Response, a DESCRIPTION maps to the UBL-2.2 element cbc:Description, which is an extension of the xsd:String).

XML example (Responses to the QUESTION(s))

This other XML snippet below shows the responses to the two QUESTION(s) expressed in the ESPD-Request for this criterion (the block related to evidences is omitted for the sake of clarity and brevity):

Reduction of Candidates - (answers in the ESPD-Response)

<!-- ... beginning of document removed for brevity -->

<cac:TenderingCriterionResponse>
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d47daca4-4a27-4461-9db9-f483d3b7a114</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c110177c-aa9a-4acd-809a-79a2353a41ef</cbc:ValidatedCriterionPropertyID> (1)
    <cac:ResponseValue>
            <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">de6f1bdd-abce-42f7-b9b8-30c4e7c4c94d</cbc:ID>
            <cbc:ResponseIndicator>true</cbc:ResponseIndicator> (2)
    </cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
    <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d47daca4-4a27-4461-9db9-f483d3b7a114</cbc:ID>
    <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">e437cac1-3a89-4f36-bcc7-3219dda49d30</cbc:ValidatedCriterionPropertyID>(3)
    <cac:ResponseValue>
            <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">de6f1bdd-abce-42f7-b9b8-30c4e7c4c94d</cbc:ID>
            <cbc:Description>This Consortium fulfills all the conditions defined by the buyer in the contract notice, and notably
             the Consortium is duly registered in the national pre-qualification system of the country of the Consortium lead where
             all the information about its classification and documentation about its financial standing are up to the date.</cbc:Description>(4)
    </cac:ResponseValue>(3)
</cac:TenderingCriterionResponse>

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

1	Notice this UUID is identical to the `cac:TenderingCriterionProperty` one. This is the way the UBL-2.2 Qualification Application Response document links each QUESTION(s) to one response (and only one), or viceversa.
2	The economic operator states here that it meets the criteria. Notice that the data element is the UBL-2.2 element `cbc:ResponseIndicator`, which is an ''semantisation'' (a specialisation) of cbc:Indicator and therefore corresponds to the type of data expected by the CA in the Request (in `cbc:ValueDataTypeCode`).
3	This is the UUID corresponding to the QUESTION in the Request ''Please describe them''.
4	The economic operator describes how it meets the criteria. The data element containing the explanation by the EO. Notice that the type of data is the UBL-2.2 element `cbc:Description`, as requested by the CA in `cbc:ValueDataTypeCode`.

VIII.8 Evidences

See formal requirements related to evidences in the e-Sens site: (tbr092-017).

Differences between the Regulated and Self-contained versions

There are no differences between the REGULATED and SELF-CONTAINED versions as far as evidences are concerned.

XSD Schema (REGULATED and SELF-CONTAINED)

Remember that evidences are indirectly linked to responses based on the identifier of the evidence: in the response, the element cac:EvidenceSupplied/cbc:ID contains the identifier set in /QualificationApplicationResponse/cac:Evidence/cbc:ID. See XML example below; see also the example XML file "SELFCONTAINED-ESPDResponse-2.1.0.xml" for an example.

The figure below shows the XSD Diagram for the UBL-2.2 component cac:Evidence (elements in blue are the expected ones in ESPD-EDM V2.1.0):

Figure 241. cac:Evidence XSD diagram

The UBL-2.2 element cac:Evidence is a specialisation of cac:DocumentReference. This other XSD diagram shows this association and, in blue, highlights the elements expected in the ESPD-EDM V2.1.0:

Figure 242. cac:DocumentReference inside cac:Evidence XSD diagram

Mock-ups and data structures

In principle only a few elements are kept in the ESPD Response document about an evidence: its Identifier, a URL from where to access its content, a Reference/Code, a Confidentiality indicator, and the Issuer.

This group of data repeats frequently in the many different mock-ups presented in this document. The one below is just one example and will be used to illustrate where the three element go in the XML instance of an evidence (compare the circled numbers #9 to #12 with the comments in the XML snippet below).

Figure 243. Conviction 'Participation in criminal organisation', mock-up (EO perspective)

Duplicity of the Issuer

Beware that the current modeel of UBL-2.2 provides two elements for the Issuer, one for the issuer of the evidence and another for the issuer of the document reference.

The ESPD-EDM V2.1.0 uses always the one inside the document reference to refer to the issuer of the evidence (and of the document that 'is' the evidence). Thus the element used in the ESPD is cac:Evidence/cac:DocumentReference/cac:IssuerParty.

Expected (and other) Elements (REGULATED and SELF-CONTAINED)

This list below enumerates the elements of cac:Evidence that could be used in (that make sense for) an ESPD Response. Notice though that the current versions of the ESPD-EDM only use the few elements mentioned above: ID, URL, Reference/Code, Confidentiality level and Issuer.

Table 45. Elements expected in an Evidence
Class name:	cac:Evidence
Definition:	A class to describe an item of evidentiary support for representations of capabilities or the ability to meet tendering requirements, which an economic operator must provide for acceptance into a tendering process.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:Evidence
Context of use:	The economic operator uses it in the ESPD Response document to provide evidentiary support to one or more criteria (tbr092-017).

Components

Type

Card

Description

Requirements

cbc:ID

Identifier

An identifier for this item of evidentiary support.

Information Requirement: tbr092-017

Rule: The Evidence ID MUST be unique in the ESPD Response XML instance (i.e. two evidences cannot have the same ID value). It is recommended to use always a UUID UUID of version 4 (random generated UUID).

Rule scope: Common (BR-TCR-09, BR-OTH-0)

cbc:EvidenceTypeCode

Code

0..1

A code signifying the type of evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

Rule: A code signifying the type of evidence. Could be used in the future in alignment to e-Certis.

Rule scope: SELF-CONTAINED (BR-OTH-01)

cbc:Name

Text

0..1

The name of the evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

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

cbc:Description

Text

0..1

The textual description for this Evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

Rule: Use this field to keep the Reference/Code of the Evidence.

cbc:CandidateStatement

Text

0..1

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

Information Requirement: tbr092-017, tbr092-007, tbr092-006

Rule: None. Not currently used in ESPD.

cbc:ConfidentialityLevelCode

Code

0..1

A code specifying the confidentiality level of this evidence.

Information Requirement: tbr092-017

Rule: Compulsory use of the Code List linkhttps://github.com/ESPD/ESPD-EDM/tree/2.1.0/docs/src/main/asciidoc/dist/cl/ods/ESPD-CodeLists-V2.1.0.ods[ConfidentialityLevel]. Software application should set this code to CONFIDENTIAL automatically when the confidentiality level code of at least one criterion to which this evidence is associated is set to CONFIDENTIAL.

Rule scope: SELF-CONTAINED (BR-TCR-02, BR-OTH-01, BR-OTH-01#18, BR-OTH-03)

This other table lists the elements from cac:Evidence/cac:DocumentReference used in the ESPD-EDM-V2.1.0:

Table 46. Elements expected from the 'cac:Evidence/cac:DocumentReference' element
Class name:	cac:DocumentReference
Definition:	A reference to the evidentiary document.
Business rule(s):	None
File:	dist/common/xsdrt/UBL-CommonAggregateComponents-Pre-award.xsd
Path:	/QualificationApplicationResponse/cac:Evidence/cac:DocumentReference
Context of use:	The economic operator uses it in the ESPD Response document to supply the URL of the evidence and the party who issued the evidentiary document. (tbr092-017, tbr092-022, tbr092-006, tbr092-007).

Components

Type

Card

Description

Requirements

cbc:ID

Identifier

An identifier for the referenced document.

Information Requirement: tbr092-017, tbr092-022, tbr092-006, tbr092-007

Rule: If the reference or verification code is provided for the evidence use this element to place it. This 'code' is used in some countries (e.g. Spain) to check that the document is authentic. If a verification code is supplied you can use an official 'end-point' to retrieve an image (or a PDF) of the document and check that the evidence is authentic.

Rule scope: SELF-CONTAINED (BR-OTH-02)

cac:Attachment/cac:ExternalReference/cbc:URI

Identifier

The Uniform Resource Identifier (URI) that identifies the external object as an Internet resource.

Information Requirement: tbr092-017, tbr092-022, tbr092-006, tbr092-007

Rule: None. Not currently used in ESPD.

cac:IssuerParty/cbc:ID

Identifier

0..1

The identifier of the party issuer of the documentary evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

Rule: Not currently used in ESPD, but if you decide to use it try to use the VAT number whenever possible.

Rule scope: SELF-CONTAINED (BR-OTH-02)

cac:IssuerParty/cbc:Name

Text

0..1

The name of the party issuer of the documentary evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

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

cac:IssuerParty/cbc:WebsiteURI

URI

0..1

The website of the party issuer of the documentary evidence.

Information Requirement: tbr092-017, tbr092-007, tbr092-006

Rule: None. Not currently used in ESPD-EDM V2.1.0.

XML Examples

Example 1: One evidence shared by two criteria

XML snippet 1.a) the criteria defined in the ESPD Request, and 'copied' in the ESPD Response

XML snippet 1.a) the criteria defined in the ESPD Request, and 'copied' in the ESPD Response (SELF-CONTAINED)

        <!-- Criterion #1:Participation in a criminal organisation -->

        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">005eb9ed-1347-4ca3-bb29-9bc0db64e1ab</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION</cbc:CriterionTypeCode>
                <cbc:Name>Participation in a criminal organisation</cbc:Name>

        <!-- ... -->
        <!-- Elements removed for brevity -->
        <!-- ... -->

                        <cac:TenderingCriterionProperty>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3f61215a-cd38-438b-a355-e4d06c57384c</cbc:ID>
                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                        <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode> (1)
                                <cac:TenderingCriterionProperty>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ID>(2)
                                        <cbc:Description>Evidence Supplied</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode> (3)
                                </cac:TenderingCriterionProperty>
                        </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:TenderingCriterionPropertyGroup>
        </cac:TenderingCriterion>

        <!-- Criterion #2:Contributions certificates -->

        <cac:TenderingCriterion>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
                <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.CONTRIBUTIONS_CERTIFICATES</cbc:CriterionTypeCode>
                <cbc:Name>Contributions certificates</cbc:Name>
                <cbc:Description>Will the economic operator be able to provide a certificate with regard to the payment of social security contributions and taxes or provide information enabling the contracting authority or contracting entity to obtaining it directly by accessing a national database in any Member State that is available free of charge?</cbc:Description>

        <!-- ... -->
        <!-- Elements removed for brevity -->
        <!-- ... -->

                                                <cbc:Description>Is this information available electronically?</cbc:Description>
                                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                                </cac:TenderingCriterionProperty>
                                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                                        <cac:TenderingCriterionProperty>
                                                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ID>(2)
                                                <cbc:Description>Evidence Supplied</cbc:Description>
                                                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                                                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>(3)
                                        </cac:TenderingCriterionProperty>
                                </cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <!-- elements removed for brevity -->
        </cac:TenderingCriterion>

1	The group of fields requesting the URL, Reference/Code and Issuer of the evidence will only be shown, validated or otherwise processed if the answer to the QUESTION is Yes (true).
2	The ID of the criterion property that the response will use in the `cac:ValidatedCriterionPropertyID`. See the response in the XML snippet 1.b) below.
3	The type of the data expected in the response value (when a code EVIDENCE_IDENTIFIER is encountered → an object `cac:Evidence` must be present in the ESPD Response XML instance.

XML snippet 1.b) One evidentiary document supporting the three responses

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

<!-- Answer to Criterion:Participation in a criminal organisation -->
<!-- Property:Evidence Supplied (PropertyID:d8d5478e-cc65-48c9-a189-19bbe87a9bfd) -->
<cac:TenderingCriterionResponse>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">219949a1-b7bb-4d7e-8c3b-cc8ca695e15b</cbc:ID>
        <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ValidatedCriterionPropertyID>(1)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CONFIDENTIAL</cbc:ConfidentialityLevelCode>(2)
        <cac:EvidenceSupplied>
                <cbc:ID>7dea9283-f8a2-481f-9ea6-41438e25fdd4</cbc:ID>(3)
        </cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>


<!-- Answer to Criterion:Contributions certificates -->
<!-- Property:URL (PropertyID:191b34a8-5af0-4d53-b431-4ecd624218ea) -->
<cac:TenderingCriterionResponse>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7c7fb445-c5f9-4f92-8b58-7f06a541951f</cbc:ID>
        <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ValidatedCriterionPropertyID>
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PUBLIC</cbc:ConfidentialityLevelCode>
        <cac:EvidenceSupplied>
                <cbc:ID>7dea9283-f8a2-481f-9ea6-41438e25fdd4</cbc:ID>(3)
        </cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>

<cac:Evidence>
        <cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">7dea9283-f8a2-481f-9ea6-41438e25fdd4</cbc:UUID>(4)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CONFIDENTIAL</cbc:ConfidentialityLevelCode>(5)
        <cac:DocumentReference>
                <!-- Verification code (an EAN-13 barcode number) used in Spain to check the authenticity of the document. -->
                <cbc:ID schemeID="EAN-13" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">5901234123457</cbc:ID>(6)
                <cac:Attachment>
                        <cac:ExternalReference>
                                <cbc:URI>http://minafhp.gob.es/pub/cert?id=5901234123457</cbc:URI>(7)
                        </cac:ExternalReference>
                </cac:Attachment>
                <cac:IssuerParty>
                        <cac:PartyName> (8)
                                <cbc:Name languageID="es">Ministerio de Hacienda y Administracions Públicas</cbc:Name>
                        </cac:PartyName>
                </cac:IssuerParty>
        </cac:DocumentReference>
</cac:Evidence>

</QualificationApplicationResponse>

1	ID value of the criterion property (QUESTION) for which this response value is the answer.
2	The criteron MUST be treated as confidential: only the members of the evaluation team should have access to it. This makes the evidence confidential too.
3	Identifier of the only evidence object that is used for both criteria: it must match the value provided for the `cac:Evidence/cbc:ID` element of the evidence.
4	Identifer of the evidence. It matches the values in the `cac:EvidenceSupplied/cbc:ID` of the two criteria.
5	Confidentiality level is set to 'CONFIDENTIAL' because the first criterion requires to be treated as confidential. Thus even if the second criterion sets 'PUBLIC' as for its level of confidentiality the evidence will be kept confidential.
6	The Reference/Verification code (5901234123457) is in this case a 13 digit EAN-13 barcode number.
7	URL to access the evidentiary document (in this case it’s and end-point using the verification code as an end-point parameter).
8	The name of the issuer party.

Example 2: Two different evidences for two criteria

The following snippet uses the same two criteria shown in the XML example snippet 1.a): hence the values of the cac:ValidatedCriterionPropertyID are 'd8d5478e-cc65-48c9-a189-19bbe87a9bfd' (criterion property 'participation in a criminal organisation') and '7c7fb445-c5f9-4f92-8b58-7f06a541951f' (criterion property 'contributions certificates').

XML snippet 2 different evidentiary documents per response

XML snippet 1.b) different evidentiary documents per response

<!-- ANSWERS TO QUESTION(s) -->

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

<!-- Answer to Criterion:Participation in a criminal organisation -->
<!-- Property:Evidence Supplied (PropertyID:d8d5478e-cc65-48c9-a189-19bbe87a9bfd) -->
<cac:TenderingCriterionResponse>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">219949a1-b7bb-4d7e-8c3b-cc8ca695e15b</cbc:ID>
        <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ValidatedCriterionPropertyID> (1)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PUBLIC</cbc:ConfidentialityLevelCode>(2)
        <cac:EvidenceSupplied>
                <cbc:ID>7dea9283-f8a2-481f-9ea6-41438e25fdd4</cbc:ID>(3)
        </cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>


<!-- Answer to Criterion:Contributions certificates -->
<!-- Property:URL (PropertyID:191b34a8-5af0-4d53-b431-4ecd624218ea) -->
<cac:TenderingCriterionResponse>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7c7fb445-c5f9-4f92-8b58-7f06a541951f</cbc:ID>
        <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ValidatedCriterionPropertyID>(4)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CONFIDENTIAL</cbc:ConfidentialityLevelCode>(5)
        <cac:EvidenceSupplied>
                <cbc:ID>3b3be32e-3b7f-4a17-a0bb-a84210f61bb8</cbc:ID>(6)
        </cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>

<!-- EVIDENCES -->

<cac:Evidence>
        <cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">7dea9283-f8a2-481f-9ea6-41438e25fdd4</cbc:UUID>(7)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PUBLIC</cbc:ConfidentialityLevelCode>(8)
        <cac:DocumentReference>
                <!-- Verification code to access an authentic 'manifestation' of the document from the original issuer end-point -->
                <cbc:ID schemeID="EAN-13" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">5901234123457</cbc:ID>(9)
                <cac:Attachment>
                        <cac:ExternalReference>
                                <cbc:URI>http://interior.gob.es/pub/cert?id=5901234123457</cbc:URI>(10)
                        </cac:ExternalReference>
                </cac:Attachment>
                <cac:IssuerParty>
                        <cac:PartyName>
                                <cbc:Name languageID="es">Ministerio del Interior</cbc:Name>(11)
                        </cac:PartyName>
                </cac:IssuerParty>
        </cac:DocumentReference>
</cac:Evidence>

<cac:Evidence>
        <cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">3b3be32e-3b7f-4a17-a0bb-a84210f61bb8</cbc:UUID>(12)
        <cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CONFIDENTIAL</cbc:ConfidentialityLevelCode>(13)
        <cac:DocumentReference>
                <!-- Verification code to access an authentic 'manifestation' of the document from the original issuer end-point -->
                <cbc:ID schemeID="EAN-13" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">6002345234568</cbc:ID>(14)
                <cac:Attachment>
                        <cac:ExternalReference>
                                <cbc:URI>http://aeat.gob.es/pub/cert?id=6002345234568</cbc:URI>(15)
                        </cac:ExternalReference>
                </cac:Attachment>
                <cac:IssuerParty>
                        <cac:PartyName>
                                <cbc:Name languageID="es">Agencia Tributaria</cbc:Name>(16)
                        </cac:PartyName>
                </cac:IssuerParty>
        </cac:DocumentReference>
</cac:Evidence>

</QualificationApplicationResponse>

1	ID value of the first criterion property (QUESTION) for which this response value is the answer.
2	The criteron is to be treated as 'PUBLIC': it could be published.
3	Identifier of the first evidence object that is used for this criterion: it must match the value provided for the `cac:Evidence/cbc:ID` element of the evidence.
4	ID value of the second criterion property (QUESTION) for which this response value is the answer.
5	Confidentiality level is set to 'CONFIDENTIAL'. Therefore the evidence linked to this response will also be treated as 'CONFIDENTIAL'.
6	Identifier of the second evidence object that is used for this second criterion: it must match the value provided for the `cac:Evidence/cbc:ID` element of the evidence.
7	The identifier of the first evidence. It matches the `cac:EvidenceSupplied/cbc:ID` element value of the first response.
8	Confidentiality code for the first evidence: 'PUBLIC', notice that it is consistent with the fact that the response is also set as 'PUBLIC'.
9	Verification code ID for the first evidence (a 13 digit EAN-13 barcode number in this case).
10	URL from where to get the document. The fact that the evidence MUST BE treated as CONFIDENTIAL is not inconsistent with the fact that the evidence is available online from a free-of-charge national data base.
11	The name of the issuer of the first evidenciary document.
12	ID of the second criterion property (QUESTION) for which this response value is the answer.
13	The criteron is to be treated as 'CONFIDENTIAL': addressed only to the evaluators.
14	Verification code ID of the second evidence.
15	URL from where to get the document.
16	The name of the issuer of the second evidenciary document.

IX Putting pieces together

The ESPD-EDM specification, notably regarding the SELF-CONTAINED ESPD, defines different complex sets of data that are scattered in distant locations of the corresponding XML instance.

Consequently, implementors of software dealing with the ESPD XML instances may have a hard time to identify what needs to go in the XML instance and where. This is the case of, specifically, the data related to three topics: 1) economic operators, 2) lots, and 3) weights.

To help implementors understand these topics and how to deal with them, the sub-sections of this chapter illustrate how to put together the different sets of data related to each topic with abundant figures and comments.

IX.1 All about lots

When a procurement procedure is divided in Lots not all the selection criteria apply to all Lots, i.e. some Lots need to be linked to specific criteria.

In the SELF-CONTAINED ESPD-EDM specification, instead of defining criteria per each Lot, it is for the criterion to specify to which Lots it applies.

To link a criterion with one or more Lots, the ESPD-EDM uses a GROUP (or SUBGROUP) of REQUIREMENT(s), where each REQUIREMENT specifies the identifier of each Lot that is affected by the criterion. The figures below show how this is represented in the four different criteria data structures listed above (''Suitability'', ''Professional risk indemnity'', ''Other economic or financial requirements'' and ''References'').

For more complete examples on how the SELF-CONTAINED ESPD-Request specifies these criteria see the sub-sections VI.2.2 Self-contained suitability (enrolments), Self-contained risk indemnity insurance, VI.7.2 Self-contained other economic or financial requirements, and VI.8.2 Self-contained references.

The folder dist/xml also contains complete XML instances of both REGULATED and SELF-CONTAINED ESPD-Request and ESPD-Response documents.

The REGULATED ESPD documents can only define the Lots into which the procedure is divided into and the Lots to which the economic operator tenders to. The maximum expressivity of information requirements related to Lots is only possible in the SELF-CONTAINED ESPD documents.

Therefore this section focuses only the SELF-CONTAINED ESPD-Response document.

Lots: general information requirement check-list

Criteria with references to Lots: The current design of the UBL-2.2 cac:TenderingCriterion allows referencing Lots for any type of Criteria. However the current version of the ESPD-EDM only identifies this need in a reduced set of Selection Criteria (see the Criteria Taxonomy spread-sheets for more details, like the Criterion description, UUID, Code, etc.):
- Suitability I
  - Criterion #25 - Enrolment in a relevant professional register
  - Criterion #26 - Enrolment in a trade register
  - Criterion #27 - For service contracts: authorisation of particular organisation needed
  - Criterion #28 - For service contracts: membership of particular organisation needed
- Risk insurance
  - Criterion #35 - Professional risk indemnity insurance
- Other economic or financial requirements
  - Criterion #36 -Other economic or financial requirements
- References
  - Criterion #37 - For works contracts: performance of works of the specified type
  - Criterion #38 - For supply contracts: performance of deliveries of the specified type
  - Criterion #39 - For service contracts: performance of services of the specified type
Order of occurrence: The table below presents the different ''blocks'' of data related to Lots in the sequence they must occur in the ESPD-Response. The aim of this table is help implementors identify the type of data structure, what it is used for, where to locate its definition (in the UBL-2.2 XSD Schema and the Criteria Taxonomy spread-sheet), and which comes first and which goes after (i.e. how they are sequenced).

A complete ESPD-Response document with the examples provided in this section can be found in the file Lots-SelfContained-Response_V2.1.0.xml

Table 47. Order of occurrence of the different blocks of data related to Lots
Nº	Data Element	Description	Location	Rules
1	Procurement Procedure Lots	The Lots into which the procurement procedure has been divided into.	At the root of the QualificationApplicationResponse document, in the element `/cac:ProcurementProjectLot`	Only the `cbc:ID` (the identifier of the lot) is required. This set of data is common to all the ESPD-Request and ESPD-Response documents about procedures divided into lots;
2	Criterion ''CA Lots''	Requirements by the CA about the submission of tenders when the procedure is divided into Lots.	Inside a ''false'' criterion data structure C#64 ''CA Lots'' (CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION)	The data provided herein by the CA must be coherent amongst themselves and with the Lots into which the procedure is divided into. This set of data is common to all the ESPD-Request and ESPD-Response documents about procedures divided into lots;
3	Criterion ''Lots the EO tenders to''	The Lots to which the economic operator tenders	Inside a UBL-2.2 element `cac:TenderingCriterion`. This criterion has been defined by the ESPD-EDM (see criterion #62 ''Lots the EO tenders to''. This criterion must occur just after `cac:ProcurementProjectLot`	The Lots specified by the EO in its response must be coherent with the list of Lots specified by the CA (e.g. if the CA has specified 5 Lots, the EO cannot tender to a ''Lot6'' (see row 1 of this table). This set of data is common to all the ESPD-Request and ESPD-Response documents about procedures divided into lots;
4	CA’s REQUIREMENT(s) and QUESTION(s) linked to specific Lots	One or more REQUERIMENT(s) and QUESTION(s) linking one criterion to the lots to which it applies (see XML examples)	Inside a specific criterion, e.g. REQUIREMENTs defined in the ''Suitability'', ''Professional risk insurance'', ''Other economic or financial requirements'' and ''References criteria''	The Lots specified by the CA inside one REQUIREMENT must be coherent with the list of Lots into which the procurement procedure is divided into (see row 1 or this table)
5	EO’s response on its Lots	List of the Lot Identifiers to which the EO tenders to	Inside `/cac:TenderingCriterionResponse/cac:ResponseValue` (as `cbc:ResponseID`)	The Lot identifiers provided by the EO must be coherent with the ones it (the EO) tenders to (see row 2 of this table) and with 1) the ones into which the procedure is divided into, and 2) the ones the CA has specified in the REQUIREMENT(s)

Example 1: Suitability

Mock-up - contracting authority perspective

For each criteria regarding suitability, the CA should be able to provide: the register name, its URL and the Lots to which each requirement apply.

This mock-up represents the situation when the procurement procedure is divided into lots. The contracting authority (CA) may request that the economic operator is registered in one or multiple registers (the REQUIREMENT). Per each register the CA specifies to which Lots this make sense.

This behaviour of “one set of lots per group of properties is regular for all those selection criteria where the allocation of lots to a set of 'criterion properties' make sense.

Figure 244. Self-contained 'Suitability' criterion with Lots (CA perspective)'

Mock-up - economic operator perspective

Notice that:

The Lots and registers specified by the contracting authority are presented to the economic operator (on the left side of the mock-up, circles 1 to 6);
The expected answer is "Yes", meaning that the economic operator fulfills the criterion;
In case of answering "No" the economic operator will have to provide the reasons why it is not registered.

Figure 245. Self-contained 'Suitability' criterion (EO perspective)'

Criterion data structure

Figure 246. 'Enrolment in a relevant professional register' suitability criterion data structure (SELF-CONTAINED)

In this case, ''Enrolment in a relevant professional register'', the ESPD-Request document will contain one or more GROUP(s) of one (only one) REQUIREMENT of multiple cardinality: it can be applied to refer to a subset of Lots. The REQUIREMENT_SUBGROUP, following this list of Lots, contains the specific CA’s constraint that affect the Lots, in this case the CA’s request that the EO needs to be registered in one concrete Register.

XML example

Many compulsory elements and attributes of the XML example below that are not related to the subject covered in this section have been removed to gain clarity and brevity. For complete XML samples download the files under folder dist/xml.

The example presented next was extracted from the file Lots-SelfContained-Response_V2.1.0.xml

'Suitability' XML example (data related to Lots in the ESPD-Response)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cac:QualificationApplicationResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" ... etc. -->
    <!-- Root elements start here-->
    <cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
    <!-- ... etc. (beware that some root elements are compulsory, e.g. cbc:ID -->
    <!-- Main aggregate components -->
    <cac:ContractingParty> ... </cac:ContractingParty>
    <cac:EconomicOperatorParty> ... </cac:EconomicOperatorParty>
    <cac:ProcurementProject>...</cac:ProcurementProject>
    <!-- Root elements end here -->

    <!-- *FIRST SET OF DATA RELATED TO LOTS!* -->
    <!-- In this example the CA informs that the Procurement Procedure is divided into three Lots -->
    <!-- Only the IDs are truly necessary, but the CA is free to provide any other additional data -->

    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot6</cbc:ID>
    </cac:ProcurementProjectLot>
    <cac:ProcurementProjectLot>
         <cbc:ID schemeAgencyID="EU-COM-GROW">Lot7</cbc:ID>
    </cac:ProcurementProjectLot>


    <!-- *2nd. SET OF DATA RELATED TO LOTS: conditions concerning the submission of tenders when a procedure is divided into Lots.
         This is currently modelled as a kind of 'participation' criterion, however UBL-2.2 has a specific different treatment of these information requirements (see the `cac:LotDistribution` element)
         This issue will be reviewed in future versions of the ESPD-EDM. For version 2.1 it is necessary to use this Criterion data structure.
        *Please do not use the UBL-2.2 `cac:LotDistribution` for the time being, as it does not catter for the specification of the type of submission as a code, which is required in the ESPD-EDM. *
        *Beware* that the data provided by the CA needs to be coherent, e.g. the Maximun number of lots that may be awarded to one tenderer
        (2 in this example) cannot be greater than the number of Lots into which this procedure is divided, nor than the value of the Maximum number of
        lots or with the code assigned to the field "Tenders may be submitted for" (LOT_ALL) in this case).
    -->

    <cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">6a21c421-5c1e-46f4-9762-116fbcd33097</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION</cbc:CriterionTypeCode>
        <cbc:Name>CA Lots</cbc:Name>
        <cbc:Description>Please take into account the following requirements regarding the lots of this procurement procedure:</cbc:Description>
        <cac:TenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">03cff8d1-4d22-4435-82fa-d6361af84be6</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f8804fa9-81b7-4f3a-a500-d9e49a4f1efe</cbc:ID>
                <cbc:Description>Tenders may be submitted for</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CODE</cbc:ValueDataTypeCode>
                <cbc:ExpectedCode listID="BidType" listAgencyID="EU-COM-GROW" listVersionID="1.0">LOT_ALL</cbc:ExpectedCode>
            </cac:TenderingCriterionProperty>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3191b16a-37d5-48c5-88b1-8012639d24a4</cbc:ID>
                <cbc:Description>Maximum number of lots</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                <cbc:ExpectedValueNumeric>7</cbc:ExpectedValueNumeric>
            </cac:TenderingCriterionProperty>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2a11f2ef-3fa8-460f-9cb9-869af94926be</cbc:ID>
                <cbc:Description>Maximum number of lots that may be awarded to one tenderer</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                <cbc:ExpectedValueNumeric>2</cbc:ExpectedValueNumeric>
            </cac:TenderingCriterionProperty>
        </cac:TenderingCriterionPropertyGroup>
    </cac:TenderingCriterion>

       <!-- *3rd. SET OF DATA RELATED TO LOTS: Lots to which the EO tenders to.*
           The next criterion data structure is not a 'true' Criterion. It is used by the Economic Operator to specify to which Lots it tenders to.
           In this example, the EO tenders to two lots, Lot1 and Lot3 (see the EO responses to complete the understanding of this. Thus, the first QUESTION
           (identified as a71cad4a-3b01-4dcb-9589-fc581cd25b13) will be used by a cac:TenderingCriterionResponse containing a "collection" of two cac:ResponseValues
           connected to the QUESTION via its identifier (i.e., the cac:TenderingCriterionResponse/cbc:ValidatedCriterionPropertyID value will be 'a71cad4a-3b01-4dcb-9589-fc581cd25b13').
       -->

       <cac:TenderingCriterion>
           <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
           <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.OTHER.EO_DATA.LOTS_TENDERED</cbc:CriterionTypeCode>
           <cbc:Name>Lots the EO tenders to</cbc:Name>
           <cbc:Description>Where applicable, indication of the lot(s) for which the economic operator wishes to tender</cbc:Description>
           <cac:TenderingCriterionPropertyGroup>
               <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
               <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                   <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a71cad4a-3b01-4dcb-9589-fc581cd25b13</cbc:ID>
                   <cbc:Description>Lot Ids</cbc:Description>
                   <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                   <!--
                       The semantisation of the identifier as "LOT_IDENTIFIER" can be used by software applications to expect a collection of identifiers of Lots,
                       i.e. several `cac:ResponseValue` linked to this QUESTION identifier (in this case to the UUID a71cad4a-3b01-4dcb-9589-fc581cd25b13).
                   -->
                   <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
               </cac:TenderingCriterionProperty>
           </cac:TenderingCriterionPropertyGroup>
           <cac:TenderingCriterionPropertyGroup>
               <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
               <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
               <cac:TenderingCriterionProperty>
                   <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">954b1d3a-46c1-4d5f-8047-fd285443c6c0</cbc:ID>
                   <cbc:Description>Is this information available electronically?</cbc:Description>
                   <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                   <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
               </cac:TenderingCriterionProperty>

               <cac:SubsidiaryTenderingCriterionPropertyGroup>
                   <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
                   <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                   <cac:TenderingCriterionProperty>
                       <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3b1af1a3-14e8-4b26-8d2e-355a8189fcf2</cbc:ID>
                       <cbc:Description>Evidence supplied</cbc:Description>
                       <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                       <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                   </cac:TenderingCriterionProperty>
               </cac:SubsidiaryTenderingCriterionPropertyGroup>
           </cac:TenderingCriterionPropertyGroup>
       </cac:TenderingCriterion>

    <!-- *4th. SET OF DATA RELATED TO LOTS: The ''true'' Selection Criterion. * -->
    <!-- List of Lots affected by one criterion GROUP of REQUIREMENT(s), i.e. the REQUIREMENT(s) related to one Register plus these particular REQUIREMENTs and QUESTIONs -->
    <!-- In this example only two Registers (REQUIREMENTs) are mentioned, the first one affects Lots 1, 2, 4 and 5. The second one affects Lots 3,6 and 7 -->
    <!-- The responses of the EO will be coherent with these REQUIREMENTs. -->

    <cac:TenderingCriterion>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6ee55a59-6adb-4c3a-b89f-e62a7ad7be7f</cbc:ID>
        <cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.SELECTION.SUITABILITY.PROFESSIONAL_REGISTER_ENROLMENT</cbc:CriterionTypeCode>
        <cbc:Name>Enrolment in a relevant professional register</cbc:Name>
        <cbc:Description>It is enrolled in relevant professional registers ...</cbc:Description>
        <cac:Legislation> ... </cac:Legislation>
        <cac:TenderingCriterionPropertyGroup>
            <cac:TenderingCriterionProperty> <Description>Lots the requirement apply to</Description><!-- ... etc. --> </cac:TenderingCriterionProperty>
            <!-- Lot1 is affected by the REQUIREMENT(s)  -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
                <cbc:Description>Lot ID</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- Lot2 is affected by the REQUIREMENT(s)  -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
                <cbc:Description>LotIDs</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- Lot4 is affected by the REQUIREMENT(s)  -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6f7c51c2-c2ac-47f2-9c7d-af9be815404a</cbc:ID>
                <cbc:Description>LotIDs</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- Lot5 is affected by the REQUIREMENT(s)  -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">69433c3f-0277-4a8d-a41e-3aeb8ac6257a</cbc:ID>
                <cbc:Description>LotIDs</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- Beginning of data about REQUIREMENT 1 (specification of the name and URL of the Register by the CA) -->
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3aacb82e-afba-440c-b64e-1834007965a2</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">624bb66e-ba57-423f-bd08-557342ed8a07</cbc:ID>
                    <cbc:Description>Register name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
                        <cbc:ExpectedDescription>THE OFFICIAL LIST OF GAS ENGINEERS</cbc:ExpectedDescription>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bd265803-ebb0-46c0-8acd-8d99c245df34</cbc:ID>
                    <cbc:Description>URL</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">URL</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeID="URI" schemeAgencyID="EU-COM-GROW">https://www.gassaferister.co.uk</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>

            <!-- QUESTIONS for REQUIREMENT 1 affecting Lots 1, 2, 4, 5 would follow -->
            <!-- ...etc. -->

        </cac:TenderingCriterionPropertyGroup>

        <cac:TenderingCriterionPropertyGroup>
            <cac:TenderingCriterionProperty> <Description>Lots the requirement apply to</Description><!-- ... etc. --> </cac:TenderingCriterionProperty>
            <!-- This will be used for Lot3 -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d01bc240-0fd2-426c-986c-123cbb7164d8</cbc:ID>
                <cbc:Description>Lot ID</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- This will be used for Lot6 -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
                <cbc:Description>LotIDs</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <!-- This will be used for Lot7 -->
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
                <cbc:Description>LotIDs</cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
                <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ExpectedID>
            </cac:TenderingCriterionProperty>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3aacb82e-afba-440c-b64e-1834007965a2</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">60c1a374-f383-450d-a4f6-484ca8a1ca58</cbc:ID>
                    <cbc:Description>Register name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
                        <cbc:ExpectedDescription>AUTOMOTIVE PROFESSIONALS</cbc:ExpectedDescription>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bd265803-ebb0-46c0-8acd-8d99c245df34</cbc:ID>
                    <cbc:Description>URL</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">URL</cbc:ValueDataTypeCode>
                    <cbc:ExpectedID schemeID="URI" schemeAgencyID="EU-COM-GROW">https://www.imiregister.co.uk</cbc:ExpectedID>
                </cac:TenderingCriterionProperty>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>

             <!-- QUESTIONs linked to REQUIREMENT 2 and Lots 3, 6 and 7 would follow -->
             <!-- ... etc. -->
        </cac:TenderingCriterionPropertyGroup>

    </cac:TenderingCriterion>

    <!-- OTHER SELECTION CRITERIA CONTAINING CA'S REQUIREMENTS AFFECTING CONCRETE LOTS WOULD FOLLOW, e.g. Risk
    indemnity insurance, Other economic or financial requirements and References. -->

    <!-- EO's responses follow -->

    <!-- *5th. SET OF DATA RELATED TO LOTS:
        Actual responses provided by the economic operator (EO) to specify that it tenders to Lot1 and Lot3.*

        The following Response below contains a ''collection'' of two values, each one identifying the Lots to which
        the Economic Operator tenders to. Notice that the `` cbc:ValidatedCriterionPropertyID` is the reference to
        the QUESTION Identifier value (UUID a71cad4a-3b01-4dcb-9589-fc581cd25b13) where the CA asks for this list of
        Lots in the ESPD-Request document (remember that the ESPD-EDM specification strongly emphasises that the
        whole criterion data structure is to be replicated also in the ESPD-Response document).
    -->

    <cac:TenderingCriterionResponse>
        <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f51c892a-9ee3-4109-a9d2-bf8a8a7458cd</cbc:ID>
        <cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">a71cad4a-3b01-4dcb-9589-fc581cd25b13</cbc:ValidatedCriterionPropertyID>
        <cac:ResponseValue>
            <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ffa35284-8812-408b-a8fb-a74024d973fd</cbc:ID>
            <cbc:ResponseID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ResponseID>
        </cac:ResponseValue>
        <cac:ResponseValue>
            <cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">817cfcff-8610-4a4b-8b71-97705e124ffd</cbc:ID>
            <cbc:ResponseID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ResponseID>
        </cac:ResponseValue>
    </cac:TenderingCriterionResponse>

    <!-- The rest of responses would 1) state whether this EO fulfills the REQUIREMENT or not (registering in the Register provided by the CA) and 2) if not, the reasons -->
    <!-- Other responses to QUESTIONs contained in other Criteria would follow below. -->

</cac:QualificationApplicationResponse>

Note for the future

Due to one strict Naming and Design Rule (NDR) in UBL, Common Basic Components (those basic data elements for which the cbc: prefix is used in UBL), cannot have multiple cardinality (of type 0..n or 1..n).

For this reason sometimes we find one REQUIREMENT that refer multiple basic elements of the same type but that, in the XML implementation needs to be broken down into multiple REQUIREMENT(s). Take for example the property labelled as "LotID" in the data structure (see figure below). This is 'one' REQUIREMENT with cardinality 1..n.

Figure 247. REQUIREMENT containing a list of elements

The fragment of XML code shows how this list of lot identifiers ends up implemented as multiple REQUIREMENTs.

    <!-- Lot1 is affected by the REQUIREMENT(s)  -->
    <cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
        <cbc:Description>Lot ID</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
        <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ExpectedID>
    </cac:TenderingCriterionProperty>
    <!-- Lot2 is affected by the REQUIREMENT(s)  -->
    <cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47d211d9-e933-4d93-b4d7-f45d46a6e83e</cbc:ID>
        <cbc:Description>LotIDs</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
        <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ExpectedID>
    </cac:TenderingCriterionProperty>
    <!-- Lot4 is affected by the REQUIREMENT(s)  -->
    <cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6f7c51c2-c2ac-47f2-9c7d-af9be815404a</cbc:ID>
        <cbc:Description>LotIDs</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
        <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot4</cbc:ExpectedID>
    </cac:TenderingCriterionProperty>
    <!-- Lot5 is affected by the REQUIREMENT(s)  -->
    <cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">69433c3f-0277-4a8d-a41e-3aeb8ac6257a</cbc:ID>
        <cbc:Description>LotIDs</cbc:Description>
        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">LOT_IDENTIFIER</cbc:ValueDataTypeCode>
        <cbc:ExpectedID schemeAgencyID="EU-COM-GROW">Lot5</cbc:ExpectedID>
    </cac:TenderingCriterionProperty>

This issue is currently being discussed in the UBL-2.3 TC and a solution will be soon provided. Once solved, the sequence of 5 properties below would be reduced to only one (of type REQUIREMENT):

IX.2 All about weights

The SELF-CONTAINED ESPD caters for two methods of evaluating criteria (the REGULATED ESP does not covers this aspect). These two methods are identified in the code list EvaluationMethodType as 1) PASSFAIL (Pass or fail), and 2) WEIGHTED (the criterion is assigned a weight).

The ''pass or fail'' method is used in open procedures and in the first stage of multi-staged procedures. In multi-staged procedures, once the list of candidates meeting the criteria have been selected, it makes sense to evaluate their tenders based on weighted selection criteria.

Hence the following general rule should be applied by software applications dealing with the ESPD-EDM:

If the procedure is open 1) no reduction of candidates is possible, and 2) criteria will not be weighted (the value of the element cbc:EvaluationMethodTypeCode is to be set to PASSFAIL);
Otherwise 1) the contracting authority should have the possibility of specifying the criteria and rules to be applied in order to limit the number of candidates, and 2) it should have the possibility of assigning a weight to any selection criterion (the value of the element cbc:EvaluationMethodTypeCode is to be set to WEIGHTED);

Information requirement check-list

Only in SELF-CONTAINED ESPD-Request and ESDP-Response documents
Only in multi-staged procedures
The need for weighting was identified only for these Selection criteria (although the data model caters for weighing any criterion):
- Abilities I (Persons)
  - Criterion #40 - Technicians or technical bodies for quality control
  - Criterion #41 - For works contracts: technicians or technical bodies to carry out the work
- Abilities II (Facilities, etc.)
  - Criterion #42 - Technical facilities and measures for ensuring quality
  - Criterion #43 - Study and research facilities
  - Criterion #44 - Supply chain management
  - Criterion #45 - Environmental management measures
  - Criterion #46 - Tools, plant or technical equipment
- Abilities III (Education)
  - Criterion #47 - Educational and professional qualifications

A complete ESPD-Response document with the examples provided in this section can be found in the file Weights-SelfContained-Request_V2.1.0.xml

Table 48. Order of occurrence of the different blocks of data related to weights
Nº	Data Element	Description	Location	Rules
1	The weighting methodology	Method that will be used to select those selection criteria that will be weighted (used for transparency purposes)	Element `cbc:WeightScoringMethodologyNote`, at the root of the Qualification Application Request document (see section III.4 Root elements, see also the UBL-2.2 Schema for the Qualification Application Request (the ESPD-Request document)	The economic operators should be informed in detail about how the selection will be performed
2	The numeric weighting type	The expression method for the weighting of the selection criteria (numeric, percentage).	Element `cbc:WeightingTypeCode`, at the root of the Qualification Application Request document	The numeric can also be used to express percentages (in the form of ''0.x''). See also the code list EvaluationMethodType
3	The criterion weight value	The concrete value assigned by the CA to the criterion for its weighting at evaluation time (e.g. 10%)	Element `cbc:WeightNumeric`, inside the `cac:TenderingCriterion` class (see section IV. Criteria, common aspects /IV.1 General behavior	None
4	The criterion evaluation method type	To inform that the criterion will be weighted (WEIGHTED vs PASSFAIL). See code list EvaluationMethodType	Element `cbc:EvaluationMethodTypeCode`, inside the `cac:TenderingCriterion` class (see section IV. Criteria, common aspects /IV.1 General behavior	The weight is used in second (or subsequent) stages of the evaluation. The first stage is always a PASSFAIL selection, even if the code WEIGHTED is assigned to this element
5	Criterion-specific evaluation approach	Explanation about how this specific criterion is weighted and will be evaluated (for transparency purposes)	Element `cbc:WeightingConsiderationDescription`, inside the `cac:TenderingCriterion` class (see section IV. Criteria, common aspects /IV.1 General behavior
6	REQUIREMENT(s) in the criterion	Criteria that are weighted carry a specific REQUIREMENT stating that ''This criterion will be weighted''	Elements `cac:TenderingCriterion` (see the figure on the data structure and the XML example,below)	BEWARE that the REQUIREMENT ''This criterion will be weighted'' is redundant with the element `cbc:EvaluationMethodTypeCode`, which may cause inconsistency. Therefore try and do not use this REQUIREMENT ''This criterion will be weighted'' and use instead the `cbc:EvaluationMethodTypeCode`. If you do not use this REQUIREMENT then you have to replace it with a CAPTION, because the cardinality constraint imposed by the UBL-2.2 requires that the first element inside a group or subgroup is a `cac:TenderingCriterionProperty` it in the XSD schema.

The figure below shows elements 1 and 2 in the UBL-2.2 XSD Schema:

Root elements related to criterion weighting

Figure 248. Elements related to the weight at the root level of the document

This other figure shows the elements inside the class Criterion:

Figure 249. Elements related to the weight inside the 'cac:TenderingCriterion' class

Mock-up - contracting authority perspective

The mock-up below illustrates how the contracting authority may specify weighted criteria.

Figure 250. Self-contained 'Abilities (I)' WEIGHTED CA REQUIREMENT edition mock-up

Notice that:

The field ''One or more criteria will be weighted'' is not stored in the data model;
The field ''Criterion weighting type'' is generic to all the criteria and is placed in the element cbc:WeightingTypeCode (element #2 in the table above);
The field ''Provide the general method used to score and evaluate the weighted criteria" is hold in the element cbc:WeightScoringMethodologyNote; and is also generic for all the weighted criteria (element #1 in the table above);
The CA has chosen ''WEIGHTED'' as the value for the combo box labeled 'Criterion evaluation method' and for the specific criterion ''For contracts: technicians or technical bodies to carry out the work'' (element #4 in the table above);
The weight assigned by the contracting authority (CA) to this criterion is 0.1. This value will be placed in the the element cbc:WeightNumeric (element #3 in the table above);
The additional information about how this specific criterion will be evaluated will be place in the element cbc:WeightingConsiderationDescription (element #5 in the table above).

Mock-up - economic operator perspective

This mock-up illustrates how all the information specified by the contracting authority (CA), concerning 1) the generic information about weights, and 2) the information specific of the criterion may be presented to the economic operator (EO):

Figure 251. Self-contained 'Abilities (I)' WEIGHTED EO mock-up

Criterion data structure

The following data structure represents the structure of one of the selection criteria that may be weighted in multi-stage procedures (''Technicians or technical bodies for quality control'').

Beware that:

The fact that the criterion will be weighted is indicated by the REQUIREMENT ''This criterion will be weighted'';
This REQUIREMENT can be replaced by a CAPTION
The purpose of this REQUIREMENT can be fulfilled using the element cbc:EvaluationMethodTypeCode

Figure 252. Weighted self-contained 'Abilities (I) - Criterion 'Technicians or technical bodies for quality control'

XML example

The fragment of XML code below illustrates how the elements related to the weighting are specified in an SELF-CONTAINED ESPD Request document.

The example presented next was extracted from the file Weights-SelfContained-Request_V2.1.0.xml

Criterion "Technicians or technical bodies for quality control" (SELF-CONTAINED and WEIHGTED)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<QualificationApplicationRequest xmlns="urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationRequest-2"
xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2"
xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" >
<!-- Some root elements remove for brevity -->
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeAgencyName="DG GROW (European Commission)" schemeVersionID="1.1">576ae724-f8e8-4b51-ae9c-2c2f4c90f433</cbc:ID>
<cbc:ContractFolderID schemeAgencyID="TeD">__ProcurementProcedureFileRefNumber</cbc:ContractFolderID>
<cbc:IssueDate>2019-01-23</cbc:IssueDate>
<cbc:ProcedureCode listID="ProcedureType" listAgencyID="EU-COM-OP" listVersionID="1.0">OPEN</cbc:ProcedureCode>
<cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">SELFCONTAINED</cbc:QualificationApplicationTypeCode>

<!--
    *DATA ELEMENTS #1 and #2!* General information about all the weighted selection criteria.
-->
<cbc:WeightScoringMethodologyNote>For weighted criteria, evaluators will allocate a score between 0 and 100 to each question reponse in accordance with the scoring guidance below:</cbc:WeightScoringMethodologyNote>(3)
<cbc:WeightScoringMethodologyNote>0 Unnaceptable</cbc:WeightScoringMethodologyNote>
<cbc:WeightScoringMethodologyNote>25 Poor</cbc:WeightScoringMethodologyNote>
<cbc:WeightScoringMethodologyNote>50 Acceptable</cbc:WeightScoringMethodologyNote>
<cbc:WeightScoringMethodologyNote>75 Good</cbc:WeightScoringMethodologyNote>
<cbc:WeightScoringMethodologyNote>100 Excellent</cbc:WeightScoringMethodologyNote>
<cbc:WeightScoringMethodologyNote>Suppliers must pass all of the pass/fail (Yes/No) questions and score a minimum of 75 overall in this section to proceed to the next stage. This will allows us to get a short list of suppliers to take through to the next stage. The final score for a criterion (or "Weighted Question Score") results from the product of the Score obtained and the weight allocated by the Contracting Authority to the criterion.</cbc:WeightScoringMethodologyNote>
<cbc:WeightingTypeCode listID="WeightingType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">PERCENTAGE</cbc:WeightingTypeCode>(2)

<!-- Data About the CA -->
<cac:ContractingParty>
    <cac:Party><!-- elements removed for brevity --></cac:Party>
</cac:ContractingParty>
<!-- Data About the Procedure -->
<cac:ProcurementProject><!-- elements removed for brevity --></cac:ProcurementProject>
<!-- Procedure divided into three Lots. Not relevant for this example about weighting. -->
<cac:ProcurementProjectLot>
    <cbc:ID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ID>
</cac:ProcurementProjectLot>
<cac:ProcurementProjectLot>
    <cbc:ID schemeAgencyID="EU-COM-GROW">Lot2</cbc:ID>
</cac:ProcurementProjectLot>
<cac:ProcurementProjectLot>
    <cbc:ID schemeAgencyID="EU-COM-GROW">Lot3</cbc:ID>
</cac:ProcurementProjectLot>
<!-- Requirements about Lots addressed to EOs. Not relevant for this example about weighting. See other examples with lots. -->
<cac:TenderingCriterion><!-- elements removed for brevity --></cac:TenderingCriterion>

<!--
        *THE REST OF THE DATA ELEMENTS RELATED TO WEIGHTING (elements #3 to #5 in the table above)
        GO INSIDE THE CRITERIA THAT ARE WEIGHTED. E.g. Selection Criteria about ''Abilities I (Persons),
        II (Facilities, etc.) and 'III (Education)': Technicians or technical bodies for quality control,
        For works contracts: technicians or technical bodies to carry out the work, Technical facilities and
        measures for ensuring quality, Study and research facilities, Supply chain management, Environmental
        management measures, Tools, plant or technical equipment, and Educational and professional qualifications.
 -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3aaca389-4a7b-406b-a4b9-080845d127e7</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CRITERION.SELECTION.TECHNICAL_PROFESSIONAL_ABILITY.TECHNICAL.TECHNICIANS_FOR_QUALITY_CONTROL</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>
<cbc:WeightNumeric>0.1</cbc:WeightNumeric>(5)
<cbc:EvaluationMethodTypeCode listID="EvaluationMethodType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">WEIGHTED</cbc:EvaluationMethodTypeCode>(4)
<cbc:WeightingConsiderationDescription>0 technicians ->   0 points</cbc:WeightingConsiderationDescription>(6)
<cbc:WeightingConsiderationDescription>1 technician ->   30 points</cbc:WeightingConsiderationDescription>(6)
<cbc:WeightingConsiderationDescription>2 technicians ->  60 points</cbc:WeightingConsiderationDescription>(6)
<cbc:WeightingConsiderationDescription>3 technicians ->  75 points</cbc:WeightingConsiderationDescription>(6)
<cbc:WeightingConsiderationDescription>4 technicians -> 100 points</cbc:WeightingConsiderationDescription>(6)
<cbc:WeightingConsiderationDescription>Minimum acceptable: 2 technicians</cbc:WeightingConsiderationDescription>(6)
<cac:Legislation>
    <cbc:Title>Public Procurement Directive 2014/24/EU</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>eu</cbc:JurisdictionLevel>
    <cbc:Article>Article 58(4)</cbc:Article>
    <cbc:URI>http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.094.01.0065.01.ENG</cbc:URI>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</cbc:ID>
    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
    <cac:TenderingCriterionProperty>
        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">2a7dcb2a-dc10-4c30-bece-66dfd0a8bc6b</cbc:ID>
        <!--
            NOTICE that this is a CAPTION, not a REQUIREMENT (as suggested in the Criteria Taxonomy). The fact that the criterion is weighted is
            already stated in the data element `cbc:EvaluationMethodTypeCode`, above. The text ''This criterion will be weighted'' could thus
            be ''calculated'' (i.e. automatically provided in the ESPD-Request, by the software application based on the value placed in the
            element `cbc:EvaluationMethodTypeCode`.
        -->
        <cbc:Description>This criterion will be weighted</cbc:Description>(1)
        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
        <!-- The type of value provided by the CA is `NONE`, as this is a CAPTION, not a REQUIREMENT. -->
        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
    </cac:TenderingCriterionProperty>

    <!-- THE REST OF THE CRITERION DOES NOT REFER ANYMORE TO ANY DATA ELEMENT RELATED TO ITS WEIGHTING. -->

    <cac:SubsidiaryTenderingCriterionPropertyGroup>
        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f156d97a-9700-4ad9-8d21-e3ac57102278</cbc:ID>
        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
        <cac:TenderingCriterionProperty>
            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">d1936fa0-4a8a-4016-8349-9e389c80fff4</cbc:ID>
            <cbc:Description>Requirement</cbc:Description>
            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">REQUIREMENT</cbc:TypeCode>
            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
            <cbc:ExpectedDescription>__TechniciansRequirement</cbc:ExpectedDescription>
        </cac:TenderingCriterionProperty>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">609cc954-64be-4b4f-800a-f17589deb936</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">5b878bbe-b575-43e4-a40c-6bf3ede91641</cbc:ID>
                <cbc:Description> </cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">acf762a6-0087-4ad3-9f95-a8b624be81b0</cbc:ID>
                    <cbc:Description>First name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">3b4b838b-1c41-42a3-a21b-a1cac72d2971</cbc:ID>
                    <cbc:Description>Last name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">95912db9-df33-44b1-97fd-63f5e0202d84</cbc:ID>
                    <cbc:Description>Profession</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9ddd05be-6194-4ad8-9f68-7ac549dff64e</cbc:ID>
                    <cbc:Description>Experience</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f4351f24-d1f7-4039-893c-e2947ba3afac</cbc:ID>
                    <cbc:Description>Other information</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">7a348140-4d0c-421b-8142-2053835272a3</cbc:ID>
                    <cbc:Description>How long with  EO</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0de6079a-3f13-4391-a8a6-1b4b350f8b2f</cbc:ID>
                        <cbc:Description>Is this information available online?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c4d4dec1-ea76-4d1c-bcf2-2d4f265982fb</cbc:ID>
                            <cbc:Description>Evidence supplied</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
        <cac:SubsidiaryTenderingCriterionPropertyGroup>
            <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">45a67f48-d146-4faf-8239-dd6977dffe29</cbc:ID>
            <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
            <cac:TenderingCriterionProperty>
                <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">c1806c05-3589-4af4-9bea-7061b30e3f4f</cbc:ID>
                <cbc:Description> </cbc:Description>
                <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">CAPTION</cbc:TypeCode>
                <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">NONE</cbc:ValueDataTypeCode>
            </cac:TenderingCriterionProperty>
            <cac:SubsidiaryTenderingCriterionPropertyGroup>
                <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">52ffcf91-3598-438f-8c3d-faf97da02602</cbc:ID>
                <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">1d07b02b-cfce-4143-8743-79943b6265a0</cbc:ID>
                    <cbc:Description>Name</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">ef2281fc-3505-4d3b-9fbc-e7655e534b28</cbc:ID>
                    <cbc:Description>Experience area</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:TenderingCriterionProperty>
                    <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9e8f3516-50fa-45d3-83cd-fa005705d4fa</cbc:ID>
                    <cbc:Description>Other information</cbc:Description>
                    <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                    <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">DESCRIPTION</cbc:ValueDataTypeCode>
                </cac:TenderingCriterionProperty>
                <cac:SubsidiaryTenderingCriterionPropertyGroup>
                    <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
                    <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ON*</cbc:PropertyGroupTypeCode>
                    <cac:TenderingCriterionProperty>
                        <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">89ae7f89-e17c-492c-a529-d137d7a5e22d</cbc:ID>
                        <cbc:Description>Is this information available online?</cbc:Description>
                        <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                        <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">INDICATOR</cbc:ValueDataTypeCode>
                    </cac:TenderingCriterionProperty>
                    <cac:SubsidiaryTenderingCriterionPropertyGroup>
                        <cbc:ID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">0a166f0a-0c5f-42b0-81e9-0fc9fa598a48</cbc:ID>
                        <cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">ONTRUE</cbc:PropertyGroupTypeCode>
                        <cac:TenderingCriterionProperty>
                            <cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.1.0">f977a875-2889-4415-920f-256c1c1a06ed</cbc:ID>
                            <cbc:Description>Evidence supplied</cbc:Description>
                            <cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">QUESTION</cbc:TypeCode>
                            <cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.1.0">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
                        </cac:TenderingCriterionProperty>
                    </cac:SubsidiaryTenderingCriterionPropertyGroup>
                </cac:SubsidiaryTenderingCriterionPropertyGroup>
            </cac:SubsidiaryTenderingCriterionPropertyGroup>
        </cac:SubsidiaryTenderingCriterionPropertyGroup>
    </cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
</QualificationApplicationRequest>

1	The contracting authority has selected that this criterion will be weighted.
2	Method that will be used to select those selection criteria that will be weighted (used for transparency purposes).
3	The expression method for the weighting of the selection criteria (numeric, percentage).
4	To inform that the criterion will be weighted (WEIGHTED vs PASSFAIL). See code list. EvaluationMethodType.
5	The concrete value assigned by the CA to the criterion for its weighting at second-stage evaluation time.
6	Explanation about how this specific criterion is weighted and will be evaluated (for transparency purposes).

IX.3 All about UUIDs

In the Regulated and Self-contained ESPD-EDM Criteria Taxonomies every element of the criterion data structures has an UUID assigned, except for the CAPTIONs, REQUIREMENT(s) and QUESTION(s).

This UUID is necessary to identify unambiguously a particular "data structure" (or "data shape"). One data structure identified with a unique identifier has always the same elements and in the same order. This allows the reuse of the same structure multiple times in the same criterion or in different criteria. These UUIDs map the ones maintained in e-Certis for each criterion.

Examples of data structure reuse

Example 1: There is a data structure that is reused by practically all the criteria, the one asking whether the information is available electronically. You will notice that all criteria where it is used the UUIDs of the groups and subgroups are identical, but also the cardinalities, the PropertyDataType and the Element Code.
Example 2: If you look into the "Convictions" data structures you will notice a data structure (a QUESTION_SUBGROUP) identified with the UUID "f4978772-3126-4ded-bc30-f50da8c3a038". This subgroup contains one QUESTION ("Have you taken measures to demonstrate your reliability (Self-Cleaning)?" and a sub-group with another QUESTION ("Please describe them"). If you search into the spread-sheet book you will observe that this very structure is also reused by other criteria (e.g. CRITERION.EXCLUSION.SOCIAL.*, CRITERION.EXCLUSION.MISCONDUCT.\*, etc.), but the UUID of the main subgroup is different in all those cases from the one used for Convictions. This is because the Element Code in the case of Convictions (and for this subgroup) is "ONTRUE" whilst in the rest of criteria it is "ON*".

As mentioned above, CAPTIONs, REQUIREMENT(s) and QUESTION(s) cannot have a reusable UUID pre-allocated. The reason for this is that each response by the economic operator (in the ESPD Response document) MUST refer to one, and only one, QUESTION of the ESPD Request. See other details on criterion properties in sections IV.4 Properties and VIII.7 Answering QUESTION(s).

Implementation challenge

The fact that Criterion Properties are to be generated dynamically may pose a challenge to developers in certain situations. One of these situations could be when the QUESTIONs are repositoried and answered in a Pre-Qualification System (PQS) that is used to pre-fill ESPD-Responses to ESPD-Request instances that are kept in another system unknown to the PQS (e.g. a Service Provider acting on behalf of one or more Contracting Authorities).

One possible solution may be based on the fact that each REQUIREMENT and QUESTION occurs always in the same position inside a group or a sub-group. If the order of the REQUIREMENTs and QUESTIONs is altered the Schematron-based validation would trigger a fatal exception.

The proposal consists in identifying each REQUIREMENT and QUESTION by concatenating the UUIDs of the CRITERION and the "parent" groups and sub-groups, as described in the Criteria Taxonomy spread-sheets, produce a short hash of the concatenated string and add to it the position of the element in the group or subgroup. This casts a constant UUID for each REQUIREMENT and QUESTION that would be known by any stakeholder, thus enabling the decoupling of systems producing ESPD-Requests and systems keeping particular QUESTIONS and RESPONSES.

Let’s take one REGULATED criterion as an example to illustrate this proposal (this works also for SELF-CONTAINED ESPD criteria):

Example: Convictions Criterion

User Story

I, as a PQS, need to provide the information about an EO’s convictions, so the EO can produce a pre-filled ESPD-Response.

Algorithm

The algorithm to generate the first subgroup of QUESTIONs (in convictions) would be:

Question_UUID = "" ;
Question_UUID += Criterion_UUID + "." ;
Question_UUID += Group_UUID + "." ;
Question_UUID += Subgroup_UUID + "." ;
Question_UUID = hash_md5(Question_UUID) ;
Question_UUID += Question_UUID + "." + Group_Position() + "." + Subgroup_Position() + "." + Question_Position() ;

Apply repeatedly this algorithm to the subsequent sub-subgroups.

The objective of hashing the concatenation of UUIDs is to produce a non-too-verbose UUID for the QUESTION.

This algorithm produces a unique digital print per each data element of the data shape. If this hash were added to an IRI, the data element could be described in a very specific namespace and its de-referencing could provide back a machine-readable description of the element (name, description, examples, etc.).

Data Structure

The figure below would represent how the criterion "Participation in a criminal organisation would look like in the Criteria Taxonomy if you applied the algorithm above:

Figure 253. A way of generating UUIDs that is agnostic of the ESPD-Request XML instance.

Annex I: XML Validation

Introduction to ISO Schematron

Schematron is a rule-based validation language to specify validation processes against XML documents. ISO Schematron is an ISO (ISO/IEC 19757-3:2006) and open standard. Please visit the ISO Schematron web-site for the technical specification and details.

ESPD Business Rules

The ESPD-EDM uses Schematron to validate business rules identified in ESPD_TestCases_v10.docx and ESPD_TestCases_mapping_v10.docx documents. The business requirements taken as input for these rules are specified in the ESPDint Business Document.

These business rules can be typified as:

Semantic validations: e.g. The "cac:TenderingCriterionResponse" in a Response document MUST match one, and only one, of the "cac:TenderingCriterionProperty" elements in the XML instance of the corresponding ESPD-Request;
Assertions about the presence or absence of patterns in XML documents: e.g. all business rules that apply to identifier nodes: mandatory attributes, structure of the identifier, etc.;
Code lists validations: e.g. values and attributes for each code list element;
Other validations that an XSD cannot do: e.g. Validates that one of the nodes has at least 1 child.

The following image shows different examples of validations:

The validation of code lists is explained in sections below.

Schematron Architecture

ISO Schematron executes the validations in two stages:

Design and implementation of the SCH files. SCH stands for Schematron Schema and contains the set of rules to be validated within the XML document.
Execution of the implemented validations in the SCH files:
1. Transformation of SCH files into XSLT files in order to be able to execute the validations against the XML.
2. Execution of the validations using the XSLT files to get the final report.

Architecture for non-code list validation

What does the SCH file contain?

Set of rules specifying the context (the element(s) and/or attribute(s) which the assertions affect);
Each rule have a set of assertions with the tests that must be evaluated in the context.

Execution

As a basis of the implementation, it has been taken into account:

Schematron "skeleton" implementation in XSLT.

This example describes the execution of the validation process using the Saxon library to execute XSLT files and the XSLT provided as a basis:

Code list validation Architecture

Business rules related to code list validates:

Architecture for Code List validation

The validation of the code lists needs an extra step on the process before executing the Schematron process. This is because it needs Genericode (GC) as input files.

The first step is the generation of Genericode (GC) files. These files contains information about the values and identifiers of each code list.
1. GC files are found in the Validation folder.
Design and implementation of the CVA files. CVA stands for Context and Value Association:
Execution of the implemented validations in the CVA files:
1. Transformation of CVA files into SCH files.
2. Continue with the Schematron execution process: (1) transformation of SCH files into XSLT and execution of the validations using the XSLT files to get the final report.

What does the SCH file contain?

Association between one or more elements of the XML and one or more code list (specified in the Genericodes).
The declaration of which attributes of the XML identify information of the Genericode.

The implementation of the CVA file has the following structure:

Execution

As a basis of the implementation, it has been taken into account:

Schematron implementation of CVA files for validation from CRANE SOFTWRIGHTS LTD

This example describes the execution of the validation process using the Saxon library to execute XSLT files and the XSLT provided as a basis:

Execution of the validation process in code lists

ESPD Validation Architecture

The validation of a ESPD XML has the following life-cycle:

The validation of the XML starts by ensuring that the input XML follows the structure defined by the XSD: QualificationApplicationRequest.xsd XSD Schema or QualificationApplicationResponse.xsd XSD Schema. These schemas can be found under the folder dist/xsdrt/maindoc (or the equivalent documented xsd folder).
1. If the validation of the structure is not successful, the process stops and sends the report with the list of errors.
2. If the validation of the structure is successful, the process continues with the code list validations and business rules. All errors found (if any) are listed in the report.
Depending on the type of application (ESPD Request or ESPD Response), and independently of the qualification application type code (either regulated or self-contained), different types of validations are executed:

ESPD Request (Regulated or Self-contained)

XSD Validation against UBL-QualificationApplicationRequest-2.2-Pre-award.xsd
Code list validations. These are common for both, Request and Response:
1. Validation of the code list values: 01 ESPD-codelist-values.cva
2. Validation of the identification of the code list: 01 ESPD Common CL Attributes.sch
Business rules related to the cardinality of the schema, that cannot be controlled using the XSD: 02 ESPD Req Cardinality BR.sch
Business rules used to validate the criteria taxonomy:
1. Validations common for Request and Response: 03 ESPD Common Criterion BR.sch
2. Validations specific for Request applications: 03 ESPD Req Criterion BR.sch
Other business rules:
1. Other validations which are common to Request and Response applications, such as the mandatory use of the attribute schemeAgencyID for identifiers: 04 ESPD Common Other BR.sch
2. Specific business rules for Request applications, in this case, the validation of the correct value for cbc:CutomisationID element: 04 ESPD Req Other BR.sch
3. Business rules related to the procurer: 05 ESPD Req Procurer BR.sch
4. Specific business rules for Self-contained application type: 05 ESPD Req Self-contained BR.sch

ESPD Response

XSD Validation against UBL-QualificationApplicationResponse-2.2-Pre-award.xsd
Code list validations. These are common for both, Request and Response:
1. Validation of the code list values: 01 ESPD-codelist-values.cva
2. Validation of the identification of the code list: 01 ESPD Common CL Attributes.sch
Business rules related to the cardinality of the schema, that cannot be controlled using the XSD: 02 ESPD Resp Cardinality BR.sch.sch
Business rules used to validate the criteria taxonomy:
1. Validations common for Request and Response: 03 ESPD Common Criterion BR.sch
2. Validations specific for Response applications: 03 ESPD Resp Criterion BR.sch
Other business rules:
1. Other validations which are common to Request and Response applications, such as the mandatory use of the attribute schemeAgencyID for identifiers: 04 ESPD Common Other BR.sch
2. Specific business rules for Response applications, in this case, the validation of the correct value for cbc:CutomisationID element: 04 ESPD Resp Other BR.sch
3. Business rules related to the economic operator: 05 ESPD Resp EO BR.sch
4. Specific business rules for Self-contained application type: 05 ESPD Resp Self-contained BR.sch
5. Specific business rules for economic operators registered in a pre-qualification system: 05 ESPD Resp Qualification BR.sch
6. Specific business rules depending on the role: 05 ESPD Resp Role BR.sch

UUID Criterion Validation

Each Criterion is defined in e-Certis and must use the Universally Unique Identifier (UUID) supplied by e-Certis:

These UUIDs are 'constant', meaning that they are maintained by DG GROW and need to be used compulsory as they were issued by DG GROW.
The value of each UUID are defined in the spreadsheets:
1. Criteria Taxonomy (Regulated ESPD)
2. https://github.com/ESPD/ESPD-EDM/blob/2.1.0/docs/src/main/asciidoc/dist/cl/xlsx/ESPD-CriteriaTaxonomy-SELFCONTAINED-V2.1.0.xlsx(Self-contained ESPD)]

ESPD validates that the UUID defined in the ESPDRequest XML or ESPDResponse XML are the ones supplied by e-Certis:

Spreadsheet row

XSD Path

{CRITERION

cac:TenderingCriterion/cbc:ID

{QUESTION_GROUP

cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup/cbc:ID

{QUESTION_SUBGROUP

cac:SubsidiaryTenderingCriterionPropertyGroup/cbc:ID

Every QUESTION_GROUP and QUESTION_SUBGROUP that has the same structure (meaning, QUESTION or QUESTION_SUBGROUP), share the same UUID, as they are the same.

Tendering Criterion

The validation of each criterion (cac:TenderingCriterion element) has the aim to check:

cbc:ID, cbc:CriterionTypeCode, cbc:Name and cbc:Description are mandatory;
cbc:ID and cbc:CriterionTypeCode values match with the ones supplied by e-Certis;
cac:TenderingCriterionPropertyGroup structure matches with the QUESTION_GROUP supplied by e-Certis (see Tendering Criterion Property Group and Subgroup section).

Tendering Criterion Property Group and Subgroup

The same validations are executed for the first level group of properties and sub-groups of properties. The rules applied are:

The cbc:ID and cbc:PropertyGroupTypeCode are mandatory elements and their values are the ones supplied by e-Certis in the corresponding cbc:TenderingCriterion;
cac:TenderingCriterionProperty structure matches with QUESTION supplied by e-Certis (see Tendering Crtierion Property section);
cac:SubsidiaryTenderingCriterionPropertyGroup matches with QUESTION_SUBGROUP supplied by e-Certis (for each property group, the same validations are applied).

Tendering Criterion Property

The validation of Tendering Criterion Property (cac:TenderingCriterionProperty element) is checked as follows:

cbc:TypeCode and cbc:ValueDataTypeCode are mandatory elements and match with the ones supplied by e-Certis;
cbc:ID and cbc:Description elements are mandatory, although their values are not validated;
If cbc:TypeCode value is "CAPTION" or "REQUIREMENT", cbc:ValueDataTypeCode value must be "NONE".

Interoperability testbed

The European Commission (EC) ISA2 Programme provides an Interoperability Testbed where Stakeholders can freely test these validation artefacts.

All the ESPD-EDM artefacts necessary to perform the validation are set up in the testbed. Thus developers and integrators can test the validity of the ESPD-Request and ESDP-Response XML instances by uploading the instances in the testbed and launching the validation.

Use this URL to upload and execute the validations: https://www.itb.ec.europa.eu/espd/upload

Annex II Code lists used in ESPD

Beware that in the ESPDD documents codes can be used in different places, e.g.:

Outside the criteria, in UBL components of type "Code Type" (e.g. cbc:ProcedureCode);
Inside the definition of a Criterion, in the ESPD Request, for the element Expected Code (cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup/cac:TenderingCriterionProperty/cbc:ExpectedCode, it is in this element that the ESPD Request defines which code list to use); and
Inside the Response Value (cac:TenderingCriterionResponse/cac:ResponseValue/cbc:ResponseCode), where the Economic Operator has to supply a valid code picked from the list specified in the ESPD Request, in the element cbc:ExpectedCode.

All this is explained and illustrated with XML examples all along this document. See for instance:

The XML example in section III.4 Root elements (use of cbc:ProcedureCode);
The XML example in section III.11 Lots - Self-contained ESPD (use of cbc:ExpectedCode); and
The XML example in section VIII.7 Answering QUESTION(s) (where the use of codes, identifiers, etc. in the responses is explained).

Additional information about the code lists can be found in:

The spread-sheet distributed with this documentation;
The multilingual Genericode *.gc files automatically produced based on these spread-sheets; and
The ESPDint BIS Document;

The table below lists the code lists used in the ESPD documents and where they are used.

Code List Issuer Agency Used In

BidType

Publications Office of the EU

See Data structure and XML examples for Criterion CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION of the SELF-CONTAINED ESPD Request

ConfidentialityLevel

DG GROW (European Commission)

See element 'cac:Evidence/cbc:ConfidentialityLevelCode` of the UBL-2.2 XSD Schemas for QualificationApplicationResponse

CountryCodeIdentifier

ISO

See element 'cac:PostalAddress/cac:Country/cbc:IdentificationCode` of the UBL-2.2 XSD Schemas, e.g. the postal address of an economic operator party)

CriteriaType

DG GROW (European Commission, defined in e-Certis)

See each Criterion taxonomy code in the Criteria Taxonomies (both REGULATED and SELF-CONTAINED). See also the Genericode file.

CriterionElementType

DG GROW (European Commission)

See element cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup/cac:TenderingCriterionProperty/cbc:TypeCode of the UBL-2.2 XSD QualificationApplicationRequest Schema

CurrencyCode

Publications Office of the EU

All UBL-2.2 elements of type cbc:Amount in its attribute @currencyID

DocRefContentType

DG GROW (European Commission)

UBL-2.2 element cac:AdditionalDocumentReference/cbc:DocumentTypeCode. See XML example in section III.5 EU and national publications

EOIDType

DG GROW (European Commission)

Attribute cac:PartyIdentification/cbc:ID@SchemeID. See 'Requirement" boxes in section VIII.6 Economic Operator

EOIndustryClassificationCode

DG GROW (European Commission)

Used in the UBL-2.2 element cac:EconomicOperatorParty/cac:QualifyingParty/cbc:IndustryClassificationCode` to specify the size of the economic operator. See example in XML Example (REGULATED economic operator)

EORoleType

DG GROW (European Commission)

Element cac:EconomicOperatorRole/cbc:RoleCode. See example in XML Example (REGULATED economic operator)

EvaluationMethodType

DG GROW (European Commission)

Element cbc:EvaluationMethodTypeCode located at the root of both the UBL-2.2 QualificationApplicationRequest (ESPD Request) and QualificationApplicationResponse (ESPD Response). See XML example in section IX.2 All about weights

FinancialRatioType

BACH Banque de France

Used in the REQUIREMENT "Ratio Type" of the Criterion CRITERION.SELECTION.ECONOMIC_FINANCIAL_STANDING.FINANCIAL_RATIO . See data structure for this criterion in the SELF-CONTAINED ESPD Request spread-sheet.

LanguageCodeEU

DG GROW (European Commission)

e.g. in cac:Legislation/cac:Language/cbc:LocaleCode. See for instance XML example in section V.7 Early termination

LegislationType

DG GROW (European Commission)

It is used as a basis to supply a value for the element cac:Legislation/cbc:JurisdictionLevel, which is not a code but a free-text. See the XML example in the section V.1 Convictions

ProcedureType

DG GROW (European Commission)

Element cbc:ProcedureCode used at the root of the UBL-2.2 QualificationApplicationRequest XSD document. See XML example in section III.4 Root elements

ProfileExecutionID

DG GROW (European Commission)

Element cbc:ProfileExecutionID used at the root of the UBL-2.2 QualificationApplicationRequest and QualificationApplicationResponse documents. See table of expected elements in section III.4 Root elements

ProjectType

DG GROW (European Commission)

Element cac:ProcurementProject/cbc:ProcurementTypeCode. See XML example in section III.9 Procurement Procedure: Self-contained ESPD

PropertyGroupType

DG GROW (European Commission)

Element cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup/cbc:PropertyGroupTypeCode. See XML example in section III.11 Lots - Self-contained ESPD, for example

QualificationApplicationType

DG GROW (European Commission)

Element cbc:QualificationApplicationTypeCode at the root of UBL-2.2 QualificationApplicationRequest and QualificationApplicationResponse documents. See XML example in section III.4 Root elements

ResponseDataType

DG GROW (European Commission)

Element cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup/cac:TenderingCriterionProperty/cbc:ValueDataTypeCode. See XML example in section III.11 Lots - Self-contained ESPD, for example

ServicesProjectSubType

Publications Office of the EU

Element cac:ProcurementProject/cbc:ProcurementSubtypeCode. See explanations in section III.9 Procurement Procedure: Self-contained ESPD, subsection XSD Schema.

WeightingType

DG GROW (European Commission)

Element cbc:WeightingTypeCode at the root of UBL-2.2 QualificationApplicationRequest and QualificationApplicationResponse documents. See XML example in section III.4 Root elements

1. CVA files are used for the validation of Codes and Identifiers. See the OASIS Genericode 1.0 specification and CRANE SOFTWRIGHTS site for more details

2. We call this the ''semantisation'' of basic elements to refer to data elements that have been specifically named to reflect a possible use of the element by an agent, e.g. boolean indicators named RADIO_BUTTON_TRUE, RADIO_BUTTON_TRUE, etc. or identifier names like LOT_IDENTIFIER or ECONOMIC_OPERATOR_IDENTIFIER

3. the ISA2 Programme provides this draft definition for eBusiness Document: "a set of interrelated Business Information representing the business facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual forms that the capability exchanges with other capabilities to support the execution of value streams". For the purposes of the ESPD, the content of eBusiness Document is always data structures according to the ESPD-Exchange Data Model (EDM) specification.

4. Received eBusiness Document should be preserved as it was sent, unaltered, before applying any enrichment, otherwise the evidence value would be lost.

5. http://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32009D0316

6. Add the '.zip' extension the 'ods' file and unzip it to get the content.xml file

7. See Article 65 of the Directive 2014/24/EU

8. CVA files are used for the validation of Codes and Identifiers. See the OASIS Genericode 1.0 specification and CRANE SOFTWRIGHTS site for more details

9. *Remember that the ESPD-EDM specification uses the definition of SME provided by the EU Recommendation 2003/361

10. The Annex 2 of the Commission Implementing Regulation (EU) No 2016/7 refers to these two as Part IV and Part V

11. The Commission is preparing for an evaluation and possible revision of some aspects of the SME Definition. A public consultation on the topic will be launched soon.

12. This is part of the schema envisioned in the Once Only Principle

The European Single Procurement Document

XML Implementation Guide v2.1.0

I. Introduction

I.1 Objectives and scope

I.1.1 The Directive

I.1.2 Contracts above the threshold and below the threshold

I.2 ESPD conformant solutions

I.3 The ESPD Profile

I.4 Regulated and Self-contained ESPDs

Mock-up

II. The ESPD Semantic Assets

II.1 ESPD Distribution package

II.2 Adoption of UBL-2.2

II.3 UBL-2.2 Documents and libraries

II.4 Codes and Identifiers

Codes and code lists

Compulsory attributes

XML Example

Code list that IS NOT used for CODE values

III. The ESPD Request document

III.1 ESPD Request Business Requirements

III.2 ESPD Request XSD Schema

III.3 ESPD Request cardinalities

III.4 Root elements

XML example

III.5 EU and national publications

Mock-up

XSD Schema

Expected elements

XML Example

III.6 Contracting Body

Related information requirements

Mock-up

XSD Schema

Expected elements

XML example

III.7 Service Provider

XSD Schema

Expected elements

XML example

III.8 Procurement Procedure: Regulated ESPD

Mock-up

XSD Schema

Expected elements

XML example

III.9 Procurement Procedure: Self-contained ESPD

Mock-up

XSD Schema

Expected elements

XML example

III.10 Lots - Regulated ESPD

XSD Schema

Expected elements

XML Example

III.11 Lots - Self-contained ESPD

Mock-up

XSD Schema

Expected elements

XML Example

Expected elements

XML Example

IV. Criteria, common aspects

IV.1 General behavior

XSD Schema

Expected elements

XML Examples

IV.2 Legislation

Expected elements

XML Examples

XML Example

IV.3 Groups of properties

Expected elements

XML Examples

IV.4 Properties

Expected elements

XML Examples

IV.5 Mock-ups

IV.6 Data Structures

IV.7 XML examples and tools

IV.8 GUI control elements