[UBL-40] Unbounded Contracting System Type Code - OASIS Technical Committees Issue Tracker

Details

Type: New Feature
Status: Closed
Priority: Major
Resolution: Fixed
Component/s: None
Labels:
None

Proposal:

Hide

Looking at this the relationship between Tendering Process and Contracting System has been hidden by the Tendering Process ABIE (in 2.1).

It has been defined with BBIEs of:
Tendering Process. Identifier
Tendering Process. Original_ Contracting System. Identifier
Tendering Process. Description. Text
Tendering Process. Negotiation_ Description. Text
Tendering Process. Procedure Code. Code
Tendering Process. Urgency Code. Code
Tendering Process. Expense Code. Code
Tendering Process. Part Presentation Code. Code
Tendering Process. Contracting System Code. Code
Tendering Process. Submission Method Code. Code
Tendering Process. Candidate Reduction_ Constraint. Indicator
Tendering Process. Government Agreement_ Constraint. Indicator

It should have been:
Tendering Process. Identifier
Tendering Process. Description. Text
Tendering Process. Negotiation_ Description. Text
Tendering Process. Procedure Code. Code
Tendering Process. Urgency Code. Code
Tendering Process. Expense Code. Code
Tendering Process. Part Presentation Code. Code
Tendering Process. Submission Method Code. Code
Tendering Process. Candidate Reduction_ Constraint. Indicator
Tendering Process. Government Agreement_ Constraint. Indicator

with an ASBIE (appears to be 0..n) to an ABIE called Contracting System, comprising...
Contracting System. Identifier
Contracting System. Contracting System Type Code. Code

… because Contracting System is not dependent on the Tendering Process. That is why we now have this problem. If you look at Tendering Process. Original_ Contracting System. Identifier it has been qualified precisely because there may be more than one Contracting System. And as time goes on we may need to add more BBIEs to Contracting System so I propose we fix it in 2.2.

I suggest that we add the Contracting System ABIE then any other ABIE (Tendering Process) can have an ASBIE to this with 0..n cardinality.

I realise this gives duplication (because we cannot remove Tendering Process. Original_ Contracting System. Identifier and Tendering Process. Contracting System Code. Code). But it means we can issue a usage note to encourage implementers to use the new structure. In UBL 3.0 we can drop the old BBIEs.

Show
Looking at this the relationship between Tendering Process and Contracting System has been hidden by the Tendering Process ABIE (in 2.1). It has been defined with BBIEs of: Tendering Process. Identifier Tendering Process. Original_ Contracting System. Identifier Tendering Process. Description. Text Tendering Process. Negotiation_ Description. Text Tendering Process. Procedure Code. Code Tendering Process. Urgency Code. Code Tendering Process. Expense Code. Code Tendering Process. Part Presentation Code. Code Tendering Process. Contracting System Code. Code Tendering Process. Submission Method Code. Code Tendering Process. Candidate Reduction_ Constraint. Indicator Tendering Process. Government Agreement_ Constraint. Indicator It should have been: Tendering Process. Identifier Tendering Process. Description. Text Tendering Process. Negotiation_ Description. Text Tendering Process. Procedure Code. Code Tendering Process. Urgency Code. Code Tendering Process. Expense Code. Code Tendering Process. Part Presentation Code. Code Tendering Process. Submission Method Code. Code Tendering Process. Candidate Reduction_ Constraint. Indicator Tendering Process. Government Agreement_ Constraint. Indicator with an ASBIE (appears to be 0..n) to an ABIE called Contracting System, comprising... Contracting System. Identifier Contracting System. Contracting System Type Code. Code … because Contracting System is not dependent on the Tendering Process. That is why we now have this problem. If you look at Tendering Process. Original_ Contracting System. Identifier it has been qualified precisely because there may be more than one Contracting System. And as time goes on we may need to add more BBIEs to Contracting System so I propose we fix it in 2.2. I suggest that we add the Contracting System ABIE then any other ABIE (Tendering Process) can have an ASBIE to this with 0..n cardinality. I realise this gives duplication (because we cannot remove Tendering Process. Original_ Contracting System. Identifier and Tendering Process. Contracting System Code. Code). But it means we can issue a usage note to encourage implementers to use the new structure. In UBL 3.0 we can drop the old BBIEs.

Description

The element "Type of contrct to be establilshed" is mapped to ContractingSystemCode.
We need to be able to use "Type of contract to be established" for different scenarios that could exist in a given procedure: framework agreement, DPS, DPS with additional purchase.

1. DPS is a procedure; framework agreement (FA) is a contract.
2. DPS is fully electronic, FA not necessarily.
3. FA is closed both sides: all CAs has to be announced at the stage of launching a procedure, all contractors has to be in the framework agreement from the beginning. DPS is open for economic operators but can be also open for CAs (DPS established by CPBs).
4. Use of DPS is limited to the commonly used purchases. For FA there is no limitation of this kind.

Therefore, it a FA maybe established under a DPS but not DPS under FA. Which means we need to be able to select both options at the same time.

In the forms being developed it seems that this will be addressed per lot, therefore it would be a good idea to add this as well in "Procurement Project"

This now makes me realise that the "Type of contract to be established" is not a good name it should perhaps be "Information about a framework agreement or a dynamic purchasing system" as in the forms, but this is question CEN BII terminology.

We therefore need 0..n as requested.

Unbounded Contracting System Type Code

Details

Description

Attachments

Activity

People

Dates