eForms Schema Usage
Disclaimer
This document refers to the version of the eForms schemas published as part of the SDK 1.11.
The schemas and the documentation can still be subject to changes. They should therefore be considered as provisional.
Acronyms & abbreviations
BG |
Business Group |
BT |
Business Term |
CA |
Contracting Authority |
CAN |
Contract Award Notice |
CE |
Contracting Entity |
CFC |
Call For Competition |
CN |
Contract Notice |
CPB |
Central Purchasing Body |
DAP |
Direct Award Prenotification |
DPS |
Dynamic Purchasing System |
ePO |
eProcurement Ontology |
ESPD |
European Single Procurement Document |
FA |
Framework Agreement |
OJEU |
Official Journal of the European Union |
OP |
Publications Office of the European Union |
OPP |
OP Production Term |
OPT |
OP Technical Term |
PIN |
Prior Information Notice or Periodic Indicative Notice |
QS |
Qualification System |
RTL / TL |
Reduce Time Limit / Time Limit |
VEAT |
Voluntary Ex-Ante Transparency Notice |
List of figures
Figure 1, “The different Form Types”
Figure 2, “Major components of a notice”
Major reused components
Figure 4, “Overall structure of the Notice Result section”
Figure 5, “Aggregated amounts of the Notice Result”
Figure 6, “Lot Result structure”
Figure 7, “Lot Tender information”
Figure 8, “Settled Contract information”
Figure 9, “Tendering Party information”
Figure 10, “Organizations structure”
Figure 11, “Information structure for an organization”
Figure 12, “Components for a Buyer”
Figure 15, “Structure of the Organizations information”
List of tables
Notice types & subtypes
Table 2, “Notice Types and their associated schemas”
Table 3, “Namespace prefixes & names”
Table 4, “Contextual interpretation of high-level repeatable components”
Table 5, “Notice related information”
Table 6, “Numbering schemes for Parts, Lots and Group of Lots”
Table 7, “Major blocks of Procurement Procedure related information”
Table 8, “Major blocks of Group of Lots related information”
Table 9, “Major blocks of Lot related information”
Table 10, “Major blocks of Part related information”
Table 11, “Tendering terms related information”
Table 12, “Tendering process related information”
Table 17, “Direct Award Justification code context use”
Table 18, “Procurement project related information”
Table 20, “Notice aggregated amounts components”
Table 21, “LotResult components”
Table 22, “LotTender components”
Table 23, “Settled Contract components”
Table 24, “Tendering Party components”
Table 25, “Organization details requirements”
Table 26, “Technical identifiers schemes”
Table 27, “Mapping: Organization BTs — Schema components”
Table 28, “Information requirement per role”
Table 29, “Roles vs subroles”
Table 30, “Roles marked using XML elements”
Table 31, “Roles marked using Codes/indicators”
Table 32, “Sub-roles marked using XML elements”
Table 33, “Role/Subrole context”
Table 34, “Role/subrole presence per notice”
Table 35, “Buyer specific information”
Table 36, “Changes associated elements”
Table 37, “Modification components”
Table 38, “Codes for "unpublished" fields at NoticeResult level”
Table 39, “Codes for "unpublished" fields at LotResult level”
Table 40, “Codes for "unpublished" fields at LotTender level”
Table 41, “Codes for "unpublished" fields at Procedure level”
Table 42, “Codes for "unpublished" fields at Lot/Group of lots level”
Table 43, “Identifiers”
Table 44, “References”
Table 45, “Sections IDs”
Table 46, “Pointless BTs due to technical design”
Audience
The main audience of this document is destined to be people in charge of the technical implementation of the schemas. The technical schemas are developed to address the new requirements of the eForms Regulation. This document only covers the XML aspect of the XML instance and does neither suppose nor address other technical or organisational aspects (e.g. rendering, information storage …).
1. Introduction
1.1. Objective and scope
The objective of this document is to provide the person in charge of the XML generation with the information necessary for integration of the schemas.
There are three schemas foreseen to cover the 40 situations listed in the eForms Regulation (Regulation (EU) 2022/2303):
-
Prior Information Notice (PIN),
-
Contract Notice (CN), and
-
Contract Award Notice (CAN).
The schemas are based on OASIS UBL v2.3 with some extensions for eForms-specific information.
Codelists, validation rules and technical integration are outside the scope of the present document; although, if there are references to some Business Rules or codelists in this document, these will not be discussed in detail.
1.2. The Regulation
A regulation on Public Procurement (eForms) has been drafted, proposed, adopted and published in October 2019 [R1], then amended and the amended version published in November 2023 [R4]. It replaces the Implementing Regulation from November 2015 [R2].
eForms is part of the Single Market Strategy of the European Commission [R3] and will help collect, manage and analyze procurement related data; this will populate a meaningful source of information for Member States to support their initiatives on Public Procurement Governance improvement with amplified efficiency, transparency and integrity.
Some aspects that the Regulation is intended to address, are:
-
increased information accuracy;
-
forms simplification;
-
extended flexibility (e.g. ability to nationally: adapt labels to regional preferences, enforce the use of some optional fields);
-
closer consistency (amongst forms and with other documents based on the same standards),
-
intensified flexibility with specifications at Lots level;
-
improved governance with identified sellers and buyers, as well as a limited number of policy related information;
-
balanced transparency-competition aspects with justified private information;
-
simplified process for Corrigenda publications;
-
use of a procedure identifier for a better Business Opportunities identification.
1.3. Background information
In addition to the Regulation, the following have been considered for the schemas development:
-
The published UBL 2.3 schemas[1];
-
The detailed spreadsheet corresponding to Annex II of the eForms Regulation[2];
-
The numerous discussions undertaken during the different consultations[3] with the collected information regularly integrated by DG GROW in the Annex II;
-
The outcome of the eProcurement Ontology workgroup activity[4];
-
The approaches adopted for other UBL based data (ESPD, eInvoicing …).
1.4. About this document
This document is divided in different sections:
-
Sections 1 to 3 with introduction of general concepts, and
-
Sections 4 to 7 more technical.
The choice has been made to be as concise as possible using tables and cross references. Navigation between text and tables, or tables and sections is possible with a "Ctrl" + click and back navigation with "Alt" + "←".
Synthetic approach and readability concerns lead to the expression of some elements usage in a table format. In these tables, the expressed cardinality does not substitute the one of the Regulation, it is only a mean to highlight the different occurrences that may be needed for some elements at specific places for a given document type. As a kind of synthesis of the requirements for all situations covered by a document type (i.e. all columns of the Regulation Annex that a given schema intents to cover), the cardinality is more generic and may lack the precision required by the Regulation and that the validation rules will verify.
Codelists and validation rules are out of the scope of this document even if they are referenced sometimes.
Some codelists justified by the technical design of the schemas[5] won’t appear on EU Vocabularies, they will however be documented and provided with the necessary artefacts required for data validation.
To clarify the usage of some elements, some validation rules had to be stated; these do not however cover the whole set of validation rules applicable which will be provided at a later stage.
Regarding illustration, samples have been provided using 2 linguistic versions; this has been done for clarification purpose regarding encoding of multilingual notices. There is no requirement to have exactly two such linguistic versions.
References
-
[R1] Commission Implementing Regulation (EU) 2019/1780 of 23 September 2019 establishing standard forms for the publication of notices in the field of public procurement and repealing Implementing Regulation (EU) 2015/1986 (eForms) (Text with EEA relevance) , Official Journal of The European Union, OJ L 272, Oct. 25th, 2019, pp. 7 - 73, available at http://data.europa.eu/eli/reg_impl/2019/1780/oj, accessed January 27th, 2020.
-
[R2] Commission Implementing Regulation (EU) 2015/1986 of 11 November 2015 establishing standard forms for the publication of notices in the field of public procurement and repealing Implementing Regulation (EU) No 842/2011, Official Journal of The European Union, OJ L 296, Nov. 12th, 2015, pp. 1 - 146, available at http://data.europa.eu/eli/reg_impl/2015/1986/oj, accessed January 27th, 2020
-
[R3] Communication From The Commission To The European Parliament, The Council, The European Economic And Social Committee And The Committee Of The Regions, Upgrading the Single Market: more opportunities for people and business, Oct. 28th, 2015, 23 p., available at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52015DC0550, accessed January 27th, 2020
-
[R4] Commission Implementing Regulation (EU) 2022/2303 of 24 November 2022 amending Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices in the field of public procurement (Text with EEA relevance) , Official Journal of The European Union, OJ L 305, Nov. 25th, 2022, pp. 12 – 50, available at http://data.europa.eu/eli/reg_impl/2022/2303/oj, accessed January 24th, 2023.
2. Documents, forms & notices
For a common understanding, it is necessary to state what is meant by "document", "form" and "notice".
2.1. Document and Document Type
The eProcurement Ontology workgroup defined a "document" as:
A set of interrelated Business Information representing the business facts.
With the additional information:
Documents may convey information in any language, medium or form, including textual, numerical, graphic, cartographic, audio-visual forms, etc.
We will use the "document" term mainly to refer to the XML document (i.e. XML instance) containing all information of a given notice.
For eForms we may distinguish three different document types:
-
Prior Information Notice,
-
Contract Notice, and
-
Contract Award Notice.
While most notices belonging to these categories are expected to have UBL XSD schemas as normative representations, some (e.g. change notices) may involve non-UBL elements and require the use of extensions.
2.2. Form and Form Types
The eForms Regulation defines a set of forms and their associated fields foreseen for editing procurement notices. A form is an interim means that assists the contracting authority in the encoding of the required information.
There are different form types. It is common to use the "form type" name as a notice attribute to specify its belonging to a specific form type family (e.g. "Planning Notice" is commonly used to refer to a Notice that has the "Planning" form type).
The Regulation identifies different form types:
-
Planning,
-
Competition,
-
Direct Award Pre-notification (DAP),
-
Result,
-
Contract Modification,
-
Change.
Figure 1 below provides an indicative time-based representation of the different Form Types. This gives an overview of the potential successions or coexistence of the different types of forms.
2.2.1. Planning forms
Planning forms group notices published before the start of the "Call for Competition"; these are often qualified as "Planning Notices". Although "Planning Notices" are not associated to any Procedure and do not have any EU Procedure Identifier assigned, the buyer may already define and use an internal Procedure identifier.
2.2.2. Competition forms
Competition forms lead to the generation of notices initiating the "Call for Competition".
2.2.3. DAP forms
Direct Award Pre-notification (DAP) forms generate notices stating the intention to award a contract directly (i.e. without prior call for competition) to one or more Economic Operators. In contrast to the Result notices generated from the Result forms[6] the DAP notices are published prior to signing the contract. Such notices should also refer to the existing Procedure and notices that enable this awarding method.
2.2.4. Result forms
Result forms are used to produce result notices, which are published shortly after contract signature. They refer to the contract notice and provide award process information like award of contract, winner, etc.
2.2.5. Contract Modification forms
During the contract execution, a contract may need modification. If the start of a new procurement procedure is not needed, then the Contract Modification forms are used to produce a modification notice reporting the modifications applied to the contract.
2.2.6. Change forms
Change forms are used to produce change notices. The purpose of change notices is multifold:
-
Correct information reported in a previous Change notice or the original notice,
-
Inform about changes to information not inside the notice (e.g. changed procurement documents),
Changes may apply to notices of any form type. A Change notice contains all the information from the initial notice with integrated changes (i.e. consolidated text), as well as information on applied changes. When a change is applied to a previous change notice, it must integrate all changes from all previous change notices, and only have the latest changes described in the change section.
When applying changes, it is essential to ensure that the changes do not require the buyer to start a new procedure. It is the duty of the buyer to check that applied changes do not:
-
impact the applicable time limits;
-
advantage some economic operators at the expense of others;
-
require a procedure restart.
2.3. Notice, Notice Types and Subtypes
The ePO workgroup provided the following definition of a "notice":
Document published by the buyer about market opportunities and results.
As clearly stated in the definition, a document may only be considered as a notice after publication; however, at business level, it is common to use the "notice" keyword for notice candidate documents (i.e. document submitted for publication), even before their validation.
Any notice has an identifier that may be referred to, for change or for search purpose.
Speaking about "notice" may designate the XML instance or other related by-products (e.g.: PDF manifestations); in this document, we will mainly refer to the XML instance.
Regarding notices, shortened expressions are commonly used. As illustrations, the two following examples may be provided with expressions like:
-
"Planning notice" to refer to a notice of form type "Planning",
-
"PIN profile" or "PIN profile notice" for a notice of notice type "PIN profile"
A given form type groups multiple notice types as shown on Table 1 in which form types, document types, notice types, a reference to the column number of Annex II of Regulation (EU) 2022/2303, and a short description, are provided.
The concept of Notice Subtype has also been introduded for a quick, easy and univocal reference to a specific context allowing the identification of the applicable rules set. For the eForms Regulation Annex, the subtype value corresponds to the column number.
| Form Type | Document Type | Notice Type | Regulation Annex Table 2 column (Subtype) | Description |
|---|---|---|---|---|
Planning |
PIN |
PIN profile |
1-3 |
Notice of the publication of a prior information notice (or a periodic indicative notice) on a buyer profile |
PIN only |
4-6 |
Prior information notice, or periodic indicative notice, used only for information |
||
PIN time limit |
7-9 |
Prior information notice, or periodic indicative notice, used to shorten time limits for receipt of tenders |
||
Competition |
PIN |
PIN CFC general |
10-11 |
Prior information notice, or periodic indicative notice, used as a call for competition — standard regime |
PIN CFC social |
12-14 |
Prior information notice, or periodic indicative notice, used as a call for competition — light regime |
||
CN |
QS |
15 |
Notice on the existence of a qualification system |
|
CN general |
16-19 |
Contract, or concession, notice — standard regime |
||
CN social |
20-21 |
Contract notice — light regime |
||
CN subco |
22 |
Subcontracting notice |
||
CN design |
23-24 |
Design contest notice |
||
DAP |
CAN |
CAN VEAT |
25-28 |
Voluntary ex-ante transparency notice |
Result |
CAN general |
29-32 |
Contract, or concession, award notice — standard regime |
|
CAN social |
33-35 |
Contract, or concession, award notice — light regime |
||
CAN design |
36-37 |
Design contest result notice |
||
CM |
Contract modification |
38-40 |
Contract modification notice |
|
Change |
* |
Change notice |
1-40 |
Change associated to any of the above notice type |
3. Notice content
For a given procurement procedure, the content of the successively published notices varies.
3.1. Notices content
Figure 2 provides a schematic representation of a notice content. The different sections are presented in detail in section 4.
(*) The "Contract Award" section and "Direct award justification" only occur in CAN notices.
3.2. The major components
3.2.1. The notice information
The notice information covers information like:
Procedure Legal Basis |
To indicate the legal regime that applies to the procedure as a whole (e.g. "Directive 23" …). |
|---|---|
Notice Type |
To specify the type of notice (e.g. "PIN only"). |
Notice SubType |
To identify precisely the SubType of a Notice (e.g. any value from 1 to 40 for the eForms Regulation Annex, E1 to E5 for extended forms …) |
Form Type |
To indicate the Form Type (i.e. major "phase" before, or during, the procurement procedure). |
Procedure Type |
To provide the type of procedure (e.g. "Competitive dialog" …). |
Dispatch Date |
The date and time, the notice is sent to OP for publication. This information will be controlled by the Publications Office after receipt of the notice. |
Procedure Identifier |
For any notice Form Type (besides "Planning"), the Identifier of the procedure to which the notice belongs. |
Notice & Notice Version Identifiers |
Notice and notice version identifiers help differentiate notices along with their versions. |
Preferred Notice Publication Date |
Preferred date for publication that the contracting authority may specify to ensure respect of the existing restrictions between national and European publication dates. |
Notice Official Languages |
The official EU languages in which the whole notice is available |
3.2.2. Buyer information
The buyer information covers key Contracting Authority/Entity related information such as:
Identification of the buyer |
Covers official name, National ID, postal address, contact details, Website and Buyer profile. |
|---|---|
Joint initiative |
Whether a Joint Procurement and/or a Central Purchasing Body are involved. |
Means of communication |
Addresses (URL, e-mail, postal) to access procurement documents, request additional information, submit tenders or a Request for Participation. |
Type of CA / CE |
Whether the buyer is a Contracting Entity or a Contracting Authority and its type (e.g. "Regional or local agency/office"). |
Buyer’s main activity |
The specific sector the contracting authority or entity is active in. |
3.2.3. Procurement object(s)
For each object, this refers to the purpose of the procurement and its subcomponents, composed as follows:
Procurement scope |
Internal reference number, title, main CPV codes, main and additional nature (e.g. Works), a short description, estimated value and information about Lots. |
|---|---|
Lot/Part description |
Lot identifier, title, additional main CPV codes, place of performance, description, awarding criteria, estimated value, duration (also for FA & DPS), variants, options, EU funds and additional information. |
Foreseen CN publication date |
Only for PINs that are not calls for competition. Foreseen date of publication of the contract notice. |
3.2.4. Selection criteria
Conditions for participation |
Professional suitability, financial standing, technical ability, reserved contract information. |
|---|---|
Contract conditions |
Reserved to a particular profession, contract performance conditions, names and qualifications of assigned staff. |
3.2.5. Procedure
Description |
Procedure type, information on FA or DPS, eAuction, GPA coverage |
|---|---|
Administrative information |
Reception time limits, tendering accepted languages, award procedure start date. |
3.2.6. Contract award
Per contract for awarded and per Lot/Group of Lots for non-awarded
Non-award information |
Justification for not awarding, and statistics on tenders and tenderers. |
|---|---|
Contract award |
Contract conclusion date, statistics about tenders, tenderers, winner identification (name & address), Contract value, Subcontract information |
3.2.7. Further information
Recurring information |
Whether the notice is a recurring one. |
|---|---|
Electronic workflows |
About the use of such workflows (e.g. for ordering, invoicing, payment) during contract execution. |
Additional information |
Any other additional information. |
Review procedures |
Review Body, Mediation Body, information & deadlines. |
Procedure justification |
Direct Award justification. |
Additional contacts |
Further contact details for: additional information, specifications & additional documents, submission of tenders/request for participation, delegating CA/CE. |
5. Schemas
Three schemas will cater for the different categories of notices. Table 2 provides the correspondence between notice categories and the schemas.
For Change notices, the required schema is the one of the notice subject to changes (e.g. a Change Notice for a change applied to an existing Contract Notice shall comply with the ContractNotice schema).
| Notice category | Notice Type | Schema |
|---|---|---|
Prior Information / Periodic Indicative Notice |
|
PriorInformationNotice |
Contract Notice |
|
ContractNotice |
Direct Award Pre-notification Notice |
|
ContractAwardNotice |
Contract Award Notice |
|
|
Contract Modification Notice |
|
|
Change Notice |
|
Any of the 3 |
The schemas are built using elements from different namespaces (some defined by UBL, others created for the purpose of eForms) and a version number will be used to distinguish different releases. Information on namespaces and schema versioning is provided below.
5.1. Namespaces
The namespaces used in the eForms schemas are described below in Table 3.
Please note that the names below are URIs (i.e. Uniform Resource Identifiers) used to uniquely identify the domains. They are not URLs (i.e. Uniform Resource Locators) to any online resource.
Prefix |
Name |
Description |
— |
urn:oasis:names:specification:ubl:schema:xsd:PriorInformationNotice-2 urn:oasis:names:specification:ubl:schema:xsd:ContractNotice-2 urn:oasis:names:specification:ubl:schema:xsd:ContractAwardNotice-2 |
No namespace prefix for the root element |
cac |
urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2 |
Covers all UBL common aggregated components |
cbc |
urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2 |
Covers all UBL common basic components |
ext |
urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2 |
Covers all UBL common extension components |
efext |
http://data.europa.eu/p27/eforms-ubl-extensions/1 |
Covers all eForms specific extension components |
efac |
http://data.europa.eu/p27/eforms-ubl-extension-aggregate-components/1 |
Covers all eForms specific extension aggregate components |
efbc |
http://data.europa.eu/p27/eforms-ubl-extension-basic-components/1 |
Covers all eForms specific extension basic components |
5.2. Versioning
Please consult the versioning information provided in detail here.
6. Notices XML structure
The information in the XML instance covers information related to:
-
The notice,
-
The procurement procedure, and
-
The Parts, Lots or Group of Lots.
As shown on Figure 3 below, the latter two share key structures that shall be interpreted in their respective contexts.
For simplification, not all information has been represented in the diagram below and the focus was placed on high level key repeating components. Also for uniformity and simplification, Procedures without lots (and PIN without parts) are to be treated technically as a procedure with exactly one lot (or part).
Notice information is represented with an orange background; Procurement Procedure information with a green one; and information for Group of Lots, Lot, or Part with a purple background.
The contextual use of each of these components is reported in Table 4, which lists the component name, its context and the associated component purpose (i.e. information it covers).
| Component | Context | Purpose |
|---|---|---|
Tendering Terms |
Document root |
Legal, economic, financial and technical information for the procurement as a whole. |
Procurement Project Lot |
Legal, economic, financial and technical information for the Lot (Part, or Group of Lots) only. |
|
Tendering Process |
Document root |
Procurement Procedure information |
Procurement Project Lot |
Specific procedure information for the Lot (Part, or Group of Lots) |
|
Procurement Project |
Document root |
Scope of the procurement |
Procurement Project Lot |
Purpose of the Lot (Part, or Group of Lots) |
Further details on these different components will be provided in Procedure, Group of Lots, Lot & Part related information and following sections.
6.1. The notice metadata
The notice metadata cover the following information:
-
Identification of the notice (notice identifier & version),
-
Procurement Procedure identifier of the Procedure it belongs to,
-
Notice context (form type, notice type, legal basis),
-
Key dates (dispatch, publication, etc.),
-
Publication related information (e.g. OJ S no., status, publication date),
-
Notice official linguistic version(s).
6.2. Procedure, Groups of Lots, Lots and Parts
Information about the Procedure, the Groups of Lots, the Lots or the Parts share the same set of components at the highest level (i.e. Tendering Terms, Tendering Process and Procurement Project). Figure 3 highlights that these major components are reused over the instance and that their meaning is highly linked to the context:
-
as direct children of the notice root component, they refer to the procurement Procedure;
-
as children of a Procurement Project Lot component, they refer to the corresponding Group of Lots, Lot or Part.
6.3. Business Terms
The Business Terms listed in Annex II of the eForms Regulation are described in this document, and use the same identifiers beginning with "BT-".
Basing the development of the eForms schema on the UBL schema, as well as conferring many advantages, has also imposed some constraints. These constraints have required the creation of a number of terms which were not anticipated in the eForms Regulation; they do not have a true Business justification. They have been assigned different abbreviations, starting with "OP" to distinguish them from the BT terms defined in the eForms Regulation (see Field metadata for more details).
6.4. Dates and Times
All dates and times in eForms XML shall be expressed in ISO-8601 format, with local time marked as an offset from Coordinated Universal Time. When a date is associated with a time, both must share the same shift to Coordinated Universal Time.
Time values shall vary from 00:00:00.0000 to 24:00:00 excluded[7], with as many decimals for the seconds as required.
A notice sent on November 26th, 2019 at 1:38:54 PM CET (i.e. UTC +1) to OP shall be marked:
<cbc:IssueDate>2019-11-26+01:00</cbc:IssueDate>
<cbc:IssueTime>13:38:54+01:00</cbc:IssueTime>When referring to midnight (end of the day for a given date), use 00:00:00 (start of the following day) instead and adjust the referenced day (month and year) accordingly.
For December 5th, 2020 at midnight CET, the markup shall be:
<cbc:IssueDate>2020-12-06+01:00</cbc:IssueDate>
<cbc:IssueTime>00:00:00+01:00</cbc:IssueTime>When dates and times in UTC are used, the offset of zero can be stated numerically as "+00:00", or the zero UTC offset zone designator "Z" may be used:
<cbc:IssueDate>2020-03-21Z</cbc:IssueDate>
<cbc:IssueTime>18:00:00Z</cbc:IssueTime>7. Notice information
The elements at the upper most level of the XML instance of a notice, concern the information listed in Table 5. This table contains the Business Terms, a shortened description, its cardinality and the XML elements used to mark the information. The specified cardinality is more restrictive than the one in the schema; it is used to express requirements stated in the 2022 Regulation Annex.
| eForms BT | Details | Card. | XSD element |
|---|---|---|---|
Notice SubType (OPP-070) |
1 |
efac:NoticeSubType/cbc:SubTypeCode |
|
Notice Dispatch Date eSender (BT-803) - date |
? |
efbc:TransmissionDate |
|
Notice Dispatch Date eSender (BT-803) - time |
? |
efbc:TransmissionTime |
|
Notice Publication ID (OPP-010) |
? |
efac:Publication/efbc:NoticePublicationID[@schemeName='ojs-notice-id'] |
|
OJEU Identifier (OPP-011) |
? |
efac:Publication/efbc:GazetteID[@schemeName='ojs-id'] |
|
OJEU Publication Date (OPP-012) |
? |
efac:Publication/efbc:PublicationDate |
|
UBL version ID (UBL) |
1 |
cbc:UBLVersionID |
|
Customization ID (UBL) |
1 |
cbc:CustomizationID |
|
Notice Identifier (BT-701) |
1 |
cbc:ID |
|
Procedure Identifier (BT-04) |
0..1 |
cbc:ContractFolderID |
|
Notice Dispatch Date (BT-05) |
1 |
cbc:IssueDate cbc:IssueTime |
|
Notice Version (BT-757) |
1 |
cbc:VersionID |
|
Notice Preferred Publication Date (BT-738) |
0..1 |
cbc:RequestedPublicationDate |
|
Future Notice (BT-127) |
0..1 |
cbc:PlannedDate |
|
Procedure Legal Basis (BT-01) |
1 |
cbc:RegulatoryDomain |
|
Form Type (BT-03) |
1 |
cbc:NoticeTypeCode/@listName |
|
Notice Type (BT-02) |
1 |
cbc:NoticeTypeCode |
|
Notice Official Language (BT-702) |
1..n |
cbc:NoticeLanguageCode cac:AdditionalNoticeLanguage/cbc:ID |
|
Organization (Buyer, CPB, Service Provider …) |
1..n |
cac:ContractingParty and child elements |
7.1. Notice Publication information
The Notice Publication information (Date, OJEU and OJS Notice IDs) shall be marked the following way:
<efac:Publication>
<efbc:NoticePublicationID schemeName="ojs-notice-id">12345678-2023</efbc:NoticePublicationID>
<efbc:GazetteID schemeName="ojs-id">123/2023</efbc:GazetteID>
<efbc:PublicationDate>2023-03-14+01:00</efbc:PublicationDate>
</efac:Publication>7.2. UBL version ID
The earliest UBL 2 version containing all elements of the schema (besides the ones from the extension) is "2.3". Unless differently stated, this is the only expected and accepted value.
<cbc:UBLVersionID>2.3</cbc:UBLVersionID>7.3. Customization ID
This element identifies the customization used for the notice. Identification is based on the complete set (schemas+rules) limited to the major and minor version numbers (cf. Versioning).
<cbc:CustomizationID>eforms-sdk-0.3</cbc:CustomizationID>7.4. Notice & Version Identifiers
The "Notice identifier" identifies a notice amongst all other existing ones. A notice may have multiple versions and only the different versions of a given notice shall share the notice identifier value. Versions of a notice are purely editorial and for a given Notice ID, a single version may be published.
The notice identifier shall follow a predefined scheme, it will be a version 4 Universally Unique Identifier (UUID):
<cbc:ID schemeName="notice-id">0f56d80f-8a5f-4876-8e24-feaa766c456d</cbc:ID>The version identifier of a given notice shall increase with any new version of that notice. New versions use the same schema as the original notice. The identifier shall be a two characters positive integer (i.e. "00" excluded). The version "01" shall be kept for the first version of the notice, subsequent versions shall be submitted and received in increasing numbering order.
<cbc:VersionID>01</cbc:VersionID>Any received valid notices shall all have a unique Notice ID independently from the version ID
7.5. Procedure Identifier
The Procedure Identifier allows distinguishing procurement procedures and shall be globally unique. Specified in the notice, it identifies the procurement procedure the notice belongs to.
Like the Notice Identifier, the Procedure Identifier shall be a version 4 UUID.
<cbc:ContractFolderID>1e86a664-ae3c-41eb-8529-0242ac130003</cbc:ContractFolderID>Performed controls ensure its uniqueness[8] and help check consistency amongst received notices (For a given procedure, sequence and content of notices will be carefully checked).
This information does not exist for notices of "Planning" form type.
7.6. Notice Dispatch Date eSender (BT-803)
The Notice Dispatch Date eSender (BT-803) represents the date and time the notice was transmitted electronically by the eSender to the Publications Office of the European Union. It may be indicated in the extensions at Root by specifying its two components (date & time):
<efbc:TransmissionDate>2022-11-17+01:00</efbc:TransmissionDate>
<efbc:TransmissionTime>08:30:03+01:00</efbc:TransmissionTime>When it comes to validation and date controls, the Notice Dispatch Date eSender (BT-803), when specified, is used instead of the Notice Dispatch Date (BT-05), see below.
7.7. Notice Dispatch Date
The date and time of the notice submission by the buyer. This date will be added before its submission to OP and its trustworthiness evaluated based on the actual receipt time and a range of acceptable variations[9].
When the processing by the eSender introduces a significant delay after the submission by the buyer, to avoid falling outside of the acceptable range, the Notice Dispatch Date eSender (BT-803) can also be used.
A notice sent on November 26th, 2019 at 1:38:54 PM CET (i.e. UTC +1) to OP shall be marked:
<cbc:IssueDate>2019-11-26+01:00</cbc:IssueDate>
<cbc:IssueTime>13:38:54+01:00</cbc:IssueTime>7.8. Notice Preferred Publication Date
The "Notice Preferred Publication Date" is the date on which the buyer wishes the notice to be published on the TED website. It can be used to help the buyer respect the requirements that exist between publications at national and European levels.
The publication request of a notice for March 15th, 2020 shall be marked:
<cbc:RequestedPublicationDate>2020-03-15+01:00</cbc:RequestedPublicationDate>7.9. Future Notice
The "cbc:PlannedDate" element is used for planning notices (PIN Profile excluded) to specify when the competition notice will be published. Mark-up should be as follows:
<cbc:PlannedDate>2020-03-15+01:00</cbc:PlannedDate>7.10. Procedure Legal Basis
The Procedure Legal Basis term refers to the EU regulatory domain that applies to the procurement.
The value is the corresponding CELEX number (e.g. "32014L0024" for Directive 2014/24). Only some values of the dedicated codelist may be used in the context of the eProcurement. The "other" value shall exclusively be used for below threshold notices. Further needed Legal Basis may be specified as specified in Cross Border Law (Procedure) (BT-09).
A notice for a procedure under Directive 2014/24 shall have its legal basis information identified using:
<cbc:RegulatoryDomain>32014L0024</cbc:RegulatoryDomain>National and other local Legal Bases should be expressed as specified in Legal Basis (BT-01).
7.11. Form and Notice Types, Notice Subtype
The information associated with these terms evolves with the procedure. Existing codelists (i.e. form-type, notice-type and the technical notice-subtype) specify acceptable values; these values must also be consistent with each other (i.e. specified values must comply with the situations as described in Notice types & subtypes).
The Notice SubType (OPP-070) shall be marked as follow:
<efac:NoticeSubType>
<cbc:SubTypeCode listName="notice-subtype">16</cbc:SubTypeCode>
</efac:NoticeSubType>A notice of "Planning" form type and "PIN only" notice type shall have this information marked the following way:
<cbc:NoticeTypeCode listName="planning">pin-only</cbc:NoticeTypeCode>7.12. Notice Official Language
The "Notice Official Language" designates an EU Official language in which the notice is officially available.
Notice official languages shall be marked:
<cbc:NoticeLanguageCode>ENG</cbc:NoticeLanguageCode>
<cac:AdditionalNoticeLanguage>
<cbc:ID>DEU</cbc:ID>
</cac:AdditionalNoticeLanguage>
<cac:AdditionalNoticeLanguage>
<cbc:ID>FRA</cbc:ID>
</cac:AdditionalNoticeLanguage>Using:
-
"cbc:NoticeLanguageCode" for a first official language[10], and
-
"cac:AdditionalNoticeLanguage" for any additional official language.
In the XML instance, the attribute "languageID" of a text-type element, identifies, using a language code, the language used for the text. The specification of the value for this attribute is required for all text-type elements within a notice[11].
A "Notice non-official language" refers to any (EU) Official Language not considered as authentic (i.e. for which only part of the notice text exist). The whole list of such languages may be deduced from the specified "languageID" attribute values and the marked-up notice official languages.
Non-EU languages are not to be considered for publication at EU level and should therefore not be referenced. Each text-type element should be used once and only once for a given language.
For a given procurement procedure, the list of official languages shall be the same for all notices.
7.13. Organizations
Organizations informations are grouped into a dedicated element in an extension and referred to in the rest of the XML instance as explained in Parties where details on information mark-up may be found.
The "cac:ContractingParty" element allows for encoding of the parties involved in the procurement procedure, like "buyer" (including description of their role in a joint procurement), or "service provider" (e-Sender, Procurement service provider …).
8. Procedure, Group of Lots, Lot & Part related information
8.1. 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 6. 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[12];
-
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 § 8.3.24;
-
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.
8.2. 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 |
|
8.3. Tendering terms
Tendering terms group information as diverse as EU funding, exclusion grounds, reserved participation/execution.
Table 11 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[13] 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 Official Language (BT-708) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Documents Unofficial Language (BT-737) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Documents Restricted Justification (BT-707) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Documents Restricted (BT-14) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Documents URL (BT-15) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
Documents Restricted URL (BT-615) |
— |
— |
? |
? |
— |
? |
— |
— |
|
|
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 Indication and 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 Description (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 Complicated (BT-543) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Number Weight (BT-5421) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Number Fixed (BT-5422) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Number Threshold (BT-5423) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Number (BT-541) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Type (BT-539) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Name (BT-734) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
Award Criterion Description (BT-540) |
— |
? |
? |
— |
? |
? |
? |
? |
|
|
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 Allowed (BT-31) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Group definition |
||||||||||
Group Identifier (BT-330) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
Group Lot Identifier (BT-1375) |
? |
— |
— |
— |
— |
— |
— |
— |
|
|
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 Description (BT-732) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Contexts: (*) (**) |
||||||||||
8.3.1. 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.
8.3.2. 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-programme">ERDF_2021</cbc:FundingProgramCode>
<cbc:Description languageID="ENG">This local project ...</cbc:Description>
<cbc:Description languageID="FRA">Ce projet local ...</cbc:Description>
</efac:Funding>8.3.3. 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[14]. 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[15]:
-
"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>8.3.4. 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>8.3.5. 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.
8.3.6. 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>8.3.7. 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>8.3.8. 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>8.3.9. 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>8.3.10. 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" (OPT-140) 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 language(s) in which the documents are available (BT-708 or BT-737), this has to be specified with values from the language codelist.
<cac:CallForTendersDocumentReference>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:NonOfficialLanguages>
<cac:Language>
<cbc:ID>FRA</cbc:ID>
</cac:Language>
<cac:Language>
<cbc:ID>DEU</cbc:ID>
</cac:Language>
</efac:NonOfficialLanguages>
<efac:OfficialLanguages>
<cac:Language>
<cbc:ID>ENG</cbc:ID>
</cac:Language>
</efac:OfficialLanguages>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<cbc:ID>20210521/CTFD/ENG/7654-02</cbc:ID>
<cbc:DocumentTypeCode listName="communication-justification">ipr-iss</cbc:DocumentTypeCode>
<cbc:DocumentType>restricted-document</cbc:DocumentType>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://mywebsite.com/proc/2019024/accessinfo</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:CallForTendersDocumentReference>8.3.11. 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>8.3.12. 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>8.3.13. 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>8.3.14. 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>8.3.15. 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>8.3.16. 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>8.3.17. 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"[16], the Subcontracting Obligation Minimum (BT-64) and Subcontracting Obligation Maximum (BT-729) shall be specified; when the code value is "subc-chng"[17], "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>8.3.18. 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>8.3.19. 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>8.3.20. 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>8.3.21. 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>8.3.22. 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>8.3.23. Submission Electronic Signature (BT-744)
Whether or not the use of electronic signature[18] 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>8.3.24. 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;
8.3.25. 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".
8.3.26. 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. § 8.3.3), 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>8.3.27. 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>8.3.28. 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>8.3.29. 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.
8.3.30. 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.
8.3.31. 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>8.3.32. 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>8.3.33. 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".
8.3.34. 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. § 8.4.21), 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>8.3.35. 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>8.4. 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 Part Identifier (BT-1251) |
— |
— |
* |
? |
— |
* |
— |
* |
|
|
Submission Nonelectronic Justification (BT-19) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Submission Nonelectronic 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 (BT-51) |
— |
— |
? |
— |
— |
? |
— |
— |
|
|
Minimum Candidates (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: (*) (**) |
||||||||||
8.4.1. 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>8.4.2. 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>8.4.3. 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>8.4.4. 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>8.4.5. 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.
The following tables provide the list of possible Procedure Type values for a given Notice subtype (X: allowed code; --: forbidden code; A: allowed code and procedure may additionally be accelerated) :
eForms subtype |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
Legal basis |
D24 |
D25 |
D81 |
D24 |
D25 |
D81 |
D24 |
D25 |
D81 |
Forbidden - Optional - Mandatory |
F |
F |
F |
F |
F |
F |
O |
O |
O |
open |
— |
— |
— |
— |
— |
— |
X |
X |
— |
restricted |
— |
— |
— |
— |
— |
— |
X |
— |
X |
neg-w-call |
— |
— |
— |
— |
— |
— |
X |
X |
X |
neg-wo-call |
— |
— |
— |
— |
— |
— |
— |
— |
— |
comp-dial |
— |
— |
— |
— |
— |
— |
— |
— |
— |
innovation |
— |
— |
— |
— |
— |
— |
— |
— |
— |
oth-single |
— |
— |
— |
— |
— |
— |
X |
X |
— |
oth-mult |
— |
— |
— |
— |
— |
— |
X |
X |
— |
comp-tend |
— |
— |
— |
— |
— |
— |
— |
— |
— |
exp-int-rail |
— |
— |
— |
— |
— |
— |
— |
— |
— |
eForms subtype |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
Legal basis |
D24 |
D25 |
D24 |
D25 |
D23 |
D25 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D81 |
D24 |
D25 |
Forbidden - Optional - Mandatory |
M |
M |
O |
O |
F |
F |
M |
M |
M |
F |
O |
O |
F |
M |
M |
open |
— |
— |
— |
— |
— |
— |
A |
A |
— |
— |
X |
X |
— |
X |
X |
restricted |
X |
X |
X |
X |
— |
— |
A |
A |
A |
— |
X |
X |
— |
X |
X |
neg-w-call |
X |
X |
X |
X |
— |
— |
A |
A |
A |
— |
X |
X |
— |
— |
— |
neg-wo-call |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
comp-dial |
X |
X |
X |
X |
— |
— |
X |
A |
X |
— |
X |
X |
— |
— |
— |
innovation |
X |
X |
X |
X |
— |
— |
X |
A |
— |
— |
X |
X |
— |
— |
— |
oth-single |
X |
X |
X |
X |
— |
— |
X |
X |
X |
— |
X |
X |
— |
X |
X |
oth-mult |
X |
X |
X |
X |
— |
— |
X |
X |
X |
— |
X |
X |
— |
X |
X |
comp-tend |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
exp-int-rail |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
eForms subtype |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
Legal basis |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D23 |
D24 |
D25 |
D24 |
D25 |
D23 |
Forbidden - Optional - Mandatory |
M |
M |
M |
M |
M |
M |
M |
F |
O |
O |
F |
M |
M |
F |
F |
F |
open |
— |
— |
— |
— |
A |
A |
— |
— |
X |
X |
— |
X |
X |
— |
— |
— |
restricted |
— |
— |
— |
— |
A |
A |
A |
— |
X |
X |
— |
X |
X |
— |
— |
— |
neg-w-call |
— |
— |
— |
— |
A |
A |
A |
— |
X |
X |
— |
— |
— |
— |
— |
— |
neg-wo-call |
X |
X |
X |
X |
X |
X |
X |
— |
X |
X |
— |
— |
— |
— |
— |
— |
comp-dial |
— |
— |
— |
— |
X |
A |
X |
— |
X |
X |
— |
— |
— |
— |
— |
— |
innovation |
— |
— |
— |
— |
X |
A |
— |
— |
X |
X |
— |
— |
— |
— |
— |
— |
oth-single |
X |
X |
X |
X |
X |
X |
X |
— |
X |
X |
— |
X |
X |
— |
— |
— |
oth-mult |
X |
X |
X |
X |
X |
X |
X |
— |
X |
X |
— |
X |
X |
— |
— |
— |
comp-tend |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
exp-int-rail |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
eForms subtype |
CEI |
T01 |
T02 |
X01 |
X02 |
Legal basis |
R1046 |
R1370 |
R1370 |
R2157 R1435 |
R2137 |
Forbidden - Optional - Mandatory |
F |
M |
M |
F |
F |
open |
— |
— |
— |
— |
— |
restricted |
— |
— |
— |
— |
— |
neg-w-call |
— |
— |
— |
— |
— |
neg-wo-call |
— |
X |
X |
— |
— |
comp-dial |
— |
— |
— |
— |
— |
innovation |
— |
— |
— |
— |
— |
oth-single |
— |
— |
— |
— |
— |
oth-mult |
— |
— |
— |
— |
— |
comp-tend |
— |
X |
X |
— |
— |
exp-int-rail |
— |
X |
X |
— |
— |
For PIN CFC social & CN social notices with procedure type "oth-mult" or "oth-single", the procedure features (BT-88) must also be specified.
As an example of the XML markup, for a competitive dialog, the Procedure Type is marked:
<cbc:ProcedureCode listName="procurement-procedure-type">comp-dial</cbc:ProcedureCode>8.4.6. 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."
8.4.7. 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>8.4.8. 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.
8.4.9. 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>8.4.10. 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>8.4.11. 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>8.4.12. 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>8.4.13. 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>8.4.14. 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>8.4.15. 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>8.4.16. 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>8.4.17. 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>8.4.18. 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[19];
-
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.
8.4.19. 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.
8.4.20. 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>8.4.20.1. 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 for an eForms notice) or to the Result or Change notice (using its ojs-notice-id for a TEDXML notice) 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 17.
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 |
||||||||
8.4.21. 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;
8.4.22. 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>8.4.23. 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>8.4.24. 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)[22]
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).
8.4.25. 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>8.5. 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 Description (BT-777) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
Procurement type (*) |
||||||||||
Green Procurement (BT-774) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
Green Procurement Criteria (BT-805) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
Social Procurement (BT-775) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
Procurement of Innovation (BT-776) |
— |
— |
* |
— |
— |
* |
— |
* |
|
|
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) |
1 |
— |
1 |
1 |
— |
1 |
— |
1 |
Or |
|
Main Classification Code (BT-262) |
1 |
— |
1 |
1 |
— |
1 |
— |
1 |
|
|
Additional Classification Code (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: (*) |
||||||||||
8.5.1. 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>8.5.2. 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.
8.5.2.1. Main & Additional Nature (BT-23, BT-531)
The possible values are listed in the contract-nature codelist[23].
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.
8.5.2.2. 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.
8.5.2.3. 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>8.5.3. 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[24].
A procurement dealing with 45,000 tonnes of supplies shall be marked:
<cbc:EstimatedOverallContractQuantity unitCode="TNE">45000</cbc:EstimatedOverallContractQuantity>8.5.4. 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>8.5.5. 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>8.5.6. 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>8.5.7. 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[25].
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>8.5.8. 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>8.5.9. 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.
Also some flexibility is given with the possibility to combine some elements for further precision without contradicting the previous requirement. All the possible cases are reported in the table below where X indicates that an element is used and (X) that an element may be used under some condition only:
Case |
Duration Start Date (BT-536) |
Duration End Date (BT-537) |
Duration Period (BT-36) |
Duration Other (BT-538) |
#1 |
X |
X |
||
#2 |
X |
|||
#3 |
X |
|||
#4 |
X |
X |
||
#5 |
X |
X |
||
#6 |
X |
X |
||
#7 |
(X) |
X |
(X): only possible when duration other differs from "unlimited"
-
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>8.5.10. 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
9. Competition Results
Competition results are shared using result notices. Such notices have a single "efac:NoticeResult" element containing information about the latest award decisions and potentially about the lots still to be awarded.
9.1. Notice Result
The Notice Result section of a Result notice contains various information (cf. Figure 4):
-
The result for a lot for which the decision was recently made or is still pending,
-
The tenders received for the lots about which a decision has been made and is shared with the notice,
-
The contracts that have been signed following the award of lots,
-
The parties that submitted tenders for the lots of the notice whose awarding decision has been made and is shared in the notice.
-
The aggregated amounts covering all awarded lots of the notice.
All these topics will be further detailed in the following sections.
It should also be considered that this structure differs from the one defined by the Standard and to comply with it, cac:TenderResult/cbc:AwardDate must be present in the XML instance. It is sufficient to have only one such occurrence and the associated value shall be "2000-01-01Z".
9.2. Notice aggregated amounts
Notice Value is about the aggregated value of all awarded lots of the notice.
Notice Framework Value is about the aggregated Maximum Framework Value, estimated or actual, for all awarded lots of the notice[26].
For any group of lots of the notice having a group framework agreement, the reference to the Group of lots as well as the Group Framework Value (Maximum and/or Reestimated) shall be specified. Group Framework Values and the associated reference to the lot may be "unpublished"; when done so, the dates of publication for all unpublished elements shall be the same.
All these amounts have to be expressed using codes of the Currency codelist to designate the currency as "currencyID" attribute and decimal numbers.
Further details on the fields may be found in the following table and an overview of the structure as well as a mark-up excerpt are provided later on.
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Notice Result associated amounts (*) |
|||
Notice Value (BT-161) |
The value of all contracts awarded in this notice, including options and renewals. |
1 |
|
Notice Framework Maximum Value (BT-118) |
The maximum value which can be spent within the framework agreement(s) announced in this notice over its whole duration, in all lots, including options and renewals. |
1 |
|
Notice Framework Approximate Value (BT-1118) |
The approximate value to be spent within the framework agreement(s) announced in this notice over its/their whole duration, in all lots |
1 |
|
Group Framework Value (**) |
|||
Unpublish fields |
|||
Group Framework Maximum Value Lot Identifier (BT-556) |
Identifier of the group of lots within this procedure. |
1 |
|
Group Framework Maximum Value (BT-156) |
The maximum value which can be spent in a framework agreement within a group of lots. It covers all contracts to be awarded within a framework agreement over its whole duration, including options and renewals. |
1 |
|
Group Framework Re-estimated Value (BT-1561) |
The estimated value which can be spent in a framework agreement within a group of lots. It covers all contracts to be awarded within a framework agreement over its whole duration, including options and renewals. |
1 |
|
Context: (*) (**) |
|||
<efac:NoticeResult>
<cbc:TotalAmount currencyID="EUR">123456.00</cbc:TotalAmount>
<efbc:OverallMaximumFrameworkContractsAmount currencyID="EUR">3400000</efbc:OverallMaximumFrameworkContractsAmount>
<efac:GroupFramework>
<efbc:GroupFrameworkMaximumValueAmount currencyID="EUR">1200000</efbc:GroupFrameworkMaximumValueAmount>
<efac:TenderLot>
<cbc:ID schemeName="LotsGroup">GLO-0001</cbc:ID>
</efac:TenderLot>
</efac:GroupFramework>
<efac:GroupFramework>
<efbc:GroupFrameworkMaximumValueAmount currencyID="EUR">800000</efbc:GroupFrameworkMaximumValueAmount>
<efac:TenderLot>
<cbc:ID schemeName="LotsGroup">GLO-0002</cbc:ID>
</efac:TenderLot>
</efac:GroupFramework>
<!-- Interrupted Mark-up -->
</efac:NoticeResult>
9.3. Lot Result
A Notice Result shall contain at least one LotResult with a made decision[27].
LotResult applies exclusively to a single lot. This element contains various information (cf. table below and against figure):
-
Statistics on received submissions (highest & lowest value tenders, received quantity per submission type),
-
Procurement procedure outcome, and when not awarded the background reason,
-
Termination of a DPS,
-
Financing and Paying Parties,
-
Review requests statistics,
-
References to the received tenders for the lot covered by this result,
-
Framework Agreement Values associated to the lot (estimated and maximal),
-
Reference(s) to the contract(s) settled as a result of the made decision,
-
Statistical results for some strategic procurement projects[28],
-
Reference to the lot the result applies to.
For each lot, there may not exist more than one LotResult within the same notice.
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Lot Result (*) |
|||
"Unpublish" fields |
(BT-710, BT-711, BT-142) Cf. LotResult Level |
||
LotResult Technical ID (OPT-322) |
Unique identifier for the LotResult. Shall follow the scheme "RES-XXXX". |
1 |
|
Tender Value highest (BT-711) |
Value of the admissible tender with the highest value. A tender shall be considered admissible where it has been submitted by a tenderer, who has not been excluded and who meets the selection criteria, and when it is in conformity with the technical specifications without being irregular (e.g. received late, having an abnormally low price or cost) or unacceptable or unsuitable. Only tenders for which it has been verified that they are admissible can be taken into account. |
1 |
|
Tender Value Lowest (BT-710) |
Value of the admissible tender with the lowest value. A tender shall be considered admissible where it has been submitted by a tenderer, who has not been excluded and who meets the selection criteria, and when it is in conformity with the technical specifications without being irregular (e.g. received late, having an abnormally low price or cost) or unacceptable or unsuitable. Only tenders for which it has been verified that they are admissible or can be taken into account. |
1 |
|
Winner Chosen (BT-142) |
Whether a winner was chosen. (Code from the Winner Selection Status codelist) |
1 |
|
Dynamic Purchasing System Termination (BT-119) |
The dynamic purchasing system is terminated. No further contracts, besides those published in this notice, will be awarded in the dynamic purchasing system. This field can be used even if no contracts are awarded in the contract award notice. Only two values are possible "true" and "false". |
? |
|
Financing Party |
Organisation whose budget is used to pay for the contract |
* |
|
Payer Party |
Organisation executing the payment |
* |
|
"Unpublish" fields |
BT-712 Cf. LotResult Level |
||
Buyer Review Complainants (BT-712) |
The number of organisations that requested the buyer to review any of its decisions (e.g. the technical specifications, award decision). |
? |
|
Buyer Review Requests Irregularity Type (BT-636) |
The type of irregularity alleged in the review requests. (Code from the Irregularity Type codelist) |
* |
|
Buyer Review Requests Count (BT-635) |
The number of requests the buyer received to review any of its decisions. |
* |
|
"Unpublish" fields |
BT-144 Cf. LotResult Level |
? |
|
Not Awarded Reason (BT-144) |
The reason for not choosing a winner. (Code from the Non Award Justification codelist) |
1 |
|
Tender Identifier Reference (OPT-320) |
Identifier to refer to the appropriate Tender object. Shall follow the "TEN-XXXX" scheme. |
* |
|
"Unpublish" fields (Framework) |
BT-709, BT-660 Cf. LotResult Level |
||
Framework Re-estimated Value (BT-660) |
The estimated value which can be spent within a framework agreement over its whole duration, including options and renewals. |
? |
|
Framework Maximum Value (BT-709) |
The maximum value which can be spent within a framework agreement over its whole duration, including options and renewals. |
? |
|
"Unpublish" fields |
(BT-759, BT-760) Cf. LotResult Level |
* |
|
Received Submissions Type (BT-760) |
The type of tenders or requests to participate received. The total number of tenders received must be given. When a notice does not fall under Directive 2009/81/EC and is not about social or other specific services, the number of tenders received from micro, small and medium enterprises; the number of tenders received from tenderers registered in other European Economic Area countries and the number of tenders received from tenderers registered in countries outside of the European Economic Area must also be given. All tenders must be counted, regardless of whether they are admissible or inadmissible. For tenders submitted by a group of tenderers (e.g. a consortium), the tender must be counted in the relevant category (e.g. SME) if the majority of the work is expected to be done by tenderers which fall within this category (e.g. they are SMEs). (Code from the Received Submission Type codelist) |
* |
|
Received Submissions Count (BT-759) |
Number of tenders or requests to participate received. Tenders including variants or multiple tenders submitted (for one lot) by the same tenderer should be counted as one tender[29]. |
* |
|
Contract Identifier Reference (OPT-315) |
Identifier to refer to the appropriate settled contract. Shall follow the scheme "CON-XXXX" |
* |
|
CVD Contract Type (BT-735) |
The type of contract of the procurement procedure within the scope of Clean Vehicles Directive 2009/33/EC. |
* |
|
Vehicle Category (BT-723) |
The category of vehicle falling within the scope of Directive 2009/33/EC. |
* |
|
Vehicle Type (OPT-155) |
"labels" for types of vehicles (BT-715, BT-716 & BT-725) |
* |
|
Vehicle Numeric (OPT-156) |
"values" for types of vehicles (BT-715, BT-716 & BT-725) |
* |
|
Result Lot Identifier (BT-13713) |
Reference to the lot this result is about. Shall follow the scheme "LOT-XXXX" (LotResult only applies to lots). |
1 |
|
Context: (*) |
|||
An XML instance excerpt is provided below for illustration:
<efac:NoticeResult>
<!-- Interrupted Mark-up -->
<efac:LotResult>
<cbc:ID schemeName="result">RES-0002</cbc:ID>
<cbc:HigherTenderAmount currencyID="EUR">4560000</cbc:HigherTenderAmount>
<cbc:LowerTenderAmount currencyID="EUR">1230000</cbc:LowerTenderAmount>
<cbc:TenderResultCode listName="winner-selection-status">selec-w</cbc:TenderResultCode>
<cac:FinancingParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0003</cbc:ID>
</cac:PartyIdentification>
</cac:FinancingParty>
<cac:FinancingParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0004</cbc:ID>
</cac:PartyIdentification>
</cac:FinancingParty>
<cac:PayerParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
</cac:PayerParty>
<cac:PayerParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0002</cbc:ID>
</cac:PartyIdentification>
</cac:PayerParty>
<efac:AppealRequestsStatistics>
<efbc:StatisticsCode listName="irregularity-type">insuf-timl</efbc:StatisticsCode>
<efbc:StatisticsNumeric>2</efbc:StatisticsNumeric>
</efac:AppealRequestsStatistics>
<efac:AppealRequestsStatistics>
<efbc:StatisticsCode listName="irregularity-type">unj-lim-subc</efbc:StatisticsCode>
<efbc:StatisticsNumeric>2</efbc:StatisticsNumeric>
</efac:AppealRequestsStatistics>
<!-- Interrupted MarkUp -->
<efac:DecisionReason>
<efbc:DecisionReasonCode listName="non-award-justification">no-rece
</efbc:DecisionReasonCode>
</efac:DecisionReason>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0002</cbc:ID>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0003</cbc:ID>
</efac:LotTender>
<efac:FrameworkAgreementValues>
<cbc:MaximumValueAmount currencyID="EUR">12345</cbc:MaximumValueAmount>
<efbc:ReestimatedValueAmount currencyID="EUR">123</efbc:ReestimatedValueAmount>
</efac:FrameworkAgreementValues>
<efac:ReceivedSubmissionsStatistics>
<efbc:StatisticsCode listName="received-submission-type">tenders</efbc:StatisticsCode>
<efbc:StatisticsNumeric>12</efbc:StatisticsNumeric>
</efac:ReceivedSubmissionsStatistics>
<efac:ReceivedSubmissionsStatistics>
<efbc:StatisticsCode listName="received-submission-type">t-sme</efbc:StatisticsCode>
<efbc:StatisticsNumeric>6</efbc:StatisticsNumeric>
</efac:ReceivedSubmissionsStatistics>
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
</efac:SettledContract>
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0003</cbc:ID>
</efac:SettledContract>
<efac:StrategicProcurement>
<efac:StrategicProcurementInformation>
<efbc:ProcurementCategoryCode listName="cvd-contract-type">oth-serv-contract</efbc:ProcurementCategoryCode>
<efac:ProcurementDetails>
<efbc:AssetCategoryCode listName="vehicle-category">n2-n3</efbc:AssetCategoryCode>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles</efbc:StatisticsCode>
<efbc:StatisticsNumeric>8</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-zero-emission</efbc:StatisticsCode>
<efbc:StatisticsNumeric>0</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-clean</efbc:StatisticsCode>
<efbc:StatisticsNumeric>5</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
</efac:ProcurementDetails>
<efac:ProcurementDetails>
<efbc:AssetCategoryCode listName="vehicle-category">m1</efbc:AssetCategoryCode>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles</efbc:StatisticsCode>
<efbc:StatisticsNumeric>12</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-zero-emission</efbc:StatisticsCode>
<efbc:StatisticsNumeric>8</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-clean</efbc:StatisticsCode>
<efbc:StatisticsNumeric>4</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
</efac:ProcurementDetails>
</efac:StrategicProcurementInformation>
<efac:StrategicProcurementInformation>
<efbc:ProcurementCategoryCode listName="cvd-contract-type">veh-acq</efbc:ProcurementCategoryCode>
<efac:ProcurementDetails>
<efbc:AssetCategoryCode listName="vehicle-category">m2</efbc:AssetCategoryCode>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles</efbc:StatisticsCode>
<efbc:StatisticsNumeric>24</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-zero-emission</efbc:StatisticsCode>
<efbc:StatisticsNumeric>18</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-clean</efbc:StatisticsCode>
<efbc:StatisticsNumeric>6</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
</efac:ProcurementDetails>
<efac:ProcurementDetails>
<efbc:AssetCategoryCode listName="vehicle-category">n1</efbc:AssetCategoryCode>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles</efbc:StatisticsCode>
<efbc:StatisticsNumeric>6</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-zero-emission</efbc:StatisticsCode>
<efbc:StatisticsNumeric>6</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-clean</efbc:StatisticsCode>
<efbc:StatisticsNumeric>0</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
</efac:ProcurementDetails>
</efac:StrategicProcurementInformation>
</efac:StrategicProcurement>
<!-- Interrupted Markup -->
<efac:TenderLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
</efac:LotResult>
<!-- Interrupted Mark-up -->
</efac:NoticeResult>9.4. Lot Tender
LotTenders are the results of the decomposition of a received tender into fragments, each corresponding to a lot or group of lots.
Multiple information items may be found in a LotTender:
-
The LotTender ID,
-
The Tender Rank,
-
The Public transportation cumulated distance (for T02 form only),
-
Whether the tender is a variant or not,
-
The tender value,
-
Paid & penalties amounts (for "Contract Completion" only),
-
Concession revenues,
-
Contract terms,
-
Origin of goods or service,
-
Subcontracting terms,
-
Reference to the "Tendering Party" that submitted the tender,
-
Reference to the Lot or Group of lots the tender is about
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Lot Tender (*) |
|||
"Unpublish" fields |
(BT-171, BT-193, BT-720) Cf. LotTender Level |
||
Tender Technical Identifier (OPT-321) |
A unique technical identifier of a tender. Shall follow the TEN-XXXX scheme. |
1 |
|
Tender Rank (BT-171) |
The position of the tender (i.e. whether the tender ended up first, second, third, etc.) in a design contest, some framework agreements with multiple winners (e.g. cascades) or an innovation partnership. |
? |
|
Kilometers Public Transport (OPP-080) |
Aggregated number of public transportation kilometers over the whole duration of the contract (T02 form only) |
1 |
|
Tender Ranked (BT-1711) |
The tender has been ranked. This needs to be set to "true" to be able to specify the Rank. A true value does not however mandate the rank specification, unless required by the Regulation Annex. |
? |
|
Tender Variant (BT-193) |
The tender is a variant. |
? |
|
"Unpublish" fields |
(BT-160, BT-162, BT-163) Cf. LotTender Level |
||
Concession Revenue Buyer (BT-160) |
The estimated revenue coming from the buyer who granted the concession (e.g. prizes and payments). |
? |
|
Concession Revenue User (BT-162) |
The estimated revenue coming from the users of the concession (e.g. fees and fines). |
? |
|
Concession Value Description (BT-163) |
The description of the method used for calculating the estimated value of the concession and any other relevant information concerning the value of the concession. |
? |
|
Tender Value (BT-720) |
The value of the tender or another result; including options and renewals. In case of the modification notice, the value of the modification. |
? |
|
"Unpublish" fields |
(BT-191) Cf. LotTender Level |
||
Country Origin (BT-191) |
A country of origin of the product or the service. Values must come from the country codelist and the "listName" attribute be set to 'country'. |
? |
|
Tender Payment Value (BT-779) |
The value of all payments executed for the tender or another result, including options and renewals. (E5 only) |
? |
|
Tender Payment Value Additional Information (BT-780) |
Additional information about the value of all payments executed for the tender or another result, including options and renewals (e.g. justification for the actual value being different from the value given in the initial contract). (E5 only) |
? |
|
Tender Penalties (BT-782) |
The value of all penalties paid by the winner as a result of late or insufficient implementation of the tender or another result. (E5 only) |
? |
|
Penalties and Rewards Code (OPP-033) |
Code for "Information on rewards & penalties" (T02 only) |
? |
|
Penalties and Rewards Description (OPP-034) |
Description for "Information on rewards & penalties" (T02 only) |
? |
|
Contract conditions Code (OPP-030) |
Code for the contract conditions (T02 only) |
* |
|
Contract conditions Description (other than revenue allocation) (OPP-031) |
Description for the contract conditions other than "Allocation of revenue of sales from tickets" (T02 only) |
* |
|
Revenues Allocation (OPP-032) |
Percentage for the "Allocation of revenue of sales from tickets" (contract conditions — T02 only) |
? |
|
"Unpublish" fields |
subcontract terms (BT-553, BT-554, BT-555, BT-730, BT-731, BT-773) Cf. LotTender Level |
||
Subcontracting Value (BT-553) |
The estimated value of the part of the contract that the contractor will subcontract to third parties. |
? |
|
Subcontracting Description (BT-554) |
The description of the part of the contract that the contractor will subcontract to third parties. |
? |
|
Subcontracting Percentage (BT-555) |
The estimated percentage of the contract that the contractor will subcontract to third parties compared to the whole contract. |
? |
|
Subcontracting (BT-773) |
Whether at least a part of the contract will be subcontracted. Possible values are from the "applicability" codelist and restricted to "yes" and "no". |
? |
|
Subcontracting Percentage Known (BT-731) |
The buyer knows at least the estimated percentage of the contract that the contractor will subcontract to third parties compared to the whole contract. Only two values are possible "true" and "false". |
? |
|
Subcontracting Value Known (BT-730) |
The buyer knows at least the estimated value of the part of the contract that the contractor will subcontract to third parties. Only two values are possible "true" and "false". |
? |
|
Tendering Party ID Reference (OPT-310) |
Reference to the Tendering Party that submitted the LotTender. Shall follow the scheme "TPA-XXXX" |
1 |
|
Tender Lot Identifier (BT-13714) |
An identifier of a lot or a group of lots for which the tender was submitted. The information in the tender section refers to this lot. Shall follow the appropriate scheme "LOT-XXXX" or "GLO-XXXX" |
1 |
|
Tender Identifier (BT-3201) |
An identifier of a tender. The information in the tender section refers to this tender. |
1 |
|
Context: (*) |
|||
An XML instance excerpt is provided below for illustration:
<efac:NoticeResult>
<!-- Interrupted Mark-up -->
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
<cbc:RankCode>1</cbc:RankCode>
<efbc:TenderRankedIndicator>true</efbc:TenderRankedIndicator>
<efbc:TenderVariantIndicator>true</efbc:TenderVariantIndicator>
<cac:LegalMonetaryTotal>
<cbc:PayableAmount currencyID="EUR">500</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<efac:AggregatedAmounts>
<cbc:PaidAmount currencyID="EUR">480</cbc:PaidAmount>
<efbc:PaidAmountDescription languageID="ENG">An amount of ...</efbc:PaidAmountDescription>
<efbc:PenaltiesAmount currencyID="EUR">23</efbc:PenaltiesAmount>
</efac:AggregatedAmounts>
<efac:ConcessionRevenue>
<efbc:RevenueBuyerAmount currencyID="EUR">350</efbc:RevenueBuyerAmount>
<efbc:RevenueUserAmount currencyID="EUR">350</efbc:RevenueUserAmount>
<efbc:ValueDescription>Bla bla bla ...</efbc:ValueDescription>
</efac:ConcessionRevenue>
<efac:Origin>
<efbc:AreaCode listName="country">FRA</efbc:AreaCode>
</efac:Origin>
<efac:Origin>
<efbc:AreaCode listName="country">ITA</efbc:AreaCode>
</efac:Origin>
<efac:SubcontractingTerm>
<efbc:TermDescription languageID="ENG">Bla bli bla bli ...</efbc:TermDescription>
<efbc:TermPercent>20</efbc:TermPercent>
<efbc:TermCode listName="applicability">yes</efbc:TermCode>
<efbc:PercentageKnownIndicator>true</efbc:PercentageKnownIndicator>
<efbc:ValueKnownIndicator>false</efbc:ValueKnownIndicator>
</efac:SubcontractingTerm>
<efac:TenderingParty>
<cbc:ID schemeName="tendering-party">TPA-0002</cbc:ID>
</efac:TenderingParty>
<efac:TenderLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
<efac:TenderReference>
<cbc:ID>BID ABD/GHI-SN/2020-002</cbc:ID>
</efac:TenderReference>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0002</cbc:ID>
<!-- Interrupted MarkUp -->
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0003</cbc:ID>
<!-- Interrupted MarkUp -->
</efac:LotTender>
<!-- Interrupted MarkUp -->
</efac:NoticeResult>9.5. Settled Contract
SettledContract covers the following information:
-
The Contract identifier,
-
The award date,
-
The issue date,
-
The contract title,
-
The URL where the contract could be found,
-
Whether the contract is awarded within a Framework Agreement,
-
The reference to the notice (ID & version) relative to the Framework Agreement when applicable,
-
References to the signatories,
-
Contract Duration Justification (for T02 only),
-
References to the Lot Tenders that, combined together, lead to the contract,
-
EU funds names & IDs.
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Settled Contract (*) |
|||
Contract Technical Identifier (OPT-316) |
Unique contract technica ID. Shall follow the CON-XXXX scheme |
1 |
|
Winner Decision Date (BT-1451) |
The date of the official decision choosing the winning tender. |
? |
|
Contract Conclusion Date (BT-145) |
The date when the contract was concluded. Typically, this is the date when the last contractual party signed the contract. However, if no contract is signed, then the date of contract conclusion may correspond to other dates (e.g. the date when the buyer notified the winning tenderer). The date of contract conclusion is always later than the end of the standstill period and only once any evidence submitted by the winner has been verified. |
? |
|
Contract Title (BT-721) |
The name of the contract or, in case of voluntary-ex ante transparency notices and design contest result notices, of the decision. |
? |
|
Contract URL (BT-151) |
The uniform resource locator (e.g. the web address) of the contract. |
? |
|
Contract Framework Agreement (BT-768) |
The contract is awarded within a framework agreement. Only two values are possible "true" and "false". |
? |
|
Framework Notice Identifier (OPT-100) |
ID of the notice related to the Framework Contract under which the current contract takes place. In either format: notice identifier (UUID) concatenated with its version identifier (i.e. <UUID>-<vv>), or Notice Publication ID (XXXXXX-YYYY). |
? |
|
Signatory Identifier Reference (OPT-300) |
Organisation signing the contract |
+ |
|
Contract Tender ID (Reference, BT-3202) |
An identifier of the tender or another result that led to this contract. |
+ |
|
Contract Identifier (BT-150) |
An identifier of the contract or, in case of voluntary-ex ante transparency notices and design contest result notices, of the decision. The information in the contract section refers to this contract or decision. |
1 |
|
Assets related contract extension indicator (OPP-020) |
Extended contract duration due to essential assets necessary for the provision of the service (T02 only) |
1 |
|
Used asset (OPP-021) |
List of assets used for the provision of the public transportation services: (T02 only) |
* |
|
Significance (%) (OPP-022) |
Significance of the essential assets provided in relation to the overall assets needed for the provision of the public services (estimated % share of assets provided in overall assets used to provide services under contract): (T02 only) |
* |
|
Predominance (%) (OPP-023) |
Predominant use of assets (estimated % share of assets provided compared to assets used for activities other than the public services): (T02 only) |
* |
|
Contract EU Funds Financing Identifier (BT-5011) |
An identifier of the European Union Programme used to at least partially finance the contract. The most concrete information must be given (e.g. about concrete projects, not just operational programs.) |
? |
|
Contract EU Funds Programme (BT-722) |
The Programme of the European Union funds used to at least partially finance the contract. |
? |
|
Contract EU Funds Details (BT-6110) |
Further information about the Union programme or project used at least partially finance the procurement. |
? |
|
Context: (*) |
|||
An XML instance excerpt is provided below for illustration:
<efac:NoticeResult>
<!-- Interrupted MarkUp -->
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
<cbc:AwardDate>2021-02-19+01:00</cbc:AwardDate>
<cbc:IssueDate>2021-02-21+01:00</cbc:IssueDate>
<cbc:Title languageID="ENG">My contract title</cbc:Title>
<cbc:URI>http://mycontract.acme.com/1234/</cbc:URI>
<efbc:ContractFrameworkIndicator>true</efbc:ContractFrameworkIndicator>
<cac:NoticeDocumentReference>
<cbc:ID schemeName="ojs-notice-id">62783-2020</cbc:ID>
</cac:NoticeDocumentReference>
<cac:SignatoryParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
</cac:SignatoryParty>
<cac:SignatoryParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0003</cbc:ID>
</cac:PartyIdentification>
</cac:SignatoryParty>
<efac:ContractReference>
<cbc:ID>CRN ABC:EFG/2020-01</cbc:ID>
</efac:ContractReference>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0002</cbc:ID>
</efac:LotTender>
<efac:Funding>
<cbc:FundingProgramCode listName="eu-programme">ABC123</cbc:FundingProgramCode>
<cbc:FundingProgram>Program for the development ...</cbc:FundingProgram>
</efac:Funding>
</efac:SettledContract>
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0002</cbc:ID>
<!-- Interrupted MarkUp -->
</efac:SettledContract>
<!-- Interrupted MarkUp -->
</efac:NoticeResult>9.6. Tendering Party
The Tendering Party is about the tenderer who submitted alone, or group of tenderers who submitted together, a tender.
This party has various information associated to it as shown on Figure 1:
-
A technical identifier,
-
References to tenderers (at least one) who submitted a given tender,
-
When multiple tenderers tender together, an indicator to identify the group leader,
-
References to all subcontractors with a reference for each of them to the main contractor(s) they are providing services to.
Table 24 provides further details on the Tendering Party components.
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Tendering Party (*) |
|||
Tendering Party ID (OPT-210) |
Unique Tendering Party technical identifier. Shall follow the scheme TPA-XXXX Reference to the Tendering Party will be made from the Tender |
1 |
|
Tenderer ID Reference (OPT-300) |
Reference to the principal Organization(s) belonging to the Tendering Party. Shall be of the form ORG-XXXX and exist at the level of the Organizations. |
+ |
|
Tendering Party Leader (OPT-170) |
Indicator used to specify whether the tenderer has the lead in the case of a consortium or equivalent. Only required when at least two Tenderers are listed. For a given Tendering Party with multiple tenderers, there should be one and only one leader. |
* |
|
Subcontractor ID Reference (OPT-301) |
Reference to the Organization(s) acting as a subcontractor for one of the tenderers. Shall be of the form ORG-XXXX and exist at the level of the Organizations. |
* |
|
Main Contractor ID Reference (OPT-301) |
Reference to the Organization the subcontractor is providing services to. The reference ID shall be of the form ORG-XXXX, this ID shall exist at the level of the Organizations and this Organization shall be one of the tenderers listed as member of the Tendering Party. |
* |
efac:SubContractor/efac:MainContractor/cbc:ID |
Context: (*) |
|||
A sample mark-up is provided below for illustration purpose. It deals with the situation where two tenderers (ORG-0005 and ORG-0008) submitted a common tender. The tenderers are involving subcontractors (ORG-0012 and ORG-0015):
<efac:NoticeResult>
<!-- Interrupted Mark-up -->
<efac:TenderingParty>
<cbc:ID schemeName="tendering-party">TPA-0003</cbc:ID>
<efac:Tenderer>
<cbc:ID schemeName="organization">ORG-0005</cbc:ID>
<efbc:GroupLeadIndicator>true</efbc:GroupLeadIndicator>
</efac:Tenderer>
<efac:Tenderer>
<cbc:ID schemeName="organization">ORG-0008</cbc:ID>
<efbc:GroupLeadIndicator>false</efbc:GroupLeadIndicator>
</efac:Tenderer>
<efac:SubContractor>
<cbc:ID schemeName="organization">ORG-0012</cbc:ID>
<efac:MainContractor>
<cbc:ID schemeName="organization">ORG-0005</cbc:ID>
</efac:MainContractor>
<efac:MainContractor>
<cbc:ID schemeName="organization">ORG-0008</cbc:ID>
</efac:MainContractor>
</efac:SubContractor>
<efac:SubContractor>
<cbc:ID schemeName="organization">ORG-0015</cbc:ID>
<efac:MainContractor>
<cbc:ID schemeName="organization">ORG-0005</cbc:ID>
</efac:MainContractor>
</efac:SubContractor>
</efac:TenderingParty>
</efac:NoticeResult>10. Parties
"Parties" refers to the different stakeholders of the public procurement process. They play different roles (or subroles) during the procedure. Roles and subroles have been listed in the eForms implementation handbook.
Should always be used when applicable:
-
Buyer,
-
Winner,
-
Review body,
-
Buyer acquiring supplies/services intended for other buyers
-
Buyer awarding public contracts or concluding FAs for works, supplies or services intended for others,
-
eSenders.
Information provision about other roles shall follow national specific requirements and implementations.
More specific rules on organizations to identify, based on their role/subrole and the type of notice, are given in Table 34 below.
The Organizations information is centralized and only some function related properties have been kept in their respective context.
The structure for Organizations information is designed to support the different classes that may be encountered. In the following sub sections, information is provided on:
-
the different organizations,
-
the way they are referred to, and
-
the function-related properties that could not be centralized.
10.1. Organizations Information design
We may distinguish two classes of parties involved in a public procurement procedure:
-
Organizations as such, and
-
Ultimate Business Owners.
In the XML, they are all under the same element "efac:Organizations" in the extensions. Their content is somewhat different as an Organization is most of the time a juridical person while the Ultimate Beneficial Owner is always a natural one.
10.2. Organization
The required information for an Organization is dependent on its type and may vary with its function (role within a context).
As the contact details for a given function may differ from the Organization ones, the concept of TouchPoint has been introduced. The link between a TouchPoint and an Organization is ensured by the parent element "efac:Organization". An Organization may have zero or more TouchPoints associated to it, depending on the performed functions and the existence or not of various communication channels.
The "efac:Company" element contains the information of the legal entity while the "efac:TouchPoint" element encompasses the information associated to one or more functions and needed to interact with it (when it differs from the ones of the Organization itself).
We should differentiate 3 different types of company:
-
The buyers,
-
The non-buying non-tendering organizations (e.g. Economic operators, non-buying administrations or other organizations with which tenderers may have to interact),
-
The Tenderers and review requesters (e.g. Winners, Subcontractors …)
The table below specifies the requirements regarding Company/TouchPoint information, which will be discussed in more details in the following sections.
| Extra Properties | Company / Touchpoint | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Buyer |
Ec. Op. |
Buyer/ Eco. Op. |
Address |
Contact |
||||||||||||||||||
Buyer Group Lead |
Acquiring CPB |
Awarding CPB |
On Regulated Market |
Natural Person |
Beneficial Owner |
Website URI |
Endpoint ID |
Company Size |
Technical ID |
Official ID |
Name |
Party Name |
Street |
City |
Postcode |
Country Subdivision |
Country Code |
Contact Name |
eMail Address |
Phone Number |
Fax Number |
|
_Buyer _ |
EM |
EM |
EM |
— |
— |
— |
EM |
O |
— |
M |
M |
M |
O |
EM |
M |
CM |
CM |
M |
CM |
M |
M |
O |
Touchpoint (Buyer) |
— |
— |
— |
— |
— |
— |
EM |
O |
— |
M |
— |
M |
O |
EM |
M |
CM |
CM |
M |
CM |
CM |
CM |
O |
Service Provider/non-buyer |
— |
— |
— |
— |
EM |
— |
EM |
CM |
— |
M |
M |
M |
O |
EM |
M |
CM |
CM |
M |
CM |
M |
M |
O |
Touchpoint (Service Provider) |
— |
— |
— |
— |
— |
— |
EM |
O |
— |
M |
— |
M |
CM |
EM |
M |
CM |
CM |
M |
CM |
CM |
CM |
O |
Winner / Tenderer |
— |
— |
— |
CM |
EM |
CM |
EM |
CM |
CM |
M |
M |
M |
O |
EM |
M |
CM |
CM |
M |
CM |
M |
M |
O |
UBO |
— |
— |
— |
— |
— |
— |
— |
— |
— |
M |
M |
M |
— |
EM |
M |
CM |
CM |
M |
O |
O |
O |
O |
To point from any place within the instance to the appropriate set of information (Company or TouchPoint related), a technical identifier is defined following the rules summarized in Table 26 and marked-up using "cac:PartyIdentification/cbc:ID".
Company type |
schemeName |
ID scheme |
Buyer |
organization |
ORG-XXXX |
Touchpoint (Buyer) |
touchpoint |
TPO-XXXX |
Non-buyer, Non-Tenderer |
organization |
ORG-XXXX |
Touchpoint (NB, NT) |
touchpoint |
TPO-XXXX |
Tenderer |
organization |
ORG-XXXX |
UBO |
ubo |
UBO-XXXX |
10.2.1. Buyer
For a buyer, there may be a need to identify whether it is:
-
a group leader,
-
an awarding CPB,
-
an acquiring CPB.
For Group Leader, the element "efbc:GroupLeadIndicator" is not allowed if there is only one Buyer. If there is more than one Buyer, then "efbc:GroupLeadIndicator" is mandatory for all Buyers, and one Buyer shall have the value "true".
For Awarding CPB, the element "efbc:AwardingCPBIndicator" must either be omitted for all Buyers, or included for all Buyers, at least one of which should have the value "true".
For Acquiring CPB, the element "efbc:AcquiringCPBIndicator" must either be omitted for all Buyers, or included for all Buyers, at least one of which should have the value "true".
In addition to the usual Organization information, a unique technical identifier shall be associated to the legal Organization. The value of this identifier shall follow the rules reported in Table 26.
For a function assumed by a given Buyer, when the associated contact details differ from the ones of the Buyer and from the other ones already defined as TouchPoint for that organization, a new TouchPoint shall be defined. This TouchPoint also has a technical identifier associated to it which should follow the scheme as reported in Table 26.
An example of mark-up for a buyer is provided below.
<efac:Organization>
<efbc:GroupLeadIndicator>false</efbc:GroupLeadIndicator>
<efbc:AcquiringCPBIndicator>false</efbc:AcquiringCPBIndicator>
<efbc:AwardingCPBIndicator>false</efbc:AwardingCPBIndicator>
<efac:Company>
<cbc:WebsiteURI>http://xyz.europa.eu/</cbc:WebsiteURI>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name languageID="ENG">Administration XYZ</cbc:Name>
</cac:PartyName>
<cac:PartyName>
<cbc:Name languageID="DEU">XYZ Verwaltung</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>2, rue de l'Europe</cbc:StreetName>
<cbc:CityName>SmallCity</cbc:CityName>
<cbc:PostalZone>2345</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">XY374</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">XYZ</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyLegalEntity>
<cbc:CompanyID>XYZ</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Press Department</cbc:Name>
<cbc:Telephone>+123 45678</cbc:Telephone>
<cbc:ElectronicMail>press@xyz.europa.eu</cbc:ElectronicMail>
</cac:Contact>
</efac:Company>
<efac:TouchPoint>
<cbc:WebsiteURI>http://abc.europa.eu/</cbc:WebsiteURI>
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name languageID="ENG">Department ABC</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>2, rue de l'Europe</cbc:StreetName>
<cbc:CityName>SmallCity</cbc:CityName>
<cbc:PostalZone>2345</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">XY374</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">XYZ</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:Contact>
<cbc:Name>Head of ABC Department</cbc:Name>
<cbc:Telephone>+123 45678</cbc:Telephone>
<cbc:ElectronicMail>abc@xyz.europa.eu</cbc:ElectronicMail>
</cac:Contact>
</efac:TouchPoint>
</efac:Organization>10.2.2. Non-Tenderer, Non-Buyer
This section refers to organizations active during the Public Procurement Procedure neither being a buyer nor a tenderer.
An indicator may be used to specify whether the legal person is a natural person or not (BT-633).
The Winner Listed (BT-746) "efbc:ListedOnRegulatedMarketIndicator" element is not allowed for Non-Tenderer, Non-Buyer organizations.
The "efac:Company" element groups all the elements related to the legal organization and the "efac:TouchPoint" element groups the contact details for a given function assumed by the organization when these differ from the ones of the legal organization.
A Mark-Up example is provided hereafter for an economic operator providing Procurement Services to the buyer in the previous section[30].
<efac:Organization>
<efbc:NaturalPersonIndicator>false</efbc:NaturalPersonIndicator>
<efac:Company>
<cbc:WebsiteURI>http://www.psp.com</cbc:WebsiteURI>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0003</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Procurement Services Sàrl</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>55 rue de la liberté</cbc:StreetName>
<cbc:CityName>Laville</cbc:CityName>
<cbc:PostalZone>87267</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">AB123</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">ABC</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyLegalEntity>
<cbc:CompanyID>AB12345</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Telephone>(+234) 98765</cbc:Telephone>
<cbc:ElectronicMail>info@psp.com</cbc:ElectronicMail>
</cac:Contact>
</efac:Company>
<efac:TouchPoint>
<cbc:WebsiteURI>http://abc.europa.eu/</cbc:WebsiteURI>
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0002</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name languageID="ENG">Department XYZ</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>2, rue de l'Europe</cbc:StreetName>
<cbc:CityName>SmallCity</cbc:CityName>
<cbc:PostalZone>2345</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">XY374</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">XYZ</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:Contact>
<cbc:Name>Public Procurement Department</cbc:Name>
<cbc:Telephone>+123 45678</cbc:Telephone>
<cbc:ElectronicMail>info@xyz.europa.eu</cbc:ElectronicMail>
</cac:Contact>
</efac:TouchPoint>
</efac:Organization>10.2.3. Winner/tenderer
This section refers to economic operators that submitted a tender.
An indicator may be used to specify whether the legal person is a natural person or not (BT-633). The value "true" specifies that the organization is a Natural Person and the value "false" specifies that the organization is a juridical person.
The element "efbc:NaturalPersonIndicator" must either be omitted for all Tenderers and subcontractors, or included for all Tenderers and subcontractors. It is not allowed with the value "true" for an organization that has the BT-746 Winner Listed "efbc:ListedOnRegulatedMarketIndicator" element with value "true".
Another indicator may be used to specify whether this organization is listed on a regulated market. When not listed, then links to the Ultimate Business Owners shall be specified.
The element "efbc:ListedOnRegulatedMarketIndicator" must either be omitted for all Tenderers and subcontractors, or included for all Tenderers and subcontractors. It is not allowed with the value "true" for an organization that has the BT-633 Organisation Natural Person "efbc:NaturalPersonIndicator" element with value "true".
<efac:Organization>
<!-- Winner Listed (BT-746) -->
<efbc:ListedOnRegulatedMarketIndicator>false</efbc:ListedOnRegulatedMarketIndicator>
<!-- When not listed, and not a natural-person, then may be linked to at least one Beneficial Owner -->
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0001</cbc:ID>
</efac:UltimateBeneficialOwner>
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0002</cbc:ID>
</efac:UltimateBeneficialOwner>
<efac:Company>
<cbc:WebsiteURI>http://www.kulk-comp.com</cbc:WebsiteURI>
<efbc:CompanySizeCode listName="economic-operator-size">sme</efbc:CompanySizeCode>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0003</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Hulk Sàrl</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>55 rue de la liberté</cbc:StreetName>
<cbc:CityName>Laville</cbc:CityName>
<cbc:PostalZone>87267</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">AB123</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">ABC</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyLegalEntity>
<cbc:CompanyID>AB12345</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Telephone>(+234) 98765</cbc:Telephone>
<cbc:ElectronicMail>contact@hulk-comp.com</cbc:ElectronicMail>
</cac:Contact>
</efac:Company>
</efac:Organization>10.2.4. Ultimate Beneficial Owner
As reporting information about a UBO is left at National Authority discretion, only the Technical Identifer and the nationality are mandatory. When the National authority enforces the report of further information or when a Buyer wishes to do so, then the information reported should satisfy the requirements as expressed in Table 25.
The Winner Owner Nationality (BT-706) is expressed using the "cbc:NationalityID" element. Values must come from the country codelist.
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0001</cbc:ID>
<cbc:FirstName>Mickey</cbc:FirstName>
<cbc:FamilyName>Mouse</cbc:FamilyName>
<cac:Contact>
<cbc:Telephone>+123 4567890</cbc:Telephone>
<cbc:Telefax>+123 4567891</cbc:Telefax>
<cbc:ElectronicMail>mickey.mouse@cheese-universe.com</cbc:ElectronicMail>
</cac:Contact>
<cac:ResidenceAddress>
<cbc:StreetName>2 CheeseStreet</cbc:StreetName>
<cbc:AdditionalStreetName>Nelson Building</cbc:AdditionalStreetName>
<cbc:CityName>MouseTown</cbc:CityName>
<cbc:PostalZone>C6HA782</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">GBK62</cbc:CountrySubentityCode>
<cac:AddressLine>
<cbc:Line>2nd floor</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode listName="country">GBR</cbc:IdentificationCode>
</cac:Country>
</cac:ResidenceAddress>
<!-- Winner Owner Nationality (BT-706) -->
<efac:Nationality>
<cbc:NationalityID>FIN</cbc:NationalityID>
</efac:Nationality>
<efac:Nationality>
<cbc:NationalityID>DEU</cbc:NationalityID>
</efac:Nationality>
</efac:UltimateBeneficialOwner>
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0002</cbc:ID>
<!-- Interrupted MarkUp -->
<efac:Nationality>
<cbc:NationalityID>FRA</cbc:NationalityID>
</efac:Nationality>
</efac:UltimateBeneficialOwner>10.3. General structure of an organization related information
All Organizations are grouped under the same element "efac:Organizations". They are organized as shown on Figure 15.
There are several pieces of information required for an organization. The mapping with schema components is reported in Table 27.
The business term Organization Notice Section Identifier (BT-13720) does not have any equivalent in the XML since the elements used to mark the organizations are referenced from the appropriate sections.
Each legal organization (i.e. in "efac:Company") is in a dedicated "efac:Organization" element and its associated alternate contact "efac:TouchPoint" (associated to one or more specific function) is sibling of "efac:Company", therefore information of the legal organization not part of the touchpoint information may be retrieved from the legal organization to which the touchpoint is associated.
Business Term |
Organization / Company / Touchpoint |
Equivalent element |
Comment |
Organization Name (BT-500) |
C |
|
Organization name, possible expression in different linguistic versions[31] |
T |
|
Trade name or organizational name (e.g. team, group …), possible expression in different linguistic versions. |
|
Organization Technical Identifier (Company OPT-200, Touchpoint OPT-201) |
C |
|
Unique technical identifier ORG-XXXX |
T |
|
Unique technical identifier TPO-YYYY |
|
Organization Identifier (BT-501) |
C |
|
Organization Legal ID. For a given organization, one or more identifiers issued by a legal authority may be used, in such a case the parent PartyLegalEntity shall be repeated. |
T |
N/A |
||
Organization Part Name (BT-16) |
C |
|
Name of the department or subdivision. |
T |
|
Name of the department, division, subgroup |
|
Organization Street (BT-510) |
C |
|
StreetName for first address line; Additional StreetName for the 2nd and a single AddressLine for 3rd and subsequent lines |
T |
|
To be used when regular mails may be used for information exchange or submission |
|
Organization City (BT-513) |
C |
|
Host town of the legal organization |
T |
|
Town where the mails have to be sent |
|
Organization Post Code (BT-512) |
C |
|
Post code of the legal organization |
T |
|
Post code for the address where mails have to be sent |
|
Organization Country Subdivision (BT-507) |
C |
|
Use of NUTS 3 codes For areas larger than a country, use the Region and associated code list. Legal organization location |
T |
|
NUTS 3 for TouchPoint |
|
Organization Country Code (BT-514) |
C |
|
Country host of legal organization Values must come from the country codelist |
T |
|
Country where mails shall be sent Values must come from the country codelist |
|
Organization Contact Point (BT-502) |
C |
|
Use preferably function in the department/subdivision rather than individual names Legal organization contact |
T |
|
TouchPoint contact name (use function or department …) |
|
Organization Contact Email Address (BT-506) |
C |
|
Legal organization contact email address (prevent personal address) |
T |
|
TouchPoint email address for information exchange |
|
Organization Contact Telephone Number (BT-503) |
C |
|
Legal Organization phone number |
T |
|
TouchPoint phone number |
|
Organization Contact Fax (BT-739) |
C |
|
Legal Organization fax number |
T |
|
TouchPoint fax number |
|
Organization Internet Address (BT-505) |
C |
|
Legal Organization website |
T |
|
TouchPoint webpage/site |
|
Organization eDelivery Gateway (BT-509) |
C |
|
Edelivery gateway legal organization |
T |
|
Edelivery gateway touchpoint |
|
Winner Size (BT-165) |
O |
|
Only for tenderers, winners and subcontractors; Code from the economic-operator-size codelist |
Organization Natural Person (BT-633) |
O |
|
Only for economic operators (tenderer, winner, service provider …) |
Winner Listed (BT-746) |
O |
|
Only for tenderer and winner. Only two values are possible "true" and "false". |
Beneficial Owner Reference (OPT-302) |
O |
|
Only for tenderer and winner when not natural person and not listed on a regulated market |
Organization Role (BT-08) |
C |
N/A |
Roles and subroles are conveyed by their dedicated element in a specific context from where a reference to the Company or TouchPoint exist, linking role/subrole to the appropriate contact information of the organization |
T |
N/A |
||
Organization Subrole (BT-770) |
C |
N/A |
|
T |
N/A |
Not all information is required for every role/subrole and the presence requirement per role is summarized in the following table; as a consequence the Touchpoint or Company the role/subrole points to shall have the appropriate information.
In the following tables, for contexts and procedures where the roles/subroles followed by the (#) are allowed, the corresponding roles/subroles have to be included and their associated organisations identified.
Required information based on stakeholders role / sub-role |
Company |
Address |
Contact |
|||||||||||||
Name |
Identifier |
Part Name |
Street |
City |
Post Code |
Country Subdivision |
Country Code |
Point |
Email Address |
Phone Number |
Fax |
Internet Address |
eDelivery Gateway |
Natural Person |
||
ROLES |
||||||||||||||||
Buyer (#) |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
M |
— |
|
Winner (#) |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
0 |
CM |
|
Subcontractor |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
0 |
CM |
|
Mediation organization |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
0 |
CM |
|
Review organization (#) |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
0 |
CM |
|
Tax legislation information provider |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
M |
O |
O |
|
Environment legislation information provider |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
M |
O |
O |
|
Employment legislation information provider |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
M |
O |
O |
|
Beneficial owner |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
O |
O |
O |
O |
O |
O |
|
Acquiring CPB (#) |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
M |
M |
EM |
EM |
O |
O |
|
Awarding CPB (#) |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
M |
M |
*EM * |
EM |
O |
O |
|
Procurement service provider |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
O |
CM |
CM |
CM |
|
Tenderer |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
M |
M |
O |
EM |
CM |
0 |
|
Review Requester |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
M |
M |
O |
EM |
CM |
0 |
|
Not-Tenderer Review Requester |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
O |
O |
O |
O |
O |
O |
|
Non-contractant review requester |
M |
M |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
eSender (#) |
M |
M |
O |
EM |
M |
CM |
CM |
M |
O |
O |
O |
O |
O |
O |
O |
|
SUBROLES |
||||||||||||||||
Group leader |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Additional Information Providing Organization |
M |
EM |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
M |
O |
O |
|
Documents provider organization |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Review Information Providing Organization |
M |
O |
O |
EM |
M |
EM |
EM |
M |
O |
M |
M |
EM |
O |
O |
O |
|
Organization receiving requests to participate |
M |
O |
O |
EM |
M |
EM |
EM |
M |
CM |
CM |
O |
O |
O |
CM |
O |
|
Organization processing requests to participate |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Tender Recipient Organization |
M |
O |
O |
EM |
M |
EM |
EM |
M |
CM |
CM |
O |
O |
O |
CM |
O |
|
Tender Evaluation Organization |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Contract Signatory |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Financing Organization |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
Paying Organization |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
|
(#) roles/subroles followed by (#) must be included and their associated organisations identified everywhere the Procedure and Context allow it. |
||||||||||||||||
The table shall be read per row. For a given row (i.e. a given role or subrole), in each column, the requirement about the existence of the information item in the column header, is expressed using the codes detailed in the legend below:
M: |
mandatory |
EM: |
existing mandatory |
O: |
optional |
CM: |
conditionally mandatory |
— : |
not applicable |
10.4. Overview of roles, sub-roles and functions
Organizations assume specific functions (role/subrole) in different contexts.
There are multiple roles and subroles defined, and subroles are only accessible to organizations which already have a given role assigned; the applicable restrictions are summarized in Table 29.
Subrole |
|||||||||||
Group Leader |
Additional Information Providing Organization |
Documents provider organization |
Review Information Providing Organization |
Requests to participate Recipient Organization |
Tender Recipient Organization |
Tender Evaluation Organization |
signatory |
Financing Organization |
Paying Organization |
||
authority Role |
Buyer (#) |
X |
X |
X |
X |
X |
X |
X |
X |
X |
X |
Winner (#) |
X |
||||||||||
Subcontractor |
|||||||||||
Mediation organization |
- |
||||||||||
Review organization (#) |
X |
||||||||||
Tax legislation information provider |
|||||||||||
Environment legislation information provider |
|||||||||||
Employment legislation information provider |
|||||||||||
Beneficial owner |
|||||||||||
Acquiring CPB (#) |
X |
X |
X |
X |
X |
X |
X |
X |
X |
X |
|
Awarding CPB (#) |
X |
X |
X |
X |
X |
X |
X |
X |
X |
X |
|
Procurement service provider |
X |
X |
X |
X |
X |
X |
X |
X |
X |
X |
|
Tenderer |
X |
||||||||||
Review Requester |
|||||||||||
eSender (#) |
|||||||||||
(#) roles/subroles followed by (#) must be included and their associated organisations identified everywhere the Procedure and Context allow it. |
|||||||||||
In eForms some roles and subroles have been identified and described [R1]. The following sections help mapping these with the appropriate schema components.
For an appropriate understanding on how the different roles subroles should be marked, there is a need for some initial clarifications.
10.4.1. Roles
Table 30 groups roles, descriptions and the associated XSD component.
Role |
Description |
XSD element |
Buyer (#) |
Organization that manages the budget allocated for the procedure and pays for the items being procured[32]. |
|
Winner (#) |
The tendering Party to whom the contract is awarded[33]. NB: A winner may be a single organization or a grouping of organizations |
Only provided as an example (*): |
Tendering Party[34] |
Party, or Parties, who has / have submitted his / their tender NB: The Tendering Party may be composed of a single organization or a grouping of organizations |
Only provided as an example (**): |
Tenderer |
Any economic operator at the forefront of work in a Tendering Party |
|
Review Requester |
Organization requesting for review |
|
Subcontractor |
Organization that performs parts of the work of a main contractor. |
|
Mediation organization |
Third party helping with Alternative Dispute Resolution |
|
Review organization (#) |
Organization dealing with review requests. |
|
Tax legislation information provider |
Organization providing information concerning the general regulatory framework for taxes applicable in the place where the contract is to be performed. |
And |
Environment legislation information provider |
Organization providing information concerning the general regulatory framework for environmental protection applicable in the place where the contract is to be performed. |
And |
Employment legislation information provider |
Organization providing information concerning the general regulatory framework for employment protection and working conditions applicable in the place where the contract is to be performed. |
And |
Review Requester |
Organization that requested a review request. |
|
Beneficial owner |
Beneficial Owner of the winning organization |
|
(*) For a given lot result, we look for the contracts listed; from these contracts we identify the tenders associated and from there we get the tendering party(-ies). Example provided for Lot 1. |
||
(**) For a given lot result, we look for tenders listed; from these tenders we identify the tendering Party. Example provided for Lot 1. |
||
(#) roles/subroles followed by (#) must be included and their associated organisations identified everywhere the Procedure and Context allow it. |
||
Table 31 lists the roles that are distinguished using codes or indicators
| Role | Description | XSD element (with code) |
|---|---|---|
Acquiring CPB (#) |
Central purchasing body acquiring supplies and/or services intended for other buyers |
|
Awarding CPB (#) |
Central purchasing body awarding public contracts or concluding framework agreements for works supplies or services intended for other buyers |
|
Procurement service provider |
Economic operator providing procurement services to contracting authorities |
set to "serv-prov" |
TED eSender (#) |
Economic operator providing data transfer services to contracting authorities |
set to "ted-esen" |
(#) roles/subroles followed by (#) must be included and their associated organisations identified everywhere the Procedure and Context allow it. |
||
10.4.2. Sub-roles
Table 32 groups subroles, description and XSD components used to mark these subroles.
Sub-role |
Description |
XSD element |
Group leader (Buyer) |
To be used when:
|
For joint procurement: |
Group leader (Tenderer) |
To be used when:
|
For winning consortium |
Additional Information Providing Organization |
Organization providing additional information about the procurement procedure |
|
Documents provider organization |
Organization providing offline access to the procurement documents |
|
Review Information Providing Organization |
Organization providing more information on the time limits for review procedures |
|
Requests to participate Recipient Organization |
Organization receiving requests to participate (*) |
|
Requests to participate processing Organization |
Organization processing requests to participate (*) |
|
Tender Recipient Organization |
Organization receiving tenders (*) |
|
Tender Evaluation Organization |
Organization processing tenders (*) |
|
Contract Signatory |
Organization signing the contract |
|
Financing Organization |
Organization whose budget is used to pay for the contract |
|
Paying Organization |
Organization executing the payment |
|
(*) The procurement context allows identification of whether this applies to "requests to participate" or to "tender". |
||
10.5. Mark-up of roles/subroles
When, for a given notice, a role/subrole exists and has to be reported, then this should be performed at the appropriate level within the XML.
Form Type |
Planning |
Comp. |
DAP / Result |
Result (subseq proc) |
Modification |
Completion |
|||||||||||||||||||||
Notice Type |
PIN profile |
PIN Only |
PIN RTL |
PIN CFC / CN / Subco / QS / Design |
VEAT |
CAN general / social |
Design |
CAN |
Contract Modification |
Contract Completion |
|||||||||||||||||
Location in Notice |
Root |
Root |
Part |
Root |
Lot |
Root |
Lot |
Root |
Result |
Lot |
Root |
Result |
Lot |
Root |
Result |
Lot |
Root |
Result |
Lot |
Root |
Result |
Lot |
Root |
Result |
Lot |
Review info |
|
Acquiring CPB |
P |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
+ |
[+] |
[+] |
|||||||||||||||
Awarding CPB |
P |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
+ |
[+] |
[+] |
|||||||||||||||
Buyer |
R |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
|||||||||||||||
Procurement service provider |
R |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
+ |
|||||||||||||||
eSender |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||
Mediation organisation |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Review organisation |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Tax legislation information provider |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Environment legislation information provider |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Employment legislation information provider |
R |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Additional Information Providing Organisation |
S |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Documents provider organisation |
S |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Review Information Providing Organisation |
S |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
||||||||||||||||||
Organisation receiving requests to participate |
S |
1 |
1 |
1 |
|||||||||||||||||||||||
Organisation processing requests to participate |
S |
1 |
1 |
1 |
|||||||||||||||||||||||
Tender Recipient Organisation |
S |
1 |
1 |
1 |
|||||||||||||||||||||||
Tender Evaluation Organisation |
S |
1 |
1 |
1 |
|||||||||||||||||||||||
Financing Organisation |
S |
{+} |
{+} |
{+} |
{+} |
{+} |
|||||||||||||||||||||
Paying Organisation |
S |
{+} |
{+} |
{+} |
{+} |
{+} |
|||||||||||||||||||||
Winner |
P |
{+} |
{+} |
{+} |
{+} |
{+} |
{+} |
||||||||||||||||||||
Beneficial owner |
R |
[+] |
[+] |
[+] |
[+] |
[+] |
[+] |
||||||||||||||||||||
Contract Signatory |
S |
/+/ |
/+/ |
/+/ |
/+/ |
/+/ |
/+/ |
||||||||||||||||||||
Subcontractor |
R |
<+> |
<+> |
<+> |
<+> |
<+> |
<+> |
||||||||||||||||||||
Tenderer |
R |
{+} |
{+} |
{+} |
{+} |
{+} |
{+} |
||||||||||||||||||||
Group leader (Tenderer) |
P |
<1> |
<1> |
<1> |
<1> |
<1> |
<1> |
||||||||||||||||||||
Review requestor |
S |
+ |
|||||||||||||||||||||||||
P: property |
1: exactly one; |
(1): exactly one at ??? level |
(+): at least one at ??? level |
||||||||||||||||||||||||
10.5.1. Tendering Party versus Tenderer
Organizations may tender separately or jointly; when they tender jointly, this may take different forms:
-
Creation of a unique legal organization (e.g. joint venture), in this case this new organization will be described (i.e. all its information provided) at the Organizations level and referred to in the Tendering Party section; or
-
There is no legal entity created and the different organizations are participating directly (e.g. consortium)
In this last case, when a reference to a tenderer or to a winner should be made, it wouldn’t be appropriate to refer to the organisations individually but rather to the whole set of organizations acting together, especially if an organization would be involved in different "partnerships".
A tender is submitted either by an Organization of by a set of organizations; it is more convenient to refer to this group without having to refer to each organization individually. Also for the winner, it is clearer to identify the group than identifying each member of the group as winner, therefore an extra "function" needed to be defined (i.e. the Tendering Party) composed of Tenderers. This also provides the opportunity to identify at the same time the subcontractors and link them to the main contractor they are working for. Let’s first define the two concepts of Tendering Party and Tenderer.
*"Tendering Party"*means a party or parties as a group who has / have participated in the tender process and submitted his / their tender in response to an invitation to participate in the tender or a party / parties who is / are prospective tenders qualified to participate in a tender based on notice issued by the Company inviting tender.
"Tenderer" means Bidder/ the Individual or Firm submitting Bids / Quotation / Tender.
https://www.lawinsider.com/dictionary/tenderer
Further details on Tendering Party (components, use and sample) may be found in Tendering Party.
10.5.2. The winner
The results are provided per Lot.
For a given Lot, winners are members of a Tendering Party which submitted a Tender that:
-
Was submitted for that Lot, and
-
Has been selected as part of the winning Tenders (Tenders associated to a Contract, i.e. Tender for which the value of its OPT-321-Tender field equals the value of a BT-3202-Contract field of an existing Contract. .).
Therefore to identify winners for a given Lot, there is a need to successively:
-
Identify the Tenders submitted for that Lot or a Group of Lots containing that Lot,
-
Extract, from these Tenders, the ones referenced in any Contracts,
-
Identify the associated Tendering Parties, and
-
Identify each Tenderer belonging to at least one of those Tendering Parties.
10.5.3. Central Purchasing Bodies
CPBs are buyers and to reduce duplication of information it is enough to distinguish with indicators whether a buyer is a CPB or not. Since there are two different CPB possible, two different indicators have been defined.
10.5.4. Group leader
A single subrole has been defined to cover two different concepts:
-
Buyer group leader (in case of joint procurement), and
-
Tenderer group leader (in the case of consortium or equivalent association of tenderers)
For a buyer, the indication that the buyer is a group leader is attached to the organization itself.
A tenderer may be involved in multiple Tendering Parties (i.e. contribute collaboratively to different tenders) while he may have different positions in each of them, therefore the specification whether a given Tenderer is a group leader or not is indicated at the level of the Tendering Party.
10.5.5. Subcontractor
The role of subcontractor, and the main contractor it is providing services to, are dependent from the Tendering Party the subcontractor is involved in, therefore this information will be found inside the cac:TenderingParty element.
10.5.6. Roles & notices
Not all identified roles may exist in a notice (e.g. a winner may only occur in a Contract Award Notice). The following table identifies the requirement regarding the presence of the information for a given role/subrole according to the type of notice.
The following convention has been used to report this information:
M: |
mandatory |
EM: |
existing mandatory |
O: |
optional |
CM: |
conditionally mandatory |
— : |
not applicable |
PIN profile |
PIN only |
PIN time limit |
PIN CFC general |
PIN CFC social |
QS |
CN general |
CN social |
CN subco |
CN design |
CAN VEAT |
CAN general |
CAN social |
CAN design |
Contract modifi-cation |
||||||||||||||||||||||||||
D24 |
D25 |
D81 |
D24 |
D25 |
D81 |
D24 |
D25 |
D81 |
D24 |
D25 |
D24 |
D25 |
D23 |
D25 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D81 |
D24 |
D25 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D81 |
D23 |
D24 |
D25 |
D23 |
D24 |
D25 |
D24 |
D25 |
D23 |
|
Notice Subtype |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
ROLES |
||||||||||||||||||||||||||||||||||||||||
Buyer (#) |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
Winner (#) |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
Subcontractor |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
Mediation organization |
— |
— |
— |
EM |
EM |
O |
EM |
O |
O |
EM |
O |
EM |
O |
EM |
O |
EM |
EM |
O |
O |
O |
O |
O |
EM |
O |
EM |
O |
O |
EM |
EM |
EM |
O |
EM |
O |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
Review organization (#) |
— |
— |
— |
M |
M |
O |
M |
O |
O |
M |
O |
M |
O |
M |
O |
M |
M |
O |
M |
O |
O |
O |
M |
O |
M |
O |
O |
M |
M |
M |
O |
M |
O |
M |
M |
M |
M |
M |
M |
M |
Tax legislation information provider |
— |
— |
— |
O |
O |
M |
O |
O |
M |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Environment legislation information provider |
— |
— |
— |
O |
O |
M |
O |
O |
M |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Employment legislation information provider |
— |
— |
— |
O |
O |
M |
O |
O |
M |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Beneficial owner |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
— |
— |
— |
Acquiring CPB (#) |
— |
— |
— |
EM |
EM |
O |
EM |
EM |
O |
EM |
O |
O |
EM |
— |
O |
EM |
EM |
O |
— |
O |
EM |
O |
EM |
EM |
EM |
EM |
O |
— |
EM |
EM |
O |
— |
O |
EM |
— |
O |
EM |
O |
O |
— |
Awarding CPB (#) |
— |
— |
— |
EM |
EM |
O |
EM |
EM |
O |
EM |
O |
O |
EM |
— |
O |
EM |
EM |
O |
— |
O |
EM |
O |
EM |
EM |
EM |
EM |
O |
— |
EM |
EM |
O |
— |
O |
EM |
— |
O |
EM |
O |
O |
— |
Procurement service provider |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Tenderer |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
Not-Tenderer Review Requester |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Non-contractant review requester |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
eSender (#) |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
M |
SUBROLES |
||||||||||||||||||||||||||||||||||||||||
Group leader (Buyer) |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
EM |
Group leader (Tenderer) |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
CM |
Additional Information Providing Organization |
— |
— |
— |
M |
M |
O |
M |
O |
O |
M |
M |
O |
O |
M |
M |
O |
M |
O |
M |
O |
M |
O |
O |
M |
O |
M |
O |
M |
O |
M |
O |
M |
O |
M |
M |
O |
O |
O |
M |
M |
Documents provider organization |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Review Information Providing Organization |
— |
— |
— |
CM |
CM |
O |
CM |
O |
O |
CM |
O |
O |
O |
CM |
O |
CM |
CM |
O |
CM |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Organization receiving requests to participate |
— |
— |
— |
EM |
EM |
O |
EM |
O |
O |
EM |
O |
O |
O |
CM |
O |
CM |
O |
O |
CM |
O |
O |
O |
O |
O |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
Organization processing requests to participate |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
0 |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
Tender Recipient Organization |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
CM |
O |
CM |
O |
O |
CM |
O |
O |
O |
EM |
O |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
Tender Evaluation Organization |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
Contract Signatory |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Financing Organization |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
Paying Organization |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
— |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
O |
(#) roles/subroles followed by (#) must be included and their associated organisations identified everywhere the Procedure and Context allow it. |
||||||||||||||||||||||||||||||||||||||||
10.6. Linking roles/subroles to organizations
For the eForms technical implementation, it has been decided to keep the normalized approach for organisations to prevent unnecessary repetitions and their associated inconsistency risks. The denormalized approach of the UBL Standard has been kept and reduced to its minimum (i.e. use of references to the organisation or touchpoint involved) as it is associated to a context which helps differentiate various roles/subroles. The references to the organisation or its touchpoint is performed using OPT-300-xxx or OPT-301-xxxx fields. As a rule of thumb, OPT-300-xxxx is associated to an organisation (i.e. identifier of the form ORG-XXXX) while OPT-301-xxxx is associated to an organisation or a touchoint (i.e. identifier of the form ORG-XXXX and TPO-XXXX respectively). Please note that exceptions may occur with business rules clarifications while the field has already been defined.
10.6.1. Buyer
10.6.1.1. Buyer information
The Organization information associated to a Buyer may be found in the extensions at the root of the notice in the "efac:Organization" element (cf. § 10.2.1). Further Buyer related information (cf. Table 35) is present in the "cac:ContractingParty" element.
| eForms BT | XSD component | Comment |
|---|---|---|
Buyer Profile URL (BT-508) |
|
|
Buyer Legal Type (BT-11) |
|
Code from buyer-legal-type |
Buyer Contracting Entity (BT-740) |
|
Code from buyer-contracting-type technical codelist |
Activity Authority (BT-10) |
|
Code from authority-activity, subset of main-activity |
Activity Entity (BT-610) |
|
Code from entity-activity, subset of main-activity |
10.6.1.2. Buyer and service providers
Different stakeholders associated to the buyer share the same "cac:ContractingParty" ancestor; this is the case for:
-
the procurement service provider,
-
the eSender.
Any Contracting Party must contain one and only one reference to an organisation acting as Buyer (OPT-300-Procedure-Buyer). When multiple buyers must explicitly be identified, then multiple "cac:ContractingParty" elements must be used.
A mark-up sample with:
-
a procurement service provider, and
-
an eSender,
is provided here:
<cac:ContractingParty>
<cbc:BuyerProfileURI>https://admin-abc.com/public-procurements/</cbc:BuyerProfileURI>
<cac:ContractingPartyType>
<cbc:PartyTypeCode listName="buyer-legal-type">body-pl</cbc:PartyTypeCode>
</cac:ContractingPartyType>
<cac:ContractingPartyType>
<cbc:PartyTypeCode listName="buyer-contracting-type">cont-aut</cbc:PartyTypeCode>
</cac:ContractingPartyType>
<cac:ContractingActivity>
<cbc:ActivityTypeCode listName="authority-activity">hc-am</cbc:ActivityTypeCode>
</cac:ContractingActivity>
<cac:Party>
<cac:PartyIdentification>
<!-- OPT-300-Procedure-Buyer: Reference (Technical ID) to the legal organization acting as a Buyer. -->
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
<cac:ServiceProviderParty>
<!-- The service provider is a Procurement Service Provider -->
<cbc:ServiceTypeCode listName="organisation-role">serv-prov</cbc:ServiceTypeCode>
<cac:Party>
<cac:PartyIdentification>
<!-- OPT-300-Procedure-SProvider: Reference (Technical ID) to the legal organization acting as a PSP. -->
<cbc:ID schemeName="organization">ORG-0005</cbc:ID>
</cac:PartyIdentification>
</cac:Party>
</cac:ServiceProviderParty>
<cac:ServiceProviderParty>
<!-- The service provider is an eSender -->
<cbc:ServiceTypeCode listName="organisation-role">ted-esen</cbc:ServiceTypeCode>
<cac:Party>
<cac:PartyIdentification>
<!-- Reference (Tech. ID) to the legal organization acting as an eSender. -->
<cbc:ID schemeName="organization">ORG-0006</cbc:ID>
</cac:PartyIdentification>
</cac:Party>
</cac:ServiceProviderParty>
</cac:Party>
</cac:ContractingParty>Other Buyer associated roles (i.e. CPBs, Group leader) are to be found as indicators in the "efac:Organization" element of the Buyer.
10.6.2. Winning organization, Tenderer, Group Leader and Tendering Party
Let’s illustrate how a winning organization will be marked.
Let’s start by specifying the economic operator information, this is done in the "Organizations" section.
<efac:Organization>
<efbc:ListedOnRegulatedMarketIndicator>false</efbc:ListedOnRegulatedMarketIndicator>
<efbc:NaturalPersonIndicator>false</efbc:NaturalPersonIndicator>
<efac:UltimateBeneficialOwner>
<!-- OPT-302-Organization: Reference (Technical ID) to the Utimate Beneficial Owner. -->
<cbc:ID schemeName="ubo">UBO-0001</cbc:ID>
</efac:UltimateBeneficialOwner>
<efac:UltimateBeneficialOwner>
<!-- OPT-302-Organization: Reference (Technical ID) to the Utimate Beneficial Owner. -->
<cbc:ID schemeName="ubo">UBO-0002</cbc:ID>
</efac:UltimateBeneficialOwner>
<efac:Company>
<cbc:WebsiteURI>http://www.xpertpro.eu</cbc:WebsiteURI>
<cbc:EndpointID>https://drive.xpertpro.eu/</cbc:EndpointID>
<efbc:CompanySizeCode listName="economic-operator-size">small</efbc:CompanySizeCode>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0002</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>XpertPro Sàrl</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>3, place de la République</cbc:StreetName>
<cbc:CityName>Le marais</cbc:CityName>
<cbc:PostalZone>41250</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">FRB05</cbc:CountrySubentityCode>
<cac:Country>
<cbc:IdentificationCode listName="country">FRA</cbc:IdentificationCode>
</cac:Country>
</cac:PostalAddress>
<cac:PartyLegalEntity>
<cbc:CompanyID>123 456 789</cbc:CompanyID>
</cac:PartyLegalEntity>
<cac:Contact>
<cbc:Name>Sales department</cbc:Name>
<cbc:Telephone>(+33) 2 34 56 78 90</cbc:Telephone>
<cbc:Telefax>(+33) 2 34 56 78 91</cbc:Telefax>
<cbc:ElectronicMail>marketing@xpertpro.eu</cbc:ElectronicMail>
</cac:Contact>
</efac:Organization>
</efac:Organization>The Ultimate Beneficial Owners of the organization are:
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0001</cbc:ID>
<cbc:FirstName>Mickey</cbc:FirstName>
<cbc:FamilyName>Mouse</cbc:FamilyName>
<cac:Contact>
<cbc:Telephone>+123 4567890</cbc:Telephone>
<cbc:Telefax>+123 4567891</cbc:Telefax>
<cbc:ElectronicMail>mickey.mouse@cheese-universe.com</cbc:ElectronicMail>
</cac:Contact>
<cac:ResidenceAddress>
<cbc:StreetName>2 CheeseStreet</cbc:StreetName>
<cbc:AdditionalStreetName>Nelson Building</cbc:AdditionalStreetName>
<cbc:CityName>MouseTown</cbc:CityName>
<cbc:PostalZone>C6HA782</cbc:PostalZone>
<cbc:CountrySubentityCode listName="nuts">GBK62</cbc:CountrySubentityCode>
<cac:AddressLine>
<cbc:Line>2nd floor</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode listName="country">GBR</cbc:IdentificationCode>
</cac:Country>
</cac:ResidenceAddress>
<!-- Winner Owner Nationality (BT-706) -->
<efac:Nationality>
<cbc:NationalityID>FIN</cbc:NationalityID>
</efac:Nationality>
<efac:Nationality>
<cbc:NationalityID>DEU</cbc:NationalityID>
</efac:Nationality>
</efac:UltimateBeneficialOwner>
<efac:UltimateBeneficialOwner>
<cbc:ID schemeName="ubo">UBO-0002</cbc:ID>
<!-- Interrupted MarkUp -->
<efac:Nationality>
<cbc:NationalityID>FRA</cbc:NationalityID>
</efac:Nationality>
</efac:UltimateBeneficialOwner>Let’s consider that the organization tendered alone and has an associated subcontractor (ORG-0005):
<efac:TenderingParty>
<cbc:ID schemeName="tendering-party">TPA-0001</cbc:ID>
<efac:Tenderer>
<!-- OPT-300-Tenderer -->
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</efac:Tenderer>
<efac:SubContractor>
<!-- OPT-301-Tenderer-SubCont -->
<cbc:ID schemeName="organization">ORG-0005</cbc:ID>
<efac:MainContractor>
<!-- OPT-301-Tenderer-MainCont -->
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</efac:MainContractor>
</efac:SubContractor>
</efac:TenderingParty>Any organization having a forefront role in a Tendering Party is a Tenderer and the previously provided sample may be used as a paradigm for its mark-up.
When a Tendering Party involves more than one tenderer:
-
the indicator "efbc:GroupLeadIndicator" shall be used to specify for any given tenderer whether it is a Group Leader or not;
-
there shall exist one and only one Group Leader (indicator set to "true").
The associated Tender is reported hereafter:
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
<cbc:RankCode>1</cbc:RankCode>
<!-- Interrupted Mark-Up -->
<efac:TenderingParty>
<!-- OPT-310-Tender: Reference to the tendering Party -->
<cbc:ID schemeName="tendering-party">TPA-0001</cbc:ID>
</efac:TenderingParty>
<efac:TenderLot>
<cbc:ID schemeName="LotsGroup">GLO-0005</cbc:ID>
</efac:TenderLot>
</efac:LotTender>As a winning tender, it will lead to the signature of a contract:
<efac:SettledContract>
<!-- Interrupted Mark-Up -->
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
<!-- Interrupted Mark-Up -->
<efac:LotTender>
<!-- Reference to the Tender -->
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
</efac:LotTender>
<!-- Interrupted Mark-Up -->
</efac:SettledContract>The existence of contracts for the considered lot is specified by using in the LotResult references to the contracts:
<efac:LotResult>
<!-- Interrupted Mark-Up -->
<efac:SettledContract>
<!-- Reference to a settled contract covering this lot -->
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
</efac:SettledContract>
<!-- Interrupted Mark-Up -->
<efac:LotTender>
<!-- Reference to the Tender -->
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
</efac:LotTender>
<!-- Interrupted Mark-Up -->
<efac:TenderLot>
<!-- Reference to the Lot -->
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
</efac:LotResult>For a LotResult:
-
there may exist multiple Tenders, not all Tenders are winning Tenders and multiple Tenders could be submitted by the same Tendering Party,
-
There may also be multiple winning Tenders (e.g. Framework Agreement),
Therefore, when identifying a specific winner of a Lot, it is important to identify the Tender and check that it is a winning one.
10.6.3. Contract Signatory
The Contract Signatory(-ies) may be found in the "efac:SettledContract" element and shall refer to the legal person that signs the contract from the Buyer side.
<efac:SettledContract>
<!-- Interrupted Mark-Up -->
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
<!-- Interrupted Mark-Up -->
<cac:SignatoryParty>
<!-- OPT-300-Contract-Signatory: Reference to the Organization signing the contract -->
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:SignatoryParty>
<!-- Interrupted Mark-Up -->
</efac:SettledContract>"cac:SignatoryParty" is repeatable to report as many signatories as needed.
10.6.4. Financing & Paying Organizations
The Financing and Paying Parties may be found in the "efac:LotResult" element. References shall be made to the legal person assuming the role:
<efac:LotResult>
<!-- Interrupted Mark-Up -->
<cac:FinancingParty>
<!-- OPT-301-LotResult-Financing: Reference to the organization financing the project -->
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
</cac:FinancingParty>
<cac:PayerParty>
<!-- OPT-301-LotResult-Paying: Reference to the organization performing payments -->
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
</cac:PayerParty>
<!-- Interrupted Mark-Up -->
<efac:TenderLot>
<!-- Reference to the Lot -->
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
</efac:LotResult>"cac:FinancingParty" and "cac:PayerParty" are repeatable to allow for reporting of as many parties as needed.
10.6.5. Legislation Information Provider
There are 3 types of such organizations, one for each of the followings:
-
Employment,
-
Environment,
-
Tax.
These roles are to be found at the Lot level:
<cac:ProcurementProjectLot>
<cbc:ID schemeName="Lot">LOT-0002</cbc:ID>
<cac:TenderingTerms>
<!-- Interrupted Mark-Up -->
<cac:FiscalLegislationDocumentReference>
<!-- ID mandated by schema, but unused in eForms -->
<cbc:ID>Fiscal1</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<!-- URL to the legislation -->
<cbc:URI>https://fiscal-legislation.gov.stat</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<!-- OPT-301-Lot-FiscalLegis: Reference to the legal person -->
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0007</cbc:ID>
</cac:PartyIdentification>
</cac:IssuerParty>
</cac:FiscalLegislationDocumentReference>
<cac:EnvironmentalLegislationDocumentReference>
<!-- ID mandated by schema, but unused in eForms -->
<cbc:ID>Env1</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<!-- URL to the legislation -->
<cbc:URI>http://environmental-legislation.gov.stat</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<!-- OPT-301-Lot-EnvironLegis: Reference to the legal person -->
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0007</cbc:ID>
</cac:PartyIdentification>
</cac:IssuerParty>
</cac:EnvironmentalLegislationDocumentReference>
<cac:EmploymentLegislationDocumentReference>
<!-- ID mandated by schema, but unused in eForms -->
<cbc:ID>Empl1</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<!-- URL to the legislation -->
<cbc:URI>http://employment-legislation.gov.stat</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<!-- OPT-301-Lot-EmployLegis: Reference to the legal person -->
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0007</cbc:ID>
</cac:PartyIdentification>
</cac:IssuerParty>
</cac:EmploymentLegislationDocumentReference>
<!-- Interrupted Mark-Up -->
</cac:TenderingTerms>
<!-- Interrupted Mark-Up -->
</cac:ProcurementProjectLot>10.6.6. Other roles/subroles
These may be found at the lot level and refer to the appropriate Organization or TouchPoint. A sample is provided hereafter for illustration purpose:
<cac:ProcurementProjectLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
<cac:TenderingTerms>
<!-- Interrupted Mark-Up -->
<cac:AdditionalInformationParty>
<!-- OPT-301-Lot-AddInfo: "Organization providing additional information on procurement procedure" -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
</cac:AdditionalInformationParty>
<cac:DocumentProviderParty>
<!-- OPT-301-Lot-DocProvider: "Organization providing offline access to procurement documents" -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
</cac:DocumentProviderParty>
<cac:TenderRecipientParty>
<!-- OPT-301-Lot-TenderReceipt: "Organization Receiving Requests to participate" or "Organization Receiving Tenders" -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
</cac:TenderRecipientParty>
<cac:TenderEvaluationParty>
<!-- OPT-301-Lot-TenderEval: "Organization evaluating Requests to participate" or "Organization evaluating Tenders" -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
</cac:TenderEvaluationParty>
<!-- Interrupted Mark-Up -->
<cac:AppealTerms>
<!-- Interrupted Mark-Up -->
<cac:AppealInformationParty>
<!-- OPT-301-Lot-ReviewInfo: Reference to the Organization or TouchPoint for further info on review -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
</cac:PartyIdentification>
</cac:AppealInformationParty>
<cac:AppealReceiverParty>
<!-- OPT-301-Lot-ReviewOrg: Reference to the Organization or TouchPoint for reviews -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0003</cbc:ID>
</cac:PartyIdentification>
</cac:AppealReceiverParty>
<cac:MediationParty>
<!-- OPT-301-Lot-Mediator: Reference to the Organization or TouchPoint for mediation -->
<cac:PartyIdentification>
<cbc:ID schemeName="touchpoint">TPO-0005</cbc:ID>
</cac:PartyIdentification>
</cac:MediationParty>
</cac:AppealTerms>
</cac:TenderingTerms>
<cac:TenderingProcess>
<!-- Interrupted Mark-up -->
</cac:TenderingProcess>
<cac:ProcurementProject>
<!-- Interrupted Mark-up -->
</cac:ProcurementProject>
</cac:ProcurementProjectLot>References
-
[R1] eForms Policy Implementation Handbook, European Commission, Directorate-General for Internal Market, Industry, Entrepreneurship and SMEs, 2019, 108 p., available at https://op.europa.eu/en/publication-detail/-/publication/73a78487-cc8b-11ea-adf7-01aa75ed71a1, accessed April 6th, 2021
11. Change Notice
As indicated previously, the purpose of change notices is multifold:
-
Correct a value reported in the previous Change notice, or if this is the first Change notice, the original notice,
-
Inform about changes to information not inside the notice (e.g. changed procurement documents),
While changes may apply to notices of any form type, the Change notice Form Type and Notice Type values must be identical to the ones of the original notice. A change notice may only concern a single notice and contains all the information from that initial notice with applied changes in addition to the information on those changes.
When a change is applied to a previous change notice, the consolidated text must integrate all changes from previous Change notices, and only the latest changes are described in the changes section. This section will allow the reporting of:
-
The identifier of the changed notice,
-
The changes that may individually apply to one or more sections, concern procurement documents and other information,
-
The main reason that led to the Change notice creation.
A change notice will have its own Notice Identifier (BT-701); this will differ from the one of the changed notice.
When applying changes, it is essential to ensure that the variations do not need the start of a new procedure instead.
The changes are indicated using the dedicated extension elements at the root of the notice.
11.1. Changed Notice
To identify the changed notice, the following business term is used:
-
Change Notice Version Identifier (BT-758)
11.2. Change
A change may contain all the following business terms:
-
Change Previous Section Identifier (BT-13716)
-
Procurement Documents Change Date (BT-719)
-
Procurement Documents Change Indicator (BT-718)
-
Change Description (BT-141)
There must exist at least one "efac:Change" element in the Change Notice, except for the case of: * a cancel notice (i.e. Change Reason set to "cancel") where no "efac:Change" node is expected, and * an intent to cancel a lot/procedure (i.e. Change Reason set to "cancel-intent") where "efac:Change" node may be used to identify the lots.
A change may cover one or more sections of a notice and the element used to reference sections (i.e. "efbc:ChangedSectionIdentifier", BT-13716) is repeatable.
The procurement documents-related elements indicate whether these documents have changed and when. For the indicator, either of the two values "true" and "false" is used; when the value is set to "true", the date the procurement documents have been changed must be specified, else the specification of this date is not allowed.
The decription is there for further information in a textual form.
11.3. Change Reason
Reason for a change shall be expressed using a code from the change-corrig-justification codelist and additional information in the description:
-
Change Reason Code (BT-140)
-
Change Reason Description (BT-762)
The use of the code is mandatory while the provision of the description is optional.
11.4. Changes elements
In Table 36 are referenced the different business terms relative to changes and their corresponding elements.
| eForms BT | Description | Cardin. | XSD element |
|---|---|---|---|
Change Notice Version Identifier (BT-758) |
Reference to the notice being changed (a combination of the Notice Identifier (BT-701) and the Notice Version (BT-757) for eForms notices only; or Publication ID of the notice being changed for eForms or TEDXML notices.) |
1 |
|
Procurement Documents Change Date (BT-719) |
Date of procurement documents changes |
? |
|
Procurement Documents Change Indicator (BT-718) |
Indication that procurement documents have changed |
? |
|
Change Description (BT-141) |
Description of the changes |
* |
|
Change Previous Section Identifier (BT-13716) |
Identification of the changed sections |
* |
|
Change Reason Code (BT-140) |
Code to express the background reasons for the change |
1 |
|
Change Reason Description (BT-762) |
The background reasons for the change expressed as text |
* |
|
11.5. Sample changes
A sample change mark-up is proposed below. It covers a text update as well as information about changes to procurement documents:
<ContractNotice>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:Changes>
<efbc:ChangedNoticeIdentifier schemeName="notice-id-ref">755db7f6-6aa1-453b-9087-1df5f7725112-02</efbc:ChangedNoticeIdentifier>
<efac:Change>
<efbc:ChangeDescription languageID="ENG">The changes have been applied to ...</efbc:ChangeDescription>
<efac:ChangedSection>
<efbc:ChangedSectionIdentifier>LOT-0001</efbc:ChangedSectionIdentifier>
</efac:ChangedSection>
</efac:Change>
<efac:Change>
<efbc:ProcurementDocumentsChangeDate>2019-10-24+01:00</efbc:ProcurementDocumentsChangeDate>
<efbc:ProcurementDocumentsChangeIndicator>true</efbc:ProcurementDocumentsChangeIndicator>
<efbc:ChangeDescription languageID="ENG">Updated procurement documents</efbc:ChangeDescription>
<efac:ChangedSection>
<efbc:ChangedSectionIdentifier>LOT-0002</efbc:ChangedSectionIdentifier>
</efac:ChangedSection>
</efac:Change>
<efac:ChangeReason>
<cbc:ReasonCode listName="change-corrig-justification">update-add </cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">Clerical corrections of ...</efbc:ReasonDescription>
</efac:ChangeReason>
</efac:Changes>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- interrupted mark-up -->
</ContractNotice>12. Contract Modification Notice
A contract modification may occur during contract execution and applies to a Result or Contract Modification notice only.
With a single Contract Modification notice, it is only possible to modify contracts belonging to the same notice, and only if none of them have been modified in the meantime. When some contracts in a notice have already been modified, then any further contract modification for these contracts has to be applied on the latest Contract Modification notice. For contracts that have not been modified, the new contract modification may be performed based on the result notice but shall not include contracts already modified.
If a notice only contains N SettledContract elements, then there may not be more than N references to contracts in the Contract Modification notice. A Contract Modification may only refer to a single contract; there may be multiple Contract Modification elements, they each have to refer to a different contract.
| Field ID | Field Name | Description | Cardin. | XSD element |
|---|---|---|---|---|
BT-1501(n)-Contract |
Modification Previous Notice Identifier |
Reference to the previous notice (Result or Contract Modification) |
1 |
|
BT-1501(c)-Contract |
Modified Contract Reference |
Reference to the modified contract (i.e. technical ID CON-xxxx) |
1 |
|
BT-202-Contract |
Modification Description |
Description of the modification |
* |
|
BT-1501(p)-Contract |
Modified Notice Part Reference |
Identification of the modified parts of the notice |
* |
|
BT-200-Contract |
Modification Reason Code |
Main reason for modifying the contract |
1 |
|
BT-201-Contract |
Modification Reason Description |
Reason, expressed as text, that justifies the Contract Modification |
1 |
|
The possible values Modified Notice Part Reference may have are:
-
BUYER to refer to the buyers,
-
RESULT to refer to the Notice Result,
-
The technical identifier of an existing LotResult (RES-xxxx),
-
The technical identifier of an existing LotTender (TEN-xxxx),
-
The technical identifier of an existing Tendering Party (TPA-xxxx),
-
The technical identifier of an existing Touchpoint (TPO-xxxx),
-
The technical identifier of an existing Organisation (ORG-xxxx),
-
The technical identifier of an existing Ultimate Beneficial Owner (UBO-xxxx)
The possible Modification reason code values are referenced in the modification-justification codelist.
The Contract Modification elements occur in the extensions at the root of the notice.
For each "efac:ContractModification" element, as part of the changed sections, there shall be, a unique reference to a contract within the Contract Modification notice using the contract technical identifier.
<efac:ContractModification>
<!-- Modification Previous Notice Identifier BT-1501(n)-Contract -->
<efbc:ChangedNoticeIdentifier schemeName="notice-id-ref">755db7f6-6aa1-453b-9087-1df5f7725112-02</efbc:ChangedNoticeIdentifier>
<!-- Modified Contract Reference BT-1501(c)-Contract -->
<efbc:ModifiedContractIdentifier schemeName="contract">CON-0001</efbc: ModifiedContractIdentifier>
<efac:Change>
<!-- Modification Description BT-202-Contract -->
<efbc:ChangeDescription languageID="ENG">The scope of the procurement ...</efbc:ReasonDescription>
<efbc:ChangeDescription languageID="FRE">Le périmètre de ...</efbc:ReasonDescription>
<efac:ChangedSection>
<!-- Modified Notice Part Reference BT-1501(p)-Contract -->
<efbc:ChangedSectionIdentifier>TEN-0001</efbc:ChangedSectionIdentifier>
</efac:ChangedSection>
<efac:ChangedSection>
<!-- Modified Notice Part Reference BT-1501(p)-Contract -->
<efbc:ChangedSectionIdentifier>TEN-0003</efbc:ChangedSectionIdentifier>
</efac:ChangedSection>
</efac:Change>
<efac:ChangeReason>
<!-- Modification Reason Code BT-200-Contract -->
<cbc:ReasonCode listName="modification-justification">mod-cir</cbc:ReasonCode>
<!-- Modification Reason Description BT-201-Contract -->
<efbc:ReasonDescription languageID="ENG">Following an Act of God ...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRE">Suite à un événement ...</efbc:ReasonDescription>
</efac:ChangeReason>
</cac:ContractModification>13. Withheld publication of information
Some information required by eForms may remain non-public ("unpublished") for a defined period[35]. This feature may be used for Result, Contract Modification and Contract Completion notices only.
For some fields, the "unpublish" feature is available independently from the directive, while for some others, it is exclusively accessible for the sectoral directive (i.e. directive 25).
The reason for keeping the information private shall be specified using a code from the codelist non-publication-justification and a description. The field whose information publication shall be withheld is identified using a code as specified in the following subsections.
To activate the mechanism, four business terms have to be used:
-
Unpublished Identifier (BT-195)
-
Unpublished Justification Code (BT-197)
-
Unpublished Justification Description (BT-196)
-
Unpublished Access Date (BT-198)
The information is encoded using dedicated elements:
<efac:FieldsPrivacy>
<efbc:FieldIdentifierCode listName="non-publication-identifier">not-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">oth-int</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">Information delayed publication because of ...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">Publication de l'information ajournée parce que ...</efbc:ReasonDescription>
<efbc:PublicationDate>2025-03-31+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>This should be indicated using the extension mechanism, under the direct parent of the element containing the information whose publication is delayed.
"efac:FieldsPrivacy" is sibling to the field to be "unpublished"; it appears in an extension when the targeted field is not itself in an extension or shares directly the same parent as the field to "unpublish".
13.1. All directives
13.1.1. Notice Result level
This covers the withheld publication of:
-
Notice Value (BT-161),
-
Notice Framework Maximum Value (BT-118),
-
Notice Framework Approximate Value (BT-1118),
-
Group Framework Maximum Value Lot Identifier (BT-556),
-
Group Framework Maximum Value (BT-156),
-
Group Framework Re-estimated Value (BT-1561).
The codes to be used to identify the field and the location where the unpublish components are to be found are given in Table 38.
| Code | What is to be covered | XPATH to "unpublish" components |
|---|---|---|
not-val |
Notice Value (BT-161) |
|
not-app-val |
Notice Framework Approximate Value (BT-1118) |
|
not-max-val |
Notice Framework Maximum Value (BT-118) |
|
gro-max-ide |
Group Framework Maximum Value Lot Identifier (BT-556) |
|
gro-max-val |
Group Framework Maximum Value (BT-156) |
|
gro-ree-val |
Group Framework Re-estimated Value (BT-1561) |
|
A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<ContractAwardNotice>
<!-- Interrupted mark-up -->
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:NoticeResult>
<efac:FieldsPrivacy>
<!-- # UNPUB-01 : The Notice Value (BT-161) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">not-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">Because ...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">Parce que ...</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-02 : The Notice Framework Maximum Value (BT-118) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">not-max-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">...</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-01 : Notice Value (BT-161) publication will be delayed -->
<cbc:TotalAmount currencyID="EUR">123456.00</cbc:TotalAmount>
<!-- # UNPUB-02 : The Notice Framework Maximum Value (BT-118) publication will be delayed -->
<efbc:OverallMaximumFrameworkContractsAmount currencyID="EUR">6000</efbc:OverallMaximumFrameworkContractsAmount>
<efac:GroupFramework>
<efac:FieldsPrivacy>
<!-- # UNPUB-03 : The Group Framework Maximum Value (BT-156) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">gro-max-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">The following ...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">L'information suivante ...</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-04 : The Group Framework Maximum Value Lot Identifier (BT-556) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">gro-max-ide</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">...</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">...</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-03 : Group Framework Maximum Value (BT-156) publication will be delayed -->
<efbc:GroupFrameworkMaximumValueAmount currencyID="EUR">1200000</efbc:GroupFrameworkMaximumValueAmount>
<!-- # UNPUB-04 : Group Framework Maximum Value Lot Identifier (BT-556) publication will be delayed -->
<efac:TenderLot>
<cbc:ID schemeName="LotsGroup">GLO-0001</cbc:ID>
</efac:TenderLot>
</efac:GroupFramework>
<!-- Interrupted mark-up -->
</efac:NoticeResult>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
<!-- Interrupted mark-up -->
</ContractAwardNotice>13.1.2. LotResult level
This covers the withheld publication of:
-
Winner Chosen (BT-142),
-
Not Awarded Reason (BT-144),
-
Framework Re-estimated Value (BT-660),
-
Framework Maximum Value (BT-709),
-
Received Submissions Count (BT-759),
-
Received Submissions Type (BT-760),
-
Tender Value Lowest (BT-710),
-
Tender Value Highest (BT-711),
-
Buyer Review Complainants (BT-712).
The codes to be used to identify the field and the location where the unpublish components are to be found are given in Table 39.
| Code | What is to be covered | XPATH to "unpublish" components |
|---|---|---|
win-cho |
Winner Chosen (BT-142) |
|
no-awa-rea |
Not Awarded Reason (BT-144) |
|
ree-val |
Framework Re-estimated Value (BT-660) |
|
max-val |
Framework Maximum Value (BT-709) |
|
rec-sub-cou |
Received Submissions Count (BT-759) |
|
rec-sub-typ |
Received Submissions Type (BT-760) |
|
ten-val-low |
Tender Value Lowest (BT-710) |
|
ten-val-hig |
Tender Value Highest (BT-711) |
|
rev-req |
Buyer Review Complainants (BT-712) |
|
buy-rev-cou |
Buyer Review Requests Count (BT-635) |
|
buy-rev-typ |
Buyer Review Requests Irregularity Type (BT-636) |
A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<efac:LotResult>
<efac:FieldsPrivacy>
<!-- # UNPUB-10 : Tender Value Highest (BT-711) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">ten-val-hig
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-11 : Tender Value Lowest (BT-710) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">ten-val-low</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-12 : Winner Chosen (BT-142) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">win-cho</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-10 : Tender Value Highest (BT-711) publication will be delayed -->
<cbc:HigherTenderAmount currencyID="EUR">456</cbc:HigherTenderAmount>
<!-- # UNPUB-11 : Tender Value Lowest (BT-710) publication will be delayed -->
<cbc:LowerTenderAmount currencyID="EUR">123</cbc:LowerTenderAmount>
<!-- # UNPUB-12 : Winner Chosen (BT-142) publication will be delayed -->
<cbc:TenderResultCode listName="winner-selection-status">selec-w</cbc:TenderResultCode>
<cac:FinancingParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0003</cbc:ID>
</cac:PartyIdentification>
</cac:FinancingParty>
<cac:FinancingParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0004</cbc:ID>
</cac:PartyIdentification>
</cac:FinancingParty>
<cac:PayerParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
</cac:PartyIdentification>
</cac:PayerParty>
<cac:PayerParty>
<cac:PartyIdentification>
<cbc:ID schemeName="organization">ORG-0002</cbc:ID>
</cac:PartyIdentification>
</cac:PayerParty>
<efac:AppealRequestsStatistics>
<efac:FieldsPrivacy>
<!-- # UNPUB-13 : Buyer Review Complainants (BT-712) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">rev-req</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efbc:StatisticsCode listName="..">..</efbc:StatisticsCode>
<!-- # UNPUB-13 : Buyer Review Complainants (BT-712) publication will be delayed -->
<efbc:StatisticsNumeric>2</efbc:StatisticsNumeric>
</efac:AppealRequestsStatistics>
<efac:AppealRequestsStatistics>
<!-- Interrupted Mark-up -->
</efac:AppealRequestsStatistics>
<efac:DecisionReason>
<efac:FieldsPrivacy>
<!-- # UNPUB-14 : Not Awarded Reason (BT-144) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">no-awa-rea</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-14 : Not Awarded Reason (BT-144) publication will be delayed -->
<efbc:DecisionReasonCode listName="non-award-justification">no-rece</efbc:DecisionReasonCode>
</efac:DecisionReason>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0002</cbc:ID>
</efac:LotTender>
<efac:LotTender>
<cbc:ID schemeName="tender">TEN-0003</cbc:ID>
</efac:LotTender>
<efac:FrameworkAgreementValues>
<efac:FieldsPrivacy>
<!-- # UNPUB-15A : Framework Maximum Value (BT-709) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">max-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-15B : Framework Re-estimated Value (BT-660) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">ree-val</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-15A : Framework Maximum Value (BT-709) publication will be delayed -->
<cbc:MaximumValueAmount currencyID="EUR">12345</cbc:MaximumValueAmount>
<!-- # UNPUB-15B : Framework Re-estimated Value (BT-660) publication will be delayed -->
<efbc:ReestimatedValueAmount currencyID="EUR">123</efbc:ReestimatedValueAmount>
</efac:FrameworkAgreementValues>
<efac:ReceivedSubmissionsStatistics>
<efac:FieldsPrivacy>
<!-- # UNPUB-16 : Received Submissions Type (BT-760) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">rec-sub-typ</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-17 : Received Submissions Count (BT-759) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">rec-sub-cou</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"></cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-16 : Received Submissions Type (BT-760) publication will be delayed -->
<efbc:StatisticsCode listName="received-submission-type">t-sme</efbc:StatisticsCode>
<!-- # UNPUB-17 : Received Submissions Count (BT-759) publication will be delayed -->
<efbc:StatisticsNumeric>12</efbc:StatisticsNumeric>
</efac:ReceivedSubmissionsStatistics>
<efac:ReceivedSubmissionsStatistics>
<!-- Interrupted Mark-up -->
</efac:ReceivedSubmissionsStatistics>
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0001</cbc:ID>
</efac:SettledContract>
<efac:SettledContract>
<cbc:ID schemeName="contract">CON-0003</cbc:ID>
</efac:SettledContract>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles</efbc:StatisticsCode>
<efbc:StatisticsNumeric>5</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:StrategicProcurementStatistics>
<efbc:StatisticsCode listName="vehicles">vehicles-zero-emission</efbc:StatisticsCode>
<efbc:StatisticsNumeric>0</efbc:StatisticsNumeric>
</efac:StrategicProcurementStatistics>
<efac:TenderLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
</efac:LotResult>13.1.3. LotTender level
This covers the withheld publication of:
-
Concession Revenue User (BT-162),
-
Concession Revenue Buyer (BT-160),
-
Value Concession Description (BT-163),
-
Country Origin (BT-191),
-
Winner Organisation Identifier (BT-1701),
-
Winning Tender Value (BT-720),
-
Tender Rank (BT-171),
-
Winning Tender Variant (BT-193),
-
Subcontracting Value Known (BT-730),
-
Subcontracting Percentage Known (BT-731),
-
Subcontracting Value (BT-553),
-
Subcontracting Percentage (BT-555),
-
Subcontracting Description (BT-554),
-
Subcontracting (BT-773).
The codes to be used to identify the field and the location where the unpublish components are to be found are given in Table 40.
| Code | What is to be covered | XPATH to "unpublish" components |
|---|---|---|
con-rev-use |
Concession Revenue User (BT-162) |
|
con-rev-buy |
Concession Revenue Buyer (BT-160) |
|
val-con-des |
Value Concession Description (BT-163) |
|
cou-ori |
Country Origin (BT-191) |
|
win-org-ide |
Winner Organisation Identifier (BT-1701) |
Remains to be identified! |
win-ten-val |
Winning Tender Value (BT-720) |
|
ten-ran |
Tender Rank (BT-171) |
|
win-ten-var |
Winning Tender Variant (BT-193) |
|
sub-val-kno |
Subcontracting Value Known (BT-730) |
|
sub-per-kno |
Subcontracting Percentage Known (BT-731) |
|
sub-val |
Subcontracting Value (BT-553) |
|
sub-per |
Subcontracting Percentage (BT-555) |
|
sub-des |
Subcontracting Description (BT-554) |
|
sub-con |
Subcontracting (BT-773) |
|
A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<efac:LotTender>
<efac:FieldsPrivacy>
<!-- # UNPUB-20 : Tender Rank (BT-171) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">ten-ran
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-21 : Winning Tender Value (BT-720) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">win-ten-val
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<cbc:ID schemeName="tender">TEN-0001</cbc:ID>
<!-- # UNPUB-20 : Tender Rank (BT-171) publication will be delayed -->
<cbc:RankCode>1</cbc:RankCode>
<efbc:TenderVariantIndicator>true</efbc:TenderVariantIndicator>
<!-- # UNPUB-21 : Winning Tender Value (BT-720) publication will be delayed -->
<cac:LegalMonetaryTotal>
<cbc:PayableAmount currencyID="EUR">500</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
<efac:AggregatedAmounts>
<!-- For Contract completion only -->
<cbc:PaidAmount currencyID="EUR">480</cbc:PaidAmount>
<efbc:PaidAmountDescription languageID="ENG">An amount of ...</efbc:PaidAmountDescription>
<efbc:PenaltiesAmount currencyID="EUR">23</efbc:PenaltiesAmount>
</efac:AggregatedAmounts>
<efac:ConcessionRevenue>
<efac:FieldsPrivacy>
<!-- # UNPUB-22 : Concession Revenue User (BT-162) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">con-rev-use
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-23 : Concession Revenue Buyer (BT-160) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">con-rev-buy
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-24 : Value Concession Description (BT-163) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">val-con-des
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-23 : Concession Revenue Buyer (BT-160) publication will be delayed -->
<efbc:RevenueBuyerAmount currencyID="EUR">350</efbc:RevenueBuyerAmount>
<!-- # UNPUB-22 : Concession Revenue User (BT-162) publication will be delayed -->
<efbc:RevenueUserAmount currencyID="EUR">350</efbc:RevenueUserAmount>
<!-- # UNPUB-24 : Value Concession Description (BT-163) publication will be delayed -->
<efbc:ValueDescription>Bla bla bla ...</efbc:ValueDescription>
</efac:ConcessionRevenue>
<efac:ContractTerm>
<!-- For T02 only -->
<efbc:TermCode/>
<efbc:TermDescription/>
<efbc:TermIndicator>true</efbc:TermIndicator>
</efac:ContractTerm>
<efac:ContractTerm>
<!-- For T02 only -->
<efbc:TermCode/>
<efbc:TermDescription/>
<efbc:TermIndicator>true</efbc:TermIndicator>
</efac:ContractTerm>
<efac:Origin>
<efac:FieldsPrivacy>
<!-- # UNPUB-25 : Country Origin (BT-191) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">cou-ori
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-25 : Country Origin (BT-191) publication will be delayed -->
<efbc:AreaCode listName="country">FRA</efbc:AreaCode>
</efac:Origin>
<efac:Origin>
<efbc:AreaCode listName="country">ITA</efbc:AreaCode>
</efac:Origin>
<!-- Associated tenderer -->
<efac:SubcontractingTerm>
<efac:FieldsPrivacy>
<!-- # UNPUB-26 : Subcontracting Value Known (BT-730) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-val-kno
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-27 : Subcontracting Percentage Known (BT-731) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-per-kno
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-28 : Subcontracting Value (BT-553) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-val
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-29 : Subcontracting Percentage (BT-555) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-per
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-30 : Subcontracting Description (BT-554) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-des
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-31 : Subcontracting (BT-773) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">sub-con
</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-28 : Subcontracting Value (BT-553) publication will be delayed -->
<efbc:TermAmount currencyID="EUR">5667</efbc:TermAmount>
<!-- # UNPUB-30 : Subcontracting Description (BT-554) publication will be delayed -->
<efbc:TermDescription languageID="ENG">Bla bli bla bli ...</efbc:TermDescription>
<!-- # UNPUB-29 : Subcontracting Percentage (BT-555) publication will be delayed -->
<efbc:TermPercent>20</efbc:TermPercent>
<!-- # UNPUB-31 : Subcontracting (BT-773) publication will be delayed -->
<efbc:TermCode listName="applicability">..</efbc:TermCode>
<!-- # UNPUB-27 : Subcontracting Percentage Known (BT-731) publication will be delayed -->
<efbc:PercentageKnownIndicator>true</efbc:PercentageKnownIndicator>
<!-- # UNPUB-26 : Subcontracting Value Known (BT-730) publication will be delayed -->
<efbc:ValueKnownIndicator>false</efbc:ValueKnownIndicator>
</efac:SubcontractingTerm>
<efac:TenderingParty>
<cbc:ID/>
</efac:TenderingParty>
<efac:TenderLot>
<cbc:ID schemeName="Lot">LOT-0001</cbc:ID>
</efac:TenderLot>
</efac:LotTender>13.2. Sectoral directive only
13.2.1. Procedure level
This covers the withheld publication of:
-
Cross Border Law (BT-09),
-
Procedure Type (BT-105),
-
Procedure Features (BT-88),
-
Procedure Accelerated (BT-106),
-
Procedure Accelerated Justification (BT-1351),
-
Direct Award Justification Code (BT-136),
-
Direct Award Justification Previous (BT-1252),
-
Direct Award Justification Text (BT-135).
The codes to be used to identify the field and the location where the unpublish components are to be found are given in Table 41.
| Code | What is to be covered | XPATH to "unpublish" components |
|---|---|---|
cro-bor-law |
Cross Border Law (BT-09) |
|
pro-typ |
Procedure Type (BT-105) |
|
pro-fea |
Procedure Features (BT-88) |
|
pro-acc |
Procedure Accelerated (BT-106) |
|
pro-acc-jus |
Procedure Accelerated Justification (BT-1351) |
|
dir-awa-jus |
Direct Award Justification Code (BT-136) |
|
dir-awa-pre |
Direct Award Justification Previous (BT-1252) |
|
dir-awa-tex |
Direct Award Justification Text (BT-135) |
|
A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<ContractAwardNotice>
<!-- interrupted mark-up -->
<cac:TenderingTerms>
<!-- interrupted mark-up -->
<cac:ProcurementLegislationDocumentReference>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:FieldsPrivacy>
<!-- # UNPUB-40 : Cross Border Law (BT-09) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">cro-bor-law</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification"> ...</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- # UNPUB-40 : Cross Border Law (BT-09) publication will be delayed -->
<cbc:ID schemeName="abc">CrossBorderLaw</cbc:ID>
<cbc:DocumentDescription languageID="ENG">Bilateral agreement ...</cbc:DocumentDescription>
<cbc:DocumentDescription languageID="FRA">Accord bilatéral ...</cbc:DocumentDescription>
</cac:ProcurementLegislationDocumentReference>
<!-- interrupted mark-up -->
</cac:TenderingTerms>
<cac:TenderingProcess>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:FieldsPrivacy>
<!-- # UNPUB-41 : Procedure Type (BT-105) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">pro-typ</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-42 : Procedure Features (BT-88) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">pro-fea</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- # UNPUB-42 : Procedure Features (BT-88) publication will be delayed -->
<cbc:Description languageID="ENG">This procedure ....</cbc:Description>
<cbc:Description languageID="FRA">Cette procédure ....</cbc:Description>
<!-- # UNPUB-41 : Procedure Type (BT-105) publication will be delayed -->
<cbc:ProcedureCode listName="procurement-procedure-type">open</cbc:ProcedureCode>
<cac:ProcessJustification>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:FieldsPrivacy>
<!-- # UNPUB-43 : Procedure Accelerated (BT-106) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">pro-acc</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-44 : Procedure Accelerated Justification (BT-1351) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">pro-acc-jus</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- # UNPUB-43 : Procedure Accelerated (BT-106) publication will be delayed -->
<cbc:ProcessReasonCode listName="accelerated-procedure-justification">..</cbc:ProcessReasonCode>
<!-- # UNPUB-44 : Procedure Accelerated Justification (BT-1351) publication will be delayed -->
<cbc:ProcessReason languageID="ENG">Due to ....</cbc:ProcessReason>
<cbc:ProcessReason languageID="FRA">Du fait de ....</cbc:ProcessReason>
</cac:ProcessJustification>
</cac:TenderingProcess>
<!-- interrupted mark-up -->
</ContractAwardNotice>A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information for some DAP related fields. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<cac:TenderingProcess>
<cbc:ProcedureCode listName="procurement-procedure-type">neg-wo-call</cbc:ProcedureCode>
<cac:ProcessJustification>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:FieldsPrivacy>
<!-- # UNPUB-60 : Direct Award Justification Code (BT-136) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">dir-awa-jus</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-61 : Direct Award Justification Previous (BT-1252) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">dir-awa-pre</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-62 : Direct Award Justification Text (BT-135) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">dir-awa-tex</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-03-02+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- # UNPUB-60 : Direct Award Justification Code (BT-136) publication will be delayed -->
<cbc:ProcessReasonCode listName="direct-award-justification">ecom-excl</cbc:ProcessReasonCode>
<!-- # UNPUB-62 : Direct Award Justification Text (BT-135) publication will be delayed -->
<cbc:ProcessReason languageID="ENG">Direct award is justified ...</cbc:ProcessReason>
<cbc:ProcessReason languageID="FRA">L'attribution ...</cbc:ProcessReason>
<!-- # UNPUB-61 : Direct Award Justification Previous (BT-1252) publication will be delayed -->
<cbc:Description>123e4567-e89b-12d3-a456-426614174000</cbc:Description>
</cac:ProcessJustification>
</cac:TenderingProcess>13.2.2. Lot/Group of lots level
This covers the withheld publication of:
-
Award Criterion Type (BT-539),
-
Award Criterion Name (BT-734),
-
Award Criterion Description (BT-540),
-
Award Criterion Number Weight (BT-5421),
-
Award Criterion Number Fixed (BT-5422),
-
Award Criterion Number Threshold (BT-5423),
-
Award Criterion Number (BT-541),
-
Award Criteria Complicated (BT-543),
-
Award Criteria Order Justification (BT-733).
The codes to be used to identify the field and the location where the unpublish components are to be found are given in Table 42.
| Code | What is to be covered | XPATH to "unpublish" components/* |
|---|---|---|
awa-cri-typ |
Award Criterion Type (BT-539) |
Or |
awa-cri-nam |
Award Criterion Name (BT-734) |
Or |
awa-cri-des |
Award Criterion Description (BT-540) |
Or |
awa-cri-wei |
Award Criterion Number Weight (BT-5421) |
Or |
awa-cri-fix |
Award Criterion Number Fixed (BT-5422) |
Or |
awa-cri-thr |
Award Criterion Number Threshold (BT-5423) |
Or |
awa-cri-num |
Award Criterion Number (BT-541) |
Or |
awa-cri-com |
Award Criteria Complicated (BT-543) |
Or |
awa-cri-ord |
Award Criteria Order Justification (BT-733) |
Or |
A mark-up sample is provided below to illustrate the use of the "unpublish" fields with their targeted information. Comments are used to highlight the relation between the "unpublish" and "unpublished" fields.
<cac:AwardingCriterion>
<cbc:Description languageID="ENG">Each criterion is evaluated separately ...</cbc:Description>
<cbc:Description languageID="FRA">Chaque critère est évalué individuellement ...</cbc:Description>
<cac:SubordinateAwardingCriterion>
<ext:UBLExtensions>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:FieldsPrivacy>
<!-- # UNPUB-50 : Award Criterion Type (BT-539) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">awa-cri-typ</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-04-01+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-51 : Award Criterion Name (BT-734) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">awa-cri-nam</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-04-01+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<efac:FieldsPrivacy>
<!-- # UNPUB-52 : Award Criterion Description (BT-540) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">awa-cri-des</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-04-01+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
<ext:UBLExtension>
<ext:ExtensionContent>
<efext:EformsExtension>
<efac:AwardCriterionParameter>
<efac:FieldsPrivacy>
<!-- # UNPUB-53 : Award Criterion Number Threshold (BT-5423) will not be published until March 2nd, 2022 -->
<efbc:FieldIdentifierCode listName="non-publication-identifier">awa-cri-thr</efbc:FieldIdentifierCode>
<cbc:ReasonCode listName="non-publication-justification">..</cbc:ReasonCode>
<efbc:ReasonDescription languageID="ENG">..</efbc:ReasonDescription>
<efbc:ReasonDescription languageID="FRA">..</efbc:ReasonDescription>
<efbc:PublicationDate>2022-04-01+01:00</efbc:PublicationDate>
</efac:FieldsPrivacy>
<!-- # UNPUB-53 : Award Criterion Number Threshold (BT-5423) publication will be delayed -->
<efbc:ParameterCode listName="number-threshold">min-score</efbc:ParameterCode>
<efbc:ParameterNumeric>50</efbc:ParameterNumeric>
</efac:AwardCriterionParameter>
</efext:EformsExtension>
</ext:ExtensionContent>
</ext:UBLExtension>
</ext:UBLExtensions>
<!-- # UNPUB-50 : Award Criterion Type (BT-539) publication will be delayed -->
<cbc:AwardingCriterionTypeCode listName="award-criterion-type">price</cbc:AwardingCriterionTypeCode>
<!-- # UNPUB-51 : Award Criterion Name (BT-734) publication will be delayed -->
<cbc:Name languageID="ENG">Fair & realistic price</cbc:Name>
<cbc:Name languageID="FRA">Prix équitable et réaliste</cbc:Name>
<!-- # UNPUB-52 : Award Criterion Description (BT-540) publication will be delayed -->
<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>
<!-- Interrupted mark-up -->
</cac:AwardingCriterion>14. Codelists and Fields
This section provides further details on some fields and codelists only. It is not foreseen to be exhaustive and gives information necessary for clarification.
14.1. Exclusion grounds codelist
This codelist covers all possible codes for exclusion grounds, it is a tailored codelist built from the criterion codelist.
Some grounds are highly recommended; From the EU legislation perspective, these are mandatory, however derogations are possible (cf. [R1] – art. 57). To identify precisely which value to use, the contracting authority shall also consider local legislation.
References
-
[R1] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC, Text with EEA relevance, Official Journal of The European Union, OJ L 94, 28.3.2014, pp. 65 - 242, Available at http://data.europa.eu/eli/dir/2014/24/oj, accessed February 11th, 2020.
15. Identifiers, References and Pointless Business Terms
The following sections further describe various identifiers and references:
-
Identifiers (to unequivocally identify an object),
-
Identifiers and References (to point to existing objects),
-
BTs introduced by the Regulation Annex irrelevant for the implementation.
15.1. Identifiers
| Business Term | Name of the Business Term | Field ID | Description | schemeName | ID format |
|---|---|---|---|---|---|
BT-01 |
Procedure Legal Basis (ELI - celex) |
BT-01-… BT-01(c)-Procedure BT-01(e)-Procedure |
ELI, celex |
Pattern matching / codes |
|
BT-04 |
Procedure Identifier |
BT-04-notice |
Generated & assigned by OP/eSender |
NA |
UUID v4 |
BT-09 |
Cross Border Law |
BT-09(a)-Procedure |
NA |
CrossBorderLaw |
|
BT-137 |
Purpose Lot Identifier |
BT-137-Lot BT-137-Part BT-137-LotsGroup |
Encoded by the Contracting Authority in accordance with the prescribed format. |
Lot Part LotsGroup |
- LOT-XXXX, |
BT-150 |
Contract Identifier |
BT-150-Contract |
Defined and encoded by the Contracting Authority. Should be unique between all Contract Identifiers of the procedure |
NA |
No restriction yet |
BT-22 |
Internal Identifier |
BT-22-Lot BT-22-LotsGroup BT-22-Part BT-22-Procedure |
CAs define it. No restriction besides string length. |
InternalID |
100 characters max. |
BT-3201 |
Tender Identifier |
BT-3201-Tender |
Defined and encoded by the Contracting Authority. Should be unique between all Tender Identifiers of the procedure |
NA |
No restriction yet |
BT-501 |
Organisation Identifier |
BT-501-Business-European BT-501-Business-National BT-501-Organization-Company |
Discussions ongoing. It will be encoded by the Contracting Authority |
No restriction yet |
|
BT-5010 |
EU Funds Financing Identifier |
BT-5010-Lot |
An identifier of the European Union programme used to at least partially finance the contract. The most concrete information must be given (e.g. the unique European identification number of the relevant programme when available, for example the CCI number for CPR funds, or grant agreement number, national identifier, project acronym, contract number). |
||
BT-5011 |
Contract EU Funds Financing Identifier |
BT-5011-Contract |
Financing Identifier; the most concrete information must be given (e.g. grant agreement number, national identifier, project acronym, contract number) |
||
BT-701 |
Notice Identifier |
BT-701-notice |
Generated & assigned by OP/eSender |
NA |
UUID v4 |
BT-757 |
Notice Version |
BT-757-notice |
01 for the initial version, assigned by the User Interface. Any new version should have a higher version number than any previous one. |
NA |
2 digits. |
BT-784 |
Review Identifier |
BT-784-Review |
An identifier of a review request or a review decision. When appealed to a higher review body instance, a review request must receive a new identifier. |
||
OPP-010 |
Notice Publication Number |
OPP-010-notice |
Information added by OP prior to publication |
ojs-notice-id |
XXXXXXXXXX-YYYY |
OPP-011 |
OJEU Identifier |
OPP-011-notice |
Information added by OP prior to publication |
ojs-id |
XXX/YYYY |
OPP-124 |
Gazette Issue Identifier |
OPP-124-Business |
Identifier of the local Gazette in which information has been published |
||
OPT-001 |
UBL version ID (UBL) |
OPT-001-notice |
Currently based on version 2.3 of the standard. |
NA |
2.3 |
OPT-002 |
Customization ID (UBL) |
OPT-002-notice |
Customization ID based on the SDK versioning |
NA |
eforms-sdk-x.y |
OPT-093 |
Review Technical Identifier |
OPT-093-Review |
Technical ID allowing reference to the Review. Should be unique between all Review technical identifiers of the procedure |
review |
REV-XXXX |
OPT-111 |
Fiscal Legislation Document ID |
OPT-111-Lot-FiscalLegis OPT-111-Part-FiscalLegis |
Technical ID required by the standard |
No restriction |
|
OPT-112 |
Environmental Legislation Document ID |
OPT-112-Lot-EnvironLegis OPT-112-Part-EnvironLegis |
Technical ID required by the standard |
No restriction |
|
OPT-113 |
Employment Legislation Document ID |
OPT-113-Lot-EmployLegis OPT-113-Part-EmployLegis |
Technical ID required by the standard |
No restriction |
|
OPT-140 |
Procurement Documents ID |
OPT-140-Lot OPT-140-Part |
Technical ID required by the standard |
No restriction |
|
OPT-200 |
Organisation Technical Identifier |
OPT-200-Organization-Company |
Identifier used in the notice to refer to the Organisation |
organization |
ORG-XXXX |
OPT-201 |
TouchPoint Technical Identifier |
OPT-201-Organization-TouchPoint |
Identifier used in the notice to refer to the alternate contact details associated to a specific role/subrole |
touchpoint |
TPO-XXXX |
OPT-202 |
Beneficial Owner Technical Identifier |
OPT-202-UBO |
Identifier used in the notice to refer to the Ultimate Beneficial Owner |
ubo |
UBO-XXXX |
OPT-210 |
Tendering Party ID |
OPT-210-Tenderer |
Technical ID allowing reference from the LotResult (or from the LotTender) to the Tendering Party with its composition (Tenderers and subcontractors). |
Tendering-party |
TPA-XXXX |
OPT-316 |
Contract Technical Identifier |
OPT-316-Contract |
Technical ID allowing reference to the contract. Should be unique between all contract technical identifiers of the procedure |
contract |
CON-XXXX |
OPT-321 |
Tender Technical Identifier |
OPT-321-Tender |
Technical ID allowing reference to the tender. Should be unique between all Tender technical identifiers of the procedure |
tender |
TEN-XXXX |
OPT-322 |
LotResult Technical Identifier |
OPT-322-LotResult |
Technical ID allowing reference to the LotResult. Should be unique between all LotResult technical identifiers of the procedure |
result |
RES-XXXX |
15.2. IDs & References
15.2.1. Referring to objects
| Business Term | Name of the Business Term | Field ID | Defined by | schemeName | ID format |
|---|---|---|---|---|---|
BT-125 |
Previous Planning Identifier |
BT-125(i)-Lot BT-125(i)-Part |
A combination of the Notice Identifier (BT-701) and the Notice Version (BT-757) of the previous planning notice |
notice-id-ref |
UUID-XX |
Publication ID of the previous planning notice |
ojs-notice-id |
XXXXXXXX-YYYY |
|||
BT-1251 |
Previous Planning Part Identifier |
BT-1251-Lot BT-1251-Part |
Purpose Lot Identifier of the previous planning notice Part |
PAR-XXXX |
|
BT-1252 |
Direct Award Justification Previous Procedure Identifier |
BT-1252-Procedure |
Procedure Identifier (BT-04), or TEDXML OJS Notice ID |
UUID v4, XXXXXXXX-YYYY |
|
BT-13713 |
Result Lot Identifier |
BT-13713-LotResult |
Points to the Lot (BT-137, LOT-XXXX) the result is about |
Lot |
LOT-XXXX |
BT-13714 |
Tender Lot Identifier |
BT-13714-Tender |
Reference to the Lot or Group of Lots the LotTender applies to. |
Lot, LotsGroup |
LOT-XXXX, GLO-XXXX |
BT-13716 |
Change Previous Section Identifier |
BT-13716-notice |
NB: points to the section of the current notice |
For eForms notices: Cf. Table 45 |
|
BT-1375 |
Group Lot Identifier |
BT-1375-Procedure |
Reference to individual lots that constitute a Group of Lots |
Lot |
LOT-XXXX |
BT-1501(n) |
Modification Previous Notice Identifier |
BT-1501(n)-Contract |
Reference to the CAN (eforms notice only) that announced the contract now subject to modification, using a combination of the Notice Identifier (BT-701) and the Notice Version (BT-757) |
notice-id-ref |
UUID-vv |
Reference to the CAN (eforms or TEDXML) that announced the contract now subject to modification, using the Publication Number |
ojs-notice-id |
XXXXXXXXXX-YYYY |
|||
BT-1501(c) |
Modified Contract |
BT-1501(c)-Contract |
Reference to the Contract that is being modified, using the Contract Technical ID (OPT-316-Contract) |
contract |
CON-XXXX |
BT-1501(p) |
Modified Notice Part Reference |
BT-1501(p)-Contract |
NB: points to the section of the current notice |
For eForms notices: Cf. Table 45 |
|
BT-195 |
Unpublished Identifier |
Values defined in a codelist of Unpublished Business Terms Codes |
|||
BT-3202 |
Contract Tender ID (Reference) |
BT-3202-Contract |
Points to one of the existing (Lot-) Tenders (OPT-321) |
tender |
TEN-XXXX |
BT-330 |
Group Identifier |
BT-330-Procedure |
Points to a defined Group of Lots (BT-137, GLO-XXXX) |
LotsGroup |
GLO-XXXX |
BT-556 |
Group Framework Value Lot Identifier |
BT-556-NoticeResult |
Reference to the Group of Lots the Framework applies to. |
LotsGroup |
GLO-XXXX |
BT-758 |
Change Notice Version Identifier |
BT-758-notice |
A combination of the Notice Identifier (BT-701) and the Notice Version (BT-757) of the notice being changed (eForms notices only). |
notice-id-ref |
UUID-vv |
Publication ID of the notice being changed. eForms or TED XML notices. |
ojs-notice-id |
XXXXXXXX-YYYY |
|||
BT-785 |
Review Previous Identifier |
BT-785-Review |
Identifier of the review request(s) that led to this decision or a review decision that is being appealed by this review request. |
||
BT-786 |
Review Notice Section Identifier |
BT-786-Review |
An identifier of one or more sections within this notice. The information in the review section refers to this section or these sections. |
||
OPP-090 |
Previous Notice Identifier |
OPP-090-Procedure |
Publication ID of the previous (TED XML) notice. |
ojs-notice-id |
XXXXXXXX-YYYY |
OPT-100 |
Framework Notice Identifier |
OPT-100-Contract |
A combination of the Notice Identifier (BT-701) and the Notice Version (BT-757) of the notice that announced the Framework Agreement (eForms notices only) |
notice-id-ref |
UUID-vv |
Publication ID of the notice that announced the Framework Agreement (eForms or TED XML notices). |
ojs-notice-id |
XXXXXXXX-YYYY |
|||
OPT-300 |
Buyer Technical Identifier Reference |
OPT-300-Procedure-Buyer |
Points to the Organisation acting as a Buyer |
organization |
ORG-XXXX |
OPT-300 |
Service Provider Technical Identifier Reference |
OPT-300-Procedure-SProvider |
Points to the Organisation acting as a Service Provider |
organization |
ORG-XXXX |
OPT-300 |
Signatory Identifier Reference |
OPT-300-Contract-Signatory |
Points to the Organisation who signed the contract |
organization |
ORG-XXXX |
OPT-300 |
Tenderer ID Reference |
OPT-300-Tenderer |
Points to an Organisation tendering alone, or jointly as part of a consortium or equivalent arrangement. |
organization |
ORG-XXXX |
OPT-301 |
Additional Info Provider Technical Identifier Reference |
OPT-301-Lot-AddInfo OPT-301-Part-AddInfo |
Points to the Organisation, or its alternate contact details, from where additional information about the procurement procedure may be obtained. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Document Provider Technical Identifier Reference |
OPT-301-Lot-DocProvider OPT-301-Part-DocProvider |
Points to the Organisation, or its alternate address, from where documents may be consulted offline. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Employment Legislation Organization Technical Identifier Reference |
OPT-301-Lot-EmployLegis OPT-301-Part-EmployLegis |
Points to the Organisation, or its alternate contact details, from where additional information about the employment legislation may be obtained. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Environmental Legislation Organization Technical Identifier Reference |
OPT-301-Lot-EnvironLegis OPT-301-Part-EnvironLegis |
Points to the Organisation, or its alternate contact details, from where additional information about the environmental legislation may be obtained. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Fiscal Legislation Information Provider Technical Identifier Reference |
OPT-301-Lot-FiscalLegis OPT-301-Part-FiscalLegis |
Points to the Organisation, or its alternate contact details, from where additional information about the tax legislation may be obtained. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Financing Party (ID reference) |
OPT-301-LotResult-Financing |
Points to the Organisation whose Budget is used to pay the contract |
organization |
ORG-XXXX |
OPT-301 |
Main Contractor ID Reference |
OPT-301-Tenderer-MainCont |
For a given Sub-contractor, points to the tenderer of the same tendering Party to which it is providing services |
organization |
ORG-XXXX |
OPT-301 |
Mediator Technical Identifier Reference |
OPT-301-Lot-Mediator OPT-301-Part-Mediator |
Points to the Organisation, or one of its alternate contact details, dealing with mediation. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Payer Party (ID reference) |
OPT-301-LotResult-Paying |
Points to the Organisation executing the payments |
organization |
ORG-XXXX |
OPT-301 |
Review Info Provider Technical Identifier Reference |
OPT-301-Lot-ReviewInfo OPT-301-Part-ReviewInfo |
Points to the Organisation, or one of its alternate contact details, where more information on the time limits for review procedures may be obtained. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Review Organization Technical Identifier Reference |
OPT-301-Lot-ReviewOrg OPT-301-Part-ReviewOrg |
Points to the Organisation, or one of its alternate contact details, dealing with reviews. |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Subcontractor ID Reference |
OPT-301-Tenderer-SubCont |
Points to the sub-contractor of a Tendering Party |
organization |
ORG-XXXX |
OPT-301 |
Tender Evaluator Technical Identifier Reference |
OPT-301-Lot-TenderEval OPT-301-Part-TenderEval |
Points to the Organisation, or one of its alternate contact details, processing tenders or requests to participate |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Tender Recipient Technical Identifier Reference |
OPT-301-Lot-TenderReceipt OPT-301-Part-TenderReceipt |
Points to the Organisation, or one of its alternate contact details, receiving tenders or requests to participate |
organization, touchpoint |
ORG-XXXX, TPO-XXXX |
OPT-301 |
Review Body (Reference ID) |
OPT-301-ReviewBody |
Points to the Organisation acting as a Review Body |
organization |
ORG-XXXX |
OPT-301 |
Review Requester (Reference ID) |
OPT-301-ReviewReq |
Points to the Organisation that requested the review |
organization |
ORG-XXXX |
OPT-302 |
Beneficial Owner Reference |
OPT-302-Organization |
For an economic operator acting as a tenderer or subcontractor, points to the Ultimate Beneficial Owner. |
ubo |
UBO-XXXX |
OPT-310 |
Tendering Party ID Reference |
OPT-310-Tender |
From a LotResult or from a LotTender, points to the associated TenderingParty |
tendering-party |
TPA-XXXX |
OPT-315 |
Contract Identifier Reference |
OPT-315-LotResult |
From a LotResult, points to a contract |
contract |
CON-XXXX |
OPT-320 |
Tender Identifier Reference |
OPT-320-LotResult |
From a Contract points to a related tender and from a LotResult to a tender that applies to the Lot (or a Group of Lots containing it) |
tender |
TEN-XXXX |
15.2.2. Referring to sections of a notice
When creating a change or modifying a Contract, an author has to identify the notice sections involved. The section references will be extracted from the Change notice or Contract Modification notice itself (i.e. the technical identifiers will exist and be known). The following table lists the usable identifiers available to refer to the different sections. Sections for which the text is in grey italic can’t be updated with a Change notice and there is therefore no code associated (NA).
| ID | Object | Information |
|---|---|---|
BUYER |
Buyers |
|
CON-XXXX |
Contract |
and for Contract Modification to identify the modified Contract |
ORG-XXXX |
Organisations |
|
PROCEDURE |
Procedure |
|
PAR-XXXX |
Nth part |
|
GLO-XXXX |
Nth Group of Lots |
|
LOT-XXXX |
Lot N |
|
RESULT |
Notice Result |
|
RES-XXXX |
Result for Lot N |
|
TEN-XXXX |
Tender |
|
TPA-xxxx |
Tendering Party |
|
TPO-XXXX |
Touchpoint |
|
REV-xxxx |
Review |
|
UBO-XXXX |
Ultimate Beneficial Owner |
|
NA |
Contract modification |
A "change" on a "Contract Modification" will act on the other sections of the parent "Contract Modification" notice |
NA |
Changes |
A "change" on a "Change" will act on the other sections of the parent "Change" notice |
NA |
Notice information |
Notice metadata can not be modified with a "Change". |
15.3. Pointless Business Terms due to design
Structural differences between the eForms Regulation Annex and UBL (e.g. normalized vs denormalized data) make some Business Terms not necessary and not possible to represent. Additionally, some indicators based rules make those indicators and their associated Business Terms useless.
| Field | Name of the field | Explanation |
|---|---|---|
BT-557 |
Group Framework Maximum Value Lot Identifier |
BT-137 |
BT-1371 |
Previous Planning Lot Identifier |
BT-137 |
BT-1372 |
Place Performance Lot Identifier |
BT-137 |
BT-1373 |
Duration Lot Identifier |
BT-137 |
BT-1374 |
Funds Lot Identifier |
BT-137 |
BT-1376 |
Second Stage Lot Identifier |
BT-137 |
BT-1377 |
Rewards Lot Identifier |
BT-137 |
BT-1378 |
Selection Lot Identifier |
BT-137 |
BT-1379 |
Requirements Lot Identifier |
BT-137 |
BT-13717 |
Terms Lot Identifier |
BT-137 |
BT-13710 |
Award Criteria Lot Identifier |
BT-137 |
BT-13711 |
Techniques Lot Identifier |
BT-137 |
BT-13712 |
Communication Lot Identifier |
BT-137 |
BT-13718 |
Documents Lot Identifier |
BT-137 |
BT-13719 |
Submission Lot Identifier |
BT-137 |
BT-13720 |
Organisation Notice Section Identifier |
Links conveyed by UBL elements at dedicated places within the XML (cf. Linking roles/subroles to organizations) |
BT-13721 |
Strategic Procurement Notice Section Identifier |
BT-137 |
BT-13722 |
Buyer Review Lot Identifier |
BT-137 |
BT-13715 |
Additional Information Lot Identifier |
BT-137 |
BT-53 |
Options |
Not represented in UBL. Not required as BT-54 is mandatory when BT-53 is "Yes". If BT-54 is not there, then BT-53 is "No" |
BT-724 |
Tool Atypical |
When dealing with an atypical tool, the URL where the tool may be found (BT-124) is mandatory, else it is not allowed. The presence of BT-124 is sufficient to detect whether the tool is atypical or not. |
BT-778 |
Framework Maximum Participants |
Not represented in UBL. Not required, if BT-113 is mandatory when BT-778 is "Yes". If BT-113 is not there, then BT-778 is "No" |
BT-5561 |
Group Framework Re-estimated Value Lot Identifier |
BT-556 |
16. Terms & definitions
- Admissible tender
-
A tender which:
-
is from a non-excluded tenderer meeting the selection criteria,
-
conforms with the technical specifications,
-
is regular (e.g. submitted on time, normal price & cost, …), acceptable, and suitable.
-
- CELEX number
-
Identifier assigned at EUR-Lex to documents regardless of the language they are written in. A short presentation may be found at https://eur-lex.europa.eu/content/help/faq/celex-number.html.
- Central Purchasing Body
-
"A procuring entity that provides centralised purchasing activities and, possibly, ancillary purchasing activities for other procuring entities." (eProcurement Ontology)
- Concession directive
-
Directive 2014/23/EU of the European Parliament and of the Council of 26 February 2014 on the award of concession contracts, Text with EEA relevance [R1]
- Contractor
-
For a given Lot, a Contractor is any Tenderer that has signed a Contract.
- Defence directive
-
Directive 2009/81/EC of the European Parliament and of the Council of 13 July 2009 on the coordination of procedures for the award of certain works contracts, supply contracts and service contracts by contracting authorities or entities in the fields of defence and security, and amending Directives 2004/17/EC and 2004/18/EC (Text with EEA relevance) [R4]
- General directive
-
Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC Text with EEA relevance [R2]
- Joint procurement
-
Combined procurement actions of two or more contracting authorities with a single call for competition published on behalf of all participating authorities.
Further information may be found on the EC factsheet.
- Legal regime
-
A system of principles and rules governing something, and which is created by law. It is framework of legal rules. (https://definitions.uslegal.com/l/legal-regime/) There are two regimes defined for eForms: standard regime, and social regime.
- Part
-
"PIN only" (prior information notice used only for information) component, that, at launch of the call for competition, may become a Lot or a self-standing Procedure.
- Procurement procedure
-
Series of actions conducted in a given sequence that leads to the conclusion of a public contract. The purpose is threefold:
-
To guarantee the widest possible participation of economic operators;
-
To ensure the transparency of operations; and
-
To obtain the desired quality of services, supplies and works at the best possible price.
Offers submitted in the context of a procurement procedure are called "tenders". An economic operator who has submitted a tender is referred to as a "tenderer".
-
- Qualification System
-
To be defined
- Sectoral directive
-
Directive 2014/25/EU of the European Parliament and of the Council of 26 February 2014 on procurement by entities operating in the water, energy, transport and postal services sectors and repealing Directive 2004/17/EC, Text with EEA relevance [R3]
- Tenderer
-
For a given Lot, a Tenderer is any organisation, Subcontractors excluded, that, alone or as part of a group (the so-called Tendering Party), submits a Tender for that Lot.
- Winner
-
For a given Lot, a Winner is any Tenderer that has been awarded a Contract.
References
-
[R1] Directive 2014/23/EU of the European Parliament and of the Council of 26 February 2014 on the award of concession contracts, Text with EEA relevance, Official Journal of The European Union, OJ L 94, March 28th, 2014, pp. 1 - 64, accessible at http://data.europa.eu/eli/dir/2014/23/oj, accessed February 11th, 2020
-
[R2] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC, Text with EEA relevance, Official Journal of The European Union, OJ L 94, 28.3.2014, pp. 65 - 242, Available at http://data.europa.eu/eli/dir/2014/24/oj, accessed February 11th, 2020.
-
[R3] Directive 2014/25/EU of the European Parliament and of the Council of 26 February 2014 on procurement by entities operating in the water, energy, transport and postal services sectors and repealing Directive 2004/17/EC, Text with EEA relevance. Official Journal of The European Union, OJ L 94, 28.3.2014, pp. 243 - 374, available at http://data.europa.eu/eli/dir/2014/25/oj, accessed February 11th, 2020.
-
[R4] Directive 2009/81/EC of the European Parliament and of the Council of 13 July 2009 on the coordination of procedures for the award of certain works contracts, supply contracts and service contracts by contracting authorities or entities in the fields of defence and security, and amending Directives 2004/17/EC and 2004/18/EC (Text with EEA relevance), Official Journal of The European Union, OJ L 216, 20.8.2009, pp. 76 - 136, accessible at http://data.europa.eu/eli/dir/2009/81/oj, accessed February 11th, 2020.
17. References
-
[R1] Commission Implementing Regulation (EU) 2019/1780 of 23 September 2019 establishing standard forms for the publication of notices in the field of public procurement and repealing Implementing Regulation (EU) 2015/1986 (eForms) (Text with EEA relevance) , Official Journal of The European Union, OJ L 272, Oct. 25th, 2019, pp. 7 - 73, available at http://data.europa.eu/eli/reg_impl/2019/1780/oj, accessed January 27th, 2020.
-
[R2] Commission Implementing Regulation (EU) 2015/1986 of 11 November 2015 establishing standard forms for the publication of notices in the field of public procurement and repealing Implementing Regulation (EU) No 842/2011, Official Journal of The European Union, OJ L 296, Nov. 12th, 2015, pp. 1 - 146, available at http://data.europa.eu/eli/reg_impl/2015/1986/oj, accessed January 27th, 2020
-
[R3] Communication From The Commission To The European Parliament, The Council, The European Economic And Social Committee And The Committee Of The Regions, Upgrading the Single Market: more opportunities for people and business, Oct. 28th, 2015, 23 p., available at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52015DC0550, accessed January 27th, 2020
-
[R4] NUTS — Nomenclature of territorial units for statistics, Eurostat, https://ec.europa.eu/eurostat/web/nuts/background, accessed April 16th, 2019.
-
[R5] Council Directive 89/665/EEC of 21 December 1989 on the coordination of the laws, regulations and administrative provisions relating to the application of review procedures to the award of public supply and public works contracts, Official Journal of The European Union, OJ L 395 , Dec. 30th, 1989 pp. 33 — 35, available at http://data.europa.eu/eli/dir/1989/665/oj, accessed January 27th, 2020
-
[R6] Council Directive 92/13/EEC of 25 February 1992 coordinating the laws, regulations and administrative provisions relating to the application of Community rules on the procurement procedures of entities operating in the water, energy, transport and telecommunications sectors, Official Journal of The European Union, OJ L 076 , March 23rd, 1992, pp. 14 - 20, available at http://data.europa.eu/eli/dir/1992/13/oj, accessed January 27th, 2020
-
[R7] Directive 2014/23/EU of the European Parliament and of the Council of 26 February 2014 on the award of concession contracts, Text with EEA relevance, Official Journal of The European Union, OJ L 94, March 28th, 2014, pp. 1 - 64, accessible at http://data.europa.eu/eli/dir/2014/23/oj, accessed February 11th, 2020
-
[R8] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC, Text with EEA relevance, Official Journal of The European Union, OJ L 94, 28.3.2014, pp. 65 - 242, Available at http://data.europa.eu/eli/dir/2014/24/oj, accessed February 11th, 2020.
-
[R9] Directive 2014/25/EU of the European Parliament and of the Council of 26 February 2014 on procurement by entities operating in the water, energy, transport and postal services sectors and repealing Directive 2004/17/EC, Text with EEA relevance. Official Journal of The European Union, OJ L 94, 28.3.2014, pp. 243 - 374, available at http://data.europa.eu/eli/dir/2014/25/oj, accessed February 11th, 2020.
-
[R10] Directive 2009/81/EC of the European Parliament and of the Council of 13 July 2009 on the coordination of procedures for the award of certain works contracts, supply contracts and service contracts by contracting authorities or entities in the fields of defence and security, and amending Directives 2004/17/EC and 2004/18/EC (Text with EEA relevance), Official Journal of The European Union, OJ L 216, 20.8.2009, pp. 76 - 136, accessible at http://data.europa.eu/eli/dir/2009/81/oj, accessed February 11th, 2020.
-
[R11] eForms Policy Implementation Handbook, European Commission, Directorate-General for Internal Market, Industry, Entrepreneurship and SMEs, 2019, 108 p., available at https://op.europa.eu/en/publication-detail/-/publication/73a78487-cc8b-11ea-adf7-01aa75ed71a1, accessed April 6th, 2021
-
[R12] Commission Implementing Regulation (EU) 2022/2303 of 24 November 2022 amending Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices in the field of public procurement (Text with EEA relevance) , Official Journal of The European Union, OJ L 305, Nov. 25th, 2022, pp. 12 – 50, available at http://data.europa.eu/eli/reg_impl/2022/2303/oj, accessed January 24th, 2023.
18. Other resources
-
EU Vocabularies, eProcurement authority tables: https://op.europa.eu/en/web/eu-vocabularies/e-procurement/tables
-
eProcurement ontology: https://github.com/eprocurementontology/eprocurementontology
-
eForms DG GROW 2nd consultation https://github.com/eForms/eForms
-
eForms on the TED website https://ted.europa.eu/en/simap/eforms
-
Law Insider, Dictionary, Tendering Party definition https://www.lawinsider.com/dictionary/tendering-party
-
Law Insider, Dictionary, Tenderer definition https://www.lawinsider.com/dictionary/tenderer