ss-pte-615_b.doc

CAGE CODE

Document Revision & Version History

Renumber Requirement IDs to Sections 3, 5 and Appendix A

TBD ITEMS

Table of Contents

11 SCOPE

11.1 Identification

11.2 System Overview

11.2.1 Global Positioning System

11.2.2 PTE Mission

11.2.3 History

21.2.4 Organization and Support Agencies

21.2.5 PTE Operations

21.3 Document Overview.

21.3.1 Document Requirements Terminology and Use

32 REFERENCED DOCUMENTS

32.1 Government Documents

32.2 Referenced Documents

43 REQUIREMENTS

43.1 States and Modes

43.2 Infrastructure

43.2.1 General

84 QUALIFICATION PROVISIONS

84.1 Test Program

84.1.1 Verification Method

94.2 Verification Methods

94.2.1 Demonstration

94.2.2 Test

94.2.3 Analysis

94.2.4 Inspection

105 REQUIREMENTS TRACEABILITY

136 NOTES

136.1 Acronyms

Appendix A Requirements Verification A-

List of Tables

10Table 5-1: Requirements Traceability Matrix

1 SCOPE

1.1 Identification

This Prime Item Development Specification (PIDS), SS-PTE-615, specifies the requirements and qualification provisions for the Global Positioning System (GPS) Positional Training Emulator (PTE). It includes the requirements and qualification provisions for the three components of PTE: the Global Positioning System (GPS) Operational Control System (OCS) Architecture Evolution Program (AEP), the GPS Satellite Training and Rehearsal Simulator (STAR Sim), and Instructor Control (IC).

1.2 System Overview

1.2.1 Global Positioning System

The GPS consists of three segments: the Space Segment, the Control Segment, and the User Segment. The Space Segment currently consists of IIA, IIR and IIF space vehicle block types. Within the control segment, the OCS consists of the AEP (command & control), the Ground Antenna(s) and the Monitor Stations. PTE trains GPS crews how to operate the entire space segment and the OCS.

1.2.2 PTE Mission

The mission of the PTE is to provide a realistic training environment that supports crew training and positional training for the Global Positioning System Operational Control System operators.

PTE provides a GPS training capability for Basic Operator (BOPR) Training and Advanced Operator Training that includes Vehicle Advanced, Payload Advanced, Crew Advanced and Navigation Warfare (NAVWAR) training.

1.2.3 History

The Air Force has an urgent requirement to train operational personnel on the new GPS AEP OCS currently being developed by Boeing. In conjunction with this effort, the Air Force has requested development of a Positional Training Emulator (PTE), which can provide a crew and positional training capability for the GPS Space Segment (SS) and OCS. Boeing will deliver the PTE in a classified software/ hardware configuration, which retains the training capabilities inherent in the AEP/GPS Simulator (GPSS) combination and adds capabilities specific to positional training and instructor control.

The need to develop an AEP PTE is documented in a memorandum, dated 21 November 2006, from the 50th Operations Group.

1.2.4 Organization and Support Agencies

The GPS Space Wing manages the GPS program. The program director is delegated the authority to develop, coordinate, and direct the GPS program. The Global Positioning System Wing (GPSW) develops and maintains the GPS, including the PTE..

1.2.5 PTE Operations

Air Force Space Command (AFSPC) is the PTE Operations Agency and all operating facilities within the PTE system are under the control and direction of AFSPC.

1.3 Document Overview.

The purpose of this document is to specify the requirements and qualification provisions of the PTE. The remaining paragraphs of this specification contain a list of referenced documents, the computer software requirements, the qualification provisions, requirements traceability and hardware linking the requirements specified in this element level specification, notes, and Verification Cross Reference Matrix (VCRM). This document is unclassified. Distribution and destruction of this document should follow the instructions specified on the title page of this document.

1.3.1 Document Requirements Terminology and Use

This specification and its supporting/subordinate specifications utilize the following requirements terminology:

a. A 'shall' identifies a requirement (or any portion thereof) that is being designed, built and unless otherwise stated, tested. Each 'shall' is uniquely numbered for identification and traceability.

b. A 'must' identifies a requirement that is not being designed, built or tested, but is a system design constraint or provision that is being provided to the designer by the government (upon which the designer is dependent). 'Musts' are not numbered, and thus there is no provision for unique identification or traceability.

c. The conventional usage of 'wills' for government furnished equipment/property (GFE/GFP) etc., is now handled as described above (now using 'musts'), except in the cases where the portion of the system being designed is not dependent upon the GFE/GFP (which is identified by the use of 'will'). 'Wills' are not numbered, and thus there is no provision for unique identification or traceability.

2 REFERENCED DOCUMENTS

2.1 Government Documents

The following documents, for the issues shown, form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification supersede the contents of the referenced documents.

2.2 Referenced Documents

3 REQUIREMENTS

3.1 States and Modes

3.2 Infrastructure

3.2.1 General

PTE shall use a consolidated hardware architecture able to run AEP, SIM, and IC software with no external interface connectivity.

The PTE MCS hardware suite does not include the following components found in the operational MCS:

· Crypto servers

· Server redundancy (no failover capability)

· Mission Operations Transfer (MOX) hardware suite

· Almanac PC

· SBMCS PC

PTE shall provide a training system that incorporates baseline AEP and Global Positioning System Simulator (GSS) software.

PTE shall provide a single universe for all student sessions consisting of a single constellation of GPS satellites with S-Band and L-Band ground stations.

PTE shall provide a positional training system that can be used for training tasks for the SSO,SVO,PSO, MC, MCH and NWO positions.

PTE shall support crew training for up to six different crew positions.

PTE shall allow students to be able to determine the functional status from displays and indicators and individually interact with instructor assigned scenarios.

3.2.7 Training Features

PTE shall permit the instructor to inject anomalies (SV, ground station).

PTE shall permit the instructor to create and modify scenario scripts.

PTE shall permit the instructor to create and modify training scenarios.

PTE shall permit the instructor to execute scenario scripts.

PTE shall permit the instructor to monitor student displays.

PTE shall permit the instructor to control Startup and Shutdown.

PTE shall permit configuration of scenario initial conditions to support multiple independent student training.

PTE shall permit pause and resume operation.

PTE shall permit fast and slow forward operations.

PTE shall permit state save and restore operations.

PTE shall permit logging of student activities.

3.2.8 Operator Training

PTE shall provide a positional training system that can be used for BOPR training tasks for up to 10 SSO students simultaneously.

PTE shall provide a positional training system that can be used for Vehicle Advanced training tasks for up to 10 SVO students simultaneously.

PTE shall provide a positional training system that can be used for Payload Advanced training tasks for up to 10 PSO students simultaneously..

PTE shall provide a positional training system that can be used for Crew Advanced training tasks for up to 10 MC/MCH students simultaneously.

PTE shall provide a positional training system that can be used for NWO training tasks for up to 10 NWO students simultaneously.

4 QUALIFICATION PROVISIONS

4.1 Test Program

For PTE, a Formal Qualification Test (FQT) event will not be performed as part of the rapid prototype process. Instead, demonstrations of the capabilities are performed with Air Force participation.

Formal test procedures will not be designed and generated. Instead, the Air Force training scenarios are used in place of test procedures. Since the training scenarios are essentially the GPS operating procedures, and the operating procedures have already been approved, there is no need to peer-review and re-approve the training scenarios for use in the verification demonstrations. Therefore, the verification method for requirements in this document (Appendix A) will be verified through demonstration.

Exception: Test procedures or scripts shall be used to demonstrate the set of Instructor Capabilities.

Verification Sheets (VS) are generated prior to each capability demonstration, which concisely describes how each capability is demonstrated. The VS is signed before and after each demonstration to document the agreement between the Air Force and Boeing. Signed VS are impounded by Quality Assurance (QA).

All demonstrations will be conducted at the Boeing GPS Center, witnessed by both the 50th Operational Support Squadron (OSS), GPSW, and Boeing QA.

The following are accomplished for rapid prototype test and verification activities:

· Develop and exercise training scenarios as the system develops

· Obtain Air Force concurrence throughout the process (not just at the end)

· Air Force participation in development and exercise of training scenarios

· Reconcile system functionality with capabilities list

· The Air Force will rate the training tasks performance based on pass/fail

· Boeing QA will witness demonstrations

· Discrepancies will be noted during demonstrations

· If necessary, software will be updated between individual capability demonstrations to achieve a passing rating.

4.1.1 Verification Method

The contractor's test program will qualify each requirement in Appendix A.

4.2 Verification Methods

4.2.1 Demonstration

Demonstration is the operation of the system, or a part of the system, that relies on observable functional operation not requiring the use of instrumentation, special test equipment, or subsequent analysis.

4.2.2 Test

Test is the operation of the system, or a part of the system, using instrumentation or other special test equipment to collect data for later analysis.

4.2.3 Analysis

Analysis is the analytical processing of accumulated data obtained from studies, calculations, analysis, modeling and/or other qualification methods. Examples are reduction, interpolation or extrapolation of test results.

4.2.4 Inspection

Inspection is the visual examination of system components, documentation, etc.

5 REQUIREMENTS TRACEABILITY

Table 5-1: Requirements Traceability Matrix

6 NOTES

6.1 Acronyms

7 Appendix A Requirements Verification

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

� EMBED Word.Document.8 \s ���

Officially Released

09 July 2009

Signatures on File

Officially Released

27 October 2009

Signatures on File i

_1318139551.doc

PREPARED BY

CAGE CODE 2D605

NUMBER

REVISION

Larry Oshiro

SS-PTE-615

B

The Boeing Company

TYPE

APPROVALS

ENGINEERING

AUTHORITY

CS SEIT –

Ryan Witham

WBS 440

PRIME ITEM DEVELOPMENT SPECIFICATION

DATE

9/9/09

TOTAL PAGES

SUBJECT:

EFFECT ON RELEASE TO FILES

CHANGE/RELEASE

PSDR/NR

PRIME ITEM DEVELOPMENT SPECIFICATION

FOR THE

POSITIONAL TRAINING EMULATOR

OF THE

GLOBAL POSITIONING SYSTEM BLOCK IIF

CONTRACT NO. F04701-96-C-0025

ADPL SEQUENCE NO. ADP 102-B

Prepared for:

U.S. AIR FORCE

HEADQUARTERS SPACE & MISSILE SYSTEMS CENTER

LOS ANGELES, CA 90009-2960

Prepared by:

The Boeing Company

Seal Beach, CA 90740

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.