VII. The ESPD Response document
VII.1 Business requirements specification
The ESPD-EDM V2.0.2 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.
VII.2 ESPD Request XSD Schema
For the ESPD Response, the ESPD-EDM V2.0.2 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 |

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

VII.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.0.2 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.

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
andcac: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.0.2 distribution package provides Schematron schemata and CVA files [1] 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.
VII.4 Root elements
The table below lists the elements that are expected in the ESPD Response V2.0.2 and provides details on the cardinalities and usage of those elements.
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 |
1 |
Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance. |
Information Requirement: tbr92-020. Rule: Use the value "2.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: tbr92-019. Rule: For the ESPD we use the value “urn:www.cenbii.eu:transaction:biitrdm092:ver3.0”. Compulsory use of the value "CEN-BII" for the schemeAgencyID attribute. Rule scope: Common (BR-OTH-02, BR-OTH-06) |
cbc:ProfileID |
Identifier |
0..1 |
An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. The identification may include the version of the specification as well as any customizations applied. |
Information Requirement: tbr92-019. Rule: Use the value "41". Use also "CEN-BII" for the scheme AgencyID attribute. Rule scope: Common (BR-OTH-07, BR-OTH-02) |
cbc: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). The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process. |
Information Requirement: tbr92-019. Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document. Rule scope: Common (BR-OTH-02) |
cbc:CopyIndicator |
Indicator |
0..1 |
Indicates whether this document is a copy (true) or not (false). |
Information Requirement: tbr92-019. Rule: It is a good practice to use the CopyIndicator component if the same document is forwarded several times to the same or to different destinations. Use it in combination with the UUID identifier: copies of an ESPD document should be identified with distinct UUIDs. |
cbc:UUID |
Identifier |
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.0#BIS41-ESPDV2.0-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 |
1 |
An identifier that is specified by the buyer and used as a reference number for all documents in the procurement process. It is also known as procurement project identifier, procurement reference number or contract folder identifier. A reference to the procurement procedure to which a Qualification request document and the delivered response documents are associated. |
Information Requirement: tbr92-013. Rule: Try always to use the reference number issued by the 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-20), SELF-CONTAINED (BR-SC-30) |
cbc:IssueDate |
Date |
1 |
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: Rule scope: SELF-CONTAINED (BR-OTH-01, BR-OTH-01#1, BR-OTH-03) |
cbc:QualificationApplicationTypeCode |
Code |
1 |
The type of European Single Procurement Document (ESPD). |
Information Requirement: tbr92-019. Rule: Compulsory use of the codelist QualificationApplicationType (values 'REGULATED`, 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 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: tbr92-011. 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: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 |
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 |
A tendering criterion describes a rule or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidates to the award decision. |
Information Requirement: tbr92-015,tbr92-016. Rule: (see examples further below in this document) |
cac:TenderingCriterionResponse |
Associated class |
1..n |
Response of the economic operator to the requirements and questions issued by the 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):

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.0.2.xml or SELFCONTAINED-ESPDResponse-2.0.2.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.0.2" 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.0.2 is entirely based on OASIS UBL-2.2 -->
<cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
<!-- How ESPD-EDM-V2.0.2 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.0.2 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.0.2">OPEN</cbc:ProcedureCode>
<!-- The type of the ESPD (REGULATED or SELFCONTAINED) -->
<cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">SELFCONTAINED</cbc:QualificationApplicationTypeCode>
<!-- ... rest of document removed for brevity -->
xml
VII.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 |
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.

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
:

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
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 |
1 |
The identifier for the referenced document, generally issued by the entity responsible for the document. |
Information Requirement: tbr92-013. Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:ID. Rule scope: Common (BR-OTH-02) |
cbc:UUID |
Identifier |
1 |
A universally unique identifier that can be used to reference this ESPD document instance. |
Information Requirement: tbr92-013. Rule: Use the same value that was used in the cac:QualificationApplicationRequest/cbc:UUID. Rule scope: SELF-CONTAINED (BR-OTH-02) |
cbc:DocumentTypeCode |
Code |
1 |
The type of document being referenced, expressed as a code. |
Information Requirement: tbr92-013. Rule: For the ESDP-EDM it is compulsory use of the value 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:
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. |
VII.6 Economic Operator
Related information requirements
See formal requirements related to the economic operators in the e-Sens site: (tbr092-001, _tbr092-008).
REQUIREMENT |
One ESPD Response per economic operator. The ESPD-EDM-2.0.2, 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. |
REQUIREMENT |
For the identification of the economic operators the UBL-2.2 element |
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.0.2 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.
**s 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.
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.0.2 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.0.2 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.0.2, 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.0.2 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.
cac:EconomicOperatorParty
The UBL-2.2 cac:EconomicOperatorParty
has three common aggregate components, the XSD Schema looks like this:

-
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.0.2 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.0.2 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) [2]; 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
.

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

cac:Party
The XSD diagram below shows (in blue) the elements for which data are expected in the ESPD Response for the cac:Party element of the economic operator.

The figures below show the cac:QualifyingParty
sub-components cac:BusinessClassificationScheme`and `FinancialCapability
, and cac:CompletedTask
in a bit more of detail. At present, the ESPD-EDM only uses one field, cbc:Description
for the references and classifications and `cbc:Amount`for the Turnover.



UBL-2.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.

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 |
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 |
1 |
The distinctive features or characteristics qualifying an economic operator to be a party in a tendering process (e.g., number of employees, number of operating units, type of business, technical and financial capabilities, completed projects). |
Information Requirement: tbr92-001 Rule: This element is compulsory in the ESPD-EDM V2.0.2 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 |
1 |
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.0.2 because depending on it different sets of data will be required or not, shown or hidden, processed or skipped. |
cac:Party |
Associated class |
1 |
Main set of data used to identify and contact the economic operator, such as official identifiers, name, address, contact person, representatives, etc. |
Information Requirement: Rule: (See expected elements and rules below in the table about this Party). |
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 Rule scope: SELF-CONTAINED ( BR-RESP-80-S10, BR-RESP-80-S20), Common (BR-RESP-50, BR-OTH-02) |
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 |
1 |
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) |
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 |
1 |
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 Rule scope: Common (BR-OTH-02) |
cbc:EndPointID |
Identifier |
0..1 |
Electronic address of the contracting body. |
Information Requirement: tbr92-001. Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the Rule scope: Common (BR-RESP-10-08) |
cac:PartyName/cbc:Name |
Text |
1 |
The name of the economic operator. |
Information Requirement: tbr92-001. Rule: Use the official name of the Party as officially registered. Be accurate in its spelling. |
cbc:IndustryClassificationCode |
Code |
1 |
Used to indicate whether the company is a micro, small, medium or large enterprise. |
Information Requirement: tbr92-004. Rule: Used only for statistical purposes. Compulsory use of 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. |
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 |
1 |
A code that identifies the country. |
Information Requirement: tbr92-012. Rule: The country of the contracting body must always be specified. Compulsory use of the Code List 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. |
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. |
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 |
cbc:EndpointID |
Identifier |
0..1 |
Electronic address of the service provider. |
Information Requirement: tbr070-021. Rule: Use it for online services (e.g. Web Services, REST services, Delivery ID, ftp, etc. For the official web site of the Party use always the Rule scope: Common (BR-RESP-10-08) |
cac:PartyIdentification/cbc:ID |
Identifier |
1 |
The national identifier of a service provider as it is legally registered (e.g. VAT identification). |
Information Requirement: tbr070-021. Rule: An identifier for the service provider must always be provided. Compulsory use of the attribute Rule scope: Common (BR-RESP-10-11, BR-OTH-02) |
cac:PartyName/cbc:Name |
Text |
1 |
The name of the service provider. |
Information Requirement: tbr070-021. Rule: The name of the service provider must always be specified. Supply the official registered name of the service provider. Rule scope: Common (BR-RESP-10-09) |
cac:PostalAddress/cac:Country/cbc:IdentificationCode |
Identifier |
1 |
The code that identifies the country of the service provider. |
Information Requirement: tbr070-021. Rule: The country of the service provider must always be specified. Compulsory use of the Code List CountryCodeIdentifier (ISO 3166-1 2A:2006). Rule scope: SELF-CONTAINED (BR-RESP-10-10, BR-OTH-01, BR-OTH-01#5, BR-OTH-03) |
VII.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:

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:

Data structure for a sheltered workshop or social business in case of reserved procurement:

Mockup (3/8): Registration on an official list, tenderer register or (pre)qualification system:

Data structure for the (pre)qualification of the economic operator by an official list or similar:

Mock-up (4/8): Role and other members of the group:

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

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

This fragment of XML does not include the responses to the QUESTIONs 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.0.2.xml.
<!-- 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.0.2">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.0.2">2043338f-a38a-490b-b3ec-2607cb25a017</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">6febbe4a-e715-427c-a2b1-19cfabadaef0</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">97402ce3-b321-469e-9fa2-d3c3e3e09ca9</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a5e33369-e2b5-45f7-9969-ddb1c3ae17c8</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERCENTAGE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.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:TenderingCriterion>
<!-- Criterion:EO registered in a PQS -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">64162276-7014-408f-a9af-080426bfe1fd</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">3f5959b0-6367-4f0e-96c2-a44635bbf84e</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 schemeID="CriteriaTaxonomy" 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">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">URL</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">ee51100f-8e3e-40c9-8f8b-57d5a15be1f2</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">d939f2c6-ba25-4dc4-889c-11d1853add19</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">843676a4-303f-4ffa-bd0b-3531dcc3b731</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f5663c5a-d311-4ae4-be14-1575754be5f2</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.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:TenderingCriterion>
<!-- Criterion:Lots the EO tenders to -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">b98984d5-95fa-45cd-a6d1-c017a6aeb62e</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">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Contributions certificates -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">2021715e-2579-4e0b-bc94-14427f49879a</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">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" 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">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.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 schemeID="CriteriaTaxonomy" 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">68d0a722-b1f1-4127-af27-7ef59b478805</cbc:ID>
<cbc:Description>URL</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:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Relied on entities -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0d62c6ed-f074-4fcf-8e9f-f691351d52ad</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">de11ac14-c2d2-4af6-a08e-e6a848f5ff77</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:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Not relied on entities -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">72c0c4b1-ca50-4667-9487-461f3eed4ed7</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">d5fe5a71-7fd3-4910-b6f4-5cd2a4d23524</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">63857106-8b44-44af-8ab4-1e3e92bbcc2c</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7f18c64e-ae09-4646-9400-f3666d50af51</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">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.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:TenderingCriterion>
<!-- EO DATA ENDS HERE -->
<!-- Exclusion and selection Criteria, Responses and Evidences removed for the sake of brevity -->
xml
VII.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 thecac:ResponseValue/cbc:ResponseID
element (and the@schemeAgencyID
attribute must be set to the defaultEU-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.

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.0.2 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 [3].
-
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[4]. 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 thecac: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 VII.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:

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) [5]. 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 elementcbc: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.

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.

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.

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 thecac:ResponseValue/cbc:ResponseID
element (and the@schemeAgencyID
attribute must be set to the defaultEU-COM-GROW
). See information requirements at the beginning of the section. See also next sections about the responses, XSD schemas and XML example.

Certificates about contributions to the Tax Agency and/or Social Security
Data structure for the certificates about contributions to the Tax Agency and/or Social Security:
This data structure is identical to the REGULATED version, see circles #22 and #23 in the mock-up above).

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.0.2 expects from this role. Remember that this information does not need to be supplied by the members of a group or other entities.

Data structure for the entities upon which the EO relies on:

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.

Data structure for the entities upon which the EO does not relies on:

XML Example (SELF-CONTAINED 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 REGULATED 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).

This fragment of XML does not include the responses to the QUESTIONs 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.0.2.xml.
<!-- 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.0.2">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.0.2">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.0.2">2043338f-a38a-490b-b3ec-2607cb25a017</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">6febbe4a-e715-427c-a2b1-19cfabadaef0</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">8d47e12d-2346-41d8-82fe-afb22ebbd791</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a5e33369-e2b5-45f7-9969-ddb1c3ae17c8</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERCENTAGE</cbc:ValueDataTypeCode>(16)
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.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:TenderingCriterion>
<!-- Criterion:EO registered in a PQS -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">64162276-7014-408f-a9af-080426bfe1fd</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">343b5c92-2a5f-4ef7-9d8a-41c8e7b70aa7</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 schemeID="CriteriaTaxonomy" 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">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">ee51100f-8e3e-40c9-8f8b-57d5a15be1f2</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">d939f2c6-ba25-4dc4-889c-11d1853add19</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</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.0.2">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">ca0e6adb-a8a3-40f0-9ffa-f9f0b3d95e31</cbc:ID>
<cbc:Description>Lot ID</cbc:Description> (27)
<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">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Contributions certificates -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">c4f182c7-5c47-4a82-9a0c-8f71f84c35a0</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 schemeID="CriteriaTaxonomy" 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">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.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 schemeID="CriteriaTaxonomy" 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">191b34a8-5af0-4d53-b431-4ecd624218ea</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:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Criterion:Relied on entities -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0d62c6ed-f074-4fcf-8e9f-f691351d52ad</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">66dd1394-b278-4ee7-b589-e6d750024d16</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">50e9a74e-969e-4d79-8e19-8af71cb7c54a</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</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.0.2">72c0c4b1-ca50-4667-9487-461f3eed4ed7</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">289f39b3-2a15-421a-8050-a29858031f35</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">2f7f9459-c020-4b89-8b27-4e52f25242ce</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 schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">50e9a74e-969e-4d79-8e19-8af71cb7c54a</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">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</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 -->
xml
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. |
VII.6.3 Economic operator representatives
Related information requirements
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:.

XSD Schema (REGULATED and SELF-CONTAINED)
In the The ESPD-EDM V2.0.2 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/orcac: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.

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.

Contact elements, such as telephone and e-mail are in the cac:Contact
associated to the the cac:Person
information element:

Expected Elements (REGULATED and SELF-CONTAINED)
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 |
1 |
Name of the natural person. |
Information Requirement: tbr92-009 Rule: Name of the natural person is mandatory. Rule scope: Common (BR-RESP-20-01) |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:FamilyName |
Text |
1 |
Family Name of the natural person. |
Information Requirement: tbr92-009 Rule: Family Name of the natural person is mandatory. Rule scope: Common (BR-RESP-20-02) |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:BirthDate |
Date |
0..1 |
Date of birth of the natural person. |
Information Requirement: tbr92-009 Rule: None. |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cbc:BirthplaceName |
Text |
0..1 |
Place of birth of the natural person. |
Information Requirement: tbr92-009 Rule: None. |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cac:AddressLine |
Text |
0..1 |
The main address line in an address. Usually the street name and number or post office box. |
Information Requirement: tbr92-009 Rule: Use it to specify the street name and number of the building of the representative natural person in one line. Beware that specifying the address of a natural person might enter in conflict with the current Data Protection rules. |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cbc:PostalZone |
Text |
0..1 |
The identifier for an addressable group of properties according to the relevant postal service, such as a ZIP code or Post Code. |
Information Requirement: tbr92-009 Rule: None. |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/cbc:CityName |
Text |
0..1 |
The common name of a city where the address is located. |
Information Requirement: tbr92-009 Rule: None. |
cac:PowerOfAttorney/cac:AgentParty/ cac:Person/cac:ResidenceAddress/ cac:Country/cbc:IdentificationCode |
Code |
1 |
A code that identifies the country. |
Information Requirement: tbr92-009 Rule: Compulsory use of the Code List 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 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.0.2">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.0.2">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.0.2">>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.0.2">>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 -->
xml
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. |
VII.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 QUESTIONS are concerned.
XSD Schema (REGULATED and SELF-CONTAINED)
To answer a QUESTION the ESPD-EDM V2.0.2 uses the UBL-2.2 component cac:TenderingCriterionResponse
. The expected elements are highlighted in blue in the figure below:

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.

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 |

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.

Mock-ups and data structures
The answers to QUESTIONs are provided in the example mock-ups of the previous sections about how the contracting authority specify REQUIREMENTs and QUESTIONs, 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)
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 |
1 |
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 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 Thus, for example, if in the ESPD Request the expected type is DESCRIPTION the cac:ResponseValue must use the element See the codes used for 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 |
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'. |
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 |
1 |
The identifier of the referenced evidence. |
Information Requirement: tbr92-018 Rule: The expected identifier must match the value of a 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).
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. |
VII.7.1 XML Example 1: Information about the EO
The information about the economic operator is distributed into the cac:EconomicOperatorParty
element and 'data structures' that use the cac:TenderingCriterion
element. The XML examples provided herein refer only to the data structured using the cac:TenderingCriterion
. See chapter VII.5. Economic Operator for more details and other XML examples.
XML snippet 1.a) EO registered in a PQS (criterion properties)
This XML shows the criterion properties to which the responses supplied by the economic operator are related. Some of these are copied from the QualificationApplicationRequest, other are added during the edition of the QualificationApplicationResponse (e.g. the ones necessary to ask for the data on the economic operator, such as name, date of birth, number of employees, etc.). See the answers corresponding to these criteria properties in the XML snippet 1.b) below.
Beware that whilst the criterion properties may be from a REGULATED or SELF-CONTAINED ESPD, the cac:TenderingCriterionResponse
(the answers) work always the same way regardless of whether the ESPD Response is REGULATED or SELF-CONTAINED.
In this particular example, the snippet 1.a) contains criterion properties from a SELF-CONTAINED ESPD Response.
<!-- Economic Operator Data: properties -->
<!-- Criterion:EO registered in a PQS -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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>(1)
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">64162276-7014-408f-a9af-080426bfe1fd</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">343b5c92-2a5f-4ef7-9d8a-41c8e7b70aa7</cbc:ID>
<cbc:Description>Your answer?</cbc:Description>(2)
<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 schemeID="CriteriaTaxonomy" 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">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9f5528c1-6f7f-41e0-9287-054a0bef2f9f</cbc:ID>
<cbc:Description>a) Alternative or additional name of the (pre)qualifiction system</cbc:Description>(3)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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>(4)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f6109977-1e25-4926-85f5-813db5c113d5</cbc:ID>
<cbc:Description>d) Does the registration or certification cover all of the required selection criteria?</cbc:Description>(5)
<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>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<!-- Rest of elements removed for the sake of brevity -->
xml
1 | Global QUESTION. If the answer to this QUESTION is Yes the content of the data structure must be processed. |
2 | 'Your answer?' needed to decide how to handle the GUI, the validation or other processing. Expected answer data type: an INDICATOR (true or false). If the answer supplied is true the group of data in the data structure is processed. The response value shall be of type a cbc:ResponseIndicator (based on the CCT udt:IndicatorType, (see folder mod and /UBL-UnqualifiedDataTypes-2.2.xsd to see examples of use and definition). |
3 | 'Alternative name of the (pre)qualifiction system'. Expected answer data type: a DESCRIPTION → the response value shall be a cbc:Description element. |
4 | Reference or certifications that led to the classification of the EO in that PQS. Expected answer data type: a DESCRIPTION. → the response value shall be a cbc:Description element. |
5 | Scope of the certification regardin the selection criteria of this procurement procedure. Expected answer data type: an INDICATOR (true or false) → the response value shall be a cbc:ResponseIndicator based on the CCT 'udt:IndicatorType' element. |
XML snippet 1.b) EO registered in a PQS (answers)
Compare now the elements marked with circled numbers [2, 5] with the elements below marked with the same numbers.
<!-- Economic Operator Data: answers -->
<!-- Answers to Criterion:EO registered in a PQS -->
<!-- Property:Your answer? (PropertyID:343b5c92-2a5f-4ef7-9d8a-41c8e7b70aa7)-->(1)
<cac:TenderingCriterionResponse>(2)
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d9e19426-fc27-4c15-bdd3-a62a0de62a63</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">343b5c92-2a5f-4ef7-9d8a-41c8e7b70aa7</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7eb59ae6-cc5e-472e-87d0-8fd0797ad325</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>(2)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:a) Alternative name of the (pre)qualifiction system (PropertyID:9f5528c1-6f7f-41e0-9287-054a0bef2f9f)-->(3)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">867cca96-d690-45b9-86db-f65a9ca613cd</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9f5528c1-6f7f-41e0-9287-054a0bef2f9f</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8afda449-b2af-405c-a929-6108765a0bfc</cbc:ID>
<cbc:Description>ROLECE, Registro Oficial de Licitadores y Empresas Clasificadas</cbc:Description> (3)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:c) Please state the references on which the registration or certification is based, and, where applicable, the classification obtained in the official list (PropertyID:3eb9b248-21de-47fa-9aa2-e34d0bf1d32c)--> (4)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">73e43330-424d-435f-8ba3-4b4d686e6144</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3eb9b248-21de-47fa-9aa2-e34d0bf1d32c</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">32c90539-ef55-47b0-acf8-1fd80f90670d</cbc:ID>
<cbc:Description>RF12134411-S, RF6113444124-S, RF-15552442-S, other</cbc:Description>(4)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:d) Does the registration or certification cover all of the required selection criteria? (PropertyID:f6109977-1e25-4926-85f5-813db5c113d5)-->(5)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6f3b6de0-7e01-49e2-ae11-75c804d0c88e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f6109977-1e25-4926-85f5-813db5c113d5</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4df26770-c662-432b-be8b-a31b5b306eaa</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>(5)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Rest of elements removed for the sake of brevity -->
xml
1 | Comment documenting to which criterion response this response is linked to. |
2 | Response value to the global QUESTION. The data type is cbc:ResponseIndicator , which is consistent with the expected data value code INDICATOR (from the Code List ResponseDataType). |
3 | Response value tot the 'Alternative name of the (pre)qualifiction system'. Expected answer data type was a DESCRIPTION → the response value is a cbc:Description element. |
4 | Reference or certifications. Expected answer data type was a DESCRIPTION. → the response value is a cbc:Description element; |
5 | Scope of the certification. Expected answer data type was an INDICATOR (true or false) → the response value is a cbc:ResponseIndicator . |
If you compare these two snippets with the mock-up you will notice that the field "b) Please provide the identification of the economic operator in the pre-qualification system" is not referred to or instantiated in the XML snippets above. This is because this identification of the economic party is placed in the element cac:EconomicParty/cac:QualifyingParty/cac:Identification/cbc:ID
. See the XML example in section "XML Example (SELF-CONTAINED economic operator)" and look for this fragment of XML code (circle #19 in the mock-up):
<cac:PartyIdentification>
<cbc:ID schemeID="VAT" schemeAgencyID="ROLECE" schemeAgencyName="Registro Oficial de Licitadores y Empresas Clasificadas del Estado">B82387770</cbc:ID>
</cac:PartyIdentification>
xml
XML snippet 2.a) Lots the EO tenders to (criterion properties)
If the procurement procedure is divided into Lots the ESPD Request will have multiple instances of the element cac:ProcurementProjectLot
(see section "III.10 Lots - Self-contained ESPD").
Based on the identifiers of the Lots specified in the ESPD Request, software applications can require the economic operator to link its answers to the Lots. One example of this are when the EO specifies the Lots it tenders to; (another example is when the EO links its references to works, supplies or services similar to the procurement procedure it is tendering. In the SELF-CONTAINED ESPD a group of references can be linked to one or more Lots. See the "XML Example 2" below).
<!-- Criterion:Lots the EO tenders to -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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>(1)
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<!-- This property below provides the UUID to which all the Lot IDs provided by the EO in the response will be linked, thus constructing the List -->
<cac:TenderingCriterionProperty>(2)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ca0e6adb-a8a3-40f0-9ffa-f9f0b3d95e31</cbc:ID>
<cbc:Description>Lot IDs</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">IDENTIFIER</cbc:ValueDataTypeCode>(3)
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
xml
1 | Text description the QUESTION. |
2 | Property to which all the Lots provided by the EO will be linked to. |
3 | The expected type of data is an IDENTIFIER. This implies that in the response the response value shall be an element based on the cbc:Identifier type defined by UBL; see snippet 2.b) below. |
Compare the circled numbers in the XML snippet above with the circled numbers in the XML snippet below.
XML snippet 2.b) Lots the EO tenders to (answers)
<!-- Answer to Criterion:Lots the EO tenders to -->
<!-- Property:Lot IDs (PropertyID:ca0e6adb-a8a3-40f0-9ffa-f9f0b3d95e31) -->(1)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9bbe78e9-e342-46fa-974c-299dc87087ef</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ca0e6adb-a8a3-40f0-9ffa-f9f0b3d95e31</cbc:ValidatedCriterionPropertyID>(2)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue> (3)
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ea861f62-50c8-4f57-9212-ffbb6f2a10a8</cbc:ID>
<cbc:ResponseID>Lot4</cbc:ResponseID>(4)
</cac:ResponseValue>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bcde4e84-936d-4b27-a873-3fe74860b0a7</cbc:ID>
<cbc:ResponseID>Lot5</cbc:ResponseID>(5)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
xml
1 | Comments identifying the criterion. |
2 | The UUID of the criterion property thus linking this answer to it and all its content, in this case a list of 2 values. |
3 | First value of the list (compare to the value supplied by the EO, circle #27 in the mock-up). |
4 | Notice that the value is placed in a cbc:Identifier (CCT udt:IdentifierType ) qualified as ResponseID (see folder mod and /UBL-UnqualifiedDataTypes-2.2.xsd to see examples of use and definition). This is consistent with the fact that the criterion property (see XML snippet 2.a) specifies the value IDENTIFIER in the element cac:ValueDataTypeCode . |
5 | Second value of the list (compare to the value supplied by the EO, circle #27 in the mock-up). |
VII.7.2 XML Example 2: References
This example is based on the EO perspective of the SELF-CONTAINED mock-up in section "VI.7.2. SELF-CONTAINED References":

XML snippet 1.a) REQUIREMENTs by the contracting authority (CA) (criterion properties)
This fragment of XML code extracts the requirement issued by the CA in a SELF-CONTAINED ESPD Request document. In this example the CA specifies 3 requirements:
-
The minimum number of references (one in this case, to shorten the example. Normally more references are required);
-
Two requirements expressed as text: 'Specific amount greater than 1,000.000 €' and 'Executed recently, after 2013 in any case.'; and
-
The Lots to which these three requirements apply: Lot1, Lot2, Lot4 and Lot5. Notice that the list of Lots is made of a set of individual criterion properties inside its own subgroup.
<!-- Criterion description removed for brevity --> (1)
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">381bea15-9460-49f7-a6d0-15d13059de29</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<!-- REQUIREMENT #1 issued by the CA -->
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">98a67182-d7b7-4fb4-ae35-ea6bd9411eac</cbc:ID>
<cbc:Description>Minimum number of references</cbc:Description> (3)
<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">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
<!-- No answer is expected here from the economic operator, as this is a REQUIREMENT issued by the contracting authority. Hence the element 'cbc:ValueDataTypeCode' contains the type of value of the requirement issued by the contracting authority -->
<cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>
</cac:TenderingCriterionProperty>
<!-- SUBGROUP OF REQUIREMENTS (2 textual requirements issued by the CA -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">53c9aad8-dc80-48f8-85d9-755c2aab8e95</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">4b19bd4b-78ae-476a-a2c5-6c409388a07b</cbc:ID>
<cbc:Description/>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d663aca5-5f3c-4980-b825-81e1bd7db381</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<!-- Requirement 2 -->
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3646852e-ebfc-463a-be95-0cf697fb138a</cbc:ID>
<cbc:Description>Requirement</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>Specific amount greater than 1,000.000 €</cbc:ExpectedDescription>(4)
</cac:TenderingCriterionProperty>
<!-- Requirement 3 -->
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">610e450c-89c9-49ec-b18a-ebb6683f9b31</cbc:ID>
<cbc:Description>Requirement</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>Executed recently, after 2013 in any case.</cbc:ExpectedDescription>(5)
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<!-- Lots these requirements apply to -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">167ab253-4fb7-4e45-81be-b049fba44b3a</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<!-- The following REQUIREMENTS apply to lots: Lot1, Lot2, Lot4, Lot5. This information is provided by the Contracting Authority. The list of Lots to which the EO tenders to, and for which it provides references must be consistent with this list (see 'QUESTIONS' and criterion responses values provided by the EO below -->(2)
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b0c6f987-227e-426b-8023-c2f56416d3eb</cbc:ID>
<cbc:Description>Lots the requirement applies to</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1af3d1c6-69e6-4af0-ba96-ba1461b29e13</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">IDENTIFIER</cbc:ValueDataTypeCode>
<cbc:ExpectedID>Lot1</cbc:ExpectedID>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1af3d1c6-69e6-4af0-ba96-ba1461b29e13</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">IDENTIFIER</cbc:ValueDataTypeCode>
<cbc:ExpectedID>Lot2</cbc:ExpectedID>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1af3d1c6-69e6-4af0-ba96-ba1461b29e13</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">IDENTIFIER</cbc:ValueDataTypeCode>
<cbc:ExpectedID>Lot4</cbc:ExpectedID>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1af3d1c6-69e6-4af0-ba96-ba1461b29e13</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">IDENTIFIER</cbc:ValueDataTypeCode>
<cbc:ExpectedID>Lot5</cbc:ExpectedID>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
xml
1 | The criterion description sentence "For public works contracts only: During the reference period, the economic operator has performed …" was removed from the example for brevity. See the XML instance document for the complete example. |
2 | List of Lots, built by the contracting authority, that are affected by these REQUIREMENTs. |
3 | Minimum number of references. In this example the CA requires only one reference (for brevity). The normal situation is to require more than one. If three had been specified by the CA then three groups of references would have been instantiated in the XML document. |
4 | First textual requirement. This group of ONE reference has to comply to two REQUIREMENTs specified by the CA: that the EO must supply references where with 'Specific amount greater than 1,000.000 €'; and (2) the reference is recent, as it had to be 'Executed recently, after 2013 in any case.' |
5 | Second textual requirement. This group of ONE reference has to comply to two REQUIREMENTs specified by the CA: that the EO must supply references where with 'Specific amount greater than 1,000.000 €'; and (2) the reference is recent, as it had to be 'Executed recently, after 2013 in any case.' |
XML snippet 1.b) QUESTIONS asked to the economic operator (criterion properties)
<!-- See previous example -->(1)(2)(3)(4)(5)
<!-- QUESTIONS ASKED TO THE EO -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a44e24e9-f878-4651-9ead-e0b1387dae09</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">8acfa508-b0db-4960-bf4a-69d98f068387</cbc:ID>
<cbc:Description>Please provide the data below requested for this group of references associated to one or more lots</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<!-- Lots the EO tenders to for which these references apply to -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b9ac8ecf-5902-408e-a9a6-604568b35e1e</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">aabbbe3f-7c9b-4f9c-a7aa-b21dee270e2a</cbc:ID>
<cbc:Description>Lots these references apply to</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<!-- Criterion property to which the lists of Lots the EO tenders to will be associated to-->
<cac:TenderingCriterionProperty>(6)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">736f6d0e-9319-45a5-86ae-bc14337a0ef6</cbc:ID>
<cbc:Description>LotIDs</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">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<!-- Subgroup of References. In this example there is only one reference required by the CA -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c8ec5c30-2c17-4936-abbb-392523d873e5</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>(7)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d470a8cd-4cf9-4b10-a7bc-642092f8ab47</cbc:ID>
<cbc:Description>Reference description</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:TenderingCriterionProperty>(8)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ed54ecc3-eb5c-409b-ab22-975cadb83e4c</cbc:ID>
<cbc:Description>Total amount</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">AMOUNT</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>(9)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">78fc0800-4966-47e4-aa85-67c4e431a382</cbc:ID>
<cbc:Description>Activity of the economic operator</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:TenderingCriterionProperty>(10)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cc6366c2-2f15-4414-8f1e-686a68be2a4d</cbc:ID>
<cbc:Description>Specific amount</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">AMOUNT</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>(11)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">229e775e-267b-4d97-a2fe-3c155f3612b4</cbc:ID>
<cbc:Description>Period (Start and End dates)</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">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>(12)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4e56602a-0281-47ee-a4f3-3c99f077e603</cbc:ID>
<cbc:Description>Confidential</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>
<!-- Sub-subgroup of recipients -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6afa7569-e4c4-4538-be89-84a82b2a301b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>(13)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8d22cea4-ae81-44d2-9ee5-c60958ed109e</cbc:ID>
<cbc:Description>Recipient name</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:TenderingCriterionProperty>(14)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4bb5b0f-b894-461d-a96b-50dead10e935</cbc:ID>
<cbc:Description>Contact person name</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:TenderingCriterionProperty>(15)
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9786fd9e-5c84-41e3-9322-e16643763319</cbc:ID>
<cbc:Description>Contact email</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:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" 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">56c3d4b1-3e79-4b31-8ccc-dcc959c462ad</cbc:ID>
<cbc:Description>Is this information available online?</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>
<!-- Evidence linked to the reference -->
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" 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">e6393edd-db19-4b6d-8d1c-8c87d45b28af</cbc:ID>
<cbc:Description>Evidence Supplied</cbc:Description>(16)
<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:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
xml
1 | See previous XML example. |
2 | See previous XML example. |
3 | See previous XML example. |
4 | See previous XML example. |
5 | See previous XML example. |
6 | This criterion property (QUESTION) is used to build up the list of Lot Identifiers. In the answer all the response values of the Lot Identifiers will be linked to the UUID of this property using the element cac:Validated(Numbers <1> to <5> were assigned to the Criteron description and the CA REQUIREMENTs in the mock-up); see XML example above. |
7 | 'Reference description'. Expected data type and response value: 'DESCRIPTION' → cbc:Description . See how the answer, in the XML snippet below, is linked to the UUID of this criterion property. |
8 | 'Total amount' to refer to the amount of the contract. Expected data type and response value: AMOUNT → cbc:ResponseAmount . See section "VI.7 References on similar works, deliveries or services" for the difference between total and specific amounts in a reference. |
9 | 'Activity of the economic operator'. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
10 | 'Specific amount' to refer to the amount of the reference. Expected data type and response value: AMOUNT → cbc:ResponseAmount . See section "VI.7 References on similar works, deliveries or services" for the difference between total and specific amounts in a reference. |
11 | Period of execution, delivery or performance of the work, supply or service object of this reference. Expected data type and response value: 'PERIOD' → cac:Period . |
12 | 'Confidential', specifies whether this reference must be treated as confidential or not. Expected data type and response value: 'INDICATOR' → cbc:ResponseIndicator . If the answer is true all evidences linked to this criterion property must be treated as confidential, even if the evidence was not considered confidential for other criterion properties. |
13 | 'Recipient name', name of the buyer of the contract, e.g. a contracting authority. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
14 | 'Contact person name' at the buyer’s organisation, e.g. a contracting authority’s contact point. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
15 | 'Contact email' of the buyer’s organisation, e.g. a contracting authority’s contact point email address. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
16 | 'Evidence(s) Supplied'. Link to one or more evidences available online to support the authenticity of the reference (and of the declaration). See the answer in the XML snippet below: in this concrete example the economic operator will state that there is no evidence is available online to support this reference (value *false'). |
XML snippet 1.c) Responses supplied by the economic operator (criterion responses, and response values)
The figure below shows how the set of response to the criterion "For works contracts: performance of works of the specified type" look like when collapsed (no details shown).

The circled numbers map the ones in the mock-up (at the beginning of this section) and the notes in the XML examples above (<6> to <16> → QUESTIONS, as REQUIREMENTS do not expect and answer by the EO, they are informative/prescriptive).
<!-- See previous example -->(1)(2)(3)(4)(5)
<!-- Answer to Criterion:For works contracts: performance of works of the specified type -->
<!-- Property:LotID (PropertyID:736f6d0e-9319-45a5-86ae-bc14337a0ef6) -->(6)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">915a33c0-2197-4e60-8374-17b14417dd44</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">736f6d0e-9319-45a5-86ae-bc14337a0ef6</cbc:ValidatedCriterionPropertyID>(6)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<!-- Notice that the two following cac:ResponseValues elements point at the same QUESTION (cac:TenderingCriterionProperty) UUID.-->
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">466faede-7831-46a6-8a32-6437fa65782a</cbc:ID>
<cbc:ResponseID>LOT1</cbc:ResponseID>(6)
</cac:ResponseValue>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">466faede-7831-46a6-8a32-6437fa65782a</cbc:ID>
<cbc:ResponseID>LOT2</cbc:ResponseID>(6)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Reference description (PropertyID:d470a8cd-4cf9-4b10-a7bc-642092f8ab47) -->(7)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">424d4573-083c-4b5e-9d67-0b8df85f951b</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d470a8cd-4cf9-4b10-a7bc-642092f8ab47</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bbb8ac45-e914-4cbe-8d79-105244dede36</cbc:ID>
<cbc:Description>Implementation of the Interoperability Platform of Electronic State Services 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 through 30 information services</cbc:Description>(7)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Total amount (PropertyID:ed54ecc3-eb5c-409b-ab22-975cadb83e4c) -->(8)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">04969adf-7c55-46e6-b4b7-0444a47a08a9</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ed54ecc3-eb5c-409b-ab22-975cadb83e4c</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">23562cf9-34a7-4ce5-aebe-17e65981c6b7</cbc:ID>
<cbc:ResponseAmount currencyID="EUR">2479914</cbc:ResponseAmount>(8)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Activity of the economic operator (PropertyID:78fc0800-4966-47e4-aa85-67c4e431a382) -->(9)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c6c5f34f-5f83-4123-93fb-a2d103568733</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">78fc0800-4966-47e4-aa85-67c4e431a382</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">38edda06-68d4-4846-a644-a7801749d865</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>(9)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Specific amount (PropertyID:cc6366c2-2f15-4414-8f1e-686a68be2a4d) -->(10)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">313b5826-9af1-403f-8b84-d0da831e98f6</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cc6366c2-2f15-4414-8f1e-686a68be2a4d</cbc:ValidatedCriterionPropertyID>(10)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fa1d042c-db7f-49b9-948f-8a704c55589b</cbc:ID>
<cbc:ResponseAmount currencyID="EUR">1123017</cbc:ResponseAmount>(10)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Period (Start and End dates) (PropertyID:229e775e-267b-4d97-a2fe-3c155f3612b4) -->(11)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9e202bf2-841d-45f9-af81-e4da5aa378da</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">229e775e-267b-4d97-a2fe-3c155f3612b4</cbc:ValidatedCriterionPropertyID>(11)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ApplicablePeriod>(11)
<cbc:StartDate>2017-01-01</cbc:StartDate>
<cbc:EndDate>2017-12-12</cbc:EndDate>
</cac:ApplicablePeriod>
</cac:TenderingCriterionResponse>
<!-- Property:Confidential (PropertyID:4e56602a-0281-47ee-a4f3-3c99f077e603) -->(12)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d6eab76d-5a21-4331-87dd-e7c45bfc5982</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4e56602a-0281-47ee-a4f3-3c99f077e603</cbc:ValidatedCriterionPropertyID>(12)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a4fbfb27-95e0-4fc8-8c89-9a00ed38aef6</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>(12)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Recipient name (PropertyID:8d22cea4-ae81-44d2-9ee5-c60958ed109e) -->(13)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a4a6ee1e-edd7-4a47-abf1-a7ef3799bae4</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8d22cea4-ae81-44d2-9ee5-c60958ed109e</cbc:ValidatedCriterionPropertyID>(13)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b180f801-8447-4367-9988-1c64867094d3</cbc:ID>
<cbc:Description>Economics Department, Government of Spain</cbc:Description>(13)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Contact person name (PropertyID:f4bb5b0f-b894-461d-a96b-50dead10e935) -->(14)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c92fbaee-7fcd-4e9e-9bc7-4065e2bba7f2</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4bb5b0f-b894-461d-a96b-50dead10e935</cbc:ValidatedCriterionPropertyID>(14)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7d10d6b9-5c9b-4ae7-aac1-a8eee56f6d17</cbc:ID>
<cbc:Description>Juan Rodriguez</cbc:Description>(14)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Contact email (PropertyID:9786fd9e-5c84-41e3-9322-e16643763319) -->(15)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b6df90d8-42d9-4add-a67c-f2e3e3ce5c6f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9786fd9e-5c84-41e3-9322-e16643763319</cbc:ValidatedCriterionPropertyID>(15)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">15757e6e-fbf7-455f-8eee-b4b07e4b39fe</cbc:ID>
<cbc:Description>Juan.rodriguez@mail.com</cbc:Description>(15)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Is this information available online? (PropertyID:56c3d4b1-3e79-4b31-8ccc-dcc959c462ad) -->(16)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5d106ff3-bbf0-4715-a8b5-82fe2cb42076</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">56c3d4b1-3e79-4b31-8ccc-dcc959c462ad</cbc:ValidatedCriterionPropertyID>(16)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d024b5ab-f002-47e6-9ccc-eab81744af9c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>(16)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
xml
1 | See previous XML example. |
2 | See previous XML example. |
3 | See previous XML example. |
4 | See previous XML example. |
5 | See previous XML example. |
6 | List of Lots the EO tenders to that are related to this reference. Compare the UUID (736f6d0e-9319-45a5-86ae-bc14337a0ef6) used to link the criterion property and the response through the element cbc:ValidatedCriterionPropertyID . |
7 | 'Reference description'. The value data type, cbc:Description matches the one expected, specified by the CA in the ESPD Request. |
8 | 'Total amount'. The value data type, cbc:ResponseAmount matches the one expected, specified by the CA in the ESPD Request. |
9 | 'Activity of the economic operator'. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
10 | 'Specific amount' to refer to the amount of the reference. Expected data type and response value: AMOUNT → cbc:ResponseAmount . See section "VI.7 References on similar works, deliveries or services" for the difference between total and specific amounts in a reference. |
11 | Period of execution, delivery or performance of the work, supply or service object of this reference. Expected data type and response value: 'PERIOD' → cac:Period . |
12 | 'Confidential', specifies whether this reference must be treated as confidential or not. Expected data type and response value: 'INDICATOR' → cbc:ResponseIndicator . If the answer is true all evidences linked to this criterion property must be treated as confidential, even if the evidence was not considered confidential for other criterion properties. |
13 | 'Recipient name', name of the buyer of the contract, e.g. a contracting authority. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
14 | 'Contact person name' at the buyer’s organisation, e.g. a contracting authority’s contact point. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
15 | 'Contact email' of the buyer’s organisation, e.g. a contracting authority’s contact point email address. Expected data type and response value: 'DESCRIPTION' → cbc:Description . |
16 | 'Evidence(s) Supplied'. Link to one or more evidences available online to support the authenticity of the reference (and of the declaration). In this concrete example the economic operator states that it no evidence is available online to support this reference. |
VII.7.3 XML Example 3: Weighting
This section presents an XML Example of a WEIGHTED SELF-CONTAINED criterion (used in a two-stages procedure). The criterion properties corresponding to REQUIREMENTs and QUESTIONs are the ones that were copied from the ESPD Request into the ESPD Request.
The XML example contains circled numbers aimed to map the fields in the CA and EO mock-ups:
The example illustrates:
-
the REQUIREMENTs issued by the CA;
-
the QUESTIONs addressed to the EO;
-
the answwers provided by the EO.
Mock-ups
Contracting authority perspective:

Economic operator perspective:

XML snippet 1.a) criterion REQUIREMENTs and QUESTIONs (SELF-CONTAINED and WEIHGTED)
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 elementscbc: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).
<!-- 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.0.2">PERCENTAGE</cbc:WeightingType>(2)
<!-- Criterion:Technicians or technical bodies for quality control -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3aaca389-4a7b-406b-a4b9-080845d127e7</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">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.0.2">1e73d705-9dc1-43f1-9b5c-2d0deac7bc5f</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">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.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">f156d97a-9700-4ad9-8d21-e3ac57102278</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">bbe06b1d-bb21-4588-a489-4bce6a51364f</cbc:ID>
<cbc:Description>Requirement</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>
<!-- 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.0.2">609cc954-64be-4b4f-800a-f17589deb936</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">96cc5c65-2395-4750-b9c7-b60dc58fcf24</cbc:ID>
<cbc:Description/>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52ffcf91-3598-438f-8c3d-faf97da02602</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">b986d088-ec14-4eca-ac99-a7119aae4f43</cbc:ID>
<cbc:Description>Technician</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a2662683-efc5-4e81-be28-57dfa78b4834</cbc:ID>
<cbc:Description>First name</cbc:Description>(7)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bc0d0694-d47f-4b1c-9770-843fe177360c</cbc:ID>
<cbc:Description>Last name</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>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9a7344fa-fc73-4e73-a440-531e90b61231</cbc:ID>
<cbc:Description>Profession</cbc:Description>(9)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">845f376f-fedb-4710-a1b8-5514c5439c1b</cbc:ID>
<cbc:Description>Experience</cbc:Description>(10)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7e9f0030-3fe9-4407-888f-f7cfe39f9df2</cbc:ID>
<cbc:Description>Other information</cbc:Description>(11)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">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.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" 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">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.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 schemeID="CriteriaTaxonomy" 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">91ee7ffe-07b5-4e87-87e5-9b1063e9d487</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:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">45a67f48-d146-4faf-8239-dd6977dffe29</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">99fe0af5-0a47-4930-b1e8-8acbc614964b</cbc:ID>
<cbc:Description/>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52ffcf91-3598-438f-8c3d-faf97da02602</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">aab9aa41-87a0-4f71-89d4-3dfdb94fc025</cbc:ID>
<cbc:Description>Technical body</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b8b76588-cc5c-4d6f-acf9-0447ab1047f4</cbc:ID>
<cbc:Description>Name</cbc:Description>(14)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3044bc5a-eb95-4639-a0b5-4c1d79da9873</cbc:ID>
<cbc:Description>Experience area</cbc:Description>(15)
<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:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">165d6fad-8915-4b20-8c75-1a661a27e2f4</cbc:ID>
<cbc:Description>Other information</cbc:Description>(16)
<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>
<cbc:ID schemeID="CriteriaTaxonomy" 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">b9b7e484-829f-47b9-8d83-545ed3ff43cf</cbc:ID>
<cbc:Description>Is this information available online?</cbc:Description>(17)
<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 schemeID="CriteriaTaxonomy" 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">5549921f-8000-45e9-8fbc-3c7bab4ba6d4</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:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
xml
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. |
XML snippet 1.b) Responses to
Beware that one subset of the data is answered in the Criterion sub-elements. The XML snippet below does only shows the responses to the QUESTIONs in data structure (compare the responses and the data structure represented in the data structure, tab "SC-Abilities_1").
<!-- Some data are placed in the root of the document and inside the Criterion -->(2)(3)(4)(5)(6)
<!-- Answer to Criterion:Technicians or technical bodies for quality control -->
<!-- Property:Your Answer (PropertyID:79f9b1c5-7c78-4530-a09b-f04109118e40)-->
<cac:TenderingCriterionResponse>(1)
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">164182ce-d536-436d-9564-2a548df929fc</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">79f9b1c5-7c78-4530-a09b-f04109118e40</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b207993f-6622-4e52-b368-9de3552320c7</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>(1)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:First name (PropertyID:a2662683-efc5-4e81-be28-57dfa78b4834)-->(7)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bde5a610-3849-4cd5-8861-86f93665ac89</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a2662683-efc5-4e81-be28-57dfa78b4834</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">07eb8c66-da1f-49cd-97e4-76f75f37b7f8</cbc:ID>
<cbc:Description>James</cbc:Description>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Last name (PropertyID:bc0d0694-d47f-4b1c-9770-843fe177360c)-->(8)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8441d730-5ad3-4b82-9b79-5c0e3ea2a25a</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bc0d0694-d47f-4b1c-9770-843fe177360c</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7934bd5a-fdc4-4978-a95a-1c3b0c621070</cbc:ID>
<cbc:Description>Mortimer</cbc:Description>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Profession (PropertyID:9a7344fa-fc73-4e73-a440-531e90b61231)-->(9)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3f765dde-e0fd-46f1-80c7-bd7e7b3c0972</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9a7344fa-fc73-4e73-a440-531e90b61231</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f239018-ca77-4a5f-a01b-e8175fbbdc62</cbc:ID>
<cbc:Description>ICT Consultant</cbc:Description>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Experience (PropertyID:845f376f-fedb-4710-a1b8-5514c5439c1b)-->(10)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e9f6b328-d716-48a7-a2c6-cc4756233336</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">845f376f-fedb-4710-a1b8-5514c5439c1b</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3c401702-c43a-4ffb-8c2b-adb7f0ad4e53</cbc:ID>
<cbc:Description>10 year as Enterprise IT Architect in the private sector. 12 years of experience as ICT consultant for the Public Sector, namely the European Institutions.</cbc:Description>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Other information (PropertyID:7e9f0030-3fe9-4407-888f-f7cfe39f9df2)-->(11)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a0943065-7ffd-4563-8ae1-e90718527fa2</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7e9f0030-3fe9-4407-888f-f7cfe39f9df2</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4943913-68b3-4419-bbc4-0d3eec37855b</cbc:ID>
<cbc:Description>Wide experience in Artificial Intelligence.</cbc:Description>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:How long with EO (PropertyID:b848f9ea-281b-4895-96c1-705d678bf125) -->(12)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9a78cb8c-5de0-42dc-ab52-cec879d9e441</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b848f9ea-281b-4895-96c1-705d678bf125</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74ec1d61-ced7-4f1f-af10-8b24e725c7e2</cbc:ID>
<cbc:ResponseQuantity>36</cbc:ResponseQuantity>(12)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Is this information available online? (PropertyID:94b53be3-b838-4538-8b43-b6b1f05fc158) --> (13)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6b4cffa7-27c5-4f9b-9b39-273610f3374a</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">94b53be3-b838-4538-8b43-b6b1f05fc158</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b2784c55-3a9f-4bca-b4ff-e12e3e4050c9</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>(13)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- No evidence supplied element instantiated! as the answer to the previous question was *No* -->
<!-- Property:Name (PropertyID:b8b76588-cc5c-4d6f-acf9-0447ab1047f4) --> (14)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4818756-7015-4223-94b2-990f0aa39064</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b8b76588-cc5c-4d6f-acf9-0447ab1047f4</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f68b4cb-801c-4438-b935-dc701bf6c888</cbc:ID>
<cbc:Description>EPD (Everis Phonetics Department)</cbc:Description>(14)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Experience area (PropertyID:3044bc5a-eb95-4639-a0b5-4c1d79da9873) -->(15)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">69d9b7fe-6874-4962-9b3d-a871731f5193</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3044bc5a-eb95-4639-a0b5-4c1d79da9873</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5276d2af-3031-4c20-a203-7f89e7e46dbc</cbc:ID>
<cbc:Description>Data-mining from audiovisual streaming</cbc:Description>(15)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Other information (PropertyID:165d6fad-8915-4b20-8c75-1a661a27e2f4)-->(16)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ddf269f3-fdf4-40d7-83af-f4180961d2c4</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">165d6fad-8915-4b20-8c75-1a661a27e2f4</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2c7cc8f7-9f4e-4521-a2f7-274bc92c4cc1</cbc:ID>
<cbc:Description>First Prize of the 2016 Technology Language Contest</cbc:Description>(16)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Is this information available online?(PropertyID:b9b7e484-829f-47b9-8d83-545ed3ff43cf) -->(17)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dfd2438e-c239-48df-b36f-f73679f96317</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b9b7e484-829f-47b9-8d83-545ed3ff43cf</cbc:ValidatedCriterionPropertyID>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">34022f7d-ed8a-488b-91c9-fd02f2c59b56</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>(17)
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<!-- Property:Evidence supplied (PropertyID:5549921f-8000-45e9-8fbc-3c7bab4ba6d4)-->(17)
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9577e16f-9bd0-4e64-9a3e-21a9b42b7673</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5549921f-8000-45e9-8fbc-3c7bab4ba6d4</cbc:ValidatedCriterionPropertyID>
<cac:EvidenceSupplied>
<cbc:ID>293b6386-9091-4081-8824-c58436e9f9a5</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:Evidence>
<cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0">293b6386-9091-4081-8824-c58436e9f9a5</cbc:UUID>(18)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PUBLIC</cbc:ConfidentialityLevelCode>(19)
<cac:DocumentReference>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>http://lt.org/contests/prizes/2016/index.html</cbc:URI>(20)
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<cac:PartyName>
<cbc:Name>lt.org (Linguistic Technologies)</cbc:Name>(21)
</cac:PartyName>
</cac:IssuerParty>
</cac:DocumentReference>
</cac:Evidence>
xml
1 | The contracting authority has selected that this criterion will be weigthed. |
2 | Datum in the root element cbc:WeightScoringMethodologyDescription . |
3 | Datum in the root element cbc:WeightingType . |
4 | Datum in the criterion element cbc:EvaluationMethodTypeCode . |
5 | Datum in the criterion element cbc:WeightNumeric . |
6 | Datum in the criterion element cbc:WeightingConsiderationDescription . |
7 | First Name of the technician. |
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 | Not available online evidence related to this technician, his experience, etc. |
14 | Name of a technical body. |
15 | Area of experience of the technical body. |
16 | Additional information related to the technical body. |
17 | Reference to a an available online evidence related to this technical body. |
18 | Evidence about the prize won by this technical body. |
19 | The evidence is publicly accessible. |
20 | The URL where to get the evidence of the prize from. |
21 | The name of the issuer of the the evidenciary document. |
VII.8 Evidences
Related information requirements
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.0.2.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.0.2):

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

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

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.0.2 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 |
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.
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 |
1 |
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 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.0.2:
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 |
1 |
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 |
1 |
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.0.2. |
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
<!-- Criterion #1:Participation in a criminal organisation -->
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">005eb9ed-1347-4ca3-bb29-9bc0db64e1ab</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">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.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 schemeID="CriteriaTaxonomy" 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> (1)
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ID>(2)
<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> (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.0.2">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.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 schemeID="CriteriaTaxonomy" 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">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ID>(2)
<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>(3)
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<!-- elements removed for brevity -->
</cac:TenderingCriterion>
xml
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.0.2">219949a1-b7bb-4d7e-8c3b-cc8ca695e15b</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ValidatedCriterionPropertyID>(1)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">7c7fb445-c5f9-4f92-8b58-7f06a541951f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">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>
xml
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
<!-- ANSWERS TO QUESTIONS -->
<!-- ... 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.0.2">219949a1-b7bb-4d7e-8c3b-cc8ca695e15b</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d8d5478e-cc65-48c9-a189-19bbe87a9bfd</cbc:ValidatedCriterionPropertyID> (1)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">7c7fb445-c5f9-4f92-8b58-7f06a541951f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">191b34a8-5af0-4d53-b431-4ecd624218ea</cbc:ValidatedCriterionPropertyID>(4)
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">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.0.2">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.0.2">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>
xml
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. |