Blasting is where a mine either stays on plan or starts paying compound interest on mistakes. A shot that’s slightly tight on timing, slightly off in burden, or slightly inconsistent in stemming rarely fails loudly. It shows up later as oversize at the crusher, higher dig times, poor wall control, more rework, increased powder factor, and a plant that keeps starving or surging. By the time the shift report explains it, the bench is already mined and the next pattern is already drilled.

Real-time KPIs make blasting more controllable by shrinking the loop between design, execution, and outcome. They help you spot drift during the shift, not after fragmentation and downstream performance have already moved on.

Blast Schedule Adherence by Pattern and Bench

• Why it Matters: Keeps the mine plan stable by ensuring shots fire when intended, preventing downstream bottlenecks and rehandling.
• What it Measures: Planned vs actual blast initiation time and completion status by pattern/bench.
• What Happens if Missed: Unplanned crusher starvation or surges, idle fleets, and constant replanning that erodes productivity.
• Formula: (Blasts Completed On Time / Blasts Planned) × 100.
• Indicator Type: Current, tracks live execution against the schedule because the gap matters immediately for coordination.
• Unit of Measure: Percentage (%) and minutes late/early.
• Ideal Visualization(s): KPI List View with status, KPI trend with real-time alerts, tables for drill-down by pattern.
• Frequency: Real-time updates during the shift.
• Data Required: Blast schedule timestamps, pattern IDs, fired/not fired status
• Pro Tip: Alert on “late beyond X minutes” differently than “early” since early firing can create safety and coordination risk.
• Red Flag: Repeated late blasts on the same bench or during the same shift handoff window.

Pattern Geometry Deviation

• Why it Matters: Burden, spacing, and drill accuracy are the foundations of predictable fragmentation and wall control.
• What it Measures: Deviation of as-drilled hole collar location, angle, depth, burden, and spacing vs design.
• What Happens if Missed: Fragmentation becomes inconsistent, toe problems increase, and dilution and wall damage become more likely.
• Formula: Mean absolute deviation and % out-of-tolerance holes (by attribute).
• Indicator Type: Leading, geometry drift predicts poor outcomes before explosives are loaded.
• Unit of Measure: Meters (m), degrees (°), and percentage (% out of tolerance).
• Ideal Visualization(s): KPI trend with real-time alerts, histogram for deviation distribution, Pareto for top rigs/crews/areas driving out-of-tolerance.
• Frequency: Per hole, aggregated continuously per pattern
• Data Required: Design geometry, as-drilled survey (collar, depth, angle), tolerance limits
• Pro Tip: Track “% out of tolerance” separately for collar position vs depth because they drive different failure modes.
• Red Flag: A widening deviation histogram over several patterns, even if averages still look acceptable.

Explosives Load Compliance

• Why it Matters: Consistent energy distribution is how you get consistent fragmentation and stable downstream performance.
• What it Measures: Actual charge mass and distribution per hole vs design, including decks and primers.
• What Happens if Missed: Uneven breakage, oversize, flyrock risk, and higher variance in muckpile diggability.
• Formula: (Holes Within Charge Tolerance / Total Loaded Holes) × 100.
• Indicator Type: Leading, charge mismatch is an early warning that the blast outcome will drift.
• Unit of Measure: Percentage (%) and kilograms per hole (kg/hole).
• Ideal Visualization(s): KPI trend with real-time alerts, bullet chart for compliance vs target, Pareto for non-compliance causes (decking, wet holes, substitutions)
• Frequency: Continuous during loading.
• Data Required: Design load plan, loading logs, measured charge weights, primer/deck info.
• Pro Tip: Alert on systematic bias (consistently light or heavy), not just single-hole exceptions.
• Red Flag: Increasing substitutions or “field fixes” without updated design control.

Timing Integrity

• Why it Matters: Timing is what controls heave, vibration, fragmentation distribution, and overall blast stability.
• What it Measures: Difference between planned vs actual initiation timing, including scatter by row and hole group.
• What Happens if Missed: Poor muckpile shape, higher vibration complaints, and unpredictable fragmentation.
• Formula: Mean timing error and standard deviation by row/hole group.
• Indicator Type: Leading, timing scatter predicts unstable outcomes before post-blast results appear.
• Unit of Measure: Milliseconds (ms).
• Ideal Visualization(s): KPI trend with real-time alerts, histogram for timing error distribution, tables for drill-down by detonator type/lot.
• Frequency: Per blast event, reviewed immediately after firing.
• Data Required: Planned delay plan, actual timing verification data (where available), detonator metadata.
• Pro Tip: Track scatter separately for surface delays vs in-hole delays. Root causes differ.
• Red Flag: Timing scatter spikes after switching detonator lots or crews.

Blast Vibration Compliance

• Why it Matters: Protects structures, slopes, and relationships with neighbors, and keeps you inside regulatory limits.
• What it Measures: Peak Particle Velocity (PPV) at monitoring points compared to allowable thresholds.
• What Happens if Missed: Regulatory action, damage claims, and constraints that reduce future blasting flexibility.
• Formula: Limit comparison (PPV vs threshold).
• Indicator Type: Current, compliance is assessed at the moment of the event, and immediate response may be required.
• Unit of Measure: mm/s (or in/s).
• Ideal Visualization(s): KPI trend with real-time alerts, bullet chart for event vs limit, tables by monitor location.
• Frequency: Per blast event.
• Data Required: Seismograph PPV readings, monitor locations, permitted limits, blast metadata.
• Pro Tip: Pair PPV with charge per delay and distance to improve predictability.
• Red Flag: Repeated near-limit events even when “compliant”. That is usually drift, not luck.

Air Overpressure Compliance

• Why it Matters: Airblast is a leading indicator of stemming issues, poor confinement, or unexpected venting.
• What it Measures: Air overpressure at monitoring points vs limits.
• What Happens if Missed: Complaints increase, flyrock risk rises, and you may face tighter operational constraints.
• Formula: Limit comparison (airblast vs threshold).
• Indicator Type: Current, measured as the blast happens. Exceedances are immediate incidents.
• Unit of Measure: dB(L) or kPa (depending on standard).
• Ideal Visualization(s): KPI trend with real-time alerts, bullet chart vs limit, Pareto for recurring exceedance locations or conditions.
• Frequency: Per blast event.
• Data Required: Airblast monitor readings, weather conditions, blast geometry and charge metadata.
• Pro Tip: Flag blasts with wind direction and speed that historically correlate with higher airblast at sensitive receptors.
• Red Flag: Overpressure spikes clustered around specific stemming materials, drill conditions, or crews.

Flyrock Risk Index

• Why it Matters: Flyrock is one of the fastest ways blasting becomes a safety and operational shutdown problem.
• What it Measures: A real-time composite risk score based on confinement, burden, charge, timing, and conditions (or direct incident/near-miss triggers).
• What Happens if Missed: Higher odds of exclusion-zone breaches, equipment damage, and serious safety events.
• Formula: N/A.
• Indicator Type: Leading, the point is to flag risk before firing.
• Unit of Measure: Index score.
• Ideal Visualization(s): KPI block with status, KPI trend with real-time alerts, tables showing drivers contributing to the score.
• Frequency: Updated as loading and conditions change.
• Data Required: Burden/spacing, hole condition (wet, voids), charge per hole, stemming, wind, exclusion-zone status.
• Pro Tip: Make the index explainable. Show the top 3 drivers so the team knows what to fix.
• Red Flag: Repeated “high risk” ratings that get waived instead of corrected.

Post-Blast Dig Rate vs Expected

• Why it Matters: This is the fastest operational feedback on fragmentation and muckpile diggability.
• What it Measures: Excavator or shovel dig rate immediately after the blast compared to expected baseline for that material and bench.
• What Happens if Missed: Poor breakage isn’t noticed until the shift loses hours and the downstream plant starts starving.
• Formula: Tonnes Loaded / Operating Hour (over a defined post-blast window).
• Indicator Type: Current, reflects near-term downstream impact and enables fast course correction on the next pattern.
• Unit of Measure: t/h (or bcm/h).
• Ideal Visualization(s): KPI trend with real-time alerts, bullet chart vs expected, Pareto when comparing benches/patterns/crews.
• Frequency: 1 to 5 minute updates.
• Data Required: Fleet payload and cycle data, blast-to-dig timestamp, bench/pattern mapping.
• Pro Tip: Normalize by material class or hardness category so you do not “blame the blast” for geology shifts.
• Red Flag: Dig rate drop paired with rising hang-ups or increased dozer assist.

Crusher Oversize Rate Attributed to Blast

• Why it Matters: Oversize is the expensive tax that shows up later if blasting drifts, and it hits throughput hard.
• What it Measures: Frequency and mass of oversize events (secondary breakage, grizzly blockages) linked to specific blast patterns.
• What Happens if Missed: Chronic constraints at the crusher, higher secondary breakage cost, and avoidable delays.
• Formula: Oversize Events per Blast, or Oversize Tonnes / Total Tonnes (by blast tag).
• Indicator Type: Lagging, confirms outcome after the blast, but still quickly enough to adjust the next designs.
• Unit of Measure: Events/shift and percentage (%) or tonnes (t).
• Ideal Visualization(s): Pareto by blast pattern/bench, KPI trend with real-time alerts, bar chart comparing patterns over time.
• Frequency: Real-time event capture with hourly rollups.
• Data Required: Crusher event logs, oversize tagging, blast-to-ore tracking (dispatch or stockpile tagging).
• Pro Tip: Pair oversize Pareto with pattern geometry deviation to separate “design drift” from “execution drift.”
• Red Flag: A small number of patterns dominate oversize contribution. That usually means a repeatable fix exists.

Fragmentation Size Distribution

• Why it Matters: You can be “on plan” for timing and loading and still produce fragmentation that punishes dig, haul, and crushing. Size distribution is the direct link between blast design and downstream energy.
• What it Measures: Post-blast fragmentation size distribution, often summarized as P80 (and optionally P20/P50) compared to expected by bench and material.
• What Happens if Missed: Higher shovel effort, more hang-ups, more crusher blockages, and hidden throughput loss that gets blamed on “operations” instead of root cause.
• Formula: Site-defined. Common summaries include P80, % oversize above a threshold, and size distribution variance by pattern.
• Indicator Type: Lagging, it confirms outcome after firing, but early enough to correct the next pattern design and loading practices.
• Unit of Measure: mm (P80) and percentage (% oversize).
• Ideal Visualization(s): Histogram for size distribution, KPI trend with real-time alerts for P80 vs target, Pareto for patterns driving the most oversize.
• Frequency: Per blast event, updated as image analysis or sampling becomes available (often within hours).
• Data Required: Fragmentation measurement source (image analysis, shovel camera, photogrammetry, or sampling), blast pattern ID, material classification.
• Pro Tip: Track size distribution variance, not only the mean. “Average OK” can hide a tail that creates most of the oversize pain.
• Red Flag: P80 trending worse on the same drill rig, crew, or geology domain even when loading compliance stays high.

Why Real-Time Visibility Matters

Blasting sits upstream of almost every cost and constraint in a mine. When you only find out a shot was “off” through delayed outcomes, your choices are limited and expensive: rehandle, secondary break, replan, or accept lost throughput.

Real-time KPIs change that dynamic. They let you detect execution drift while the pattern is still being drilled or loaded, and they give fast feedback on downstream impact while the next design can still be adjusted. That’s how blasting becomes a controlled process instead of a recurring surprise generator.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us