A single blocked-outlet scenario at a refinery or gas processing plant can trigger four or five pressure relief valves at once, and if the shared flare header was never sized for that combined load, built-up back pressure can push those valves past their certified limits before the emergency even peaks. iFluids Engineering’s flare network analysis services model exactly this scenario: the complete flare header network, from individual relief device outlets through the knockout drum to the flare tip, under every credible combined relief case a facility can face. We work with process engineers, safety engineers, and asset integrity teams across GCC, India, and Southeast Asia to validate, or redesign, flare header networks against API 521 and API 520 Part II requirements before a revamp, debottlenecking project, or regulatory audit exposes a gap that a single-valve calculation would never catch.
This is not a relief valve sizing exercise repeated in isolation. It is a system-wide hydraulic model that accounts for two-phase flow, node-by-node pressure interaction across the header network, and the worst-case combination of simultaneous relief events a plant’s operating envelope allows. Facilities running brownfield expansions, capacity debottlenecking, or preparing for a management-of-change review use this flare network analysis service to confirm the existing header can carry new relief loads, or to identify precisely where it cannot.
What Is Flare Network Analysis and What Does It Cover
iFluids Engineering delivers flare network analysis that models the complete relief disposal system, including header piping, the knockout drum, and the flare tip, against combined relief-load scenarios defined per API 521. Our scope spans facility design, brownfield revalidation, and debottlenecking studies for onshore and offshore oil, gas, and petrochemical assets.
A flare network analysis differs from a standalone relief valve study in one fundamental way: it evaluates the shared piping system, not a single device. Individual pressure safety valves are sized against their own set pressure and required capacity, but once several valves discharge into the same header during a plant-wide upset such as total power failure or cooling water loss, back pressure at each valve outlet depends on every other valve discharging at the same time. A flare header hydraulic analysis, covering two-phase flashing flow behavior, elevation changes, and pipe routing, determines that shared back pressure across the network. The flare network analysis also verifies knockout drum liquid dropout performance and confirms the flare tip can pass the governing combined load without exceeding exit velocity (Mach number) limits or smokeless capacity thresholds. Where an existing network fails any of these checks, the deliverable identifies the specific bottleneck, whether that is an undersized header run, a knockout drum operating past its design vapor velocity, or a flare tip approaching sonic velocity, and quantifies what re-rating or re-routing resolves it.
This scope is distinct from the Flare Radiation and Dispersion Study iFluids also provides: the network analysis sizes and validates the header, drum, and tip against relief loads, while the radiation and dispersion study models the thermal and toxic footprint once flaring occurs. Facilities often commission both in sequence.
Our Flare Network Analysis Methodology
Our flare network analysis methodology follows a structured, standards-aligned sequence: relief case identification, network hydraulic modeling, back pressure verification against each valve’s certified limit, and a documented recommendation register. Every step traces to API 521 governing scenarios, not a generic checklist applied regardless of facility type.
The engineering sequence runs as follows:
- Define the relief case matrix. Identify every credible single and combined relief scenario (fire, power failure, cooling water failure, blocked outlet, control valve failure) applicable to the unit, per API 521’s contingency analysis approach.
- Build the header network model. Map every relief device tie-in, pipe segment, elevation change, and header junction from each PSV outlet through to the flare tip.
- Run the combined relief load analysis. Calculate simultaneous flow and pressure drop across the network for each governing scenario, including two-phase flashing flow where applicable.
- Verify built-up back pressure. Compare calculated back pressure at each valve outlet against its certified limit, typically 10% of set pressure for a conventional spring-loaded valve, higher for balanced-bellows or pilot-operated types.
- Check knockout drum and flare tip performance. Confirm liquid dropout efficiency, vapor velocity, and flare tip exit Mach number against the governing combined case.
- Issue the recommendation register. Document any header, drum, or tip modifications required, ranked by relief case severity and implementation complexity.
This sequence produces a defensible, standard-traceable basis for every recommendation, not a black-box output an operator’s HSE reviewer cannot audit.
Recognized for excellence.
PROJECTS DELIVERED ACROSS THE GLOBE
Industries and Facilities We Serve
iFluids Engineering performs flare network analysis for onshore refineries, gas processing plants, petrochemical complexes, offshore platforms, and FPSOs across the GCC, India, and Southeast Asia. Our scope covers greenfield design packages, brownfield revalidation ahead of a revamp, and debottlenecking studies tied to capacity expansion.
Refinery process units, particularly crude distillation, FCC, and hydroprocessing trains, generate the highest-consequence combined relief scenarios because multiple units frequently share a common flare header. Gas processing and LNG facilities present a distinct challenge: two-phase and cryogenic relief streams behave differently in header hydraulics than typical refinery vapor loads, and the analysis must account for that. Offshore platforms and FPSOs add weight and space constraints that make header re-routing far costlier than onshore, which is why flare system debottlenecking on a platform depends on getting the combined-load sizing right in the flare network analysis the first time, before steel is cut. Across all these facility types, the same underlying question drives the flare network analysis engagement: can the existing or proposed flare header network safely absorb the governing combined relief event, and if not, what is the minimum modification that closes the gap.
Regulatory and Standards Compliance
iFluids Engineering’s flare network analysis addresses API 521 (Pressure-relieving and Depressuring Systems) and API 520 Part II (Sizing, Selection, and Installation of Pressure-relieving Devices, Installation) as the governing technical basis, supplemented by regional regulatory requirements across GCC, India, and Southeast Asia.
Our related API 520 vs API 521 vs API 526 standards guide breaks down how these three standards divide responsibility across relief valve selection, disposal system design, and flanged fitting requirements relevant to any flare network analysis scope.
API 521 limits allowable thermal radiation at grade during emergency flaring to levels appropriate for manned and unmanned areas, commonly referenced at 3,160 BTU/hr·ft² for areas requiring rapid personnel egress, and our flare network analysis confirms the combined relief load driving that radiation case is itself correctly sized before any radiation modeling is performed downstream. In India, deliverables are structured to align with OISD process safety guidelines; in the GCC, study packages are formatted for acceptance by ADNOC and KOC technical review, and for submission to KAHRAMAA where applicable.
We are a global authority in process safety and risk engineering. That authority shows up in the traceability of every calculation back to a named standard clause, not an unreferenced assumption. Where local regulations impose a stricter back pressure or radiation criterion than the base API requirement, the study applies the more conservative limit and documents which governs.
Why Engineering Teams Choose iFluids
Engineering teams choose our flare network analysis services because the output is a fully documented, standards-traceable engineering package, not a proprietary black box dependent on any single calculation platform, and because that same standards-first discipline carries across every project we deliver.
Our team holds ISO 9001, 14001, 27001, and 45001 certification and is accredited by KOC and ADNOC for process safety scope of work, and the same team delivers our broader Process Safety Management engagements.
Because the methodology is grounded entirely in API 521 and API 520 Part II calculation logic rather than a specific licensed tool, an operator’s engineering review team can audit every assumption, every relief case, and every back pressure result the flare network analysis produces against the standard itself. That matters most during a management-of-change review or a third-party HSE audit, when a reviewer needs to trace a recommendation back to its technical basis rather than accept a vendor’s output at face value. Our engineers have executed flare network analysis studies for brownfield refinery revamps, offshore platform debottlenecking projects, and greenfield gas processing developments, carrying that same standards-first discipline across every project regardless of facility type or region. The result is a recommendation register that survives scrutiny from an operator’s own process safety department, not just from the consultant who produced it.
Deliverables and Outcomes
iFluids Engineering delivers a flare network analysis report, a hydraulic model summary, and a ranked recommendation register for every engagement. Typical outcomes include a validated header network, or a defined set of modifications with capital cost implications ranked by relief case severity.
Each flare network analysis deliverable below is formatted for direct submission to an operator’s engineering review board:
| Deliverable | Standard Basis | Typical Timeline |
| Relief case matrix and combined-load definition | API 521 | 1-2 weeks |
| Flare header hydraulic model and back pressure report | API 521, API 520 Part II | 3-5 weeks |
| Knockout drum and flare tip performance verification | API 521 | 1-2 weeks |
| Recommendation register with ranked modifications | Client review template | 1 week |
Combined project duration for a flare network analysis engagement typically runs 6-10 weeks depending on network complexity and the number of relief scenarios evaluated, with brownfield revalidation studies generally faster than greenfield design packages that require full network modeling from a blank sheet.
Ready to Discuss Your Project
If your facility is planning a revamp, debottlenecking project, or management-of-change review that adds relief load to an existing header, a flare network analysis gives your engineering team a standards-traceable answer before the project reaches detailed design. iFluids Engineering has delivered this scope for refineries, gas processing plants, and offshore platforms across GCC, India, and Southeast Asia, with every recommendation documented against API 521 and API 520 Part II.
Our track record includes flare network analysis revalidation work such as the Flare Network Analysis at Honeywell’s Penang Plant, where combined relief-load modeling confirmed the existing header’s capacity ahead of a capacity change.
Contact iFluids Engineering to discuss your facility’s relief case matrix, current header configuration, and the standards your engineering review team requires the study to meet. Our process safety team will scope these flare network analysis services against your specific facility type, region, and project timeline.
Frequently Asked Questions
A relief valve study sizes an individual pressure safety valve against its own set pressure and required relieving capacity. A flare network analysis evaluates the shared header, knockout drum, and flare tip under combined relief loads from multiple valves discharging simultaneously, which a single-valve study cannot capture on its own.
A facility needs a flare network study before adding new relief devices, during a capacity debottlenecking project, ahead of a management-of-change review affecting process conditions, or when an existing header has never been validated against current combined relief-load scenarios. Revamps and tie-ins are the most common triggers; skipping the study risks discovering header inadequacy only after a relief event.
Back pressure is calculated by modeling simultaneous flow from every relief device active in a given scenario through the shared header network, accounting for two-phase flow and elevation changes. The result at each valve outlet is compared against its certified built-up back pressure limit, typically 10% of set pressure for conventional valves.
A flare network analysis delivers a documented relief case matrix, a hydraulic model summary showing back pressure at every valve outlet, a knockout drum and flare tip performance check, and a ranked recommendation register identifying required header, drum, or tip modifications. Each item is formatted for direct submission to an engineering review board.
A typical engagement runs 6-10 weeks depending on network complexity and the number of governing relief scenarios. Brownfield revalidation of an existing header generally completes faster than a greenfield design package, which requires building the full network model from initial process data. Combined relief case complexity and the number of tie-in points drive most schedule variation.
Yes. iFluids Engineering formats deliverables for acceptance by ADNOC and KOC technical review in the GCC and for alignment with OISD process safety guidelines in India, with every recommendation traceable to API 521 and API 520 Part II clause references rather than an unreferenced assumption. This traceability lets an operator’s own process safety department accept the findings without independent re-verification.
