Working Group meeting 28/02/2023
Date: 28/02/2023
Participants: Ahmed Abid, Wim Kok, Natalie Muric, Csongor Nyulas, Sellitto Giovanni Paolo
Model editor: Andreea Pasăre, Eugen Costetchi
Note editor: Jana Ahmad
Discussion
GH 370
-
To be closed only after we get confirmation that (and perhaps a link to) an issue asking for the introduction of appropriate code(s) in the at-voc:direct-award-justification vocabulary was opened with DG GROW.
GH 431
-
hasRestatedAwardedValue: This is wrongly modeled and applied in the mappings. It will be updated in the context of modeling eContract. To be discussed in RDF meeting
Procedure and sub-procedure:
-
WG decided to:
-
Separate a procedure from its scope
-
Drop down plan into its phases.
-
-
Notes from WG:
-
Procedure itself is a plan.
-
It is not correct to use process concept to refer to plan/procedure.
-
Nothing is to be executed in procedure, it is just a plan
-
Lot is referring to purpose.
-
-
Plan hierarchy model
-
Lot is procurementScope not a ProcurementObject
-
-
SelectioCriteria and ExclusionGround are specified for LotQualificationPhase
-
Lot Plan composition model contains the phases/stages of procurement lifecycle
-
Overall plan composition model
-
Note, if we have hundreds of lots and anything is applied to one lot it will be applied to all lots in the same procedure (to be discussed later).
-
We should find a better term than LotPreAwardLifecycle/Workflow.
