Instrument Index.
An instrument index is the master register of every tagged instrument across a facility, with metadata richer than what fits in an I/O list. Teams use it as the cross-reference between P&ID tags, datasheets, calibration records, loop folders, and SIS proof-test schedules.
Three drawings included on a new account.
What Instrument Index means.
The instrument index sits between the P&ID set and the instrument datasheet library. It collects every tagged item into a single structured table: the wired instruments in the I/O list, and alongside them the mechanical gauges, pressure-relief valves, rupture discs, thermowells, and any other device that carries a tag on the P&ID. The index is the document that establishes tag uniqueness across the entire facility. Two instruments on two different P&ID sheets cannot share a tag number. The instrument index enforces that. In detailed engineering, it is typically created early, populated from P&ID extraction or transcription, and then extended through procurement, construction, and commissioning as manufacturer data, calibration ranges, and location coordinates are confirmed. ISA 20 datasheets are referenced by tag from the instrument index, giving every instrument a traceable record path.
How it differs from an I/O list
An I/O list answers the question. What does the PLC or DCS need to read or drive. An instrument index answers the question. What physical devices exist in this plant and where do their records live. The instrument index includes pressure-relief valves, mechanical gauges, thermowells, and sight glasses that have no signal class because they are not wired to a control system. On a typical facility the instrument index can be twice the row count of the I/O list. Most projects maintain both. The I/O list is the controls-engineering record, the instrument index is the operations and maintenance record.
Typical columns
Tag number, service description, equipment served or location, P&ID drawing number and revision, loop number, instrument type or function, manufacturer, model number, process connection, engineering range with units, calibration range, accuracy class, calibration interval, ISA 20 datasheet reference, location coordinates or elevation, control system point ID, if wired, SIL allocation, if SIS-classified, commissioning status, and as-built confirmation flag. A complete instrument index at plant handover runs 30 to 40 columns. The minimum viable version at issued-for-design is about 12 columns. Tag, description, P&ID reference, loop, type, and range.
Revision control and ISA 20 linkage
The instrument index is a controlled document. Each row carries a revision marker so you can tell whether the datasheet, calibration, and loop-folder record are current with the latest P&ID revision. ISA 20, Specification Forms for Process Measurement and Control Instruments, Primary Elements, and Control Valves provides the standard datasheet format that most owner-operators reference from the instrument index. The index row points to the datasheet number. The datasheet carries the full specification. On projects following ISO 10628-2 or project-specific standards, similar linkage structures apply.
When the instrument index is created
On most projects the instrument index is opened at the start of detailed engineering, seeded from an initial P&ID review, and then kept current through every subsequent P&ID revision. Construction and commissioning add physical data, serial numbers, calibration certificates, as-built loop numbers. At mechanical completion the instrument index is handed over to the operating company as part of the as-built documentation package. From that point forward it lives in the plant's maintenance management system or a dedicated instrument-management database and is updated through the MOC process.
What makes an instrument index hard to build
P&ID sets across large facilities span dozens to hundreds of drawings, often with tags in multiple naming conventions if the plant was built in phases. Tag uniqueness conflicts, inconsistent abbreviations between drawing packages, and instrument types that appear only once, unusual analyzer variants, specialty flow meters all slow manual transcription. Processing the full P&ID set into a structured tag register is far faster than hand-transcription, though the result still needs reconciliation against procurement records and existing datasheet files.
Instrument index columns grouped by the document that owns them
The index is the cross reference between every other instrumentation document. Grouping the columns by source is what makes it maintainable, because each group goes stale for a different reason.
| Group | Columns | Source document |
|---|---|---|
| Identity | Tag number, service description, instrument type and function | The P&ID |
| Location | P&ID number, area or unit, line or equipment number, elevation | P&ID and the plot plan |
| Process data | Fluid, operating and design pressure and temperature, and the calibrated range | Process datasheets |
| Signal | Signal type, transmission method, power source and loop number | Loop diagrams and control system design |
| Control system | Controller, cabinet, rack, card and channel | The I/O list |
| Area classification | Zone, gas group, temperature class, protection concept and certificate number | The hazardous area schedule and the vendor certificate |
| Procurement | Manufacturer, model, requisition, purchase order and serial number | Procurement records |
| Installation | Hook-up detail number, junction box, cable number, mounting and tracing | Installation details, the junction box schedule and the cable schedule |
| Documentation | Datasheet number, loop diagram number, and the certificate references | The document register |
| Lifecycle | Calibration range and record, criticality, maintenance strategy and spares | The maintenance management system |
| Control of the record | Revision, issue status and the management of change reference | Document control |
Instrument index against the neighbouring registers
All four are built from the same P&ID set and all four are commonly confused. The difference is what one row represents.
| Register | One row is | Primary reader | Created at |
|---|---|---|---|
| Instrument index | One tagged instrument | Instrumentation engineering, then maintenance for the life of the plant | Early detailed design, from the P&IDs |
| I/O list | One signal landing on a control system channel | Control system engineering and the panel builder | Once the control system architecture is fixed |
| Line list | One numbered pipe run | Piping engineering and stress | Early detailed design, from the P&IDs |
| Loop folder index | One control or safety loop, with all its documents | Commissioning and loop checking | Late detailed design, before commissioning |
Common questions
Is the instrument index the same as the master tag list.
How does the instrument index get created from P&IDs.
Who maintains the instrument index once the plant is operational.
Does the instrument index replace the instrument datasheet.
How does instrument index scope relate to SIS scope.
Get the instrument index template.
One row per instrument tag with the columns process and maintenance reference across the asset lifetime. Plain .xlsx.