Skip to content
Fiscal Receipts

UAS Integration and Interoperability

NavyRDT&EReconciledPE0305205N
What it is
UAS Integration and Interoperability (0305205N) is a Navy research & development line funded in the Research, Development, Test and Evaluation, Navy account. Its J-book detail breaks the line into 1 project.
What changed
No FY25→26 comparison — endpoints unavailable or on different bases.
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
$12.7MR-1 TOA · PB2026
FY25 Enacted
$0J-book detail · PB2026
FY26 Request
$0J-book detail · PB2026
FY25→26 Change
No comparison: endpoints unavailable or on different bases

No FY2026 R-1/P-1 request line for this program element. The FY2026 President's Budget request workbook carries no FY2026 line for it; its last workbook figure is FY2024. The PB2026 J-book detail below does carry an FY2026 row for this line, recorded as zero. A workbook blank and a documented zero are different records, and this page shows both. An absent line is not by itself an ending — PB2026 renumbered program elements at scale across the services and defense agencies, so this work may continue under a different number. No successor is linked for this line: this site's program-lineage layer holds no keyed edge pointing forward from here. That is an absence in this site's lineage layer, not a finding about the program: if the J-book narrative on this page describes a realignment, it is quoted below in the document's own words, and this note does not restate it.

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 lower 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 lower 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: $12.7MFY25: $0FY26: $0FY24FY25FY26
Budget trajectory: one row per fiscal year, carrying the summary figure the sparkline plots. Every figure opens its own citation.
Fiscal yearAmount
FY24$12.7MR-1 TOA · PB2026
FY25$0J-book detail · PB2026
FY26$0J-book detail · 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

10 fiscal years of this program as published (FY2015–FY2024): 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.
10 fiscal years of this program as published (FY2015–FY2024): 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.FY2015 actuals — PB2017 editionFY2016 actuals — PB2018 editionFY2017 actuals — PB2019 editionFY2018 actuals — PB2020 editionFY2019 actuals — PB2021 editionFY2020 actuals — PB2022 editionFY2021 actuals — PB2023 editionFY2022 actuals — PB2024 editionFY2023 actuals — PB2025 editionFY2024 actuals — PB2026 editionFY2016 enacted — PB2017 editionFY2017 enacted — PB2018 editionFY2018 enacted — PB2019 editionFY2019 enacted — PB2020 editionFY2020 enacted — PB2021 editionFY2021 enacted — PB2022 editionFY2022 enacted — PB2023 editionFY2023 enacted — PB2024 editionFY2024 enacted — PB2025 editionFY2017 request — PB2017 editionFY2018 request — PB2018 editionFY2019 request — PB2019 editionFY2020 request — PB2020 editionFY2021 request — PB2021 editionFY2022 request — PB2022 editionFY2023 request — PB2023 editionFY2024 request — PB2024 editionFY15FY16FY17FY18FY19FY20FY21FY22FY23FY24

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.
SeriesFY15FY16FY17FY18FY19FY20FY21FY22FY23FY24
Actuals$0$42.2M$21.5M$20.8M$24.2M$37.7M$61.2M$4.84M$15.1M$12.7M
Enacted$41.8M$36.5M$39.7M$24.7M$40.4M$61.2M$5.00M$15.4M$16.4M
Request$36.5M$39.7M$41.2M$42.3M$62.1M$9.80M$18.4M$16.4M

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

Asked vs spent: the PB2018 book requested $39.7M for FY2018; the PB2020 book reported $20.8M as actual total obligation authority — $18.9M below the request. 20.8 − 39.7 = -18.9 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 — UAS Integration & Interoperability

Unmanned Aircraft Systems (UAS) Integration and Interoperability funding supports the development of solutions for Command and Control (C2) and interoperability of UAS platforms across the Naval Aviation Enterprise (NAE). Project 3379: All Common Control System (CCS) efforts for Autonomy and Executive Control of multiple unmanned aircraft previously funded under PU 3379 have been transferred to PU 1993 - "Architect and Cap for Autonomy in the Naval Enterprise (ARCANE). This budget profile supports executive control of multiple unmanned aircraft through the development of an autonomy architecture for Naval Aviation platforms. This is an extension of the line of effort established by Common Control System (CCS) (Project 3379), expanding into autonomy and capabilities aligned with the National Defense Strategy. New PU established for clarity. Project 1993: Architecture and Capabilities for Autonomy in the Naval Enterprise (ARCANE) budget profile supports executive control of multiple unmanned aircraft through the development of an autonomy architecture for Naval Aviation platforms. This is an extension of the line of effort established by Common Control System (CCS) (Project 3379), expanding into autonomy and capabilities aligned with the National Defense Strategy. New PU established for clarity. The CCS program was redirected in FY21 to focus on autonomy, executive control, artificial intelligence, and machine learning for Unmanned Systems (UxS) systems. This direction was consistent with decisions to implement existing solutions for UAS control, while continuing to advance development in valid requirements captured in the CCS requirements document. Under this new direction the program is operating under the name ARCANE. JUSTIFICATION FOR BUDGET ACTIVITY: This program is funded under OPERATIONAL SYSTEMS DEVELOPMENT because it includes development efforts to upgrade systems that have been fielded or have received approval for full rate production and anticipate funding in the current or subsequent fiscal year. Program termination starting in FY25.

Mission — Architecture and Capabilities for Autonomy in the Naval Enterprise (ARCANE)

Architecture and Capabilities for Autonomy in the Naval Enterprise (ARCANE) budget profile supports executive control of multiple unmanned aircraft through the development of an autonomy architecture for Naval Aviation platforms. This is an extension of the line of effort established by CCS (Project 3379), expanding into autonomy and capabilities aligned with the National Defense Strategy. New PU established for clarity. The CCS program was redirected in FY21 to focus on autonomy, executive control, artificial intelligence, and machine learning for Unmanned Systems (UxS) systems. This direction was consistent with decisions to implement existing solutions for UAS control, while continuing to advance development in valid requirements captured in the CCS requirements document. Under this new direction the program is operating under the name ARCANE. As part of this transition in focus, the ARCANE program is moving forward under the DoD Adaptive Acquisition Framework Software Acquisition Pathway. This pathway will allow the program to be more responsive to the autonomy needs of Naval Aviation platforms and allow for more efficient delivery of incremental capability. An Acquisition Decision Memorandum authorizing ARCANE to enter the Planning Phase of the Software Acquisition Pathway was signed by the Decision Authority in Q3 FY2023. A draft acquisition strategy has been developed and will continue to be refined throughout the Planning Phase. The ARCANE program will be a provider of autonomous capability solutions for Naval Aviation systems in order to provide interoperability between unmanned and autonomous Naval Aviation platforms, achieving integrated warfighting capability. ARCANE will consist of a common autonomy architecture framework; a process to enable Naval Aviation platforms to identify, achieve, and sustain autonomy needs; and a repository of autonomous behaviors developed for all ARCANE implementations across the Naval Aviation Enterprise (NAE). ARCANE will establish the autonomy enterprise architecture that supports the high-end fight and reduces impact on platform and OEM schedule / business arrangements. Autonomous capabilities will reduce cognitive decision-making workload and required operator actions to maximize warfighting impact in future "great power competition." The Software Acquisition Pathway will provide for the growth of autonomy-enabled capabilities at software pace, not traditional acquisition pace. Concurrent with enterprise-level work on standards and architectures, the ARCANE program will transition the autonomy elements of the AVATAR Manned-Unmanned Teaming (MUM-T) program, fielding an initial MUM-T capability. The foundational autonomy elements of the MUM-T capability will also serve as the starting point for additional autonomy solutions for the NAE. Establishment of the initial MUM-T warfighting capability will be dependent on partner program integration, within that partner's resourcing approach and acquisition strategy. The ARCANE Acquisition Strategy is in revision in accordance with the redirection in the program to focus on autonomy, executive control, artificial intelligence, and machine learning for UxS systems and continuing to reduce barriers to integration of Government-owned software services. Program termination starting in FY25.

Justification

No accomplishments or planned-program narratives in this line's J-book detail — some exhibits carry figures without per-project prose.

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, NavyNFY24 Actuals$12.7M

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$12.7M$0$0$0
1993: Architecture and Capabilities for Autonomy in the Naval Enterprise (ARCANE)$0$12.7M$0$0$0

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 UAS Integration and Interoperability. 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.