Description:
Dear all,
There will be two topics to be discussed in the pre-award subcommittee.
1- Need: add new types in the TenderingCriterionProperty ABIE. ExpectedURL, ExpectedIndicator)
The ResponseValue ABIE that was developed in the post award context caters for all the generic needs of the TenderingCriterionProperty.
There is an opportunity to streamline pre and post award.
Yet the backward compatibility constraint prevent from deprecating the TenderingCriterionProperty.
Do we wish to add an ExpectedResponse component of type ResponseValue while creating confusion as some information will have more information carriers by doing so?
2- Need : allow for expressing multiple CPV codes as one requirement
Increasing the cardinality ExpectedCode or ResponseCode from 0..1 to 0..n would support this requirement.
Yet there seem to be a NDR rule that prevents to add a cardinality n on a BBIE. This is because attributes apply to the information itself and would there be more elements in one BBIE it would not be possible to qualify those with different attributes.
Do we wish to break this rule for the sake of managing CPV codes requirements or which other option do we have?
KRs,
Cécile GUASCH
==========
Agenda:
==========
Minutes:
==========
Attendance: