REPORT ON THE FIRST 2024 BIANNUAL WORKING GROUP MEETING OF THE EPROCUREMENT ONTOLOGY

Online meeting: 10/07/2024

Participants: Paloma Arillo (OP), Wim Kok (loginus.nl), Natalie Muric(OP), Gonçalo Negrão, Nicole Paterson-Jones (OP), Giovanni Paolo Sellitto (ANAC IT), Dragos Stoica (OP), Volodymyr Tarnay (OCP), Pascaline Laure Tchienehom (NTTDATA France)
Presenter: Andreea Pasare (Meaningfy/Infeurope),
Note editor: Achilles Dougalis (Meaningfy/Infeurope)

Meeting Agenda

  • Welcome

  • Review of 2024

  • ePO 4.1.0-rc.2 (published)

  • ePO 4.1.0-rc.3 (in progress)

  • 5 minute break

  • ePO 4.2.0-rc.1 (in progress)

  • Pre-Award updates

  • Future work

  • Updates to the documentation

  • Open discussion

  • Closing

Welcome:

Natalie Muric explained the aim of the meeting is to present the work carried out since the last meeting in December 2023 and to present the plan for the second half of 2024. Stakeholders’ attention was drawn to the release of eAccess, eSubmission and eInvoicing modules as well as the Publication of ePO 4.1.0 and the first candidate of ePO 4.2.0

The following sections provide a summary of what was presented by Andrea Pasare and discussed by the Working Group.

Publication of ePO 4.1.0-rc.2

The release candidate 4.1.0-rc.2 was presented. This release and its corresponding technical files can be found at https://github.com/OP-TED/ePO/tree/4.1.0-rc.2 . ePO 4.1.0-rc.2 includes the new modules of eAccess and eSubmission modules as well as updates to the other modules. For more information on what has changed, please consult the corresponding release notes.

eAccess module

eSubmission module

Work in progress

ePO 4.1.0-rc.3

The upcoming release candidate 4.1.0-rc.3 was discussed. This particular version contains fixes of Github issues related to ePO 4.1.0-rc.2.

ePO 4.2.0-rc.1

The upcoming release candidate 4.2.0-rc.1 was Presented. This version contains the eInvoicing module. Andreea Pasare presented the module, including the Conceptual Model diagrams (found on the 2024 July WGM presentation), the Roles involved in the eInvoicing phase, and the use cases and user stories that were used in order to develop the module. During the presentation, it was mentioned that the eInvoicing model was based on PEPPOL’s einvoicing data model standard.

Future Work

Future work for 2024 includes the publication of ePO 4.1.0-rc.3, and ePO 4.2.0-rc.2 release candidates, as well as the actual release of ePO 4.1.0. Other activities include the continuation of the alignment with PEPPOL on Post-Award and Pre-Award ePO module updates as well as Concept definition updates. Furthermore, the working group will continue addressing the existing GitHub issues.

Updates to the documentation

Achilles Dougalis presented the documentation updates on Github repository including Readme files on all Implementation subfolders, and the addition of the Discussions section. Also, a short presentation of the updated Documentation Page including User Guides to the ePO Conceptual model was made.

Open Discussion

There was a question regarding the existing data using the structure of the Ontology. Natalie Muric replied that Contact award Notice data are available on Cellar, and that soon eforms data will be available. It was also noted that the harmonization of Post award and pre award ePO concepts will facilitate the usage of ePO.

Closing:

Natalie Muric of the Publications Office presented the next meeting schedule for ePO: They take place twice a week from 14:30 to 16:30 (EET) during the year on Microsoft Teams. Everybody is welcome. Tuesday meetings are more about ePO core development. Thursday meetings are more specific for different modules: eCatalogue, eOrdering, etc. Users do not need to follow on a weekly basis and any doubt can be put also in a GitHub issue.

We would like to release version 4.1.0 by mid of September and we would appreciate any feedback even if it is sent late. The suggestions will be taken into consideration for a future release. All addresses to contact the ePO team are provided in the last slide:

or alternatively via:

ePO Working Group meetings:


Any comments on the documentation?