Why it matters
Without it, unexpected storms can cause lift stoppages, delayed openings, and gaps in staff and guest safety during severe weather events.
From design to safety
Design
Weather design inputs for layouts
Reads historical weather data, lightning climatology, and terrain-influenced storm behaviour to determine lightning protection, shelter placement, and early-warning thresholds. Incorporates terrain shading, wind shear profiles, and subalpine microclimates to map protected routes and emergency egress.
- Lightning detector sensor array
- Storm cell detection radar interface
- Summit shelters and protection plan
Build
Systems wired for sensing and alerts
Specs and installs integration points for detection sensors, data feeds, automatic closures, and staff alert channels, with commissioning tests and safety verifications. Includes cable routing, redundant power, and gateway security.
- Lightning detector sensor array
- Storm cell detection radar interface
- Lift closure relay
- Emergency communications console
Operation
Real-time weather-informed operations
Reads live strike data, storm polygons, wind shifts, and wet-bulb cues to decide lift closures, shelter activations, and staff notification pacing. Establishes recovery timelines and post-event debriefs for safety logs.
- Lightning detector sensor array
- Storm cell detection radar interface
- Lift closure relay
- Staff alert transmitter network
Maintenance
Sensor health and data integrity checks
Monitors sensor response times, data latency, analog-digital conversions, and alarm routing accuracy to prevent false negatives or positives. Schedules field calibration, documentation updates, and test traverses.
- Lightning detector sensor array
- Storm cell detection radar interface
- Emergency communications console
Safety
Guarded procedures and approvals
Alerts trigger controlled evacuations, shelter staffing, and regulator-compliant documentation; final sign-off by mountain-safety lead and ski patrol coordination. Maintains audit trails for compliance and incident reviews.
- Summit shelters and protection plan
- Lift closure relay
- Staff alert transmitter network
Part by part
- 1
Lightning detector sensor array
- Watch for
- drift in sensitivity, spurious readings from interference, degraded calibration
- AI action
- adjust detection thresholds and route alerts to control systems
- 2
Storm cell detection radar interface
- Watch for
- data latency, calibration drift, missing storm cell polygons
- AI action
- update storm ETA polygons and escalation ring to operations
- 3
Lift closure relay
- Watch for
- unverified closure commands, actuator jam, mis-timed opens/closes
- AI action
- execute validated closure sequence and logging
- 4
Summit shelters and protection plan
- Watch for
- shelter occupancy limits, door failure, ventilation issues
- AI action
- allocate shelter staffing and trigger crowd-control alerts
- 5
Staff alert transmitter network
- Watch for
- communication blackout, device battery failure, misrouted alerts
- AI action
- re-route alerts, switch to backup channels, notify supervisors
- 6
Emergency communications console
- Watch for
- console downtime, cross-channel messaging gaps, archive failures
- AI action
- switch to redundant channel, confirm message delivery to all devices
Worked example
Catching a lightning-driven closure before a charter halt
Illustrative scenario with sample data.
An incoming storm cell forms rapidly near the summit, with elevated wind shear and lightning strikes predicted to cross the ridgeline within minutes, requiring preemptive action to protect guests and staff.
Signal in
sensor_id: LD-RA-01, time: 14:32, intensity: high, polygon: SummitWest, wind: 28km/h, wetbulb: 1.0°C, shelter_status: ready, staff_alert: pending, patrol_status: on-scene
System out
closure_order: LIFT-101, LIFT-102; shelter_activation: SummitSouth Shelter; alert: all_staff_high_priority; log_id: LOG-45321; escalation: regional supervisor notified
Human sign-off: Ropeway Technical Manager signs off on the closure and shelter activation based on threshold confidence, wind feel, and staff readiness; ski patrol confirms evac routes before clearing for re-entry.
How to roll it out
Phase 1
Weeks 1 to 4: Baseline
Install core sensors, establish data feeds, and test automated alerts in controlled weather windows.
Phase 2
Weeks 5 to 8: Field Validation
Validate detection accuracy, closure timing, and staff notification flows during real storms.
Phase 3
Weeks 9 to 12: Full Ops
Operate live with monitoring, refine thresholds, and lock final procedures in the mountain-safety playbook.
Where people stay in charge
- All decisions affecting lift operations must remain with the chair of mountain safety or an appointed accredited supervisor, to ensure regulatory compliance and guest safety.
- All automated closures must require a human-in-the-loop approval when wind or lightning readings are near regulatory thresholds to prevent undesired outages.
- All data handling and alerting must comply with privacy, safety, and regulator guidelines, with auditable logs for safety audits.
Questions owners and crews ask
What triggers an automated lift closure in a severe weather scenario?
The system triggers closure based on validated thresholds from lightning detectors and storm cell polygons, with human confirmation for final execution by the Lift Operations Manager.
How are staff informed during a lightning event?
Staff receive real-time alerts via the staff alert network, with redundancy to backup channels and clear role assignments from the mountain-safety lead.
What happens if a sensor goes offline during a storm?
The system reroutes alerts through backup sensors and communications, and on-site staff follow manual procedures while a maintenance trigger schedules diagnostics.
How is safety documented and audited after a severe weather event?
Event data, sensor readings, and decision logs are archived in the safety records system and reviewed by the ski patrol director and regulator liaison.