The short answer
Commissioning Checklist
Commissioning is the ordered set of activities that takes an installed control system from energization through loop checks, functional tests, integrated tests, and performance demonstration to handover, with each activity having prerequisites, a procedure, a record, and a signature. This checklist organizes those activities in the order they must happen and lists what each one produces, so that the project ends with a system that has been proven to work and a set of documents that show how.
Key points
- Commissioning is staged: energize, loop check, function test, integrate, perform, hand over. Each stage has prerequisites.
- Nothing is tested until the drawings it is tested against are current.
- Every test produces a signed record. A test with no record did not happen.
- The utility witnesses the tests that matter to it and signs them.
- Handover includes the record documents, the backups, the training, and the open items list.
The stages
Commissioning a control system is a sequence, and the sequence exists because each stage assumes the one before it. A functional test on a loop that was never loop-checked finds wiring errors dressed up as logic errors. An integrated test on a plant whose sequences were never function-tested finds everything at once and fixes nothing. The stages, their prerequisites, and their records are the checklist.
| Stage | Purpose | Prerequisites | Record |
|---|---|---|---|
| Pre-energization inspection | Confirm the panel and the field installation are complete, correct, and safe to energize | Installation complete; drawings current; FAT report accepted | Inspection checklist with punch list |
| Energization | Apply power in a controlled order and confirm voltages, rotations, and protective devices | Inspection signed; lockout removed by procedure; utility notified | Energization record: voltages, phase rotation, breaker settings |
| Controller and network startup | Load the program and configuration, bring the network up, confirm communications | Energized; backups on hand; IP plan issued | Startup record: firmware, program version, network verification |
| Loop checks | Prove every I/O point from the field device to the HMI | Controller running; I/O list current; instruments installed and calibrated | Loop check sheet per point, signed |
| Functional tests | Prove each device and each control function against the narrative | Loop checks complete for the devices involved | Function test sheet per device or function, signed |
| Integrated tests | Prove the sequences and the interactions across devices and systems, including failure modes | Functional tests complete; process available for testing | Integrated test record per sequence; alarm test record |
| Performance demonstration | Run the process under real conditions for a defined period and show it meets the requirements | Integrated tests complete; operations trained | Performance test report |
| Handover | Transfer the system, the documents, and the responsibility to the utility | Performance accepted; punch list closed or agreed | Handover certificate; record document register; open items list |
Before energization
- Panel installed, anchored, grounded, and bonded; enclosure rating intact; nameplates and SCCR marking present.
- Field wiring complete and terminated per the drawings; every cable labeled at both ends; megger results for power cables on file.
- Instruments installed per the installation details, with calibration certificates, and impulse lines, valves, and supports complete.
- Drawings, I/O list, and instrument list at the current revision, with field changes incorporated or red-lined.
- FAT report accepted, with every FAT punch item closed or carried into the site punch list.
- Lockout applied; energization procedure written and agreed; the utility electrical staff involved.
- Torque check on power terminations; foreign material removed from the panel; filters and fans installed.
Loop checks
A loop check proves one point end to end. For an input, the technician drives the field device or injects a signal at the device terminals, and someone at the HMI confirms the value, the units, the scaling, and the alarm. For an output, the operator commands the device from the HMI and the technician confirms it responds in the field. Every point on the I/O list gets a sheet, the sheet is signed by both people, and the I/O list status is updated. Three points on an analog loop, zero, mid, and full scale; both states on a discrete; both directions on an output. The loop check page has the detail; the checklist item is that every row of the I/O list has a signed sheet before functional testing begins.
Functional and integrated tests
A functional test takes one device or one control function and exercises it against the narrative: the pump starts in HAND, in AUTO on the level call, alternates, fails to prove and drops out, trips on seal-leak, responds to every permissive. An integrated test takes a sequence or a process area and runs it as a whole, then breaks things: kills communications, fails a transmitter, pulls the PLC into program mode, loses power, and confirms that the system does what the narrative says it does on each. The test sheets come from the narrative and the cause and effect matrix, so that every statement in those documents is tested once and signed.
Performance and handover
A performance demonstration runs the system under real process conditions for a defined period, often 7 to 30 days, with the integrator on call and a log of every intervention. Its acceptance criteria are written before it starts: uptime, alarm rate, control performance against setpoints, and the absence of unresolved faults. Handover follows acceptance and includes the record documents at their final revision, the program and configuration backups with a restore test, the spare parts, the training records, and the open items list with owners and dates. The utility signs for all of it, and from that signature the system is theirs.
The checklist
- 01Record documents current: drawings, I/O list, instrument list, narrative, cause and effect, network drawings.
- 02FAT accepted and FAT punch list closed.
- 03Pre-energization inspection complete and signed.
- 04Energization record complete: voltages, rotation, protection settings.
- 05Controller and network startup record complete, with firmware and program versions.
- 06Loop check sheet signed for every row of the I/O list, including spares marked as not tested.
- 07Instrument calibration certificates on file for every instrument.
- 08Functional test sheet signed for every device and control function in the narrative.
- 09Integrated test record signed for every sequence, including the failure cases.
- 10Alarm test record: every alarm in the master alarm database driven, indicated, and notified as configured.
- 11SCADA verification: every display, faceplate, trend group, and report checked against the standard.
- 12Security items: default credentials changed, remote access configured per the design, backups taken and restore-tested.
- 13Performance demonstration complete with acceptance criteria met and the intervention log reviewed.
- 14Training delivered and recorded for operators and maintenance.
- 15Spare parts delivered and listed.
- 16Open items list agreed with owners and dates.
- 17Handover certificate signed by the utility.
Frequently asked questions
- How long does commissioning take?
- Loop checks run at roughly 20 to 40 points per day per two-person team, depending on distance to the field devices. Functional and integrated testing is days to weeks depending on the plant. The performance demonstration is whatever the contract sets. A duplex lift station is commissioned in a few days; a treatment plant in weeks to months. Every project underestimates it.
- Who should witness the tests?
- The utility, through its operations and maintenance staff and its engineer, for every test whose result it will live with: the functional tests on its equipment, the integrated tests including the failures, and the alarm tests. The integrator runs the test; the utility signs that it saw it pass.
- What if the process is not available for testing?
- Simulate what can be simulated, at the field terminals or in the controller, and record which tests were simulated and which were done on the live process. A test done in simulation is repeated on the process when it becomes available, and the open items list carries it until then.
- Can commissioning be skipped for a small change?
- The scope scales; the stages do not. A replaced transmitter gets a calibration and a loop check. A program change gets a functional test of what it changed and a regression check of what it touches. A new pump gets the full sequence for that pump. Skipping the record is how a small change becomes an unexplained problem later.
Related topics
- Factory Acceptance TestingTesting a control system before it leaves the shop: what must exist before the test, how the procedure is built from the narrative and the matrix, how the field is simulated, what is witnessed, and what the punch list and the sign-off mean.
- Site Acceptance TestingProving the installed system with the real field: loop checks first, then end-to-end I/O, real communications, sequences on real equipment, alarms to real recipients, and failure modes on the real network, with the record that becomes the as-built.
- Control NarrativesWhat a control narrative is, what it must contain, how to write statements that can be tested, and how it drives programming, FAT, and the owner’s acceptance.
- Cause and Effect MatricesThe table that lists every trip condition against every action it causes: how to build one, what goes in the cells, how it distinguishes hardwired from software protection, and how it becomes the test.
- I/O ListsThe document that ties the field to the controller: what every I/O list column means, how tags, terminals, and module channels are assigned, spare capacity rules, how the list drives the drawings and the program, and how to keep it true after commissioning.
- Lift Station Backup ControlHow a lift station keeps pumping when the transmitter, the PLC, or the SCADA link is gone: float backup logic, the control transfer relay, redundant-off protection, and how to test it with the controller actually dead.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.