Skip to content
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

How to to represent disqualified tenderers #763

Closed
jpmckinney opened this issue Nov 1, 2018 · 3 comments
Closed

How to to represent disqualified tenderers #763

jpmckinney opened this issue Nov 1, 2018 · 3 comments
Labels
question Questions with no impact on the standard or documentation
Milestone

Comments

@jpmckinney
Copy link
Member

jpmckinney commented Nov 1, 2018

The Kyrgyz Republic combines qualification and award into one action. Disqualified bidders have an 'award decision' document. To disambiguate unsuccessful awards (which means unsuccessful for any reason besides cancellation) from disqualified bidders, it was proposed to add a 'disqualified' status, or to put 'disqualified' under a new statusDetails field. This issue also arose in Ukraine. In both cases, there is a 'decision protocol', which contains information on (1) who is the winner and (2) who was disqualified during evaluation.

This issue might require more research into how to represent qualification in OCDS, to give this publisher an option to express this information separately from awards.

@jpmckinney jpmckinney added Schema Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.) Codelist: Closed Relating to a closed codelist and removed Schema Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.) labels Nov 1, 2018
@MusicMaker1337
Copy link

It may be better to separate the status of the award decision from the decision itself because these are totally different concepts.

Imagine a situation, where the procuring entity decided to disqualify a bidder, but then changed its mind and canceled the decision. Tn this case the decision 'disqualified' itself did not change at all, but the status of that decision changed: "I cancel my disqualification decision".

Maybe there can be an awardDecision object, which would have two separate fields: status for the decision status (the same as award.status) and decision for the decision itself.

@jpmckinney
Copy link
Member Author

jpmckinney commented Nov 28, 2018

This might involve finding a way to make the following extension backwards-compatible with OCDS and available for wider use: https://github.com/open-contracting/ocds_qualification_extension

@jpmckinney jpmckinney added this to the 1.2 milestone Nov 29, 2018
@jpmckinney
Copy link
Member Author

Looking back at this issue, we already have a Bid extension, in which a particular tenderer's bid can be given a status of 'disqualified'.

Different jurisdictions will disclose disqualifications at different points in their process (whether in an award decision, after opening the first envelope only, etc.). However, conceptually, disqualification means the same thing. As such, I think all jurisdictions can use a common model using the bids extension.

Happy to re-open to consider any disadvantages.

@jpmckinney jpmckinney changed the title awardStatus: Discussion of 'disqualified' status How to to represent disqualified tenderers Jul 17, 2020
@jpmckinney jpmckinney added question Questions with no impact on the standard or documentation and removed Codelist: Closed Relating to a closed codelist labels Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions with no impact on the standard or documentation
Projects
Archived in project
Development

No branches or pull requests

2 participants