Cyber-physical systems need a twin that stays coupled
Before you call a system cyber-physical, ask whether the digital side still receives live floor state. A 3D file that stopped updating is geometry, not a coupled twin.
What a cyber-physical system actually requires
A cyber-physical system (CPS) integrates physical processes with computation and networks so that software monitors and influences the physical world through feedback. Industry literature on CPS treats the physical asset, its digital counterpart, the applications that use both, and the communication and security between them as one design. Industry 4.0 took CPS as a core idea for the smart factory. The point is not a nicer drawing. The point is a living link.
If the digital side stops receiving state, the loop is broken. What remains is a digital model or, at best, a delayed shadow of selected signals. The academic split between model, shadow, and twin still matters on the floor. It is explained in plant language in digital model, digital shadow, and digital twin.
Coupling is the bar, not the render
A static geometry export can be valuable for clearance and training. It is not coupled. A simulation study can be valuable before you buy equipment. It is coupled to assumptions, not to this afternoon's aisle. An operational twin stays coupled when positions, material states, and selected process signals keep updating the same hall people trust.
Industry sources and twin taxonomies keep repeating the same warning: many deployments sold as twins stop at visualization. Monitoring that stays bound to the asset with history is a higher bar. Prediction and write-back sit later, and only when the coupling is trusted. On that coupled record the plant gets three equal jobs: live logistics on the shift, a spatially oriented dataset under the live view, and later correlation and causality analytics. Plants that skip the live bond and jump to autonomy language mix observation with control. That boundary is also why a dark-factory claim needs more than a map, as described under what a true dark factory demands.
What stays human inside the loop
Coupling does not mean the twin must command every actuator. Many plants keep write authority in PLC, MES, and people for safety and skill reasons. The CPS idea still holds when the digital side continuously reflects the physical side so people and systems can act on current state. Vendor slides that promise bidirectional twin control while the floor still runs on radio are a related trap, covered in bidirectional twin control on the slide, radio on the floor.
For logistics and improvement teams, coupling means the free truck, the waiting cage, and the starved station share one clock and one map. That shared state is what later kaizen and correlation work consume. Without it, continuous improvement returns to calendar snapshots.
How teams test whether the twin is still a CPS piece
1. Ask what refreshes, and how often - If the answer is only when someone exports a new file, you have a model, not a coupled twin.
2. Ask which physical objects are in the loop - Machines alone, or also movers and material that decide whether the line waits.
3. Ask who acts on the coupled view - If nobody on the shift uses it, the feedback loop is organizationally broken even when the feed is technically live.
4. Keep Industry 4.0 scope wider than one cell - A coupled cell is progress. A plant program still needs interconnection across the systems that already run orders and inventory, which is why protocol and integration questions sit beside twin purchases in why "no need to replace" is a protocol problem.
Where twin types sit in the wider stack is in which twin type belongs where in an Industry 4.0 stack. Capability depth for the live layer is on the features overview. Get in touch if you want to check whether your current twin is still coupled to the hall it claims to represent.