Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Worked example of Framework Contracts for documentation #310

Closed
timgdavies opened this issue Feb 26, 2016 · 9 comments
Closed

Worked example of Framework Contracts for documentation #310

timgdavies opened this issue Feb 26, 2016 · 9 comments
Assignees
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Milestone

Comments

@timgdavies
Copy link
Contributor

timgdavies commented Feb 26, 2016

Requested by a user.

@timgdavies timgdavies added the Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues label Feb 26, 2016
@timgdavies timgdavies self-assigned this Feb 26, 2016
@timgdavies timgdavies added this to the Version 1.1 milestone Jul 25, 2016
@duncandewhurst duncandewhurst self-assigned this Aug 3, 2016
@timgdavies
Copy link
Contributor Author

@duncandewhurst has been working to identify the different kinds of framework, and how these can be modelled in OCDS. These are listed below for comment.

Framework type OCDS approach
Single supplier with direct call-offs A single contracting process using award(s) to represent the framework agreement and contract(s) to represent the call-offs.
Multiple suppliers with direct call offs A single contracting process using award(s) to represent the framework agreement and contract(s) to represent the call-offs.
Multiple suppliers with mini-competitions for call-offs Multiple contracting processes: One process using awards to represent suppliers on the framework agreement; Multiple selective or limited processes to represent the mini-competitions linked to the framework agreement via relatedProcess (see #371).
Multiple suppliers with either direct call-offs or mini-competitions Multiple contracting processes: One process using awards to represent suppliers on the framework agreement and contract(s) to represent the direct call-offs; Multiple selective or limited processes to represent the mini-competitions linked to the framework agreement via relatedProcess (see #371).
Dynamic Purchasing System Multiple contracting processes: One process using awards to represent suppliers joining the DPS. tender/status should be active for the lifetime of the dynamic purchasing system with tender/tenderPeriod and tender/awardPeriod reflecting that suppliers can join the DPS at any time. Multiple selective or limited processes to represent competitions between suppliers on the DPS for individual contracts, linked to the DPS via relatedProcess (see #371).

@duncandewhurst
Copy link
Contributor

Feedback from the teams at Colombia Compra and Buenos Aires Compra:

The single supplier with direct call-offs and multiple suppliers with mini-competitions for call offs framework types are in use in both jurisdictions. No other types of framework agreement are used.

Colombia Compra also suggested modelling the single supplier with direct call-offs and multiple suppliers with direct call-offs framework types using multiple contracting processes. This approach could also be used for direct awards in the multiple suppliers with either direct call-offs or mini-competitions framework type.

This approach would be more consistent with the approach used for the other framework types, reducing overall complexity, but would also mean that information about these framework types could not be contained within a single OCID/release, increasing complexity for users interested in only those framework types.

This approach also raises the issue of extending the codelist for initiationType to include a code for framework call-off so that this type of contracting process can be more easily distinguished from other contracting processes. We may also want to consider introducing a code for dynamic purchasing system to the initiationType codelist.

This issue is also related to linking related processes where we should consider whether the relatedProcess field should be an array to capture multiple relationships, e.g. a framework with multiple call-offs.

Please indicate support or opposition for these proposals using the +1 / -1 buttons or a comment. If opposing the proposal, please give clear justifications, and where possible, make an alternative proposals.

@duncandewhurst
Copy link
Contributor

Framework agreements were discussed on today's community call.

Eliza Niewiadomska from the European Bank for Reconstruction & Development directed us to the UNCITRAL Model Law on Public Procurement (2011) which gives the following definition of framework agreements:

"Framework agreement procedure” means a procedure conducted in two stages: a first stage to select a supplier (or suppliers) or a contractor (or contractors) to be a party (or parties) to a framework agreement with a procuring entity, and a second stage to award a procurement contract under the framework agreement to a supplier or contractor party to the framework agreement:

  1. “Framework agreement” means an agreement between the procuring entity and the selected supplier (or suppliers) or contractor (or contractors) concluded upon completion of the first stage of the framework agreement procedure;
  2. “Closed framework agreement” means a framework agreement to which no supplier or contractor that is not initially a party to the framework agreement may subsequently become a party;
  3. “Open framework agreement” means a framework agreement to which a supplier (or suppliers) or a contractor (or contractors) in addition to the initial parties may subsequently become a party or parties;
  4. “Framework agreement procedure with second-stage competition” means a procedure under an open framework agreement or a closed framework agreement with more than one supplier or contractor in which certain terms and conditions of the procurement that cannot be established with sufficient precision when the framework agreement is concluded are to be established or refined through a second-stage competition;
  5. “Framework agreement procedure without second-stage competition” means a procedure under a closed framework agreement in which all terms and conditions of the procurement are established when the framework agreement is concluded;

We discussed what determines whether a framework agreement has direct awards and competitive call-offs which can depend on a threshold for procurement value defined either in trade agreements, national legislation or the discretion of the procuring entity.

We also discussed whether there is a single buyer for both the selection of suppliers for the framework and the direct awards or competitive call-offs resulting from the framework - in some jurisdictions (e.g. France) there is a single buyer but in other jurisdictions and depending government tooling and payment mechanisms there may be different buyers for each call-off.

We should also consider how lots and frameworks will interact in OCDS.

Finally Angelos Hatzikyriacos from European Dynamics raised the question of whether catalogue buying can be modelled in OCDS which we will investigate further alongside the broader question of whether purchase orders are within the scope of OCDS.

@duncandewhurst
Copy link
Contributor

We gathered some useful feedback on frameworks terminology at Open Contracting Day at IODC:

  • Rose Gill Hearn from Bloomberg Associates highlighted that in the US call-offs are known as drawdowns
  • @JachymHercher and @myroslav confirmed that in the EU (and Ukraine specifically) the framework is known as an agreement whilst call-offs are known as contracts

We also heard about the UK government's G Cloud framework which can involve an additional security assessment process for certain buyers/services.

@duncandewhurst
Copy link
Contributor

The Chartered Institute of Procurement and Supply (CIPS) knowledge summary on framework arrangements gives a useful overview of this area

@JachymHercher
Copy link
Contributor

The CIPS note seems to be a bit out of date, see e.g. "(Note: The new consolidated Public Procurement Directive (currently - June 2003 - in its final stages in Brussels) does for the first time explicitly address the issue of framework agreements."

@duncandewhurst
Copy link
Contributor

@JachymHercher well spotted - thank you

@duncandewhurst
Copy link
Contributor

We should consider whether the approach to modelling qualification processes in the PPP extension could be reused for any types of framework agreement.

@jpmckinney
Copy link
Member

Page resolving this issue is readable at http://standard.open-contracting.org/latest/en/implementation/related_processes/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Documentation Includes corrections, clarifications, new guidance, and UI/UX issues
Projects
None yet
Development

No branches or pull requests

4 participants