I.G. DESCRIPTION OF NEW DEVELOPMENT
1. Functional Description. GCCS-M provides centrally-managed C4I services to the Fleet allowing both United States and allied maritime forces the ability to operate in network-centric warfare operations. GCCS-M is organized to support three different force environments: Afloat, Ashore and Tactical/Mobile forces as depicted in Figure E-1. Afloat configurations can be categorized as force-level and unit-level configurations. Ashore configurations of GCCS-M are located in fixed site Fleet and Tactical command centers as well as mobile rapid deploy command centers such as MICFACs, mobile command facilities designed to provide the CJTF commander with similar C4I capabilities when forward-deployed ashore. In order to allow for maximum interoperability among GCCS systems at all sites and activities (Afloat, Ashore and Tactical/Mobile), GCCS-M utilizes common communications media to the maximum extent possible. The Secure Internet Protocol Router Network (SIPRNET), Non-Secure Internet Protocol Router Network (NIPRNET) and the Joint Worldwide Intelligence Communication System (JWICS) provide the necessary Wide Area Network (WAN) connectivity. JMCOMS will provide the WAN connectivity for the Afloat and Tactical/Mobile GCCS-M systems. Operating "system–high" at the Secret and SCI security levels, both networks use the same protocols as the Internet. In addition to the SIPRNET operating at Secret/SCI security levels, GCCS-T supports collaborative planning at the National Command Authority level by providing Top Secret connectivity to a limited number of sites. OPLANS developed at NCA level can then be downgraded to secret for dissemination using SIPRNET.
Figure I-3 Conceptual GCCS-M LAN/WAN Architecture
Figure I-4 JMCIS Traditional Architecture |
 |
Figure I-5 GCCS-M Architecture |
|
Figure I-6 Future GCCS-M Architecture Goal |
|
a. Platform/Premise. The GCCS-M architecture onboard a ship or within a command will look much like the traditional JMCIS architecture. One of the most significant differences, however, will be the phased replacement of UNIX servers with Windows NT servers and UNIX client workstations with Windows NT clients. In order to avoid using both a GCCS-M PC and UNIX workstation to perform separate functions, the architecture will require a phased migration whereby segments are migrated in discrete groups (JUMPs). As shown in the diagrams in Figures I-4, I-5, and I-6 GCCS-M early phases will favor the migration of client segments, followed by the migration of server segments. Services will be provided in such a manner that users will be unaware of what platform is being used to generate requests or perform functions. Migration planning will be synchronized and coordinated with customers to facilitate the integration process.
b. DII COE. DISA/D6 Joint Interoperability and Engineering Organization (JIEO) is responsible for DII COE definition and evolution. All Joint and Service C4I systems are required to be fully DII COE compliant in order to achieve interoperability and to improve DoD C4I capabilities. The DII COE consists of a kernel, infrastructure services, and common support applications. Kernel components include the operating system and extensions, common desktop, software install and de-install tools, security extensions, and printer services. DII COE infrastructure services (horizontal common services) include RDBMS servers/clients (Informix, Sybase, Oracle), Web servers/clients (Netscape), Network Management, Message Profiling (GCCS, DMS), Office Automation (MS Office), and PC Services (Wabi, WinDD). Common support applications (vertical market services) include Mapping, Charting, Geodesic & Imagery (MCG&I), communications input and output, message encoding and decoding, correlation and fusion, and tactical data replication. Figure I-7 depicts the DII COE.
c. DII COE with Naval Extensions. The DII COE will be supplied as Government Furnished Items (GFI) from DISA. Upon receipt of the DII COE from DISA, unique Naval extensions will be applied, integrated and tested. The result will be a developer’s release of the DII COE with Naval extensions. The developer’s release will be the product that Naval segment developers use to perform the segment migration and to begin to develop appropriate training products.
Figure I-7 DII COE Architecture (click for more detailed view)
d. Major GCCS-M Component Systems
(1). GCCS-M System Afloat. The GCCS-M Afloat C4I System (formerly known as NTCS-A) is an afloat GCCS-M component. It provides the afloat tactical commander with a timely, authoritative, and fused tactical picture with integrated intelligence services and databases. Major sub-components include the Ship's Signal Exploitation Equipment Phase II (SSEE II) system and the Navy Integrated Tactical Environmental Subsystem (NITES).
(2). GCCS-M Ashore. The GCCS-M Ashore C4I system is the GCCS-M component designed for support at major shore based commands. GCCS-M Ashore provides the shore based operational commander with a timely, authoritative, and fused tactical picture with integrated intelligence services and databases, just as the GCCS-M Afloat provides C4I for operational commanders afloat. However, GCCS-M Ashore also includes applications for monitoring the status of forces assigned and carrying out principal staff functions such as command briefing support and force scheduling. GCCS-M Ashore has three major variants, based on mission: Command Center Support (CCS) for major shore commands, Anti-Submarine Warfare Support (ASWS) at major shore based ASW commands, and Shore Targeting Operations Support System (STOSS) at the submarine operating authorities.
(3). GCCS-M Tactical/Mobile. GCCS-M Tactical/Mobile provides the Navy Component Commander, maritime Sector Commander (Ashore), the Theater Commander (Ashore) or the Naval Liaison Element Commander (Ashore) with the capability to plan, direct and control the tactical operations of joint and Naval Expeditionary Forces (NEFs) and other assigned units within his respective area of responsibility. Missions includes anti-surface warfare, over-the-horizon targeting, power projection, littoral and open ocean surveillance, anti-submarine warfare, mining, search and rescue, counter-drug operations, force protection, and special operations. GCCS-M Tactical/Mobile has four major variants: TSCs (formerly Anti-Submarine Warfare Operations Centers), MOCCs, MASTs, and MICFACs.
(4). OSIS Evolutionary Development (OED). The OED system will replace the presently fielded OSIS Baseline Upgrade (OBU). When the OED system is fielded, it will become an integrated element of the Navy Command and Control System (NCCS) Ashore program. The OED System supports command, control, and intelligence assessment. This includes indications and warnings (I&W) and power projection; maintaining dynamic databases to support a common air, and sea battlefield picture using ground force and maritime symbology. It also provides access to multiple communications networks for inter-force compatibility and interoperability that supports database sharing; data analysis and intelligence fusion; and supports briefings to Joint Task Force commanders, Commanders-in-Chief (CINCs), service components and subordinate units.
The OED System operates in a sensitive compartmented information facility (SCIF). The OED System can provide indirect users automated data feeds utilizing full-duplex General Service (GENSER) and Sensitive Compartmented Information (SCI) connectivity.
(5). Contingency Theater Automated Planning System (CTAPS)/Theater Battle Management Core system (TBMCS). CTAPS is currently in transition to TBMCS. CTAPS is an U.S. Air Force system designated by the Joint Chiefs of Staff as the air planning system for joint operations. This system assists the Joint Forces Air Component Commander (JFACC) in managing and tasking all air operations. This system is being installed on designated command-capable ships to support a JFACC Afloat, should this command be established within a Joint Task Force (JTF). Currently, CTAPS runs in a non-GCCS-M compatible COTS environment. CTAPS system administration course (CSAC) has already transitioned to TBMCS system administration.
e. GCCS-M Application Segments. Application segments are special use applications that are loaded into the system as needed to perform a specific C4I function. These segments are developed to meet specific needs of specific sponsors. Detailed explanations about the function of each GCCS-M Segment listed below is found in the Joint Maritime Command Information Strategy (JMCIS) Segment Description document published by SPAWAR.
(1). GCCS-M [Click on each segment title for more information from Annex A.2.]
f. GCCS-Integrated Imagery and Intelligence (GCCS-I3). In addition to DII COE-compliant applications which are unique to the Naval Services, GCCS has developed segments which are of broader, general purpose value. These applications fall under the purview of GCCS-I3. Among these are segments which enable fusion and display of multi-source and multi-media data, contributing substantially to air, sea and ground components of the Common Operational Picture (COP) of the battlespace. Although far from comprehensive, these capabilities map directly to requirements defined under J2 auspices by the GCCS Intelligence Functional Working Group (IFWG), and they constitute an important technical basis for significant, near term improvements in Joint-Service C4I system interoperability. The definition and refinement of GCCS-I3 requirements, in terms of both functionality and performance, will continue to evolve as will corresponding technical options. Proper COE-compliant implementation of these baseline capabilities will provide a "plug and play" foundation for rapid development of additional functionality by multiple Services and Agencies to approach answering the full requirement.
The Intelligence Shared Data Server (ISDS) and the Imagery Transformation Services (ITS) server and their associated applications segments are the primary components of GCCS-I3. The ISDS is the central repository for all shipboard intelligence data. ISDS databases include the MIDB 2.0 General Military Intelligence (GMI), Naval Intelligence Database (NID), Naval Emitter Reference File (NERF) and ELectronic INTelligence (ELINT) Parameters List (EPL). The ISDS also holds reference data for imagery available on the ITS that has been associated with GMI records. The ISDS has the ability to receive and process national and tactical intelligence updates. A intelligence analyst will play an integral role in managing and maintaining a current intelligence view of the battlespace. Besides serving GCCS-M Intel consumers and decision makers, the ISDS will also be the source of intelligence data for other shipboard systems including TAMPS, CTAPS/TBMCS, and the Aegis Weapons System.
g. GCCS-M Activities and Associated Hardware Configurations. The number of GCCS-M sites expand every quarter, and GCCS-M hardware at these sites changes to keep pace with the evolution of commercial information management systems. Table I-1 summarizes current worldwide GCCS-M configurations.
Table I-1 GCCS-M Activities and Their Associated Hardware Variants
| GCCS-M Afloat Sites |
| These sites are continuously updated at the following URL: |
| GCCS-M Ashore Sites |
| These sites are continuously updated at the following URL: |
| GCCS-M Tactical/Mobile Sites |
| These sites are continuously updated at the following
URL: http://c4iweb.spawar.navy.mil/install/teamarea/tacmobile/tacmobilesystems.htm |
2. Physical Description. The GCCS-M system is described in paragraph I.E.1, above.
3. New Development Introduction.
a. Requirements. Every aspect of GCCS-M , including outstanding user requirements, has been analyzed to determine the optimal design approach for future capabilities. This philosophy of incremental improvements and design reviews yields matrices of candidate segments for elimination, limited support, migration to the DII COE (UNIX), or direct migration to the PC/Web. Five (5) successive architecture phases were defined to accomplish GCCS-M objectives. These phases, referred to as the GCCS-M Uniform Migration Plan (JUMP), comprise the logical steps necessary for GCCS-M to achieve the architectural goals of DII COE migration and migration to the PC environment, while preserving system interoperability.
b. JUMP Strategy. The JUMP strategy and GCCS-M fielding plan provide the framework that will enable GCCS-M to advance toward the GCCS-M architecture in incremental steps. The JUMP strategy permits the large task of migration to be divided into several smaller, more manageable steps. Additionally, it provides a mechanism for continuing to incorporate new Fleet requirements into the architecture as the migration proceeds. It will also permit the incorporation of necessary interfaces with other programs and systems (e.g., ATWCS, AEGIS, ACDS, NAVSSI, TAMPS, TSC, etc.) as well as to field-related C4I initiatives (DMS, GCCS segments, etc.).
(1). JUMP Evolution. The first two JUMPs, JUMP 0 and 1, incorporate GCCS-M v2.2 COE. Beginning with JUMP 2, GCCS-M incorporate the DII COE. JUMP 2 uses version 3.0.2 of the DII COE. JUMPS 3 and 4 use DII COE versions 3.1 and 3.2, respectively, as depicted in Figure I-8.
Figure I-8 JUMP Concept
GCCS-M and the JUMP strategy make up the roadmap for migration to the DII COE and for fielding of the Naval implementation of GCCS. The Joint Maritime Communications System (JMCOMS) is the enabling technology to provide the required connectivity from a shipboard and ashore tactical communications perspective. JMCOMS and GCCS-M are expected to proceed in lockstep to provide the seamless capability and connectivity that will allow users to perform their mission in the C4I arena.
Wherever practical, functionality will be implemented using commercial standards and products to reduce cost and increase productivity of GCCS-M development, testing and training. This strategy will enable GCCS-M to satisfy Fleet requirements faster and more effectively, and is expected to reduce the current backlog of requirements. The backlog would be expected to increase with the continuation of conventional development and implementation practices.
As part of the migration strategy, commercial products that serve as a bridge between current and desired technology will be used. These products (e.g., Software 32, NTED, WinDD) will increase the initiative’s flexibility in moving current UNIX applications to the PC and Web environments by enabling users with UNIX workstations to run PC applications, and vice versa.
An important tenet of GCCS-M ’98 is its transition from UNIX to PC workstations. The transition from UNIX workstations to PCs results in a number of significant, cost-related benefits (click for more information from Annex A.3.).
(2). Schedule. DISA is planning major DII COE releases every eighteen months and minor releases every six (6) months. Backward GCCS-M capability will be maintained via Application Programming Interfaces (APIs). The timing of the availability of DII COE releases is tied to the DII migration plan for each segment.
4. Significant Interfaces.
a. GCCS-M interfaces. (click for more information from Annex A.4.)
5. New Features, Configurations, or Material. GCCS-M 3.1 functionality includes new DII COE, Tactical non-Tactical (TnT), JMHS and GCCS-I3 features for Afloat, Tactical/Mobile and Ashore.
a. GCCS-M 3.1 is DII COE 3.1 Level 5 compliant, (a Maritime extension was added to retain unique previous functionality), Year 2000 (Y2K) compliant, with security improvements, enhanced functionality with reconfigurable 11300 tracks database, correlation improvements, .1 sec map resolution and multi-coordinate input capability. It also contains TADIL-B/TADIL-J (receive), ATOX (JFACC pull, target/track auto-pairing, ACOs, ground symbology, SDs i/f, major BGDBM improvements and numerous HCI improvements.
b. GCCS-M 3.1 TnT has an extended system to the NT/PC/Web environment allowing user to operate both standard non-tactical and tactical applications including C2PC, OOB pull and plot capability, CDS Web access to Imagery services, JIVE imagery exploitation, JMHS PC functionality and Office 97.
c. GCCS-M 3.1 JMHS offers integrated profiler capability, faster and improved security features, separate Ilog/Ologs/Review and Release catalogs for improved performance, capability of handling larger messages, configuration of catalog size at installation, Common Message Processor (CMP), PC Review and Release, JMHS PC and improved profiling.
d. GCCS-I3 provides MIDB 2.0 (Juliet), tactical data management, IES-significant improvements, ruler, JAVA Image and Video Exploitation (JIVE) – integrated image and video capabilities.
