Procedure, Group of Lots, Lot & Part related information
Introduction
Procedure related information exists at the root of the notice as shown in Major reused components above.
Each Groups of Lots, Lot, and Part, has its information in its dedicated "cac:ProcurementProjectLot" element whose identifier is built using the appropriate scheme from Table 1. These technical identifiers are unique within a notice and may not evolve (i.e. the same Lot will have the same technical identifier from the start to the end of the procurement procedure).
| Object | Scheme Name | Scheme | Comment |
|---|---|---|---|
Group of Lots |
LotsGroup |
GLO-XXXX |
XXXX: set of 4 digits. Leading 0 should be used to satisfy the 4 digits format For Procedure without Lots (i.e. with a single "technical" lot), the ID shall be LOT-0000. |
Lot |
Lot |
LOT-XXXX |
|
Part |
Part |
PAR-XXXX |
As Procedures without lots (and PIN without parts) are to be treated technically as a procedure with exactly one lot (or part), there shall always be at least one "cac:ProcurementProjectLot" element. This approach will simplify the processing for all notices by differentiating high level description purpose (i.e. procurement procedure purpose - § II.1 of former forms) from the more specific ones (i.e. Lot specific purpose - § II.2 of former forms)
The extract below illustrates, for a Group of Lots and two Lots, the way the schemes are used to identify the objects whose information (not reported here for readability purpose) is specified.
<cac:ProcurementProjectLot>
<cbc:ID schemeName="LotsGroup">GLO-0001</cbc:ID>
<!-- Interrupted Mark-Up -->
<!-- Information about Group of Lots 1 -->
</cac:ProcurementProjectLot>
<cac:ProcurementProjectLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
<!-- Interrupted Mark-Up -->
<!-- Information about Lot 1 -->
</cac:ProcurementProjectLot>
<cac:ProcurementProjectLot>
<cbc:ID schemeName="Lot">LOT-0002</cbc:ID>
<!-- Interrupted Mark-Up -->
<!-- Information about Lot 2 -->
</cac:ProcurementProjectLot>Regarding Group of Lots:
-
The Buyer defines Groups of Lots at the start of the whole Procurement Procedure;
-
Groups shall not coexist with Parts[1];
-
They shall not contain less than two Lots;
-
The group composition (i.e. the exhaustive list of Lots a group contains) is specified in the Tendering Terms at root level using child elements of "cac:LotDistribution" as described in Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition;
-
Other information about a Group of Lots is located separately from its composition, under a dedicated "cac:ProcurementProjectLot" element;
-
With information already specified at Lots level, fewer data are needed for Group of Lots.
Information relative to each object
As illustrated in Major reused components, each object ("Procedure", "Group of Lots", "Lot" and "Part") has its information encoded in 3 main blocks: "TenderingTerms", "TenderingProcess" and "ProcurementProject".
The following tables highlight, for each of them, the main information covered by each block. This information is purely indicative as the content evolves according to the stages (e.g. some information relevant for a contract notice may become irrelevant for a contract award notice, while other information is only known after awarding a Lot).
| Block | Topics |
|---|---|
Tendering Terms |
|
Tendering Process |
|
Procurement Project |
|
(*) Internal Identifier assigned by the Contracting Authority. It is not required to be globally unique |
|
| Block | Topics |
|---|---|
Tendering Terms |
|
Tendering Process |
|
Procurement Project |
|
| Block | Topics |
|---|---|
Tendering Terms |
|
Tendering Process |
|
Procurement Project |
|
| Block | Topics |
|---|---|
Tendering Terms |
* Tenderer and execution requirements. |
Tendering Process |
|
Procurement Project |
|
Tendering terms
Tendering terms group information as diverse as EU funding, exclusion grounds, reserved participation/execution.
Table 6 lists, in their order of appearance in the XML, each of the eForms Business Terms that have a corresponding component in the "cac:TenderingTerms" element, along with a short description, indicative cardinalities[2] and the relative XPATH to the node(s) used to mark it.
Cardinalities are expressed using the following notation:
? |
Optional (0 or 1) |
* |
Optional repeatable (0 or more) |
1 |
Mandatory & unique (only one) |
+ |
Mandatory repeatable (1 or more) |
— |
Not allowed (0) |
(*) |
Table notes |
eForms BT |
Details |
Procedure |
PIN |
CN |
CAN |
XSD element |
||||
G.Lot |
Lot |
Part |
G.Lot |
Lot |
G.Lot |
Lot |
||||
Clean Vehicle Directive (*) |
||||||||||
Clean Vehicle Directive (BT-717) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
CVD Contract Type (BT-735) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
|---|---|---|---|---|---|---|---|---|---|---|
EU Funds Information (*) |
||||||||||
EU Funds Financing Identifier (BT-5010) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
EU Funds Programme (BT-7220) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
EU Funds Details (BT-6140) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Selection Criteria (*) |
||||||||||
Selection Criteria Type (BT-747) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Selection Criteria Name (BT-749) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Selection Criteria Description (BT-750) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Selection Criteria Used (BT-748) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Second Stage Invite |
||||||||||
Selection Criteria Second Stage Invite (BT-40) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Selection Criteria Second Stage Invite Number Weight (BT-7531) |
— |
— |
* |
— |
— |
* |
— |
— |
|
|
Selection Criteria Second Stage Invite Number Threshold (BT-7532) |
— |
— |
* |
— |
— |
* |
— |
— |
|
|
Selection Criteria Second Stage Invite Number (BT-752) |
— |
— |
* |
— |
— |
* |
— |
— |
|
|
Misc. terms (*) |
||||||||||
Variants (BT-63) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
EU Funds (BT-60) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Performing Staff Qualification (BT-79) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Recurrence (BT-94) |
— |
— |
— |
— |
— |
? |
— |
— |
|
|
Recurrence Description (BT-95) |
— |
— |
— |
— |
— |
? |
— |
— |
|
|
Security Clearance Deadline (BT-78) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Multiple Tenders (BT-769) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Financial guarantee (**) |
||||||||||
Guarantee Required (BT-751) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Guarantee Required Description (BT-75) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Procurement documents (**) |
||||||||||
Documents Restricted Justification (BT-707) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
Documents Official Language (BT-708) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
Documents Unofficial Language (BT-737) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
AND |
Documents Restricted (BT-14) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
Documents URL (BT-15) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
Documents Restricted URL (BT-615) |
Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
Financial terms (**) |
||||||||||
Terms Financial (BT-77) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Participation, exclusion & legal (**) |
||||||||||
Cross Border Law (BT-09) |
* |
— |
— |
— |
— |
— |
— |
— |
|
|
Other Legal Basis (BT-01) — Local - Code |
* |
— |
— |
— |
— |
— |
— |
— |
|
|
Other Legal Basis (BT-01) — Local - Text |
* |
— |
— |
— |
— |
— |
— |
— |
|
|
Exclusion Grounds (BT-67) |
? |
— |
— |
— |
— |
— |
— |
— |
AND |
|
Reserved Participation (BT-71) |
— |
— |
+ |
— |
— |
+ |
— |
— |
|
|
Tenderer requirement (**) |
||||||||||
Tenderer Legal Form (BT-761) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Tenderer Legal Form Description (BT-76) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Late Tenderer Information (BT-771) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Late Tenderer Information Description (BT-772) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Subcontracting obligations (Dir. 81 only) (**) |
||||||||||
Subcontracting Tender Indication (BT-651) |
— |
— |
* |
— |
— |
+ |
— |
— |
|
|
Subcontracting Obligation (BT-65) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Subcontracting Obligation Maximum (BT-729) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Subcontracting Obligation Minimum (BT-64) |
— |
— |
? |
— |
— |
1 |
— |
— |
|
|
Execution requirements (**) |
||||||||||
Reserved Execution (BT-736) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Electronic Invoicing (BT-743) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Non Disclosure Agreement (BT-801) |
Non Disclosure Agreement Indicator and Description (BT-801, BT-802) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Non Disclosure Agreement Description (BT-802) |
Non Disclosure Agreement Indicator and Description (BT-801, BT-802) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Terms Performance (BT-70) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Submission Electronic Catalog (BT-764) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Submission Electronic Signature (BT-744) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Awarding consequences (**) |
||||||||||
Following Contract (BT-41) |
— |
— |
— |
— |
— |
+ |
— |
— |
|
|
Jury Decision Binding (BT-42) |
— |
— |
— |
— |
— |
+ |
— |
— |
|
|
No Negotiation Necessary (BT-120) |
— |
— |
— |
— |
— |
+ |
— |
— |
|
|
Award Criteria (**) |
||||||||||
Award Criteria Order Justification (BT-733) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criteria Complicated (BT-543) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Number Weight (BT-5421) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Number Fixed (BT-5422) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Number Threshold (BT-5423) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Number (BT-541) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Type (BT-539) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Name (BT-734) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Award Criterion Description (BT-540) |
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
Jury (**) |
||||||||||
Jury Member Name (BT-46) |
— |
— |
— |
— |
— |
* |
— |
— |
|
|
Prize information (CN Design per prize) (**) |
||||||||||
Prize Rank (BT-44) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Value Prize (BT-644) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Rewards Other (BT-45) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Tenders processing parties (**) |
||||||||||
_Organization providing additional information _ (Organization subrole) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Organization providing offline access to the procurement documents |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Organization receiving tenders / Requests to participate (Organization subrole) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Submission URL (BT-18) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Organization processing tenders / Requests to participate (Organization subrole) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Tender validity (**) |
||||||||||
Tender Validity Deadline (BT-98) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Appeal terms (**) |
||||||||||
Review Deadline Description (BT-99) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
*Review organization * (Organization role) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Organization providing more information on the time limits for review (Organization subrole) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Mediation Organization (Organization role) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Tendering language (**) |
||||||||||
Submission Language (BT-97) |
— |
— |
+ |
— |
— |
+ |
— |
— |
|
|
Lots distribution (**) |
||||||||||
Lots Max Awarded (BT-33) |
Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition |
? |
— |
— |
— |
— |
— |
— |
— |
|
Lots Max Allowed (BT-31) |
Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition |
? |
— |
— |
— |
— |
— |
— |
— |
|
Group definition |
||||||||||
Group Identifier (BT-330) |
Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition |
? |
— |
— |
— |
— |
— |
— |
— |
|
Group Lot Identifier (BT-1375) |
Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition |
? |
— |
— |
— |
— |
— |
— |
— |
|
Post award process (**) |
||||||||||
Electronic Ordering (BT-92) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Electronic Payment (BT-93) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Participants (**) |
||||||||||
Participant Name (BT-47) |
— |
— |
— |
— |
— |
? |
— |
— |
|
|
Security Clearance (**) |
||||||||||
Security Clearance Code (BT-578) |
Security Clearance (BT-578), Deadline (BT-78) & Description (BT-732) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Security Clearance Description (BT-732) |
Security Clearance (BT-578), Deadline (BT-78) & Description (BT-732) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Contexts: (*) (**) |
||||||||||
CVD information at Lot level
At Lot level, only the following information is expected:
-
Clean Vehicle Directive (BT-717, field BT-717-Lot), and
-
CVD Contract Type (BT-735, field BT-735-Lot)
The Clean Vehicle Directive Business Term is used to specify whether this directive applies or not. When used, it should contain either of the two values "true" or "false". When BT-717 exists and has its value set to true, the CVD Contract Type may also be specified using one of the values of the CVD Contract Type codelist. This BT is repeatable.
A sample mark-up is provided below for a case where the directive applies and procurement concerns "Vehicle purchase, lease or rent" as well as "Other service contract" (the structure occurs in the extensions of the TenderingTerms of the given Lot):
<efac:StrategicProcurement>
<efbc:ApplicableLegalBasis listName="cvd-scope">true</efbc:ApplicableLegalBasis>
<efac:StrategicProcurementInformation>
<efbc:ProcurementCategoryCode listName="cvd-contract-type">oth-serv-contract</efbc:ProcurementCategoryCode>
</efac:StrategicProcurementInformation>
<efac:StrategicProcurementInformation>
<efbc:ProcurementCategoryCode listName="cvd-contract-type">veh-acq</efbc:ProcurementCategoryCode>
</efac:StrategicProcurementInformation>
</efac:StrategicProcurement>This information is also possible at Lot level for Result notices, especially if the Lot is listed but not awarded.
EU Funds (BG-61)
In all notices, the element "cbc:FundingProgramCode" is used per Lot to specify whether it is foreseen or not to have the procurement project partly financed with EU Funds (BT-60). The value "eu-funds" is used to specify the intention to get the project partly funded with EU funds (i.e. "true" value for the indicator), and the value "no-eu-funds" is used to indicate that no EU funds is foreseen for financing the procurement project (i.e. "false" value for the indicator).
<cbc:FundingProgramCode listName="eu-funded">eu-funds</cbc:FundingProgramCode>In "PIN time limit" and Competition notices, when EU Funds (BT-60) indicates that EU Funds are involved in the procurement, EU Funds Information (BG-614) may be given; this covers:
-
EU Funds Programme (BT-7220),
-
EU Funds Financing Identifier (BT-5010), and
-
EU Funds Details (BT-6140).
EU Funds Information (BG-614) may be repeated for each source of funding. Within each BG-614, at least one of BT-7220 or BT-5010 shall be specified. The content of EU Funds Programme (BT-7220) must match one of the codes of the eu-programme codelist. The content of the EU Funds Financing Identifier shall be the most concrete possible (e.g. grant agreement number, national identifier or project acronym). EU Funds Details (BT-6140) may only be provided once for each BG-614.
<efac:Funding>
<efbc:FinancingIdentifier>CON_PRO-123/ABC</efbc:FinancingIdentifier>
<cbc:Description languageID="ENG">This project will be financed ...</cbc:Description>
<cbc:Description languageID="FRA">Ce projet sera financé ...</cbc:Description>
</efac:Funding>
<efac:Funding>
<efbc:FinancingIdentifier>CAS-LEO/2022/PDM</efbc:FinancingIdentifier>
<cbc:FundingProgramCode listName="eu-proramme">ERDF_2021</cbc:FundingProgramCode>
<cbc:Description languageID="ENG">This local project ...</cbc:Description>
<cbc:Description languageID="FRA">Ce projet local ...</cbc:Description>
</efac:Funding>Selection criteria
Selection criteria apply at "Lot" level. There are different types of selection criteria (BT-747), and the main ones are "Technical", "Financial" and "Professional". Each of these categories is respectively encoded with the "tp-abil", "ef-stand" and "sui-act" value of the selection-criterion codelist[3]. This information is marked using the "cbc:CriterionTypeCode" element. Multiple instances of Selection Criteria using the same type may be used.
A name (BT-749) may be given to a single selection criterion (or to a group of them). When specified, the name, of type text, must be provided in all linguistic versions identified as official languages for the notice. Information is marked with the "cbc:Name" element.
The Selection Criteria Used (BT-748) indicates whether the selection criteria are "used", "not used" or "not yet known". This is marked using the "cbc:CalculationExpressionCode" element. Codes are from the usage codelist. The "nyk" value to express that the use of the criteria/criterion is "not yet known", is only allowed for "PIN time limit" and "PIN CFC" notices.
If the "used" value is used for BT-748, Selection Criteria Description (BT-750) shall be provided in the "cbc:Description" element. This includes:
-
minimum requirements,
-
required information (e.g. self-declaration, documentation) and
-
criteria usage for selection of candidates to be invited for the second stage of the procedure (if a maximum number of candidates was set).
The indication that the criteria/criterion is used for selection of candidates for a second stage is given by the presence of the element "efbc:SecondStageIndicator" (BT-40), with its value set to "true". This element should be set to 'false' when the criteria/criterion is not used for selection of candidates for a second stage. If the element is set to 'true', then details about the criteria/criterion associated numbers may be provided (BT-7531, BT-7532, BT-752).
These details are reported in the "efac:CriterionParameter" element. The type of criterion is indicated by the "efbc:ParameterCode" element, with BT-7531 Selection Criteria Second Stage Invite Number Weight using one of the values from the number-weight codelist, and BT-7532 Selection Criteria Second Stage Invite Number Threshold using one of the values from the number-threshold codelist. The "efbc:ParameterNumeric" element shall hold the value associated with the criterion.
When shall second stage information be reported?
-
When this is applicable, also information is mandatory for CN General under Directive 24
-
If Procedure Type (BT-105) is[4]:
-
"open", "other single stage procedure" or "negotiated without prior call for competition", then the 2nd stage information is not allowed,
-
different from "open", "other single stage procedure" and "negotiated without prior call for competition", then the 2nd stage information may/shall be reported.
-
<efac:SelectionCriteria>
<cbc:CriterionTypeCode listName="selection-criterion">ef-stand</cbc:CriterionTypeCode>
<cbc:Name languageID="ENG">Minimum Turnover</cbc:Name>
<cbc:Name languageID="FRA">Chiffre d'affaire (HT) minimal</cbc:Name>
<cbc:Description languageID="ENG">Turnover over contract value rate</cbc:Description>
<cbc:Description languageID="FRA">Rapport Chiffre d'affaire sur valeur du contrat.</cbc:Description>
<cbc:CalculationExpressionCode listName="usage">used</cbc:CalculationExpressionCode>
<efbc:SecondStageIndicator>true</efbc:SecondStageIndicator>
<efac:CriterionParameter>
<efbc:ParameterCode listName="number-threshold">min-score</efbc:ParameterCode>
<efbc:ParameterNumeric>2</efbc:ParameterNumeric>
</efac:CriterionParameter>
</efac:SelectionCriteria>
<efac:SelectionCriteria>
<cbc:CriterionTypeCode listName="selection-criterion">tp-abil</cbc:CriterionTypeCode>
<cbc:Name languageID="ENG">Experience with similar projects</cbc:Name>
<cbc:Name languageID="FRA">Expérience avec des projets similaires</cbc:Name>
<cbc:Description languageID="ENG">Minimum number of years of experience on similar projects</cbc:Description>
<cbc:Description languageID="FRA">Nombre minimal d'années d'expérience avec des projets similaires</cbc:Description>
<cbc:CalculationExpressionCode listName="usage">used</cbc:CalculationExpressionCode>
<efbc:SecondStageIndicator>true</efbc:SecondStageIndicator>
<efac:CriterionParameter>
<efbc:ParameterCode listName="number-threshold">min-score</efbc:ParameterCode>
<efbc:ParameterNumeric>5</efbc:ParameterNumeric>
</efac:CriterionParameter>
</efac:SelectionCriteria>Variants (BT-63)
The Variants business term is used to specify whether tenderers are "allowed", "not allowed" or "required" to provide tenders fulfilling the needs a different way than the one exposed in the procurement documents. Code values are listed in the permission codelist and the BT is expressed as follows:
<cbc:VariantConstraintCode listName="permission">allowed</cbc:VariantConstraintCode>Performing Staff Qualification (BT-79)
To indicate whether supporting information for staff qualification shall be provided, or not, and when (e.g. with the tender, with the Request To Participate, …); the requirement shall be marked as follows:
<cbc:RequiredCurriculaCode listName="requirement-stage">t-requ</cbc:RequiredCurriculaCode>Allowed values are those listed in the requirement-stage codelist.
Recurrence (BT-94) and Recurrence Description (BT-95)
For QS and CN Notices (design excluded), the Recurrence (BT-94) may be used to identify a Procurement whose purpose is likely to also be included in another procedure in the foreseeable future. Any additional information about recurrence (e.g. estimated timing) may be reported using the Recurrence Description (BT-95). The "cbc:RecurringProcurementIndicator" has 2 possible values "true" and "false" to indicate that this respectively is or is not a recurring procurement (i.e. a procurement that is likely to be included later in another procedure).
<cbc:RecurringProcurementIndicator>true</cbc:RecurringProcurementIndicator>
<cbc:RecurringProcurementDescription languageID="ENG">The current procurement ...</cbc:RecurringProcurementDescription>
<cbc:RecurringProcurementDescription languageID="FRA">Le marché courant ...</cbc:RecurringProcurementDescription>Clearance Deadline (BT-78)
The time limit by which tenderers not holding the required security clearances may obtain them is identified with the Business Term Security Clearance Deadline (BT-78) and marked with the element "cbc:LatestSecurityClearanceDate":
<cbc:LatestSecurityClearanceDate>2019-11-15+01:00</cbc:LatestSecurityClearanceDate>Multiple Tenders (BT-769)
The Multiple Tenders business term allows to specify for a given Lot whether a tenderer may submit more than one tender ("allowed") or not ("not-allowed"). This information is marked using the "cbc:MultipleTendersCode" for which only the two previous values of the permission codelist are accepted.
<cbc:MultipleTendersCode listName="permission">allowed</cbc:MultipleTendersCode>Financial guarantee (BT-751, BT-75)
Whether a provisional guarantee (BT-751) is required, or not, shall be specified using the element "cbc:GuaranteeTypeCode" with "tender-guarantee-required" as a "listName" attribute and the appropriate indicator (i.e. true/false); when "true", its description (BT-75) shall also be provided:
<cac:RequiredFinancialGuarantee>
<cbc:GuaranteeTypeCode listName="tender-guarantee-required">true</cbc:GuaranteeTypeCode>
<cbc:Description languageID="ENG">Bids shall include a bid security (Provisional Bank Guarantee or bid bond), ...</cbc:Description>
<cbc:Description languageID="FRA">Les offres doivent comprendre une garantie de soumission (garantie bancaire provisoire ou caution de soumission), ...</cbc:Description>
</cac:RequiredFinancialGuarantee>Procurement documents (BT-14, BT-15, BT-615, BT-707, BT-708, BT-737)
The URL to procurement documents BT-15 (or to information on documents with controlled accesses BT-615) is marked using the "cbc:URI" element.
The identifier "cbc:ID" is mandatory and shall not be empty. There is no predefined structure or list and any relevant value may be used so long it does not exceed the string length limitation.
The document type code value provides the background reason (BT-707) for restricted access ("restricted-document" value of the "cbc:DocumentType" element, BT-14).
Possible "cbc:DocumentTypeCode" values are listed in the communication-justification codelist. When access is not restricted, cbc:DocumentType shall have the "non-restricted-document" value and the element cbc:DocumentTypeCode shall not be used.
When there is a need to specify the linguistic version (BT-708 or BT-737), then the "cbc:LanguageID" element has to be used with values from the language codelist. This element is not repeatable and when multiple linguistic versions have to be referenced, the whole block "cac:CallForTendersDocumentReference" has to be repeated.
The status of a given linguistic version may also be specified using the "cbc:DocumentStatusCode" element with either of the two values: "official" (for BT-708) or "non-official" (for BT-737).
<cac:CallForTendersDocumentReference>
<cbc:ID>20210521/CTFD/ENG/7654-02</cbc:ID>
<cbc:DocumentTypeCode listName="communication-justification">ipr-iss</cbc:DocumentTypeCode>
<cbc:DocumentType>restricted-document</cbc:DocumentType>
<cbc:LanguageID>ENG</cbc:LanguageID>
<cbc:DocumentStatusCode listName="linguistic-status">official</cbc:DocumentStatusCode>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://mywebsite.com/proc/2019024/accessinfo</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:CallForTendersDocumentReference>Financial terms (BT-77)
Financing and payment terms, or reference to any provision governing them, is marked with the "cbc:Note" child of the "cac:PaymentTerms" element.
<cac:PaymentTerms>
<cbc:Note languageID="ENG">Any payment ...</cbc:Note>
<cbc:Note languageID="FRA">Tout paiement ...</cbc:Note>
</cac:PaymentTerms>Cross Border Law (Procedure) (BT-09)
To specify applicable cross border law for the procurement involving buyers from different countries, the information shall be marked specifying "CrossBorderLaw" in the "cbc:ID" element with the appropriate information about the legislation reported in the "cbc:DocumentDescription" text field:
<cac:ProcurementLegislationDocumentReference>
<cbc:ID>CrossBorderLaw</cbc:ID>
<cbc:DocumentDescription languageID="ENG">Directive XYZ on Cross Border ...</cbc:DocumentDescription>
<cbc:DocumentDescription languageID="FRA">La directive XYZ sur les échanges ...</cbc:DocumentDescription>
</cac:ProcurementLegislationDocumentReference>Other Legal Basis (BT-01)
Local legal basis that apply to the procurement may also be specified. It shall be marked the same way as Cross Border Law:
-
when an identifier exists, specifying the Identifier (e.g. ELI, celex) in the BT-01(c)-Procedure field ("cbc:ID" element) in addition to the legislation description in the BT-01(d)-Procedure field ("cbc:DocumentDescription" element):
<cac:ProcurementLegislationDocumentReference>
<cbc:ID>http://data.europa.eu/eli/dir/2014/24/oj</cbc:ID>
<cbc:DocumentDescription languageID="ENG">Directive XYZ applies ...</cbc:DocumentDescription>
<cbc:DocumentDescription languageID="FRA">La directive XYZ ...</cbc:DocumentDescription>
</cac:ProcurementLegislationDocumentReference>-
Or, when no identifier is available, specifying the predefined text "LocalLegalBasis" in the BT-01(e)-Procedure field ("cbc:ID" element) in addition to a short description of applicable law(s) in the BT-01(f)-Procedure field ("cbc:DocumentDescription" element): :
<cac:ProcurementLegislationDocumentReference>
<cbc:ID>LocalLegalBasis</cbc:ID>
<cbc:DocumentDescription languageID="ENG">Directive XYZ applies ...</cbc:DocumentDescription>
<cbc:DocumentDescription languageID="FRA">La directive XYZ ...</cbc:DocumentDescription>
</cac:ProcurementLegislationDocumentReference>Exclusion Grounds (BT-67)
Exclusion Grounds (BT-67) refer to criteria that, not met and justified (even with self-declaration), lead to the tenderer exclusion. This information is expected as a code from the technical codelist "exclusion-ground" tailored from the criterion codelist. More than one exclusion ground may be used, each in a dedicated "cac:SpecificTendererRequirement" element, a given code may however be used only once. Additionally to the code, a text ("cbc:Description") may be used.
<cac:TendererQualificationRequest>
<cac:SpecificTendererRequirement>
<cbc:TendererRequirementTypeCode listName="exclusion-ground">crime-org</cbc:TendererRequirementTypeCode>
<cbc:Description languageID="ENG">Applicants not satisfying ...</cbc:Description>
<cbc:Description languageID="FRA">Les candidats ne satisfaisant pas ...</cbc:Description>
</cac:SpecificTendererRequirement>
<cac:SpecificTendererRequirement>
<cbc:TendererRequirementTypeCode listName="exclusion-ground">fraud</cbc:TendererRequirementTypeCode>
<cbc:Description languageID="ENG">Applicants not satisfying ...</cbc:Description>
<cbc:Description languageID="FRA">Les candidats ne satisfaisant pas ...</cbc:Description>
</cac:SpecificTendererRequirement>
<!-- interrupted MarkUp -->
</cac:TendererQualificationRequest>Reserved Participation (BT-71)
Reserved Participation (BT-71) expresses a participation restriction; only tenderers with specific social missions may tender. Information is encoded with the "cbc:TendererRequirementTypeCode" element. Possible values are from the reserved procurement codelist. When multiple restrictions apply, the parent "cac:SpecificTendererRequirement" has to be repeated as many times as required.
When no Reserved Procurement requirements exist, while the business term is mandatory, the value "none" shall be used and no other "Reserved Participation" requirement shall be specified.
<cac:TendererQualificationRequest>
<cac:SpecificTendererRequirement>
<cbc:TendererRequirementTypeCode listName="reserved-procurement">res-pub-ser</cbc:TendererRequirementTypeCode>
</cac:SpecificTendererRequirement>
<cac:SpecificTendererRequirement>
<cbc:TendererRequirementTypeCode listName="reserved-procurement">res-ws</cbc:TendererRequirementTypeCode>
</cac:SpecificTendererRequirement>
</cac:TendererQualificationRequest>Tenderer requirements (BT-76, BT-761, BT-771, BT-772)
The existence of a constraint on a legal form that a group of tenderers awarded a contract has to take (BT-761), is marked with the "cbc:CompanyLegalFormCode" element. It is expressed using either of the two values "true" or "false" and specifying "required" as a "listName" attribute. When the value is "true", the Tenderer Legal Form Description (BT-76) is provided and marked using the "cbc:CompanyLegalForm" element.
Information about the tolerance for supporting documents provision after tender submission (BT-771), is marked with the element "cbc:TendererRequirementTypeCode", a code from the codelist missing-info-submission, and detailed text using "cbc:Description" (BT-772).
<cac:TendererQualificationRequest>
<cbc:CompanyLegalFormCode listName="required">true</cbc:CompanyLegalForm>
<cbc:CompanyLegalForm languageID="ENG">The tenderer ...</cbc:CompanyLegalForm>
<cbc:CompanyLegalForm languageID="FRA">Le soumissionaire ...</cbc:CompanyLegalForm>
</cac:TendererQualificationRequest>
<cac:TendererQualificationRequest>
<cac:SpecificTendererRequirement>
<cbc:TendererRequirementTypeCode listName="missing-info-submission">late-all</cbc:TendererRequirementTypeCode>
<cbc:Description languageID="ENG">Economic operators who ...</cbc:Description>
<cbc:Description languageID="FRA">Les opérateurs économiques qui ...</cbc:Description>
</cac:SpecificTendererRequirement>
</cac:TendererQualificationRequest>Subcontracting obligations (BT-64, BT-65, BT-651, BT-729)
These Business Terms apply only for Directive 2009/81 notices of notice types "PIN time limit" and "CN general".
The Subcontracting Obligation (BT-65) expresses, with the "cbc:SubcontractingConditionsCode" element, using a code from the subcontracting-obligation codelist, the obligations the contractor will have to follow concerning subcontracting. When the code value is "subc-min"[5], the Subcontracting Obligation Minimum (BT-64) and Subcontracting Obligation Maximum (BT-729) shall be specified; when the code value is "subc-chng"[6], "subc-oblig-2009-81" or "none", no other element shall be associated at the same level.
Subcontracting Obligation Maximum (BT-729) and Subcontracting Obligation Minimum (BT-64) are respectively marked using the "cbc:MaximumPercent" and "cbc:MinimumPercent" with decimal values.
The expression of multiple complementary obligations is performed with multiplication of the parent element "cac:AllowedSubcontractTerms".
<cac:AllowedSubcontractTerms>
<cbc:SubcontractingConditionsCode listName="subcontracting-obligation">subc-chng</cbc:SubcontractingConditionsCode>
</cac:AllowedSubcontractTerms>
<cac:AllowedSubcontractTerms>
<cbc:SubcontractingConditionsCode listName="subcontracting-obligation">subc-min</cbc:SubcontractingConditionsCode>
<cbc:MaximumPercent>45.5</cbc:MaximumPercent>
<cbc:MinimumPercent>25.5</cbc:MinimumPercent>
</cac:AllowedSubcontractTerms>Subcontracting Tender Indication (BT-651) provides information about subcontracting information a tenderer shall specify in its tender; this is marked with the "efbc:TenderSubcontractingRequirementsCode" element. Allowed code values are listed in the subcontracting-indication codelist.
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:TenderSubcontractingRequirements>
<efbc:TenderSubcontractingRequirementsCode listName="subcontracting-indication">subc-oblig</efbc:TenderSubcontractingRequirementsCode>
</efac:TenderSubcontractingRequirements>
<efac:TenderSubcontractingRequirements>
<efbc:TenderSubcontractingRequirementsCode listName="subcontracting-indication">subj-noblig</efbc:TenderSubcontractingRequirementsCode>
</efac:TenderSubcontractingRequirements>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>Reserved Execution (BT-736)
This business term is used to specify whether the procurement execution is reserved or not, or whether this is not yet known. The business term must be specified everywhere mandated by the Regulation. The "listName" attribute of the "cbc:ExecutionRequirementCode" element should be set to "reserved-execution". The possible values for this element are the codes of the applicability codelist (i.e. "yes", "no" or "not-known"):
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="reserved-execution">not-known</cbc:ExecutionRequirementCode>
</cac:ContractExecutionRequirement>Electronic Invoicing (BT-743)
Use of e-invoicing for the contract execution is encoded with the "cbc:ExecutionRequirementCode" element, having its "listName" attribute set to "einvoicing", the code value selected from the permission codelist:
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="einvoicing">required</cbc:ExecutionRequirementCode>
</cac:ContractExecutionRequirement>Non Disclosure Agreement Indicator and Description (BT-801, BT-802)
Use of a Non Disclosure Agreement for the contract execution may be encoded with the "cbc:ExecutionRequirementCode" element, having its "listName" attribute set to "nda", and either the 'true' or 'false' value. When the value is set to 'true', further details may be provided as text in the cbc:Description element.
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="nda">true</cbc:ExecutionRequirementCode>
<cbc:Description languageID="ENG">A Non Disclosure Agreement will need to ...</cbc:Description>
</cac:ContractExecutionRequirement>Terms Performance (BT-70)
The main information about the performance of the contract (e.g. intermediary deliverables, compensation for damages, intellectual property rights) shall be marked:
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="conditions">performance</cbc:ExecutionRequirementCode>
<cbc:Description languageID="ENG">During execution of the contract, ...</cbc:Description>
<cbc:Description languageID="FRA">Pendant l'exécution du contrat, ...</cbc:Description>
</cac:ContractExecutionRequirement>Submission Electronic Catalogue (BT-764)
The possibility to submit (parts of) tenders as electronic catalogues is specified with the "cbc:ExecutionRequirementCode" element, having its "listName" attribute set to "ecatalog-submission", with the value selected from the permission codelist:
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="ecatalog-submission">allowed</cbc:ExecutionRequirementCode>
</cac:ContractExecutionRequirement>Submission Electronic Signature (BT-744)
Whether or not the use of electronic signature[7] is required, is indicated by a "true"/"false" value in the "cbc:ExecutionRequirementCode" element, having its "listName" attribute set to "esignature-submission":
<cac:ContractExecutionRequirement>
<cbc:ExecutionRequirementCode listName="esignature-submission">false</cbc:ExecutionRequirementCode>
</cac:ContractExecutionRequirement>Lots Max Awarded (BT-33), Lots Max Allowed (BT-31) & Group of Lots definition
Regarding Lots distribution, relevant information is:
-
The maximum number of Lots that can be awarded to one economic operator,
-
The maximum number of Lots that one economic operator can submit a tender for,
-
The grouping of Lots.
Restrictions and Group of Lots should only be specified when applicable.
<cac:LotDistribution>
<cbc:MaximumLotsAwardedNumeric>4</cbc:MaximumLotsAwardedNumeric>
<cbc:MaximumLotsSubmittedNumeric>6</cbc:MaximumLotsSubmittedNumeric>
<cac:LotsGroup>
<!-- Definition of Group of Lots 1 -->
<cbc:LotsGroupID schemeName="LotsGroup">GLO-0001</cbc:LotsGroupID>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeName="Lot">LOT-0002</cbc:ID>
</cac:ProcurementProjectLotReference>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeName="Lot">LOT-0005</cbc:ID>
</cac:ProcurementProjectLotReference>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeName="Lot">LOT-0006</cbc:ID>
</cac:ProcurementProjectLotReference>
</cac:LotsGroup>
<cac:LotsGroup>
<!-- Definition of Group of Lots 2 -->
<cbc:LotsGroupID schemeName="LotsGroup">GLO-0002</cbc:LotsGroupID>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeName="Lot">LOT-0002</cbc:ID>
</cac:ProcurementProjectLotReference>
<cac:ProcurementProjectLotReference>
<cbc:ID schemeName="Lot">LOT-0005</cbc:ID>
</cac:ProcurementProjectLotReference>
</cac:LotsGroup>
</cac:LotDistribution>Considerations:
-
The "maximum number of tenderable Lots per economic operator" shall be equal or greater than the "maximum number of awardable Lots per economic operator";
-
No Group of Lots may contain more Lots than the maximum number of awardable Lots per economic operator; otherwise the Group of Lots would not be awardable;
-
A Group of Lots shall only contain Lots (i.e. no Group of Lots);
-
A "PIN only" notice shall not have any Group of Lots;
-
Any Group of Lots shall have at least 2 Lots;
-
Two different Groups of Lots may contain the same Lot; in such a situation, these will compete at the time of tenders evaluation;
Awarding consequences (BT-41, BT-42, BT-120)
Awarding consequences like:
-
Following Contract (BT-41)
-
Jury Decision Binding (BT-42)
-
No Negotiation Necessary (BT-120)
Shall be respectively marked using the indicators:
-
cbc:FollowupContractIndicator,
-
cbc:BindingOnBuyerIndicator, and
-
cbc:NoFurtherNegotiationIndicator.
<cbc:FollowupContractIndicator>true</cbc:FollowupContractIndicator>
<cbc:BindingOnBuyerIndicator>true</cbc:BindingOnBuyerIndicator>
<cbc:NoFurtherNegotiationIndicator>true</cbc:NoFurtherNegotiationIndicator>The elements must be specified everywhere mandated by the Regulation. To indicate that a particular awarding consequence does not apply, the respective element should have the value "false".
Award Criteria (BT-539, BT-540, BT-541, BT-543, BT-733, BT-734, BT-5421, BT-5422, BT-5423)
The way Award criteria is marked has some similarities with Selection criteria (cf. Selection criteria), they however have some additional dedicated elements. Related Award Criteria are specified in a "cac:AwardingCriterion" element.
Each criteron of an award criteria is specified using a "cac:SubordinateAwardingCriterion" element. For any criterion of the award criteria, the type (BT-539) and description (BT-540) shall be provided; the name (BT-734) is however optional. The type of award criterion shall be one of the award-criterion-type codelist.
This criterion may be quantified in one or more dimensions, each within an "efac:AwardCriterionParameter" element. The dimension is specified with the "efbc:ParameterCode" element, and the "efbc:ParameterNumeric" element shall hold the value associated with that dimension (Award Criterion Number, BT-541).
The number dimension shall be:
-
for weights (BT-5421), a code from the number-weight codelist;
-
for fixed values (BT-5422), a code from the number-fixed codelist; and
-
for threshold values (BT-5423), a code from the number-threshold codelist.
The node that encapsulates the Award Criterion information (i.e. cac:SubordinateAwardingCriterion) is repeatable. For a given Lot or Group of lots, Award Criteria (i.e. cac:AwardingCriterion) is not repeatable and shall contain each and every Award Criterion used for score computation so that expressed weighting may be properly understood and, in case percentage is used, the 100% rule verified (i.e. sum of the weighting percentages shall equal 100%).
<cac:AwardingCriterion>
<cac:SubordinateAwardingCriterion>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-weight">per-exa</efbc:ParameterCode>
<efbc:ParameterNumeric>60</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">price</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Price</cbc:Name>
<cbc:Name languageID="FRA">Prix</cbc:Name>
<cbc:Description languageID="ENG">The price score contributes for 60 % ...</cbc:Description>
<cbc:Description languageID="FRA">Le score du prix participe pour 60 % ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
<cac:SubordinateAwardingCriterion>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-weight">per-exa</efbc:ParameterCode>
<efbc:ParameterNumeric>40</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">quality</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Quality</cbc:Name>
<cbc:Name languageID="FRA">Qualité</cbc:Name>
<cbc:Description languageID="ENG">The quality score contributes for 40 % ...</cbc:Description>
<cbc:Description languageID="FRA">Le score qualité participe pour 40 % ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
</cac:AwardingCriterion>For a given Award Criteria (BG-707), "Order of Importance" may be used instead of precise weightings (i.e. code for Award Criterion Number Weight is set to "ord-imp"); in that case:
-
Each and every Award Criterion (BG-38) within the Award Criteria:
-
Shall have an Award Criterion Number Weight (BT-5421) set to "ord-imp",
-
Shall not have an Award Criterion Number Weight (BT-5421) with a code different from "ord-imp";
-
-
The use of Order of Importance instead of weighted scores shall be justified (BT-733) using the "cbc:Description" element of "cac:AwardingCriterion",
-
Associated Award Criterion Numbers (BT-541) shall be integers starting with "1" ("1" being for the Criterion with highest importance and importance decreases with number increase).
For a given Award Criteria (BG-707), when "Order of Importance" is not used, then there should be within that Award Criteria no Award Criterion with Award Criterion Number Weight (BT-5421) set to "ord-imp".
<cac:AwardingCriterion>
<cbc:Description languageID="ENG">For this procurement, quality is a major concern and ...</cbc:Description>
<cbc:Description languageID="FRA">Pour cet achat, la qualité est une préoccupation majeure et ...</cbc:Description>
<cac:SubordinateAwardingCriterion>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-threshold">min-score</efbc:ParameterCode>
<efbc:ParameterNumeric>50</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-weight">ord-imp</efbc:ParameterCode>
<efbc:ParameterNumeric>2</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">price</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Fair and realistic price</cbc:Name>
<cbc:Name languageID="FRA">Prix équitable et réaliste</cbc:Name>
<cbc:Description languageID="ENG">Tenders with a price score lower than 50 ...</cbc:Description>
<cbc:Description languageID="FRA">Les offres avec un score sur les prix inférieur ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
<cac:SubordinateAwardingCriterion>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-threshold">min-score</efbc:ParameterCode>
<efbc:ParameterNumeric>65</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
<efac:AwardCriterionParameter>
<efbc:ParameterCode listName="number-weight">ord-imp</efbc:ParameterCode>
<efbc:ParameterNumeric>1</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">quality</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Technical merit</cbc:Name>
<cbc:Name languageID="FRA">Mérite technique</cbc:Name>
<cbc:Description languageID="ENG">Tenders with a quality score lower than 65 ...</cbc:Description>
<cbc:Description languageID="FRA">Les offres avec un score qualité inférieur ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
</cac:AwardingCriterion>When Award Criteria calculation is too complex to be described with the proposed structure based on the use of Award Criterion Number (BT-541), the complicated expression, or a reference to the procurement document section where this information may be found, should be specified in Award Criteria Complicated (BT-543). Information is encoded as text with the element "cbc:CalculationExpression". For a given Award Criteria (i.e. "cac:AwardingCriterion" element), the children "cbc:Description" (Award Criteria Order Justification, BT-733) and "cbc:CalculationExpression" (Award Criteria Complicated, BT-543) shall not coexist. Similarly, for a given Award Criteria (i.e. "cac:AwardingCriterion" element), the child element "cbc:CalculationExpression" (Award Criteria Complicated, BT-543) shall not coexist with the descendant elements "efbc:ParameterNumeric" (BT-541) or "efbc:ParameterCode" (BT-5421, BT-5422, BT-5423).
<cac:AwardingCriterion>
<cbc:CalculationExpression languageID="ENG">Price-quality score calculation is based on ...</cbc:CalculationExpression>
<cbc:CalculationExpression languageID="FRA">Le calcul du score prix-qualité est basée sur ...</cbc:CalculationExpression>
<cac:SubordinateAwardingCriterion>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">price</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Price</cbc:Name>
<cbc:Name languageID="FRA">Prix</cbc:Name>
<cbc:Description languageID="ENG">The price score is calculated by ...</cbc:Description>
<cbc:Description languageID="FRA">Le score de prix est calculé par ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
<cac:SubordinateAwardingCriterion>
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">quality</cbc:AwardingCriterionTypeCode>
<cbc:Name languageID="ENG">Quality</cbc:Name>
<cbc:Name languageID="FRA">Qualité</cbc:Name>
<cbc:Description languageID="ENG">The quality score is calculated by ...</cbc:Description>
<cbc:Description languageID="FRA">Le score de qualité est calculé par ...</cbc:Description>
</cac:SubordinateAwardingCriterion>
</cac:AwardingCriterion>Jury Member Name (BT-46)
For a contest, Jury composition (BT-46) is described by providing the name of each member:
<cac:TechnicalCommitteePerson>
<cbc:FamilyName>Mrs Pamela Smith</cbc:FamilyName>
</cac:TechnicalCommitteePerson>
<cac:TechnicalCommitteePerson>
<cbc:FamilyName>Mr John Doe</cbc:FamilyName>
</cac:TechnicalCommitteePerson>Prize information (BT-44, BT-45, BT-644)
Prize information may be used for various Planning and Competition notices. While it is necessary for Design Contest competition notices, it may also be useful for other notices when Procedure Type (BT-105) is set to "innovation" (Innovation Partnership) or "comp-dial" (Competitive Dialogue). Prize Information covers Prize Rank (BT-44), Value Prize (BT-644) and Rewards Other (BT-45); the last one being for prizes not having equivalent monetary value.
The Prize Rank is marked using "cbc:RankCode", and shall be an integer.
The Value Prize is encoded by specifying currency and amount.
Finally the prize description is provided as text.
<cac:Prize>
<cbc:RankCode>1</cbc:RankCode>
<cbc:ValueAmount currencyID="EUR">5000</cbc:ValueAmount>
<cbc:Description languageID="ENG">The first prize winner will be awarded ...</cbc:Description>
<cbc:Description languageID="FRA">Le gagnant du 1er prix se verra attribuer ...</cbc:Description>
</cac:Prize>
<cac:Prize>
<cbc:RankCode>2</cbc:RankCode>
<cbc:ValueAmount currencyID="EUR">0</cbc:ValueAmount>
<cbc:Description languageID="ENG">The winners of 2nd rank and below ...</cbc:Description>
<cbc:Description languageID="FRA">Les gagnants de second rang et au-delà ...</cbc:Description>
</cac:Prize>Tenders processing parties (BT-18)
Other parties that can be involved in processing tenders are:
-
the organization that provides additional information ("cac:AdditionalInformationParty"),
-
the organization receiving tenders ("cac:TenderRecipientParty"),
-
the organization evaluating tenders ("cac:TenderEvaluationParty").
They may then be coded in the instance using the elements shown below.
<cac:AdditionalInformationParty>
<!-- Interrupted Mark-Up -->
</cac:AdditionalInformationParty>
<cac:TenderRecipientParty>
<!-- Interrupted Mark-Up -->
<cbc:EndpointID>https://www.acme.com/tender-submission/</cbc:EndpointID>
<!-- Interrupted Mark-Up -->
</cac:TenderRecipientParty>
<cac:TenderEvaluationParty>
<!-- Interrupted Mark-Up -->
</cac:TenderEvaluationParty>The mark-up of the information for these organizations is presented in Parties.
Submission URL (BT-18) is marked using the "cbc:EndpointID" child of the "cac:TenderRecipientParty" element.
Tender Validity Deadline (BT-98)
The period, starting from the tender submission deadline, during which the tender must remain valid is expressed as follows:
<cac:TenderValidityPeriod>
<cbc:DurationMeasure unitCode="MONTH">4</cbc:DurationMeasure>
</cac:TenderValidityPeriod>The unitCode value is one of the duration measure units existing in the timeperiod codelist. Acceptable codes are: YEAR, MONTH, WEEK, DAY. No combined value may be used and the chosen unit of measure should allow the expression of the duration using integers.
Appeal terms
Different stakeholders may request a decision review, and such initiative is subject to a deadline (Review Deadline Description — BT-99). The review process involves a Review Organization (collecting review requests) and a Mediation Organization (dealing with the expressed concerns). An organization is also available to provide further information on the Review Request process (identified as the "Organization providing more information on the time limits for review procedures" in the organization subrole codelist).
<cac:AppealTerms>
<cac:PresentationPeriod>
<cbc:Description languageID="ENG">Any review request shall be submitted ...</cbc:Description>
<cbc:Description languageID="FRA">Toute demande de revision doit être ...</cbc:Description>
</cac:PresentationPeriod>
<cac:AppealInformationParty>
<!-- Interrupted Mark-Up -->
</cac:AppealInformationParty>
<cac:AppealReceiverParty>
<!-- Interrupted Mark-Up -->
</cac:AppealReceiverParty>
<cac:MediationParty>
<!-- Interrupted Mark-Up -->
</cac:MediationParty>
</cac:AppealTerms>Tendering language (BT-97)
The languages that may be used to submit tenders (BT-97) shall be marked using language codes:
<cac:Language>
<cbc:ID>ENG</cbc:ID>
</cac:Language>
<cac:Language>
<cbc:ID>FRA</cbc:ID>
</cac:Language>Post award process (BT-92, BT-93)
The use of Electronic Ordering (BT-92) and Payment (BT-93) during execution is specified by two indicators:
<cac:PostAwardProcess>
<cbc:ElectronicOrderUsageIndicator>true</cbc:ElectronicOrderUsageIndicator>
<cbc:ElectronicPaymentUsageIndicator>true</cbc:ElectronicPaymentUsageIndicator>
</cac:PostAwardProcess>To indicate that Electronic Ordering (BT-92) or Electronic Payment (BT-93) shall be used, the respective element should be used with the value "true". To indicate that Electronic Ordering (BT-92) or Electronic Payment (BT-93) shall not be used, the respective element should be used with the value "false". These indicators are mandatory for Notice subtype 16 (Contract, or concession, notice — standard regime, Directive 2014/24/EU). For this Notice subtype, as for any other notice above threshold, when used, BT-93 should be set to "true".
Economic Operator Shortlist
The "cac:EconomicOperatorShortList" element in the Tendering Terms block shall not be confused with the one in the Tendering Process one. Here it is used to specify a list of preselected sellers (Participant Name BT-47), while in the other context (cf. Maximum Candidates Indicator (BT-661), Maximum & Minimum Candidates (Procedure) (BT-51, BT-50)), it is used to specify the limitations that will be applied to establish a short list.
<cac:EconomicOperatorShortList>
<cac:PreSelectedParty>
<cac:PartyName>
<cbc:Name>Mrs L. Hürst</cbc:Name>
</cac:PartyName>
</cac:PreSelectedParty>
<cac:PreSelectedParty>
<cac:PartyName>
<cbc:Name>Mr P. Sanchez</cbc:Name>
</cac:PartyName>
</cac:PreSelectedParty>
</cac:EconomicOperatorShortList>Security Clearance (BT-578), Deadline (BT-78) & Description (BT-732)
The Security Clearance description is marked with the "cbc:Description" element of the "cac:SecurityClearanceTerm" for the associated Lot. It covers information like the required level and period, and the people concerned. When Security Clearance is required, Security Clearance (BT-578) shall be specified using the "true" value for "cbc:Code", and Security Clearance Deadline (BT-78) and Security Clearance Description (BT-732) shall be specified. When Security Clearance is not required, the element "cac:SecurityClearanceTerm" may be omitted, or used with the value "false" in the "cbc:Code" element, and Security Clearance Deadline (BT-78) and Security Clearance Description (BT-732) are not allowed.
<cbc:LatestSecurityClearanceDate>2019-11-15+01:00</cbc:LatestSecurityClearanceDate>
<!--Interrupted Mark-up -->
<cac:SecurityClearanceTerm>
<cbc:Code listName="required">true</cbc:Code>
<cbc:Description languageID="ENG">"EU Confidential" security clearance of Key Management Personnel must be achieved before access to procurement documents be granted</cbc:Description>
<cbc:Description languageID="FRA">L'habilitation sécurité "confidentiel UE" du personnel de direction doit être obtenue avant que l'accès aux documents de passation de marché ne soit accordé.</cbc:Description>
</cac:SecurityClearanceTerm>Tendering Process
For Group of Lots, only two types of information are reported at the level of the Tendering process:
-
Statistics related to the tendering process and referring to this specific Group of Lots,
-
Framework Agreement related information.
eForms BT |
Details |
Procedure |
PIN |
CN |
CAN |
XSD element |
||||
G.Lot |
Lot |
Part |
G.Lot |
Lot |
G.Lot |
Lot |
||||
Miscellaneous (*) |
||||||||||
Procurement Relaunch (BT-634) |
? |
— |
— |
— |
— |
? |
— |
? |
|
|
|---|---|---|---|---|---|---|---|---|---|---|
Tool Name (BT-632) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Deadline Receipt Expressions (BT-630) |
— |
— |
? |
— |
— |
? |
— |
— |
AND |
|
Procedure Features (BT-88) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Procedure Type (BT-105) |
1 |
— |
— |
— |
— |
— |
— |
— |
|
|
PIN Competition Termination (BT-756) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Lots All Required (BT-763) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
SubmissionElectronic (BT-17) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Successive Reduction Indicator (Procedure) (BT-52) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
GPA Coverage (BT-115) |
— |
— |
? |
? |
— |
? |
— |
? |
|
|
Tool Atypical URL (BT-124) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Deadline Receipt Tenders (BT-131) |
— |
— |
? |
— |
— |
? |
— |
— |
AND |
|
Dispatch Invitation Tender (BT-130) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Dispatch Invitation Interest (BT-631) |
— |
— |
? |
— |
— |
— |
— |
— |
|
|
Deadline Receipt Requests (BT-1311) |
— |
— |
? |
— |
— |
? |
— |
— |
AND |
|
Additional Information Deadline (BT-13) |
— |
— |
? |
? |
— |
? |
— |
— |
AND |
|
Previous Notice (OPP-090) |
* |
— |
— |
— |
— |
— |
— |
— |
|
|
Previous Planning Identifier (BT-125) |
Previous Planning & Planning Part Identifiers (BT-125, BT-1251) |
— |
— |
? |
? |
— |
? |
— |
? |
|
Previous Planning Part Identifier (BT-1251) |
Previous Planning & Planning Part Identifiers (BT-125, BT-1251) |
— |
— |
* |
? |
— |
* |
— |
* |
|
Submission Nonelectronic Justification (BT-19) |
Submission Nonelectronic Justification (BT-19) & Description (BT-745) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Submission Nonelectronic Description (BT-745) |
Submission Nonelectronic Justification (BT-19) & Description (BT-745) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Procedure Accelerated Justification (*) / Direct Award Justification (also T01 with Direct Award) |
||||||||||
Procedure Accelerated (BT-106) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Procedure Accelerated Justification (BT-1351) / Code |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Procedure Accelerated Justification (BT-1351) / Text |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Direct Award Justification Previous Procedure Identifier (BT-1252) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Direct Award Justification (BT-136) / Code |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Direct Award Justification (BT-135) / Text |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Candidates (*) |
||||||||||
Maximum Candidates Indicator (BT-661) |
Maximum Candidates Indicator (BT-661), Maximum & Minimum Candidates (Procedure) (BT-51, BT-50) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Maximum Candidates (BT-51) |
Maximum Candidates Indicator (BT-661), Maximum & Minimum Candidates (Procedure) (BT-51, BT-50) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Minimum Candidates (BT-50) |
Maximum Candidates Indicator (BT-661), Maximum & Minimum Candidates (Procedure) (BT-51, BT-50) |
— |
— |
? |
— |
— |
? |
— |
— |
|
Opening event (*) |
||||||||||
Public Opening Date (BT-132) |
— |
— |
? |
— |
— |
? |
— |
— |
AND |
|
Public Opening Description (BT-134) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Public Opening Place (BT-133) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Auction Terms (*) |
||||||||||
Electronic Auction (BT-767) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Electronic Auction Description (BT-122) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Electronic Auction URL (BT-123) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Framework Agreement (**) |
||||||||||
Framework Maximum Participants Number (BT-113) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Framework Duration Justification (BT-109) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Group Framework Maximum Value (BT-157) |
— |
? |
— |
— |
? |
— |
? |
— |
|
|
Buyer Categories (OPT-090) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Framework Buyer Categories (BT-111) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Framework Agreement (BT-765) |
— |
— |
? |
? |
— |
? |
— |
? |
|
|
Dynamic Purchasing System (BT-766) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Context: (*) (**) |
||||||||||
Procurement Relaunch (BT-634)
The Procurement Relaunch indicator (BT-634) may apply at different levels (Lot & Procedure) to specify that, for the corresponding object, the process will be restarted.
The "efbc:ProcedureRelaunchIndicator" element shall only be used when "true"; when it applies to the whole procurement, it shall appear in the "cac:TenderingProcess" of the notice (i.e. at notice level) only.
When applied to a Lot that is included in a Group of Lots defined in preceding notices of the same procedure, all the individual Lots included in that Group of Lots shall be marked as such, and that Group of Lots shall not exist in the current notice.
<cac:TenderingProcess>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efbc:ProcedureRelaunchIndicator>true</efbc:ProcedureRelaunchIndicator>
<!--Interrupted Mark-up -->
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!--Interrupted Mark-up -->
</cac:TenderingProcess>Tool Name (BT-632)
The name of the electronic tool or device used for electronic communication.
This optional Business Term is to be used, for PIN and CN notices only, in conjunction with BT-124. It shall be marked using the extension mechanism at the level of the "cac:TenderingProcess" element of the Lot or Part it applies to.
<cac:TenderingProcess>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efbc:AccessToolName>AbcKomSoft</efbc:AccessToolName>
<!--Interrupted Mark-up -->
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!--Interrupted Mark-up -->
<cac:TenderingProcess>Deadline Receipt Expressions (BT-630)
The deadline for receipt of expressions of interests is marked using the extension mechanism at the "cac:TenderingProcess" level of the concerned object:
<cac:TenderingProcess>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<!--Interrupted Mark-up -->
<efac:InterestExpressionReceptionPeriod>
<cbc:EndDate>2019-10-28+01:00</cbc:EndDate>
<cbc:EndTime>18:00:00+01:00</cbc:EndTime>
</efac:InterestExpressionReceptionPeriod>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!--Interrupted Mark-up -->
<cac:TenderingProcess>Procedure Features (BT-88)
This business term describes the main features of the whole Procedure; it provides information on the individual stage(s) and the availability of the whole set of applicable rules.
The business term applies to the whole Procedure (i.e. does not apply per Lot or Group of Lots), and is mandatory when the procedure is not one of those mentioned in the procurement Directives (i.e. for values "oth-mult" and "oth-single" of the procurement-procedure-type codelist).
<cac:TenderingProcess>
<cbc:Description languageID="ENG">A two stages procedure ...</cbc:Description>
<cbc:Description languageID="FRA">Une procedure en deux étapes ...</cbc:Description>
<!-- Interrupted Mark-Up -->
</cac:TenderingProcess>Procedure Type (BT-105)
This term refers to the type of procurement procedure (e.g. according to the types given in the procurement Directives). It is marked for the whole Procedure with the "cbc:ProcedureCode" element. Allowed values are reported in the procurement-procedure-type codelist.
For procedures types codified with the "oth-mult" or "oth-single" values (i.e. PIN CFC social & CN social), the procedure features (BT-88) must also be specified.
For a competitive dialog, the Procedure Type shall be marked:
<cbc:ProcedureCode listName="procurement-procedure-type">comp-dial</cbc:ProcedureCode>PIN Competition Termination (BT-756)
This indicator marks the end of a competition associated to a PIN used as a call for competition (or a specific Lot) and no further contracts, besides those published in this notice, will be awarded. This field can be used even if no contracts are awarded in the contract award notice and is marked as follows:
<cbc:TerminatedIndicator>true</cbc:TerminatedIndicator>It should apply at the Procedure or Lot level depending on the concerned object. Applied at the Procedure level, it does not however mark the end of notice publications since Change notices and Contract Modifications could still be created.
The field is mandatory for Notice subtypes 29 and 30 (Contract, or concession, award notice — standard regime, Directives 2014/24/EU and 2014/25/EU) when started with a Call For Competition. The value may be:
-
true when "No further contracts, besides those published in this notice, will be awarded following the prior information notice used as a call for competition. This field can be used even if no contracts are awarded in the contract award notice."
-
false when "further contracts, besides those published in this notice, may be awarded following the prior information notice used as a call for competition."
Lots All Required (BT-763)
This term is used to specify that any tenderer must submit tenders for all Lots. This Business Term shall be used when and only when tendering for all existing Lots is mandatory. For this, the "cbc:PartPresentationCode" element is used with a single possible value: "all".
<cbc:PartPresentationCode listName="tenderlot-presentation">all</cbc:PartPresentationCode>SubmissionElectronic (BT-17)
This term is used to specify the electronic transmission requirement for document submission (tenders, request to participate and expression of interest).
This information shall be reported per Lot. Allowed values are listed in the permission codelist.
<cbc:SubmissionMethodCode listName="esubmission">allowed</cbc:SubmissionMethodCode>The presence of the appropriate information for electronic (e.g. URL, email address …) and non-electronic (e.g. postal address) transmissions is driven by the specified value.
Successive Reduction Indicator (Procedure) (BT-52)
This term is an indicator used to specify per Lot whether the procedure is a multi-stages one or not; At each stage, participants may be eliminated.
Only two values are possible, "true" and "false":
<cbc:CandidateReductionConstraintIndicator>true</cbc:CandidateReductionConstraintIndicator>GPA Coverage (BT-115)
An indicator with only two acceptable values ("true" and "false") may be used to specify whether a procurement associated to a Lot is covered by a Government Procurement Agreement or not.
<cbc:GovernmentAgreementConstraintIndicator>true</cbc:GovernmentAgreementConstraintIndicator>Tool Atypical URL (BT-124)
When communication requires an atypical tool or device, the URL to access this tool or device shall be marked:
<cbc:AccessToolsURI>https://my-atypical-tool.com/</cbc:AccessToolsURI>Deadline Receipt Tenders (BT-131)
For a given Lot, the deadline for tender receipt is marked by specifying date and time:
<cac:TenderSubmissionDeadlinePeriod>
<cbc:EndDate>2019-11-30+01:00</cbc:EndDate>
<cbc:EndTime>12:00:00+01:00</cbc:EndTime>
</cac:TenderSubmissionDeadlinePeriod>Dispatch Invitation Tender (BT-130)
For procedures involving 2 or more stages, the estimated date for the dispatching of the invitation to tender is encoded using a "cac:InvitationSubmissionPeriod" component:
<cac:InvitationSubmissionPeriod>
<cbc:StartDate>2019-11-15+01:00</cbc:StartDate>
</cac:InvitationSubmissionPeriod>Dispatch Invitation Interest (BT-631)
For PIN call for competition notices, the estimated date of dispatch of the invitations to confirm interest is encoded using "cac:ParticipationInvitationPeriod":
<cac:ParticipationInvitationPeriod>
<cbc:StartDate>2019-11-15+01:00</cbc:StartDate>
</cac:ParticipationInvitationPeriod>Deadline Receipt Requests (BT-1311)
For a given Lot, the deadline for receipt of requests to participate is expressed with components of the "cac:ParticipationRequestReceptionPeriod" element:
<cac:ParticipationRequestReceptionPeriod>
<cbc:EndDate>2019-11-25+01:00</cbc:EndDate>
<cbc:EndTime>12:00:00+01:00</cbc:EndTime>
</cac:ParticipationRequestReceptionPeriod>Additional Information Deadline (BT-13)
For a given Lot, or Group of Lots, the deadline to request for additional information is encoded as follows:
<cac:AdditionalInformationRequestPeriod>
<cbc:EndDate>2019-11-08+01:00</cbc:EndDate>
<cbc:EndTime>18:00:00+01:00</cbc:EndTime>
</cac:AdditionalInformationRequestPeriod>Previous Notice (OPP-090)
Previous Notice (OPP-090) may be used to associate a notice to one or more immediately preceding TEDXML notices. It is also not intended to replace:
-
Change Notice Version Identifier (BT-758),
-
Modification Previous Notice Section Identifier (BT-1501),
-
Previous Planning Identifier (BT-125), or
-
Framework Notice Identifier (OPT-100),
which should still be used even when referring to a TEDXML notice.
Previous Notice (OPP-090) is only foreseen for cases where no other option to refer to a previous notice exists. It may be useful when some notices for a Procedure have been published in TEDXML (format which does not have a Procedure ID), and it is desired to publish following notices of the Procedure in eForms. This Business Term allows the notices to be associated despite the absence of Procedure ID in TEDXML.
A TEDXML notice is referred to using its Notice Publication ID (XXXXXX-YYYY).
Previous Notice (OPP-090) applies to the whole notice, and not just a single lot. It may also be repeated to point to multiple previous notices when needed.
<cac:NoticeDocumentReference>
<cbc:ID schemeName="ojs-notice-id">1624-2023</cbc:ID>
</cac:NoticeDocumentReference>
<cac:NoticeDocumentReference>
<cbc:ID schemeName="ojs-notice-id">38976-2022</cbc:ID>
</cac:NoticeDocumentReference>Previous Planning & Planning Part Identifiers (BT-125, BT-1251)
Identification of a Planning notice related to this notice is done using its notice identifier (UUID) concatenated with the associated version identifier (2 digits) in the form <UUID>-<vv>. Another option is to refer to the Notice Publication ID (XXXXXX-YYYY). Both may be differentiated with the schemeName: "notice-id-ref" and "ojs-notice-id" respectively.
Parts of the referenced Planning notice are individually identified using multiple occurrences of the element "cbc:ReferencedDocumentInternalAddress". The ID for the reference to the Part shall following the scheme ID reported in IDs & References, namely "PAR-XXXX".
<cac:NoticeDocumentReference>
<cbc:ID schemeName="notice-id-ref">123e4567-e89b-12d3-a456-426614174000-06</cbc:ID>
<cbc:ReferencedDocumentInternalAddress>PAR-0001</cbc:ReferencedDocumentInternalAddress>
<cbc:ReferencedDocumentInternalAddress>PAR-0003</cbc:ReferencedDocumentInternalAddress>
</cac:NoticeDocumentReference>Considerations:
-
Reference to Parts shall be encoded only when the referred Planning notice is of type "PIN only";
-
Since a Lot may be defined based on multiple Parts, and Parts may belong to different "PIN only" notices, "cac:NoticeDocumentReference" and "cbc:ReferencedDocumentInternalAddress" are repeatable;
-
Two "cac:NoticeDocumentReference" elements with the same parent (i.e. leading by combination to the definition of a given Lot) shall have different notice identifiers[8];
-
When the referenced notice is of any other type, since Lots shall neither be added/suppressed/redefined, only notice identifier & version should be reported;
-
The reference to a previous notice shall be reported in the "cac:TenderingProcess" element of the relevant Lots or Parts.
Submission Nonelectronic Justification (BT-19) & Description (BT-745)
For a Lot, when the electronic submission is prohibited (i.e. the value associated to BT-17 equals "not-allowed"), BT-19 and BT-745 must be specified:
<cac:ProcessJustification>
<cbc:ProcessReasonCode listName="no-esubmission-justification">phy-mod</cbc:ProcessReasonCode>
<cbc:Description languageID="ENG">Tenders shall be sent per registered letter ...</cbc:Description>
<cbc:Description languageID="FRA">Les offres doivent être transmises par lettre ...</cbc:Description>
</cac:ProcessJustification>Possible values for the "No eSubmission Justification" are listed in the communication-justification codelist.
Procedure Accelerated (BT-106) and Justification (BT-1351)
When the Procedure is accelerated the "true" code shall be used, otherwise the "false" code shall apply. For an accelerated Procedure, the justification is encoded with the "ProcessReason" element:
<cac:ProcessJustification>
<cbc:ProcessReasonCode listName="accelerated-procedure">true</cbc:ProcessReasonCode>
<cbc:ProcessReason languageID="ENG">The urgent aspect of ...</cbc:ProcessReason>
<cbc:ProcessReason languageID="FRA">Le caractère urgent de ...</cbc:ProcessReason>
</cac:ProcessJustification>Direct Award Justification (BT-135, BT-136, BT-1252)
When the Procedure Type is a Direct Award, then the justification is encoded with the "cbc:ProcessReasonCode" element. The "cbc:ProcessReason" element may be used to provide further information as text when required and "cbc:Description" may be used to refer to the previous procedure (using its UUID) that justified the Direct Award:
<cac:ProcessJustification>
<cbc:ProcessReasonCode listName="direct-award-justification">ecom-excl</cbc:ProcessReasonCode>
<cbc:ProcessReason languageID="ENG">Direct award is justified ...</cbc:ProcessReason>
<cbc:ProcessReason languageID="FRA">L'attribution ...</cbc:ProcessReason>
<cbc:Description>123e4567-e89b-12d3-a456-426614174000</cbc:Description>
</cac:ProcessJustification>The list to be used for the ProcessReasonCode is the direct-award-justification, of which the use of codes is context dependent as shown in Table 8.
Code |
V E A T |
C A N |
MOVE |
||||||
|---|---|---|---|---|---|---|---|---|---|
D23 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D81 |
||
dir81-annexii |
X |
||||||||
unsuitable |
X |
X |
X |
X |
|||||
irregular |
X |
||||||||
resd |
X |
X |
X |
||||||
rd |
X |
||||||||
technical |
X |
X |
X |
X |
|||||
artistic |
X |
X |
X |
||||||
exclusive |
X |
X |
X |
||||||
other-exclusive |
X |
||||||||
crisis |
X |
||||||||
urgency |
X |
||||||||
existing |
X |
X |
X |
||||||
repetition |
X |
X |
X |
||||||
contest |
X |
X |
|||||||
commodity |
X |
X |
X |
||||||
closure |
X |
X |
X |
||||||
liquidator |
X |
X |
X |
||||||
bargain |
X |
||||||||
dir81-transport |
X |
||||||||
additional |
X |
X |
|||||||
below-thres |
X |
X |
X |
X |
X |
||||
ecom-excl |
X |
X |
|||||||
int-rules |
X |
X |
X |
X |
|||||
serv-excl |
X |
X |
X |
X |
|||||
sc-right |
X |
X |
X |
||||||
in-house |
X |
X |
X |
||||||
defse-excl |
X |
X |
X |
X |
|||||
dir24-list |
X |
||||||||
rl-third |
X |
||||||||
other-activity |
X |
X |
|||||||
water-purch |
X |
X |
|||||||
energy-supply |
X |
||||||||
spe-arrang |
X |
X |
|||||||
tra-ser |
X |
||||||||
non-p-int |
X |
X |
X |
||||||
non-buyer-aw |
X |
X |
X |
||||||
not-wss |
X |
X |
X |
||||||
non-contr |
X |
X |
|||||||
int-oper |
X |
||||||||
below-thres-sme |
X |
||||||||
rail |
X |
||||||||
Maximum Candidates Indicator (BT-661), Maximum & Minimum Candidates (Procedure) (BT-51, BT-50)
Respectively:
-
the existence of a maximum number of candidates (BT-661),
-
this maximum number of candidates (BT-51), and
-
the minimum number of candidates to be invited for the second stage (BT-50),
are marked as follows:
<cac:EconomicOperatorShortList>
<!-- Maximum Candidates Indicator (BT-661) -->
<cbc:LimitationDescription>true</cbc:LimitationDescription>
<!-- Maximum Candidates Number (BT-51) -->
<cbc:MaximumQuantity>10</cbc:MaximumQuantity>
<!-- Minimum Candidates (BT-50) -->
<cbc:MinimumQuantity>3</cbc:MinimumQuantity>
</cac:EconomicOperatorShortList>It shall not be confused with the construction built in Tendering Terms using the same element "cac:EconomicOperatorShortList". Here it references a process establishing a short list, while in the Tendering Terms, it references an existing list of already screened tenderers.
"cbc:LimitationDescription":
-
is used as an indicator (only possible values are "true" & "false"), the "languageID" attribute shall not be used;
-
shall not occur more than once in the same parent;
-
must be given and set to "true", when "cbc:MaximumQuantity" is specified.
"cbc:MaximumQuantity" and "cbc:MinimumQuantity":
-
shall be integers with the first one greater or equal to the second one, when both are specified;
Opening event
For a given Lot, the Public Opening Date (BT-132), Description (BT-134) and Place (BT-133) are encoded as follows:
<cac:OpenTenderEvent>
<cbc:OccurrenceDate>2019-11-05+01:00</cbc:OccurrenceDate>
<cbc:OccurrenceTime>14:00:00+01:00</cbc:OccurrenceTime>
<cbc:Description languageID="ENG">Any tenderer may attend ...</cbc:Description>
<cbc:Description languageID="FRA">Tout soumissionaire peut participer ...</cbc:Description>
<cac:OccurenceLocation>
<cbc:Description languageID="ENG">online at URL https://event-on-line.org/d22f65 ...</cbc:Description>
<cbc:Description languageID="FRA">en ligne à l'URL https://event-on-line.org/d22f65 ...</cbc:Description>
</cac:OccurenceLocation>
</cac:OpenTenderEvent>Auction Terms
The use for a given Lot of an electronic auction system (BT-767) is specified with an indicator. When the value is "true", Description (BT-122) and URL (BT-123) may be specified.
<cac:AuctionTerms>
<cbc:AuctionConstraintIndicator>true</cbc:AuctionConstraintIndicator>
<cbc:Description languageID="ENG">The online auction solution ...</cbc:Description>
<cbc:Description languageID="FRA">La solution d'enchères en ligne ...</cbc:Description>
<cbc:AuctionURI>https://my-online-eauction.eu/</cbc:AuctionURI>
</cac:AuctionTerms>Framework Agreement
When, for a lot (or Group of Lots), no Framework Agreement (FA) is used, then, when the information is expected, it may be reported as follows:
<cac:ContractingSystem>
<cbc:ContractingSystemTypeCode listName="framework-agreement">none</cbc:ContractingSystemTypeCode>
</cac:ContractingSystem>When, for a Lot, a framework agreement (FA) is foreseen (PIN & CN) for the execution:
should be specified.
<cac:FrameworkAgreement>
<cbc:MaximumOperatorQuantity>50</cbc:MaximumOperatorQuantity>
<cbc:Justification languageID="ENG">The exceptional duration of ...</cbc:Justification>
<cbc:Justification languageID="FRA">La durée exceptionnelle de ...</cbc:Justification>
<cac:SubsequentProcessTenderRequirement>
<cbc:Name>buyer-categories</cbc:Name>
<cbc:Description languageID="ENG">Offices of the "greater region" ...</cbc:Description>
<cbc:Description languageID="FRA">Bureaux de la "Grande région" ...</cbc:Description>
</cac:SubsequentProcessTenderRequirement>
</cac:FrameworkAgreement>
<cac:ContractingSystem>
<cbc:ContractingSystemTypeCode listName="framework-agreement">fa-wo-rc</cbc:ContractingSystemTypeCode>
</cac:ContractingSystem>When, for a Group of Lots, a framework agreement (FA) is foreseen (PIN & CN) for the execution:
-
the Group Framework Maximum Value (BT-157)[11]
should be specified.
<cac:FrameworkAgreement>
<cbc:EstimatedMaximumValueAmount currencyID="EUR">200000</cbc:EstimatedMaximumValueAmount>
</cac:FrameworkAgreement>Generally:
-
The maximum number of participants (BT-113) shall be an integer;
-
the duration justification (BT-109) shall be of type text,
-
the framework maximum value for the Group of Lots (BT-157) shall be a monetary value,
-
the buyer categories shall be of type text; and
-
the framework agreement type (BT-765) shall be one of the values listed in the framework-agreement codelist.
For a CAN, when, for a given Lot, a Framework Agreement is involved, only the following information is expected at the level of the Lot definition:
-
The framework buyer categories (BT-111) with its associated technical field (OPT-090), and
-
The Framework Agreement type (BT-765).
<cac:FrameworkAgreement>
<cac:SubsequentProcessTenderRequirement>
<cbc:Name>buyer-categories</cbc:Name>
<cbc:Description languageID="ENG">Offices of the "greater region" ...</cbc:Description>
<cbc:Description languageID="FRA">Bureaux de la "Grande région" ...</cbc:Description>
</cac:SubsequentProcessTenderRequirement>
</cac:FrameworkAgreement>
<cac:ContractingSystem>
<cbc:ContractingSystemTypeCode listName="framework-agreement">fa-wo-rc</cbc:ContractingSystemTypeCode>
</cac:ContractingSystem>For a CAN, when for a given Group of Lots a Framework Agreement is involved, only the following information is expected at the level of the Group of Lots definition:
-
Group Framework Maximum Value (BT-157).
<cac:FrameworkAgreement>
<cbc:EstimatedMaximumValueAmount currencyID="EUR">200000</cbc:EstimatedMaximumValueAmount>
</cac:FrameworkAgreement>For a CAN, when Lots with Framework Agreements have been awarded, further Framework Agreement related information is to be expected in the Result section (cf. Competition Results).
Dynamic Purchasing System (BT-766)
The existence of a Dynamic Purchasing System (DPS) and its use is specified with the "cbc:ContractingSystemTypeCode" element with a value from the dps-usage codelist; It shall be marked:
<cac:ContractingSystem>
<cbc:ContractingSystemTypeCode listName="dps-usage">dps-nlist</cbc:ContractingSystemTypeCode>
</cac:ContractingSystem>Procurement Project
eForms BT |
Details |
Procedure |
PIN |
CN |
CAN |
XSD element |
||||
G.Lot |
Lot |
Part |
G.Lot |
Lot |
G.Lot |
Lot |
||||
Identification (*) |
||||||||||
Internal Identifier (BT-22) |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
|
|
Title (BT-21) |
1 |
? |
1 |
1 |
? |
1 |
? |
1 |
|
|
Description (BT-24) |
1 |
? |
1 |
1 |
? |
1 |
? |
1 |
|
|
Nature (*) |
||||||||||
Main Nature (BT-23) |
1 |
— |
1 |
1 |
— |
1 |
— |
1 |
|
|
Additional Nature (different from Main) (BT-531) |
* |
— |
* |
* |
— |
* |
— |
* |
|
|
Strategic Procurement (*) |
||||||||||
Strategic Procurement (BT-06) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Strategic Procurement Description (BT-777) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Procurement type (*) |
||||||||||
Green Procurement (BT-774) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Green Procurement Criteria (BT-805) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Social Procurement (BT-775) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Procurement of Innovation (BT-776) |
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
Accessibility |
||||||||||
Accessibility Justification (BT-755) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
|---|---|---|---|---|---|---|---|---|---|---|
Accessibility (BT-754) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Quantity (*) |
||||||||||
Quantity (BT-25) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Unit (BT-625) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Aggregated amounts & additional information |
||||||||||
Suitable for SMEs (BT-726) |
— |
? |
? |
? |
? |
? |
— |
— |
|
|
Additional Information (BT-300) (*)* |
? |
? |
? |
? |
? |
? |
? |
? |
|
|
Framework Maximum Value (BT-271) |
? |
? |
? |
? |
? |
? |
? |
? |
|
|
Estimated Value (BT-27) |
? |
? |
? |
? |
? |
? |
? |
? |
|
|
Classification (*) |
||||||||||
Classification Type (e.g. CPV) (BT-26) |
Classification Type (BT-26), Main & Additional Classification Codes (BT-262, BT-263) |
1 |
— |
1 |
1 |
— |
1 |
— |
1 |
Or |
Main Classification Code (BT-262) |
Classification Type (BT-26), Main & Additional Classification Codes (BT-262, BT-263) |
1 |
— |
1 |
1 |
— |
1 |
— |
1 |
|
Additional Classification Code (BT-263) |
Classification Type (BT-26), Main & Additional Classification Codes (BT-262, BT-263) |
* |
— |
* |
* |
— |
* |
— |
* |
|
Place of Performance (*) |
||||||||||
Place of Performance Additional Information (BT-728) |
? |
— |
? |
? |
— |
? |
— |
? |
|
|
Place Performance City (BT-5131) |
? |
— |
? |
? |
— |
? |
— |
? |
|
|
Place Performance Post Code (BT-5121) |
? |
— |
? |
? |
— |
? |
— |
? |
|
|
Place Performance Country Subdivision (BT-5071) |
? |
— |
? |
? |
— |
? |
— |
? |
|
|
Place Performance Services Other (BT-727) |
? |
— |
? |
? |
— |
? |
— |
? |
use of codelist "Place Performance Services Other" |
|
Place Performance Street (BT-5101) |
? |
— |
? |
? |
— |
? |
— |
? |
First line: Second line: Third line: |
|
Place Performance Country Code (BT-5141) |
? |
— |
? |
? |
— |
? |
— |
? |
|
|
Planned period (*) |
||||||||||
Duration Start Date (BT-536) |
— |
— |
? |
? |
— |
? |
— |
? |
|
|
Duration End Date (BT-537) |
— |
— |
? |
? |
— |
? |
— |
? |
|
|
Duration Period (BT-36) |
— |
— |
? |
? |
— |
? |
— |
? |
AND |
|
Duration Other (BT-538) |
— |
— |
? |
? |
— |
? |
— |
? |
with value "unlimited" AND |
|
Contract extensions (*) |
||||||||||
Options Description (BT-54) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Renewal maximum (BT-58) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Renewal Description (BT-57) |
— |
— |
? |
— |
— |
? |
— |
? |
|
|
Contexts: (*) |
||||||||||
Internal ID (BT-22), Title (BT-21) & Description (BT-24)
For the Procedure, the Parts, the Lots and the Group of Lots, a contracting authority may specify an internal identifier. There is no specific restriction regarding its structure, and any construct is possible.
While no specific rules apply, the contracting authority should ensure that, for all Procedures it advertises using notices, the internal identifier would be unique. Otherwise, for a given contracting authority, having two different Procedures sharing the same internal ID, would make it impossible to list notices belonging to one or the other Procedure, based on the Buyer’s and Internal Procedure Identifiers only.
Internal Identifier shall be marked:
<cbc:ID schemeName="InternalID">PROC/2020/0024-ABC-FGHI</cbc:ID>Title and description may also be specified for the procedure, Parts, Groups of Lots and Lots; title and description are language dependant.
The corresponding elements, of type text, shall have their associated "languageID" attribute value specified using a language code.
For each linguistic version, these shall exist only once.
<cbc:Name languageID="ENG">Computer Network extension</cbc:Name>
<cbc:Name languageID="FRA">Extension du réseau informatique</cbc:Name>
<cbc:Description languageID="ENG">Procedure for the procurement of ...</cbc:Description>
<cbc:Description languageID="FRA">Procédure pour la fourniture de ...</cbc:Description>Main & Additional Nature (BT-23, BT-531), Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805), and Accessibility (BT-754, BT-755)
Main Nature (BT-23) is specified using the element "cbc:ProcurementTypeCode" directly within the "cac:ProcurementProject" element. All the other business terms use the "cbc:ProcurementTypeCode" element within a "cac:ProcurementAdditionalType" element. This may also contain a multilingual text description in a "cbc:ProcurementType" element.
Main & Additional Nature (BT-23, BT-531)
The possible values are listed in the contract-nature codelist[12].
The "Additional Nature" may use one of the 3 values, however it shall be different from "Main Nature" and from the other "Additional Nature", when it exists.
Considerations:
-
There shall be one and only one "Main Nature" for a Procedure, Lot, or Part;
-
Given that :
-
there are 3 distinct nature codes usable to qualify the Main and Additional Natures,
-
Additional Natures must differ from the Main Nature,
-
Additional Natures must not be duplicated,
-
then, for a given Procedure, Lot or Part, there may be up-to two Additional Natures only.
Strategic Procurement (BT-06, BT-774, BT-775, BT-776, BT-777, BT-805)
For a given Lot, strategic projects are identified using the "listName" attribute of the "cbc:ProcurementTypeCode" element. The value of the "listName" attribute shall refer to the appropriate codelist (strategic-procurement for strategic procurement BT-06, environmental-impact for Green Procurement BT-774, innovative-acquisition for Procurement of Innovation BT-776, social-objective for Social Procurement BT-775, gpp-criteria for Green Procurement Criteria BT-805).
Multiple "cac:ProcurementAdditionalType" elements may be used to highlight the different aspects of the procurement (e.g. for an Procurement of Innovation aiming at reducing environmental impacts as illustrated in the example below).
The Strategic Procurement description (BT-777) shall be marked using the "cbc:ProcurementType" element.
Accessibility (BT-754, BT-755)
Whether accessibility criteria for persons with disabilities are included (BT-754) for a lot may be indicated with a "cbc:ProcurementTypeCode" element, with the "listName" attribute set to "accessibility", and a value from the accessibility codelist. BT-754 is not repeatable, as the values in the codelist are mutually exclusive. If the procurement is intended for natural persons, but no accessibility criteria are given, then the value "n-inc-just" shall be used, and the Accessibility Justification (BT-755) shall be given using the "cbc:ProcurementType" element.
The below example illustrates the expression of one Main and two Additional Natures, two strategic projects, and a code and justification for the absence of accessibility criteria.
<cbc:ProcurementTypeCode listName="contract-nature">works</cbc:ProcurementTypeCode>
<!-- Interrupted Mark-up -->
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="contract-nature">services</cbc:ProcurementTypeCode>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="contract-nature">supplies</cbc:ProcurementTypeCode>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="strategic-procurement">inn-pur</cbc:ProcurementTypeCode>
<cbc:ProcurementType languageID="ENG">This is a strategic procurement involving the innovative use of ...</cbc:ProcurementType>
<cbc:ProcurementType languageID="FRA">Il s'agit d'une fourniture stratégique impliquant l'utilisation innovante de...</cbc:ProcurementType>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="strategic-procurement">env-imp</cbc:ProcurementTypeCode>
<cbc:ProcurementType languageID="ENG">Compliance with EMAS ...</cbc:ProcurementType>
<cbc:ProcurementType languageID="FRA">Conformité à l'EMAS ...</cbc:ProcurementType>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="innovative-acquisition">mar-nov</cbc:ProcurementTypeCode>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="innovative-acquisition">buy-eff</cbc:ProcurementTypeCode>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="environmental-impact">emas-com</cbc:ProcurementTypeCode>
</cac:ProcurementAdditionalType>
<cac:ProcurementAdditionalType>
<cbc:ProcurementTypeCode listName="accessibility">n-inc-just</cbc:ProcurementTypeCode>
<cbc:ProcurementType languageID="ENG">Accessibility criteria are not included ...</cbc:ProcurementType>
<cbc:ProcurementType languageID="FRA">Les critères d'accessibilité ne sont pas inclus ...</cbc:ProcurementType>
</cac:ProcurementAdditionalType>Quantity & Unit (BT-25, BT-625)
The list of possible units is in the measurement-unit codelist.
Quantity is any numeric value representing the quantity in a given unit[13].
A procurement dealing with 45,000 tonnes of supplies shall be marked:
<cbc:EstimatedOverallContractQuantity unitCode="TNE">45000</cbc:EstimatedOverallContractQuantity>Suitable for SMEs (BT-726)
For PIN and CN, the contracting authority may specify that a Group of lots, Lot, or Part, is suitable for SMEs by using the "cbc:SMESuitableIndicator" in the "cac:ProcurementProject" element of the corresponding Group of Lots/Lot/Part, with a value of "true". The contracting authority may explicitly specify that a Group of lots, Lot, or Part, is not suitable for SMEs by using a value of "false".
<cbc:SMESuitableIndicator>true</cbc:SMESuitableIndicator>Additional information
For the Procedure, Part, Lot, or Group of Lots, any additional information not reported elsewhere may be marked using the "cbc:Note" child of the appropriate "cac:ProcurementProject" element.
<cbc:Note languageID="ENG">For the current procedure ...</cbc:Note>
<cbc:Note languageID="FRA">Pour la procedure courante ...</cbc:Note>Estimated and Framework Maximum Values (BT-27, BT-271)
The Estimated Value is marked using the "cbc:EstimatedOverallContractAmount" and represents the aggregated amount of all the individual components that constitute the current notice, Group of Lots, Lot or Part. Currency and amount shall be specified. Possible "currencyID" values are in the codelist currency.
The amount is a rough estimation by the contracting authority at launch of the Call for Competition (or even earlier). When the estimation was possible (except for "PIN profile" notices), the value may be specified.
<cac:RequestedTenderTotal>
<cbc:EstimatedOverallContractAmount currencyID="EUR">250000</cbc:EstimatedOverallContractAmount>
</cac:RequestedTenderTotal>The Framework Maximum Value is marked using the "efbc:FrameworkMaximumAmount" and represents the early evaluation of the Framework Maximum value for the Group of Lots, the Lot or the Procedure as a whole. Currency and amount shall be specified. When the early evaluation was possible (except for "PIN profile" and "PIN only" notices), the value may be specified.
<cac:RequestedTenderTotal>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efbc:FrameworkMaximumAmount currencyID="EUR">120000</efbc:FrameworkMaximumAmount>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
</cac:RequestedTenderTotal>Classification Type (BT-26), Main & Additional Classification Codes (BT-262, BT-263)
These business terms are used to designate the classification system along with the main and the additional commodities classifications.
The used classification (Classification Type — BT-26) is specified using the "listName" attribute of the "cbc:ItemClassificationCode".
The main commodity is the one representing the highest value fraction. Additional commodities are other commodities belonging to the same Lot/Part or Procedure and which, taken individually and compared to the main commodity, represent a lower portion of the overall lot/group value.
Classification is currently only based on the main "Common Procurement Vocabulary" codes (CPV) and "Supplementary CPV" are not implemented for eForms.
Other classification systems could later be used[14].
For illustration purpose, we have reported below, a typical mark-up based on different classifications:
-
the CPV, and
-
a hypothetical classification ABC with subsidiary codes (subsidiary codes appear in extensions of the major classification of the commodity it refers to).
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode listName="cpv">15311100</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:SubsidiaryClassification>
<cbc:ItemClassificationCode listName="subsidiary-abc">AFGH</cbc:ItemClassificationCode>
</efac:SubsidiaryClassification>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:ItemClassificationCode listName="abc">XYZ/002</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:AdditionalCommodityClassification>
<cbc:ItemClassificationCode listName="cpv">15311200</cbc:ItemClassificationCode>
</cac:AdditionalCommodityClassification>
<cac:AdditionalCommodityClassification>
<cbc:ItemClassificationCode listName="cpv">15311500</cbc:ItemClassificationCode>
</cac:AdditionalCommodityClassification>
<cac:AdditionalCommodityClassification>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:SubsidiaryClassification>
<cbc:ItemClassificationCode listName="subsidiary-abc">hdjd</cbc:ItemClassificationCode>
</efac:SubsidiaryClassification>
<efac:SubsidiaryClassification>
<cbc:ItemClassificationCode listName="subsidiary-abc">lelja</cbc:ItemClassificationCode>
</efac:SubsidiaryClassification>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:ItemClassificationCode listName="abc">SCE/548</cbc:ItemClassificationCode>
</cac:AdditionalCommodityClassification>Place of performance (BG-708)
Since performance may take place at multiple locations, the place of performance is repeatable.
This group may contain the following information:
-
Additional Information (BT-728)
-
City (BT-5131)
-
Post Code (BT-5121)
-
Country Subdivision (BT-5071)
-
Services Other (as a codelist) (BT-727)
-
Street (BT-5101)
-
Country Code (BT-5141)
Use "cbc:Region" and a code from the codelist other-place-service to identify regions not covered with the cbc:CountrySubentityCode (e.g. "country wide", "EEA wide", "anywhere"). When Place Performance Services Other (BT-727) has the value "anyw-cou", the Place Performance Country Code (BT-5141) is mandatory. Values must come from the country codelist.
<!-- 1st Place of Performance -->
<cac:RealizedLocation>
<cbc:Description languageID="ENG">The main location is ...</cbc:Description>
<cbc:Description languageID="FRA">La localisation principale est ...</cbc:Description>
<cac:Address>
<cbc:StreetName>Main Street, 2</cbc:StreetName>
<cbc:AdditionalStreetName>Building B1</cbc:AdditionalStreetName>
<cbc:CityName>BigCity</cbc:CityName>
<cbc:PostalZone>XY14 2LG</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">UKG23</cbc:CountrySubentityCode>
<cac:AddressLine>
<cbc:Line>3rd floor</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode listName="country">GBR</cbc:IdentificationCode>
</cac:Country>
</cac:Address>
</cac:RealizedLocation>
<!-- 2nd place of performance -->
<cac:RealizedLocation>
<cbc:Description languageID="ENG">Further realizations ...</cbc:Description>
<cbc:Description languageID="FRA">Des réalisations complémentaires ...</cbc:Description>
<cac:Address>
<cbc:Region>anyw-eea</cbc:Region>
</cac:Address>
</cac:RealizedLocation>Procedure planned period
Multiple exclusive ways exist to report the Procurement duration:
-
indicating a code (for the special cases where duration is "unknown" or "unlimited"),
-
Specifying the duration, or
-
using start & end dates,
and the most suitable one shall be adopted.
-
Duration is "unlimited" or "unknown" (Duration Other BT-538)
The "cbc:DescriptionCode" element shall be used with the respective code value "UNLIMITED" or "UNKNOWN". In this specific context, any other value from the timeperiod codelist is prohibited:
<cac:PlannedPeriod>
<cbc:DescriptionCode listName="timeperiod">UNLIMITED</cbc:DescriptionCode>
</cac:PlannedPeriod>-
Duration is limited (Duration Period BT-36)
The "cbc:DurationMeasure" element shall be used with the specification of the unit (e.g. "days") and its total number to cover the whole period. Unit of measure shall correspond to one of the duration units defined in the timeperiod codelist.
<cac:PlannedPeriod>
<cbc:DurationMeasure unitCode="DAY">3</cbc:DurationMeasure>
</cac:PlannedPeriod>-
Start & end dates are known (Duration Start Date BT-536 & End Date BT-537)
These dates shall be reported as follows:
<cac:PlannedPeriod>
<cbc:StartDate>2019-11-15+01:00</cbc:StartDate>
<cbc:EndDate>2019-11-19+01:00</cbc:EndDate>
</cac:PlannedPeriod>Extensions & renewals
When Options exist (Options BT-53), they shall be described (Options Description BT-54) using the "cbc:OptionsDescription" element.
For renewals, the maximum number of times a contract may be renewed (Renewal Maximum BT-58) shall be marked with "cbc:MaximumNumberNumeric", further information about renewal (Renewal Description BT-57) shall be marked with "cbc:Description" as illustrated below:
<cac:ContractExtension>
<cbc:OptionsDescription languageID="ENG">The buyer reserves the right to ...</cbc:OptionsDescription>
<cbc:OptionsDescription languageID="FRA">L'acheteur se réserve le droit ...</cbc:OptionsDescription>
<cbc:MaximumNumberNumeric>3</cbc:MaximumNumberNumeric>
<cac:Renewal>
<cac:Period>
<cbc:Description languageID="ENG">The buyer reserves the right to ...</cbc:Description>
<cbc:Description languageID="FRA">L'acheteur se réserve le droit ...</cbc:Description>
</cac:Period>
</cac:Renewal>
</cac:ContractExtension>Considerations:
-
"cbc:MaximumNumberNumeric" is mandatory for Notice subtypes 15 (Notice on the existence of a qualification system), 17 and 18 (Contract, or concession, notice — standard regime, Directives 2014/25/EU and 2009/81/EC)
-
"cbc:MaximumNumberNumeric" shall be a whole number (when no extension is foreseen, the element shouldn’t be used, except for Notice subtypes 15, 17 and 18, where it should have the value 0)
-
"cbc:MaximumNumberNumeric" refers to the number of possible renewals; an encoded value of "3" involves an initial contract followed by up to 3 renewals