Instrument Index vs I/O List vs Line List. What Each Document Is For.
The differences between an instrument index, an I/O list, and a line list, who consumes each document, and why mixing them causes problems during detailed engineering.
Engineering documents for a control system project come in layers. The same instrument appears in an instrument index, an I/O list, and sometimes a line list. The documents overlap but each serves a different purpose and a different audience. Mixing them leads to data loss, orphaned references, and the kind of scope gap that surfaces during commissioning.
Instrument index
The instrument index is the master list. Every instrument tag that appears on the engineering documents, on any P&ID, utility diagram, or equipment drawing lives here.
What it contains
- Tag number
- Description
- Service, process area
- P&ID reference, drawing number plus revision
- Manufacturer, model, when selected
- Datasheet reference, when issued
Who consumes it
- Project engineers tracking instrument count and scope
- Procurement building the instrument purchase package
- Document control routing datasheets for review
- Commissioning building the loop-check register
What it does not contain
- Signal class, AI, AO, DI, DO. That belongs in the I/O list
- PLC channel assignment. That belongs in the I/O list
- Wire numbers. Those belong in the cable schedule
An instrument index entry does not imply a wired signal. A local pressure gauge is in the instrument index. It is not in the I/O list.
I/O list
The I/O list is a filtered, annotated extension of the instrument index. It contains only the instruments wired to a PLC or DCS, with the signal class and channel assignment added.
What it contains
- Tag number, from the instrument index
- Signal class, AI, AO, DI, DO
- PLC rack, slot, channel
- Data type, INT, REAL, BOOL
- Process variable, flow, pressure, level, temperature
- Range and engineering units
- Protocol, 4-20mA, HART, fieldbus, hardwired discrete
- Connected equipment
- BPCS or SIS flag
Who consumes it
- Control system integrator loading the tag database
- HMI, SCADA builder mapping display tags
- Loop-check technician during commissioning
- PLC programmer importing tags into TIA Portal, Studio 5000, or equivalent
What it does not contain
- Local-only indicators, no wired signal
- Pipe specs, line sizes, services, that is the line list
The I/O list drives card sizing, cabinet layout, and the PLC tag database. Its count directly determines hardware cost.
Line list
The line list catalogs every pipe segment on the P&IDs. It is oriented around lines, not instruments, but it cross-references the instruments that sit on each line.
What it contains
- Line number, e.g.
4"-CS-101-A1A - Size
- Pipe spec, CS, SS, alloy, insulation
- Service, process fluid, utility
- From, to, equipment tags at each end
- Design pressure, design temperature
- Insulation spec
- Heat trace requirement
Who consumes it
- Piping designer producing the pipe class library and 3D model routing
- Stress engineer feeding pipe stress analysis inputs
- Process engineer verifying service assignment
- Estimator building bulk material takeoff
- I&C engineer routing signal cables alongside process lines
What it does not contain
- Instrument tag information. Lines reference instruments by tag, but the detail sits in the instrument index, I/O list
Three-way comparison table
| Attribute | Instrument Index | I/O List | Line List |
|---|---|---|---|
| Primary key | Tag number | Tag number | Line number |
| Scope | All instruments | Wired instruments only | All pipe segments |
| Includes local gauges | Yes | No | No, instruments are cross-references only |
| Signal class column | No | Yes, AI, AO, DI, DO | No |
| PLC channel assignment | No | Yes | No |
| Range and units | No, references datasheet | Yes | No |
| Pipe spec | No | No | Yes |
| Design pressure, temperature | No | No | Yes |
| Primary author | I&C, instrument engineer | I&C, controls engineer | Piping designer |
| Primary consumer | Procurement, document control | PLC programmer, loop-check | Piping, stress, estimating |
| Created in FEED. | Preliminary | No, follows index | Preliminary |
| Issued for construction | Yes | Yes | Yes |
| As-built version required | Yes | Yes | Yes |
| Source document | P&ID | Instrument index plus P&ID | P&ID |
Worked example. The same separator skid across all three documents
Consider a gas separator skid with an inlet flow measurement loop, a level control loop, and a high-high level trip. The three instruments are FT-101, flow transmitter, LT-405, level transmitter, and LSH-405, level switch, SIS.
**In the instrument index. **
| Tag | Description | P&ID | Manufacturer | Datasheet |
|---|---|---|---|---|
| FT-101 | Separator inlet flow transmitter | PID-001, Rev C | Endress and Hauser | DS-0101 |
| LT-405 | Separator level transmitter | PID-001, Rev C | Rosemount | DS-0405 |
| LSH-405 | Separator high-high level switch | PID-001, Rev C | Gems Sensors | DS-0406 |
| PI-110 | Separator inlet pressure gauge, local | PID-001, Rev C | Wika | DS-0110 |
PI-110 is a local pressure gauge with no wired signal. It appears in the instrument index but will not appear in the I/O list.
**In the I/O list. **
| Tag | Loop | Class | Range | Units | BPCS, SIS | Cabinet |
|---|---|---|---|---|---|---|
| FT-101 | 101 | AI | 0 to 500 | m3, h | BPCS | MCC-101 |
| LT-405 | 405 | AI | 0 to 3000 | mm | BPCS | MCC-101 |
| LSH-405 | 405 | DI | , | , | SIS | SIS-101 |
PI-110 is absent. LSH-405 is in a separate SIS cabinet. The ranges and units for FT-101 and LT-405 are confirmed from the datasheets.
**In the line list. **
| Line Number | Size | Spec | Service | From | To | DP | DT |
|---|---|---|---|---|---|---|---|
| 4"-CS-101-A1A | 4" | CS | Gas | Feed header | V-101 | 5500 kPa | 60 degC |
| 2"-CS-405-A1A | 2" | CS | Gas | V-101 | Flare | 5500 kPa | 60 degC |
FT-101 sits on line 4"-CS-101-A1A. That cross-reference lives in the line list, not in the instrument index or the I/O list. The piping designer knows the process conditions on that line. The I&C engineer uses those conditions when specifying FT-101's pressure rating.
Project lifecycle. When each document is created
Each document is published at different stages of a project, based on what information is available.
FEED, Front End Engineering Design
The preliminary instrument index is created here, drawn from the preliminary P&IDs. Tag counts are used for estimating and scope definition. The I/O list and line list are not yet issued because too many decisions are still open.
Basic engineering, detailed design, 30-60% complete
The instrument index is expanded and revised to match the issued-for-design P&IDs. The I/O list is created as the instrument index stabilizes. Signal classes are assigned. The PLC hardware bill of materials is generated from the I/O count. The line list is issued for piping design.
Issued for construction, 90% complete
All three documents are at the IFC revision. The instrument index drives the procurement package. The I/O list drives the PLC tag database load. The line list drives the pipe spool fabrication schedule.
Commissioning and as-built
The instrument index is updated with as-installed manufacturer and model data. The I/O list is updated with confirmed PLC channel assignments from the loop check. The line list is updated with as-built dimensions and any field changes. All three are issued as the as-built record at project close.
How they connect
+---------------------+
| Instrument Index | <- master list, all instruments
| (tag, description) |
+----------+----------+
|
+-------------+-------------+
v v
+------------------+ +------------------+
| I/O List | | Line List |
| (wired subset, | | (pipes, cross- |
| signal class) | | referenced |
| | | to instruments |
+------------------+ +------------------+
The instrument index is the root. The I/O list is a wired-only subset with signal class and channel assignment. The line list is a peer document keyed on line number but cross-referenced to instrument tags.
All three should share a single source of truth. When an instrument is added to the instrument index, the I/O list and line list update accordingly. When an instrument is retagged, every reference propagates.
Who owns each document
Ownership ambiguity is the cause of most version-control failures on these documents.
The instrument index is owned by the lead instrument engineer on the EPC or engineering team. Document control holds the controlled master and issues revisions. Procurement, commissioning, and other disciplines consume it but do not own it. The instrument index master class guide covers in depth how to structure, maintain, and gate the instrument index across project phases.
The I/O list is owned by the controls or systems engineer, sometimes by the control system integrator for the portions covering PLC channel assignment. On projects where the integrator and the EPC are different companies, agree on ownership at kickoff. A common failure mode. The EPC issues the instrument index and expects the integrator to build the I/O list, but the integrator expects to receive a draft. The gap gets discovered at the PLC factory acceptance test.
The line list is owned by the piping lead or lead piping designer. It is a piping document, not an I&C document. I&C engineers consume it for cable routing and pressure, temperature data. They do not own it.
Where they come from
The P&ID is the canonical source for all three. A structured extraction from a P&ID set produces.
- The instrument index directly. Every bubble becomes a row
- The I/O list by filtering to wired signals and assigning signal class
- The line list by parsing line tags and cross-referencing connected equipment
See P&ID to I/O list and P&ID to line list for extraction workflows.
Version control
These documents change together. A revision to the P&ID propagates to the instrument index first, then to the I/O list and line list. Treat the P&ID revision number as the parent revision. Tag each downstream document with the P&ID revision it was generated from.
For projects with frequent drawing revisions, brownfield revamps, in-progress design, a revision comparison workflow that produces an added, removed, modified diff is the only way to keep downstream documents in sync without missing changes.
Related
- P&ID to I/O list
- P&ID to TIA Portal XML tag table. The Siemens-specific I/O list output
- P&ID to equipment list
- P&ID to line list
- P&ID revision comparison
- The Line List Explained: What's In It and Where the Data Comes From. A deeper look at line list columns, data sources, and how it feeds stress and isometrics
- PLC tag naming conventions
- ISA 5.1 instrument identification
- ISA 5.1 vs IEC 81346. When a project uses both identification systems and how the instrument index carries the cross-reference
- ANSI/IEEE C37.2 device function numbers. The identification system that sits alongside ISA 5.1 on electrical-scope documents
FAQ
Which document does a commissioning technician use most during loop checks.
The I/O list, because it maps each tag to a PLC cabinet, rack, slot, and channel. The technician needs to know where to apply a test signal and where to confirm receipt in the PLC. The instrument index is referenced for manufacturer and model. The line list is rarely used during loop checks. A well-prepared commissioning package has the I/O list sorted by loop number, with the corresponding P&ID page noted so the technician can trace the signal path.
If a flow transmitter also has a HART output for diagnostics, does it appear twice in the I/O list.
Once in the I/O list for the 4-20mA signal, signal class AI, with "HART" noted in a Protocol column. The HART secondary variable does not create a separate I/O row unless it is wired to a second analog input channel. HART multiplexers that read secondary variables create a separate software tag in the DCS, but that is a configuration item, not a new I/O row.
Can the line list include instrument nozzle connections.
Yes, as an extension. Some line lists include a nozzle schedule that cross-references each nozzle on a vessel or exchanger to the line that connects to it and to the instrument tag sitting on that nozzle. This is most common on large pressure vessels with many connections. The nozzle schedule is usually attached to the line list as a separate tab or sub-table, not merged into the main line list rows.
At what point does the instrument index become the as-built record.
After commissioning is complete and all field changes have been incorporated. The as-built instrument index should reflect. Final tag numbers as installed, confirmed manufacturer and model numbers, confirmed datasheet revision, and any tags that were added or removed during construction. On facilities that operate under continuous improvement programs, the instrument index is a living document that is updated whenever an instrument is replaced or added. The P&ID revision is always the trigger. The index follows the drawing.
How do I cross-reference the three documents without duplicating data.
Use the tag number as the join key between the instrument index and the I/O list. Use the line number as the join key between the line list and the other two. In a single Excel workbook, VLOOKUP or XLOOKUP on tag number lets the I/O list pull description and P&ID reference from the instrument index without duplicating those fields. Power Query is more reliable than VLOOKUP for large lists because it handles missing keys explicitly instead of returning error values that get overlooked during QA.