How does the OCDS work?¶
The Open Contracting Data Standards (OCDS) is designed to support publishing data about contracting processes. This page will:
Show how a contracting process is represented using the OCDS
Introduce the OCDS schema
Describe the formats for publishing OCDS data
The OCDS defines a unique contracting process as all the actions aimed at implementing one or more contracts. An individual contracting process has several different stages: tendering, awarding, contracting and implementation. The OCDS describes a way to model and publish data in a standardized way along entire public contracting processes.
Details of award
Completion or Termination info
The OCDS brings together the data published at each stage using a single open contracting process identifier: the OCID. An OCID is composed of a prefix, registered by the publisher with OCP, and a unique process identifier chosen by the publisher.
The OCID helps users to join up data across the whole contracting process – a key feature and benefit of publishing and using OCDS data.
In designing the OCDS, we explored a range of different user needs and use cases for data about public contracting. Each use case has different data needs in terms of data fields, documents, publication frequency, and data quality. The OCDS provides a common framework to maximize the number of user needs that can be met through data and document disclosure.
When mapping your data to the OCDS or when using OCDS data, you will encounter a number of common data fields and structures, which are described by the schema:
release metadata - contextual information about each release of data;
parties - information about the organizations and participants in the contracting process;
planning - information about the goals, budgets and projects a contracting process relates to;
tender - information about how a tender will take place, or has taken place;
awards - information on awards made as part of a contracting process;
contract - information on contracts signed as part of a contracting process;
implementation - information on the progress of each contract towards completion.
Some schema fields refer to codelists, to limit and standardize the possible values of the fields, in order to promote data interoperability.
In addition to the default format of JSON, you can convert and publish your OCDS data as Excel and CSV (comma-separated values) files.
Publication formats: JSON and Excel/CSV
While the OCDS schema is described using JSON Schema, OCDS data can be converted from its JSON format to tabular formats such as CSV files or spreadsheets. JSON is favored by developers because it uses human-readable text to exchange complex information, such as nested objects. It can contain large volumes of information and is particularly good at handling one-to-many relationships (such as multiple bids per tender notice).
Tabular formats, such as CSV (or comma separated values) are commonly used in spreadsheets applications and other analysis tools. Many people are comfortable working with spreadsheets using tools like Excel. While JSON is the default format, a good publication will publish tabular formats as well both so that more users’ needs can be satisfied.
No matter what type of contracting data you are working with or format you publish in, following OCDS rules and guidance will help you and your users to:
Access clear definitions for the meaning, structure and format of your data
Access a growing ecosystem of reusable tools and methodologies for working with OCDS data
Compare your data with other publishers’ data to examine value for money and other types of analysis
Check the structure, format and quality of your data against the OCDS schema
To learn more, go to the next page in the Primer: How is OCDS data published? You can also review the further resources below to go deeper into the subjects introduced on this page.