Working Group meeting

Date: 23/08/2022
Participants: Cecile Guasch, Natalie Muric, Giovanni Paolo Sellito
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda

  • Standard forms mappings F21 & F22

    • F21

      • II.1.6.1 II.1.6.1.1 II.1.6.1.2 II.1.6.1.3

      • II.1.6.2

      • II.1.6.3

      • V.2.4.1 (It is the same as II.2.6)

Discussion

  • II.1.6) Information about lots

    • epo:ProcedureSubmissionTerm is created:

      • Subclass of epo:ProcedureSpecificTerm

ReUAAAAASUVORK5CYII=
  • Renaming epo:SubmissionTerm to epo:LotSubmissionTerm and the definition modified appropriately

  • Adding new attribute epo:isSubmissionForAllLotsAllowed in class epo:ProcedureSubmissionTerm for subsection “Tenders may be submitted for all lots” with the following definition: “Indicates whether tenders may be submitted for all Lots.

Additional information:
This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms)

WG approval 23/08/2022“

  • Renaming attribute epo:hasLotSubmissionLimit to epo:hasMaximumLotSubmissionAllowed

  • Adding boolean attribute epo:isOneLotOnlyAllowed with the following definition: “Indicates whether tenders may be submitted for only one Lot.

Additional information:
This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms).

WG approval 23/08/2022”

  • Moved epo:hasMaximumNumberOfLotsToBeAwarded attribute in epo:ProcedureTerm

  • Decided to delete class epo:ProcedureSubmissionTerm and moved attributes to epo:ProcedureTerm

ImfoXHZM3MryFXAdcC090Pk+JiLI3+m5lQLBALkKgAAANwKcIwnzfziGjaGfv6fkEvHgF6X13QVlrYgz7ch5fZTIrIGIHOQbDJTIwqmhQi7gAVja4Aek0BMCcUDxwA8NsQiUf6nppgUxsYmeNDzLYBp74cLny8g06vw1DIul4dcBQAAANcAx3jSFHxuLqvpPH993TEWl9Yh9xAJhchLFHLRGB1NH+Wfdyo60yI+z4vsBQNe4m0tb5ysVMWmAccAPCp43BNiVkUqpfToiItcBdgBpr0fNJBOZxc2JKQVgVvdAACApwDHeLpwubyQyKyNzZ3zL687hkwmjU0tHJ2YRV6lkPN6iNhijtDmEoLhzOCc8fPXDpCuAscAPCp2dg+gvEVj1AkFDg0cYA+Y9n7oSKWSTxVtUcn5oGsHAAA84v8DdUaxVwRA+FUAAAAASUVORK5CYII=
  • For the subsection “The contracting authority reserves the right to award contracts combining the following lots or groups of lots:” a new string attribute should be created on the epo:ProcedureTerm, epo:hasLotAwardCombination, with the following definition: “The contracting authority reserves the right to award contracts combining lots or groups of lots.

Additional Information:
This property contains information about the Lots concerned.
This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms).

WG approval 23/08/2022”

  • V.2.4.1 (It is the same as II.2.6)

    • The value in section II is used only when we have a call for competition.

    • The value in section V is used in all other cases.

    • They do not appear at the same time

    • In case we have different values between contract notice and contract award notice we need to provide another predicate.

    • Created the predicate epo:hasRestatedEstimatedValue. “A forecast of the value of the procurement before competition, which is repeated in the contract award notice.

Additional Information:
This property should be equivalent to the epo:hasEstimatedValue. It is created, however because the existent data model two different fields (with the same conceptual meaning) and therefore the values may differ.

This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms).

WG Approval 23/08/2022”

  • In all Contract Awarded Notices, in section V, we should use epo:hasRestatedEstimatedValue and in section II, we should use epo:hasEstimatedValue

B5aRIH9tIpN9AAAAAElFTkSuQmCC
  • In the next meeting should be discussed which metadata should be included as part of the content.