Printed from https://fiscalreceipts.com/program/0207611F/ — data as of July 28, 2026. Every figure is citation-backed; see the page online for per-number provenance.
Readiness Decision Support Enterprise
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 | $8.88M |
blank = series not published for this year; – = absent from that edition.
Program Lineage
No predecessor/successor lineage was recorded for this program element — no FY-to-FY transfer into or out of this line was stated in the ingested J-books, and none was inferred from the program structure.
Description
Mission — Defense Readiness Reporting System (DRRS)
This package incorporates RDT&E funds to maintain constant readiness landscape changes, which entail software changes, new requirements, etc. to Air Force DRRS-S. DRRS-S is an OSD platform providing readiness reporting capabilities to the DoD. The DRRS-S mission is to establish a mission focused, capabilities based, common framework that provides the combatant commanders, military services, Joint Chiefs of Staff, and other key DoD users a data-driven environment and tools in which to evaluate, in near real-time, the readiness and capability of the U.S. Armed Forces to carry our assigned and potential tasks. These assigned and potential tasks sometimes drive software changes and development specifically for the Air Force which require RDT&E funding to achieve the ability to measure readiness. One example would be the development of Combat Wing. This drives a new assessment framework which needs to be developed within DRRS-S so commanders can measure the readiness of combat wings as a single capability, which are different from the way the Air Force currently assesses readiness. By not having the development ability with the RDT&E funding, readiness reporting will not meet the needs of Joint Staff, Congress, Commanders, or any end users of Air Force Readiness data. MODIFY THE DEFENSE READINESS REPORTING SYSTEM TO SUPPORT ENCHANCE RESOURCE REPORTING FOR COMBAT WINGS: Air Force modifications to force presentation and organization requires modifications new capabilities in DRRS to allow for presented forces to reflect meaningful resource and capability ratings that fully encompass the entirety of capability packages. This change will allow the AF to present fully capability packages with a single resource rating informed by supporting unit ratings. This will provide key decision makers with decision quality data reflecting the full capability package. This is in addition to the current functional unit structure that requires deeper cross referencing to account for the full capability package. The system will combine resource data from multiple units (where reasonable) to reflect combat unit readiness informed by combat support and combat service support limits. MODIFY THE DEFENSE READINESS REPORTING SYSTEM AIR FORCE INPUT TOOL TO STREAMLINE REPORTING: The Air Force Input Tool module of DRRS is the interface by which Air Force units report Readiness. This effort streamlines the input process with structured in-system guidance to increase data quality. This effort utilizes robust tools to summarize unit resources for assessors and direct both qualitative and quantitative inputs to generate, value and risk to assigned capabilities and missions. The end state provides robust qualified Readiness data that highlights resource impacts to specific capabilities. MODIFY THE DEFENSE READINESS REPORTING SYSTEM AIR FORCE INPUT TOOL TO SUPPORT ENHANCED ANALYITCS: Updating the Air Force Input Tool to align reported resources to specific capability elements and support advanced analytics that reflect detailed data impact to specific resource shortfalls. Additionally, this effort will support ‘what if' reporting to provide AF leadership with preliminary evaluations given proposed Courses of Action (COA) options. This program is in Budget Activity 7, Operational System Development because this budget activity includes development efforts to upgrade systems that have been fielded or have received approval for full rate production and anticipate production funding in the current or subsequent fiscal year.
Justification
Accomplishments & Planned Programs (1)
Defense Readiness Report System - Strategic
Readiness Reporting Software Development
Budget Line Items(workbook-cited)
Exhibit R-1
| Account | Org | Type | Amount |
|---|---|---|---|
| Research, Development, Test and Evaluation, Air Force | F | FY26 Disc. Request | $8.88M |
| Research, Development, Test and Evaluation, Air Force | F | FY26 Total | $8.88M |
Budget Details(R-2/P-40 facts)
| Project | All Prior Years | FY24 Actuals | FY25 Total | FY26 Base | FY26 Request |
|---|---|---|---|---|---|
| 675273: Defense Readiness Reporting System (DRRS) | $0 | $0 | $0 | $8.88M | $8.88M |
| Program Element | $0 | $0 | $0 | $8.88M | $8.88M |
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? →