ePO - eProcurement Ontology 1.0.0

The ultimate objective of the e-procurement ontology is to put forth a commonly agreed OWL ontology that will conceptualise, formally encode and make available in an open, structured and machine-readable format data about public procurement, covering it from end to end, i.e. from notification, through tendering to awarding, ordering, invoicing and payment. It is the intention of the e-procurement ontology to unify existing practices, thus facilitating seamless exchange, access and reuse of data.

In the framework of this project, we will identify and give examples of each step of the process for creating the e-procurement ontology. Clearly specifying the roles of the different actors and the input required of them within the timeline of creating the ontology. The different phases needed to create the ontology and the intermediary processes within these phases will be clearly defined giving examples taken from the 3 use cases. In parallel to this process, a working group composed of stakeholders from multiple interested groups will be set up. This working group will decide by consensus on how the ontology should be developed at all stages and may decide to adapt the first draft of the specification proposed and described during the first meeting. This project will provide the working group with the process, methodology and technology to be followed for developing the final version of the e-procurement ontology.

The D02.01 Specification of the process and methodology can be downloaded from here. The D02.02 Project Charter proposal can be read here.

The landscaping report on policy support for e-Procurement is available here.

The OWL file created from the current data model is available here.

Release Notes

Version 1.0.0

  • Defines of three Use Cases:

    • Use Case 1: "Data Journalism"

    • Use Case 2: "Automated matchmaking of procured services and products with businesses"

    • Use case 3: "Verifying VAT payments on intra-community service provision"

  • Identifies Information Requirements in alignment with the Use Cases

  • Defines a Conceptual Data Model

  • Maps the Conceptual Data Model entities to OWL

  • Implements the Conceptual Data Model in OWL

  • Release year: 2017