Virtual commissioning before anything physical exists

Controls engineers shake out a robot sequence on a virtual line for weeks. The physical cell is still on order. The program calls it a digital twin. Wikipedia's sync rule has nothing to attach to yet. ## Why pre-physical twins are still a real slice Wikipedia's design and prototyping sections describe [virtual commissioning](https://www.twinzo.com/glossary/virtual-commissioning) and related models that test a line before equipment is installed. Academy subtypes call that stage a [digital twin prototype](https://www.twinzo.com/glossary/digital-twin-prototype). The job is clear: find sequence faults, reach clashes, and logic bugs before you buy the equipment and burn the start-up window. The stricter twin definition on the same encyclopedia page wants continuous data from a physical counterpart. A cell that does not exist cannot sync. That is not a reason to skip virtual commissioning. It is a reason to stop treating the pre-physical file as the finished plant twin after go-live. Cost and benefit of the start-up filter sit under [what virtual commissioning costs and what it buys before start-up](https://www.twinzo.com/wiki/what-virtual-commissioning-costs-and-buys-before-start-up). ## Where the label should change after start-up After the line runs, the useful twin verbs shift toward monitoring and maintenance of the instance. Live positions, [MES](https://www.twinzo.com/glossary/mes-manufacturing-execution-system) state, and door or energy joins answer different questions than the PLC. If sponsorship never renames the workstream, the plant keeps polishing the prototype while operations still runs blind. Simulation-without-sync is the sibling trap under [simulation is not a twin until the floor talks back](https://www.twinzo.com/wiki/simulation-is-not-a-twin-until-the-floor-talks-back). A typical moment: virtual commissioning finds three handshake faults and saves a week of debug. The twin program is declared complete at FAT. Three months later kits still vanish between buffer and cell because no operational layer was funded. The prototype did its job. The blank verbs were never listed. Shared geometry helps the handoff. The shell used for commissioning should be reusable for the live hall instead of remodeled under a new vendor. That reuse story is under [paying once for geometry three twin types can reuse](https://www.twinzo.com/wiki/paying-once-for-geometry-three-twin-types-can-reuse). Controls teams sometimes keep the virtual line as a sandbox after start-up for recipe changes. That remains prototype-style work on a soft twin. It should not block funding for the operational instance that watches the real meter and the real kit path. Two tools can stay in the program. One label should not hide which one answers the starve. ## How teams keep both definitions honest Keep Wikipedia's sync language for the running asset. Keep prototype language for the period before anything physical exists. Write both into the roadmap so finance does not expect one PO to cover design proof and shift visibility. Prototype, instance, and aggregate subtypes are under [digital twin prototype, instance, and aggregate](https://www.twinzo.com/wiki/digital-twin-prototype-instance-and-aggregate). ## How to decide the next spend after commissioning **1. List faults found only in the virtual run** - That list is the ROI of the pre-physical slice. **2. Name the first live decision after start-up** - If it is a starve or empty round, fund an [operational](https://www.twinzo.com/glossary/operational-digital-twin) instance, not another soft scenario. **3. Reuse the hall model on purpose** - Refuse a live tool that cannot inherit the commissioned geometry. **4. Retire the "twin complete" stamp at FAT** - Mark prototype complete. Leave instance work open or explicitly out of scope. twinzo is not the virtual commissioning engine. It is the live hall layer that can inherit geometry and join plant signals after start-up, with clear scope and integration into systems already on site. That supports [production monitoring](https://www.twinzo.com/monitor-production) and [internal logistics optimization](https://www.twinzo.com/optimize-internal-logistics). Capability depth sits on the [features overview](https://www.twinzo.com/features). Static shell economics are under [what a static digital twin costs and what it buys](https://www.twinzo.com/wiki/what-a-static-digital-twin-costs-and-buys). Rollout shape is under [pricing](https://www.twinzo.com/pricing). [Get in touch](https://www.twinzo.com/contact-us) if you want to walk how to close a virtual commissioning twin without pretending the shift twin already shipped.