On a traditional industrial commissioning, the PLC code meets reality for the first time when an engineer pushes a button on the live equipment. Every undiscovered logic defect — every off-by-one in a sequence step, every missed alarm transition, every state-machine deadlock — has to be found and fixed while the line is down, conveyors are running with safety guards in service mode, and a project sponsor is checking the clock. Virtual commissioning removes that surprise by giving the PLC a digital twin to talk to weeks before the first physical I/O point is energized.
What virtual commissioning actually is
Virtual commissioning is the practice of connecting your real PLC program — running on real controller hardware or a soft-PLC instance — to a 3D kinematic simulation of the plant. From the controller’s perspective, every input it reads and every output it drives looks identical to the physical machine: photoeyes trip on cue, motors report running and at-speed, encoders count pulses, scanners return barcodes. The difference is that the entire plant lives in a desktop window where you can pause time, rewind a fault, and reproduce a defect on demand.
Rockwell Automation Emulate3D is the simulation platform that ships with first-class integration into the Rockwell control stack. The same model also connects via OPC UA to Siemens TIA Portal, Mitsubishi GX Works, and Beckhoff TwinCAT — so a single virtual-commissioning environment can validate code across mixed-vendor sites that are increasingly common in Asian manufacturing.
The integration patterns we deploy
Pattern 1 — Hardware-in-the-loop (HIL)
A real ControlLogix or CompactLogix processor sits on the bench. Emulate3D drives the I/O via Ethernet/IP, so the controller runs unmodified production firmware against virtual sensors and actuators. This is the most faithful integration and the one we recommend when the controller will ship as-is to site.
Pattern 2 — Software-in-the-loop (SIL)
Logix Emulate or a soft-PLC instance hosts the controller program inside a virtual machine. Emulate3D talks to the soft-PLC over a virtual backplane. This pattern accelerates earlier-stage debug because dozens of engineers can each run their own private commissioning copy without a hardware controller per seat.
Pattern 3 — Mixed-vendor OPC UA bridge
For sites that mix Rockwell with Siemens, Mitsubishi, or Omron, an OPC UA server exposes the Emulate3D model as a tag namespace. Each controller subscribes only to the I/O it owns. We use this pattern routinely on multi-cell Japanese factories where line A is Rockwell-controlled and line B is Mitsubishi-controlled but share a common downstream sorter.
What virtual commissioning catches that paper engineering misses
- State-machine deadlocks that only appear after specific event ordering — e.g., an emergency stop during a mid-step transfer move
- Off-by-one errors in sequence steps that pass code review but fail at the physical timing boundary
- Race conditions in distributed-I/O networks where a remote rack updates at a different scan rate than the master
- Missing alarm transitions — alarms that fire but never reset, or reset paths that leave the machine in an inconsistent state
- Recovery logic gaps where a faulted machine can be cleared in 90% of cases but locks operators out in the remaining 10%
- Throughput bottlenecks introduced by overly conservative interlocking that the design review failed to catch
A representative project timeline
On a recent palletizing-cell project, the comparable on-site commissioning estimate from the integrator was four weeks of round-the-clock effort with two control engineers and one mechanical technician. The virtual-commissioning track ran in parallel: three weeks of model construction, two weeks of HIL debug against the customer’s actual ControlLogix processor, and one week of on-site verification. Total on-site time after virtual commissioning: five days. The fault list closed during virtual debug numbered 87, of which 9 would have been classified as safety-impacting if they had been discovered live.
The economics are predictable. Industry data and our own project records converge on the same range: virtual commissioning reduces on-site commissioning duration by 50–70 percent, reduces post-go-live punch-list defects by 40–60 percent, and shifts roughly 15 percent of total project effort from the highest-cost phase (live commissioning) to the lower-cost engineering phase.
What we look for in a virtual-commissioning model
Not every Emulate3D model is a virtual-commissioning model. A throughput model can ignore individual photo-eye debounce timing because it averages over thousands of cycles. A commissioning model cannot — it must reproduce the exact signal timing the PLC will see. Our internal acceptance criteria for handing a model over to PLC engineers are:
- Every input the controller reads has a corresponding sensor model with realistic on/off transition timing
- Motor controls report state in the same sequence the variable-frequency drive will report (commanded, ramping, at-speed, deceleration)
- Conveyor speed responses include acceleration curves rather than instantaneous step changes
- Fault injection is scriptable — every safety device, drive, and barcode reader can be commanded to fail on cue
- Recipe and product changeover is exposed via the same handshake the WMS uses on site
When virtual commissioning does not pay back
Virtual commissioning is not free. The model takes effort to build, the integration with the PLC requires control-engineering time, and the team needs people fluent in both Emulate3D and the controller stack. As a rough rule, we tell customers that virtual commissioning pays back on any project where the on-site commissioning bill exceeds 200,000 USD, or where downtime during commissioning would cost the operator more than 50,000 USD per day. Below those thresholds, a lighter throughput-only simulation is usually the right tool.
Working with iPlus on virtual commissioning
iPlus Solution runs a dedicated Emulate3D and Rockwell Automation simulation practice serving manufacturers and integrators across Japan, Vietnam, Korea, and Southeast Asia. Our engineers carry both mechanical-systems modeling experience and PLC programming background, which is the combination that makes the difference between a model that looks correct and a model that holds up against live controller code. To scope a virtual-commissioning engagement, visit /services/e3d or write to [email protected].
Need help with this?
Explore the iPlus Solution services most relevant to this article.
