Skip to content
Fiscal Receipts

Open Architecture Management

Air ForceRDT&EReconciledPE0605056F
What it is
Open Architecture Management (0605056F) is an Air Force research & development line funded in the Research, Development, Test and Evaluation, Air Force account. Its J-book detail breaks the line into 1 project.
What changed
+$2.93M FY25→26 R-1 TOA · PB2026
Who gets it
No company is linked to this line. Award records do not carry the program element, so the crosswalk is silent here — why.

Budget figures

FY24 Actuals
$34.2MR-1 TOA · PB2026
FY25 Total
$41.2MR-1 TOA · PB2026
FY26 Request
$44.1MR-1 TOA · PB2026
FY25→26 Change
+$2.93MR-1 TOA · PB2026
Data coverage

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

The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends higher than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.
The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends higher than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.FY24: $34.2MFY25: $41.2MFY26: $44.1MFY24FY25FY26
Budget trajectory: one row per fiscal year, carrying the summary figure the sparkline plots. Every figure opens its own citation.
Fiscal yearAmount
FY24$34.2M
FY25$41.2M
FY26$44.1M

All series figures: R-1 TOA · PB2026

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

9 fiscal years of this program as published (FY2018–FY2026): a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line rises across the span. The grid below is the same data as text, one cited figure per cell.
9 fiscal years of this program as published (FY2018–FY2026): a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line rises across the span. The grid below is the same data as text, one cited figure per cell.FY2018 actuals — PB2020 editionFY2019 actuals — PB2021 editionFY2020 actuals — PB2022 editionFY2021 actuals — PB2023 editionFY2022 actuals — PB2024 editionFY2023 actuals — PB2025 editionFY2024 actuals — PB2026 editionFY2019 enacted — PB2020 editionFY2020 enacted — PB2021 editionFY2021 enacted — PB2022 editionFY2022 enacted — PB2023 editionFY2023 enacted — PB2024 editionFY2024 enacted — PB2025 editionFY2025 enacted — PB2026 editionFY2020 request — PB2020 editionFY2021 request — PB2021 editionFY2022 request — PB2022 editionFY2023 request — PB2023 editionFY2024 request — PB2024 editionFY2025 request — PB2025 editionFY2026 request — PB2026 editionFY18FY19FY20FY21FY22FY23FY24FY25FY26

The vertical scale does not start at zero: the baseline sits just below this program’s smallest year, so a low point on this line is not a small amount. Read the shape for direction and the grid below for the figures.

● actuals (line)  ·  ○ enacted  ·  ◇ request — gaps are editions the program is absent from, never interpolated.

Decade series values by fiscal year and President's Budget edition: one row per series (actuals, enacted, request), one column per fiscal year. Every figure opens its own citation.
SeriesFY18FY19FY20FY21FY22FY23FY24FY25FY26
Actuals$0$0$28.9M$29.7M$36.2M$37.3M$34.2M
Enacted–$0$30.0M$30.5M$37.1M$38.2M$36.6M$41.2M
Request––$30.0M$30.5M$37.1M$38.2M$36.6M$41.2M$44.1M

blank = series not published for this year; – = absent from that edition.

Asked vs spent: the PB2024 book requested $36.6M for FY2024; the PB2026 book reported $34.2M as actual total obligation authority — $2.34M below the request. 34.24 − 36.58 = -2.34 USD millions — the compact figures above are rounded for reading.

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 — Standards Management

The Open Architecture Management (OAM) program element (PE) funds Modular Open Systems Approach (MOSA) maturation and its adoption by weapon systems across the Department of the Air Force (DAF) and the Department of Defense (DoD). Weapons systems that implement MOSA standards streamline integration of capabilities, reduce development timeline, lower life-cycle cost, reduce vendor-lock, and ensure interoperability with emerging capabilities. This enables weapon systems to field capabilities more rapidly and affordably in response to a dynamic threat environment. This budget funds the progression of Open Mission Systems (OMS), the Universal Command and Control Interface (UCI), and other emerging MOSA standards such as the Sensors Open System Architecture (SOSA). OMS is a non-proprietary, open architecture standard to create reusable and replaceable components that promote speed of integration for adopting weapons systems. The UCI is the DAF's messaging standard for mission-level Command and Control (C2), providing common message definitions to enable C2 coordination across sensors, vehicles, data products, and software. Funding supports development of new mission-critical OMS/UCI features requested by the 30+ operational adopting platforms across the DAF, DoD and international partners. Funding also supports experimentation, modeling, integration events, and studies to establish a common DAF MOSA approach. This includes leveraging commercial industry standards and government-driven standards. Additionally, funding supports alignment and interoperability across Government Reference Architectures (GRAs) and standards. These efforts use Agile methodologies and Development, Security, and Operations (DevSecOps) software practices to deliver products securely to adopting platforms and enable continuous feedback to improve the standards. Further, funding provides targeted technical exploration and risk reduction with adopting platforms to facilitate their MOSA adoption while identifying any changes required within the DAF's MOSA standards. In October 2024, the Open Architecture Management Office (OAMO) that managed this funding transitioned to the Architecture and Systems Engineering (ASE) group, Air Force Life Cycle Management Center (AFLCMC), Wright Patterson AFB. In addition to this PE, the ASE group will continue execution of these related activities under the following PEs: 0305206F / Airborne Reconnaissance Systems (672003 / Sensor Open Systems Architecture) 0604602F / Armament/Ordnance Development (655361 / Stores/Aircraft Interface) This program element may include necessary civilian pay expenses required to manage, execute, and deliver weapon system capability. The use of such program funds would be in addition to the civilian pay expenses budgeted in program element 0605829F, 0605831F, 0605833F, or 0605898F. This program is in Budget Activity 5, System Development and Demonstration (SDD) because it has passed Milestone B approval and is conducting engineering and manufacturing development tasks aimed at meeting validated requirements prior to full rate production.

Justification

Accomplishments & Planned Programs (1)

Open Architecture Management

Funding supports development of new mission-critical OMS/UCI features requested by the 30+ operational adopting platforms across the DAF, DoD and international partners. Funding also supports experimentation, modeling, integration events, and studies to establish a common DAF MOSA approach. This includes leveraging non-traditional industry standards and government-driven standards, such as the AFRL's Big Iron, and the "Horizontal Integration” approach (formerly known as Government Avionics Reference Architecture or GARA) effort to streamline integration across multiple architectures and standards. These efforts use agile methodologies and Development, Security, and Operations (DevSecOps) software practices to deliver products securely to adopting platforms and enable continuous feedback to improve the standards. Additionally, funding provides targeted technical exploration and risk reduction with adopting platforms to facilitate their MOSA adoption while identifying any changes required within the DAF's MOSA standards.

Budget line items(workbook-cited)

P-1/R-1 workbook Total Obligation Authority basis (USD thousands) · PB2026.

Exhibit R-1

AccountOrgTypeAmount
Research, Development, Test and Evaluation, Air ForceFFY24 Actuals$34.2M
Research, Development, Test and Evaluation, Air ForceFFY25 Enacted$41.2M
Research, Development, Test and Evaluation, Air ForceFFY25 Total$41.2M
Research, Development, Test and Evaluation, Air ForceFFY26 Disc. Request$44.1M
Research, Development, Test and Evaluation, Air ForceFFY26 Total$44.1M

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.

ProjectAll Prior YearsFY24 ActualsFY25 TotalFY26 BaseFY26 Request
Program Element$0$34.2M$41.2M$44.1M$44.1M
656060: Standards Management$0$34.2M$41.2M$44.1M$44.1M

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 Open Architecture Management. 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

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.