P&ID instrument tags: FT, FIC, and FV in one flow-control loop

In this worked P&ID, FT-101 measures flow, FIC-101 indicates that measurement and performs the control function, and FV-101 is the final control valve that changes the flow. The shared loop number 101 groups those functions into one flow-control loop; it does not mean they are one device. The FC beside the valve means the example assumes a fail-closed final element on loss of actuating energy—not that the whole process has been proven safe.

Scope and terminology first

A piping and instrumentation diagram, or P&ID, records relationships among process equipment, piping, valves, instruments, and control functions. It is not the same deliverable as a process flow diagram, an instrument loop sheet, an electrical wiring drawing, or a cause-and-effect matrix. Each may contain detail that the others intentionally omit.

ANSI/ISA-5.1-2024 establishes a uniform identification system for instrumentation and control functions. ISA describes the purpose as letting a reader with reasonable plant knowledge understand the means of measurement and control without requiring every instrument detail on the flow diagram. The 2024 edition is the current edition as checked on August 22, 2026; it supersedes the 2009 and 2022 editions often named by older drawings and software documentation.

This example uses a fictional, nonhazardous water-transfer service. It assumes:

• one continuous process path from feed tank T-101 to receiving tank T-102;
• centrifugal pump P-101 provides the driving head;
• the controlled variable is flow at the pump-discharge measurement point;
• the manipulated variable is the position of control valve FV-101;
• FT-101 sends an electrical measurement signal to FIC-101;
• FIC-101 sends a pneumatic command to the valve actuator; and
• the valve is annotated fail closed for loss of actuating energy.

The drawing does not specify flow range, setpoint, controller tuning, valve size, air-supply pressure, process pressure, pipe class, alarm limits, interlocks, bypasses, isolation valves, power sources, or an independent protection layer. Those are deliberately outside this notation exercise.

Decode the three tags without guessing

The durable reading method is variable first, function second, loop number last. Under the common ISA identification convention used here, F identifies flow as the measured or initiating variable. Subsequent letters identify functions. Project legends can define optional or user-assigned meanings, so the approved project standard remains controlling.

Do not decode FIC as three separate pieces of hardware. It names one instrument or control function with multiple duties: flow is its associated variable, indication is visible to an operator, and control is performed. Likewise, FV-101 is a functional tag; the physical valve assembly may include a body, actuator, positioner, solenoid, limit switches, and accessories described elsewhere.

Trace the worked loop in process order

The U.S. Department of Energy's Instrumentation and Control handbook, Volume 2 separates the basic automatic-control loop into measurement, comparison/control, and final control action. Apply that functional sequence to the P&ID:

1. Water leaves T-101 and enters P-101 on the solid process path.
2. The pump discharge is the stated flow-measurement point. A thin process connection makes that sensing relation visible, and FT-101 converts the sensed flow into the loop's measurement signal. This simplified tap is not an installation detail for an impulse-line or primary-element arrangement.
3. The explicit dashed electrical path carries the FT-101 measurement to FIC-101.
4. FIC-101 represents the indicating controller. The controller compares measured flow with a setpoint and determines the required output. The setpoint source and algorithm are not drawn.
5. The controller output reaches the pneumatic actuator on FV-101. Moving the valve changes flow resistance and therefore manipulates the controlled flow.
6. Changed process flow is measured again, closing the feedback loop functionally even though the P&ID is not a dynamic block diagram.

That final distinction prevents a common category error. The process line shows where fluid can move; signal lines show how information or actuator energy moves. A signal line crossing a process pipe does not create a fluid connection. Conversely, a solid pipe between the pump and valve does not tell the reader whether the control command is electrical, pneumatic, hydraulic, or software-based.

Reproducible Schematex source

pid "Flow-control loop FT-101 / FIC-101 / FV-101" [direction: LR]

equip T-101 : tank_atm [tag: "T-101"]
equip P-101 : pump_centrifugal [tag: "P-101"]
equip FV-101 : valve_control [tag: "FV-101 · FC", actuator: "pneumatic", fail: "closed"]
equip T-102 : tank_atm [tag: "T-102"]

line L1 from T-101.bottom to P-101.in [type: "process"]
line L2 from P-101.out to FV-101.in [type: "process"]
line L3 from FV-101.out to T-102.top [type: "process"]

inst FT-101 : field_discrete
inst FIC-101 : cr_shared
  controls FV-101

line M1 from P-101.out to FT-101 [type: "process_minor"]
line S1 from FT-101 to FIC-101 [type: "electric"]

Schematex 1.0.13 strictly parsed and rendered this source with no diagnostics on August 22, 2026. The parsed model contained four equipment items, two instrument functions, three main process lines, one minor sensing connection, and one explicit electrical signal line; the controller's controls relation produced the pneumatic connection to the valve. The explicit M1 path makes the assumed pump-discharge measurement relation visible rather than asking the reader to infer it.

The source uses Schematex's field_discrete category for the plain FT-101 field bubble and cr_shared for the shared-display/control form used for FIC-101. Those are renderer categories, not a claim that every project uses the same control-room location convention. The current Schematex P&ID syntax reference lists the supported equipment, instrument categories, line styles, and present layout limits.

What FC means—and what it does not

The valve label includes FC as a fail-position annotation. Emerson's Control Valve Handbook, sixth edition defines fail-closed as the valve closure member moving closed when the actuating energy source fails. That definition is narrower than several claims reviewers sometimes attach to the letters:

• FC does not mean “the valve closes whenever the transmitter signal is low.” Controller action and signal-failure strategy are separate design decisions.
• FC does not mean “the valve is guaranteed to reach tight shutoff.” Available spring force, process differential pressure, friction, mechanical condition, and shutoff requirements still matter.
• FC does not mean “closed is safe for every failure.” The process hazard analysis must justify the desired state and consider upstream pressure, downstream demand, loss of cooling, trapped liquid, and other consequences.
• FC does not describe a double-acting actuator with stored energy, lock-up, or fail-in-place behavior unless the design documents say so.

For this fictional transfer, fail closed is only an assumption that stopping inflow is the desired response to lost actuator energy. It is not a design recommendation for another service.

Invariants for a P&ID tag review

Run these checks before accepting the diagram:

1. Every tag is unique. No second FT-101, FIC-101, or FV-101 exists elsewhere in the drawing set unless the project convention explicitly permits a suffix or duplicate representation.
2. The variable stays consistent. All three functional tags begin with F; a stray LIC-101 would introduce level as the controlled variable and needs explanation.
3. The loop number stays consistent. The measurement, controller, and final element use 101; FV-102 would point to another loop unless documented as cascade, override, or split-range logic.
4. The signal chain is complete. A reviewer can trace measurement point → transmitter → controller → final element without inventing a missing connection.
5. Line styles have declared meanings. Process, electrical, and pneumatic paths are visually distinguishable and agree with the project legend.
6. The valve is on the manipulated process path. A controller connected to a valve on an unrelated branch would be topologically wrong even if every tag were spelled correctly.
7. Fail position is explicit and justified elsewhere. The annotation agrees with actuator data, control narrative, cause-and-effect documentation, and the hazard review.
8. Drawing scope is stated. Omitted setpoints, alarms, interlocks, bypasses, and utilities are either outside scope or shown in the appropriate companion documents.

A useful negative test is to change only FV-101 to FV-102. The SVG will still render because the syntax remains valid, but the engineering association is now ambiguous: the controller and valve no longer share a loop number. Syntax validation catches malformed notation; it cannot decide whether the loop assignment matches the process design.

Failure modes and review boundary

Common failures include treating the loop number as an equipment number, using FC as if it were a controller function letter, showing a signal without its type, placing the transmitter on the wrong process location, omitting the final element, combining basic process control and an independent shutdown function into one bubble, and assuming a clean P&ID proves the wiring or safety logic.

For U.S. processes covered by OSHA Process Safety Management, 29 CFR 1910.119 lists P&IDs among required process-equipment information and separately requires documentation of the design codes and standards employed. That rule is not a claim that every P&ID everywhere has the same legal status, nor does using this figure establish compliance.

Paste the source into the Schematex playground, then replace the fictional equipment and loop number with one real loop at a time. Before issuing the drawing, reconcile the result against the project's instrument index, I/O list, control narrative, valve datasheet, loop sheet, cause-and-effect matrix, and approved P&ID legend; a mismatch among those records is more important than a visually perfect bubble.