The Largest Security-Cleared Career Network for Defense and Intelligence Jobs - JOIN NOW


Global Command and Control System (GCCS)

Primary Purpose GCCS is the nation's premier system for the

command and control of joint and coalition

forces. It is a distributed, client-server based

architecture that incorporates a Common Operating

Environment (COE) infrastructure with interfaces

that support the hosting and execution of

heterogeneous applications. GCCS incorporates the

force planning and readiness assessment

applications required by battlefield commanders

to effectively plan and execute military

operations. The Common Operational Picture (COP)

application within GCCS correlates and fuses data

from multiple sensors and intelligence sources

to produce a graphical representation of the

battlespace in order to provide commanders with

the situational awareness necessary for rapid,

effective decision-making. GCCS also provides an

extensive suite of integrated office automation,

messaging, and collaborative applications. GCCS

replaced the World Wide Military Command and

Control System (WWMCCS).

Sub-Functions GCCS currently uses 209 system applications to

create the COE used to facilitate

interoperability between stand alone operational

systems and the GCCS terminal. A list of current

system applications include:

AdHoc Query (AHQ)

Adobe Acrobat Reader

Airfields Database (AIRFDB)

Air Force Option 4 (AFOPT4)

APPLIX Office Products

Audio TLCF Tool

Automated Message Handling System (AMHS)

Collaborative Planning, Modeling & Simulation


Command and Control Personal Computer (C2PC)

Computer Misuse and Detection System (CMDS)

COP Embedded Training

COP Synchronization Tools

Enhanced Linked Virtual Information System


Evacuation System (EVAC)

Force Validation Tool (FVT)

Global Combat Support System (GCSS) Client

Global Positioning System (GPS) Time

Global Reconnaissance Information System (GRIS)

Global Status of Resources and Training Systems


GNU Zip Compression Utility (GZIP)

GRIS Web Interface (GRISWI)

GSORTS Readiness Assessment System (RAS) Input


GSORTS Readiness Assessment System (RAS) Output


Information Management Subsystems (IMS)

Internet Relay Chat (IRC)

Joint Deployable Intelligence Support System


Joint Engineer Planning and Execution System

(JEPES) Client

Joint Force Requirements Generator II (JFRG II)

Joint Mapping Tool Kit (JMTK)

Joint Operations Planning and Execution System


JOPES Editing Tool (JET)

JOPES Navigation (JNAV)

Joint Tactical Interface Module

Logistics Sustainment Analysis and Feasibility

Estimator (LOGSAFE) Client

Medical Analysis Tool (MAT)

METOC Tactical Forecast System (TFS)

Microsoft FrontPage 98

Microsoft NetMeeting

Microsoft Office 97

MTF Editor

Near Real Time Intelligence GENSER (NRTIG)

Netscape News Server

Netscape Web Browser
Network Information Service Plus (NIS+) Group
Newsgroups and Internet News
ORACLE Relation Database Management System (ORACLE RDBMS)
Predefined Reports Database
Real Property Inventory Database
Remote Dialup (AT&T STU III)
Rapid Query Tool (RQT)
Requirements Development Analysis (RDA)
Reference File Administration (RFA)
Rendezvous Whiteboard Client
Scheduling and Movement (S&M) Client
Seagate Backup
Secret Agent (AT&T)
Security Alignment Tool (SALIGN)
System Services Client
Sun Java Runtime Environment (SUNJRE)
Tactical Information Broadcast System (TIBS)
Theater Ballistic Missile Defense (TBMD)
Theater Ballistic Missile Warning and Display
TPEDIT Database
Unified Build (UB) Core
Video TLCF Tool

Equipment Requirements UNIX and Microsoft Windows NT.

(NT Client Guidance) To effectively run a

Windows NT 4.0 environment within the Defense

Information Infrastructure (DII) Common Operating

Environment (COE) and GCCS, specific hardware

capabilities are required. Minimum system

requirements for GCCS NT client workstations are

as follows:

Pentium 233 MHz processor or equivalent;

64MB Synchronous Dynamic Random Access Memory

(SDRAM) Dynamic Integrated Memory Module (DIMM);

Video Graphics Array (VGA) graphics card with 4MB

of Video Random Access Memory (VRAM) on board

and capable of supporting 1024 x 768 x 64 million

colors video resolution;

NE2000 compatible network adapter with RJ-45

connector in Industry Standard Architecture (ISA)


2GB Enhanced Integrated Drive Electronics (EIDE)

hard drive;

24x CD-ROM EIDE drive;

3.5" High Density (HD) Floppy Disk Drive;

AT Extended (ATX) form factor motherboard with

four PCI slots available;

ATX CPU case;

Three button mouse;

17 inch VGA Monitor (supporting minimum

resolution listed above); and

16-bit sound card with externally amplified


Recommended system requirements for GCCS NT

client workstations are as follows:

Pentium 400 MHz processor or equivalent;


Super Video Graphics Array (SVGA) graphics card

with 8MB of VRAM on board with Advanced Graphic

Port (AGP) slot;

Network adapter with RJ-45 connector in PCI slot

capable of 10/100 Mbps with auto-sensing feature;

4GB or larger Ultra Direct Memory Access (UDMA)

EIDE hard drive;

32x Compact Disk CD-ROM EIDE drive;

3.5 inch HD Floppy Disk Drive;

ATX form factor motherboard with four PCI and one

AGP slot available;

ATX CPU case;

Three-button mouse;

19 inch SVGA Monitor; and

32-bit sound card with externally amplified


Connectivity Requirements Ethernet (TCP/IP) client-server environment.

T1/T3 backbone.

Crypto Requirements The Network Encryption System (NES) is used for

garrison sites and connects to the T1 / T3

backbone. KG-194s are used in tactical

environments. GCCS must be connected to the

SIPRNET or a secure Local Area Network (LAN).

Normal Locations GCCS sites are located at all levels of the

military command structure to include; National

Command Authorities (NCA), the National Security

Agency (NSC), the Joint Chiefs of Staff (JCS),

service headquarters, Commanders in Chiefs

(CINCs), subordinate commanders, major

operational units, and government Agencies such

as the Central Intelligence Agency (CIA), Federal

Bureau of Investigation (FBI), and the Federal

Emergency Management Administration (FEMA). GCCS

liaison cells can be provided to coalition

partners, United Nations (UN), and

Non-governmental Organizations during

humanitarian or peacekeeping operations.

Information Managed GCCS manages information dealing with force

deployment, unit positions, force status,

intelligence, fire support, personnel, air

operations, logistics, narrative information, and

crisis and deliberate planning.

Products Created Common Operating Picture (Air, Land, Maritime).

Time Phase Force Deployment Data (TPFDD). Many

other products created by over 200 applications.

Lead Service/Contractor Joint Program. OASD (C3I) is the Milestone

Decision Authority (MDA) for GCCS; Joint Staff

(J3) is the Office of Primary Responsibility

(OPR) for GCCS; DISA is the Program Manager and

Lead Engineering Office for GCCS. MCTSSA (Camp

Pendleton, CA) is the Marine Corps Help Desk for

GCCS and MAGTF C4I systems, as well the contract

manager for Post Deployment Software Support


Current Fielding Status 625 GCCS sites worldwide. DISA anticipates

complete fielding by year 2003.

Known Problems Need to decrease number of major database sites

in order to enable better

synchronization/validity of data while still

supporting the user. Integration of GCCS function

requirements. Software licensing agreements

continue to be a problem; need to streamline

acquisition so all services benefit rather than

individual services performing acquisition for

same software licenses. Individual services

acquisitions are not currently funded equally.

DIICOE Compliance Rating The Defense Information Infrastructure (DII)

Common Operating Environment (COE) concept is

best described as: an architecture that is fully

compliant with the DOD Technical Architecture for

Information Management (TAFIM), Volume 3, an

approach for building interoperable systems, a

reference implementation containing a collection

of reusable software components, a software

infrastructure for supporting mission-area

applications, and a set of guidelines, standards,

and specifications.

Platform hardware, application software, and API

software must meet various levels of DII COE

compliance before being added to GCCS. Once

added, hardware and software will be redefined

until they reach full compliance (DII COE Level


Point of Contact LtCol Dave Bither, USA, at Comm (703) 735-8185 or

DSN 635-8185,

Updated by Capt Steven Bowers, USMC, CCSC-01





Join the mailing list

One Billion Americans: The Case for Thinking Bigger - by Matthew Yglesias