search

OP-TED / ePO

The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
European Union Public License 1.2
58 stars 18 forks source link

Modelling procedure & sub-procedure in the cases of DPS, FA, PQS and possibly others #416

Closed costezki closed 1 year ago

costezki commented 1 year ago

It was discovered that the Dynamic Purchasing System, Qualification System, Framework agreement, and other multi-stage procedures need to consider the concept of mini-competition. This has impact on the core of the EPO.

Some (possibly) related tickets: #169 #193 #198 #216 #267 #161

costezki commented 1 year ago

Context: comments on the mappings to F06 (tx1-2)

IV.1.3.1 is about the establishment of a FA whereas the concept from the ontology is epo:uses technique. However is probably ok as used in combination with termination of FA

IV.1.3.2 is about the set-up of a DPS whereas the concept from the ontology is epo:uses technique. However is probably ok as used in combination with termination of DPS

Although the ontology foresees by default one lot. In the case of CAN for DPSs and FAs the relation to the lot can not be used for all awarded contracts they need to be done at the level of the mini-competition which in turn could be related to the lot it is part of the same procedure (231436-2021)

231436-2021 V2.2.1-V.2.2.6 Concerns a DPS with only 1 lot but many contracts concerned therefore the information about the tenders received per “mini-competition” needs to be made rather than per lot there is only 1 lot but 22 SubmissionStatisticalInformation the submissionStatistical needs to relate to the” mini-competitions”

V.2.4.3 if a DPS and FA is used the statistical informationof the lowest and highest TenderValue will not work as it is not per lot but mini competition

The problems of DPS for mini competitions will be the same/similar for FAs. It should be noted that you can have a procedure with many lots and several DPSs or several FAs so the DPSs/FAs will need to have a relation to the corresponding procedures and lots.

231436-2021 V.2.4 Lot hasRestatedEstimatedValue. The estimated value varies per contract however as this is calculated from the lot in this case it does not work as there is only one lot and this is about DPS, the same could be seen in the case of FAs. The estimated value probably comes from the “sub-procedure.

muricna commented 1 year ago

One lot can have many contracts as noted in the ontology. And one contract can result from 0..* LotAwardOutcome And many LotAwardOutcome can describe one Lot Therefore the problem does not seem to be between the lot, lot Award and Contract The problem may be that the relation SubmissionStaticialInformation concerns SubmissionsForLot Lot

andreea-pasare commented 1 year ago

image

andreea-pasare commented 1 year ago

The ePO v4.0.0-rc.1 provides the following: image