The starting point is still a collection of disconnected systems
Most Industry 4.0 programs do not start from a blank plant. They start from working systems that still refuse to share place and time.
What the disconnected baseline actually is
ERP still owns planning and orders. MES still owns execution and structured production state. WMS still owns inventory bookings. SCADA still owns machine status. Radios and walks still close the gaps when material or movers are not where the last transaction said they were. Each system can be healthy in its own lane and still leave the plant without one shared view of where work is 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. Locations may live nowhere visible at all. Brownfield plants often keep that mix for years because the packages already run the business. The inventory of what is already on most floors is separate from this journey page: see the systems already running on most floors.
What the first journey decision is
The practical choice is whether to keep adding screens that stay in their own lanes, or to place one live spatial layer on top of the stack that already schedules and books work. The layer does not replace ERP, MES, or WMS. It ingests the streams those systems already own and puts location, time, and process context in the same hall view. The companion decision is why "no need to replace" only holds when protocols and ownership stay clear: see why "no need to replace" is a protocol problem.
That overlay is an operational digital twin job when it stays coupled to the shift. Live logistics on the hall is only one of three equal reasons to build it. The same feeds must grow a spatially oriented dataset under the live view, the place-and-time record that continuous improvement and later models need. Correlation and causality analytics use that record when the same buffer wait keeps preceding a starve, or when empty travel keeps climbing before the plant asks for another leased truck. Shift reaction, the stored spatial record, and hall-wide pattern work stay equal pillars from day one of the journey.
A two-to-four-week pilot is the first concrete milestone
A useful first prove window is typically two to four weeks on one zone: one hall, one logistics corridor, a bounded set of movers and material points, and a clear pass line. The length is deliberate. It is short enough that production does not stop for a campus rebuild, and long enough to instrument a limited area with a real-time location system (RTLS) feed and put the first live movements on a facility model people recognize.
In those weeks the plant turns the existing layout into a basic 3D model from floor dimensions, connects the position and order feeds that the pass line needs, and checks that supervisors can act from the shared view. The pilot does not aim for a perfect twin. It aims to prove that locations, timestamps, and simple work acceptance can sit together without months of custom coding or system replacement. Accuracy must match the job: BLE often lands in the medium-precision band of about 1–3 m (3–10 ft) for aisle and buffer logistics, while UWB is the usual path when the job needs exact floor position below 30 cm (below 12 in). Coarse zone presence is a different, lower-accuracy job and is not a synonym for that medium band.
What those weeks should cost to learn, and how finance should write pass and fail, sit under what a two-to-four-week hall pilot actually costs to learn. This journey page only needs the sequence: disconnected baseline, bounded prove, then expand.
What has to be true before the plant expands
1. Accuracy matches the decision - Medium precision for aisle search and fleet load. Exact floor position only where the mark matters. Do not buy sub-meter language for a bay-balancing job.
2. Feeds arrive through existing interfaces - Position and order data pull through APIs or industrial protocols already on the floor without inventing a second system of record.
3. Someone will act from the shared view - Supervisors and drivers cut radio hunts or unnecessary walks because the picture is trusted, not because a demo looked finished.
4. The three twin jobs leave a trail - Live logistics, the stored spatial record, and at least one pattern question the plant can ask later are all in scope. A map that never stores events has not finished the first milestone.
Full deployment usually takes one to three months
After the pilot zone works, a modest whole-facility rollout typically stretches from one to three months. That calendar covers tagging the rest of the fleet or material set, expanding the 3D model across the halls in scope, adding the remaining data streams (PLC status, MES order detail, selected sensor readings), and getting the teams that will open the map every shift comfortable with it.
The spatial layer stays additive. twinzo is built as an umbrella that ingests what is already there rather than rewriting core systems. The work is calibration, connection, and training. Historical location data becomes available for replay, so route and dwell analysis can start from measured movement instead of estimates. Hosting may still be cloud-first at this stage. When security or latency later hardens, the hosting choice is a mid-journey checkpoint covered in cloud is the default starting point.
Living with the live spatial layer
Once that one-to-three-month window closes, the plant has one live view of forklifts, people, and materials on a facility model people trust. Supervisors can read location without a status walk for every open question. Logistics can move from push radio calls toward drivers accepting work on a device. The same hall view stays available for the morning review and for floor tablets, updating every few seconds.
The disconnected baseline does not disappear as a history lesson. ERP, MES, and WMS still own their transactions. What changed is that place and time no longer live only in a radio call or a walk. The same additive path that defines a working Industry 4.0 data path is described in the data path that actually defines Industry 4.0. Visibility before automation for internal transport remains the logistics rule once the map is trusted: see lean logistics under Industry 4.0 is visibility before automation.
That operating habit is the concrete path from disconnected systems to a working smart manufacturing picture measured in weeks and months rather than vision statements. Live internal logistics context sits under internal logistics optimization. Production context on the same hall sits under production monitoring. Capability depth for the spatial layer sits on the features overview. Get in touch if you want to map the first prove zone on your own facility model.