Gemba and twin types: who goes to which place
An engineer opens the layout twin to check if a new rack fits. A logistics lead opens a live map to find a free truck. A CI manager opens last month's trails to see why second shift always piles cages at the same corner. All three say they went to gemba. They went to three different places.
One word, several places
Gemba means the actual place. In a plant that also runs digital twins, "place" can mean the physical floor or a representation that is good enough for a defined question. Confusion starts when the wrong representation is asked the wrong question. What gemba still means when digital modes exist is in what gemba means when the plant is also digital.
Industry 4.0 programs that fund one twin icon for every observation need this split. Twin types already differ by job. Stacking them for Industry 4.0 is covered in which twin type belongs where in an Industry 4.0 stack.
Which twin answers which gemba question
A static digital twin is the place for fit, clearance, and as-built truth. Go there when the question is whether the new stillage lane collides with a column. Do not go there when the question is where today's WIP is sitting.
A simulation digital twin is the place for a planned change that is not yet real. Go there when the question is what happens to dock waits if you cut one tugger from the loop. The physical gemba still matters before you trust the assumptions, and again after the change lands.
An operational digital twin is the place for the shift already running. Go there when the question is which mover is free, which buffer is dwelling, or which path the last starve followed. Keep genchi genbutsu for the human and physical detail the feed cannot show.
A predictive twin is the place for pattern questions that need history. Go there only after the operational record exists. Asking it to replace today's walk is how plants buy foresight on empty files. The dependency is stated in predictive digital twins wait on stored history.
The physical floor stays on the list
None of the twin types removes the real gemba. Operators still invent workarounds. Fixtures still wear. Safety still needs presence. Digital observation aims the walk. The walk still teaches what the twin cannot smell, hear, or negotiate. Plants that declare the walk obsolete usually rediscover it after the first incident the sensors never named.
Lean culture also lives at the physical place. Coaching, trust, and frontline ownership of kaizen do not transfer fully through a screen. Matching twin type to question is efficiency. Keeping the walk is discipline.
How teams assign the visit
1. Write the question in one sentence - Fit, what-if, live state, or pattern. That sentence picks the twin type or the physical floor.
2. Prefer the cheapest place that can answer it - Do not run a full simulation to ask where the truck is. Do not walk the whole hall to check a clearance that the static file already settles.
3. Chain places when the question spans modes - Simulate, then implement, then check on the operational twin, then walk the exception. That chain is Industry 4.0 observation, not four disconnected hobbies.
4. Keep ownership clear - Engineering owns static updates. Industrial engineering owns simulation cases. Operations owns the live view. Continuous improvement owns pattern questions once history is dense. How types differ on the shop floor is also in not every digital twin is the same.
Get in touch if you want a simple matrix of gemba questions against twin types for your own program.