The whole point of stabilizing condensate is to make a liquid that will not flash off vapor when it sits in a tank or rides in a truck or a pipeline, and the number that captures how well that has been achieved is the vapor pressure of the product. Condensate RVP control is the practice of driving a stabilizer to hit a target Reid, or true, vapor pressure on the liquid it makes, so the product is neither so volatile that it loses value and vents vapor nor so heavily stripped that useful components have been boiled away. The main handle is heat at the bottom of the column. This guide explains how reboiler duty and bottoms temperature set the product vapor pressure, why the RVP spec matters for tank, truck, and pipeline vapor loss, and how SCADA closes the loop on an inferred RVP.
Condensate RVP Control in one line: Condensate RVP control regulates a stabilizer so the liquid product meets a target Reid vapor pressure, which measures how much vapor the product will try to release at a reference temperature. It is achieved mainly by manipulating reboiler duty and therefore the column bottoms temperature: more heat boils off more of the light, volatile components, lowering the product's vapor pressure, while less heat leaves more of them in and raises it. Because RVP cannot be measured instantly inline, SCADA usually infers it from the bottoms temperature and pressure and closes the loop on that inferred value.
The vapor pressure of the stabilized product is set by how much light, volatile material is left in it, and that is decided at the bottom of the column by the reboiler. The reboiler adds heat to the bottoms, boiling the lighter components back up the column and out overhead, and the more heat it adds, the more of those volatile ends are driven off and the lower the vapor pressure of the liquid that remains. So reboiler duty is the primary lever on product RVP: turn up the heat and the product gets more thoroughly stripped and less volatile; turn it down and the product keeps more light ends and becomes more volatile.
In practice the reboiler duty shows up as a bottoms temperature, and at the column's operating pressure that temperature corresponds to a particular degree of stripping and therefore a particular product vapor pressure. Running the bottoms hotter means a lower RVP product, running it cooler means a higher RVP product, and the relationship is tight enough that bottoms temperature at a known pressure is a good proxy for the vapor pressure of the liquid leaving the column. This is why stabilizer control so often comes down to holding a bottoms temperature: that temperature is standing in for the RVP the operator actually cares about.
There is a tradeoff hiding in that lever, which is what makes control rather than simple maximisation the goal. Over-stripping by running the bottoms too hot does hit a low RVP, but it also boils useful heavier components out into the overhead where they are lost from the liquid product, shrinking the volume and value of what is made. Under-stripping saves that heat and keeps the volume up but leaves the product too volatile to meet spec. The correct control drives the bottoms just hot enough to bring the product to its RVP target with a small margin, and no hotter, so the product is on spec without giving away recovery.
Reid vapor pressure is not an arbitrary number; it is a direct measure of how much the product will try to vaporise, and everything that happens to the condensate after it leaves the stabilizer depends on keeping it low enough. In a storage tank, a product with too high a vapor pressure flashes off vapor into the tank's vapor space, which raises the pressure, works the tank vents or the VRU harder, and shows up as emissions or lost product. The whole reason for stabilizing in the first place is to stop the product from breathing away its value in the tank, and the RVP spec is the yardstick for whether it will.
The same volatility drives the requirements for moving the product. Trucks and pipelines set vapor-pressure limits on the liquids they will accept, because product that is too volatile behaves badly in a tanker or a line, generating vapor, complicating loading, and posing a safety concern. Meeting the RVP spec is often a hard condition of being allowed to ship at all, so a stabilizer that cannot hold RVP does not just lose a little vapor, it can produce a product that the takeaway simply will not take. The spec is therefore a gate on the product being sellable and movable, not merely a quality preference.
Because so many downstream consequences hinge on it, RVP control is really about consistently landing on the right side of a line rather than chasing the lowest possible number. Just below the spec limit, with a modest margin, is the ideal place to run: it satisfies the tank, truck, and pipeline requirements and keeps vapor loss in check, while not over-stripping the product and throwing away recoverable volume. Control that hunts around the limit, sometimes over and sometimes under, either risks a rejected batch or wastes value, which is why steady, close control of the inferred RVP is what a well-run stabilizer aims for.
RVP is a laboratory measurement that cannot be read instantly off the running liquid the way a temperature or pressure can, so a stabilizer control almost never closes a loop on a live RVP reading directly. Instead it uses an inferred RVP: because the bottoms temperature at the column's operating pressure corresponds closely to the product's vapor pressure, SCADA computes an estimate of RVP from the measured bottoms temperature and pressure and controls to that. In effect the loop holds a bottoms temperature, but it is framed and displayed as holding an RVP, so the operator thinks in the spec that matters rather than in a raw temperature.
Running the loop on inferred RVP lets the control ride out the disturbances a stabilizer sees while keeping the product on spec. As feed rate, feed composition, and reboiler heating change, the loop trims reboiler duty to hold the inferred RVP steady, which is more meaningful than freezing the reboiler at a fixed firing rate and letting the product wander. Periodic laboratory RVP samples are used to check and correct the inference, so the estimate stays honest against the real measured vapor pressure, and the setpoint can be biased to keep the true RVP comfortably inside spec with a small margin.
A cloud SCADA and monitoring platform such as Merobix is a natural fit for this because a product that drifts off RVP spec is expensive to discover late, whether as a rejected shipment or as tanks quietly venting. Merobix trends the bottoms temperature, pressure, and the inferred RVP against the spec limit, logs the reboiler duty, and can alarm when the inferred RVP climbs toward or past the limit, so an under-stripped batch is flagged while it is still in the column rather than after it has been loaded. Recording the inferred RVP alongside the occasional lab result lets an engineer keep the inference calibrated and see how much margin the stabilizer is really running with, and for an unattended facility that continuous view is what gives confidence that every batch leaving the column is on spec and safe to ship.
It manipulates the reboiler duty, and therefore the column bottoms temperature, to control how much light volatile material is left in the product. More heat boils off more of the light ends and lowers the product's vapor pressure, while less heat leaves them in and raises it. The control drives the bottoms just hot enough to bring the product to its RVP target with a small margin, without over-stripping and losing recoverable heavier components to the overhead.
Reid vapor pressure measures how much the product will try to vaporise, and product that is too volatile flashes vapor in storage tanks, raising pressure and causing emissions or lost product. Trucks and pipelines set vapor-pressure limits on the liquids they accept because volatile product is harder and less safe to load and move. Meeting the RVP spec is often a hard condition of being allowed to ship, so a stabilizer that cannot hold RVP can make product the takeaway will not take.
RVP is a laboratory measurement that cannot be read live off the running liquid, so SCADA infers it from the bottoms temperature and pressure, which correspond closely to the product's vapor pressure at the column's operating conditions. The loop controls reboiler duty to hold that inferred RVP steady, and periodic lab samples are used to keep the inference calibrated. The setpoint is biased so the true RVP stays comfortably inside spec with a small margin.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.