Roll-up of 3 projects. Projects are the summable leaves — the PE total is their sum, never added to it.
For fiscal year 2027, the U.S. Navy is requesting $120.8M for Cooperative Engagement Capability under RDT&E program element 0607658N, down 11% from FY2026.
Funding profile, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 138.7 |
| FY2026 | Enacted | 136.4 |
| FY2027 | Request | 120.8 |
| FY2028 | Outyear | 135.8 |
| FY2029 | Outyear | 131.4 |
| FY2030 | Outyear | 129.9 |
| FY2031 | Outyear | 132.3 |
Acquisition lifecycle
This program is funded in RDT&E Budget Activity 7 — Operational System Development.
3 projects roll up into PE 0607658N
Projects are the summable leaves — the PE total is their sum, never added to it. Program elements and projects carry the full five-year plan; activities stop at the budget year. This PE moves -11% overall, which can hide much larger swings below.
COOP Engagement
Navigation Systems
COOP is funded on 4 lines across 3 appropriations
This page shows $50.5M of COOP, 89% of the program's $56.6M FY2027 request. The rest is appropriated elsewhere.
| Also funded here | Type | Component | FY2027 $M |
|---|---|---|---|
| International Coop RDT&E | RDT&E | Navy | 3.5 |
| Nato Coop R&D | RDT&E | Air Force | 2.3 |
| Precision and Coop Weapons in a Denied Env Tech | RDT&E | Army | 0.3 |
| COOP total | Air Force, Army, Navy | 56.6 |
Lines whose title names the program. 28 further lines only mention COOP in their justification text — those fund something else and are deliberately excluded from the total.
Congressional marks
Committee marks on the FY2027 request. Adds and cuts are reconciled in conference before they become law.
Where the FY2027 request goes
Performers named in the R-3 exhibit, resolved into industry, government-lab, and unspecified shares. Budget-justification contract funding, not obligations.
| Where FY2027 funding flows | Share | $M |
|---|---|---|
| Industry primes | 16% | 18.9 |
| Government labs & warfare centers | 19% | 23.2 |
| Other / unspecified | 65% | 78.7 |
| FY2027 request | 100% | 120.8 |
Mission & acquisition strategy
Cooperative Engagement Capability (CEC) significantly improves Battle Force Anti-Air Warfare (AAW) capability by coordinating all Battle Force AAW sensors into a single, realtime, composite track picture to support integrated fire control. CEC distributes sensor data from each USMC Command Control Unit, US Navy Ship, and US Navy Aircraft, or Cooperating Unit (CU), to all other CUs in the battle force through a real-time, line of sight, high data-rate sensor and engagement data distribution network. CEC is highly resistant to jamming and provides accurate gridlocking between CUs.
Full Rate Production for CEC AN/USG-3B variant approved April 2014. Current version of CEC Acquisition Strategy (AS) approved by ASN (RDA) on 17 March 2023. Current version of CEC Acquisition Plan (AP) approved 03 May 2023. Contracts: CEC DA/ES Follow on sole source awarded Q1 FY 2025. For DA, the contractor will maintain the CEC hardware and software development environment and testing infrastructure including; Systems and Software Laboratories, the external RF Range, the Compact Antenna Range, and the CEC Classified Development LAN. For ES, the contractor will develop software implementing CEC capability improvements; support advanced studies and software and hardware integration; and perform CEC software sustainment and support.
- Product Development
Ask this program element
Answers are generated from the figures on this page — the FY2027 justification exhibits and the marks tracked above — and nothing else is consulted. Confirm any figure against the cited exhibit before you use it externally.
This page carries the budget justification and the NDAA marks — nothing else. For what NSMA has actually been obligated, the ledger is at hitchintel.com/vendors; for live solicitations, hitchintel.com/opportunities. Both are member surfaces.
Cite this page
/programs/0607658N.md · MCP mcp.hitchintel.com → budget_get_program_element, budget_get_cong_marksCEC Increment II — one RDT&E project inside PE 0607658N. Congressional marks are recorded on the program element, not on a project.
Project 3240 — CEC Increment II — requests $62.1M in FY2027, 51% of the $120.8M requested for program element 0607658N. Year over year it falls 10% against FY2026.
Project 3240 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 47.7 |
| FY2026 | Enacted | 69.1 |
| FY2027 | Request | 62.1 |
| FY2028 | Outyear | 69.2 |
| FY2029 | Outyear | 68.7 |
| FY2030 | Outyear | 68.3 |
| FY2031 | Outyear | 69.6 |
8 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
Begin transition to CEC BLK III capability feature development. Begin follow-on CEC BLK III software development efforts to expand CEC speed, acceleration, and altitude attributes for inclusion in the CEC Composite Tracking environment to address advanced and more stressing threats (hypersonics).
Begin transition to CEC BLK III capability feature development. Continue a cryptographic modernization effort for the Signal Data Processor (SDP), to include the continued development of a new Programmable Cryptographic Module (PCM), in support of the significant increase in cryptographic performance, to include a subset of Cryptographic…
Begin transition to CEC BLK III capability feature development. Begin follow-on CEC BLK III CEP and DDS software development efforts to expand the use of EW data within the CEC system, DDS network, and Composite ID processing.
Complete System Integration Testing (SIT). Complete integration and development of 'Patterns of Life' algorithms for inclusion in the CEC track picture to assist with identification of anomalies and events of interest.
Continue CEC BLK III software development efforts for CEC capability improvements outlined in the CEC Increment 2 CDD. Conduct CEC BLK III SRR and SFR.
Develop and mature prototype CEC system antenna waveform and communications technologies and architectures to be incorporated into future CEC system hardware including the Signal Data Processor and antenna. CEC system hardware modernization is required to provide increased waveform and communications technologies that support data rates…
Read the FY2027 plan →Continue CEC system hardware and software integration efforts. As incremental CEC Increment 2 software capabilities and system signal data processor and antenna technologies evolve, conduct the necessary integration efforts to meet requirements in the CEC Increment 2 CDD.
Read the FY2027 plan →What project 3240 buys
The Cooperative Engagement Capability (CEC) Increment 2 (Inc 2) Capability Development Document (CDD) evolves legacy CEC capabilities by enhancing the current Naval air defense and sensor network system capabilities through extension of kill chains, extension of communications Beyond Line of Sight (BLOS), expansion of composite track management capability-Joint and Force Level, expansion of network capacity, as well as expansion into other warfare mission domains. The CEC Inc 2 CDD integrates new sensor types and track data sources into the network, such as surface search radars and passive detection sensors, as well as relevant data from other networks. The CEC Inc 2 CDD provides a more complete, robust, and resilient situational awareness picture, composite identification, and Integrated Fire Control. It also accommodates more Cooperating Units with assured communications for Integrated Air and Missile Defense, Surface Warfare, and Electronic Warfare domains. The CEC Inc 2 CDD was signed by Vice Chief of Naval Operations (VCNO) on 26 June 2019 and approved by the Joint Capabilities Board (JCB) on 18 March 2020. Although CEC BLK II is a Navy program, it does have joint force interest through potential inclusion in higher-level sensor-to-shooter networks like the Naval Tactical Grid (NTG), the Joint Tactical Grid (JTG), and Joint All Domain Command and Control (JADC2) concept and capability developments. New capability development designated in the CEC Inc 2 CDD will be realized through a series of Acquisition Category (ACAT) II Block (BLK) upgrades (BLK II-IV), with the first being enumerated as CEC BLK II. CEC BLK II is a software intesive capability insertion into the existing CEC ACAT IC Full Rate Production system. The new capability development within each BLK upgrade is further organized and phased into incrementally developed and delivered capability groups (CGs). Delivered CEC BLK II capability enabling features are grouped and integrated into CEC software baselines for fielding. The CEC Program has realigned RDT&E funding from PU 2039 COOP Engagement to PU 3240 CEC Increment 2 for the incremental development of CEC software and hardware improvements necessary to meet the requirements in the CEC Increment 2 CDD.
- Product Development
COOP Engagement — one RDT&E project inside PE 0607658N. Congressional marks are recorded on the program element, not on a project.
Project 2039 — COOP Engagement — requests $50.5M in FY2027, 42% of the $120.8M requested for program element 0607658N. Year over year it falls 16% against FY2026.
Project 2039 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 91.0 |
| FY2026 | Enacted | 60.1 |
| FY2027 | Request | 50.5 |
| FY2028 | Outyear | 58.2 |
| FY2029 | Outyear | 54.6 |
| FY2030 | Outyear | 53.3 |
| FY2031 | Outyear | 54.3 |
9 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
Continue software development and test for E-2D DSSC 5.X CEC software, including interface development and integration of new CEC capabilities, and of E-2D CEC networking, sensor, and tracker capability and performance improvements included in DSSC 5.X software and associated hardware. Conduct laboratory and flight test events for E-2D…
Continue DT-C1 of CEC Increment 2 Block II Capability Group 3 in multiple shipboard, airborne, and land mobile combat system configurations. Continue planning for DT-C2 of Increment 2 Block II capabilities. Complete OT-D3 of CEC AN/USG-2B on DDG 1000.
Read the FY2027 plan →Complete Agile Software Reviews and associated Systems Engineering Technical Review (SETR) events. Complete multiple CEC Product Release Panels (PRP) and Product Certification Panels (PCP) in support of CEC deliveries to Aegis, SSDS, DDG-1000, and E-2D platforms. Complete Integration, Testing, and Certification of Joint Track Management…
Continue field activity support of CEC development and fielding efforts (including Software Engineering/Integration Agent (SE/IA), Technical Direction Agent, In-Service Engineering Agent, Integrated Logistics Support planning) and program management support. Facilitate fielding of systems improvements and maintenance efforts.
Support robust system engineering and design activities, using results of Land Based, At-Sea, and Live Fire test events as feedback for the current design. Conduct assessment of NIFC functionality and assess any regression to legacy capability, and conduct systems engineering efforts to address required CEC design changes.
Provide CEC Program Protection support to manage risks from foreign intelligence collection threats to CEC hardware, software, or supply chain exploitation. CEC critical program information (CPI) is required to be protected with antitamper. The effort will further the use of anti-tamper protection within the program. CEC will work…
Continue integration of CEC Increment 2 Blk II capabilities with SSDS Baseline 12 and EASR baselines.
Continue execution of CEC Cyber Ready Lines of Effort, and regularly review Cyber Ready process enforcement. Continue reviewing CTT and field cybersecurity test results and developing and implementing cybersecurity risk mitigation capabilities based on test/analysis findings. Participate in combat system cybersecurity test events planned…
Named performers on project 2039
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 2039 buys
Cooperative Engagement Capability (CEC) significantly improves Battle Force Anti-Air Warfare (AAW) capability by coordinating all Battle Force AAW sensors into a single, realtime, composite track picture to support integrated fire control. CEC distributes sensor data from each USMC Command Control Unit, US Navy Ship, and US Navy Aircraft, or Cooperating Unit (CU), to all other CUs in the battle force through a real-time, line of sight, high data-rate sensor and engagement data distribution network. CEC is highly resistant to jamming and provides accurate gridlocking between CUs. Each CU independently employs high capacity, parallel processing and advanced algorithms to combine all distributed sensor data into a fire control quality track picture which is the same for all CUs. CEC data is presented as a superset of the best AAW sensor capabilities from each CU, all of which are integrated into a single input to each CU's combat weapons system. CEC significantly improves our Battle Force defense in depth, including both local area and ship defense capabilities against current and future AAW threats. Moreover, CEC provides critical connectivity and integration of over-land air defense systems capable of countering emerging air threats, including land attack cruise missiles, in a complex littoral environment. The CEC Program Office oversees CEC development for all services with funding provided for their respective combat systems. CEC consists of the Data Distribution System (DDS), the Cooperative Engagement Processor (CEP), and interface with Combat Systems and sensors. The DDS encodes and distributes own-ship sensor and engagement data and is a high capacity, jam resistant, directional system providing high data throughput as well common time and common positional frame of reference. The CEP is a high capacity distributed processor that processes data from all integrated radars. The data is passed to the ship's combat system as a high quality, common, continuous, engageable track. CEC operates in an increasingly contentious cyber-space. Measures are being taken to robustly mitigate, and where possible, completely remediate cyber vulnerabilities.
- Product Development
- Test and Evaluation
- Management Services
Navigation Systems — one RDT&E project inside PE 0607658N. Congressional marks are recorded on the program element, not on a project.
Project 3311 — Navigation Systems — requests $8.2M in FY2027, 6.8% of the $120.8M requested for program element 0607658N. Year over year it grows 13% against FY2026.
Project 3311 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 0.0 |
| FY2026 | Enacted | 7.2 |
| FY2027 | Request | 8.2 |
| FY2028 | Outyear | 8.4 |
| FY2029 | Outyear | 8.2 |
| FY2030 | Outyear | 8.2 |
| FY2031 | Outyear | 8.4 |
3 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them.
FY2027 planned work Conduct AN/WSN-12 EQT AN/WSN-12 LRIP first ship delivery Start Follow-On Development
FY2026 to FY2027 change Increase due to EQT, first ship delivery support, and start of follow-on development
FY2026 plans — current year Complete AN/WSN-12 EDM development AN/WSN-12 EDM delivery AN/WSN-12 EDM testing/element certification
FY2027 planned work Continue new speed sensor research and development
FY2026 to FY2027 change Decrease due to reduction of development scope
FY2026 plans — current year Continue new speed sensor research and development
FY2027 planned work Continue engineering, logistics, and programmatic support for AN/WSN-12 and SSS including system integration, testing, and evaluation at multiple land-based and shipboard sites
FY2026 to FY2027 change Decrease due to support requirement changes within various Navigation development efforts including systems integration, testing and evaluation at multiple land-based and shipboard sites.
FY2026 plans — current year Continue engineering, logistics, and programmatic support for AN/WSN-12 and SSS including system integration, testing, and evaluation at multiple land-based and shipboard sites
Named performers on project 3311
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 3311 buys
In FY26, Navigation Systems RDT&E transition from PE 0204228N to PE 0607658N. This was a zero-sum transition, there is no growth. The Surface Support RDT&E funding will be used for the research, design, development, integration, testing, and documentation of the Inertial Navigation System (INS) AN/WSN-12 for all Navy ships and submarines. The INS provides mission critical ship position and attitude data to shipboard sensors (such as radars), combat and weapon systems. The INS uses data from the Global Positioning System (GPS) to periodically update (i.e., reset) its position and internal clock. The INS is the ship's primary position source in the absence of GPS, and it consists of an Inertial Sensor Module (ISM) and a Navigation Processing Module (NPM) that will provide a significant improvement with respect to attitude and velocity data over previous INS. RDT&E funding will support continued system design to create a baseline for Pre-Production Units (PPU), Low Rate Initial Production (LRIP), and Full Rate Production (FRP). Submarine Speed Sensors will provide investigation, development, testing and integration of new Own-Ship Speed sensors to address new capabilities, reduce counter-detection, and improve reliability.
- Product Development
- Support