No. The backbone reads equipment status, process parameters and energy consumption from existing machines through edge gateways, and can be deployed one line at a time, then one plant, then one industrial park. Existing ERP and MES keep running; the backbone is responsible for bringing the equipment-side data up, not for replacing business systems.
The physical layer is an edge gateway plus protocol adaptation. Different equipment brands expose different protocols — Modbus, OPC UA, proprietary interfaces — and the gateway handles acquisition and conversion before passing data to the hub. The change happens on the equipment and data side, not inside the ERP or MES.
Phased deployment is the recommended path: one line, then one plant, then one park. Starting with a single line proves within two to three weeks whether data can be collected reliably and whether definitions match the finance and quality teams' expectations. Risk and spend stay bounded while that question is answered.
The first outputs from the backbone are usually energy and carbon. In the deployed park, 149,771.53 kWh of electricity is collected automatically and converted to 91,923.8 kgCO₂e. Once figures like these are generated rather than assembled, export audits and ESG evidence stop depending on manually compiled spreadsheets — which is usually the point at which the business case becomes obvious.
| Connection method | Edge gateway read-out; existing business systems unchanged |
|---|---|
| Scale-up path | One production line → one plant → one industrial park |
| First outputs | 149,771.53 kWh park electricity · 91,923.8 kgCO₂e |