Most industrial facilities are designed to a standard. An engineer consults NFPA 13, NFPA 30, or the applicable SAES document, selects a system that meets the listed requirements, and the project moves forward. It is a proven, reliable approach — and for the vast majority of scenarios, it works exactly as intended.

But some facilities don’t fit the prescriptive mold. Complex geometries, mixed occupancy types, novel process hazards, or retrofit constraints can put a facility in a gray zone where the code’s explicit requirements either don’t quite apply or don’t produce an efficient design. That’s where performance-based fire protection design enters, and where tools like FDS and CFAST become the engineer’s most powerful instruments.

What Performance-Based Design Actually Means

Performance-based design (PBD) is not a shortcut or a workaround. It is a structured engineering methodology that replaces prescriptive compliance with demonstrated compliance. Instead of asking “does this design meet the code’s stated requirement?”, the engineer asks “does this design achieve the safety outcome the code is trying to guarantee?”

NFPA 101 and NFPA 5000 both include explicit performance-based design options, and the framework is recognized under the broader body of fire safety engineering standards including SFPE (Society of Fire Protection Engineers) guidelines. The approach requires:

• Defining specific fire safety goals and objectives for the facility
• Establishing performance criteria — measurable thresholds for tenability, structural integrity, or egress
• Developing fire scenarios that represent credible, worst-case, and design-basis events
• Running engineering analysis to demonstrate the proposed design meets those criteria under those scenarios
• Documenting the analysis in a format reviewable and defensible to the authority having jurisdiction (AHJ)

In a Saudi Aramco context, SAES standards establish the baseline requirements for most process facilities. Where a specific facility configuration falls outside the explicit scope of those standards, or where an operator wants to justify an alternative protection approach, a performance-based analysis — supported by fire modeling — provides the technical basis for that justification.

FDS: The Industry Standard for Fire Dynamics Simulation

Fire Dynamics Simulator (FDS) is a computational fluid dynamics (CFD) model developed by the National Institute of Standards and Technology (NIST). It solves the Navier-Stokes equations for low-speed, thermally driven flows, with particular attention to smoke and heat transport generated by fire. For industrial fire protection engineers, FDS is the primary tool for high-consequence scenario analysis.

What FDS does well:

• Smoke movement and visibility modeling — predicts how combustion products migrate through complex geometries, including open-plan process areas, large equipment enclosures, and multi-level structures
• Radiant heat flux analysis — quantifies thermal exposure to adjacent equipment, structural members, and egress paths for pool fires, jet fires, and flares
• Sprinkler and suppression activation — models detector and sprinkler response timing based on plume characteristics and ceiling jet behavior
• Ventilation interaction — assesses how HVAC systems, natural openings, and wind affect fire growth and smoke layering

FDS requires a geometry input (typically built from CAD or BIM data), fuel characterization, boundary conditions, and a defined fire growth curve. The output is a time-resolved, three-dimensional dataset that can be post-processed in Smokeview — NIST’s companion visualization tool — to produce the kind of frame-by-frame fire progression imagery that makes a performance-based analysis legible to regulators, project managers, and clients.

It is important to be clear about what FDS is not: it is not a predictive oracle, and results are only as reliable as the inputs and the modeler’s judgment. Verification and validation against published experimental datasets — which NIST has documented extensively — are part of responsible FDS use, and any defensible performance analysis will document those limitations explicitly.

CFAST: Zone Modeling for Faster Scenario Screening

Where FDS is a high-resolution tool suited to detailed, site-specific analysis, CFAST (Consolidated Fire and Smoke Transport) is a two-zone model — also developed by NIST — that divides a compartment into a hot upper layer and a cooler lower layer and tracks their growth over time. It runs orders of magnitude faster than FDS and is well-suited to:

• Early-stage scenario screening to identify which fire scenarios warrant full CFD analysis
• Sensitivity analysis across a range of fire sizes, ventilation configurations, or suppression response times
• Egress and tenability calculations where compartment-level gas temperatures, CO concentrations, and visibility are the primary outputs of interest
• Documentation of simpler enclosed-space scenarios where the two-zone assumption is physically reasonable

CFAST is not appropriate for large, open industrial geometries or scenarios where detailed three-dimensional flow behavior is critical to the analysis outcome. The engineer’s job is to match the tool to the question — and to clearly document that match in the analysis report.

Together, FDS and CFAST form a tiered modeling approach: CFAST for breadth, FDS for depth. Many performance-based analyses use both, with CFAST results informing which fire scenarios receive full FDS treatment.

A Worked Example: Process Facility Muster Area Verification

Consider a hypothetical scenario that is representative of the kind of engineering problem that drives performance-based analysis in Saudi industrial facilities.

A process facility has a muster station located 80 meters from a flammable liquid processing area. The prescriptive standard specifies a minimum separation distance, but the facility’s site constraints mean the muster station is in a partially enclosed structure adjacent to a pipe rack. The question: under a credible worst-case pool fire scenario in the processing area, does the muster station remain tenable for the duration required for personnel accountability and evacuation?

The performance-based approach would proceed as follows:

1. Define the design fire scenario — characterize the flammable liquid, maximum credible spill area, and fire growth rate based on NFPA 30 and historical incident data for similar materials
2. Set performance criteria — tenability thresholds for radiant heat flux, air temperature, and smoke visibility at the muster station, derived from SFPE guidelines and NFPA 101 exposure limits
3. Build and validate the FDS model — import facility geometry, specify boundary conditions including wind, and run the design fire scenarios
4. Evaluate results against criteria — does the muster station exceed the radiant heat flux threshold? At what time? Does ventilation in the partial enclosure accelerate smoke accumulation?
5. Iterate on design if needed — if the first design fails the criteria, modify the geometry, add shielding, or relocate the muster point and rerun
6. Document and submit — prepare a full performance-based design report for AHJ review, including all assumptions, model inputs, and a clear statement of what the analysis can and cannot demonstrate

This process is more work than prescriptive design. It is also the only rigorous way to evaluate a non-standard configuration — and in a Saudi Aramco context, where the AHJ is technically sophisticated and the consequences of getting it wrong are significant, a well-executed performance-based analysis provides a level of defensibility that no prescriptive checklist can match.

When to Use Performance-Based Design — and When Not To

Performance-based design is not the answer to every fire protection problem. It adds cost, time, and specialized expertise to a project. It is most clearly justified when:

• The prescriptive standard does not address the specific occupancy or hazard configuration
• Prescriptive compliance would require a design that is technically infeasible or economically disproportionate
• The operator wants to document the engineering basis for an alternative protection approach
• Regulatory or insurance requirements demand a quantified risk justification rather than a code-compliance checklist

It is not appropriate as a mechanism to avoid legitimate prescriptive requirements or to justify a lower level of protection without rigorous analysis. The AHJ — whether that is Saudi Civil Defense, Saudi Aramco’s engineering authority, or an international regulator — will scrutinize the assumptions. If the analysis cannot stand up to that scrutiny, the design cannot stand either.

The engineer’s obligation in a performance-based analysis is the same as in prescriptive design: the building doesn’t care what methodology you used. It performs the way the physics dictates. The analysis has to get the physics right.

The Bottom Line

Performance-based fire protection design, executed with validated tools like FDS and CFAST, is a mature engineering discipline with a clear role in industrial fire safety. For complex process facilities — particularly those in the Saudi petrochemical sector where SAES standards meet challenging geometry and high-consequence hazards — it provides the technical foundation to make defensible engineering decisions that prescriptive codes alone cannot support.

Used correctly, it is not a workaround. It is the most rigorous thing an engineer can do.

Work With Ignis Sentinel Engineering

Need a fire risk assessment, a third-party plan review, or an NFPA/SAES
compliance check for your facility? Our engineers help Saudi and international
industrial operators design safer operations.

Book a consultation