Qualification

Only use this extension as part of the OCDS for PPPs profile, as it is not clear that it is consistent with the semantics of OCDS.

This extension adds a preQualification section between planning and tender. It was designed to be used as part of the OCDS for PPPs profile: see the documentation in II.1 and II.2.

Example

{
  "preQualification": {
    "id": "1",
    "title": "Example PPP pre-qualification",
    "status": "active",
    "submissionMethod": [
      "electronicSubmission"
    ],
    "submissionMethodDetails": "Prospective bidders must submit their RFQ responses to the electronic portal at http://eprocurement.example.gov",
    "period": {
      "startDate": "2015-10-31T00:00:00Z",
      "endDate": "2015-11-30T00:00:00Z"
    },
    "enquiryPeriod": {
      "startDate": "2015-10-31T00:00:00Z",
      "endDate": "2015-11-06T23:59:59Z"
    },
    "eligibilityCriteria": "All interested parties are eligible to submit a RFQ response",
    "qualificationPeriod": {
      "startDate": "2015-12-01T00:00:00Z",
      "endDate": "2015-12-01T23:59:59Z"
    },
    "procuringEntity": {
      "id": "XX-GOV-12345678",
      "name": "Ministry of Communications"
    }
  }
}

Issues

Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.

Changelog

2024-03-28

• Abandon in-file translations.

2020-06-04

• Review normative and non-normative words.

2020-04-24

• Add minProperties, minItems and/or minLength properties.

2019-05-01

• Add 'qualifiedBidder' and 'disqualifiedBidder' codes to +partyRole.csv.

2019-03-20

• Set "uniqueItems": true on array fields, and add "minLength": 1 on required string fields.

2019-01-24

• Remove multilingual support for non-existent PreQualification.procurementMethodRationale and PreQualification.awardCriteriaDetails fields.

This extension was originally discussed in open-contracting-extensions/public-private-partnerships#36.