- Documentation
- /
- Ggcm
- /
- Quick Reference
Quick Reference
Menu map, demo-data codes and statuses
Menu Map
| Group | Models |
|---|---|
| Inspections & Observations | Inspection, Inspection Response, Ground Observation, Inspection Template, Inspection Item |
| Monitoring & Thresholds | Monitoring Instrument, Instrument Channel, Monitoring Current, Monitoring Reading, Threshold Set, Threshold Rule |
| TARP & Restrictions | TARP Activation, TARP Action Execution, Operational Restriction, TARP Plan, TARP Action |
| Hazards & Controls | Geotechnical Hazard, Hazard Control |
| Events, Work & Review | Geotechnical Event, Work Request, Work Verification, Technical Review, Corrective Action, Management of Change |
| Ground Support | Ground Support Design, Ground Support Installation, Support Inspection |
| Sites, Areas & Excavations | Site, Area, Excavation, Geotechnical Domain, Excavation Domain |
| Plans & Design Basis | Ground Control Plan, Design Basis |
| People & Organisations | Person, Organisation |
| Documents & Evidence | Document, Evidence Attachment |
Key Codes in the Demo Data
The demo runs one site — Demonstration Mine (DEMO01), open pit, Queensland — through the pack's north-wall escalation scenario, with a quieter second excavation carrying the healthy, in-control case alongside it.
| Code | What it is |
|---|---|
DEMO01 |
The site. Areas PIT-A → NORTH-WALL, RAMP-3 |
NW-HIGHWALL-01 |
North Wall Highwall — the excavation at the centre of the escalation |
NW-BENCH-420 |
North Wall Bench RL420 — the quiet, healthy path (routine inspection, closed rockfall) |
RAMP3-CUT |
Ramp 3 Cut — the exposure area that gets excluded |
DOM-FAULT-N1 |
North Wall Fault Zone (structural) — the domain the planar hazard sits in |
GEO-HAZ-00001 |
The escalating hazard. North highwall planar failure on fault — POSSIBLE × MAJOR, inherent HIGH, residual MODERATE |
GEO-HAZ-00002 |
Bench crest rockfall and raveling — LIKELY × MODERATE |
GCP-DEMO-001-A / -B |
Ground-control plan Rev A (SUPERSEDED) and Rev B (ACTIVE, adds the radar-driven TARP) |
GEO-DES-00013 / -00014 |
Design basis 2024 (SUPERSEDED) and 2025 (ACTIVE) |
RAD-NW-01 / MOVEMENT_RATE |
Slope radar movement-rate channel — the one the thresholds watch |
PRISM-NW-101 / TOTAL_MOVEMENT |
Prism total displacement — the independent confirmation |
PIEZ-NW-05 / WATER_LEVEL |
Piezometer — carries the SUSPECT reading that cannot lower a level |
NW-WALL-THRESH v1.0 |
Threshold set: LEVEL_1 ≥ 2.0, LEVEL_2 ≥ 5.0, LEVEL_3 ≥ 10.0 mm/h |
TARP-NW-WALL |
North Wall Ground Movement TARP — 5 actions across LEVEL_1 → LEVEL_3 |
GEO-TARP-2026-00003 |
The activation. Triggered by the 2.4 mm/h radar reading + the HIGH crack observation; activated LEVEL_1, escalated to current LEVEL_2; still ACTIVE, not de-escalated |
GEO-OBS-2026-000501 |
The HIGH highwall crest tension crack (35 mm, opening) that escalated |
GEO-RES-2026-00003 |
The LEVEL_2 exclusion zone on the ramp exposure area — ACTIVE, release criteria set, not yet released |
GEO-WR-2026-00003 |
Scale + drainage work request — status VERIFIED, release recommended |
GEO-REV-2026-00003 |
TARP-review of the activation; requested the supplementary prism survey |
GEO-ACT-2026-00011 |
Corrective action — add CH1420 drainage to the re-entry inspection (COMPLETED, verified) |
GEO-MOC-2026-0004 |
Management of change — add a piezometric trigger to the TARP (status REVIEW) |
GEO-EVT-2026-00007 |
The closed rockfall on bench RL420 — caught by the catch bench, 0 exposed, CLOSED |
The Escalation, Step by Step
- 38.5 mm overnight rain → post-rainfall wall re-entry inspection
GEO-INSP-2026-000101on the highwall. - Inspection fails: new 35 mm tension crack, access DETERIORATING,
safe_for_access = false,immediate_restriction_required = true. - Radar movement rate climbs 0.4 → 1.2 → 2.4 mm/h, crossing LEVEL_1 for its persistence.
GEO-TARP-2026-00003created (LEVEL_1), triggered by the reading and the HIGH crack observation; preservesNW-WALL-THRESH v1.0 / LEVEL_1.- Movement continues → escalates to LEVEL_2; ramp exposure area put under
the exclusion
GEO-RES-2026-00003. - TARP actions executed and cross-verified; technical review requests a supplementary prism survey.
- Scaling + drainage work
GEO-WR-2026-00003→ drains cleared, toe bund reinstated at CH1420 → work VERIFIED. - Radar returns to 0.5 mm/h by 22 July — but the TARP stays LEVEL_2; de-escalation waits on the recorded competent-person approval.
Status Vocabularies (the important ones)
Record lifecycle (most models): DRAFT → REVIEW → APPROVED → ACTIVE, then
SUSPENDED · COMPLETED · CLOSED · CANCELLED · SUPERSEDED · ARCHIVED
Restriction status: PROPOSED · ACTIVE · SUSPENDED · RELEASE_PENDING ·
RELEASED · EXPIRED · SUPERSEDED
Work status: REQUESTED · APPROVED · PLANNED · READY · IN_PROGRESS ·
ON_HOLD · COMPLETE · VERIFIED · CLOSED · CANCELLED
Reading quality: VALID · ESTIMATED · SUSPECT · REJECTED · MISSING — only
VALID/ESTIMATED may update the live picture; SUSPECT/REJECTED can never
lower a TARP level
TARP level: NORMAL · LEVEL_1 · LEVEL_2 · LEVEL_3 · EMERGENCY
Observation / inspection severity: INFORMATION · NORMAL · MONITOR · ALERT ·
HIGH · CRITICAL
Risk: LOW · MODERATE · HIGH · EXTREME;
Likelihood: RARE · UNLIKELY · POSSIBLE · LIKELY · ALMOST_CERTAIN;
Consequence: INSIGNIFICANT · MINOR · MODERATE · MAJOR · CATASTROPHIC
Verification outcome: PASS · PASS_WITH_ACTION · FAIL · NOT_VERIFIED
Support condition: GOOD · SERVICEABLE · DAMAGED · FAILED · CORRODED ·
OVERLOADED · MISSING · UNKNOWN
Rules of Thumb
- A radar reading that breaches a threshold preserves the threshold version on the activation — the number alone is never enough.
- A TARP never de-escalates because a later reading is quiet. It waits on a recorded competent-person approval. The demo shows exactly this.
- A
SUSPECTorREJECTEDreading can flag a problem but can never lower a level or update the liveMonitoringCurrent. - Completed work does not release an exclusion. Verification only
recommends release; the restriction's criteria and an authorised approval
still gate the
RELEASEDstatus. - Corrections to approved records are superseding rows with a reason, not edits — see the plan and design-basis revisions.
- Release, verification and change approval are done by a different person from the one who requested or owns the work — the columns are separate on purpose.