Skip to content

News

A point-to-point loop check, from the device to the screen

  • News
  • 1 min read

The BMS graphic shows 21.5 °C. Nothing on the screen says whether that is this room's sensor or the one next door on the wrong channel.

A swapped pair is one of the most ordinary wiring faults on a new system, and it passes the checks made from the desk. Both rooms read plausibly, both trend, both alarm. It shows when someone stands at the device and disturbs it.

The point-to-point check takes each loop from the field to the screen:

  1. Find the device by its tag in the field. Compare tag, model and range with the instrument list.
  2. Follow the wiring to the terminal and the I/O channel on the loop drawing.
  3. Apply a known input at the device, low and high. A simulator at the panel terminals proves the channel and skips the field cable, which is where the swap lives.
  4. At the workstation, confirm the value, the unit and the tag on the graphic, then on the trend and in the alarm list. Scaling faults show here: a 4–20 mA transmitter ranged 0–50 °C and scaled 0–100 °C in the controller reads double.
  5. Sign the loop sheet for that tag, with the test instrument and the readings.

Outputs run the other way: command from the screen, watch the actuator, read the feedback.

IEC 62382 sets out loop checks for process plants, and a BMS or EMS deserves the same habit of one signed sheet per tag. Calibration is a separate job. The loop check proves the signal path, and its sheets are what the IQ of the monitoring system draws on.

Topics

Related

More on this subject

A vendor IQ/OQ protocol and the URS lines it leaves out

A supplier's standard IQ/OQ protocol was written for the standard machine, before your URS existed. EU GMP Annex 15 (2015) says site personnel should confirm its suitability before approval, and that vendor protocols may be supplemented. Trace each URS line to a test, then write a short supplementary protocol for the lines left uncovered.

InsightRead