Selecting P&ID Instrument Tags with ISA S5.1 Symbols

A P&ID tag works only when its letters, numeric fields, symbol, and connections are interpreted through one documented convention. The letters classify the measured variable and instrument functions; the numeric fields associate the device with a plant subdivision and control loop. A plausible-looking tag is not sufficient: the drawing legend, tag register, and governing standard must produce the same interpretation.

Identification mechanism

The term loop here means the instruments and functions associated with one process measurement or control objective. Identification letters describe the variable and functions, while a loop number links related devices. Graphic symbols then add information that the tag alone cannot carry, such as instrument representation, connection type, and display or control arrangement.

For example, FIC identifies a flow-indicating controller, and PT identifies a pressure transmitter. In 04FIC100 and 22PT333, however, the meanings of 04, 22, 100, and 333 depend on the project numbering convention. A leading field may identify an area, unit, system, or another plant subdivision; a trailing field may be a loop or sequence number. Read those meanings from the P&ID legend or tagging specification rather than from field width or position.

Drawing scope and governing document

1. Check 1: identify the drawing type. Expect the title block to classify the document as a P&ID, mechanical flow diagram, instrument interconnection diagram, or another defined drawing. If it is a process drawing, continue with its P&ID convention. If it is an interconnection drawing, use the symbol rules selected for that document because it carries different detail.
2. Check 2: read the standards block. Expect one named standard, edition or revision, and a project-specific legend. If the standard is absent, stop assigning new symbols until the project authority records the governing document. Mixing familiar symbols from several systems produces drawings that are readable only by their author.
3. Check 3: match the standard to the required information. Expect its scope to cover the functions shown on the drawing. Continue to the tag grammar only after this match is established.

The ISA publication channel identified for the cited document is http://www.isa.org. Confirm the project-required edition before purchasing or applying a document.

Tag grammar and loop ownership

1. Check 4: divide the tag into documented fields. Expect the tagging specification to show field order, permitted separators, field lengths, and examples. For 04FIC100, record FIC as the functional group, then resolve 04 and 100 against the legend. For 22PT333, resolve 22, PT, and 333 the same way.
2. Check 5: decode the letters in order. Expect the first identification letter to state the measured or initiating variable and the succeeding letters to state functions. Thus, FIC reads as flow, indication, and control; PT reads as pressure and transmission. If a project adds user-defined letters, expect their meanings in the legend.
3. Check 6: test loop ownership. Expect instruments serving the same measurement or control objective to carry the same documented loop-number field, with functional letters distinguishing their roles. If associated devices have unrelated loop fields, consult the tag register: either the devices belong to different loops or one identifier is wrong.
4. Check 7: test uniqueness. Expect every complete instrument identifier in the project scope to resolve to one asset or function in the tag register. A duplicate means the scope boundary, suffix convention, or register entry needs correction.

Do not force every numeric string into an assumed area-plus-loop pattern. A convention can encode plant subdivisions differently, and omitted separators can make two grammars look identical. The legend is the deciding record.

Symbol and connection semantics

1. Check 8: compare the symbol with the decoded function. Expect the graphic representation to agree with the role expressed by the tag. A mismatch means either the tag letters or the symbol was copied incorrectly.
2. Check 9: trace each connection. Expect process connections and instrument-function connections to follow the line conventions in the legend. A valid tag attached to the wrong process line still identifies the wrong measurement point.
3. Check 10: compare related drawings. Expect the P&ID, interconnection drawing, loop documentation, and tag register to use the same complete identifier. Differences in punctuation may be permitted only when the project convention explicitly treats them as formatting rather than identity.

Symbols for knobs, on/off markings, or speed adjustment on a manufactured control panel solve a different problem from P&ID instrumentation identification. Do not place product-interface icons into the P&ID symbol library merely because both use graphical symbols. Select the governing document for the artifact being designed.

Structured tagging procedure

1. Record the drawing class, governing standard, edition or revision, and project legend in the drawing-control data.
2. Define each tag field in a controlled template: plant subdivision field, functional-letter group, loop or sequence field, and any project-authorized suffix.
3. Assign the measured variable from the process duty, then assign only the functions actually represented by the instrument or control function.
4. Allocate the numeric loop field from the controlled tag register. Reuse that loop field only for functions belonging to the same documented loop.
5. Select the graphic symbol and connection lines from the same project legend used to decode the tag.
6. Add the complete identifier to the tag register and cross-reference related drawings.
7. Run duplicate, orphan, and cross-drawing checks before releasing the P&ID.

Wrong practice is creating tags directly on the drawing and updating the register afterward. Allocate identifiers through the controlled register first; otherwise parallel drawing edits can create duplicates and inconsistent loop ownership.

Verification sequence

1. Verification 1: standards reading. Expect the title block or project specification to name the governing symbol document and applicable revision.
2. Verification 2: grammar reading. Expect every character position in 04FIC100 or 22PT333 to map to a defined field in the project legend, with no unexplained digits.
3. Verification 3: function reading. Expect the tag letters, graphic symbol, and represented process duty to describe the same variable and functions.
4. Verification 4: register reading. Expect one unique record for the complete tag and matching loop ownership for every associated function.
5. Verification 5: cross-document reading. Expect the identical controlled identifier on the P&ID, tag register, and each applicable instrument or interconnection document.

Frequently asked questions