Add Mine Type (Underground/Surface) delineation per QGN35 Appendix 2

Resolved 💬 2 comments Opened Mar 2, 2026 by schnetler Closed Mar 5, 2026

Context

QGN35 (May 2025, Rev 3) explicitly distinguishes between Underground Coal Mines and Surface Coal Mines throughout the document:

  • Appendix 2 (p.17): Separate tables of Principal Hazards for Underground vs Surface mines
  • Step 3 examples (p.7): Separate "Underground example" and "Surface example" for the Control Identification Decision Tree
  • Step 5 (p.9): Notes "An underground and surface mine example" for CC Information Summary Sheet

Currently RiskSight has no mine type concept at all — no field on organizations, no filtering of Principal Hazards by mine type, and the CCM process flowchart doesn't show the distinction.

What Needs to Happen

1. Organization-level Mine Type field

  • Add mineType enum to Organization: UNDERGROUND, SURFACE, BOTH
  • Configurable in organization settings
  • Determines which Principal Hazards are relevant

2. Principal Hazard seed data split by mine type

Per QGN35 Appendix 2, additional PHs beyond CMSHR prescribed list:

Underground only:
| Principal Hazard | MUE |
|---|---|
| Gravity – (Structural Failure) | Structural Collapse |

Surface only:
| Principal Hazard | MUE |
|---|---|
| Emergency response failure | Common in all MUEs |
| Stored Fluids / Dams / Aquifers | Inrush / Flooding |
| Gravity – (Structural Failure) | Structural collapse |

Common (both): The prescribed CMSHR Principal Hazards apply to all coal mines.

3. Filter PH/MUE lists by mine type

  • When creating/viewing Principal Hazards, filter suggestions by organization's mine type
  • Show all PHs if mine type is BOTH
  • Tag each PH with applicableTo: UNDERGROUND | SURFACE | BOTH

4. Update CCM Process Flowchart

  • The HTML flowchart at docs/ccm-process-flowchart.html should show the Underground/Surface branching at Step 2 (Identify PH & MUEs)

5. Examples and context hints

  • When showing examples in the Control ID Decision Tree (Step 4), show mine-type-appropriate examples
  • Underground: roadway bords, ERZCs, drivage alignment
  • Surface: highwall excavation, dig plans, Mining Supervisors/OCEs

QGN35 References

  • Appendix 2: Potential Principal Hazards (p.17)
  • Section 5.2: Step 2 - Identify all Principal Hazards & MUEs (p.6)
  • Section 5.3: Step 3 - Identify Controls, Underground/Surface examples (p.7)
  • Section 5.5: Step 5 - Underground and surface mine CC Info Summary examples (p.9)

Acceptance Criteria

  • [ ] Organization has a mineType field (Underground/Surface/Both)
  • [ ] Principal Hazards tagged with applicable mine type
  • [ ] PH/MUE creation UI filters by organization mine type
  • [ ] Seed data includes QGN35 Appendix 2 PHs split by mine type
  • [ ] CCM flowchart reflects the delineation

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗