Digital model, digital shadow, and digital twin
IT shows a finished 3D hall and calls it a twin. Logistics still radios for the free truck. The file never heard from the floor. That is a digital model wearing a twin label, and it is where most plants still sit.
What the three levels mean on the floor
Manufacturing papers often sort integration into three levels. A digital model is a virtual copy with no automated link from the physical hall. A digital shadow receives automatic updates from sensors or systems into that copy, but does not write control back. A digital twin, in that stricter sense, exchanges data both ways so the virtual side can also change the physical side.
Wikipedia's public definition stresses continuous sync with the physical counterpart. Academy writing that follows Grieves, NASA-era work, and later integration-level papers makes the direction of data the sorting key. Some research even notes that papers titled twin often describe only a shadow. Plant purchasing is usually one level lower still. How one slice gets declared finished sits under the Wikipedia digital twin vs what plants can actually buy.
Where plants actually stop: the model
Digital models are the default "twin" on site. CAD, BIM, meshed scans, offline what-if scenes, and photoreal walkthroughs are models until something on the floor updates them without a person re-exporting. They earn money before you buy the equipment. They go quiet when Line 3 waits. Leadership still hears digital twin because the 3D looks finished.
Plants stop there for a practical reason, not because the model unlocks the most twin value. A clever engineer, a workstation, and a software license can ship a convincing hall file. Live shadow work needs sensors or location, joins into plant systems, and agreement across logistics, production, IT, and facilities on naming, ownership, and who acts when the picture moves. That effort is interdisciplinary on purpose. If the plant wants the wider value Wikipedia and academy papers attach to digital twins, the spend and the staffing have to match that breadth, not only the easy modeling desk.
That wider value is not logistics alone. A live shadow into a shared 3D hall answers the radio hunt this shift. Under the same view it should store a spatially oriented dataset, and that record is what correlation and causality analytics need for hall-wide optimization later. Stopping at a silent model skips the search job, the stored replica, and the pattern work in one cut. Plants may already own live tables: MES completes, WMS moves, SCADA alarms, even a forklift telematics list. Those streams rarely land as continuous updates on the same hall model people walk in a review. Dashboards and the 3D file stay separate. Until location, plant signals, or both refresh the model automatically, and until that picture is kept as history, the plant has not reached shadow, no matter what the slide says.
Bidirectional twins that push setpoints or dispatch without a human are rarer again. They need a control owner and a safety case. Most halls that reach a useful live picture still stay on the shadow level, with a lead closing the loop by radio. That is progress from a silent model. It is not the academy's highest level.
A typical moment: facilities opens a polished scan from last rebuild and tells the board the twin is live. On Monday the dock still hunts kits by phone. IoT and MES screens exist in other rooms. Nothing moves the icons on the hall. The plant did not fail at shadow. It never left the model level.
Why the levels matter for the next budget
If sponsorship thinks every 3D file is a twin, the next euro (dollar) buys prettier geometry instead of a data link into that geometry. Naming the level as model makes the missing step visible: sensors, joins, and a habit of opening one live hall. Naming a rare live map as a full bidirectional twin oversells the other direction. Textbook label confusion across departments is under textbook labels rarely match the live floor.
Provider demos rarely open with model, shadow, twin. They open with the product name. Ask whether the 3D updates by itself from the floor, how often, and who still owns the next action. That filter sits beside different providers sell different twins.
BIM-first programs especially freeze on the model level while operations still runs blind. That case is under a BIM twin is not an operational twin of the shift. Simulation files without floor talk-back stay models too, covered under simulation is not a twin until the floor talks back.
How teams decide which level they are funding
1. Ask whether the 3D changes without a person updating the file - If not, you are on a model, even if live systems exist elsewhere.
2. Match the level to this quarter's decision - Fit before purchase needs a model. Seeing the starve, storing the shift, and asking which pairings keep preceding waits need a shadow. Automatic write-back needs a true twin with ownership.
3. Say the level out loud in the go-live note - "We have a digital model of Hall B" or "we have a digital shadow of Hall B" beats "we have a digital twin" when the board still expects control loops. Say whether the shadow also keeps the spatially oriented record, or only paints a live screen.
4. Price the next step from where you actually are - Most plants fund model to shadow first: bring live data onto the hall and keep it. Budget people and joins across teams, not only another license. Shadow to bidirectional twin is a later authority problem, not the first gap.
twinzo's usual job is that first real step: turning a silent hall model into a live operational shadow with plug-and-play style joins into systems plants already run, and a clear scope that humans still assign the next move. That view supports internal logistics optimization and production monitoring on equal footing with the spatially oriented dataset underneath and the correlation and causality work that dataset enables. Capability depth is on the features overview. How the operational type carries all three jobs is under operational digital twins show the shift. Twin types sorted by plant job are under not every digital twin is the same. Rollout shape is under pricing.
Get in touch if you want to walk whether your current "twin" is still a model, and what it takes to put live floor data onto that hall for the first time.