Documentation

Planning processes can relate to different types of projects, including:

This extension adds a planning.project object to describe the infrastructure or public-private partnership (PPP) project to which a planning process is related. The identifier of the project ought to be disclosed in planning.project.id.

The planning.budget.projectID field ought to not be used to disclose the identifier of an infrastructure or PPP project. Rather, this field is used to disclose the identifier of a programme of work as it appears in a budget, like a national or state budget. Since such programmes of work can include many infrastructure projects, it is necessary to disclose their identifiers separately.

This extension must be used with the Location extension.

Example

A buyer announces a planning process for the design of a bridge.

This planning process is part of an infrastructure project, which covers the design, construction and supervision of the bridge. Information about the infrastructure project is disclosed in the planning.project object. For example, the planning.project.sector field describes the project's sector, using the OC4IDS projectSector codelist.

A separate OC4IDS dataset describes infrastructure projects in greater detail. In the planning process, planning.project.id and planning.project.uri reference the project's identifier and URI in that OC4IDS dataset.

The planning process and infrastructure project are funded through a programme of work to upgrade the nation's highways. The name and identifier of the programme of work as it appears in the national budget are disclosed in the budget.project and budget.projectID fields.

Note: Planning processes related to public-private partnership projects are modelled in the same way. Information about the PPP project is disclosed in planning.project, not planning.budget.project or planning.budget.projectID.

{
  "ocid": "ocds-213czf-0000",
  "id": "1",
  "date": "2024-01-01T00:00:00Z",
  "tag": [
    "planning"
  ],
  "planning": {
    "project": {
      "id": "oc4ids-bu3kcz-0000",
      "title": "State Highway 1 Clutha River Bridge",
      "description": "Design, construction and supervision of a new bridge crossing for State Highway 1 over the Clutha River.",
      "totalValue": {
        "amount": 113000000,
        "currency": "NZD"
      },
      "uri": "http://example.com/projects/oc4ids-bu3kcz-0000.json",
      "sector": {
        "id": "transport.road",
        "description": "Road transport, including roads, highways, streets, tunnels and bridges.",
        "scheme": "oc4idsProjectSector"
      },
      "additionalClassifications": [
        {
          "id": "03.04.05",
          "description": "Bridges for road transport.",
          "scheme": "My local scheme"
        }
      ],
      "locations": [
        {
          "description": "Balclutha, Otago",
          "geometry": {
            "type": "Point",
            "coordinates": [
              169.745,
              -46.2359
            ]
          }
        }
      ]
    },
    "budget": {
      "project": "National Highway Upgrade",
      "projectID": "001-001-002"
    }
  },
  "tender": {
    "id": "1",
    "title": "Bridge design"
  }
}

Changelog

2024-03-28

2021-04-15

  • Add infrastructure project example.

2020-04-24

  • Add minProperties, minItems and/or minLength properties.

2020-04-16

  • Remove guidance related to the planning.budget object. See #701.

2018-05-03

  • Add additional guidance on the use of OCDS fields in the context of this extension.

2017-12-29

  • Remove the repetition of OCDS fields in this extension.

2017-07-08

  • Add multilingual support for Project.title fields.
  • Remove multilingual support for non-existent Project.source and Project.project fields.
  • Restore Budget.project and Budget.projectID fields.
  • Remove obsolete mergeStrategy properties.

Issues

Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.