In October 2020, the Italian civil society organization onData launched AppaltiPOP, a platform for citizens and stakeholders to monitor public procurement processes. The project makes public sector data more accessible and increases transparency in the public procurement sector in Italy.
onData sources the data for AppaltiPOP from public administrations, often via ANAC. Italian public administrations are obliged by a 2012 law to release all annual data on public procurement as XML files to the anti-corruption authority by January 31st of the subsequent year. AppaltiPOP’s team then helps to identify corruption risks, or red flags, and aims to send this data back to ANAC to support their investigations.
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.
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:
220,459
Planning
Count of planning activities:
0
Tenders
Count of tenders:
61,958
Count of tenderers:
0
Count of tender items:
0
Awards
Count of awards:
61,958
Count of suppliers:
64,459
Count of award items:
0
Contracts
Count of contracts:
61,958
Count of contract items:
0
Count of transactions:
61,958
Documents
Count of documents:
0
Milestones
Count of milestones:
0
Amendments
Count of amendments:
0
No extensions or additional fields are used.
Data quality
Summary
The dataset has quality issues to take into account, notably:
The tender/contractPeriod/endDate date field is incorrectly formatted.
The publisher is incorrectly declared in the package metadata, using the commune name instead of onData
The same OCID is used for multiple contracting processes
Release tags do not reflect the sections which are provided in each release. For example, releases with the “award” tag, also contain contract and implementation information
For all contracts, the award referenced in the awardID field does not match the award ID.
The data includes organization references for buyers and procuring entities without an associated entry in the parties array.
Organizations with multiple roles are repeated in the parties section with different identifiers.
Last reviewed: Nov 2020
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.