Mining App Development

Mining operations teams building management platforms need engineering teams who understand the specific data architecture of mine environments: heavy mobile equipment telemetry, gas monitoring pipelines, blast clearance state machines, shift and crew management, and the safety audit trails that regulators require. Scrums.com provides dedicated software engineering teams for mining app development, deploying production-ready systems with append-only production event ledgers, configurable safety alert engines, GPS-tracked equipment pipelines, and the analytics infrastructure that measures tonnes moved, equipment utilisation, and production versus plan.

Mine Site Operations, Shift Management, and Production Tracking

The mine site hierarchy (site, pit or level, stope or drive, panel) is stored in mine_sites, each node carrying type, status, and an access_restrictions config governing which roles may enter. Shift plans record shift_type (DAY | NIGHT | AFTERNOON), crew_ids, work_centre_ids, planned_start, planned_end, and production_target_tonnes. Shift events (SHIFT_START, PRE_SHIFT_SAFETY_COMPLETE, SHIFT_HAND_OVER, SHIFT_END) append to shift_events with operator_id and timestamp. Pre-shift safety checks write to pre_shift_safety_checks (check_type, result: PASS | FAIL | OVERRIDE); OVERRIDE requires override_justification and override_approver_id before the shift can advance to PRE_SHIFT_SAFETY_COMPLETE: the approval is enforced at the state transition level. Production records are append-only: one row per haul cycle (equipment_id, operator_id, load_location, dump_location, material_type, estimated_tonnes, recorded_at). A shift_production_summary materialised view computes total tonnes per shift per material type from production_records: always recomputable, never a mutable counter. A production_vs_plan materialised view compares shift production against planned target_tonnes without touching either source table.

Equipment Management, GPS Telemetry, and Blast Clearance

The asset registry holds every piece of equipment with type (HAUL_TRUCK | EXCAVATOR | DRILL_RIG | LOADER | DOZER | GRADER | EXPLOSIVE_TRANSPORT), capacity_tonnes, and max_payload_kg. Status follows OPERATIONAL / STANDBY / BREAKDOWN / MAINTENANCE / DECOMMISSIONED with each transition appended to asset_status_events. GPS positions from on-board devices write to equipment_position_events (equipment_id, latitude, longitude, speed_kmh, heading, recorded_at) stored in TimescaleDB hypertables, with idempotency via ON CONFLICT DO NOTHING on (equipment_id, recorded_at). Geo-zones are stored as polygons in geo_zones (zone_type: PIT | BLAST_EXCLUSION | RESTRICTED | DUMP_POINT | PROCESSING_PLANT); geo_fence_events fire when equipment crosses a zone boundary, computed via PostGIS containment queries. The blast clearance state machine (PLANNED / CHARGED / CLEARANCE_IN_PROGRESS / CLEARED / FIRED / POST_BLAST_INSPECTION / COMPLETE) is enforced with immutable transition rows in blast_event_transitions. A blast cannot advance to FIRED unless a database-layer check confirms no equipment_position_events place any asset inside the blast_exclusion_zone polygon within the preceding configurable window: a check that runs within the state transition transaction and cannot be bypassed at the application layer. Post-blast inspection records dud_count; duds write dud_events (location, detonator_id) before COMPLETE status is permitted.

Mining apps like these are built and delivered by dedicated engineering teams through our mobile app development service.

Gas Monitoring, Ventilation Control, and Safety Compliance

Gas readings from underground sensors write to a TimescaleDB hypertable with ON CONFLICT DO NOTHING on (sensor_id, gas_type, reading_timestamp): retransmissions are discarded at ingest. Gas types monitored include CO, H2S, CH4, O2, NO2, and SO2 in ppm. Alert rules in gas_alert_rules (sensor_id, gas_type, threshold_ppm, alert_level: ADVISORY | WARNING | DANGER | EVACUATE, cooldown_seconds) are config-driven and keyed per sensor; threshold changes write new config rows and take effect at next evaluation. Alert events follow a state machine (TRIGGERED / ACKNOWLEDGED / RESOLVED | AUTO_RESOLVED | ESCALATED); an EVACUATE-level alert writes to evacuation_events and automatically blocks any blast from advancing to FIRED until the zone is cleared and an authorised safety officer lifts the lock. Ventilation commands follow a state machine (NORMAL | BOOST | PURGE | LOCKOUT); LOCKOUT is triggered automatically when gas concentration exceeds DANGER threshold and cannot be manually released until gas_readings return to SAFE levels and an authorised officer writes an approval event. All safety-critical state transitions (gas alert escalation, ventilation LOCKOUT, blast clearance override) write to safety_audit_events with user_id, justification, and an HMAC chain for tamper detection. Regulatory inspections (GAS_MONITORING | BLAST_CERTIFICATION | FIRE_SUPPRESSION | EMERGENCY_EXITS) are never deleted; DEFERRED status requires a rescheduled_at before the transition is permitted.

Geological Data, Ore Grade Management, and Mining Analytics

Drill holes carry location as a GEOMETRY point, total_depth_m, azimuth, dip, and purpose (EXPLORATION | GRADE_CONTROL | GEOTECHNICAL | DEWATERING). Assay results are immutable once received from the laboratory: each row records drill_hole_id, from_depth_m, to_depth_m, element (AU | CU | FE | NI | ZN), grade_ppm_or_pct, and sample_id; resamples write new rows referencing the original sample_id rather than overwriting. Ore blocks carry estimated_grade, confidence_level, and classification (MEASURED | INDICATED | INFERRED) with polygon GEOMETRY; classification upgrades write new rows, never mutating the historical block record. Grade control dispatch decisions (MILL | ROM_PAD | WASTE | LOW_GRADE_STOCKPILE) are immutable once recorded; corrections write grade_control_corrections rows referencing the original dispatch_id. Analytics materialised views include production_tonnes_by_shift_by_material, equipment_utilisation_by_asset_by_shift, tonnes_moved_vs_plan_by_day, average_grade_by_dispatch_destination, and gas_exceedance_count_by_zone_by_shift: all recomputable from append-only source events without touching operational records.