Global Command and Control System: Difference between revisions

Revision as of 23:04, 7 June 2024

Latest revision as of 07:45, 8 August 2025

(5 intermediate revisions by 5 users not shown)

Line 3:

==History==

[[File:US Navy 041016-N-1513W-052 Operations Specialist^rsquo,sSpecialists monitor Global Command Control Systems (GCCS) in the Combat Direction Center (CDC).jpg|thumb|left|[[Operations Specialist (United States Navy)|Operations Specialists]] monitor (GCCS) in the [[Combat Direction Center]] (CDC) aboard the Nimitz-class aircraft carrier [[USS John C. Stennis (CVN-74)|USS ''John C. Stennis'' (CVN-74)]].]]

GCCS evolved from earlier predecessors such as TBMCS (Theater Battle Management Core Systems), Joint Operations Tactical System (JOTS), and Joint Maritime Command Information System (JMCIS). It fulfilled requirements for technological, procedural and security improvements to the aging [[Worldwide Military Command and Control System]] (WWMCCS) plus its [[Tempest (codename)|TEMPEST]] requirement of Cold War defenses from wiretapping and electromagnetic signal interception that include physical (special wire and cabinet shielding, double locks) and operational (special access passes and passwords) measures. On August 30, 1996, the Defense Information Systems Agency (DISA) officially decommissioned WWMCCS and the Joint Staff declared the Global Command and Control System (GCCS) as the joint command and control system of record.<ref>{{cite web |url=http://www.fas.org/nuke/guide/usa/c3i/gccs.htm |title=GCCS |accessdate=2012-10-19 |archive-date=2013-02-15 |archive-url=https://web.archive.org/web/20130215050652/http://www.fas.org/nuke/guide/usa/c3i/gccs.htm |url-status=live }}</ref>

==Applications, Functionalityfunctionality==

GCCS systems comprise various data processing and [[web services]] which are used by many applications supporting combat operations, troop/force movements (JOPES), intelligence analysis and production, targeting, ground weapons and radar analysis, and terrain and weather analysis. Some next-generation applications designed for GCCS may support collaboration using chat systems, newsgroups, and email. (See JOPES, Mob/ODEE, etc.)

Line 15:

GCCS may use [[NIPRNet]], [[SIPRNet]], [[Joint Worldwide Intelligence Communications System|JWICS]], or other [[Internet Protocol|IP]] based networks for connectivity. In some installations, GCCS aggregates over 94 different sources of data.<ref>{{cite web |url=http://www.govexec.com/features/0606-01/0606-01s3.htm |title=Netcentric In a Snap |accessdate=2008-07-06 |archive-date=2008-07-25 |archive-url=https://web.archive.org/web/20080725053723/http://govexec.com/features/0606-01/0606-01s3.htm |url-status=dead }}</ref>

==Components/Variantsvariants==

* GCCS-A [[United States Army|Army]]

* GCCS-AF [[United States Air Force|Air Force]]

Line 21:

* GCCS-J [[United States Marine Corps|Marine Corps]], [[United States Joint Forces Command|Joint Forces]]

* GCCS-M (Maritime) ([[United States Navy|Navy]], [[United States Coast Guard|Coast Guard]])

The Navy's life cycle development of what is currently referred to as the Global Command and Control System, was and continues to be evolutionary in nature and will probably never result in a permanent system. From the early 1980s when SPAWARs PD-40 VADM Jerry O. Tuttle's Joint Operations Tactical System was the premier system, through the tenure of VADMRADM John Gauss's Joint Maritime Command Information System (JMCIS), the final product would be realized as the Global Command and Control System (GCCS), introduced conceptually by the Defense Information Systems Agency (DISA).

==See also==