# Instrument Tagging and Identification Standards (ISA-5.1) > The instrument tag is the identity of every measurement and control function in a plant: PT-1001 , FV-2042 , TE-3108 — and the tagging standard is the language… - Canonical URL: https://wiki.aspotomasyon.com/article/instrument-tagging-standards - Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki) - Category: Field Devices & Instrumentation - Published: 2026-08-11 · Updated: 2026-09-13 - Reading time: 4 min · Language: English The instrument tag is the identity of every measurement and control function in a plant: `PT-1001`, `FV-2042`, `TE-3108` — and the tagging standard is the language the whole plant speaks. **ANSI/ISA-5.1** ("Instrumentation Symbols and Identification") defines the letters, the numbering, and the symbols; consistent tagging is what makes drawings readable, databases joinable, and work orders unambiguous. This article covers the standard's structure and the practical rules that keep a plant's instrument identification coherent for decades. ![A measurement chain from the process to an application. Calibration, loop checks, and process validation answer different questions; retain evidence for each applicable check.](https://wiki.aspotomasyon.com/assets/diagrams/field-devices-instrumentation-context.svg) *A measurement chain from the process to an application. Calibration, loop checks, and process validation answer different questions; retain evidence for each applicable check.* ## The Tag Structure An instrument tag per ISA-5.1 has three parts: - **Function letters** — the first letter is the measured variable (P pressure, T temperature, F flow, L level, A analysis, I current, W weight), the succeeding letters the functions (I indicator, C controller, T transmitter, R recorder, A alarm, S switch, V valve, Y relay/compute). Examples: `PT` pressure transmitter, `PIC` pressure indicating controller, `FT` flow transmitter, `FIC` flow indicating controller, `LSHH` level switch high-high. - **Loop number** — the identifier of the loop (1001, 2042…): the same loop number appears on the transmitter, the controller, and the valve (the loop is one functional entity), with the function letters distinguishing the elements: `FT-1001` , `FIC-1001` , `FV-1001` . - **Suffix letters** — optional modifiers for elements in the same loop (A, B: redundant or multi-element) and for device-specific numbering (e.g., `PT-1001-1` for the first sensing point). The letters are English-based by standard, but the logic transfers to any language — the tag is an ID, the function letters are its semantics. ## Tagging Conventions That Survive - **Unique everywhere** — one tag, one instrument: the tag appears identically on the P&ID, the loop diagram, the I/O list, the DCS database, the calibration records, and the nameplate. The rule sounds trivial; plants violate it daily (the P&ID says PT-1001, the DCS says AI-1037, the work order says "pressure switch boiler"). - **Plant-wide vs unit-specific** — the loop number convention (per-unit ranges: unit 1 uses 1000s, unit 2 uses 2000s, or a plant-wide sequence) is decided once and enforced; the choice matters less than the consistency. - **Functional, not physical** — the tag follows the function, not the location: a transmitter moved from tank A to tank B keeps its tag if it serves the same loop — or gets a new loop number if the function changed; the change record follows the tag. - **No meaning overloading** — the tag is an identifier, not a description: adding service codes into the tag (PT-1001-STEAM) creates two naming systems; the service lives in the instrument database (see the data sheet article), the tag stays standard. - **Logical next in line** — new instruments take the next free loop number; retired numbers are never reused (the historical record stays unambiguous). ## Symbols and the Drawing Set ISA-5.1 also defines the symbols: the instrument bubble (circle) with the tag inside, the line conventions (field-mounted, panel-mounted, software function — see the P&ID article), and the signal lines (pneumatic, electric, data link). The bubble's position tells the reader where the function lives: a transmitter bubble (no horizontal line) is field hardware; a line through it is a panel device; a dashed circle is a DCS/software function. The discipline: draw the P&ID exactly as built — the symbol set is the plant's shared vocabulary, and a sloppy P&ID is a sloppy plant (see the loop diagram article for the detail level below). ## Tag Management in the Digital Age The instrument database (CMMS or dedicated) is where tagging lives operationally: - The tag is the primary key: every record (calibration, work order, spare part, configuration) hangs off the tag. - Tag creation and changes are controlled: the new-tag process (who may allocate, what the minimum metadata is) prevents the tag chaos that comes with projects and modifications. - The DCS/SCADA tags map to the field tags (the I/O list is the mapping); the mapping review after every project is a standard checklist item (see the commissioning article). - Retirements are recorded: a decommissioned tag keeps its history and is marked retired — never deleted, never reused. ## Summary Instrument tagging per ISA-5.1 is the plant's identification language: function letters for the meaning, loop numbers for the identity, and consistent usage across drawings, systems, and records. Decide the conventions once, enforce uniqueness and non-reuse, keep the tag functional rather than physical, and manage the tag database as the primary key of the instrument lifecycle. When the plant's systems disagree, the tag is the judge; make it a reliable one. ## Apply this to your project - Confirm the instrument tag, range, engineering unit, process connection, and environmental suitability against approved documents. - Check the complete measurement chain, including sensor configuration, channel scaling, quality indication, and display units. - Record reference equipment, uncertainty where relevant, test points, deviations, and the final configuration. [Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance. ![Engineering review sequence: Specify → Inspect → Compare → Record. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/field-devices-instrumentation-review.svg) *Engineering review sequence: Specify → Inspect → Compare → Record. Keep the recorded evidence with the accepted configuration.* ## Primary references and further reading Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results. - [FieldComm Group — HART technology](https://www.fieldcommgroup.org/technologies/hart) - [NIST — Policy on metrological traceability](https://www.nist.gov/calibrations/traceability) --- Cite the canonical article: https://wiki.aspotomasyon.com/article/instrument-tagging-standards (Instrument Tagging and Identification Standards (ISA-5.1), ASP OTOMASYON, updated 2026-09-13).