Add a field to indicate a project's procurement approach

[duncandewhurst]

SIF's SOURCE platform includes:

• a boolean isPPP/concession field with the following semantics:

  Whether the project intended to be tendered as a PPP/Concession or as a traditional procurement

• a boolean Unsolicited Project field, to indicate whether a project resulted from an unsolicited proposal.

[jpmckinney]

In OCDS, this would usually be communicated as tender/procurementMethodDetails in a planning release, to describe the intended procedure.

From #249: In OCDS, this would broadly fall under the semantics of tender/procurementMethodDetails (the name of the field obviously not being friendly to non-procurement contracts).

We can consider renaming the field for OC4IDS, since its values are broader than in OCDS.

[duncandewhurst]

My understanding is that, in SOURCE, this information relates to planning the project as a whole so there likely wouldn't be any entries in the contractingProcesses array at that stage.

[jpmckinney]

Like #249, I meant in terms of an analogue that can be added to the Project object.

[duncandewhurst]

ANZIP includes a Procurement Approach field which mixes various concepts but includes some values relevant to this issue:

• Market Led Proposal
• Confirmed PPP
• Traditional Procurement
• Possible PPP
• Alliance
• Privatisation
• Unconfirmed
• Operations & Maintenance
• Power Purchase Agreement

[duncandewhurst]

Like #249, I meant in terms of an analogue that can be added to the Project object.

Adding an example, based on SOURCE's data:

{
  "projects": [
    {
      "procurementMethodDetails": "Unsolicted proposal"
    }
  ]
}