| | Global Command & Control System - Maritime (GCCS-M) |
| | Primary Purpose | The Global Command and Control System -Maritime |
| | (GCCS-M) is the Navy's single command and control |
| | program-of-record that integrates and interfaces |
| | over 80 separate C4I systems providing naval |
| | commanders afloat and ashore a near-real-time |
| | Common Operating Picture (COP). GCCS-M enhances |
| | the operational commander's warfighting |
| | capability and aids in the decision-making |
| | process by receiving, retrieving, and displaying |
| | information to allow warfighters to plan, |
| | coordinate, exercise, execute and evaluate naval |
| | and joint operations. GCCS-M is an open-ended |
| | architecture system consisting of servers, |
| | workstations, routers, hubs, and encryption |
| | devices, and integrates information from multiple |
| | C4I functional areas. |
| | Sub-Functions | GCCS-M (Afloat), GCCS-M (Ashore), GCCS-M |
| | (Tactical Mobile Variants - Mobile Ashore Support |
| | Terminal, Mobile Integrated Command Facility, |
| | Mobile Operations Command Center) and GCCS |
| | (Joint). |
| | Equipment Requirements | Currently a UNIX and Windows NT based platform. |
| | UNIX systems and Windows NT systems are |
| | interoperable. Migrating towards a primarily |
| | Windows based platform. |
| | Connectivity Requirements | Uses IP routing over the Secret Internet Protocol |
| | Routing Network (SIPRNET). Typically SHF SATCOM |
| | with inputs via UHF and HF. |
| | Crypto Requirements | No external equipment required. Primarily uses |
| | SIPRNET. |
| | Normal Locations | GCCS-M is located at both fixed and mobile |
| | locations: U.S. and NATO CINCs, U.S. Naval |
| | Installations, U.S. ships, and ashore tactical |
| | locations. |
| | Information Managed | TCO, IAS, AFATDS, JOPES, CTAPS, JOTS, NWSS, FHLT, |
| | OSS, TSC, STT, NIPS, TFCC, ACS, EWCM, POST, ATP, |
| | FTAS, ASCOMM, ASWOC, ATOS, MAST, MOCC, RMAST, |
| | MICFAC, OSIS. |
| | Products Created | An integrated common operating picture afloat and |
| | ashore. |
| | Lead Service/Contractor | U.S. Navy, Naval Warfare Systems Command |
| | (SPAWARSYSCOM) Program Directorate 15 (PD-15). |
| | Current Fielding Status | U.S., over 300 ships and submarines; 57 ashore |
| | sites, and 30 tactical variants. Marine |
| | Expeditionary Units are also using GCCS-M. |
| | Known Problems | Currently not directly interoperable with U.S. |
| | Army's GCCS-A. GCCS-M and GCCS-A are |
| | individually interoperable with GCCS. A fix is |
| | being developed. |
| | DIICOE Compliance Rating | Level 5. |
| | Point of Contact | SPAWAR, Navy Command and Control Program Office |
| | (PMW-157), 4301 Pacific Highway, San Diego, CA |
| | 92110-3127 (858) 537-0264. |
| CNO POC: Butorac, Diane M | |
| [Butorac.Diane@hq.navy.mil] (703) 601-1422 | |
| Updated by | LCDR Tom Wester, USN, CCSC-01 |
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
