The starting point is still a collection of disconnected systems
Walk any plant floor and the same pattern shows up. MES holds the orders. WMS knows inventory locations in theory. SCADA shows machine status. Radios still handle the calls for material movement. When a line is waiting, people walk or call until they locate the forklift. The data exists, but it does not share the same space or the same time. That fragmented baseline is where most Industry 4.0 conversations actually begin, not with a fully connected factory slide.
The practical decision is whether to keep adding more screens or to place one live spatial layer on top of the systems that already run the plant. The layer does not replace ERP, MES or WMS. It ingests their data and puts position, time and context in the same view.
A 2-4 week pilot is the first concrete milestone
A typical pilot runs 2 to 4 weeks. That length is deliberate. It is short enough that production does not stop and long enough to instrument a limited zone—one hall, one logistics corridor, a handful of forklifts and material points—with BLE or UWB tags.
In those weeks the existing layout is turned into a basic 3D model from floor dimensions, the position feeds are connected, and the first live movements appear on the spatial view. The pilot does not aim for a perfect twin. It aims to prove that real-time positions, timestamps and simple work-order acceptance can sit together without months of custom coding or system replacement.
What has to be true by the end of the pilot
Three checks matter. Does the accuracy match the use case—BLE typically in the 1-3 meter range for most internal logistics, UWB under 30 cm where tighter control is required? Can position and order data be pulled through existing APIs without heavy custom work? Can supervisors and drivers actually use the spatial view to cut radio chatter and unnecessary walking?
If those three hold, the pilot has earned the next step. It is measured evidence, not a polished demo.
Full deployment usually takes 1 to 3 months
After the pilot zone works, the full rollout typically stretches from 1 to 3 months. That calendar covers tagging the rest of the fleet, expanding the 3D model across the whole facility, adding the remaining data streams—PLC status, MES order details, sensor readings—and getting the teams that will use the map every shift comfortable with it.
The spatial layer stays an umbrella. It continues to ingest what is already there. The work is calibration, connection and training, not rewriting core systems. Historical position data becomes available for replay, so route and dwell analysis can start from measured movements instead of estimates.
Living with the live spatial layer
Once the 1-3 month window closes, the plant has one live view of forklifts, people and materials overlaid on the facility model. Supervisors see location without leaving the desk. Logistics can shift from push calls to drivers accepting work orders on a device. The map is checked in the morning meeting and stays open on the floor tablet, updated every few seconds.
That is the concrete path from disconnected systems to a working live spatial view, measured in weeks and months rather than vision statements.