Publication Policies
Data User Guide [Cross River State Government]
For data published using the Open Contracting Data Standard
The Open data policy of the Government of Cross River state of Nigeria commenced in the year 2021 with the launch of the current e-procurement portal [ http://dppib- crsgov.org ].
The procurement and contracting procedure carried out in the state is implemented through the computerized registry system for procurement within the scope of the Cross River State Due Process and Price Intelligence Bureau along with its regulatory decree. decree.
The adoption of the Open Contracting Data Standard (OCDS) was a challenge for the State Government as it involved reviewing its current procurement processes and translating them to the standard provided by the Open Contracting Partnership. This contributed to the transparency and public integrity policy that is being carried out.
The publication of purchases and contracts in an Open format and with the Open Contracts Standard was thanks to the joint work between the Cross River State Government and Due Process and Price Intelligence Bureau
Purpose of publication
The Open Contracting Data Standard (OCDS) is a global data standard that promotes the disclosure of data and documents at all stages of the contracting process. This standard has been developed for information providers to share structured, standardized and reusable data.
The publication of the procurement data at [ http://dppib- crsgov.org ]. is to ensure that all information on public procurement of the Cross River State Government and its Ministry Department Agencies (MDA) are accessible online and in open formats for the perusal, use, reuse and redistribution by all interested party.
Uses of the data
Cross River State Government is working together with Due Process and Price Intelligence Bureau to use open contracting data to:
- deliver better value for government funds,
- create fairer competition and a level playing field for business,
- drive higher quality goods, works and services for citizens.
- prevent fraud and corruption
- Promote evidence-based decision making
- promote smarter analysis and better solutions for public problems
Creation of OCDS datasets
The Cross River State Due Process and Price Intelligence Bureau (CRSDPP),acts as the reviewBody according to OCDS Organization/Parties role code-list I.e the legal Entity with the permission for the complete extraction and overview of Cross River State Procurement database that includes the three stages of purchasing and contracting process, contracting modality.
The data available in this publication contains two different set of data collection method. First is the manually collected backlog procurement datasets mapped to OCDS source fields. Another is the e-procurement system auto generated datasets
Manually Collected Datasets
These datasets were collected using custom built forms, spreadsheet templates etc. to collate backlog data of past executed contract projects spilled into the year 2020 or procured in the same year 2020.
These datasets do not include real time contracting information but captures brief summary of each contracting stages for each executed projects.
Auto generated e-Procurement datasets
This method generates and updates reports gathered from contracting data entered into the e-Procurement platform. Different fields collected within the source system is mapped to OCDS data field. The information is pulled from our main data store and and converted into OCDS version which is being indexed for search and downloads.
The published data is refreshed nightly through a process which pulls it from our main data store, converts it to OCDS version and indexes it for search, view and download. The information available from [ http://dppib- crsgov.org ].is subject to these updates, which updates itself in real time next to the commencement or completion of a milestone. The following diagrams show a non extensive approach we use to generate OCDS data.
With this Modular approach we use a single API to maintain and to call for third party systems. With this approach, complex or high volume APIs calls do not add additional load on live system and with this implemented approach, it is possible to share and re-use open code for providing the data store and API.
Accessing the data
Cross River State Government makes OCDS data available in various formats to meet the needs of different users. The following formats are available:
| Format | Description | Link(s) |
|---|---|---|
| Bulk OCDS release download (JSON) | Annual files segmented by release date Suitable for analysis and/or storage in a document database | [ http://dppib- crsgov.org ]. |
| Bulk OCDS record download (JSON) | Annual files segmented by initial release date Suitable for analysis and/or storage in a document database | [ http://dppib- crsgov.org ]. |
| Bulk OCDS release download (CSV) | Annual files containing a multi-table CSV serialization of OCDS data, segmented by release date and OCID Suitable for analysis in spreadsheet software and/or storage in a relational database. | [ http://dppib- crsgov.org ]. |
| Bulk OCDS record download (CSV) | Annual files containing a multi-table CSV serialization of OCDS data, segmented by release date and OCID Suitable for analysis in spreadsheet software and/or storage in a relational database. | [ http://dppib- crsgov.org ]. |
| Release API (JSON) | Programmatic API with query parameters for ocid, release id, release date and buyer. Suitable for access by digital tools to obtain recently updated data or to download a subset of data | [ http://dppib- crsgov.org ]. |
| Record API (JSON) | Programmatic API with query parameters for ocid and buyer. Suitable for access by tools, to obtain recently updated data or to download a subset of data | http://ocdsapi.dppib-crsgov.org/api/ocdsAPI/getReleasePackageFile?id=year&month E.g. http://ocdsapi.dppib-crsgov.org/api/ocdsAPI/getRecordPackageFile?id=202106 |
Cross River State Government provides an open contracting portal to support exploration and use of contracting data at the following URL: http://dppib-crsgov.org/ The portal provides filters and visualizations to help users explore the stages (releases) of the contracting process.
Other Contracting data
We previously published backlog or past Cross River State executed procurement datasets dating from 2020 active project in written format. OCDS data is now our [primary / sole / focus] publication method for procurement data, and we are discontinuing publication of our previous releases in written format and making it available in API, JSON, CSV formats all in accordance to OCD Standards
Data Resources
The information on the purchasing and contracting system is published here https://ocds.dppib-crsgov.org
JSON structure sample
Files with JSON format that contains the information of all the purchasing processes published in their different stages (call, award, contracting, participants). For each purchase process an OCID (Open Contracting Identifier) is assigned, to all information referring to the stages through which the associated process passes.
PLANNING
File in JSON, CSV (comma, separated, values) format with the information on budget source, budget amount, rationale for budget, reference budget document for all purchases and contracting processes managed through the system.
| Section | Qualification | Description | Kind |
|---|---|---|---|
| Planning | Plan title | A title for this Plan | string |
| Planning | Description of the plan | A summary of the line items captured in during the Plan stage | string |
| Planning | Planning Rationale | This the reason behind the plan. This mostly denotes the factor to which a a tender should be initiated. | string |
| Planning | Budget | This refers to the total amount allocated to carry out the contracting process. | object |
| Planning | Budget Source | This refers to the source/origin of funds, this could government raised funds, crowdfunding, donations e.t.c. | string |
| Planning | Documents | The planning document captures all stages of the planning process extensively which could be in various supported formats to be referenced in time. | string |
TENDER
File in JSON, CSV (comma, separated, values) format with the information on call for participants for all purchasing and contracting processes managed. It contains the details of the bidding documents and conditions (dates, amounts, organizations), the web documents where the information is published and the items to be contracted.
| Section | Qualification | Description | Kind |
|---|---|---|---|
| Tender | Tender title | A title for this tender. This will be used by applications as a header to attract interest and help analysts understand the nature of this engagement. | string |
| Tender | Description of the tender | A summary description of the tender. This will complement structured information provided using the items array. | string |
| Tender | Bid status | The current status of the tender based on the tender status code list | string |
| Tender | Contracting entity | The entity that manages the hiring process. This may be different from the buyer who pays / uses the purchased items. | object |
| Tender | Organization name's | The name of the stakeholder that is being referenced. This must be the same as the name of an entry in the participants section | string |
| Tender | Organization ID | The id of an involved party that is referenced. This must be equal to the id of an entry in the section of parties involved. | string, integer |
| Tender | Items to be purchased | The goods and services to be purchased, divided into types of items of a pre-exist classification when possible. Items should not be duplicated, instead a quantity of 2 should be specified.t | array |
| Tender | ID | A local identifier to refer to and with which to link the articles. It is unique in relation to the other items of the same contracting process present in the article matrix. | string, integer |
| Tender | Description | A description of the goods or services that are the object of the contracting procedure. | string |
| Tender | Item Classification | The primary classification for items in our publication is the UNSPSC classification. A classification consists of two parts; an identifier for the list (schema) from which the classification is drawn, and an identifier for the category of that list that is applied. It is also useful to post a text tag and / or a URI that users can use to interpret the ranking. | object |
| Tender | Scheme | A classification must be taken from an existing code list or scheme. This field is used to indicate the scheme / code-list from which the classification is taken. For articles or items of a pre-exist classification, this value should represent a known Article Classification Scheme when possible. | string |
| Tender | ID | The classification code taken from a selected schema. | string, integer |
| Tender | Quantity | The number of units required | number |
| Tender | Unit | A description of the unit in which the supplies, services or works are provided (e.g hours, kilograms) and the unit-price. For comparability, an established list of units can be used. | object |
| Tender | URL | direct link to the document or attachment. The server providing access to this document should be configured to correctly report the document mime type. | string |
| Tender | Publication date | The publication date of the document. This is particularly important for legally relevant documents, such as tender notices. | string |
Award
File in JSON, CSV format with the information of the purchasing processes. It incorporates the detail of the documents published after the award and the items awarded.
| Section | Qualification | Description | Kind |
|---|---|---|---|
| Award | Award ID | The identifier of this award. This is a unique code that cannot change within the Open Contracting Process of which it is part (defined by a single ocid). See the identifier guide for more details. | string, integer |
| Award | Title | Award title | string |
| Award | Description | Description of the award | string |
| Award | Award Status | The current status of the award taken from the award Status codelist | string |
| Award Status | Value | The total value or amount of this award. In the case of a framework contract, this can be the estimate of the total value or maximum value of the agreement. There may be more than one award per hiring process. A negative value indicates that the award may involve payments from the supplier to the buyer (commonly used in concession contracts).Financial values must always be published paired with a currency. | object |
| Award | Amount | The amount as a figure. | number |
| Award | Currency | The currency for each amount should always be specified using the ISO4217 3-letter currency code in capital letters. | string |
| Award | ID | A local identifier to refer to and with which to link the articles. It must be unique in relation to the other items of the same contracting process present in the article matrix. | string, integer |
| Award | Description | A description of the goods or services that are the object of the contracting procedure. | string |
| Award | Classification | The primary classification for the article. See the itemClassificationScheme to identify preferred classification lists, including CPV and GSIN. | object |
| Award | Scheme | A classification must be taken from an existing code list or scheme. This field is used to indicate the scheme / codelist from which the classification is taken. For articles or items of a pre-existing classification, this value should represent a known Article Classification Scheme when possible. | object |
| Award | ID | The classification code taken from a selected schema. | string, integer |
| Award | Quantity | The number of units required | number |
| Award | Unit | A description of the unit in which the supplies, services or works are provided (eg hours, kilograms) and the unit-price. For comparability, an established list of units can be used. | object |
| Award | Scheme | The list from which the unit of measure identifiers are taken. This should be an entry taken from the options available in the unit ClassificationScheme codelist. The use of the "UNCEFACT" scheme is recommended for UN-CEFACT Recommendation 20. The list of "Codes for units of measurement used in international trade" is recommended, although other options are available. | string |
| Award | Name | Name of the unit. | string |
| Award | Value | The monetary value of a unit | object |
| Award | Value | Financial values must always be published paired with a currency. | object |
| Award | Amount | The amount as a figure. | number |
| Award | Currency | The currency for each amount should always be specified using the ISO4217 3-letter currency code in capital letters. | string |
| Award | Contract period | The period for which the contract has been awarded. | object |
| Award | Period | Milestones during a hiring process can have a known start date, end date, duration, or maximum scope (the last date the period can be extended). In some cases, not all of these fields will have known or relevant values. | object |
| Award | Duration (days) | The maximum duration of this period in days. A user interface may want to get or display this data in months or years, but must convert it to days when this field is filled. The field can be used when exact dates are not known. When a startDate and endDate are provided, this field is optional and should reflect the difference between those two days. When a startDate and maxExtentDate are provided, this field is optional and should reflect the difference between startDate and maxExtentDate. | integer |
| Award | Documents | All documents and attachments related to the award, including any notices or notices. | array |
| Award | ID | Local and unique identifier for this document. This field is used to keep track of the multiple versions of a document in the process of creating a record of the contracting process (record) that is generated from the deliveries (release). | string, integer |
| Award | Document type | A classification of the described document taken from the documentType codelist. Values from the provided codelist should be used whenever possible, although extended values can be provided if the codelist does not have a relevant code. | string |
| Award | URL | direct link to the document or attachment. The server providing access to this document should be configured to correctly report the document mime type. | string |
| Award | Publication date | The publication date of the document. This is particularly important for legally relevant documents, such as tender notices. | string |
Contract
File in CSV format with the information of the contracts signed by the parties participating in the process. It contains the detail of the amount actually disbursed by the departments of the GCBA, the items contracted, the contracting terms.
| Section | Qualification | Description | Kind |
|---|---|---|---|
| Contract | Contract ID | The identifier for this contract. It must be unique and cannot change during your Open Contract Process (defined by a single ocid). See the identifier guide for more details. | string, integer |
| Contract | Award ID | The award identifier (award.id) against which this contract is being issued. | string, integer |
| Contract | Contract title | Contract title | string |
| Contract | Description of the contract | Description of the contract | string |
| Contract | Contract Status | The current status of the contract. Taken from the contractStatus code list | string |
| Contract | Period | The start and end dates of the contract. | object |
| Contract | Period | Milestones during a hiring process can have a known start date, end date, duration, or maximum scope (the last date the period can be extended). In some cases, not all of these fields will have known or relevant values. | object |
| Contract | Start date | The start date of the period. When known, a precise start date must be provided. | string |
| Contract | Ending date | The end date of the period. When known, a termination date must always be provided. | string |
| Contract | Duration (days) | The maximum duration of this period in days. A user interface may want to get or display this data in months or years, but must convert it to days when this field is filled. The field can be used when exact dates are not known. When a startDate and endDate are provided, this field is optional and should reflect the difference between those two days. When a startDate and maxExtentDate are provided, this field is optional and should reflect the difference between startDate and maxExtentDate. | integer |
| Contract | Value | A total value or amount of this contract. A negative value indicates that the contract will involve payments from the supplier to the buyer (commonly used in concession contracts). | object |
| Contract | Value | Financial values must always be published paired with a currency. | object |
| Contract | Amount | The amount as a figure. | number |
| Contract | Currency | The currency for each amount should always be specified using the ISO4217 3-letter currency code in capital letters | string |
| Contract | Contracted Items | The goods, services and any intangible results of this contract. Note: Do not repeat if the items are the same as the award. | array |
| Contract | ID | A local identifier to refer to and with which to link the articles. It must be unique in relation to the other items of the same contracting process present in the article matrix. | string, integer |
| Contract | Description | A description of the goods or services that are the object of the contracting procedure. | string |
| Contract | Classification | The primary classification for the article. See the itemClassificationScheme to identify preferred classification lists, including CPV and GSIN. | object |
| Contract | Classification | A classification consists of at least two parts: an identifier for the list (schema) from which the classification is drawn, and an identifier for the category of that list that is applied. It is also useful to post a text tag and / or a URI that users can use to interpret the ranking. | object |
| Contract | Scheme | A classification must be taken from an existing code list or scheme. This field is used to indicate the scheme / codelist from which the classification is taken. For articles or items of a pre-existing classification, this value should represent a known Article Classification Scheme when possible. | string |
| Contract | ID | The classification code taken from a selected schema. | string, integer |
| Contract | Quantity | The number of units required | number |
| Contract | Unit | The detail of the unit in which the good or service is provided (units, hours, kilograms). | object |
| Contract | Scheme | The list from which the unit of measure identifiers are taken. This should be an entry taken from the options available in the unitClassificationScheme codelist. The use of the "UNCEFACT" scheme is recommended for UN-CEFACT Recommendation 20. The list of "Codes for units of measurement used in international trade" is recommended, although other options are available. | string |
| Contract | Name | Name of the unit. | string |
| Contract | Value | The monetary value of a unit. | object |
| Contract | Value | Financial values must always be published paired with a currency. | object |
| Contract | Amount | The amount as a figure. | number |
| Contract | Currency | The currency for each amount should always be specified using the ISO4217 3-letter currency code in capital letters. | string |
| Contract | Signature Date | The date the contract was signed. In the case of multiple signatures, the date of the last signature. | string |
| Contract | Contract signatories | Detail of the parties signing the contract for the provision of goods or services. It consists of a contracting entity and another provider. | string |
| Contract | Name of signatory | Entity name | string |
| Contract | Signer id | Entity identifier | string |
Parties
CSV format file that contains the details of the participating parties (suppliers, buyers, purchasing units) of each of the purchasing processes managed through the system.
| Section | Qualification | Description | Kind |
|---|---|---|---|
| Parties | Common name | A common name for this organization or another participant in the recruitment process. The "Principal Identifier" object provides a space for the legal name or company name; this attribute can repeat that value or it can provide the common name by which this entity or organization is known. This field can also include details of the department or sub-unit involved in this hiring process. | string |
| Parties | Entity ID | The ID used to refer to this stakeholder from other sections of the release. This field can be constructed with the following structure {identifier.scheme} - {identifier.id} (- {department-identifier}). | string |
| Parties | Primary identifier | The primary identifier for this organization or participant. Identifiers that uniquely denote a legal entity are preferable. See the org identifier guide for the preferred identifier and schema. | object |
| Parties | Identifier | A unique identifier for a stakeholder (organization). | string |
| Parties | Scheme | Organization identifiers can be taken from an existing identifier list. This field is used to indicate the scheme or codelists in which the identifier will be found. This value must be taken from the Organization Identification Scheme. | string |
| Parties | ID | The identifier of the organization in the selected schema. | string, integer |
| Parties | Legal name | The legally registered name of the organization. | string |
| Parties | Address | The street address. For example: 1600 Amphitheater Pkwy. | string |
| Parties | Location | The location. For example: Obudu resort, calabar | string |
| Parties | Postal Code | The zip code. For example: 94043 | string |
| Parties | Country | The name of the country. For example: Nigeria | string |
| Parties | Name | The name of the contact person, department or point of contact in relation to this hiring process. | string |
| Parties | The email address of the contact point or person | string | |
| Parties | Telephone | The telephone number of the contact point or person. This must include the international dialing code. | string |
| Parties | URI | .A URI to identify the organization, such as those provided by Open Corporate or some other relevant URI provider. This field should not be used to specify the organization's website, which can be specified in the URL field of the Organization's point of contact. | string |
| Parties | Roles of the parties | The roles of the parties involved in the hiring process. The role (s) must be taken from the partyRole codelist. Values provided in the codelist should be used when possible, although extended values can be used if the codelist does not have a relevant code. | string |
Data Scope
| Dates | Data published here includes project whose contract status remains active from the year 2020 and onwards |
| Buyers | The Federal, state and local government agencies procure goods, works or services for, with or on behalf of the Cross River State Government. |
| Values | Federal government, State government and Local government does not have a contracts value below or above which the contracting data is excluded. |
| Process types | Open, selective and direct tenders for purchases, including Public Private Partnerships. |
| Stages | We publish tender and awards data for each contracting process. In addition to this we also provide the contract stage where available in our current scope, we publish financial implementation |
| Change History | A change history for each contracting process is provided through releases associated with each contract’s id (OCID). This publish is updated in real time per milestone set/met |