# CRADA Target Labs — ATLAS Outreach List This is the short list of federal laboratories and tech-transfer offices where ATLAS is the right kind of partner. The list is short on purpose. A CRADA conversation that goes anywhere takes weeks of one Principal's attention; spreading thin produces nothing. For each lab below: why ATLAS fits, the publicly-known engagement entry point, and a draft first-contact email body. **Personal names and direct phone numbers are intentionally omitted — they change frequently and the T2 office routes inbound traffic to the right human anyway.** Use the lab's public T2 / Tech Transfer mailbox or web form. Do not cold-email named scientists; route through ORTA. Hard rule: every outreach discloses SDVOSB-pending status and the no-FedRAMP / no-IL-5 / no-ATO posture up front. The whole point of the CRADA model is that the lab does NOT need any of those authorities. --- ## Tier 1 — best fit ### 1. AFRL Information Directorate (AFRL/RI), Rome, NY **Why ATLAS fits:** AFRL/RI's mission is C2, ISR fusion, and decision-support — exactly what ATLAS is. Their public portfolio includes Multi-Domain Sensemaking, Distributed Information Systems, and Trusted Autonomy. ATLAS as a fusion layer between civil-emergency feeds (IPAWS / HSIN / WFDSS) and DoD-side CoT/TAK is a clean unclassified-level evaluation candidate for them. They sign software-only CRADAs constantly. **Engagement entry point:** - AFRL Tech Transfer (corporate): https://www.afrl.af.mil/Partner-with-Us/ - Air Force tech transfer portal (the official channel): https://aftechconnect.com - AFRL/RI public site: https://www.afrl.af.mil/About-Us/Fact-Sheets/ (filter for Information Directorate) **First-contact ask:** A 30-minute introductory call between the ATLAS Principal Investigator and AFRL/RI's Office of Research and Technology Applications (ORTA), to scope a possible CRADA covering ATLAS as a fusion layer in an upcoming AFRL/RI multi-organization unclassified exercise. **Draft email body (edit before sending):** > Subject: CRADA inquiry — ATLAS fusion / decision-support layer for > AFRL/RI Multi-Domain Sensemaking > > AFRL/RI Tech Transfer team, > > ISS LLC (CAGE 9VKK3, UEI C7YDV3P8EHL7, SDVOSB-pending) operates > SHIELD/ATLAS, a fielded civil-emergency and DSCA decision-support > layer. ATLAS fuses unclassified federal feeds — FEMA IPAWS-CAP, > DHS HSIN, USDA/NIFC fire data, CISA Community Lifelines, FIRMS / > GOES-R / NOAA HMS, ESF Resource Request Forms, and ICS-209 records > shaped for Juvare WebEOC Fusion — and emits decision-support > outputs to the ICS echelons that own the response. > > We are not asking for funds. We are asking for a CRADA under > 15 U.S.C. § 3710a to evaluate ATLAS inside one of AFRL/RI's > upcoming unclassified multi-organization exercises. ATLAS is > deployed; live operator surfaces and a 16-slide capability deck > are at the URLs in our signature. > > Disclosures up front: we do not hold FedRAMP, IL-5, FIPS, CAC, > SIPRNET, or ATO. The CRADA model is what fits us, which is why we > are writing. > > Could we schedule a 30-minute scoping call with ORTA in the next > three weeks? > > Dr. Terry Flood > Principal, ISS LLC > [phone] [email] > Capability deck: [public URL]/fema-tak-bridge-deck > JWS template: [public URL]/crada-pathway --- ### 2. NIST Public Safety Communications Research (PSCR), Boulder, CO **Why ATLAS fits:** PSCR runs the federal R&D program for FirstNet, Next Generation 911, public-safety analytics, and the IPAWS profile work that ATLAS's CAP module already implements against. PSCR's whole mission is to test commercial public-safety capabilities at federal scale and feed results to standards bodies. ATLAS is the kind of software they test routinely. NIST CRADAs are unusually founder-friendly because tech transfer IS the agency mission. **Engagement entry point:** - NIST Technology Partnerships Office: https://www.nist.gov/tpo - CRADA process: https://www.nist.gov/tpo/cooperative-research-and-development-agreements-cradas - PSCR program: https://www.nist.gov/ctl/pscr (public-safety-specific) - Generic PSCR contact: pscr@nist.gov (publicly listed) **First-contact ask:** A scoping call with the PSCR program lead and the NIST Technology Partnerships Office to discuss a CRADA covering ATLAS as an end-to-end IPAWS-CAP authoring + HSIN-CAP staging demonstrator, evaluated against PSCR's reference test environment. **Draft email body:** > Subject: CRADA inquiry — ATLAS as IPAWS-CAP authoring + HSIN-CAP > staging demonstrator for PSCR evaluation > > NIST PSCR / TPO team, > > ISS LLC operates SHIELD/ATLAS, a fielded civil-emergency > decision-support layer. Of direct relevance to PSCR: ATLAS is a > compliant CAP 1.2 + IPAWS-profile authoring and HSIN-CAP staging > environment with end-to-end scope-dependent field validation > (CAP 1.2 §3.2.1.5 / §3.2.1.6 enforced as errors, not warnings), > XML emission of and per spec, and a > header-only fail-closed admin gate on the HSIN outbox. > > We would like to propose a CRADA under 15 U.S.C. § 3710a to > evaluate ATLAS against PSCR's reference IPAWS / HSIN test > environment, with a Joint Test Report as the primary deliverable. > ATLAS is software-only; no PSCR funds requested. > > Disclosures: SDVOSB-pending, no FedRAMP, no IL-5, no ATO. ATLAS > does not, during a CRADA, submit to live IPAWS-OPEN or push to > live HSIN — the evaluation is end-to-end against test feeds. > > Live operator surfaces and a 16-slide capability deck are at the > URLs below. Could we schedule a 30-minute scoping call? > > Dr. Terry Flood > Principal, ISS LLC > CAGE 9VKK3, UEI C7YDV3P8EHL7 > Capability deck: [public URL]/fema-tak-bridge-deck > CAP / IPAWS module: [public URL]/fema-cap-author > HSIN-CAP module: [public URL]/fema-hsin --- ## Tier 2 — strong second-stage targets ### 3. USTRANSCOM Technology Transfer (T2), Scott AFB, IL **Why ATLAS fits:** USTRANSCOM J6 owns the joint-mobility C2 problem. Their public-facing T2 office actively recruits non-traditional software partners (the article that motivated this whole engagement plan reproduces their CRADA process diagram). ATLAS's ESF logistics routing + RRF generation + DoD DSCA bridge maps directly to JECC (Joint Enabling Capabilities Command, a USTRANSCOM-aligned sub-organization) movement-planning workflows. **Engagement entry point:** - USTRANSCOM Tech Transfer office (public): https://www.ustranscom.mil (search "Technology Transfer" or "T2"; the office's process artifact is published) - USTRANSCOM Industry Engagement: https://www.ustranscom.mil/cmd/ind.cfm **First-contact ask:** A scoping call with USTRANSCOM T2 to discuss a CRADA covering ATLAS's ESF logistics + RRF + DSCA module as a mobility-decision-support evaluation candidate. **Draft email body:** Adapt the AFRL/RI template; lead with the ESF router + RRF capability and the DSCA bridge, and explicitly cite the USTRANSCOM T2 process the office has publicly documented. --- ### 4. DHS Science & Technology Directorate, First Responders / Operations (FRG) **Why ATLAS fits:** ATLAS's civil-emergency leg is exactly DHS S&T First Responders' lane — IPAWS, HSIN, ESF, fire fusion, CISA Lifelines. DHS S&T has a less-publicized CRADA program than DoD labs, but they sign them. They also run SAFETY Act and SBIR programs that complement the CRADA path. **Engagement entry point:** - DHS S&T (corporate): https://www.dhs.gov/science-and-technology - DHS Tech Transfer Program: https://www.dhs.gov/science-and-technology/technology-transfer-program - First Responders / Operations: https://www.dhs.gov/science-and-technology/first-responders **First-contact ask:** A scoping call with the DHS S&T Tech Transfer office, with First Responders / Operations as the operational sponsor on the lab side, to discuss a CRADA covering ATLAS's civil-emergency module suite (CAP, HSIN, WebEOC, ESF, fire fusion) as an integrated evaluation candidate. **Draft email body:** Use the NIST PSCR template as a base; replace PSCR-specific language with FRG-specific language and add the SAFETY Act / SBIR complement (we are interested in CRADA first; we recognize SAFETY Act and SBIR as parallel paths). --- ## Tier 3 — DSCA bridge target ### 5. USNORTHCOM (DoD Support to Civil Authorities) **Why ATLAS fits:** NORTHCOM owns the DSCA mission. The deck's "DoD DSCA Joint" column is built for them. NORTHCOM's exercise calendar (Falcon Peak, Vigilant Shield) is exactly the kind of government-instrumented venue the article's case-study companies used to validate before scaling. **Engagement entry point:** NORTHCOM industry engagement is less formal than the lab T2 path. The right move here is to use the AFRL/RI or NIST PSCR CRADA, then ask the Lab partner to sponsor ATLAS into a NORTHCOM exercise as part of the Lab's existing participation. CRADA → exercise → demo data → follow-on award is the documented pipeline. --- ## What we will NOT do during a CRADA To keep this honest and to give the T2 office something concrete to hand to their counsel: 1. We will not submit to live IPAWS-OPEN. (Requires FEMA-designated COG and signed PKI. ATLAS authors; the COG submits.) 2. We will not push to live HSIN-Connect. (Requires sponsored DHS HSIN administrator. ATLAS stages; the sponsor completes the federation.) 3. We will not write to a live WebEOC instance. (Requires Juvare integration partnership. ATLAS produces the Fusion-shaped record; the EOC operator wires the inbound board.) 4. We will not push to live WFDSS. (Requires USDA / NIFC sponsored credentials. ATLAS exports import-ready JSON; the fire IC imports.) 5. We will not bring classified, ITAR, or CUI//SP-PROCURE data into the evaluation. CRADA work is at the Unclassified level only. These boundaries are features, not limitations. They are why the CRADA can be signed in 6-8 weeks instead of 6-8 quarters.