GSS_user_manual.pdf

PREPARED BY CAGE CODE 3L1K7 NUMBER REV

THE BOEING COMPANY MG50533001033U1 B

BOEING TYPE

APPROVALS ENGINEERING

Lucille Basker AUTHORITY

CS SW IPT WBS 432

Norman Churchill

SUM

DATE

30 November 2011

TOTAL

PAGES 420 SMC/GPL

SUBJECT

EFFECT ON: RELEASE TO FILES CHANGE/RELEASE

PSDR/NR

SOFTWARE USER’S MANUAL

FOR THE

SYSTEM SIMULATOR CSCI

OF THE

GLOBAL POSITIONING SYSTEM BLOCK IIF – REL 3

CONTRACT NO. F04701-96-C-0025

ADPL SEQUENCE NO. ADP 121

Prepared for:

U.S. AIR FORCE

GLOBAL POSITIONING SYSTEM DIRECTORATE

CONTROL SEGMENT GROUND SUPPORT BRANCH

PETERSON AFB, CO 80914-2902

Prepared by:

BOEING

MISSION OPERATIONS AND SUPPORT CENTER

440 NORTH WOOTEN ROAD

COLORADO SPRINGS, CO 80916

Distribution D. Distribution authorized to DOD and US DOD contractors only. (Reason: Administrative or Operational Use) (Date of Determination: 28 September 1995). Other requests for this document shall be referred to NAVSTAR Global Positioning System Joint Program Office ( SMC/CZ).

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2571 et seq.) or Executive Order 12470. Violation of these export control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DOD directive 5230.25 and AFI 61-204. Include this notice with any reproduced part of this document.

DESTRUCTION NOTICE: For classified documents, follow DOD 5220.22M, National Industrial Security Program Operating Manual. For unclassified limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

CAGE CODE

3L1K7

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

PAGE

ii

Revision History

Date Revision Event

16 Oct 2007 NEW Initial Release for Release 3 FQT.

11/30/2011 A Skipped

11/30/2011 B Incoproate DCR-57814, DCR-58770, DCR-59997, DCR-57847, DCR-57768, DCR-60507, DCR-59983, DCR-57901

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 iii

TABLE OF CONTENTS

List of Paragraphs

Paragraph Page

1. SCOPE 1

1.1 Identification 1

1.2 System overview 1

1.2.1 Project sponsor, acquirer, developer, user and support agencies 2

1.3 Document overview 2

2. REFERENCED DOCUMENTS 3

2.1 Government references 3

2.2 Non-government references 3

3. SOFTWARE SUMMARY 5

3.1 Software application 5

3.2 Software inventory 5

3.2.1 List of GPSS source files and COTS files 5

3.2.2 Software needed in case of emergency 6

3.3 Software environment 6

3.3.1 Software storage requirements 6

3.3.2 Facility requirements 6

3.4 Software organization and overview of operation 6

3.4.1 Logical components of the software 6

3.4.2 Performance characteristics 7

3.4.3 Functions and interfacing systems 8

3.4.4 Supervisory controls 10

3.5 Contingencies and alternate states and modes of operation 10

3.6 Security and privacy 10

3.7 Assistance and problem reporting 10

4. ACCESS TO THE SOFTWARE 10

4.1 First time user of the software 10

4.1.1 Equipment familiarization 10

4.1.2 Access control 24

4.1.3 Installation and setup 27

4.2 Initiating a session 28

4.2.1 Logging onto SIMCON 28

4.2.2 Logging onto the simulator 29

4.2.3 Initializing the simulator 30

4.2.4 Synchronizing with a local MCS 31

4.2.5 Executing a simulation independent from a local MCS 32

4.2.6 Logging onto ARTS 33

4.2.7 Restoring the simulation state save 35

4.2.8 Common initiating problems 36

4.3 Stopping and suspending work 36

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 iv

4.3.1 Stopping the simulation 36

4.3.2 Terminating the simulation 37

4.3.3 Logging off of the simulator 37

4.3.4 Exiting the simulator 37

4.3.5 Logging off of SIMCON 38

4.3.6 Termination procedures to check for errors 38

5. PROCESSING REFERENCE GUIDE 38

5.1 Capabilities 38

5.1.1 Execution/Playback 38

5.1.2 Build/Update 39

5.1.3 Administration 39

5.2 Conventions 39

5.2.1 SUM table conventions 39

5.2.2 Simulator display coloring conventions 40

5.2.3 Simulator naming conventions 40

5.2.4 Simulator alarm and event conventions 41

5.3 Processing procedures 41

5.3.1 Pausing and restarting the simulator 41

5.3.2 Saving the simulator state 41

5.3.3 Updating the simulation state save 42

5.3.4 Initial condition sets 43

5.3.5 Scripts 51

5.3.6 Tasks 57

5.3.7 Parameter variation 66

5.3.8 Directives 374

5.3.9 Session logs 392

5.3.10 Tutorial and training materials 394

5.4 Related processing 394

5.5 Data backup 394

5.6 Recovery from errors, malfunctions and emergencies 395

5.6.1 Recovery options 395

5.6.2 Preventing unpredictable GPSS results and errors 396

5.7 Messages 396

5.7.1 Alarm messages 396

5.7.2 Error messages 405

5.8 Quick reference guide 408

6. NOTES 408

6.1 Acronyms and abbreviations 408

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 v

List of Tables

Table Page

Table 2-1 Government Reference Documents

Table 2-2 Boeing Document Standards

Table 2-3 Non-government References

Table 4-1 Logging onto the GPSS SIMCON

Table 4-2 Logging onto the GPSS

Table 4-3 Initializing the GPSS

Table 4-4 Synchronizing the GPSS with a Local MCS

Table 4-5 Executing the GPSS Independent from a Local MCS

Table 4-6 Logging onto ARTS

Table 4-7 Retoring a Simulation State Save on the GPSS

Table 4-8 Stopping a Simulation on the GPSS

Table 4-9 Terminating the Simulation

Table 4-10 Logging off the Simulator

Table 4-11 Exiting the Simulator

Table 4-12 Logging Off SIMCON

Table 5-1 List of Conventions for Procedures Described in the SUM

Table 5-2 Pausing and Restarting a Simulation on the GPSS

Table 5-3 Saving the Simulation State

Table 5-4 Updating a Simulation State Save on the GPSS

Table 5-5 Creating the Initial Condition Set on the GPSS

Table 5-6 Updating the Initial Condition Set on the GPSS

Table 5-7 Updating the Universal Time Coordinate on the GPSS

Table 5-8 Converting the State Save to an Initial Condition Set on the GPSS

Table 5-9 Copying the Initial Condition Set on the GPSS

Table 5-10 Printing the Initial Condition Set Listing on the GPSS

Table 5-11 Deleting an Initial Condition Set on the GPSS

Table 5-12 Creating a Script on the GPSS

Table 5-13 Updating a Script on the GPSS

Table 5-14 Copying a Script on the GPSS

Table 5-15 Viewing and Printing a Script on the GPSS

Table 5-16 Deleting a Script on the GPSS

Table 5-17 Building a Task on the GPSS

Table 5-18 Updating a Task on the GPSS

Table 5-19 Real-Time Task Injection on the GPSS

Table 5-20 Manual Task Injection on the GPSS

Table 5-21 Viewing and Printing a Task on the GPSS

Table 5-22 Deleting a Task on the GPSS

Table 5-23 Viewing State and Varied Parameters on the GPSS

Table 5-24 Updating Varied Parameters on the GPSS

Table 5-25 State and Varied Parameters on the GPSS

Table 5-26 Viewing Directives on the GPSS

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 vi

Table 5-27 Reference List of GPSS Directives

Table 5-28 Session Log Playback on the GPSS

Table 5-29 Viewing and Printing a Session Log on the GPSS

Table 5-30 Alarm Error Messages for the GPSS

Table 5-31 Error Messages on the GPSS

List of Figures

Figure Page

Figure 3-1 GPSS System Overview

Figure 4-1 Solaris Common Development Environment Screen

Figure 4-2 Simulator Logon Window

Figure 4-3 Alarms and Events Window

Figure 4-4 Simulator Main Menu Window

Figure 4-5 Item Selection Window

Figure 4-6 IC Builder Window

Figure 4-7 Model Selector Window

Figure 4-8 Model Specific State Data Window

Figure 4-9 Task Builder Window

Figure 4-10 Script Builder Window

Figure 4-11 Task/Directive Information Window

Figure 4-12 Execution/Playback Parameter Selection Window

Figure 4-13 Script Execution Window

Figure 4-14 Sessions Parameters Window

Figure 4-15 Directive Status Window

Figure 4-16 Task Injection Window

Figure 4-17 Live Model Window

Figure 4-18 State Saves Window

Block Type

Subsystem

Parameter Name

Parm Type

Range

Units

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

1. SCOPE

1.1 Identification

This Software User Manual (SUM) applies to the Navigation Timing and Ranging (NAVSTAR)

Global Positioning System (GPS) Simulator (GPSS) for Release 3. The simulator, or Sim, is comprised of one Computer Software Configuration Item (CSCI). The GPSS software suite is composed of the software listed in Table 3-1 Materials Released and Table 3-2 COTS software vendor information both of which are in the GPSS SIM Software Version Description, document number 50533001-Rel 3.

Release 3.1 is a modified version of Release 3.0. The following will describe the key parameters differentiating the two releases:

1. Release 3.0

Utilizes 0107050101 SCPC IIF flight software

Utilizes 0518050101 plus some 0324060101 NDUC IIF flight software

Is CML D02 compatible

Supports AEP V5.5 utilizing CML D02

Utilizes BOL 10-26-05 Solar Force Model data

2. Release 3.1

a. Utilizes 0523060101 SCPC IIF flight software

b. Utilizes 0719060101 NDUC IIF flight software

c. Is CML D08 compatible

d. Supports AEP V5.5 and V5.2.2 utilizing CML D08

e. Incorporates ICD-GPS-601and PIRN-601-001 updates

f. Utilizes BOL 6-26-06 and EOL 6-26-06 Solar Force Model data

1.2 System overview

GPS is a space-based radio navigation, time distribution and nuclear detonation (NUDET) detection system. The GPS mission is to provide precise, continuous, all-weather, three-dimensional position, velocity, timing, and NUDET information to properly equipped air, land, sea, and space-based users. The GPS consists of three segments: the Space Segment (SS); the

User Segment, which consists of the NUDET detection users and navigation users; and the

Control Segment (CS). The Control Segment consists of four Elements: the GPS SIM, the

Operational Control Segment (OCS), the Integrated Mission Operations Support Center

(IMOSC), and the Launch/early Orbit Anomaly Resolution, Disposal and Routine Operations

(LADO).

The Simulator provides simulation of the GPS capabilities that are not provided directly by the

Master Control Station (MCS) in support of operator training, data analysis, and software test functions. Specifically, the Simulator will simulate the GPS SS, OCS Ground Antenna (GA), OCS Monitor Station (MS) and 14 National Geospatial-Intelligence Agency (NGA) MSs, OCS

Communications, Automated Remote Tracking Stations (ARTS) and certain external users. It

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 interfaces to, and works in conjunction with, a Replica MCS (RMCS). The Replica MCS is a copy of both the hardware and software used for the MCS. The Simulator will simulate Block II, IIA, IIR, IIRM, and IIF satellite functions, and provide remote ground resource functions for crew training, OCS software validation and anomaly resolution. For the OCS, the Simulator uses no operational equipment resources and will not interfere with real time operations. It responds accurately to crewmember inputs and allows crewmembers to experience and exercise realistic crew operations.

1.2.1 Project sponsor, acquirer, developer, user and support agencies

This project is sponsored and acquired by the United States Air Force (USAF) Space and Missile

Systems Center (SMC), Los Angeles Air Force Base (LAAFB) for use by USAF 50th Space

Wing, Schriever Air Force Base. The Boeing Company is the developer and support agency for the GPSS.

1.3 Document overview

The purpose of this SUM is to describe how to install and use the GPSS. This document is intended for personnel who use GPSS for testing and training, as well as for personnel who install the GPSS. More detailed information on installing the GPSS can be found in the Software

Version Description for the System Simulator of the GPS Control Segment.

This SUM has been prepared in accordance with Data Item Description (DID) DI-IPSC-81438 and is compliant with the tailored GV3224-001, Software User‟s Manual, standard expressed in

Appendix B to the Software Development Plan (SDP) (MG50500000012M1). The major sections of this document are as follows:

Section 1 SCOPE. This section provides an identification and overview of the system and software to which this SUM applies, an overview of the document itself, and describes the relationship to other project management plans.

Section 2 REFERENCE DOCUMENTS. This section lists the documents referenced by, or applicable to, this SUM.

Section 3 SOFTWARE SUMMARY. This section describes the intended uses of the software, the software inventory of the GPSS, the software environment for the GPSS, the organization and operation of the GPSS, the security and privacy considerations of the GPSS, and points of contact for reporting problems with the GPSS.

Section 4 ACCESS TO THE SOFTWARE. This section provides some GPSS equipment familiarization, discusses the access control and security features of the GPSS, installation and setup of the GPSS, and procedures for initializing and terminating a simulation session using

GPSS.

Section 5 PROCESSING REFERENCE GUIDE. This section will discuss the capabilities related to the use of the GPSS, conventions used by the GPSS, processing procedures, aspects of the GPSS software use, related processing, data backup procedures for the GPSS, error/malfunction recovery procedures for the GPSS, and a list of possible messages that can occur while running with the GPSS.

Section 6 NOTES. This section contains general information that aids in the understanding of this document, including an alphabetical listing of all acronyms, abbreviations, and their meanings.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

2. REFERENCED DOCUMENTS

The documents of exact issue shown in Table 2-1 and Table 2-3 are applicable to this document.

In event of conflict between the documents referenced herein and the contents of this document, the contents of Software Requirements Specification (SRS-SIM-662) are considered superseding requirements.

2.1 Government references

Table 2-1 Government Reference Documents

Document Data Document Title

NISPOM

DoD 5220.22-M

February 2006

National Industrial Security Program

50533001-Rel 3 Rev NEW

9 November 2007

Software Version Description for the System Simulator CSCI of the

Global Positioning System Block IIF-Rel 3

MG50500000012M1 Rev J

12 Dec 2006

Software Development Plan for the Global Positioning System Block IIF

50532000-V5.5 Rev NEW

13 June 2007

Software Version Description for the Operational Control System of the

Global Positioning System Block IIF-V5.5

GPSS SO Trainee Guide, May 2005

GPSS Simulator Operator Training Guide

MG50533001033E2 Rev A, 3 July 2007

Software Requirements Specification for the System Simulator CSCI of the Global Positioning System Block IIF – Rel 3

MG50533001033E4,

26 Oct 2007

Software Product Specification for the System Simulator CSCI of the

Global Positioning System Block IIF Release 3

MG50532000013E1

7 March 2005

Element Design Description for the Operational Control System Element

Software Release Version 5.2

2.2 Non-government references

The documents in Table 2-2 Boeing Document Standards, describe the Boeing standards for software development and test activities. These provide guidance and are not contained in the

SDP.

Table 2-2 Boeing Document Standards

Document Data Document Title

GV3224-001 Software User‟s Manual Standard Requirements

(DID) DI-IPSC-81438 Data Item Description DI-IPSC-81438

Table 2-3 Non-government References

Document Data Document Title

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Version 5.2

June 2003

P/N: 816-6696-10

Sun™ ONE Directory Server 5.2 Release Notes

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

3. SOFTWARE SUMMARY

3.1 Software application

The GPSS provides a realistic environment in support of:

Crew training (general and specific training exercises and evaluations).

Engineering support functions (anomaly analysis and resolution).

OCS software evaluation and validation (software development testing, command plan validation, upload validation, and satellite database validation).

The GPSS provides flexible usage and control of a simulation session through a single operator interface, the Simulator Operator (SO) position.

For crew training, the SO develops a simulation script and Initial Condition (IC) set designed towards a specific crew position or a group of crew positions. When the GPSS is connected to the Training RMCS, the SO can observe the effects of actions taken by the crewmember and inject anomalies or degrade components in real-time to train the crewmember how to correctly respond to anomalous situations. Simulator capabilities support Initial Qualification Training, Unit Qualification Training, Monthly Recurring Training, Additional Training, Refresher

Training, Corrective Training and evaluations. In this way, the GPSS offers a powerful training tool.

For anomaly resolution and analysis, the satellite vehicle (SV) engineer, OCS software engineer or hardware engineer develops a simulation script and IC set to recreate a problem. Through simulation, the Engineer troubleshoots/analyzes the problem. In this way, the GPSS eliminates much of the guesswork involved in real world anomaly resolution.

For software evaluation and validation, the tester develops a simulation script to execute the new software functions and ensure the new software does not regress the Control or Space segments.

A tester may also support command, upload, and satellite database validation by using the GPSS to realistically model Block II/IIA, IIR/IIRM, and IIF telemetry, command responses, GA status and configuration data, and MS messages. In this way, the GPSS eliminates much of the live testing done currently when new software is delivered.

3.2 Software inventory

3.2.1 List of GPSS source files and COTS files

A list of all COTS and simulator media and identifications for the GPSS software are provided in Section 3.1.2.2 Materials Released and Table 3-1, COTS software vendor information of the

GPSS SIM SVD (50533001-Rel 3).

A list of all simulator source files and their file sizes is located in Section 6 REQUIREMENTS

TRACEABILITY of the Software Product Specification (MG50533001023E4). Several of the source code files contain information classified as secret. These file names are listed in Section

3.3 Packaging Requirements of the SPS (MG50533001023E4) and should follow the appropriate security requirements as outlined in the latest version of the National Industrial Security Program

(NISPOM).

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

3.2.2 Software needed in case of emergency

In case of an emergency (i.e., inadvertent power outage, fatal error, etc.) all delivered simulator software and COTS software are needed to resume full functionality. See Section 5.6 Recovery from errors, malfunctions and emergencies for emergency procedures.

3.3 Software environment

3.3.1 Software storage requirements

Storage requirements are identified in the following tables of the GPSS SIM SVD (50533001-

Rel 3):

1. Tables 3-10 Disk Configuration for SIMENG

2. Tables 3-16 Disk Configuration for SIMCON

3. Table 3-17 Disk Configuration for SCP1/SCP2.

4. Table 3-26 Disk Configuration for SSP

In addition the file size of every GPSS source code file is listed in Section 6 REQUIREMENTS

TRACEABILITY of the SPS (MG50533001023E4).

3.3.2 Facility requirements

The following facility and equipment conditions must be satisfied:

1. Since certain files and some data displayed on computer screens are considered secret level classified, the fully functional and operational GPSS hardware and software must be stored, located and handled in a secret level classified facility according to NISPOM

(DoD 5220.22-M).

2. The facility architecture, hardware and environment must adhere to facility and equipment guidelines specified in Section 4.2.12 Equipment and facilities of the Element

Design Description for the Operational Control System Element Software Release

Version 5.2 (EDD-OCS-623-V5.2).

3. The facility must also provide connectivity to an MCS.

Further information pertaining to the software environment for the GPSS software, including hardware, operating systems, databases, and utilities, is provided in Sections 1, 2, and 3 of the

SVD (50533001-Rel 3).

3.4 Software organization and overview of operation

3.4.1 Logical components of the software

The GPSS consists of a combination of Commercial Off-the-Shelf (COTS) and developed code.

3.4.1.1 COTS

Sun Solaris OS 8 (version 5.8) – provides the underlying operating environment for all Sun computer programs and provides a wide variety of services, including process management, user interface support, security, communications access, printer support, and many others. Solaris is a

POSIX-compliant UNIX Operating System from Sun Microsystems.

Solaris Common Desktop Environment (CDE) – CDE is a standardized, Motif-based implementation of a user interface running on top of the X Window System, and is available for a variety of systems.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

HP JetAdmin – provided by Hewlett Packard comes bundled with the simprt printer. It provides various configuration and status functions for HP printers.

SL-GMS – provided by SL Corporation, is a set of user interface utilities and interfaces used internally by OS/Comet and Consolidated Operator Support Environment (COSE).

OS/Comet – provided by Harris Inc., is the Telemetry, Tracking, and Commanding (TT&C) software used by the GPSS OCS Remote Site simulation. It is the heart of processing for the

Simulation Communication Processors (SCPs). This includes SCP1 and SCP2. For the current

OS/Comet release, please see the latest Operational Control Segment Software Version

Description (50532000-V5.5).

Software Bus – supplied by Harris Inc., provides communications for GPSS OCS Remote Site simulation. It is a reliable queue-based messaging system for communications between

OS/Comet products within a simulated OCS remote site, as well as between an OCS remote site and the MCS.

Pam_tally – provides a method to lockout accounts after three unsuccessful login attempts.

Lightweight Directory Access Protocol (LDAP) – provides some additional layers of security beyond those available in a conventional UNIX environment.

ORACLE Server Enterprise Edition, from ORACLE Corporation - provides a relational database for storage and retrieval of several types of data. The database server resides on Simulation

Support Processor (SSP) with the other GPSS processors accessing the database via clients on the Simulation Engine (SIMENG) and the Simulation Controller (SIMCON).

3.4.1.2 Developed code

GPSS Release 3 – The GPSS provides simulation of the GPS capabilities that are not provided directly by the MCS in support of crew member (operator) training, engineering analysis, and software test functions. Specifically, the GPSS provides a complete real-time simulation of the space segment, the OCS GAs, the OCS MSs and ARTS for both nominal and anomalous conditions. Real-time communication simulation for the NGA and External User Agencies

(EUA) is also provided. The space segment simulation includes II/IIA, IIR/IIRM, and IIF SVs, and environmental effects.

The GPSS simulates Block II/IIA, IIR/IIRM, and IIF satellite functions and provides remote ground resource functions for crew training, software validation and anomaly resolution. The

GPSS responds accurately to crewmember inputs across the range of operations and allows crewmembers to experience realistic crew interactions with the GPS Space and Control segments.

3.4.2 Performance characteristics

The only performance requirement imposed on the GPSS is the initialization time. Time to initialize for the GPSS is the measure of time it takes to load a pre-built set of initial conditions and begin executing the simulation. The time is computed from the number of minutes from the start of the simulation to the actual running of the simulation. The initialization time is less than thirty minutes.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

3.4.3 Functions and interfacing systems

The GPSS developed software includes six software domains. Figure 3-1 GPSS System

Overview maps the five main functional software domains

{Space Simulation, Ground Simulation, Environmental Simulation, Simulation Engineer Control

(SEC), and Human Computer Interface (HCI)} to the GPSS hardware of this single string configuration. The Common Services domain supports each of the five functional domains and is not shown. The HCI and SEC domains reside on the SSP and SIMCON workstations. Ground

Simulation is distributed across the Sun Sunfire 4800 and Sun workstations. The Space

Simulation domain and the Environment Simulation domain reside on a Sun Microsystems, Inc.

workstation. SIMCON, SIMENG, SSP, SCP1 and SCP2 are all connected via a Cisco 2950 switch. This switch can be connected to a Cisco 2612 (or better) router for connection to outside inputs. The code was developed in the Ada and C programming languages. The double dashed line depicts the GPSS system boundary while the double solid line depicts the boundary for

GPSS system administrators. The peripheral equipment, which includes laser printers and other

Network Computing Devices (NCDs), is not shown in the figure.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

HCI

Simulation Controller WS

Sim Engr Control

Execution

Ground Simulation

GA/MS Workstation S/W

Simulation

Communication

Processor

OS Comet

Simulation Engine Processor

Space

Simulation

Environment

Simulation

Ground Simulation

Simulation Controller

(SIMCON)

Simulation

Engine

(SIMENG)

Simulation

Communication

Processor

(SCP1)

Simulation

Communication

Processor

OS Comet

Simulation

Communication

Processor

(SCP2)

Simulation Support

Processor

(SSP)

HCI

Simulation Support Processor

WS

Sim Engr Control

Task/Script development

Ground Simulation

Router

Switch

Ground Simulation

GA/MS Workstation S/W

HCI

Simulation Controller WS

Sim Engr Control

Execution

Ground Simulation

GA/MS Workstation S/W

Simulation

Communication

Processor

OS Comet

Simulation Engine Processor

Space

Simulation

Environment

Simulation

Ground Simulation

Simulation Controller

(SIMCON)

Simulation

Engine

(SIMENG)

Simulation

Communication

Processor

(SCP1)

Simulation

Communication

Processor

OS Comet

Simulation

Communication

Processor

(SCP2)

Simulation Support

Processor

(SSP)

HCI

Simulation Support Processor

WS

Sim Engr Control

Task/Script development

Ground Simulation

Router

Switch

Ground Simulation

GA/MS Workstation S/W

Figure 3-1 GPSS System Overview

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

3.4.4 Supervisory controls

User ID‟s of authorized simulator users are held in a database table and used in conjunction with other tables to determine the authorities of a particular user. Users may have access to only certain directories and they may also have authority to perform only some simulator functions. If a user does not have access to a given function through the Graphical User Interface (GUI), the associated button or menu selection is grayed out. There are separate libraries in which scripts and condition sets are contained. Users will only have access to the libraries for which their user

ID shows that they have authority.

3.5 Contingencies and alternate states and modes of operation

Not applicable.

3.6 Security and privacy

The simulator contains classified (secret) information and should be handled in accordance with the latest version of NISPOM (DoD 5220.22-M). The government has complete right of usage of the simulator due to it‟s compliance with the aforementioned document.

3.7 Assistance and problem reporting

If problems are encountered while running the simulator, follow the steps in Section 5.6

Recovery from errors, malfunctions and emergencies, or contact the system administrator for your site. The system administrator can contact GPSS experts who will assess the problem, and if necessary, open a problem report.

4. ACCESS TO THE SOFTWARE

4.1 First time user of the software

For step-by-step instructions for running the simulator, refer to the appropriate section within this document.

4.1.1 Equipment familiarization

The principal interaction of the SO with GPSS is the SIMCON workstation. SIMCON displays are essential to successful GPSS performance. The following four sections briefly discuss aspects of these displays of which the SO should be aware.

The features of the SIMCON display are described in the following sections.

4.1.1.1 Grayed out items

On many displays, grayed out items indicate options which are not available at that time. There are two reasons why items are grayed out:

Some items apply only to builder functions or only to execution functions. The display is used for both builder and execution functions. Only the applicable functions are available. The others are grayed out.

Some items are grayed out until certain conditions are met; for example, on the

Execution/Playback Parameter Selection window, the <Select> button for the Initial

Conditions field is grayed out until the Script or Session Log Name field is filled in.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.1.1.2 Mouse button usage

The mouse used by the operator is a three-button mouse. All three mouse buttons are used. The majority of the SO functions respond to the left button. Throughout this document, the word

“click” is used to refer to a left mouse click. The left mouse button is used to select (“click”) menu items, push (“click”) buttons, and highlight (“click”) text fields.

The middle mouse button is used for drag and drop operations. These operations include the following builder functions:

Adding directives to tasks

Deleting directives from tasks

Adding tasks to scripts

Deleting tasks from scripts

Clicking the right mouse button does nothing when the cursor is in a GPSS display window.

However, when the cursor is in the Sun workstation Common Desktop Environment (CDE) and the right mouse button is clicked, a workspace menu pops up giving the user several options.

4.1.1.3 Mouse pointer appearances

The mouse pointer takes on three different shapes, depending upon the functions being executed:

Pointer

Blinking Cursor

Hourglass (Clock)

An active mouse pointer is either a pointer or a blinking cursor. Most often the mouse pointer is a solid black arrow. This indicates that the GPSS is ready for SO selections.

When a button is depressed, the button‟s perimeter is highlighted unless it‟s a round orange button or a square blue button. When a round orange button is selected, it turns into a green checkmark indicating the button has been selected. When a square blue button is selected, it brings up another display. Round orange buttons are used for manually selecting tasks in scripts and for selecting items to include in an IC set. Square blue buttons allow the SO to view or edit model state data.

A blinking cursor appears when the pointer is in a text field and the left mouse button has been clicked. A blinking cursor indicates a text field. Sometimes, however, a blinking cursor appears but no text may be typed. For example, in the Execution/Playback Parameter Selection window, there are three text fields but text only appears when items are selected from lists. Typing the names of scripts or initial condition sets does not make text appear even when there is a blinking cursor.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.1.1.4 Mouse actions

When the pointer changes into an hourglass, it indicates that the GPSS is busy and SO actions cannot be performed.

When text fields are selected with a mouse, text is selected, buttons are selected, or a window is selected, and these items become highlighted:

Fields are highlighted around their perimeter.

Selected text changes color.

Buttons are highlighted around their perimeter.

An active window is highlighted around the perimeter.

4.1.1.5 GPSS display types

There are four categories of displays: General Displays, Builder Displays, Execution Displays, and Administration displays.

General Displays are displays that are available once the GPSS is started; for example, the Login Window, the Simulator Main Menu, the Alarms and Events window, or displays which are available and contain the same functionality across the

Builder, Execution and/or Administration functions.

Builder displays are displays that the user has access to from the Build/Update button on the Simulator Main Menu display. These displays provide access to all of the builder functions.

Execution displays are accessible through the Execution/Playback button on the

Simulator Main Menu. These displays provide access to all of the execution functions.

Administration displays are accessible through the Administration button on the

Simulator Main Menu. These displays are used by the GPSS SA. The SO does not use Administration items.

4.1.1.6 GPSS displays

The following figures illustrate the most commonly used display windows of the GPSS.

After logging onto the Solaris Workstation, the Solaris Common Development Environment, or

“Solaris Background” desktop, fills the terminal screen. Right click on the desktop, select Tools and then Terminal. The Terminal window shown in Figure 4-1 appears with the SO home directory and individual user name as the path.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-1 Solaris Common Development Environment Screen

When the simulator has been started from the terminal window, the Simulator Logon Window

(Figure 4-2) is displayed on the screen. For logon instructions see Step 5 in Table 4-2 Logging onto the GPSS.

Figure 4-2 Simulator Logon Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-3 illustrates the Alarms and Events window.

Figure 4-3 Alarms and Events Window

Figure 4-4 illustrates the Simulator Main Menu window.

Figure 4-4 Simulator Main Menu Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Selecting the Build/Update button in the Simulator Main Menu window brings up the Item

Selection window as shown in Figure 4-5.

Figure 4-5 Item Selection Window

Figure 4-6 illustrates the IC Builder window.

Figure 4-6 IC Builder Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-7 illustrates the Model Selector window.

Figure 4-7 Model Selector Window

Figure 4-8 illustrates an example of viewing model specific state data for any given SV. This figure shows a snap shot of the IIF RCS state data for SVN 62.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-8 Model Specific State Data Window

Figure 4-9 illustrates the Task Builder window.

Figure 4-9 Task Builder Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-10 illustrates the Script Builder window.

Figure 4-10 Script Builder Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-11 illustrates the Task/Directive Information window. It shows an example of filling in the parameters for new task/directives. Although not shown, the Remarks field should be filled in.

Figure 4-11 Task/Directive Information Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-12 illustrates the Execution/Playback Parameter Selection window.

Figure 4-12 Execution/Playback Parameter Selection Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-13 illustrates the Script Execution window.

Figure 4-13 Script Execution Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-14 illustrates the Sessions Parameters window.

Figure 4-14 Sessions Parameters Window

Figure 4-15 illustrates the Directive Status window.

Figure 4-15 Directive Status Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-16 illustrates the Task Injection window.

Figure 4-16 Task Injection Window

Figure 4-17 illustrates the Live Model window.

Figure 4-17 Live Model Window

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Figure 4-18 illustrates the State Saves window.

Figure 4-18 State Saves Window

4.1.2 Access control

4.1.2.1 User access overview

Users are logged in using the UNIX (Sun Solaris) login. The User login is managed through the database by keeping track of login status of the users in several database tables. The User Login remains active while the member performs his/her duties. When a user signs onto the system, he will use his own account and password. They will have to be authenticated by LDAP before the user can continue. Once it is verified and the user is authorized to use the system, he will be allowed to use all of the functions associated with his chosen role.

Database security is maintained through the use of GPS roles. All GPS database objects (tables, stored procedures, etc.) are owned by a privileged Oracle user. The database administrator then grants specific, controlled access to the GPS user through the GPS_MISSION_ROLE for mission database objects and GPS_ENO_ROLE for experimental NAV objects. All GPS applications run under the GPS user ID. Oracle O/S authentication is used to authenticate the connection that the applications make to the database. Once connected, applications only enjoy those access privileges granted to the GPS user ID by the database administrator.

All passwords are generated, maintained and administered by the local site system administrator.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.1.2.2 LDAP account management

GPSS LDAP accounts are managed by root using the LDAP_SUPPORT.ksh utility located on the root slice of “simeng”. Once it is run (./LDAP_SUPPORT.ksh), the following menu is shown:

# USER MANAGEMENT INTERFACE for the GPSS LDAP_SUPPORT.ksh utility.

Management Options:

1. CREATE a New User Account

2. RESET a Users Password

3. LIST Users

4. Inactivate a user

Exit

To manage an account, the Security Administrator may choose an option (1, 2, 3, 4 or exit):

After the option number is entered, instructions will follow explaining how to perform the required function.

These additional commands may also be useful:

Passwords can be changed with the standard Solaris command: “passwd”.

LDAP commands can be used to manage accounts as well. See the SUN One

Directory Server documentation for more information.

Accounts can be listed using “ldaplist passwd \*”. More information can be listed on individual accounts with “ldaplist –l passwd USER”.

4.1.2.2.1 GPSS user account creation

1. GPSS user-

a. Login as “root” and use the LDAP_SUPPORT.ksh utility option 1 to create a new

GPSS user.

4.1.2.2.2 Account deletion

Before an account is deleted, the decision should be made concerning what to do with the files owned by the user. The user‟s home directory can be deleted (rm –r ~USER) or moved (mv

~USER new_dir). Files owned by the user can be found and the ownership changed or the file removed. The “find” command can be used to do this (i.e. find / -user USER –ls).

1. GPSS user –

a. Have the local system administrator log into the LDAP directory server on simeng.

b. Enter the user name and password for the directory server login.

c. Expand the simeng.gps.sim domain and double click on the „directory server‟ tab.

d. Right click on the user id to be deleted and click „delete‟.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.1.2.2.3 Changing a password

1. GPSS user -

a. If the old password is known, as the user (su USER), run the “passwd” command.

b. If the old password is not known, reset the password. Have the local System

Administrator reset the password using the LDAP_SUPPORT.ksh utility. Choose the

“RESET a Users Password” option and type in the userid to be reset.

c. The user needs to sign on using the default password and change the password as soon as possible.

2. Administrator user -

a. If the old password is known, as the user (su USER), run the “passwd” command.

b. If the old password is not known, as “root”, run the “passwd” command.

4.1.2.2.4 Disabling an account

2. GPSS user-

a. Use the LDAP_SUPPORT.ksh utility option 4 to deactivate a GPSS user.

3. Administrator user –

a. Use the “passwd -l“ utility to disable the account, substituting the user ID for

“USER” below. This replaces the password with “*NP*”:

passwd -l USER

4.1.2.2.5 To re-enable/unlock an account

1. GPSS user-

a. Have the local System Administrator reset the password using the

LDAP_SUPPORT.ksh utility. Choose the “RESET a Users Password” option and type in the userid to be reset.

2. Administrator user –

a. Use the “passwd -l“ utility to clear out the password, substituting the user ID for

“USER” below:

passwd -l USER

b. Use the “passwd“ utility to set an initial password, substituting the user ID for

“USER” below. This must be communicated to the user in a secure manner:

passwd USER

c. Use the “passwd -f“ utility to force the user to change the password on next login, substituting the user ID for “USER” below:

passwd –f USER

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.1.3 Installation and setup

4.1.3.1 Installation of simulator source code and COTS products

For complete installation procedures for all simulator source code and COTS products see

Section 3.6 Installation instructions within the SVD (50533001-Rel 3).

4.1.3.2 Build preparation

This section identifies the procedure to build a new baseline (aka. prod level) from the installed software described in Section 4.1.3.1 Installation of simulator source code and COTS products of this document. In the procedure below, a new Release X baseline is created.

3. Prep Work:

g. Logon to SIMENG

h. Create /sim/RELEASE_X directory, if necessary, as specified by Section 4.1.3.3

New baseline generation of this document.

i. chown lm_cm:cm /sim/ RELEASE_X.

j. rsh to SSP and SIMCON as root. Add the new prod level to /etc/auto_direct and type: automount –v.

k. Update the new prod level source code files with files modified by the developers, if necessary, as specified in Section 4.1.3.4 Create / implement developer modified files.

4. Code Build on SIMCON:

a. Logon to SIMCON as lm_cm

b. cd /sim/RELEASE_X/build

c. ./build_simcon

5. Code Build on SSP:

a. Logon to SSP as lm_cm

b. cd /sim/RELEASE_X/build

c. ./build_ssp

6. Code Build on SIMENG:

a. Logon to SIMENG as lm_cm

b. cd /sim/RELEASE_X/build

c. ./build_simeng

7. Build Completion and Finalization:

a. Logon to SIMENG as lm_cm

b. cd /sim/RELEASE_X/build

c. ./post_build (enter root password when prompted)

4.1.3.3 New baseline generation

The following steps specify how to copy an existing baseline (aka. prod level) and rename it to create a new baseline:

1. Logon to SIMENG by typing: sulm_cm

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

2. cd /home/lm_cm/promote_scripts

3. Modify the “make_prod” script to include the correct prod levels by specifying:

a. “Previous_Level”: which is the old baseline to be copied

b. “New_Level”: which is the new baseline name (aka. Release X)

4. ./make_prod

4.1.3.4 Create / implement developer modified files

The following steps specify how to copy, modify and update source files modified by developers for a new baseline:

1. Modify the “copy_verified” script to include the correct prod levels by changing

“Level” to the new/current baseline directory name. Running “copy_verified” creates an output of affected files and a script that copies the files to the appropriate location.

2. Run: ./copy_verified <script name> <output file>

3. (For example, ./copy_verified /tmp/MyScript /tmp/build.log)

4. Review (and modify as necessary) the script created by copy_verified. Be sure to compare the output file contents to the files affected portion of the Deficiency

Reports for the release.

4.1.3.5 Upgrading with new simulator release files

If a new SIM release is to be installed, the release directory name (i.e., RELEASE_3) must be different than any previously existing release directory name. If the names are identical, the new release will over-write any existing release(s) that has the same name without warning. If both releases are to be kept, verify that both release directories are named differently.

4.2 Initiating a session

4.2.1 Logging onto SIMCON

The procedure in Table 4-1 defines the steps required to logon to the SIMCON workstation. It assumes successful power up of the SIMCON workstation.

Table 4-1 Logging onto the GPSS SIMCON

Step Action Result

1 On the Solaris logon window, select the Please enter your user name text field box. Enter the user name assigned to you by the System

Administrator.

The Solaris logon window awaits a user action.

2 On the Solaris logon window, select the <OK> widget. Otherwise, select <Start Over> and re-enter the user name.

The Solaris Common Desktop Environment

(CDE) logon window awaits a user action.

3 On the Solaris CDE logon window, select the

Please enter your password text field box. Enter the user name assigned to you by the System

Administrator. (The password is not indicated in this handbook for security purposes.)

The Solaris CDE logon window awaits a user action.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

Step Action Result

4 On the Solaris CDE logon window, select the

<OK> widget. Otherwise, select <Start Over> and re-enter a password.

The Solaris CDE opens on both displays.

4.2.2 Logging onto the simulator

The procedure in Table 4-2 defines the steps required to logon to the GPSS. It assumes successful logon to the SIMCON workstation.

Table 4-2 Logging onto the GPSS

Step Action Result

1 On the Simcon left display, right select the desktop if there is not a terminal window.

Otherwise, proceed to step 3.

The drop down Workspace Menu opens and indicates various user selections.

2 On the Workspace Menu, select Tools |

Terminal.

The terminal window opens on the left display.

3 On the left display terminal window, enter the following at the Unix prompt:

xhost + (include a space after xhost)

Select <Return> from the keyboard.

The Unix command is processed.

4 On the left display terminal window, enter the following at the Unix prompt:

susim

Select < Return > from the keyboard.

The Unix command is processed.

5 On the left display terminal window, enter the following at the Unix prompt:

startsim

Select < Return > from the keyboard.

The Simulator Login window opens on the left display.

6 On the Login window. select the Login Name text field box and enter the login name provided to you by the System Administrator.

Select the Password text field box and enter the password provided to you by the System

Administrator.

Select the <OK> widget.

The Alarms and Events window and the

Simulator Main Menu window opens on the left display, indicating a successful logon.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

4.2.3 Initializing the simulator

The procedure in Table 4-3 defines the steps required to initiate a simulation on the GPSS. It assumes successful access to the Simulator Main Menu window.

NOTE:

On the Execution/Playback Parameter Selection window, a Script object file name must first be selected by use of the corresponding <Select> widget before the Initial Conditions text field box can be enabled with the corresponding

<Select> widget.

Table 4-3 Initializing the GPSS

1 On the Simulator Main Menu window, select the

<Execution/Playback> widget.

The Execution/Playback Parameter

Selection window opens on the left display.

2 On the Execution/Playback Parameter Selection window, choose the <Select> widget corresponding to the text field box labeled Script or Session Log Name.

The Item Selection window opens on the left display indicating available directories in the Directories field box.

3 On the Item Selection window Directories field box, select the directory that contains the required script file name object.

The Item Selection window Object field box indicates the available files.

4 On the Item Selection window Object field box, select the appropriate script file name object.

The script file name object highlights and awaits a user action.

5 On the Item Selection window, select the

<Accept> widget.

The Item Selection window closes.

The Execution/Playback Parameter

Selection window activates.

The script file in the Script or Session Log

Name text field box indicates the selection.

6 On the Execution/Playback Parameter Selection window, choose the <Select> widget corresponding to the text field box labeled Initial

Conditions.

The Item Selection window opens on the left display indicating available directories in the Directories field box.

7 On the Item Selection window Directories field box, select the directory that contains the required

Initial Condition Set file name object.

The Item Selection window Object field box indicates the available files.

8 On the Item Selection window Object field box, select the appropriate Initial Condition Set file name object.

The file name object highlights and awaits a user action.

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011

9 On the Item Selection window, select the <Accept> widget.

The Item Selection window closes.

The Execution/Playback Parameter

Selection window activates indicating selected file names.

A defaulted time displays in the Initial

Conditions Start Time text field box.

10 On the Execution/Playback Parameter Selection window, select the <Execute> widget.

The Execution/Playback Parameter

Selection window parameters are accepted and the window closes.

Simulation initialization commences.

The Script Execution window opens on the left display.

The Alarms and Events window displays the following message after successful processing:

All models initialized

NOTE:

The GPSS can run independent from a Local MCS. To run the system in this mode, refer to Section 0 Executing a simulation independent from a local MCS.

4.2.4 Synchronizing with a local MCS

The procedure in Table 4-4 defines the steps required to synchronize the GPSS with a Local

MCS. It assumes successful initialization of the GPSS. If initialization fails, contact the System

Administrator.

Table 4-4 Synchronizing the GPSS with a Local MCS

Step Action Result

1 On the right Simcon display, right select the desktop.

The drop down Workspace Menu opens and indicates various user selections.

2 On the Workspace Menu, select <Tools |

Terminal>.

The terminal window opens on the right display.

3 On the right display terminal window, enter the following at the Unix prompt:

susim

Select <Return> from the keyboard.

The Unix command is processed.

4 On the terminal window, enter the following at the Unix prompt, including a space between rsh and simeng:

rsh simeng

Select <Return> from the keyboard.

The Unix terminal window displays a successful Simeng logon.

5 On the terminal window, enter the following at The Alarms and Events window will

NUMBER

MG50533001033U1

REV

B

DATE

11/30/2011 the Unix prompt, including the dot at the beginning and all spaces shown:

./do_all simcon:0.1

Select <Return> from the keyboard.

display the following message:

All models initialized

A Local MCS sim_clock, .check_comet, and standard_code window opens on the right display.

6 On the Script Execution window, select the <Sync> widget

The Sync Parameter window opens on the left display.

7 On the Sync Parameter window, select the text field box and enter a date/time combination approximately 5 minutes ahead of the Local MCS time located on the sim_clock window on the right display.

Format: YYYY.JDD HH:MM:SS, with JDD representing a three digit day of the year

Select the <Sync> widget. Otherwise, select the

<Cancel> widget to revoke the sync process.

The Script Execution window activates and awaits a user response.

After a processing delay, the Alarms and

Events window on the left display displays the following…