0010 - Demo Facilitation

Andi Lamprecht ·2026-05-11· 5 min read· Draft

Problem Statement

Demo scenarios are hand-built by the engineering team and require engineering involvement to set up, modify, or reset. During live demos, small click targets and manual navigation through the demo control panel interrupt the narrative and draw attention to tooling rather than product capabilities. These constraints limit who can run demos, increase preparation overhead, and reduce confidence in high-stakes presentations.

Three specific gaps compound the problem: (1) there is no self-service path to create scenarios for Fort Campbell or the National Mall — both required for upcoming JIATF and Booz Allen presentations; (2) there is no way to simulate realistic non-participatory background traffic; and (3) trust level labels in the product (L4, L5) do not match the language used in external communications (“Verified”, “Verified+”).

Business Justification

• Enables product and sales staff to run demos without engineering involvement or preparation time
• Improves live demo quality: fewer misclicks, smoother scenario transitions, more credible storytelling
• Unlocks Fort Campbell and National Mall demo scenarios for upcoming JIATF and Booz Allen meetings
• Aligns product labels with external product positioning before those labels appear in customer recordings or screenshots

Personas

Internal demo operators: Jake, Andi, Colin — product and sales staff who set up and run live demos

Outcomes

Requirements

Hotkeys — simulated aircraft:

• A hotkey for each trust level (L1–L5) places one simulated aircraft of that level at a random position within the current map view
• A separate hotkey enters “flight plan draw” mode: the demo operator clicks an origin on the map, then a destination; ATOMx creates a simulated L3–L5 aircraft with an attached flight plan between those two points without opening the demo control panel

Hotkeys — map controls:

• A hotkey toggles the flight plan source filter between interUSS and ATOMx

Click targets:

• Aircraft icons on the live map have enlarged click targets sufficient to click reliably during a demo without misclicking into empty map space (exact dimensions TBD with design)

Demo control panel — scenario setup:

• The existing demo control panel (accessible from the live map) supports on-demand scenario creation and reset for: Fort McNair, Fort Campbell, and the National Mall
• Each scenario can be created and reset by a demo operator without engineering involvement

Demo control panel — scripted ADS-B traffic:

• A demo operator can configure scripted ADS-B traffic by specifying: origin location, destination location, and aircraft count
• Scripted aircraft follow a simulated flight path between origin and destination and appear as unidentified (L1) non-participatory traffic

Trust level labeling — product-wide:

• L4 is relabeled “Verified” in all locations where the label appears: map legend, aircraft detail panel
• L5 is relabeled “Verified+” in the same locations

Scope

In scope:

• Hotkeys: L1–L5 aircraft placement, inline flight plan creation (hotkey + two map clicks), flight plan source filter toggle
• Enlarged aircraft icon click targets
• Demo control panel: Fort McNair, Fort Campbell, National Mall scenario setup and reset
• Scripted ADS-B traffic: origin, destination, count
• L4 → “Verified” / L5 → “Verified+” relabeling across legend and detail panel

Out of scope:

• Role-gating or access control on the demo control panel (future productization)
• Real ADS-B feed ingestion
• Automated scenario scripting or playback recording
• Renaming L1–L3 labels

Operational Environment

Physical — Demos run on a laptop connected to a large display or shared over video call. All features must work reliably in a screen-share context. The Mac Android emulator path for CivTAK demos must not interfere with demo hotkey bindings.

Regulatory — No regulatory constraints. Simulated aircraft and traffic are clearly synthetic; demo data is never transmitted to real UTM or airspace management systems.

Organizational — Demo control panel is currently accessible to all users in demo builds. Access control is explicitly out of scope for this build; productization of the control panel (including role-gating) is a future workstream.

Constraints

• All demo scenario changes must be self-service — no Slack to engineering, no backend scripts
• Hotkeys must not conflict with browser default shortcuts or common OS-level bindings
• “Verified” and “Verified+” are product-wide label changes; they must be consistent across every surface where L4/L5 currently appears before the next customer-facing demo

Product Surfaces