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

Bid evaluation publication #1546

Open
yolile opened this issue Sep 8, 2022 · 1 comment
Open

Bid evaluation publication #1546

yolile opened this issue Sep 8, 2022 · 1 comment

Comments

@yolile
Copy link
Member

yolile commented Sep 8, 2022

Currently, with Bid statistics and details extension, the publisher can publish if a bid was accepted or disqualified (among other statuses). However, there is no way to disclose the information about each bid evaluation.

In Argentina, this information is available as structured data. It includes information about each item and tenderer bid evaluation, including the price evaluation, the technical evaluation, and the administrative evaluation (but only for the disqualified bids). All are disclosed as free text but in separate fields, as seen in example 1 and example 2.

For the qualified bids, they suggest an "order of preference" for each bid that should be followed when awarding the process.

Discussion

To disclose this information, we could add a "evaluation" object to the Bid object and model the evaluation here. Another option could be to put this as part of the requirementsResponse object from the requirements extension, and another option is to model this differently in a separate extension.

@jpmckinney
Copy link
Member

jpmckinney commented May 3, 2023

Regarding the requirements extension, in the Core Criterion and Core Evidence Vocabulary (CCCEV) model on which it is based, a Requirement Response is how a bid responds to a requirement.

How a buyer (or bid evaluation committee) evaluates that response is semantically different.

That said, if we have publishers who use the requirements extension and who have detailed, requirement-specific evaluations, then we can integrate with that extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants