Annotated Revised GPA

This document annotates selected parts of the GPA, with details on how to publish the information using OCDS in a way that is consistent with the rules of the GPA. It is intended for both policy and technical audiences.

Article VII Notices

Notice of Intended Procurement

Reference GPA text OCDS guidance
VII:2 Except as otherwise provided in this Agreement, each notice of intended procurement shall include:
  1. Create an OCDS release

  2. Add 'tender' to the tag array

  3. Set tender/status to 'active'

VII:2(a) the name and address of the procuring entity and other information necessary to contact the procuring entity and obtain all relevant documents relating to the procurement, and their cost and terms of payment, if any;
  1. Add an Organization object to the parties array:

    1. Add 'procuringEntity' to its roles

    2. Enter an identifier in its id, which can be arbitrary as it is primarily to allow referencing from other parts of the file

    3. Enter the name of the procuring entity in its name

    4. Enter the address of the procuring entity in its address

    5. Enter other information necessary to contact the procuring entity in its contactPoint

    6. Add a Classification object to its details/classifications array

      1. Set its scheme to 'gpaCoverageSchedule' (GPA coverage schedule documentation)

      2. Set its id

        • to 'annex1' if the procuring entity is a central government entity

        • to 'annex2' if the procuring entity a sub-central government entity

        • to 'annex3' if the procuring entity is another type of entity

  2. Enter the above identifier in tender/procuringEntity/id

  3. Enter the name of the procuring entity in tender/procuringEntity/name

  4. You can proactively enter the cost and terms of payment of all relevant documents relating to the procurement in tender/participationFees

  5. You can proactively enter any relevant documents relating to the procurement in tender/documents

This requires the Organization Classification and Participation Fees extensions.

VII:2(b) a description of the procurement, including the nature and the quantity of the goods or services to be procured or, where the quantity is not known, the estimated quantity;
  1. Enter a description of the procurement in tender/description

  2. Enter the nature and the quantity of the goods or services to be procured or, where the quantity is not known, the estimated quantity in tender/description or, if possible, split this into Item objects in the tender/items array:

    1. Enter the nature in an item's description and/or unit

    2. Enter the quantity in an item's quantity

The method of representing an estimated quantity is under discussion.

VII:2(c) for recurring contracts, an estimate, if possible, of the timing of subsequent notices of intended procurement;
  1. Set tender/hasRecurrence to true

  2. Enter an estimate, if possible, of the timing of subsequent notices of intended procurement in tender/recurrence/dates

  3. Enter any further information in tender/recurrence/description

This requires the Recurrence extension.

VII:2(d) a description of any options;
  1. Set tender/hasOptions to true

  2. Enter this in tender/options/description

This requires the Options extension.

VII:2(e) the time-frame for delivery of goods or services or the duration of the contract;
  1. If the duration of the contract is disclosed, enter it in tender/contractPeriod

  2. If the time-frame for delivery of goods or services is disclosed, add a Milestone object to the tender/milestones array:

    1. Use 'delivery' for its type

    2. If the time-frame for delivery of goods or services is a specific date, enter it in the object's dueDate or, if it is a time period, enter it in the object's period

The addition of period to the Milestone building block is under discussion.

VII:2(f) the procurement method that will be used and whether it will involve negotiation or electronic auction;
  1. Use 'open', 'selective' or 'limited' for the procurement method that will be used in tender/procurementMethod

  2. If it will involve negotiation, add "negotiated" to tender/procurementMethodDetails

  3. If it will involve electronic auction, set tender/techniques/hasElectronicAuction to true

This requires the Techniques extension.

VII:2(g) where applicable, the address and any final date for the submission of requests for participation in the procurement;
  1. Add a Milestone object to the tender/milestones array:

    1. Use 'requestToParticipate' for its type

    2. Enter any final date for the submission of requests for participation in the procurement in its dueDate

    3. Add the address for the submission of requests for participation in the procurement to its description

VII:2(h) the address and the final date for the submission of tenders;
  1. Enter the final date for the submission of tenders in tender/tenderPeriod/endDate

  2. Add the address for the submission of tenders to tender/submissionMethodDetails

VII:2(i) the language or languages in which tenders or requests for participation may be submitted, if they may be submitted in a language other than an official language of the Party of the procuring entity;
  1. Find the Organization object in the parties array whose id matches tender/procuringEntity/id

  2. Enter the language or languages in which tenders or requests for participation may be submitted in its contactPoint/availableLanguage

This requires the Additional Contact Points extension.

VII:2(j) a list and brief description of any conditions for participation of suppliers, including any requirements for specific documents or certifications to be provided by suppliers in connection therewith, unless such requirements are included in tender documentation that is made available to all interested suppliers at the same time as the notice of intended procurement;
  1. Add a list and brief description of any conditions for participation of suppliers to tender/eligibilityCriteria

  2. If requirements are included in tender documentation that is made available to all interested suppliers:

    1. For each document, add a Document object to the tender/documents array

    2. Set its documentType to 'eligibilityCriteria'

    3. Fill any other known information for the document (Document object schema)

VII:2(k) where, pursuant to Article IX, a procuring entity intends to select a limited number of qualified suppliers to be invited to tender, the criteria that will be used to select them and, where applicable, any limitation on the number of suppliers that will be permitted to tender; and
  1. Enter the number of suppliers that will be permitted to tender in tender.secondStage.maximumCandidates

  2. Add the criteria that will be used to select [the suppliers] to tender.selectionCriteria.description or, if possible, split this into SelectionCriterion objects in the tender/selectionCriteria/criteria array.

  3. If the criteria that will be used to select [the suppliers] are published as documents:

    1. For each document, add a Document object to the tender/documents array

    2. Set its documentType to 'selectionCriteria'

    3. Fill any other known information for the document (Document object schema)

This requires the Second Stage Description and Selection Criteria extensions.

VII:2(l) an indication that the procurement is covered by this Agreement.
  1. Add 'GPA' to tender/coveredBy

This requires the Covered By extension.

Summary Notice

Reference GPA text OCDS guidance
VII:3 For each case of intended procurement, a procuring entity shall publish a summary notice that is readily accessible, at the same time as the publication of the notice of intended procurement, in one of the WTO languages. The summary notice shall contain at least the following information:
VII:3(a)
VII:3(b)
VII:3(c)
the subject-matter of the procurement;
the final date for the submission of tenders or, where applicable, any final date for the submission of requests for participation in the procurement or for inclusion on a multi-use list; and
the address from which documents relating to the procurement may be requested.

The information included in the notice of intended procurement covers all the information included in a summary notice. As such, no OCDS release needs to be published that corresponds to the summary notice.

Notice of Planned Procurement

Reference GPA text OCDS guidance
VII:4 Procuring entities are encouraged to publish in the appropriate paper or electronic medium listed in Appendix III as early as possible in each fiscal year a notice regarding their future procurement plans (hereinafter referred to as "notice of planned procurement"). The notice of planned procurement should include the subject-matter of the procurement and the planned date of the publication of the notice of intended procurement.
  1. Create an OCDS release

  2. Add 'planning' to the tag array

  3. Set tender/status to 'planning'

  4. Enter the subject-matter of the procurement in tender/description. The value of tender/description can be updated when the data described in article VII:2(b) is published.

  5. Enter the planned date of the publication of the notice of intended procurement in tender/communication/futureNoticeDate

  6. If notice regarding their future procurement plans is also published as a document:

    1. Add a Document object to the tender/documents array

    2. Set its documentType to 'plannedProcurementNotice'

    3. Fill any other known information for the document (Document object schema)

This requires the Communication extension.

VII:5 A procuring entity covered under Annex 2 or 3 may use a notice of planned procurement as a notice of intended procurement provided that the notice of planned procurement includes as much of the information referred to in paragraph 2 as is available to the entity and a statement that interested suppliers should express their interest in the procurement to the procuring entity.
  1. Follow the guidance for VII:2.

Article IX Qualification of suppliers

Multi-Use Lists

Reference GPA text OCDS guidance
IX:8 The notice provided for in paragraph 7 shall include:

If you are interested in using OCDS to publish this, please contact mailto:data@open-contracting.org or comment on this GitHub issue.

IX:8(a) a description of the goods or services, or categories thereof, for which the list may be used;
IX:8(b) the conditions for participation to be satisfied by suppliers for inclusion on the list and the methods that the procuring entity will use to verify that a supplier satisfies the conditions;
IX:8(c) the name and address of the procuring entity and other information necessary to contact the entity and obtain all relevant documents relating to the list;
IX:8(d) the period of validity of the list and the means for its renewal or termination, or where the period of validity is not provided, an indication of the method by which notice will be given of the termination of use of the list; and
IX:8(e) an indication that the list may be used for procurement covered by this Agreement.
IX:9 Notwithstanding paragraph 7, where a multi-use list will be valid for three years or less, a procuring entity may publish the notice referred to in paragraph 7 only once, at the beginning of the period of validity of the list, provided that the notice:
IX:9(a) states the period of validity and that further notices will not be published; and
IX:9(b) is published by electronic means and is made available continuously during the period of its validity.

Article X Technical Specifications and Tender Documentation

Tender Documentation

Reference GPA text OCDS guidance
X:7 A procuring entity shall make available to suppliers tender documentation that includes all information necessary to permit suppliers to prepare and submit responsive tenders. Unless already provided in the notice of intended procurement, such documentation shall include a complete description of:
  1. Create an OCDS release

  2. Add 'tenderUpdate' to the tag array

X:7(a) the procurement, including the nature and the quantity of the goods or services to be procured or, where the quantity is not known, the estimated quantity and any requirements to be fulfilled, including any technical specifications, conformity assessment certification, plans, drawings or instructional materials;
  1. For the procurement, including the nature and the quantity of the goods or services to be procured or, where the quantity is not known, the estimated quantity, follow the guidance for VII:2(b)

  2. For any requirements to be fulfilled, including any technical specifications, conformity assessment certification, plans, drawings or instructional materials, append to tender/description.

X:7(b) any conditions for participation of suppliers, including a list of information and documents that suppliers are required to submit in connection with the conditions for participation;
  1. Follow the guidance for VII:2(j)

X:7(c) all evaluation criteria the entity will apply in the awarding of the contract, and, except where price is the sole criterion, the relative importance of such criteria;
  1. Map all evaluation criteria the entity will apply in the awarding of the contract and the relative importance of such criteria to tender.awardCriteriaDetails

  2. If price is the sole criterion, set tender.awardCriteria to 'priceOnly'

X:7(d) where the procuring entity will conduct the procurement by electronic means, any authentication and encryption requirements or other requirements related to the submission of information by electronic means;
  1. Set tender/submissionMethod to 'electronicSubmission'

  2. Enter or append authentication and encryption requirements or other requirements related to the submission of information by electronic means in tender/submissionMethodDetails

  3. If the electronic communication with the procuring entity requires the use of tools and devices that are not generally available, enter the Web address of these tools in tender.communication.atypicalToolUrl

This requires the Communication extension.

X:7(e) where the procuring entity will hold an electronic auction, the rules, including identification of the elements of the tender related to the evaluation criteria, on which the auction will be conducted;
  1. Set tender/techniques/hasElectronicAuction to true

  2. Enter the rules, including identification of the elements of the tender related to the evaluation criteria, on which the auction will be conducted in tender/techniques/electronicAuction/description

This requires the Techniques extension.

X:7(f) where there will be a public opening of tenders, the date, time and place for the opening and, where appropriate, the persons authorized to be present;
  1. Enter the date and the time in tender/bidOpening/date

  2. Enter the place in tender/bidOpening/address, tender/bidOpening/location or tender/bidOpening/gazetteer

  3. Enter the persons authorized to be present in tender/bidOpening/description

This requires the Bid Opening extension.

X:7(g) any other terms or conditions, including terms of payment and any limitation on the means by which tenders may be submitted, such as whether on paper or by electronic means; and
  1. Enter the terms of payment in tender/participationFees

  2. Enter the means by which tenders may be submitted in tender/submissionMethod:

    1. If it's on paper, enter 'written'

    2. If it's by electronic means, enter 'electronicSubmission'

This requires the Participation Fees extension.

X:7(h) any dates for the delivery of goods or the supply of services
  1. Follow the guidance for VII:2(e)

X:9 The evaluation criteria set out in the notice of intended procurement or tender documentation may include, among others, price and other cost factors, quality, technical merit, environmental characteristics and terms of delivery
  1. Enter the evaluation criteria set out in the notice of intended procurement or tender documentation in tender/awardCriteriaDetails

  2. If the evaluation criteria are published as a document:

    1. Add a Document object to the tender/documents array

    2. Set its documentType to 'evaluationCriteria'

    3. Fill any other known information for the document (Document object schema)

Modifications

Reference GPA text OCDS guidance
X:11 Where, prior to the award of a contract, a procuring entity modifies the criteria or requirements set out in the notice of intended procurement or tender documentation provided to participating suppliers, or amends or reissues a notice or tender documentation, it shall transmit in writing all such modifications or amended or re-issued notice or tender documentation: (a) to all suppliers that are participating at the time of the modification, amendment or re-issuance, where such suppliers are known to the entity, and in all other cases, in the same manner as the original information was made available; and (b) in adequate time to allow such suppliers to modify and re-submit amended tenders, as appropriate.
  1. Create a new OCDS release and follow the corresponding guidance, depending on the information that has been modified:

    1. If the the criteria or requirements are modified, follow the guidance for X:9, and add 'tenderAmendment' to the tag array

    2. If a notice (of intended procurement) is amended or reissued, follow the guidance for VII:2, but instead add 'tenderAmendment' to the tag array

    3. If the tender documentation is amended or reissued, follow the guidance for X:7, but instead add 'tenderAmendment' to the tag array

Article XIII Limited Tendering

Reference GPA text OCDS guidance
XIII:2 A procuring entity shall prepare a report in writing on each contract awarded under paragraph 1. The report shall include the name of the procuring entity, the value and kind of goods or services procured and a statement indicating the circumstances and conditions described in paragraph 1 that justified the use of limited tendering.
  1. Create an OCDS release

  2. Add 'award' to the tag array

  3. Set tender/status to 'complete'

  4. If the following data has not been published following the guidance for VII:2

    1. For the name of the procuring entity, follow the guidance for VII:2(a)

    2. For the kind of goods or services procured, follow the guidance for VII:2(b)

  5. Add an Award object to the awards array

    1. Enter an identifier in its id, which can be arbitrary as it is primarily to allow referencing from other parts of the file

    2. Enter the kind of goods or services procured in its description or, if possible, split it into Item objects in its items array.

    3. Enter the value [of the goods or services] in its value/amount

    4. Enter the currency in value/currency (see the currency codelist)

    5. If the report in writing is also published as a document

      1. Add a Document object to its documents array

      2. Set its documentType to 'awardNotice'

      3. Fill any other known information for the document (Document object schema)

  6. Enter the circumstances and conditions described in paragraph 1 that justified the use of limited tendering in tender/procurementMethodRationale

Article XIV Electronic Auctions

Reference GPA text OCDS guidance
XIV:1 Where a procuring entity intends to conduct a covered procurement using an electronic auction, the entity shall provide each participant, before commencing the electronic auction, with:
XIV:1(a) the automatic evaluation method, including the mathematical formula, that is based on the evaluation criteria set out in the tender documentation and that will be used in the automatic ranking or re-ranking during the auction;
  1. Create an OCDS release

  2. Enter or append the automatic evaluation method, including the mathematical formula in tender/techniques/electronicAuction/description

XIV:1(b) the results of any initial evaluation of the elements of its tender where the contract is to be awarded on the basis of the most advantageous tender; and
  1. If the results of any initial evaluation of the elements of [each participant's] tender are published as a document:

    1. Add a Document object to the award's documents array

    2. Set its documentType to 'evaluationReports'

    3. Fill any other known information for the document (Document object schema)

XIV:1(c) any other relevant information relating to the conduct of the auction.
  1. Enter or append any other relevant information relating to the conduct of the auction in tender/techniques/electronicAuction/description

Article XVI Transparency of Procurement Information

Publication of Award Information

Reference GPA text OCDS guidance
XVI:2 Not later than 72 days after the award of each contract covered by this Agreement, a procuring entity shall publish a notice in the appropriate paper or electronic medium listed in Appendix III. Where the entity publishes the notice only in an electronic medium, the information shall remain readily accessible for a reasonable period of time. The notice shall include at least the following information:
XVI:2(a) a description of the goods or services procured;
  1. Create an OCDS release

  2. Add 'award' to the tag array

  3. Set tender/status to 'complete'

  4. Add an Award object to the awards array

    1. Enter an identifier in its id, which can be arbitrary as it is primarily to allow referencing from other parts of the file

    2. Enter the description of the goods or services procured in its description or, if possible, split it into Item objects in its items array.

XVI:2(b) the name and address of the procuring entity;
  1. Follow the guidance for VII:2(a)

XVI:2(c) the name and address of the successful supplier;
  1. Add an Organization object to the parties array:

    1. Add 'supplier' to its roles

    2. Enter an identifier in its id, which can be arbitrary as it is primarily to allow referencing from other parts of the file

    3. Enter the name in its name

    4. Enter the address in its address

  2. Add an OrganizationReference object to the award's suppliers array:

    1. Enter the organization id of the supplier in its id

    2. Enter the name of the supplier in its name

XVI:2(d) the value of the successful tender or the highest and lowest offers taken into account in the award of the contract;
  1. Enter the value of the successful tender in the award's value/amount

  2. Enter the currency in the award's value/currency (see the currency codelist

  3. For the highest offer taken into account in the award of the contract, add a BidsStatistic object to the bids/statistics array:

    1. Enter an identifier in its id, which can be arbitrary as it is primarily to allow referencing from other parts of the file

    2. Enter the value of the offer in its value

    3. Enter the currency of the offer in its currency

    4. Set its measure to highestValidBidValue

  4. For the lowest offer taken into account in the award of the contract, repeat the above guidance and set measure to lowestValidBidValue

XVI:2(e) the date of award; and
  1. Enter the date of the award in the award's date

XVI:2(f) the type of procurement method used, and in cases where limited tendering was used in accordance with Article XIII, a description of the circumstances justifying the use of limited tendering.
  1. For the type of procurement method used, follow the guidance for VII:2(f)

  2. For description of the circumstances justifying the use of limited tendering, follow the guidance for XIII:2

Collection and Reporting of Statistics

Reference GPA text OCDS guidance
XVI:4 Each Party shall collect and report to the Committee statistics on its contracts covered by this Agreement. Each report shall cover one year and be submitted within two years of the end of the reporting period, and shall contain:

If you are interested in calculating statistics using OCDS data, please contact mailto:data@open-contracting.org or comment on this GitHub issue.

In the meantime, you might be interested in this Python notebook, which demonstrates how to calculate statistics using Australia's data.

XVI:4(a) for Annex 1 procuring entities:
XVI:4(a)(i) the number and total value, for all such entities, of all contracts covered by this Agreement;
XVI:4(a)(ii) the number and total value of all contracts covered by this Agreement awarded by each such entity, broken down by categories of goods and services according to an internationally recognized uniform classification system; and
XVI:4(a)(iii) the number and total value of all contracts covered by this Agreement awarded by each such entity under limited tendering;
XVI:4(b) for Annex 2 and 3 procuring entities, the number and total value of contracts covered by this Agreement awarded by all such entities, broken down by Annex; and
XVI:4(c) estimates for the data required under subparagraphs (a) and (b), with an explanation of the methodology used to develop the estimates, where it is not feasible to provide the data.