[OASIS Issue Tracker] (UBL-40) Unbounded Contracting System Type Code

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63109#comment-63109 ] 

Ken Holman commented on UBL-40:
-------------------------------

Available in: artefacts-ubl-2.2-csd01wd06-20160808-1240z.zip

https://www.oasis-open.org/committees/document.php?document_id=58668 


> Unbounded Contracting System Type Code
> --------------------------------------
>
>                 Key: UBL-40
>                 URL: https://issues.oasis-open.org/browse/UBL-40
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: New Feature
>            Reporter: Oriol Bausa Peris
>            Assignee: Ken Holman
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)