MAG 5000 MAG 5100 W Flowmeter TAG Identification per ISA-5.1

Overview: SITRANS FM MAG 5000 Transmitter with MAG 5100 W Sensor

The electromagnetic flowmeter system used in the project under discussion pairs a Siemens SITRANS FM MAG 5000 transmitter with a MAG 5100 W flow sensor on ductile iron piping at DN 500 mm and DN 600 mm nominal diameters. Because the two physical devices (sensor and transmitter) live on the same measurement loop but serve different functional roles in the control narrative, the loop must be documented so that any operator, instrument technician, or DCS engineer can recover the following information from a single alphanumeric identifier:

• The measured variable (flow rate).
• The functional role of each hardware element (primary element vs. transmitter vs. indicator).
• The sensor model and the transmitter model.
• The pipe nominal size and the material that drove the sensor selection.
• The plant area and the loop sequence number.

This identifier is the instrument TAG. The customer's requirement that "the description of the system should relate the tag of the flowmeter with the model of the sensor and transmitter, which naturally depends on the pipe size" is therefore a requirement about the TAG construction scheme, not about the physical wiring. The relation between tag and physical device is implemented through documentation; the relation between transmitter and sensor calibration parameters is implemented automatically by SENSORPROM memory inside the sensor.

System Architecture and SENSORPROM Auto-Configuration

The MAG 5100 W sensor carries a SENSORPROM memory module that, per the SITRANS FM MAG 5100 W Operating Instructions (A5E03063678en), "automatically configures the transmitter at start up providing calibration data, pipe size, sensor type, and output settings." This means that once the transmitter is powered and SENSORPROM is read, the MAG 5000 knows the exact pipe bore of the sensor in front of it without manual entry of the DN value.

This has two consequences for the TAG design exercise:

1. The TAG is the only externally visible link between the control system, the P&ID, and the physical sensor. SENSORPROM binds the transmitter to that specific sensor; the TAG must bind the loop to that transmitter.
2. If the sensor is replaced on a DN 500 line with a sensor from a different loop, the transmitter must be re-paired or SENSORPROM data must be re-entered, so the TAG must always identify a specific sensor body, not "a DN 500 sensor".

ISA-5.1-1984 (R1992) Instrument Identification Standard

The conventional framework used in the discussion is the ANSI/ISA-5.1-1984 (R1992) Instrumentation Symbols and Identification standard. ISA-5.1 defines a TAG as a functionally coded alphanumeric string. The body of the TAG is built from 4 to 6 letters, followed by a loop number, optionally preceded by a prefix and followed by a suffix.

Functional letter position rules

• First letter: identifies the measured or initiating variable. F = flow, P = pressure, L = level, T = temperature, Q = quantity (totalization).
• Subsequent letters (read in order): identify the readout, output, or passive function of the device.
• Letters after the first are modifying letters: I = indicate, T = transmit, R = record, C = control, E = primary element, A = alarm, H = high, L = low.

Functional Letter Codes for Flow Loops

TAG Differentiation: Sensor vs. Transmitter

The customer's question hinges on whether the sensor and the transmitter should each carry a separate TAG or whether one shared TAG should describe the "flowmeter" as a whole. Both conventions exist in the field; the chosen scheme is a project-level decision that must be written into the instrumentation specification.

For a MAG 5100 W + MAG 5000 combination, where the transmitter is mounted remote from the sensor using a factory-supplied signal cable, the separate TAG per device approach is the conventional choice. This produces three documents per loop:

1. A datasheet for FE-XXX covering sensor body, flange, liner, electrode, DN, PN, calibration.
2. A datasheet for FIT-XXX or FT-XXX covering the transmitter, output configuration, SENSORPROM pairing.
3. A loop diagram (or "loop folder") that ties both datasheets to one loop number.

Pipe Size Encoding in Loop TAGs

The customer's specification also requires that the TAG depend on the pipe size. There are two valid encodings: the recommended one uses ISA-5.1 with the pipe size appearing in the datasheet, P&ID, and loop diagram but not inside the TAG itself; the alternative embeds the size as a suffix on the loop number.

A practical hybrid that follows the loop-numbered-by-size idea and stays within ISA-5.1 conventions is to reserve distinct numeric ranges for distinct pipe diameters in the same area:

• DN 500 mm loops: loop numbers in the 5xx series (e.g. FE-501, FE-502, FIT-501).
• DN 600 mm loops: loop numbers in the 6xx series (e.g. FE-601, FE-602, FIT-601).

This satisfies the customer's requirement ("depends on the pipe size") while keeping the TAG string within the 4-6 letter + numeric format that DCS tag generators expect.

Step-by-Step TAG Construction Procedure

1. Identify the plant area prefix. Pick a 1- to 4-character code for the unit or area where the flowmeters are installed. Examples: RAW- for raw water intake, WW- for wastewater, TK- for tank farm, PMP- for pump station. Document the code in the project's instrument identification legend.
2. Establish the measured variable. Both DN 500 and DN 600 lines carry treated water; the variable is flow. First letter = F.
3. Identify the devices in the loop. Each DN 500 / DN 600 line contains one sensor (MAG 5100 W) and one transmitter (MAG 5000). Decide whether the MAG 5000 will have local indication: with graphical HMI module, FIT; with blind cover, FT.
4. Assign functional code per device. Sensor → FE (primary element). Transmitter → FIT or FT. Loop diagram elements such as indicators, totalizers, and controllers follow from the DCS tag database.
5. Allocate the loop number. Pick the numeric scheme. Reserve, for instance, 5xx for DN 500 loops and 6xx for DN 600 loops within the same area. Allocate 501 and 601 for the first DN 500 and DN 600 loops respectively.
6. Combine fields. Apply the prefix, the functional code, and the loop number with a hyphen separator: RAW-FE-501 and RAW-FIT-501 for the DN 500 line, RAW-FE-601 and RAW-FIT-601 for the DN 600 line.
7. Add a suffix only if needed. Use suffixes for redundancy (-A, -B), for service-id tracking, or for material codes required by the site. Avoid suffixes that the DCS tag database cannot parse (e.g. embedded DN codes in numeric fields).
8. Cross-reference P&ID and datasheets. Confirm that the loop number used in the P&ID, the loop folder, the instrument datasheets, and the DCS tag database all match. The customer's specification is satisfied when a single search for 601 recovers all four documents.

Plant-Wide TAG Examples for DN 500 and DN 600 Ductile Iron Service

The customer's required link between "the tag of the flowmeter" and "the model of the sensor and transmitter, depending on the pipe size" is satisfied for each row above by:

• The numeric block (5xx, 6xx) encoding nominal diameter.
• The datasheet title field naming the MAG 5100 W model and DN value explicitly.
• The P&ID equipment symbol explicitly showing MAG 5100 W with body material (DI) and DN on the symbol or its callout.

P&ID, Loop Diagram, and Asset Register Integration

An ISA-5.1 TAG only does its job when every document that mentions the loop uses the same identifier. Validation checklist before commissioning:

• P&ID balloon: shows the loop number, the functional symbol, the sensor model (MAG 5100 W), the DN, and the line number it sits on.
• Loop diagram: lists every instrument in the loop with the same loop number; e.g. FE-501, FIT-501, FI-501, FQ-501 all use 501.
• Instrument datasheet: header carries the full TAG, including prefix and suffix if any.
• DCS tag database: tag length and permitted characters must accept the chosen form. If the DCS rejects hyphens, drop them: RAWFIT501.
• Asset register / CMMS: equipment record tied to the sensor serial number for traceability; SENSORPROM pairing event logged here.

Verification and Documentation Requirements

Five-point verification after the TAG scheme is written into the project specification:

1. Uniqueness. Run a search across the entire instrument register for each new TAG. No duplicate loop numbers in the same area prefix.
2. Functional code consistency. Confirm that the same loop number uses FE for the sensor and FIT or FT for the transmitter; never FE on a transmitter or FT on a sensor body.
3. Size encoding. Cross-check every TAG against the layout drawing; a 5xx loop must sit on a DN 500 line and a 6xx loop on a DN 600 line.
4. Plant diagram conformance. The P&ID callout, the instrument index, the hook-up drawing, and the DCS faceplate must all carry identical TAGs.
5. Customer acceptance. Submit the instrument list with full TAG, DN, sensor model, and transmitter model so the reviewer can satisfy the original specification ("the description of the system should relate the tag of the flowmeter with the model of the sensor and transmitter, which depends on the size of the pipe").

Common Pitfalls and Corrections

FAQ