-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add Bid section to Tender #197
Comments
There is a clear proposal at http://api-docs.openprocurement.org/en/latest/standard/bid.html which we should consider, work up and test with data from Mexico City and other contexts. (cc @myroslav - any learning from use of your bid section we should take into account?) |
Our procurement process has no pre-qualification and so called self-declaration principle is employed. i.e. it is assumed that all bidders are able to provide qualification The winner (and only the one) is able to provide her extra qualification The other not-so-smooth part was bid There is only single element in Bid These are the most important elements of Bid in our procurement process. |
Bidding information is also desired in Taiwan, where draft data includes a block along the lines below, capturing failed bids:
|
I've not had time to work up a full schema here yet, but as a quick example of what a bids block could look like which would fit with the current approach in Ukraine, and potentially help model the Taiwan data, here's an example: {"bids":[
{
"id":"123",
"date":"2015-12-05T13:11:59+00:00",
"tenderers":[{ }],
"status":"failed",
"statusDetails":"",
"value": {
"amount":12356.00,
"currency":"USD"
},
"documents":[]
}
]
} In this case, the data above from Taiwan could be modelled as: {"bids":[
{
"id":"1",
"status":"failed",
"statusDetails":"資格、規格合於招標文件但非最低(高)標",
},
{
"id":"2",
"status":"failed",
"statusDetails":"資格、規格合於招標文件但非最低(高)標",
},
]
} |
Developed in #379 |
Bidding information was not included in the 1.0 RC due to a range of different proposals. There is however demand to be able to express bidding information
Based on discussions in #78 we should provide an updated bidding schema proposal and work this up as an extension.
The text was updated successfully, but these errors were encountered: