Root elements
The table below lists the elements that are expected in the ESPD Request and provides details on the cardinalities and usage of those elements.
|
A note about the Business Rules identifiers From this point on in the document, the tables defining classes and its properties refer frequently to business rules. As stated in the e-Sens BIS document, "[..] business rules are sets of rules that clarify the content of instances by stating mandatory fields, fixed values (like code lists), dependency between fields in the same object and dependency between different objects". Information requirement: Beware that all theses documents do share the same business rule identifiers (e.g. tbrxx-yyy for Business Requirement Identifiers in ESPDInt, and BR-Type-Id#n for the Test Cases technical rules). |
Table 5. Class QualificationApplicationRequest, components required by the ESPD-EDM
| Document name: | QualificationApplicationRequest |
|---|---|
Definition 1: |
"A structured electronic business document for requesting qualification information through an ESPD (conform to an ESPD template). Directive 2014/24/EU, Art. 59." (source: ESPD Request transaction (Trdm070)). Document provided by a buyer defining the exclusion and selection criteria for a given procurement procedure. |
Business rule(s): |
None |
File: |
/ubl-2.3/xsd/maindoc/UBL-QualificationApplicationRequest-2.3.xsd |
| Components | Type | Card | Description | Requirements |
|---|---|---|---|---|
cbc:UBLVersionID |
Identifier |
1 |
Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance. |
Information Requirement: tbr070-002. Rule: Use the value "2.3". Use also "OASIS-UBL-TC" for the schemeAgencyID attribute. Rule scope: Common (BR-OTH-05, 2.BR-OTH-02) |
cbc: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, e.g. a buyer, or the supplier, e.g. an economic operator). An identifier for this document, normally generated by the system that creates the ESPD document, or the organisation responsible for the document (e.g. the buyer, e.g. a buyer, or the supplier, e.g. an economic operator). The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process. |
Information Requirement: tbr070-002. Rule: Compulsory use of schemeAgencyID attribute. Use it to identify the organisation responsible for the document. Rule scope: Common (BR-OTH-02) |
cbc:CopyIndicator |
Indicator |
0..1 |
Indicates whether this document is a copy (true) or not (false). |
Information Requirement: tbr070-002. Rule: It is a good practice to use the CopyIndicator component if the same document is forwarded several times to the same or to different destinations. Use it in combination with the UUID identifier: copies of an ESPD document should be identified with distinct UUIDs. |
cbc:UUID |
Identifier |
1 |
A universally unique identifier that can be used to reference this ESPD document instance. |
Information Requirement: tbr070-002. Rule: This UUID will be used to link the ESPD Response to its corresponding ESPD Request (thus its compulsoriness). Copies of a document must be identified with a different UUID. Compulsory use of schemeAgencyID attribute. Rule scope: BR-OTH-02 |
cbc:ContractFolderID |
Identifier |
1 |
An identifier that is specified by the buyer and used as a reference number for all documents in the procurement process. It is also known as procurement project identifier, procurement reference number or contract folder identifier. A reference to the procurement procedure to which a Qualification request document and the delivered response documents are associated. |
Information Requirement: tbr070-007. Rule: Try always to use the reference number issued by the buyer. This information will be provided in eForms using the same cbc:ContractFolderID, therefore the ESPD should include the same identifier in order to link both models, and shall be globally unique. This number in combination with a registered buyer ID (e.g. the VAT number) results in a universally unique identifier of the procurement procedure. Rule scope: BR-SC-10 |
cbc:IssueDate |
Date |
1 |
Date when the document was issued by the buyer. |
Information Requirement: tbr070-002. Rule: Format "YYYY-MM-DD". |
cbc:IssueTime |
Time |
0..1 |
Time when the document was issued by the buyer. |
Information Requirement: tbr070-002. Rule: Format "hh:mm:ss". |
cbc:VersionID |
Identifier |
0..1 |
The version identifying the content of this document. |
Information Requirement: tbr070-014. Rule: Changes in content should entail the modification of the version identifier and a reference to the previous version. |
cbc:PreviousVersionID |
Identifier |
0..1 |
The version identifying the previous modification of the content of this document. |
Information Requirement: tbr070-014. Rule: None |
cbc:ProcedureCode |
Code |
1 |
The type of the procurement administrative procedure according to the EU Directives. |
Information Requirement: tbr070-007. Rule: For the ESPD, this information will be linked to eForms. And ESPD should include the same procedure code as the one stated in eForms notices. |
cac:ContractingParty |
Associated class |
1 |
The buyer or contracting entity who is buying supplies, services or public works using a tendering procedure as described in the applicable directive (Directives 2014/24/EU, 2014/25/EU). |
Information Requirement: tbr070-01. Rule: UBL-2.3 defines multiple cardinality ContractingParties presumably to allow joint procurements. However the ESPD only expects data about one buyer. The decision was made that in case of joint procurement the data collected in the ESPD would be about the leader of the joint procurement procedure. In ESPD the contracting party information will come from eForms. Which also uses cac:ContractingParty to specify the information about buyer. |
cac:ProcurementProject/ cbc:Description |
Text |
1 |
Text describing this procurement project. |
This element is required in the ESPD, however it should be identical to that provided in eForms. In general the corresponding eForm should feed the corresponding ESPD with the corresponding data. |
cac:TenderingCriterion |
Associated class |
1..n |
A tendering criterion describes a rule or a condition that is used by the contracting body to evaluate and compare tenders by economic operators and which will be used for the exclusion and the selection of candidates to the award decision. |
Information Requirement: tbr70-003, tbr70-009. Rule: (see examples further below in this document) |
cac:TenderingCriterion/ cac:ProcurementProject LotReference/cbc:ID |
Identifier |
0..n |
One or more of the procurement project lots Identifier to which this criterion can be related to. |
Information Requirement: (see section [lot_management]) Rule: This element is mandatory for all Selection Criteria with cardinality 1..n because different Selection Criteria can be associated with different procurement lots. This element is not necessary for exclusion grounds because exclusion grounds are applied to all procurements. |
cac:AdditionalDocumentReference |
Associated class |
0..n |
A reference to an additional document associated with this document. |
Information Requirement: tbr70-007. Rule: For procurement procedures above the threshold it is compulsory to make reference to the Contract Notice of the procedure published in TED. See section "Reference to the Contract Notice" for a complete example. |
