I/O List
Template (Excel)

An I/O list (also called an Input/Output list or IO schedule) is the register of every analog and digital signal exchanged between the field instruments and the control system (DCS, PLC, SIS, or vibration monitoring). For each signal it records the tag number, service description, signal type (analog input AI, analog output AO, digital input DI, digital output DO, HART, Foundation Fieldbus, Profibus), engineering and raw range, control system destination, cabinet and marshalling reference, module slot and channel, power source, intrinsic safety, hazardous area, SIL classification per IEC 61511, and the C&E matrix reference.

Required columns: tag number per ISA 5.1, service description, P&ID reference with revision, loop number, signal type, engineering range and raw range (typically 4-20 mA mapped to engineering units), control system destination, cabinet reference, module slot and channel, power source, intrinsic safety flag, hazardous area classification per IEC 60079, SIL classification for safety-critical signals, C&E matrix reference for SIS signals, cable number cross-referenced to the cable schedule. For SIS-specific I/O lists, add proof test interval and SIF identifier columns.

Pathnovo, an engineering document intelligence platform, extracts every instrument tag and signal annotation from your P&IDs and cross-references the corresponding instrument datasheets to populate the signal type, range, and control system destination. SIS-classified signals are flagged automatically from C&E matrix cross-reference. Typical project turnaround is 48 hours for the initial batch with 99.5% contractual accuracy. Output is configurable to your DCS or PLC vendor format (Honeywell Experion, Emerson DeltaV, Yokogawa CENTUM, Siemens PCS 7, ABB Ability 800xA). See the I/O list automation workflow.

The instrument index is the master register of every instrument on the project (one row per instrument tag, capturing physical attributes like sensor type, range, material, datasheet reference). The I/O list is the subset of the instrument index covering only instruments wired into the control system, augmented with control-system-side data (signal type, cabinet, module slot, channel, cable number). Instrument index is owned by the instrumentation discipline; I/O list is co-owned with control system engineers and is the handoff document to system integrators. See the instrument index template.

Safety-instrumented signals (sensors, final elements, and logic solver I/O) are identified during HAZOP and SIL determination. Per IEC 61511, each signal participating in a Safety Instrumented Function (SIF) is assigned SIL 1, SIL 2, or SIL 3. The I/O list SIL Classification column flags these signals, drives separate SIS hardware (Triconex, Honeywell Safety Manager, HIMA, Yokogawa ProSafe-RS) rather than the BPCS, and triggers redundancy requirements per the SIL level. Pathnovo cross-validates the I/O list against the cause and effect matrix to catch SIL-classified signals routed to the wrong system. See the SIL standard reference.

The I/O list captures the cabinet, marshalling reference, module slot, and channel for each signal at the control-system end. The cable schedule captures the field-end-to-marshalling-end cable run for each cable, with from / to tags, cable type, voltage, length, drum number, glanding, and route. The two are joined on the Cable Number column. Industry practice: I/O list is generated first from the P&IDs and DCS architecture, then the cable schedule is generated from the I/O list plus the SLD and the plot plan. See the cable schedule template.

Smart instrument signals (HART overlaid on 4-20 mA, Foundation Fieldbus H1 / HSE, Profibus PA / DP) are captured in the Signal Type column. Smart signals carry both the primary process value and diagnostic data; the I/O list typically captures the primary value as the signal range entry, with diagnostic configuration handled in the asset management system (Emerson AMS, Honeywell FDM, Yokogawa Plant Resource Manager). For Foundation Fieldbus, multiple instruments share one H1 segment, so the I/O list captures the segment ID along with the per-instrument identifier on that segment.