Skip to content

README.md: add guidance on expressions of interest #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 30 commits into from
Apr 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
4cbdf4e
README.md: add guidance on using extension for pre-qual responses.
odscjen Dec 4, 2023
4cb4db7
README.md: update line 13
odscjen Dec 4, 2023
cc65155
Merge branch 'master' into 41_pre-qual_guidance
odscjen Dec 5, 2023
e5dbbf7
README.md: change request to participate to expression of interest as…
odscjen Jan 16, 2024
700b084
Merge branch 'master' into 41_pre-qual_guidance
jpmckinney Jan 30, 2024
995bf2e
readme: Copy-edit guidance on expressions of interest
jpmckinney Jan 30, 2024
33fdab8
Merge branch 'master' into 41_pre-qual_guidance
jpmckinney Jan 30, 2024
4fec68d
Merge branch 'master' into 41_pre-qual_guidance
jpmckinney Jan 30, 2024
4235196
metadata: Update extension name and description
jpmckinney Jan 30, 2024
3496e85
Merge branch 'master' into 41_pre-qual_guidance
jpmckinney Jan 30, 2024
018e0a9
add submissionType and codelist and update examples
odscjen Apr 4, 2024
0c9b690
Merge branch 'master' into 41_pre-qual_guidance
odscjen Apr 4, 2024
6fbd346
readme: Fix changelog order (bad merge)
jpmckinney Apr 4, 2024
a84ae2f
readme: Add more references to expressions of interest. Copy-edit.
jpmckinney Apr 4, 2024
4111edf
Apply suggestions from code review
odscjen Apr 9, 2024
67b3cae
review suggests re style guide field descriptions
odscjen Apr 9, 2024
a734425
Merge branch 'master' into 41_pre-qual_guidance
odscjen Apr 10, 2024
639730b
readme: Move changelog entry, and unlist changes to newly added codes
jpmckinney Apr 11, 2024
2cc0c76
bidStatus: Remove "listed" to be consistent with withdrawn code
jpmckinney Apr 11, 2024
24dbf30
release-schema: Parenthesize "(or expressions of interest)" as awards…
jpmckinney Apr 11, 2024
9d1177a
release-schema: Eliminate unnecessary definition
jpmckinney Apr 11, 2024
ea278b2
release-schema: Remove wording that asks publisher to be consistent (…
jpmckinney Apr 11, 2024
377e50a
release-schema: Use "summary statistics" instead of "aggregate statis…
jpmckinney Apr 11, 2024
a939a0c
release-schema(Statistic): Omit sentence relating to a specific field…
jpmckinney Apr 11, 2024
c863bc8
release-schema(bids/details): Avoid listing fields. Omit sentence tha…
jpmckinney Apr 11, 2024
7a8560f
release-schema: Use "submission" in titles
jpmckinney Apr 11, 2024
78c6f4c
release-schema: Remove use of "qualification stage" which does not ex…
jpmckinney Apr 11, 2024
99d3b31
release-schema: Add missing "expression of interest" in `identifiers`…
jpmckinney Apr 12, 2024
1020d28
release-schema(bids/statistics): Match readme wording. readme: Fix ch…
jpmckinney Apr 12, 2024
6d8c299
readme: Fix references to bids.details and .statistics
jpmckinney Apr 12, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 30 additions & 21 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,32 @@
# Bid statistics and details
# Bids and expressions of interest

Information about bids is important for many use cases, including:

* Market analysis, to understand competition
* Red flag analysis, to monitor corruption risk
* Value for money analysis

This extension introduces a top-level `bids` object to describe individual bids and aggregate statistics.
This extension introduces a top-level `bids` object to describe individual bids and expressions of interest (also called requests to participate), and summary statistics.

Depending on the procedure, a bid can be an estimate, offer, proposal, quote or quotation. Regulatory regimes vary on the extent to which they allow information about bids to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders is published in a tender notice, and full details on the bids received are published in an award notice. In other systems, only summary statistics, like the number of bids received, is published.

## Schema

The `bids.details` array is used to provide one or more `Bid` objects, each representing a unique bid received.
### Bids and expressions of interest

The `bids.statistics` array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a `Statistic` object containing at least:
The `bids.details` array contains one or more `Bid` objects, each representing a unique bid or expression of interest.

### Summary statistics

The `bids.statistics` array contains statistical information about the number of bidders, bids and expressions of interest. Each entry in the array is a `Statistic` object containing at least:

* An identifier
* A measure, from the `statistic.csv` codelist
* A value for that measure

The `statistic.csv` codelist is an **open** codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.

For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
The `statistic.csv` codelist is an **open** codelist. Publishers can add their own codes for additional statistics to this codelist: for example, for the number of bids from minority or women-owned businesses. Publishers are encouraged to engage with the OCDS community to agree upon the definitions of new codes.

The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
The codelist's Category column indicates whether the statistic applies to bidders, bids or expressions of interest, or whether it is specified or required by a particular regulatory context (e.g. EU).

## Guidance

Expand All @@ -44,9 +46,13 @@ If a potential supplier submits a bid for multiple lots as a single document, fo

If the bid cannot be divided (for example, the data source describes only the total value of the bid, and not the individual value for each lot within the bid), create one `Bid` object, and add all lots' identifiers to the object's `relatedLots`.

### Expressions of interest

Expressions of interest are also disclosed in the `bids.details` array. Use the `bids.details.submissionType` field to indicate whether a submission is a bid or an expression of interest.

## Examples

Aggregate post-award statistics and individual bid submissions:
Post-award statistics and bid submissions:

```json
{
Expand Down Expand Up @@ -85,6 +91,7 @@ Aggregate post-award statistics and individual bid submissions:
"scheme": "internal"
}
],
"submissionType": "bid",
"items": [
{
"id": "1",
Expand Down Expand Up @@ -119,6 +126,7 @@ Aggregate post-award statistics and individual bid submissions:
"id": "2",
"date": "2016-12-10T01:00:00+01:00",
"status": "disqualified",
"submissionType": "bid",
"value": {
"amount": 1500,
"currency": "USD"
Expand Down Expand Up @@ -173,6 +181,7 @@ A potential supplier submits a bid for two lots as a single document:
"scheme": "internal"
}
],
"submissionType": "bid",
"value": {
"amount": 1000,
"currency": "USD"
Expand All @@ -196,6 +205,7 @@ A potential supplier submits a bid for two lots as a single document:
"scheme": "internal"
}
],
"submissionType": "bid",
"value": {
"amount": 500,
"currency": "USD"
Expand Down Expand Up @@ -231,31 +241,30 @@ Report issues for this extension in the [ocds-extensions repository](https://git
* `Bid.hasRank`
* `Bid.rank`
* `Bid.relatedLots` (moved from the Lots extension)
* `Bid.submissionType`
* `Bid.validityPeriod`
* `Bid.variant`
* `BidsStatistic.valueGross`
* `Award.relatedBids`
* `Contract.relatedBids`
* Add `submissionType.csv` codelist
* Add codes to `statistic.csv`:
* 'microBids'
* 'smallBids'
* 'mediumBids'
* 'disqualifiedBids'
* Change category in `statistic.csv` from 'EU' to 'bids':
* 'electronicBids'
* 'smeBids'
* 'foreignBids'
* Deprecate the `Award.relatedBid` field
* Update and clarify `Statistic.value` field description
* Rename the `BidStatistic` definition to `Statistic`, and remove bid-specific language from its fields' descriptions
* Rename the `bidStatistics.csv` codelist to `statistic.csv`
* Add guidance:
* Correct a bid's value
* Bids submitted for multiple lots
* Change category in `statistic.csv` from 'EU' to 'bids':
* 'disqualifiedBids'
* 'electronicBids'
* 'microBids'
* 'smeBids'
* 'smallBids'
* 'mediumBids'
* 'foreignBids'
* Expressions of interest

### v1.1.5

Expand All @@ -268,16 +277,16 @@ Report issues for this extension in the [ocds-extensions repository](https://git

* Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA.
* Add a 'foreignBidsFromNonEU' code to `bidStatistics.csv`
* Remove invalid `required` property on array field `Bids.details`
* Fix the merge behavior of `Bids.statistics` and `Bid.tenderers` to use identifier merge strategy
* Remove invalid `required` property on array field `bids.details`
* Fix the merge behavior of `bids.statistics` and `Bid.tenderers` to use identifier merge strategy
* Remove Sphinx directives from readme
* Update extension.json for Extension Explorer

### v1.1.3

* Disallow required fields `BidsStatistic.id`, `BidsStatistic.measure`, `BidsStatistic.value` from being null
* Disallow `Bids.statistics` from having null in its array of objects
* Allow `Bids.statistics` to be null
* Disallow `bids.statistics` from having null in its array of objects
* Allow `bids.statistics` to be null
* Add enum to `Bid.status`
* Move `BidsStatistic.requirementResponses` to requirements extension
* Add descriptions to bidStatus.csv
Expand Down
10 changes: 5 additions & 5 deletions codelists/bidStatus.csv
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Code,Title,Description
invited,Invited,A bid has been invited from the listed tenderer(s).
pending,Pending,A bid has been submitted but not yet evaluated.
valid,Valid,The submitted bid met the qualification requirements in order to be evaluated.
disqualified,Disqualified,The submitted bid did not meet the qualification requirements in order to be evaluated.
withdrawn,Withdrawn,The submitted bid was withdrawn by the tenderer(s).
invited,Invited,A bid or expression of interest has been invited from the tenderer(s).
pending,Pending,A bid or expression of interest has been submitted but not yet evaluated.
valid,Valid,The submitted bid or expression of interest met the qualification criteria.
disqualified,Disqualified,The submitted bid or expression of interest did not meet the qualification criteria.
withdrawn,Withdrawn,The submitted bid or expression of interest was withdrawn by the tenderer(s).
2 changes: 1 addition & 1 deletion codelists/statistic.csv
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Category,Code,Title,Description
bids,requests,Requests to participate,The total number of unique requests to participate received
expressionsOfInterest,requests,Expressions of interest,The total number of unique expressions of interest received.
bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage."
bids,disqualifiedBids,Disqualified bids,"The number of bids that were found inadmissible. A bid is found inadmissible where it has been verified that it has been submitted by a tenderer who has been excluded or who did not meet the selection criteria, or when it is not in conformity with the technical specifications, or is irregular (e.g. it was received late, having an abnormally low price or cost), unacceptable or unsuitable."
Expand Down
3 changes: 3 additions & 0 deletions codelists/submissionType.csv
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Code,Title,Description
expressionOfInterest,Expression of interest,"A submission made by a potential supplier describing its qualifications, for the purpose of being invited to submit a bid. This submission is also called a request to participate."
bid,Bid,"A submission made by a potential supplier describing its offer, for the purpose of being awarded a contract. Depending on the procedure, a bid can be an estimate, offer, proposal, quote or quotation."
7 changes: 4 additions & 3 deletions extension.json
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
{
"name": {
"en": "Bid statistics and details"
"en": "Bids and expressions of interest"
},
"description": {
"en": "Adds a bids object to describe individual bids and aggregate statistics."
"en": "Adds a bids object to describe individual bids and expressions of interest, and summary statistics."
},
"documentationUrl": {
"en": "https://extensions.open-contracting.org/en/extensions/bids/"
Expand All @@ -14,7 +14,8 @@
"codelists": [
"statistic.csv",
"bidStatus.csv",
"country.csv"
"country.csv",
"submissionType.csv"
],
"schemas": [
"release-schema.json"
Expand Down
Loading