| Class name | -Attribute name | -Definition | -Data type / cardinality | +epo-cat:CatalogueResponseInformation | +|
|---|---|---|---|---|---|
| adms:Identifier | -adms:schemaAgency | -The name of the agency that issued the identifier. | -rdf:PlainLiteral [0..*] | +epo-cat:CatalogueResponseLine | +|
| cccev:Criterion | -cccev:bias | -Parameter used to adjust the evaluation of the Criterion. + | epo-cat:ChargeInformation | +Information about tax, fee or duty imposed. Additional Information: - The bias parameter tries to correct a systematic error. For example in procurement, - a home bias corresponds to the "presence of local preferences distorting international - specialisation and resource allocation". When quantified, this systematic error can - be removed. | -xsd:decimal [0..1] | + Charge category indicates the nature of the tax/duty/fee, for example VAT, CAR, etc. + Charge category modifier may be used in case different levels, exemptions or other + modifications apply. + The charge can be fixed or relative to the price. + + WG approval 16/05/2023
| cccev:Criterion | -cccev:weight | -Relative importance of the Criterion. + | epo-cat:InformationHub | +Grouping of data that may be associated to various concepts. Additional Information: - The weight must be between 0 and 1. Usually, all Criteria can be integrated within - a weighted sum equal to 1. | -xsd:decimal [0..1] | + For example, AllowanceChargeInformation may be associated to the Order or the Catalogue + (either at the Line level or at the Document level), amongst others. + + WG approval 16/05/2023
| cccev:Criterion | -cccev:weightingConsiderationDescription | -Explanation of how the weighting of a Criterion is to be used. + | epo-cat:Item | +A product, work, service or any combination of them. Additional Information: - This description gives the view of the creator of the Criterion weights on how to - interpret and use them during the evaluation process. | -rdf:PlainLiteral [0..1] | + An Item can be an atomic Thing or a composition of things that together are seen as + a unit, e.g. a tetrabrik of milk or an indivisible package of six tetrabriks. + + No distinction is provided between services, goods and works to leave room for innovation. + + WG approval 30/06/2022
| cpov:ContactPoint | -cpov:email | -The email of the Organisation. + | epo-cat:ItemAccessoryRelation | +Combination of two Items where the former enhances the latter. + WG Approval: 30/06/2022 | -rdf:PlainLiteral [0..*] |
| cpov:ContactPoint | -cpov:telephone | -A telephone number through which the Contact Point can be contacted. + | epo-cat:ItemComplementaryRelation | +Combination of two Items which mutually enhance one another. + + WG Approval: 30/06/2022 + | -rdf:PlainLiteral [0..*] |
| person:Person | -cv:birthDate | -The point in time on which the Person was born. | -xsd:date [0..1] | +epo-cat:ItemComposition | +Inclusion of an Item into in the described Item. + + Additional Information: + The Item is provided with its components, however, the component Items may also be + provided separately. + For example, a bicycle has wheels as components, but they may be provided as spare + parts as well. + This relation is useful to describe different package levels of an item or hierarchies + of Items. + + WG Approval: 19/05/2022 + + + |
| locn:Geometry | -cv:coordinates | -The coordinate list. | -rdf:PlainLiteral [0..*] | +epo-cat:ItemModel | +A specific design or version of a product or service. + + Additional information: + This class is meant as a reusable reference to the model name rather than as a set + of specifications of an Item of this particular model. + + WG acceptance 10/03/2022 + + |
| locn:Geometry | -cv:latitude | -The latitude. | -rdf:PlainLiteral [0..*] | +epo-cat:ItemProperty | +Construct meant to represent the association between an attribute defined in an external + classification scheme and the value ascribed to it. + + WG approval 26/07/2022 |
| locn:Geometry | -cv:longitude | -The longitude. | -rdf:PlainLiteral [0..*] | +epo-cat:ItemRelation | +Connection between two Items. + + WG Approval: 30/06/2022 + |
| person:Person | -dct:alternative | -Any name by which an individual is known other than their full name. - WG 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo-cat:ItemReplacement | +Supplantment, displacement or suspension of an Item by the described Item. + + WG Approval: 30/06/2022 + |
| cccev:Evidence cccev:InformationConcept cccev:Requirement cpov:ContactPoint cv:Channel epo:AgentInRole epo:Document epo:ElectronicSignature epo:Fund epo:NonDisclosureAgreementTerm epo:SecurityClearanceTerm epo:SubcontractingEstimate epo:SubcontractTerm epo:System epo:Technique epo:LotGroup epo:ProcurementElement epo:TenderGroup |
- dct:description | -An account of the resource. + | epo-cat:ItemRequirement | +Necessity of an Item by the described item. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + The described item is provided without other items that are required for proper functionality. - WG Approval 30/05/2023 An account of the resource. + For example, a printer cannot be used without ink cartridge; or a Server cannot be + used without its installation. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG Approval: 19/05/2022 - WG Approval 30/05/2023 An account of the resource. + | +|
| epo-cat:Line | ++ | ||||
| epo-cat:Manufacturer | +The Producer of goods or provider of services. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + Also, known as Supplier and Manufacturer. - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + We do not care who provides these service or products we care with whom Business is + done. - WG Approval 30/05/2023 An account of the resource. + PEPPOL - Invoice: + The Supplier is the Legal Person or Organisation who provides a product and/or service. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + PEPPOL - Order: The supplier is the legal person or organisation who provides a product + or service. + Examples of supplier roles: seller, despatch party, creditor, economic operator. - WG Approval 30/05/2023 An account of the resource. + | +||||
| epo-cat:PostAwardDocument | ++ | ||||
| epo-cat:Price | +Amount of money required or given in exchange for Items. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + Additional information: + The Price excludes any charges (such as taxes, duties and fees) and discounts. - WG Approval 30/05/2023 An account of the resource. + WG approval 26/07/2022 | +||||
| epo-cat:ProductSpecification | +Document providing information about an Item. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG approval 07/04/2022 - WG Approval 30/05/2023 - An account of the resource. + | +||||
| epo-con:ContractAmendment | +A change to an existing Contract that is agreed by the contracting parties. | +||||
| epo-con:ContractModificationInformation | ++ | ||||
| epo-con:Deliverable | ++ | ||||
| epo-ful:AbstractContainer | ++ | ||||
| epo-ful:Carrier | +The Role of an Agent who handles the physical Delivery/Transportation of the (Despatched) + Shipment. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. + This Role is also known as Deliverer. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG approval: 11/10/2022 | +||||
| epo-ful:Consignment | +A batch of goods destined for or delivered to someone. - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - | -rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [1..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] |
+ Additional information:
+ Consignment it is a Transport Agreement. They do not care about the content of what
+ is being shipped. (only if there are dangerous goods, and temperature requirements).
+ How to move from place a to place B.
|||
| epo:Document | -dct:issued | -Date of formal issuance of the resource. - - Additional information: - This is generally used for modules other than eNotice. - The xsd:dateTime here means that we can provide either xsd:date, xsd:dateTime, or - xsd:timeStamp or any other variant of time expression. This extension needs to be - encoded/automated in the ontology and in the application profile. - Why is it like this? Because UML cannot handle such expressions of disjunctive property - ranges. - - WG approval 26/01/2023 | -xsd:dateTime [0..1] | +epo-ful:DespatchAdvice | +|
| epo:AgentInRole epo:Document epo:Fund foaf:Agent epo:LotGroup epo:ProcurementElement epo:TenderGroup |
- dct:title | -A name given to the resource. - - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 - - A name given to the resource. - - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 A name given to the resource. + | epo-ful:Despatcher | +Role of an Agent who sends the goods or notifies of the service or works execution. - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 A name given to the resource. - WG approval 30/05/2023 - | -rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] |
+ Additional Information:
+ The Role is carried out by the Supplier or on behalf of the Supplier.
+ Despatcher is also known as Despatch Party, Consignor, Deliverer.
| epo:SelectionCriteriaSummary | -epo:describesMinimumLevelOfStandards | +epo-ful:DespatchLine | - | rdf:PlainLiteral [0..1] | |
| epo:ParticipationConditionsSummary | -epo:describesObjectiveParticipationRules | +epo-ful:FreightForwarder | - | rdf:PlainLiteral [0..1] | |
| epo:ProfessionalSuitabilitySummary | -epo:describesProfession | -- | rdf:PlainLiteral [0..1] | +epo-ful:GoodsItem | +An Item including its initial packaging during transportation. + + Additional information: + For example, the Item being bought is the computer. The weight of the computer is + X. + The weight of the Goods Item is the weight of the computer plus the weight of the + initial packaging. + During transportation you have for example trace ID which is applied to the GoodsItem, + rather than on the Item itself. + The declared statistical value can only apply once you have a GoodsItem. + + WG approval 30/03/2023 |
| epo:ProfessionalSuitabilitySummary | -epo:describesProfessionRelevantLaw | +epo-ful:Notifier | +The party to be notified upon arrival of goods and when special occurrences (usually + pre-defined) take place during a transportation service. (UBL) + | +||
| epo-ful:Package | - | rdf:PlainLiteral [0..1] | |||
| epo:ParticipationConditionsSummary | -epo:describesVerificationMethod | +epo-ful:ReceiptAdvice | - | rdf:PlainLiteral [0..1] | |
| epo:SubmissionStatisticalInformation | -epo:hasAbnormallyLowTenders | -Tenders received that were found irregular and non-acceptable due to an abnormally - low price or cost. - - Additional Information - The definition implies that abnormally Low Tender Lots are Inadmissible Tender Lots. - - WG Approval 28/07/2020 - - | -xsd:integer [0..1] | +epo-ful:ReceiptAdviceLine | +|
| epo:Procedure | -epo:hasAcceleratedProcedureJustification | -The reasons why the procedure is accelerated. + | epo-ful:ShipmentAgreement | +The Commercial Agreement between the Commercial Parties. Additional Information: - A procedure is accelerated to cover needs of extraordinary circumstances ie earthquake - relief. - - WG Approval 09/06/2020 - + It describes items being shipped. What is being moved. | -rdf:PlainLiteral [0..*] |
| epo:NonPublishedInformation | -epo:hasAccessibilityDate | -The date at which unpublished data shall be published. + | epo-ful:ShipmentInformation | +The Transportation of an identifiable collection of Goods Items from one party (the + Despatch Party) to another party (the Consignee) via one or more modes of transport. - WG Approval 11/06/2020 | -xsd:date [0..1] | + Addition Information + This represents the "where" and "when".
| epo:Document | -epo:hasAccessURL | -Location where the resource can be accessed. - - WG approval 07/04/2022 | -xsd:anyURI [0..*] | +epo-ful:ShipmentStage | +|
| epo:Buyer | -epo:hasActivityDescription | -In the ePO ontology a taxonomy with all activities, based on different classifications - (COFOG, UTILITIES, NACE), will be provided. In ePO this field is to be used exclusively - to complement the definition attached to the MainActivityCode. - - However, in eForms there is the code "other" to cover undefined activities. For mapping - to this eForms feature one could also use this property. - | -rdf:PlainLiteral [0..*] | +epo-ful:TemperatureSpecification | +|
| epo:ChangeInformation epo:Notice epo:ProcurementCriterion epo:ProcurementObject |
- epo:hasAdditionalInformation | -Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 - Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 | -rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] |
+ epo-ful:TransportEquipment | +|
| epo:AccessTerm | -epo:hasAdditionalInformationDeadline | -The time limit for requesting further information. - - Additional information: - - This is generally used to indicate the deadline for Economic Operators to request - further information of the procedure before the submission deadline. - - This corresponds in eForms to BT-13 Additional Information Deadline. - - WG Approval 09/06/2020 - | -xsd:dateTime [0..1] | +epo-ful:TransportEquipmentSeal | +|
| epo:AwardDecision | -epo:hasAdditionalNonAwardJustification | -Further justification for the non award . - - Additional information: - This is generally used when the non award reason code is set to "Other". - - WG: 18/01/2022 | -rdf:PlainLiteral [0..1] | +epo-ful:TransportHandlingUnit | +A description of Individual Handling Units in which the Line Items are packed. |
| cv:Channel | -epo:hasAddressURL | +epo-ful:TransportMeans | - | xsd:anyURI [0..1] | |
| foaf:Agent | -epo:hasAlias | -Acronym or alternative name of the Agent. - WG Approval 25/03/2021 | -rdf:PlainLiteral [0..*] | +epo-ful:TransportMeansOperator | +|
| epo:MonetaryValue | -epo:hasAmountValue | -The numeric value of the amount, including decimals. | -xsd:decimal [1..1] | +epo-not:CANDefence-D81 | +|
| epo:AwardEvaluationTerm | -epo:hasAwardCriteriaEvaluationFormula | -The mathematical equation or any other description used for complicated weighing of - criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing - cannot be expressed per criterion. - - Additional Information: - This corresponds in eForms to BT-543 Award Criteria Complicated. | -rdf:PlainLiteral [0..*] | +epo-not:CANSocial-D25 | +|
| epo:AwardEvaluationTerm | -epo:hasAwardCriteriaOrderJustification | -The justification for only indicating the award criteria's order of importance, not - their weighing. - - Additional Information: - This corresponds in eForms to BT-733 Award Criteria Order Justification. | -rdf:PlainLiteral [0..1] | +epo-not:CANSocialNotice | +|
| epo:AwardCriterion | -epo:hasAwardCriteriaStatedInProcurementDocuments | -- | xsd:boolean [1..1] | +epo-not:CANSocialNotice-D25 | +Additional information: + Social and other specific services – utilities + |
| epo:ProcessPlanningTerm | -epo:hasAwardDateScheduled | -Planned date for the award decision. - WG Approval 09/11/2021 | -xsd:date [0..1] | +epo-not:CANStandard-D24 | +|
| epo:AwardDecision | -epo:hasAwardDecisionDate | -The official date of the award decision. - - Additional Information: - This corresponds in eForms to BT-1451 Winner Decision Date. - - WG Approval 09/01/2020 - | -xsd:dateTime [0..1] | +epo-not:CANStandardNotice | +|
| epo:TenderAwardOutcome | -epo:hasAwardRank | -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. - - Additional Information: - This corresponds in eForms to BT-171 Tender Rank. - | -xsd:integer [0..1] | +epo-not:CNDefence-D81 | +|
| epo:Period | -epo:hasBeginning | -The date and time on which this period begins. | -xsd:dateTime [0..1] | +epo-not:CNSocial-D25 | +|
| epo:FrameworkAgreementTerm | -epo:hasBuyerCategoryDescription | -A classification of buyers participating in a framework agreement. - - Additional Information: - Buyers that can use the Framework Agreement not mentioned by name. - - For example, the classification "all hospitals in the Tuscany region" is used instead - of naming each individual buyer. - - This corresponds in eForms to BT-111 Framework Buyer Categories. - - WG Approval 2019-05-06 | -rdf:PlainLiteral [0..*] | +epo-not:CNSocialNotice | +|
| org:Organization | -epo:hasBuyerLegalTypeDescription | -Self-explanatory text about the Buyer Legal Type. - - Additional information: - This field is used when the Buyer Legal Type is not available in the controlled list - at-voc:buyer-legal-type . This is necessary in to cover data provided in the TED Standard - Forms. It shall be deprecated in the future. - - WG Approval 06/09/2022 | -rdf:PlainLiteral [0..1] | +epo-not:CNSocialNotice-D25 | +Additional information: + Social and other specific services – utilities + |
| epo:Buyer | -epo:hasBuyerProfile | -Website address where the buyer publishes information on its procurement procedures - and general information. - - Additional information: - This corresponds in the eForms to BT-508 Buyer Profile URL. + | epo-not:CNStandard-D24 | ++ | |
| epo-not:CNStandardNotice | ++ | ||||
| epo-not:CompetitionNotice | +An announcement of the launch of a Procurement Procedure by a Procuring Entity. - WG approval 04/05/2018 + WG approval 18/05/2018 | -xsd:anyURI [0..1] | |||
| epo:ConcessionEstimate | -epo:hasCalculationMethod | -Formula for obtaining values. - - Additional Information: - The possible values are monetary values, ranking scores, criterion weighting. - - WG Approval 25/05/2018 | -rdf:PlainLiteral [0..1] | +epo-not:CompletionNotice | +An announcement of the end of a Procurement by a Buyer. |
| epo:Certificate | -epo:hasCertificationNumber | -The unique identifier of the certificate. - - WG approval 26/07/2022 | -rdf:PlainLiteral [0..1] | +epo-not:ConcessionAwardNotice-D23 | +|
| epo:ChangeInformation | -epo:hasChangeDescription | -Explanatory text about the instance of the concept. - - WG Approval 30/09/2019 | -rdf:PlainLiteral [0..*] | +epo-not:ConcessionNotice-D23 | +|
| epo:ChangeInformation | -epo:hasChangeReasonDescription | -Explanatory text about why the element is altered. - - Additional information: - This corresponds in eForms to BT-762 Change Reason Description. | -rdf:PlainLiteral [0..*] | +epo-not:ContractModificationNotice | +An announcement of the Modification Of a Contract/Concession during its term by a + Procuring Entity. |
| epo:VehicleInformation | -epo:hasCleanVehicles | -The number of all clean vehicles that have either been purchased, leased, rented, - hired-purchased or their use has been contractually committed to for the provision - of a purchased service. - - Additional Information - In the European Union, the legal requirements and scope for the provision of these - vehicles or services are covered by Directive 2009/33/EC. - - WG Approval 28/07/2020 - | -xsd:integer [0..1] | +epo-not:DesignContest-D24 | +|
| epo:QualificationCriteriaSummary | -epo:hasConditionVerificationMethod | +epo-not:DesignContest-D25 | - | rdf:PlainLiteral [0..*] | |
| epo:NonPublishedInformation | -epo:hasConfidentialityJustification | -A narrative explanation of why data is not published. - - Additional Information: - This element is generally used when the non-publication-justification code chosen - is "other". - - WG Approval 09/11/2021 - | -rdf:PlainLiteral [0..1] | +epo-not:DesignContestNotice | +|
| cpov:ContactPoint | -epo:hasContactName | -A short text by which a contact is known or referred to. - - WG Approval: 27/01/2022 | -rdf:PlainLiteral [0..1] | +epo-not:DesignContestResult-D24 | +|
| epo:Contract | -epo:hasContractConclusionDate | -The date the contract was signed by the last signatory party. - - <u>Additional Information:</u> - In exceptional cases contracts may be concluded without signature and therefore another - date may be used. The date of contract conclusion is always later than the end of - any standstill period. - This concept is not to be confused with the date of completion/end of the contract. - - This corresponds in eForms to BT-145 Contract Conclusion Date. - - WG Approval 09/01/2020 | -xsd:date [0..1] | +epo-not:DesignContestResult-D25 | +|
| epo:ProcedureTerm | -epo:hasCrossBorderLaw | -The applicable law when buyers from different countries procure together within one - procurement procedure. - - Additional Information: - This corresponds in eForms to BT-09 Cross Border Law. | -rdf:PlainLiteral [0..*] | +epo-not:DesignContestResultNotice | +|
| epo:MonetaryValue | -epo:hasCurrencyCodeListAgencyID | -Identifier of the agency that maintains the currency code list used. - WG approval 13/04/2021 | -rdf:PlainLiteral [0..*] | +epo-not:DirectAwardPrenotificationNotice | +Notice which sets out the Buyer's purchasing intention to award a Contract without + prior notification of Competition. |
| epo:MonetaryValue | -epo:hasCurrencyCodeListAgencyName | -Name of the agency that maintains the currency code list used. - WG approval 13/04/2021 | -rdf:PlainLiteral [0..*] | +epo-not:eFormsNotice | +|
| epo:MonetaryValue | -epo:hasCurrencyCodeListID | -Concept scheme URI used for the currency code list. - WG approval 13/04/2021 | -rdf:PlainLiteral [0..*] | +epo-not:Modification-D23 | +|
| epo:SecurityClearanceTerm | -epo:hasDeadline | -The deadline by which the security clearance must be submitted to the buyer. - - WG Approval 12/09/2019 - - | -xsd:dateTime [0..1] | +epo-not:Modification-D24 | +|
| epo:ReviewDecision | -epo:hasDecisionDate | -The date of the review decision. - - Additional information: - This attribute corresponds to the BT-787 Review Date in eForms. - | -xsd:date [0..1] | +epo-not:Modification-D25 | +|
| epo:DesignContestRegimeTerm | -epo:hasDescriptionOfPrizes | +epo-not:Notice1 | - | rdf:PlainLiteral [0..1] | |
| epo:Document | -epo:hasDispatchDate | -Date and time of transmission of a record to an Organization. - - WG Approval 31/08/2023 | -xsd:dateTime [0..1] | +epo-not:Notice10 | +|
| epo:FrameworkAgreementTerm | -epo:hasDurationExtensionJustification | -The explanation of the reason why the framework agreement has an extended duration. - - Additional Information: - This corresponds in eForms to BT-109 Framework Duration Justification. - The justification for exceptional cases when the duration of the framework agreement - exceeds the legal limits. - - Four years in the case of the general procurement Directive, seven years in the case - of the defence Directive, and eight years in the case of the sectoral Directive. - - WG Approval 26/09/2019 | -rdf:PlainLiteral [0..1] | +epo-not:Notice11 | +|
| epo:SubmissionTerm | -epo:hasEAuctionURL | -The internet address of the electronic auction. - - Additional Information: - - This corresponds in eForms to BT-123 Electronic Auction URL. | -xsd:anyURI [0..1] | +epo-not:Notice12 | +|
| epo:SubmissionStatisticalInformation | -epo:hasEEAReceivedTenders | -The amount of tenders received from economic operators in other EEA countries other - than the country of the buyer. - - WG Approval 12/12/2019 | -xsd:integer [0..1] | +epo-not:Notice13 | +|
| epo:Notice | -epo:hasEFormsSubtype | +epo-not:Notice14 | - | xsd:integer [0..1] | |
| epo:ContractTerm | -epo:hasEInvoicing | -Electronic means will be used for invoicing in the post-award process. - - Additional Information: - This attribute is used for standard form mappings. - - WG Approval 12/09/2019 - | -xsd:boolean [0..1] | +epo-not:Notice15 | +|
| epo:Tender | -epo:hasElectronicSubmission | -Transmission of tenders is possible by electronic means of communication. | -xsd:boolean [0..1] | +epo-not:Notice16 | +|
| epo:SubmissionStatisticalInformation | -epo:hasElectronicTenders | -Electronic Tender Lots received. - - WG Approval 28/07/2020 - | -xsd:integer [0..1] | +epo-not:Notice17 | +|
| epo:ReviewObject | -epo:hasElementReference | -Reference to the class instance in the current notice. - - Additional information: - This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier, - BT-786 Review Notice Section Identifier and BT-1501 Modification Previous - Notice Section Identifier. | -xsd:anyURI [0..*] | +epo-not:Notice18 | +|
| epo:Period | -epo:hasEnd | -The date and time at which this period ends. | -xsd:dateTime [0..1] | +epo-not:Notice19 | +|
| epo:Contract | -epo:hasEntryIntoForceDate | -The date on which the contract enters into force. - - Additional information: - - This is generally the date on which the fulfillment of the contract begins. - - This corresponds in eForms to - - WG approval 05/11/2019 | -xsd:date [0..1] | +epo-not:Notice2 | +|
| epo:ContractTerm | -epo:hasEOrdering | -Electronic means will be used for requesting and purchasing in the post-award process. - - WG Approval 12/09/2019 - - | -xsd:boolean [0..1] | +epo-not:Notice20 | +|
| epo:ContractTerm | -epo:hasEPayment | -Electronic means must be used for paying. - WG Approval 09/11/2021 - | -xsd:boolean [0..1] | +epo-not:Notice21 | +|
| epo:Notice | -epo:hasESenderDispatchDate | -The date and time the notice was transmitted electronically by the eSender to the - Publications Office of the European Union. - - Additional Information: - Typically, eSenders include national Official Journals, Buyers sending a large number - of electronic Notices, public or private bodies acting on behalf of Buyers and eProcurement - software developers. - - WG approval 20/06/2023 | -xsd:dateTime [0..1] | +epo-not:Notice22 | +|
| epo:ProcessPlanningTerm | -epo:hasEstimatedContractNoticePublicationDate | -Foreseen date for publication of Contract Notice. - - Additional information: - This corresponds in eForms BT-127 Future Notice. - - | -xsd:date [0..1] | +epo-not:Notice23 | +|
| epo:MultipleStageProcedureTerm | -epo:hasEstimatedInvitationToExpressInterestDate | -The estimated date of dispatch of the invitations to confirm interest. - - Additional Information: - This corresponds in eForms to BT-631 Dispatch Invitation Interest. | -xsd:date [0..1] | +epo-not:Notice24 | +|
| epo:MultipleStageProcedureTerm | -epo:hasEstimatedInvitationToTenderDate | -The estimated date of dispatch of the invitations to submit tenders in two (or more) - stage procedures. - - Additional Information: - This corresponds in eForms to BT-130 Dispatch Invitation Tender. - - WG Approval 01/10/2019 | -xsd:date [0..1] | +epo-not:Notice25 | +|
| epo:SubcontractingEstimate | -epo:hasEstimatedPercentage | -The estimated proportion foreseen to be subcontracted. - - WG Approval 07/01/2020 | -xsd:decimal [0..1] | +epo-not:Notice26 | +|
| epo:ProcessPlanningTerm | -epo:hasEstimatedTenderInvitationDate | -The planned date for the dispatch of the invitations to submit tenders. - WG Approval 09/11/2021 | -xsd:date [0..1] | +epo-not:Notice27 | +|
| epo:SubmissionStatisticalInformation | -epo:hasEstimatedTotalSubcontracts | -The estimated amount of work to be subcontracted in the contract resulting from the - lot. - WG Approval 09/11/2021 | -xsd:integer [0..1] | +epo-not:Notice28 | +|
| epo:SubmissionStatisticalInformation | -epo:hasEUReceivedTenders | -The amount of tenders received from economic operators in other EU countries other - than the country of the buyer. | -xsd:integer [0..1] | +epo-not:Notice29 | +|
| cpov:ContactPoint | -epo:hasFax | -The fax number used to reach a person or an organisation. | -rdf:PlainLiteral [0..*] | +epo-not:Notice3 | +|
| epo:AwardCriterion | -epo:hasFixedValue | -This corresponds in the eForms to BT-541 Award Criterion Number in association with - BT-5422 Award Criterion Number Fixed. | -xsd:decimal [0..1] | +epo-not:Notice30 | +|
| epo:DesignContestRegimeTerm | -epo:hasFollowupContract | -Any subsequent service contract will be awarded to the winner or, in the case of a - design contest, winners. - - WG Approval 29/08/2019 | -xsd:boolean [0..1] | +epo-not:Notice31 | +|
| epo:DesignContestRegimeTerm | -epo:hasFollowupContractInformation | -Further information about follow-up contracts, prizes and payments (for example non-monetary - prizes, payments given for participation). - - WG Approval 03/09/2019 | -rdf:PlainLiteral [0..*] | +epo-not:Notice32 | +|
| epo:Notice | -epo:hasFormNumber | +epo-not:Notice33 | - | rdf:PlainLiteral [0..1] | |
| epo:ProcurementCriterion | -epo:hasFormula | -The mathematical equation or any other description used for complicated weighing of - criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing - cannot be expressed per criterion. - - Additional Information: - This corresponds in eForms to BT-543. | -rdf:PlainLiteral [0..1] | +epo-not:Notice34 | +|
| epo:ProcedureTerm | -epo:hasGroupLotEvaluationMethod | -Description of how lots and groups of lots are evaluated against one another in the - procedure. - - - - | -rdf:PlainLiteral [0..*] | +epo-not:Notice35 | +|
| epo:OrganisationGroup | -epo:hasGroupType | -Form of collaboration agreement between organisations. - - Additional Information: - This is not a legal type; not to be mistaken with epo:hasLegalFormType which may also - be used for Organisation Groups. - - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo-not:Notice36 | +|
| epo:SubmissionTerm | -epo:hasGuaranteeDescription | -Information on the financial commitment required from the economic operator. - - Additional Information: - 1. This information may include the amount and the way of delivering of the guarantee - 2. The financial commitment may be retained by the buyer in the case the tenderer - withdraws the submitted information (i.e. tender, expression of interest and request - for participation, but not request for clarifications) before the award of the contract - or does not sign the contract. - 3. Usual modalities are bonds, cheques, loans, other. - - WG Approval 21/07/20 - | -rdf:PlainLiteral [0..*] | +epo-not:Notice37 | +|
| epo:SubmissionStatisticalInformation | -epo:hasInadmissibleTenders | -Tenders received that cannot be awarded due to non-compliance to procurement document - requirements or having an abnormally low price or cost. - - <u>Additional Information: </u> - Non-compliance with a Procurement Document requirements include exclusion grounds, - selection criteria and submission deadline, etc. - - WG Approval 12/12/2019 | -xsd:integer [0..1] | +epo-not:Notice38 | +|
| cpov:ContactPoint org:Organization |
- epo:hasInternetAddress | -The main web page used by the instance of the concept. - - WG Approval 01/06/2023 - - The main web page used by the instance of the concept. - - WG Approval 01/06/2023 - | -xsd:anyURI [0..1] xsd:anyURI [0..*] |
+ epo-not:Notice39 | +|
| epo:DirectAwardTerm | -epo:hasJustification | -An explanation about the reasons for using the concept. - WG Approval 5/11/2019 - | -rdf:PlainLiteral [0..*] | +epo-not:Notice4 | +|
| epo:SubmissionTerm | -epo:hasLateSubmissionInformationDescription | -A narrative text explaining the content of the economic operator information that - can be submitted late. - - Additional Information - This does not apply to requests for clarifications. - | -rdf:PlainLiteral [0..*] | +epo-not:Notice40 | +|
| epo:ProcurementObject | -epo:hasLegalBasisDescription | +epo-not:Notice5 | - | rdf:PlainLiteral [0..*] | |
| epo:ContractTerm | -epo:hasLegalFormRequirement | -The legal form to be taken by a Contractor. - - Additional Information: - Generally, this is defined to cover the case where an Organisation Group is involved. - Note that the codelist provided at national level should be used. | -rdf:PlainLiteral [0..1] | +epo-not:Notice6 | +|
| org:Organization | -epo:hasLegalFormType | -The classification of an Organisation according to legislation. - - Additional Information: - Generally, this is defined for Tenderers who want to submit as an Organisation Group. - Note that the codelist provided at national level should be used. - | -rdf:PlainLiteral [0..1] | +epo-not:Notice7 | +|
| org:Organization | -epo:hasLegalName | -The officially registered name of an organisation. - - WG Approval 10/01/2023 | -rdf:PlainLiteral [0..*] | +epo-not:Notice8 | +|
| epo:ProcedureTerm | -epo:hasLotAwardCombination | -The contracting authority reserves the right to award contracts combining lots or - groups of lots. - - Additional Information: - This property contains information about the Lots concerned. - This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard - Forms). - - WG approval 23/08/2022 + | epo-not:Notice9 | ++ | |
| epo-not:PIN-CFCSocial-D25 | ++ | ||||
| epo-not:PIN-CFCSocialNotice | ++ | ||||
| epo-not:PIN-CFCSocialNotice-D25 | +Additional information: + Social and other specific services – utilities | -rdf:PlainLiteral [0..1] | |||
| org:Organization | -epo:hasMainActivityDescription | -Self-explanatory text about the Main Activity . - - Additional information: - This field is used when the Main Activity is not available in the controlled list - at-voc:main-activity-type . This is necessary in to cover data provided in the TED - Standard Forms. It shall be deprecated in the future. - - WG Approval 06/09/2022 + | epo-not:PIN-CFCStandard-D24 | ++ | |
| epo-not:PIN-CFCStandardNotice | ++ | ||||
| epo-not:PINDefence-D81 | ++ | ||||
| epo-not:PINOnly-D24 | ++ | ||||
| epo-not:PINOnly-D25 | ++ | ||||
| epo-not:PINOnlyNotice | +PriorInformationNotice | +||||
| epo-not:PINProfile-D24 | ++ | ||||
| epo-not:PINProfile-D25 | ++ | ||||
| epo-not:PINProfile-D81 | ++ | ||||
| epo-not:PINProfileNotice | ++ | ||||
| epo-not:PIN-RTL-D24 | ++ | ||||
| epo-not:PIN-RTL-D25 | ++ | ||||
| epo-not:PINTimeLimitNotice | ++ | ||||
| epo-not:PlanningNotice | +Notice which sets out the Contracting Authority's purchasing intentions. It is used + by Contracting Authorities to provide Suppliers with information about a Procurement + Process. | -rdf:PlainLiteral [0..1] | |||
| epo:Procedure | -epo:hasMainFeature | -Main features of the procedure and information about where the full rules for the - procedure can be found. + | epo-not:PreMarketConsultationNotice | ++ | |
| epo-not:QS-D25 | ++ | ||||
| epo-not:QSNotice | ++ | ||||
| epo-not:QSNotice-D25 | +Additional information: + Social and other specific services – utilities + | +||||
| epo-not:ResultNotice | +An announcement of the award or non-award of a Contract by a Buyer. - Additional Information: - This information should be given when the procedure is not one of those mentioned - in the procurement directives. This can be the case for example for concessions, for - social and other specific services, and in case of voluntary publication of procurement - procedures below the EU procurement thresholds. | -rdf:PlainLiteral [0..*] | + (WG approval 27/03/2019)|||
| epo:ProcedureTerm | -epo:hasMaximumLotSubmissionAllowed | -The total number of lots for which one Tenderer can submit Tenders. + | epo-not:SocialAndOtherSpecificServices-D23 | ++ | |
| epo-not:SocialAndOtherSpecificServices-D24 | +public contracts | +||||
| epo-not:StandardFormsNotice | ++ | ||||
| epo-not:Subcontract-D81 | ++ | ||||
| epo-not:SubcontractNotice | ++ | ||||
| epo-not:VEAT-D23 | ++ | ||||
| epo-not:VEAT-D24 | ++ | ||||
| epo-not:VEAT-D25 | ++ | ||||
| epo-not:VEAT-D81 | ++ | ||||
| epo-not:VoluntaryEx-AnteTransparencyNotice | +A Notice informing of the intention to award a Contract without prior publication + of a Contract Notice. - Additional information: - This field is used to complement the SubmissionTerms (which are at the Lot level) - for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled - in the TED Standard Forms). + Additional Information: - WG approval 12/12/2018 + For European Notices above the threshold + + "A means of advertising the intention to award the Contract without opening it up + to formal Competition. A Contracting Authority may decide that a Contract does not + require prior publication through a Contract Notice in the O.J.E.U. A reason for this + decision may be that the Contract meets the exceptional conditions described in Article + 31 of Directive 2004/18/EC. In a recent V.E.A.T notice the reason was listed as “extreme + urgency brought about by events unforeseeable by the Contracting Entity and in accordance + with the strict conditions stated in the Directive” . + "Voluntary Ex-Ante Transparency Notice" (VEAT) where a Contracting Authority deems + that a Contract does not require prior publication of a Contract Notice in the European + Journal (OJEU). This may apply, for example, if the Contract meets the exceptional + conditions justifying direct award of contracts. + <b>This definition is still to be worked on.</b> | -xsd:integer [0..1] | |||
| epo:MultipleStageProcedureTerm | -epo:hasMaximumNumberOfCandidates | -Maximum number of candidates to be invited for the second stage of the procedure. + | epo-ord:AllowanceChargeInformation | +Information about discounts, taxes, duties and fees imposed. - WG Approval 22/08/2019 | -xsd:integer [0..1] | + WG approval 16/05/2023
| epo:ProcedureTerm | -epo:hasMaximumNumberOfLotsToBeAwarded | -The maximum number of lots for which contract(s) can be awarded to one tenderer. - - Additional information: - This field is used to complement the SubmissionTerms (which are at the Lot level) - for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled - in the TED Standard Forms). + | epo-ord:AllowanceInformation | +Information about the discounts imposed. - WG Approval 22/08/2019 | -xsd:integer [0..1] | + WG approval 16/05/2023 +
| epo:ContractTerm | -epo:hasMaximumNumberOfRenewals | -The maximum number of times the contract can be renewed. + | epo-ord:Consignee | +A Role of an Agent that receives the Shipment of the Procurement (service, goods or + works) and who is taking possession. - Additional Information + Additional information: + The Role is carried out by the Customer or on behalf of the Customer. + The possession of the goods does not necessary imply ownership. + The Consignee may be the end-user or the beneficiary. - By renewing, the buyer reserves the right (i.e. not an obligation) to renew the contract - (i.e. extend its duration) without a new procurement procedure. - For example, a contract may be valid for one year and the buyer may keep a possibility - to renew it (e.g. once, twice) for another three months, if he is content with the - services he received. + (Consignee) Definition from PEPPOL Despatch: + The Consignee is the person or Organisation to which the products will be shipped + and who is taking possession. The Role is carried out by the Customer or on behalf + of the Customer. - PLEASE REVIEW THIS DEFINITION AGAIN WITH THE WORKING GROUP. It was originally taken - from eForms. + WG approval: 21/02/2023 | -xsd:integer [0..1] |
| epo:FrameworkAgreementTerm | -epo:hasMaximumParticipantsNumber | -The maximum number of participants in the framework agreement. + | epo-ord:ContractInformation | +Information about the Contract. - Additional Information: - Maximum number of tenderers who may be awarded a contract within the framework agreement. + WG approval 20/04/2023 | +|
| epo-ord:DeliveryAgreement | +Term applying to the delivery of goods, services and works. - The number is a positive integer. + Additional Information: + Delivery terms identifier can normally be Incoterms accompanied by the description + of specific conditions related to the delivery. - This corresponds in eForms to BT-113 Framework Maximum Participants Number. + WG approval 16/05/2023 | +||||
| epo-ord:DeliveryInformation | +Information about the timing, the delivery destination, the delivery agreement and + the involved parties. - WG Approval 2019-02-05 | -xsd:integer [0..1] | + WG approval 16/05/2023 +|||
| epo:SubcontractTerm | -epo:hasMaximumShare | -The maximum proportion of something to be distributed. + | epo-ord:Order | +A formal request of the Buyer to the Seller specifying the goods, services or works + to be delivered. Additional Information: - In the case of subcontracting the share may refer to the proportion of works, services - or supplies being subcontracted. + A Buyer submits an Order for delivery of goods, services or works to a Seller. - WG Approval 17/09/2019 + WG approval 23/04/2023 | -xsd:decimal [0..1] |
| epo:SubmissionStatisticalInformation | -epo:hasMediumTenderPerLots | -Tenders from medium-sized enterprise. + | epo-ord:OrderLine | +Details concerning a given unit of goods, services or works requested in the Order. - <u>Additional Information:</u> + Additional information: + In general, an Order Line contains the Quantity and Price of the goods, services and + goods requested in the Order. + However, in certain cases, the Price may not be known, as the Price may fluctuate + from one day to the other. - See Commission Recommendation 2003/361/EC. - | -xsd:integer [0..1] | + WG approval 20/04/2023
| epo:MultipleStageProcedureTerm | -epo:hasMinimumNumberOfCandidates | -Minimum number of candidates to be invited for the second stage of the procedure. + | epo-ord:OrderResponse | +A formal reply from the Seller to the Buyer stating the Seller's ability to fulfil + the order. - WG Approval 22/08/2019 | -xsd:integer [0..1] | + Additional Information: + The Order Response is used to inform on the acceptance or rejection of an Order or + to make a counter-offer. + + WG approval 20/04/2023 +
| epo:SubcontractTerm | -epo:hasMinimumShare | -The minimum proportion of something to be distributed. + | epo-ord:OrderResponseInformation | ++ | |
| epo-ord:OrderResponseLine | +Details concerning the Seller's ability to fulfil a given Order Line. Additional Information: - In the case of subcontracting the share may refer to the proportion of works, services - or supplies being subcontracted. + The Order Response Line is used to inform on the acceptance or rejection of an Order + Line or to make a counter-offer. - WG Approval 17/09/2019 | -xsd:decimal [0..1] | + WG approval 20/04/2023|||
| epo:SubcontractTerm | -epo:hasMinimumSubcontractorsProposedObligation | -The minimum percentage of the contract value that the contractor must subcontract. + | epo-ord:Originator | +A Role of an Agent that expresses the needs to trigger the Procurement. - Additional information: - This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + Additional Information: + The Originator is often the end-user or the Beneficiary. + WG approval: 20/10/2022 - WG Approval 09/11/2021 | -xsd:decimal [0..1] | +
| epo:ProcedureTerm | -epo:hasNationalProcedureRules | -- | xsd:anyURI [0..*] | +epo-ord:OriginatorInformation | +Information about the Originator of the Order. + + WG approval 20/03/2023 |
| epo:StrategicProcurement | -epo:hasNonAccessibilityCriterionJustification | -Reason for not applying accessibility criteria. + | epo-ord:Seller | +A Role of an Agent who transfers the ownership of the Procurement results (goods, + services or works) to the Buyer. Additional information: - This corresponds in eForma to BT-755 Accessibility Justification. + A Role of an Agent that sells a Procurement Result (goods, services or work) to a + Buyer. + The Seller is bound by a Contract i.e. it has legal responsibility. + The Seller may or may not be the same as the Supplier. + The Seller may or may not issue the Invoice. + The Seller may or may not be the owner of the credit owed by the Buyer. - WG Approval 05/03/2019 | -rdf:PlainLiteral [0..*] | + WG acceptance 08/09/2022
| epo:LotAwardOutcome | -epo:hasNonAwardedContractNumber | -The number the contract would have had if it had been awarded. - - Additional information: - - This field is provided to support the data provided in the TED Standard Forms, and - it should be discontinued in the future. + | epo-ord:TaxInformation | +Information about the imposition of mandatory levies required by law. - WG agreement: 06/09/2022 + WG approval 25/04/2023 | -rdf:PlainLiteral [0..1] |
| epo:LotAwardOutcome | -epo:hasNonAwardedContractTitle | -The title the contract would have had if it had been awarded. + | epo-sub:CertificateInformation | +Information about a Certificate. - Additional information: + WG approval 12/03/2024 | +|
| epo-sub:ESPDResponse | +A document conveying the fulfilment or not by the economic operator of the Exclusion + Grounds and the Selection Criteria set out by the Buyer for a specific Procurement + using an European Single Procurement Document (ESPD) Request. - This field is provided to support the data provided in the TED Standard Forms, and - it should be discontinued in the future. + WG Approval 05/03/2024 | +||||
| epo-sub:LegalRepresentative | +The Role of an Agent that can represent an Organization. - WG agreement: 06/09/2022 | -rdf:PlainLiteral [0..1] | + WG approval 05/03/2024|||
| epo:SubmissionStatisticalInformation | -epo:hasNonEEAReceivedTenders | -The amount of tenders received from economic operators in non-EEA countries. + | epo-sub:Mandate | +An authorization to act as a representative of an Organization. - WG Approval 12/12/2019 15:20:36 | -xsd:integer [0..1] | + WG approval 05/03/2024
| epo:MultipleStageProcedureTerm | -epo:hasNoNegotiationNecessary | -The buyer reserves the right to award the contract on the basis of the initial tenders - without any further negotiations. + | epo-sub:NationalPreQualificationData | +Data that describe the distinctive features or characteristics that qualify an economic + operator to take part in a tendering process. - Additional information: - See Article 29(4) of Directive 2014/24/EU. - | -xsd:boolean [0..1] | + WG approval 05/03/2024
| epo:SubmissionTerm | -epo:hasNonElectronicSubmissionDescription | -Textual explanation of how non-electronic information is to be presented. + | epo-sub:PowerOfAttorney | +A legal document that grants someone the authority to make decisions on behalf of + an Organization. - WG Approval 21/07/2020 - - | -rdf:PlainLiteral [0..*] | + WG approval 05/03/2024
| epo:SubmissionStatisticalInformation | -epo:hasNonEUReceivedTenders | -The amount of tenders received from economic operators in non-EU countries. - | -xsd:integer [0..1] | +epo-sub:Response | +An answer given to a question that is part of an ESPD Request. + + WG approval 12/03/2024 |
| epo:Notice | -epo:hasNoticePublicationNumber | -- | rdf:PlainLiteral [0..1] | +foaf:Agent | +A Person, an Organisation, or a System that acts in Procurement or have the power + to act in Procurement. + + WG Approval 28/04/2020 |
| epo:ReviewRequest | -epo:hasNumberOfReviewRequests | -The number of requests the buyer received to review any of its decisions. | -xsd:integer [1..1] | +foaf:Person | +The Person class represents people. Something is a Person if it is a Person. We don't + nitpick about whether they're alive, dead, real, or imaginary. The Person class is + a sub-class of the Agent class, since all people are considered 'Agents' in FOAF. |
| epo:SubmissionStatisticalInformation | -epo:hasNumberOfTenderersInvited | -Number of economic operators invited to tender. + | locn:Address | +The particulars of the place where a Person or an Organisation is located. - Additional Information - This may be used for single-stage procedures or to indicate the number of candidates - invited to tender in multi-stage procedures. + WG Approval 28/04/2020 - WG Approval 01/12/2020 + Additional Information: + An "Address Representation" as conceptually defined by the INSPIRE Address Representation + data type: "Representation of an address spatial object for use in external application + schemas that need to include the basic, address information in a readable way.". - | -xsd:integer [0..1] | -
| epo:Notice | -epo:hasOJSIssueNumber | -- | xsd:integer [0..1] | + + The representation of Addresses varies widely from one country's postal System to + another. Even within countries, there are almost always examples of Addresses that + do not conform to the stated national standard. At the time of publication, work is + progressing on ISO 19160-1 that defines a method through which different Addresses + can be converted from one conceptual model to another. + + + This specification was heavily based on the INSPIRE Address Representation data type. + It is noteworthy that if an Address is provided using the detailed breakdown suggested + by the properties for this class, then it will be INSPIRE-conformant. To this very + granular set of properties, we add two further properties: + + - full address (the complete address as a formatted string) + - addressID (a unique identifier for the address) + The first of these allows publishers to simply provide the complete Address as one + string, with or without formatting. This is analogous to vCard's label property. + + The addressID is part of the INSPIRE guidelines and provides a hook that can be used + to link the Address to an alternative representation, such as vCard or OASIS xAL.||
| epo:Notice | -epo:hasOJSType | -- | rdf:PlainLiteral [0..1] | +locn:Geometry | +The Geometry class provides the means to identify a Location as a point, line, polygon, + etc. expressed using coordinates in some coordinate reference System. + + Additional Information: + This class defines the notion of "Geometry" at the conceptual level, and it shall + be encoded by using different formats (see usage note of the locn:geometry property). + We also refer to the Examples section of this specification for a number of different + Geometry examples expressed in different formats. |
| epo:OpeningTerm | -epo:hasOpeningDateTime | -Date and time for the opening of tenders. - - WG Approval 12/03/2019 + | org:Organization | +A collection of people organized together into a community or other social, commercial + or political structure. The group has some common purpose or reason for existence + which goes beyond the set of people belonging to it and can act as an Agent. Organisations + are often decomposable into hierarchical structures. + (WG approval 23/11/2018). | -xsd:dateTime [1..1] |
| epo:OpeningTerm | -epo:hasOpeningDescription | -Further information about the opening of tenders. - - Additional Information - For example, who may participate in the opening and whether any authorization is needed. - - WG Approval 12/03/2019 | -rdf:PlainLiteral [0..*] | +person:Person | +A individual human being who may be dead or alive, but not imaginary. + |
| epo:OpeningTerm | -epo:hasOpeningURL | -The identifier of the address of the Opening of Tenders. - WG Approval 09/11/2021 | -xsd:anyURI [0..1] | +time:Duration | +Duration of a temporal extent expressed as a number scaled by a temporal unit. |
| epo:ContractTerm | -epo:hasOptions | -The buyer reserves the right (not an obligation) for additional purchases from the - contractor (while the contract is valid). | -xsd:boolean [0..1] | +Class name | +Attribute name | +Definition | +Data type / cardinality |
|---|---|---|---|---|---|---|---|
| epo:ContractTerm | -epo:hasOptionsDescription | -The motivation and details about additional purchases that the buyer may undertake - while the contract is valid. - - WG Approval 09/04/2019 | +adms:Identifier | +adms:schemaAgency | +The name of the agency that issued the identifier. | rdf:PlainLiteral [0..*] | |
| epo:SubmissionStatisticalInformation | -epo:hasOtherCountriesReceivedTenders | -- | xsd:integer [0..1] | -||||
| epo:AwardEvaluationTerm | -epo:hasOverallCostAwardCriteriaPonderation | -The weighting given to cost. + | cccev:Criterion | +cccev:bias | +Parameter used to adjust the evaluation of the Criterion. Additional Information: - This weighting covers usually all cost criteria against price or quality criteria. | + The bias parameter tries to correct a systematic error. For example in procurement, + a home bias corresponds to the "presence of local preferences distorting international + specialisation and resource allocation". When quantified, this systematic error can + be removed.xsd:decimal [0..1] | |
| epo:AwardEvaluationTerm | -epo:hasOverallPriceAwardCriteriaPonderation | -The weighting given to price. - - Additional Information: - This weighting covers usually all price criteria against cost or quality criteria. | -xsd:decimal [0..1] | +cccev:SupportedValue | +cccev:value | +Value for the Information Concept that the Evidence supports. | +rdf:PlainLiteral [0..*] |
| epo:AwardEvaluationTerm | -epo:hasOverallQualityAwardCriteriaPonderation | -The weighting given to quality. + | cccev:Criterion | +cccev:weight | +Relative importance of the Criterion. Additional Information: - This weighting covers usually all quality criteria against price or cost criteria. | + The weight must be between 0 and 1. Usually, all Criteria can be integrated within + a weighted sum equal to 1.xsd:decimal [0..1] | |
| epo:DesignContestRegimeTerm | -epo:hasParticipationPayment | -Details on payments to participants - WG Approval 09/11/2021 | +cccev:Criterion | +cccev:weightingConsiderationDescription | +Explanation of how the weighting of a Criterion is to be used. + + Additional Information: + This description gives the view of the creator of the Criterion weights on how to + interpret and use them during the evaluation process. | rdf:PlainLiteral [0..1] | |
| epo:ContractTerm | -epo:hasPaymentArrangement | -Information about financial clauses that will govern some economic aspects of the - execution of the contract. - - Additional Information: These clauses usually refer to financial and payment provisions. - - This type of information should be structured instead of a free text in order to reuse - it an ideal world. Unfortunately this is an information that in the real life no one - is willing to provide pro-actively. + | cpov:ContactPoint | +cpov:email | +The email of the Organisation. - WG Pending of discussion with eForms | +rdf:PlainLiteral [0..*] | |
| epo:ContractLotCompletionInformation | -epo:hasPaymentValueDiscrepancyJustification | -- | rdf:PlainLiteral [0..1] | +cpov:ContactPoint | +cpov:telephone | +A telephone number through which the Contact Point can be contacted. + | +rdf:PlainLiteral [0..*] |
| epo:ContractTerm | -epo:hasPerformanceConditions | -The particular conditions and additional information related to the execution of the - contract. - - Additional Information: - - For example, specific information about the place of performance, intermediary deliverables, - compensation for damages, intellectual property rights. - - WG approval 15-01-2019 | +person:Person | +cv:birthDate | +The point in time on which the Person was born. | +xsd:date [0..1] | +|
| locn:Geometry | +cv:coordinates | +The coordinate list. | rdf:PlainLiteral [0..*] | ||||
| epo:ContractTerm | -epo:hasPlaceOfPerformanceAdditionalInformation | -Further details on the location of the execution of the contract. - - WG Approval 30/07/2019 | +locn:Geometry | +cv:latitude | +The latitude. | rdf:PlainLiteral [0..*] | |
| epo:Prize | -epo:hasPrizeRank | -The position of the prize (e.g. first place, second place) in a design contest list - of prizes. + | locn:Geometry | +cv:longitude | +The longitude. | +rdf:PlainLiteral [0..*] | +|
| person:Person | +dct:alternative | +Any name by which an individual is known other than their full name. + WG 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| cccev:Evidence cccev:InformationConcept cccev:Requirement cpov:ContactPoint cv:Channel epo:AgentInRole epo:Document epo:ElectronicSignature epo:Fund epo:NonDisclosureAgreementTerm epo:SecurityClearanceTerm epo:SubcontractingEstimate epo:SubcontractTerm epo:System epo:Technique epo:LotGroup epo:ProcurementElement epo:TenderGroup epo-cat:Line epo-cat:Item epo-ord:DeliveryAgreement epo-ord:TaxInformation epo-ful:ShipmentInformation epo-ful:TemperatureSpecification epo-ful:TransportEquipment cccev:EvidenceTypeList eli:LegalExpression eli:LegalResource epo-sub:CertificateInformation |
+ dct:description | +An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + | +rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [1..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [1..1] rdfs:Literal [0..*] rdfs:Literal [1..1] rdf:PlainLiteral [0..1] |
+ ||||
| eli:LegalExpression eli:LegalResource |
+ dct:identifier | +An unambiguous reference to the resource within a given context. + An unambiguous reference to the resource within a given context. + | +xsd:anyURI [0..*] xsd:anyURI [0..*] |
+ ||||
| epo:Document | +dct:issued | +Date of formal issuance of the resource. + + Additional information: + This is generally used for modules other than eNotice. + The xsd:dateTime here means that we can provide either xsd:date, xsd:dateTime, or + xsd:timeStamp or any other variant of time expression. This extension needs to be + encoded/automated in the ontology and in the application profile. + Why is it like this? Because UML cannot handle such expressions of disjunctive property + ranges. + + WG approval 26/01/2023 | +xsd:dateTime [0..1] | +||||
| epo:AgentInRole epo:Document epo:Fund foaf:Agent epo:LotGroup epo:ProcurementElement epo:TenderGroup epo-cat:Brand epo-cat:ItemModel epo-cat:Item eli:LegalExpression |
+ dct:title | +A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 + + A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. | +rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [1..1] rdf:PlainLiteral [1..1] rdf:PlainLiteral [1..1] rdfs:Literal [1..*] |
+ ||||
| eli:LegalExpression eli:LegalResource |
+ eli:number | +An identifier or other disambiguating feature for a legal resource or legal expression. + This can be the number of a legislation, the number of an article, or the issue number + of an official journal. An identifier or other disambiguating feature for a legal resource or legal expression. + This can be the number of a legislation, the number of an article, or the issue number + of an official journal. | +xsd:string [0..*] xsd:string [0..*] |
+ ||||
| epo:SelectionCriteriaSummary | +epo:describesMinimumLevelOfStandards | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ParticipationConditionsSummary | +epo:describesObjectiveParticipationRules | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ProfessionalSuitabilitySummary | +epo:describesProfession | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ProfessionalSuitabilitySummary | +epo:describesProfessionRelevantLaw | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ParticipationConditionsSummary | +epo:describesVerificationMethod | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasAbnormallyLowTenders | +Tenders received that were found irregular and non-acceptable due to an abnormally + low price or cost. + + Additional Information + The definition implies that abnormally Low Tender Lots are Inadmissible Tender Lots. + + WG Approval 28/07/2020 + + | +xsd:integer [0..1] | +||||
| epo:Procedure | +epo:hasAcceleratedProcedureJustification | +The reasons why the procedure is accelerated. + + Additional Information: + A procedure is accelerated to cover needs of extraordinary circumstances ie earthquake + relief. + + WG Approval 09/06/2020 + + | +rdf:PlainLiteral [0..*] | +||||
| epo:NonPublishedInformation | +epo:hasAccessibilityDate | +The date at which unpublished data shall be published. + + WG Approval 11/06/2020 | +xsd:date [0..1] | +||||
| epo:Document | +epo:hasAccessURL | +Location where the resource can be accessed. + + WG approval 07/04/2022 | +xsd:anyURI [0..*] | +||||
| epo:Buyer | +epo:hasActivityDescription | +In the ePO ontology a taxonomy with all activities, based on different classifications + (COFOG, UTILITIES, NACE), will be provided. In ePO this field is to be used exclusively + to complement the definition attached to the MainActivityCode. + + However, in eForms there is the code "other" to cover undefined activities. For mapping + to this eForms feature one could also use this property. + | +rdf:PlainLiteral [0..*] | +||||
| epo:ChangeInformation epo:Notice epo:ProcurementCriterion epo:ProcurementObject |
+ epo:hasAdditionalInformation | +Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 + Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 | +rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] |
+ ||||
| epo:AccessTerm | +epo:hasAdditionalInformationDeadline | +The time limit for requesting further information. + + Additional information: + + This is generally used to indicate the deadline for Economic Operators to request + further information of the procedure before the submission deadline. + + This corresponds in eForms to BT-13 Additional Information Deadline. + + WG Approval 09/06/2020 + | +xsd:dateTime [0..1] | +||||
| epo:AwardDecision | +epo:hasAdditionalNonAwardJustification | +Further justification for the non award . + + Additional information: + This is generally used when the non award reason code is set to "Other". + + WG: 18/01/2022 | +rdf:PlainLiteral [0..1] | +||||
| cv:Channel | +epo:hasAddressURL | ++ | xsd:anyURI [0..1] | +||||
| foaf:Agent | +epo:hasAlias | +Acronym or alternative name of the Agent. + WG Approval 25/03/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:MonetaryValue | +epo:hasAmountValue | +The numeric value of the amount, including decimals. | +xsd:decimal [1..1] | +||||
| epo:AwardEvaluationTerm | +epo:hasAwardCriteriaEvaluationFormula | +The mathematical equation or any other description used for complicated weighing of + criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing + cannot be expressed per criterion. + + Additional Information: + This corresponds in eForms to BT-543 Award Criteria Complicated. | +rdf:PlainLiteral [0..*] | +||||
| epo:AwardEvaluationTerm | +epo:hasAwardCriteriaOrderJustification | +The justification for only indicating the award criteria's order of importance, not + their weighing. + + Additional Information: + This corresponds in eForms to BT-733 Award Criteria Order Justification. | +rdf:PlainLiteral [0..1] | +||||
| epo:AwardCriterion | +epo:hasAwardCriteriaStatedInProcurementDocuments | ++ | xsd:boolean [1..1] | +||||
| epo:ProcessPlanningTerm | +epo:hasAwardDateScheduled | +Planned date for the award decision. + WG Approval 09/11/2021 | +xsd:date [0..1] | +||||
| epo:AwardDecision | +epo:hasAwardDecisionDate | +The official date of the award decision. + + Additional Information: + This corresponds in eForms to BT-1451 Winner Decision Date. + + WG Approval 09/01/2020 + | +xsd:dateTime [0..1] | +||||
| epo:TenderAwardOutcome | +epo:hasAwardRank | +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. + + Additional Information: + This corresponds in eForms to BT-171 Tender Rank. + | +xsd:integer [0..1] | +||||
| epo:Period | +epo:hasBeginning | +The date and time on which this period begins. | +xsd:dateTime [0..1] | +||||
| epo:FrameworkAgreementTerm | +epo:hasBuyerCategoryDescription | +A classification of buyers participating in a framework agreement. + + Additional Information: + Buyers that can use the Framework Agreement not mentioned by name. + + For example, the classification "all hospitals in the Tuscany region" is used instead + of naming each individual buyer. + + This corresponds in eForms to BT-111 Framework Buyer Categories. + + WG Approval 2019-05-06 | +rdf:PlainLiteral [0..*] | +||||
| org:Organization | +epo:hasBuyerLegalTypeDescription | +Self-explanatory text about the Buyer Legal Type. + + Additional information: + This field is used when the Buyer Legal Type is not available in the controlled list + at-voc:buyer-legal-type . This is necessary in to cover data provided in the TED Standard + Forms. It shall be deprecated in the future. + + WG Approval 06/09/2022 | +rdf:PlainLiteral [0..1] | +||||
| epo:Buyer | +epo:hasBuyerProfile | +Website address where the buyer publishes information on its procurement procedures + and general information. + + Additional information: + This corresponds in the eForms to BT-508 Buyer Profile URL. + + WG approval 04/05/2018 + | +xsd:anyURI [0..1] | +||||
| epo:ConcessionEstimate | +epo:hasCalculationMethod | +Formula for obtaining values. + + Additional Information: + The possible values are monetary values, ranking scores, criterion weighting. + + WG Approval 25/05/2018 | +rdf:PlainLiteral [0..1] | +||||
| epo:Certificate | +epo:hasCertificationNumber | +The unique identifier of the certificate. + + WG approval 26/07/2022 | +rdf:PlainLiteral [0..1] | +||||
| epo:ChangeInformation | +epo:hasChangeDescription | +Explanatory text about the instance of the concept. + + WG Approval 30/09/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:ChangeInformation | +epo:hasChangeReasonDescription | +Explanatory text about why the element is altered. + + Additional information: + This corresponds in eForms to BT-762 Change Reason Description. | +rdf:PlainLiteral [0..*] | +||||
| epo:VehicleInformation | +epo:hasCleanVehicles | +The number of all clean vehicles that have either been purchased, leased, rented, + hired-purchased or their use has been contractually committed to for the provision + of a purchased service. + + Additional Information + In the European Union, the legal requirements and scope for the provision of these + vehicles or services are covered by Directive 2009/33/EC. + + WG Approval 28/07/2020 + | +xsd:integer [0..1] | +||||
| epo:QualificationCriteriaSummary | +epo:hasConditionVerificationMethod | ++ | rdf:PlainLiteral [0..*] | +||||
| epo:NonPublishedInformation | +epo:hasConfidentialityJustification | +A narrative explanation of why data is not published. + + Additional Information: + This element is generally used when the non-publication-justification code chosen + is "other". + + WG Approval 09/11/2021 + | +rdf:PlainLiteral [0..1] | +||||
| cpov:ContactPoint | +epo:hasContactName | +A short text by which a contact is known or referred to. + + WG Approval: 27/01/2022 | +rdf:PlainLiteral [0..1] | +||||
| epo:Contract | +epo:hasContractConclusionDate | +The date the contract was signed by the last signatory party. + + <u>Additional Information:</u> + In exceptional cases contracts may be concluded without signature and therefore another + date may be used. The date of contract conclusion is always later than the end of + any standstill period. + This concept is not to be confused with the date of completion/end of the contract. + + This corresponds in eForms to BT-145 Contract Conclusion Date. + + WG Approval 09/01/2020 | +xsd:date [0..1] | +||||
| epo:ProcedureTerm | +epo:hasCrossBorderLaw | +The applicable law when buyers from different countries procure together within one + procurement procedure. + + Additional Information: + This corresponds in eForms to BT-09 Cross Border Law. | +rdf:PlainLiteral [0..*] | +||||
| epo:MonetaryValue | +epo:hasCurrencyCodeListAgencyID | +Identifier of the agency that maintains the currency code list used. + WG approval 13/04/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:MonetaryValue | +epo:hasCurrencyCodeListAgencyName | +Name of the agency that maintains the currency code list used. + WG approval 13/04/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:MonetaryValue | +epo:hasCurrencyCodeListID | +Concept scheme URI used for the currency code list. + WG approval 13/04/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:SecurityClearanceTerm | +epo:hasDeadline | +The deadline by which the security clearance must be submitted to the buyer. + + WG Approval 12/09/2019 + + | +xsd:dateTime [0..1] | +||||
| epo:ReviewDecision | +epo:hasDecisionDate | +The date of the review decision. + + Additional information: + This attribute corresponds to the BT-787 Review Date in eForms. + | +xsd:date [0..1] | +||||
| epo:DesignContestRegimeTerm | +epo:hasDescriptionOfPrizes | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:Document | +epo:hasDispatchDate | +Date and time of transmission of a record to an Organization. + + WG Approval 31/08/2023 | +xsd:dateTime [0..1] | +||||
| epo:FrameworkAgreementTerm | +epo:hasDurationExtensionJustification | +The explanation of the reason why the framework agreement has an extended duration. + + Additional Information: + This corresponds in eForms to BT-109 Framework Duration Justification. + The justification for exceptional cases when the duration of the framework agreement + exceeds the legal limits. + + Four years in the case of the general procurement Directive, seven years in the case + of the defence Directive, and eight years in the case of the sectoral Directive. + + WG Approval 26/09/2019 | +rdf:PlainLiteral [0..1] | +||||
| epo:SubmissionTerm | +epo:hasEAuctionURL | +The internet address of the electronic auction. + + Additional Information: + + This corresponds in eForms to BT-123 Electronic Auction URL. | +xsd:anyURI [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasEEAReceivedTenders | +The amount of tenders received from economic operators in other EEA countries other + than the country of the buyer. + + WG Approval 12/12/2019 | +xsd:integer [0..1] | +||||
| epo:Notice | +epo:hasEFormsSubtype | ++ | xsd:integer [0..1] | +||||
| epo:ContractTerm | +epo:hasEInvoicing | +Electronic means will be used for invoicing in the post-award process. + + Additional Information: + This attribute is used for standard form mappings. + + WG Approval 12/09/2019 + | +xsd:boolean [0..1] | +||||
| epo:Tender | +epo:hasElectronicSubmission | +Transmission of tenders is possible by electronic means of communication. | +xsd:boolean [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasElectronicTenders | +Electronic Tender Lots received. + + WG Approval 28/07/2020 + | +xsd:integer [0..1] | +||||
| epo:ReviewObject | +epo:hasElementReference | +Reference to the class instance in the current notice. + + Additional information: + This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier, + BT-786 Review Notice Section Identifier and BT-1501 Modification Previous + Notice Section Identifier. | +xsd:anyURI [0..*] | +||||
| epo:Period | +epo:hasEnd | +The date and time at which this period ends. | +xsd:dateTime [0..1] | +||||
| epo:Contract | +epo:hasEntryIntoForceDate | +The date on which the contract enters into force. + + Additional information: + + This is generally the date on which the fulfillment of the contract begins. + + This corresponds in eForms to + + WG approval 05/11/2019 | +xsd:date [0..1] | +||||
| epo:ContractTerm | +epo:hasEOrdering | +Electronic means will be used for requesting and purchasing in the post-award process. + + WG Approval 12/09/2019 + + | +xsd:boolean [0..1] | +||||
| epo:ContractTerm | +epo:hasEPayment | +Electronic means must be used for paying. + WG Approval 09/11/2021 + | +xsd:boolean [0..1] | +||||
| epo:Notice | +epo:hasESenderDispatchDate | +The date and time the notice was transmitted electronically by the eSender to the + Publications Office of the European Union. + + Additional Information: + Typically, eSenders include national Official Journals, Buyers sending a large number + of electronic Notices, public or private bodies acting on behalf of Buyers and eProcurement + software developers. + + WG approval 20/06/2023 | +xsd:dateTime [0..1] | +||||
| epo:ProcessPlanningTerm | +epo:hasEstimatedContractNoticePublicationDate | +Foreseen date for publication of Contract Notice. + + Additional information: + This corresponds in eForms BT-127 Future Notice. + + | +xsd:date [0..1] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasEstimatedInvitationToExpressInterestDate | +The estimated date of dispatch of the invitations to confirm interest. + + Additional Information: + This corresponds in eForms to BT-631 Dispatch Invitation Interest. | +xsd:date [0..1] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasEstimatedInvitationToTenderDate | +The estimated date of dispatch of the invitations to submit tenders in two (or more) + stage procedures. + + Additional Information: + This corresponds in eForms to BT-130 Dispatch Invitation Tender. + + WG Approval 01/10/2019 | +xsd:date [0..1] | +||||
| epo:SubcontractingEstimate | +epo:hasEstimatedPercentage | +The estimated proportion foreseen to be subcontracted. + + WG Approval 07/01/2020 | +xsd:decimal [0..1] | +||||
| epo:ProcessPlanningTerm | +epo:hasEstimatedTenderInvitationDate | +The planned date for the dispatch of the invitations to submit tenders. + WG Approval 09/11/2021 | +xsd:date [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasEstimatedTotalSubcontracts | +The estimated amount of work to be subcontracted in the contract resulting from the + lot. + WG Approval 09/11/2021 | +xsd:integer [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasEUReceivedTenders | +The amount of tenders received from economic operators in other EU countries other + than the country of the buyer. | +xsd:integer [0..1] | +||||
| cpov:ContactPoint | +epo:hasFax | +The fax number used to reach a person or an organisation. | +rdf:PlainLiteral [0..*] | +||||
| epo:AwardCriterion | +epo:hasFixedValue | +This corresponds in the eForms to BT-541 Award Criterion Number in association with + BT-5422 Award Criterion Number Fixed. | +xsd:decimal [0..1] | +||||
| epo:DesignContestRegimeTerm | +epo:hasFollowupContract | +Any subsequent service contract will be awarded to the winner or, in the case of a + design contest, winners. + + WG Approval 29/08/2019 | +xsd:boolean [0..1] | +||||
| epo:DesignContestRegimeTerm | +epo:hasFollowupContractInformation | +Further information about follow-up contracts, prizes and payments (for example non-monetary + prizes, payments given for participation). + + WG Approval 03/09/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:Notice | +epo:hasFormNumber | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ProcurementCriterion | +epo:hasFormula | +The mathematical equation or any other description used for complicated weighing of + criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing + cannot be expressed per criterion. + + Additional Information: + This corresponds in eForms to BT-543. | +rdf:PlainLiteral [0..1] | +||||
| epo:ProcedureTerm | +epo:hasGroupLotEvaluationMethod | +Description of how lots and groups of lots are evaluated against one another in the + procedure. + + + + | +rdf:PlainLiteral [0..*] | +||||
| epo:OrganisationGroup | +epo:hasGroupType | +Form of collaboration agreement between organisations. + + Additional Information: + This is not a legal type; not to be mistaken with epo:hasLegalFormType which may also + be used for Organisation Groups. + + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionTerm | +epo:hasGuaranteeDescription | +Information on the financial commitment required from the economic operator. + + Additional Information: + 1. This information may include the amount and the way of delivering of the guarantee + 2. The financial commitment may be retained by the buyer in the case the tenderer + withdraws the submitted information (i.e. tender, expression of interest and request + for participation, but not request for clarifications) before the award of the contract + or does not sign the contract. + 3. Usual modalities are bonds, cheques, loans, other. + + WG Approval 21/07/20 + | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasInadmissibleTenders | +Tenders received that cannot be awarded due to non-compliance to procurement document + requirements or having an abnormally low price or cost. + + <u>Additional Information: </u> + Non-compliance with a Procurement Document requirements include exclusion grounds, + selection criteria and submission deadline, etc. + + WG Approval 12/12/2019 | +xsd:integer [0..1] | +||||
| cpov:ContactPoint org:Organization |
+ epo:hasInternetAddress | +The main web page used by the instance of the concept. + + WG Approval 01/06/2023 + + The main web page used by the instance of the concept. + + WG Approval 01/06/2023 + | +xsd:anyURI [0..1] xsd:anyURI [0..*] |
+ ||||
| epo:DirectAwardTerm | +epo:hasJustification | +An explanation about the reasons for using the concept. + WG Approval 5/11/2019 + | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionTerm | +epo:hasLateSubmissionInformationDescription | +A narrative text explaining the content of the economic operator information that + can be submitted late. + + Additional Information + This does not apply to requests for clarifications. + | +rdf:PlainLiteral [0..*] | +||||
| epo:ProcurementObject | +epo:hasLegalBasisDescription | ++ | rdf:PlainLiteral [0..*] | +||||
| epo:ContractTerm | +epo:hasLegalFormRequirement | +The legal form to be taken by a Contractor. + + Additional Information: + Generally, this is defined to cover the case where an Organisation Group is involved. + Note that the codelist provided at national level should be used. | +rdf:PlainLiteral [0..1] | +||||
| org:Organization | +epo:hasLegalFormType | +The classification of an Organisation according to legislation. + + Additional Information: + Generally, this is defined for Tenderers who want to submit as an Organisation Group. + Note that the codelist provided at national level should be used. + | +rdf:PlainLiteral [0..1] | +||||
| org:Organization | +epo:hasLegalName | +The officially registered name of an organisation. + + WG Approval 10/01/2023 | +rdf:PlainLiteral [0..*] | +||||
| epo:ProcedureTerm | +epo:hasLotAwardCombination | +The contracting authority reserves the right to award contracts combining lots or + groups of lots. + + Additional Information: + This property contains information about the Lots concerned. + This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard + Forms). + + WG approval 23/08/2022 + | +rdf:PlainLiteral [0..1] | +||||
| org:Organization | +epo:hasMainActivityDescription | +Self-explanatory text about the Main Activity . + + Additional information: + This field is used when the Main Activity is not available in the controlled list + at-voc:main-activity-type . This is necessary in to cover data provided in the TED + Standard Forms. It shall be deprecated in the future. + + WG Approval 06/09/2022 + | +rdf:PlainLiteral [0..1] | +||||
| epo:Procedure | +epo:hasMainFeature | +Main features of the procedure and information about where the full rules for the + procedure can be found. + + Additional Information: + This information should be given when the procedure is not one of those mentioned + in the procurement directives. This can be the case for example for concessions, for + social and other specific services, and in case of voluntary publication of procurement + procedures below the EU procurement thresholds. | +rdf:PlainLiteral [0..*] | +||||
| epo:ProcedureTerm | +epo:hasMaximumLotSubmissionAllowed | +The total number of lots for which one Tenderer can submit Tenders. + + Additional information: + This field is used to complement the SubmissionTerms (which are at the Lot level) + for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled + in the TED Standard Forms). + + WG approval 12/12/2018 + + | +xsd:integer [0..1] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasMaximumNumberOfCandidates | +Maximum number of candidates to be invited for the second stage of the procedure. + + WG Approval 22/08/2019 | +xsd:integer [0..1] | +||||
| epo:ProcedureTerm | +epo:hasMaximumNumberOfLotsToBeAwarded | +The maximum number of lots for which contract(s) can be awarded to one tenderer. + + Additional information: + This field is used to complement the SubmissionTerms (which are at the Lot level) + for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled + in the TED Standard Forms). + + WG Approval 22/08/2019 | +xsd:integer [0..1] | +||||
| epo:ContractTerm | +epo:hasMaximumNumberOfRenewals | +The maximum number of times the contract can be renewed. + + Additional Information + + By renewing, the buyer reserves the right (i.e. not an obligation) to renew the contract + (i.e. extend its duration) without a new procurement procedure. + For example, a contract may be valid for one year and the buyer may keep a possibility + to renew it (e.g. once, twice) for another three months, if he is content with the + services he received. + + PLEASE REVIEW THIS DEFINITION AGAIN WITH THE WORKING GROUP. It was originally taken + from eForms. + | +xsd:integer [0..1] | +||||
| epo:FrameworkAgreementTerm | +epo:hasMaximumParticipantsNumber | +The maximum number of participants in the framework agreement. + + Additional Information: + Maximum number of tenderers who may be awarded a contract within the framework agreement. + + The number is a positive integer. + + This corresponds in eForms to BT-113 Framework Maximum Participants Number. + + WG Approval 2019-02-05 | +xsd:integer [0..1] | +||||
| epo:SubcontractTerm | +epo:hasMaximumShare | +The maximum proportion of something to be distributed. + + Additional Information: + In the case of subcontracting the share may refer to the proportion of works, services + or supplies being subcontracted. + + WG Approval 17/09/2019 + + | +xsd:decimal [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasMediumTenderPerLots | +Tenders from medium-sized enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. + | +xsd:integer [0..1] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasMinimumNumberOfCandidates | +Minimum number of candidates to be invited for the second stage of the procedure. + + WG Approval 22/08/2019 | +xsd:integer [0..1] | +||||
| epo:SubcontractTerm | +epo:hasMinimumShare | +The minimum proportion of something to be distributed. + + Additional Information: + In the case of subcontracting the share may refer to the proportion of works, services + or supplies being subcontracted. + + WG Approval 17/09/2019 | +xsd:decimal [0..1] | +||||
| epo:SubcontractTerm | +epo:hasMinimumSubcontractorsProposedObligation | +The minimum percentage of the contract value that the contractor must subcontract. + + Additional information: + This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + + + WG Approval 09/11/2021 | +xsd:decimal [0..1] | +||||
| epo-con:ContractModificationInformation | +epo:hasModificationDescription | +An explanatory text about this context. + + Additional Information + + This corresponds in Standard forms to Field VII.2.1 in F20 + This corresponds in eForms to BT-202 . + + WG Approval 5/11/2019 + | +rdf:PlainLiteral [0..1] | +||||
| epo-con:ContractModificationInformation | +epo:hasModificationReasonDescription | +An explanation about the reasons for using the concept. + + Additional Information + This corresponds in Standard forms to Field VII.2.2.2 and VII.2.2.4 in F20. + + This corresponds in eForms to BT-201 . + + WG Approval 5/11/2019 + | +rdf:PlainLiteral [0..1] | +||||
| epo:ProcedureTerm | +epo:hasNationalProcedureRules | ++ | xsd:anyURI [0..*] | +||||
| epo:StrategicProcurement | +epo:hasNonAccessibilityCriterionJustification | +Reason for not applying accessibility criteria. + + Additional information: + This corresponds in eForma to BT-755 Accessibility Justification. + + WG Approval 05/03/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:LotAwardOutcome | +epo:hasNonAwardedContractNumber | +The number the contract would have had if it had been awarded. + + Additional information: + + This field is provided to support the data provided in the TED Standard Forms, and + it should be discontinued in the future. + + WG agreement: 06/09/2022 + | +rdf:PlainLiteral [0..1] | +||||
| epo:LotAwardOutcome | +epo:hasNonAwardedContractTitle | +The title the contract would have had if it had been awarded. + + Additional information: + + This field is provided to support the data provided in the TED Standard Forms, and + it should be discontinued in the future. + + WG agreement: 06/09/2022 | +rdf:PlainLiteral [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasNonEEAReceivedTenders | +The amount of tenders received from economic operators in non-EEA countries. + + WG Approval 12/12/2019 15:20:36 | +xsd:integer [0..1] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasNoNegotiationNecessary | +The buyer reserves the right to award the contract on the basis of the initial tenders + without any further negotiations. + + Additional information: + See Article 29(4) of Directive 2014/24/EU. + | +xsd:boolean [0..1] | +||||
| epo:SubmissionTerm | +epo:hasNonElectronicSubmissionDescription | +Textual explanation of how non-electronic information is to be presented. + + WG Approval 21/07/2020 + + | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasNonEUReceivedTenders | +The amount of tenders received from economic operators in non-EU countries. + | +xsd:integer [0..1] | +||||
| epo:Notice | +epo:hasNoticePublicationNumber | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ReviewRequest | +epo:hasNumberOfReviewRequests | +The number of requests the buyer received to review any of its decisions. | +xsd:integer [1..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasNumberOfTenderersInvited | +Number of economic operators invited to tender. + + Additional Information + This may be used for single-stage procedures or to indicate the number of candidates + invited to tender in multi-stage procedures. + + WG Approval 01/12/2020 + + | +xsd:integer [0..1] | +||||
| epo:Notice | +epo:hasOJSIssueNumber | ++ | xsd:integer [0..1] | +||||
| epo:Notice | +epo:hasOJSType | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:OpeningTerm | +epo:hasOpeningDateTime | +Date and time for the opening of tenders. + + WG Approval 12/03/2019 + + | +xsd:dateTime [1..1] | +||||
| epo:OpeningTerm | +epo:hasOpeningDescription | +Further information about the opening of tenders. + + Additional Information + For example, who may participate in the opening and whether any authorization is needed. + + WG Approval 12/03/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:OpeningTerm | +epo:hasOpeningURL | +The identifier of the address of the Opening of Tenders. + WG Approval 09/11/2021 | +xsd:anyURI [0..1] | +||||
| epo:ContractTerm | +epo:hasOptions | +The buyer reserves the right (not an obligation) for additional purchases from the + contractor (while the contract is valid). | +xsd:boolean [0..1] | +||||
| epo:ContractTerm | +epo:hasOptionsDescription | +The motivation and details about additional purchases that the buyer may undertake + while the contract is valid. + + WG Approval 09/04/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasOtherCountriesReceivedTenders | ++ | xsd:integer [0..1] | +||||
| epo:AwardEvaluationTerm | +epo:hasOverallCostAwardCriteriaPonderation | +The weighting given to cost. + + Additional Information: + This weighting covers usually all cost criteria against price or quality criteria. | +xsd:decimal [0..1] | +||||
| epo:AwardEvaluationTerm | +epo:hasOverallPriceAwardCriteriaPonderation | +The weighting given to price. + + Additional Information: + This weighting covers usually all price criteria against cost or quality criteria. | +xsd:decimal [0..1] | +||||
| epo:AwardEvaluationTerm | +epo:hasOverallQualityAwardCriteriaPonderation | +The weighting given to quality. + + Additional Information: + This weighting covers usually all quality criteria against price or cost criteria. | +xsd:decimal [0..1] | +||||
| epo:DesignContestRegimeTerm | +epo:hasParticipationPayment | +Details on payments to participants + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..1] | +||||
| epo:ContractTerm | +epo:hasPaymentArrangement | +Information about financial clauses that will govern some economic aspects of the + execution of the contract. + + Additional Information: These clauses usually refer to financial and payment provisions. + + This type of information should be structured instead of a free text in order to reuse + it an ideal world. Unfortunately this is an information that in the real life no one + is willing to provide pro-actively. + + WG Pending of discussion with eForms | +rdf:PlainLiteral [0..*] | +||||
| epo:ContractLotCompletionInformation | +epo:hasPaymentValueDiscrepancyJustification | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:ContractTerm | +epo:hasPerformanceConditions | +The particular conditions and additional information related to the execution of the + contract. + + Additional Information: + + For example, specific information about the place of performance, intermediary deliverables, + compensation for damages, intellectual property rights. + + WG approval 15-01-2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:ContractTerm | +epo:hasPlaceOfPerformanceAdditionalInformation | +Further details on the location of the execution of the contract. + + WG Approval 30/07/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:Prize | +epo:hasPrizeRank | +The position of the prize (e.g. first place, second place) in a design contest list + of prizes. + + WG Approval 29/08/2019 + | +xsd:integer [0..1] | +||||
| epo:ChangeInformation | +epo:hasProcurementDocumentChangeDate | +The date and time of the change. + + Additional information: + This corresponds in eForms to BT-719 Change Procurement Documents Date + + WG Approval 5/11/2019 + | +xsd:dateTime [0..1] | +||||
| epo:AccessTerm | +epo:hasPublicAccessURL | +Web page where the procurement documents can be downloaded. + + Additional Information: + This corresponds in the eForms to BT-15 Documents URL. + + WG Approval 09/03/2021 + | +xsd:anyURI [0..1] | +||||
| epo:Document | +epo:hasPublicationDate | +Date of formal public issuance of the document. + + WG approval 20/06/2023 | +xsd:date [0..1] | +||||
| epo:QualificationCriteriaSummary | +epo:hasQualificationCondition | ++ | rdf:PlainLiteral [0..*] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasQualificationSystemRenewalDescription | ++ | rdf:PlainLiteral [0..1] | +||||
| epo:Quantity | +epo:hasQuantityValue | +The numeric value of the quantity, including decimals. | +xsd:decimal [1..1] | +||||
| epo:SubmissionTerm | +epo:hasReceiptDeadline | +The time limit for receiving submissions. + + Additional Information + This is the deadline by which the buyer must receive submissions (e.g. tenders, requests + to participate, clarifications, etc.) and is not the time at which the information + is submitted by the economic operator. + This attribute should be used for standard forms mappings. + + WG Approval 21/07/2020 + | +xsd:dateTime [0..1] | +||||
| epo:SubmissionTerm | +epo:hasReceiptExpressionDeadline | +Time limit for receipt of expressions of interest. + + Pending of review by the WG + + | +xsd:dateTime [0..1] | +||||
| epo:SubmissionTerm | +epo:hasReceiptParticipationRequestDeadline | ++ | xsd:dateTime [0..1] | +||||
| epo:SubmissionTerm | +epo:hasReceiptPreliminaryMarketConsultationDeadline | ++ | xsd:dateTime [0..1] | +||||
| epo:SubmissionTerm | +epo:hasReceiptTenderDeadline | ++ | xsd:dateTime [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasReceivedMicroTenders | +The amount of tenders received from a micro enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. | +xsd:integer [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasReceivedParticipationRequests | +The amount of applications to participate from economic operators. + + WG Approval 12/12/2019 | +xsd:integer [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasReceivedSmallTenders | +Tenders from small enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. + + | +xsd:integer [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasReceivedTenders | +The total amount of tenders received. + + WG Approval 12/12/2019 | +xsd:integer [0..1] | +||||
| epo:Document | +epo:hasReceptionDate | +Notes: Date when a record is acknowledged by an organisation. + + WG Approval 12/05/2020 | +xsd:date [0..1] | +||||
| epo:ProcurementObject | +epo:hasRecurrenceDescription | +Any additional information about the recurrence of the Procurement. + + Additional Information: + For example estimated timing of the Procedure. + + This corresponds in eForms to BT-95 Recurrence Description. + + (WG approval 2019-01-16) + | +rdf:PlainLiteral [0..1] | +||||
| epo:CertificationLabel | +epo:hasReferenceURI | +A reference to where the label specification (norms, expectations, standards and policies) + can be found. + + WG approval 26/07/2022 | +xsd:anyURI [0..1] | +||||
| epo:ContractTerm | +epo:hasRenewalDescription | +Any other information about the renewal(s). + + WG approval 16/04/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:ReviewRequest | +epo:hasRequestDate | +The date when the review request was submitted. + + Additional information: + This attribute corresponds to the BT-787 Review Date in eForms. + | +xsd:date [0..1] | +||||
| epo:AccessTerm | +epo:hasRestrictedAccessURL | +The internet address with information on accessing the restricted (part of the) procurement + document. + + Additional Information: + This corresponds in eForms to BT-615 Documents Restricted URL. + | +xsd:anyURI [0..1] | +||||
| epo:ReviewTerm | +epo:hasReviewDeadline | +The time limit for review procedures. + + WG Approval 09/11/2021 | +xsd:dateTime [0..1] | +||||
| epo:ReviewTerm | +epo:hasReviewDeadlineInformation | +The description of the time limits for review procedures. + + WG Approval 01/10/2019 | +rdf:PlainLiteral [0..*] | +||||
| epo:ReviewIrregularitySummary | +epo:hasReviewIrregularityCount | +The number of requests for a given irregularity. + + Additional information: + This attribute corresponds in eForms to BT-635 Buyer Review Requests Count. | +xsd:integer [1..1] | +||||
| epo:ReviewTerm | +epo:hasReviewProcedure | +The description of the method used to request the verification that the procedure + has been carried out correctly. + + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:ReviewObject | +epo:hasReviewURL | +The internet address of the documents concerning the review instance. + + Additional information: + This attribute corresponds in eForms to BT-794 Review URL. + | +xsd:anyURI [0..1] | +||||
| adms:Identifier | +epo:hasScheme | +The name of the identification scheme. | +rdf:PlainLiteral [0..*] | +||||
| adms:Identifier | +epo:hasSchemeVersion | +The version of the identification scheme. | +rdf:PlainLiteral [0..*] | +||||
| epo:SelectionCriteriaSummary | +epo:hasSelectionCriteriaStatedInProcurementDocuments | ++ | xsd:boolean [0..1] | +||||
| epo:ProfessionalSuitabilitySummary | +epo:hasServiceReservedToParticularProfession | ++ | xsd:boolean [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasSMEReceivedTenders | +The amount of tenders received from micro, small and medium-sized enterprises. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. + The ReceivedSMETenderLots is used when the size of the company is not exactly knokn. + + WG Approval 05/03/2020 + | +xsd:integer [0..1] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasSMEReceivedTendersExcludingSubcontractors | ++ | xsd:integer [0..1] | +||||
| epo:StrategicProcurement | +epo:hasStrategicProcurementDescription | +Self-explanatory text about a concept. + | +rdf:PlainLiteral [0..*] | +||||
| epo:SubcontractTerm | +epo:hasSubcontractingInvolved | +List of Subcontractors and the subject matter they cover are required. + + Additional Information: + The tenderer will ned to supply this information in the tender. + + WG Approval 28/02/2019 | +xsd:boolean [0..1] | +||||
| epo:SubcontractTerm | +epo:hasSubcontractorsProposedAboveObligation | +The maximum percentage of the contract value that the contractor must subcontract. + + Additional information: + This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + + + WG Approval 09/11/2021 | +xsd:decimal [0..1] | +||||
| epo:SubcontractingEstimate | +epo:hasSubjectMatter | +Description of the share of the contract that is to be subcontracted. + + Additional infromation: + This can be an aggregate of several subcontracts. + + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionTerm | +epo:hasSubmissionURL | ++ Additional Information: + This corresponds to the eForms BT-18 Submission URL. + + This corresponds in eForms to BT-509 Organisation eDelivery Gateway. | +xsd:anyURI [0..*] | +||||
| epo:MultipleStageProcedureTerm | +epo:hasSuccessiveReduction | +The number of solutions or tenders will be reduced in iterative evaluations for multiple + staged procedures. + + Additional information: + This refers to multiple-stage procedures (included two-stage procedures, at least). + Open Procedures can be seen as one-stage procedures. + WG Approval 22/08/2019 | +xsd:boolean [0..1] | +||||
| cccev:Constraint | +epo:hasThresholdValue | +The cut-off level for a given concept. + + Additional Information: + This value is given as e.g. a minimum score, a maximum number of tenders with the + highest score passing (see codelist at-voc:number-threshold). | +xsd:decimal [1..1] | +||||
| epo:ReviewRequestSummary | +epo:hasTotalNumberOfComplainants | +The number of economic operators that requested the buyer to review any of its decisions + (e.g. the technical specifications, award decision), as set out in Art. 1(5) of Directive + 89/665/EEC and Directive 92/13/EEC. + + Additional information: + This attribute corresponds in eForms to BT-712 Buyer Review Complainants + + WG Approval 11/04/2019 | +xsd:integer [0..1] | +||||
| epo:VehicleInformation | +epo:hasTotalVehicles | +The number of all vehicles (regardless of whether clean or not) that have either been + purchased, leased, rented, hired-purchased or their use has been contractually committed + to for the provision of a purchased service. + + Additional Information + + In the European Union, the legal requirements and scope for the provision of these + vehicles or services are covered by Directive 2009/33/EC. + + WG Approval 28/07/2020 + | +xsd:integer [0..1] | +||||
| epo:Quantity | +epo:hasUnitDescription | +A narrative explanation defining the units of items being counted + + Additional information: This could be for example individual items or pack or two. + + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| epo:SubmissionStatisticalInformation | +epo:hasUnverifiedTenders | +Offers received for which it has not been verified if they are admissible or inadmissible + (e.g. because award criteria have been evaluated for all tenders and admissibility + is checked only for the winning tender). + + WG Approval 28/07/2020 + | +xsd:integer [0..1] | +||||
| cccev:Evidence epo:Fund |
+ epo:hasURL | +The identifier of a resource. + + Additional Information + + For example: + + 1. The URL of the system from where to access the procurement documents; + 2. The URL of the system for the submission of tender documents; + 3. The URL of the system from where to download a tool to communicate with the Buyer; + 4. The URL of the system used by a Technique to allow Economic Operators to exchange + information with the Buyer (e.g. eAuction and DPS Systems) + 5. The URL of the system used to exchange information between Buyer and EO for questions + and clarifications; + + WG Approval 30/09/2019 + The identifier of a resource. + + Additional Information + + For example: + + 1. The URL of the system from where to access the procurement documents; + 2. The URL of the system for the submission of tender documents; + 3. The URL of the system from where to download a tool to communicate with the Buyer; + 4. The URL of the system used by a Technique to allow Economic Operators to exchange + information with the Buyer (e.g. eAuction and DPS Systems) + 5. The URL of the system used to exchange information between Buyer and EO for questions + and clarifications; + + WG Approval 30/09/2019 | +xsd:anyURI [0..1] xsd:anyURI [0..1] |
+ ||||
| epo:Document | +epo:hasVersion | +A number that identifies a specific state of a document. + + WG approval: 18/11/2021 + | +rdf:PlainLiteral [0..1] | +||||
| epo:ReviewRequest | +epo:hasWithdrawalDate | +The date and time when the request for review was withdrawn. + + Additional information: + This attribute corresponds in eForms to BT-797 Review Request Withdrawn Date. | +xsd:date [0..1] | +||||
| epo:ReviewRequest | +epo:hasWithdrawalReason | +The explanation for withdrawing the request for review. + + Additional information: + This attribute corresponds in eForms to BT-798 Review Request Withdrawn Reasons | +rdf:PlainLiteral [0..1] | +||||
| epo:VehicleInformation | +epo:hasZeroEmissionVehicles | +The number of all zero-emission heavy-duty vehicles that have either been purchased, + leased, rented, hired-purchased or their use has been contractually committed to for + the provision of a purchased service. + + Additional Information + + In the European Union, the legal requirements and scope for the provision of these + vehicles or services are covered by Directive 2009/33/EC. + + WG Approval 28/07/2020 + | +xsd:integer [0..1] | +||||
| epo:ProcurementCriteriaSummary | +epo:indicatesPerformingStaffInformationRequirement | ++ | xsd:boolean [0..1] | +||||
| epo:Procedure | +epo:isAccelerated | +Statement about the fact that the procedure will be reduced due to a state of urgency. + + Additional Information + + This modifies the time limit for the receipt of requests to participate or the receipt + of tenders. + + WG Approval 20/08/2019 + | +xsd:boolean [0..1] | +||||
| epo:SubmissionTerm | +epo:isAdvancedElectronicSignatureRequired | +Advanced or qualified electronic signature or seal (as defined in Regulation (EU) + No 910/2014) is required. + + + + The submitted information is required to be signed electronically. + + Additional Information: + + Signature can be defined as "data in electronic form which is attached to or logically + associated with other data in electronic form and which is used by the signatory to + sign. + For more details on the meaning and uses of electronic signature you may consult different + authoritative sources, a relevant one being for instance the Regulation (EU) 910/2014 + on electronic identification and trust services for electronic transactions in the + internal market. + + WG Approval 21/07/2020 + | +xsd:boolean [0..1] | +||||
| epo:ProcedureTerm | +epo:isAwardedByCPB | +Procedure is awarded by a Central Purchasing Body. + + | +xsd:boolean [0..1] | +||||
| epo:ProcurementProcessInformation | +epo:isCompetitionTerminated | +No further contracts will be awarded in this procedure. + + Additional Information: + This can be instantiated in the post award phase. + + PIN for Competition needs to be signaled. This field can be used even if no contracts + are awarded in the contract award notice. + + This corresponds in eForms to BT-756 PIN Competition Termination. | +xsd:boolean [0..1] | +||||
| epo:Buyer | +epo:isContractingEntity | +Role of entities, which: + + (a) are contracting authorities or public undertakings and which pursue one of the + activities referred to in Articles 8 to 14 of the Directive 2014/25/EU. + + (b) when they are not contracting authorities or public undertakings, have as one + of their activities any of the activities referred to in Articles 8 to 14, or any + combination thereof and operate on the basis of special or exclusive rights granted + by a competent authority of a Member State. + + Additional Information + + The indicator is needed in order to discriminate between those contracts where the + Contracting Entity acts as a Contracting Authority undergoing the limits and the rules + of Directive 24 and those where it acts as a Contracting Entity, with certain relaxed + constraints. + For example, the Contracting Entities have different thresholds for the application + of Directive 24 if compared with Contracting Authorities. + + WG Approval 28/04/2020 + | +xsd:boolean [0..1] | +||||
| epo:ProcurementObject | +epo:isCoveredByGPA | +Specifies whether the Agreement on Government Procurement (GPA) applies. + + Additional information: + The GPA aims to establish a multilateral framework of balanced rights and obligations + relating to public contracts with a view to achieving the liberalization and expansion + of world trade. + + This corresponds in the e Forms to BT-115 GPA Coverage. + + WG Approval 15/10/2019 + + | +xsd:boolean [0..1] | +||||
| epo:Procedure | +epo:isDesignContest | +A competition which enables the buyer to acquire a plan or design via a jury. + + Additional information: + Design contests have traditionally mostly been used in the fields of town and country + planning, architecture and engineering or data processing, other purposes, such as + to obtain plans for financial engineering + + The contest may include or not the award of prizes; + + WG approval 04-02-2021 | +xsd:boolean [0..1] | +||||
| epo:ProcurementProcessInformation | +epo:isDPSTerminated | +End of the Dynamic Purchase System (DPS). + + Additional Information: This property can be used in the contract award notice even + if no contracts are awarded. + + WG Approval 22/11/2019 + | +xsd:boolean [0..1] | +||||
| epo:SubmissionTerm | +epo:isGuaranteeRequired | +The submitted information must include a financial commitment to be used in case of + default. + + Additional Information: + See the additional information provided in the definition of the 'Guarantee Description' + element. + + WG Approval 21/07/20 + + | +xsd:boolean [0..1] | +||||
| epo:Procedure | +epo:isJointProcurement | +Multiple buyers procure together within the same procedure. + + Addition Information: + In case the joint procurement involves buyers from different countries, the national + law is specified by the epo:hasCrossBorderLaw in the ProcedureTerm . | +xsd:boolean [0..1] | +||||
| epo:DesignContestRegimeTerm | +epo:isJuryDecisionBinding | +Indicates whether the procuring entity is bound to apply the decision of the jury. | +xsd:boolean [0..1] | +||||
| epo:Business | +epo:isListedCompany | +Public companies listed on a stock exchange and subject to disclosure requirements + (either by stock exchange + rules or through law or enforceable means), which impose requirements to ensure adequate + transparency of + beneficial ownership. + + <u>Additional Information:</u> + + In eForms this indicator is used when the nationality of beneficial owner is not provided + because the Economic Operator is registered in a regulated market that is subject + to disclosure requirements consistent with Union law or subject to equivalent international + standards which ensure adequate transparency of ownership information. + + WG Approval 21/11/2019 | +xsd:boolean [0..1] | +||||
| epo:SubmissionTerm | +epo:isMultipleTenderSubmissionAllowed | +Tenderers may submit more than one competing tenders. + + WG Approval 10/10/2019 + + | +xsd:boolean [0..1] | +||||
| epo:NonDisclosureAgreementTerm | +epo:isNonDisclosureAgreementRequired | ++ | xsd:boolean [0..1] | +||||
| epo:ProcedureTerm | +epo:isOneLotOnlyAllowed | +Indicates whether tenders may be submitted for only one Lot. + + Additional information: + This field is used to complement the SubmissionTerms (which are at the Lot level) + for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled + in the TED Standard Forms). + + WG approval 23/08/2022 + + | +xsd:boolean [0..1] | +||||
| epo:ChangeInformation | +epo:isProcurementDocumentChanged | +One or more procurement documents have been changed. + + Additional information: + This corresponds in eForms to BT-718 Change Procurement Documents + + WG Approval 05/11/2019 | +xsd:boolean [0..1] | +||||
| epo:AccessTerm | +epo:isProcurementDocumentRestricted | +The access to certain procurement documents is restricted. + + Additional Information: + This corresponds in eForms to BT-14 Documents Restricted. + + WG Approval 10/10/2019 | +xsd:boolean [0..1] | +||||
| epo:ProcurementObject | +epo:isRecurrent | +The Procurement being notified is likely to be included in another procedure in the + foreseeable future. + + Additional Information: + + For example, a regularly re-tendered municipal service. This does not include awarding + multiple contracts within a single qualification system, framework agreement, or a + dynamic purchasing system. + + This corresponds in eForms to BT-94 Recurrence. + + WG Approval 12/05/2020 + | +xsd:boolean [0..1] | +||||
| epo:ContractTerm | +epo:isRenewalIndicator | +Indicates whether the contract is subject to a renewal clause. + WG Approval 09/11/2021 | +xsd:boolean [0..1] | +||||
| epo:SecurityClearanceTerm | +epo:isSecurityClearanceRequired | ++ | xsd:boolean [0..1] | +||||
| epo:ProcurementObject | +epo:isSMESuitable | +The Lot is suitable for small and medium enterprises (SMEs). + + Additional Information + + This allows the buyer to make emphasis on the fact that the procedure has been designed + having SMEs in mind. This indicator is also to be reflected in the selection criteria. + + For example, number of employees and turnover are applicable to the definition of + an SME. + + WG Approval 15/10/2019 + | +xsd:boolean [0..1] | +||||
| epo:ProcedureTerm | +epo:isSubmissionForAllLotsRequired | +Indicates whether tenders must be submitted for all Lots. + | +xsd:boolean [0..1] | +||||
| epo:ProcurementProcessInformation | +epo:isToBeRelaunched | +Indicator of whether the procurement object is to be relaunched. + + Additional information: + This can be instantiated in the post award phase. + + This corresponds in eForms to BT-634 Procurement Relaunch. + + WG Approval: 18/01/2022 + | +xsd:boolean [0..1] | +||||
| epo:SelectionCriterion | +epo:isUsedForCandidateRestriction | +The criterion will be used to select the candidates to be invited for the second stage + of a multistage procedure. + + Additional Information: + This property is only used if a maximum number of candidates was foreseen in the procedure. + This corresponds in eForms to BT-40 Selection Criteria Second Stage Invite | +xsd:boolean [0..1] | +||||
| epo:ProcurementObject | +epo:isUsingEUFunds | +The procurement foresees funding by the Union. + + Additional Information: + The funding may cover the whole procurement or part of the procurement. + + For example the European Structural and Investment Funds or grants awarded by the + European Union. + + | +xsd:boolean [0..1] | +||||
| epo:Tender | +epo:isVariant | +Alternative solution to fulfil the buyer's needs as opposed to solutions indicated + in the procurement documents. + + Additional Information: + + The permission to offer variants is only allowed if specified in a Contract Notice + or a Prior Information Notice that used as a means for calling for a competition. + The buyer lays out minimum requirements in the procurement documents that must be + respected by tenderers submitting variants. + + WG Approval 29/05/2019 + + | +xsd:boolean [0..1] | +||||
| epo:ReviewRequest | +epo:isWithdrawn | +The review request was withdrawn. + + Additional information: + This attribute corresponds in eForms to BT-796 Review Request Withdrawn. | +xsd:boolean [0..1] | +||||
| epo:GreenProcurement | +epo:usesCleanVehicleDirective | +The procurement falls within the scope of the European Parliament and Council 2009/33/EC + (Clean Vehicles Directive – CVD). | +xsd:boolean [0..1] | +||||
| epo-cat:ItemProperty | +epo-cat:hasAttributeType | +The property defined in a classification scheme. + + Additional Information: + For example, the following two properties are defined in the ECLASS classification + of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, + (0173-1#02-AAA030#007) flange diameter: flange diameter . + + + WG approval 28/07/2022 | +rdf:PlainLiteral [1..1] | +||||
| epo-cat:Batch | +epo-cat:hasBestBeforeDate | +The day until which the quality of the item will remain optimal. + + WG approval 10/03/2021 | +xsd:date [0..1] | +||||
| epo-cat:ItemProperty | +epo-cat:hasClassificationScheme | +The classification scheme where a property is defined. + + Additional Information: + For example, the following two properties are defined in the ECLASS classification + of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, + (0173-1#02-AAA030#007) flange diameter: flange diameter . + + WG approval 28/07/2022 + | +rdf:PlainLiteral [1..1] | +||||
| epo-cat:Item | +epo-cat:hasDimensionDescription | +Textual description of the item's dimensions. | +rdf:PlainLiteral [0..*] | +||||
| epo-cat:Batch | +epo-cat:hasExpiryDate | +The last day until which the item can be used. + + WG approval 10/03/2021 + | +xsd:date [0..1] | +||||
| epo-cat:ItemRelation | +epo-cat:hasFactor | +The number or the fraction of a related item. | +xsd:decimal [0..1] | +||||
| epo-cat:Item | +epo-cat:hasHazardousClass | +Specification of the hazardous nature of an item according to a classification schema. + Provides detail of the classification and nature of a hazardous item. | +rdf:PlainLiteral [0..*] | +||||
| epo-cat:Item | +epo-cat:hasKeyword | +List of words (e.g, synonyms) to make the item searchable. + + WG Approval 7/04/2022 + | +rdf:PlainLiteral [0..*] | +||||
| epo-cat:ItemProperty | +epo-cat:hasLiteralValue | +Simple value of the property, which is defined in a classification scheme. + + Additional Information: + For example, the (0173-1#02-AAV139#001) coating 1 of an optical material has value + of "silver". + + This simple literal value is for the cases when the property value does not have units, + in which case the qualifiedValue shall be used. + + WG approval 28/07/2022 + + + | +rdf:PlainLiteral [0..1] | +||||
| epo-cat:Batch | +epo-cat:hasManufactureDate | +The day of production. + | +xsd:dateTime [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:hasOrderableQuantityIncrement | +Orderable quantity increment: The increment of Orderable units that can be ordered. | +xsd:integer [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:hasOrderableUnitFactorRate | +The factor by which the Item net price of an unit of an item can be converted to the + orderable unit. | +xsd:decimal [0..1] | +||||
| epo-ord:AllowanceChargeInformation epo-ord:TaxInformation |
+ epo-cat:hasPercentage | +The factor relative to the price charged in addition. + + WG approval 26/07/2022 The factor relative to the price charged in addition. + + WG approval 26/07/2022 + | +xsd:decimal [0..1] xsd:decimal [0..1] |
+ ||||
| epo-cat:Catalogue | +epo-cat:hasSpecificPaymentArrangement | +Information about payment conditions applied to all items in the catalogue. + + Additional information: + This property may need to be used together with the payment arrangements provided + in the ContractTerms, where such terms exists. + + WG approval 30/06/2022 + + | +rdf:PlainLiteral [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:hasTransactionConditions | +Textual description of the specific transaction conditions (purchasing, sales, payment) + for an item. | +rdf:PlainLiteral [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:hasWarrantyInformation | +Warranty information that applies to the catalogue line item. | +rdf:PlainLiteral [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:isContractedItem | +Indicator if the item is offered in accordance to an existing contract. | +xsd:boolean [0..1] | +||||
| epo-cat:Item | +epo-cat:isInStock | +Indicator whether an item is in the supplier's stock. If not in stock the supplier + has to order the item. | +xsd:boolean [0..1] | +||||
| epo-cat:CatalogueLine | +epo-cat:isOrderable | +Indicator, if the item is orderable or not, e.g. because it is temporarily out of + stock. | +xsd:boolean [0..1] | +||||
| epo-ful:ShipmentInformation | +epo-ful:despatchDate | ++ | xsd:dateTime [0..1] | +||||
| epo-ord:AllowanceChargeInformation | +epo-ful:hasAllowanceChargeReasonDescription | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment | +epo-ful:hasCarrierServiceInstruction | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment | +epo-ful:hasDeliveryInstruction | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment epo-ful:TransportHandlingUnit |
+ epo-ful:hasHandlingInstruction | ++ | rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] |
+ ||||
| epo-ful:DespatchLine | +epo-ful:hasOutstandingQuantityReason | ++ | rdf:PlainLiteral [0..1] | +||||
| epo-ful:Package | +epo-ful:hasPackagingTypeDescription | ++ | rdf:PlainLiteral [0..1] | +||||
| epo-ful:TransportHandlingUnit | +epo-ful:hasShippingMark | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment | +epo-ful:hasSpecialInstruction | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment | +epo-ful:hasSpecialServiceInstruction | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-ful:Consignment | +epo-ful:hasVehicleDescription | ++ | rdf:PlainLiteral [0..1] | +||||
| epo-ful:AbstractContainer epo-ful:Consignment epo-ful:ShipmentStage |
+ epo-ful:isHazardousRisk | ++ | xsd:boolean [0..1] xsd:boolean [0..1] xsd:boolean [0..1] |
+ ||||
| epo-ful:TransportEquipment | +epo-ful:isPowerIndicated | ++ | xsd:boolean [0..1] | +||||
| epo-ful:TransportEquipment | +epo-ful:isRefrigerated | ++ | xsd:boolean [0..1] | +||||
| epo-ful:TransportEquipment | +epo-ful:isReturnable | ++ | xsd:boolean [0..1] | +||||
| epo-ful:AbstractContainer | +epo-ful:isReturnableMaterial | ++ | xsd:boolean [0..1] | +||||
| epo-ord:Order | +epo-ord:hasAccountingCost | +The accounting reference used by the Buyer to specify the account to which the order + and the corresponding invoice are booked. + + WG approval 2023-01-26 | +rdf:PlainLiteral [0..1] | +||||
| epo-ord:Order | +epo-ord:hasCustomerReference | +A supplementary reference for the order. + + Additional information: + This information can be used for the buyer's internal processes. + This reference can also be used in the invoice. + + WG approval 2023-01-26 | +xsd:boolean [0..1] | +||||
| epo-ord:DeliveryInformation | +epo-ord:hasDeliveryDeadline | ++ | xsd:dateTime [0..1] | +||||
| epo-ord:Order | +epo-ord:hasPaymentTerm | ++ | rdf:PlainLiteral [0..1] | +||||
| epo-ord:OrderResponse | +epo-ord:hasResponseDescription | +Response clarification of the Supplier decision. | +rdf:PlainLiteral [0..1] | +||||
| epo-ord:DeliveryInformation | +epo-ord:hasShippingMark | ++ | rdf:PlainLiteral [0..*] | +||||
| epo-sub:CertificateInformation | +epo-sub:coversAllSelectionCriteria | +Indicator that the Certificate proves whether the Organization fulfils all Selection + Criteria. + + WG approval 12/03/2024 | +xsd:boolean [0..1] | +||||
| epo-sub:NationalPreQualificationData | +epo-sub:providesOrganisationCompletedTaskDescription | +Text describing the works, supplies or services executed, delivered or performed in + a procurement project that can be used as an evidence for the classification of the + Organization. + + WG approval 05/03/2024 | +rdf:PlainLiteral [0..1] | +||||
| person:Person | +foaf:familyName | +The hereditary surname of a family. + | +rdf:PlainLiteral [0..*] | +||||
| person:Person | +foaf:givenName | +The name(s) that identify the Person within a family with a common surname. + | +rdf:PlainLiteral [0..*] | +||||
| person:Person | +foaf:name | +The complete name of the Person as one string. | +rdf:PlainLiteral [0..*] | +||||
| locn:Address | +locn:addressArea | +The name or names of a geographic area or locality that groups a number of addressable + objects for addressing purposes, without being an administrative unit. + + Additional Information: + This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:adminUnitL1 | +The name or names of a unit of administration related to the exercise of jurisdictional + rights, for local, regional and national governance. Level 1 refers to the uppermost + administrative unit for the address, almost always a country. + + Additional Information: + Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, + country names should be provided in a consistent manner to reduce ambiguity. For example, + either write 'France' or 'FRA' consistently throughout the dataset and avoid mixing + the two. The Country controlled vocabulary from the Publications Office can be reused + for this. | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:adminUnitL2 | +The name or names of a unit of administration related to the exercise of jurisdictional + rights, for local, regional and national governance. Level 2 refers to the region + of the address, usually a county, state or other such area that typically encompasses + several localities. + + Additional Information: + Some recommended codelists from the EU Publications Office include: Administrative + Territorial Units (ATU), NUTS and Local Administrative Units (LAU). The first arrondissement + of Paris is for example expressed as "http://publications.europa.eu/resource/authority/atu/FRA_AR_PAR01" + in the ATU controlled vocabulary. + | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:fullAddress | +The complete address written as a formatted string. + + Additional Information: + Use of this property is recommended as it will not suffer any misunderstandings that + might arise through the breaking up of an address into its component parts. This property + is analogous to vCard's label property but with two important differences: (1) formatting + is not assumed so that, unlike vCard label, it may not be suitable to print this on + an address label, (2) vCard's label property has a domain of vCard Address; the fullAddress + property has no such restriction. An example of a full address is "Champ de Mars, + 5 Avenue Anatole France, 75007 Paris, France". | +rdf:PlainLiteral [0..1] | +||||
| dct:Location | +locn:geographicName | +A textual description for a Location. + + Additional Information: + The INSPIRE Data Specification on Geographical Names provides a detailed model for + describing a 'named place', including methods for providing multiple names in multiple + scripts. This is beyond what is necessary for the Core Location Vocabulary but, importantly, + the concept of a geographic name used here is consistent. + + A geographic name is a proper noun applied to a spatial object. Taking the example + used in the INSPIRE document (page 15), the following are all valid geographic names + for the Greek capital: + + - "Aθnνa"@gr-Grek (the Greek endonym written in the Greek script) + - "Athína"@gr-Latn (the standard Romanisation of the endonym) + - "Athens"@en (the English language exonym) + INSPIRE has a detailed (XML-based) method of providing metadata about a geographic + name and in XML-data sets that may be the most appropriate method to follow. When + using the Core Location Vocabulary in data sets that are not focussed on environmental/geographical + data (the use case for INSPIRE), the Code datatype or a simple language identifier + may be used to provide such metadata. + + The country codes defined in ISO 3166 may be used as geographic names and these are + generally preferred over either the long form or short form of a country's name (as + they are less error prone). The Publications Office of the European Union recommends + the use of ISO 3166-1 codes for countries in all cases except two: + + - use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; + - use 'EL' in preference to the ISO 3166 code GR for Greece. + Where a country has changed its name or no longer exists (such as Czechoslovakia, + Yugoslavia etc.) use the ISO 3166-3 code. + | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:locatorDesignator | +A number or a sequence of characters which allows a user or an application to interpret, + parse and format the locator within the relevant scope. A locator may include more + locator designators. + + Additional Information: + In simpler terms, this is the building number, apartment number, etc. For an address + such as "Flat 3, 17 Bridge Street", the locator is "flat 3, 17". | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:locatorName | +Proper noun(s) applied to the real world entity identified by the locator. + + Additional Information: + The locator name could be the name of the property or complex, of the building or + part of the building, or it could be the name of a room inside a building. + + The key difference between a locator and a locator name is that the latter is a proper + name and is unlikely to include digits. For example, "Shumann, Berlaymont" is a meeting + room within the European Commission headquarters for which locator name is more appropriate + than locator. | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:postCode | +The post/zip code of an address. (INSPIRE's definition is "A code created and maintained + for postal purposes to identify a subdivision of addresses and postal delivery points.") + + Additional Information: + Post codes are common elements in many countries' postal address systems. One of the + many post codes of Paris is for example "75000". | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:postName | +The key postal division of the address, usually the city. (INSPIRE's definition is + "One or more names created and maintained for postal purposes to identify a subdivision + of addresses and postal delivery points.) For example, "Paris". | +rdf:PlainLiteral [0..1] | +||||
| locn:Address | +locn:thoroughfare | +An address component that represents the name or names of a passage or way through + from one location to another. A thoroughfare is not necessarily a road, it might be + a waterway or some other feature. + + Additional Information: + For example, "Avenue des Champs-Élysées". | +rdf:PlainLiteral [0..1] | +||||
| person:Person | +person:birthName | +Family name of the Person given upon their birth. + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| person:Person | +person:patronymicName | +Name based on the given name of the Person's father. + WG Approval 09/11/2021 | +rdf:PlainLiteral [0..*] | +||||
| adms:Identifier | +skos:notation | +The literal identifying an entity, like a person or an object. | +rdf:PlainLiteral [1..1] | +||||
| cccev:InformationConcept cccev:Requirement cccev:EvidenceTypeList |
+ skos:prefLabel | +The preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 + + The preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 The preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 + | +rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] |
+ ||||
| epo:SpecificDuration | +time:numericDuration | +Value of a temporal extent expressed as a number. | +xsd:decimal [1..1] | +
| Predicate name | +Definition | +Domain, Range and Cardinality | +||||
|---|---|---|---|---|---|---|
| adms:identifier | +Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. A unique identifier of the instance of the concept. + + Additional Information + + For example, in the case of the Procurement Identifier, this could be the European + Public Procurement Identifier, and/or any other identifier provided by the buyer, + the service provider or any other stakeholder. + + WG Approval 12/11/2019 + + Links a resource to an adms:Identifier class. A unique identifier of the instance of the concept. + + Additional Information + + For example, in the case of the Procurement Identifier, this could be the European + Public Procurement Identifier, and/or any other identifier provided by the buyer, + the service provider or any other stakeholder. + + WG Approval 12/11/2019 A unique identifier of the instance of the concept. + + Additional Information + + For example, in the case of the Procurement Identifier, this could be the European + Public Procurement Identifier, and/or any other identifier provided by the buyer, + the service provider or any other stakeholder. + + WG Approval 12/11/2019 + A unique identifier of the instance of the concept. + + Additional Information + + For example, in the case of the Procurement Identifier, this could be the European + Public Procurement Identifier, and/or any other identifier provided by the buyer, + the service provider or any other stakeholder. + + WG Approval 12/11/2019 + Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. | +cccev:Evidence -> adms:Identifier [1] cccev:InformationConcept -> adms:Identifier [0..1] cccev:Requirement -> adms:Identifier [0..1] dct:Location -> adms:Identifier [0..1] epo:Document -> adms:Identifier [0..*] epo:Fund -> adms:Identifier [0..1] epo:Project -> adms:Identifier [0..1] foaf:Agent -> adms:Identifier [0..*] epo:LotGroup -> adms:Identifier [0..1] epo:ProcurementElement -> adms:Identifier [1] epo:TenderGroup -> adms:Identifier [0..1] cccev:EvidenceType -> adms:Identifier [0..1] epo-ful:Consignment -> adms:Identifier [0..1] epo-ful:TransportEquipment -> adms:Identifier [0..1] epo-ful:ShipmentStage -> adms:Identifier [0..1] epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1] cccev:EvidenceTypeList -> adms:Identifier [0..1] epo-ful:ShipmentInformation -> adms:Identifier [0..1] epo-cat:Line -> adms:Identifier [0..1] epo-ful:AbstractContainer -> adms:Identifier [0..1] |
+ ||||
| cccev:confidentialityLevelType | +Security classification assigned to an Evidence e.g. classified, sensitive, public. + + Additional Information: + + Classifications should be defined by an organisation/country as an outcome of a security + assessment. + Security classification assigned to an Evidence e.g. classified, sensitive, public. + + Additional Information: + + Classifications should be defined by an organisation/country as an outcome of a security + assessment. | +cccev:Evidence -> at-voc:access-rights [0..1] epo-sub:Response -> at-voc:access-rights [] |
+ ||||
| cccev:constrains | +Information Concept about which a Constraint expresses a limitation. + + Additional Information: + Information Concepts are tools to make Requirements more machine processable: they + allow to provide more detail about a Requirement. This way, Constraints can be made + very precise, namely the limit that must be achieved, is a limit on the value for + the associated Information Concept. For example, the Information Concept would be + the age of a person and the Constraint would be the required age in the context of + a specific evaluation. | +cccev:Constraint -> cccev:InformationConcept [0..*] | +||||
| cccev:hasConcept | +Information Concept for which a value is expected by the Requirement. + + Additional Information: + Information Concepts defined for specific Requirements also represent the basis for + specifying the Supported Value an Evidence should provide. | +cccev:Requirement -> cccev:InformationConcept [0..*] | +||||
| cccev:hasEvidenceTypeList | +Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement. + + Additional Information: + One or several Lists of Evidence Types can support a Requirement. At least one of + them must be satisfied by the response to the Requirement. | +cccev:Requirement -> cccev:EvidenceTypeList [0..*] | +||||
| cccev:hasRequirement | +A more specific Requirement that is part of the Requirement. | +cccev:Requirement -> cccev:Requirement [0..*] | +||||
| cccev:isDerivedFrom | +Reference Framework on which the Requirement is based, such as a law or regulation. + + Additional Information: + The relation between a parent Requirement and a sub-Requirement can be complex. Therefore, + qualified relations (see hasQualifiedRelation) can be used to represent this relationship + on its own and qualify it with additional information such as a date, a place. This + is left to implementers. In the case where the purpose is to link the two Requirements + without additional information, the simple relationship as proposed here can be directly + used. | +cccev:Requirement -> eli:LegalResource [] | +||||
| cccev:providesValueFor | +Information Concept for which the Supported Value provides a value. | +cccev:SupportedValue -> cccev:InformationConcept [0..*] | +||||
| cccev:specifiesEvidenceType | +Evidence Type included in this Evidence Type List. | +cccev:EvidenceTypeList -> cccev:EvidenceType [0..*] | +||||
| cccev:supportsConcept | +Information Concept providing facts found/inferred from the Evidence. + + Additional Information: + Examples of Information Concepts are values found explicitly in the evidence such + as a birth date or information derived from the Evidence such as "I am older that + 18 years" or "this is a Fair Trade product". | +cccev:Evidence -> cccev:InformationConcept [0..*] | +||||
| cccev:supportsRequirement | +Requirement for which the Evidence provides proof. | +cccev:Evidence -> cccev:Requirement [0..*] | +||||
| cccev:supportsValue | +Supported Value that the Evidence contains. Supported Value that the Evidence contains. | +cccev:Evidence -> cccev:SupportedValue [0..*] epo-sub:Response -> cccev:SupportedValue [0..*] |
+ ||||
| cccev:validityPeriodConstraint | +Temporal condition on the validity period of the Evidence Type. + + Additional Information: + E.g. A Belgian birth evidence is valid for X months after emission. To express constraints + on the validity period that must hold when assessing the evidence (e.g. the certificate + of good conduct cannot be issued more than 3 months ago), we refer to the Constraint + class. | +cccev:EvidenceType -> epo:Period [0..*] | +||||
| cv:registeredAddress | +The registered address relationship links a Resource with the legally registered Address. + + Additional Information: + It is the address to which formal communications can be sent, such as the postal address. The registered address relationship links a Resource with the legally registered Address. + + Additional Information: + It is the address to which formal communications can be sent, such as the postal address. + | +person:Person -> locn:Address [0..1] org:Organization -> locn:Address [0..1] |
+ ||||
| dct:conformsTo | +An established standard to which the described resource conforms. + + Additional Information: + Examples of characteristics could be the layout or the configuration of the Evidence. | +cccev:Evidence -> cccev:EvidenceType [0..*] | +||||
| dct:hasPart | +A related resource that is included either physically or logically in the described + resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item is part of another item. + + WG Approval: 30/06/2022 + | +epo-cat:Item -> epo-cat:Item [0..*] | +||||
| dct:isPartOf | +A related resource in which the described resource is physically or logically included. | +eli:Work -> eli:Work [0..*] | +||||
| dct:isReplacedBy | +A related resource that is supplanted, displaced, or superseded by the described resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item replaces another item. + + WG Approval: 30/06/2022 + A related resource that is supplanted, displaced, or superseded by the described resource. + | +epo-cat:Item -> epo-cat:Item [0..*] | +||||
| dct:language | +A language of the resource. | +eli:LegalExpression -> at-voc:language [1..*] | +||||
| dct:replaces | +A related resource that is supplanted, displaced, or superseded by the described resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item replaces another item. + + WG Approval: 30/06/2022 + A related resource that is supplanted, displaced, or superseded by the described resource. + | +epo-cat:Item [,0..*] <- epo-cat:Item | +||||
| dct:requires | +A related resource that is required by the described resource to support its function, + delivery, or coherence. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one Item requires another Item. + + WG Approval: 30/06/2022 + | +epo-cat:Item -> epo-cat:Item [0..*] | +||||
| dct:type | +Category to which the Requirement belongs. | +cccev:Criterion -> at-voc:criterion [0..1] | +||||
| eli:is_realized_by | +Relates a work to an expression of this work in the form of a "sequence of signs" + (typically alpha-numeric characters in a legal context). Inverse of "realizes". | +eli:LegalExpression -> eli:Work [1] | +||||
| eli:jurisdiction | +The jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + The jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + | +eli:LegalExpression -> at-voc:atu [0..*] eli:LegalResource -> at-voc:atu [0..*] |
+ ||||
| eli:uri_schema | +Schema describing the URI of an ELI instance. ELI uses URI template specifications + (IETF RFC 6570). Schemes should be associated with member states and will be published + in a registry. + Schema describing the URI of an ELI instance. ELI uses URI template specifications + (IETF RFC 6570). Schemes should be associated with member states and will be published + in a registry. + | +eli:LegalResourceSubdivision -> adms:Identifier [0..*] eli:LegalExpression -> adms:Identifier [0..*] |
+ ||||
| epo:actsOnBehalfOf | +Represents. | +epo:ProcurementServiceProvider -> epo:Buyer [1..*] epo-sub:LegalRepresentative -> epo:OfferingParty [0..1] |
+ ||||
| epo:amendsContract | ++ | epo-con:ContractAmendment -> epo:Contract [1] | +||||
| epo:announcesAwardDecision | ++ | epo-not:ResultNotice -> epo:AwardDecision [0..*] epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*] |
+ ||||
| epo:announcesCompletionOfContract | ++ | epo-not:CompletionNotice -> epo:Contract [1] | +||||
| epo:announcesContract | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*] epo-not:ResultNotice -> epo:Contract [0..*] |
+ ||||
| epo:announcesContractAmendment | ++ | epo-not:ContractModificationNotice -> epo-con:ContractAmendment [1] | +||||
| epo:announcesLot | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*] epo-not:CompetitionNotice -> epo:Lot [1..*] |
+ ||||
| epo:announcesLotGroup | ++ | epo-not:CompetitionNotice -> epo:LotGroup [0..*] epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*] |
+ ||||
| epo:announcesLotGroupAwardInformation | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*] epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*] |
+ ||||
| epo:announcesNoticeAwardInformation | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1] epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1] |
+ ||||
| epo:announcesPlannedProcurementPart | ++ | epo-not:PlanningNotice -> epo:PlannedProcurementPart [0..*] | +||||
| epo:announcesProcedure | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1] epo-not:CompetitionNotice -> epo:Procedure [1] |
+ ||||
| epo:announcesReviewObject | ++ | epo-not:CompletionNotice -> epo:ReviewObject [1..*] | +||||
| epo:announcesRole | ++ | epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*] epo-not:ContractModificationNotice -> epo:AgentInRole [0..*] epo-not:PlanningNotice -> epo:AgentInRole [1..*] epo-not:CompetitionNotice -> epo:AgentInRole [1..*] epo-not:CompletionNotice -> epo:AgentInRole [0..*] |
+ ||||
| epo:answersExclusionGround | ++ | epo-sub:ESPDResponse -> epo:ExclusionGround [1] | +||||
| epo:answersSelectionCriteria | ++ | epo-sub:ESPDResponse -> epo:SelectionCriterion [1] | +||||
| epo:associatedWith | +The document to which a document is associated. + + WGM 01/03/2022 + | +epo:Document -> epo:Document [0..*] | +||||
| epo:attestedByLabel | +Relation indicating which label the certificate is about. + + WG approval 28/07/2022 | +epo:Certificate -> epo:CertificationLabel [0..1] | +||||
| epo:bindsBuyer | +Provides legal constraint on the Buyer. | +epo:Contract -> epo:Buyer [0..*] | +||||
| epo:bindsContractor | +Provides legal constraint on the Contractor. | +epo:Contract -> epo:Contractor [0..*] | +||||
| epo:canProvideNonDiscriminatoryEvidence | +Relation showing that an Organization can supply an Evidence with regard to the fulfilment + of non-discriminatory criteria or the rules applied in order to reduce the number + of participants. + + WG approval 12/03/2024 | +org:Organization -> cccev:Evidence [0..*] | +||||
| epo:canProvideTaxAndSocialSecuritiesEvidence | +Relation showing that an Organization can supply an Evidence with regard to the payment + of social security contributions and taxes. + + WG approval 12/03/2024 | +org:Organization -> cccev:Evidence [0..*] | +||||
| epo:comprisesAwardOutcome | +Incorporates AwardOutcome. | +epo:AwardDecision -> epo:AwardOutcome [0..*] | +||||
| epo:comprisesTender | +Incorporates Tender. | +epo:TenderGroup -> epo:Tender [1..*] | +||||
| epo:comprisesTenderAwardOutcome | +Incorporates TenderAwardOutcome. | +epo:AwardOutcome -> epo:TenderAwardOutcome [0..*] | +||||
| epo:concernsContractAmendment | ++ | epo-con:ContractModificationInformation -> epo-con:ContractAmendment [1] | +||||
| epo:concernsGreenProcurement | ++ | epo:VehicleInformation -> epo:GreenProcurement [1] | +||||
| epo:concernsLot | +Relates to Lot. Relates to Lot. | +epo:LotAwardOutcome -> epo:Lot [1] epo:ProcurementProcessInformation -> epo:Lot [0..1] |
+ ||||
| epo:concernsNotice | ++ | epo:ChangeInformation -> epo:Notice [1] epo:NonPublishedInformation -> epo:Notice [1] |
+ ||||
| epo:concernsProcedure | +Relates to Procedure. Relates to Procedure. + + WG approval 05/03/2024 + | +epo:ProcurementProcessInformation -> epo:Procedure [0..1] epo-acc:ESPDRequest -> epo:Procedure [1] |
+ ||||
| epo:concernsReviewSummaryForLot | +Relates to Lot review summary. + + Additional information: + This relation corresponds in eForms to BT-13722 Buyer Review Lot Identifier. | +epo:ReviewRequestSummary -> epo:Lot [1] | +||||
| epo:concernsTender | ++ | epo:TenderAwardOutcome -> epo:Tender [1] | +||||
| epo:conformsToLegalBasis | +The Notice was designed in accordance with the given legal basis. + + Additional Information: + This Notice can be used for Procedures which do not have the same legal basis. + This holds for standard forms. | +epo:Notice -> at-voc:legal-basis [0..*] | +||||
| epo:containsCandidate | ++ | epo:SelectedCandidateList -> epo:Candidate [0..*] | +||||
| epo:contextualisedBy | +The place of the AgentInRole in the procurement is expressed by a ProcurementObject. | +epo:AgentInRole -> epo:ProcurementObject [0..*] | +||||
| epo:definesBudgetProvider | +Relation indicating a ProcedureTerm has a BudgetProvider. | +epo:ProcedureTerm -> epo:BudgetProvider [0..1] | +||||
| epo:definesCatalogueProvider | +Relation indicating an AccessTerm has a CatalogueProvider. | +epo:AccessTerm -> epo:CatalogueProvider [0..*] | +||||
| epo:definesCatalogueReceiver | +Relation indicating an AccessTerm has a CatalogueReceiver. | +epo:AccessTerm -> epo:CatalogueReceiver [0..*] | +||||
| epo:definesContractDuration | +Relation indicating a ContractTerm has a Duration. | +epo:ContractTerm -> epo:Duration [0..1] | +||||
| epo:definesContractPeriod | +Relation indicating a ContractTerm has a Period. | +epo:ContractTerm -> epo:Period [0..1] | +||||
| epo:definesInformationProvider | +Relation indicating a ProcedureTerm has an information provider. | +epo:ProcedureTerm -> epo:AuxiliaryParty [0..*] | +||||
| epo:definesLotGroup | +Relation indicating a ProcedureTerm has a LotGroup. | +epo:ProcedureTerm -> epo:LotGroup [0..*] | +||||
| epo:definesMediator | +Relation indicating a ProcedureTerm has a Mediator. | +epo:ProcedureTerm -> epo:Mediator [0..1] | +||||
| epo:definesOfflineAccessProvider | +Relation indicating an AccessTerm has an OfflineAccessProvider. | +epo:AccessTerm -> epo:OfflineAccessProvider [0..1] | +||||
| epo:definesOpeningPlace | +The place where the tenders will be publicly opened. + + WG Approval 10-10-2019 | +epo:OpeningTerm -> locn:Address [0..1] | +||||
| epo:definesParticipationRequestProcessor | +Relation indicating a ParticipationRequestTerm has a ParticipationRequestProcessor. | +epo:ParticipationRequestTerm -> epo:ParticipationRequestProcessor [0..1] | +||||
| epo:definesParticipationRequestReceiver | +Relation indicating a ParticipationRequestTerm has a ParticipationRequestReceiver. | +epo:ParticipationRequestTerm -> epo:ParticipationRequestReceiver [0..1] | +||||
| epo:definesPaymentExecutor | +Relation indicating a ContractTerm has a PaymentExecutor. | +epo:ContractTerm -> epo:PaymentExecutor [0..1] | +||||
| epo:definesPrize | +Relation indicating a DesignContestRegimeTerm has a Prize. | +epo:DesignContestRegimeTerm -> epo:Prize [0..*] | +||||
| epo:definesProcurementProcedureInformationProvider | +Relation indicating an AccessTerm has a ProcurementProcedureInformationProvider. | +epo:AccessTerm -> epo:ProcurementProcedureInformationProvider [0..1] | +||||
| epo:definesReviewer | +Relation indicating a ReviewTerm has a Reviewer. | +epo:ReviewTerm -> epo:Reviewer [0..*] | +||||
| epo:definesReviewProcedureInformationProvider | +Relation indicating a ReviewTerm has a ReviewProcedureInformationProvider. | +epo:ReviewTerm -> epo:ReviewProcedureInformationProvider [0..1] | +||||
| epo:definesSpecificPlaceOfPerformance | +Relation indicating a ContractTerm has a specific place of performance. | +epo:ContractTerm -> dct:Location [0..*] | +||||
| epo:definesSubcontractingTerm | +Relation indicating a ContractTerm has a SubcontractingTerm.Relation indicating a + term has a subterm. | +epo:ContractTerm -> epo:SubcontractTerm [0..1] | +||||
| epo:definesTenderProcessor | +Relation indicating a SubmissionTerm has a TenderProcessor. | +epo:SubmissionTerm -> epo:TenderProcessor [0..1] | +||||
| epo:definesTenderReceiver | +Relation indicating a SubmissionTerm has a TenderReceiver. | +epo:SubmissionTerm -> epo:TenderReceiver [0..1] | +||||
| epo:delegatesAncillaryActivitiesTo | +Entrusts ancillary purchasing activities to ProcurementServiceProvider. + + Additional Information: + Directive 2014/24/EU describes ancillary purchasing activities as activities consisting + in the provision of support to purchasing activities, in particular in the following + forms: + + (a) technical infrastructure enabling contracting authorities to award public contracts + or to conclude framework agreements for works, supplies or services; + + (b) advice on the conduct or design of public procurement procedures; + + (c) preparation and management of procurement procedures on behalf and for the account + of the contracting authority concerned; | +epo:Buyer -> epo:ProcurementServiceProvider [0..*] | +||||
| epo:describesDirectAwardPrenotificationNotice | ++ | epo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice [0..1] | +||||
| epo:describesLotCompletion | ++ | epo:ContractLotCompletionInformation -> epo:Lot [1] | +||||
| epo:describesLotGroup | ++ | epo:LotGroupAwardInformation -> epo:LotGroup [1] | +||||
| epo:describesResultNotice | ++ | epo:NoticeAwardInformation -> epo-not:ResultNotice [0..1] | +||||
| epo:distributesOffer | ++ | epo:OfferIssuer -> epo:Offer [0..*] | +||||
| epo:exposesChannel | ++ | epo:AgentInRole -> cv:Channel [0..*] | +||||
| epo:exposesInvoiceeChannel | ++ | epo:Buyer -> cv:Channel [0..*] | +||||
| epo:followsRulesSetBy | ++ | epo:PurchaseContract -> epo:FrameworkAgreement [0..1] | +||||
| epo:foreseesConcession | ++ | epo:Tender -> epo:ConcessionEstimate [0..1] epo:ProcurementObject -> epo:ConcessionEstimate [0..1] |
+ ||||
| epo:foreseesContractSpecificTerm | ++ | epo:ProcurementObject -> epo:ContractSpecificTerm [0..*] | +||||
| epo:foreseesProcurementObject | +Relation indicating the instance of a Procurement Object that is planned. + + Additional Information: + The properties of the Procurement Object that is foreseen should be read as foreseen + properties. + For example, Procedure isSMESuitable should be read as Procedure foreseesToBeSMESuitable. + For example, Procedure isFundedBy should be read as Procedure foreseesToBeFundedBy. | +epo:PlannedProcurementPart -> epo:ProcurementObject [0..1] | +||||
| epo:foreseesSubcontracting | ++ | epo:Tender -> epo:SubcontractingEstimate [0..*] | +||||
| epo:foreseesTechnique | ++ | epo:PlannedProcurementPart -> epo:Technique [0..*] | +||||
| epo:fulfillsRequirement | +The requirement to which the concept meets. + WG Approval 09/11/2021 + The requirement to which the concept meets. + WG Approval 09/11/2021 + + The requirement to which the concept meets. + WG Approval 09/11/2021 + + The requirement to which the concept meets. + WG Approval 09/11/2021 + + | +epo:GreenProcurement -> at-voc:green-public-procurement-criteria [0..*] epo:GreenProcurement -> at-voc:environmental-impact [0..*] epo:InnovativeProcurement -> at-voc:innovative-acquisition [0..*] epo:SocialProcurement -> at-voc:social-objective [0..*] |
+ ||||
| epo:fulfillsStrategicProcurement | ++ | epo:ProcurementObject -> epo:StrategicProcurement [0..*] | +||||
| epo:hasAdditionalClassification | ++ | epo:Purpose -> at-voc:cpv [0..*] | +||||
| epo:hasAdditionalContractNature | +Additional type of acquisition taken into consideration in the contract. + + WG Approval 11/06/2020 + + | +epo:ContractTerm -> at-voc:contract-nature [0..*] | +||||
| epo:hasAllegedIrregularityType | +Additional information: + This relation corresponds in eForms to BT-791 Review Irregularity Type + | +epo:ReviewRequest -> at-voc:irregularity-type [1..*] | +||||
| epo:hasApproximateFrameworkAgreementValue | +The estimated value to be spent within the Framework Agreement(s). - WG Approval 29/08/2019 + Additional information: + In the case of an Award Decision for a Lot, this relation represents the estimated + value for the awarded Framework Agreement. + In the case of a Notice, this relation represents the estimated value for all Framework + Agreements covered by the Notice. + The estimated value to be spent within the Framework Agreement(s). + + Additional information: + In the case of an Award Decision for a Lot, this relation represents the estimated + value for the awarded Framework Agreement. + In the case of a Notice, this relation represents the estimated value for all Framework + Agreements covered by the Notice. | -xsd:integer [0..1] | +epo:LotAwardOutcome -> epo:MonetaryValue [0..1] epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] |
|||
| epo:ChangeInformation | -epo:hasProcurementDocumentChangeDate | -The date and time of the change. + | epo:hasArrivalShipmentInformation | ++ | epo-ful:ShipmentStage -> epo-ful:ShipmentInformation [0..*] | +|
| epo:hasAwardCriterionType | +Category of award criterion. - Additional information: - This corresponds in eForms to BT-719 Change Procurement Documents Date + | +epo:AwardCriterion -> at-voc:award-criterion-type [0..1] | +||||
| epo:hasAwardedValue | +The value of the procurement provided by the Award Decision. + + Additional Information: + Different cases of awarded values may refer to a lot, the global value of the procedure, + or of a combinatorial value of a group of lots. + + In the case of framework agreements and dynamic purchasing systems this refers to + the maximum awarded value. + + WG Approval 10/12/2019 | +epo:AwardOutcome -> epo:MonetaryValue [0..1] | +||||
| epo:hasAwardStatus | +Indicates whether the lot is awarded, not awarded or still open. + WG Approval 03/12/2019 - WG Approval 5/11/2019 | -xsd:dateTime [0..1] | +epo:AwardOutcome -> at-voc:winner-selection-status [0..1] | |||
| epo:AccessTerm | -epo:hasPublicAccessURL | -Web page where the procurement documents can be downloaded. + | epo:hasBargainPrice | +The value of procured supplies that have used a particularly advantageous opportunity + available for a very short time at a value considerably lower than normal market prices. + + WG approval 23/05/2023 | +epo:AwardOutcome -> epo:MonetaryValue [0..1] | +|
| epo:hasBatchID | +The identifier assigned to a specific batch of the produced Item. + WG Approval 16/05/2023 + | +epo-cat:Batch -> adms:Identifier [0..1] | +||||
| epo:hasBeneficialOwner | +A role of any natural person(s) who ultimately owns or controls the organisation or + on whose behalf a transaction or activity is being conducted. + Additional Information: + This role is defined in the directive EU 2015/849 and it's beyond the scope for public + eProcurement domain. + WG approval 14/09/2021 | +epo:Business -> person:Person [0..*] | +||||
| epo:hasBroadPlaceOfPerformance | +Geopolitical zone where the contract can be executed. + + Additional Information + + Used for setting restrictions that cannot be established with one country code or + a geographical zone identifier (like NUTS), because they have a broader scope (geographical, + economic, political, other). + | +epo:ContractTerm -> at-voc:other-place-service [0..1] | +||||
| epo:hasBusinessSize | +The category of the business depending on number of employees and turnover. + + Additional information: + + See Commission Recommendation of 6 May 2003 concerning the definition of micro, small + and medium-sized enterprises. + + WG Approval 28/05/2020 + + | +epo:Business -> at-voc:economic-operator-size [0..1] | +||||
| epo:hasBuyerItemID | +The general identifier assigned to the concept as defined by the Buyer. + + WG approval 16/05/2023 + | +epo-cat:Item -> adms:Identifier [0..1] | +||||
| epo:hasBuyerLegalType | +A category that indicates the right of an Organisation to play the role of a buyer. Additional Information: - This corresponds in the eForms to BT-15 Documents URL. + The category also effects the rules that the buyer has to abide to within the public + procurement procedure. + WG 07/09/2021 - WG Approval 09/03/2021 | -xsd:anyURI [0..1] | +org:Organization -> at-voc:buyer-legal-type [0..1] | |||
| epo:Document | -epo:hasPublicationDate | -Date of formal public issuance of the document. + | epo:hasCertification | +Relation to the proof of conformance. - WG approval 20/06/2023 | -xsd:date [0..1] | + WG approval 30/05/2023 Relation to the proof of conformance. + + WG approval 30/05/2023 Relation to the proof of conformance. + + WG approval 30/05/2023 +foaf:Person -> epo:Certificate [0..*] org:Organization -> epo:Certificate [0..*] epo-cat:Item -> epo:Certificate [0..*] |
| epo:QualificationCriteriaSummary | -epo:hasQualificationCondition | +epo:hasChangeJustification | +Code explaining the change. + + WG Approval 5/11/2019 + The motives for the change. + + WG 5/11/2019 + + The codelist to be used is at-voc:change-corrig-justification which is available at + + http://publications.europa.eu/resource/dataset/change-corrig-justification | +epo:ChangeInformation -> at-voc:change-corrig-justification [1] | +||
| epo:hasConcessionEstimatedValue | - | rdf:PlainLiteral [0..*] | +epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | |||
| epo:MultipleStageProcedureTerm | -epo:hasQualificationSystemRenewalDescription | +epo:hasConfirmedIrregularityType | +Additional information: + This relation corresponds in eForms to BT-791 Review Irregularity Type | +epo:ReviewDecision -> at-voc:irregularity-type [0..*] | +||
| epo:hasConstraint | ++ | cccev:InformationRequirement -> cccev:Constraint [0..*] epo:ProcurementCriterion -> cccev:Constraint [0..*] |
+ ||||
| epo:hasContactPointInRole | - | rdf:PlainLiteral [0..1] | +epo:AgentInRole -> cpov:ContactPoint [0..*] | |||
| epo:Quantity | -epo:hasQuantityValue | -The numeric value of the quantity, including decimals. | -xsd:decimal [1..1] | +epo:hasContractNatureType | +Subject of the acquisition. + + WG Approval 11/06/2020 + + | +epo:ContractTerm -> at-voc:contract-nature [0..1] |
| epo:SubmissionTerm | -epo:hasReceiptDeadline | -The time limit for receiving submissions. + | epo:hasContractValue | ++ | epo:Contract -> epo:MonetaryValue [0..1] | +|
| epo:hasCountryCode | ++ | +dct:Location -> at-voc:country [0..1] locn:Address -> at-voc:country [0..1] |
+ ||||
| epo:hasCountryOfBirth | +The country in which the Person was born. + | +person:Person -> at-voc:country [0..1] | +||||
| epo:hasCurrency | +The identifier of the currency as in the standard code list used. - Additional Information - This is the deadline by which the buyer must receive submissions (e.g. tenders, requests - to participate, clarifications, etc.) and is not the time at which the information - is submitted by the economic operator. - This attribute should be used for standard forms mappings. + | +epo:MonetaryValue -> at-voc:currency [0..1] | +||||
| epo:hasDirectAwardJustification | +List of reasons for using a procedure which allows awarding contracts directly without + publishing a notice. - WG Approval 21/07/2020 + WG Approval 28/05/2020 | -xsd:dateTime [0..1] | +epo:DirectAwardTerm -> at-voc:direct-award-justification [0..1] | |||
| epo:SubmissionTerm | -epo:hasReceiptExpressionDeadline | -Time limit for receipt of expressions of interest. + | epo:hasDocumentRestrictionJustification | +An explanation about the reasons why some procurement documents are restricted. - Pending of review by the WG + Additional Information: + This corresponds in eForms to BT-707 Documents Restricted Justification. + WG Approval 09/03/2021 | -xsd:dateTime [0..1] | +epo:AccessTerm -> at-voc:communication-justification [0..1] |
| epo:SubmissionTerm | -epo:hasReceiptParticipationRequestDeadline | +epo:hasDocumentStatus | +https://test-docs.peppol.eu/logistics/transport-execution/codelist/DocumentStatusCode/ | +epo-cat:PostAwardDocument -> at-voc-new:document-status [0..1] | +||
| epo:hasDPSScope | +Explanation as to whether a dps is used and by whom. + + Additional Information: + This corresponds in eForms to BT-766 Dynamic Purchasing System. + WG Approval 09/11/2021 + Explanation as to whether a dps is used and by whom. + WG Approval 09/11/2021 + + The codelist to be used is at-voc:dps-usage which is available at http://publications.europa.eu/resource/dataset/dps-usage | +epo:DynamicPurchaseSystemTechnique -> at-voc:dps-usage [0..1] | +||||
| epo:hasDriverPerson | - | xsd:dateTime [0..1] | +epo-ful:TransportMeans -> epo-ful:TransportMeansOperator [1..*] | +|||
| epo:hasECataloguePermission | +The extent to which electronic catalogues may be used in tenders. + + WG Approval 03/10/2019 + | +epo:SubmissionTerm -> at-voc:permission [0..1] | +||||
| epo:hasEInvoicingPermission | ++ | epo:ContractTerm -> at-voc:permission [0..1] | +||||
| epo:hasElectronicDigest | ++ | epo:Document -> epo:Document [0..*] | ||||
| epo:SubmissionTerm | -epo:hasReceiptPreliminaryMarketConsultationDeadline | +epo:hasElectronicSignature | - | xsd:dateTime [0..1] | +epo:Document -> epo:ElectronicSignature [0..*] | |
| epo:SubmissionTerm | -epo:hasReceiptTenderDeadline | +epo:hasEndpointIdentifier | - | xsd:dateTime [0..1] | +cv:Channel -> adms:Identifier [0..*] | |
| epo:SubmissionStatisticalInformation | -epo:hasReceivedMicroTenders | -The amount of tenders received from a micro enterprise. + | epo:hasEstimatedBuyerConcessionRevenue | +The expected payments made by the buyer to the economic operator awarded the concession + that are not directly related to the use of the concession. <u>Additional Information:</u> + For example the public buyer pays a yearly fee to provide a ticketing solution to + the public. The fee the public pays for every ticket sold through the solution is + not included in this estimation but in the estimation of the user concession revenue. - See Commission Recommendation 2003/361/EC. | -xsd:integer [0..1] | -|
| epo:SubmissionStatisticalInformation | -epo:hasReceivedParticipationRequests | -The amount of applications to participate from economic operators. + This corresponds to BT-160 in eForms. - WG Approval 12/12/2019 | -xsd:integer [0..1] | + WG Approval 07/01/2020 +epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | ||
| epo:SubmissionStatisticalInformation | -epo:hasReceivedSmallTenders | -Tenders from small enterprise. - - <u>Additional Information:</u> + | epo:hasEstimatedDuration | +Relation indicating a Contract has an estimated Duration. - See Commission Recommendation 2003/361/EC. + Additional Information + When the Lot uses a Technique the contract estimated duration applies to the Technique. | -xsd:integer [0..1] | +epo:Contract -> epo:Duration [0..1] |
| epo:SubmissionStatisticalInformation | -epo:hasReceivedTenders | -The total amount of tenders received. + | epo:hasEstimatedUserConcessionRevenue | +The estimated revenue coming from the use of the concession. - WG Approval 12/12/2019 | -xsd:integer [0..1] | -|
| epo:Document | -epo:hasReceptionDate | -Notes: Date when a record is acknowledged by an organisation. + Additional Information: + Revenues are for example fees and fines. For example, the fees and fines coming from + the cars using a motorway. - WG Approval 12/05/2020 | -xsd:date [0..1] | + This corresponds to BT-162 in eForms. + +epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | ||
| epo:ProcurementObject | -epo:hasRecurrenceDescription | -Any additional information about the recurrence of the Procurement. + | epo:hasEstimatedValue | +A forecast of the value of the procurement before competition. Additional Information: - For example estimated timing of the Procedure. + Different cases of estimated values may refer to a lot, the global value of the procedure, + or of a combinatorial value of a group of lots. + The forecast is calculated by the buyer and covers all revenues whether coming from + the buyer or third parties. + See for example recital (19), Article 5 of Directive 2014/24/EU and other articles + from the rest of Directives about procurement. - This corresponds in eForms to BT-95 Recurrence Description. + In the case of framework agreements and dynamic purchasing systems this refers to + the maximum estimated value. - (WG approval 2019-01-16) - | -rdf:PlainLiteral [0..1] | -|
| epo:CertificationLabel | -epo:hasReferenceURI | -A reference to where the label specification (norms, expectations, standards and policies) - can be found. + This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used + for BT-157 (for LotGroup). + <b> + </b>WG Approval 05/12/2019 + A forecast of the value of the procurement before competition. - WG approval 26/07/2022 | -xsd:anyURI [0..1] | -|||
| epo:ContractTerm | -epo:hasRenewalDescription | -Any other information about the renewal(s). + Additional Information: + Different cases of estimated values may refer to a lot, the global value of the procedure, + or of a combinatorial value of a group of lots. + The forecast is calculated by the buyer and covers all revenues whether coming from + the buyer or third parties. + See for example recital (19), Article 5 of Directive 2014/24/EU and other articles + from the rest of Directives about procurement. - WG approval 16/04/2019 | -rdf:PlainLiteral [0..*] | -|||
| epo:ReviewRequest | -epo:hasRequestDate | -The date when the review request was submitted. + In the case of framework agreements and dynamic purchasing systems this refers to + the maximum estimated value. - Additional information: - This attribute corresponds to the BT-787 Review Date in eForms. - | -xsd:date [0..1] | -|||
| epo:AccessTerm | -epo:hasRestrictedAccessURL | -The internet address with information on accessing the restricted (part of the) procurement - document. + This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used + for BT-157 (for LotGroup). + <b> + </b><b>WG Approval 05/12/2019</b> - Additional Information: - This corresponds in eForms to BT-615 Documents Restricted URL. | -xsd:anyURI [0..1] | +epo:LotGroup -> epo:MonetaryValue [0..1] epo:ProcurementElement -> epo:MonetaryValue [0..1] |
||
| epo:ReviewTerm | -epo:hasReviewDeadline | -The time limit for review procedures. + | epo:hasESubmissionPermission | +The requirements as to what extent electronic submission is allowed. - WG Approval 09/11/2021 | -xsd:dateTime [0..1] | -|
| epo:ReviewTerm | -epo:hasReviewDeadlineInformation | -The description of the time limits for review procedures. + WG Approval 03/10/2019 - WG Approval 01/10/2019 | -rdf:PlainLiteral [0..*] | + +epo:SubmissionTerm -> at-voc:permission [0..1] | ||
| epo:ReviewIrregularitySummary | -epo:hasReviewIrregularityCount | -The number of requests for a given irregularity. + | epo:hasFinancialOfferValue | +The value offered by the Tenderer for a Lot. - Additional information: - This attribute corresponds in eForms to BT-635 Buyer Review Requests Count. | -xsd:integer [1..1] | -|
| epo:ReviewTerm | -epo:hasReviewProcedure | -The description of the method used to request the verification that the procedure - has been carried out correctly. + Additional Information: + This value is normally the one awarded for a winning Tender Lot. In case of negotiated + procedures the original financial value may be reviewed and the offer updated. - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | + This corresponds to BT-720 in eForms. +epo:Tender -> epo:MonetaryValue [0..1] | ||
| epo:ReviewObject | -epo:hasReviewURL | -The internet address of the documents concerning the review instance. + | epo:hasFixedValueType | +The method to interpret the fixed value as pertaining to a total or unit. + + WG Approval 17/09/2019 - Additional information: - This attribute corresponds in eForms to BT-794 Review URL. | -xsd:anyURI [0..1] | -|
| adms:Identifier | -epo:hasScheme | -The name of the identification scheme. | -rdf:PlainLiteral [0..*] | -|||
| adms:Identifier | -epo:hasSchemeVersion | -The version of the identification scheme. | -rdf:PlainLiteral [0..*] | +epo:AwardCriterion -> at-voc:number-fixed [0..1] | ||
| epo:SelectionCriteriaSummary | -epo:hasSelectionCriteriaStatedInProcurementDocuments | -- | xsd:boolean [0..1] | +epo:hasFormType | +A categorisation of the steps in which the Notice is used. + + WG Approval 12/05/2020 + + | +epo:Notice -> at-voc:form-type [0..1] epo-not:Notice1 -> planning [0..1] epo-not:Notice10 -> competition [0..1] epo-not:Notice11 -> competition [0..1] epo-not:Notice12 -> competition [0..1] epo-not:Notice13 -> competition [0..1] epo-not:Notice14 -> competition [0..1] epo-not:Notice15 -> competition [0..1] epo-not:Notice16 -> competition [0..1] epo-not:Notice17 -> competition [0..1] epo-not:Notice18 -> competition [0..1] epo-not:Notice19 -> competition [0..1] epo-not:Notice2 -> planning [0..1] epo-not:Notice20 -> competition [0..1] epo-not:Notice21 -> competition [0..1] epo-not:Notice22 -> competition [0..1] epo-not:Notice23 -> competition [0..1] epo-not:Notice24 -> competition [0..1] epo-not:Notice25 -> dir-awa-pre [0..1] epo-not:Notice26 -> dir-awa-pre [0..1] epo-not:Notice27 -> dir-awa-pre [0..1] epo-not:Notice28 -> dir-awa-pre [0..1] epo-not:Notice29 -> result [0..1] epo-not:Notice3 -> planning [0..1] epo-not:Notice30 -> result [0..1] epo-not:Notice31 -> result [0..1] epo-not:Notice32 -> result [0..1] epo-not:Notice33 -> result [0..1] epo-not:Notice34 -> result [0..1] epo-not:Notice35 -> result [0..1] epo-not:Notice36 -> result [0..1] epo-not:Notice37 -> result [0..1] epo-not:Notice38 -> cont-modif [0..1] epo-not:Notice39 -> cont-modif [0..1] epo-not:Notice4 -> planning [0..1] epo-not:Notice40 -> cont-modif [0..1] epo-not:Notice5 -> planning [0..1] epo-not:Notice6 -> planning [0..1] epo-not:Notice7 -> planning [0..1] epo-not:Notice8 -> planning [0..1] epo-not:Notice9 -> planning [0..1] epo-not:CANDefence-D81 -> Form18 [0..1] epo-not:CANSocial-D25 -> Form6 [0..1] epo-not:CANSocialNotice-D25 -> Form22 [0..1] epo-not:CANStandard-D24 -> Form3 [0..1] epo-not:CNDefence-D81 -> Form17 [0..1] epo-not:CNSocial-D25 -> Form5 [0..1] epo-not:CNSocialNotice-D25 -> Form22 [0..1] epo-not:CNStandard-D24 -> Form2 [0..1] epo-not:ConcessionAwardNotice-D23 -> Form25 [0..1] epo-not:ConcessionNotice-D23 -> Form24 [0..1] epo-not:DesignContest-D24 -> Form12 [0..1] epo-not:DesignContest-D25 -> Form12 [0..1] epo-not:DesignContestResult-D24 -> Form13 [0..1] epo-not:DesignContestResult-D25 -> Form13 [0..1] epo-not:Modification-D23 -> Form20 [0..1] epo-not:Modification-D24 -> Form20 [0..1] epo-not:Modification-D25 -> Form20 [0..1] epo-not:PIN-CFCSocial-D25 -> Form4 [0..1] epo-not:PIN-CFCSocialNotice-D25 -> Form22 [0..1] epo-not:PIN-CFCStandard-D24 -> Form1 [0..1] epo-not:PIN-RTL-D24 -> Form1 [0..1] epo-not:PIN-RTL-D25 -> Form4 [0..1] epo-not:PINDefence-D81 -> Form16 [0..1] epo-not:PINOnly-D24 -> Form1 [0..1] epo-not:PINOnly-D25 -> Form4 [0..1] epo-not:PINProfile-D24 -> Form8 [0..1] epo-not:PINProfile-D25 -> Form8 [0..1] epo-not:PINProfile-D81 -> Form8 [0..1] epo-not:QS-D25 -> Form7 [0..1] epo-not:QSNotice-D25 -> Form22 [0..1] epo-not:SocialAndOtherSpecificServices-D23 -> Form23 [0..1] epo-not:SocialAndOtherSpecificServices-D24 -> Form21 [0..1] epo-not:Subcontract-D81 -> Form19 [0..1] epo-not:VEAT-D23 -> Form15 [0..1] epo-not:VEAT-D24 -> Form15 [0..1] epo-not:VEAT-D25 -> Form15 [0..1] epo-not:VEAT-D81 -> Form15 [0..1] |
| epo:ProfessionalSuitabilitySummary | -epo:hasServiceReservedToParticularProfession | +epo:hasFrameworkAgreementMaximumValue | - | xsd:boolean [0..1] | +epo:LotAwardOutcome -> epo:MonetaryValue [0..1] | |
| epo:SubmissionStatisticalInformation | -epo:hasSMEReceivedTenders | -The amount of tenders received from micro, small and medium-sized enterprises. + | epo:hasFrameworkAgreementType | +The form of framework agreement used in a procurement procedure. - <u>Additional Information:</u> + Addition information: - See Commission Recommendation 2003/361/EC. - The ReceivedSMETenderLots is used when the size of the company is not exactly knokn. + A concept to distinguish the different types of framework agreement, which are: + 1. Framework agreement without reopening of competition, + 2. Framework agreement with reopening of competition, or + 3. Framework agreement partly without reopening of competition. + + WG Approval 19/09/2019 - WG Approval 05/03/2020 | -xsd:integer [0..1] | +epo:FrameworkAgreementTerm -> at-voc:framework-agreement [1] |
| epo:SubmissionStatisticalInformation | -epo:hasSMEReceivedTendersExcludingSubcontractors | +epo:hasFundProgramme | - | xsd:integer [0..1] | +epo:Fund -> at-voc:EU-programme [0..1] | |
| epo:StrategicProcurement | -epo:hasStrategicProcurementDescription | -Self-explanatory text about a concept. - | -rdf:PlainLiteral [0..*] | +epo:hasGroupFrameworkAgreementMaximumValue | +This corresponds to BT-156 in the eForms. | +epo:LotGroupAwardInformation -> epo:MonetaryValue [0..1] |
| epo:SubcontractTerm | -epo:hasSubcontractingInvolved | -List of Subcontractors and the subject matter they cover are required. - - Additional Information: - The tenderer will ned to supply this information in the tender. + | epo:hasHighestReceivedTenderValue | +Amount of the Tender with the highest value. - WG Approval 28/02/2019 | -xsd:boolean [0..1] | -|
| epo:SubcontractTerm | -epo:hasSubcontractorsProposedAboveObligation | -The maximum percentage of the contract value that the contractor must subcontract. + Additional Information + The value must correspond to an admissible tender. For example, tenders compliant + with the procurement document requirements, not having an abnormally low price or + cost, etc. - Additional information: - This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + WG Approval 12/12/2019 - WG Approval 09/11/2021 | -xsd:decimal [0..1] | + + +epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1] | ||
| epo:SubcontractingEstimate | -epo:hasSubjectMatter | -Description of the share of the contract that is to be subcontracted. - - Additional infromation: - This can be an aggregate of several subcontracts. - - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo:hasImplementingRegulation | ++ | epo-not:StandardFormsNotice -> (EU) 2015/1986 [0..1] epo-not:eFormsNotice -> (EU) 2019/1780 [0..1] |
| epo:SubmissionTerm | -epo:hasSubmissionURL | -- Additional Information: - This corresponds to the eForms BT-18 Submission URL. - - This corresponds in eForms to BT-509 Organisation eDelivery Gateway. | -xsd:anyURI [0..*] | +epo:hasInternalIdentifier | ++ | epo:LotGroup -> adms:Identifier [0..*] epo:ProcurementElement -> adms:Identifier [0..*] |
| epo:MultipleStageProcedureTerm | -epo:hasSuccessiveReduction | -The number of solutions or tenders will be reduced in iterative evaluations for multiple - staged procedures. - - Additional information: - This refers to multiple-stage procedures (included two-stage procedures, at least). - Open Procedures can be seen as one-stage procedures. - WG Approval 22/08/2019 | -xsd:boolean [0..1] | +epo:hasIrregularityType | +Additional information: + This relation corresponds in eForms to BT-636 Buyer Review Requests Irregularity + Type | +epo:ReviewIrregularitySummary -> at-voc:irregularity-type [1] |
| cccev:Constraint | -epo:hasThresholdValue | -The cut-off level for a given concept. + | epo:hasItemCountryOfOrigin | +The source country of the product or service. Additional Information: - This value is given as e.g. a minimum score, a maximum number of tenders with the - highest score passing (see codelist at-voc:number-threshold). | -xsd:decimal [1..1] | -|
| epo:ReviewRequestSummary | -epo:hasTotalNumberOfComplainants | -The number of economic operators that requested the buyer to review any of its decisions - (e.g. the technical specifications, award decision), as set out in Art. 1(5) of Directive - 89/665/EEC and Directive 92/13/EEC. - Additional information: - This attribute corresponds in eForms to BT-712 Buyer Review Complainants + The country of origin can be provided by the buyer as a requirement or by the tenderer + information of the item to be provided. - WG Approval 11/04/2019 | -xsd:integer [0..1] | + WG Approval 07/01/2020 + + The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country +epo:Tender -> at-voc:country [0..*] | ||
| epo:VehicleInformation | -epo:hasTotalVehicles | -The number of all vehicles (regardless of whether clean or not) that have either been - purchased, leased, rented, hired-purchased or their use has been contractually committed - to for the provision of a purchased service. + | epo:hasItemStandardID | +The general identifier assigned to the concept based on a standard scheme. - Additional Information - - In the European Union, the legal requirements and scope for the provision of these - vehicles or services are covered by Directive 2009/33/EC. + Additional information: + For example the GTIN scheme (Global Trade Item Number). - WG Approval 28/07/2020 - | -xsd:integer [0..1] | + WG approval 16/05/2023 +epo-cat:Item -> adms:Identifier [0..*] |
| epo:Quantity | -epo:hasUnitDescription | -A narrative explanation defining the units of items being counted - - Additional information: This could be for example individual items or pack or two. - - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo:hasLabelType | +The label type such environmental, quality, social etc. | +epo:CertificationLabel -> at-voc-new:certification-label-type [0..1] |
| epo:SubmissionStatisticalInformation | -epo:hasUnverifiedTenders | -Offers received for which it has not been verified if they are admissible or inadmissible - (e.g. because award criteria have been evaluated for all tenders and admissibility - is checked only for the winning tender). + | epo:hasLanguage | +Language in which the submitted information is to be expressed. + + WG Approval 21/07/2020 - WG Approval 28/07/2020 | -xsd:integer [0..1] | +epo:SubmissionTerm -> at-voc:language [0..*] |
| cccev:Evidence epo:Fund |
- epo:hasURL | -The identifier of a resource. + | epo:hasLateSubmissionPermission | +Whether economic operator-related information can be supplemented even after the submission + deadline. Additional Information + This is specific to the information on the economic operator and not the actual offer. + This does not apply to the requests for clarification. - For example: + WG Approval 21/07/2020 + | +epo:SubmissionTerm -> at-voc:missing-info-submission [0..1] | +|
| epo:hasLaunchFrameworkAgreementMaximumValue | ++ | epo:ProcurementObject -> epo:MonetaryValue [0..1] epo:LotGroup -> epo:MonetaryValue [0..1] |
+ ||||
| epo:hasLegalBasis | +The legal basis under which the procurement procedure takes place. - 1. The URL of the system from where to access the procurement documents; - 2. The URL of the system for the submission of tender documents; - 3. The URL of the system from where to download a tool to communicate with the Buyer; - 4. The URL of the system used by a Technique to allow Economic Operators to exchange - information with the Buyer (e.g. eAuction and DPS Systems) - 5. The URL of the system used to exchange information between Buyer and EO for questions - and clarifications; + Additional Information: + For example European Directives or Regulations, national laws etc. + The recommended code list is the example for the legal basis at the European level. - WG Approval 30/09/2019 - The identifier of a resource. + WG 04/04/2023 - Additional Information + The legal basis under which the procurement procedure takes place. - For example: + Additional Information: + For example European Directives or Regulations, national law - 1. The URL of the system from where to access the procurement documents; - 2. The URL of the system for the submission of tender documents; - 3. The URL of the system from where to download a tool to communicate with the Buyer; - 4. The URL of the system used by a Technique to allow Economic Operators to exchange - information with the Buyer (e.g. eAuction and DPS Systems) - 5. The URL of the system used to exchange information between Buyer and EO for questions - and clarifications; + WG 09/11/2021 - WG Approval 30/09/2019 | -xsd:anyURI [0..1] xsd:anyURI [0..1] |
+ The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis
+
+ epo:ProcurementObject -> at-voc:legal-basis [0..*] epo-not:VEAT-D23 -> Directive 23 [0..1] epo-not:Notice35 -> Directive 23 [0..1] epo-not:Modification-D23 -> Directive 23 [0..1] epo-not:Notice32 -> Directive 23 [0..1] epo-not:Notice19 -> Directive 23 [0..1] epo-not:ConcessionNotice-D23 -> Directive 23 [0..1] epo-not:ConcessionAwardNotice-D23 -> Directive 23 [0..1] epo-not:Notice40 -> Directive 23 [0..1] epo-not:Notice28 -> Directive 23 [0..1] epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 [0..1] epo-not:Notice14 -> Directive 23 [0..1] epo-not:Notice10 -> Directive 24 [0..1] epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 [0..1] epo-not:VEAT-D24 -> Directive 24 [0..1] epo-not:PINOnly-D24 -> Directive 24 [0..1] epo-not:Notice25 -> Directive 24 [0..1] epo-not:Notice23 -> Directive 24 [0..1] epo-not:CNStandard-D24 -> Directive 24 [0..1] epo-not:PIN-CFCStandard-D24 -> Directive 24 [0..1] epo-not:Notice29 -> Directive 24 [0..1] epo-not:Notice38 -> Directive 24 [0..1] epo-not:Notice36 -> Directive 24 [0..1] epo-not:Notice1 -> Directive 24 [0..1] epo-not:DesignContestResult-D24 -> Directive 24 [0..1] epo-not:Notice33 -> Directive 24 [0..1] epo-not:CANStandard-D24 -> Directive 24 [0..1] epo-not:DesignContest-D24 -> Directive 24 [0..1] epo-not:PIN-RTL-D24 -> Directive 24 [0..1] epo-not:Notice20 -> Directive 24 [0..1] epo-not:PINProfile-D24 -> Directive 24 [0..1] epo-not:Notice12 -> Directive 24 [0..1] epo-not:Notice4 -> Directive 24 [0..1] epo-not:Notice16 -> Directive 24 [0..1] epo-not:Notice7 -> Directive 24 [0..1] epo-not:Modification-D25 -> Directive 25 [0..1] epo-not:Notice26 -> Directive 25 [0..1] epo-not:CNSocial-D25 -> Directive 25 [0..1] epo-not:PIN-CFCSocial-D25 -> Directive 25 [0..1] epo-not:PINOnly-D25 -> Directive 25 [0..1] epo-not:Notice2 -> Directive 25 [0..1] epo-not:PINProfile-D25 -> Directive 25 [0..1] epo-not:PIN-RTL-D25 -> Directive 25 [0..1] epo-not:Notice37 -> Directive 25 [0..1] epo-not:VEAT-D25 -> Directive 25 [0..1] epo-not:CANSocialNotice-D25 -> Directive 25 [0..1] epo-not:QSNotice-D25 -> Directive 25 [0..1] epo-not:QS-D25 -> Directive 25 [0..1] epo-not:DesignContestResult-D25 -> Directive 25 [0..1] epo-not:CNSocialNotice-D25 -> Directive 25 [0..1] epo-not:Notice34 -> Directive 25 [0..1] epo-not:Notice24 -> Directive 25 [0..1] epo-not:CANSocial-D25 -> Directive 25 [0..1] epo-not:Notice30 -> Directive 25 [0..1] epo-not:Notice8 -> Directive 25 [0..1] epo-not:Notice13 -> Directive 25 [0..1] epo-not:Notice5 -> Directive 25 [0..1] epo-not:Notice39 -> Directive 25 [0..1] epo-not:Notice21 -> Directive 25 [0..1] epo-not:Notice15 -> Directive 25 [0..1] epo-not:Notice17 -> Directive 25 [0..1] epo-not:DesignContest-D25 -> Directive 25 [0..1] epo-not:Notice11 -> Directive 25 [0..1] epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 [0..1] epo-not:VEAT-D81 -> Directive 81 [0..1] epo-not:PINProfile-D81 -> Directive 81 [0..1] epo-not:Notice6 -> Directive 81 [0..1] epo-not:PINDefence-D81 -> Directive 81 [0..1] epo-not:Subcontract-D81 -> Directive 81 [0..1] epo-not:Notice27 -> Directive 81 [0..1] epo-not:Notice22 -> Directive 81 [0..1] epo-not:CNDefence-D81 -> Directive 81 [0..1] epo-not:Notice18 -> Directive 81 [0..1] epo-not:CANDefence-D81 -> Directive 81 [0..1] epo-not:Notice3 -> Directive 81 [0..1] epo-not:Notice9 -> Directive 81 [0..1] epo-not:Notice31 -> Directive 81 [0..1] |
|||
| epo:Document | -epo:hasVersion | -A number that identifies a specific state of a document. - - WG approval: 18/11/2021 - | -rdf:PlainLiteral [0..1] | +epo:hasLegalIdentifier | ++ | org:Organization -> adms:Identifier [0..*] |
| epo:ReviewRequest | -epo:hasWithdrawalDate | -The date and time when the request for review was withdrawn. - - Additional information: - This attribute corresponds in eForms to BT-797 Review Request Withdrawn Date. | -xsd:date [0..1] | +epo:hasLotReference | ++ | epo:Contract -> epo:Lot [1..*] |
| epo:ReviewRequest | -epo:hasWithdrawalReason | -The explanation for withdrawing the request for review. + | epo:hasLowestReceivedTenderValue | +Amount of the Tender with the lowest value. - Additional information: - This attribute corresponds in eForms to BT-798 Review Request Withdrawn Reasons | -rdf:PlainLiteral [0..1] | + Additional Information + The value must correspond to an admissible tender. For example, tenders compliant + with the procurement document requirements, not having an abnormally low price or + cost, etc. + + WG Approval 12/12/2019 + + +epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1] |
| epo:VehicleInformation | -epo:hasZeroEmissionVehicles | -The number of all zero-emission heavy-duty vehicles that have either been purchased, - leased, rented, hired-purchased or their use has been contractually committed to for - the provision of a purchased service. + | epo:hasMainActivity | +The principal sectoral area in which an organisation operates. - Additional Information + Additional information: - In the European Union, the legal requirements and scope for the provision of these - vehicles or services are covered by Directive 2009/33/EC. + The activities associated with buyers are derived from the top level of the Classification + of the functions of the government (COFOG) from the United Nations Statistics Division. + + The activities associated with buyer are derived from sectors explicitly falling within + the sectoral directive (2014/25/EU Art. 8 - Art. 14). + + WG Approval 05/05/2020 - WG Approval 28/07/2020 | -xsd:integer [0..1] | +org:Organization -> at-voc:main-activity [0..1] |
| epo:ProcurementCriteriaSummary | -epo:indicatesPerformingStaffInformationRequirement | +epo:hasMainClassification | - | xsd:boolean [0..1] | +epo:Purpose -> at-voc:cpv [1..*] | |
| epo:Procedure | -epo:isAccelerated | -Statement about the fact that the procedure will be reduced due to a state of urgency. + | epo:hasManufacturerID | +The manufacturer's identifier for the item. + | +epo-cat:Manufacturer -> adms:Identifier [0..1] | +|
| epo:hasManufacturerItemID | +The general identifier assigned to the concept as defined by the Manufacturer. - Additional Information + WG approval 16/05/2023 + | +epo-cat:Item -> adms:Identifier [0..1] | +||||
| epo:hasMaximumFrameworkAgreementAwardedValue | +The maximum value which can be spent through all the framework agreements announced + in this notice, including options and renewals of contracts. - This modifies the time limit for the receipt of requests to participate or the receipt - of tenders. + Additional information: - WG Approval 20/08/2019 - | -xsd:boolean [0..1] | + The value provided is a threshold value that implicity means that it cannot be exceeded + however it may not be reached during the execution of a contract. + + The Framework Agreements in a CAN are to be traced back and added to provide this + value. + + This corresponds to the BT-118 in eForms. + + WG Approval 03/12/2019 +epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +|||
| epo:hasMember | ++ | epo:OrganisationGroup -> org:Organization [1..*] | ||||
| epo:SubmissionTerm | -epo:isAdvancedElectronicSignatureRequired | -Advanced or qualified electronic signature or seal (as defined in Regulation (EU) - No 910/2014) is required. + | epo:hasModificationJustification | +Explanation of why a contract was modified. + WG Approval 09/11/2021 + The codelist to be used is at-voc:modification-justification which is available at + http://publications.europa.eu/resource/dataset/modification-justification - The submitted information is required to be signed electronically. + Additional Information - Additional Information: + This corresponds in Standard forms to Field VII.2.2.1 and VII.2.2.3 in F20 . + + This corresponds in eForms to BT-200. - Signature can be defined as "data in electronic form which is attached to or logically - associated with other data in electronic form and which is used by the signatory to - sign. - For more details on the meaning and uses of electronic signature you may consult different - authoritative sources, a relevant one being for instance the Regulation (EU) 910/2014 - on electronic identification and trust services for electronic transactions in the - internal market. - WG Approval 21/07/2020 | -xsd:boolean [0..1] | +epo-con:ContractModificationInformation -> at-voc:modification-justification [1] |
| epo:ProcedureTerm | -epo:isAwardedByCPB | -Procedure is awarded by a Central Purchasing Body. - + | epo:hasNationality | +- | xsd:boolean [0..1] | +person:Person -> at-voc:country [0..*] |
| epo:ProcurementProcessInformation | -epo:isCompetitionTerminated | -No further contracts will be awarded in this procedure. - - Additional Information: - This can be instantiated in the post award phase. + | epo:hasNonAwardJustification | +On hold; Enumeration. - PIN for Competition needs to be signaled. This field can be used even if no contracts - are awarded in the contract award notice. - This corresponds in eForms to BT-756 PIN Competition Termination. | -xsd:boolean [0..1] | + +epo:AwardOutcome -> at-voc:non-award-justification [0..1] |
| epo:Buyer | -epo:isContractingEntity | -Role of entities, which: - - (a) are contracting authorities or public undertakings and which pursue one of the - activities referred to in Articles 8 to 14 of the Directive 2014/25/EU. - - (b) when they are not contracting authorities or public undertakings, have as one - of their activities any of the activities referred to in Articles 8 to 14, or any - combination thereof and operate on the basis of special or exclusive rights granted - by a competent authority of a Member State. + | epo:hasNonElectronicSubmissionJustification | ++ Reason for not accepting electronic information. - Additional Information + WG Approval 21/07/2020 + | +epo:SubmissionTerm -> at-voc:communication-justification [0..*] | +|
| epo:hasNonPublicationJustification | +The reason why data is not published. + WG Approval 11/06/2020 + | +epo:NonPublishedInformation -> at-voc:non-publication-justification [1] | +||||
| epo:hasNoticeType | ++ | epo:Notice -> at-voc:notice-type [1] epo-not:CANSocialNotice -> can-social [1] epo-not:CANStandardNotice -> can-standard [1] epo-not:CNSocialNotice -> cn-social [1] epo-not:CNStandardNotice -> cn-standard [1] epo-not:CompletionNotice -> compl [1] epo-not:ContractModificationNotice -> can-modif [1] epo-not:DesignContestNotice -> cn-desg [1] epo-not:DesignContestResultNotice -> can-desg [1] epo-not:PIN-CFCSocialNotice -> pin-cfc-social [1] epo-not:PIN-CFCStandardNotice -> pin-cfc-standard [1] epo-not:PINOnlyNotice -> pin-only [1] epo-not:PINProfileNotice -> pin-buyer [1] epo-not:PINTimeLimitNotice -> pin-rtl [1] epo-not:PreMarketConsultationNotice -> pmc [1] epo-not:QSNotice -> qu-sy [1] epo-not:SubcontractNotice -> subco [1] epo-not:VoluntaryEx-AnteTransparencyNotice -> veat [1] |
+ ||||
| epo:hasNutsCode | ++ | dct:Location -> at-voc:nuts [0..1] locn:Address -> at-voc:nuts [0..1] |
+ ||||
| epo:hasOfficialLanguage | +The language(s) in which the instances of the given concepts are officially available. + These linguistic versions are equally legally valid. - The indicator is needed in order to discriminate between those contracts where the - Contracting Entity acts as a Contracting Authority undergoing the limits and the rules - of Directive 24 and those where it acts as a Contracting Entity, with certain relaxed - constraints. - For example, the Contracting Entities have different thresholds for the application - of Directive 24 if compared with Contracting Authorities. + WG Approval 03/10/2019 - WG Approval 28/04/2020 | -xsd:boolean [0..1] | +epo:Document -> at-voc:language [1..*] | |||
| epo:ProcurementObject | -epo:isCoveredByGPA | -Specifies whether the Agreement on Government Procurement (GPA) applies. - + | epo:hasPerformingStaffQualificationInformation | +Additional information: - The GPA aims to establish a multilateral framework of balanced rights and obligations - relating to public contracts with a view to achieving the liberalization and expansion - of world trade. - - This corresponds in the e Forms to BT-115 GPA Coverage. - WG Approval 15/10/2019 + This relation corresponds in eForms to BT-79.Explanation as to if and/or when information + of the persons to carry out the contract is to be provided. + WG Approval 09/11/2021 + The codelist to be used is at-voc:requirement-stage which is available at http://publications.europa.eu/resource/dataset/requirement-stage | -xsd:boolean [0..1] | +epo:ProcurementCriterion -> at-voc:requirement-stage [0..*] |
| epo:Procedure | -epo:isDesignContest | -A competition which enables the buyer to acquire a plan or design via a jury. + | epo:hasPlannedDuration | ++ | epo:PlannedProcurementPart -> epo:Duration [0..1] | +|
| epo:hasPlannedPeriod | ++ | epo:PlannedProcurementPart -> epo:Period [0..1] | +||||
| epo:hasPriceSurchargeInformation | ++ | epo-cat:Price -> epo-cat:ChargeInformation [0..1] | +||||
| epo:hasPrimaryContactPoint | ++ | org:Organization -> cpov:ContactPoint [0..1] | +||||
| epo:hasPrizeValue | +The monetary value of a prize, if any, for the winner (or runners-up) of the design + contest. - Additional information: - Design contests have traditionally mostly been used in the fields of town and country - planning, architecture and engineering or data processing, other purposes, such as - to obtain plans for financial engineering + Additional Information: + This corresponds to BT-644 in eForms. - The contest may include or not the award of prizes; + WG Approval 29/08/2019 - WG approval 04-02-2021 | -xsd:boolean [0..1] | + +epo:Prize -> epo:MonetaryValue [0..1] | |||
| epo:ProcurementProcessInformation | -epo:isDPSTerminated | -End of the Dynamic Purchase System (DPS). - - Additional Information: This property can be used in the contract award notice even - if no contracts are awarded. + | epo:hasProcedureType | +Identification of the Procedure used. - WG Approval 22/11/2019 + WG Approval 09/06/2020 | -xsd:boolean [0..1] | +epo:Procedure -> at-voc:procurement-procedure-type [1] |
| epo:SubmissionTerm | -epo:isGuaranteeRequired | -The submitted information must include a financial commitment to be used in case of - default. + | epo:hasProcurementHighestReceivedTenderValue | +The highest received tender value for the procurement. Additional Information: - See the additional information provided in the definition of the 'Guarantee Description' - element. + This corresponds to section II.1.7.3. according to Regulation (EU) 2015/1986. | +epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +|
| epo:hasProcurementLowestReceivedTenderValue | +The lowest received tender value for the procurement. - WG Approval 21/07/20 + Additional Information: + This corresponds to section II.1.7.2. according to Regulation (EU) 2015/1986. | +epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +||||
| epo:hasProcurementScopeDividedIntoLot | ++ | epo:Procedure -> epo:Lot [1..*] | +||||
| epo:hasPurpose | +Relation indicating the Purpose of a concept. | +epo:Contract -> epo:Purpose [0..1] epo:ProcurementObject -> epo:Purpose [0..1] |
+ ||||
| epo:hasQualificationSystemDuration | ++ | epo:MultipleStageProcedureTerm -> epo:Duration [0..1] | +||||
| epo:hasReceivedSubmissionType | ++ | epo:SubmissionStatisticalInformation -> at-voc:received-submission-type [0..1] | +||||
| epo:hasRegistrationCountry | ++ | org:Organization -> at-voc:country [0..1] | +||||
| epo:hasRejectedQuantity | ++ | epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] | +||||
| epo:hasRemedyValue | +Additional information: + This relation corresponds in eForms to BT-793 Review Remedy Value. | +epo:ReviewDecision -> epo:MonetaryValue [0..1] | +||||
| epo:hasReservedExecution | ++ | epo:ContractTerm -> at-voc:applicability [0..1] | +||||
| epo:hasReservedProcurement | +Explanation as to whether a procurement may be reserved for the participation of certain + types of organisation. + Additional information: + This property corresponds in eForms to the BT-71 + WG Approval 09/11/2021 + Explanation as to whether a procurement may be reserved for the participation of certain + types of organisation. + + Additional information: + This property corresponds in eForms to the BT-71 + WG Approval 09/11/2021 | -xsd:boolean [0..1] | +epo:ParticipationCondition -> at-voc:reserved-procurement [0..*] epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*] |
|||
| epo:Procedure | -epo:isJointProcurement | -Multiple buyers procure together within the same procedure. - - Addition Information: - In case the joint procurement involves buyers from different countries, the national - law is specified by the epo:hasCrossBorderLaw in the ProcedureTerm . | -xsd:boolean [0..1] | +epo:hasResourceType | ++ | eli:LegalResource -> at-voc:resource-type [1..*] | +
| epo:hasReviewBodyType | ++ | epo:Reviewer -> at-voc:review-body-type [0..*] | +||||
| epo:hasReviewDecisionType | +Additional information: + This relation corresponds in eForms to BT-790 Review Decision Type. | +epo:ReviewDecision -> at-voc:review-decision-type [0..*] | +||||
| epo:hasReviewIrregularitySummary | +Additional information: + This relation corresponds in eForms to BG-613 Buyer Review Requests | +epo:ReviewRequestSummary -> epo:ReviewIrregularitySummary [0..*] | +||||
| epo:hasReviewRequestFee | +Additional information: + This relation corresponds in eForms to BT-795 Review Request Fee. | +epo:ReviewRequest -> epo:MonetaryValue [0..1] | ||||
| epo:DesignContestRegimeTerm | -epo:isJuryDecisionBinding | -Indicates whether the procuring entity is bound to apply the decision of the jury. | -xsd:boolean [0..1] | +epo:hasSelectionCriteriaUsage | ++ Additional Information: + This corresponds in eForms to BT-748 Selection Criteria Used. | +epo:SelectionCriterion -> at-voc:usage [0..1] |
| epo:Business | -epo:isListedCompany | -Public companies listed on a stock exchange and subject to disclosure requirements - (either by stock exchange - rules or through law or enforceable means), which impose requirements to ensure adequate - transparency of - beneficial ownership. - - <u>Additional Information:</u> + | epo:hasSelectionCriterionType | +The classification of the selection criteria. - In eForms this indicator is used when the nationality of beneficial owner is not provided - because the Economic Operator is registered in a regulated market that is subject - to disclosure requirements consistent with Union law or subject to equivalent international - standards which ensure adequate transparency of ownership information. - WG Approval 21/11/2019 | -xsd:boolean [0..1] | -|
| epo:SubmissionTerm | -epo:isMultipleTenderSubmissionAllowed | -Tenderers may submit more than one competing tenders. + Additional Information: - WG Approval 10/10/2019 + This corresponds in eForms to BT-747 Selection Criteria Type. + WG Approval 09/11/2021 | -xsd:boolean [0..1] | +epo:SelectionCriterion -> at-voc:selection-criterion [0..1] | ||
| epo:NonDisclosureAgreementTerm | -epo:isNonDisclosureAgreementRequired | -- | xsd:boolean [0..1] | +epo:hasSellerItemID | +The general identifier assigned to the concept as defined by the Seller. + + WG approval 16/05/2023 + | +epo-cat:Item -> adms:Identifier [0..1] |
| epo:ProcedureTerm | -epo:isOneLotOnlyAllowed | -Indicates whether tenders may be submitted for only one Lot. - - Additional information: - This field is used to complement the SubmissionTerms (which are at the Lot level) - for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled - in the TED Standard Forms). - - WG approval 23/08/2022 - + | epo:hasSerialID | +The identifier assigned to the specific instance of the produced concept. + WG Approval 16/05/2023 | -xsd:boolean [0..1] | +epo-cat:Item -> adms:Identifier [0..1] |
| epo:ChangeInformation | -epo:isProcurementDocumentChanged | -One or more procurement documents have been changed. - - Additional information: - This corresponds in eForms to BT-718 Change Procurement Documents - - WG Approval 05/11/2019 | -xsd:boolean [0..1] | +epo:hasStartDate | ++ | epo:SelectedCandidateList -> epo:Period [0..1] |
| epo:AccessTerm | -epo:isProcurementDocumentRestricted | -The access to certain procurement documents is restricted. - - Additional Information: - This corresponds in eForms to BT-14 Documents Restricted. - - WG Approval 10/10/2019 | -xsd:boolean [0..1] | +epo:hasSubcontracting | ++ | epo:Tender -> at-voc:applicability [0..1] |
| epo:ProcurementObject | -epo:isRecurrent | -The Procurement being notified is likely to be included in another procedure in the - foreseeable future. + | epo:hasSubcontractingEstimatedValue | +The estimated value of a single subcontract. - Additional Information: + This relates to BT-553 in eForms. - For example, a regularly re-tendered municipal service. This does not include awarding - multiple contracts within a single qualification system, framework agreement, or a - dynamic purchasing system. + WG Approval 01/09/2020 - This corresponds in eForms to BT-94 Recurrence. + | +epo:SubcontractingEstimate -> epo:MonetaryValue [0..1] | +|
| epo:hasSubcontractingObligation | +The requirement the tender must meet with regard to subcontracting parts of the contract. + WG Approval 09/11/2021 - WG Approval 12/05/2020 | -xsd:boolean [0..1] | +epo:SubcontractTerm -> at-voc:subcontracting-obligation [0..*] | |||
| epo:ContractTerm | -epo:isRenewalIndicator | -Indicates whether the contract is subject to a renewal clause. - WG Approval 09/11/2021 | -xsd:boolean [0..1] | +epo:hasSubdivision | ++ | eli:LegalResourceSubdivision -> at-voc:subdivision [0..1] |
| epo:SecurityClearanceTerm | -epo:isSecurityClearanceRequired | +epo:hasTaxIdentifier | - | xsd:boolean [0..1] | +org:Organization -> adms:Identifier [0..*] | |
| epo:ProcurementObject | -epo:isSMESuitable | -The Lot is suitable for small and medium enterprises (SMEs). - - Additional Information - - This allows the buyer to make emphasis on the fact that the procedure has been designed - having SMEs in mind. This indicator is also to be reflected in the selection criteria. + | epo:hasTenderSubcontractingInformation | +The information about subcontracting that must be indicated in the tender. - For example, number of employees and turnover are applicable to the definition of - an SME. + WG Approval 10/10/2019 - WG Approval 15/10/2019 | -xsd:boolean [0..1] | +epo:SubmissionTerm -> at-voc:subcontracting-indication [0..*] |
| epo:ProcedureTerm | -epo:isSubmissionForAllLotsRequired | -Indicates whether tenders must be submitted for all Lots. + | epo:hasTenderValidityDuration | ++ | epo:SubmissionTerm -> epo:Duration [0..1] | +|
| epo:hasTenderValidityPeriod | +The relation indicating until when a tender instance is applicable. | -xsd:boolean [0..1] | +epo:SubmissionTerm -> epo:Period [0..1] | |||
| epo:ProcurementProcessInformation | -epo:isToBeRelaunched | -Indicator of whether the procurement object is to be relaunched. - - Additional information: - This can be instantiated in the post award phase. - - This corresponds in eForms to BT-634 Procurement Relaunch. + | epo:hasThresholdType | +The method to interpret the threshold value as minimum or a maximum. - WG Approval: 18/01/2022 + WG Approval 17/09/2019 | -xsd:boolean [0..1] | +cccev:Constraint -> at-voc:number-threshold [0..*] |
| epo:SelectionCriterion | -epo:isUsedForCandidateRestriction | -The criterion will be used to select the candidates to be invited for the second stage - of a multistage procedure. + | epo:hasTimePeriod | +- Additional Information: - This property is only used if a maximum number of candidates was foreseen in the procedure. - This corresponds in eForms to BT-40 Selection Criteria Second Stage Invite | -xsd:boolean [0..1] | + +epo:Period -> at-voc:timeperiod [1..*] |
| epo:ProcurementObject | -epo:isUsingEUFunds | -The procurement foresees funding by the Union. + | epo:hasTotalAwardedValue | +The awarded value of all lots announced in this notice, including options and renewals. - Additional Information: - The funding may cover the whole procurement or part of the procurement. - For example the European Structural and Investment Funds or grants awarded by the - European Union. + Additional information: + The values of the individual Lots awarded under a framework agreement and mentioned + in this notice are included. + + The values of the individual lots announced in a CAN are to be traced back and added + to provide this value. + + This corresponds to the BT-161 in eForms. + WG Approval 03/12/2019 | -xsd:boolean [0..1] | +epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] |
| epo:Tender | -epo:isVariant | -Alternative solution to fulfil the buyer's needs as opposed to solutions indicated - in the procurement documents. + | epo:hasTotalQuantity | +The number of units required. Additional Information: + The quantity needs to go along with the unit. - The permission to offer variants is only allowed if specified in a Contract Notice - or a Prior Information Notice that used as a means for calling for a competition. - The buyer lays out minimum requirements in the procurement documents that must be - respected by tenderers submitting variants. - WG Approval 29/05/2019 | -xsd:boolean [0..1] | +epo:Purpose -> epo:Quantity [0..1] |
| epo:ReviewRequest | -epo:isWithdrawn | -The review request was withdrawn. - - Additional information: - This attribute corresponds in eForms to BT-796 Review Request Withdrawn. | -xsd:boolean [0..1] | +epo:hasTotalValue | ++ | epo:TenderGroup -> epo:MonetaryValue [0..1] epo-con:Deliverable -> epo:MonetaryValue [0..1] |
| epo:GreenProcurement | -epo:usesCleanVehicleDirective | -The procurement falls within the scope of the European Parliament and Council 2009/33/EC - (Clean Vehicles Directive – CVD). | -xsd:boolean [0..1] | +epo:hasUnitCode | ++ | epo:Quantity -> at-voc:measurement-unit [1] |
| person:Person | -foaf:familyName | -The hereditary surname of a family. + | epo:hasUnofficialLanguage | +The language translation(s) in which the instances of the given concepts are available. + These linguistic versions are not an official translation, they are provided only + for information. + + WG Approval 03/10/2019 | -rdf:PlainLiteral [0..*] | +epo:Document -> at-voc:language [0..*] |
| person:Person | -foaf:givenName | -The name(s) that identify the Person within a family with a common surname. + | epo:hasUsage | +The codelist to be used is at-voc:usage which is available at http://publications.europa.eu/resource/dataset/usage | -rdf:PlainLiteral [0..*] | -|
| person:Person | -foaf:name | -The complete name of the Person as one string. | -rdf:PlainLiteral [0..*] | -|||
| locn:Address | -locn:addressArea | -The name or names of a geographic area or locality that groups a number of addressable - objects for addressing purposes, without being an administrative unit. - - Additional Information: - This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. | -rdf:PlainLiteral [0..1] | +epo:Technique -> at-voc:usage [0..1] | ||
| locn:Address | -locn:adminUnitL1 | -The name or names of a unit of administration related to the exercise of jurisdictional - rights, for local, regional and national governance. Level 1 refers to the uppermost - administrative unit for the address, almost always a country. + | epo:hasUUID | +A universally unique identifier for an instance of this document. - Additional Information: - Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, - country names should be provided in a consistent manner to reduce ambiguity. For example, - either write 'France' or 'FRA' consistently throughout the dataset and avoid mixing - the two. The Country controlled vocabulary from the Publications Office can be reused - for this. | -rdf:PlainLiteral [0..1] | -|
| locn:Address | -locn:adminUnitL2 | -The name or names of a unit of administration related to the exercise of jurisdictional - rights, for local, regional and national governance. Level 2 refers to the region - of the address, usually a county, state or other such area that typically encompasses - several localities. + WG Approval 12/05/2020 A universally unique identifier for an instance of this document. - Additional Information: - Some recommended codelists from the EU Publications Office include: Administrative - Territorial Units (ATU), NUTS and Local Administrative Units (LAU). The first arrondissement - of Paris is for example expressed as "http://publications.europa.eu/resource/authority/atu/FRA_AR_PAR01" - in the ATU controlled vocabulary. + WG Approval 12/05/2020 | -rdf:PlainLiteral [0..1] | +epo:Document -> adms:Identifier [0..1] epo-cat:CatalogueResponseLine -> adms:Identifier [1] |
||
| locn:Address | -locn:fullAddress | -The complete address written as a formatted string. + | epo:hasValidityPeriod | +The relation indicating until when a given instance of a concept is applicable. - Additional Information: - Use of this property is recommended as it will not suffer any misunderstandings that - might arise through the breaking up of an address into its component parts. This property - is analogous to vCard's label property but with two important differences: (1) formatting - is not assumed so that, unlike vCard label, it may not be suitable to print this on - an address label, (2) vCard's label property has a domain of vCard Address; the fullAddress - property has no such restriction. An example of a full address is "Champ de Mars, - 5 Avenue Anatole France, 75007 Paris, France". | -rdf:PlainLiteral [0..1] | + WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. + + WG approval 30/05/2023 + The relation indicating until when a given instance of a concept is applicable. + + WG approval 30/05/2023 +cccev:Evidence -> epo:Period [0..1] epo:Technique -> epo:Period [0..1] epo-cat:Catalogue -> epo:Period [0..1] |
| dct:Location | -locn:geographicName | -A textual description for a Location. + | epo:hasVariantPermission | +The obligation or possibility for tenderers to submit variants or not. Additional Information: - The INSPIRE Data Specification on Geographical Names provides a detailed model for - describing a 'named place', including methods for providing multiple names in multiple - scripts. This is beyond what is necessary for the Core Location Vocabulary but, importantly, - the concept of a geographic name used here is consistent. - A geographic name is a proper noun applied to a spatial object. Taking the example - used in the INSPIRE document (page 15), the following are all valid geographic names - for the Greek capital: + Variants are alternative ways to fulfil the buyer's needs as opposed to solutions + indicated in the procurement documents. - - "Aθnνa"@gr-Grek (the Greek endonym written in the Greek script) - - "Athína"@gr-Latn (the standard Romanisation of the endonym) - - "Athens"@en (the English language exonym) - INSPIRE has a detailed (XML-based) method of providing metadata about a geographic - name and in XML-data sets that may be the most appropriate method to follow. When - using the Core Location Vocabulary in data sets that are not focussed on environmental/geographical - data (the use case for INSPIRE), the Code datatype or a simple language identifier - may be used to provide such metadata. + eForms: Whether tenderers are required, allowed or forbidden to submit tenders which + fulfil the buyer's needs differently than as proposed in the procurement documents. - The country codes defined in ISO 3166 may be used as geographic names and these are - generally preferred over either the long form or short form of a country's name (as - they are less error prone). The Publications Office of the European Union recommends - the use of ISO 3166-1 codes for countries in all cases except two: - - use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; - - use 'EL' in preference to the ISO 3166 code GR for Greece. - Where a country has changed its name or no longer exists (such as Czechoslovakia, - Yugoslavia etc.) use the ISO 3166-3 code. + Additional Information: + + Further conditions for submitting variant tenders are in the procurement documents. | -rdf:PlainLiteral [0..1] | +epo:SubmissionTerm -> at-voc:permission [0..1] |
| locn:Address | -locn:locatorDesignator | -A number or a sequence of characters which allows a user or an application to interpret, - parse and format the locator within the relevant scope. A locator may include more - locator designators. + | epo:hasWeightValueType | +No definition. Waiting on CCCEV alignment. - Additional Information: - In simpler terms, this is the building number, apartment number, etc. For an address - such as "Flat 3, 17 Bridge Street", the locator is "flat 3, 17". | -rdf:PlainLiteral [0..1] | + + +epo:ProcurementCriterion -> at-voc:number-weight [0..1] |
| locn:Address | -locn:locatorName | -Proper noun(s) applied to the real world entity identified by the locator. - - Additional Information: - The locator name could be the name of the property or complex, of the building or - part of the building, or it could be the name of a room inside a building. + | epo:includesAccessibilityCriterion | +Explanation as to whether accessibility Criterion are used or not. + WG Approval 09/11/2021 - The key difference between a locator and a locator name is that the latter is a proper - name and is unlikely to include digits. For example, "Shumann, Berlaymont" is a meeting - room within the European Commission headquarters for which locator name is more appropriate - than locator. | -rdf:PlainLiteral [0..1] | + +epo:StrategicProcurement -> at-voc:accessibility [0..*] |
| locn:Address | -locn:postCode | -The post/zip code of an address. (INSPIRE's definition is "A code created and maintained - for postal purposes to identify a subdivision of addresses and postal delivery points.") + | epo:includesNationalCriterion | +Relation indicating that a Criterion contains a Criterion that is specific to a given + Member State. Additional Information: - Post codes are common elements in many countries' postal address systems. One of the - many post codes of Paris is for example "75000". | -rdf:PlainLiteral [0..1] | + In the ESPD, a Subcriterion is used to define national sub-criteria; maps to a UBL-2.3 + cac:SubTenderingCriterion class. It is currently used only for purely national criteria, + to be able to establish the mapping from eCertis. + + WG approval 07/11/2023 + + +epo:QualificationCriterion -> epo:QualificationCriterion [0..*] |
| locn:Address | -locn:postName | -The key postal division of the address, usually the city. (INSPIRE's definition is - "One or more names created and maintained for postal purposes to identify a subdivision - of addresses and postal delivery points.) For example, "Paris". | -rdf:PlainLiteral [0..1] | +epo:includesTender | +Additional information: + This corresponds in eForms to BT-3202 Contract Tender Identifier. + | +epo:Contract -> epo:Tender [0..*] |
| locn:Address | -locn:thoroughfare | -An address component that represents the name or names of a passage or way through - from one location to another. A thoroughfare is not necessarily a road, it might be - a waterway or some other feature. - - Additional Information: - For example, "Avenue des Champs-Élysées". | -rdf:PlainLiteral [0..1] | +epo:indicatesAwardToWinner | +Reveals the winner to whom the tender award outcome is attributed. | +epo:TenderAwardOutcome -> epo:Winner [0..1] |
| person:Person | -person:birthName | -Family name of the Person given upon their birth. - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo:indicatesInvoiceeContactPoint | ++ | epo:Buyer -> cpov:ContactPoint [] |
| person:Person | -person:patronymicName | -Name based on the given name of the Person's father. - WG Approval 09/11/2021 | -rdf:PlainLiteral [0..*] | +epo:involvesBuyer | ++ | epo:Procedure -> epo:Buyer [0..*] |
| adms:Identifier | -skos:notation | -The literal identifying an entity, like a person or an object. | -rdf:PlainLiteral [1..1] | +epo:involvesProcurementDocument | ++ | epo:AccessTerm -> epo:ProcurementDocument [0..1] |
| cccev:InformationConcept cccev:Requirement |
- skos:prefLabel | -The preferred lexical label for a resource, in a given language. - - WG approval 30/05/2023 - - The preferred lexical label for a resource, in a given language. + | epo:isBasedOnImplementingRegulation | +Indicates under which regulation a notice is created. - WG approval 30/05/2023 | -rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] |
+ WG Acceptance 06/09/2022
+ epo:Notice -> at-voc:legal-basis [0..1] |
| epo:SpecificDuration | -time:numericDuration | -Value of a temporal extent expressed as a number. | -xsd:decimal [1..1] | +epo:isBeneficialOwnerOf | +A role of any natural person(s) who ultimately owns or controls the organisation or + on whose behalf a transaction or activity is being conducted. + Additional Information: + This role is defined in the directive EU 2015/849 and it's beyond the scope for public + eProcurement domain. + WG approval 14/09/2021 | +epo:Business [,0..*] <- person:Person |
| Predicate name | -Definition | -Domain, Range and Cardinality | +epo:isCalculatedOn | +The monetary amount to which the multiplier factor is applied in calculating the amount + of this allowance or charge. + + The monetary amount to which the multiplier factor is applied in calculating the amount + of this allowance or charge. | +epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1] epo-ord:TaxInformation -> epo:MonetaryValue [0..1] |
|---|---|---|---|---|---|
| adms:identifier | -Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. A unique identifier of the instance of the concept. - - Additional Information - - For example, in the case of the Procurement Identifier, this could be the European - Public Procurement Identifier, and/or any other identifier provided by the buyer, - the service provider or any other stakeholder. - - WG Approval 12/11/2019 - - Links a resource to an adms:Identifier class. A unique identifier of the instance of the concept. - - Additional Information - - For example, in the case of the Procurement Identifier, this could be the European - Public Procurement Identifier, and/or any other identifier provided by the buyer, - the service provider or any other stakeholder. - - WG Approval 12/11/2019 A unique identifier of the instance of the concept. - - Additional Information - - For example, in the case of the Procurement Identifier, this could be the European - Public Procurement Identifier, and/or any other identifier provided by the buyer, - the service provider or any other stakeholder. - - WG Approval 12/11/2019 - A unique identifier of the instance of the concept. - - Additional Information - - For example, in the case of the Procurement Identifier, this could be the European - Public Procurement Identifier, and/or any other identifier provided by the buyer, - the service provider or any other stakeholder. - - WG Approval 12/11/2019 - Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. | -cccev:Evidence -> adms:Identifier [1] cccev:InformationConcept -> adms:Identifier [0..1] cccev:Requirement -> adms:Identifier [0..1] dct:Location -> adms:Identifier [0..1] epo:Document -> adms:Identifier [0..*] epo:Fund -> adms:Identifier [0..1] epo:Project -> adms:Identifier [0..1] foaf:Agent -> adms:Identifier [0..*] epo:LotGroup -> adms:Identifier [0..1] epo:ProcurementElement -> adms:Identifier [1] epo:TenderGroup -> adms:Identifier [0..1] |
+ epo:isExecutedByProcurementServiceProvider | ++ | epo:Procedure -> epo:ProcurementServiceProvider [0..1] |
| cccev:confidentialityLevelType | -Security classification assigned to an Evidence e.g. classified, sensitive, public. + | epo:isFundedBy | +Funding is provided either completely or partially by a Fund. - Additional Information: + Additional information: + This corresponds in eForms to BG - 61 EU Funds (specified per Lot) and to BG - 611 + Contract EU Funds (applied per Contract lot) + Funds may change between the lot and the contract, for example in the case of an emergency + crisis, a contract may be financed by a budget that was not foreseen in the call. - Classifications should be defined by an organisation/country as an outcome of a security - assessment. - Security classification assigned to an Evidence e.g. classified, sensitive, public. + Funding is provided either completely or partially by a Fund. - Additional Information: + Additional information: + This corresponds in eForms to BG - 61 EU Funds (specified per Lot) and to BG - 611 + Contract EU Funds (applied per Contract lot) + Funds may change between the lot and the contract, for example in the case of an emergency + crisis, a contract may be financed by a budget that was not foreseen in the call. - Classifications should be defined by an organisation/country as an outcome of a security - assessment. | -cccev:Evidence -> at-voc:access-rights [0..1] |
+
+ epo:Contract -> epo:Fund [0..*] epo:ProcurementObject -> epo:Fund [0..*] |
| cccev:constrains | -Information Concept about which a Constraint expresses a limitation. - - Additional Information: - Information Concepts are tools to make Requirements more machine processable: they - allow to provide more detail about a Requirement. This way, Constraints can be made - very precise, namely the limit that must be achieved, is a limit on the value for - the associated Information Concept. For example, the Information Concept would be - the age of a person and the Constraint would be the required age in the context of - a specific evaluation. | -cccev:Constraint -> cccev:InformationConcept [0..*] | +epo:isOwnedByAgent | ++ | epo:System -> foaf:Agent [0..1] |
| cccev:hasConcept | -Information Concept for which a value is expected by the Requirement. + | epo:isResponsibilityOfBuyer | +The buyer in charge of the procedure. Additional Information: - Information Concepts defined for specific Requirements also represent the basis for - specifying the Supported Value an Evidence should provide. | -cccev:Requirement -> cccev:InformationConcept [0..*] | + In case there are multiple buyers, it may be the case that one or more buyers are + in charge of the procedure. + + +epo:Procedure -> epo:Buyer [0..*] |
| cccev:hasRequirement | -A more specific Requirement that is part of the Requirement. | -cccev:Requirement -> cccev:Requirement [0..*] | +epo:isSubjectToContractSpecificTerm | ++ | epo:Contract -> epo:ContractSpecificTerm [0..*] |
| cccev:supportsConcept | -Information Concept providing facts found/inferred from the Evidence. - - Additional Information: - Examples of Information Concepts are values found explicitly in the evidence such - as a birth date or information derived from the Evidence such as "I am older that - 18 years" or "this is a Fair Trade product". | -cccev:Evidence -> cccev:InformationConcept [0..*] | +epo:isSubjectToGrouping | ++ | epo:Tender -> epo:LotGroup [0..1] |
| cccev:supportsRequirement | -Requirement for which the Evidence provides proof. | -cccev:Evidence -> cccev:Requirement [0..*] | +epo:isSubjectToLotSpecificTerm | ++ | epo:Lot -> epo:LotSpecificTerm [0..*] |
| cv:registeredAddress | -The registered address relationship links a Resource with the legally registered Address. - - Additional Information: - It is the address to which formal communications can be sent, such as the postal address. The registered address relationship links a Resource with the legally registered Address. - - Additional Information: - It is the address to which formal communications can be sent, such as the postal address. - | -person:Person -> locn:Address [0..1] org:Organization -> locn:Address [0..1] |
+ epo:isSubjectToProcedureSpecificTerm | ++ | epo:Procedure -> epo:ProcedureSpecificTerm [1..*] |
| dct:type | -Category to which the Requirement belongs. | -cccev:Criterion -> at-voc:criterion [0..1] | +epo:isSubjectToTerm | ++ | epo:ProcurementObject -> epo:Term [0..*] |
| epo:actsOnBehalfOf | -Represents. | -epo:ProcurementServiceProvider -> epo:Buyer [1..*] |
+ epo:isSubmitedBy | +Relation indicating the submission of a tender by an economic operator. + WG approval 18/05/2021 | +epo:Tender -> epo:Tenderer [0..1] |
| epo:associatedWith | -The document to which a document is associated. - - WGM 01/03/2022 - | -epo:Document -> epo:Document [0..*] | +epo:isSubmittedForLot | ++ | epo:Tender -> epo:Lot [1] |
| epo:attestedByLabel | -Relation indicating which label the certificate is about. + | epo:isSubmittedForLotGroup | ++ | epo:TenderGroup -> epo:LotGroup [1] | +|
| epo:issuedByCertifier | +Relation indicating the Certifier responsible for providing the ItemCertificate. - WG approval 28/07/2022 | -epo:Certificate -> epo:CertificationLabel [0..1] | + Additional Information: + Certifier is a role played by an organisation. + + WG approval 26/07/2022 +epo:Certificate -> epo:Certifier [0..1] | ||
| epo:bindsBuyer | -Provides legal constraint on the Buyer. | -epo:Contract -> epo:Buyer [0..*] | +epo:isSupportedBy | ++ | epo:Tender -> epo-sub:ESPDResponse [1] |
| epo:bindsContractor | -Provides legal constraint on the Contractor. | -epo:Contract -> epo:Contractor [0..*] | +epo:leadBy | +The epo:OrganisationGroup epo:leadBy org:Organization was implemented to be used in + case of an Economic Operator Group. | +epo:OrganisationGroup -> org:Organization [0..1] |
| epo:canProvideNonDiscriminatoryEvidence | -Relation showing that an Organization can supply an Evidence with regard to the fulfilment - of non-discriminatory criteria or the rules applied in order to reduce the number - of participants. - - WG approval 12/03/2024 | -org:Organization -> cccev:Evidence [0..*] | +epo:needsToBeATenderer | +The Winner must be a Tenderer. | +epo:Winner -> epo:Tenderer [0..1] |
| epo:canProvideTaxAndSocialSecuritiesEvidence | -Relation showing that an Organization can supply an Evidence with regard to the payment - of social security contributions and taxes. - - WG approval 12/03/2024 | -org:Organization -> cccev:Evidence [0..*] | +epo:needsToBeAWinner | +The Contractor must be a Winner. + | +epo:Contractor -> epo:Winner [0..1] |
| epo:comprisesAwardOutcome | -Incorporates AwardOutcome. | -epo:AwardDecision -> epo:AwardOutcome [0..*] | +epo:ownsSystem | ++ | epo:System [,0..*] <- foaf:Agent |
| epo:comprisesTender | -Incorporates Tender. | -epo:TenderGroup -> epo:Tender [1..*] | +epo:playedBy | ++ | epo:AgentInRole -> foaf:Agent [1] epo:JuryMember -> person:Person [0..1] epo-ful:TransportMeansOperator -> foaf:Person [0..1] |
| epo:comprisesTenderAwardOutcome | -Incorporates TenderAwardOutcome. | -epo:AwardOutcome -> epo:TenderAwardOutcome [0..*] | +epo:providesContractTotalPaymentValue | +Additional Information: + This corresponds to BT-779 in eForms. | +epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] |
| epo:concernsGreenProcurement | -- | epo:VehicleInformation -> epo:GreenProcurement [1] | +epo:providesContractTotalPenaltyValue | ++ Additional Information: + This corresponds to BT-782 in eForms. + | +epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] |
| epo:concernsLot | -Relates to Lot. Relates to Lot. | -epo:LotAwardOutcome -> epo:Lot [1] epo:ProcurementProcessInformation -> epo:Lot [0..1] |
+ epo:providesRulingOnRemedy | +States the measures to be taken after a review procedure. | +epo:ReviewDecision -> at-voc:remedy-type [0..*] |
| epo:concernsNotice | +epo:refersToAwardDecision | - | epo:ChangeInformation -> epo:Notice [1] epo:NonPublishedInformation -> epo:Notice [1] |
+ epo-not:CompletionNotice -> epo:AwardDecision [0..*] epo-not:ContractModificationNotice -> epo:AwardDecision [0..*] |
|
| epo:concernsProcedure | -Relates to Procedure. Relates to Procedure. - - WG approval 05/03/2024 - | -epo:ProcurementProcessInformation -> epo:Procedure [0..1] |
+ epo:refersToContract | ++ | epo:ContractLotCompletionInformation -> epo:Contract [1] |
| epo:concernsReviewSummaryForLot | -Relates to Lot review summary. - - Additional information: - This relation corresponds in eForms to BT-13722 Buyer Review Lot Identifier. | -epo:ReviewRequestSummary -> epo:Lot [1] | +epo:refersToContractToBeModified | ++ | epo-not:ContractModificationNotice -> epo:Contract [1] |
| epo:concernsTender | +epo:refersToLot | ++ | epo:Notice -> epo:Lot [1..*] epo-not:CompletionNotice -> epo:Lot [1..*] epo-not:ContractModificationNotice -> epo:Lot [1..*] epo-not:ResultNotice -> epo:Lot [1..*] |
+ ||
| epo:refersToLotGroup | ++ | epo-not:ContractModificationNotice -> epo:LotGroup [0..*] epo-not:ResultNotice -> epo:LotGroup [0..*] epo-not:CompletionNotice -> epo:LotGroup [0..*] |
+ |||
| epo:refersToLotGroupAwardInformation | ++ | epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*] epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*] |
+ |||
| epo:refersToNotice | - | epo:TenderAwardOutcome -> epo:Tender [1] | +epo:Notice -> epo:Notice [0..1] | ||
| epo:conformsToLegalBasis | -The Notice was designed in accordance with the given legal basis. - - Additional Information: - This Notice can be used for Procedures which do not have the same legal basis. - This holds for standard forms. | -epo:Notice -> at-voc:legal-basis [0..*] | +epo:refersToNoticeAwardInformation | ++ | epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1] epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1] |
| epo:containsCandidate | +epo:refersToPlannedPart | - | epo:SelectedCandidateList -> epo:Candidate [0..*] | +epo:AccessTerm -> epo:PlannedProcurementPart [0..*] | |
| epo:contextualisedBy | -The place of the AgentInRole in the procurement is expressed by a ProcurementObject. | -epo:AgentInRole -> epo:ProcurementObject [0..*] | +epo:refersToPrevious | ++ | epo:Document -> epo:Document [0..*] |
| epo:definesBudgetProvider | -Relation indicating a ProcedureTerm has a BudgetProvider. | -epo:ProcedureTerm -> epo:BudgetProvider [0..1] | +epo:refersToPreviousNotice | ++ Additional information: + This corresponds in eForms to BT-758 Change Notice Version Identifier. | +epo:ChangeInformation -> epo:Notice [1] |
| epo:definesCatalogueProvider | -Relation indicating an AccessTerm has a CatalogueProvider. | -epo:AccessTerm -> epo:CatalogueProvider [0..*] | +epo:refersToPreviousProcedure | +Reference to a previous procedure. + + Additional Information: + In the case of Direct Award Terms, this property points to a previous Procedure justifying + the use of Direct Award without a prior publication. + + This corresponds in the eForms to BT-1252 Direct Award Justification Previous + Procedure Identifier | +epo:DirectAwardTerm -> epo:Procedure [0..1] |
| epo:definesCatalogueReceiver | -Relation indicating an AccessTerm has a CatalogueReceiver. | -epo:AccessTerm -> epo:CatalogueReceiver [0..*] | +epo:refersToPreviousProcedureLot | +Reference to one or more Lots in a previous procedure. + + Additional Information: + In the case of Direct Award Terms, this property points to a previous Procedure justifying + the use of Direct Award without a prior publication. + + This corresponds in the eForms to BT-1252 Direct Award Justification Previous + Procedure Identifier + + WG Approval 22/11/2019 14:33:55 | +epo:DirectAwardTerm -> epo:Lot [0..*] |
| epo:definesContractDuration | -Relation indicating a ContractTerm has a Duration. | -epo:ContractTerm -> epo:Duration [0..1] | +epo:refersToPreviousReview | +Additional information: + This relation corresponds in eForms to BT-785 "Review Previous Identifier". | +epo:ReviewObject -> epo:ReviewObject [0..1] |
| epo:definesContractPeriod | -Relation indicating a ContractTerm has a Period. | -epo:ContractTerm -> epo:Period [0..1] | +epo:refersToProcedure | ++ | epo:Notice -> epo:Procedure [1] epo-not:ResultNotice -> epo:Procedure [1] epo-not:ContractModificationNotice -> epo:Procedure [1] epo-not:CompletionNotice -> epo:Procedure [1] |
| epo:definesInformationProvider | -Relation indicating a ProcedureTerm has an information provider. | -epo:ProcedureTerm -> epo:AuxiliaryParty [0..*] | +epo:refersToProject | ++ | epo-ord:Order -> epo:Project [0..1] |
| epo:definesLotGroup | -Relation indicating a ProcedureTerm has a LotGroup. | -epo:ProcedureTerm -> epo:LotGroup [0..*] | +epo:refersToRole | ++ | epo-not:CompletionNotice -> epo:AgentInRole [0..*] |
| epo:definesMediator | -Relation indicating a ProcedureTerm has a Mediator. | -epo:ProcedureTerm -> epo:Mediator [0..1] | +epo:relatesToEFormSectionIdentifier | ++ | epo:ChangeInformation -> adms:Identifier [1..*] epo:NonPublishedInformation -> adms:Identifier [1..*] epo-con:ContractModificationInformation -> adms:Identifier [0..1] |
| epo:definesOfflineAccessProvider | -Relation indicating an AccessTerm has an OfflineAccessProvider. | -epo:AccessTerm -> epo:OfflineAccessProvider [0..1] | +epo:requestsRemedyType | +Additional information: + This relation corresponds in eForms to BT-792 Review Remedy Type | +epo:ReviewRequest -> at-voc:remedy-type [0..*] |
| epo:definesOpeningPlace | -The place where the tenders will be publicly opened. - - WG Approval 10-10-2019 | -epo:OpeningTerm -> locn:Address [0..1] | +epo:resolvesReviewRequest | ++ | epo:ReviewDecision -> epo:ReviewRequest [1] |
| epo:definesParticipationRequestProcessor | -Relation indicating a ParticipationRequestTerm has a ParticipationRequestProcessor. | -epo:ParticipationRequestTerm -> epo:ParticipationRequestProcessor [0..1] | +epo:resultsFromLotAwardOutcome | ++ | epo:DirectContract -> epo:LotAwardOutcome [0..*] epo:FrameworkAgreement -> epo:LotAwardOutcome [0..*] |
| epo:definesParticipationRequestReceiver | -Relation indicating a ParticipationRequestTerm has a ParticipationRequestReceiver. | -epo:ParticipationRequestTerm -> epo:ParticipationRequestReceiver [0..1] | +epo:resultsFromMiniCompetitionAwardOutcome | ++ | epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome [0..1] |
| epo:definesPaymentExecutor | -Relation indicating a ContractTerm has a PaymentExecutor. | -epo:ContractTerm -> epo:PaymentExecutor [0..1] | +epo:resultsFromUsingCandidateList | ++ | epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList [0..1] |
| epo:definesPrize | -Relation indicating a DesignContestRegimeTerm has a Prize. | -epo:DesignContestRegimeTerm -> epo:Prize [0..*] | +epo:setsGroupingContextForLot | ++ | epo:LotGroup -> epo:Lot [1..*] |
| epo:definesProcurementProcedureInformationProvider | -Relation indicating an AccessTerm has a ProcurementProcedureInformationProvider. | -epo:AccessTerm -> epo:ProcurementProcedureInformationProvider [0..1] | +epo:signedByBuyer | ++ | epo:Contract -> epo:Buyer [0..*] |
| epo:definesReviewer | -Relation indicating a ReviewTerm has a Reviewer. | -epo:ReviewTerm -> epo:Reviewer [0..*] | +epo:signedByContractor | ++ | epo:Contract -> epo:Contractor [0..*] |
| epo:definesReviewProcedureInformationProvider | -Relation indicating a ReviewTerm has a ReviewProcedureInformationProvider. | -epo:ReviewTerm -> epo:ReviewProcedureInformationProvider [0..1] | +epo:signsAwardDecision | ++ | epo:Buyer -> epo:AwardDecision [0..*] |
| epo:definesSpecificPlaceOfPerformance | -Relation indicating a ContractTerm has a specific place of performance. | -epo:ContractTerm -> dct:Location [0..*] | +epo:specifiesBuyer | ++ | epo-cat:Catalogue -> epo:Buyer [0..*] epo-ord:Order -> epo:Buyer [1] |
| epo:definesSubcontractingTerm | -Relation indicating a ContractTerm has a SubcontractingTerm.Relation indicating a - term has a subterm. | -epo:ContractTerm -> epo:SubcontractTerm [0..1] | +epo:specifiesCarrier | ++ | epo-ful:ShipmentStage -> epo-ful:Carrier [0..1] |
| epo:definesTenderProcessor | -Relation indicating a SubmissionTerm has a TenderProcessor. | -epo:SubmissionTerm -> epo:TenderProcessor [0..1] | +epo:specifiesCatalogueProvider | ++ | epo-cat:Catalogue -> epo:CatalogueProvider [0..1] epo-cat:CatalogueResponse -> epo:CatalogueProvider [1] |
| epo:definesTenderReceiver | -Relation indicating a SubmissionTerm has a TenderReceiver. | -epo:SubmissionTerm -> epo:TenderReceiver [0..1] | +epo:specifiesCatalogueReceiver | ++ | epo-cat:Catalogue -> epo:CatalogueReceiver [0..1] epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1] |
| epo:delegatesAncillaryActivitiesTo | -Entrusts ancillary purchasing activities to ProcurementServiceProvider. - - Additional Information: - Directive 2014/24/EU describes ancillary purchasing activities as activities consisting - in the provision of support to purchasing activities, in particular in the following - forms: - - (a) technical infrastructure enabling contracting authorities to award public contracts - or to conclude framework agreements for works, supplies or services; - - (b) advice on the conduct or design of public procurement procedures; - - (c) preparation and management of procurement procedures on behalf and for the account - of the contracting authority concerned; | -epo:Buyer -> epo:ProcurementServiceProvider [0..*] | +epo:specifiesCleanVehicleDirectiveContractType | ++ | epo:VehicleInformation -> at-voc:cvd-contract-type [0..1] |
| epo:describesLotCompletion | +epo:specifiesCleanVehicleDirectiveVehicleCategory | - | epo:ContractLotCompletionInformation -> epo:Lot [1] | +epo:VehicleInformation -> at-voc:vehicle-category [0..1] | |
| epo:describesLotGroup | +epo:specifiesDeliverable | - | epo:LotGroupAwardInformation -> epo:LotGroup [1] | +epo:Contract -> epo-con:Deliverable [0..*] | |
| epo:distributesOffer | +epo:specifiesDespatcher | - | epo:OfferIssuer -> epo:Offer [0..*] | +epo-ord:Order -> epo-ful:Despatcher [0..1] | |
| epo:exposesChannel | +epo:specifiesFreightForwarder | - | epo:AgentInRole -> cv:Channel [0..*] | +epo-ful:Consignment -> epo-ful:FreightForwarder [0..*] | |
| epo:exposesInvoiceeChannel | +epo:specifiesNotifier | - | epo:Buyer -> cv:Channel [0..*] | +epo-ful:Consignment -> epo-ful:Notifier [0..*] | |
| epo:followsRulesSetBy | +epo:specifiesProcurementCriteriaSummary | - | epo:PurchaseContract -> epo:FrameworkAgreement [0..1] | +epo:Procedure -> epo:ProcurementCriteriaSummary [0..*] | |
| epo:foreseesConcession | +epo:specifiesProcurementCriterion | ++ | epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*] epo:Lot -> epo:ProcurementCriterion [0..*] epo:LotGroup -> epo:ProcurementCriterion [0..*] |
+ ||
| epo:specifiesSeller | - | epo:Tender -> epo:ConcessionEstimate [0..1] epo:ProcurementObject -> epo:ConcessionEstimate [0..1] |
+ epo-cat:Catalogue -> epo-ord:Seller [0..*] epo-ord:Order -> epo-ord:Seller [1] |
||
| epo:foreseesContractSpecificTerm | +epo:specifiesSubcontractors | - | epo:ProcurementObject -> epo:ContractSpecificTerm [0..*] | +epo:Tender -> epo:Subcontractor [0..*] | |
| epo:foreseesProcurementObject | -Relation indicating the instance of a Procurement Object that is planned. + | epo:substantiatesExclusionGround | ++ | epo:Tenderer -> epo:ExclusionGround [0..1] | +|
| epo:summarisesInformationForAwardOutcome | +Relates to submission for the given competition, either at Lot level or Mini-Competition + level. - Additional Information: - The properties of the Procurement Object that is foreseen should be read as foreseen - properties. - For example, Procedure isSMESuitable should be read as Procedure foreseesToBeSMESuitable. - For example, Procedure isFundedBy should be read as Procedure foreseesToBeFundedBy. | -epo:PlannedProcurementPart -> epo:ProcurementObject [0..1] | + WG approval 30/05/2023 +epo:SubmissionStatisticalInformation -> epo:AwardOutcome [1] | ||
| epo:foreseesSubcontracting | +epo:updatesContractValue | - | epo:Tender -> epo:SubcontractingEstimate [0..*] | +epo-con:ContractAmendment -> epo:MonetaryValue [0..1] | |
| epo:foreseesTechnique | +epo:usesChannel | - | epo:PlannedProcurementPart -> epo:Technique [0..*] | +epo:ProcurementElement -> cv:Channel [0..*] | |
| epo:fulfillsRequirement | -The requirement to which the concept meets. - WG Approval 09/11/2021 - The requirement to which the concept meets. - WG Approval 09/11/2021 - - The requirement to which the concept meets. - WG Approval 09/11/2021 - - The requirement to which the concept meets. - WG Approval 09/11/2021 + | epo:usesTechnique | ++ | epo:ProcurementObject -> epo:Technique [0..*] | +|
| epo-acc:refersToNotice | +Reference to a Notice. - | -epo:GreenProcurement -> at-voc:green-public-procurement-criteria [0..*] epo:GreenProcurement -> at-voc:environmental-impact [0..*] epo:InnovativeProcurement -> at-voc:innovative-acquisition [0..*] epo:SocialProcurement -> at-voc:social-objective [0..*] |
+ WG approval 12/03/2024
+ epo-acc:ESPDRequest -> epo:Notice [0..*] | ||
| epo:fulfillsStrategicProcurement | +epo-cat:comprisesCatalogueLine | - | epo:ProcurementObject -> epo:StrategicProcurement [0..*] | +epo-cat:Catalogue -> epo-cat:CatalogueLine [1..*] | |
| epo:hasAdditionalClassification | +epo-cat:comprisesCatalogueResponseLine | - | epo:Purpose -> at-voc:cpv [0..*] | +epo-cat:CatalogueResponse -> epo-cat:CatalogueResponseLine [0..*] | |
| epo:hasAdditionalContractNature | -Additional type of acquisition taken into consideration in the contract. - - WG Approval 11/06/2020 - - | -epo:ContractTerm -> at-voc:contract-nature [0..*] | +epo-cat:describesItem | ++ | epo-cat:ItemProperty -> epo-cat:Item [1] |
| epo:hasAllegedIrregularityType | -Additional information: - This relation corresponds in eForms to BT-791 Review Irregularity Type - | -epo:ReviewRequest -> at-voc:irregularity-type [1..*] | +epo-cat:foreseesPackage | ++ | epo-cat:CatalogueLine -> epo-ful:Package [0..1] |
| epo:hasApproximateFrameworkAgreementValue | -The estimated value to be spent within the Framework Agreement(s). + | epo-cat:hasAccessoryItem | +An item that can be added to another item to enhance it. - Additional information: - In the case of an Award Decision for a Lot, this relation represents the estimated - value for the awarded Framework Agreement. - In the case of a Notice, this relation represents the estimated value for all Framework - Agreements covered by the Notice. - The estimated value to be spent within the Framework Agreement(s). - - Additional information: - In the case of an Award Decision for a Lot, this relation represents the estimated - value for the awarded Framework Agreement. - In the case of a Notice, this relation represents the estimated value for all Framework - Agreements covered by the Notice. - | -epo:LotAwardOutcome -> epo:MonetaryValue [0..1] epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] |
- |
| epo:hasAwardCriterionType | -Category of award criterion. + WG Approval: 30/06/2022An additional item that can enhance the original item. + WG Approval: 19/05/2022 | -epo:AwardCriterion -> at-voc:award-criterion-type [0..1] | +epo-cat:Item -> epo-cat:Item [0..*] | ||
| epo:hasAwardedValue | -The value of the procurement provided by the Award Decision. - - Additional Information: - Different cases of awarded values may refer to a lot, the global value of the procedure, - or of a combinatorial value of a group of lots. - - In the case of framework agreements and dynamic purchasing systems this refers to - the maximum awarded value. - - WG Approval 10/12/2019 | -epo:AwardOutcome -> epo:MonetaryValue [0..1] | +epo-cat:hasActivityCode | ++ | epo-cat:Catalogue -> at-voc-new:activity-code [0..1] epo-cat:CatalogueLine -> at-voc-new:activity-code [0..1] |
| epo:hasAwardStatus | -Indicates whether the lot is awarded, not awarded or still open. - WG Approval 03/12/2019 + | epo-cat:hasAmount | +The predetermined monetary value charged in addition to the price. + + WG approval 26/07/2022 The predetermined monetary value charged in addition to the price. + + WG approval 26/07/2022 | -epo:AwardOutcome -> at-voc:winner-selection-status [0..1] | +epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1] epo-ord:TaxInformation -> epo:MonetaryValue [0..1] |
| epo:hasBargainPrice | -The value of procured supplies that have used a particularly advantageous opportunity - available for a very short time at a value considerably lower than normal market prices. - - WG approval 23/05/2023 | -epo:AwardOutcome -> epo:MonetaryValue [0..1] | +epo-cat:hasBaseQuantity | +The quantity at which the net monetary value applies. | +epo-cat:Price -> epo:Quantity [0..1] |
| epo:hasBeneficialOwner | -A role of any natural person(s) who ultimately owns or controls the organisation or - on whose behalf a transaction or activity is being conducted. - Additional Information: - This role is defined in the directive EU 2015/849 and it's beyond the scope for public - eProcurement domain. - WG approval 14/09/2021 | -epo:Business -> person:Person [0..*] | +epo-cat:hasBrand | ++ | epo-cat:Item -> epo-cat:Brand [0..1] |
| epo:hasBroadPlaceOfPerformance | -Geopolitical zone where the contract can be executed. + | epo-cat:hasCatalogueLineValidity | +The relation indicating until when a Catalogue Line instance is applicable. - Additional Information - - Used for setting restrictions that cannot be established with one country code or - a geographical zone identifier (like NUTS), because they have a broader scope (geographical, - economic, political, other). - | -epo:ContractTerm -> at-voc:other-place-service [0..1] | + WG approval 21/09/2023 +epo-cat:CatalogueLine -> epo:Period [0..1] |
| epo:hasBusinessSize | -The category of the business depending on number of employees and turnover. + | epo-cat:hasChargeInformation | ++ | epo-cat:CatalogueLine -> epo-cat:ChargeInformation [0..*] | +|
| epo-cat:hasComplementaryItem | +An item that if used with another item provides mutual enhancements to both of them. Additional information: + For example, gin and tonic; or smart-phone and smart-watch. - See Commission Recommendation of 6 May 2003 concerning the definition of micro, small - and medium-sized enterprises. - - WG Approval 28/05/2020 + WG Approval: 19/05/2022 | -epo:Business -> at-voc:economic-operator-size [0..1] | +epo-cat:Item -> epo-cat:Item [0..*] | ||
| epo:hasBuyerLegalType | -A category that indicates the right of an Organisation to play the role of a buyer. + | epo-cat:hasCountryOfOrigin | +The source country of the product or service. Additional Information: - The category also effects the rules that the buyer has to abide to within the public - procurement procedure. - WG 07/09/2021 + The country of origin can be provided by the buyer as a requirement or by the tenderer + information of the item to be provided. + + WG Approval 07/01/2020 | -org:Organization -> at-voc:buyer-legal-type [0..1] | +epo-cat:Item -> at-voc:country [0..1] |
| epo:hasCertification | -Relation to the proof of conformance. - - WG approval 30/05/2023 Relation to the proof of conformance. - - WG approval 30/05/2023 Relation to the proof of conformance. - - WG approval 30/05/2023 | -foaf:Person -> epo:Certificate [0..*] org:Organization -> epo:Certificate [0..*] |
+ epo-cat:hasDeliveryClassification | ++ | epo-cat:Item -> at-voc-new:delivery-item-type [0..1] |
| epo:hasChangeJustification | -Code explaining the change. - - WG Approval 5/11/2019 - The motives for the change. - - WG 5/11/2019 - - The codelist to be used is at-voc:change-corrig-justification which is available at - - http://publications.europa.eu/resource/dataset/change-corrig-justification | -epo:ChangeInformation -> at-voc:change-corrig-justification [1] | +epo-cat:hasDeliveryLocation | +Location delivery area where the Item can be ordered to the given price. + | +epo-cat:Price -> dct:Location [0..1] |
| epo:hasConcessionEstimatedValue | +epo-cat:hasDocumentType | - | epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | +epo-cat:PostAwardDocument -> at-voc-new:document-type [0..1] | |
| epo:hasConfirmedIrregularityType | -Additional information: - This relation corresponds in eForms to BT-791 Review Irregularity Type | -epo:ReviewDecision -> at-voc:irregularity-type [0..*] | +epo-cat:hasExpectedDeliveryTime | +The expected amount of time between the order and delivery of an item. + + WG approval 26/07/2022 + | +epo-cat:Price -> epo:Duration [0..1] |
| epo:hasConstraint | -- | cccev:InformationRequirement -> cccev:Constraint [0..*] epo:ProcurementCriterion -> cccev:Constraint [0..*] |
+ epo-cat:hasExternalSpecification | +URI reference to external item information or specifications, e.g. web address. + | +epo-cat:Item -> epo:Document [] |
| epo:hasContactPointInRole | -- | epo:AgentInRole -> cpov:ContactPoint [0..*] | +epo-cat:hasHazardousItemUNDGCode | +Specification of the hazardous nature of an item according to the UNDG classification + schema. Provides detail of the classification and nature of a hazardous item. + | +epo-cat:Item -> at-voc-new:dangerous-goods-list [0..*] |
| epo:hasContractNatureType | -Subject of the acquisition. + | epo-cat:hasItemClassification | +A classification of this item according to a specific system for classifying products + or services. - WG Approval 11/06/2020 + Additional information: + Examples of classification schemes are: CPV, UNSPC, eCl@ss, GPC, ... - | -epo:ContractTerm -> at-voc:contract-nature [0..1] | + WG acceptance 10/03/2022 +epo-cat:Item -> at-voc-new:item-classification [0..*] |
| epo:hasContractValue | -- | epo:Contract -> epo:MonetaryValue [0..1] | +epo-cat:hasManufacturer | +The product maker or service provider. | +epo-cat:Item -> epo-cat:Manufacturer [0..1] |
| epo:hasCountryCode | -+ | epo-cat:hasMaximumOrderQuantity | +The maximum number of orderable units that can be ordered according to details provided + in the catalogue line, such as price. | -dct:Location -> at-voc:country [0..1] locn:Address -> at-voc:country [0..1] |
+ epo-cat:CatalogueLine -> epo:Quantity [0..1] |
| epo:hasCountryOfBirth | -The country in which the Person was born. + | epo-cat:hasMinimumQuantityGuaranteedForDelivery | +The minimum quantity of an item that is guaranteed by the seller to be delivered. + | -person:Person -> at-voc:country [0..1] | +epo-cat:CatalogueLine -> epo:Quantity [0..1] |
| epo:hasCurrency | -The identifier of the currency as in the standard code list used. - - | -epo:MonetaryValue -> at-voc:currency [0..1] | +epo-cat:hasModel | ++ | epo-cat:Item -> epo-cat:ItemModel [0..1] |
| epo:hasDirectAwardJustification | -List of reasons for using a procedure which allows awarding contracts directly without - publishing a notice. - - WG Approval 28/05/2020 + | epo-cat:hasNetMonetaryValue | +The price amount of an Item exclusive of taxes and after substracting price discounts. | -epo:DirectAwardTerm -> at-voc:direct-award-justification [0..1] | +epo-cat:Price -> epo:MonetaryValue [1] |
| epo:hasDocumentRestrictionJustification | -An explanation about the reasons why some procurement documents are restricted. - - Additional Information: - This corresponds in eForms to BT-707 Documents Restricted Justification. - - WG Approval 09/03/2021 + | epo-cat:hasNetQuantity | +The net quantity of the item that is contained in each consumable unit, excluding + any packaging materials. | -epo:AccessTerm -> at-voc:communication-justification [0..1] | +epo-cat:Item -> epo:Quantity [0..1] |
| epo:hasDPSScope | -Explanation as to whether a dps is used and by whom. + | epo-cat:hasOrderabableUnitFactorRate | +The factor by which the base unit of the price can be converted to orderable unit. - Additional Information: - This corresponds in eForms to BT-766 Dynamic Purchasing System. - WG Approval 09/11/2021 - Explanation as to whether a dps is used and by whom. - WG Approval 09/11/2021 + Additional information: + This is needed when the base price is provided different than the orderable unit. + For example, when selling paper, the price may be set per page, but the orderable + unit is a package of 500 pieces. Therefore the price needs to be converted to the + orderable unit. - The codelist to be used is at-voc:dps-usage which is available at http://publications.europa.eu/resource/dataset/dps-usage | -epo:DynamicPurchaseSystemTechnique -> at-voc:dps-usage [0..1] | + +epo-cat:Price -> epo:Quantity [0..1] |
| epo:hasECataloguePermission | -The extent to which electronic catalogues may be used in tenders. - - WG Approval 03/10/2019 - | -epo:SubmissionTerm -> at-voc:permission [0..1] | +epo-cat:hasOrderableUnit | +The unit in which the item described in this catalogue line can be ordered. | +epo-cat:CatalogueLine -> at-voc-new:orderable-unit [0..1] |
| epo:hasEInvoicingPermission | -- | epo:ContractTerm -> at-voc:permission [0..1] | +epo-cat:hasPrice | ++ | epo-ord:OrderLine -> epo-cat:Price [0..1] epo-cat:CatalogueLine -> epo-cat:Price [1..*] |
| epo:hasElectronicDigest | +epo-cat:hasPriceType | - | epo:Document -> epo:Document [0..*] | +epo-cat:Price -> at-voc-new:price-type [0..1] | |
| epo:hasElectronicSignature | -- | epo:Document -> epo:ElectronicSignature [0..*] | +epo-cat:hasPriceValidity | +The period of time when the Item can be ordered to the given price. + | +epo-cat:Price -> epo:Period [1] |
| epo:hasEndpointIdentifier | +epo-cat:hasQualifiedItemRelation | - | cv:Channel -> adms:Identifier [0..*] | +epo-cat:Item -> epo-cat:ItemRelation [0..*] | |
| epo:hasEstimatedBuyerConcessionRevenue | -The expected payments made by the buyer to the economic operator awarded the concession - that are not directly related to the use of the concession. - - <u>Additional Information:</u> - For example the public buyer pays a yearly fee to provide a ticketing solution to - the public. The fee the public pays for every ticket sold through the solution is - not included in this estimation but in the estimation of the user concession revenue. + | epo-cat:hasQualifiedValue | +Qualified value of the property, which is defined in a classification scheme. - This corresponds to BT-160 in eForms. + Additional Information: + For example, the (0173-1#02-AAA026#007) drilling diameter of an item has value of + 12 inches. - WG Approval 07/01/2020 | -epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | + WG approval 28/07/2022 +epo-cat:ItemProperty -> epo:Quantity [0..1] |
| epo:hasEstimatedDuration | -Relation indicating a Contract has an estimated Duration. - - Additional Information - - When the Lot uses a Technique the contract estimated duration applies to the Technique. - | -epo:Contract -> epo:Duration [0..1] | +epo-cat:hasQuantity | ++ | epo-ord:OrderLine -> epo:Quantity [1] epo-con:Deliverable -> epo:Quantity [0..1] |
| epo:hasEstimatedUserConcessionRevenue | -The estimated revenue coming from the use of the concession. - - Additional Information: - Revenues are for example fees and fines. For example, the fees and fines coming from - the cars using a motorway. - - This corresponds to BT-162 in eForms. - | -epo:ConcessionEstimate -> epo:MonetaryValue [0..1] | +epo-cat:hasQuantityThreshold | +The minimum quantity of the item that can be ordered to the given net monetary value. | +epo-cat:Price -> epo:Quantity [0..1] |
| epo:hasEstimatedValue | -A forecast of the value of the procurement before competition. - - Additional Information: - Different cases of estimated values may refer to a lot, the global value of the procedure, - or of a combinatorial value of a group of lots. - The forecast is calculated by the buyer and covers all revenues whether coming from - the buyer or third parties. - See for example recital (19), Article 5 of Directive 2014/24/EU and other articles - from the rest of Directives about procurement. - - In the case of framework agreements and dynamic purchasing systems this refers to - the maximum estimated value. - - This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used - for BT-157 (for LotGroup). - <b> - </b>WG Approval 05/12/2019 - A forecast of the value of the procurement before competition. + | epo-cat:hasSpecification | ++ | epo-cat:Item -> epo-cat:ProductSpecification [0..*] | +|
| epo-cat:hasStandardisedUnitPrice | +The item price based on a standardised unit. Additional Information: - Different cases of estimated values may refer to a lot, the global value of the procedure, - or of a combinatorial value of a group of lots. - The forecast is calculated by the buyer and covers all revenues whether coming from - the buyer or third parties. - See for example recital (19), Article 5 of Directive 2014/24/EU and other articles - from the rest of Directives about procurement. - - In the case of framework agreements and dynamic purchasing systems this refers to - the maximum estimated value. - - This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used - for BT-157 (for LotGroup). - <b> - </b><b>WG Approval 05/12/2019</b> - - | -epo:LotGroup -> epo:MonetaryValue [0..1] epo:ProcurementElement -> epo:MonetaryValue [0..1] |
+ The unit must be indicated in the Quantity, with a quantity value of 1.
+ epo-cat:CatalogueLine -> epo-cat:Price [0..*] | ||
| epo:hasESubmissionPermission | -The requirements as to what extent electronic submission is allowed. - - WG Approval 03/10/2019 - - | -epo:SubmissionTerm -> at-voc:permission [0..1] | +epo-cat:hasTaxCategory | ++ | epo-ord:TaxInformation -> at-voc-new:tax-category [0..1] |
| epo:hasFinancialOfferValue | -The value offered by the Tenderer for a Lot. - - Additional Information: - This value is normally the one awarded for a winning Tender Lot. In case of negotiated - procedures the original financial value may be reviewed and the offer updated. - - This corresponds to BT-720 in eForms. | -epo:Tender -> epo:MonetaryValue [0..1] | +epo-cat:hasTaxScheme | ++ | epo-ord:TaxInformation -> at-voc-new:tax-scheme [0..1] |
| epo:hasFixedValueType | -The method to interpret the fixed value as pertaining to a total or unit. - - WG Approval 17/09/2019 - + | epo-cat:hasTransactionConditionsCode | +Coded description of the specific transaction conditions (purchasing, sales, payment) + for an item. | -epo:AwardCriterion -> at-voc:number-fixed [0..1] | +epo-cat:CatalogueLine -> at-voc-new:transaction-conditions [0..1] | +
| epo-cat:isProductionOf | ++ | epo-cat:Batch -> epo-cat:Item [1] | +|||
| epo-cat:isRelatedToItem | ++ | epo-cat:ItemRelation -> epo-cat:Item [1] | |||
| epo:hasFormType | -A categorisation of the steps in which the Notice is used. - - WG Approval 12/05/2020 - - | -epo:Notice -> at-voc:form-type [0..1] | +epo-cat:isSpecificToCatalogueResponseLine | ++ | epo-cat:CatalogueResponseInformation -> epo-cat:CatalogueResponseLine [0..1] |
| epo:hasFrameworkAgreementMaximumValue | +epo-cat:isSpecificToLine | - | epo:LotAwardOutcome -> epo:MonetaryValue [0..1] | +epo-cat:InformationHub -> epo-cat:Line [0..*] | |
| epo:hasFrameworkAgreementType | -The form of framework agreement used in a procurement procedure. - - Addition information: - - A concept to distinguish the different types of framework agreement, which are: - 1. Framework agreement without reopening of competition, - 2. Framework agreement with reopening of competition, or - 3. Framework agreement partly without reopening of competition. - - WG Approval 19/09/2019 - - | -epo:FrameworkAgreementTerm -> at-voc:framework-agreement [1] | +epo-cat:isSubordinatedToContract | ++ | epo-cat:Catalogue -> epo:Contract [0..1] |
| epo:hasFundProgramme | +epo-cat:refersToCatalogue | - | epo:Fund -> at-voc:EU-programme [0..1] | +epo-cat:CatalogueResponse -> epo-cat:Catalogue [1] | |
| epo:hasGroupFrameworkAgreementMaximumValue | -This corresponds to BT-156 in the eForms. | -epo:LotGroupAwardInformation -> epo:MonetaryValue [0..1] | +epo-cat:refersToCatalogueLine | ++ | epo-cat:CatalogueResponseLine -> epo-cat:CatalogueLine [1] |
| epo:hasHighestReceivedTenderValue | -Amount of the Tender with the highest value. - - Additional Information - The value must correspond to an admissible tender. For example, tenders compliant - with the procurement document requirements, not having an abnormally low price or - cost, etc. - - - WG Approval 12/12/2019 - - - | -epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1] | +epo-cat:specifiesCatalogueResponseInformation | ++ | epo-cat:CatalogueResponse -> epo-cat:CatalogueResponseInformation [1] |
| epo:hasInternalIdentifier | -- | epo:LotGroup -> adms:Identifier [0..*] epo:ProcurementElement -> adms:Identifier [0..*] |
+ epo-cat:specifiesChargeInformation | ++ | epo-ord:Order -> epo-cat:ChargeInformation [0..*] |
| epo:hasIrregularityType | -Additional information: - This relation corresponds in eForms to BT-636 Buyer Review Requests Irregularity - Type | -epo:ReviewIrregularitySummary -> at-voc:irregularity-type [1] | +epo-cat:specifiesItem | ++ | epo-cat:Line -> epo-cat:Item [1] |
| epo:hasItemCountryOfOrigin | -The source country of the product or service. - - Additional Information: - - The country of origin can be provided by the buyer as a requirement or by the tenderer - information of the item to be provided. - - WG Approval 07/01/2020 - - The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country | -epo:Tender -> at-voc:country [0..*] | +epo-ful:agreedByBuyer | ++ | epo-ful:ShipmentAgreement -> epo:Buyer [1..*] |
| epo:hasLabelType | -The label type such environmental, quality, social etc. | -epo:CertificationLabel -> at-voc-new:certification-label-type [0..1] | +epo-ful:agreedBySeller | ++ | epo-ful:ShipmentAgreement -> epo-ord:Seller [1..*] |
| epo:hasLanguage | -Language in which the submitted information is to be expressed. - - WG Approval 21/07/2020 - - | -epo:SubmissionTerm -> at-voc:language [0..*] | +epo-ful:comprisesDespatchLine | ++ | epo-ful:DespatchAdvice -> epo-ful:DespatchLine [1..*] |
| epo:hasLateSubmissionPermission | -Whether economic operator-related information can be supplemented even after the submission - deadline. - - Additional Information - This is specific to the information on the economic operator and not the actual offer. - This does not apply to the requests for clarification. - - WG Approval 21/07/2020 - | -epo:SubmissionTerm -> at-voc:missing-info-submission [0..1] | +epo-ful:comprisesReceiptAdviceLine | ++ | epo-ful:ReceiptAdvice -> epo-ful:ReceiptAdviceLine [0..*] |
| epo:hasLaunchFrameworkAgreementMaximumValue | -- | epo:ProcurementObject -> epo:MonetaryValue [0..1] epo:LotGroup -> epo:MonetaryValue [0..1] |
+ epo-ful:containsGoodsItem | ++ | epo-ful:Package -> epo-ful:GoodsItem [1..*] |
| epo:hasLegalBasis | -The legal basis under which the procurement procedure takes place. - - Additional Information: - For example European Directives or Regulations, national laws etc. - The recommended code list is the example for the legal basis at the European level. - - WG 04/04/2023 - - The legal basis under which the procurement procedure takes place. - - Additional Information: - For example European Directives or Regulations, national law - - WG 09/11/2021 + | epo-ful:containsPackage | ++ | epo-ful:Package -> epo-ful:Package [0..*] | +|
| epo-ful:containsTransportHandlingUnit | ++ | epo-ful:Consignment -> epo-ful:TransportHandlingUnit [1..*] | +|||
| epo-ful:hasAllowanceChargeReason | +https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL5189/ - The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis - | -epo:ProcurementObject -> at-voc:legal-basis [0..*] | + https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7161/ +epo-ord:AllowanceChargeInformation -> at-voc-new:allowance-charge-reason [0..1] | ||
| epo:hasLegalIdentifier | +epo-ful:hasAssociatedDocument | ++ | epo-ful:ReceiptAdvice -> epo:Document [0..1] epo-ful:DespatchAdvice -> epo:Document [0..1] epo-ful:DespatchLine -> epo:Document [0..1] |
+ ||
| epo-ful:hasCarrierConsignmentID | - | org:Organization -> adms:Identifier [0..*] | +epo-ful:Consignment -> adms:Identifier [0..1] | ||
| epo:hasLotReference | +epo-ful:hasChargeableWeight | - | epo:Contract -> epo:Lot [1..*] | +epo-ful:Consignment -> epo:Quantity [0..1] | |
| epo:hasLowestReceivedTenderValue | -Amount of the Tender with the lowest value. - - Additional Information - The value must correspond to an admissible tender. For example, tenders compliant - with the procurement document requirements, not having an abnormally low price or - cost, etc. - - WG Approval 12/12/2019 - - | -epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1] | +epo-ful:hasConsigneeConsignmentID | ++ | epo-ful:Consignment -> adms:Identifier [0..1] |
| epo:hasMainActivity | -The principal sectoral area in which an organisation operates. - - Additional information: - - The activities associated with buyers are derived from the top level of the Classification - of the functions of the government (COFOG) from the United Nations Statistics Division. - - The activities associated with buyer are derived from sectors explicitly falling within - the sectoral directive (2014/25/EU Art. 8 - Art. 14). - - WG Approval 05/05/2020 - - | -org:Organization -> at-voc:main-activity [0..1] | +epo-ful:hasConsignmentDeclaredStatisticsValue | ++ | epo-ful:Consignment -> epo:MonetaryValue [0..1] |
| epo:hasMainClassification | +epo-ful:hasConsignmentFreeOnBoardValue | - | epo:Purpose -> at-voc:cpv [1..*] | +epo-ful:Consignment -> epo:MonetaryValue [0..1] | |
| epo:hasMaximumFrameworkAgreementAwardedValue | -The maximum value which can be spent through all the framework agreements announced - in this notice, including options and renewals of contracts. + | epo-ful:hasConsignmentInvoiceValue | +Declared amount of the Consignment. - Additional information: - - The value provided is a threshold value that implicity means that it cannot be exceeded - however it may not be reached during the execution of a contract. - - The Framework Agreements in a CAN are to be traced back and added to provide this - value. - - This corresponds to the BT-118 in eForms. + Additional Information: - WG Approval 03/12/2019 | -epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | + This is a logistics information needed for logistics, security measures, customs check, + etc. +epo-ful:Consignment -> epo:MonetaryValue [0..1] |
| epo:hasMember | +epo-ful:hasDeclaredStatisticalValue | - | epo:OrganisationGroup -> org:Organization [1..*] | +epo-ful:GoodsItem -> epo:MonetaryValue [0..*] | |
| epo:hasNationality | -- | -person:Person -> at-voc:country [0..*] | +epo-ful:hasDepartureShipmentInformation | ++ | epo-ful:ShipmentStage -> epo-ful:ShipmentInformation [0..*] |
| epo:hasNonAwardJustification | -On hold; Enumeration. - - + | epo-ful:hasDespatchAdviceType | +https://test-docs.peppol.eu/logistics/transport-execution/codelist/DespatchAdviceTypeCode/ | -epo:AwardOutcome -> at-voc:non-award-justification [0..1] | +epo-ful:DespatchAdvice -> at-voc-new:despatch-advice-type [0..1] |
| epo:hasNonElectronicSubmissionJustification | -- Reason for not accepting electronic information. - - WG Approval 21/07/2020 - | -epo:SubmissionTerm -> at-voc:communication-justification [0..*] | +epo-ful:hasDespatchedQuantity | +Quantity despatched for delivered. | +epo-ful:DespatchLine -> epo:Quantity [1] |
| epo:hasNonPublicationJustification | -The reason why data is not published. - WG Approval 11/06/2020 - | -epo:NonPublishedInformation -> at-voc:non-publication-justification [1] | +epo-ful:hasEstimatedDeliveryPeriod | ++ | epo-ful:ShipmentInformation -> epo:Period [0..1] |
| epo:hasNoticeType | +epo-ful:hasFreightAllowanceCharge | - | epo:Notice -> at-voc:notice-type [1] | +epo-ful:Consignment -> epo-cat:ChargeInformation [0..*] | |
| epo:hasNutsCode | +epo-ful:hasFreightForwarderConsignmentID | ++ | epo-ful:Consignment -> adms:Identifier [0..1] | +||
| epo-ful:hasGrossVolume | - | dct:Location -> at-voc:nuts [0..1] locn:Address -> at-voc:nuts [0..1] |
+ epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:Consignment -> epo:Quantity [0..1] |
||
| epo:hasOfficialLanguage | -The language(s) in which the instances of the given concepts are officially available. - These linguistic versions are equally legally valid. - - WG Approval 03/10/2019 - - | -epo:Document -> at-voc:language [1..*] | +epo-ful:hasGrossWeight | ++ | epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:Consignment -> epo:Quantity [0..1] |
| epo:hasPerformingStaffQualificationInformation | -- Additional information: - - This relation corresponds in eForms to BT-79.Explanation as to if and/or when information - of the persons to carry out the contract is to be provided. - WG Approval 09/11/2021 - - The codelist to be used is at-voc:requirement-stage which is available at http://publications.europa.eu/resource/dataset/requirement-stage - | -epo:ProcurementCriterion -> at-voc:requirement-stage [0..*] | +epo-ful:hasHandlingInstructionCode | ++ | epo-ful:Consignment -> at-voc-new:handling-instruction [0..1] epo-ful:TransportHandlingUnit -> at-voc-new:handling-instruction [0..1] |
| epo:hasPlannedDuration | +epo-ful:hasHeight | - | epo:PlannedProcurementPart -> epo:Duration [0..1] | +epo-ful:AbstractContainer -> epo:Quantity [0..1] | |
| epo:hasPlannedPeriod | +epo-ful:hasLength | - | epo:PlannedProcurementPart -> epo:Period [0..1] | +epo-ful:AbstractContainer -> epo:Quantity [0..1] | |
| epo:hasPrimaryContactPoint | +epo-ful:hasLoadingLength | - | org:Organization -> cpov:ContactPoint [0..1] | +epo-ful:Consignment -> epo:Quantity [0..1] | |
| epo:hasPrizeValue | -The monetary value of a prize, if any, for the winner (or runners-up) of the design - contest. - - Additional Information: - This corresponds to BT-644 in eForms. - - WG Approval 29/08/2019 - - | -epo:Prize -> epo:MonetaryValue [0..1] | +epo-ful:hasMainCarriageShipmentStage | ++ | epo-ful:Consignment -> epo-ful:ShipmentStage [0..1] |
| epo:hasProcedureType | -Identification of the Procedure used. - - WG Approval 09/06/2020 - | -epo:Procedure -> at-voc:procurement-procedure-type [1] | +epo-ful:hasMaximumTemperature | ++ | epo-ful:TemperatureSpecification -> epo:Quantity [0..1] |
| epo:hasProcurementHighestReceivedTenderValue | -The highest received tender value for the procurement. - - Additional Information: - This corresponds to section II.1.7.3. according to Regulation (EU) 2015/1986. | -epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +|||
| epo-ful:hasMinimumTemperature | ++ | epo-ful:TemperatureSpecification -> epo:Quantity [0..1] | |||
| epo:hasProcurementLowestReceivedTenderValue | -The lowest received tender value for the procurement. - - Additional Information: - This corresponds to section II.1.7.2. according to Regulation (EU) 2015/1986. | -epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +epo-ful:hasNetVolume | ++ | epo-ful:AbstractContainer -> epo:Quantity [0..1] |
| epo:hasProcurementScopeDividedIntoLot | +epo-ful:hasNetWeight | ++ | epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:Consignment -> epo:Quantity [0..1] |
+ ||
| epo-ful:hasOnCarriageShipmentStage | - | epo:Procedure -> epo:Lot [1..*] | +epo-ful:Consignment -> epo-ful:ShipmentStage [0..*] | ||
| epo:hasPurpose | -Relation indicating the Purpose of a concept. | -epo:Contract -> epo:Purpose [0..1] epo:ProcurementObject -> epo:Purpose [0..1] |
+ epo-ful:hasOutstandingQuantity | ++ | epo-ful:DespatchLine -> epo:Quantity [0..1] |
| epo:hasQualificationSystemDuration | +epo-ful:hasOversupplyQuantity | - | epo:MultipleStageProcedureTerm -> epo:Duration [0..1] | +epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] | |
| epo:hasReceivedSubmissionType | +epo-ful:hasPackagingType | - | epo:SubmissionStatisticalInformation -> at-voc:received-submission-type [0..1] | +epo-ful:Package -> at-voc-new:packaging-type [0..1] | |
| epo:hasRegistrationCountry | +epo-ful:hasPreCarriageShipmentStage | - | org:Organization -> at-voc:country [0..1] | +epo-ful:Consignment -> epo-ful:ShipmentStage [0..*] | |
| epo:hasRemedyValue | -Additional information: - This relation corresponds in eForms to BT-793 Review Remedy Value. | -epo:ReviewDecision -> epo:MonetaryValue [0..1] | +epo-ful:hasReceivedQuantity | ++ | epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] |
| epo:hasReservedExecution | +epo-ful:hasRejectReason | - | epo:ContractTerm -> at-voc:applicability [0..1] | +epo-ful:ReceiptAdviceLine -> at-voc-new:reject-reason [0..1] | |
| epo:hasReservedProcurement | -Explanation as to whether a procurement may be reserved for the participation of certain - types of organisation. - - Additional information: - This property corresponds in eForms to the BT-71 - WG Approval 09/11/2021 - Explanation as to whether a procurement may be reserved for the participation of certain - types of organisation. - - Additional information: - This property corresponds in eForms to the BT-71 - WG Approval 09/11/2021 - | -epo:ParticipationCondition -> at-voc:reserved-procurement [0..*] epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*] |
+ epo-ful:hasRequestedPickUpInformation | ++ | epo-ful:Consignment -> epo-ful:ShipmentInformation [1] |
| epo:hasReviewBodyType | +epo-ful:hasShortageAction | - | epo:Reviewer -> at-voc:review-body-type [0..*] | +epo-ful:ReceiptAdviceLine -> at-voc-new:action-code [0..1] | |
| epo:hasReviewDecisionType | -Additional information: - This relation corresponds in eForms to BT-790 Review Decision Type. | -epo:ReviewDecision -> at-voc:review-decision-type [0..*] | +epo-ful:hasShortQuantity | ++ | epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] |
| epo:hasReviewIrregularitySummary | -Additional information: - This relation corresponds in eForms to BG-613 Buyer Review Requests | -epo:ReviewRequestSummary -> epo:ReviewIrregularitySummary [0..*] | +epo-ful:hasSizeType | ++ | epo-ful:TransportEquipment -> at-voc-new:size-type [0..*] |
| epo:hasReviewRequestFee | -Additional information: - This relation corresponds in eForms to BT-795 Review Request Fee. | -epo:ReviewRequest -> epo:MonetaryValue [0..1] | +epo-ful:hasTemperatureSpecification | ++ | epo-ful:AbstractContainer -> epo-ful:TemperatureSpecification [0..1] |
| epo:hasSelectionCriteriaUsage | -- Additional Information: - This corresponds in eForms to BT-748 Selection Criteria Used. | -epo:SelectionCriterion -> at-voc:usage [0..1] | +epo-ful:hasTotalGoodsItemQuantity | ++ | epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:Consignment -> epo:Quantity [0..1] |
| epo:hasSelectionCriterionType | -The classification of the selection criteria. + | epo-ful:hasTraceID | +The identifier used for tracking the goods item + Additional information: + An example is the EPC number used in RFID. - Additional Information: - - This corresponds in eForms to BT-747 Selection Criteria Type. - - WG Approval 09/11/2021 + WG approval 21/09/2023 | -epo:SelectionCriterion -> at-voc:selection-criterion [0..1] | +epo-ful:GoodsItem -> adms:Identifier [0..1] |
| epo:hasStartDate | +epo-ful:hasTrackingID | - | epo:SelectedCandidateList -> epo:Period [0..1] | +epo-ord:DeliveryInformation -> adms:Identifier [0..1] | |
| epo:hasSubcontracting | +epo-ful:hasTransportEquipmentSeal | - | epo:Tender -> at-voc:applicability [0..1] | +epo-ful:TransportEquipment -> epo-ful:TransportEquipmentSeal [0..*] | |
| epo:hasSubcontractingEstimatedValue | -The estimated value of a single subcontract. - - This relates to BT-553 in eForms. - - WG Approval 01/09/2020 - - | -epo:SubcontractingEstimate -> epo:MonetaryValue [0..1] | +epo-ful:hasTransportEquipmentType | ++ | epo-ful:TransportEquipment -> at-voc-new:transport-equipment-type [0..*] |
| epo:hasSubcontractingObligation | -The requirement the tender must meet with regard to subcontracting parts of the contract. - WG Approval 09/11/2021 - - | -epo:SubcontractTerm -> at-voc:subcontracting-obligation [0..*] | +epo-ful:hasTransportHandlingUnitQuantity | ++ | epo-ful:Consignment -> epo:Quantity [0..1] |
| epo:hasTaxIdentifier | +epo-ful:hasTransportMeansType | - | org:Organization -> adms:Identifier [0..*] | +epo-ful:TransportMeans -> at-voc-new:transport-means-type [0..1] | |
| epo:hasTenderSubcontractingInformation | -The information about subcontracting that must be indicated in the tender. - - WG Approval 10/10/2019 - - | -epo:SubmissionTerm -> at-voc:subcontracting-indication [0..*] | +epo-ful:hasTransportMode | ++ | epo-ful:TransportMeans -> at-voc-new:transport-mode [1] |
| epo:hasTenderValidityDuration | +epo-ful:hasVehicleID | - | epo:SubmissionTerm -> epo:Duration [0..1] | +epo-ful:TransportMeans -> adms:Identifier [1] | |
| epo:hasTenderValidityPeriod | -The relation indicating until when a tender instance is applicable. - | -epo:SubmissionTerm -> epo:Period [0..1] | +epo-ful:hasVehicleSegmentID | ++ | epo-ful:TransportMeans -> adms:Identifier [0..1] |
| epo:hasThresholdType | -The method to interpret the threshold value as minimum or a maximum. - - WG Approval 17/09/2019 - | -cccev:Constraint -> at-voc:number-threshold [0..*] | +epo-ful:hasWidth | ++ | epo-ful:AbstractContainer -> epo:Quantity [0..1] |
| epo:hasTimePeriod | -- - | -epo:Period -> at-voc:timeperiod [1..*] | +epo-ful:isSpecificToDespatchLine | ++ | epo-ful:ShipmentInformation -> epo-ful:DespatchLine [0..1] |
| epo:hasTotalAwardedValue | -The awarded value of all lots announced in this notice, including options and renewals. - - - Additional information: - The values of the individual Lots awarded under a framework agreement and mentioned - in this notice are included. - - The values of the individual lots announced in a CAN are to be traced back and added - to provide this value. - - This corresponds to the BT-161 in eForms. - - WG Approval 03/12/2019 - | -epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] | +epo-ful:isSubmittedForDespatchAdvice | +Additional information: + In PEPPOL (https://test-docs.peppol.eu/logistics/qa/codelist/ReceiptAdviceTypeCode/) + this predicate is used for option D - Response to the Advanced Despatch Advice document. | +epo-ful:ReceiptAdvice -> epo-ful:DespatchAdvice [0..1] |
| epo:hasTotalQuantity | -The number of units required. - - Additional Information: - The quantity needs to go along with the unit. - - - - | -epo:Purpose -> epo:Quantity [0..1] | +epo-ful:isSubmittedForDespatchLine | ++ | epo-ful:ReceiptAdviceLine -> epo-ful:DespatchLine [1] |
| epo:hasTotalValue | -- | epo:TenderGroup -> epo:MonetaryValue [0..1] |
+ epo-ful:isSubmittedForShipment | ++ | epo-ful:ReceiptAdvice -> epo-ful:ShipmentInformation [0..1] |
| epo:hasUnitCode | +epo-ful:refersToConsignment | - | epo:Quantity -> at-voc:measurement-unit [1] | +epo-ful:DespatchAdvice -> epo-ful:Consignment [1] | |
| epo:hasUnofficialLanguage | -The language translation(s) in which the instances of the given concepts are available. - These linguistic versions are not an official translation, they are provided only - for information. - - WG Approval 03/10/2019 - | -epo:Document -> at-voc:language [0..*] | +epo-ful:refersToDeliveryInformation | ++ | epo-ful:ShipmentInformation -> epo-ord:DeliveryInformation [1] |
| epo:hasUsage | -The codelist to be used is at-voc:usage which is available at http://publications.europa.eu/resource/dataset/usage - | -epo:Technique -> at-voc:usage [0..1] | +epo-ful:refersToDespatchLine | ++ | epo-ful:GoodsItem -> epo-ful:DespatchLine [1] |
| epo:hasUUID | -A universally unique identifier for an instance of this document. - - WG Approval 12/05/2020 A universally unique identifier for an instance of this document. - - WG Approval 12/05/2020 - | -epo:Document -> adms:Identifier [0..1] |
+ epo-ful:refersToOrder | ++ | epo-ful:DespatchAdvice -> epo-ord:Order [0..1] |
| epo:hasValidityPeriod | -The relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023 - The relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023 | -cccev:Evidence -> epo:Period [0..1] epo:Technique -> epo:Period [0..1] |
+ epo-ful:refersToOrderLine | ++ | epo-ful:DespatchLine -> epo-ord:OrderLine [0..1] |
| epo:hasVariantPermission | -The obligation or possibility for tenderers to submit variants or not. - - Additional Information: - - Variants are alternative ways to fulfil the buyer's needs as opposed to solutions - indicated in the procurement documents. - - eForms: Whether tenderers are required, allowed or forbidden to submit tenders which - fulfil the buyer's needs differently than as proposed in the procurement documents. - - - Additional Information: - - Further conditions for submitting variant tenders are in the procurement documents. - | -epo:SubmissionTerm -> at-voc:permission [0..1] | +epo-ful:refersToShipmentAgreement | ++ | epo-ful:DespatchAdvice -> epo-ful:ShipmentAgreement [0..1] |
| epo:hasWeightValueType | -No definition. Waiting on CCCEV alignment. - - - | -epo:ProcurementCriterion -> at-voc:number-weight [0..1] | +epo-ful:RejectionAction | ++ | epo-ful:ReceiptAdviceLine -> at-voc-new:action-code [0..1] |
| epo:includesAccessibilityCriterion | -Explanation as to whether accessibility Criterion are used or not. - WG Approval 09/11/2021 - - | -epo:StrategicProcurement -> at-voc:accessibility [0..*] | +epo-ful:specifiesBuyer | ++ | epo-ful:ReceiptAdvice -> epo:Buyer [0..1] |
| epo:includesNationalCriterion | -Relation indicating that a Criterion contains a Criterion that is specific to a given - Member State. - - Additional Information: - In the ESPD, a Subcriterion is used to define national sub-criteria; maps to a UBL-2.3 - cac:SubTenderingCriterion class. It is currently used only for purely national criteria, - to be able to establish the mapping from eCertis. - - WG approval 07/11/2023 - - | -epo:QualificationCriterion -> epo:QualificationCriterion [0..*] | +epo-ful:specifiesConsignee | ++ | epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*] epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*] |
| epo:includesTender | -Additional information: - This corresponds in eForms to BT-3202 Contract Tender Identifier. - | -epo:Contract -> epo:Tender [0..*] | +epo-ful:specifiesDespatcher | ++ | epo-ful:DespatchAdvice -> epo-ful:Despatcher [1..*] epo-ful:ReceiptAdvice -> epo-ful:Despatcher [1] |
| epo:indicatesAwardToWinner | -Reveals the winner to whom the tender award outcome is attributed. | -epo:TenderAwardOutcome -> epo:Winner [0..1] | +epo-ful:specifiesOriginator | ++ | epo-ful:DespatchAdvice -> epo-ord:Originator [0..*] | +
| epo-ful:specifiesPlaceOfDespatch | ++ | epo-ful:ShipmentInformation -> dct:Location [0..1] | +|||
| epo-ful:specifiesSeller | ++ | epo-ful:ReceiptAdvice -> epo-ord:Seller [0..1] | |||
| epo:indicatesInvoiceeContactPoint | +epo-ful:specifiesShipment | - | epo:Buyer -> cpov:ContactPoint [] | +epo-ful:DespatchAdvice -> epo-ful:ShipmentInformation [0..1] | |
| epo:involvesBuyer | +epo-ful:specifiesTransportHandlingUnits | - | epo:Procedure -> epo:Buyer [0..*] | +epo-ful:DespatchAdvice -> epo-ful:TransportHandlingUnit [0..*] | |
| epo:involvesProcurementDocument | +epo-ful:transportsItemFrom | - | epo:AccessTerm -> epo:ProcurementDocument [0..1] | +epo-ful:TransportHandlingUnit -> epo-ful:DespatchLine [1..*] | |
| epo:isBasedOnImplementingRegulation | -Indicates under which regulation a notice is created. - - WG Acceptance 06/09/2022 | -epo:Notice -> at-voc:legal-basis [0..1] | +epo-ful:usesTransportEquipment | ++ | epo-ful:TransportHandlingUnit -> epo-ful:TransportEquipment [0..*] |
| epo:isBeneficialOwnerOf | -A role of any natural person(s) who ultimately owns or controls the organisation or - on whose behalf a transaction or activity is being conducted. - Additional Information: - This role is defined in the directive EU 2015/849 and it's beyond the scope for public - eProcurement domain. - WG approval 14/09/2021 | -epo:Business [,0..*] <- person:Person | +epo-ful:usesTransportMeans | ++ | epo-ful:ShipmentStage -> epo-ful:TransportMeans [1..*] |
| epo:isExecutedByProcurementServiceProvider | +epo-not:announcesRole | - | epo:Procedure -> epo:ProcurementServiceProvider [0..1] | +epo-not:ResultNotice -> epo:AgentInRole [0..*] | |
| epo:isFundedBy | -Funding is provided either completely or partially by a Fund. - - Additional information: - This corresponds in eForms to BG - 61 EU Funds (specified per Lot) and to BG - 611 - Contract EU Funds (applied per Contract lot) - Funds may change between the lot and the contract, for example in the case of an emergency - crisis, a contract may be financed by a budget that was not foreseen in the call. - - Funding is provided either completely or partially by a Fund. - - Additional information: - This corresponds in eForms to BG - 61 EU Funds (specified per Lot) and to BG - 611 - Contract EU Funds (applied per Contract lot) - Funds may change between the lot and the contract, for example in the case of an emergency - crisis, a contract may be financed by a budget that was not foreseen in the call. - - | -epo:Contract -> epo:Fund [0..*] epo:ProcurementObject -> epo:Fund [0..*] |
+ epo-not:hasLegalBasis | ++ | epo-not:Modification-D24 -> Directive 24 [0..1] |
| epo:isOwnedByAgent | +epo-not:refersToRole | - | epo:System -> foaf:Agent [0..1] | +epo-not:ResultNotice -> epo:AgentInRole [1..*] | |
| epo:isResponsibilityOfBuyer | -The buyer in charge of the procedure. - - Additional Information: - In case there are multiple buyers, it may be the case that one or more buyers are - in charge of the procedure. - - | -epo:Procedure -> epo:Buyer [0..*] | +epo-ord:comprisesOrderLine | ++ | epo-ord:Order -> epo-ord:OrderLine [1..*] |
| epo:isSubjectToContractSpecificTerm | +epo-ord:comprisesOrderResponseLine | - | epo:Contract -> epo:ContractSpecificTerm [0..*] | +epo-ord:OrderResponse -> epo-ord:OrderResponseLine [0..*] | |
| epo:isSubjectToGrouping | +epo-ord:concernsConsignee | - | epo:Tender -> epo:LotGroup [0..1] | +epo-ord:DeliveryInformation -> epo-ord:Consignee [0..1] | |
| epo:isSubjectToLotSpecificTerm | +epo-ord:concernsContract | - | epo:Lot -> epo:LotSpecificTerm [0..*] | +epo-ord:ContractInformation -> epo:Contract [1] | |
| epo:isSubjectToProcedureSpecificTerm | +epo-ord:concernsOriginator | - | epo:Procedure -> epo:ProcedureSpecificTerm [1..*] | +epo-ord:OriginatorInformation -> epo-ord:Originator [1] | |
| epo:isSubjectToTerm | +epo-ord:concernsOriginatorRequest | - | epo:ProcurementObject -> epo:Term [0..*] | +epo-ord:OriginatorInformation -> epo:OriginatorRequest [0..1] | |
| epo:isSubmitedBy | -Relation indicating the submission of a tender by an economic operator. - WG approval 18/05/2021 | -epo:Tender -> epo:Tenderer [0..1] | +epo-ord:hasAcceptanceStatus | ++ | epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1] epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus [1] |
| epo:isSubmittedForLot | +epo-ord:hasAmountDueForPayment | - | epo:Tender -> epo:Lot [1] | +epo-ord:Order -> epo:MonetaryValue [1] | |
| epo:isSubmittedForLotGroup | +epo-ord:hasDeliveryPeriod | ++ | epo-ord:OrderResponseInformation -> epo:Period [0..1] epo-ord:DeliveryInformation -> epo:Period [0..1] |
+ ||
| epo-ord:hasPrepaidAmount | - | epo:TenderGroup -> epo:LotGroup [1] | +epo-ord:Order -> epo:MonetaryValue [0..1] | ||
| epo:issuedByCertifier | -Relation indicating the Certifier responsible for providing the ItemCertificate. - - Additional Information: - Certifier is a role played by an organisation. - - WG approval 26/07/2022 | -epo:Certificate -> epo:Certifier [0..1] | +epo-ord:hasPriceDiscountInformation | ++ | epo-cat:Price -> epo-ord:AllowanceInformation [0..1] |
| epo:leadBy | -The epo:OrganisationGroup epo:leadBy org:Organization was implemented to be used in - case of an Economic Operator Group. | -epo:OrganisationGroup -> org:Organization [0..1] | +epo-ord:hasRoundingAmount | ++ | epo-ord:Order -> epo:MonetaryValue [0..1] |
| epo:needsToBeATenderer | -The Winner must be a Tenderer. | -epo:Winner -> epo:Tenderer [0..1] | +epo-ord:hasSellerOrderID | ++ | epo-ord:Order -> adms:Identifier [0..1] |
| epo:needsToBeAWinner | -The Contractor must be a Winner. - | -epo:Contractor -> epo:Winner [0..1] | +epo-ord:hasTaxInformation | ++ | epo:Contract -> epo-ord:TaxInformation [0..1] epo-cat:Item -> epo-ord:TaxInformation [0..*] epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation [0..1] |
| epo:ownsSystem | +epo-ord:hasTotalAllowanceAmount | - | epo:System [,0..*] <- foaf:Agent | +epo-ord:Order -> epo:MonetaryValue [0..1] | |
| epo:playedBy | -- | epo:AgentInRole -> foaf:Agent [1] epo:JuryMember -> person:Person [0..1] |
+ epo-ord:hasTotalChargeAmount | ++ | epo-ord:Order -> epo:MonetaryValue [0..1] |
| epo:providesContractTotalPaymentValue | -Additional Information: - This corresponds to BT-779 in eForms. | -epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] | +epo-ord:hasTotalLineAmount | ++ | epo-ord:Order -> epo:MonetaryValue [1] |
| epo:providesContractTotalPenaltyValue | -- Additional Information: - This corresponds to BT-782 in eForms. - | -epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] | +epo-ord:hasTotalTaxExclusiveAmount | ++ | epo-ord:Order -> epo:MonetaryValue [0..1] |
| epo:providesRulingOnRemedy | -States the measures to be taken after a review procedure. | -epo:ReviewDecision -> at-voc:remedy-type [0..*] | +epo-ord:hasTotalTaxInclusiveAmount | ++ | epo-ord:Order -> epo:MonetaryValue [0..1] |
| epo:refersToContract | +epo-ord:implementsContract | - | epo:ContractLotCompletionInformation -> epo:Contract [1] | +epo-ord:OrderResponse -> epo:Contract [0..1] | |
| epo:refersToLot | -- | epo:Notice -> epo:Lot [1..*] |
+ epo-ord:isSpecificToOrderLine | +Information that is particular to one or multiple Order Lines. + Information that is particular to one or multiple Order Lines. + Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. + | +epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*] epo-ord:AllowanceInformation -> epo-ord:OrderLine [0..*] epo-ord:ContractInformation -> epo-ord:OrderLine [0..*] epo-ord:DeliveryInformation -> epo-ord:OrderLine [0..*] epo-ord:OriginatorInformation -> epo-ord:OrderLine [0..*] |
| epo:refersToNotice | +epo-ord:isSpecificToOrderResponseLine | - | epo:Notice -> epo:Notice [0..1] | +epo-ord:OrderResponseInformation -> epo-ord:OrderResponseLine [0..*] | |
| epo:refersToPlannedPart | +epo-ord:isSubmittedForOrder | - | epo:AccessTerm -> epo:PlannedProcurementPart [0..*] | +epo-ord:OrderResponse -> epo-ord:Order [1] | |
| epo:refersToPrevious | +epo-ord:isSubmittedForOrderLine | - | epo:Document -> epo:Document [0..*] | +epo-ord:OrderResponseLine -> epo-ord:OrderLine [1..*] | |
| epo:refersToPreviousNotice | +epo-ord:refersToCatalogue | - Additional information: - This corresponds in eForms to BT-758 Change Notice Version Identifier. | -epo:ChangeInformation -> epo:Notice [1] | + Additional information: + If an order refers to multiple catalogues then all these catalogues ideally are subordinated + to the same contract. + Some countries however may allow multiple contracts per order (i.e Italy). +epo-ord:Order -> epo-cat:Catalogue [0..*] | |
| epo:refersToPreviousProcedure | -Reference to a previous procedure. - + | epo-ord:refersToCatalogueLine | +Additional Information: - In the case of Direct Award Terms, this property points to a previous Procedure justifying - the use of Direct Award without a prior publication. - - This corresponds in the eForms to BT-1252 Direct Award Justification Previous - Procedure Identifier | -epo:DirectAwardTerm -> epo:Procedure [0..1] | + The reference to the catalogue line is for information only, to trace the source of + the information provided in the order line. +epo-ord:OrderLine -> epo-cat:CatalogueLine [0..1] |
| epo:refersToPreviousProcedureLot | -Reference to one or more Lots in a previous procedure. - - Additional Information: - In the case of Direct Award Terms, this property points to a previous Procedure justifying - the use of Direct Award without a prior publication. - - This corresponds in the eForms to BT-1252 Direct Award Justification Previous - Procedure Identifier - - WG Approval 22/11/2019 14:33:55 | -epo:DirectAwardTerm -> epo:Lot [0..*] | +epo-ord:specifiesAllowanceInformation | ++ | epo-ord:Order -> epo-ord:AllowanceInformation [0..*] |
| epo:refersToPreviousReview | -Additional information: - This relation corresponds in eForms to BT-785 "Review Previous Identifier". | -epo:ReviewObject -> epo:ReviewObject [0..1] | +epo-ord:specifiesBuyer | ++ | epo-ord:OrderResponse -> epo:Buyer [0..1] |
| epo:refersToProcedure | -- | epo:Notice -> epo:Procedure [1] |
+ epo-ord:specifiesContractInformation | ++ | +epo-ord:Order -> epo-ord:ContractInformation [0..*] |
| epo:relatesToEFormSectionIdentifier | -- | epo:ChangeInformation -> adms:Identifier [1..*] epo:NonPublishedInformation -> adms:Identifier [1..*] |
+ epo-ord:specifiesDeliveryAgreementLocation | ++ | epo-ord:DeliveryAgreement -> dct:Location [0..1] |
| epo:requestsRemedyType | -Additional information: - This relation corresponds in eForms to BT-792 Review Remedy Type | -epo:ReviewRequest -> at-voc:remedy-type [0..*] | +epo-ord:specifiesDeliveryInformation | ++ | epo-ord:Order -> epo-ord:DeliveryInformation [1..*] |
| epo:resolvesReviewRequest | +epo-ord:specifiesGeneralDeliveryAgreement | - | epo:ReviewDecision -> epo:ReviewRequest [1] | +epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement [0..1] | |
| epo:resultsFromLotAwardOutcome | -- | epo:DirectContract -> epo:LotAwardOutcome [0..*] epo:FrameworkAgreement -> epo:LotAwardOutcome [0..*] |
+ epo-ord:specifiesOrderResponseInformation | ++ | epo-ord:OrderResponse -> epo-ord:OrderResponseInformation [0..*] |
| epo:resultsFromMiniCompetitionAwardOutcome | +epo-ord:specifiesOriginatorInformation | - | epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome [0..1] | +epo-ord:Order -> epo-ord:OriginatorInformation [0..1] | |
| epo:resultsFromUsingCandidateList | +epo-ord:specifiesPlaceOfDelivery | - | epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList [0..1] | +epo-ord:DeliveryInformation -> dct:Location [0..1] | |
| epo:setsGroupingContextForLot | +epo-ord:specifiesSeller | - | epo:LotGroup -> epo:Lot [1..*] | +epo-ord:OrderResponse -> epo-ord:Seller [0..1] | |
| epo:signedByBuyer | +epo-ord:specifiesSpecificDeliveryAgreement | - | epo:Contract -> epo:Buyer [0..*] | +epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement [0..1] | |
| epo:signedByContractor | -- | epo:Contract -> epo:Contractor [0..*] | +epo-sub:answersQuestion | +Relation indicating that the Response replies to a question. + + WG approval 12/03/2024 | +epo-sub:Response -> cccev:InformationRequirement [0..*] |
| epo:signsAwardDecision | -- | epo:Buyer -> epo:AwardDecision [0..*] | +epo-sub:concernsOrganisation | +Relates to Organization. + + WG approval 05/03/2024 + + | +epo-sub:NationalPreQualificationData -> org:Organization [1] |
| epo:specifiesCleanVehicleDirectiveContractType | -- | epo:VehicleInformation -> at-voc:cvd-contract-type [0..1] | +epo-sub:hasMandate | +Relation indicating that a Legal Representative has a Mandate. + + WG approval 12/03/2024 | +epo-sub:LegalRepresentative -> epo-sub:Mandate [0..*] |
| epo:specifiesCleanVehicleDirectiveVehicleCategory | -- | epo:VehicleInformation -> at-voc:vehicle-category [0..1] | +epo-sub:hasPowerOfAttorney | +Relation indicating that a Legal Representative has a Power of Attorney. + + WG approval 12/03/2024 | +epo-sub:LegalRepresentative -> epo-sub:PowerOfAttorney [0..1] |
| epo:specifiesProcurementCriteriaSummary | -- | epo:Procedure -> epo:ProcurementCriteriaSummary [0..*] | +epo-sub:isReinforcedBy | +Relation indicating an Evidence that supports the Response. + + WG approval 12/03/2024 | +epo-sub:Response -> cccev:Evidence [0..*] |
| epo:specifiesProcurementCriterion | -- | epo:Lot -> epo:ProcurementCriterion [0..*] epo:LotGroup -> epo:ProcurementCriterion [0..*] |
+ epo-sub:providesInformationOn | +Offers information about an instance of a concept. + + WG approval 05/03/2024 | +epo-sub:ESPDResponse -> org:Organization [0..*] |
| epo:specifiesSubcontractors | -- | epo:Tender -> epo:Subcontractor [0..*] | +epo-sub:providesOrganisationEmployeeQuantity | +The number of people hired by the Organization. + + WG approval 05/03/2024 | +epo-sub:NationalPreQualificationData -> epo:Quantity [0..1] |
| epo:substantiatesExclusionGround | -- | epo:Tenderer -> epo:ExclusionGround [0..1] | +epo-sub:providesOrganisationFinancialCapability | +A monetary amount representing the financial capability of the Organization. + + Additional information: + Used to represent the general Turnover of the Organization (for statistical purposes). + + WG approval 05/03/2024 | +epo-sub:NationalPreQualificationData -> epo:MonetaryValue [0..1] |
| epo:summarisesInformationForAwardOutcome | -Relates to submission for the given competition, either at Lot level or Mini-Competition - level. + | epo-sub:providesOrganisationPreQualificationListingIdentifier | +The identifier assigned to an economic operator in a national pre-qualification system + or official list. - WG approval 30/05/2023 | -epo:SubmissionStatisticalInformation -> epo:AwardOutcome [1] | + WG approval 05/03/2024 +epo-sub:NationalPreQualificationData -> adms:Identifier [0..*] |
| epo:usesChannel | -- | epo:ProcurementElement -> cv:Channel [0..*] | +epo-sub:refersToApplicablePeriod | +Relation indicating the period to which the Response shall apply. + + WG approval 12/03/2024 | +epo-sub:Response -> epo:Period [0..1] |
| epo:usesTechnique | -- | epo:ProcurementObject -> epo:Technique [0..*] | +epo-sub:refersToOtherESPDResponse | +Reference to other European Single Procurement Document (ESPD) Response. + + WG approval 05/03/2024 | +epo-sub:ESPDResponse -> epo-sub:ESPDResponse [0..*] | +
| epo-sub:relatesToESPDRequest | +Is about an European Single Procurement Document (ESPD) Request. + + WG approval 05/03/2024 | +epo-sub:ESPDResponse -> epo-acc:ESPDRequest [1] | +|||
| epo-sub:specifiesResponse | +Relation indicating that an ESPD Response contains a Response. + + WG approval 12/03/2024 | +epo-sub:ESPDResponse -> epo-sub:Response [1..*] | +|||
| epo-sub:summarisesInformationAboutCertificate | +Relation indicating the Certificate that the information refers to. + + WG approval 12/03/2024 | +epo-sub:CertificateInformation -> epo:Certificate [1] | |||
| locn:address | diff --git a/implementation/ePO_core/conventions_report/ePO_core_convention_report.html b/implementation/ePO_core/conventions_report/ePO_core_convention_report.html index 058e15f5..0133ab62 100644 --- a/implementation/ePO_core/conventions_report/ePO_core_convention_report.html +++ b/implementation/ePO_core/conventions_report/ePO_core_convention_report.html @@ -19,7 +19,7 @@