Printed from https://fiscalreceipts.com/program/0606118A/ — built September 26, 2026. Every figure is citation-backed; see the page online for per-number provenance.
AIAMD Software Development & Integration
Budget figures
$358.9M discretionary + $103.0M one-time reconciliation.
Two official figures, one label— reconciled below
Fiscal Receipts uses P-1/R-1 workbook total obligation authority (TOA) as the headline figure sitewide. The workbook TOA includes budget rows that the R-2/P-40 J-book program line excludes — advance procurement in an ordinary year, and in FY2026 the one-time reconciliation appropriation as well. Each row below names the one it is. How the two bases relate →
FY26 Request · $461.9M TOA − $358.9M J-book line = 103.0M (461.9 − 358.9 = 103.0) — $103.0M of one-time FY2026 reconciliation money accounts for this gap — not advance procurement
Figures in the sentence are rounded for reading; the parenthesised arithmetic is the same subtraction in USD millions, at the precision where it closes.
FY2026 award data is a partial year — USAspending reports awards on a rolling basis, and this corpus runs through 2026-09-04. why partial FY2026 data? →
Budget trajectory
Insufficient trajectory data for sparkline (only FY26 available).
Decade view
P-1/R-1 workbook TOA basis, shown compact in $B/$M (the workbook records USD thousands); each figure cites its own President's Budget edition
● 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
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.
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.
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.
Budget line items(workbook-cited)
P-1/R-1 workbook Total Obligation Authority basis (USD thousands) · PB2026.
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)
J-book detail basis (R-2/P-40, USD millions) · PB2026 — a different accounting basis from the P-1/R-1 workbook TOA above; where the two disagree, the reconciliation strip under Budget figures shows both.
Wider than this screen — swipe the table sideways for the remaining fiscal-year columns.
| Project | FY26 Base | FY26 Request |
|---|---|---|
| Program Element | $358.9M | $358.9M |
| DM2: AIAMD Software Development & Integration | $358.9M | $358.9M |
Follow the dollar
No follow-the-dollar view — this program's awards haven't been crosswalked at high confidence (flows cover 312 of 1,938 programs). why coverage is partial? →
Awards
No awards are linked to this program element at high or medium 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.
Oversight
Department-level designation (not specific to this program)
GAO lists 5 high-risk areas for DOD as a whole. That designation covers the department, not AIAMD Software Development & Integration. No program-specific GAO finding for this line is in the ingested data. See the DOD oversight record.
Program dossier
No research dossier for this program — dossiers cover 50 of 1,938 programs, the largest fully J-book-detailed lines by FY2026 requested dollars. why no dossier here? →
Primary sources
Open any budget figure for its exact receipt. Verified line items lead with the highlighted government PDF; original spreadsheets download with their budget edition and exhibit in the filename.
Budget totals · TOA sources
FY2026 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · P196
Complete workbook · unchanged saved copy. Saves as PB2026_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2017 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · P130
Complete workbook · unchanged saved copy. Saves as PB2017_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2018 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · W142
Complete workbook · unchanged saved copy. Saves as PB2018_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2019 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · W144
Complete workbook · unchanged saved copy. Saves as PB2019_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2020 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · R168
Complete workbook · unchanged saved copy. Saves as PB2020_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2021 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · S177
Complete workbook · unchanged saved copy. Saves as PB2021_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2022 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · L153
Complete workbook · unchanged saved copy. Saves as PB2022_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2023 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · L153
Complete workbook · unchanged saved copy. Saves as PB2023_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2024 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · N154
Complete workbook · unchanged saved copy. Saves as PB2024_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
FY2025 Department of Defense Budget: RDT&E Programs (R-1) · comptroller.war.gov
Exhibit R-1 · L154
Complete workbook · unchanged saved copy. Saves as PB2025_DoD_R-1_Research-Development-Test-Evaluation.xlsx.
Detailed budget justification
The related TOA spreadsheets above use a different accounting basis from R-2/P-40 detail. Their amounts are not assumed to match these detailed sources.
RDTE - Vol 4 - Budget Activity 6 · www.asafm.army.mil
PDF page 261
RDTE - Vol 3 - Budget Activity 5A · www.asafm.army.mil