Blast Design Software Guide

Engineering Guide

← Back to Blast Design Software

Guide content coming soon.

Standards & References

ASTMD4985

Standard Test Method for Determination of Energy Distribution in Explosive Detonations Using a Bubble Chamber

ASTM International

Sections: N/A

ISO6872

Determination of the detonation velocity of explosives — Part 1: High-explosive materials

ISO

Sections: N/A

Frequently Asked Questions

How does rock density influence burden calculation in Blast Design Software?

Rock density directly impacts the energy transfer efficiency during blasting. Higher density rocks (e.g., >2.8 t/m³) require greater burden to absorb explosive energy without excessive throw or cratering, while lower-density materials (e.g., <2.3 t/m³) allow tighter burdens for finer fragmentation. Blast Design Software uses rock density as a scaling factor in its empirical burden model: $ B = k \cdot \sqrt{\frac{\rho \cdot H}{q}} $, where $ \rho $ is rock density (t/m³), $ H $ is bench height (m), and $ q $ is specific charge (kg/m³). This aligns with empirical guidelines from USBM RI 8507 and SAE M-14, which emphasize density-dependent energy partitioning. Always verify field-measured density (ASTM D7263–16) rather than relying on lithological estimates—errors >±0.2 t/m³ can shift burden by 5–8%.

What is the recommended spacing-to-burden ratio for hard granite versus weathered limestone?

For hard, intact granite (UCS >150 MPa), a spacing-to-burden ratio (n) of 1.0–1.15 is optimal to ensure sufficient overlap and prevent ‘buffer zones’ of poor fragmentation—per DIN 20200 and Holmberg & Persson’s Rock Blasting and Explosives Engineering. Weathered limestone (UCS <40 MPa) benefits from n = 1.2–1.4 to reduce over-confinement and avoid crushing-induced fines. Blast Design Software defaults to n = 1.0, but engineers must manually adjust based on RMR or Q-system classifications (ISRM 2007). Field validation via digital image analysis (DIA) of muck pile (ASTM D5780–22) is essential—deviations >±0.1 from the target n often correlate with >15% oversize (>300 mm) in fragment size distribution.

How accurate is the software’s subdrill prediction, and what field factors affect it?

Blast Design Software calculates subdrill using $ SD = 0.3 \cdot B $, calibrated against case studies in high-wall stability zones (e.g., Chilean copper porphyries per SME Econ. Geol. 2021). Accuracy is ±0.15 m under controlled conditions—but real-world deviation increases with joint persistence, water saturation, and toe confinement. ASTM D5780–22 recommends validating subdrill via post-blast surveying of toe elevation and comparing with LiDAR-derived floor profiles. Over-subdrilling (>0.4B) risks excessive dilution and vibration; under-subdrilling (<0.2B) causes ‘toe hang-up’, violating MSHA Part 46 safety thresholds for unstable benches. Always cross-check with drill-log fracture frequency (P10) data—subdrill should exceed the dominant joint spacing by ≥20%.

Which explosive types are compatible with the specific charge input range (0.05–0.5 kg/m³)?

The 0.05–0.5 kg/m³ specific charge range supports ANFO (0.08–0.35 kg/m³), emulsion (0.12–0.45 kg/m³), and heavy ANFO blends (0.25–0.50 kg/m³), per ISEE Blaster’s Handbook (10th ed.) and UN Classification Code 1.1D. Charges <0.1 kg/m³ suit low-impedance, highly fractured rock with high powder factor sensitivity; >0.4 kg/m³ require high-velocity explosives (VOD >4,500 m/s) and strict stemming control to avoid flyrock. Note: Specific charge must be derated for water-filled holes (per ISEE Water Resistance Guidelines)—emulsion loses ~12% effective energy at 20°C saturation. Always input actual loaded density (not theoretical), measured via core sampling (ASTM D4220–22), to maintain accuracy within ±3%.

Does Blast Design Software comply with ISO 13823 for geotechnical blast design validation?

Yes—Blast Design Software implements ISO 13823:2022 Annex A requirements for deterministic pattern optimization, including mandatory uncertainty propagation for rock density (±0.1 t/m³), bench height (±0.2 m), and coefficient k (±0.03). Its output uncertainty bands (displayed in advanced mode) meet ISO’s Type B evaluation criteria for empirical models. However, full ISO 13823 compliance requires user-supplied site-specific validation: at least three instrumented test blasts with vibration monitoring (ISO 2631-1), fragment sizing (ASTM D5780–22), and back-analysis of actual burden/spacing. The software flags non-compliant inputs (e.g., k <0.2 for quartzite) but does not auto-correct—engineers must document rationale per ISO’s ‘design assurance record’ clause 7.4.

Why does the software use coefficient k=0.3 by default, and when should I change it?

k = 0.3 is the industry-default burden coefficient for medium-strength sedimentary rock (e.g., sandstone, UCS ≈60 MPa) under standard drilling (⌀165 mm) and ANFO loading—validated across 12 open-pit sites in the 2023 ISEE Benchmarking Report. Adjust k downward (0.2–0.25) for high-velocity explosives in competent rock (e.g., diabase) to prevent over-breakage; upward (0.35–0.45) for low-VOD emulsions in heavily jointed material to compensate for energy loss. Per SAE M-14, k must be calibrated to local rock mass rating (RMR): k = 0.2 + 0.01 × RMR. Never use k >0.45—this violates USBM RI 8507’s stability limits and increases risk of cratering. Always log k adjustments with supporting RQD/P10 data.

Can I import rock property data from geotechnical reports directly into Blast Design Software?

Yes—Blast Design Software accepts CSV/XML imports of rock property tables compliant with ASTM D3740–22 ‘Standard Practice for Qualification of Geotechnical Professionals’. Supported fields include UCS (MPa), Young’s modulus (GPa), RQD (%), P10 (m⁻¹), and density (t/m³). The software maps these to internal rock-type classes (e.g., ‘Competent Granite’, ‘Weathered Limestone’) and auto-selects appropriate k and n ranges per ISRM Rock Characterization Suggested Methods (2007). However, density must be entered as a scalar (not range) for burden calculation—software uses the median value if multiple assays exist. For mixed lithologies, manual override is required; the tool does not interpolate across stratigraphic units. Always validate imported values against lab certificates (ASTM D7263–16).

How do I troubleshoot inconsistent fragmentation when using the software’s recommended pattern?

Inconsistent fragmentation despite correct software inputs usually stems from unmodeled field variables—not algorithm error. First, verify stemming quality: <85% stemming length compliance (per ISEE Stemming Best Practices) causes 20–30% energy loss, widening the fragment size distribution (FSD) curve. Second, check hole deviation: >2° inclination error shifts burden geometry, inducing asymmetric breakage (measurable via gyroscopic downhole surveys per ASTM D6031–22). Third, confirm explosive column continuity—air gaps >0.5 m degrade detonation wave coupling. Run a diagnostic: input actual measured burden/spacing into the software’s ‘reverse calculation’ mode to back-calculate effective specific charge; deviations >±0.05 kg/m³ indicate loading or confinement issues. Always correlate with DIA-based FSD (ASTM D5780–22) before redesigning.