Drone Verification
Turqoa's Drone Verification module extends perimeter security beyond fixed cameras by dispatching autonomous or semi-autonomous drones in response to security events. Drones act as mobile verification assets, confirming or dismissing threats before human responders are dispatched.
Architecture
The drone verification stack sits between the Decision Engine and the physical fleet. When a security event triggers a drone response, the following pipeline executes:
Security Event → Decision Engine → Mission Planner → Fleet Controller → Drone → Evidence Capture → Operator Review
| Component | Responsibility |
|---|---|
| Mission Planner | Translates security events into flight plans with waypoints, altitude, and camera angles |
| Fleet Controller | Selects the optimal drone based on battery level, proximity, and current assignments |
| Telemetry Service | Streams real-time position, battery, signal strength, and sensor data |
| Evidence Pipeline | Captures, timestamps, and stores video and thermal imagery with chain-of-custody metadata |
| Operator Console | Provides live video feed, manual override controls, and mission status |
Mission Types
Turqoa supports four mission types, each optimized for a specific security scenario:
Alarm Verification
Dispatched automatically when a perimeter sensor or camera triggers an alarm. The drone flies directly to the alarm location, captures a 360-degree video sweep, and streams the feed to the operator for confirmation.
Patrol
Scheduled or on-demand flights along predefined routes. Patrol missions cover blind spots between fixed cameras and provide periodic visual confirmation of perimeter integrity.
Investigation
Operator-initiated missions where a drone is manually directed to a point of interest. The operator controls flight path and camera orientation in real time.
Perimeter Sweep
A full-perimeter flight triggered by elevated threat levels. The drone follows the facility boundary at configurable altitude and speed, recording continuous video.
Operator-in-the-Loop Controls
All autonomous drone actions require operator confirmation by default. The operator console provides:
- Live video feed with thermal overlay toggle
- Manual flight override to redirect a drone mid-mission
- Abort button with automatic return-to-base
- Evidence tagging to mark points of interest in the video stream
- Escalation controls to trigger a human response team
operator_controls:
auto_dispatch: true
require_confirmation:
alarm_verification: false
patrol: false
investigation: true
perimeter_sweep: true
abort_policy: return_to_base
max_flight_time_minutes: 25
low_battery_threshold_percent: 20
Integration with Security Events
Drone missions are triggered by the Decision Engine based on configurable rules. Events from any Turqoa module can initiate a drone response:
| Event Source | Example Trigger | Default Mission Type |
|---|---|---|
| Perimeter cameras | Motion detected in restricted zone | Alarm Verification |
| Gate OS | Unrecognized vehicle at gate | Investigation |
| Maritime module | Vessel approaching exclusion zone | Perimeter Sweep |
| Scheduled | Daily 06:00 and 18:00 | Patrol |
| Manual | Operator request | Investigation |
{
"trigger": {
"source": "perimeter_camera",
"event_type": "motion_detected",
"zone": "north_fence_sector_3",
"confidence": 0.87
},
"mission": {
"type": "alarm_verification",
"priority": "high",
"drone_selection": "nearest_available",
"evidence_capture": {
"video": true,
"thermal": true,
"resolution": "4K"
}
}
}
Fleet Requirements
| Requirement | Minimum | Recommended |
|---|---|---|
| Drones per site | 2 | 4+ |
| Charging stations | 1 per 2 drones | 1 per drone |
| Network connectivity | 4G LTE | 5G or dedicated RF link |
| Weather rating | IP43 | IP55 |
| Flight endurance | 20 minutes | 35+ minutes |
Next Steps
- Mission Profiles -- detailed configuration for each mission type
- Decision Engine Rules -- configure triggers for drone dispatch
- Command Center -- operator console for drone oversight