Printed from https://fiscalreceipts.com/program/4604/ — data as of July 28, 2026. Every figure is citation-backed; see the page online for per-number provenance.
Architect & Cap for Autonomy in Nav Enter (AR
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 FY24 available).
● actuals (line) · ○ enacted · ◇ request — gaps are editions the program is absent from, never interpolated.
| Series | FY22 | FY23 | FY24 |
|---|---|---|---|
| Actuals | $0 | – | $1.61M |
| Enacted | – | $0 | $1.61M |
| Request | – | – | $1.61M |
blank = series not published for this year; – = absent from that edition.
Asked vs spent: the PB2024 book requested $1.61M for FY2024; the PB2026 book reports $1.61M actually spent — $1.00K below the request.
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
Description — Architect & Cap for Autonomy in Nav Enter (ARCANE)
OPN funding is required to procure and sustain elements of the ARCANE (Architecture and Capabilities for Autonomy in the Naval Enterprise) software enterprise architecture, including software licenses, host hardware, and data center services. This is an extension of the line of effort established by Common Control System (CCS) (LI 4250), expanding into autonomy and capabilities aligned with the National Defense Strategy. New LI 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. ARCANE has requested entry into the Planning Phase of the Software Acquisition Pathway, and is routing for DA approval. 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 manned and unmanned Naval Aviation systems in order to provide interoperability between unmanned and autonomous Naval Aviation platforms. 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.
Justification
Justification — Architect & Cap for Autonomy in Nav Enter (ARCANE)
Program termination starting in FY25.
Budget Line Items(workbook-cited)
Exhibit P-1
| Account | Org | Type | Amount |
|---|---|---|---|
| Other Procurement, Navy | N | FY24 Actuals | $1.61M |
Budget Details(R-2/P-40 facts)
| Project | All Prior Years | FY24 Actuals | FY25 Total | FY26 Base | FY26 Request |
|---|---|---|---|---|---|
| Program Element | $0 | $1.61M | $0 | $0 | $0 |
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? →