A flare and relief system protects process equipment from unacceptable overpressure. It does not hold pressure at the maximum allowable working pressure (MAWP) indefinitely: applicable design codes permit a defined margin of overpressure and accumulation under specified relieving scenarios, and the system’s job is to keep actual pressure within those allowable limits, not to prevent any pressure rise at all. ASME’s Boiler and Pressure Vessel Code addresses this overpressure protection requirement directly for the pressurized equipment it covers.
Flare and relief verification services confirm that protection is still valid, often years after the original design calculations were signed off. iFluids Engineering provides flare and relief verification covering overpressure scenario revalidation, PRV/PSV sizing verification, inlet and discharge piping checks, flare network hydraulic analysis, and disposal system capacity assessment for existing and modified process facilities. Operating conditions change: debottlenecking raises throughput, feed composition shifts, and a pressure safety valve sized a decade ago for one relieving case may no longer protect the vessel it sits on.
This is not a first-time design exercise. It is an independent technical check on pressure relief valve (PRV/PSV) sizing, flare header hydraulics, and disposal system adequacy, run against the facility as it actually operates today, not as it was originally designed. We have sat through the review meetings where a plant rerate quietly invalidated relief calculations nobody had re-checked in years. This service exists to catch that before a regulator, an insurer, or an incident does.
Every verification package we deliver stands on its own as an auditable technical record: calculation basis, standard clause references, and a clear pass, marginal, or fail finding for every relief device and header segment reviewed. Clients do not need to take our word for it. They need a report a third-party auditor, an insurer, or their own HSE authority can independently check.
What Is Flare and Relief Verification and What Does It Cover
iFluids Engineering delivers flare and relief verification services covering pressure relief system verification, PSV inlet and outlet piping checks, and flare network hydraulic analysis for facilities in operation or under modification. Our verification packages produce documented technical evidence structured around the specific standard each finding is checked against, not a single generic compliance statement.
The scope is organized around six linked technical checks. Each is a distinct engineering question with its own governing standard, and treating them as interchangeable is where thinner verification studies fall short.
Overpressure Scenario Revalidation
Credible overpressure scenarios, such as blocked outlet, external fire exposure, control valve failure, exchanger tube rupture, and utility failure, are re-evaluated against current operating data to confirm the required relieving load for each protected system. For each scenario, the applicable relieving-fluid regime, vapor, liquid, flashing, or two-phase, is then identified separately, since this determines which sizing method applies. For an external fire scenario specifically, API 521 establishes the basis for the fire-exposure relieving load, and API 520 Part I is then applied to size or confirm the relief device against that load.
Recognized for excellence.
PROJECTS DELIVERED ACROSS THE GLOBE
PRV / PSV Sizing Verification
This step is the core of any PRV sizing verification or relief valve adequacy study: the required relieving capacity and minimum required effective discharge area are recalculated using API 520 relief valve sizing methods and compared against the installed valve’s selected orifice designation, where applicable, rated capacity, and certified performance data. This is a three-way comparison, required area versus selected orifice versus certified capacity, not a simple required-versus-installed check.
PSV Inlet and Outlet Piping Verification
PRV inlet and discharge piping configuration is checked for adequacy, including inlet pressure loss, against API 520 Part II, which addresses the installation of pressure-relief devices. Excessive inlet pressure loss can contribute to valve instability even when the device itself is correctly sized, so inlet piping is checked against applicable API 520 Part II recommendations and engineering-analysis requirements rather than assumed adequate by default.
Flare Network Hydraulic Analysis
This is where flare header hydraulic analysis and API 521 flare system analysis converge: the flare header network is rebuilt or checked hydraulically against the governing relieving scenarios identified above. Because multiple devices often relieve simultaneously under a single upset, the network is checked against credible simultaneous loading, not one device’s relief in isolation.
Backpressure and PRV Compatibility
PSV backpressure analysis calculates superimposed and built-up backpressure for each governing flare scenario and checks it against every affected PRV under API 520 requirements, the device’s valve type (conventional, balanced bellows, or pilot-operated), and its certified performance data. Allowable backpressure is not one universal percentage: it depends on valve design, backpressure type, and manufacturer-stated capacity correction and stability limits, so each device is checked against its own certified basis.
Flare KO Drum and Disposal System Verification
The flare tip, knockout drum, and header segments are checked for unacceptable backpressure, excessive velocity or Mach number, choked-flow constraints, excessive pressure drop, and unacceptable liquid carryover under the governing simultaneous relief case, following API 521.
Relief System Revalidation for Existing and Modified Facilities
Relief system revalidation is not a periodic formality. It is triggered by specific engineering events, and treating it as routine paperwork is how gaps go unnoticed until an audit or an upset finds them first.
A management of change (MOC) affecting throughput, composition, pressure, temperature, control philosophy, or equipment configuration should include an assessment of whether the existing relief and flare design basis remains valid. This assessment is easy to skip when an MOC’s primary focus is elsewhere, such as a debottlenecking project centered on a compressor or a heat exchanger rather than the relief system itself. A plant debottlenecking or capacity rerate carries the same risk on a larger scale: throughput increases without a proportional review of relief and flare capacity.
An abnormal relief or flare event, including unexpected valve lifting, unusual flare behavior, or operating conditions outside the established flare design basis, is a further trigger worth investigating, though it does not by itself prove the relief or flare system is undersized. Assist-medium performance, flare gas composition, and transient loading can all produce unusual flare behavior independent of hydraulic capacity, which is exactly why a documented verification, rather than a visual assessment alone, is the appropriate response. A fourth trigger, often overlooked, is simple data age: relief calculations older than the operating envelope they were built for, with no documented review since the last major turnaround.
Engagements scoped directly against an MOC record are usually narrower and faster to close than a full-facility revalidation, since the review targets the specific change rather than every device on site. This gives the operator a defensible technical basis to attach directly to the MOC package before it is signed off.
PSV Sizing Verification vs Flare Network Analysis
These two checks are related but not the same, and scoping a study without distinguishing them is a common source of underestimated cost and missed findings. PSV sizing verification confirms an individual device against its own protected system. Flare network analysis confirms the connected disposal network can safely carry the credible simultaneous relief loads associated with each governing scenario.
| PSV / PRV Verification | Flare Network Verification |
| Individual protected system | Entire connected disposal network |
| Required relief rate | Simultaneous network load |
| Required PRV area | Header hydraulic capacity |
| Inlet and outlet conditions | Network pressure profile |
| PRV selection and capacity | Built-up backpressure |
| API 520 focus | API 521 focus |
A device can pass its individual sizing check under API 520 and still sit on a header network that no longer has the API 521 hydraulic capacity to carry the governing simultaneous load. Most engagements need both checks for exactly this reason.
Our Flare and Relief Verification Methodology
iFluids Engineering applies a documented methodology to every flare and relief verification engagement, producing calculation packages structured to hold up to independent technical review by operators, insurers, and regulatory bodies.
Our methodology follows six steps:
- Collect the current process basis. Gather up-to-date P&IDs, heat and material balances, PSV datasheets, and the facility’s existing flare network model or header isometrics.
- Re-derive governing overpressure scenarios. Identify the controlling case for every protected system under API 521, including scenarios introduced since the original design.
- Recalculate required relief area and sizing. Apply API 520 Part I methods, distinguishing relieving-fluid regime, and compare against each device’s certified orifice and rated capacity.
- Verify inlet and discharge piping. Check inlet pressure loss and discharge piping configuration against API 520 Part II installation requirements.
- Rebuild the flare header hydraulic model. Check backpressure, velocity, and pressure drop at every relief point under credible simultaneous loading, following API 521.
- Issue the verification register. Document every device and header segment with a pass, marginal, or fail finding, the governing standard, and a specific corrective recommendation.
| Deliverable | Primary Standards / Basis | Typical Trigger |
| PRV/PSV sizing verification | API 520 Part I, API 521, applicable ASME requirements | MOC, rerate, revalidation |
| PRV installation and piping verification | API 520 Part II | Existing installation review, modification |
| Flare header hydraulic verification | API 521 | Debottlenecking, rerate, new tie-in |
| PRV backpressure compatibility | API 520, API 521, manufacturer data | Header modification, capacity increase |
| Flare disposal system verification | API 521 | Rerate, network modification |
| Verification register | Client and project requirements | All engagement types |
Information Required for the Study
Any relief and flare system study is only as accurate as the process data behind it. iFluids Engineering scopes every engagement against the client’s own P&IDs, datasheets, and operating history rather than a generic data template, and we tell a client upfront exactly what is missing before work starts, not partway through the review.
We typically request current P&IDs and PFDs, heat and material balances, equipment and PSV datasheets, existing relief calculations, the line list, and piping isometrics covering PRV inlet and outlet runs. On the disposal side, we request the flare network model or header isometrics, flare tip and knockout drum data, and design and operating conditions for each relieving scenario in scope. Where available, process simulation results, relevant MOC records, and applicable project or operator specifications shorten the review cycle and reduce the number of clarification requests during the study.
Standards and Engineering Basis
iFluids Engineering verifies flare and relief systems in accordance with applicable requirements and guidance from API 520 Parts I and II, API 521, API 526, the relevant ASME Boiler and Pressure Vessel Code provisions for overpressure protection, client specifications, and applicable local regulations. Each standard is applied to the specific technical question it governs.
| Technical Question | Governing Standard |
| Required relief area, valve sizing and selection | API 520 Part I |
| PRV installation, inlet and discharge piping | API 520 Part II |
| Overpressure scenarios, relief loads, flare and disposal system | API 521 |
| Flanged PRV dimensions, orifice designations, procurement | API 526 |
| Overpressure protection requirements, allowable overpressure and accumulation | Applicable ASME BPVC construction section, and Section XIII where applicable |
Where a project requires it, the verification basis is supplemented by applicable operator engineering standards, national regulations, OISD standards, PESO requirements, statutory pressure-equipment requirements, and project-specific design criteria. iFluids Engineering has project and prequalification experience with major GCC operators, including ADNOC and KOC, and applies the equivalent supplementary framework for clients in other jurisdictions. API publishes and maintains the 520, 521, and 526 standards our methodology is built around, and we track edition updates against active client engagements.
Industries and Facilities We Support
iFluids Engineering verifies flare and relief systems for onshore and offshore oil and gas facilities, petrochemical complexes, LNG terminals, and gas processing plants, for clients across the GCC, India, Southeast Asia, and other markets. Facility age matters less than data currency: a newly commissioned unit undergoing early debottlenecking needs the same rigor as a decades-old refinery train.
Clients typically engage us either directly, as the operator’s process safety or asset integrity function, or through an EPC contractor managing a rerate or expansion project on the operator’s behalf. Both engagement models follow the same methodology and produce the same standard of deliverable, regardless of where the facility is located.
Flare and Relief Verification Deliverables
iFluids Engineering delivers a complete, auditable flare and relief verification package: sizing calculations, a flare header hydraulic model summary, a device-by-device findings register, and a prioritized corrective action list, each traceable to the specific standard clause it is checked against.
The findings register tracks each device and each scenario individually rather than reporting a single pass or fail for the whole facility:
| Per-PRV Record | Per-Flare-Scenario Record |
| Tag, protected equipment, set pressure, MAWP | Scenario and active relief sources |
| Governing scenario, required relieving rate | Total simultaneous relief load |
| Relieving pressure and temperature | Network pressure profile |
| Required area vs. installed area vs. certified capacity | Critical header segment |
| Valve type, inlet loss, backpressure | Maximum backpressure, velocity or Mach number |
| Status and corrective action | KO drum or tip limitation, and status |
Where a facility engages us following an abnormal relief or flare event, we additionally provide a technical basis document suitable for submission to the investigating authority. For engagements scoped as PSV sizing verification only, without a full header hydraulic rebuild, we issue a device-level report on the same timeline as the sizing phase of a full engagement, so a client with a narrower scope is not forced into a full-facility review to get a defensible answer.
Relevant Project Experience
Our flare system analysis and flare network analysis for a petrochemical facility in Penang, Malaysia applied this same verification discipline at project scale, identifying header segments approaching capacity limits before they became a constraint. See also our API 520, API 521 and API 526 pressure relief standards reference for the standards background behind this study.
Why iFluids Engineering
Engineering teams choose iFluids Engineering for flare and relief verification because our findings are traceable to a specific standard clause and device tag, not a generic compliance statement.
iFluids Engineering delivers process safety and risk engineering services across oil and gas, petrochemical, LNG, and energy facilities in multiple international markets. We are a global authority in process safety and risk engineering, and every verification report we issue is built to be checked independently rather than taken on trust. iFluids Engineering holds ISO 9001, ISO 14001, ISO 45001, and ISO 27001 certification, and our engineers hold recognized process safety and mechanical engineering credentials.
Engagement teams typically include a lead verification engineer, a hydraulics specialist for the flare network model, and a senior reviewer who signs off the final register before issue. We do not oversell scope: if a facility’s relief basis is already current and defensible, our verification confirms that in writing, which is itself a useful outcome for an operator preparing for an insurance audit or a regulatory inspection.
Ready to Discuss Your Project
If your facility has undergone a management of change, a debottlenecking project, or simply has not had its relief and flare basis reviewed since the last major turnaround, that is precisely the gap flare and relief verification is built to close. iFluids Engineering scopes each engagement against your specific P&IDs and operating data, not a generic checklist, and we are transparent about scope and timeline before work begins.
Our verification methodology is the same one applied in projects such as our flare network analysis in Penang, Malaysia, and it sits alongside our broader technical reference on API 520, API 521, and API 526 pressure relief standards for teams who want the background before scoping a study.
Contact iFluids Engineering to discuss your facility’s relief and flare verification needs, or to request a scope and timeline estimate for your specific plant.
Frequently Asked Questions
A single-unit verification covering PRV sizing and flare header hydraulics typically takes four to eight weeks from data receipt to final report, depending on the number of relief devices in scope. Multi-unit or full-site verifications tied to a plant-wide rerate generally run twelve to sixteen weeks, longer where key process data has to be reconstructed first.
The most common triggers are a management of change affecting throughput, composition, or equipment configuration, a plant debottlenecking or rerate, an abnormal relief or flare event, and simple data age, where relief calculations predate the current operating envelope. Any of these can mean a previously adequate relief basis no longer represents the current operating envelope, potentially leaving equipment or flare system capacity inadequately verified.
PSV sizing verification checks an individual relief device against its own protected system under API 520. Flare network analysis checks whether the connected header and disposal system can carry the combined relief loads associated with the applicable governing scenarios under API 521. A facility can pass one check and fail the other, which is why most engagements scope both together.
We typically need current P&IDs, heat and material balances, PSV datasheets, existing relief calculations, piping isometrics for PRV inlet and outlet runs, and the flare network model or header isometrics. Process simulation results and relevant MOC records, where available, shorten the review cycle considerably.
Not automatically, but any modification affecting relief load, feed composition, or header configuration should trigger an assessment of whether the existing flare and relief basis still applies. Skipping that assessment, rather than the modification itself, is a common way for a previously adequate relief basis to become outdated.
Clients receive PRV/PSV sizing verification calculations, a flare header hydraulic verification summary, a device-by-device findings register with pass, marginal, or fail status, and a prioritized corrective action list ranked by risk. Reports are formatted for direct use in MOC closure packages, insurance renewal submissions, or regulatory compliance files.
Verification engagements are led by senior process and mechanical engineers holding recognized process safety credentials, with direct hands-on experience applying API 520, API 521, and API 526 on operating facilities across multiple regions. Every deliverable is independently reviewed and signed off by a senior engineer before it reaches the client.