Global Command and Control System

Abstract

Based on the termination of the Net Enabled Command Capability (NECC) Program and the renewed focus on the existing Global Command and Control System – Joint (GCCS-J), this submission reflects the shift in the GCCS-J program from funding only the GCCS-J Program Management Office (PMO) activities to sustaining a portfolio of Joint command and control (C2) activities within DISA in support of the overall Department. These Joint C2 activities include GCCS-J, Joint Planning and Execution Services (JPES), and the support to the development and sustainment of the Joint C2 architecture. GCCS-J. The GCCS-J suite of mission applications/systems provides critical joint warfighting C2 capabilities by presenting an integrated, near real-time picture of the battle space for planning and execution of joint military and multinational operations. GCCS-J is used by all nine combatant commands (COCOMs) at sites around the world, supporting joint and coalition operations. Additionally, through the continued evolution of the GCCS Family of Systems (FoS), the Services are also utilizing components of the GCCS-J infrastructure to build their Service unique variants thus reducing the number of unique components. Funding will be used to evolve existing capabilities within the GCCS-J operational baselines with the goal of reducing cost to the field through the use of enterprise hosting and increasing data sharing through the availability of common services, while enhancing the existing functionality available to the user today. GCCS-J entered into sustainment with the closeout of Block V in August 2009. JPES. JPES (formerly known as Adaptive Planning and Execution (APEX) is a set of capabilities that address components of the DoD’s Adaptive Planning Roadmap (13 December 2005) and Adaptive Planning Roadmap II (5 March 2008). JPES produces enhancements to the Joint Operations Planning and Execution System (JOPES), focused adaptive planning capabilities, and an integrating framework intended to provide the warfighter a fully interoperable objective adaptive planning and execution system solution. Joint C2 Architecture. The Joint C2 Architecture is a foundational element of the Joint C2 capabilities for the Department, containing a set of net-centric tenets associated with data, functional service and the C2 infrastructure that is based on a Service Oriented Architecture (SOA) design pattern. Each year, the DISA architecture team produces a transitional architecture that documents the current state of C2 capabilities and anticipated changes/enhancements either in progress or planned by the C2 community. The yearly updates document the use of enterprise services and standards in the development, integration and implementation of Joint C2 capabilities across the Department. The GCCS-J Overseas Contingency Operations for Integrated Imagery and Intelligence (I3) provides operational enhancements to the existing GCCS-J I3/Common Operating Picture (COP) baseline in direct support of United States Central Command (USCENTCOM) identified requirements. This includes access to additional data sources or tracks, ensures visualization of this intelligence data on the COP, and enhancements to capabilities unique to the USCENTCOM Area of Responsibility (AOR). The Collaborative Force Analysis Sustainment and Transportation (CFAST) portal was the primary adaptive planning operational prototype capability. Due to operational issues, CFAST was cancelled on 30 June 2009. The DoD examined various strategies for providing a replacement adaptive planning capability. Adaptive Planning and Execution (APEX, which later became JPES (see above)) is the DoD's replacement methodology for constructing timely and agile war plans that achieve national security objectives. APEX is a suite of software tools that provides Adaptive Planning (AP) capabilities to include: campaign planning, forecast predictions, information management, and rapid execution. Currently the Department of Defense has several operational capabilities and systems that provide functionality to support the APEX business process.

Document Details

• Document Type: R2 Budgetary Justification
• Publication Date: Oct 01, 2012
• Source ID: 0303150K_7_0400_PB_2012
• Change Summary Explanation: The FY 2010 decrease in funding of -$0.049 is due to the shifting of priorities to meet new Departmental goals. The FY 2012 base increase of +$27.759 provides funding to support four requirements: Technical refresh of the GCCS-J system due to Commercial off the Shelf (COTS) and Hardward (HW) being obsolete. This is an issue because of the longer life cycle required with the termination of the NECC program. Family of Systems (FoS) interoperability between GCCS-J and the Service GCCS systems and external applications necessary to provide the Joint Operator with relevant and timely data. Accelerated development of the JPES applications to support critical adaptive planning activities. Implementation of GFM DI data within the GCCS-J system to support current operational needs to access and view enhanced tracks and data. The FY 2012 includes a $2.000 million request to fund OCO requirements.
• Service Agency Name: Defense Information Systems Agency

Entities

Organizations

• Defense Information Systems Agency

Tags

Communities of Interest

• C4I

DTIC Thesaurus Topics

• Acquisition
• Combatant Commanders
• Command And Control
• Command And Control Systems
• Command Centers
• Contingency Operations (Military)
• Contracts
• Control Systems
• Cross Domain
• Department Of Defense
• Information Systems
• Infrastructure
• Software Development
• Test And Evaluation
• Unified Combatant Commands
• United States
• United States Central Command

Fields of Study

• Computer science
• Engineering

Readers

• Enterprise Information Systems Architecture and Joint Command Capability Interoperability Support.

Technology Areas

• Fully Networked C3
• Fully Networked C3 - Command and Control
• Space