Printed from https://fiscalreceipts.com/program/0606118A/ — data as of July 28, 2026. Every figure is citation-backed; see the page online for per-number provenance.
AIAMD Software Development & Integration
Budget Figures
FY2026 award data is a partial year — USASpending awards are reported on a rolling basis and the fiscal year does not close until September 30. why partial FY2026 data? →
Insufficient trajectory data for sparkline (only FY26 available).
● actuals (line) · ○ enacted · ◇ request — gaps are editions the program is absent from, never interpolated.
| Series | FY26 |
|---|---|
| Request | $461.9M |
blank = series not published for this year; – = absent from that edition.
Program Lineage
Predecessors (funding flowed in)
- realigned from · per FY2026 J-book · BA5
show sentence
“In FY 2026, funds were realigned to PE 0606118A, AIAMD Software Development & Integration to support entering into the Software Pathway.”
0606118A — AIAMD Software Development & IntegrationFamily Funding Line
Funding chain: 0605457A0606118A — Army Integrated Air and Missile Defense (AIAMD)
- FY2017$252.8M
- FY2018$336.4M
- FY2019$277.6M
- FY2020$208.9M
- FY2021$193.9M
- FY2022$157.9M
- FY2023$265.3M
- FY2024$284.1M
- FY2025$602.0M
- FY2026
0605457A$146.1M0606118A$461.9M
Description
Mission — AIAMD Software Development & Integration
Agile software development is the key pacing activity for introducing enhanced Army Integrated Air and Missile Defense (AIAMD) system capabilities, integrating with emerging AMD effectors and sensors, and interoperating with joint and higher echelon mission command systems. The Defense Acquisition Executive (DAE) approved AIAMD entry into the Software Acquisition Pathway (SWP) Execution Phase on September 21, 2021. This pathway facilitates rapid and iterative delivery of software capability to the user and enables multiple 1-N capability items to be worked concurrently as defined by emerging joint Warfighter priorities. The IAMD Battle Command System (IBCS) based AIAMD architecture is a software intensive capability that enables net-centric, system of systems (SoS) command and control of AIAMD. The AMD Mission Command Product Office executes the IBCS program in accordance with the SWP utilizing the Scaled Agile Framework (SAFe) development methodology. This approach delivers Program Increments (PI) in the form of quarterly software-based improvements and annual capability releases that address Warfighter priorities (1-N), emerging threats, and weapon and sensor integration requirements. Software testing occurs at the end of each PI cycle with functional testing at the Contractor System Integration Lab (C-SIL), followed by validation of performance requirements at the Government System Integration Lab (G-SIL). The software is then delivered to White Sands Missile Range (WSMR) for testing with tactical sensors and weapons. Funding of $358.854 million in FY 2026 supports Integrated Fires System of Systems agile software development, updates and integration, developmental testing, requirements verification of the software build, operational testing, modeling and simulation and integration activities for integrated fires capabilities to include Patriot, IFPC, LTAMDS, and Forward Area Air Defense Command and Control (FAAD C2) Convergence into IBCS. The program also expands development capacity to meet increasing integration demands to support 1-N capability. Development and testing in FY26 contributes to the Guam Defense System (GDS) architecture including countering advanced threats and capability integration with LTAMDS, IFPC, Sentinel A4, RIG-360, and ALPS. The FY 2026 request for AIAMD Software Development & Integration includes $358,854 thousand of discretionary and $103,000 thousand of mandatory (reconciliation) for a total of $461,854 thousand. The mandatory funds support full THAAD integration into the AIAMD architecture and foundational requirements for Golden Dome for America (GDA) to include remotely operated autonomous system and AI enabled fire control. Software development activities for GDA support significantly reducing human-in-the-loop interactions across sensor and effector platforms, leverage AI technologies and techniques reducing human cognitive load, augmenting required tasks, and increasing system performance and enabling consolidated remote operations of sensors and shooters. Further information for this reconciliation request is provided in section 20003 (Missile Defense) of the Reconciliation Exhibit. The FY 2026 request for AIAMD Software Development & Integration includes $358,854 thousand of discretionary and $103,000 thousand of mandatory (reconciliation) for a total of $461,854 thousand. The mandatory funds support full THAAD integration into the AIAMD architecture and foundational requirements for Golden Dome for America (GDA) to include remotely operated autonomous system and AI enabled fire control. Software development activities for GDA support significantly reducing human-in-the-loop interactions across sensor and effector platforms, leverage AI technologies and techniques reducing human cognitive load, augmenting required tasks, and increasing system performance and enabling consolidated remote operations of sensors and shooters. Further information for this reconciliation request is provided in section 20003 (Missile Defense) of the Reconciliation Exhibit.
Mission — AIAMD Software Development & Integration
Agile software development is the key pacing activity for introducing enhanced Army Integrated Air and Missile Defense (AIAMD) system capabilities, integrating with emerging AMD effectors and sensors, and interoperating with joint and higher echelon mission command systems. The Defense Acquisition Executive (DAE) approved AIAMD entry into the Software Acquisition Pathway (SWP) Execution Phase on September 21, 2021. This pathway facilitates rapid and iterative delivery of software capability to the user and enables multiple 1-N capability items to be worked concurrently as defined by emerging joint Warfighter priorities. The IAMD Battle Command System (IBCS) based AIAMD architecture is a software intensive capability that enables net-centric, system of systems (SoS) command and control of AIAMD. The AMD Mission Command Product Office executes the IBCS program in accordance with the SWP utilizing the Scaled Agile Framework (SAFe) development methodology. This approach delivers Program Increments (PI) in the form of quarterly software-based improvements and annual capability releases that address Warfighter priorities (1-N), emerging threats, and weapon and sensor integration requirements. Software testing occurs at the end of each PI cycle with functional testing at the Contractor System Integration Lab (C-SIL), followed by validation of performance requirements at the Government System Integration Lab (G-SIL). The software is then delivered to White Sands Missile Range (WSMR) for testing with tactical sensors and weapons. Funding of $358.854 million in FY 2026 supports Integrated Fires System of Systems agile software development, updates and integration, developmental testing, requirements verification of the software build, operational testing, modeling and simulation and integration activities for integrated fires capabilities to include Patriot, IFPC, LTAMDS, and Forward Area Air Defense Command and Control (FAAD C2) Convergence into IBCS. The program also expands development capacity to meet increasing integration demands to support 1-N capability. Development and testing in FY26 contributes to the Guam Defense System (GDS) architecture including countering advanced threats and capability integration with LTAMDS, IFPC, Sentinel A4, RIG-360, and ALPS. The FY 2026 request for AIAMD Software Development & Integration includes $358,854 thousand of discretionary and $103,000 thousand of mandatory (reconciliation) for a total of $461,854 thousand. The mandatory funds support full THAAD integration into the AIAMD architecture and foundational requirements for Golden Dome for America (GDA) to include remotely operated autonomous system and AI enabled fire control. Software development activities for GDA support significantly reducing human-in-the-loop interactions across sensor and effector platforms, leverage AI technologies and techniques reducing human cognitive load, augmenting required tasks, and increasing system performance and enabling consolidated remote operations of sensors and shooters. Further information for this reconciliation request is provided in section 20003 (Missile Defense) of the Reconciliation Exhibit.
Justification
Accomplishments & Planned Programs (3)
Software Development
Software development is the key pacing activity for introducing enhanced Integrated Fires capabilities, integrating with emerging AMD effectors and sensors, and interoperating with joint/higher echelon mission command systems. The AIAMD program's Agile development approach enables flexibility to reprioritize integration capabilities to meet changing Warfighter requirements and defeat emerging threats. The Program uses Scalable Agile Framework (SAFe) SW development methodology in the digital engineering environment. SAFe is a scalable and configurable framework that guides incremental development of software and rapid development of functional capabilities within the IBCS to continuously address evolving threats. Each program increment (PI) is comprised of four Sprints. There are four PIs annually which culminate in the release of a yearly Minimum Viable Capability Release (MVCR). In this construct, capability to address the user needs and requirements are developed and refined in each successive PI, allowing for the continuous delivery and fielding of new and/or improved functional capabilities. Through Agile methods, the IFMC PO will provide the Warfighter with 1-N capabilities faster and with minimal re-work due to Warfighter feedback from requirement implementation to final product testing and deployment.
Test and Evaluation
Conduct developmental and follow-on operational test events for baseline and future capability (1-N list). High-fidelity testing of the IAMD system, to include the Integrated Air and Missile Battle Command System (IBCS) software, is conducted at the Tactical Systems Integration Lab (T-SIL) and WSMR with tactical A-Kit components for the integrated AMD sensors and/or weapons. The AIAMD program continues to integrate emerging sensors and effectors through new IBCS Agile software builds. A testing rhythm of development integration testing with the latest IBCS Agile Program Increment (PI) release, collective training with the AMD Battalions preparing for fielding, and an operational test and evaluation phase will occur for each emerging sensor and effector integrated and evaluated with the operational IBCS system. System of Systems (SoS) level DT and OT conducted at annual Integrated Fires Test Campaign (IFTC) that includes Developmental, Operational Test and Evaluation (DOT&E) to verify compatibility and IBCS operational functionality. Integrated Fires testing enables efficient use of test resources, range time, and funding via recurring IFTCs to qualify and field Integrated Fires materiel solutions. Developmental testing is designed to not only test new capability but to understand and reduce risk ahead of upcoming Operational Test Events. Operational Test events occur annually and exercise control of the adapted capability in a live environment. Operational events focus on material performance gaps and ensure cross component capabilities (i.e. safety considerations, friendly protection, combat identification) are done in concert with Agile development processes initiated under the AIAMD program. IBCS serves as the command and control element for Integrated Fires Operational testing.
Modeling and Simulation
The use of M&S is the most cost- and schedule-effective method, allowing incremental complexity, flexibility, and data collection across the widest distribution of variables. Each software Program Increment (PI) will be tested at the G-SIL to validate performance requirements. The product of each PI is assessed by the G-SIL to inform test readiness to evaluate new, viable software products as well as related hardware changes. Additionally, required scenarios and defense planning products are developed at multiple venues with configuration control. Commonality between the component developmental environment and the G-SIL integration environment supports validation and verification of simulations anchoring the lab environment to the large-scale, tactically representative span of control of the DT testbed. Live Air and high-fidelity sensor stimulation from Mobile Flight Mission Simulator provides additional looks at real world phenomenology impacted surveillance, tracking, identification, and engagement. The G-SIL conducts lower-fidelity solution-level testing, using hardware-in-the-loop and/or models and simulations for adapted components. This funding also supports updates and execution of IAMD Simulation (IAMDSIM) which is a high fidelity end-to-end digital simulation used to test the IAMD system in a fully simulated environment.
Budget Line Items(workbook-cited)
Exhibit R-1
| Account | Org | Type | Amount |
|---|---|---|---|
| Research, Development, Test and Evaluation, Army | A | FY26 Disc. Request | $358.9M |
| Research, Development, Test and Evaluation, Army | A | FY26 Reconciliation | $103.0M |
| Research, Development, Test and Evaluation, Army | A | FY26 Total | $461.9M |
Budget Details(R-2/P-40 facts)
| Project | FY26 Base | FY26 Request |
|---|---|---|
| DM2: AIAMD Software Development & Integration | $358.9M | $358.9M |
| Program Element | $358.9M | $358.9M |
No follow-the-dollar view — this program's awards haven't been crosswalked at high confidence (flows cover 17 of 1741 programs). why coverage is partial? →
Awards
No awards are linked to this program element at high confidence — the budget→award crosswalk only asserts links it can defend, and this line has none yet.
Lobbying Mentions
No Senate LDA lobbying filing in the tracked data mentions this program element by code or alias.
No research dossier for this program — dossiers cover 50 of 1741 programs, the largest fully J-book-detailed lines by FY2026 requested dollars. why no dossier here? →