Overview
Boundary components are the starting point for every reliable pipe network model. In FluidFlow, tanks, reservoirs, vessels, and pressure boundaries define the physical limits of the system: where fluid enters, where it leaves, and what pressure, level, temperature, or flow condition the solver must satisfy.
For plant managers, boundary setup determines whether a model can be trusted for design, troubleshooting, energy optimization, and safety review. For engineers, boundary components translate real plant conditions into hydraulic inputs that govern pressure drop, pump duty, flow distribution, NPSH available, control valve performance, and relief or overflow behavior.
This article explains how FluidFlow boundary components are used, why they matter, and what good boundary definition looks like in practical engineering projects.
What are boundary components in FluidFlow?
Boundary components represent known conditions at the edges of a pipe network. They are not simply “start” and “end” points; they define the assumptions that anchor the hydraulic calculation.
Typical boundary components include:
Reservoir or Accumulator or Vessel (a) — open or closed sources/sinks with defined liquid level, elevation, temperature, and pressure conditions. Can represent a tank, vessel, or Accumulator
Known or Assigned Pressure boundaries (b) — fixed pressure points used to represent supply headers, discharge headers, atmosphere, or known process pressures.
Known or Assigned Flow boundaries (c) — imposed flow conditions where a required inflow or outflow is known.
Open Pipe (d) — used as an outlet boundary only. Simulates atmospheric discharge with a pressure loss coefficient (K) of 1.0.
Sprinkler (e) — used as an outlet boundary mainly for firefighting networks. This is supported by a database where the pressure loss can be calculated using a pressure loss coefficient (K) or via a Pressure Loss versus Flow rate curve.
Known Resistance (f) — used only as an outlet boundary condition. The user can specify a Pressure Loss Coefficient (K), and the solver will calculate the corresponding exit pressure loss and account for it in the overall calculation.
Figure 1. Overview of the available boundary components in FluidFlow.
In a pipe network solver, every calculation depends on how these conditions are defined. A pump curve, control valve Cv, or pipe pressure drop calculation can only be as realistic as the boundary conditions around it.
Why boundary components matter
Poorly defined boundaries are one of the most common causes of misleading hydraulic results. A model may converge numerically while still representing the real system incorrectly.
For engineering teams
Correct boundary setup helps engineers answer questions such as:
Is the pump operating near its expected duty point?
Is the suction side providing enough NPSH available?
Will the system meet flow requirements at low tank level?
How does vessel pressure affect downstream flow?
Is a control valve oversized because the available pressure drop was overestimated?
What happens when a receiving tank level rises, or a supply vessel pressure falls?
For plant managers and principal engineers
Boundary components support better decisions by making models more traceable and scenario-ready. They help teams:
Validate whether a design works across real operating conditions.
Compare equipment options with fewer spreadsheet assumptions.
Reduce commissioning surprises caused by missing static head or pressure constraints.
Identify where system limitations come from: pumps, pipes, valves, vessel pressure, or available liquid level.
Build a defensible technical basis for capital expenditure, debottlenecking, and energy reduction projects.
Common FluidFlow boundary types and when to use them
1. Reservoir or Accumulator or Vessel boundary
Use a reservoir when the equipment is maintained at a known pressure or atmospheric conditions.
Typical applications include:
Water storage tanks
Pressurized Vessels
Open sumps
Raw water reservoirs
Atmospheric drain or collection tanks
Separators
Reactors
Vacuum Vessels
Key inputs usually include:
Liquid level or elevation
Fluid temperature
Connection elevation
Atmospheric or specified surface pressure
The liquid level directly affects static head. This is especially important on pump suction systems, where a low-level case may reduce NPSH available and increase cavitation risk. Note that a pressurized vessel can significantly change system behavior. Positive pressure may increase available head, while vacuum conditions can reduce NPSH available or encourage flashing.
The input editor for the reservoir is shown below:
Figure 2. The Input Editor of the Reservoir or Accumulator or Vessel component in FluidFlow.
2. Known or Assigned pressure boundary
Use a known pressure boundary when the model connects to a larger system whose pressure is known or controlled externally.
Typical examples include:
Utility headers
Plant compressed air systems
Steam headers
Process supply or return headers
Discharge to atmosphere
Tie-ins to existing networks
A fixed pressure boundary is useful when the external network does not need to be fully modeled. However, it should be used carefully: if the “fixed” pressure varies in reality, scenario cases should be created for minimum, normal, and maximum pressure.
Note that the static pressure and stagnation pressure for the known pressure is always different. The solver accounts for the velocity pressure of the entering or exiting stream. The static pressure is typically calculated using the formula below (for incompressible flow):
The input editor for the Known or Assigned Pressure boundary is shown below:
Figure 3. The Input Editor of the Known or Assigned Pressure component in FluidFlow.
3. Known or Assigned Flow boundary
Use a flow boundary when the flow rate is known, and the model must calculate the pressure required to deliver or remove that flow.
Typical examples include:
Known process demand
Metered flow delivery
Injection rates
Batch transfer targets
Consumption points in distribution systems
Flow boundaries are useful for sizing pipework and checking required pressure. They are less appropriate when flow is not actually fixed in operation and depends on pump curves, control valves, or downstream resistance.
The input editor for the Known or Assigned Flow boundary is shown below:
Figure 4. The Input Editor of the Known or Assigned Flow component in FluidFlow.
Engineering considerations for tanks and vessels
Liquid level is not a minor detail
Tank level often creates a large part of the available static head. A model based only on normal operating level may look acceptable, but the same system may fail at minimum level.
Figure 5. Sample tank drawing from a specification sheet, showing the different liquid levels that should be considered when creating a hydraulic model.
Recommended cases:
Case | Why it matters |
Low Liquid Level | Checks worst-case pump suction and NPSH available |
Normal liquid level | Represents expected routine performance |
High liquid level | Checks high-head or overflow-related scenarios |
Startup or drawdown level | Captures transient operating envelopes in steady-state snapshots, if available. |
FluidFlow is a steady-state pipe network analysis tool, so time-dependent liquid level changes should be represented through multiple operating cases. A script can be developed using the scripting feature if time-based calculation is needed. Contact our Support Team for more details.
Elevation drives static head
Boundary elevation and nozzle elevation should reflect the real physical system. Confusing tank base elevation, liquid surface elevation, and pipe connection elevation can produce incorrect head calculations.
Engineers should confirm:
Datum used for elevations
Liquid surface level
Nozzle centerline elevation
Pump centerline elevation
Whether pressure values are gauge or absolute
Pressure values must match the physical reference
For closed vessels, pressure should be defined consistently. Gauge and absolute pressure confusion can lead to large errors, especially in vacuum systems, gas systems, or cavitation checks.
Use clear conventions:
Gauge pressure for plant instruments and most operating data
Absolute pressure when comparing against vapor pressure or evaluating NPSH available
Consistent units across pressure, elevation, and fluid property inputs
Boundary temperature affects fluid properties
Temperature can change density, viscosity, vapor pressure, and therefore pressure drop, NPSH available, and flashing risk, particularly in flow elements or at the inlet of a control valve.
This is especially important for:
Hot water systems
Condensate systems
Hydrocarbon liquids
High-viscosity fluids
Refrigerants
Slurries and non-Newtonian fluids where apparent viscosity may vary strongly with temperature
Boundary components and NPSH available
Pump suction boundaries are critical because they determine NPSH available.
NPSH available depends on:
Absolute pressure at the source
Static head between liquid surface and pump suction
Vapor pressure of the fluid
Suction line pressure drop
Fluid density and temperature
A reliable model should evaluate NPSH available at the most demanding condition, not just the easiest condition. For example:
Minimum tank level
Highest fluid temperature
Maximum suction line flow
Dirty strainer or added suction losses
Lower-than-normal vessel pressure
For safety-critical or high-value equipment, engineers should apply appropriate design margins and verify results against pump manufacturer NPSH required data. For more information, refer to the knowledge base blog about NPSH:
NPSH and Cavitation: How FluidFlow Identifies Cavitation and Flashing Risks | Fluid Flow Help Center
Boundary components and control valve sizing
Control valve sizing depends heavily on available pressure drop. If boundary pressures are unrealistic, the calculated valve Cv, authority, and installed performance may be misleading.
For example:
Overstated upstream vessel pressure can make a valve appear smaller than required.
Understated downstream pressure can exaggerate available pressure drop.
Ignoring high receiving tank level can hide a future capacity limitation.
Treating a variable pressure header as fixed can produce poor control decisions.
Saturated or liquid near the boiling point needs a specific change in elevation to avoid flashing at the entrance of the control valve.
A good FluidFlow model should test valves across realistic boundary scenarios, including low differential pressure and maximum demand cases.
Best-practice workflow for boundary setup in FluidFlow
Figure 6. Recommended workflow for selecting and verifying the appropriate boundary conditions when setting up a FluidFlow model.
Step 1: Define the real physical boundary
Start with the actual equipment or system interface:
Is it open to atmosphere?
Is it pressurized or under vacuum?
Is the pressure controlled?
Does the liquid level vary?
Is the boundary part of a larger network?
Step 2: Select the correct boundary component
Choose the component that best represents the physical condition rather than forcing the model to match a preferred result.
Step 3: Enter verified operating data
FluidFlow database is a powerful function that reduces the inputs of the user when using the software. However, engineers must verify if the properties in the database are similar to the project specifications. Use source data such as:
P&IDs
Datasheets
Tank level ranges
Control narratives
Instrument readings
Pump curves
Process design basis
Site survey elevations
Should there be any discrepancies between the values presented by the software and those expected from the process simulation, users may need to adjust the database values to ensure they accurately reflect the process conditions. These discrepancies may arise from differences in the thermodynamic packages used during the process simulation.
Step 4: Build scenario cases
At minimum, consider:
Minimum, normal, and maximum liquid level
Minimum and maximum vessel pressure
Summer and winter temperature cases where relevant
Normal and peak flow demand
Clean and fouled suction condition where applicable
Step 5: Review results in engineering context
Do not only check whether the model converges. Review whether the results make physical sense:
Are pressures reasonable?
Are flows in the expected direction?
Is pump suction pressure plausible?
Is NPSH available above NPSH required with margin?
Are valves operating in a controllable range?
Are high and low cases consistent with plant experience?
Common modeling mistakes to avoid
Mistake | Why it matters |
Using normal tank level only | Misses low-level suction and NPSH risks |
Mixing gauge and absolute pressure | Can cause major errors in cavitation, vacuum, and gas models |
Ignoring nozzle elevation | Distorts static head |
Treating a variable header as fixed | Overstates model certainty |
Applying fixed flow where flow is not controlled | Produces unrealistic required pressure |
Omitting downstream back pressure | Overpredicts capacity |
Using generic fluid properties | Can distort pressure drop and NPSH available |
Forgetting operating envelopes | Turns the model into a single-point calculation rather than a decision tool |
Modeling boundaries when there are high points | Creates vacuum points which sometimes leads to negative static pressure |
Example: transfer from a storage tank to a pressurized vessel
Consider a water transfer system with:
An atmospheric storage tank
A centrifugal pump
A control valve
An elevated receiving vessel operating at variable pressure
The boundary components define the most important system constraints:
The source tank liquid level determines static suction head.
The source fluid temperature determines density, viscosity, and vapor pressure.
The receiving vessel pressure determines discharge back pressure.
The receiving vessel level may affect the downstream static head.
The control valve must be evaluated against the actual available pressure drop.
A single normal case may show adequate flow. However, a more useful decision model tests:
Minimum source level + maximum receiving pressure
Maximum source level + minimum receiving pressure
Normal operation at design flow
High temperature case for NPSH available
Reduced pump speed or throttled valve case for control performance
Figure 7. FluidFlow calculation showing the effects of varying temperature and liquid level in an atmospheric tank on the pump NPSHa and pressure rise.
The results show that higher liquid temperatures reduce the NPSHa, thereby increasing the risk of cavitation. Conversely, a higher liquid level increases the NPSHa by providing additional static head at the pump suction.
The pump pressure rise remains relatively constant across all cases because the flow rate and discharge conditions remain essentially unchanged. However, increasing the liquid temperature may result in a slightly lower pump pressure rise.
When the destination pressure was changed, the control valve compensated by adjusting its pressure loss to maintain the specified flow rate to the destination. For example, when the destination pressure was increased, the control valve reduced its pressure loss to ensure that the required flow rate could still be delivered.
This approach gives engineers a more realistic view of operating limits and gives decision makers a clearer basis for equipment selection, project approval, and risk management.
Boundary condition checklist
Use this checklist when building or reviewing FluidFlow models:
[ ] Confirm whether each boundary is open, closed, pressurized, or flow-controlled.
[ ] Record the pressure basis: gauge or absolute.
[ ] Confirm the elevation datum.
[ ] Enter liquid surface level and nozzle elevation separately where applicable.
[ ] Use realistic fluid temperature and properties.
[ ] Test minimum, normal, and maximum operating cases.
[ ] Check pump NPSH available at worst-case suction condition.
[ ] Confirm downstream back pressure or receiving vessel pressure.
[ ] Avoid fixed-flow assumptions unless flow is genuinely imposed.
[ ] Document every boundary assumption in the model notes or project basis.
Conclusion
Boundary components are among the most important inputs in a FluidFlow model. Tanks, reservoirs, vessels, pressure boundaries, and flow boundaries define the physical conditions that drive pressure drop, pump duty, NPSH available, valve sizing, and system capacity.
For engineers, careful boundary setup improves model accuracy and troubleshooting value. For plant managers, it provides a stronger basis for approving designs, prioritizing upgrades, and reducing operational risk.
A FluidFlow model is only as reliable as the boundary conditions that define it. When boundaries reflect real operating envelopes - not just ideal design points - the model becomes a practical decision-making tool for safer, more efficient pipe systems.