Italy: Ministry of Infrastructure and Transport

The OpenData project by the Italian Ministry of Infrastructure and Transport publishes notices, tenders and tender results of public contracts in the infrastructure and transport sectors through the Public Contracts Service database. The OCDS data publication is available through their API.

The Public Contracts Service database is a key component of the OpenData project, managed by the General Directorate for Regulation and Public Contracts. It serves as a repository for notices, tenders, and results of public contracts in the infrastructure and transport sectors. The service helps meet legal requirements for transparency and information sharing as set out in the Public Contracts Code, Legislative Decree 50/2016. The service covers:

  • Publishing notices, announcements, and results of public contracts for construction, services, and supplies (according to articles 29 and 73 of the Public Contracts Code and the Decree from December 2, 2016).
  • Releasing biennial procurement plans for goods and services, and triennial plans for public works projects, including their annual updates (as per article 21 of the Public Contracts Code and a decree dated January 16, 2018, no. 14).
  • Disclosing the documents mentioned in Article 29, paragraph 1, of the Public Contracts Code.

The Public Contracts Service also publishes data for unrealized works and infrastructure projects.

Available formats:
JSON
Excel
CSV

Overview

Data date range:
Jan 2022 - Jan 2024
Update frequency:
Daily
Main language:
Italian
OCID prefix:
ocds-8mw9gh
License:
European Union Public License (EUPL), version 1.2

You are free to:

  • Reproduce, modify, communicate, distribute, lend, rent, sublicense rights in, or otherwise use the Work in any circumstance and for all usage, on any media, supports and formats.

Under the following terms:

  • Attribution right: The Licensee shall keep intact all copyright, patent or trademarks notices and all notices that refer to the Licence and to the disclaimer of warranties. The Licensee must include a copy of such notices and a copy of the Licence with every copy of the Work he/she distributes or communicates. The Licensee must cause any Derivative Work to carry prominent notices stating that the Work has been modified and the date of modification.
  • Copyleft clause: If the Licensee distributes or communicates copies of the Original Works or Derivative Works, this Distribution or Communication will be done under the terms of this Licence or of a later version of this Licence unless the Original Work is expressly distributed only under this version of the Licence — for example by communicating ‘EUPL v. 1.2 only’. The Licensee (becoming Licensor) cannot offer or impose any additional terms or conditions on the Work or Derivative Work that alter or restrict the terms of the Licence.
  • Compatibility clause: If the Licensee Distributes or Communicates Derivative Works or copies thereof based upon both the Work and another work licensed under a Compatible Licence, this Distribution or Communication can be done under the terms of this Compatible Licence. For the sake of this clause, ‘Compatible Licence’ refers to the licences listed in the appendix attached to this Licence. Should the Licensee’s obligations under the Compatible Licence conflict with his/her obligations under this Licence, the obligations of the Compatible Licence shall prevail.
  • Provision of source code: When distributing or communicating copies of the Work, the Licensee will provide a machine-readable copy of the Source Code or indicate a repository where this Source will be easily and freely available for as long as the Licensee continues to distribute or communicate the Work.
  • Legal protection: This Licence does not grant permission to use the trade names, trademarks, service marks, or names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the copyright notice.
Publication policy:
-
Last retrieved:
Nov 2024 (retrieved monthly)
Retrieved from:
https://www.serviziocontrattipubblici.it/ocds-ms/swagger-ui.html#/v1.0

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:
6,955

Planning

Count of planning activities:
0

Tenders

Count of tenders:
1,519
Count of tenderers:
0
Count of tender items:
1,916

Awards

Count of awards:
3,027
Count of suppliers:
2,950
Count of award items:
0

Contracts

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

Documents

Count of documents:
6,771

Milestones

Count of milestones:
0

Amendments

Count of amendments:
0

In addition to the core OCDS fields, the Public Contracts Service also publishes other relevant information through OCDS extensions, such as links, pagination, OCDS for the European Union, and lots.

Data quality

Summary

The dataset has quality issues to take into account, notably:

  • Some of the dates relating to stages of the contracting process do not follow a coherent timeline.
  • buyer/id does not match its parties.id
  • Some organizations in the parties section are not referenced, e.g. a procuring entity listed in the parties section is not referenced in the tender section
  • There is some duplication of party ids and supplier ids

Last reviewed: May 2024

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?