Working Group meeting

Date: 01/06/2023
Participants: Natalie Muric, Glan Luigi Albano, Giovanna Filippone, Goncalo Negrao, Martina Pititto, Paolo De Lazzaro, Peter, Thomas Pettersson
Model editor: Andreea Pasăre
Note editor: Jana Ahmad

Agenda:

  • ePO module harmonisation

  • Discuss eContract model

Discussion:

ePO module harmonisation

It was noted that the models had become easier to work with after the changes made during the previous post-award meeting. In the updated models, each line can now have a description and specify an item. The Information Hub has a direct link to the line, and the AllowanceChargeInformation could be defined at both the Document and Line levels.

8D9jXSo8xmAAAAABJRU5ErkJggg==

The participants then discussed modeling virtual locations for service deliveries it was decided to use location based on coordinates, indicating a geographical location where the delivery could take place.
It was noted after the WGM that a virtual delivery location should be represented as a URL and further discussion is needed on this matter.

CC8AAACZqQkvUYwvceVLPvFf1o0xy2eK0UV4AQAAmLLwUlX8gGeMWX4DAACw2gkvxpixDQAAwGo31eEFAAAAYDkTXgAAAADGRHgBAAAAGBPhBQAAAGBMhBcAAACAMRFeAAAAAMZEeAEAAAAYE+EFAAAAYEyEFwAAAIAxEV4AAAAAxkR4AQAAABgT4QUAAABgTIQXAAAAgDERXgAAAADGRHgBAAAAGBPhBQAAAGBMhBcAAACAMRFeAAAAAMZEeAEAAAAYE+EFAAAAYEyEFwAAAIAxEV4AAAAAxkR4AQAAABiTWngxxhhjjDHGGGOMMaOb6P8HHHC3FlIgQ14AAAAASUVORK5CYII=

Contract

The Contract model was presented whereby a Contract is a Document and is subject to Contract Terms. It is signed by both the Contractor and the Buyer(s). It has reference to the Lot(s).
The contract model requirements were mapped to the ePO ontology as follows, where the main bullet represents the requirement, and the sub-bullets represent the corresponding ePO mapping:

  • Contract

    • epo:Contract

  • Contract identifier

    • epo:Contract adms:identifier adms:identifier

  • Contract issue date:

    • Dct:issued in epo:Document

  • Contract issue time

    • Dct:issued in epo:Document

  • Contract type

    • At-voc:contract-nature codelist. But it was noted that, it does not cover for FA or DPS needs to be checked. Also, Reference number of the contract needs to be checked.

  • Process control

    • In the meeting, it was noted that Process control is not applicable in data-oriented modelling (ePO)

  • Contracting body

    • epo:Buyer

  • Economic operator

    • epo:Contractor

  • Procurement project name

    • Dct:title on epo:Contract

  • Procurement project description

    • Dct:description on epo:Contract

  • Procurement project type

    • uses contract-nature on ContractTerms

  • Estimated total value

    • is at the ProcurementObject level.

  • Description of extension and options:

    • epo:hasOptionsDescription on ContractTerms

  • CPV

    • at-voc:cpv codelist at Contract level

  • CPV

    • supplementary is not included in ePO

  • Procurement project location NUTS code

  • epo:ContractTerm epo:definesPlaceOfPerformance dct:Location

  • dct:Location epo:hasNutsCode at-voc:nuts

  • Period start date

    • epo:ContractTerm epo:definesContractPeriod epo:Period

  • Period start time

    • epo:ContractTerm epo:definesContractPeriod epo:Period

  • Period end date

    • epo:ContractTerm epo:definesContractPeriod epo:Period

  • Period end time

    • epo:ContractTerm epo:definesContractPeriod epo:Period

  • Lot identifier

    • epo:Contract epo:hasLotReference epo:Lot

  • Award criterion type

    • epo:Lot epo:specifiesProcurementCriterion epo:AwardCriterion epo:hasAwardCriterionType at-voc:award-criterion-type

  • Legal references

    • epo:Lot epo:hasLegalBasis at-voc:legal-basis OR epo:hasLegalBasisDescription on epo:ProcurementObject

  • Tender identifier

    • epo:Contract epo:includesTender epo:Tender

  • Tender digest

    • epo:hasElectronicDigest

  • Tender signature

    • epo:hasElectronicSignature

  • Tender total amount:

    • epo:Tender epo:hasFinancialOfferValue epo:MonetaryValue

  • Tender total taxes amount:

    • epo:Tender epo:hasTaxInformation epo-ord:TaxInformation epo-cat:hasAmount

    • It was noted a conflict in the definitions of Tender total taxes amount and Tender total amount in the in contract model requirements.

      • Tender total amount: The total amount of the offered deliverables in the tender excluding all taxes payable by the contracting authority.

      • Tender total taxes amount: The total amount of taxes included in the total amount.

  • Award identifier:

    • epo:AwardDecision adms:identifier adms:Identifier

  • Award date

    • epo:hasAwardDecisionDate (by using xsd:dateTime attribute)

  • Award time

    • epo:hasAwardDecisionDate (by using xsd:dateTime attribute)

  • Winner economic operator

    • epo:Winner

  • Economic operator name

    • dct:title on the foaf:Agent

  • Economic operator identifier:

    • adms:identifier on the foaf:Agent

  • Economic operator registration country code:

    • org:Organization epo:hasRegistrationCountry at-voc:country.

  • Documents:

    • epo:Document epo:associatedWith epo:Document

    • epo:Contract is an epo:Document

  • Attachment identifier:

    • adms:identifier on epo:Document

  • Attachment description:

    • dct:description on epo:Document

  • Attached document

    • We do not provide the binary object, only URL (epo:hasAccessURL on the epo:Document)

  • Deliverable offered

    • epo:Contract epo:specifiesDeliverable epo:Item

  • Deliverable name

    • dct:title on the epo:Item

  • Deliverable description

    • dct:description on the epo:Item

  • Delivered quantity

    • epo:Deliverable epo-cat:hasQuantity epo:Quantity

  • Deliverable total amount

    • epo:Deliverable epo:hasTotalValue epo:MonetaryValue The model below was validated.

IP+PwHrnIbrcjTtAAAAAElFTkSuQmCC

The property epo:hasAccessURL has been removed from the Contract class because it was inherited from the Document class.
The property epo:hasHomePage was changed to epo:hasInternetAddress in cpov:ContactPoint class.
It was noted that epo:hasInternetAddress is used in various places

  • cpov:ContactPoint epo:hasInternetAddress

  • Org: Organization epo:hasInternetAddress

  • Org: Organization epo:hasPrimaryContactPoint cpov:ContactPoint The epo:hasInternetAddress was defined:
    epo:hasInternetAddress: The main webpage used by the instance of the concept.
    It was noted that the Contract class needs to have its own estimated value, as it is not considered a Procurement Element. This is to distinguish between the Tender value and the Contract value. As a result, the Contract now includes the relation epo:hasContractValue to capture the value associated with the contract. This property is linked to the epo:MonetaryValue class. Additionally, the Contract has a lot reference through the property "epo:hasLotReference" which connects it to the epo:Lot class.
    Further discussion is needed to determine how to model Monetary Values with respect to both Contract and Tender.

The Contract class has an Amended Contract subclass. The Amended Contract class inherits all attributes from the Contract class.

s7jRZficYUUAAAAASUVORK5CYII=

The following Notices were discussed, and it was suggested to update the Notice modules accordingly to implement them.

  • Contract Completion Notice Announcement of the completion of a contract The main purpose of this notice is to understand if the contract was completed as set out in the contract award notice (to be published on 2023-06-14 in EU Vocabularies) It was noted that the Completion Notice announces the completion of the Contract, not the Contract itself. Therefore: epo:announcesContract was changed to epo:announcesCompletionOfContract.

  • Pre-Market Consultation Notice Announcement of a pre-market consultation. A pre-market consultation is not a call for competition, and no procurement documents are available at the time of consultation. A consultation may or may not be followed by a future competition (to be published 2023-06-14 in EU Vocabularies).

AHk26Ufs8JFVAAAAAElFTkSuQmCC

Action Points

  • Points to be followed up

    • What is the Reference number of the contract

    • The conflict in the definitions of Tender total taxes amount and Tender total amount needs to be addressed.

      • Tender total amount: The total amount of the offered deliverables in the tender excluding all taxes payable by the contracting authority.

      • Tender total taxes amount: The total amount of taxes included in the total amount.

    • Contract type is mapped to at-voc:contract-nature codelist (works, service and supplies) in ePO. However in the contract model requirements contract type can also be FA and DPS it should be checked if there is a valid reason for this?

    • Update the Notice modules to implement Contract Completion Notice and Pre-Market Consultation Notice.