Prepare I/O Checks Before Site Startup

Establish a Controlled I/O Basis

The check should start from the latest approved I/O list and drawing set. Each point should identify, as applicable:

• equipment or instrument tag;
• service description;
• signal type;
• normal and fail state;
• engineering range and units;
• field cable and junction-box reference;
• panel terminal;
• PLC or remote-I/O address;
• HMI/SCADA tag;
• alarm, permissive, interlock, or sequence use;
• test method and expected result.

Uncontrolled spreadsheets copied from an earlier project should not become the site test basis. The list must match the installed panel and the software revision being tested.

Confirm Identity Before Function

The device tag, cable marker, junction-box terminal, panel terminal, drawing reference, PLC address, and HMI tag should describe the same point. A signal can appear electrically correct while belonging to the wrong field device or wrong terminal.

Digital inputs are checked for the intended contact state and de-energised behaviour. A normally closed protection contact, a normally open run feedback, and a selector status cannot be interpreted correctly from the PLC value alone. The test record should show the physical condition that produced each state.

For analogue signals, polarity, loop power, range, units, and device configuration are checked before scaling is accepted. RTDs, thermocouples, pulse inputs, frequency signals, and communication data each require an appropriate test method.

Verify Scaling, Direction, and Quality

An analogue check should use more than one point. Minimum, mid-range, and maximum or another suitable set of values confirm scaling and direction. The field device, PLC engineering value, HMI display, alarm thresholds, and reported value should agree.

The check must also confirm what happens outside the valid range or when the signal is lost. Open circuit, underrange, overrange, bad quality, or communication loss should create the defined diagnostic state and control response. The HMI should not continue presenting a stale number as valid.

For outputs and position commands, increasing the control value should produce the intended physical direction. Valve fail position, actuator stroke, VFD speed reference, and actual response are verified against the process requirement.

Test Commands with Feedback

A digital output is not closed merely because voltage appears at a terminal. A motor start test includes command source, starter or drive response, run feedback, trip feedback, local/remote status, and applicable permissives. A valve test includes open and close command, movement, end-position feedback, timeout, and mismatch alarm.

Where equipment is not safe or ready to operate, the test method should be defined in advance using approved isolation, simulation, or dry-test conditions. Every temporary lift, force, or simulated feedback must be logged and removed.

Prove Permissives, Interlocks, and Alarms

I/O checks should connect the signal to its control purpose. If a level switch is a pump permissive, the check confirms both the input and the blocked-start indication. If pressure loss is a running interlock, the check confirms the trip or controlled stop, alarm, and reset condition. If a signal is monitoring-only, the test confirms that it does not create an unintended equipment action.

This step exposes discrepancies between the I/O list, control philosophy, PLC program, and HMI text before full sequence testing begins.

Classify and Close Exceptions

Each failed point should be assigned to a technical category such as field wiring, panel termination, drawing error, PLC addressing, signal configuration, scaling, mechanical feedback, communication, or software logic. The record should identify the responsible party, corrective action, retest status, and affected documents.

A point is not complete while it depends on an undocumented force, lifted wire, bypassed interlock, or assumed device state. Open points can remain, but their impact and ownership must be visible.

Use the Completed Check as a Startup Baseline

After the I/O and loop checks are complete, sequence and process testing can proceed with confidence that the signal paths are known. If the plant then behaves unexpectedly, the team can distinguish a new process or software issue from an unverified field connection.

The final I/O record should match the as-commissioned PLC addresses, ranges, units, and field wiring. It becomes a maintenance reference and a controlled starting point for future modifications.

Next steps: Back to Engineering Notes · Commissioning service · Instrumentation service · Discuss Scope