Guide for companies
Industry 4.0 and Transition 5.0: the interconnection that unlocks the incentives
Updated August 2026
Italy’s incentives for capital equipment change name and rate almost every year — hyper-depreciation, the Transition 4.0 tax credit, Transition 5.0, and hyper-depreciation again. What never changes is the requirement that unlocks them all: the machine must be genuinely interconnected to the company’s systems. And here is what many companies discover late: interconnection does not come in the crate with the machine. It gets built, and two thirds of it is software developer work — not just PLC work.
This is a technical guide, not tax advice: rates, ceilings and deadlines must be checked with your accountant against current law. The technical requirements described here, however, have been stable since 2017.
What the rules require (the part that does not change)
For tangible assets in Annex A (law 232/2016), the machine must have five mandatory characteristics plus at least two of three additional ones. The five:
The five mandatory ones
- Control via CNC or PLC;
- Interconnection to factory IT systems with remote loading of instructions and/or part programs;
- Automated integration with the factory logistics system, the supply network and/or other machines in the production cycle;
- A simple, intuitive human-machine interface;
- Compliance with the latest safety standards.
Plus at least two of these three
- Remote maintenance and/or remote diagnostics and/or remote control systems;
- Continuous monitoring of working conditions and process parameters;
- Integration between the physical machine and/or plant and the modelling and/or simulation of its own behaviour (cyber-physical systems).
What “interconnected” means in practice
The word in the decree that generates the most work — and the most failed appraisals — is “interconnection”. In practice it means four things, none of them optional.
Bidirectional data exchange
The machine must send data to company systems AND receive it (orders, recipes, programs). Monitoring alone is not enough: the flow must run both ways, over documented protocols (OPC UA, MQTT, API calls).
Unique identification
Every machine recognisable on the network with a unique address (IP or equivalent). It sounds trivial; in plants whose networks grew in layers, it is not.
ERP integration
The production order leaves the ERP and reaches the machine; produced pieces, times and stops flow back. This is the heart of the requirement — and it is not PLC work: it is a software bridge between machine and ERP or MES. APIs, databases, queues, error handling: fullstack developer work.
Documented evidence
The appraisal must show all this actually works: network architecture, data exchange traces, logs. If the integration is real, the documentation almost writes itself; if it is fake, it shows immediately.
What Transition 5.0 adds
Transition 5.0 added a certified energy-saving target on top of interconnection (reduction of facility or process consumption, certified ex ante and ex post). In practice: more software.
- Continuous consumption monitoring: meters to read, store and aggregate by machine, line and department.
- Baseline and comparison: proving the saving means comparing before and after — you need a solid data foundation, not a hand-filled spreadsheet.
- Energy dashboards for certification: the certifier wants to see the numbers, the company wants to understand them. Dashboards, reports, exports.
- Software itself qualifies: energy monitoring and efficiency programs are among the intangible assets incentivised by 5.0.
Who you need (spoiler: two profiles, not one)
A typical interconnection project has three layers, and no single professional covers all three well.
The PLC / automation engineer
Opens up the machine: exposes data from the PLC (or adds a PLC/gateway to older machines), configures protocols, handles signals and safety. Irreplaceable on retrofits of older machines.
The fullstack developer
Builds everything above: the service that talks to machines and ERP, the database storing production and consumption, the APIs, the monitoring dashboards, the reports for the appraisal. In many projects this is the biggest share of the work.
Appraiser and accountant
The appraiser certifies the requirements are met (mandatory above the thresholds), the accountant frames the right incentive and current rates. They come at the end — but involving them from the start avoids building the wrong thing.
Order of magnitude for the software work: exposing and storing data from an already-modern machine, €3–8,000; a bidirectional ERP bridge, €8–25,000; multi-machine energy monitoring with dashboards, €10–30,000; full retrofit of an older line, €20,000 and up. Indicative figures: they depend on how many machines, how open they are and the state of the ERP.
The “paper interconnection”
- The requirement must hold for the whole benefit period: if the interconnection stops working after the appraisal, the incentive can be revoked — with penalties and interest.
- A gateway installed and never connected to the ERP is not interconnection: it is an object in an electrical cabinet. In an audit, the logs speak.
- A sworn appraisal carries criminal liability for whoever signs it: no serious appraiser will certify an integration that does not work. Better to find out before booking the incentive.
- The machine vendor’s “we’ll interconnect it for you” often stops at their own proprietary panel and never reaches your ERP: read what the offer actually includes.
Frequently asked questions
Can I interconnect an old machine?
Yes — that is the classic retrofit: add a PLC or gateway exposing the data, wire the essential signals and build the ERP integration on top. The machine must also meet the other requirements (safety included): it has to be assessed case by case.
How much does interconnecting a machine cost?
From €3–8,000 to expose and store data from an already-modern machine, €8–25,000 for a bidirectional ERP bridge, €20,000 and up for a full retrofit of an older line. The incentive covers the assets and often the software too: the real net cost is a calculation for your accountant.
Do I need an MES?
No. The decree requires integration with factory systems, not a specific product: for many SMEs a well-built software bridge between machines and the existing ERP is enough. An MES makes sense when shop-floor complexity justifies it — not as an entry fee to 4.0.
Does software qualify, or only machinery?
Software too: related intangible assets (Annex B) have historically qualified, and Transition 5.0 expressly incentivises energy monitoring and efficiency software. Rates and windows change with each budget law: it is the right question for your accountant.
What work is there for a fullstack developer in 4.0?
More than people think: services reading machine data (OPC UA, MQTT, APIs), ERP and MES integration, production and consumption databases, dashboards and appraisal reports. It is software development through and through, in a domain — the factory — with far less competition than the web.
Who finds me the right people for a project like this?
On Araknet you post the project anonymously describing machines, ERP and goal (4.0 interconnection, 5.0 monitoring) and receive offers from both PLC specialists and fullstack developers, with price and timeline. You can also hire the two profiles separately, with two projects.
See also: Software development for industrial automation and PLC · Modernising outdated business software.
Need to interconnect machines to your ERP?
Describe machines, ERP and goal anonymously: receive offers from PLC specialists and fullstack developers with price and timeline. No commission on the work.
Post the project