Blast Planning & Explosives Documentation

Blast Planning and Explosives Management — design and approval, drilling and hole validation, explosives custody from magazine to hole, charging, clearance and firing, post-blast outcomes, misfire response, and the reconciliation that must balance before a blast can close

This section covers the Blast Planning and Explosives Management application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.

In This Section

The Application in One Paragraph

Blast Planning and Explosives Management runs the full operational record for a mine blast, from the request that raises it to the reconciliation that closes it. A BlastRequest becomes a Blast, which carries versioned designs (a revision supersedes its predecessor rather than overwriting it), the approvals those designs need from separate technical, environmental and management roles, a risk assessment with hazard-by-hazard initial and residual ratings, exclusion boundaries, and an assessment against every sensitive receiver — homestead, pipeline, public road. Holes are then drilled, surveyed and condition- inspected, and a hole that fails inspection cannot be charged. In parallel the explosives chain runs on batch-level custody: products and batches held in licensed magazines, issued to a mobile processing unit against the blast, transported under a movement record, consumed hole by hole, and returned — every kilogram accounted for by an ExplosiveStockTransaction. Charging is planned per hole and deck and recorded as actuals with any deviation and its reason; quality checks catch what the plan did not. Then initiation and tie-in, notifications, the clearance plan with its guard posts and area clearances, weather suitability, and the fifteen-point pre-fire checklist that gates the shotfirer's authorisation to fire. Afterwards: post-blast inspection, and if it finds misfire indicators the area stays excluded until the misfire is treated under an approved plan and independently verified by somebody other than the person who treated it; only then is re-entry authorised. Monitoring, flyrock, fume, fragmentation and muckpile results are captured, and the blast closes only when the reconciliation of holes, explosives and tonnage balances — which, in the demo, it does not.