Working Group meeting
Date: 21/03/2023
Participants: Natalie Muric, Wim Kok, Giampaolo Sellitto
Model editor: *Andreea Pasăre
*Note editor: Jana Ahmad
Discussion:
WG discussed the eContract model, mainly the initial contract information requirements:
-
A epo-con: announces contract exists between epo:Contract and epo-con:ContractDocument. Note: Contract document: it is not a contract, it is maybe some additional things such as meta data. What is in the contract is in the contract document.
-
An excel document is created in sharepoint including Contract related concepts and their definitions.
-
epo:bindsBuyer relation created between contract and Buyer.
-
epo:signedByBuyer relation is created between Buyer and contractDocument
WG did a Mapping between Contract model and initial contract information requirements:
-
Issue date, time and identifies should be in the document
-
isSubjectToContractSpesificTerm relation is created between contract and ContractTerm
-
Procurement project type: is contract-nature on ContractTerm
-
Description of Extension and option: epo:ContractTerm has epo:hasOptionsDescription data property. Duration is considered to be about Options.
-
Period start date, Period start time: contractTerm defines the contract period.
-
At-voc:cpvsuppl is removed
-
CPV: At-voc:cpv enumeration is added.
-
CPV supplementary: is not included in ePO
-
Project execution location: epo:ContractTerm defines place of performance which is dct:location
-
Procurement project lot: Contract and lot class is created.
-
Lot identifier:
-
epo:hasTenderReference relation is renamed between contract and tender.
-
epo:hasLotReference relation is renamed between contract and lot.
-
Working Group meeting
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 procurementSope not a ProcrumentObject
-
-
SelectioCriteria and ExclusionGround are specified for LotQualificationPhase
-
Lot Plan composition model
-
Contain 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.
Working Group meeting
Date: 07/02/2023
Participants: Jana Ahmad, Natalie Muric, Csongor Nyulas
Model editor: Andreea Pasăre
Note editor: Eugeniu Costetchi
Agenda
-
Standard form mappings - ePO GitHub issues:
-
GH 422 Missing fields F21, IV.2.5, IV.2.9
-
-
Procedure/Sub-procedure