Loop checks and functional tests are both part of commissioning a control system, and because they overlap in time and both involve exercising the system, they are easy to blur together. They answer two genuinely different questions, though: a loop check asks whether the signal gets from the field to the screen correctly, while a functional test asks whether the system does the right thing with that signal. This guide draws the line between them, explains cold versus hot loop checks, and shows how the two fit together in the commissioning sequence.
Loop Check vs. Functional Test in one line: A loop check verifies the physical signal path from a field device to the operator display - confirming the right value arrives on the right tag with the right scaling. A functional test verifies that the control logic, interlocks, and sequences respond correctly to those signals. In short, a loop check proves the plumbing carries the signal; a functional test proves the system does the right thing with it, and loop checks are normally completed before functional testing.
A loop check follows a single signal along its whole path and confirms that path is intact and correct. Starting at a field instrument, a technician applies or reads a known value and confirms it appears on the operator display as the right value, on the right tag, in the right engineering units, with the right scaling. If a transmitter is at fifty percent of range, the display should read the corresponding engineering value; if a pump is commanded on, the field output should energize. A loop check is fundamentally about integrity of the signal path - is the wire landed correctly, is the point configured correctly, does the value survive the journey - and it does not, on its own, care whether the system then makes a good decision with that value.
A functional test picks up where the loop check leaves off and exercises the logic. It sets up conditions and confirms that the control system responds the way the specification says it should: that an interlock trips a pump when a level gets too high, that a permissive prevents a start until conditions are met, that a sequence steps through its stages in order, that an alarm annunciates at the right priority. Where a loop check proves a single value arrives correctly, a functional test proves the relationships between values and actions - the behavior the plant actually depends on for safe, correct operation.
The distinction matters because the two failures are different and need different fixes. A loop check failure usually points to wiring, termination, or point configuration - a crossed wire, a wrong scaling, a mismapped tag. A functional test failure usually points to the logic - a mistake in the interlock, a wrong setpoint in the program, a sequence step out of order. Testing them separately means that when something fails, you already know roughly where to look, instead of chasing a logic problem that is really a wiring fault or vice versa.
Loop checks come in two flavors depending on how the signal is generated. A cold loop check is done without the real process, by injecting a simulated or artificial signal at the field end - a calibrator applying a current, a technician stroking a valve by hand, a signal forced at the transmitter - and confirming it reaches the display correctly. Cold checks are done early, while the plant is not running product, because they are safe and let the whole signal path be verified before any process fluid is involved. They are the workhorse of I/O verification.
A hot loop check uses the real process signal instead of an injected one. Once the plant is running or being brought up, the actual measured value - a real level, a real pressure, a real flow - is confirmed to read correctly on the display. Hot checks catch things a cold check cannot, such as a value that reads plausibly in isolation but is wrong under real conditions, and they confirm that the loop behaves correctly with genuine process dynamics rather than a clean injected signal. Because they involve the live process, they come later, once the cold checks are clean and it is safe to introduce real conditions.
In sequence, cold loop checks typically come first, during energized commissioning while the process is still offline, followed by functional testing of the logic, and then hot loop checks and live functional confirmation once the process is introduced. A point-to-point checkout of the wiring precedes even the cold loop check, because there is no sense confirming a value reaches the screen until you have confirmed each wire lands where the drawing says it should.
The two tests build on each other in a deliberate order. Point-to-point checkout confirms the wiring is physically correct; cold loop checks then confirm each signal reaches the operator display accurately; functional tests then confirm the logic does the right thing with those trusted signals; and hot loop checks and live functional confirmation finally prove everything holds up with the real process. Each layer assumes the one beneath it is sound, which is why the order matters - a functional test run before the loops are checked can waste hours chasing a wiring fault that masquerades as a logic problem.
Keeping the tests distinct also keeps the paperwork clean. Loop checks are usually recorded per loop, with a signed record that each signal was verified, while functional tests are recorded per function or per specification requirement, with expected results and pass or fail marks. That separation makes it obvious, at handover, both that every signal path was verified and that every specified behavior was demonstrated - two different kinds of evidence that a reviewer or auditor can check independently.
For an operation supervised by a cloud SCADA platform such as Merobix, the two tests still exist for the reasons above, but where the display lives changes how they are witnessed. Because the operator display is a browser view of a hosted supervisory system, the person confirming that a loop check value arrives correctly, or that a functional test behaves as specified, can be watching the same live displays from anywhere, while a technician injects signals or exercises logic at the site. The field end - the instruments, wiring, and I/O that a loop check verifies - is exactly as physical as ever and still has to be checked hands-on, but the verification of what reaches the screen can be shared between a field crew and a remote engineer, which is helpful when the loops and functions being checked are spread across many remote sites.
A loop check verifies the physical signal path - that a value gets from a field device to the operator display correctly, on the right tag and with the right scaling. A functional test verifies the control logic - that interlocks, permissives, sequences, and alarms respond correctly to those signals. A loop check proves the signal arrives; a functional test proves the system does the right thing with it.
A cold loop check injects a simulated signal at the field end - a calibrator, a hand-stroked valve, or a forced value - and confirms it reaches the display correctly while the process is still offline, which is safe and done early. A hot loop check uses the real process signal once the plant is running, confirming the loop reads correctly under genuine conditions. Cold checks verify the path safely first; hot checks confirm it with live process dynamics.
Loop checks come first. Cold loop checks confirm each signal reaches the operator display accurately before functional tests exercise the logic, because a functional test run before the loops are verified can waste time chasing a wiring fault that looks like a logic error. The usual order is point-to-point checkout, then cold loop checks, then functional testing, then hot loop checks and live confirmation once the process is introduced.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.