Calculator D3

ROC Situational Awareness Dashboard Design Principles

A ROC Situational Awareness Dashboard is like a mission control center’s 'live dashboard' — it shows real-time, reliable, and actionable information about all remote mine sites in one place so operators can see what’s happening, spot problems early, and act decisively.

Typical Scale
Monitors 3–12 mine sites, 15,000–250,000 telemetry points
Certification Standards
IEC 62443-3-3 (SL2), ISO/IEC 27001, ISA-101.01
Mean Time to SA Recovery
Target <45 sec post-alarm (per Rio Tinto & BHP ROC SLAs)

⚠️ Why It Matters

1
Inconsistent data latency across sites
2
Delayed detection of conveyor belt stoppage
3
Unplanned mill feed interruption
4
Ore grade dilution due to blending errors
5
Reduced recovery and increased unit operating cost

📘 Definition

The ROC Situational Awareness Dashboard is a human-centered, fault-tolerant software system integrating telemetry, alarm management, geospatial context, and workflow-aware visualization to support cognitive task performance by remote operators managing distributed mining assets. It conforms to ISO 9241-210 (human-centred design) and IEC 62591 (WirelessHART) interoperability principles, with architecture aligned to NIST SP 800-82 for industrial control system security. Its core function is to reduce situation awareness degradation across time, space, and operational abstraction layers.

🎨 Concept Diagram

Site A — PilbaraOKAlertSite B — NewmanOKActiveROCCentral Dashboard

AI-generated illustration for visual understanding

💡 Engineering Insight

Dashboards don’t fail because of missing features — they fail because they violate the operator’s mental model of the system. The most effective ROC dashboards are built backward: start with the operator’s decision tree for a Tier-1 failure (e.g., ‘mill trip’), then instrument only the data needed to answer each branching question — nothing more, nothing less. Every extra widget erodes SA faster than missing data.

📖 Detailed Explanation

At its core, situational awareness (SA) in a Remote Operations Centre means operators know *what* is happening, *why* it’s happening, and *what will happen next* — across dozens of geographically dispersed sites. This requires more than just data aggregation: it demands intentional reduction of cognitive noise, preservation of causal linkages, and alignment with procedural memory.

Advanced implementation recognizes that SA is not static but *dynamic and hierarchical*. Operators shift attention between strategic (e.g., fleet utilization across 4 sites), tactical (e.g., current crusher circuit status), and micro-tactical (e.g., bearing temperature trend on Pump-7B) layers — and the dashboard must support seamless, low-friction transitions. This requires layered visualization (e.g., top-level heatmaps → drill-down to time-series + event correlation graphs) and adaptive information density.

The highest maturity dashboards embed *predictive SA*: they don’t just show current state — they project likely future states using lightweight physics-informed models (e.g., ore flow continuity prediction from bin level + feeder speed + moisture sensor fusion). These projections are rendered with calibrated uncertainty bounds (per ISO/IEC 14763-3), enabling operators to distinguish between probable outcomes and outliers requiring intervention — turning passive monitoring into anticipatory control.

🔄 Engineering Workflow

Step 1
Step 1: Define SA Criticality Matrix per asset class (e.g., SAG mill = Tier-1, dewatering pump = Tier-2)
Step 2
Step 2: Map telemetry sources to SA layers (per Endsley’s 3-level model: perception → comprehension → projection)
Step 3
Step 3: Apply alarm rationalization per ISA-18.2 and configure dynamic suppression logic
Step 4
Step 4: Design context-aware visualization using ISO/IEC 2382-23 cognitive ergonomics rules
Step 5
Step 5: Validate with ROC operators using scenario-based SA probes (SAGAT or SPAM)
Step 6
Step 6: Deploy with dual-path redundancy (primary SCADA + backup edge-processed telemetry)
Step 7
Step 7: Monitor WAI & Context Fidelity monthly; recalibrate every 6 months or after major process change

📋 Decision Guide

Rock/Field Condition Recommended Design Action
Multi-site alarm flood (>0.3 alarms/100 tags/min) + latency >12 sec Activate ‘SA Preservation Mode’: suppress non-critical alarms, overlay root-cause path, lock map view to affected asset cluster
Geospatial context loss (e.g., GPS drift >15 m on haul truck fleet) Switch to fused INS/GNSS mode; render uncertainty ellipses; disable auto-zoom; flag affected telemetry with amber border
Critical process deviation (e.g., crusher throughput <70% nominal for >90 sec) + no alarm raised Trigger silent diagnostic overlay: show upstream/downstream KPIs, recent maintenance logs, and last calibration timestamp

📊 Key Properties & Parameters

Data Latency

2–15 seconds (telemetry), ≤60 seconds (batch analytics)

Time delay between physical event occurrence at site and its representation on the dashboard

⚡ Engineering Impact:

Latency >8 sec degrades operator response time to critical alarms by ≥37% (per NASA HRP-2022 studies)

Alarm Density

0.05–0.3 alarms/100 tags/min

Number of active high-priority alarms per 100 monitored tags per minute

⚡ Engineering Impact:

Alarm density >0.25/100 tags/min increases operator cognitive load beyond validated SA thresholds (ISA-18.2 Annex B)

Context Fidelity

65–92% (measured via operator recall accuracy in controlled SA trials)

Degree to which dashboard visualizations preserve spatial, temporal, and causal relationships among assets and events

⚡ Engineering Impact:

Fidelity <75% correlates with 4.3× higher misdiagnosis rate of cascading failures (Rio Tinto ROC Validation Report, 2023)

Workflow Alignment Index (WAI)

0.68–0.91

Normalized score (0–1) quantifying how closely dashboard layout matches actual operator task sequence per ISA-101.01

⚡ Engineering Impact:

WAI <0.75 increases average task completion time by 22–38% and error rate by 2.1× (BHP Pilbara ROC Usability Benchmark)

📐 Key Formulas

Situation Awareness Index (SAI)

SAI = (Perception Score × 0.3) + (Comprehension Score × 0.4) + (Projection Score × 0.3)

Composite metric derived from validated SA probe (SAGAT) scoring across three Endsley levels

Variables:
Symbol Name Unit Description
Perception Score Perception Score Score reflecting accuracy of environmental element detection (Endsley Level 1)
Comprehension Score Comprehension Score Score reflecting understanding of current situation and relationships among elements (Endsley Level 2)
Projection Score Projection Score Score reflecting ability to anticipate future states (Endsley Level 3)
Typical Ranges:
ROC baseline
0.65–0.75
High-maturity ROC
0.82–0.93
⚠️ SAI <0.70 triggers mandatory dashboard redesign review

Alarm Load Ratio (ALR)

ALR = (Active High-Priority Alarms / Total Monitored Tags) × 100

Quantifies cognitive pressure from concurrent alarms per tag population

Variables:
Symbol Name Unit Description
Active High-Priority Alarms Active High-Priority Alarms count Number of high-priority alarms currently active
Total Monitored Tags Total Monitored Tags count Total number of process tags under alarm monitoring
Typical Ranges:
Normal operations
0.02–0.15%
Emergency response
0.20–0.45%
⚠️ ALR >0.35% requires immediate alarm suppression protocol activation

🏭 Engineering Example

Roy Hill Iron Ore – Central ROC (Pilbara, WA)

Banded Iron Formation (BIF)
Data Latency
3.2 sec (average)
Alarm Density
0.14 alarms/100 tags/min
Context Fidelity
87%
SA Probe Accuracy
91% (SAGAT score)
Workflow Alignment Index
0.89

🏗️ Applications

  • Real-time fleet dispatch coordination across 5+ open-pit mines
  • Predictive shutdown sequencing during power grid instability
  • Cross-site water balance optimization during cyclone season

📋 Real Project Case

Iron Ore Mine ROC Consolidation in Western Australia

Rio Tinto’s Pilbara ROC consolidation across 8 open pit sites

Challenge: Fragmented legacy SCADA systems with inconsistent alarm protocols and manual handovers
Iron Ore Mine ROC Consolidation Western Australia • IIoT Platform Integration Legacy SCADA (Fragmented) A B C • Inconsistent alarm protocols • Manual handovers (avg 22 min) Unified IIoT Platform OPC UA Standardized Interfaces ISA-18.2 Alarm Management ROC Output Alarm Flood ↓ 82% (Pre−Post ROC) Handover Time ↓ 18 min (per shift)
Read full case study →

🎨 Technical Diagrams

Layer 1: Perception\n(Sensors, raw telemetry)→ Filtering &\nNormalizationLayer 2: Comprehension\n(Alarms, KPIs, context)Layer 3: Projection\n(Trends, forecasts, scenarios)SA Output
Crusher-3A StatusConveyor-B7 SpeedMill Feed Grade

📚 References

[1]
[3]
Human Factors in Control Room Design: A Practical Guide — UK Health and Safety Executive (HSE)
[4]
Endsley’s Situation Awareness Model — MITRE Corporation (cited in NASA HRP-2022)