Australia: New South Wales: Treasury

The Treasury of New South Wales (NSW) is responsible for NSW eTendering, the system used by NSW government agencies to publish information about procurement opportunities and concluded contracts.

According to the NSW Procurement Policy Framework, all NSW government agencies, excluding state-owned corporations and local councils, must publish the following on eTendering:

  • All open tenders
  • All procedures with an estimated value at or above the following thresholds, except when using a list of pre-qualified suppliers or when limited tendering is exceptionally allowed:
    • $680,000 for goods and services
    • $9,584,000 for works
  • All contracts with a value at or above $150,000 (including VAT) within 45 working days of being concluded

Accredited agencies must also publish an annual procurement plan on eTendering.

Available formats:
JSON
Excel
CSV

Overview

Data date range:
Dec 2005 - Nov 2024
Update frequency:
Real time
Main language:
English
OCID prefix:
ocds-43qwtd
License:
Creative Commons Attribution 3.0 Australia (CC BY 3.0 AU)

You are free to:

  • Share — copy and redistribute the material in any medium or format
  • Adapt — remix, transform, and build upon the material for any purpose, even commercially.

The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

  • Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  • No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
Publication policy:
-
Last retrieved:
Dec 2024 (retrieved monthly)
Retrieved from:
https://github.com/NSW-eTendering/NSW-eTendering-API/wiki

Data available

A contracting process has several stages: tendering, awarding, contracting and implementation. You can learn about the contracting stages in this tutorial.

Parties

Count of parties:
0

Planning

Count of planning activities:
0

Tenders

Count of tenders:
29,387
Count of tenderers:
66,091
Count of tender items:
29,388

Awards

Count of awards:
16,262
Count of suppliers:
16,262
Count of award items:
16,264

Contracts

Count of contracts:
0
Count of contract items:
0
Count of transactions:
0

Documents

Count of documents:
76,198

Milestones

Count of milestones:
0

Amendments

Count of amendments:
44,147

The OCDS data includes over 60 additional fields related to tenders, tenderers, and awards, whose semantics are undocumented and unclear.

Data quality

The dataset has minor issues that should not interfere with most uses. They include:

  • Some fields are incorrectly formatted:
    • tender/tenderers/address/postalCode is not a string
    • awards/title is not a string
    • tender/tenderers/address/region is not a string
    • awards/suppliers/name is not a string
    • tender/tenderers/name is not a string
  • The tender/tenderers field includes duplicate entries

Last reviewed: Jul 2018

Access data

This OCDS dataset is available for download in JSON, Excel or CSV format. You can download the data for contracting processes in a specific year or for all time.

JSON

Each contracting process is represented as one line of JSON text in the .jsonl file.

The .jsonl file is compressed using Gzip. Windows users need 7-Zip, WinRAR or WinZip to decompress the .gz file.

Excel

Each contracting process is represented as one row in the main sheet. Other sheets link to it via the _link_main column.

Excel files can have at most 1,048,576 rows. If a year is missing, it had too many rows. Download the CSV files, instead.

CSV

Each contracting process is represented as one row in the main.csv file. Other files link to it via the _link_main column.

The .csv files are archived using tar and compressed using Gzip. Windows users need 7-Zip, WinRAR or WinZip to decompress the .tar.gz file.

Do you have any questions or feedback on this dataset or any other content on this page?