Highway Watch

4Active Nodes4 of 4 online

0Active Wildlife AlertsAll clear

3Wildlife Events Today

99.4%Corridor UptimeLast 30 days

Pilot corridor: plan view, drawn to scale

Gateway to cloud: online

Monitoring zone 40 to 90 m Warning zone 20 to 40 m Danger zone 0 to 20 m, incl. roadway Distances measured from the pavement edge. Select any node, sign or the gateway to inspect it.

Active track

Edge AI output

Roadside warning signs

Local control

Edge event log

Recorded on the corridor gateway, newest first

Pilot Corridor

Operating

Trans-Canada Highway

Pilot corridor P-01 · Central Newfoundland

Coverage: 0.5 km
Nodes: 4
Warning signs: 2 (eastbound, westbound)
Last wildlife detection: 18 minutes ago

Demonstration mode. The gateway loses LTE/5G while the roadside safety system keeps working.

Simulation options

Demo control

Playback speed

Safety buffer after crossing

Asset inspector

Select an asset

Wildlife events

Metadata received by the government cloud platform

Period Status Highest zone Species Node

Status	Event	Started (NDT/NST)	Node	Species	Highest zone	Signs	Duration	Cloud

No personal driver information collected.This record holds wildlife and equipment data only. No driver identity, licence plate, VIN, face, name, email or phone number.

Event summary

Animal path: Monitoring → Warning → Danger

MonitoringWarningDanger

Distance from the road over time

North above the road, south below

Event timeline

Full edge log

Warning signs

Thermal camera preview

Demonstration Wildlife Frame

Illustration only, drawn by the prototype. In the real system, wildlife processing happens on the node. A short clip is kept only when an event needs validation, and only event metadata and health data go to the government platform.

Sensor evidence

Mean confidence

Data path

Metadata sent to cloud

Wildlife events

Demo data

Crossing outcomes

Demo data

Direction of travel

Demo data

Time distribution

Demo data

Prototype demonstration data — not field results.

Average warning duration

Demo data

Hotspot map: detections along the 0.5 km corridor

Demo data

Prototype demonstration data — not field results.

Detections per month

Demo data

Prototype demonstration data — not field results.

What the data suggests

Demo data

Node health

Select a node to open its details

Node	Status	Sensors	Power

Gateway and warning signs

Read only

Work orders

Fictional demonstration records

Order	Asset	Issue	Priority	Status	Due

Service schedule

Asset	Last service	Next service

Fault demonstration

Demo control

Injecting a fault raises a work order and changes the status shown on the Nodes page and the Live Map. A failed sign is skipped by the local rule engine. Run a detection afterwards to see the effect.

PROTOTYPE DESIGN STATEMENT

Highway Watch watches wildlife, not people. This page shows what the system collects, what it does not need, and where data is processed.

Highway Watch collects

8 data types

Wildlife species estimateMoose, deer or unknown large animal, with a confidence score.
Detection timestampWhen the animal was first seen and when it changed zone.
Detection locationPosition along the corridor and which side of the road.
Movement directionToward, away from or parallel to the road, and north to south or south to north.
Estimated distanceMetres from the pavement edge.
Crossing eventWhether the animal entered the roadway, crossed, or turned back.
Node healthPower, temperature, sensors, network and storage status.
Short wildlife event imagery when required for validationOnly when staff need to confirm a detection. A brief clip of the animal, not used to identify drivers or vehicles.

Highway Watch does NOT require

7 items

Driver nameNever asked for, read or stored.
Licence plateNot read. Not stored.
Vehicle VINNot read. Not stored.
Driver faceNot captured or used.
EmailNo email address is needed.
Phone numberNo phone number is needed.
Personal accountNo sign-in or account for drivers or the public.

Privacy by design

Wildlife processing occurs at the roadside node where possible. Only wildlife-event metadata and system-health data are transmitted to the government platform.

1Roadside sensorsThermal camera, RGB camera and radar

→

2Roadside nodeDetects, classifies and tracks the animal here. Raw sensor data stays on the node.

→

3Corridor gatewayQueues and forwards metadata and health data

→metadata only

4Government platformWildlife events and system health

Prototype assumption Validation clips are short, limited to the animal, and kept only when an event needs checking. Retention and access rules are set by the department and are not modelled here.

Example: wildlife event message

Demo data

Example: node health message

Demo data

Fields that never appear in any message

driver_namelicence_platevinfaceemailphoneaccount_id

How the safety system works

How the corridor works

The dashed green boundary keeps working with no internet

Roadside: local, always on

SensorsThermal camera, RGB camera and radar on each node

→

Node edge AIDetect, classify, track, place in zone, decide

→

Warning signsFlashing amber beacons for approaching drivers, commanded directly over the node mesh

→

Government cloudWildlife event metadata and system health only

Node to nodeNodes share hazard events with neighbours over a local mesh, so a detection at one node can raise signs controlled by another.

Corridor gatewayCollects metadata and telemetry from all nodes. If the uplink drops, it stores events and forwards them, in order, when the link returns.

Zone rules (edge rule engine)

Configurable by operations

Zone	Distance from pavement	Local action
Monitoring	40 to 90 m	Track and classify. Signs stay off unless the animal is heading for the road and could reach it within 5 s.
Warning	20 to 40 m	Approaching: prepare the warning and arm both signs. Moving parallel or stationary: flash both signs.
Danger	0 to 20 m and on the roadway	Flash both approach signs (MOOSE DETECTED AHEAD, SLOW DOWN), notify the dashboard. Faster flash if the animal is on the road.
Clearing	Left the danger zone	Signs stay on for a configurable safety buffer after the animal has crossed or left the danger zone, then deactivate automatically.

If the cloud is unreachable

Detection, zone logic and sign activation run on the nodes. Nothing waits on the cloud.
The gateway queues event metadata and health telemetry with original timestamps.
When the link returns, queued events appear on the dashboard marked as delayed.
Try it: press Simulate Cellular Outage on the Live Map, then run a moose detection.