The I/O list — columns that matter
What an I/O (signal) list must contain for design, panel building, programming, loop check and maintenance, with a recommended column set and common mistakes.
The I/O list (signal list) is the single table that links process design, electrical design, PLC/DCS programming, HMI, loop check and maintenance. If it is incomplete, every later phase invents its own version.
Recommended columns
| Group | Columns |
|---|---|
| Identification | Tag (e.g. FT-1201), description, P&ID number, unit/area |
| Signal | Signal type (AI/AO/DI/DO/PI, HART, fieldbus), range and engineering units, 2-/3-/4-wire, loop powered or externally powered |
| Hardware | Cabinet, controller, rack/station, slot, channel, terminal numbers, cable number |
| Processing | Scaling (raw min/max → EU min/max), filtering, square root, alarm limits (HH/H/L/LL), deadband, fail-safe value |
| Safety & interlocks | SIL/safety function reference, interlock reference, normal state (NO/NC), fail-safe direction |
| Status | Revision, design status, loop-check date and signature |
Rules that save time
- One row per channel, including spares — so the list doubles as the channel allocation.
- Use consistent tag naming (ISA-5.1 style letters or your plant standard) — HMI, alarms and historian take the tag as is.
- Fill the scaling and units before programming; most commissioning mistakes are scaling (e.g. 0–10 bar vs 0–16 bar) and wiring type (2-wire vs 4-wire).
- Plan 10–20 % spare channels per module type and cabinet.
- Keep it in a controlled, versioned format and generate PLC/DCS bulk data from it instead of retyping.
Typical mistakes
- Digital inputs without defined normal state → inverted alarms.
- Missing information about external power for 4-wire transmitters.
- Channels reassigned on site but not updated in the list.
Connections
Open in Knowledge Graph →Loading the map…
Sources
Updated 2026-10-04