Why “no need to replace” is a protocol problem
Plant managers hear Industry 4.0 talk and immediately picture a multi-year project that rips out the MES, rewrites the WMS, and forces every PLC onto a new stack. Twinzo states the opposite: there is no need to replace ERP, MES, or WMS. That statement only survives contact with a real floor if the platform can speak the protocols the existing equipment and systems already use.
The technical specification lists the edge protocols Twinzo supports—OPC UA, Profinet, Modbus TCP, Ethernet/IP, and MQTT—and notes that the platform does not depend exclusively on these. For a plant still running decades-old controllers, the workable path is to leave those controllers and the enterprise systems in place and pull the data they already produce.
How the four common protocols actually show up
Modbus TCP is still the language of a large share of older PLCs. Ethernet/IP appears on most Rockwell and Allen-Bradley installations. OPC UA has become the preferred secure bridge for newer cells and for gateways that translate older register maps. MQTT works for lighter IoT sensors and for edge devices that prefer to publish rather than expose memory addresses.
Twinzo’s IoT / Data module is built to ingest from PLC sources, APIs, and physical sensors. Once the data reaches the platform it sits in the same spatial layer that already receives RTLS positions of forklifts, people, and materials. The live operational view therefore does not require the MES or WMS to be rewritten or replaced.
Where production data still lives
Production metrics, downtime events, and structured KPIs continue to originate in the MES or in the separate OEE processing engine. Twinzo integrates through secure APIs to ingest those values and then places them into spatial context. In this architecture the MES remains the system of record for structured manufacturing intelligence. Twinzo supplies visualization, spatial context, and decision support on top.
That separation is what makes the non-replacement claim hold. Twinzo functions as an umbrella layer for ingesting data from other systems, including but not limited to RTLS, MES, ERP, WMS, and SCADA. It does not become the new system of record for production or logistics transactions.
Constraints that appear on a mixed floor
A typical plant with legacy equipment does not speak one clean protocol. Some lines still run Modbus TCP, others Ethernet/IP, and newer cells use OPC UA. Gateways often sit between the old controllers and the plant network. Twinzo’s deployment options—public cloud, private cloud, fully on-premises, or hybrid—let the plant keep the data path inside its existing OT/IT segmentation rules.
On-premises deployment runs on Ubuntu 24.04 LTS with Docker. Security measures include TLS, role-based access control, OT/IT segmentation, and audit logging; optional VPN is also available. The design goal stays consistent: read the data the existing systems already produce and put it into a live 3D context that operators and supervisors can use without abandoning the tools they already trust.
The companion concept piece covers the RTLS and IoT data path that feeds the spatial layer. Protocol interoperability is the piece that lets that path work with the equipment and software already on the floor.