What the FY2027 request buys
Verbatim from the R-2A exhibit for project CC01 of PE 0303150K. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
Sustainment Produce ongoing releases to sustain all GCCS-J baselines and continuously meet warfighter needs, keeping the systems current in accordance with JC2 Mission operational requirements, priorities, and the DoW’s JC2 Reference Architecture. Additional sustainment activities include: • Expand the SPINE footprint to additional Combatant Commands and increase system capabilities on-demand to support exercises and operations. • Continue to decompose applicable existing applications into services. • Continue cybersecurity patching and trouble ticket fixes for operational systems. • Continue to support, sustain, and maintain operationally fielded systems. • Limit local deployment by fielding as much capability to the enterprise as possible. • Continue to expose data and scale services to support enterprise implementation. • Continue to evolve more economical hardware and software architecture without impact to the operational user or Family of Systems or interface partners. Modernization Conduct the following modernization activities: • Strategic Platform Information Network Environment (SPINE): Deploy capabilities redeveloped or added in the C2 Global Logical Data Model (GLDM) in the DISA-run forward-deployed Joint Operational Edge (JOE) and Joint Operational Edge Coalition Environment (JOE-CE) cloud nodes. • GCCS-J Web/GCCS-J Cloud: Continue expansion of GCCS-J capabilities available via SIPRNet to more closely mirror on- premises GCCS-J capabilities. Enable import/export of GCCS-J overlays into and out of GCCS-J Web to enable shared planning and reduce duplicative workload. Increase the availability of granular details of track groups. • Zero Trust Architecture: Continue adoption of any Zero Trust elements not yet incorporated into all GCCS-J baselines. Incorporate DISA’s Enterprise Identity, Credential, and Access Management (E-ICAM) tool. • Core Backend Data Pipelines: Continue updating channels and data flows in preparation for out-year replacement of the legacy Integrated C4I Integrated Framework (ICSF) kernel to improve data flow (reduce latency) for ingesting, tagging, storing, correlating, fusing, associating, analyzing, displaying, and accessing data. Implement data tagging monitoring to ensure correct distribution of information among allies and enclaves by automating analysis of inputs. • Global Logical Data Model: Continue incremental replacement of capabilities in the legacy data model with rebuilt or new features using the modern, standardized yet flexible data model to improve interoperability and simplify (reduce costs of) future modernization efforts and to expand the ability to exchange data with a vastly wider array of data sources and consumers. • Container Orchestration: Containerize software components developed in the Command and Control (C2) Global Logical Data Model (GLDM) to improve system performance and enable easier future system upgrades. • Open Data Service Application Programming Interfaces (APIs): Expand use of standard bi-directional, CJADC2-compliant data service APIs to facilitate integration of future external data sources/recipients using open standards-based interfaces. • IPv6 Transition: Finalize development of an IPv6 operations model as mandated to run in an IPv6-only environment when IPv4 is no longer supported. • Joint Range Extension Applications Protocol (JREAP): Enable bilateral interface with the JREAP-C standard protocol and message structure to extend data link communication across longer distances without signal degradation. JREAP-C makes use of internet protocols to enable long-haul data transfer without reliance on specialized radio terminals. • Artificial Intelligence: Begin incorporation of artificial intelligence and machine learning in C2 data analysis, correlation, and fusion.
The increase of +$29.855 million from FY 2026 to FY 2027 is required to accelerate modernization of GCCS-J to meet Joint Staff and user community requirements. GCCS-J requires a new system architecture and data model, which will allow for development of microservices for quicker future capability enhancements and updates, support Zero Trust principles, IPv6 compatibility, cloud enablement, and compliance with the Department’s CJADC2 principles for enhanced interoperability and data sharing.
FY2025–FY2026: what came before
Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.
GCCS-J is continuing GCCS-J sustainment activities and beginning GCCS-J modernization. Development occurs in accordance with Joint C2 (JC2). Mission operational priorities and the Department’s JC2 Reference Architecture. Sustainment Produce ongoing releases to sustain GCCS-J and continuously meet warfighter needs. Additional sustainment activities include: • Field additional capabilities in response to validated user community requirements. • Decompose applicable existing applications into services. • Continue cybersecurity patching and trouble ticket fixes for operational systems. • Continue to support, sustain, and maintain operationally fielded systems. • Expose data and scale services to support an enterprise implementation. • Evolve more economical hardware and software architecture without impact to the operational user or Family of Systems or interface partners. • Field a Non-classified Internet Protocol Router Network (NIPRNet) GCCS-J offering to allow adopting units to coordinate humanitarian assistance and disaster relief operations with non-traditional information partners in emergencies without risking classified data spillage. Modernization Conduct the following modernization activities: • Strategic Platform Information Network Environment (SPINE): Field GCCS-J backend services in the DISA-run forward- deployed Joint Operational Edge (JOE) and Joint Operational Edge Coalition Environment (JOE-CE) cloud nodes alongside a third-party display system as a proof of concept in support of United States Indo-Pacific Command (USINDOPACOM) exercises. • GCCS-J Web/GCCS-J Cloud: Expand upon the capabilities of GCCS-J as a Secret Internet Protocol Router (SIPR) web application by increasing the breadth of services available to more closely mirror on-premises GCCS-J capabilities. Field missile warning capabilities currently residing within GCCS-J, so they may be shared with other C2 display systems. • Zero Trust Architecture: Adopt a Zero Trust architecture as mandated to improve system security and minimize risk of unauthorized access exploitation. • Core Backend Data Pipelines: Prepare for future replacement of the legacy Integrated C4I Integrated Framework (ICSF) kernel by updating channels and data flows to improve data flow (reduce latency) for ingesting, tagging, storing, correlating, fusing, associating, analyzing, displaying, and accessing data. • Global Logical Data Model: Begin incremental replacement of the current data model which is the product of years of system evolution on an as-needed basis. Implementation of a modern, standardized yet flexible data model will improve interoperability and simplify (reduce costs of) future modernization efforts. • Container Orchestration: Expand upon the limited containerization of software components to improve scalability, resiliency, performance, resource utilization, security, system installation/upgrade efficiency, and other areas. Containerization will also make future system upgrades easier as services are isolated from each other. • Open Data Service Application Programming Interfaces (APIs): Standardize bi-directional, CJADC2-compliant data service APIs to facilitate integration of future external data sources/recipients using open standards-based interfaces. • IPv6 Transition: Transition to an IPv6-only operations model as mandated to run in an IPv6-only environment when IPv4 is no longer supported.
Develop a GCCS-J migration and modernization strategy and execute sustainment activities that achieve the following GCCS-J Modernization objectives in accordance with Joint C2 (JC2) Mission operational priorities and the DoD’s JC2 Reference Architecture: • Continue to decompose applicable existing applications into services. • Continue Cyber Security patching and trouble ticket fixes for operational systems. • Continue to support, sustain, and maintain operationally fielded systems. • Limit local deployment and move as much to the enterprise as possible. • Continue to expose data and scale services to support an enterprise implementation. • Continue to evolve more economical hardware and software architecture without impact to the operational user or Family of Systems (FoS)/interface partners. Reduce overall sustainment cost through use of more cost effective and appropriate Commercial-off-the-Shelf (COTS) and Hardware (HW) products: • Evolve to increase use of agile development practices. • Consolidate clients and tools. Produce ongoing releases to sustain GCCS-J and continuously meet warfighter needs. Improve capability in accordance with the modernization strategy wherever possible within the sustainment budget.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 32.6 |
| FY2026 | Enacted | 44.5 |
| FY2027 | Request | 74.3 |
This activity is 60% of project CC01's FY2027 request and 60% of PE 0303150K's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
3 activities in project CC01
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the program-element page.