How to Commission a New RTU Panel
A new RTU panel arrives at site as a claim: everything inside was built and tested to the drawings. Commissioning converts that claim into evidence, in an order that catches problems while they are still cheap - before power is applied, before field wires are trusted, before operators rely on the data. This is the field sequence for a controls tech bringing up a wellsite or remote-facility RTU panel, from crate to a SCADA screen someone can believe.
RTU Panel Commissioning in one line: To commission a new RTU panel, inspect and verify it dead first - terminations, labels, grounding - then energize in stages and confirm the power rails, prove every I/O point end to end against the point list, establish communications to the SCADA host, and finish by testing alarms and recording a punch list. The order matters: each stage assumes the previous one is proven.
What You Need
Bring the drawing package and I/O list, a multimeter, a loop calibrator or signal simulator, the RTU configuration and its programming tool, and details of the comms path - radio, cellular, or wired - including whatever the SCADA side needs to see the unit. Half of commissioning pain is discovering at site that the point list and the panel drawings disagree, so reconcile the paperwork before travel if possible.
Agree the roles up front too: who operates field devices, who watches the SCADA side, and who signs off. A pre-commissioning check completed by the installer - mounting, conduit, cable pulls, terminations landed - is the assumed starting point for this procedure.
Inspect Everything Before Applying Power
Open the panel and look for transport and installation damage: components shaken loose on the DIN rail, wires pulled from terminals, debris on the backplate, metal shavings from field drilling - a classic cause of mystery shorts. Spot-check termination tightness, confirm the wire numbers match the drawings at a sample of terminals, and verify the ground conductor and shield landings are in place before anything is energized.
Then check the incoming power against the drawings: correct voltage present at the disconnect, correct polarity and conductor sizing, branch protection matching the schedule. The sequence of checks in this dead state is boring by design; every fault found here costs minutes instead of hardware.
Energize in Stages and Verify the Power Rails
Apply power the way described in the site's procedure for first energization: branch devices off, main closed, then branches one at a time while watching for anything unhappy. Measure the DC rails at the distribution terminals, confirm the power supply indicators and any redundancy alarms behave, and if the panel has a battery or UPS, confirm the charger takes over correctly.
Let the RTU boot and confirm it holds its configuration through a deliberate power cycle. A surprising number of field visits end with an RTU that lost its program on the first outage because a backup battery or retention setting was never verified at commissioning.
Prove Every I/O Point End to End
Work the I/O list point by point with a partner: operate or simulate each field device and confirm the right tag changes, with the right value and units, at the RTU and at the SCADA display. That is a point-to-point checkout, and no sampling shortcut replaces it - crossed pairs and off-by-one terminal errors are exactly what full coverage catches. For analogs, inject known signals and check both endpoints and a midpoint; the full method is in the guide to loop checking a 4-20 mA analog input.
Do outputs with the same rigor but more caution: command each output from SCADA and confirm the correct field device operates, with the process in a state where the operation is safe and with the field partner confirming. Record as-found discrepancies rather than silently fixing them - a swapped pair corrected in the panel must also be corrected in the drawings or it will bite the next technician.
Establish Communications and Test the Alarms
Bring up the comms path and confirm the SCADA host polls the RTU reliably: watch for stable updates, sensible poll success, and correct timestamps. Then test the failure direction - disconnect the antenna or link and confirm the host declares the unit offline and someone gets notified. A panel whose comms failure is invisible is a panel whose data quietly goes stale.
Finish with alarms: force a few representative conditions through the real chain, from field device to the notification a human receives. On a platform like Merobix this is also the moment to confirm the new tags trend correctly and the site appears in the dashboards operations will actually watch.
Verifying the Result
Close commissioning with a structured walk of what remains: every discrepancy found, its resolution or its punch-list entry, and sign-off on the I/O list showing each point proven. The discipline of the commissioning punch walk - graded items, owners, dates - keeps the last stubborn items from evaporating into memory.
Leave behind a panel that documents itself: red-lined drawings in the pocket, setpoints recorded, spare fuses in the holder, and the as-left configuration backed up somewhere other than the RTU's own memory.
Common Mistakes
The recurring ones: energizing everything at once and debugging by smell; proving a sample of I/O instead of all of it; testing comms only in the working direction; and commanding outputs without a field partner watching what actually moved. Each saves an hour and risks a return trip - or worse, a wrong action on a live site.
The quietest mistake is documentation drift: fixes made in the panel that never reach the drawings or the SCADA database. A commissioned panel is not just working; it matches its paper.
Frequently Asked Questions
How long does commissioning a new RTU panel take?
It scales with I/O count and comms complexity more than anything else, because the point-to-point checkout dominates the schedule and cannot honestly be sampled. A small wellsite panel with a short point list is a very different day from a facility panel with hundreds of points. Budget from the I/O list, add time for the discrepancies you will find, and resist compressing the checkout - it is the step that catches the wiring errors.
Can I skip the point-to-point check if the panel shop tested the panel?
No. The shop test proved the panel's internal wiring against the drawings; it proved nothing about the field wiring, the terminations made at site, or the mapping through to the live SCADA database. Crossed pairs, off-by-one terminals, and transposed tags are installation-side errors, and the end-to-end check from field device to operator screen is the only test that covers the whole chain the operators will rely on.
What should be left on site when commissioning is done?
Red-lined drawings reflecting every field correction, the recorded as-left configuration and setpoints, a backed-up copy of the RTU program stored off the device, spare fuses, and the signed-off I/O list. The next person to open that panel - possibly years later, possibly at night - inherits exactly what you leave, and a panel that matches its documentation is the difference between a repair and an archaeology project.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.