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

mapping of notice type information #1469

Closed
odscjen opened this issue Jan 26, 2022 · 2 comments
Closed

mapping of notice type information #1469

odscjen opened this issue Jan 26, 2022 · 2 comments

Comments

@odscjen
Copy link
Contributor

odscjen commented Jan 26, 2022

In the pilot OCDS publication for Canada an additional field has been used, tender/noticeType. The values used within this field are:

  • ["invitation to Tender (ITT)"],
  • [“Advance contract Award Notice (ACAN)”],
  • [“Notice of Proposed Procurement (NPP)”],
  • [“Request for Proposal (RFP)”],
  • [“Request for Quotation (RFQ)”],
  • [“Request for Standing Offer (RFSO)”]

The initial thought was to map to procurementMethodDetails but as these values relate to the tender notice type (as the field name suggests) rather than the contracting process that perhaps wouldn't make sense in the context of a compiled release?

It's therefore unclear how best to map this data. Possibly using tender/documents/documentTypeDetails extension https://gitlab.com/dncp-opendata/ocds_document_type_details?

@jpmckinney
Copy link
Member

Related: #750 #1144

Canada's terms are defined here: https://buyandsell.gc.ca/for-government/buying-for-the-government-of-canada/solicit-bids/types-of-bid-solicitations

These are all different types of procedures (each procedure uses a different initial notice), so procurementMethodDetails would be appropriate.

Right now Canada is using the pair procurementMethod and procurementMethodDetails for:

  • open: All interested suppliers may submit a bid
  • qualified: If 2+ bids offer Canadian goods/services other bids will not be considered
  • qualified: Suppliers on permanent list or able to meet qualification requirements
  • qualified: The bid solicitation document will be sent directly to Conforming Suppliers.

Note that 'qualified' is not an allowed code for procurementMethod. My understanding is that it should be 'selective'.

  • "All interested suppliers may submit a bid" is the description of the 'open' code. This content is not needed.
  • "If 2+ bids offer Canadian goods/services other bids will not be considered" is more like tender.selectionCriteria (a new field scheduled for 1.2). It's an interesting sort of conditional criterion that I haven't seen before.
  • For "Suppliers on permanent list or able to meet qualification requirements", the second clause is the meaning of 'selective', and the first clause is more or less a repetition, since the only way to get on the list is to be qualified. So, this content is not needed.
  • "The bid solicitation document will be sent directly to Conforming Suppliers." This is more about communication, for which we have an extension. In the EU, we modelled restricted access to solicitation documents as a participation fee, though access can be restricted without fees. This might instead involve a change to the communications extension.

So, all told, procurementMethodDetails is the correct mapping, and the content that is currently in procurementMethodDetails either belongs elsewhere or nowhere.

@jpmckinney
Copy link
Member

I've opened an issue for the last bullet: open-contracting/ocds-extensions#178

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

No branches or pull requests

2 participants