Publication Date:  16 February 1996
System Version:  GCCS 2.1/Update 4
Web Page Created:  14 March 1996

Setup.  None.

Overview.  This lesson covers selected Global Command and Control System (GCCS) terms and definitions, JOPES site locations, their hardware and connectivity, the JOPES software available, and the agencies responsible for maintaining the hardware, connectivity, and software.

Now that you have a road map of what you will be doing for the next hour or so, the lesson continues by laying some basic groundwork for understanding and using JOPES in the new GCCS environment.

OBJECTIVE.  From several alternatives, select the best definition regarding the purpose of JOPES running in the GCCS environment.

Define GCCS/JOPES.  GCCS was developed to replace existing Worldwide Military Command and Control System (WWMCCS) Command, Control, Communications, Computers, and Intelligence (C4I) systems and applications.
GCCS is More than JOPES.  GCCS, which continues to evolve, is to be the single, global C4I system to support the war fighter, whether from a foxhole or from a Commander-in-Chief's (CINC's) command post.  A major part of the initial GCCS application environment is JOPES, which is migrated, translated, and developed from legacy and prototype subsystems to run on the GCCS hardware.

So What is JOPES?  JOPES is the integrated, joint, conventional command and control system used by the Joint Planning and Execution Community (JPEC) to conduct joint planning, execution, and monitoring activities.  JOPES supports senior-level decision-makers and their staffs at the National Command Authority (NCA) level and throughout the JPEC.  Combatant commanders use JOPES to determine the best Course of Action (COA) to accomplish assigned tasks and direct the actions necessary to accomplish the mission.  JOPES is a system that includes people, procedures, policies, communications, and supporting Information Systems (IS) software.

JOPES Software Applications.  JOPES is not a single application, rather it is a set of applications that can be used independently but interact with a shared database.  The JNAV window is where most JOPES applications (except JFAST, which must run on a DOS machine) can be accessed.  Other notable exceptions are the RFM and IMS tools that are started from the Launch Window.  These JOPES applications are grouped by function and are defined below.

Note:  The applications are discussed in the order as shown on the JNAV window.

Requirements.  This grouping includes applications used to define or refine the supported CINCs requirements.
Requirements Development & Analysis (RDA).  RDA allows planners to analyze and edit Time-Phased Force and Deployment Data (TPFDD).  It can also provide a preliminary analysis of the transportation feasibility of a COA.

Force Module Editor (FMEDIT).  Although not yet available in GCCS Version 2.1, this application will allow a user to create and edit Force Modules.

GCCS Status of Resources and Training System (GSORTS).  GSORTS provides information about the status and location of registered units of U.S. military forces and other registered foreign or domestic agencies or organizations.

Transportation/Scheduling.  This grouping includes applications used to analyze transportation feasibility and schedule movement requirements against movement assets.

Joint Flow and Analysis System for Transportation (JFAST).  JFAST determines transportation feasibility of an OPLAN or COA, makes closure estimates, determines optimum transportation modes, assesses attrition effects, identifies shortfalls, and determines gross lift capability.

Scheduling and Movement (S&M).  S&M allows the user to review, update, schedule, and create manifests of both Transportation Component Command (TCC) carrier and organic movement data before and during deployment.  It provides the capability to review and analyze an extensive variety of source requirements and scheduling and movement data.

TCC External System Interface (ESI).  TCC ESI provides a link between JOPES and TCC scheduling systems.  It also supports the TPFDD validation process.

Sustainment Modeling.  This grouping of applications includes models used to plan personnel, logistics, and other support required to maintain and prolong operations or combat.

Joint Engineer Planning and Execution System (JEPES).  JEPES assists the planner in developing the Civil Engineering Support Plan (CESP) appendix to an OPLAN.  JEPES allows the planner to add, delete, modify, and analyze data in the JEPES database.

Force Augmentation Planning and Execution System (FAPES).  FAPES furnishes planning information for mobilizing forces, monitors mobilization, and displays data to the user.

Individual Manpower Requirements and Availability System (IMRAS).  IMRAS captures and integrates manpower and personnel planning capabilities across the JOPES mission areas of mobilization, deployment, employment, and sustainment.  It prescribes one set of planning and execution procedures for application in both crisis and deliberate planning situations to support decision makers and personnel planners.  It also adds personnel replacement requirements to the TPFDD.  Development of IMRAS continues because of the creation of personnel replacements is the only capability currently available.  This application retains its old name of Nonunit Personnel Generator (NPG) until additional capability is added.

Logistics Sustainment Analysis and Feasibility Estimator (LOGSAFE).  LOGSAFE estimates logistics sustainment requirements of a proposed OPLAN for deliberate or crisis planning, evaluates overall logistics feasibility of OPLANs and COAs, and furnishes sustainment data to transportation feasibility analysis tools.  It also generates CIN records for TPFDD.

Medical Planning and Execution System (MEPES).  MEPES assists the medical planner in quantifying the impact of an OPLAN on the medical system.  MEPES can define Medical Working Files (MWF), compute the medical requirements, and print an appropriate set of reports.  It also provides the algorithms for determining personnel replacements created by NPG.

Reports and Retrievals.  This grouping of applications provides you with a variety of predefined or user-defined reports and displays.

Ad-Hoc Query (AHQ).  AHQ provides users with an efficient means to develop and save tailored queries to extract data from the JOPES Core database. 

Reports.  Reports allows the user to generate various reports with predefined formats that give requirements detail data, FM data, and results of OPLAN analyses.

System Resources.  This grouping of applications allow functional management of JOPES (such as permissions) and quick navigation within JOPES.

System Services (SS).  SS performs database management functions.  The use of the SS subsystem is restricted to authorized managers.

Reference File Administration (RFA).  RFA provides the capability to update and maintain the following reference tables in the JOPES Core database: 

Specified Geographic (GEO) Location File (GEOFILE).
Type Unit Data File [formerly Type Unit Characteristics (TUCHA)].
Type Unit Equipment Detail (TUDET).
Logistics Factors File (LFF).
Ports Characteristics (PORTS).
Aerial Ports (APORTS).

Note:  RFA use is restricted to DISA/Joint Interoperability and Engineering Organization (JIEO)/TEXNCP.

JOPES Information Trace (JSIT) Commands.  JSIT commands provide support for the JSIT-like system-wide navigation.  It provides the capability to execute functions in the background, while the user is performing other functions.

Communications.  This grouping of applications allows you to:  1) communicate with other JOPES users informally or in a formal, controlled format; 2) access data; and 3) transfer data and textual files.

Internet News.  Articles are uploaded to the server network which distributes the articles to all subscribing sites.  Users connected at a subscribing site can then browse articles.

Internet Chatter.  This application allows users to participate in teleconference-style communications, similar to a telephone teleconference.

SIPRNET WEB (SWEB).  The SWEB provides access to graphical and textual information from various sites and sources.  If you have attended the current JBOC, you used the Netscape application to browse the JOPES Users' Guide.

Now that you know about the JOPES applications, you should be ready to attach a definition to the correct JOPES term.

OBJECTIVE.  Given a list, match the GCCS or JOPES definitions with the appropriate terms.

JOPES Functional Manager Terms and Definitions.  As a Functional Manager, you should know several terms associated with GCCS.
Server.  The server is a computer or software program that provides disk space or some type of service to other computers over a network.

Client.  A client is a computer that requests or uses the services provided by a server.  For example, in our current environment, the Sun computer acts as a server, and various desktop computers act as clients.

Local Area Network (LAN).  A LAN provides a means of communication between connected workstations, printers, and servers using transceiver cables and fiber optic cables over a relatively small area.

Wide Area Network (WAN).  A WAN provides a means of communication between connected workstations, printers, and servers usually using some common carrier communications capabilities over a large area.

Defense Information System Network/Secret Internet Protocol Router Network (DISN/SIPRNET).  The SIPRNET provides a Secret level communications capability to the Defense Information System Network.  The SIPRNET is the communications link that provides the WAN connectivity.

JOPES Core Database.  The JOPES Core Database contains the standard reference file data and OPLAN-related requirements and transportation data. 

Note:  In general, a database is a collection of data managed by specialized software.  Oracle is the database software primarily in use within GCCS.

Note:  Some applications, like GSORTS or JFAST, maintain a separate database that shares data with the JOPES Core database.

GCCS/JOPES Permissions.  GCCS has many types of permissions, e.g., functional, login, and database access.  While you will learn more about permissions throughout this course, it is important for you to understand that permissions provide authorization to a function.  Examples include logging in to a system or creating an OPLAN within JOPES.

Now that you know something about LANs and WANs, you may be curious about the computers that can be used with GCCS.

OBJECTIVE.  Given a diagram of GCCS hardware and communications connectivity, identify by name the equipment used within GCCS to support the JOPES applications.

GCCS/JOPES Environment.  The client/server environment permits connectivity between the various GCCS applications running on servers connected to workstations where you can access most of the applications.
Hardware.  The technology involved with the GCCS environment creates an open systems architecture where many different kinds of computers can interact with one another across a LAN.  Figure 1-1 depicts a generic installation scheme for a local LAN.

SUN Servers.  Most of the JOPES and JOPES-related applications, as well as the JOPES database, reside on the servers.  It is very unlikely that any two sites will be absolutely identical.  The data server contains the JOPES database while the primary and secondary application servers contain many of the JOPES applications such as RDA, S&M, AHQ, and so on.  There are also other servers supporting the automated message handling capability and a mapping capability.  In theory, a server to support almost anything can be added to the LAN.

Workstations/Clients.  The workstation is where most people access the applications available on the LAN.  A variety of workstations are used.  The key to whether or not a particular type of workstation can be used is its ability to run some type of Windows software package.  These workstations can function as dumb terminals or they can support some of the JOPES applications as well.

WWS (OS=A/UX).  The WIS workstation, with its A/UX operating system, can access and execute all of the JOPES applications except JFAST.

Note:  Most locations are getting rid of the WIS workstation and have replaced them with one of the following types of workstations.

DOS PC (OS=MS DOS).  An MS DOS-based machine can also be used to access and execute all of the JOPES applications.  The JOPES application, JFAST, actually runs on a 486 (or better) machine.

SPARC (OS Solaris 2.3).  Many locations are purchasing the Sun SPARCstation as their preferred workstation.  It can access all the applications except JFAST.

HP (OS HP 9.0).  Hewlett-Packard also builds a machine that uses a version of UNIX, called HP 9.0, as an operating system.  It has much the same capability as the Sun SPARCstation.

GCCS Communications/Connectivity.  All of the computers have the power and capability to run programs in a stand-alone mode, but an enhanced planning efficiency is derived from sharing the same reference file information and computed results between planning cells and JOPES applications.

Local LAN.  At each site, the clients and the servers are connected to each other via a LAN.  Most LANs will be hardwired using fiber optic cables.

Remote LAN.  Many locations also have one or more remote LANs connected to the GCCS local LAN (Figure 1-2).

An example would be several JOPES users on a LAN in a different building.  They can access the applications resident on the servers and the database via bridges and/or routers.  The workstations can be any one or a combination of the four already discussed.

Remote Dial-in.  Remote users may also be connected to the network via a dial-in capability (Figure 1-3).

Remote users may have to dial-in and access a communications server via a STU-III or a multiplexer (MUX) and an encryption device (KG).  Remote users may need to do this if they are not conveniently collocated with the GCCS LAN, either on a permanent basis or a temporarily deployed basis.  Again, any one or a combination of all four types of workstations can be used.

DISN/SIPRNET WAN.  The GCCS local LANs around the world will be connected to each other via the DISN/SIPRNET WAN router (Figure 1-4).

The DISN/SIPRNET WAN router also has a communication server to support remote users in the same manner as the communication servers directly connected to a local LAN.

Think of the whole GCCS system as one large computer with multiple processors and lots of users who, given the right permissions and skills, could theoretically access all the system data and applications from any location in the system.  If you need the information, know where it is, and how to get to it, the system will support your planning requirements.  The rest of the lesson shows you where the GCCS sites are located and the various jobs/positions associated with JOPES.

GCCS/JOPES Sites/Locations.  Figure 1-5 shows the current GCCS/JOPES sites. 

JOPES Application Sites.  All of the sites shown in Figure 1-5 are JOPES application sites.  Configuration at GCCS sites will be different not only because the hardware and communications suites are different, but also because planners have requirements for different applications.  There is no standard configuration, but the pieces all work together so it is important for you to know where the pieces are and who has them.

JOPES Database Sites.  The underlined sites in Figure 1-5 indicate JOPES database sites.  These database sites will maintain their OPLAN data and the OPLAN data from any attached, application only, site.

GCCS is more than hardware and software; it also includes the personnel required to keep it running and provide user support and training.

OBJECTIVE.  From a list, match the GCCS or JOPES position title with the associated task.

JOPES Jobs/Positions.  There are several designated positions that must work closely together to keep all the applications operational, the database updated, and all the communication links in working condition.  You should expect the sites to be organized differently and, in some cases, staff duties may overlap.
Functional Manager (FM).  The Functional Manager handles the assignment of JOPES functional permissions as well as enjoying the reputation (deservedly or not) as the local JOPES experts.  In many instances, Functional Managers will also continue to be the coordinators and facilitators of almost everything that has traditionally had a JOPES connotation.

Note:  Functional Managers are occasionally referred to as Functional Database Managers.

System Administrator (SA).  The System Administrator keeps the various applications running, ensures the local LANs are connected properly, and ensures individuals with the appropriate permissions can access the applications.  Their responsibilities include backing up the software and maintaining audit trails.

Database Administrator (DBA).  The Database Administrator keeps the JOPES database accessible and accurate.  Their duties include backups of the JOPES database.

Information System Security Officer (ISSO).  The Information System Security Officer ensures proper security measures are implemented and adhered to by all system users and administrators.  They provide new users access to GCCS.  They also formulate the procedures governing the physical and personnel access controls that must be in place.

Network Administrator.  The Network Administrator keeps the appropriate network hardware and software functioning.  DISA Network Administrators are also responsible for SIPRNET WAN operations.

Site Administrator (TLCF).  Teleconference Site Administrators control and manage the teleconference suite of applications.  Their duties include creating a newsgroup, IRC channel, or SWEB page.  Additionally, the Teleconference Site Administrator controls access to a newsgroup, IRC channel, or SWEB page.

Users.  This category includes all those individuals who want and need to do nothing more than access the system to use one or more of the applications available.  They range from the teleconference user, to the OPLAN creator, the TPFDD sourcing commands, the transporters, the report builders, and the slide creators.

Summary.  During this lesson, you have been exposed to a myriad of terms and definitions that included hardware and communication topics.  Servers, LANs, and WANs should now be a part of your vocabulary as well as SIPRNET, Network Manager, and System Administrator.

Think of GCCS as one large computer spread between multiple sites, connected by classified LANs or dial-up modems, running integrated application software, and managed by trained system specialists.  When it is all done, you should be able to login at a location and access all the resources required to do your job.