AirfieldpathOrlando Sanford International

2.28 · Proof of concept · Drones

Inspection Mission Simulated

How a drone inspection is planned from an asset and held until it is safe to fly.

Picture: Headless capture of poc/index.html?v=mission&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Clip: Excerpt of poc/flybys/drone-grid.mp4, 2.0 to 6.0 seconds. A drawing of the process: A drone survey grid, findings, evidence. No sound.

Screen · Proof of concept · Drones

Inspection Mission Simulated

How a drone inspection is planned from an asset and held until it is safe to fly.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
target
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
RFP rowsM-144

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

Inspection Mission, a capture of the screen
Capture of the screen: Inspection Mission. Dark and light modes.

Narration line

It lets you plan a mission from a twin asset (a pavement section, a lighting circuit, an apron), its path drawn over the asset.

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

Flyby: A drone survey grid, findings, evidence. A drawing of the process, not the product. No sound.
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)
  • Plan a mission from a twin asset (a pavement section, a lighting circuit, an apron), its path drawn over the asset (REQ-FUNC-080)
  • Gate the launch on airspace authorization, tower coordination, NOTAM, weather, crew credentials, Remote ID, runway separation and prohibited equipment; each passes, fails or cannot be evaluated, and the worst result decides (REQ-FUNC-081)
  • Hold a launch with its reasons and what would clear it (REQ-FUNC-082)
  • Release by a person after a go; one release flies once (REQ-FUNC-083)
  • Return the flight's findings to the asset as evidence, unverified until a person confirms each one, never changing a value a system of record owns (REQ-FUNC-084, REQ-FUNC-085, REQ-ARCH-006)
Requirements matrix rows that name this screen (1)
RowRFP sectionRequirementStatus
M-144Beyond the RFPDrone inspections of the airfieldtarget