A prover loop is the permanently installed proving subsystem at a metering station - the piping, valves, detectors, and instrumentation that let a meter be proved on demand without bringing in a portable prover. Rather than a single prover barrel, it is the whole assembly around it: the four-way valve that launches and reverses the displacer, the detector switches, the temperature and pressure taps, and the connections that route flow through the meter and prover in series. This guide describes the prover loop as a station subsystem and how a flow computer sequences an automatic prove through it.
Prover Loop in one line: A prover loop is a permanently installed proving system built into a metering station, comprising the prover barrel, a four-way valve to launch and reverse the displacer, detector switches, temperature and pressure taps, and the piping that puts the meter and prover in series. Because it is fixed in place and instrumented, a flow computer can sequence a full automatic prove through it on demand, without dispatching a portable prover to the site.
A prover loop is more than the prover barrel; it is the complete assembly that makes proving a routine, repeatable station operation. At its centre is the prover itself - commonly a bidirectional pipe prover or a compact small volume prover - with its calibrated volume and detector switches. Around it, the four-way valve is the key piece of station hardware: it routes the flowing liquid so the displacer launches through the calibrated volume, and on a bidirectional loop it reverses to send the displacer back, all without an operator repositioning anything.
The loop also carries the instrumentation that a valid prove requires. Temperature and pressure taps sit on both the prover and the meter run so the flow computer can correct both volumes to common conditions - a prove is only as good as the conditions it is referenced to. Isolation and block-and-bleed valves let the prover be brought in and out of the flow path and proven leak-tight, since any valve passing flow around the calibrated section would corrupt the result. Detector switch wiring, pulse inputs from the meter, and a densitometer connection on some liquid loops complete the instrumentation.
The reason to build all this permanently into a station is throughput and confidence. On a high-value pipeline or LACT station where meters must be proved frequently, a permanent prover loop lets a prove be run whenever it is due - on a schedule, a throughput trigger, or a condition change - in minutes and without mobilising equipment. The capital cost of the loop is justified by the number of proves it will run over the station's life and by keeping the meters continuously and demonstrably accurate.
The prover loop is designed to be driven by a flow computer, which turns proving from a manual procedure into an automated sequence. When a prove is initiated, the flow computer first stabilises the flow and equalises conditions, then commands the four-way valve to launch the displacer. As the displacer trips the first detector switch, the flow computer starts counting the meter's pulses; when it trips the second detector, it stops. On a bidirectional loop it reverses the four-way valve and repeats the pass the other way, adding the two into a round trip.
Throughout, the flow computer reads the prover and meter temperatures and pressures and applies the corrections that bring both volumes to common conditions. It compares the meter's pulse-derived volume to the prover's certified base volume for each run and computes a provisional meter factor. It keeps launching runs until it has enough consecutive results that agree within the configured repeatability tolerance, at which point it averages them into the accepted meter factor, or it flags the prove as failed if repeatability cannot be met.
Finally the flow computer generates the prove report - the runs, the conditions, the repeatability, and the new factor - and loads the accepted factor for correcting subsequent flow. Because the loop is permanent and instrumented and the flow computer holds the whole sequence, the entire prove can run with minimal operator intervention: the person confirms the prove is due and reviews the result, while the loop and flow computer do the launching, timing, correcting, and calculating.
A permanent prover loop is a station subsystem that generates a lot of useful state: the last prove's date and result, the current meter factor, the repeatability of recent runs, the health of the detector switches and four-way valve, and whether a meter is coming due for its next prove. Because the loop is fixed and flow-computer-driven, all of this exists as data rather than something a technician has to be present to observe, which makes the loop well suited to remote supervision.
That matters because prover loops sit on stations that may be far from the measurement office, and the questions the team needs answered are ongoing: did the last prove pass, is the factor drifting, is a meter overdue, and is the loop hardware healthy. A four-way valve that is slow to seal or a detector that is starting to stick shows up as degrading repeatability over successive proves, which is exactly the kind of slow trend that a single on-site prove does not reveal but a history does.
A cloud SCADA platform such as Merobix reads the prove results, meter factors, repeatability, and prove-due status from the station's flow computers over an industrial protocol and trends them. Measurement staff can then confirm automatic proves are completing and passing across a fleet of stations, watch meter factors for drift, be alerted when a meter is overdue or a prove fails, and catch degrading loop hardware early - keeping oversight of many remote prover loops from one place while each loop and its flow computer run the physical proving on site.
A prover is the reference device with the calibrated volume - the pipe or piston prover itself. A prover loop is the whole permanently installed subsystem around it: the four-way valve, detector switches, temperature and pressure taps, isolation valves, and the piping that puts the meter and prover in series so a flow computer can run an automatic prove on demand at the station.
The four-way valve routes the flowing liquid to launch the displacer through the prover's calibrated volume, and on a bidirectional loop it reverses the flow to send the displacer back through the volume the other way. It is the piece of hardware that lets the flow computer sequence launches and reversals automatically, without an operator manually repositioning the displacer between runs.
It stabilises flow, commands the four-way valve to launch the displacer, counts meter pulses between the detector-switch trips, reads prover and meter temperatures and pressures to correct both volumes to common conditions, and computes a meter factor per run. It repeats runs until several agree within the repeatability tolerance, averages them into the accepted factor, logs the prove report, and loads the new factor for subsequent flow.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.