The systems already running on most floors
Most plants already run ERP, MES, WMS, and SCADA. Those systems work, but they stay in their own lanes until a shared place-and-time layer joins them.
What those systems own
In the common ISA-95 framing, ERP owns business planning and logistics commitments. MES and related manufacturing operations systems own execution, genealogy, and structured production state. SCADA and control layers own machine supervision and real-time equipment state. WMS owns inventory bookings and warehouse moves. Each package can be healthy in its lane and still leave the plant without one shared view of where work sits right now.
That pattern is a data silo problem in operations language, not a claim that any single package failed. Orders live in one clock. Inventory lives in another. Positions may live nowhere visible at all. Brownfield plants often keep that mix for years because the packages already run the business. The journey framing for that baseline is covered in the starting point is still a collection of disconnected systems.
What Industry 4.0 asked for on top
The original Industry 4.0 framing described one connected cyber-physical environment in which physical assets and their digital counterparts stayed synchronized. Sensors, machines, people, and material would feed a shared live picture. Decisions could rest on current state rather than last night's report or a verbal hand-off. The plant would behave as a single system instead of a collection of departmental tools.
That vision never required throwing out ERP or MES. Modern integration practice in the ISA-95 spirit says the same: keep authority with each system of record, and add a connecting layer that moves state without becoming the new ledger for every booking. Why interconnection is a protocol and ownership problem rather than a rip-and-replace program is covered in why "no need to replace" is a protocol problem. Why the paradigm is not the same purchase as a twin is covered in Industry 4.0 is not the same as a digital twin.
Where place and time are still missing
The gap is spatial context, not missing brand names. Material requests can sit in one system while mover location sits in another, or nowhere visible. Line stops can appear in MES while logistics still learns by radio. Basic tracking, when it exists, often stays in yet another silo and rarely lands next to the production event that needed the material. Historical replay of movement is limited or missing. The systems know pieces of the story. Almost no one sees the full spatial picture in real time.
That is why status still forces walks after dashboards land (the cost is covered in walking still costs more than most dashboards admit), and why three true screens can still burn a morning huddle (covered in what three true screens cost you every morning huddle).
Closing the gap with an operational twin overlay
An operational digital twin sits above the existing stack. It ingests data from ERP, MES, WMS, SCADA, and real-time location system (RTLS) feeds through APIs and common industrial protocols. It places that data on a live facility model so position, time, and process state appear together. Live logistics, a spatially oriented dataset, and later correlation and causality analytics are equal readers of that layer.
twinzo works this way. It does not replace the systems of record. MES continues to own structured production and OEE data. twinzo adds spatial context and decision support. Logistics modules can turn material requests into claimable work instead of radio dispatch. The RTLS layer shows live locations of forklifts, people, and materials, with replay and spaghetti diagrams for route analysis. Medium-precision location around 1–3 m (3–10 ft) is usually enough for aisle and bay joins. Exact floor position is a different accuracy job.
Deployment options include public cloud, private cloud, or fully on-premise for sites with stricter data or latency requirements. The layer is designed to sit on top of what is already running rather than force a rip-and-replace project. Hosting trade-offs later in the journey are covered in cloud is the default starting point.
What progress against the original promise looks like
Progress is visible when the plant can answer spatial questions that used to require a walk to confirm: where the material that was supposed to arrive is sitting, which forklift is free, how yesterday's routes actually looked compared with the planned ones. Documented twinzo logistics RTLS cases on automotive Tier-2 halls of about 30,000 m² (about 323,000 ft²) show what that overlay can unlock for fleet and empty-travel decisions. Those cases are covered in forklift productivity from 63% to 75% and when buying more forklifts is the wrong first answer.
Those outcomes sit inside the existing system landscape rather than outside it. The connected cyber-physical picture Industry 4.0 described is not a distant future architecture. In many plants it is simply the missing overlay that turns the systems already running into a coherent operational picture. A smart factory program still refuses to share place and time until that overlay exists.
Capability depth is covered on the features overview. Live logistics and production monitoring are covered in internal logistics optimization and production monitoring. Get in touch if you want to map which systems you already own still refuse to share place and time.