Atch 2 WARDEN Statement of Objectives 14 Oct 2026.pdf

AIR FORCE LIFE CYCLE MANAGEMENT CENTER (AFLCMC)

COMMAND, CONTROL, COMMUNICATION & BATTLE MANAGEMENT (C3BM)

KESSEL RUN (C3C)

WING C2 BRANCH (C3CW)

Statement of Objectives (SOO)

14 October 2026

1. OVERVIEW

1.1 This Statement of Objectives (SOO) defines the operational, functional, and technical objectives for the Department of the Air Force (DAF) to acquire and field an innovative software solution through project Worldwide Airbase Resiliency, Defense, and Engineering Navigator (WARDEN). Project WARDEN will serve as the baseline for a modernized next-generation DAF Emergency Management Information System (DAF EMIS), transitioning installation emergency management capabilities to an advanced, resilient, full-lifecycle emergency management platform. The objective is to demonstrate an enterprise software capability that can be deployed within designated Department of War (DoW) software ecosystems. DAF EMIS will automate and accelerate all four core phases of the Emergency Management (EM) lifecycle— Preparedness, Protection, Response, and Recovery—across a range of operating conditions, from peacetime incidents to high-threat scenarios. The ultimate objective is to ensure force survivability and accelerate decision advantage to sustain mission generation under duress.

2. BACKGROUND

2.1 Adversary capabilities and complex hazards pose a significant threat to DAF installations. These threats can trigger rapid, cascading disruptions across critical base and surrounding community lifelines. When an installation is targeted, these disruptions directly imperil personnel and degrade command and control. Under emerging operating concepts that emphasize agility and dispersal, forces must be able to operate dynamically from various locations. A modernized EM capability is required to provide the situational awareness needed to support these concepts and ensure the resilience of airbase operations.

3. CAPABILITY REQUIREMENTS

3.1 The end state requires an innovative software platform with a target Technology

Readiness level (TRL) of 7 or greater that combines automated data ingestion, resilient edge architectures, platform-agnostic mobile connectivity, and embedded decision support tools. The system should transform emergency management into a proactive and predictive process.

3.2 Program and Architectural Requirements

3.2.1 Ecosystem & Platform Integration:

3.2.1.1 The solution must be designed to operate within designated DoW enterprise cloud and software ecosystems. The Contractor should provide relevant experience developing, configuring, integrating, or deploying capabilities for Government approved enterprise data and workflow platforms.

3.2.1.2 The solution must ingest, manipulate, and expose operational entities and relationships in alignment with EM mission areas and community lifeline status systems, facilitating automated cross-echelon data synchronization

3.2.1.3 The solution must operate securely across separate security domains (e.g., unclassified and classified networks), supporting secure cross-domain data filtering to pass critical information without spillage.

3.2.2 Tactical Communications Architecture:

3.2.2.1 The system must operate reliably during intermittent or denied communications without data loss. It should demonstrate a distributed edge architecture where tactical users retain core operational capabilities locally when network connectivity is disrupted.

3.2.2.2 The architecture should be optimized for low-bandwidth and high-latency networks.

3.2.3 Platform-Agnostic Edge:

3.2.3.1 All data within this requirement shall be API accessible.

3.2.4 Data-Centric Security, Governance, and Administration:

3.2.4.1 The solution must demonstrate fine-grained, data-centric security controls, with the ability to tag and restrict individual data objects based on classification levels and releasability.

3.2.4.2 It must demonstrate dynamic, hybrid role-based access controls driven by user personas and assigned units.

3.2.4.3 It must include high-volume bulk edit tools, configuration management utilities, and content import mechanisms to rapidly establish or modify organizational data.

3.2.4.4 The system must generate comprehensive audit logs for all security-relevant events, exportable to a Security Information and Event Management (SIEM) system.

3.3 Mission Objectives: Lifecycle Mission Areas

3.3.2 Cross-Cutting Mission Objectives:

3.3.2.1 Automated Data Foundation: A self-populating data architecture that ingests authoritative datasets automatically to reduce manual data entry.

3.3.2.2 Authoritative Geospatial Foundation: Demonstrate a curated, enterprise-level global geospatial library delivering Open Geospatial Consortium (OGC)-compliant map and feature services. The system must ingest authoritative spatial data from government and civil sources to create a common operating picture that extends beyond the installation boundary.

3.3.2.3 Organizational & User Persona Alignment Foundation:

Automate the ingest and mapping of official DAF organizational structures and align system user profiles with EM program personas to reduce operational friction.

3.3.2.4 Broad Operational Decision Support: Deliver an interactive assistant that interprets commands to help users operate the application. The system should also provide proactive advice regarding the EM lifecycle, with all automated recommendations subject to human-in-the-loop validation.

3.3.2.5 Predictive Impact Analysis: Deliver infrastructure status across installation lifelines and project potential secondary and tertiary effects of disruptions.

3.3.2.6 Interactive Visualization: Provide an interactive visualization tool that combines geospatial data with a timeline, enabling commanders to review historical event sequences and anticipate future effects.

3.3.2.7 Dynamic Data Manipulation: Demonstrate ability for users to enrich ingested geospatial and tabular data sets with common operational observations and custom data fields.

3.3.2.8 Conditions: Demonstrate the ability to track regional/local lifelines and expanded installation conditions depicting the installation/operating condition.

Include a standardized hierarchical library for managing and reporting on conditions.

3.3.2.9 Personnel Accountability: Provide unit-level personnel accountability tools.

3.3.2.10 Mission Status: Provide relevant aircraft and mission status details to C2 nodes to support response and recovery prioritization.

3.3.2.11 Dashboards: Demonstrate a modular, low-code/no-code

dashboard engine for users to construct and share interactive operational displays.

3.3.2.12 Theater-Wide View: Develop a common operating picture that can provide a broader theater-wide rollup of installation conditions.

3.3.2.13 Chat Integration: Provide for bi-directional machine-to-machine integrations between DAF EMIS and enterprise tactical chat services to automatically broadcast critical alerts.

3.3.3 Prepare Mission Area Objectives:

3.3.3.1 Automated Role Management: Demonstrate an administrative workflow that identifies required versus vacant unit emergency preparedness roles and helps manage appointments.

3.3.3.2 Threat/Hazard Identification: Automatically ingest and project historical, environmental, and adversarial threat data from a curated global hazard library.

3.3.3.3 Asset Prioritization & Vulnerability: Enable EM planners to catalog, map, and prioritize key installation assets and model asset vulnerabilities against various hazards.

3.3.3.4 Consequence Modeling: Model the potential consequences of hazard/threat events, projecting estimated impacts on personnel, resources, and infrastructure.

3.3.3.5 Exercise Sandbox Builder: Demonstration of an integrated exercise planning suite that enables the use of real-world data and map layers for simulated scenarios without corrupting operational logs.

3.3.4 Protect Mission Area Objectives:

3.3.4.1 Passive Defense Library: Demonstrate a tailorable library of passive defense countermeasures.

3.3.4.2 Protection Planning: Provide an interactive spatial modeling tool to evaluate defensive coverage and compare alternative defensive configurations.

3.3.4.3 Protective Course of Action (COA) Generation: Provide an automated engine that analyzes threats/hazards and generates a prioritized, actionable list of protective recommendations.

3.3.5 Respond Mission Area Objectives:

3.3.5.1 Multi-Domain Warning & Notification: Ingest threat warnings from external systems trigger automated alerts.

3.3.5.2 C2 Node & Leadership Tracking: Demonstrate ability for users to have access to directory and geospatial tracking of installation C2 nodes.

3.3.5.3 Checklist Tool: Demonstrate a dynamic, collaborative checklist capability.

3.3.5.4 Directives & Accountability: Demonstration of the ability for key C2 Nodes to have tools to draft, distribute, and track directives with mandatory acknowledgment.

3.3.5.5 Geospatial Incident Management: Demonstrate ability for users to place, edit, and link standardized incident reports and response icons onto the common operating picture.

3.3.5.6 Sweep Management: Provide a tool for coordinating post-attack reconnaissance and damage assessment sweeps.

3.3.5.7 Automated Logging & Request Tracking: Develop an auditable, time-stamped log of system events and a capability for users to submit and track requests for information or resources.

3.3.6 Recovery Mission Area Objectives:

3.3.6.1 Automated Damage Assessment: Demonstrate the ability to ingest post-incident imagery to automatically detect and classify physical damage.

3.3.6.2 Mission-Prioritized Repair: Provide a functional outcome where the system can help facilitate airfield recovery operations by evaluating runway damage against mission requirements to assist in determining a minimum operating surface.

4. SYSTEM INTEGRATION OBJECTIVES

4.1 The contractor shall develop secure machine-to-machine interfaces with relevant systems

(e.g. C2IMERA, GEOMAP, EMOC, BLADE, etc), adhering to a Zero Trust model that enforces authentication and authorization for every transaction. Integration will be required with sources that provide:

4.1.1 Demonstrate Authoritative Common Installation Picture map layers.

4.1.2 Demonstrate Situational awareness data from tactical edge devices.

4.1.3 Demonstrate Imagery and video from aerial systems.

4.1.4 Demonstrate Aircraft maintenance and location status.

4.1.5 Early-warning telemetry.

4.1.6 Real-time logistics and resource data.

4.1.7 Official unit organizational structures.

4.1.8 Hazard plume models and sensor data.

5. PERFORMANCE STANDARDS AND METRICS

5.1 The proposed solution will be evaluated against objective performance metrics related to geospatial latency, data ingestion automation, decision support speed, and damage recognition accuracy. Specific thresholds will be defined in a controlled, formal Request for Proposal (RFP).

6. SECURITY

6.1 Software Supply Chain and Code/AI Security: The contractor must be able to generate a

Software Bill of Materials (SBOM), demonstrate a mature DevSecOps pipeline, and establish security measures to ensure the resiliency of AI/ML models against adversarial attacks.

6.2 Data Rights and Security: All developed plugins, translation code, and database schemas must be non-proprietary and delivered with unlimited Government data rights.

6.3 Facility Clearance Level (FCL): The Contractor is required to have a secret clearance prior to award. The Contractor is required to have a TS/SCI FCL after delivery of solution at the Government designated data platform ecosystem but prior to scaling/fielding.

7. INTEGRATION

7.1 The Contractor shall successfully deploy within the DoW’s cloud environments and other military applications and/or data systems.

8. FIELDING

8.1 The Contractor shall be able to deploy to the field, provide exercise support, and stand-up instance in other locations.

9. SUSTAINMENT

9.1 The Contractor shall maintain the software 365/24/7.

10. FACILITY ACCESS

10.1 TBD, pending responses from the Market Research. The Contractor will provide a comprehensive plan to obtain TS/SCI development environment (e.g. Contractor owned, Hanscom AFB MA or other locations deemed necessary for software development up to TS/SCI level).

11. DIRECTIVES AND STANDARDS

11.1 EM Mission Workflow: Demonstrate the alignment of emergency management mission area workflows as specified in DAFI 10-2501, Emergency Management Program.

11.2 Interoperability and Security Standards: Comply with NIST SP 800-53; DoDI 8510.01; DoD Cloud Computing Security Requirements Guide (SRG) for Impact Level 5 (IL5) and Impact Level 6 (IL6); and Open Geospatial Consortium (OGC) Standards (WMS, WFS, GeoJSON).

12. GOVERNMENT FURNISHED DATA/PROPERTY

12.1 The Government may provide Government Furnished Data and/or Government

Furnished Property based on the best interest of the Government. If Government Furnished Data is provided, a bidder’s library will be released to the industry during the draft RFP phase.

12.1.1 High-level architecture Diagrams – Enterprise, cloud, edge, and external-system views.

12.1.2 Data-model information – Available data schemas and formats.

12.1.3 Interfaces and integrations – Anticipated systems, API expectations, and machine-to-machine data exchanges.

12.1.4 Data transfer and synchronization – Requirements for data exchange, synchronization, and operations in disconnected, low-bandwidth, or high-latency environments.

12.1.5 Geospatial requirements – Map layers, features services, and applicable geospatial data standards.

12.1.6 Cybersecurity and access controls – Authentication, authorization, user access, audit logs, and related security expectations.

12.1.7 Operational use cases and performance expectations – Representative mission scenarios and the outcomes vendors should be prepared to demonstrate