ocp-logo-only

Open Contracting

Data Standard

v1.1
  • Getting Started
  • Guidance
    • Design
    • Map
      • Involve the right people
      • Identify your data sources
      • Map your data to OCDS
        • Localizing OCDS
        • Mapping organization identifiers
        • Working in parallel
        • Splitting up the work
        • Mapping the hard cases
          • Amendments
          • Awards, contracts, buyers and suppliers
          • Milestones
          • Organization classifications
          • Organization identifiers
          • Personal Identifiers
          • Organization references
          • Organizational Units
          • Pre-qualification and pre-selection
          • Frameworks and related processes
          • Unsuccessful tenders
      • Extensions
      • Wrapping up
    • Build
    • Publish
  • Reference
  • Getting Help
  • History
  • Governance
  • Data Review Tool

Developed by

Open Contracting Partnership
Open Contracting Data Standard v1.1
  • Docs »
  • Guidance »
  • Map »
  • Frameworks and related processes
  • View page source

Frameworks and related processes¶

OCDS defines a contracting process as:

All the planning, tendering information, awards, contracts and contract implementation information related to a single initiation process.

A contracting process brings together, under a single identifier, the information that users need to answer questions such as:

  • Was a contract signed as a result of this tender?

  • What was the total value of spending that resulted from this award?

  • Was a renewal of this contract signed?

In some cases, complex contracting processes cannot be represented under a single identifier because:

  • There are multiple initiation stages: for example, when a framework is setup, and then mini-competitions are used for purchases from the framework;

  • The procurement systems through which stages of the process are managed by different bodies, and are not integrated;

There are also cases when users want to know about related, but separate, contracting processes - such as the tender for renewal of a contract, or sub-contracting processes.

The relatedProcess block can be used in these cases to link together multiple contracting processes.

Framework types¶

The table below provides a number of examples of when to use related process, and when to keep information within a single contracting process.

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.

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.

Dynamic Purchasing System

Multiple contracting processes: One process using awards to represent suppliers joining the DPS. tender/status is '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.

Next Previous

Copyright (c) Open Contracting Partnership, and released under the Apache License 2.0, source available on GitHub. Privacy notice.