Planning: Reference price quotes #1625
Labels
Schema: Fields
Relating to adding or deprecating fields in the JSON Schema
Schema
Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.)
Milestone
Split from #599
Examples
As an example from Mexico, see the issue description of #599. (Note: the term "request for quotes" should not be used for this concept, because that term is commonly used to mean a type of invitation to bid.)
Paraguay gathers this information via emails to suppliers (before the tender notice), requesting to fill out a form which then is published as a document within the tender. Email text example: "This quote will be used to average the reference price to be used in the tender process, it will not be taken into account as a bid in the tender process, nor does it represent any commitment for your company." Example (see "Antecedentes de Estimación de Costos")
This might also be relevant to Chile.
Model
In terms of modelling, we'll want to align with existing
tender
andbids/details
models where possible. We should also be informed by what information multiple potential publishers can actually release.Paraguay uses the (machine-translated) terms "cost estimation background" and "background for calculating referential prices".
Paraguay has the fields name, identifier (RUC), date issued (submitted), amount, currency, VAT included (see #817).
Noting that in #1522 there was a question (bullet 3) about adding a role for tenderers who participate in and/or submit to market consultations.
Additional context
A reference price can be determined based on multiple sources.
Here's a list of sources from a guide for medical device procurement:
the buyer and not bundled with the price of the device) prices for medical devices are manufacturer quotes and published lists of ex-factory prices. Procurement teams across states, districts, or counties within a country can be called upon to assist in obtaining these manufacturer quotes.
The text was updated successfully, but these errors were encountered: