Instrument index · editable CSV · no signup
Instrument IndexTemplate & Field Guide
Control every instrument tag from P&ID intent through data sheet, I/O assignment, procurement, installation, calibration and handover.
What this document controls
An instrument index is the controlled register of measurement and final-control devices in a project. One row identifies the tag and service, process variable, range and units, signal/interface, P&ID and data-sheet references, area, status and connected control-system record. It prevents instruments from being designed independently in drawings, procurement lists, PLC I/O and commissioning sheets.
File facts
- Format
- CSV / spreadsheet
- Account
- Not required
- Project data upload
- None
- License
- CC BY 4.0
Field dictionary
Columns worth keeping
| Field | Why it exists | Example |
|---|---|---|
| Instrument tag | Stable identifier used across the P&ID, data sheet, I/O list, loop drawing and test record. | PT-201 |
| Service / description | Plain-language process duty so reviewers can identify the real device. | Reactor feed pressure |
| Variable / type | Separates pressure, temperature, flow, level, analysis, control valve and other functions. | Pressure transmitter |
| Range and units | Controls engineering scaling and instrument selection; preserve LRV and URV explicitly. | 0–10 bar(g) |
| Signal / protocol | Defines the electrical or network interface and drives I/O/hardware design. | 4–20 mA + HART |
| P&ID / drawing | Traces the row to approved process intent and location. | PID-2101, rev C |
| Data-sheet reference | Points to the controlled specification rather than copying every property into the index. | DS-PT-201, rev B |
| I/O / system owner | Connects the physical instrument to the PLC, DCS, SIS or package control-system record. | AI-03-07 / PLC-201 |
| Area / equipment | Supports installation packages, maintenance filters and physical ownership. | Area 200 / R-201 |
| Hazard / safety class | Flags where hazardous-area, SIL or other controlled requirements apply without replacing their records. | Ex ia / SIL loop ref SIF-04 |
| Vendor / model | Records the selected item after technical bid evaluation and preserves installed identity. | Project-selected model |
| Lifecycle status | Uses one vocabulary from proposed through ordered, installed, calibrated and handed over. | Installed — loop check open |
Workflow
Build it in the right order
- 01
Seed from approved process documents
Extract instrument bubbles and final elements from the current P&IDs and package drawings. Record the drawing revision used.
- 02
Normalize tags and services
Apply the project tagging convention, remove accidental duplicates and make service descriptions understandable without opening the drawing.
- 03
Attach engineering properties
Add ranges, units, materials, process connection, signal, hazardous-area and functional-safety references from controlled data sheets.
- 04
Reconcile with controls and procurement
Match each signal-bearing instrument to the I/O list and each purchased item to requisition/vendor records. Resolve interface gaps early.
- 05
Carry the row through commissioning
Update installed identity, calibration and loop-check status without deleting the original design trace or unresolved deviation.
Quality gate
Review before issue
- Every P&ID instrument tag appears once in the index unless the project convention documents a deliberate exception.
- The same physical device is not duplicated under package, PLC and process naming variants.
- Range, units and signal agree with the data sheet, I/O configuration and HMI display.
- Drawing and data-sheet references include controlled revision identifiers.
- Network-only instruments still have a control-system owner and validity/diagnostic contract.
- Hazardous-area and safety-related attributes point to approved specialist records.
- Deleted or replaced instruments are retired with a reason instead of silently removed.
- As-built vendor/model/serial details are captured where the handover specification requires them.
Worked record
Worked record: PT-201 reactor-feed pressure
This row is intentionally a cross-document index, not a substitute for the transmitter data sheet. It tells a reviewer where the process intent, device specification, I/O mapping and commissioning evidence live.
| Tag | Service | Range | Signal | P&ID | I/O / test | Status |
|---|---|---|---|---|---|---|
| PT-201 | Reactor feed pressure | 0–10 bar(g) | 4–20 mA + HART | PID-2101 rev C | AI-03-07 / LC-PT-201 | Installed; loop check open |
| PSHH-201 | Feed pressure high-high trip | 8.5 bar set point | 24 VDC discrete | PID-2101 rev C | DI-02-11 / SIF-04 | Validation by SIS team |
Connect it to the rest of the project
P&ID guide
Understand how instrument tags and process intent originate on the diagram.
Open reference →PLC I/O list builder
Map physical signals into cabinets, modules, channels, tags and commissioning.
Open reference →Loop-check procedure
Carry each installed signal through field-to-control-room verification.
Open reference →Frequently asked questions
Is an instrument index the same as an I/O list?
No. The instrument index controls devices and their engineering/document status. The I/O list controls signals and their control-system channels. One instrument can have several I/O signals, and some instruments communicate over a network without one row per physical I/O channel.
Should valves and analyzers be included?
Usually yes when they are within the project instrumentation boundary. Final control elements, analyzers, switches, transmitters and package instruments may all need register ownership, but the exact scope belongs in the project document plan.
Who owns the instrument index?
Ownership varies by organization, often instrumentation or controls engineering. The important control is one accountable owner with formal input from process, electrical, mechanical, packages, procurement and commissioning.
Can this CSV be opened in Excel?
Yes. Download it and open or import it in Excel, Google Sheets, LibreOffice or a document-control system that accepts CSV. Preserve controlled revision and approvals outside the raw CSV when required.
Share or cite this template
Link to this landing page so readers receive the field definitions, use boundary and future revisions with the file.
https://plcprogramming.io/tools/instrument-index-template