ISA 5.1 vs IEC 81346. Two Tag Identification Standards That Refuse to Agree.

ISA 5.1 and IEC 81346 are both used to label objects on engineering drawings, and that is roughly where the overlap ends. Treating them as interchangeable is the source of most cross-border project pain.

The starting point. Different questions, different answers

ISA 5.1 was written to answer one question. Given a bubble on a P&ID, what is inside it and what is it doing. The letter codes encode measured variable, modifier, and function. A reader fluent in the standard can decode FIT-101 in about a second.

IEC 81346 was written to answer a much broader question. Given any object in an industrial system, where does it sit in the hierarchical breakdown of that system. It is not specific to instrumentation. The same standard tags pumps, switchgear cubicles, structural supports, and rooms.

That difference in scope is why direct translation between the two is rarely clean.

ISA 5.1 in one paragraph

The tag is a string of letters followed by a loop number. The first letter is the measured variable. The middle letters modify or describe the function. Final letters describe what the device does. So PSHH-201 reads as Pressure, Switch, High-High, on loop 201. The standard publishes around twenty first letters, eight or so modifiers, and a dozen function letters. Once you internalize the table, every new tag you read decodes itself.

What ISA 5.1 does not tell you is where the loop sits in the plant. Loop 201 could be in the boiler house or on the dock. The drawing context provides that.

IEC 81346 in one paragraph

The tag is a structured reference designation organized by aspect. Three aspects matter most.

• The functional aspect, prefixed =, names what the object does in the functional system breakdown.
• The product aspect, prefixed -, names which physical product realizes that function.
• The location aspect, prefixed +, names where in space the object sits.

A full designation like =K01+A12-B3 reads as functional position K01, located at A12, implemented by product B3. Each aspect is independently extensible. The functional code may itself be hierarchical, so you can drill from plant to system to subsystem to device.

The codes themselves come from IEC 81346-2, objects and IEC 81346-1, rules, with industry supplements like IEC 81346-10 for power plants and 81346-12 for buildings.

A direct comparison

A flow transmitter on a feedwater line in a combined-cycle power plant might appear as.

• ISA 5.1. FT-3201, Flow Transmitter on loop 3201
• IEC 81346. =H10+UCB01-CF001, functional position in heat-cycle subsystem H10, located in cabinet UCB01, product reference CF001

Both labels point to the same physical device. They tell you almost completely different things.

Where the two standards quietly overlap

There is one zone of agreement. Both standards expect tag uniqueness within the system being described. Both expect the tag to live near the symbol on the drawing. Both expect a cross-reference list, instrument index for ISA, equipment list for IEC that ties tags back to specifications. The administrative scaffolding is similar even when the syntax is not.

Both also accept that an object can carry more than one designation. ISA 5.1 allows redundancy suffixes like FT-101A and FT-101B. IEC 81346 builds redundancy into the aspect notation itself.

Where they diverge in practice

Granularity. ISA 5.1 stops at the instrument. IEC 81346 keeps going up the tree. A control panel, a junction box row, the room they sit in, and the building those rooms belong to all get designations.

Reuse across drawing types. An IEC 81346 reference designation on a P&ID is the same designation that appears on the single-line diagram, the loop sheet, and the layout drawing. ISA 5.1 stops being useful once you leave the P&ID family.

Discipline coverage. ISA 5.1 is an instrumentation standard. IEC 81346 is intentionally cross-discipline.

Reading ergonomics. A trained ISA 5.1 reader sees LSHH-401 and knows what it does without looking anything up. IEC 81346 reads more like a filesystem path. You usually need the project's coding manual to decode it.

Realistic project scenarios

Scenario A. North American refinery revamp. ISA 5.1 throughout. No IEC 81346 in sight. Skip the rest of this section.

Scenario B. European EPC building a polymer plant in the Middle East. Engineering done in Germany using IEC 81346. Construction handed to a local contractor who wires loops the way they always have. Result. Every drawing carries IEC 81346 designations on the equipment, ISA 5.1 tags in the instrument bubbles, and a cross-reference table that matches one to the other.

Scenario C. Norwegian offshore platform. NORSOK Z-DP-002 imposes a tag system that is structurally close to IEC 81346 but with offshore-specific function codes. Local engineers treat it as the master. ISA 5.1 letters appear inside the function code position rather than as a parallel system.

Scenario D. Greenfield combined-cycle plant in Asia. Licensor is European. Engineering contractor is Korean. Operator is Chinese. Three coding manuals, one drawing set. The cross-reference table is not optional, it is the only document that keeps the project legible.

Common errors when bridging the two

A few patterns repeat across projects.

• Treating the IEC 81346 product code as a tag. The product aspect names the device family, not the unique instance. Two transmitters with the same product code are not the same instrument.
• Dropping the aspect prefix. Stripping the = or + to save column width breaks any tooling that parses the designation. Tools either keep the prefixes or store the aspects in separate columns.
• Reusing ISA loop numbers as IEC functional positions. They look similar. They are not. The loop number is local. The functional position is global within the plant breakdown.
• Assuming a one-to-one mapping exists. Some IEC 81346 designations cover assemblies that contain several ISA-tagged instruments. The mapping is one to many.

Most cross-border project rework comes from one of two places. The drawings were tagged in one convention and the operator's CMMS expects another. Or the I/O list was built in ISA 5.1 and the as-built equipment list shipped in IEC 81346. Both problems are cheap to prevent and expensive to fix. The cheap fix is deciding the convention before the first drawing is issued, then enforcing the cross-reference table for every revision. The instrument index master class guide covers how to structure that cross-reference column inside a multi-standard instrument index so the mapping stays maintainable across revisions.

If you are inheriting a project mid-stream, the first thing to do is read the project coding manual. If there is no coding manual, the second thing to do is write one. The third thing is to make sure your extraction tooling does not silently collapse two different identification systems into one column.

Further reading

• ISA 5.1-2009 Instrumentation Symbols and Identification
• IEC 81346-1 Industrial systems, installations, and equipment. Structuring principles
• IEC 81346-2 Classification of objects and codes for classes
• IEC 81346-10 Power plants
• ISO, TR 16952 Reference designation system, technical product documentation