REPORT ON THE 2025 WIDE WORKING GROUP MEETING OF THE EPROCUREMENT ONTOLOGY
Online meeting: 03/06/2025
Presenter: Andreea Pasare (Meaningfy/Infeurope),
Note editor: Achilles Dougalis (Meaningfy/Infeurope)
Meeting Agenda
-
Welcome
-
Review of work: July 2024 – June 2025
-
ePO v5.0.0-rc.1 (published)
-
Updated workflow and model2owl evolution
-
ePO v5.1.0-rc.1 (in progress)
-
Future work
-
Closing
Welcome:
Natalie Muric explained the aim of the meeting is to present the work carried out since the last meeting in july 2024 and to present the plan for the second half of 2025. Stakeholders’ attention was drawn to the release of eQualification, eEvaluation, eAwarding, eRequest as well as the publication of first release candidate of ePO 5.0.0 and the first candidate of ePO 5.1.0
The following sections provide a summary of what was presented by Andrea Pasare and discussed by the Working Group.
Publication of ePO v5.0.0-rc1
The release candidate v5.0.0-rc1 was presented. This release and its corresponding technical files can be found at https://github.com/OP-TED/ePO/tree/release/5.0.0 . ePO 5.0.0 includes the new modules of eQualification, eEvaluation, eAwarding and eRequest as well as updates to the other modules. For more information on what has changed, please consult the corresponding release notes.
eQualification module
It was mentioned that eQualification may be used in :
-
The qualification of Tenderers, in particular for an open Procedure.
-
The prequalification of economic operators, in particular for Dynamic Purchase System (DPS) and Prequalification systems (specifically for works).
It was discussed that the Following Documents are included in the eQualification module
-
Evidence Request
-
Evidence Receipt
-
Evidence Submission
The eQualification conceptual model diagrams were presented.
eEvaluation module
eEvaluation refers to the evaluation report in digital format that evaluates the tenders submitted by tenderers or candidates (in the case of multistage procedures) depending on the procedure that is adopted, to provide input for the award decision.
It was discussed that the Following Documents are included in the eEvaluation module
-
Evaluation Report
-
Tender Clarification Request
-
Tender Clarification
The eEvaluation conceptual model diagrams were presented.
eAwarding module
It was mentioned that eAwarding may refer to :
-
The Award Decision in the digital format created and signed by the Unique Responsible of the Procurement.
-
The notification to all Tenderers as to the result of the Procurement The Award Decision is based on the Evaluation Report. The Unique Responsible of the Procurement either accepts the findings of the Evaluation Report or takes another decision (if the Winner does not fulfill all the criteria for the award of the contract).
It was discussed that the Award Decision Notification is included in the eAwarding module
The eAwarding conceptual model diagrams were presented.
eRequest module
eRequest represents a document created by the Buyer to request an offer for goods and services from a Contractor within a Framework Agreement and direct awards for procurements below threshold (small scale procurement).
It was discussed that the Request for Offer document is included in the eRequest module
The eRequest conceptual model diagrams were presented.
eForms mapping requirements
A selection of eForms mapping requirements Github Issues on the ePO Github repository which were implemented for ePO 5.0.0 was presented. Specifically the following tickets and their solutions were presented:
eOrdering updates
The new eOrdering diagrams depicting Order Change, Order Cancellation and Order Agreement transactions were presented.
eCatalogue updates
A selection of Github Issues on the ePO Github repository related with the eCatalogue module which were implemented for ePO 5.0.0 was presented. Specifically the following tickets and their solutions were presented:
eFulfilment updates
A selection of Github Issues on the ePO Github repository related with the eFulfilment module which were implemented for ePO 5.0.0 was presented. Specifically the following tickets and their solutions were presented:
Updated workflow and model2owl evolution
It was mentioned that the model2owl configuration files was transferred from the ePO repository to the epo-conceptual-model repository.
An update on the Enterprise Architect file modifications was given, specifically that:
-
The WG approval date was moved to the skos:historyNote tags.
-
The eForms terms (BT/BG) references were moved to skos:editorialNote tags.
-
Links to the original definitions were added for all external terms used by the Ontology.
-
epo:status tags with the values 'proposed', 'approved' and 'implemented' were added to all ePO terms.
Work in progress
ePO ePO v5.1.0-rc.1
The upcoming release candidate 5.1.0-rc.1 was Presented. This version contains the ePayment module. Andreea Pasare presented the module, including the Conceptual Model diagrams (found on the 2025 June WGM presentation.
The ePayment module concerns payment data. ePayment data is checked against the invoice data in a Contract registry. It was mentioned that the ePayment module includes the Remittance Advice document.
Future Work
Future work for 2025 includes:
-
Publish final release of ePO v5.0.0.
-
Publish ePO v5.1.0-rc.1.
-
Publish final release of ePO v5.1.0.
-
ePO v5.2.0-rc1 that includes
-
Publish pre-award documents models
-
Minor updates for post-award modules
-
-
Finalise definition for all ePO concepts
-
Create simplified views of ePO
Closing:
Natalie Muric of the Publications Office presented the schedule for ePO Working Group meetings:
-
every Tuesday from 14:30 to 16:30 (EET)
-
every Thursday from 14:30 to 16:30 (EET)
In addition, all addresses to contact the ePO team were provided:
-
GitHub discussions: https://github.com/OP-TED/ePO/discussions
-
GitHub issues: https://github.com/OP-TED/ePO/issues
Any comments on the documentation?
