2.3 · Proof of concept · Command
Security Console Real Camera feeds by area, detections a person confirms, the security drone and the incidents.
Picture: Headless capture of poc/index.html?v=security&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale. Clip: Capture of poc/index.html?v=security&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.
Screen · Proof of concept · Command
Camera feeds by area, detections a person confirms, the security drone and the incidents.
Sources Interchange Twin Screens Plan
Kind Screen
Status not linked
Airport layer Screens: the POC story and the spines
Airport area not linked
System not linked
Sensor type not linked Open the screen · Open the detail
Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
Open this screen in the proof of concept
Narration line It shows a wall of feeds by area, each with a camera view and a scene rebuilt from detections.
Source: poc/bearings/security.json, beat "What it shows"
Group Command
Status as the app labels it Real
Basis The screen runs. Data: carefully crafted and curated test data for common use cases.
What the screen must do (5) Show a wall of feeds by area, each with a Camera and a Lidar-style view, labelled not SFB until real feeds connect (REQ-SFB-025) List video analytics detections, each confirmed by a person before dispatch (REQ-SFB-025, REQ-SFB-036) Launch a docked security drone through the release gate, its live view beside the fixed cameras (REQ-SFB-032) Detect and report a drone that does not belong, never act against it Open each event as an incident that replays in Flashback (REQ-SFB-032)
Requirement identifiers (3) REQ-SFB-025, REQ-SFB-032, REQ-SFB-036
Previous Local ControllersNext Nightly Round