Virtual commissioning (VC) is the practice of testing and validating a robot cell's complete control logic — PLC programs, robot programs, safety systems, and HMI — in a physics-accurate simulation before any physical installation takes place. In 2026, virtual commissioning has moved from a niche practice in automotive to a mainstream methodology across electronics, food, logistics, and pharmaceutical manufacturing.
Manufacturers who adopt virtual commissioning report:
- 47% faster actual on-site commissioning
- 82% fewer integration failures discovered during physical startup
- 60–70% reduction in PLC programming errors found on-site
- 2–4 week reduction in time-to-production for complex cells
The Problem Virtual Commissioning Solves
Traditional robot cell commissioning works like this:
- Mechanical and electrical installation complete (8–16 weeks)
- PLC programmer arrives on-site
- Robot integrator arrives on-site
- Both spend 3–8 weeks debugging interface issues, sequence logic errors, and timing problems — with the physical robot sitting idle
- Each bug discovered requires physical robot motion to reproduce → safety risk, slow iteration
The core problem: PLC program and robot program are written independently and meet for the first time during physical commissioning. The integration errors that take weeks to debug on-site could have been caught in hours in simulation.
Virtual commissioning moves steps 3–5 into simulation, before the cell is physically assembled. The actual on-site commissioning becomes verification — not discovery.
How Virtual Commissioning Works
The Three-Layer Model
Layer 1: Robot Kinematics (geometric twin)
Accurate 3D model of the robot with correct joint ranges, TCP definition, and collision geometry. Generates robot programs via offline programming (OLP).
Layer 2: Process Simulation
Physics simulation of the robot's task — grip forces, conveyor speeds, part positioning, welding heat — producing realistic cycle times and predicting quality outcomes.
Layer 3: PLC-in-the-Loop (PLCSIL)
The actual PLC code (not a simplified model) executes inside or alongside the simulation. The virtual robot cell responds to PLC signals exactly as the physical cell would. The PLC programmer tests and debugs real code against the simulated cell.
This third layer is what separates virtual commissioning from simple robot simulation — it's testing the real control system against a virtual plant.
Key Technologies
PLC-in-the-Loop (PLCSIL)
PLCSIL connects the actual PLC runtime to the simulation environment:
Software PLCs (recommended): The PLC runs as software on an engineering PC, communicating with the simulation via shared memory or OPC-UA. Siemens PLCSIM Advanced and Beckhoff TwinCAT 3 are the most widely used.
Hardware-in-the-loop (HIL): Physical PLC hardware connects to the simulation via I/O simulation modules. Higher fidelity but requires physical PLC hardware and more complex setup.
Communication protocols used:
- OPC-UA (universal, brand-agnostic)
- PROFINET (Siemens ecosystems)
- EtherNet/IP (Rockwell/Allen-Bradley ecosystems)
- EtherCAT (Beckhoff ecosystems)
Simulation Software
| Software | Best PLC Compatibility | Robot Brands | Pricing |
|---|---|---|---|
| Siemens Tecnomatix Process Simulate | Siemens PLCSIM Advanced | FANUC, ABB, KUKA, Yaskawa, UR | $20K–$80K/year |
| Visual Components | Siemens, Beckhoff, Rockwell via OPC-UA | 2,000+ models | $4K–$12K/year |
| FANUC ROBOGUIDE | Limited PLC integration | FANUC only | $5K–$15K/year |
| ABB RobotStudio | Siemens via add-in | ABB only | $8K–$15K/year |
| KUKA.Sim Pro | Siemens, Beckhoff | KUKA only | Contact KUKA |
| Emulate3D | Siemens, Rockwell | Multi-brand | $8K–$25K/year |
For most manufacturers: Visual Components (multi-brand, mid-price) or Tecnomatix Process Simulate (deepest PLC integration, higher cost) are the most practical choices.
Step-by-Step Virtual Commissioning Process
Step 1: 3D Cell Design and Robot Placement
Build the virtual cell from CAD files of fixtures, conveyors, and robot base positions. Import the robot kinematic model. Verify:
- Robot reach covers all required positions
- No collisions in any required motion
- Safety zone geometry is correct
Deliverable: Validated cell layout that can be handed directly to mechanical/electrical engineering for physical build.
Step 2: Offline Robot Programming
Program all robot motions in the simulation:
- Teach all pick, place, weld, or process positions
- Optimize path speeds and acceleration profiles
- Verify cycle time against production rate requirement
- Generate robot program files for direct upload to physical robot
Deliverable: Complete, tested robot program ready for physical robot — no teach-pendant programming required on-site.
Step 3: I/O Definition and PLC Interface Design
Define all I/O signals between robot and PLC:
- Robot outputs: at-home position, program complete, error signals
- Robot inputs: start, stop, program select, safety OK
- Conveyor/fixture I/O: part present, clamp open/closed, gate signals
Document the complete I/O map before PLC programming begins — eliminating interface ambiguity.
Step 4: PLC-in-the-Loop Testing
Connect the PLC program to the simulated cell:
- Load PLCSIM Advanced (Siemens) or TwinCAT3 (Beckhoff) on engineering PC
- Start simulation in Visual Components or Tecnomatix
- Map simulated I/O to PLC tag addresses
- Execute the PLC sequence against the simulation
- Debug sequence logic, timing, and interlock errors
Typical errors caught in this phase:
- Sequence step triggered before prior step completes (timing error)
- Safety interlock preventing motion when it shouldn't (logic error)
- Robot start signal sent before fixture clamp confirmed (missing interlock)
- Conveyor runaway due to missing stop condition (sequence gap)
Iterate until: Full production cycle runs without errors in simulation for 50+ consecutive cycles.
Step 5: HMI Testing in Simulation
Connect the HMI (Wonderware, FactoryTalk, Siemens WinCC) to the simulated PLC. Test:
- All operator commands execute correctly in simulation
- Fault messages appear with correct descriptions
- Production counters increment correctly
- Recipe changes produce expected robot program selection
Step 6: Physical Commissioning (Verification Phase)
With validated programs and PLC code, on-site commissioning becomes verification:
- Upload robot program (generated in Step 2) — no teach programming
- Download PLC program (tested in Step 4) — minimal debugging
- Test cycle at slow speed
- Verify all I/O — should match simulation model exactly
- Run production speed cycle
Expected timeline: 3–5 days for a cell that would traditionally take 3–5 weeks to commission.
When to Use Virtual Commissioning
High ROI situations:
- Complex cells with 3+ robots or 50+ I/O signals
- Short on-site access windows (customer plant won't allow extended commissioning)
- Repeated cell installations (same design, multiple sites) — program once, reuse
- High-value production lines where downtime during commissioning is expensive
- Greenfield plants where physical cell isn't built yet but project timeline is tight
Lower ROI situations:
- Simple 1-robot cells with under 20 I/O
- Robot integrator has decades of experience with identical applications
- Physical robot is available for programming from day one
Cost vs. Benefit Example
Scenario: Automotive body welding cell — 3 FANUC robots, 120 I/O, 6-week traditional commissioning estimate.
| Cost Item | Traditional | With Virtual Commissioning |
|---|---|---|
| Simulation software (Tecnomatix) | $0 | $25,000/year |
| Engineering for VC | $0 | $15,000 (100 hrs × $150) |
| On-site commissioning (weeks × $8,000/week) | $48,000 | $16,000 (2 weeks) |
| Production line delay (weeks × $50,000/week) | $300,000 | $100,000 (2 weeks) |
| **Total** | **$348,000** | **$156,000** |
| **Saving** | — | **$192,000** |
First-year savings alone cover the software investment — and subsequent projects have no additional software cost.
Frequently Asked Questions
What is virtual commissioning?
Virtual commissioning tests a robot cell's complete control system — PLC programs, robot programs, safety logic, and HMI — against a physics-accurate simulation before physical installation. It replaces most on-site debugging with pre-installation simulation.
What software is used for virtual commissioning?
Siemens Tecnomatix Process Simulate + PLCSIM Advanced is the most complete solution for Siemens ecosystems. Visual Components + OPC-UA works for multi-brand and multi-PLC environments. Emulate3D is popular in North America for Rockwell/Allen-Bradley environments.
Does virtual commissioning work with Chinese robot brands?
Yes. Visual Components supports URDF/STEP models from Chinese brands including Estun, EFORT, and SIASUN. OPC-UA connectivity enables PLCSIL regardless of robot brand.
How long does virtual commissioning take?
For a typical 3-robot cell: 4–8 weeks of virtual commissioning (PLC programming + debugging) replaces 6–10 weeks of traditional on-site commissioning. The calendar total may be similar, but virtual commissioning happens before the cell is physically built — compressing the overall project timeline.
Is virtual commissioning worth it for small projects?
For cells with 3+ robots or 50+ I/O, yes. For simple 1-robot cells with straightforward sequences, traditional commissioning is typically faster. The breakeven point is roughly: if expected on-site debugging exceeds 1 week, virtual commissioning pays.
Plan Smarter Robot Deployments
GrabaRobot helps manufacturers source the right robots. For virtual commissioning support and system integration, connect with our certified integrator network.
Digital Twin for Robotics Guide →