Drone surveillance & training

Sentinel SkyWatch integrations

Connections belong to this product’s deployment. Each source, device and external service needs the appropriate permission and commissioning.

Architecture and information flow

Component	Purpose
Aircraft and controller	The operator flies using the manufacturer’s own equipment.
Video connection	A supported capture device or receiver exposes the feed as a camera input.
Sentinel SkyWatch workspace	The local browser/application organise cameras, aircraft, rules and observations.
Data and training	Configured local storage holds records/media; the separate practice lab simulates flying.

Connection	Setup	Validation / limitation
Controller video output	Compatible receiver or capture device exposing a supported input.	This is video review, not aircraft command/control integration.
Visible / thermal camera	Appropriate hardware and camera type selection.	Thermal interpretation requires real thermal input and calibration.
Site alerts	Configured categories, thresholds and notification permissions.	Test sound and desktop notification delivery.
Maps and place search	Configured external imagery and search providers.	These need their network services; the practice city is procedural.
Practice controllers	Compatible browser gamepad, on-screen sticks or keyboard.	Test mappings, dead zones and disconnect behavior.

The intended aircraft input opens with usable quality and latency.
Site rules create expected reviewed alerts on representative footage.
True thermal and pseudo-thermal views remain correctly identified.
Status changes and captures appear in reports/storage.
Unauthorised roles cannot change protected configuration.
Practice landing, return-home and controller inputs pass the intended exercises.
Backup, HTTPS and ledger checks succeed.

Discuss Sentinel SkyWatch with your team and agree the relevant scope, input sources, deployment, training and support.