PLC commissioning on site: process, preparation and pitfalls

PLC commissioning is the moment when the control program, wiring, drives and people come together for the first time. What was carefully planned and tested in the office now has to prove itself on the real plant – with real signals, real tolerances and often under time pressure, because production is supposed to restart.

Whether commissioning runs smoothly or drags on for days is usually decided long before the first power-up. This guide explains what should be ready in advance, what a structured process on site looks like and where projects typically stall. It is written for operators, project managers and maintenance teams who are having a new or modernized control system put into operation.

What needs to be ready before power-up

On-site commissioning becomes expensive when it has to wait: for a missing approval, for a cable, for the colleague with the key to the control cabinet. Most delays do not originate in the program but in its surroundings. That is why it pays to go through the prerequisites together a few days in advance and to record open items in writing.

A verified wiring installation is especially important. Anyone who checks the terminal diagrams only during commissioning mixes two tasks that are faster when done separately: the electrician checks wiring and connections, the programmer checks signals and functions. It should also be clear how the commissioning engineer will access the controller – via an approved network port in the cabinet, via the company network or via remote access – and who grants these approvals.

• Wiring checked against the circuit diagrams and documented, deviations marked
• Power supply, fusing and, where needed, compressed air available and released
• Network access to the controller clarified: connection, IP addresses, IT approvals
• Current documents: circuit diagrams, I/O list, device documentation, parameter lists
• A dedicated contact on site who knows the plant and the process and is authorized to make decisions
• Material for functional tests: products, workpieces or media in sufficient quantity
• Time slot agreed with production, including a buffer

Offline testing and simulation: find errors before reaching the plant

The more that has been tested before commissioning, the shorter the time at the plant. Large parts of a control program can be tested without the real machine: step sequences, interlocks, error handling and operating modes can be run through with simulated inputs. That way, logic errors show up at the desk and not only when a drive moves in the wrong direction.

How far simulation makes sense depends on the plant. For simple conveyor systems, testing the step sequences with manually set signals is often enough. For more complex processes with many axes, cycle times and dependencies, a simplified plant model that emulates sensors and actuators can help. Interfaces to higher-level systems such as ERP or a database can also be checked in advance with test data.

Simulation does not replace commissioning. Mechanical tolerances, signal delays, the switching behavior of sensors and the behavior of real products only become visible at the plant. It does, however, shift the focus: on site, the work is then about fine-tuning instead of basic troubleshooting. How to describe the requirements properly from the start is covered in our guide to requirements for PLC programming.

The process at the plant: from I/O check to the first function

Structured PLC commissioning works its way from the bottom up. It starts with the I/O check: every input and every output is tested individually. Does the limit switch trigger, and does the signal arrive at the correct input? Does the valve switch when the output is set? Analog signals are checked for measuring range and scaling. Only once the hardware is confirmed does it make sense to look at the logic.

Next come signal and functional tests of individual assemblies in manual mode: a cylinder extends and retracts, a conveyor starts and stops, a flap opens and reports its end position. Fieldbus devices, for example connected via PROFINET or EtherCAT, are checked for communication and diagnostics. Drives are parameterized, and direction of rotation, speed and homing are verified – slowly at first, until the behavior is clear.

The plant is then commissioned step by step: first individual stations in automatic mode, then several stations working together, and finally the complete process. Each step builds on a verified previous one. This keeps it traceable where a fault lies, and there are never too many unknown factors at play at the same time.

• I/O check: test every input and output individually and tick it off in the I/O list
• Manual mode: move assemblies one by one, check end positions and feedback signals
• Drives: parameters, direction of rotation and homing, initially at reduced speed
• Automatic mode station by station first, then as a whole
• Provoke fault cases deliberately: what happens with a missing signal, a malfunction or a power failure?

Optimization, acceptance and an accompanied go-live

Once the process basically runs, optimization during operation begins. This is when details appear that no planning fully anticipates: a sensor switches too late with certain products, a waiting time is too short, a message for the operator is ambiguous. Such points are refined under real conditions, ideally together with the people who will later work at the plant.

Acceptance should also take place under real conditions – with real products, at the intended cycle rate and over a period that also covers less frequent situations. It is based on acceptance criteria agreed in writing beforehand: which functions are tested, which performance must be reached, which remaining items are acceptable? Anything left open at acceptance goes onto a punch list with responsible persons and due dates.

For modernization projects, the changeover adds another dimension. An accompanied go-live with a fallback option means that the old state is backed up and a way back is prepared in case something unexpected happens in the first hours of production. Teams that plan a fallback option rarely need it – but it takes pressure out of the situation and leads to better decisions.

Handover and training

Commissioning is only complete when operators and maintenance staff can handle the plant on their own. This includes handover documentation that describes the actual state – including the changes made during commissioning. Program version, parameters and device configurations should be backed up and handed over with clear versioning.

Training is just as important. Operators need to know how to start and stop the plant and how to restart it after a fault. Maintenance staff need insight into the program structure, diagnostics and typical fault patterns. Instruction directly at the plant, with the real messages and operator screens, works better than a presentation in a meeting room. At Arevano Engineering, handover and training are therefore part of the project, with maintenance and further development afterward on request.

• Current program version as a backup, with version number
• Updated diagrams, parameter and I/O lists
• List of open items with clear responsibilities
• Instruction for operation and maintenance at the plant

Typical pitfalls – and how to avoid them

Most problems in PLC commissioning repeat themselves from project to project. They are rarely complicated from a technical point of view, but they cost time because they only become visible on site.

What these points have in common is that they can be resolved with some lead time. A short checklist that the operator and the commissioning engineer go through together a few days in advance prevents a large share of the waiting time at the plant.

• Missing or outdated documentation: If the circuit diagrams do not match the as-built state, every deviation turns into a search. For existing plants, it helps to record the current state in advance.
• Unverified wiring: Swapped wires and missing jumpers otherwise only show up during the I/O check – and then block every further step.
• Time pressure: A tight downtime window tempts teams to skip tests. A realistic schedule with a buffer and a prepared fallback option are the better safeguard.
• Unclear acceptance criteria: Without agreed criteria, acceptance turns into a negotiation. What “done” means should be settled before commissioning starts.
• Access to third-party systems: Interfaces to ERP, databases, higher-level controllers or equipment from other suppliers need contacts, credentials and test options. Requesting them only on site often means waiting for days.

A note on safety functions

Safety functions such as emergency stop, guard door monitoring or light curtains do not belong in the general functional test. They are tested, documented and accepted separately – even if they run on the same controller as the standard program. The specifications of the machine builder and the operator are decisive here.

This guide describes the technical process of commissioning and is not legal advice. Which tests and records are required for your plant in detail should be clarified with the responsible persons in your company or with appropriate specialists.