What Is Not an Instrument. Tags That Don't Belong on the I/O List.
An I/O list counts wired field signals, not every tagged item on a P&ID. Hand valves, local gauges, line numbers, and legend entries carry tags but earn no channel.
The trap on a brownfield sheet is that a hand valve, a line number, and a legend entry all wear tag-shaped text. Count them as instruments and the channel budget is wrong before the design starts.
Missing instruments is the error everyone watches for. The quieter one, the one that survives all the way to the rack-sizing spreadsheet, is counting things that were never channels.
What earns a row
A bubble is a drawing notation, not a definition. For the I/O list, an instrument is a field device that terminates a wired signal at a PLC or DCS channel. Three conditions, all required.
- It exists in the field as a real instrument or actuator.
- A signal path connects it to the control or safety system. 4-20 mA, a discrete contact, HART, Profibus, fieldbus, any wired link to an I/O card.
- The signal lands on a channel that shows up in the PLC config and on the list.
Miss any one of the three and there is no row, bubble or not, clean ISA code or not.
Signal class then follows the tag, not a judgment call. TT, PT, FT, LT, PDT are AI. TCV, FCV, PCV, LCV are AO. XV, SDV, ESDV and solenoids are DO. PSH, LSL, FSL, TSH are DI. ZSO, ZSC, ZT wired back are DI or AI depending on whether the output is a contact or an analog signal. Same prefix, same class, every row. For the symbols and signal lines behind these codes, see P&ID instrument symbols explained.
Manual valves and local-only devices
A hand valve with a handwheel and no actuator is wired to nothing. Zero channels. It goes on the valve list with the rest of the piping hardware. The exception is a position switch. Bolt a ZSO-501 onto that valve and run it back to the PLC, and the switch earns a DI. The valve body still belongs on the valve list. Two different items on one piece of steel.
Local indicators are the same story. A pressure gauge, a sight glass, a local TI with no wire to the control system goes on the instrument index, not here. The signal line settles it. A plain circle with nothing leaving it toward the control system is local-only. The split between the three documents is laid out in instrument index vs I/O list vs line list.
Line numbers, connectors, and notes
4"-CS-101-A1A is structured, organised, and not an instrument. It is a line number, and it goes on the line list, along with every other size-material-spec string boxed against a pipe run.
An off-page connector reading to PID-002, FCV-302 is a cross-reference, not a second valve. FCV-302 is counted once, on PID-002, where its bubble and signal line live. A unit prefix changes nothing. 12-PT-101 is one transmitter and one AI row, not an address to throw away.
The legend, the notes block, the title block, the revision table, a column header that happens to read AI. Drawing furniture, all of it, and none of it a device.
Vendor model codes
Now and then a bubble carries a positioner or damper-actuator model number instead of a tag, because someone copied it straight off the cut sheet. The bubble is still a real instrument. The model code just is not its tag. Pull the tag from the equipment list, an adjacent reference, or the notes, and keep the model number as an attribute of the row.
One bubble, one channel
A control valve arrives with its tag and a fistful of modifiers. An M for a motor, a spring-return symbol, a positioner. None of it adds a channel. FCV-302 is one AO, the command from the DCS to the actuator. The actuator type is a column, not a row. The only thing that adds a row is a separate signal, a limit switch wired back on its own.
The mirror case. Two separately tagged bubbles inside one housing are two instruments and two rows. A combined temperature and humidity sensor with its own tags is two AI. The housing is not a third row.
PID-001, worked
The feed section of a gas-processing unit. What you find, and where each item lands.
- PT-101, pressure transmitter on the separator inlet, signal line to the DCS. AI row.
- FCV-302, flow control valve on the bypass, modulating, signal to the DCS. AO row.
- ZSO-501, open limit switch on a shutdown valve, signal to the SIS rack. DI row.
- HV-305, hand isolation valve on a sample line, handwheel only. Valve list.
- PI-110, local gauge at the inlet, no signal line. Instrument index.
4"-CS-101-A1A, line number boxed on the main run. Line list.to PID-002, FCV-302, off-page arrow. Counted on PID-002, not here.- the legend block in the corner. Ignored.
Three rows from eight items examined. PT-101, AI, FCV-302, AO, ZSO-501, DI. "Count every bubble" hands you four. "Count every tag-like label" hands you the legend and the connector on top of that. Both are wrong, and both are wrong in a direction that costs money.
Why it matters
Channel count drives card count, card count drives rack and cabinet sizing, and the spare percentage comes off the total. Count a row of hand valves as DO and you buy the cards and the rack space to wire nothing. Miss a bank of limit switches and the SIS rack comes up short at commissioning. Carry model codes as tags and the list cannot go to PLC programming until someone cleans it, which is far worse once it has been issued to other disciplines.
So before a bubble earns a row. It exists, a signal line reaches the control system, and the signal lands on a channel. Hand valves, local indicators, line numbers, off-page references, legend text, none of them clear that bar. One bubble, one channel, and the function letter sets the class.
BPCS versus SIS is the next question. It decides which rack the channel lands on and which columns the list needs, and it is covered in SIL-rated I/O and BPCS separation.