UNCLASSIFIED
UNCLASSIFIED
SHIELD | ATLAS  ·  BRIEFING RUNBOOK
UNCLASSIFIED

Briefing Runbook click-along demo

A guided sequence for walking a general officer, program manager, or evaluator through the platform without anything reading as broken. Every page below opens cleanly, every page has a built-in ? Operator Guide, every claim is backed by what the page actually does.

PRIME
ISS LLC
CAGE
9VKK3
UEI
C7YDV3P8EHL7
STATUS
SDVOSB pending

Universal control: every page has an Operator Guide

Every standalone briefing surface (COP, C-RAM, Sensor Lab, Kill Web, GPS-Denied, Swarm C2, Sandbox) carries a floating ? button bottom-right. Click it for a one-paragraph what-this-is, a numbered walkthrough, and one-click "try this" actions. It auto-opens the first time per page and per browser. Press ? or H any time to reopen.

If the brief room is screen-sharing and the audience asks "what am I looking at", click ?. That guide is your script.

Demo sequence (about 35 minutes)

  1. Common Operating Picture (COP) — the picture a watch officer sees · 4 min
  2. Kill Web — sensor-to-shooter at machine speed · 3 min
  3. C-RAM Operator Dashboard — the engagement loop with safeties · 5 min
  4. Sensor Lab — plug-and-play acoustic detect, no kit · 4 min
  5. GPS-Denied Navigation — operating without PNT · 4 min
  6. Swarm C2 — multi-UAS command in formation · 3 min
  7. Sandbox — timed exercise with real injects · 5 min
  8. Dual-use catalog — the whole portfolio in one shell · 3 min
  9. Wrap, claim guardrails, and what we are asking for · 4 min

One-fight script — TF DAGGER (notional)

The unit you are fighting today. Everything that follows belongs to one notional task force: TF DAGGER. PTDS-1 aerostat overhead. ALPHA-1..8 small-UAS team (LEAD ISR, WINGMAN ISR, STRIKE, EW, DECOY, RELAY, two KAMIKAZE). CRAM-1 Phalanx for counter-RAM. BRAVO-6 infantry squad for QRF and dismounted reach. CHARLIE-1 EOD. LOG-1 trains. One commander, one common picture, one sensor-to-shooter loop.

"What you are about to see is one task force fighting one fight on one screen. Same unit on the swarm board, the C-RAM board, the maritime board, and the kill-chain board. Every recommendation is filtered against who is actually available. Every lethal call is human-in-the-loop. We never generate ballistic numbers."

Script (10-minute pivot version)

  1. Set the picture — open /cop. "This is the watch officer's view. Live ADS-B, FIRMS, NOAA, USGS. Same shell a city or a brigade gets."
  2. Show the unit — open /swarm-c2. Point to the TF DAGGER — FRIENDLIES roster on the left. "Every supporting element. PTDS aerostat overhead is the persistent ISR."
  3. Mass parallel engagement — on /swarm-c2 click MASS ENGAGE. Sensor-to-shooter chains draw on the map. Each hostile gets the best AVAILABLE tool — non-lethal preferred for UAS, lethal staged behind human-in-loop. The TF DAGGER roster on the left flips assets to ENGAGED in real time.
  4. Drone-controller takedown — on /swarm-c2 click TARGET CONTROLLER. Watch the four-step chain narrate at the top: PTDS detects RF leak → ALPHA-4 SIGINT triangulates the operator → EW jams the uplink (non-lethal first) → if no return-to-home, ALPHA-7 KAMIKAZE on the operator with human-in-loop. "Cheapest outcome wins. We do not jump to kinetic when EW solves it."
  5. Counter-fire cell — open /cram. Same task force. Click PLACE MY UNIT, click on the map — CRAM-1 emplaces. Click MASS ENGAGE — the five engagement options light up in sequence with live tasking text in the log. "PTDS feeds the C-RAM cell. Same picture, different operator surface."
  6. Maritime — open /maritime. Pick a region (Strait of Hormuz, Bab-el-Mandeb, etc.). If live AIS is thin, the panel falls back to a clearly tagged NOTIONAL DEMO set so the brief never reads as broken. Same threat-priority taxonomy as the ground fight.
  7. Kill chain sandbox — open /kill-chain. Run any scenario through DETECT → TRACK → IDENTIFY → DECIDE → ENGAGE → ASSESS. AI proposes COAs; commander selects.
  8. Multi-unit interop — open /unit-demo. Spawn a unit into the live hierarchy and watch it appear on the COP. "This is how a new unit comes online — minutes, not weeks."
  9. Wrap — "One platform. One unit. One fight. Browser-native. SDVOSB-pending. What do you need next from us to get this in front of a using unit?"

URL hot-list (paste into browser bookmarks before the brief) 

/cop                         Common Operating Picture
/swarm-c2                    Swarm C2 + TF DAGGER + MASS ENGAGE / TARGET CONTROLLER
/cram                        C-RAM dashboard + PLACE MY UNIT + MASS ENGAGE
/maritime                    Maritime domain awareness (live AIS + notional fallback)
/kill-chain                  Six-step kill chain sandbox with AI COAs
/unit-demo                   Unit onboarding + multi-unit interoperability
/sensor-lab                  Browser acoustic detection demo
/gps-denied                  GPS-denied navigation (jammer library)
/sandbox                     Timed exercise engine
/                            Dual-use catalog shell
/brief-runbook               This runbook (you are here)

Open with this

Frame in 30 seconds: SHIELD/ATLAS is one operator-facing platform that fuses defense, public safety, and emergency response into a common picture. Built by a service-disabled veteran owned firm. Everything you are about to see runs in this browser, today, with real public data feeds. There is no installer, no driver, no separate VM. If you can open a tab, you can run this.

"Sir/Ma'am, what I'm going to show you is a working operator surface, not a slideware demo. Every page has a built-in walkthrough — see the question mark bottom-right. Tell me at any point to slow down, jump, or stop."

Step 1 — Common Operating Picture

1
COP — Live theater map
~4 min

LIVE DATA ADS-B air tracks, NASA FIRMS wildfire detects, NOAA weather, USGS quake.

Open COP → Copy link

What to do on screen

  1. Page lands. Click the ? bottom-right — show them the operator guide auto-opens.
  2. Drag the map. Scroll to zoom. Click an aircraft icon — show the ID/altitude/heading popup.
  3. Click a wildfire dot — show VIIRS detect time, confidence.
  4. Bottom-right coords: click LL to flip lat/lon to MGRS. (General officers want MGRS.)
  5. Top toolbar: open LAYERS, then open KILL CHAIN overlay.
"This is what a watch officer or division command post sees. Everything here is real public data — air traffic from ADS-B, fires from NASA FIRMS, weather from NOAA. We add the symbology, the kill-chain overlay, and the sidebar so an operator can act, not just look."

Step 2 — Kill Web

2
Sensor-to-shooter visualization
~3 min

SCENARIO-DRIVEN Animated chain DETECT → IDENTIFY → TRACK → DECIDE → ENGAGE → ASSESS with real systems and SLA per node.

Open Kill Web →

What to do on screen

  1. Page auto-loads C-UAS Engagement on arrival — never empty.
  2. Watch dots move through the chain. Each node names the real system or unit responsible.
  3. Click a node — show capability detail, supported protocols (Link 16, CoT, MQTT), SLA.
  4. Switch the dropdown to Counter-Battery Fire. Show how the chain reshapes.
"This isn't an animation for the sake of it. The point we make to a J3 is — these nodes are real, the protocols are real, and we are honest about which step today is human-in-the-loop and which is machine-speed."

Step 3 — C-RAM Operator Dashboard

3
The engagement loop with safeties
~5 min

DEMO INJECT + LIVE MIC OPTIONAL Counter-rocket / artillery / mortar / drone operator console with sensor fusion and a press-and-hold authorize.

Open C-RAM →

What to do on screen

  1. Click the DEMO button in the top toolbar. A simulated threat appears.
  2. Show the fusion table — acoustic + radar + visual confirms.
  3. Hover the threat blip — show TTI countdown and predicted impact point.
  4. Single-click the AUTHORIZE STRIKE button. Nothing happens. Pause and explain.
  5. Press AND HOLD the button for one full second. Engagement commits.
"Watch this — single click, nothing. That is on purpose. Operator doctrine is that an effects authorization can never be one accidental click. Press and hold is the safety. We bake doctrine into the UI, not into a 30-page SOP nobody reads."
Guardrail: If asked, this is decision support — the operator authorizes. We do not claim AI generates ballistic numbers. We do not claim live FIRES iPhone camera control.

Step 4 — Sensor Lab

4
Plug-and-play acoustic detect
~4 min

LIVE BROWSER MIC No driver, no firmware, no install. Detects drone-like acoustic signatures live and cross-checks against ADS-B.

Open Sensor Lab →

What to do on screen

  1. Click Start Microphone — Allow mic permission.
  2. Click Enable Location for ADS-B context (so we know what real aircraft are nearby).
  3. Hold a phone near the laptop and play any drone audio sample on YouTube.
  4. Watch the spectrum graph spike. The system labels the signature and flags Unattributed if no nearby ADS-B aircraft matches.
  5. Click Start Recording for an MP4 capture you can drop into a brief deck. Pick "This Tab" in the share dialog.
"Most C-UAS demos require a $40k receiver, a vendor laptop, and three days of integration. This needs a USB mic and a browser. That's the point — we lower the floor so a city, a school district, a forward firebase can stand it up the same morning they decide they need it."

Step 5 — GPS-Denied Navigation

5
Operating without PNT
~4 min

SIMULATOR 9-jammer library with real Russian and Chinese profiles (R-330Zh Zhitel, Pole-21 Moskit, etc.). Shows uncertainty growth and terrain-fix recovery.

Open GPS-Denied →

What to do on screen

  1. Defaults are the Pentagon. Pick a jammer — start with R-330Zh Zhitel (broadband, kills GPS + comms).
  2. Click START GPS-DENIED SESSION. Note the initial uncertainty in meters.
  3. Click ADVANCE POSITION 4–5 times. Watch the cone of uncertainty grow.
  4. Click APPLY TERRAIN FIX. Cone collapses. That is the recovery loop.
"This is the J3 conversation that matters. Adversaries will take our PNT. The question is not 'can you protect GPS' — it is 'can your formation still maneuver and shoot when it's gone.' This sandbox lets a planner walk that with their team in the room."

Step 6 — Swarm C2

6
Multi-UAS command in formation
~3 min

8-DRONE SIMULATED SWARM Formation control, group commands, hostile contact overlay.

Open Swarm C2 →

What to do on screen

  1. Page opens with 8 friendly UAS in WEDGE formation.
  2. Click LINE, then BOX, then DIAMOND — drones reform live on the map.
  3. Issue PATROL, then ENGAGE, then RTB — telemetry list updates each second.
  4. Click any individual drone in the right-side list to zoom and see its detail.
"Friendly aircraft data isn't on this screen on purpose — that lives on the COP via ADS-B. This page is the swarm operator's view. We separate operator surfaces by job, not by data."

Step 7 — Sandbox

7
Timed exercise with real injects
~5 min

5 SCENARIOS Core Platform, C-UAS, Fires & Targeting, PNT. Each scenario delivers events on a clock with evaluation criteria.

Open Sandbox →

What to do on screen

  1. Pick Platform Orientation — Multi-Module Navigation (beginner, 30 min, 6 injects).
  2. Click start. Show the inject timeline ticking.
  3. Type a response to the first inject and submit.
  4. Show that the system is scoring against the scenario criteria, not just running a slideshow.
"This is how a unit qualifies. We do not hand a SOP and check the box. We put a scenario clock on, deliver real injects, and score. Same engine for an exercise, a qualifier, and a contractor evaluation."

Step 8 — Dual-use catalog

8
The whole portfolio in one shell
~3 min

28 INTERACTIVE + 16 CAPABILITY CARDS All ATLAS modules in one navigable shell — defense and public-safety side by side.

Open Catalog →

What to do on screen

  1. Land on the catalog. Click any tile, e.g. ALERT. The sidebar tab switches and the panel below scrolls into view with a brief outline flash and an "Opened ALERT" toast.
  2. Click another, e.g. SENTINEL. Same behavior — operators can see the surface change.
  3. Click DEFENSE MODE in the toolbar. Defense-only modules unlock in the catalog.
  4. Mention the honest split — most tiles open real interactive panels; a subset open a capability description card. We label both clearly.
"The platform isn't 44 separate apps. It's one shell with one auth, one map, one event feed. A city that buys this for fire response gets the SAME shell a brigade gets — they just see different tiles based on their permissions."

Step 9 — Wrap, guardrails, the ask

Close in 60 seconds

"Three things to take away. One — this is operator-facing software, not slideware. Two — every page has a built-in walkthrough so anyone in your unit can pick it up cold. Three — we are an SDVOSB-pending veteran-owned prime, ready to move on a Phase II SBIR or a CSO. What do you need next from us to get this in front of a using unit?"

Things to say

  • "Built by a service-disabled veteran-owned firm, ISS LLC."
  • "Decision support — the operator authorizes."
  • "Public data feeds where they exist; clearly labeled simulators where they don't."
  • "Browser-native — same shell on a laptop, a tablet, a TOC display."
  • "Walkthroughs are baked in — anyone can pick this up cold."

Do not claim

  • FIPS 140-3 validated
  • FedRAMP, ATO, IL-5
  • SIPRNET / classified network access
  • CAC / PIV authentication today
  • AI-generated ballistic firing solutions
  • Live iPhone camera control of FIRES assets

If something doesn't look right during the brief

  1. Click the ? bottom-right of any operator surface — the guide is your script.
  2. Most "blank page" perceptions are the panel landing below the fold. Scroll. The patched dual-use shell now scrolls and flashes the panel automatically.
  3. If a feed is slow (ADS-B, FIRMS), it's a public API rate limit. Say so. Don't fake it.
  4. Refresh is safe. Sessions are restored from the URL.
CHEATSHEET
ASK AI
✚
PRESENCE ✓
⚠ SANDBOX / TRAINING MODE — Live read-only data. Write commands are inhibited (train as you fight, missile button safed).