FEMA already has the map (TAK / ATAK-CIV / Booz Allen Sit(x)). FEMA already has the boards (WebEOC). FEMA already has the framework (NIMS / ICS / NRF / 15 ESFs). What FEMA does not have is a single decision-support layer that fuses the federal data feeds, authors compliant outputs into the systems FEMA already runs, and respects the 10 Regions × 5 ICS echelons of authority. SHIELD/ATLAS is that layer.
Open with the punchline so the room knows where you're landing. Sit(x) is the pipe; ATLAS is the brain. We are not asking FEMA to swap any tool. We are filling the analyst gap between the feeds FEMA already pays for and the boards FEMA already runs. The rest of the deck shows that gap closed at every echelon, with deep links to live working modules — not slides about future capability.
Organized by ORG × ECHELON per Greg Funk standing rule. Every slide deep-links to the live ATLAS module that produces the data.
Use this slide to set scope: fourteen content slides organized by the customer's own org chart, not ours. Every slide names the org and the ICS echelon it speaks to, so a Region IV deputy administrator and a fire IC both know which slides are for them. Two engagement tracks at the close: civil-side via Apex Accelerator into FEMA, DoD-side via CRADA into AFRL/RI or NIST PSCR. Skip slides freely; the deep links keep working out of order.
NRCC's job is to maintain federal awareness, not to run the incident. ATLAS gives the watch officer a fused national picture without standing up a custom feed contract. We don't replace FEMA OCIO's ESRI infrastructure; we enrich it with three feeds OCIO doesn't have to procure.
Every RRCC runs WebEOC. We don't ask them to swap. ATLAS produces the record they were going to type by hand — already populated, already validated, ready to file. The integration is as light as paste-into-Fusion-board, and as heavy as a server-to-server inbound feed if the EOC's WebEOC operator wants it that way.
The bottleneck at the JFO is not policy, it's documentation latency. Most RRFs are typed by hand, and the wrong ESF gets named because the requestor is a county EM director under pressure, not a federal-grade form-filler. ATLAS routes the request and produces the form. The JFO Liaison still owns the submission decision.
The state EOC is where DSCA goes well or poorly. The agencies that have run it well — Florida 2017 Irma, Texas 2024 Beryl — had a single COP across Title 10 and Title 32 forces, plus civilian EM. ATLAS is built so that picture exists by default, not as a one-off integration project per storm.
Be precise here: ATLAS is not an authorized IPAWS originator and we do not claim to be. We are an authoring tool. A FEMA-designated COG (the state, the county, the tribal nation) submits. This separation is a feature — it keeps the legal authority where it belongs and reduces the customer's compliance lift.
This is the lane Apex Accelerator helps us reach: small county EM offices, tribal EM directors, regional health authorities. We don't compete with their existing tools; we fill the gap between dispatch and after-action that they currently fill with spreadsheets.
The DSCA seam is where federalization disputes happen. ATLAS' contribution is removing the picture-disagreement layer of those disputes. Decisions still belong to humans; agreement on what's actually happening is now baseline.
FIRMS has 3-hour latency and you can lose a fire start in that window. GOES-R FDC closes the gap to 5 minutes. The fire IC gets one fused layer instead of toggling between three browser tabs. WFDSS handoff is the moment of friction; ATLAS makes the handoff a file, not a re-key.
CISA's Community Lifelines framework is the language federal partners now use for incident impact. ATLAS speaks that language natively. We are not replacing the Sector Risk Management Agencies; we are the analyst that spots the cascade before the SRMAs are paged.
HSIN is gated by sponsorship. We don't pretend otherwise. ATLAS stages the messages and exposes a manifest that an HSIN administrator can subscribe to. That is the cleanest, most boring, most defensible posture: no impersonation, no claimed credentials, no integration that breaks if DHS rotates a key.
The Apex Accelerator conversation will hit this question: "we already have TAK." Excellent — that means the field is already wired. ATLAS becomes the bridge adapter that pumps decision support into the groups operators are already in. We do not compete with the COP; we are the analyst it has been waiting for.
This is the trust slide. Put it in front of the audience early in any procurement conversation so they know we know our lane. Every "we are not" maps to a sponsored party that does hold that authority — FEMA-designated COG for IPAWS, Juvare for WebEOC, DHS for HSIN, USDA/NIFC for WFDSS. ATLAS doing the authoring layer means the customer keeps their authority chain intact and we don't trip a single ATO requirement.
This is not an ask-for-money conversation. It is an ask-for-a-pilot conversation. The pilot is no-cost on FEMA's side, runs on FEMA's existing exercise calendar, and produces an AAR that turns into a production engagement. Apex Accelerator's value is the warm intro to the right Region Industry Liaison; we bring the working capability.
The CRADA path is parallel to, not a substitute for, the Apex Accelerator path. Civil-side moves through FEMA Region Industry Liaisons; DoD-side moves through federal lab T2 offices. Both produce the same artifact at the end — a Joint Test Report or After-Action Report that contracting officers will actually act on. Tier 1 targets are AFRL/RI (best DoD fit, software CRADAs are routine) and NIST PSCR (best civil-emergency fit, tech transfer IS NIST's mission). Tier 2 are USTRANSCOM T2 and DHS S&T FRG. Disclose SDVOSB-pending and the no-FedRAMP / no-IL-5 / no-ATO posture in the first email — the CRADA model is precisely what fits a software-only partner without those authorities, which is why the conversation works.
This page works best with your current GPS location.