Working Group meeting

Date: 19/10/2021
Participants: Hilde Kjølset, Giorgia Lodi, Natalie Muric, Thor Steinar Møller, Giovanni Paolo Sellitto
Model editor: Eugen Costezki
Note editor: Andreea Pasăre

Agenda:

  1. Glossary points to be discussed

    • Attribute definitions (see the file)

      • epo:AdditionalInformation

      • epo:ThresholdType

  2. Continue modelling the subroles

List of subroles:

Organisation-subrole table definition: This table provides the list of the different sub-functions of the organisations in a procurement procedure.

bud-pay

Organisation whose budget is used to pay for the contract

Permitted values for ‘hasRole’: Context: Contract

exec-pay

Organisation executing the payment

Permitted values for ‘hasRole’: buyer or the service provider

group-lead

Group leader

Permitted values for ‘hasRole’: buyer, winner, tenderer or the service provider. Context for the buyer: Procedure

info-prov

Organisation providing additional information about the procurement procedure

Permitted values for ‘hasRole’: buyer or the service provider. Context: Procedure

offl-acc

Organisation providing offline access to the procurement documents

Permitted values for ‘hasRole’: buyer or the service provider. Context: Lot,

processor

Organisation processing tenders

Permitted values for ‘hasRole’: buyer or the service provider. Context: Lot

recepient

Organisation receiving tenders

Permitted values for ‘hasRole’: buyer or the service provider. Context: Lot

req-proc

Organisation processing requests to participate

Permitted values for ‘hasRole’: buyer or the service provider. Context: Lot

req-recep

Organisation receiving requests to participate

rev-info

Organisation providing more information on the review procedures

signatory

Organisation signing the contract

Discussion

  1. Glossary points to be discussed

    • epo:AdditionalInformation - Keep definition from epo:Lot

    • epo:ThresholdType - No definition yet. Wait for Criterion discussion ().

  2. Continue modelling the subroles

signatory subrole:

dateOfSignature is useful to emphasize that the date of signing can be different for the Buyer or the Winner.

The signatory is not possible in Competition Notices.

We can still use a common approach to model the situation, and the only difference will be whether this is anchored in time or in a different legal modality (obligation, permission).

The dateOfSignature from Contract represents the date of the last signature of the Contract.

4AAAAASUVORK5CYII=

req-recep subrole:

Permitted values for ‘hasRole’ are: Buyer (two CPBs included), ServiceProvider.

Question:

  • Are we including in the model all the specializations of the Procurement Situation?

General participation pattern

*Choice 1: *

+MB+oTb4b6GwYAgA+GZgAAwF59ys34f7X1fBzRXdKNAAAAAElFTkSuQmCC

Decision:

  • Subroles can be modeled outside the WG, based on the general participation pattern. Context is always the Lot. Subroles are defining the Contract Notice.

Comments for EU Vocabulary List:

  • bud-pay - Should this not be the 'Organisation that provides funding for the contract'?

  • organisation-subrole - This table provides a list of subfunctions, therefore it is not necessary to put the word 'organisation' in the label. Re-labeling these concepts would harmonise the labels with those in the organisation role code list.

Questions for DG GROW:

  • In the case of a signatory subrole, are we modeling a permission or an actual contract signing?

  • What are the subroles used for?

  • Group-lead is a subrole for the Tenderer?