CoST IDS & OCDS Mapping¶
CoST – the Infrastructure Transparency Initiative (CoST) is the leading global initiative improving transparency and accountability in public infrastructure.
The CoST approach is based on four core features:
Disclosure - where procuring entities are asked to follow the CoST Infrastructure Data Standard. This describes 40 items of data that should be proactively disclosed at key stages of an infrastructure project cycle.
Assurance - an independent review of the disclosed data by assurance teams based within CoST national programmes. Teams may identify key issues of concern analyzing the data that has been disclosed, and will put technical terms into plain language to allow stakeholders to understand the issues, and hold decision makers to account.
Multi-stakeholder working - each CoST national programme is managed by a stakeholder group including government, private sector and civil society.
Social accountability - raising awareness of key issues arising from the assurance process, and engaging civil society and media to hold decision makers to account.
The 'Infrastructure Data Standard' is a framework for disclosure which has been adapted by a range of CoST national programmes, who have variously prioritized different elements based on their local needs, or who have included additional elements that they wish to monitor: particularly additional kinds of documentation that should be provided for each infrastructure project.
You can read more about the Infrastructure Data Standard on the CoST website.
Frameworks and standards
There is an important distinction between the Infrastructure Data Standard (IDS) and the Open Contracting Data Standard (OCDS). IDS provides a framework to identify categories of information that should be disclosed. OCDS describes specific fields and how they should be structured as data.
The Open Contracting for Infrastructure Data Standard (OC4IDS) documented on this site acts as a bridge between the IDS framework, and the idea of a more structured technical data standard.
The following tables document two mappings:
The CoST IDS to OC4IDS mapping describes how to represent each element of the CoST IDS as structured data using OC4IDS. Use this mapping if you already collect data according to the CoST IDS and you want to publish your data using OC4IDS, or if you want to make sure that your OC4IDS publication conforms to the CoST IDS.
The OCDS to OC4IDS mapping describes how to use OCDS data to populate the sections of an OC4IDS file which relate to the CoST IDS. Use this mapping if you have access to OCDS data on infrastructure contracting processes and you want to create a summary by project in OC4IDS format, or if you want to check which CoST IDS elements your OCDS data covers.
The organization of the mapping tables reflects the structure of the CoST IDS, which is described in Getting Started.
The mapping tables use /
notation to reference fields in OCDS data, e.g. /tender/status
, and .
notation to reference fields in the OC4IDS schema, e.g. .budget.approvalDate
.
The CoST IDS also 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 reactive disclosures in each mapping.
Common operations¶
To avoid repetition in the mapping, we refer and link to the following common operations.
Add a project document¶
Add a Document
object to the documents
array and set its fields as follows:
Set its
.id
incrementallySet its
.url
to a direct link to the documentSet its
.title
to the title of the document
Add a contracting process document¶
Add a Document
object to the contractingProcesses.summary.documents
array and set its fields as follows:
Set its
.id
incrementallySet its
.url
to a direct link to the documentSet its
.title
to the title of the document
CoST IDS to OC4IDS Mapping¶
Project level¶
Identification¶
CoST IDS element |
CoST IDS draft definition |
Mapping to OC4IDS |
---|---|---|
Project owner |
Name of the sponsoring Government department |
Project Level: Add an |
Sector |
Develop a list of sectors relevant to country e.g. housing, transport, energy, water etc. |
Project Level: Map to the projectSector codelist and publish one or more values in |
Subsector |
Develop a subset for each sector e.g. Transport could be subdivided into national highway, local road, railway, port, airport etc. |
Project Level: Publish in |
Project name |
Specify the project name |
Project Level: Publish in |
Project Location |
Briefly specify location of the project |
Project Level: Publish using the |
Purpose |
Specify the socio-economic purpose of the project |
Project Level: Publish in |
Project description |
Concise description and details of the project |
Project Level: Publish in |
Preparation¶
CoST IDS element |
CoST IDS draft definition |
Mapping to OC4IDS |
---|---|---|
Project Scope (main output) |
Main outputs from the project that are being taken forward into construction (type, quantity, unit) |
Project Level: Publish in |
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. |
Project Level: Publish in |
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). |
Project Level: Publish in |
Contact details |
Postal and electronic address of the Project Owner |
Project Level: Publish in the |
Funding sources |
Name the funding organization(s)/sources of funding |
Project Level: If a funding organization is the project owner, add 'funder' to the |
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. |
Project Level: Publish in |
Project budget approval date |
Date project budget was authorized |
Project Level: Publish in |
Project completion¶
CoST IDS element |
CoST IDS draft definition |
Mapping to OC4IDS |
---|---|---|
Project status (current) |
The current stage of the project. Select from identification, preparation, construction, completion, completed or cancelled. |
Project Level: Publish in |
Project completion cost |
State projected or actual completion cost (currency and amount) |
Project Level: Publish in |
Completion date |
State projected or actual completion date |
Project Level: Publish in |
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) |
Project Level: Publish free text as |
Reasons for project changes |
Summary of primary reasons for any changes in scope, time and cost |
Project Level: Publish using |
Reference to audit and evaluation reports |
Reference to publicly available technical and financial audits |
Project Level: Publish in |
Reactive disclosures¶
Identification and preparation¶
Completion¶
Implementation progress reports¶
In addition to the documents listed in the mapping table, you can use OC4IDS to publish structured data on planned and actual physical and financial progress.
Choose from the following options, depending on the data you collect and the data required by your use cases.
Actual progress over time
Add a
Metric
object to themetrics
array and:For financial progress, set its
id
to 'financialProgress' and set its title to 'Financial progress', or the equivalent in the language of your publication.For physical progress, set its
id
to 'physicalProgress' and set its title to 'Physical progress', or the equivalent in the language of your publication.
For each progress update, add an
Observation
object to theMetric
object's.observations
array and:Set its
.id
incrementallySet its
.measure
to the financial progress of the project. For example, for a project that is 75% complete, set.measure
to75
Set its
.unit.name
to 'percent', set itsunit.id
to 'P1' and set itsunit.scheme
to 'UNCEFACT'Set its
period.startDate
andperiod.endDate
to the date on which the financial progress was measured
Example:
{
"metrics": [
{
"id": "physicalProgress",
"title": "Physical progress",
"observations": [
{
"id": "1",
"measure": "4.04",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-03-31T23:59:59Z",
"endDate": "2017-03-31T23:59:59Z"
}
},
{
"id": "2",
"measure": "7.98",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-04-30T23:59:59Z",
"endDate": "2017-04-30T23:59:59Z"
}
},
{
"id": "3",
"measure": "8.38",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-05-31T23:59:59Z",
"endDate": "2017-05-31T23:59:59Z"
}
}
]
}
]
}
A single progress figure
If your implementation does not store a change history, you can publish a single Observation
object for each Metric
and update the Observation
object's .measure
each time there is a progress update.
Example:
{
"metrics": [
{
"id": "financialProgress",
"title": "Financial progress",
"observations": [
{
"id": "1",
"measure": "4.04",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-03-31T23:59:59Z",
"endDate": "2017-03-31T23:59:59Z"
}
}
]
}
]
}
Planned progress over time
You can use the forecasts
array to publish progress forecasts for different points in time.
Add a
Metric
object to theforecasts
array and:For financial progress, set its
id
to 'financialProgress' and set its title to 'Financial progress', or the equivalent in the language of your publication.For physical progress, set its
id
to 'physicalProgress' and set its title to 'Physical progress', or the equivalent in the language of your publication.
For each forecast, add an
Observation
object to theMetric
object's.observations
array and:Set its
.id
incrementallySet its
.measure
to the forecast progress of the project. For example, to forecast when the project is expected to be complete, set.measure
to100
.Set its
.unit.name
to 'percent', set itsunit.id
to 'P1' and set itsunit.scheme
to 'UNCEFACT'Set its
period.startDate
andperiod.endDate
to the date on which you expect the progress to be achieved
Example:
{
"forecasts": [
{
"id": "physicalProgress",
"title": "Physical progress",
"observations": [
{
"id": "1",
"measure": "4.04",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-03-31T23:59:59Z",
"endDate": "2017-03-31T23:59:59Z"
}
},
{
"id": "2",
"measure": "7.98",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-04-30T23:59:59Z",
"endDate": "2017-04-30T23:59:59Z"
}
},
{
"id": "3",
"measure": "8.38",
"unit": {
"name": "percent",
"id": "P1",
"scheme": "UNCEFACT"
},
"period": {
"startDate": "2017-05-31T23:59:59Z",
"endDate": "2017-05-31T23:59:59Z"
}
}
]
}
]
}
Process level¶
The mappings in this section relate to the contractingProcesses
section of the OC4IDS schema, unless otherwise specified.
Procurement¶
CoST IDS element |
CoST IDS draft definition |
Mapping to OC4IDS |
---|---|---|
Procuring entity |
Enter name of the organization carrying out the procurement |
Project Level: Add an entry to |
Procuring entity contact details |
Postal and Electronic address |
Project Level: Publish the postal address in |
Contract administrative entity |
Enter name of the organization carrying out the contract administrative entity if different from the Procuring Entity |
Project Level: Add an entry to |
Contract status |
Select from pre-award, active or closed |
Contracting process: Publish in |
Procurement process |
Develop a list such as International Competitive Bidding, National Competitive Bidding, Donor Procurement Rules, Framework, Direct Award |
Contracting process: Publish in |
Contract type |
Develop a list such as Design, Supervision, Design & Supervision, Design & Build, Construction |
Contracting process: Add one or more values to the |
Number of firms tendering |
Number of firms who submit a tender |
Contracting process: Publish in |
Cost estimate |
Currency and amount of the original pre-tender estimate of the contract |
Contracting process: Publish in |
Contract title |
The formal name of the contract |
Contracting process: Publish in |
Contract firm(s) |
Legal name of supplier |
Project Level: Add an entries to |
Contract price |
Currency and price at contract award |
Contracting process: Publish in |
Contract scope of work |
Main outputs from the contract e.g. detailed design, supervision, project management and or type, quantity, unit for construction |
Contracting process: Publish in |
Contract start date and contract period (duration) |
Enter dates and Number of weeks from contract start date to (anticipated) completion date |
Contracting process: Publish in |
Implementation¶
CoST IDS element |
CoST IDS draft definition |
Mapping to OC4IDS |
---|---|---|
Variation to contract price |
Difference between the price at contract award and the current projected price |
Contracting process: For each variation, publish an entry with a |
Escalation of contract price |
Escalation to date of the price of materials, labour, equipment etc. due to fluctuations in inflation, currency etc. |
Contracting process: For each escalation, publish an entry with a |
Variation to contract duration |
Difference between original duration at contract award and the current projected duration in weeks. |
Contracting process: For each variation, publish an entry with a |
Variation to contract scope |
Any changes between original scope at contract award and the current scope |
Contracting process: For each variation, publish an entry with a |
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. |
Contracting process: For each variation, provide a |
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. |
Contracting process: For each variation, provide a |
Reactive disclosures¶
Procurement¶
CoST IDS element |
Description |
Mapping to OC4IDS |
---|---|---|
Contract officials and roles |
Name and position of the public official in charge of administration of the contract(s). |
From the
Add a
|
Procurement method |
Specify tendering method using the method codelist (open, selective, limited, direct). |
Set |
Tender documents |
Documentation for potential suppliers, describing the goals of the contract (e.g. goods and services to be procured), and the bidding process. |
|
Tender evaluation results |
Documentation on the evaluation of the bids and the application of the evaluation criteria, including the justification for the award. |
|
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. |
Contract¶
CoST IDS element |
Description |
Mapping to OC4IDS |
---|---|---|
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. |
|
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. |
Document: and set Data: Add an
|
Specifications and drawings |
Detailed technical information about goods or services to be provided. |
Implementation¶
CoST IDS element |
Description |
Mapping to OC4IDS |
---|---|---|
List of variations, changes, amendments |
Details of changes to the duration, price, scope or other significant features of the contracting process |
For each variation, change or amendment, publish an entry with a Set |
List of escalation approvals |
Documentation of one or more approved escalations of the contract price during the project life-cycle. |
|
Quality assurance reports |
Documentation identifying deficiencies in designs, specifications, standards, methods, procedures and practices, and identifying best practices. |
|
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 |
Data: For each disbursement, add a Documents: |
Contract amendments |
A legal document that changes or adds to the terms of an existing contract. |
OCDS to OC4IDS Mapping¶
Guidance¶
Command-line tool and reference implementation¶
OCDS Kit's convert-to-oc4ids command is a command-line tool and reference implementation for converting OCDS data to OC4IDS format.
convert-to-oc4ids
covers most mappings in the following categories:
project-level identification
project-level preparation
process-level procurement
However, convert-to-oc4ids
does not cover all mappings, nor does it perform currency conversions. Mappings which convert-to-oc4ids
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 may differ by publisher. For example, mapping to the OC4IDS projectSector codelist.
Alternative mappings¶
Some mappings offer optional alternatives in case the primary mapping isn't available. For example, for OCDS data in which planning.project.title
isn't available, you can optionally set the project title
based on the tender.title
.
In order to provide analysts with additional context, alternative mappings may copy additional fields which don't appear in OC4IDS schema. You should 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 should 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-to-oc4ids
transformation notes to learn about how OCDS Kit handles the above scenarios.
Handling multiple currencies¶
Some mappings involve converting values in OCDS, which may be in different currencies, to a base currency.
Implementations which include multiple currencies should give consideration to value dating. One approach is to use the compiled release's date
.
Mapping¶
Project level¶
Identification¶
CoST IDS element |
CoST IDS draft definition |
Mapping from OCDS |
---|---|---|
Project owner |
Name of the sponsoring Government department |
Check the |
Sector |
Develop a list of sectors relevant to country e.g. housing, transport, energy, water etc. |
Copy the |
Subsector |
Develop a subset for each sector e.g. Transport could be subdivided into national highway, local road, railway, port, airport etc. |
Copy each |
Project name |
Specify the project name |
Set |
Project Location |
Briefly specify location of the project |
Copy each |
Purpose |
Specify the socio-economic purpose of the project |
Set |
Project description |
Concise description and details of the project |
Set |
Preparation¶
CoST IDS element |
CoST IDS draft definition |
Mapping from OCDS |
---|---|---|
Project Scope (main output) |
Main outputs from the project that are being taken forward into construction (type, quantity, unit) |
Check the |
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. |
Check the |
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). |
Check the |
Contact details |
Postal and electronic address of the Project Owner |
Check the |
Funding sources |
Name the funding organization(s)/sources of funding |
Check the |
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. |
If the project has only one contracting process, set |
Project budget approval date |
Date project budget was authorized |
Check the |
Project completion¶
CoST IDS element |
CoST IDS draft definition |
Mapping from OCDS |
---|---|---|
Project status (current) |
The current stage of the project. Select from identification, preparation, construction, completion, completed or cancelled. |
Infer from |
Project completion cost |
State projected or actual completion cost (currency and amount) |
Infer projected cost from |
Completion date |
State projected or actual completion date |
Infer from |
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) |
Check |
Reasons for project changes |
Summary of primary reasons for any changes in scope, time and cost |
Infer from |
Reference to audit and evaluation reports |
Reference to publicly available technical and financial audits |
Check the |
Reactive disclosures¶
Identification and preparation¶
CoST IDS element |
Description |
Mapping from OCDS |
---|---|---|
Multi-year programme & Budget |
A detailed breakdown of the budget by period and/or participating funders. |
Copy the contents of |
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. |
Check the |
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.). |
Check the |
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. |
Check the |
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) |
Check the |
Financial agreement |
Loan or donation agreement with financing conditions. |
Check the |
Procurement plan |
Documentation that sets out the basis for this particular contracting process. |
Check the |
Project approval decision |
Additional details about the approval of the budget. |
Check the |
Completion¶
CoST IDS element |
Description |
Mapping from OCDS |
---|---|---|
Implementation progress reports |
Planned and actual physical and financial progress over time. |
Optionally, check the Optionally, copy the contents of the |
Budget amendment decision |
Document accrediting the approval of budget expansion or extension for this project. |
Check the |
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. |
Check the |
Project evaluation report |
Generally published at the conclusion of a project, providing a technical and financial summary of delivery |
Check the |
Technical audit reports |
Documentation of checks that construction work has been undertaken as specified. |
Check the |
Financial audit reports |
Documentation of checks that a project's financial statements are correct and complete. |
Check the |
Process level¶
The mappings in this section relate to the contractingProcesses
section of the OC4IDS schema, unless otherwise specified.
Procurement¶
CoST IDS element |
CoST IDS draft definition |
Mapping from OCDS |
---|---|---|
Procuring entity |
Enter name of the organization carrying out the procurement |
Check the |
Procuring entity contact details |
Postal and Electronic address |
Check the |
Contract administrative entity |
Enter name of the organization carrying out the contract administrative entity if different from the Procuring Entity |
Check the |
Contract status |
Select from pre-award, active or closed |
Set |
Procurement process |
Develop a list such as International Competitive Bidding, National Competitive Bidding, Donor Procurement Rules, Framework, Direct Award |
Set |
Contract type |
Develop a list such as Design, Supervision, Design & Supervision, Design & Build, Construction |
Map from |
Number of firms tendering |
Number of firms who submit a tender |
Set |
Cost estimate |
Currency and amount of the original pre-tender estimate of the contract |
Check the individual releases for the contracting process and set |
Contract title |
The formal name of the contract |
If the contracting process has only one |
Contract firm(s) |
Legal name of supplier |
Check the |
Contract price |
Currency and price at contract award |
If the value of |
Contract scope of work |
Main outputs from the contract e.g. detailed design, supervision, project management and or type, quantity, unit for construction |
If there is more than one Otherwise, if there is only one Otherwise, if there is only one |
Contract start date and contract period (duration) |
Enter dates and Number of weeks from contract start date to (anticipated) completion date |
Set |
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 may include an explanation of changes in the relevant amendments
block. In other cases, the reason may need to be manually entered.
CoST IDS element |
CoST IDS draft definition |
Mapping from OCDS |
---|---|---|
Variation to contract price |
Difference between the price at contract award and the current projected price |
Monitor |
Escalation of contract price |
Escalation to date of the price of materials, labour, equipment etc. due to fluctuations in inflation, currency etc. |
Monitor |
Variation to contract duration |
Difference between original duration at contract award and the current projected duration in weeks. |
Monitor |
Variation to contract scope |
Any changes between original scope at contract award and the current scope |
Monitor |
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. |
Copy |
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. |
Copy |
Reactive disclosures¶
Procurement¶
CoST IDS element |
Description |
Mapping from OCDS |
---|---|---|
Contract officials and roles |
Name and position of the public official in charge of administration of the contract(s). |
Check the |
Procurement method |
Specify tendering method using the method codelist (open, selective, limited, direct). |
Set |
Tender documents |
Documentation for potential suppliers, describing the goals of the contract (e.g. goods and services to be procured), and the bidding process. |
Check the |
Tender evaluation results |
Documentation on the evaluation of the bids and the application of the evaluation criteria, including the justification for the award. |
Check the |
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. |
Check the |
Contract¶
CoST IDS element |
Description |
Mapping from 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. |
Check the |
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. |
Check the Check the |
Specifications and drawings |
Detailed technical information about goods or services to be provided. |
Check the |
Implementation¶
CoST IDS element |
Description |
Mapping from OCDS |
---|---|---|
List of variations, changes, amendments |
Details of changes to the duration, price, scope or other significant features of the contracting process |
Monitor the following fields for changes:
Copy |
List of escalation approvals |
Documentation of one or more approved escalations of the contract price during the project life-cycle. |
Check the |
Quality assurance reports |
Documentation identifying deficiencies in designs, specifications, standards, methods, procedures and practices, and identifying best practices. |
Check the |
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 |
Copy the contents of the Check the |
Contract amendments |
A legal document that changes or adds to the terms of an existing contract. |
Check the |