Executive Summary
A fertilizer facility operating ammonia storage and synthesis units required updated consequence modelling to support a statutory ERDMP revision, triggered by an increase in ammonia storage capacity. The facility's existing ERDMP had been based on dispersion modelling reflecting the previous, smaller storage capacity, and the capacity increase meant the emergency planning distances underpinning both the on-site and off-site emergency plans needed to be recalculated rather than assumed to remain conservative. This representative example illustrates consequence modelling methodology and findings typical of ERDMP updates triggered by inventory changes at ammonia-handling fertilizer facilities.
Facility Background
The facility operated an ammonia synthesis loop and associated refrigerated bulk storage, supplying downstream urea and other fertilizer production units. A capacity expansion had increased refrigerated ammonia storage inventory, a change that directly affects the credible release scenarios and hazard footprint distances used in the facility's ERDMP, since the potential release quantity in a worst-credible-case tank failure scenario scales with stored inventory. The facility's existing ERDMP, on-site emergency plan, and the District Disaster Management Authority's off-site emergency plan had all been developed against the prior, smaller storage capacity's hazard footprint.
Hazard Profile
- —Toxic ammonia release from refrigerated bulk storage, with consequence severity dependent on release rate, quantity, and prevailing weather conditions
- —Increased worst-credible-case release quantity following the storage capacity expansion, directly affecting downwind toxic dispersion distances
- —Synthesis loop process releases as a secondary but distinct scenario category from bulk storage releases, given different release rate and duration characteristics
- —Population exposure at varying distances and directions from the facility, requiring weather-category-specific consequence assessment rather than a single worst-case wind direction
Study Methodology
- 1.Scenario selection covering credible releases from the expanded bulk storage and the synthesis loop, including full containment failure and partial release scenarios
- 2.Source term calculation for each scenario, reflecting the increased storage inventory and its effect on release rate and duration assumptions
- 3.Heavy-gas dispersion modelling appropriate to ammonia's density behaviour at the relevant release conditions, run across multiple representative weather categories
- 4.Toxic concentration-time exposure threshold assessment at varying distances, identifying credible harm zones for emergency planning purposes
- 5.Hazard footprint distance determination for each scenario and weather category, identifying the governing (most conservative reasonably credible) case for emergency planning zone definition
- 6.Coordination of updated hazard footprint data with the facility's on-site emergency plan revision and input to the District Disaster Management Authority's off-site plan
Key Findings
- —The increased storage inventory extended the worst-credible-case toxic dispersion distance beyond what the existing ERDMP's emergency planning zones covered
- —Certain less-frequent but more conservative weather categories produced governing hazard footprint distances different from the weather category assumed in the facility's prior ERDMP basis
- —The synthesis loop process release scenarios, while smaller in consequence than bulk storage scenarios, indicated a distinct, shorter-distance planning zone relevant to on-site emergency response
- —Existing off-site emergency plan evacuation routing had not been reviewed against the revised hazard footprint, representing a coordination gap with the district authority
Risk Reduction Measures
- —Revised emergency planning distances submitted for both on-site and off-site emergency plan updates, reflecting the expanded storage's actual hazard footprint
- —On-site emergency response procedures updated to reflect the synthesis loop's distinct, shorter-distance planning zone alongside the bulk storage zone
- —Coordination meeting convened with the District Disaster Management Authority to review revised hazard footprint data and its implications for off-site evacuation routing
- —Updated ERDMP submitted incorporating the revised consequence modelling basis and coordination outcomes
Lessons Learned
Inventory changes should trigger consequence modelling refresh as a standing rule, not a discretionary judgment call.
The relationship between stored inventory and worst-credible-case release consequence is direct enough that any capacity change of this kind should automatically trigger a consequence modelling review, rather than relying on an engineering judgment that prior modelling remains conservative.
The governing weather category is not always the one assumed in an older ERDMP basis.
Revisiting the full set of representative weather categories, rather than only re-running the previously assumed governing case with updated inventory, revealed a different weather category actually producing the more conservative hazard footprint.
Updated hazard footprint data is only useful once it reaches the off-site planning authority in a form they can act on.
Technically correct consequence modelling results still require active coordination with the District Disaster Management Authority to actually update evacuation routing and off-site response — the modelling update and the coordination step are both necessary, and neither substitutes for the other.
Technical Takeaways
- —Treat any hazardous inventory increase as an automatic trigger for consequence modelling and ERDMP review
- —Re-run the full set of representative weather categories after an inventory change, rather than only the previously governing case
- —Distinguish bulk storage and process-loop release scenarios explicitly, since they can produce different governing planning zones
- —Actively coordinate updated hazard footprint data with the off-site emergency planning authority, not only the on-site plan