Working Group meeting

Date: 12/10/2021
Participants: Cecille Guasch, Hilde Kjølset, Giorgia Lodi, Natalie Muric,Thor Steinar Møller, Giovanni Paolo Sellitto
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda:

  • Presentation of the note-taking

  • Apply the note-taking to a simple issue:

    • Identify the context/process where each “sub-role” is involved.

    • For each context/process, what other participants (actors or objects) are involved?

    • Is the term “sub-role” appropriate?

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

exec-pay

Organisation executing the payment

group-lead

Group leader

info-prov

Organisation providing additional information about the procurement procedure

offl-acc

Organisation providing offline access to the procurement documents

hprocessor

Organisation processing tenders

recepient

Organisation receiving tenders

req-proc

Organisation processing requests to participate

req-recep

Organisation receiving requests to participate

rev-info

Organisation providing more information on the review procedures

signatory

Organisation signing the contract

Decision: “signatory” subrole

Issue

Identify the situation where the signatory subrole is used and what is the proper way to model it.
It is labelled as “Organisation signing the contract”.

Alternative choices

Choice 1: so-called “subrole” as function specification in a contract signing situation with a role

wd2OotQW8XUsAAAAABJRU5ErkJggg==
AdhWl1kD+00QAAAAAElFTkSuQmCC

Discussion

We need a natural person signing on the behalf of the Organisation.
The goal is to identify one or more of those organisations that have the role of the contractor.
If the Winner doesn’t sign, he doesn’t become a Contractor.
The triggering event to become a Contractor is the Signing of the contract by the Winner.
The other side of the Contractor Situation is the Contractee Situation.

Should we call Situation instead of Process?
According to the Oxford dictionary, a Situation is a set of circumstances of only one actor in a state of affairs.
Participation is preferred instead of Situation, like ProcurementParticipation.

ContractorSituation becomes ContractorParticipation. The same happens with ContracteeParticipation.

The Commission always signs last.

The Role embedded in the Situations: ContracteeParticipation and ContractorParticipation?

Maybe we should consider ContractSituation instead of ContractingSigningActivity.
In eForms, they want to convey the information in which Organisation performed an activity for which they have an organised Role.

This can be modelled according to the Award Reification diagram from version 2.0.2
The Winner doesn’t become the Contractor until the Contract is signed.
Subroles should be named functions.
There is always a Natural Person behind an Organisation that signs the contract.

Chosen solution

No final decision

Question: items in the subrole list

Note: The subroles controlled list enumerates actual (sub)roles in a granular action (i.e. action part of a broader process where the “primary” roles take part), but we think they should be functions, i.e. names of activities/actions.

  • Question for GD GROW: What is the difference between the organisation that executes the payment and the organisation that has the budget?

  • Can we remove the “organisation” term from the label of the concept and, instead, refer to the action only?