AirfieldpathOrlando Sanford International

2.27 · Proof of concept · Drones

Drone Operations Simulated

Drones that could help inspect the airfield, and the airspace rules they must meet. Not in the RFP's scope today.

Picture: Headless capture of poc/index.html?v=droneops&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Clip: Capture of poc/index.html?v=droneops&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.

Screen · Proof of concept · Drones

Drone Operations Simulated

Drones that could help inspect the airfield, and the airspace rules they must meet. Not in the RFP's scope today.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met, target
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

Drone Operations, a capture of the screen
Capture of the screen: Drone Operations. Dark and light modes.

Narration line

It shows every drone mission over the airfield, each serving a named Part 139 duty (pavement, lighting, FOD, wildlife), with its state from draft to flown.

Source: poc/bearings/droneops.json, beat "What it shows"

Group
Drones
Status as the app labels it
Simulated
Basis
The drone flights are simulated. The screen runs. Data: carefully crafted and curated test data for common use cases.
What the screen must do (5)
  • Show every drone mission over the airfield, each serving a named Part 139 duty (pavement, lighting, FOD, wildlife), with its state from draft to flown (REQ-FUNC-076)
  • Show the airport's airspace class and tower hours from the FAA record, and the authorization each flight needs before release (REQ-FUNC-077, REQ-COMP-004)
  • Show each aircraft's eligibility: maker domicile, Florida security tier, FCC Covered List status and Remote ID (REQ-FUNC-078)
  • Show the response to an unauthorized drone as the emergency plan sets it, with detection coordinated with the FAA and mitigation left to federal agencies (REQ-FUNC-079)
  • Label the drone layer envisioned: drones are beyond the RFP's known scope (REQ-FUNC-089)
Requirements matrix rows that name this screen (3)
RowRFP sectionRequirementStatus
M-054B i; RFP 10.4.1Experience implementing digital twin, asset visualization or integrated OT platformspartly met
M-069B iiiFuture roadmap for expansionpartly met
M-144Beyond the RFPDrone inspections of the airfieldtarget