Global Command and Control System-Maritime (GCCS-M)
Navy Training System Plan

APPROVAL LETTER:

EXECUTIVE SUMMARY

The Global Command and Control System – Maritime (GCCS-M) is the Navy’s primary operational Command and Control (C2) system and a key component of both the Copernicus....Forward Command, Control, Communications, Computers and Intelligence (C4I) strategy and the evolving joint-service Global Command and Control System (GCCS). GCCS-M has aggressively pursued an evolutionary acquisition strategy in rapidly developing and fielding new C4I capabilities for Afloat, Ashore and Tactical/Mobile users. GCCS-M describes the latest phase of that evolution and the first version of the GCCS-M architecture that will be used as the maritime variant of GCCS.

The GCCS-M strategy includes the migration of GCCS-M to the Defense Information Infrastructure Common Operating Environment (DII COE), meeting Fleet requirements to merge tactical and non-tactical networks, maturing of Web and Personal Computer (PC) technologies to provide required information/capabilities, and a continued emphasis on acquisition streamlining. GCCS-M represents a significant departure from "business as usual," and the expanded use of modern technology to satisfy GCCS-M training requirements outlined in this training plan matches this trend exactly.

GCCS-M is a key component of the Navy's Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) strategy, Information Technology for the 21st Century (IT21). Under Joint Staff mandate, the Navy and the other Services must develop the C4ISR infrastructure required to achieve the warfighting capabilities defined by 'Joint Vision 2010' (JV 2010) and the 'Concept for Future Joint Operations: Expanding Joint Vision 2010' (Dominant Maneuver, Precision Engagement, Focused Logistics, Full Dimensional Protection). The foundation of these JV 2010 warfighting capabilities is Information Superiority--the capability to collect, process, and disseminate an uninterrupted flow of information while exploiting or denying an adversary’s ability to do the same.

Information Superiority has three key components: Information Systems, Information Operations, and Relevant Information. The IT21 strategy's goal is to attain Information Superiority within the Navy so these future JV 2010 warfighting capabilities can be realized. IT21 will attain this goal by:

1. focusing existing C4I programs and systems to support a secure, global Naval intranet (Naval Virtual Intranet),
2. accelerating the fielding of advanced C4I and commercial information technologies to the Fleet in a disciplined manner,
3. synchronizing Navy bandwidth requirements with the terrestrial, afloat, and space segments on a theater basis,
4. articulating Navy C4I requirements to support war time vice peace time operations,
5. enforcing Joint Technical Architecture (JTA), DII COE, Department of the Navy Chief Information Officer (DON CIO) Information Technology Standards Guidance (ITSG), and Shared Data Environment (DII SHADE) compliance, and
6. integrating fielded C4I systems such that they provide an "end to end" Network Centric Warfare capability to the Battle Force.

Further, the IT21 strategy incorporates emphasis on fielding Y2K-compliant systems, information management tools, initiatives for technology refreshment of computer and network hardware/software, increased reliance on commercial technology, and the integration of C2 and combat support systems under a common Asynchronous Transfer Mode (ATM) Local Area Network (LAN), PC-based architecture. Initiatives are underway to provide these capabilities to the Fleet by the end of FY03.

The training challenge to support this rapidly increasing use of information technology at the watch station should be obvious. Not only is information at each individual watch station increasing in volume and changing more rapidly than ever before, but the number and type of Fleet personnel exposed to new Information Technology tasks is expanding beyond the previous concentration on just a few rates or officer specialties.

This dramatic change in Fleet training requirements is also influenced by the rapid pace of technology infusion into Fleet units. Navy training specialists must break with the past as they satisfy the GCCS-M training challenges of today and tomorrow. They must use available technology and new management initiatives to fashion a training program geared to the realities of the changing workplace.

These concepts are at the core of recent initiatives by both the Chief of Naval Operations (CNO) and the Chief of Naval Education and Training (CNET) to develop a dynamic training strategy to address the accelerating challenges of C4I/IO training. GCCS-M training initiatives employ many of the modern technologies identified by the CNO including use of modularized courses, the use of high technology computer-based training and the use of non-traditional instructional methodologies such as interactive courseware.

This Navy Training System Plan outlines the first steps in this evolution. It is prepared to be read and used in a Internet-based environment where individual commands and staffs around the world can participate real time in its formulation and program execution. It can be adjusted quickly to meet changing Fleet requirements and stays current by providing web-based links to sites with continuously updated data on Fleet usage and  GCCS-M hardware/software configurations. As one of the first Training Plans that use these technology enhancements, it aligns itself perfectly with the cutting-edge nature of the GCCS-M program itself.

List of Acronyms

Glossary of Terms

Developing Agency (DA).

The office, command, or headquarters assigned by the Navy Acquisition Executive (NAE) in accordance with SECNAVINST 5400.15 to undertake the management and technical responsibility for the weapon system development effort, including timely budgeting and allocation of resources.

Equipment Facility Requirements (EFR).

The means by which the Navy coordinates the design, acquisition, and incorporation of a training system into a schoolhouse. The policy and procedures for EFR development are resident in OPNAVINST 11102.1. The TSA/DA are responsible for initiating EFR development and ensuring timely updates.

Fleet Project Team (FPT).

A team of knowledgeable representatives from the fleet or other user and interested non-user activities, consisting of qualified military and civilian personnel. They assist and advise the DA in technical, operational, tactical, and fleet specific matters relative to the TD design, development, test, and acceptance.

Initial Operating Capability (IOC).

The first attainment of the capability to employ effectively a weapon, item of equipment, or system of approved specific characteristics, and which is manned or operated by a trained, equipped, and supported military unit or force.

Java.

Sun Microsystems' object-oriented programming language.

MPT Advisory Board.

Provides vital assistance to the Program Manager in the identification and review of MPT requirements; is part of the TRPPM process.

Navy Training System Plan (NTSP).

The principal document for defining manpower, personnel, and training requirements and resources for new developments (formerly the NTP). The NTSP is a life cycle document which identifies the resources required to establish and maintain an effective training program throughout the new development’s life cycle. It controls planning for meeting the training requirements of the new development, and identifying personnel required to install, operate, maintain, or to otherwise use the new development being introduced into the Navy.

Non-Developmental Items (NDI) and Commercial off-the-Shelf (COTS).

Any item available in the commercial marketplace, or any previously developed item in use by a federal, state, or local agency of the U.S. or a foreign government with which the U.S. has a mutual cooperation agreement. Any item that requires only minor modification to meet the requirements of the procuring agency. A commercial product is a non-developmental item that has been produced for sale in the commercial marketplace.

Program Executive Officer (PEO).

A military or civilian official who has primary responsibility for directing several Acquisition Category (ACAT) I programs and for assigned ACAT II, III, and IV programs. A PEO has no other command or staff responsibilities within the Component, and only reports to and receives guidance and direction from the DOD Component Acquisition Executive.

Program Manager (PM).

The Program Manager is a military or civilian official who is responsible for managing an acquisition program.

Program Sponsor.

A Program Sponsor is an OPNAV Principal Official (OPO) by organizational charter. The Program Sponsor determines program objectives and time-phased support requirements and appraises programs, readiness and military worth for a given weapon system function or task in support of the goals and objectives of the appropriate Resource Sponsor, if assigned separately. The Program Sponsor provides day-to-day OPNAV management of the assigned programs by acting as the central point of contact for the hardware systems coordinators, Resource Sponsor, and the appropriation sponsor as necessary.

Ready for Training (RFT).

The date a training system and its associated logistics, maintenance, syllabus, and instructors are certified to be available for training at the training site.

Resource Sponsor.

A Resource Sponsor is an OPNAV Principal Official responsible for an identifiable aggregation of resources which constitute inputs to warfare and supporting warfare tasks.

Systems Command (SYSCOM).

The SYSCOMs are responsible for establishing policy and procedures for execution of the total acquisition program. They manage the Integrated Logistics Support Program (ILSP) through their functional and program management organizations. For each weapon system or equipment acquisition for which the SYSCOMs are responsible, a Program Manager (PM), Program Management Office (PMO), and ILS Manager (ILSM) are designated.

Technical Training Equipment (TTE).

Investment cost end items of operational equipment, devoted to the training and instruction of Naval personnel, for which Program Managers or Systems Commanders have the responsibility for the design, development, modernization or selection for service or special use.

Training Agency (TA).

An office, bureau, command or headquarters exercising command of and providing support to some major increment of the Navy's formalized training effort. Once a training course has been approved, the TA assumes responsibility from the TSA for follow-on training as long as the course is required.

Training Effectiveness Evaluation (TEE).

An analysis of training capability and potential value of a TD in enabling students to achieve program learning objectives.

Training Effectiveness Evaluation Plan (TEEP).

A plan for evaluating the effectiveness of a TD in meeting its criteria for specific training objectives.

Training Planning Process Methodology (TRPPM) (formerly HARDMAN Methodology).

The TRPPM program provides an integrated approach to early MPT analysis and planning consistent with the requirements of DOD Directives, Navy Instructions, Military Standards, and Logistics Support Analysis. It supports the NTSP and manpower and training planning and programming processes.

Training Support Agency (TSA).

An office, bureau, command or headquarters responsible for supporting the Training Agency by providing material and other forms of support within the cognizance of the office involved. The TSA provides initial training for the equipment/system until the TA can acquire the capability for training.

UNIX.

A multi-user, multi-tasking opoerating system control program in workstations and servers.

WinDD.

A family of C, C++ and Fortran compilers for PCs from Sybase Waterloo, a division of Sybase.

List of Figures

FIGURE / TITLE    [Click on figure title to view figure]

Figure I-1 Genesis of GCCS-M

Figure I-2 JMCIS Tactical LAN

Figure I-3 Conceptual GCCS-M LAN/WAN Architecture

Figure I-4 JMCIS Traditional Architecture

Figure I-5 GCCS-M Architecture

Figure I-5 Future GCCS-M Architecture Goal

Figure I-7 DII COE Architecture

Figure I-8 JUMP Concept

Figure I-9 GCCS-M Training Architecture

Figure I-10 GCCS-M Operator Course

Figure I-11 Strike Warfare Applications Course

Figure I-12 GCCS-M OPINTEL Analyst Course

Figure I-13 OED User / Analyst Course

Figure I-14 GCCS-M Ashore Operator Course

Figure I-15 TSC System Operator Course

Figure I-16 TSC Operations Control Operator Course

Figure I-17 TSC Comm Operator Course

Figure I-18 GCCS-M System Administration Core Course

Figure I-19 GCCS-M Afloat System Administration Course

Figure I-20 OED System Manager Course

Figure I-21 GCCS-M Ashore System Administration Course

Figure I-22 TSC/CV-ASWM 4.3 System Administration Course

Figure I-23 GCCS-M Manager Course

Figure I-24 GCCS-M Intelligence Center Manager Course

Figure I-25 TSC Watch Officer Course

Figure I-26 TAC-N Maintenance Course

Figure I-27 Intelligence Center Maintenance Course

Figure I-28 Command Center Maintenance Course

Figure I-29 TSC Acoustic System Maintenance Course

Figure I-30 TSC COMM Maintenance Technician Course

Figure I-31 Surface Cryptologic System Supervisor Pipeline

Figure I-31a TACINTEL Operator/Supervisor Pipeline

Figure I-32 Surface Cryptologic System Supervisor Pipeline

Figure I-33 Surface Cryptologic Division Officer Pipeline

Figure I-34 Submarine FT Pipeline

Figure I-34a Submarine FT Journeyman Pipeline

Figure I-34b Submarine FT Master Pipeline

Figure I-35 TSC / MOCC Watch Officer Course

Figure I-36 TSC / MOCC OPCON Course

Figure I-37 Division of Responsibilities

Figure I-38 Joint GCCS COP Core Course

Figure I-39 Notional GCCS-M Strand Course

Figure I-40 ACC CTAPS Operator / Technician Course (COTC)

Figure I-41 Theater Battle Management System Administration Course (TBMSAC)

Figure I-42 ACC Joint Air Operations Staff Course (JAOSC)

Figure I-43 Joint Doctrine Air Campaign Course (JDACC)

Figure I-44 Battle Group Intermediate Training (TTG)

List of Tables

TABLE / TITLE  [Click on table title to view table]

Table I-1 GCCS-M Activities and Their Associated Hardware Variants

Table I-2 Level of Knowledge Baselines

Table I-3 Follow-On Classroom Training Summary

Table I-4  Sample Training Matrix Format

Table I-5 GCCS-M Submarine Training Requirements

Table I-6 Training Requirements for Countries with OBU / OED Sites

Table I-7 Aircraft Carrier Battle Group Commander's Staffs

Table I-8 Aircraft Carriers

Table I-9 Air Warfare Commanders

Table I-10 Destroyer Squadrons

Table I-11 Aircraft Carrier Air Wing Staffs

Table I-12 Aircraft Carrier Air Wing Squadron Personnel

Table I-13 Amphibious Squadron Staffs

Table I-14 Amphibious Assault Ships and Amphibious Command Ships

Table I-15 Commander Second Fleet's Staff

Table I-16 Numbered Fleet Commanders' Staffs

Table I-17 Marine Air Wings

Table I-18 Navy Strike Warfare Center

Table I-19 FWWSs

Table I-20 Surface Warfare Officer School

Table I-21 Commander Aircraft Carrier Groups One and Four Staffs

Table I-22 MAWTS-1

Table I-23 Navy/Marine Corps Intelligence Training Center / Fleet Intelligence Training Center Pacific

Table I-24 NDC and Chief of Naval Operations Staff

Table I-25 Flyaway Augmentees

Table I-26 Other Navy Users

Table IV-1 GPETE Requirements

Table IV-2 General Purpose Tools Requirements

Table IV-3 GCCS-M Training Services

Table IV-4 GCCS-M Training Aids

PREFACE

The Global Command and Control System – Maritime (GCCS-M) provides a single, integrated, scalable Command, Control, and Intelligence (C2I) system that receives, processes, displays, and maintains current geo-locational information on friendly, hostile, and neutral land, sea, and air forces integrated with intelligence and environmental information. The architecture is comprised of four variants: GCCS-M Afloat (formerly known as Navy Tactical Command System-Afloat (NTCS-A) ), GCCS-M Ashore (formerly known as Operations Support System (OSS)), Tactical/Mobile (incorporating Tactical Support Centers (TSCs), Mobile Operations Control Center (MOCC), Mobile Ashore Support Terminal (MAST), and Mobile Integrated Command Facilities (MICFACs) ) and Multi-Level Security (MLS) System. The GCCS-M program is managed by the Commander, Space and Naval Warfare Systems Command (COMSPAWARSYSCOM), Command and Control, Communications, Computers, and Intelligence (C4I) Integrated Systems Program Directorate (PMW-157).

The Multi-Level Security (MLS) system, incorporating the Ocean Surveillance Information System (OSIS) Baseline Upgrade (OBU) Evolutionary Development (OED) System operates within the GCCS-M architecture. Enabling GCCS-M to disseminate/receive multiple classifications and levels of sensitivity in support of the command, control and intelligence assessment needs of Combined Joint Task Force (CJTF) operations. 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; providing access to multiple communications networks for inter-force compatibility and interoperability that supports database sharing and data analysis; and supporting briefings to Joint Task Force commanders, CINCs, service components and subordinate units. The manpower and training requirements for OBU/OED are included in this NTSP.

This Navy Training Systems Plan (NTSP) supercedes the previous Joint Maritime Command Information System (JMCIS) NTPs E-70-9401 dated June 1994 and E-70-9401A dated January 1996.  Significant changes in this NTSP over the previous version, besides the integration of new programs, include:

• Incorporation of the evolving tenets or the Navy-wide C4ISR Information Technology  training strategy as developed by CNO N6 and N7.
• Conversion to a HTML medium for display of the NTSP on the World Wide Web to a far greater audience at a significant savings in publishing resources.
• Use of a web-based collaborative authoring environment during the authoring and review phases of document preparation to allow near-real time worldwide input. This allowed over forty naval commands to influence the composition of the document on literally a day-to-day basis and allowed for a streamlined Fleet review and approval process with minimal postage expense and expenditure of staff resources.
• Evaluation of billet and training requirements by use of the new Training Planning Process Methodology (TRPPM) instead of the more traditional HARDMAN analysis.
• Reorganization of several sections of the NTSP to meet newly standardized formatting requirements.
• Inclusion of course descriptions and training requirements for the first courses to support the tri-Service GCCS and its maritime component, GCCS-M.
• Aggressive use of hyperlinks to specific URL addresses on the Internet for the inclusion of information that decays rapidly with time but is maintained continuously at various web sites. This innovative use of the Internet allows for a publication that will retain its accuracy much longer than a traditional bound volume.
• Expanded system and functional component descriptions.
• SNAP II/III, NALCOMIS, NTLSS, USMC Aviation Logistics, although included in previous JMCIS NTP’S, were not included in this NTSP as they are programmatically associated now with program management outside the purview of the GCCS-M Program Manager.

Click here to continue