Working Group meeting 12/07/2022

Date: 12/07/2022
Participants: Georgia Lodi, Natalie Muric
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre


  • Discuss Status Information GH issues 357 and 358.


Status Information

  • We made considerable changes between the beta release and the final release. This discussion will have an impact on the model.

  • Having a status seems reasonable, but if we commit to a status we also need to commit to a process, to the status of phases, etc.

  • Then why not add the epo:isTerminated boolean at the level of Competition notice or DPS?

  • Are Procurement Relaunch BT-634 and PIN Competition Termination BT-756 mutually exclusive? Probably not. We can not see that from the eForms mapping.

  • We should choose the minimum for this release.

  • Should we add a boolean at the procurement object level?

  • But in the future we need to refer to that procurement object.

  • Relaunch and recurrence information are about the rules of succession of procedure. The difference is that the recurrence information is announced at the beginning of the procedure, and the relaunch is in the end.

  • We don’t need to distinguish if it is a termination of the competition or DPS. We can infer this based on the previous notice reference. (see standard form F03, section IV.2)

  • We need to create a proper systematisation of techniques and classes.

Decision taken:

  • Change StatusInformation to ProcurementProcessInformation

  • Add specific booleans for Competition and DPS

  • Create a link to a previous notice

  • This should be refactored in a future release.