Reading Owner-Operator Instrument Tags Built on ISA 5.1.

Most owner-operators do not invent a tag system from scratch. They take the ISA 5.1 letter grammar as the base and layer a set of company-specific rules on top, a relettered relief valve here, a substituted letter there. So an owner-operator P&ID reads almost like plain ISA, until a tag like PZV appears where you expected PSV and you slow down. That is the right instinct. The safe way to read any such set is to decode the ISA part with confidence and check the company exceptions deliberately.

This is a contractor-facing reference for that situation, worked through a public example. Saudi Aramco's SAES-J-004 is one of the few owner-operator instrument standards documented well enough in public sources to teach from, so it carries the worked example here, and the method transfers to any operator's standard. The note covers how the functional identifier reads, the publicly reported deviations, and how to build a clean instrument index without guessing at anything the drawing does not state.

The standard behind the tags

Aramco instrument tagging is governed by the engineering standard SAES-J-004, "Instrumentation Symbols and Identification." It establishes a uniform way to designate instruments and instrumentation systems across Aramco projects, and it is built on ANSI/ISA-5.1-1984, reaffirmed 1992. SAES-J-004 does not replace ISA 5.1. It takes that base and adds, excepts, modifies, or deletes specific items.

The practical consequence for a reader is good news. The readable backbone of an Aramco tag is the public ISA 5.1 grammar. If you can read an ISA-conformant drawing, you can read most of an Aramco one. What you have to learn separately is the smaller set of company-specific exceptions, and SAES-J-004 itself is a controlled document, so the authority for the specific set in front of you is its own legend sheet.

The functional identifier

The ISA 5.1 grammar that the Aramco tag is built on structures the functional identifier as a first letter for the measured or initiating variable, one or more succeeding letters for the readout and output functions, and then a loop number. These are the public ISA letters behind it.

So FT is a flow transmitter, TIC is a temperature indicating controller, and PSV would be a pressure safety valve on a plain-ISA sheet. This grammar is public and is the part of an Aramco tag you read the same way as any ISA drawing.

The deviations that trip up first-time readers

The exceptions are where an Aramco set departs from plain ISA. The following are publicly reported deviations. Treat them as a guide and confirm each against the drawing legend, because the controlled standard is the only complete authority.

• Relief and safety devices are relettered. It is publicly reported that SAES-J-004 uses PZV in place of PSV and PZE in place of PSE. A relief or safety valve that plain ISA labels PSV appears as PZV.
• Letter substitutions in the identification table. Public summaries describe company-specific letter substitutions in the identification table. Confirm the specific ones against the legend rather than carrying them over from another project.
• Valve position limit switches. Limit switches proving valve open and closed positions appear as position-tagged forms such as XSH and XSL, or the equivalent the project legend defines.

These are the commonly summarized ones. They are not a complete list, and the exact, paragraph-level tables live in the controlled standard. The discipline is to read the public ISA grammar, then check the legend for the company exceptions, and flag anything the legend does not resolve.

The tag is also the mark number

One feature of SAES-J-004 is worth knowing before you build an index. The instrument identification on the P&ID is also used as the mark number on equipment, on material requisitions, on specification sheets, and on installation schedules. The tag is not just a drawing label. It is the identifier that flows through procurement and construction documents.

That is why the structure of the tag matters. The numeric tail is read structurally, not numerically. Leading zeros and any area or unit segment carry meaning and must not be stripped. Parsing the numeric tail as an integer drops the leading zeros and silently corrupts the identifier that the spec sheet and installation schedule depend on.

Which ISA edition is your set drawn to

SAES-J-004 is based on the 1984, R1992 edition of ISA 5.1. ISA 5.1 has since been revised, with 2022 and 2024 editions, and the 2024 edition retitled the standard to "Instrumentation and Control Symbols and Identification." A given Aramco set is drawn to whichever edition its project specified, so do not assume the edition. Read it from the legend and title block. The grammar is stable enough that the common letters read the same across editions. The edition is what settles any ambiguous symbol.

Building a clean instrument index from an owner-operator set

The structure-preserving approach to an Aramco-tagged set is the same discipline that pays off on any owner-operator convention.

• Keep the tag exactly as drawn, structure and leading zeros intact.
• Decode the functional letters into columns for measured variable, function, loop or area, and the plain-ISA equivalent where there is one.
• Record the deviations as read. A PZV is captured as a relief or safety valve, with the deviation noted rather than silently normalized to PSV.
• Carry the tag through as the mark number it also serves as, so the index, the spec sheet, and the installation schedule agree.

Read this way, the set yields a structured instrument index in which every tag is decoded into its functional columns and carried through intact, with deviations flagged rather than guessed. Structuring that index is covered in the instrument index reference note.

A worked example

Take an invented tag PZV-10-0421 on an Aramco-style sheet. The functional identifier decodes from the public ISA 5.1 grammar. P is pressure, the first-letter measured variable. Z is the Aramco-substituted relief and safety designator. V is valve. So this is a pressure relief or safety valve, where a plain-ISA drawing would have printed PSV-0421. The numeric tail 10-0421 is the loop or area-sequence identifier, read structurally and not numerically, because the leading zeros and the area segment carry meaning.

A companion invented instrument FT-10-0421 on the same loop area decodes as F flow and T transmit, a flow transmitter. A temperature switch with a high trip would read TSH-10-0431, where T is temperature, S is switch, and H is high. For a valve limit switch you would see the position-tagged form such as ZSH and ZSL, or the XSH and XSL variant per the project legend, indicating valve-open and valve-closed proof. The lesson is to decode the letters with the public ISA table, then check the project legend sheet for the specific Aramco substitutions before populating the instrument index.

What to flag rather than guess

The firm rule on a controlled-standard set is simple. When the drawing does not state it, flag it, do not invent it.

• A symbol the legend does not define goes to the document owner, not into the index as a guess.
• An equipment prefix you cannot resolve from the legend is flagged, not assumed, because the company equipment tables are controlled.
• A deviation that does not match the publicly reported ones is confirmed against the legend before it is recorded.
• The ISA edition, if the title block is ambiguous, is confirmed rather than assumed.

Further reading

• ANSI/ISA-5.1, Instrumentation, or Instrumentation and Control, Symbols and Identification, the public base standard
• ISA 5.1 edition history, the 1984, R1992, 2022, and 2024 editions
• The drawing's own legend and title block, which are the authority for the specific set