AI Quick Summary

Compare consequence and risk-analysis software by the decision, scenario and review needs. Learn what vendor descriptions establish and what still needs independent verification.

Choose a modelling workflow from the decision and physical scenario, then confirm the required methods, inputs and review criteria. Software can calculate specified models; it cannot decide whether the scenario set, data or assumptions are suitable for a site-specific risk assessment.
For South African Major Hazard Installations, regulation 10 requires a duty holder to ensure that an approved inspection authority (AIA) carries out a risk assessment in accordance with SANS 1461. The Regulations do not name a particular software product. The selection should therefore be checked against the scope and method required for the assessment, and agreed with the AIA and relevant reviewers. South African MHI Regulations, regulation 10

Consequence modelling and QRA are different tasks

Consequence modelling estimates the effects of a defined release or event, such as dispersion, thermal radiation or overpressure. Quantitative risk assessment combines defined scenarios and their frequencies with consequence results to assess risk. A tool that calculates consequences alone may be one part of a QRA workflow, but that does not make it a complete QRA system.

Need Questions to answer before selecting a tool
Screening or emergency planning Is the tool intended for the use, chemical and level of detail? What assumptions and limitations must be communicated?
Consequence assessment Can the model represent the release phase, source term, weather, terrain, congestion or geometry that matters?
Quantitative risk assessment Can the workflow handle the required scenario frequencies, event sequences, risk measures, aggregation and review trail?
Complex geometry or physics Does the case need specialist modelling, such as computational fluid dynamics, and who will validate the model setup?

What the product descriptions say

DNV Phast is described by DNV as software for consequence analysis, including discharge, dispersion, fires, explosions and toxic effects. DNV identifies applications such as HAZOP and emergency response planning. Its capabilities and add-ons vary, so confirm the version and modules required for the scenario. DNV also offers Safeti for QRA; check the current product documentation and proposed licence scope with the supplier. DNV Phast · DNV consequence-analysis products · DNV Phast and Safeti FAQs
Gexcon EFFECTS and RISKCURVES have distinct roles in the vendor’s documented workflow. Gexcon describes EFFECTS as a consequence-modelling tool and RISKCURVES as a QRA tool that can use consequence results. Its documentation says RISKCURVES focuses on QRA rather than detailed consequence analysis and directs users to EFFECTS for source-term analysis. Check the documentation for the model and mixture relevant to your case. Gexcon RISKCURVES scenario guidance
ALOHA, part of the US EPA CAMEO software suite, estimates threat zones for chemical releases and is used for chemical emergency planning and response. EPA describes models for toxic and flammable clouds, fires and explosions. NOAA’s ALOHA guidance documents model limitations. Treat its output as an estimate for the scenario and use it only where the intended decision and limitations fit; do not assume it performs a complete frequency-based QRA. US EPA ALOHA · NOAA ALOHA FAQs and limitations
These descriptions come from the software developers and government agencies. They explain stated capabilities; they do not establish that a tool is accepted for every project, regulator or South African MHI submission.

A reviewable selection process

Before commissioning or purchasing a tool, write down:

  1. The decision: What will the analysis support: emergency arrangements, design, siting, a safety report or another decision?
  2. The scenarios: Which substances, equipment, release conditions, physical effects and receptor locations must be represented?
  3. The workflow: Which parts need consequence modelling, event frequencies, risk aggregation, mapping or specialist simulation?
  4. The evidence: What input data, model version, assumptions, validation records and sensitivity cases will be retained?
  5. The review: Who will challenge scenario selection, frequencies, model limits and conclusions? What must the AIA, client or authority see?
  6. The commercial scope: Which modules, users, support, training and licence terms are included? Obtain a current supplier quote rather than relying on old online price claims.
    The output should let a reviewer trace each result back to its scenario, data, model choice and assumptions. Document uncertainty and show how it affects the decision. A precise-looking contour is not proof that the inputs are accurate.

Common selection mistakes

  • Comparing software before defining the scenario. A model suited to a simple release may not represent complex mixtures, congestion or three-dimensional geometry.
  • Treating a consequence tool as a complete QRA. Check whether the workflow also covers the required frequencies, event sequences and risk aggregation.
  • Assuming that a popular product guarantees acceptance. Confirm project and regulatory requirements with the relevant reviewer; the product name alone does not establish compliance.
  • Relying on generic comparison numbers. Results depend on source term, weather, model settings, endpoints and scenario assumptions. Compare only documented runs with a reviewable basis.
  • Choosing on licence price alone. Include specialist effort, data development, validation, review and lifecycle support in the project scope.

Frequently asked questions

Does South African MHI regulation require a named QRA software package?

Regulation 10 refers to an AIA risk assessment in accordance with SANS 1461. The cited Regulations do not name a particular software product. Confirm the required method and submission basis with the AIA and relevant authorities.

Can ALOHA replace a full QRA?

ALOHA estimates hazard threat zones for emergency planning and response. A full QRA also requires suitable scenario frequencies and risk assessment. Whether ALOHA fits a specific task depends on the decision, model scope and limitations.

Which tool is most accurate?

There is no single tool that is most accurate for every scenario. Check whether its models and inputs represent the physical case, use appropriate data, document uncertainty and obtain competent review.
For an assessment, agree the scenario list, model scope and review requirements before selecting software. Read our QRA guide and consequence modelling overview, or contact MMRisk to discuss a project scope.

Product references