OCDS to OC4IDS mapping¶
This page provides guidance and documents a mapping from OCDS fields and codes to OC4IDS fields and codes. The organization of the mapping tables reflects the structure of the CoST IDS.
The CoST IDS sets out a number of disclosure requirements under the heading of "information for disclosure upon request," also known as "reactive disclosure." You can disclose these elements proactively using OC4IDS. Separate tables are provided for project-level and process-level reactive disclosures.
Guidance¶
Command-line tool and reference implementation¶
OC4IDS Kit's convert-from-ocds command is a command-line tool and reference implementation for converting OCDS data to OC4IDS format.
convert-from-ocds
covers most mappings in the following categories:
project-level identification
project-level preparation
process-level procurement
However, convert-from-ocds
does not cover all mappings, nor does it perform currency conversions. Mappings that convert-from-ocds
does not cover are shown in italics.
Mapping codelists¶
Mappings that depend on the specific classification or codelist used in the OCDS data are not documented in detail, as they can differ by publisher. For example, mapping to the OC4IDS projectSector codelist.
Alternative mappings¶
Some mappings offer alternatives in case the primary mapping isn't available. For example, for OCDS data in which planning.project.title
isn't available, you can set the project title
based on the tender.title
.
In order to provide analysts with additional context, some alternative mappings copy additional fields which don't appear in OC4IDS schema. You ought to remove these fields if you plan to publish your OC4IDS data.
OCDS extensions¶
Some mappings use fields from OCDS extensions. In these cases, the names of extensions are noted in parentheses; where possible, alternative mappings are provided that use only fields from the core OCDS schema.
Handling conflicts and duplicates¶
Implementations of the mapping ought to give consideration to:
OCDS data that contains fields that differ between contracting processes but map to a single field in OC4IDS: for example, where
planning.project.title
differs for two contracting processes that relate to the same project, but OC4IDS has a singletitle
field at the project level.OCDS data that contains multiple
Organization
objects with the same.role
that map to a single field in OC4IDS: for example, where a contracting process has twoOrganization
s with the 'procuringEntity' role, but OC4IDS has a single.summary.tender.procuringEntity
field at the contract level.Checking for duplicates when copying objects from OCDS. For example, checking whether an
Organization
object has already been copied before copying it again.Handling identifier conflicts when copying objects from OCDS. For example, where two contracting processes both contain a
Document
with the same.id
.
Read the convert-from-ocds
transformation notes to learn about how OC4IDS Kit handles the above scenarios.
Handling multiple currencies¶
Some mappings involve converting values in OCDS, which can be in different currencies, to a base currency.
Implementations which include multiple currencies ought to give consideration to value dating. One approach is to use the compiled release's date
.
Mapping¶
Project level¶
Identification¶
Elemento del CoST IDS |
Borrador de definiciones del CoST IDS |
Mapeo desde OCDS |
---|---|---|
Project owner |
Name of the sponsoring Government department |
Validar la lista |
Sector |
Develop a list of sectors relevant to country e.g. housing, transport, energy, water etc. |
Copiar el objeto |
Subsector |
Develop a subset for each sector e.g. Transport could be subdivided into national highway, local road, railway, port, airport etc. |
Copiar cada uno de los objetos |
Project name |
Specify the project name |
Establecer |
Project Location |
Briefly specify location of the project |
Copiar cada objeto |
Purpose |
Specify the socio-economic purpose of the project |
Establecer |
Project description |
Concise description and details of the project |
Establecer |
Preparation¶
Elemento del CoST IDS |
Borrador de definiciones del CoST IDS |
Mapeo desde OCDS |
---|---|---|
Project Scope (main output) |
Main outputs from the project that are being taken forward into construction (type, quantity, unit) |
Validar la lista |
Environmental impact |
Briefly describe the environmental impacts and mitigation measures for this project e.g. impacts on flora, fauna & woodlands, areas of natural beauty, carbon emissions etc. and mitigation measures e.g. pollution control, low carbon solutions, sustainable timber etc. |
Validar la lista |
Land and settlement impact |
State the amount of land and property that was acquired for the project e.g. 25km2 land, and related impacts e.g. archaeological issues (moved Saxon burial site), local/indigenous settlements (relocated 5 indigenous villages of 500 villagers each), impacts on local businesses e.g. (30 business properties purchased). |
Validar la lista |
Contact details |
Postal and electronic address of the Project Owner |
Validar la lista |
Funding sources |
Name the funding organization(s)/sources of funding |
Validar la lista |
Project Budget |
Specify the projected costs/allocated budget for the project (currency and amount). The budget includes land / property acquisition, environmental mitigation measures, H&S provisions, client, consultant & contractor costs, VAT etc. |
Si el proyecto tiene un solo proceso de contratación, establecer |
Project budget approval date |
Date project budget was authorized |
*Validar la lista |
Project completion¶
Elemento del CoST IDS |
Borrador de definiciones del CoST IDS |
Mapeo desde OCDS |
---|---|---|
Project status (current) |
The current stage of the project. Select from identification, preparation, construction, completion, completed or cancelled. |
Inferir a partir de |
Project completion cost |
State projected or actual completion cost (currency and amount) |
Inferir el costo proyectado a partir de |
Completion date |
State projected or actual completion date |
Inferir a partir de |
Project Scope at completion (projected) |
Indicate projected or actual scope of project. Aim is to show if the completed project scope differs from the original project scope. Specify main outputs (type, quantity, unit) |
Validar en |
Reasons for project changes |
Summary of primary reasons for any changes in scope, time and cost |
Inferir a partir de |
Reference to audit and evaluation reports |
Reference to publicly available technical and financial audits |
Validar ficar la lista |
Reactive disclosures¶
Identification and preparation¶
Elemento del CoST IDS |
Descripción |
Mapeo desde OCDS |
---|---|---|
Multi-year programme & Budget |
A detailed breakdown of the budget by period and/or participating funders. |
Copiar el contenido de |
Project brief or Feasibility study |
Documentation of feasibility studies carried out for this contracting process or project, providing information on net benefits or costs of the proposed goods, works or services. |
Validar la lista |
Environmental and social impact assessment |
Environmental impact assessment Documentation of assessments of the environmental impacts (e.g. impacts on flora, fauna & woodlands, areas of natural beauty, carbon emissions etc.) and mitigation measures (e.g. pollution control, low carbon solutions, sustainable timber etc.) for this contracting process or project. Social impact assessment Documentation of assessments of the intended and unintended social consequences of this project, and documentation of mitigation measures for those social consequences. Social impacts are changes that affect people, directly or indirectly (e.g. changes to people’s way of life, culture, community, health and well-being etc.). |
Validar la lista |
Resettlement and compensation plan |
Documentation of the procedures and actions to mitigate adverse effects, compensate losses, and provide development benefits to people and communities affected by the contracting process or project. |
Validar la lista |
Project officials and roles |
Name and position of the highest authority in the procuring entity where the budget for this project is allocated (project owner) |
Verificar la lista |
Financial agreement |
Loan or donation agreement with financing conditions. |
Validar la lista |
Procurement plan |
Documentation that sets out the basis for this particular contracting process. |
Validar la lista |
Project approval decision |
Additional details about the approval of the budget. |
Validar la lista |
Completion¶
Elemento del CoST IDS |
Descripción |
Mapeo desde OCDS |
---|---|---|
Implementation progress reports |
Planned and actual physical and financial progress over time. |
Opcionalmente, validar la lista Opcionalmente, copiar el contenido de la lista |
Budget amendment decision |
Document accrediting the approval of budget expansion or extension for this project. |
Validar la lista |
Project completion report |
A completion certificate issued by a relevant authority providing evidence that works were completed to a certain level of quality. Completion certificates might only be relevant for particular kinds of contracting processes or projects. |
Validar la lista |
Project evaluation report |
Generally published at the conclusion of a project, providing a technical and financial summary of delivery |
Validar la lista |
Technical audit reports |
Documentation of checks that construction work has been undertaken as specified. |
Validar la lista |
Financial audit reports |
Documentation of checks that a project's financial statements are correct and complete. |
Validar la lista |
Process level¶
The mappings in this section relate to the contractingProcesses
section of the OC4IDS schema, unless otherwise specified.
Procurement¶
Elemento del CoST IDS |
Borrador de definiciones del CoST IDS |
Mapeo desde OCDS |
---|---|---|
Procuring entity |
Enter name of the organization carrying out the procurement |
Verificar la lista |
Procuring entity contact details |
Postal and Electronic address |
Verificar la lista |
Contract administrative entity |
Enter name of the organization carrying out the contract administrative entity if different from the Procuring Entity |
Verificar la lista |
Contract status |
Select from pre-award, active or closed |
Establecer |
Procurement process |
Develop a list such as International Competitive Bidding, National Competitive Bidding, Donor Procurement Rules, Framework, Direct Award |
Establecer |
Contract type |
Develop a list such as Design, Supervision, Design & Supervision, Design & Build, Construction |
Mapear de |
Number of firms tendering |
Number of firms who submit a tender |
Establecer |
Cost estimate |
Currency and amount of the original pre-tender estimate of the contract |
Validar las entregas individuales para el proceso de contratación y establecer |
Contract title |
The formal name of the contract |
Si el proceso de contratación tiene un solo objeto |
Contract firm(s) |
Legal name of supplier |
Verificar la lista |
Contract price |
Currency and price at contract award |
Si el valor de |
Contract scope of work |
Main outputs from the contract e.g. detailed design, supervision, project management and or type, quantity, unit for construction |
Si hay más de un objeto Por otro parte, si hay solo un objeto Por otra parte, si hay solo un |
Contract start date and contract period (duration) |
Enter dates and Number of weeks from contract start date to (anticipated) completion date |
Establecer |
Implementation¶
Disclosures in the implementation section of the CoST IDS relate to changes to a contract's value, duration or scope that were made after the contract was awarded.
If OCDS data is available, these changes can be determined by comparing the most recent OCDS release to a compiled release created from all prior releases (to better understand these concepts, refer to the OCDS documentation). The specific fields to monitor for changes between releases are described in the mapping table below.
In some cases, OCDS data might include an explanation of changes in the relevant amendments
block. In other cases, the reason might need to be manually entered.
Elemento del CoST IDS |
Borrador de definiciones del CoST IDS |
Mapeo desde OCDS |
---|---|---|
Variation to contract price |
Difference between the price at contract award and the current projected price |
Monitorear |
Escalation of contract price |
Escalation to date of the price of materials, labour, equipment etc. due to fluctuations in inflation, currency etc. |
Monitorear |
Variation to contract duration |
Difference between original duration at contract award and the current projected duration in weeks. |
Monitorear |
Variation to contract scope |
Any changes between original scope at contract award and the current scope |
*Monitorear |
Reasons for price changes |
Summary of reasons for primary changes (e.g. variations) that then lead to changes in contract price, major price fluctuations and accumulative increase or decrease in price. |
*Copiar el valor de |
Reasons for scope and duration changes |
Summary of reasons for primary changes (e.g. variations) that then lead to changes in the scope and duration. |
*Copiar el valor de |
Reactive disclosures¶
Procurement¶
Elemento del CoST IDS |
Descripción |
Mapeo desde OCDS |
---|---|---|
Contract officials and roles |
Name and position of the public official in charge of administration of the contract(s). |
Validar la lista |
Procurement method |
Specify tendering method using the method codelist (open, selective, limited, direct). |
Establecer |
Tender documents |
Documentation for potential suppliers, describing the goals of the contract (e.g. goods and services to be procured), and the bidding process. |
Validar la lista |
Tender evaluation results |
Documentation on the evaluation of the bids and the application of the evaluation criteria, including the justification for the award. |
Validar la lista |
Project design report |
A record of the justification for the design approach adopted in the project, typically issued before the works start, by the consultant or firm that will supervise the works. |
Validar la lista |
Contract¶
Elemento del CoST IDS |
Descripción |
Mapeo desde OCDS |
---|---|---|
Contract agreement and conditions |
A copy of the signed contract. Consider providing both machine-readable (e.g. original PDF, Word or Open Document format files), and a separate document entry for scanned-signed pages where this is required. |
Validar la lista /contracts/documents |
Registration and ownership of firms |
A document issued by the relevant government registry as confirmation of the due incorporation and valid existence of the organization. |
Validar la lista Validar la lista |
Specifications and drawings |
Detailed technical information about goods or services to be provided. |
Validar la lista |
Implementation¶
Elemento del CoST IDS |
Descripción |
Mapeo desde OCDS |
---|---|---|
List of variations, changes, amendments |
Details of changes to the duration, price, scope or other significant features of the contracting process |
Monitorear los siguientes campos en busca de cambios:
Copiar |
List of escalation approvals |
Documentation of one or more approved escalations of the contract price during the project life-cycle. |
Validar las listas |
Quality assurance reports |
Documentation identifying deficiencies in designs, specifications, standards, methods, procedures and practices, and identifying best practices. |
Validar las listas |
Disbursement records or payment certificates |
A list of the spending transactions made against this contract and/or a document certifying that the work specified on a supplier's estimate or invoice is complete and that payment to the supplier is approved |
Copiar los contenidos de la lista Validar la lista |
Contract amendments |
A legal document that changes or adds to the terms of an existing contract. |
Validar la lista |