Working Group meeting

Date: 12/12/2023
Participants: Paloma Arillo, Klaus Nielsen, Laurent Schoojans, Dragos Stoica, Pascaline Laure Tchienehom, Cristian Vasquez
Model editor: Andreea Pasăre
Note editor: Natalie Muric

Agenda

  • Questions whilst addressing the ESPD Request

  • Review eAccess diagrams to be published in the release candidate

  • eAccess concept definitions

Discussion

Questions whilst addressing the ESPD Request

  • epo-acc:includesNationalCriteria changed to epo:includesNationalCriteria to be aligned with epo:QualificationCriterion.

8C+LQbxYEExacAAAAASUVORK5CYII=
  • ProcurementCriterion epo:hasConstraint can probably be removed as it is probably not the ProcurementCriterion that has a Constraint and we need to check in the modelling of the notices. This relation is used for standard form mappings:

B6c5C1YHsZ8aAAAAAElFTkSuQmCC

It was decided to keep epo:ProcurementCriterion epo:hasConstraint cccev:Constraint because removing it would create a major release.
Review eAccess diagrams to be published in the release candidate

  • epo-acc:ESPDRequest epo-acc:concernsProcedure predicate looks redundant since we have epo:Notice epo:refersToProcedure However, the ESPD Request does not have to be associated to a notice so it was decide to keep
    epo-acc:ESPDRequest epo-acc:concernsProcedure predicate:

wcjFlxfGHf8ugAAAABJRU5ErkJggg==
  • A clean-up of the eAccess diagrams has been done, resulting in the removal of redundancies such as:

  • epo:QuestionSubgroup epo:containsQuestion

  • epo:QuestionGroup epo:containsQuestion

  • epo:QuestionGroup does not have to have a QuestionSubgroup, so the cardinality of epo-acc:containsQuestionSubgroup is changed to 0.* instead of 1..*.

  • In an ESPD-Request, a Procurement Criterion must be initiated by a RequirementGroup or a QuestionGroup. Therefore, although both have a cardinality of 0..* from the Procurement Criterion, only one of the two concepts must be present.

The resulting diagram is depicted below:

2FBY8ZKMyU8AAAAASUVORK5CYII=

eAccess concept definitions

  • The following definition was added for epo-acc:Requirement:

“Data that a Buyer requests from a Tenderer.

Additional information:
The Requirement often has a Constraint.

WG approval 12/12/2023”

  • The following definition was added for epo-acc:RequirementGroup:

“A concept that contains one or more related Requirements or Requirement Subgroup.

WG approval 12/12/2023”

  • A proposal to replace the group and subgroup concepts with the use of identifiers was suggested and implemented as depicted below:

QE8RPcM5gTlwwAAAAASUVORK5CYII=

Action Points

  • Create instance diagram using group and subgroups identifiers instead of the concepts.