Root elements

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

Table 26. Class QualificationApplicationResponse, components required by the ESPD-EDM

Document name:

QualificationApplicationResponse

Definition:

"A structured electronic business document for providing qualification information in a simplified way through an ESPD when responding to a Call for Tender." (source: ESPD Response transaction (Trdm092)).

Preliminary evidence certificates in the form of a self-declaration submitted by the economic operator during the tendering phase. On awarding, the winning party has to supply the real attestations and certificates.

Business rule(s):

None

File:

ubl-2.3/xsdrt/maindoc/UBL-QualificationApplicationResponse-2.3.xsd

Components	Type	Card	Description	Requirements
cbc:UBLVersionID	Identifier	1	Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance.	Information Requirement: tbr92-020. Rule: Use the value "2.3". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute. Rule scope: Common (BR-OTH-05, 2.BR-OTH-02)
cbc:ProfileExecutionID	Identifier	1	The identification and version of the ESPD Exchange Data Model used to create the XML instance. The identification may include the exact version of the specification.	Information Requirement: tbr070-002. Rule: Compulsory use of the CodeList ProfileExecutionID. Use the value "OP" for th SchemeAgencyID attribute. Rule scope: Common (BR-OTH-01, BR-OTH-01#13, BR-OTH-03)
cbc:ID	Identifier	1	An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, or the supplier, e.g. an economic operator). The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.	Information Requirement: tbr92-019. Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document. Rule scope: Common (BR-OTH-02)
cbc:CopyIndicator	Indicator	0..1	Indicates whether this document is a copy (true) or not (false).	Information Requirement: tbr92-019. Rule: It is a good practice to use the CopyIndicator component if the same document is forwarded several times to the same or to different destinations. Use it in combination with the UUID identifier: copies of an ESPD document should be identified with distinct UUIDs.
cbc:UUID	Identifier	1	A universally unique identifier that can be used to reference this ESPD document instance.	Information Requirement: tbr92-019. Rule: Other documents, e.g. the tender, might refer to the ESPD Response using this identifier (thus its compulsoriness). Copies of a document must be identified with a different UUID. Compulsory use of schemeAgencyID attribute.
cbc:ContractFolderID	Identifier	1	An identifier that is specified by the buyer and used as a reference number for all documents in the procurement process. It is also known as procurement project identifier, procurement reference number or contract folder identifier. A reference to the procurement procedure to which a Qualification request document and the delivered response documents are associated.	Information Requirement: tbr92-013. Rule: Try always to use the reference number issued by the buyer. This number in combination with a registered buyer ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure. Rule scope: (BR-SC-30)
cbc:IssueDate	Date	1	Date when the document was issued by the buyer.	Information Requirement: tbr92-019. Rule: Format "YYYY-MM-DD".
cbc:IssueTime	Time	0..1	Time when the document was issued by the buyer.	Information Requirement: tbr92-019. Rule: Format "hh:mm:ss".
cbc:EconomicOperatorGroupName	Text	0..1	The name of the group that presents a tender to which this economic operator belongs (e.g. the name of a consortium, a joint venture, etc.).	Information Requirement: tbr92-008. Rule: The leader of the group must take care of ensuring that the name of the group is identical in all the ESPDs of the tender. Rule scope: (BR-LEAD-10-S10)
cbc:VersionID	Identifier	0..1	The version identifying the content of this document.	Information Requirement: tbr92-020. Rule: Changes in content should entail the modification of the version identifier and a reference to the previous version.
cbc:PreviousVersionID	Identifier	0..1	The version identifying the previous modification of the content of this document.	Information Requirement: tbr92-020. Rule: None
cbc:ProcedureCode	Code	1	The type of the procurement administrative procedure according to the EU Directives.	Information Requirement: tbr070-007. Rule: For the ESPD, this information will be linked to eForms. And ESPD should include the same procedure code as the one stated in eForms notices.
cac:ContractingParty	Associated class	1	The buyer or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU). See section Contracting Body for more specification details.	Information Requirement: tbr92-011. Rule: UBL-2.3 defines multiple cardinality ContractingParties presumably to allow joint procurements. However the ESPD only expects data about one buyer. The decision was made that in case of joint procurement the data collected in the ESPD would be about the leader of the joint procurement procedure.
cac:EconomicOperatorParty	Associated class	1	Any natural or legal person or public entity which offers the execution of works and/or a work, the supply of products or the provision of services on the market. Information about the party submitting the qualification.	Information Requirement: tbr92-001. Rule: The ESPD Response only refers to one, and only one, economic operator. Rule scope: Common (BR-RESP-10)
cac:ProcurementProject/cbc:Description	Text	1	Text describing this procurement project.	This element is required in the ESPD, however it should be identical to that provided in eForms. In general the corresponding eForm should feed the corresponding ESPD with the corresponding data. Information Requirement: tbr92-013. Rule: Use this component to identify and describe the procurement administrative procedure.
cac:ProcurementProjectLot	Associated class	1	The procurement project lot or group of lots this ESPD Response tenders to.	Information Requirement: tbr92-014. Rule: The economic operator has to specify the Procurement Project Lot the ESPD refers to. Rule scope: (BR-LOT-30)
cac:TenderingCriterion	Associated class	1..n	A tendering criterion describes a rule or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidates to the award decision.	Information Requirement: tbr92-015,tbr92-016. Rule: (see examples further below in this document)
cac:TenderingCriterionResponse	Associated class	1..n	Response of the economic operator to the requirements and questions issued by the buyer in the ESPD Request.	Information Requirement: br92-018, tbr92-007, tbr92-005, tbr92-006. Rule: (see examples further below in this document)
cac:AdditionalDocumentReference	Associated class	0..n	A reference to an additional document associated with this document.	Information Requirement: tbr92-013. Rules: At least two instances of the AdditionalDocumentReference are expected: For procurement procedures above the threshold it is compulsory to make reference to the Contract Notice of the procedure published in TED. See section "Reference to the Contract Notice" for a complete example.* In the ESPD Response it is also compulsory to make reference to the ESPD Request document. Rule scope: Common (BR-COM-10)
cac:Evidence	Associated class	0..n	A reference to an online document available for free in a national or EU database.	Information Requirement: tbr92-017, tbr92-007, tbr92-006. Rule: Used to point at an instance of the cac:Evidence.

Components

Type

Card

Description

Requirements

cbc:UBLVersionID

Identifier

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

Information Requirement: tbr92-020.

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

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

cbc:ProfileExecutionID

Identifier

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

Information Requirement: tbr070-002.

Rule: Compulsory use of the CodeList ProfileExecutionID. Use the value "OP" for th SchemeAgencyID attribute.

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

cbc:ID

Identifier

An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, 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

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

Information Requirement: tbr92-019.

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

cbc:ContractFolderID

Identifier

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

Information Requirement: tbr92-013.

Rule: Try always to use the reference number issued by the buyer. This number in combination with a registered buyer ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure.

Rule scope: (BR-SC-30)

cbc:IssueDate

Date

Date when the document was issued by the buyer.

Information Requirement: tbr92-019.

Rule: Format "YYYY-MM-DD".

cbc:IssueTime

Time

0..1

Time when the document was issued by the buyer.

Information Requirement: tbr92-019.

Rule: Format "hh:mm:ss".

cbc:EconomicOperatorGroupName

Text

0..1

The name of the group that presents a tender to which this economic operator belongs (e.g. the name of a consortium, a joint venture, etc.).

Information Requirement: tbr92-008.

Rule: The leader of the group must take care of ensuring that the name of the group is identical in all the ESPDs of the tender.

Rule scope: (BR-LEAD-10-S10)

cbc:VersionID

Identifier

0..1

The version identifying the content of this document.

Information Requirement: tbr92-020.

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

cbc:PreviousVersionID

Identifier

0..1

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

Information Requirement: tbr92-020.

Rule: None

cbc:ProcedureCode

Code

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

Information Requirement: tbr070-007.

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

cac:ContractingParty

Associated class

The buyer or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU). See section Contracting Body for more specification details.

Information Requirement: tbr92-011.

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

cac:EconomicOperatorParty

Associated class

Any natural or legal person or public entity which offers the execution of works and/or a work, the supply of products or the provision of services on the market. Information about the party submitting the qualification.

Information Requirement: tbr92-001.

Rule: The ESPD Response only refers to one, and only one, economic operator.

Rule scope: Common (BR-RESP-10)

cac:ProcurementProject/cbc:Description

Text

Text describing this procurement project.

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

Rule: Use this component to identify and describe the procurement administrative procedure.

cac:ProcurementProjectLot

Associated class

The procurement project lot or group of lots this ESPD Response tenders to.

Information Requirement: tbr92-014.

Rule: The economic operator has to specify the Procurement Project Lot the ESPD refers to.

Rule scope: (BR-LOT-30)

cac:TenderingCriterion

Associated class

1..n

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

Information Requirement: tbr92-015,tbr92-016.

Rule: (see examples further below in this document)

cac:TenderingCriterionResponse

Associated class

1..n

Response of the economic operator to the requirements and questions issued by the buyer in the ESPD Request.

Information Requirement: br92-018, tbr92-007, tbr92-005, tbr92-006.

Rule: (see examples further below in this document)

cac:AdditionalDocumentReference

Associated class

0..n

A reference to an additional document associated with this document.

Information Requirement: tbr92-013.

Rules: At least two instances of the AdditionalDocumentReference are expected:

For procurement procedures above the threshold it is compulsory to make reference to the Contract Notice of the procedure published in TED. See section "Reference to the Contract Notice" for a complete example.*

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

Rule scope: Common (BR-COM-10)

cac:Evidence

Associated class

0..n

A reference to an online document available for free in a national or EU database.

Information Requirement: tbr92-017, tbr92-007, tbr92-006.

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

XML example

The XML snippet below shows how the beginning of an ESPD Response XML instance looks like. For a complete instance of an ESPD Response XML document see the the example files in the dist/xml folder: or ESPD-Response.xml.

<QualificationApplicationResponse

xmlns="urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationResponse-2"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"

xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions"

xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"

xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"

xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"

xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0" xmlns:util="java:java.util.UUID"

xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:QualificationApplicationResponse-2 ../xsdrt/maindoc/UBL-QualificationApplicationResponse-2.3.xsd">

<!-- The ESPD-EDM is entirely based on OASIS UBL-2.3 -->

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

<!-- The identifier of this document generally generated by the systems that creates the ESPD -->

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

<!-- Indicates whether this document is an original or a copy. In this case the document is the original -->

<cbc:CopyIndicator>false</cbc:CopyIndicator>

<!-- The unique identifier for this instance of the document. Copies of this document should have different UUIDs -->

<cbc:UUID schemeID="ISO/IEC 9834-8:2008 - 4UUID" schemeAgencyID="OP" schemeVersionID="2.0">43afa3db-fbed-4565-9ef7-cd7089698836</cbc:UUID>

<!-- The reference number the buyer assigns to this procurement procedure -->

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

<cbc:IssueDate>2021-02-11+01:00</cbc:IssueDate>

<cbc:IssueTime>16:27:06.248+01:00</cbc:IssueTime>

<!-- The version of the content of this document. If the document is modified the element cbc:PreviousVersionID should be instantiated -->

<cbc:VersionID schemeAgencyID="OP" schemeVersionID="2.0">1.0</cbc:VersionID>

<!-- The type of the procurement procedure; this information is provided by eForms and the concret notice per procedure. e.g. open = In open procedures any interested economic operator may submit a tender in response to a call for competition.-->

<cbc:ProcedureCode listID="procurement-procedure-type" listAgencyID="" listVersionID="">open</cbc:ProcedureCode>

_<!-- ... rest of document removed for brevity -->_

Root elements

XML example

Need Help?

Follow us

Legal

About us

Other services

Contact the EU

Social Media

EU institutions and bodies