UBL PR - Comment - "TenderingProcess" in "ProcurementProjectLot"

["Mr. Yves Jordan" <yves.jordan@ext.publications.europa.eu>]

Hi,

The forthcoming regulation aims at simplifying the work for the contracting authorities, increasing consistency, traceability and reliability of notices reported information. It is also an opportunity to get rid of current notices limitations.
Every notice will have at least one lot; when more than one lot exist in the notice, these may have some process related information that differ although they may be driven by a single major procurement project (i.e. belong to the same procedure).
Removal of current restrictions by the regulation will lead to an increasing number of such situations; currently, process related information likely to differ between lots are:
 AccessToolsURI,
 TenderSubmissionDeadlinePeriod / EndDate,
 ParticipationRequestReceptionPeriod / EndDate,
 OpenTenderEvent / OccurrenceDate, Description, OccurenceLocation,
 AuctionTerms / Description, AuctionURI.

Currently, UBL 2.2 considers ÂTenderingTerms at the lot and at the notice levels, allowing this way to properly mark lots specific terms; however for whatever reason, in UBL-2.2, ÂTenderingProcess is only permitted at notice level and CAs are not given a way to encode lots specific process information.

For:
 approach consistency between ÂTenderingTerms and ÂTenderingProcessÂ, 
 backward compatibility and solution simplicity, and
 prevention of unnecessary and incomprehensible customization,
I suggest having ÂTenderingProcess optional and non-repeatable added to ÂProcurementProjectLot right after ÂTenderingTermsÂ.

Kind regards,
Yves