Table of contents
Glossary
Class names and definitions
Class name | Definition |
---|---|
adms:Identifier | A character string to identify and distinguish uniquely, one instance of an object in an identification scheme from all other objects in the same scheme together with relevant supplementary information. |
cccev:Constraint | Limitation applied to an Information Concept. Additional Information: Constraints are Requirements in themselves, since they impose prerequisites which influence the definition, use and/or Fulfilment of the Requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying Organisation to select the Candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context. |
cccev:Criterion | Condition for evaluation or assessment. Additional Information: In general, Criteria are used for comparison, filtering or Selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the Requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as Exclusion Grounds, Selection Criteria or Award Criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an Exclusion Ground Criterion in the procurement domain or for requiring a public service. |
cccev:Evidence | Proof that a Requirement is met. Additional Information: The class Evidence provides the means to support responses to Criteria or to a concrete Information Requirement or to an Information Concept inside an Information Requirement. The proof described by an Evidence can [1] verify a claim (i.e. is it true that John is 25, yes/no), [2] prove a condition (i.e. is John 18+, yes/no), or [3] simply provide data (i.e. the age of a person, namely 25). The proof can be given through documents or extracts of base registries, independently from its structure, format or medium used to exchange it: a pdf document, a video, a recording, etc. |
cccev:InformationConcept | Piece of information that the Evidence provides or the Requirement needs. Additional Information: The Information Concept class offers the ability to describe conceptually the Requirements and provided facts in Evidences. In complementarity with the Supported Value class, this is a (first) step towards facilitating the assessment of the requirements in an automated way based on the Evidence provided. |
cccev:InformationRequirement | Requested data that is to be proven by Evidence. Additional Information: Information Requirements are the most neutral kind of Requirements. They aim to request information in any form, e.g. a person's date of birth or a company's turnover. They represent requests for data that prove one or more facts of the real world in a formal manner, or that leads to the source of such a proof. They can be understood as 'requests for Evidences'. The response to an Information Requirement is an Evidence when the issuer of the response is an authoritative source (e.g. a Civil Registry providing data about a natural person for the provision of public service through the Single Digital Gateway). In other cases, the responses might not be issued by an authoritative source, but the issuer supports the responses with Evidences (or commits to support them timely, e.g. a self-declaration or a declaration of oath). The Information Requirement can require structured data or documents of any form. For structured data, the Requirement can use 'Concepts' to specify the structure and type of the data expected in the response. For both structured and unstructured data, the Information Requirement can indicate the expected Type of Evidence, its format, source, and other properties related to the Evidence. |
cccev:Requirement | Condition or prerequisite that is to be proven by Evidence. Additional Information: Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. To illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional Organisations, adopted in the exercise of their legal autonomy. To stay consistent to how identification is realised in the eProcurement ontology, we switch to using `adms:identifier` instead of `dct:identifier` as per CCCEV specification. |
cpov:ContactPoint | Information (e.g. e-mail address, telephone number) of a Person or department through which the user can get in touch with. Additional information: This class represents the contact information for a Public Service, Channel, Public Organisation, etc. The Contact Point could be a role, email address, telephone number, etc. WG approval 5/11/2019 |
cpov:PublicOrganisation | An Organisation that is defined as being part of the public sector by a legal framework at any level. Additional information: A body governed by public law: - (a) established for the specific Purpose of meeting needs in the general interest - (b) having legal personality; - (c) financed, for the most part by the State, or regional or local authorities. Examples of Public Organisations are municipality, international public body, ministry, others. WG Approval 28/04/2020 |
cv:Channel | A medium through which Agents interact. Additional Information Typical examples include online services, email, endpoint on eDelivery infrastructure, phone, etc. Software solutions and electronic devices for communication and exchange of information between Buyers and economic Operators. Lots may use ad-hoc electronic means of communication that are not generally available such as specific solutions for secure and dedicated communication or non-standard eCatalogues. See also Directive recitals 53 to 56. WG approval 2023-02-14 |
dct:Location | An identifiable geographic place or named place. |
epo:AccessTerm | Conditions and stipulations about where and how to access the Procurement Documents. WG Approval 09/03/2021 |
epo:AcquiringCentralPurchasingBody | Role of an Agent procuring activities conducted on a permanent basis in the form of the acquisition of supplies and/or services intended for other Buyers. Additional Information: In Public Procurement the Role of Acquiring Central Purchasing Body is carried out by a Central Purchasing Body for other Contracting Authorities. WG approval 05/08/2021 |
epo:AcquiringParty | The Role of an Agent that acts on the buying side of a Procurement Process. |
epo:AdHocChannel | Web page where tools and devices for electronic communication that are not generally available can be downloaded free of charge. Additional Information: This corresponds in eForms to BT-724 Tool Atypical. WG Acceptance 10/01/2023 |
epo:AgentInRole | Relative concept that ties an Agent to a part they play in a given Situational Context. Additional information: The classification of roles is based is based on the degree of involvement into the Procurement Process: - Primary (Procurement) Pole is directly involved in the Procurement Process; - Secondary (Procurement sub-) Role is secondary to the Procurement Process - Tertiary (Related) Role is not involved in the Procurement Process. |
epo:AuxiliaryParty | Role of an Agent who may be mentioned in the information exchanged during the Procurement Process but who does not play an active part in it. |
epo:AwardCriteriaSummary | |
epo:AwardCriterion | Criterion that describes a Requirement that the Tender needs to resolve and on which the Tender is evaluated and ranked. WG approval 05/11/2018 |
epo:AwardDecision | Resolution of the Buyer as to the result of the Procurement Procedure. WG approval 14/11/2018 |
epo:Awarder | A Role of an Agent that signs the Award Decision. Additional information: BT-08 can be Awarding CBP; BG-03 is the Buyer. But Awarding CPB is not the same as the Buyer; the organisations may differ for these roles. Having the Awarder Role allows us to specify which Organisation is involved in the Award Decision. |
epo:AwardEvaluationTerm | Conditions and stipulations defining particularities of the evaluation of Award Criteria. |
epo:AwardingCentralPurchasingBody | Role of an Agent procuring activities conducted on a permanent basis in the form of the award of Public Contracts or the conclusion of Framework Agreements for works, supplies or services intended for other Buyers. Additional Information: In Public Procurement the Role of Awarding Central purchasing Body is carried out by a Central Purchasing Body for other Contracting Authorities. WG approval 05/08/2021 |
epo:AwardOutcome | |
epo:BudgetProvider | A role of an agent whose Budget is used to pay for the Contract. |
epo:Business | A private law company registered in a national registry. WG Approval 28/04/2020 |
epo:Buyer | A Role of an Agent that awards a Contract and/or purchases items. Additional information: In Public Procurement the Role of Buyer is carried out by the following types of Organisation: Contracting Authority, Contracting Entity, a defense Contractor, an international Organisation, or an organisation awarding a Contract subsidized by a Contracting Authority. In Pre-Award, the Buyer generally awards the Contract, however future purchasers may be foreseen. In Post-Award the buyer generally refers to the purchaser of items. |
epo:Candidate | The Role of an Agent that has sought an invitation or has been invited to take part in a restricted Procedure, in a competitive Procedure with negotiation, in a negotiated Procedure without prior publication, in a competitive dialogue or in an innovation partnership. WG approval 30/05/2023 |
epo:CatalogueProvider | A Role of an Agent compiling and supplying a Catalogue. Additional Information: The Catalogue Provider Role is usually played by the Agent that acts as a Seller, or by another Agent that acts on behalf of the Seller. WG Approval 28/01/2021 |
epo:CatalogueReceiver | A Role of an Agent processing a Catalogue. Additional Information: The Catalogue Receiver may not only receive it but also validate it, process it, etc. The Catalogue Receiver role is usually played by the agent that acts as a Buyer, or by another Agent that acts on behalf of the Buyer. WG Approval 28/01/2021 |
epo:CentralPurchasingBody | Role of an Agent that provides centralised purchasing activities and, possibly, ancillary purchasing activities for other Buyers. Additional Information: In Public Procurement the Role of Central Purchasing Body is carried out by a Contracting Authority for other Contracting Authorities. Contracting Authority procuring activities conducted on a permanent basis, in one of the following forms:[...](b) the award of Public Contracts or the conclusion of Framework Agreements for works, supplies or services intended for Contracting Authorities; WG approval 05/08/2021 |
epo:Certificate | Proof of conformance of the instance of the concept to a defined set of criteria. Additional Information: Certificates provide assurance of credibility, trust, and transparency in the procurement process. WG approval 16/05/2023 |
epo:CertificationLabel | Concept that stands for a set of norms, expectations, standards and policies. Additional Information: Such standards may relate to social, ethical and quality etc. WG approval 26/07/2022 |
epo:Certifier | The role of an agent who issues a certificate. Additional Information: The certifier is responsible for verifying and confirming the conformance of the instance of the concept to a defined set of criteria. WG approval 16/05/2023 |
epo:ChangeInformation | Alteration to previously provided details. |
epo:ConcessionContract | A Contract between one or more Buyers and one or more Economic Operators giving the right to the Economic Operators to exploit the rights foreseen in the Contract which may include the receipt of Payments. WG Approval 24/05/2022 |
epo:ConcessionEstimate | |
epo:ContextDescription | A description concerning a Procurement Object or a Notice in a specific Situation Context. Additional Information: The description has its own identity (+I) but is dependent (+D) on the concerned Entity. We say that ContextDescription *concerns* an Entity. |
epo:ContextualProjection | Projection of an Entity and all of its properties that hold in a given Situation Context. Additional Information: The contextual projection does not have its own identity (-I), is dependent (+D) on the described Entity, and is anti-rigid (~R) We say that ContextualProjection *describes* an Entity. Adaptation of ContextSlices pattern encoding a 4D view. http://ontologydesignpatterns.org/wiki/Submissions:Context_Slices |
epo:Contract | A voluntary, deliberate, and legally binding agreement between two or more competent parties. Additional information: This includes Concession Contracts. WG approval 01/06/2018 |
epo:ContractLotCompletionInformation | Information related to a given Lot at the end of the procurement. |
epo:Contractor | The Role of an Agent that has signed a Contract with a Buyer. WG approval 08/11/2022 |
epo:ContractSpecificTerm | Gathering class for conditions and stipulations related to a contract in the Post-Award Phase. |
epo:ContractTerm | Conditions and stipulations defining particularities of the Post Award Phase. (WG approval 23/11/2018) |
epo:DesignContestRegimeTerm | Conditions and stipulations defining particularities of a Design Contest. WG approval: 04-02-2021 |
epo:DirectAwardTerm | Conditions and stipulations defining particularities of the award of a Contract without prior publication. Addtional Information: Direct award may refer to a previous Procedure and/or specific Lot(s). It may also refer to other justified situations whereby there is no previous Procedure. See Directive 2014/24/EU Article 32. WG Approval 22/11/2019 |
epo:DirectContract | |
epo:Document | A set of interrelated Business Information representing the Business facts and associated metadata. The information may be conveyed in any language, medium or form, including textual, numerical, graphic, cartographic, audio-visual forms, etc. WG Approval 23/05/2019 |
epo:Duration | The length of time in which a concept occurs. |
epo:DynamicPurchaseSystemTechnique | A Technique that allows the selection of Candidates throughout the Procedure via the Qualification Criteria, followed by individual Mini-Competitions for the Award of Purchase Contracts. WG approval 23/05/2023 |
epo:EAuctionTechnique | A repetitive Technique in which new Prices, revised downwards, and/or new values concerning certain elements of Tenders are bid on-line. Additional Information: This corresponds in eForms to BT-767 Electronic Auction . WG approval 20/07/2018 |
epo:EconomicStandingSummary | |
epo:ElectronicSignature | |
epo:EmploymentInformationProvider | A Role of an Agent responsible for providing information concerning the general regulatory framework for employment protection and working conditions. |
epo:EnvironmentalProtectionInformationProvider | A Role of an Agent responsible for providing information concerning the general regulatory framework for Environmental Protection. |
epo:Estimate | An approximate calculation or a judgement of the value, number, Quantity or extent of something. |
epo:EvaluationTerm | Conditions and stipulations defining particularities of the Tender evaluation. (WG approval 23/11/2018) |
epo:ExclusionGround | Criterion that describes a legal Requirement to be met by the Economic Operator to be a Candidate in the Procurement. Additional Information: This corresponds in eForms to BG-701 Exclusion Grounds. WG approval 31/10/2018 |
epo:ExclusionGroundsSummary | |
epo:ExpressionOfInterest | Document presenting an Economic Operator's Request to be considered for Procedures covering a specific domain. WG approval 13/04/2021 |
epo:FrameworkAgreement | An agreement between one or more Contracting Authorities and one or more Economic Operators. Additional Information: When a Framework Agreement is concerned, the FA will result from LotAwardOutcome which describes a Lot which specifies the both the Qualification and Award Criteria. WG approval 18/05/2021 |
epo:FrameworkAgreementTechnique | Technique that establishes the terms governing Contracts to be awarded during a given Period, in particular with regard to Price and, where appropriate, the Quantity envisaged. WG approval 18/05/2021 |
epo:FrameworkAgreementTerm | Conditions and stipulations defining particularities in a Framework Agreement. |
epo:Fund | A financial resource used to support the Procurement. Additional Information: In the context of EU, Funds can be divided into programmes, actions and projects. Examples of EU funds are: the European Structural and Investment Funds, European Social Fund (ESF), the Connecting Europe Facility (CEF) programme, or the ISA2 programme and its actions (e.g. Action 2016.05 European Public Procurement Initiative, which supports the eProcurement Ontology under sub-action 3). 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. WG Approved 14/05/2019 |
epo:GreenProcurement | Approach whereby Buyers seek to procure with a reduced Environmental Impact. Additional Information: The approach may apply to the complete life cycle. The reduced Environmental Impact is in comparison to goods, services and works with the same primary function that would otherwise be procured. Tightly related are article 68 - Life-cycle costing and article 67 - most economically advantageous Tender (see GPP handbook) https://ec.europa.eu/environment/gpp/pdf/Buying-Green-Handbook-3rd-Edition.pdf An instance of the class GreenProcurement is represented in eForms with the code "env-imp" defined in the codelist Strategic-Procurement.Paragraphs) https://ec.europa.eu/environment/gpp/pdf/Buying-Green-Handbook-3rd-Edition.pdf |
epo:IndefiniteDuration | |
epo:InnovativeProcurement | Approach whereby Buyers seek to procure an innovative work, supply or service. Additional Information: ‘innovation’ means the implementation of a new or significantly improved product, service or process, including but not limited to production, building or construction processes, a new marketing method, or a new organizational method in business practices, workplace Organisation or external relations inter alia with the purpose of helping to solve societal challenges or to support the Europe 2020 strategy for smart, sustainable and inclusive growth; See: Directive 2014/24 Articles: 2, 26 (3), 31, 67 (2.a) |
epo:JuryMember | |
epo:LeadBuyer | A Role of an Agent who is a Buyer and takes the administrative lead of the Procedure. WG agreement: 2022-11-22 |
epo:Lot | A qualitative, quantitative or strategic subdivision of the goods, services or works to be procured, allowing the award of one or more Contracts. WG approval 12/09/2018 |
epo:LotAwardOutcome | Result concerning the Lot attributed by the Awarder. |
epo:LotGroup | Combination of several Lots to conduct comparative assessment of the Tenders. Additional Information: The comparative assessment may refer to the Selection Criteria, Award and Value that apply to several Lots. Pending of discussion with eForms Member States may provide that, where more than one lot may be awarded to the same tenderer, contracting authorities may award contracts combining several or all lots where they have specified in the contract notice or in the invitation to confirm interest that they reserve the possibility of doing so and indicate the lots or groups of lots that may be combined. |
epo:LotGroupAwardInformation | Award information related to a given Group of Lots. |
epo:LotSpecificTerm | Gathering class for conditions and stipulations related to a Lot. |
epo:Mediator | A Role of an Agent that attempts to resolve a dispute between different Agents and come to an agreement. WG approval 20/04/2021 |
epo:MiniCompetitionAwardOutcome | Result concerning the process where multiple winners or candidates of previous stages of a procedure bid for a specific procurement attributed by the Awarder. Additional Information: It is typically used in framework agreements where the suppliers have already been pre-selected, and the mini competition is used to determine which supplier is best suited for a particular project or contract. It is also used in a Dynamic Purchasing System where the suppliers come from a list of Candidates. |
epo:MonetaryValue | A number of monetary units specified using a given unit of currency. Additional information: In the pre-award phase of the procurement, all monetary values are considered to exclude VAT based on the Directive 2014/24/EU. WG approval 13/04/2021 |
epo:MultipleStageProcedureTerm | Conditions and stipulations defining particularities of Procedures carried out in several steps Additional Information: Generally this refers to Procedures where selection is carried out to qualify Tenderers who are then requested to submit the rest of their Tender for evaluation is Restricted Procedure. WG Approval 15/04/2021 |
epo:NonDisclosureAgreementTerm | Conditions and stipulations |
epo:NonPublishedInformation | Information about fields not published in this Notice. Additional Information: The non-published information may become available at a later date and may differ from one element to another within a given Document. Examples of fields that may not be immediately published are Winner, Tender and Procedure Lot Result, etc., e.g. for security reasons. |
epo:Notice | Document published by the Buyer about market opportunities and results. WG Approval 23/05/2019 |
epo:NoticeAwardInformation | Information about an Award Notice. |
epo:Offer | Document providing the Monetary Value and the details to fulfill the Requirements set out in the Procurement Documents or Request for Offer. Additional information: A quotation is considered to be an Offer in the eProcurement Ontology. WG approval 09/02/2023 |
epo:OfferingParty | The Role of an Agent that acts on the Economic Operator side during a Procurement Process. Additional information: As per the European Procurement Directives the notion of ‘Economic Operators’ should be interpreted in a broad manner so as to include any Persons and/or Entities which offer the execution of works, the supply of products or the provision of services on the market, irrespective of the legal form under which they have chosen to operate. Thus, firms, branches, subsidiaries, partnerships, cooperative societies, limited companies, universities, public or private, and other forms of entities than natural Persons should all fall within the notion of Economic Operator, whether or not they are ‘Legal Persons’ in all circumstances. |
epo:OfferIssuer | The Role of an Agent that distributes an Offer. WG approval 09/02/2023 |
epo:OfflineAccessProvider | A Role of an Agent responsible for providing offline access to the Procurement Documents. |
epo:OpeningTerm | Conditions and stipulations defining particularities of the opening of Tenders. Additional Information: The opening of Tenders is the event when Tenders are made accessible for evaluation, it is generally the same date and time for all Tenders. WG Approval 15/04/2021 |
epo:OrganisationGroup | Agreed collaboration of several Organisations. Additional Information: This concept has been created to fulfill the need to represent a grouping of Organisations that is not necessarily registered i.e, consortia. WG approval 15/04/2021 |
epo:OriginatorRequest | Document in which the Originator describes his needs. WG approval 09/02/2023 |
epo:OtherEntity | Economic Operator (who is not a Subcontractor) on which the Tenderer relies upon, to meet Selection Criteria. |
epo:ParticipationCondition | Criterion that describes a Requirement to take part in a procurement. WG approval 30/05/2023 |
epo:ParticipationConditionsSummary | |
epo:ParticipationRequestProcessor | A Role of an Agent responsible for processing Requests To Participate. |
epo:ParticipationRequestReceiver | A Role of an Agent responsible for receiving Requests To Participate. |
epo:ParticipationRequestTerm | Conditions and stipulations defining particularities of requesting participation in a Procedure. |
epo:PaymentExecutor | A Role of an Agent responsible for executing the Payment. |
epo:Period | A time interval or a Duration. WG approval 28/04/2020 |
epo:PlannedProcurementPart | A subdivision of a Planned Procurement that may later become one or more Lots or a self-standing Procedure. A Lot or a Procedure can also cover one or more parts of the Planned Procurement. WG Approval 20/06/2019 |
epo:Prize | A reward given in a Contest. WG approval: 15/04/2021 |
epo:Procedure | A legally defined set of administrative activities conducted to conclude one or more Contracts. Additional Information The Procedure is categorised in the law according to different rules determining whether the Procedure is Open, Restricted, Negotiated with or without publicity, etc. (see Procedure Type). WG Approval 20/08/2019 |
epo:ProcedureSpecificTerm | Gathering class for conditions and stipulations related to a Procedure. |
epo:ProcedureTerm | Conditions and stipulations defining particularities of the Procedure. (WG approval 23/11/2018) |
epo:ProcessPlanningTerm | Conditions and stipulations defining particularities of the unfolding of the Procurement Process. |
epo:ProcurementCriteriaSummary | WG approval 24/01/2023 |
epo:ProcurementCriterion | A criterion specific to Procurement. Additional Information: This Procurement Criterion can be only Exclusion Ground, Selection Criterion or Award Criterion. Each of these Criteria can contain subcriteria (Criterion class). WG Approval 23/04/2020 |
epo:ProcurementDocument | Document produced or referred to by the Buyer to describe or determine elements of the Procurement. Additional information: Procurement Documents are to be accessible since the date of publication of the Contract Notice or the prior information Notice when used as a call for competition. Examples of Procurement Documents are Technical Specifications, the Descriptive Document, proposed conditions of Contract, formats for the presentation of Documents by Candidates and Tenderers, information on generally applicable obligations. Other Documents related to the Procedure such as Notices are not considered to be Procurement Documents. WG Approval 23/05/2019 17:08:30 |
epo:ProcurementElement | Gathering class for critical/central elements in the Procurement Process. TODO: add definition Additional information: Alias: ProcurementComponent |
epo:ProcurementObject | The whole or a division of goods, services or works to be procured. Additional Information: Anything that can specify the procurement content (i.e. goods, services, work) is a Procurement Object. In a sense, such an "object" can constitute the "object of a Contract". To test whether something is a Procedure Object check if it can have a Purpose and/or CPV classification (<i>The CPV establishes a single classification system for public procurement aimed at standardising the references used by Contracting Authorities and entities to describe the subject of Procurement Contracts.</i>). Note: Procedure, seems to be an exception from this rule. Because it is a conflated term: it carries process properties and "purpose" properties. |
epo:ProcurementProcedureInformationProvider | A Role of an Agent responsible for providing additional information about the Procurement Procedure. |
epo:ProcurementProcessInformation | Information about the temporal unfolding or succession of Procurement Objects. |
epo:ProcurementServiceProvider | Role of a public or private body which offers ancillary purchasing activities on the market. Additional information "Ancillary Purchasing Activities" means 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; Source: Directive 2014/24/EU, Article 2, paragraphs 17 and 15. This would be equivalent to the concept of 'ProcuringEntity' in OCDS: 'The Entity managing the Procurement, which may be different from the Buyer who is paying / using the items being procured'. WG Approval 24/03/2020 |
epo:ProfessionalSuitabilitySummary | |
epo:Project | A collaborative enterprise that is carefully planned to achieve a particular aim. |
epo:PurchaseContract | A Contract resulting from using a Dynamic Purchasing System Technique or Framework Agreement Technique. |
epo:Purpose | The description of the objectives related to a Procurement. Additional information: The description of the objectives includes the Subject Matter and Quantities. The quantification of the objectives related to a procurement. To be re-reviewed by the WG the soonest. (WG to be discussed, this was pointed out on the 09/04/2019 14:38:25 WG Meeting) The old definition read as follows: The description of the objectives related to a procurement. (WG approval 05/12/2018) |
epo:QualificationCriteriaSummary | |
epo:QualificationCriterion | Criterion used in the first stage of procurement. WG approval 30/05/2023 |
epo:Quantity | A counted number of non-monetary units possibly including fractions. |
epo:RequestForClarification | A demand for elucidation of received information. Additional Information: Requests for clarification are usually used by Buyers during the process of award or evaluation to understand specific aspects of the Tender without altering the Tender. WG approval 20/04/2021 |
epo:RequestForParticipation | Application of an Economic Operator to be included in a Procurement Procedure. WG approval: 20/04/2021 |
epo:ReviewDecision | Information about Review Decisions. |
epo:Reviewer | Role of an Agent who investigates the overall correctness of a Procurement Procedure, producing a related report. Additional Information: Any Organisation or Person may request a review of a Procurement Procedure. WG approval: 20/04/2021 |
epo:ReviewIrregularitySummary | Information about the number and type of requests the Buyer received to review any of its decisions (e.g. the Technical Specifications, Award Decision). Additional information: This class corresponds in eForms to BG-613 Buyer Review Requests. |
epo:ReviewObject | Information about a Review Request or a Review Decision. Additional information: This class corresponds to the BG-714 Review in eForms. |
epo:ReviewProcedureInformationProvider | A Role of an Agent who is providing more information on the time limits for review Procedures. |
epo:ReviewRequest | Information about requests to review procedures. |
epo:ReviewRequester | Role of an Agent who requests the review of a (Procurement) Procedure. WG Approval 23/10/2021 |
epo:ReviewRequestSummary | Summary information about the requests the Buyer received 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, and about the complainants that submitted the requests. Additional information: This class corresponds in eForms to BG-612 Buyer Review Summary. |
epo:ReviewTerm | Conditions and stipulations defining particularities of the review. WG approval 23/11/2018 |
epo:SecurityClearanceTerm | Conditions and stipulations about the status requested of individuals allowing them access to classified information (state or organisational secrets) or to restricted areas, after completion of a thorough background check. Additional information: This corresponds in eForms to BT-578, BT-78, BT-732 . WG approval 20/06/2023 |
epo:SelectedCandidateList | Record of Candidates admitted to take part in award phases of procurements. WG approval 30/05/2023 |
epo:SelectionCriteriaSummary | |
epo:SelectionCriterion | Criterion that describes a capacity Requirement that the Economic Operator needs to fulfill to participate in the procurement. Additional Information: Selection criteria may relate to: (a) suitability to pursue the professional activity; (b) economic and financial standing; (c) technical and professional ability WG approval 31/10/2018 |
epo:SelectionEvaluationTerm | Conditions and stipulations defining particularities of the evaluation of Selection Criteria. |
epo:SocialProcurement | Approach whereby Buyers seek to procure by fulfilling social objectives. Additional Information: Socially Responsible Public Procurement (SRPP) - ‘SRPP’ means Procurement Operations that take into account one or more of the following social considerations: employment opportunities, decent work, compliance with social and labour rights, social inclusion (including persons with disabilities), equal opportunities, accessibility design for all, taking account of sustainability criteria, including ethical trade issues and wider voluntary compliance with corporate social responsibility (CSR), while observing the principles enshrined in the Treaty for the European Union (TFEU) and the Procurement Directives. Source: Buying Social - A Guide to Taking Account of Social Considerations in Public Procurement (Publications Office of the European Union, 2011) https://op.europa.eu/en/publication-detail/-/publication/cb70c481-0e29-4040-9be2-c408cddf081f/language-en See Article 18 and Annex X Directive 2014/24. |
epo:SpecificDuration | |
epo:StatisticalInformation | Statistical data on the Procedure and the Lot. Additional Information At the present time Procurement Procedures are not fully electronic. At a later date, information on the Tenders received could be inferred by the data in the eProcurement System. Therefore this class is temporal and should cease to exist in fully electronic Procurement. The need for its presence responds also to the alignment with the Regulation (EU) 2019/1780 (eForms). Attention will have to be paid in the future to possible inconsistencies derived from data placed in other classes and data held in the Statistical Information class; e.g. the TenderEvaluation class (see eEvaluation diagram) has the attribute admissibileTender indicator, which in case of being false, may enter in contradiction with the highest or lowest Tender value for that very same inadmissible Tender. WG Approval 12/12/2019 |
epo:StrategicProcurement | Public Procurement that contributes to achieving pressing policy goals. Additional Information: Specific strategic goals could be, for example, Environmental Protection, innovation, job creation and the development of small and medium enterprises. This corresponds in eForms to BG-713 Strategic Procurement. The subclasses are given by the choices in BT-06 Strategic Procurement. Based on https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0411 (see paragraph on "background information". WG Approval 10/03/2020 |
epo:SubcontractingEstimate | Information on the approximation of the foreseen Subcontracting. |
epo:Subcontractor | A Role of an Agent that has an agreement to perform part or all of the obligations of another Agents's Contract. Additional information For some Procedures, the Subcontractor signs as well the Contract between the Buyer and the Contractor. At tendering time, entities relied upon by the Economic Operators can be Subcontractors or not. When modelling ESPD we will analyze whether we need or not a Role named "relied upon". WG approval 05/08/2021 |
epo:SubcontractTerm | A concept to describe the main information regarding the share of parts of the Contract to third parties. |
epo:SubmissionStatisticalInformation | Statistical information about submissions on a given competition, either at Lot level or Mini-Competition level. WG approval 30/05/2023 |
epo:SubmissionTerm | Conditions and stipulations defining particularities of submitting Documents to the Buyer. Additional Information: These Documents can be Tenders, Request To Participate and expressions of interest. WG Approval 14/07/2020 |
epo:System | Software application used for performing Procurement activities. WG Approval 28/04/2020 |
epo:TaxInformationProvider | A Role of an Agent responsible for providing information concerning the general regulatory framework for taxes. |
epo:TechnicalAbilitySummary | |
epo:TechnicalSpecification | A set of documented Requirements applicable to the object of the Procurement. Additional Information: A specification often includes technical standards. WG approval: 20/04/2021 |
epo:Technique | Method used for conducting Procurement Procedures. Addtional information: This corresponds in eForms to BG-706 Techniques. Several Techniques can be combined in one single Procurement Procedure (e.g. eAuction can be carried out in a Framework Agreement or DPS). WG Approval 19/09/2019 |
epo:Tender | Information submitted by the Economic Operator to specify its Offer regarding a specific Lot, in response to the call for Tender. (WG approval 03/05/2022) |
epo:TenderAwardOutcome | Result concerning the Tender attributed by the Awarder. |
epo:Tenderer | A Role of an Agent that has submitted a Tender. Additional Information: A Tenderer is an Economic Operator or group of Economic Operators that has submitted a Tender. WG approval 05/08/2021 |
epo:TenderGroup | Specific Offer in response to a Lot Group. Additional Information: This class is generally used to provide the Monetary Value in response to a Lot Group. |
epo:TenderProcessor | A Role of an Agent responsible for processing Tenders. |
epo:TenderReceiver | A Role of an Agent responsible for receiving Tenders. |
epo:Term | A governing condition or stipulation. |
epo:VehicleInformation | |
epo:Winner | A Role of an Agent to whom a Lot is awarded. WG approval 05/08/2021 (revised 26/10/2021) |
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 |
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. |
locn:Address | The particulars of the place where a Person or an Organisation is located. WG Approval 28/04/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.". 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. |
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. |
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). |
person:Person | A individual human being who may be dead or alive, but not imaginary. |
time:Duration | Duration of a temporal extent expressed as a number scaled by a temporal unit. |
Attributes (datatype properties) names and definitions
Class name | Attribute name | Definition | Data type / cardinality |
---|---|---|---|
adms:Identifier | adms:schemaAgency | The name of the agency that issued the identifier. | rdf:PlainLiteral [0..*] |
cccev:Criterion | cccev:bias | Parameter used to adjust the evaluation of the Criterion. 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] |
cccev:Criterion | cccev:weight | Relative importance of the Criterion. 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] |
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] |
cpov:ContactPoint | cpov:email | The email of the Organisation. | rdf:PlainLiteral [0..*] |
cpov:ContactPoint | cpov:telephone | A telephone number through which the Contact Point can be contacted. | rdf:PlainLiteral [0..*] |
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..*] |
locn:Geometry | cv:latitude | The latitude. | rdf:PlainLiteral [0..*] |
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 |
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 | 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..*] |
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 |
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 | rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..*] rdf:PlainLiteral [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: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] |
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 |
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 | rdf:PlainLiteral [0..*] rdf:PlainLiteral [0..1] |
epo:SpecificDuration | time:numericDuration | Value of a temporal extent expressed as a number. | xsd:decimal [1..1] |
Predicates (object properties) and definitions
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: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] |
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:hasRequirement | A more specific Requirement that is part of the Requirement. | cccev:Requirement -> cccev:Requirement [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..*] |
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:type | Category to which the Requirement belongs. | cccev:Criterion -> at-voc:criterion [0..1] |
epo:actsOnBehalfOf | Represents. | epo:ProcurementServiceProvider -> epo:Buyer [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: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: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:describesLotCompletion | epo:ContractLotCompletionInformation -> epo:Lot [1] | |
epo:describesLotGroup | epo:LotGroupAwardInformation -> epo:LotGroup [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). 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. | 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 | epo:AwardOutcome -> at-voc:winner-selection-status [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: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:hasBuyerLegalType | A category that indicates the right of an Organisation to play the role of a buyer. Additional Information: The category also effects the rules that the buyer has to abide to within the public procurement procedure. WG 07/09/2021 | org:Organization -> at-voc:buyer-legal-type [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: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 | epo:ConcessionEstimate -> epo:MonetaryValue [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:hasConstraint | cccev:InformationRequirement -> cccev:Constraint [0..*] epo:ProcurementCriterion -> cccev:Constraint [0..*] |
|
epo:hasContactPointInRole | epo:AgentInRole -> cpov:ContactPoint [0..*] | |
epo:hasContractNatureType | Subject of the acquisition. WG Approval 11/06/2020 | epo:ContractTerm -> at-voc:contract-nature [0..1] |
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. | 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 28/05/2020 | epo:DirectAwardTerm -> at-voc:direct-award-justification [0..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:AccessTerm -> at-voc:communication-justification [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: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:hasElectronicSignature | epo:Document -> epo:ElectronicSignature [0..*] | |
epo:hasEndpointIdentifier | cv:Channel -> adms:Identifier [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. This corresponds to BT-160 in eForms. WG Approval 07/01/2020 | epo:ConcessionEstimate -> epo:MonetaryValue [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: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: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. 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] |
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: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:hasFixedValueType | The method to interpret the fixed value as pertaining to a total or unit. WG Approval 17/09/2019 | epo:AwardCriterion -> at-voc:number-fixed [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:hasFrameworkAgreementMaximumValue | epo:LotAwardOutcome -> epo:MonetaryValue [0..1] | |
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:hasFundProgramme | epo:Fund -> at-voc:EU-programme [0..1] | |
epo:hasGroupFrameworkAgreementMaximumValue | This corresponds to BT-156 in the eForms. | epo:LotGroupAwardInformation -> epo:MonetaryValue [0..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:hasInternalIdentifier | epo:LotGroup -> adms:Identifier [0..*] epo:ProcurementElement -> adms:Identifier [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: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:hasLabelType | The label type such environmental, quality, social etc. | epo:CertificationLabel -> at-voc-new:certification-label-type [0..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: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: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. 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 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:hasLegalIdentifier | org:Organization -> adms:Identifier [0..*] | |
epo:hasLotReference | epo:Contract -> epo:Lot [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: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:hasMainClassification | epo:Purpose -> at-voc:cpv [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. 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. WG Approval 03/12/2019 | epo:NoticeAwardInformation -> epo:MonetaryValue [0..1] |
epo:hasMember | epo:OrganisationGroup -> org:Organization [1..*] | |
epo:hasNationality | person:Person -> at-voc:country [0..*] | |
epo:hasNonAwardJustification | On hold; Enumeration. | epo:AwardOutcome -> at-voc:non-award-justification [0..1] |
epo:hasNonElectronicSubmissionJustification | Reason for not accepting electronic 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: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. WG Approval 03/10/2019 | epo:Document -> at-voc:language [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:hasPlannedDuration | epo:PlannedProcurementPart -> epo:Duration [0..1] | |
epo:hasPlannedPeriod | epo:PlannedProcurementPart -> epo:Period [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: This corresponds to BT-644 in eForms. WG Approval 29/08/2019 | epo:Prize -> epo:MonetaryValue [0..1] |
epo:hasProcedureType | Identification of the Procedure used. WG Approval 09/06/2020 | epo:Procedure -> at-voc:procurement-procedure-type [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: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: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: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 | epo:ParticipationCondition -> at-voc:reserved-procurement [0..*] epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*] |
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:hasSelectionCriteriaUsage | Additional Information: This corresponds in eForms to BT-748 Selection Criteria Used. | epo:SelectionCriterion -> at-voc:usage [0..1] |
epo:hasSelectionCriterionType | The classification of the selection criteria. Additional Information: This corresponds in eForms to BT-747 Selection Criteria Type. WG Approval 09/11/2021 | epo:SelectionCriterion -> at-voc:selection-criterion [0..1] |
epo:hasStartDate | epo:SelectedCandidateList -> epo:Period [0..1] | |
epo:hasSubcontracting | epo:Tender -> at-voc:applicability [0..1] | |
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: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:hasTaxIdentifier | org:Organization -> adms:Identifier [0..*] | |
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:hasTenderValidityDuration | epo:SubmissionTerm -> epo:Duration [0..1] | |
epo:hasTenderValidityPeriod | The relation indicating until when a tender instance is applicable. | epo:SubmissionTerm -> epo:Period [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:hasTimePeriod | epo:Period -> at-voc:timeperiod [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:hasTotalQuantity | The number of units required. Additional Information: The quantity needs to go along with the unit. | epo:Purpose -> epo:Quantity [0..1] |
epo:hasTotalValue | epo:TenderGroup -> epo:MonetaryValue [0..1] |
|
epo:hasUnitCode | epo:Quantity -> at-voc:measurement-unit [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: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: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: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: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:hasWeightValueType | No definition. Waiting on CCCEV alignment. | epo:ProcurementCriterion -> at-voc:number-weight [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: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:includesTender | Additional information: This corresponds in eForms to BT-3202 Contract Tender Identifier. | epo:Contract -> epo:Tender [0..*] |
epo:indicatesAwardToWinner | Reveals the winner to whom the tender award outcome is attributed. | epo:TenderAwardOutcome -> epo:Winner [0..1] |
epo:indicatesInvoiceeContactPoint | epo:Buyer -> cpov:ContactPoint [0..*] | |
epo:involvesBuyer | epo:Procedure -> epo:Buyer [0..*] | |
epo:involvesProcurementDocument | epo:AccessTerm -> epo:ProcurementDocument [0..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: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:isExecutedByProcurementServiceProvider | epo:Procedure -> epo:ProcurementServiceProvider [0..1] | |
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:isOwnedByAgent | epo:System -> foaf:Agent [0..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:isSubjectToContractSpecificTerm | epo:Contract -> epo:ContractSpecificTerm [0..*] | |
epo:isSubjectToGrouping | epo:Tender -> epo:LotGroup [0..1] | |
epo:isSubjectToLotSpecificTerm | epo:Lot -> epo:LotSpecificTerm [0..*] | |
epo:isSubjectToProcedureSpecificTerm | epo:Procedure -> epo:ProcedureSpecificTerm [1..*] | |
epo:isSubjectToTerm | epo:ProcurementObject -> epo:Term [0..*] | |
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:isSubmittedForLot | epo:Tender -> epo:Lot [1] | |
epo:isSubmittedForLotGroup | epo:TenderGroup -> epo:LotGroup [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: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:needsToBeATenderer | The Winner must be a Tenderer. | epo:Winner -> epo:Tenderer [0..1] |
epo:needsToBeAWinner | The Contractor must be a Winner. | epo:Contractor -> epo:Winner [0..1] |
epo:ownsSystem | epo:System [,0..*] <- foaf:Agent | |
epo:playedBy | epo:AgentInRole -> foaf:Agent [1] epo:JuryMember -> person:Person [0..1] |
|
epo:providesContractTotalPaymentValue | Additional Information: This corresponds to BT-779 in eForms. | epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] |
epo:providesContractTotalPenaltyValue | Additional Information: This corresponds to BT-782 in eForms. | epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1] |
epo:providesRulingOnRemedy | States the measures to be taken after a review procedure. | epo:ReviewDecision -> at-voc:remedy-type [0..*] |
epo:refersToContract | epo:ContractLotCompletionInformation -> epo:Contract [1] | |
epo:refersToLot | epo:Notice -> epo:Lot [1..*] |
|
epo:refersToNotice | epo:Notice -> epo:Notice [0..1] | |
epo:refersToPlannedPart | epo:AccessTerm -> epo:PlannedProcurementPart [0..*] | |
epo:refersToPrevious | epo:Document -> epo:Document [0..*] | |
epo:refersToPreviousNotice | Additional information: This corresponds in eForms to BT-758 Change Notice Version Identifier. | epo:ChangeInformation -> epo:Notice [1] |
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: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:refersToPreviousReview | Additional information: This relation corresponds in eForms to BT-785 "Review Previous Identifier". | epo:ReviewObject -> epo:ReviewObject [0..1] |
epo:refersToProcedure | epo:Notice -> epo:Procedure [1] |
|
epo:relatesToEFormSectionIdentifier | epo:ChangeInformation -> adms:Identifier [1..*] epo:NonPublishedInformation -> adms:Identifier [1..*] |
|
epo:requestsRemedyType | Additional information: This relation corresponds in eForms to BT-792 Review Remedy Type | epo:ReviewRequest -> at-voc:remedy-type [0..*] |
epo:resolvesReviewRequest | epo:ReviewDecision -> epo:ReviewRequest [1] | |
epo:resultsFromLotAwardOutcome | epo:DirectContract -> epo:LotAwardOutcome [0..*] epo:FrameworkAgreement -> epo:LotAwardOutcome [0..*] |
|
epo:resultsFromMiniCompetitionAwardOutcome | epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome [0..1] | |
epo:resultsFromUsingCandidateList | epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList [0..1] | |
epo:setsGroupingContextForLot | epo:LotGroup -> epo:Lot [1..*] | |
epo:signedByBuyer | epo:Contract -> epo:Buyer [0..*] | |
epo:signedByContractor | epo:Contract -> epo:Contractor [0..*] | |
epo:signsAwardDecision | epo:Buyer -> epo:AwardDecision [0..*] | |
epo:specifiesCleanVehicleDirectiveContractType | epo:VehicleInformation -> at-voc:cvd-contract-type [0..1] | |
epo:specifiesCleanVehicleDirectiveVehicleCategory | epo:VehicleInformation -> at-voc:vehicle-category [0..1] | |
epo:specifiesProcurementCriteriaSummary | epo:Procedure -> epo:ProcurementCriteriaSummary [0..*] | |
epo:specifiesProcurementCriterion | epo:Lot -> epo:ProcurementCriterion [0..*] epo:LotGroup -> epo:ProcurementCriterion [0..*] |
|
epo:specifiesSubcontractors | epo:Tender -> epo:Subcontractor [0..*] | |
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. WG approval 30/05/2023 | epo:SubmissionStatisticalInformation -> epo:AwardOutcome [1] |
epo:usesChannel | epo:ProcurementElement -> cv:Channel [0..*] | |
epo:usesTechnique | epo:ProcurementObject -> epo:Technique [0..*] | |
locn:address | Associates any Resource with the corresponding Address. Additional Information: Asserting the address relationship implies that the Resource has an Address. Associates any Resource with the corresponding Address. Additional Information: Asserting the address relationship implies that the Resource has an Address. | cpov:ContactPoint -> locn:Address [0..1] dct:Location -> locn:Address [0..1] org:Organization -> locn:Address [0..*] |
locn:addressID | A globally unique identifier for each instance of an Address. Additional Information: The concept of adding a globally unique identifier for each instance of an address is a crucial part of the INSPIRE data spec. A number of EU countries have already implemented an ID (a UUID) in their Address Register/gazetteer, among them Denmark. OASIS xAL also includes an address identifier. It is the address Identifier that allows an address to be represented in a format other than INSPIRE whilst remaining conformant to the Core Vocabulary. The INSPIRE method of representing addresses is very detailed, designed primarily for use in databases of addresses. Whilst data that is published in full conformance with the INSPIRE data structure can be made available using the Location Core Vocabulary the reverse is not true since the Core Vocabulary allows much greater flexibility. Many datasets that include address data as one piece of information about something else are likely to have that data in simpler formats. These might be tailored to the specific need of the dataset, follow a national norm, or make use of a standard like vCard. To provide maximum flexibility in the Core Vocabulary, whilst remaining interoperable with INSPIRE Address Guidelines (which EU Member States are obliged to use), the Location Core Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID. | locn:Address -> adms:Identifier [0..1] |
locn:geographicIdentifier | A URI that identifies the Location. Additional Information: GeoNames.org provides stable, widely recognised identifiers for more than 10 million geographical names that can be used as links to further information. For example, http://sws.geonames.org/593116/ identifies the Lithuanian capital Vilnius. Unfortunately these URIs cannot easily be automatically deduced since the URI scheme uses simple numeric codes. Finding a GeoNames identifier for a Location is almost always a manual process. Where such identifiers are known or can be found, however, it is recommended that they be used. Where the Location Class is used to identify a country, if the geonames URI is not known, the recommendation is to use DBpedia URIs of the form http://dbpedia.org/resource/ISO_3166-1:XX where XX is the ISO 3166 two character code for the country. The EU's Publication Office diverges from ISO 3166-1 and uses EL and UK for Greece and the United Kingdom respectively. DBpedia sticks to the ISO codes and so the correct URIs for these countries are: - http://dbpedia.org/resource/ISO_3166-1:GR - http://dbpedia.org/resource/ISO_3166-1:GB even when the geographic name is given as EL or UK. The use of a URIs has added advantages: - it can be used by automated systems to look up additional data (linked data); - a triple store may store only one copy of the URI, whereas if a string is used, a copy of that string is always stored for each and every person in the database. Thus, in large data sets, the saving on memory capacity and the improvement in transmission efficiency can be substantial. | dct:Location -> adms:Identifier [0..1] |
locn:geometry | dct:Location -> locn:Geometry [0..1] | |
org:subOrganizationOf | Represents hierarchical containment of Organizations or OrganizationalUnits; indicates an Organization which contains this Organization. WG 31/08/2023 | org:Organization -> org:Organization [0..*] |
time:unitType | epo:SpecificDuration -> time:TemporalUnit [1] |