Skip to main content
Call Eric:863-698-8266
CURRYCONTROLS.COMControls & Automation Knowledge Hub
ReferenceDocumentationPLCDesignEngineering

I/O Lists

The 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.

9 min readUpdated Sep 5, 2026Published Sep 5, 2026By Eric Sullivan

The short answer

I/O Lists

An I/O list is a table with one row per controller input or output, giving the tag, the description, the signal type and range, the field device, the controller rack, slot, and channel, the terminal numbers, and the engineering units and scaling. It is produced early in design from the P&ID and the control narrative, it drives the panel drawings, the loop sheets, and the controller configuration, and it is the reference used at loop check and for every change after. A list that is not maintained after commissioning is the first thing that stops being true.

Key points

  • One row per point, one point per row. No merged cells, no notes that carry data.
  • The tag is the primary key. Everything else in the system refers to it.
  • Rack, slot, channel, and terminal numbers are assigned in the list, then copied to the drawings and the program, never the reverse.
  • Carry 20 percent spare per module type, wired to terminals.
  • Check the list at loop check, then keep it under change control for the life of the system.

What the list is for

Every signal between the field and the controller passes through a chain: a device, a cable, a terminal, a module channel, a controller address, a scaled value, a tag on the HMI. The I/O list is the document that records that chain for every point, so that the panel builder wires the right terminal, the programmer configures the right channel, the technician finds the right wire at loop check, and the person troubleshooting in ten years can trace a bad value back to the transmitter. It is a spreadsheet, or a table in a database or an engineering tool, and it is the most referenced document on a controls project.

The columns

ColumnContentNote
TagThe unique identifier, following the site tag convention, such as LIT-101 or P-201-RUNThe primary key; matches the P&ID and the program
DescriptionWhat the point is, in words an operator recognizes: Wet Well Level, Pump 2 RunningBecomes the HMI description and the alarm message base
I/O typeAI, AO, DI, DO, or a network pointDecides the module
Signal4-20 mA loop-powered, 4-20 mA 4-wire, 0-10 V, dry contact, 24 V DC sourcing, 120 V AC, RTD, thermocoupleDecides the wiring and the module channel type
Range and unitsCalibrated range and engineering units: 0 to 20 ft, 0 to 100 psigFeeds scaling and HMI configuration
Field deviceDevice tag, type, manufacturer, and model where knownCross-references the instrument list
LocationWhere the device is: structure, area, elevationFor the cable schedule and the technician
CableCable number from the cable scheduleOne cable may carry several points
Panel, terminal strip, terminalsThe panel and the terminal numbers the field wires land onFrom the panel drawings, assigned here first
Rack, slot, channelController chassis, module position, and channelAssigned here first, then configured in the program
Controller address or tagThe program tag or address that holds the raw valueOn tag-based platforms this is the tag; on address-based platforms it is the address
Fail stateWhat the output does on controller fault or loss of communicationOff, hold, or a defined value; safety-relevant
Alarm or interlock useWhether the point is used for an alarm, an interlock, or bothFlags the points that need testing at SAT
StatusDesign, wired, loop-checked, commissioned, spare, deletedThe list is a living record, and this column is how

Building it

  1. 1

    Extract from the P&ID

    Every instrument bubble and every controlled device on the P&ID generates points: a transmitter is an AI; a pump is at least a run command, a run status, a fault, and an HOA in auto; a modulating valve is an AO and a position AI. Walk the drawing and list them.

  2. 2

    Add what the narrative needs

    The control narrative adds points the P&ID does not show: an intrusion switch, a generator status, a phase monitor, a UPS alarm, a spare float. List them.

  3. 3

    Group by panel and by module type

    Points that land in one panel are wired to that panel; within the panel, group by signal type so that modules fill sensibly.

  4. 4

    Assign modules and channels

    Fill modules in a consistent order, leaving spare channels on each. Keep related points together: a pump status and fault on adjacent channels of the same module, so a module failure takes one pump, not half the plant.

  5. 5

    Assign terminals

    Terminal numbers follow the panel layout convention: a strip per signal type, numbered in channel order, so that the terminal number tells the technician the channel.

  6. 6

    Issue it to the drawings and the program

    The panel drawings, the loop sheets, and the controller configuration are produced from the list. When they disagree with it, the list wins and the other document is corrected.

Spare capacity

Every project adds points after design, and every plant adds points after commissioning. The list allocates spare channels, commonly 20 percent per module type and at least one spare of each type in every panel, and the spares are wired to terminals so that using one is a field connection and a configuration change, not a panel modification. Spares are listed as rows with the status Spare, so they are visible and their terminals are reserved.

Keeping it true

The list is correct on the day of loop check, when each row was tested from the field device to the HMI and marked. After that it drifts unless it is under change control: a point added for a new float, a channel moved when a module failed, a range changed when a transmitter was replaced. Each of those is a change record that updates the list, the drawing, and the program together. The list should live somewhere that every change references, and its Status column and revision history are how a reader knows whether to trust a row.

  • One master, in one place, with a revision number and a date on every issue.
  • Field changes marked up and returned to the master within days, not at project close.
  • A periodic comparison of the list against the controller configuration, using the platform export, to catch changes made at the keyboard.
  • Deleted points kept as rows with the status Deleted, so the terminal and channel history is preserved.

Frequently asked questions

Is the I/O list the same as the instrument list?
No. The instrument list is one row per instrument with its process data, range, and specification; the I/O list is one row per controller point. A transmitter appears once on the instrument list and once or more on the I/O list, depending on its signals. The two cross-reference each other by tag.
Should network points be on the I/O list?
Yes, as rows with a network I/O type, the device address, and the register or tag in the device. A drive on a network provides a dozen points that need the same documentation as hardwired ones, and a list that omits them is incomplete.
Who owns the I/O list after commissioning?
The utility, held by whoever owns the controller configuration. The integrator delivers it as a record document; from then on it is maintained with the program. An integrator who keeps the only copy is a risk to the utility.
What tag convention should we use?
The site standard, and if there is none, one based on ISA-5.1 for instruments and a consistent equipment-based scheme for devices, written down before the first tag is assigned. Changing the convention after commissioning is a project of its own.

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.