Searching...

Found

No results found for ""

Control Valve Sizing and Pressure Drop: Engineering Workflow

Engineering context

Control valve sizing is a pressure-balance problem, not simply picking a Cv. In a pipe network the valve is the balancing element: it takes up whatever pressure drop remains after the fixed terms (the boundary-to-boundary differential, static head, and any fixed equipment ΔP) and the flow-dependent variable losses (pipe and fitting friction, velocity head losses, equipment) are accounted for. Preliminary sizing in FluidFlow produces the process data a manufacturer needs — the preliminary Cv or Kv and the process conditions at the valve inlet and outlet — which the vendor then uses for detailed sizing and to propose a suitable valve model from their catalog.

Sizing centres on the maximum-flow case, because that is where the available valve pressure drop is at its lowest and the required Cv is at its highest, while the minimum-flow case sets the minimum Cv the manufacturer also needs for selection.

A practical workflow centres on the maximum-flow case — the model is built so maximum flow is achieved, whether driven by the highest pressure difference between two boundaries or, for pumped systems, the highest flow across the pump and/or control valve. The control valve can be represented with any of the control valve types depending on the data available, but care is needed during simultaneous pump and valve sizing, where defining flow in series at both the pump and the valve over-constrains the model. In that case the valve is modelled as an element generating a set pressure drop at maximum flow (commonly an assumed 10–15 psi as standard practice); where pressure boundaries serve as the inlet and outlet, the flow control valve can model it directly and no pressure drop need be assumed, since the model is not over-constrained. FluidFlow then calculates the preliminary Cv and the valve inlet and outlet conditions. The minimum-flow case is also established for the minimum Cv the manufacturer needs — by setting the flow control valve to the expected minimum flow, or for pumped systems by holding the maximum-flow duty pressure rise constant (a flat-curve pump assumption), since the valve absorbs the change in variable losses.

Start with guided FluidFlow training

Free Training

Engineering workflow

  1. Establish the maximum-flow case — build the model so that maximum flow is achieved, whether that is driven by the highest pressure difference between two boundaries or, for pumped systems, the highest flow across the pump and/or the highest flow across the control valve. This is the governing case for valve pressure drop and required Cv.
  2. Build and connect the network — place and define the boundary conditions (the fluid is selected from the database, which carries its properties, and applied at the boundary and carried through), then add pipes, fittings, elevations, and any equipment and connect them to establish topology.
  3. Represent the control valve according to the data available — it can be modelled with any of the control valve types. Take particular care during simultaneous control valve and pump sizing: defining flow in series — one definition at the pump and another at the control valve — over-constrains the model, since there is no pressure basis between them.
  4. When that situation occurs, model the control valve instead as an element that generates a set pressure drop at the maximum flow across it. There are different methods to establish a pressure drop that keeps the valve operating stably; the most common is to assume a value coinciding with maximum flow — typically 10–15 psi as standard practice.
  5. For systems that use pressure boundaries as the inlet and outlet points, the flow control valve can be used to model the control valve directly. Here there is no need to allocate or assume a pressure drop across the valve — the model already has enough information to complete its calculation and is not over-constrained, so FluidFlow resolves the valve pressure drop on its own.
  6. Solve the model — let FluidFlow calculate the preliminary control valve Cv and the corresponding process conditions at the valve inlet and outlet.
  7. Determine the minimum-Cv (minimum-flow) case — this is also important, as the manufacturer uses it in valve selection. For systems with pressure boundaries at inlet and outlet, set the flow control valve to the expected minimum flow. For pumped systems, capture how valve pressure drop varies with flow using a flat-curve pump assumption: take the duty pressure rise calculated at maximum flow and hold it constant at minimum flow. This works because the control valve absorbs the variable pressure drop, so any change in variable losses (here, the lower friction at reduced flow) is taken up — or “supplied” — by the control valve pressure drop.
  8. Hand off the process data — provide the preliminary Cv (maximum and minimum cases) and the inlet/outlet conditions to the manufacturer, who uses them for their detailed sizing calculation and proposes a suitable control valve model from their catalog.

How FluidFlow helps

FluidFlow sizes control valves inside a steady-state pipe network using the ISA/IEC 60534 method, returning the preliminary Cv/Kv and the valve inlet and outlet conditions against the connected system — pump or boundary driving pressure, pipe and fitting losses, equipment, and the overall pressure balance. It handles the balancing-element behaviour automatically and lets the valve be represented either directly or, during simultaneous pump sizing, as an element holding an assumed pressure drop at maximum flow. Final valve and trim selection remains with the manufacturer.

Go deeper

knowledge base

The complete control valve sizing guide

Cv, valve authority, and choked flow — the full engineering workflow.