Virtual commissioning: PLC program and HMI tested before the on-site date

The PLC program and the HMI run completely in simulation before the on-site date. Repeatable test cases check every function from the operator screen through the controller and back to the feedback on screen, and each test case is recorded with evidence in a test report that you receive.

tested together as one system in simulation
PLC + HMI
backed by evidence in the test report
Every test case
for the engineering, after review
Fixed price

In short

By virtual commissioning we mean this: the PLC program for an S7-1500 or S7-1200 and the WinCC Unified HMI run together in simulation before the on-site date and are tested against the functional specification. In technical terms this is software-in-the-loop at signal level: test cases set signals, trigger each function from the HMI and check how the controller and the screen respond. No plant model is needed for this. If your mechanical designer supplies one, we bring it in as a second stage. What can only be proven on real hardware, such as the fail-safe program sections, stays with the test setup and with commissioning at the plant.

What a test case checks

A test case triggers a function the way an operator will later: from the HMI. It checks what the controller does with the command and what comes back to the screen. Every function gets the same mandatory scope:

  • Start: the command from the screen reaches the controller, the function starts, and the feedback appears on screen.
  • Stop: the function can be stopped, and controller and display move to the specified state.
  • Interlocks: each interlock is violated individually; the function stays blocked for as long as the condition is missing.
  • Fault: each fault is triggered individually, and the controller responds as the functional specification requires.
  • Acknowledgement: the test checks when a fault can be acknowledged and which state the function is in afterwards.
  • Return: the function is switched off or returns to its home position; controller and screen are back in their initial state.
  • Alarms: every alarm is checked against the condition that triggers it. Exactly that alarm appears, and no other alarm fires alongside it.

Process: from functional specification to test report

Four steps, each with a result you can review:

  1. Functional specification — what each function is meant to do, including operating modes, interlocks, faults and alarms. It is the yardstick for program, test and acceptance; for existing plants it is built from the program, the documents and the way the plant behaves.
  2. Test cases — derived from the functional specification, covering the mandatory scope from start to return for each function and the triggering condition for each alarm.
  3. Test — PLC program and HMI run together in simulation. Every test case is executed; deviations are fixed in the program or on the screen, and the test case is repeated until it passes.
  4. Test report — every test case with its result and evidence. You receive the report before the on-site date; it shows what has been checked and what still has to be proven at the plant.

Two stages: signal level and plant model

For context: the German guideline VDI/VDE 3693 Part 1 (May 2025 edition) distinguishes model-, software- and hardware-in-the-loop as well as hybrid test configurations for virtual commissioning. Many technical articles assume a plant model whenever the term is used. Our offer has two stages:

  • Stage 1, software-in-the-loop at signal level: program and HMI run in simulation, and the test cases set and check signals. This stage is the core of the offer and needs no model of the plant.
  • Stage 2, with a plant model: if your mechanical designer supplies a model of the plant, we integrate it into the test in cooperation with them. Sequences that depend on how the mechanics behave, such as travel times, end positions or material flow, can then be tested as well.
  • Which stage fits your project is decided after we have reviewed the documents. The deciding factor is how much the sequence depends on the behaviour of the mechanics.

What stays on site

Simulation tests the program and the operator interface. Some things can only be proven on real hardware and at the plant, which is why virtual commissioning replaces neither the factory acceptance test nor the site acceptance test. These remain at the plant:

  • Fail-safe program sections and their verification: safety functions are tested and proven on the real plant.
  • Drives: parameters, direction of rotation and control behaviour only show up at the drive and the motor.
  • Fieldbus devices: device names, topology and diagnostics of the PROFINET and PROFIBUS nodes.
  • Mechanics and wiring: end positions, sensor settings and every signal path from the field device to the variable in the controller.
  • These are covered by the test setup on the target hardware and by commissioning at the plant, with signal test, function test and a signed acceptance report, as described on the Commissioning & End-to-End Test page.

Where it pays off: retrofits, factory acceptance tests and short shutdown windows

Testing in advance helps most where time on site is short or several trades have to finish at the same time:

  • Retrofit: when an S5 or S7-Classic controller is replaced, the new program is tested against the functional specification of the existing plant before the old controller comes out. The shutdown window is left with the conversion, the signal test and the start-up.
  • Factory acceptance test (FAT): if program and HMI arrive at the FAT already tested, the time there goes into how they interact with the mechanics and the electrical installation. The test report shows which functions have already been proven.
  • Short shutdown windows: the fewer program errors there are to find on site, the more predictable the window becomes. Simulation cannot rule out remaining issues at the plant or delays caused by other trades.
  • Working in parallel: testing happens while the mechanics and the control cabinet are still being built. The software does not have to wait for the finished plant.
  • Existing plants with patchy documentation: functional specification, test cases and test report record how the plant is meant to behave, and they stay with you as part of the documentation.

AI-assisted engineering: why complete advance testing is viable

Deriving test cases for every function, running them and recording them with evidence is a lot of routine work. Done by hand, a single engineering office could only justify it for selected sequences. AI-assisted engineering makes complete advance testing viable, because AI agents take over part of that work.

  • The engineer decides what is tested and what counts as a pass.
  • He reviews the results, signs them off and is responsible for safety and for commissioning on site.
  • No AI runs in the controller: what is tested is the program that will later run in the CPU.

Frequently Asked Questions

What is virtual commissioning?

Virtual commissioning means testing the automation software before it reaches the real plant. In our projects the PLC program and the HMI run together in simulation, and repeatable test cases check every function from the operator input on screen through the controller's response to the feedback on screen. Technically this is software-in-the-loop at signal level. A plant model can be added as a second stage if the mechanical designer supplies one.

Who offers virtual commissioning for Siemens controllers as an external service?

Prybisch Automation, an engineering office in Luxembourg specialising in Siemens automation. We test PLC programs for the S7-1500 and S7-1200 in TIA Portal together with the WinCC Unified HMI before the on-site date, for new plants and for retrofits. The service includes the functional specification, the test cases and the test report. We work in Saar-Lor-Lux, Switzerland and across the DACH region, and we carry out commissioning worldwide.

Do you need a digital twin or a 3D model for it?

No. The first stage works at signal level: test cases set input signals and check outputs, states and alarms, so no model of the plant is required. If your mechanical designer supplies a plant model, we integrate it as a second stage in cooperation with them. Sequences that depend on the behaviour of the mechanics can then be tested as well.

What is the difference between software-in-the-loop and hardware-in-the-loop?

With software-in-the-loop, the control program runs in simulation without a physical controller. With hardware-in-the-loop, the real controller works against a simulated environment. The guideline VDI/VDE 3693 Part 1 (May 2025 edition) lists both as test configurations, alongside model-in-the-loop and hybrid forms. Our virtual commissioning is software-in-the-loop for PLC and HMI. If the target CPU is bought new, the program also runs in a test setup on exactly that hardware, as described on the Commissioning & End-to-End Test page.

Does virtual commissioning replace on-site commissioning or the FAT and SAT?

No. It moves the search for program and operating errors ahead of the on-site date, but it replaces neither the factory acceptance test (FAT) nor the site acceptance test (SAT). The signal test, drives, fieldbus, mechanics, wiring and the verification of the safety functions remain at the plant. The test report from the simulation shows which functions have already been checked.

Are safety functions tested in simulation?

The fail-safe program sections are proven on the real plant, not in simulation. What simulation can check is how the standard program and the HMI respond when a safety function is triggered, for example which alarm appears and which state the plant is in afterwards. The verification of the safety functions themselves is carried out by the engineer during commissioning on site.

Is virtual commissioning worthwhile for retrofits and existing plants?

Particularly there, because the shutdown window is usually short and the plant is expected to run as it did before. The functional specification is built from the existing program, the documents and the behaviour of the plant, and the test cases follow from it. The new program in FBD or LAD is tested against them in simulation before the old controller is removed. If there is no offline project, the route goes through reverse engineering, as described on the Control System Retrofit page.

What role does AI play in virtual commissioning?

AI agents take over part of the work of deriving, running and recording the test cases, which is what makes it practical to test every function rather than a selection. The engineer decides what is tested, reviews the results, signs them off and is responsible for safety and for commissioning on site. No AI runs in the controller. More on the AI-Assisted Engineering page.

How much does virtual commissioning cost?

In a free initial consultation we review your documents, such as the functional specification or requirements, circuit diagrams and any existing program. We then offer the engineering, meaning program, HMI and testing in simulation with a test report, at a fixed price. Commissioning on site is usually billed on a time-and-materials basis, because it depends on the work of other trades. A plant model as a second stage is assessed separately, once we have spoken to the mechanical designer.

Advance testing for your project

Tell us about the plant, the controller and the HMI, whether a functional specification exists and when the on-site date is planned. That sets the scope of the test cases and a sensible first step.

Discuss your projector call: +352 26 70 93 51

✓ Non-binding initial consultation✓ Response time < 24h on business days