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.
Read one of your own drawings.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
The instrument index sits between the P&ID set and the instrument datasheet library. It collects every tagged item into a single structured table. Not only the wired instruments in the I/O list, but also mechanical gauges, pressure-relief valves, rupture discs, thermowells, and any 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.
Frequently asked.
Is the instrument index the same as the master tag list.
Often yes. Some companies separate them. The master tag list is the unique-tag register enforcing uniqueness. The instrument index is the metadata-rich extended view with manufacturer data, calibration records, and datasheet references. Functionally most teams maintain one document and call it whichever name their template uses.
How does the instrument index get created from P&IDs.
Either by manual transcription or by processing the P&ID set into a structured register. Either way, signal class is normalized to the project's identification standard, tag uniqueness is enforced, and the result is reconciled against legacy datasheets where they exist. Processing a large drawing set is faster than hand-transcription. The bottleneck shifts to reconciliation with procurement and calibration records rather than the initial tag capture.
Who maintains the instrument index once the plant is operational.
The operating company's instrument engineering or reliability team owns the live index. Every change that touches a tag on a P&ID revision triggers an instrument-index update through the management-of-change process. Commissioning hands over the as-built index. The operations team extends it with calibration intervals, spare parts lists, and inspection records.
Does the instrument index replace the instrument datasheet.
No. The instrument index is a register that points to datasheets. It does not replace them. Each instrument index row has a datasheet reference column. The datasheet, ISA 20 format or equivalent carries the full specification. Process conditions, materials of construction, connection ratings, and vendor selection criteria. The index tells you what exists. The datasheet tells you what each item is.
How does instrument index scope relate to SIS scope.
SIS-classified instruments appear in the instrument index alongside BPCS instruments, but most projects mark them with a SIL allocation column or a system flag. Some projects maintain a separate SIS instrument index so the safety system vendor and their proof-test team work from a clean filtered list. Whether combined or split, all SIS tags must appear in the master instrument index so the facility has a complete picture of what exists in the plant.