I/O List.
An I/O list is a structured spreadsheet enumerating every analog input, analog output, digital input, and digital output a control system reads or drives. It is the first document produced from a P&ID set and the source-of-truth for PLC, DCS, and SIS engineering. Marshalling, wiring, programming, HMI scoping, and commissioning all reference it.
What I/O List means.
The I/O list is the translation of a P&ID set into a form the controls-engineering team can act on. Each row represents one field signal. The I/O list does not cover every instrument in the facility. Only those wired to the control system. Mechanical gauges, thermowells, and pressure-relief valves with no electronic output are in the instrument index but not the I/O list. The four signal classes, analog input, analog output, digital input, and digital output, map directly to PLC or DCS I/O card types. Getting this classification right early is critical because I/O cards are long-lead items. An error discovered after the panel is wired means physical rework. Beyond the standard AI, AO, DI, DO classes, HART-enabled cards carry both the 4-20 mA analog value and a digital communication channel on the same pair. Foundation Fieldbus and Profibus-PA cards replace analog wiring with a digital bus. These variants need a separate column or flag in the I/O list so the panel builder wires the correct card type.
What columns belong in every I/O list.
Tag number, per the project's naming convention. ISA 5.1, KKS, DIN 19227, IEC 81346, NORSOK, or in-house, service description, signal class, AI, AO, DI, DO and HART or Fieldbus variant where applicable, engineering range with engineering units, source P&ID drawing number, and target system, BPCS or SIS. These six columns are the minimum viable I/O list. Every downstream consumer can work from them. Most projects add. Loop number, area or unit code, vendor model number, cable number, junction box reference, marshalling terminal, PLC rack and slot, and a notes column for exceptions. A mature I/O list at issued-for-construction typically runs 20 to 30 columns.
What is in scope on an I/O list, and what is out.
In scope. All field instruments connected to the BPCS or SIS, including transmitters, control valves, on, off valves with solenoid or actuator, motor starters with DI, DO status and command, analyzers, and level sensors. Out of scope by convention. Pneumatic-only loops with no electronic signal, pressure-relief valves, they go to the instrument index and relief-device register, local indicators with no output, and power supply panels. If a brownfield project has instruments wired to a marshalling panel but not connected to the logic solver, their inclusion depends on project scope. The scope boundary should be stated explicitly in the I/O list header or project-specific instructions.
How is the BPCS vs SIS split represented on an I/O list.
Most projects maintain one master I/O list and then filter or fork it into BPCS and SIS workbooks for the respective vendors. The SIS I/O list goes to the safety system vendor for logic-solver configuration. The BPCS I/O list goes to the DCS or PLC integrator. Tags that appear in both, for example, a transmitter whose 4-20 mA signal is monitored by both systems get a row in each workbook with the system flag noted. IEC 61511 requires that SIS field signals are physically separate. They do not share I/O cards or wiring with the BPCS, so even a monitoring-only signal in the SIS needs its own SIS I/O row with its own SIS hardware assignment.
What does an I/O list error cost on a project.
Wrong signal class means the wrong card type is purchased or configured. An AI card cannot drive an analog output. A DI card cannot read a 4-20 mA signal. Fixing this after panels are wired means physically swapping cards, re-labeling terminals, and re-testing the loop. Missing tags mean a field instrument has no home in the control system. Duplicate tags create ambiguous wiring labels and break loop-folder cross-references. The I/O list is also the boundary document during contractor handover. A clean, complete I/O list at that point is the difference between a predictable FAT and one that stalls on day one.
How are I/O list revisions and exports handled.
The I/O list is a controlled document. Every change goes through the project's MOC or document-control process. Revision letters and change descriptions are tracked in a header block or a separate change-log tab. The master format is Excel on most projects because the downstream consumers, PLC programmer, panel builder, commissioning team all work in Excel. Vendor-specific import formats, TIA Portal XML for Siemens S7, Rockwell L5X for Allen-Bradley, PLCCreator Device IO List are exported from the master rather than maintained separately. The master is the source of truth. The vendor format is a snapshot.
Standard I/O list columns
The 14 columns most projects use. Any specific project tightens or extends the list, but these are the canonical headers downstream tools, TIA Portal, Studio 5000, PLCCreator map to.
| Column | Example | Purpose |
|---|---|---|
| Tag number | FT-101 | Unique instrument identifier in the drawing’s own dialect |
| Loop number | 101 | Groups instruments in the same control loop |
| Instrument type | Flow transmitter | Plain-language device type |
| Signal class | AI | AI, AO, DI, or DO. Drives PLC, DCS module selection |
| Description | Feed line flow to E-101 reboiler | Service text, carried into PLC tag comment |
| P&ID reference | PID-001 | Drawing number |
| Page number | 1 | Sheet on that drawing |
| Service, area | Crude unit overhead | Process area, used for site segmentation |
| Process variable | Flow | First-letter expansion, F for flow, P for pressure, etc. |
| Range | 0-500 m3, h | Calibrated span |
| Protocol | 4-20 mA HART | Signal protocol. Drives marshalling and DCS card selection |
| Connected equipment | E-101 | Equipment tag the instrument is on |
| BPCS, SIS | BPCS | Layer of protection. SIS rows route to the safety controller |
| Notes | Vendor-supplied, calibrated 2026-02-12 | Free text for project-specific information |
Common questions
What format is an I/O list usually in.
Who owns the I/O list.
What is the difference between an I/O list and an instrument index.
How does signal class get determined for each tag.
Does the I/O list include HART or Fieldbus instruments differently.
Can the I/O list be built before the P&IDs are complete.
Get the I/O list template.
Fourteen columns with the signal class as a dropdown, auto-filter on every column, frozen header. Plain .xlsx.