Plan

planID

string, auto-generated, read-only

The plan identifier to refer plan to in “paper” documentation.

OpenContracting Description: planID should always be the same as the OCID. It is included to make the flattened data structure more convenient.

procuringEntity

PlanOrganization, required

Organization conducting the tender.

OpenContracting Description: The entity managing the procurement, which may be different from the buyer who is paying / using the items being procured.

status

string

Possible values:
  • draft
  • scheduled
  • cancelled
  • complete

Status of the Plan.

digraph G {

    rankdir = LR

    draft [
        shape = circle
        fixedsize = true
        width = .9
        style = filled
        fillcolor = cadetblue1
    ]
    scheduled [
        shape = circle
        fixedsize = true
        width = .9
        style = filled
        fillcolor = deepskyblue1
    ]
    complete [
        shape = circle
        fixedsize = true
        width = .9
        style = filled
        fillcolor = aquamarine3
    ]
    cancelled [
        shape = circle
        fixedsize = true
        width = .9
        style = filled
        fillcolor = coral1
    ]

    draft -> scheduled
    scheduled -> complete
    scheduled -> cancelled
}

buyers

List of PlanOrganization objects, required at least 1 object

Identifications of the subjects in whose interests the purchase is made

milestones

List of PlanMilestone objects

Milestones of type approval used to provide Central procurement organization approve feature

tender

PlanTender, required

Data regarding tender process.

budget

Budget, required (except tender.procurementMethodType is “esco”).

Total available tender budget.

OpenContracting Description: The total estimated value of the procurement.

classification

Classification, required

OpenContracting Description: The primary classification for the item. See the itemClassificationScheme to identify preferred classification lists, including CPV and GSIN.

It is mandatory for classification.scheme to be CPV or ДК021. The classification.id should be valid CPV or ДК021 code.

additionalClassifications

List of Classification objects

OpenContracting Description: An array of additional classifications for the item. See the itemClassificationScheme codelist for common options to use in OCDS. This may also be used to present codes from an internal classification scheme.

Item wich classification.id starts with 336 and contains additionalClassification objects have to contain no more than one additionalClassifications with scheme=INN.

Item with classification.id=33600000-6 have to contain exactly one additionalClassifications with scheme=INN.

It is mandatory to have at least one item with ДКПП as scheme.

documents

List of Document objects

OpenContracting Description: All documents and attachments related to the tender.

tender_id

string, auto-generated, read-only

id of the linked tender object. See Tender creation from a procurement plan

items

list of Item objects, required

List that contains single item being procured.

OpenContracting Description: The goods and services to be purchased, broken into line items wherever possible. Items should not be duplicated, but a quantity of 2 specified instead.

cancellation

milestones

List of PlanMilestone objects

dateModified

string, Date, auto-generated

datePublished

string, Date, auto-generated

owner

string, auto-generated

revisions

List of Revision objects, auto-generated

Historical changes to Tender object properties.


PlanTender

procurementMethod

string

Possible values:
  • ‘’
  • ‘open’
  • ‘limited’

Procurement Method of the Tender.

procurementMethodType

string Possible values for procurementMethod == ‘’:

  • ‘’ - Without using an electronic system
  • ‘centralizedProcurement’ - Procurement via Central Purchasing Body

Possible values for procurementMethod == ‘open’:

  • belowThreshold
  • aboveThresholdUA
  • aboveThresholdEU
  • aboveThresholdUA.defense
  • esco
  • closeFrameworkAgreementUA
  • competitiveDialogueEU
  • competitiveDialogueUA

Possible values for procurementMethod == ‘limited’:

  • reporting
  • negotiation
  • negotiation.quick

tenderPeriod

Period, required

Period when bids can be submitted. At least endDate has to be provided.

OpenContracting Description: The period when the tender is open for submissions. The end date is the closing date for tender submissions.


Budget

id

string, required

description

string, multilingual, required

amount

float, required

amountNet

float, required

currency

string, required, length = 3

project

year

integer, >=2000, deprecated in favor of period

notes

string

breakdown

List of BudgetBreakdown, required (except tender.procurementMethodType is “belowThreshold”, “reporting”, “esco”, “”)

Project

id

string, required

name

string, multilingual, required

BudgetPeriod

startDate

string, required, Date

OpenContracting Description: The start date for the period.

endDate

string, required, Date

OpenContracting Description: The end date for the period.

startDate should always precede endDate.

BudgetBreakdown

id:

uid, auto-generated

title:

string, required

Possible values are:

  • state
  • crimea
  • local
  • own
  • fund
  • loan
  • other
description:

string, multilingual, required if title == other

Detailed description of budget breakdown.

value:

Guarantee

Budget breakdown value

Currency should be identical for all budget breakdown values and budget

Sum of the breakdown values amounts can’t be greater than budget amount (except tender.procurementMethodType is “esco”)