Sustainability modules

This page documents a mapping from the elements in the CoST IDS sustainability modules to OC4IDS fields and codes.

The mapping for each element covers only the fields needed to satisfy the specific data needs described in the CoST IDS. In order for your data to meet the widest range of user needs, when implementing the mapping, you are encouraged to consider collecting and publishing the other fields described in the OC4IDS schema. To view a field's details, click on its name, e.g. id.

Download this page in PDF format

In Google Chrome, Microsoft Edge or Mozilla Firefox, open the Print dialog (Ctrl+P) and set Destination (Printer, in Microsoft Edge) to 'Save to PDF'. In Safari, open the File menu and click Export as PDF.

Economic and fiscal

CoST IDS element

Procurement strategy

Disclose the procurement strategy risk assessment. This tends to be part of the decision-making strategy and likely includes discussions regarding capabilities, the delivery model and the rationale for the risk allocation decision. (E.g. [Document]).

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'procurementStrategyRiskAssessment'.

{
  "documents": [
    {
      "id": "1",
      "title": "Procurement strategy risk assessment",
      "documentType": "procurementStrategyRiskAssessment",
      "url": "http://example.com/documents/procurementStrategyRiskAssessment.pdf"
    }
  ]
}

CoST IDS element

Life cycle cost

Disclose the life cycle cost of the project, which is the cost of an asset throughout its life cycle while fulfilling the performance requirements (ISO 15686-5:2017) (E.g. [value]).

OC4IDS mapping

Project Level:

Add a CostMeasurement object to the costMeasurements array and map to its .lifeCycleCosting.value.

{
  "costMeasurements": [
    {
      "id": "1",
      "lifeCycleCosting": {
        "value": {
          "amount": 10000000,
          "currency": "USD"
        }
      }
    }
  ]
}

CoST IDS element

Life cycle cost calculation methodology

Disclose the methodology used to calculate the life-cycle cost. The methodology ought to specify whether income and externalities are included in the calculation and the common date, discount rate and period of analysis used.

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'lifeCycleCostMethodology'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "lifeCycleCostMethodology",
      "url": "http://example.com/documents/lifeCycleCostMethodology.pdf"
    }
  ]
}

CoST IDS element

Funding source for preparation, implementation and operation

Name the funding organization(s)/sources of funding for Preparation, Implementation and Operation. If the information is not available for any of the stages, select ['funding/budget source not specified'] for the respective stage where the nature of the funding/budget source could not be identified.

OC4IDS mapping

Project level:

  1. Get the BudgetBreakdowns object in the budget.budgetBreakdowns array whose .description is "Breakdown by stage". If none exists yet, add a BudgetBreakdowns object to the budget.budgetBreakdowns array, set its .id incrementally and its .description to "Breakdown by stage".

  2. For each stage:

    a. Get the BudgetBreakdown object in the budget breakdowns' .budgetBreakdown array whose .description is the name of the stage. If none exists yet, add a BudgetBreakdown object to the budget breakdowns' .budgetBreakdown array, set its .id incrementally and set its .description to the name of the stage.

    b. Get the Organization object in parties that represents the funding source. If none exists yet, add an organization and add 'funder' to its .roles.

    c. Set the budget breakdown's .sourceParty to the .id and .name of the funding source.

{
  "budget": {
    "budgetBreakdowns": [
      {
        "id": "1",
        "description": "Breakdown by stage",
        "budgetBreakdown": [
          {
            "id": "1",
            "description": "Preparation",
            "sourceParty": {
              "id": "1",
              "name": "Agency for Agricultural Development of Morocco"
            }
          },
          {
            "id": "2",
            "description": "Implementation",
            "sourceParty": {
              "id": "1",
              "name": "Agency for Agricultural Development of Morocco"
            }
          }
        ]
      }
    ]
  },
  "parties": [
    {
      "id": "1",
      "name": "Agency for Agricultural Development of Morocco",
      "roles": [
        "funder"
      ]
    }
  ]
}

CoST IDS element

Budget for preparation, implementation and operation

Specify the allocated budget for preparation, implementation, operation. If no amount is allocated for each of the stages, select the option 'amount not allocated" (E.g. Preparation [currency and amount], Implementation[currency and amount], Operation [currency and amount]

OC4IDS mapping

Project level:

  1. Get the BudgetBreakdowns object in the budget.budgetBreakdowns array whose .description is "Breakdown by stage". If none exists yet, add a BudgetBreakdowns object to the budget.budgetBreakdowns array, set its .id incrementally and its .description to "Breakdown by stage".

  2. For each stage:

    a. Get the BudgetBreakdown object in the budget breakdowns' .budgetBreakdown array whose .description is the name of the stage. If none exists yet, add a BudgetBreakdown object to the budget breakdowns' .budgetBreakdown array, set its .id incrementally and set its .description to the name of the stage.

    b. Map to the budget breakdown's .amount.

{
  "budget": {
    "budgetBreakdowns": [
      {
        "id": "1",
        "description": "Breakdown by stage",
        "budgetBreakdown": [
          {
            "id": "1",
            "description": "Preparation",
            "amount": {
              "amount": 350000,
              "currency": "USD"
            }
          },
          {
            "id": "2",
            "description": "Implementation",
            "amount": {
              "amount": 300000,
              "currency": "USD"
            }
          }
        ]
      }
    ]
  }
}

CoST IDS element

Cost benefit analysis

Disclose the project cost-benefit analysis. This information tends to be part of the appraisal documents. (E.g. [Document]).

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'costBenefitAnalysis'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "costBenefitAnalysis",
      "url": "http://example.com/documents/costBenefitAnalysis.pdf"
    }
  ]
}

CoST IDS element

Value for money

A summary of the value for money analysis carried out for the project, along with supporting figures, calculations and business case, based on projected or actual procurement outcomes. This tends to include considerations of economy, efficiency, effectiveness and equity, and is part of the appraisal documents. (E.g. [Document]).

OC4IDS mapping

Project Level: Add a project document and set its .documentType to 'valueForMoneyAnalysis'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "valueForMoneyAnalysis",
      "url": "http://example.com/documents/valueForMoneyAnalysis.pdf"
    }
  ]
}

CoST IDS element

Budget projections

In case of multiyear project implementation, disclose information on budget projection for all years of implementation (E.g. Y1: [currency and amount], Y2: [currency and amount], etc).

OC4IDS mapping

Project level:

  1. Add a BudgetBreakdowns object to the budget.budgetBreakdowns array, set its .id incrementally and set its .description to "Breakdown by year of implementation".

  2. For each year:

    1. Add a BudgetBreakdown object to the budget breakdowns' .budgetBreakdown array and set its .id incrementally.

    2. Map the year's start and end dates to its .period

    3. Map the budget projection to its .amount.

{
  "budget": {
    "budgetBreakdowns": [
      {
        "id": "1",
        "description": "Breakdown by year of implementation",
        "budgetBreakdown": [
          {
            "id": "1",
            "period": {
              "startDate": "2024-01-01T00:00:00Z",
              "endDate": "2024-12-31T00:00:00Z"
            },
            "amount": {
              "amount": 350000,
              "currency": "USD"
            }
          },
          {
            "id": "2",
            "period": {
              "startDate": "2025-01-01T00:00:00Z",
              "endDate": "2025-12-31T00:00:00Z"
            },
            "amount": {
              "amount": 300000,
              "currency": "USD"
            }
          }
        ]
      }
    ]
  }
}

CoST IDS element

Budget shortfall

Disclose any shortfall in the allocated budget (E.g. [currency and amount] and [free text: reasons for the funding shortfall]

OC4IDS mapping

Project level:

  1. Add a Metric object to the metrics array, set its .id incrementally and set its .title to "Budget shortfall".

  2. Add an Observation object to the metric's .observations array and set its .id incrementally.

  3. Map the shortfall's value to its .value.

  4. Map the reasons for the shortfall to its .notes.

{
  "metrics": [
    {
      "id": "1",
      "title": "Budget shortfall",
      "observations": [
        {
          "id": "1",
          "value": {
            "amount": 2500000,
            "currency": "USD"
          },
          "notes": "Funding shortfall due to construction overruns and a lack of budgetary approval"
        }
      ]
    }
  ]
}

Environment and climate

CoST IDS element

Environmental impact category

Indicate the category that reflects the magnitude of environmental impact. Consider the following to rate the project:

  • Category A: projects with potential significant adverse environmental or social risks and/or impacts that are diverse, irreversible, or unprecedented.

  • Category B: projects with potential limited adverse environmental or social risks and/or impacts that are few in number, generally site-specific, largely reversible, and readily addressed through mitigation measures.

  • Category C: projects with minimal or no adverse environmental or social risks and/or impacts.

(Select from a list: A/B/C - Specify list as IFC's Environmental and Social Categorization).

OC4IDS mapping

Project level:

If an environmental impact assessment was conducted:

  1. Set environment.hasImpactAssessment to true.

  2. Add a Classification object to the environment.impactCategories array, set its .scheme to 'ifc-environmental-social' and set its .id to the lowercase letter of the category into which the project falls.

If an environmental impact assessment was not conducted, set environment.hasImpactAssessment to false.

{
  "environment": {
    "hasImpactAssessment": true,
    "impactCategories": [
      {
        "scheme": "ifc-environmental-social",
        "id": "a"
      }
    ]
  }
}

CoST IDS element

Environmental measures

Disclose the measures adopted by the project to mitigate and/or remedy the environmental impact (E.g. [free text justification/explaining the measures adopted] and document).

OC4IDS mapping

Project level:

Add a project document, set its .documentType to 'environmentalMeasures' and map the justification and explanation to its .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "environmentalMeasures",
      "description": "The following environmental measures are adopted by the project...",
      "url": "http://example.com/documents/environmentalMeasures.pdf"
    }
  ]
}

CoST IDS element

Environmental exceptions

Disclose all exemptions and/or amnesties obtained for the project. (E.g. [Document]). This can be planning, environmental, construction and/or operational related.

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'environmentalExemption'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "environmentalExemption",
      "url": "http://example.com/documents/environmentalExemption.pdf"
    }
  ]
}

CoST IDS element

Protected area

Identify whether the project is located in a protected area. Use the project location/coordinates at the WDPA - World Database of Protected Areas to disclose the information.

OC4IDS mapping

Project level:

If the project is located in a protected area:

  1. Set environment.inProtectedArea to true.

  2. Add a Location object to the .locations array, set its .id incrementally and set its .gazetteer.scheme to 'WDPA'.

  3. For each protected area in which the project is located, add the area's WDPA identifier to the .gazetteer.identifiers array.

If the project is not located in a protected area, set environment.inProtectedArea to false.

{
  "environment": {
    "inProtectedArea": true
  },
  "locations": [
    {
      "id": "1",
      "gazetteer": {
        "scheme": "WDPA",
        "identifiers": [
          "555566673"
        ]
      }
    }
  ]
}

CoST IDS element

Conservation measures

Disclose and provide further details on the measures adopted by the project to protect and enhance biodiversity. This can comprise, without limitation the following:

  • avoidance of ecological sitting

  • buffers for ecological land

  • nature-based solutions

  • land restoration

  • protection to landscape and historical sites

  • invasive species management

  • management of wildlife mortality risk

  • reduce habitat loss

  • pollution reduction

  • soil management

  • hazardous material management])

  • others (explain)

OC4IDS mapping

Project level:

  1. For each measure, add a ConservationMeasure object to the environment.conservationMeasures array, set its .type according to the open conservationMeasure codelist and map any further details to its .description.

  2. If there is an accompanying document, add a project document and set its .documentType to 'conservationMeasures'.

{
  "environment": {
    "conservationMeasures": [
      {
        "type": "habitatRestoration",
        "description": "Habitat restoration measures for the project include..."
      }
    ]
  },
  "documents": [
    {
      "id": "1",
      "documentType": "conservationMeasures",
      "url": "http://example.com/conservationMeasures.pdf"
    }
  ]
}

CoST IDS element

Climate and disaster risk assessment

Clarify the type of climate and disaster risks to which the project is exposed to (E.g. [document or free text to list and explain risks]). This tends to be part of the appraisal documents.

OC4IDS mapping

Project level:

Add a project document, set its .documentType to 'climateAndDisasterRiskAssessment' and map any free text to its .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "climateAndDisasterRiskAssessment",
      "description": "The project is exposed to the following climate and disaster risks...",
      "url": "http://example.com/documents/climateAndDisasterRiskAssessment.pdf"
    }
  ]
}

CoST IDS element

Climate measures

Clarify whether the project design considered climate change mitigation and/or adaptation measures,. disclosing the design demonstrating how the measures were incorporated. This can comprise, without limitation the following:

use of lower-emission sources of energy use of lower-emission materials use of recycled and reused materials regenerative design retrofitting design use of carbon capture technology assessment of extreme weather events assessment of precipitation patterns assessment of rising temperatures assessment of rising sea levels others (explain)

And [Document]).

OC4IDS mapping

Project level:

  1. For each measure, add a ClimateMeasure object to the environment.climateMeasures array, set its .type according to the open climateMeasures codelist and map any further explanation to its .description.

  2. If there is an accompanying document, add a project document and set its .documentType to 'climateMeasures'.

{
  "environment": {
    "climateMeasures": [
      {
        "type": [
          "regenerativeDesign"
        ],
        "description": "Regenerative design measures for the project include biomimicry to imitate nature."
      }
    ]
  },
  "documents": [
    {
      "id": "1",
      "documentType": "climateMeasures",
      "url": "http://example.com/climateMeasures.pdf"
    }
  ]
}

CoST IDS element

Forecast of greenhouse gas emissions

Disclose the forecast greenhouse gas emissions related to the project, informing the calculation, the methodology applied and where the calculation can be found (E.g. [amount] and [free text for methodology clarification]).

OC4IDS mapping

Project level:

  1. Add a Metric object to the .forecasts array.

  2. Set the metric's .title to "Greenhouse gas emissions (carbon dioxide equivalent)" and map the methodology clarification to its .description.

  3. Add an Observation object to the metric's .observations array and:

  • Map the amount of greenhouse gas emissions in tonnes of CO2 equivalent to the observation's .measure

  • Set the .unit.name to "Tonne (metric ton)", .unit.scheme to 'UNCEFACT' and .unit.id to "TNE"

  • Set .period to the period covered by the forecast.

  1. If supporting documentation is available, add a project document and set its .documentType to 'ghgEmissionsForecast'.

{
  "forecasts": [
    {
      "id": "1",
      "title": "Greenhouse gas emissions (carbon dioxide equivalent)",
      "description": "Emission forecasts are calculated using the following methodology...",
      "observations": [
        {
          "id": "1",
          "period": {
            "startDate": "2024-01-01T00:00:00Z",
            "endDate": "2049-12-31T00:00:00Z"
          },
          "measure": 1000000,
          "unit": {
            "name": "Tonne (metric ton)",
            "scheme": "UNCEFACT",
            "id": "TNE"
          }
        }
      ]
    }
  ],
  "documents": [
    {
      "id": "1",
      "documentType": "ghgEmissionsForecast",
      "url": "http://example.com/GhgEmissionForecast.pdf"
    }
  ]
}

CoST IDS element

Environmental certifications

Disclose environmental and/or climate related certifications issued for contractors and subcontractors such as ISO 14001 for environmental management (E.g. [Document]).

OC4IDS mapping

Contracting process level:

Add a contracting process document and set its .documentType to 'supplierEnvironmentalCertification'.

{
  "contractingProcesses": [
    {
      "id": "1",
      "summary": {
        "documents": [
          {
            "id": "1",
            "documentType": "supplierEnvironmentalCertification",
            "url": "http://example.com/documents/contractorEnvironmentalCertification.pdf"
          }
        ]
      }
    }
  ]
}

CoST IDS element

Decommissioning plans

Disclose the decommissioning plans for the project assets [document]..

OC4IDS mapping

Project level:

Add a project document and set its .documentType to 'decommissioningPlans'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "decommissioningPlans",
      "url": "http://example.com/documents/decommissioningPlans.pdf"
    }
  ]
}

CoST IDS element

Decommissioning cost forecast

Disclose the forecast decommissioning costs for the project assets [value, currency].

OC4IDS mapping

Project level:

  1. Add a CostMeasurement object to the costMeasurements array and set its .id incrementally.

  2. Add a CostGroup object to the cost measurement's .costGroups array, set its .id incrementally and set its .category to 'endOfLife'.

  3. Add a Cost object to the cost group's .costs array, set its .id incrementally and map to its .value.

{
  "costMeasurements": [
    {
      "id": "1",
      "costGroups": [
        {
          "id": "1",
          "category": "endOfLife",
          "costs": [
            {
              "id": "1",
              "value": {
                "amount": 50000000,
                "currency": "USD"
              }
            }
          ]
        }
      ]
    }
  ]
}

Climate finance

CoST IDS element

Climate objective

Disclose the main climate objective that the project addresses.

Select from a list: Eg:

  • mitigation

  • adaptation

  • cross-cutting

OC4IDS mapping

Project level:

Map to environment.goals using the closed environmentalGoal codelist.

{
  "environment": {
    "goals": [
      "climateChangeMitigation",
      "climateChangeAdaptation"
    ]
  }
}

CoST IDS element

Financial instrument

Disclose the financial instrument type from the list:

  • loan

    • concessional

    • non-concessional

  • grant

  • equity

  • guarantees

OC4IDS mapping

  1. Get the Finance object in .udget.finance or contractingProcesses.summary.finance that represents the financing arrangement. If none exists yet, add a financing arrangement.

  2. Set the the financing arrangement's .assetClass and .type according to the instrument type:

Instrument type

.assetClass

.type

loan

'debt'

'loan'

grant

'grant'

equity

'equity'

'shares.listed' or 'shares.unlisted'

guarantee

'guarantee'

  1. If the instrument is a concessional loan, set .concessional to true.

  2. If the instrument is a non-concessional loan, set .concessional to false.

  3. If the instrument is results-based, set .resultsBased to true.

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "assetClass": [
          "debt"
        ],
        "type": "loan",
        "concessional": false,
        "resultsBased": true
      }
    ]
  }
}

CoST IDS element

Climate transformation

Clarify the theory of change, systemic transition or transformation that is intended [free text to explain].

OC4IDS mapping

Project level:

Add a project document, set its .documentType to 'climateTransformation' and map any free text to .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "climateTransformation",
      "url": "http://example.com/climateTransformation.pdf"
    }
  ]
}

CoST IDS element

Climate finance decision-maker

Identify who approved the climate finance investment in the country (organization, party, role)

OC4IDS mapping

Project level:

Add an organization for the decision maker and add 'climateFinanceFocalPoint' to its .roles array.

{
  "parties": [
    {
      "id": "1",
      "name": "Presidential Climate Commission",
      "roles": [
        "climateFinanceFocalPoint"
      ]
    }
  ]
}

CoST IDS element

Nationally Determined Contributions (NDC)

Clarify how the investment is aligned with the country's nationally determined contributions. [codelist, free text to explain].

CoST IDS element

Paris Agreement

Clarify how the investment is aligned with the country's Paris Agreement commitments. [codelist, free text to explain].

CoST IDS element

Beneficiaries

Disclose who is the climate finance investment intended to benefit [free text to explain the beneficiaries] and number of beneficiaries. [Select from the list: Direct Indirect]

CoST IDS element

Amount of investment

Disclose the quantum of the climate finance investment [value, currency].

OC4IDS mapping

  1. Get the Finance object in budget.finance or contractingProcesses.summary.finance that represents the financing arrangement. If none exists yet, add a financing arrangement.

  2. Map to the financing arrangement's .value.

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "value": {
          "amount": 3000000,
          "currency": "EUR"
        }
      }
    ]
  }
}

CoST IDS element

Funding source

Disclose who is providing the finance [party/organization/role].

OC4IDS mapping

  1. Get the Finance object in budget.finance or contractingProcesses.summary.finance that represents the financing arrangement. If none exists yet, add a financing arrangement.

  2. Map to the financing arrangement's .source.

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "source": "Green Climate Fund"
      }
    ]
  }
}

CoST IDS element

Green Climate Fund Accredited Entity

For projects financed by the Green Climate Fund, disclose the accredited entities through which GCF resources are accessed.

OC4IDS mapping

  1. Get the Finance object in budget.finance or contractingProcesses.summary.finance that represents the financing arrangement. If none exists yet, add a financing arrangement.

  2. Get the Organization object in parties that represents the party providing the finance. If none exists yet, add an organization and add 'funder' to its .roles.

  3. Set the financing arrangement's .financingParty to the .id and .name of the organization.

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "financingParty": {
          "id": "1",
          "name": "Agency for Agricultural Development of Morocco"
        }
      }
    ]
  },
  "parties": [
    {
      "id": "1",
      "name": "Agency for Agricultural Development of Morocco",
      "roles": [
        "funder"
      ]
    }
  ]
}

CoST IDS element

Accredited Entity Type

Select from the lists:

  • Private

  • Public

  • non-governmental

  • sub-national

  • national

  • regional

  • international

OC4IDS mapping

  1. Get the Organization object in parties that represents the accredited entity. If none exists yet, add an organization and add 'funder' to its .roles.

  2. Add a Classification object to the organization's .classifications array, set its .scheme to 'costIdsLegalType' and map the organization's legal type ('private', 'public' or 'non-government') to its .id.

  3. Add a Classification object to the organization's .classifications array, set its .scheme to 'costIdsAdministrativeLevel' and map the organization's administrative level ('international', 'regional', 'national' or 'sub-national') to its .id.

{
  "parties": [
    {
      "id": "1",
      "name": "Development Bank of South Africa",
      "roles": [
        "funder"
      ],
      "classifications": [
        {
          "id": "public",
          "scheme": "costIdsLegalType"
        },
        {
          "id": "national",
          "scheme": "costIdsAdministrativeLevel"
        }
      ]
    }
  ]
}

CoST IDS element

Project preparation costs

Disclose the amounts invested in project preparation [value, currency].

CoST IDS element

Project preparation period

Disclose dates for project preparation [start date, end date].

OC4IDS mapping

Project level:

Map to preparationPeriod.

{
  "preparationPeriod": {
    "startDate": "2016-07-01T00:00:00Z",
    "endDate": "2016-12-31T00:00:00Z"
  }
}

CoST IDS element

Project approval period

Disclose dates for project approval [submission date, approval date].

OC4IDS mapping

Project level:

For each date:

  1. Add a Milestone to the milestones array and set its:

  1. If disclosing the submission date, set the milestone's .title to "Climate finance submission" and its .dateMet to the date of the submission.

  2. If disclosing the approval date, set the milestone's .title to "Climate finance approval" and its .dateMet to the date of the approval.

{
  "milestones": [
    {
      "id": "1",
      "title": "Climate finance submission",
      "type": "financing",
      "dateMet": "2023-06-01T00:00:00Z",
      "status": "met"
    }
  ]
}

CoST IDS element

Ratio of co-finance

Disclose the ratio of co-finance. Select from a list to specify amounts.

Eg:
Domestic mobilisations [value or NA] Private Finance [value or NA]

OC4IDS mapping

The OC4IDS data model provides the information needed to calculate co-finance ratios by modeling a project's individual financing arrangements. For more information, see the mappings for amount of investment, funding source, Green Climate Fund Accredited Entity and Accredited Entity Type.

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "source": "Green Climate Fund",
        "value": {
          "amount": 3000000,
          "currency": "USD"
        }
      },
      {
        "id": "2",
        "source": "GEF Trust Fund",
        "value": {
          "amount": 150000,
          "currency": "USD"
        }
      }
    ]
  }
}

CoST IDS element

Terms of climate finance

This includes several financial terms:

  • maturity (years)

  • Grace period (years)

  • annual principal repayment years (% of initial principle)

  • Interest (%)

  • Service fee (per annum)

  • Commitment fee (per annum)

OC4IDS mapping

  1. Get the Finance object in budget.finance or contractingProcesses.summary.finance that represents the financing arrangement. If none exists yet, add a financing arrangement.

  2. Map the terms to the financing arrangement's properties:

{
  "budget": {
    "finance": [
      {
        "id": "1",
        "period": {
          "startDate": "2024-01-01T00:00:00Z",
          "endDate": "2043-12-31T00:00:00Z"
        },
        "paymentPeriod": {
          "startDate": "2029-01-01T00:00:00Z",
          "endDate": "2043-12-31T00:00:00Z"
        },
        "interestRate": {
          "margin": 0.0075
        },
        "description": "Annual principal repayment years 11-20 (% of initial principal): 6.7%. Service fee (per annum): 0.50%. Commitment fee (per annum): Up to 0.75%."
      }
    ]
  }
}

CoST IDS element

Carbon efficiency

Disclose the cost per tonne of CO2 equivalent [value, currency].

OC4IDS mapping

Project level:

Map to environment.abatementCost. If a document that describes the methodology used to calculate the cost is available, add a project document and set its .documentType to 'abatementCostMethodology'.

{
  "environment": {
    "abatementCost": {
      "amount": 12.29,
      "currency": "USD"
    }
  },
  "documents": [
    {
      "id": "1",
      "documentType": "abatementCostMethodology",
      "url": "http://example.com/abatementCostMethodology.pdf"
    }
  ]
}

CoST IDS element

Non-climate co-benefits

Identify potential non-climate impacts that have been factored into the project planning. Select from the list:

  • economic

  • social

  • environmental

  • gender empowerment

[add free text to explain the co-benefits].

OC4IDS mapping

Project level:

For each co-benefit, add a Benefit object to the benefits array, map the option from the list to its .title and map the explanation to its .description.

{
  "benefits": [
    {
      "title": "environmental",
      "description": "The new water management plant will mean less water is removed from the delta meaning more is left in place for use by the local biome."
    }
  ]
}

CoST IDS element

Public consultation meetings

Disclose the occurrence of public meetings with communities and impacted groups including the minutes, number of the participants, dates and location of these meetings (E.g. Meeting 1 [date] [location] [number of participants] [Document], Meeting 2 [date] [location] [number of participants], [Document]).

CoST IDS element

Disbursement records

Disbursements dates according to financial agreement versus actual disbursements dates [value, currency, date].

OC4IDS mapping

For each planned disbursement:

  1. If the disbursement relates to a contracting processes, for example a payment from a funder to a supplier or to a subcontractor of a supplier, get the ContractingProcess in the contractingProcesses array to which the disbursement relates and add a Milestone object to its .summary.milestones array. Otherwise, if the disbursement relates to the project, for example a payment from a funder to the public authority, add a Milestone object to the project-level milestones array.

  2. Set the milestone's:

  • .id incrementally

  • .status to 'scheduled'

  • .dueDate to the date on which the disbursement is planned to occur

  • .type to 'payment'

  • .value to the amount and currency of the planned disbursement

For each actual disbursement:

  1. If the disbursement relates to a contracting processes, for example a payment from a funder to a supplier or to a subcontractor of a supplier, get the ContractingProcess in the contractingProcesses array to which the disbursement relates and add a Transaction object to its .summary.transactions array. Otherwise, if the disbursement relates to the project, for example a payment from a funder to the public authority, add a Transaction object to the project-level transactions array.

  2. Set the transaction's:

  • .id incrementally

  • .date to the date of the disbursement

  • .value to the amount and currency of the disbursement.

  1. Get the Organization in parties that represents the payer. If none exists yet, add an organization for the payer:

  • Add 'payer' to the organization's .roles array

  • Set the transaction's .payer to the .id and .name of the organization.

  1. Get the Organization in parties that represents the payee. If none exists yet, add an organization for the payee:

  • Add 'payee' to the organization's .roles array.

  • Set the transaction's .payee to the .id and .name of the organization.

  1. Get the Milestone in milestones that represents that planned disbursement:

{
  "milestones": [
    {
      "id": "1",
      "title": "Grant disbursement",
      "status": "met",
      "dueDate": "2023-07-01T00:00:00Z",
      "dateMet": "2023-08-01T00:00:00Z",
      "type": "payment",
      "value": {
        "amount": 5000000,
        "currency": "USD"
      }
    }
  ],
  "transactions": [
    {
      "id": "1",
      "date": "2023-08-01T00:00:00Z",
      "value": {
        "amount": 5000000,
        "currency": "USD"
      },
      "payer": {
        "id": "1",
        "name": "United Nations Development Programme"
      },
      "payee": {
        "id": "2",
        "name": "Ministry of works"
      },
      "relatedImplementationMilestone": {
        "id": "1",
        "title": "Grant disbursement"
      }
    }
  ]
}

CoST IDS element

Type of project monitoring

Select from a list:

  • internal

  • external

  • mixed

OC4IDS mapping

Project level:

Map to environment.climateOversightTypes using the closed climateOversightTypes codelist.

{
  "environment": {
    "climateOversightTypes": [
      "internal",
      "external"
    ]
  }
}

CoST IDS element

Performance monitoring

Disclose Key Performance Indicators adopted by the project (E.g. [free text]).

OC4IDS mapping

Project level:

For each KPI, add a Metric object to the metrics array and set its fields according to the schema. Prefix the metric's .title with "KPI: ".

{
  "metrics": [
    {
      "id": "1",
      "title": "KPI: Capacity utilization"
    }
  ]
}

CoST IDS element

Reporting period

It could be quarterly, annually, biannually, etc. [free text].

OC4IDS mapping

Project level:

Get the Metric object in the metrics array that represents the KPI and map to its .description using the format "Reporting period: {period}".

{
  "metrics": [
    {
      "id": "1",
      "title": "KPI: Capacity utilization",
      "description": "Reporting period: Annual"
    }
  ]
}

CoST IDS element

Oversight reports

Disclose oversight reports.[document].

OC4IDS mapping

Project level:

Add a project document and set its .documentType to 'oversightReport'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "oversightReport",
      "url": "http://example.com/oversightReport"
    }
  ]
}

CoST IDS element

Independent monitoring

Identify the entities acting as independent monitors of the project (E.g. [free text]).

CoST IDS element

Independent evaluation

Disclose technical audits produced at end of the project (E.g. [free text].

OC4IDS mapping

Project level:

For each audit report, add a project document, set its .documentType to 'technicalAuditReport' and map any free text to its .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "technicalAuditReport",
      "description": "The project has been constructed as specified...",
      "url": "http://example.com/technicalAuditReport.pdf",
      "pageStart": "13",
      "pageEnd": "14"
    }
  ]
}

CoST IDS element

Impact measurement

Clarify the methodology or system to measure the long-term impact of the project solution (E.g. [free text].

OC4IDS mapping

Project level:

Add a project document, set its .documentType to 'impactMethodology' and map any free text to its .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "impactMethodology",
      "description": "The long term impact of this project will be measured according to...",
      "url": " http://example.com/impactMethodology.pdf "
    }
  ]
}

CoST IDS element

Carbon footprint

Disclose the carbon footprint of the project, informing the calculation, the methodology applied, and where the calculation can be found. [value, tons CO2 equivalent, free text to describe the methodology used to measure the carbon footprint].

OC4IDS mapping

Project level:

  1. Add a Metric object to the metrics array.

  2. Set the metric's .title to "Greenhouse gas emissions (carbon dioxide equivalent)" and map the methodology clarification to its .description.

  3. Add an Observation object to the metric's .observations array and:

  • Map the amount of greenhouse gas emissions in tonnes of CO2 equivalent to the observation's .measure

  • Set the .unit.name to "Tonne (metric ton)", .unit.scheme to 'UNCEFACT' and .unit.id to "TNE"

  • Set .period to the period covered by the calculation.

  1. If supporting documentation is available, add a project document and set its .documentType to 'ghgEmissions'.

{
  "metrics": [
    {
      "id": "1",
      "title": "Greenhouse gas emissions (carbon dioxide equivalent)",
      "description": "Emissions are calculated using the following methodology...",
      "observations": [
        {
          "id": "1",
          "period": {
            "startDate": "2024-01-01T00:00:00Z",
            "endDate": "2049-12-31T00:00:00Z"
          },
          "measure": 1000000,
          "unit": {
            "name": "Tonne (metric ton)",
            "scheme": "UNCEFACT",
            "id": "TNE"
          }
        }
      ]
    }
  ],
  "documents": [
    {
      "id": "1",
      "documentType": "ghgEmissions",
      "url": " http://example.com/ghgEmissions.pdf "
    }
  ]
}

CoST IDS element

Infrastructure assets to be decommissioned

Identify the asset for disposal purpose [free text].

OC4IDS mapping

For each set of decommissioned assets in a specified location, create a new OC4IDS project and:

  1. Set its type to 'decommissioning'.

  2. Set its title to the name of the asset.

  3. Add a RelatedProject object to the relatedProjects array and set its:

{
  "id": "oc4ids-bu3kcz-123456789",
  "title": "Otahuhu B Power Station",
  "type": "decommissioning",
  "relatedProjects": [
    {
      "id": "oc4ids-bu3kcz-987654321",
      "scheme": "oc4ids",
      "title": "Otahuhu C Power Station",
      "relationship": "replacement"
    }
  ]
}

CoST IDS element

Decommission period

Intended start and end dates of decommissioning.

OC4IDS mapping

Project level:

Map to decommissioningPeriod.

{
  "decommissioningPeriod": {
    "startDate": "2040-07-01T00:00:00Z",
    "endDate": "2041-06-30T00:00:00Z"
  }
}

CoST IDS element

Decommission plan

Disclose the technical plan for decommissioning (E.g.: [Doc]).

CoST IDS element

Carbon decommission savings

Disclose the evaluation of CO2 savings as a result of decommissioning [value, tons CO2 equivalent].

OC4IDS mapping

Project level:

  1. Add a Metric object to the forecasts array.

  2. Set the metric's .title to "Greenhouse gas emissions reduction (carbon dioxide equivalent)" and map the methodology clarification to its .description.

  3. Add an Observation object to the metric's .observations array and:

  • Map the amount of greenhouse gas emission savings in tonnes of CO2 equivalent to the observation's .measure

  • Set the .unit.name to "Tonne (metric ton)", .unit.scheme to 'UNCEFACT' and .unit.id to "TNE"

  • Set .period to the period covered by the calculation.

  1. If supporting documentation is available, Add a project document and set its .documentType to 'ghgEmissionsReduction'.

{
  "id": "oc4ids-bu3kcz-123456789",
  "forecasts": [
    {
      "id": "1",
      "title": "Greenhouse gas emissions reduction (carbon dioxide equivalent)",
      "description": "Emission reduction forecasts are calculated using the following methodology...",
      "observations": [
        {
          "id": "1",
          "period": {
            "startDate": "2024-01-01T00:00:00Z",
            "endDate": "2049-12-31T00:00:00Z"
          },
          "measure": 1000000,
          "unit": {
            "name": "Tonne (metric ton)",
            "scheme": "UNCEFACT",
            "id": "TNE"
          }
        }
      ]
    }
  ],
  "documents": [
    {
      "id": "1",
      "documentType": "ghgEmissionsReduction",
      "url": " http://example.com/GhgEmissionsReduction.pdf "
    }
  ]
}

CoST IDS element

Decommission mitigation plan

Disclose mitigation plan for people and communities affected by decommissioning (E.g.: [Doc]).

OC4IDS mapping

Project level:

Add a project document and set its .documentType to 'socialImpact'.

{
  "id": "oc4ids-bu3kcz-123456789",
  "documents": [
    {
      "id": "1",
      "documentType": "socialImpact",
      "url": "http://example.com/socialImpact.pdf",
      "pageStart": "13",
      "pageEnd": "14"
    }
  ]
}

Social

CoST IDS element

Number of beneficiaries

Indicate the number of direct and indirect project beneficiaries (E.g. direct: [number]; indirect: "number"). Beneficiaries are the individuals who benefit directly or indirectly from the project; they are the target group of the infrastructure project and their needs are addressed by the intervention.

OC4IDS mapping

Project level:

  1. Add a Benefit object to the benefits array.

  2. Add a Beneficiary object to the benefit's .beneficiaries array, set its .description to "Direct beneficiaries" and set its .numberOfPeople to the number of direct beneficiaries.

  3. Add a Beneficiary object to the benefit's .beneficiaries array, set its .description to "Indirect beneficiaries" and set its .numberOfPeople to the number of indirect beneficiaries.

{
  "benefits": [
    {
      "beneficiaries": [
        {
          "description": "Direct beneficiaries",
          "numberOfPeople": 1000
        },
        {
          "description": "Indirect beneficiaries",
          "numberOfPeople": 2000
        }
      ]
    }
  ]
}

CoST IDS element

Inclusive design and implementation

Clarify whether gender, people with disabilities and vulnerable and disadvantaged populations were considered in the project design (e.g. "free text to explain how the design meets inclusion goals" and document to support - the project design) and project implementation (e.g. "free text to explain implementation practices targeting inclusion goals" and document to support - contractor policy and procedures).

OC4IDS mapping

Project level:

  1. Add a project document, set its .documentType to 'inclusiveDesign' and map any free text to its .description.

  2. Add a project document, set its .documentType to 'inclusiveImplementation' and map any free text to its .description.

{
  "documents": [
    {
      "id": "1",
      "documentType": "inclusiveDesign",
      "description": "The project's design meets its inclusion goals by...",
      "url": "http://example.com/documents/inclusiveDesign.pdf"
    },
    {
      "id": "2",
      "documentType": "inclusiveImplementation",
      "description": "The project's implementation practices target inclusion goals by...",
      "url": "http://example.com/documents/inclusiveImplementation.pdf"
    }
  ]
}

CoST IDS element

Indigenous land

Identify whether the project is located or cut through indigenous land. Use the information at the LandMark - Global Platform of Indigenous and Community Lands on both databases Indigenous Lands Acknowledged by Government and Not Acknowledged by Government (customary tenure or with formal land claim submitted) to disclose the information.

OC4IDS mapping

Project level:

If the project is located in or cuts through indigenous land:

  1. Set social.inIndigenousLand to true.

  2. Add a Location object to the locations array, set its .id incrementally and set its description to "Indigenous land: ()" substituting and for the name and land category from the Landmark database.

If the project is not located in and does not cut through indigenous land, set social.inIndigenousLand to false.

{
  "social": {
    "inIndigenousLand": true
  },
  "locations": [
    {
      "id": "1",
      "description": "Indigenous land: Section 1 Block III Rowallan Survey District (Maori Freehold Land)"
    }
  ]
}

CoST IDS element

Public consultation meetings

Disclose the occurrence of public meetings with communities and impacted groups including meeting invite, the number of the participants, dates and location of these meetings.

OC4IDS mapping

Project Level:

For each meeting:

  1. Publish the meeting invite: add a project document and set its .documentType to 'consultationMeetingInvitation'.

  2. Publish the meeting details: add a Meeting object to the social.consultationMeetings array and set its:

  1. Publish the meeting minutes: add a project document and set its .documentType to 'minutes.consultationMeeting'.

{
  "social": {
    "consultationMeetings": [
      {
        "id": "1",
        "date": "2024-01-01T00:00:00Z",
        "address": {
          "streetAddress": "1600 Amphitheatre Pkwy",
          "locality": "Mountain View",
          "region": "CA",
          "postalCode": "94043",
          "countryName": "United States"
        },
        "numberOfParticipants": 12
      }
    ]
  },
  "documents": [
    {
      "id": "1",
      "documentType": "consultationMeetingInvitation",
      "url": "http://example.com/consultationMeetingInvitation.pdf"
    },
    {
      "id": "2",
      "documentType": "minutes.consultationMeeting",
      "url": "http://example.com/consultationMeetingMinutes.pdf"
    }
  ]
}

CoST IDS element

Land compensation budget

Disclose budget allocated to fund land compensation (E.g. [value]).

OC4IDS mapping

Project Level:

Map to social.landCompensationBudget.

{
  "social": {
    "landCompensationBudget": {
      "amount": 1000000,
      "currency": "USD"
    }
  }
}

CoST IDS element

Labour obligations

Disclose labour obligations in the construction contract. This can include, without limitation, the following:

  • Minimum wage

  • Overtime

  • Prohibition of forced labour

  • Prohibition of child labour

  • Equal opportunity

  • Non-discrimination

  • Freedom of association

  • Grievance mechanism

  • Working at height

  • Underground work

  • Handling of materials/equipment

  • Monitoring of accidents

  • Traffic management

  • Accommodation

  • Protective equipment

  • Others (explain)

OC4IDS mapping

Contracting process level:

  1. Publish a summary of the labor obligations:

    1. For each labor obligation, add the relevant code from the open laborObligations codelist to the .summary.social.laborObligations.obligations array.

    2. Optionally, add a further explanation of the labor obligations to summary.social.laborObligations.description.

  2. Publish the bidding documents that specify labor obligations: add a contracting process document and set its .documentType to 'biddingDocuments'.

  3. Publish the signed contract that includes labor obligations: add a contracting process document and set its .documentType to 'contractSigned'.

{
  "contractingProcesses": [
    {
      "id": "1",
      "summary": {
        "social": {
          "laborObligations": {
            "obligations": [
              "minimumWage",
              "paidOvertime"
            ],
            "description": "The contract's labor obligations include a minimum wage of $20 per hour and an overtime limit of 10 hours per week."
          }
        },
        "documents": [
          {
            "id": "1",
            "documentType": "biddingDocuments",
            "url": "http://example.com/biddingDocuments.pdf"
          },
          {
            "id": "2",
            "documentType": "contractSigned",
            "url": "http://example.com/contractSigned.pdf"
          }
        ]
      }
    }
  ]
}

CoST IDS element

Labour budget

Disclose the amount allocated by the main contractor to cover for labour costs (E.g. [value]).

OC4IDS mapping

Contracting process level:

Map to summary.social.laborBudget.

{
  "contractingProcesses": [
    {
      "id": "1",
      "summary": {
        "social": {
          "laborBudget": {
            "amount": 10000000,
            "currency": "USD"
          }
        }
      }
    }
  ]
}

CoST IDS element

Workers' accidents

Disclose summary statistics on accidents and fatalities involving construction workers, and an explanation of these events.

OC4IDS mapping

Project level:

Publish summary statistics on worker accidents:

  1. Add a Metric object to the metrics array, set its .id incrementally and set its .title to "Worker accidents".

  2. For each reporting period, add an Observation object to the metric's .observations array and set its:

  1. If further details are available, add them to the observation's .notes field.

Publish summary statistics on worker fatalities:

  1. Add a Metric object to the metrics array, set its .id incrementally and set its .title to "Worker fatalities".

  2. For each reporting period, add an Observation object to the metric's .observations array set its:

  1. If further details available, add them to the observation's .notes field.

{
  "metrics": [
    {
      "id": "1",
      "title": "Worker accidents",
      "observations": [
        {
          "id": "1",
          "period": {
            "startDate": "2024-01-01T00:00:00Z",
            "endDate": "2024-06-30T00:00:00Z"
          },
          "measure": 12,
          "notes": "In H1 2024, most accidents were related to..."
        }
      ]
    },
    {
      "id": "2",
      "title": "Worker fatalities",
      "observations": [
        {
          "id": "1",
          "period": {
            "startDate": "2024-01-01T00:00:00Z",
            "endDate": "2024-06-30T00:00:00Z"
          },
          "measure": 0
        }
      ]
    }
  ]
}

CoST IDS element

Health and safety certifications

Disclose labour related certifications issued in relation to project contractors and subcontractors such as ISO 45001 for Health and Safety (E.g. [Document]).

OC4IDS mapping

Contracting process level:

Add a contracting process document and set its .documentType to 'supplierHealthAndSafetyCertification'.

{
  "contractingProcesses": [
    {
      "id": "1",
      "summary": {
        "documents": [
          {
            "id": "1",
            "documentType": "supplierHealthAndSafetyCertification",
            "url": "http://example.com/documents/contractorHealthAndSafetyCertification.pdf"
          }
        ]
      }
    }
  ]
}

CoST IDS element

Construction materials testing

Disclose construction materials tests performed during project implementation. This can include, without limitation, the following:

  • Asphalt

  • Aggregate and rock

  • Bricks

  • Cement

  • Concrete

  • Coarse and fine aggregate

  • Masonry

  • Metallic materials

  • Mortar

  • Plywood

  • Timber

  • Resin and polymer

  • Soil

  • Stone

  • Others (explain).

[Free text to add not mentioned tests]

Document

OC4IDS mapping

Project level:

Publish a summary of the material tests:

  1. For each material test, add a code from the open constructionMaterial codelist to the social.healthAndSafety.materialTests.tests array.

  2. Add any further explanation of the tests to social.healthAndSafety.materialTests.tests, including the international or national standards that the tests conform to.

Publish test results: For each test result, add a project document and set its .documentType to 'materialTestResults'.

{
  "social": {
    "healthAndSafety": {
      "materialTests": {
        "tests": [
          "metal",
          "masonry"
        ],
        "description": "Tests were conducted of the steel frame and masonry of each structure according to ASTM International standards..."
      }
    }
  },
  "documents": [
    {
      "id": "1",
      "documentType": "materialTestResults",
      "url": "http://example.com/materialTestResults.pdf"
    }
  ]
}

CoST IDS element

Building inspections

Disclose building inspections during project implementation (E.g. [Document]).

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'buildingInspectionReport'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "buildingInspectionReport",
      "url": "http://example.com/buildingInspectionReport.pdf"
    }
  ]
}

CoST IDS element

Jobs generated

Disclose estimated and actual jobs (direct/indirect) during project implementation and estimated and actual jobs during operation (E.g. [direct: value] [indirect: value]).

OC4IDS mapping

Project level:

Publish job creation estimates:

  1. Add a Metric object to the forecasts array and set its .title to "Jobs created".

  2. For each job relationship - stage pair, add an Observation object to the metric's .observations array and set its:

Publish actual jobs created:

  1. Add a Metric object to the metrics array and set its .title to 'Jobs created'.

  2. For each job relationship - stage pair, add an Observation object to the metric's .observations array and set its:

{
  "forecasts": [
    {
      "id": "1",
      "title": "Jobs created",
      "observations": [
        {
          "id": "1",
          "measure": 1000,
          "dimensions": {
            "relationship": "direct",
            "stage": "implementation"
          }
        },
        {
          "id": "2",
          "measure": 5000,
          "dimensions": {
            "relationship": "indirect",
            "stage": "implementation"
          }
        },
        {
          "id": "3",
          "measure": 300,
          "dimensions": {
            "relationship": "direct",
            "stage": "operation"
          }
        },
        {
          "id": "4",
          "measure": 2000,
          "dimensions": {
            "relationship": "indirect",
            "stage": "operation"
          }
        }
      ]
    }
  ],
  "metrics": [
    {
      "id": "1",
      "title": "Jobs created",
      "observations": [
        {
          "id": "1",
          "measure": 979,
          "dimensions": {
            "relationship": "direct",
            "stage": "implementation"
          }
        },
        {
          "id": "2",
          "measure": 4120,
          "dimensions": {
            "relationship": "indirect",
            "stage": "implementation"
          }
        },
        {
          "id": "3",
          "measure": 295,
          "dimensions": {
            "relationship": "direct",
            "stage": "operation"
          }
        },
        {
          "id": "4",
          "measure": 1875,
          "dimensions": {
            "relationship": "indirect",
            "stage": "operation"
          }
        }
      ]
    }
  ]
}

Institutional

CoST IDS element

Policy coherence

Disclose documentation that evidences that the project is part of, or aligned with existing plans and policies, providing further details on the project's policy alignment. Consider alignment with:

  • SDGs

  • National plan or strategy

  • Infrastructure plan or strategy

  • Sector plan or strategy

  • Procuring entity plan or strategy

  • Paris Agreement

  • Nationally Determined Contributions (NDCs)

  • National Adaptation Plans

  • Medium-term fiscal frameworks/targets

[free text]

OC4IDS mapping

Project level:

  1. For each plan or policy to which the project is aligned, add a code from the open policyAlignment codelist to the policyAlignment.policies array and add a further explanation of the alignment to policyAlignment.description.

  2. For each United Nations Sustainable Development Goal to which the project is aligned, add a Classification object to the additionalClassifications array and set its:

  1. For each United Nations Sustainable Development Goal Target to which the project is aligned, add a Classification object to the additionalClassifications array and set its:

  1. If further documentation of the project's policy alignment is available, add a project document and set its .documentType to 'policyAlignment'.

{
  "additionalClassifications": [
    {
      "scheme": "sdg",
      "id": "6",
      "description": "Ensure availability and sustainable management of water and sanitation for all"
    },
    {
      "scheme": "sdgTarget",
      "id": "6.3",
      "description": "By 2030, improve water quality by reducing pollution, eliminating dumping and minimizing release of hazardous chemicals and materials, halving the proportion of untreated wastewater and substantially increasing recycling and safe reuse globally"
    }
  ],
  "policyAlignment": {
    "policies": [
      "infrastructurePlan"
    ],
    "description": "The project is intended to contribute towards the goals set out in the 2021 Australian Infrastructure Plan."
  },
  "documents": [
    {
      "id": "1",
      "documentType": "policyAlignment",
      "url": "http://example.com/infrastructurePlanAlignment.pdf"
    }
  ]
}

CoST IDS element

Freedom of information requests

Disclose Freedom of Information (FoI) requests that have been presented in relation to the project [E.g. Document]. Note that FoI requests can also be known as access to information requests.

OC4IDS mapping

Project level:

For each freedom of information request, add a project document and set its .documentType to 'informationRequest'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "informationRequest",
      "url": "http://example.com/foiRequest-1.pdf"
    }
  ]
}

CoST IDS element

Answers to Freedom of information requests

Disclose the responses provided by authorities to Freedom of Information (FoI) requests related to the project (Eg. [Document]). Note that FoI requests may also be known as access to information requests.

OC4IDS mapping

Project level:

For each freedom of information request response, add a project document and set its .documentType to 'informationRequestResponse'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "informationRequestResponse",
      "url": "http://example.com/foiRequest-1.pdf"
    }
  ]
}

CoST IDS element

Lobbying transparency

Disclose the occurrence of meetings with interest groups, including the meeting agenda and minutes, the number of the participants, dates and location of these meetings (E.g. Meeting 1 [date] [location] [number of participants] [Document], Meeting 2 [date] [location] [number of participants] [Document]).

OC4IDS mapping

Project Level:

For each meeting:

Publish the meeting details:

  1. Add a Meeting object to the lobbyingMeetings array and set:

  1. Get the Organization in parties that represents the public office. If none exists yet, add an organization.

  2. Set the meeting's .publicOffice.organization to the .id and .name of the organization.

Publish the meeting minutes: add a project document and set its .documentType to 'minutes.lobbyingMeeting'.

{
  "lobbyingMeetings": [
    {
      "id": "1",
      "date": "2024-01-01T00:00:00Z",
      "address": {
        "streetAddress": "1600 Amphitheatre Pkwy",
        "locality": "London",
        "region": "London",
        "postalCode": "WC1 8HG",
        "countryName": "United Kingdom"
      },
      "numberOfParticipants": 4,
      "publicOffice": {
        "person": {
          "name": "Brett Gliddon"
        },
        "organization": {
          "name": "Motorways UK",
          "id": "GB-GOR-XX1234"
        },
        "jobTitle": "Group General Manager Transport Services"
      }
    }
  ],
  "documents": [
    {
      "id": "2",
      "documentType": "minutes.lobbyingMeeting",
      "url": "http://example.com/lobbyingMeetingMinutes.pdf"
    }
  ]
}

CoST IDS element

Beneficial ownership

Disclose the beneficial owners of the contractors and suppliers appointed in the project (E.g. [name, identifier]).

OC4IDS mapping

Project level:

For each beneficial owner:

  1. Get the Organization in parties that represents the contractor or supplier.

  2. Add a Person object to the organization's .beneficialOwners array.

  3. Set the person's:

  • .id incrementally

  • .name to the beneficial owner's name

  • .identifier to the beneficial owner's identifier

{
  "parties": [
    {
      "id": "1",
      "beneficialOwners": [
        {
          "id": "1",
          "name": "Juan Perez",
          "identifier": {
            "scheme": "PRY-IDCARD",
            "id": "12345"
          }
        }
      ]
    }
  ]
}

CoST IDS element

Sustainability criteria

Identify the presence of sustainability and non-price attributes in the award criteria.

OC4IDS mapping

Contracting process level:

Add a Sustainability object to the summary.tender.sustainability array and add 'awardCriteria' to its .strategies array.

{
  "contractingProcesses": [
    {
      "id": "1",
      "summary": {
        "tender": {
          "sustainability": [
            {
              "strategies": [
                "awardCriteria"
              ]
            }
          ]
        }
      }
    }
  ]
}

CoST IDS element

Anti-corruption certifications

Disclose anti-corruption certifications of the project, such as ISO 37001 on Anti-Bribery Management Systems Standard (E.g. [Document]).

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'antiCorruptionCertification'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "antiCorruptionCertification",
      "url": "http://example.com/ISO37001Certification.pdf"
    }
  ]
}

CoST IDS element

Independent monitoring

Identify the entities acting as independent monitors of the project (E.g. [free text]).

OC4IDS mapping

Project level:

Add an organization for the independent monitor and add 'independentMonitor' to its .roles array.

{
  "parties": [
    {
      "id": "1",
      "name": "Transparency International New Zealand",
      "roles": [
        "independentMonitor"
      ]
    }
  ]
}

CoST IDS element

Performance monitoring

Disclose Key Performance Indicators adopted by the project (E.g. [free text]).

CoST IDS element

Risk management plans

Disclose risk management plans prepared for the project (E.g. [Document]).

OC4IDS mapping

Project Level:

Add a project document and set its .documentType to 'riskProvisions'.

{
  "documents": [
    {
      "id": "1",
      "documentType": "riskProvisions",
      "url": "http://example.com/riskManagementPlan.pdf"
    }
  ]
}

CoST IDS element

Sustainable sub-sectors

Identify relevant sub-sectors related to the project scope. Select from a list (non-exhaustive):

  • Renewable energy

    • Solar

    • Wind

    • Hydropower

    • Biomass

    • Geothermal

  • Water and wastewater management

  • Transport

    • Low carbon transport

  • Natural resource management

    • Flood protection

Free text to add not mentioned sub-sectors

OC4IDS mapping

Project Level:

Map to sector, using the open ProjectSector codelist.

{
  "sector": [
    "solar"
  ]
}