SS_GIN_660_25 Jan 11signed.pdf

ii 25 January 2011 SS-GIN-660

Document Version History

Version Date Event

Initial Release 25 January 2011 Initial Authentication

SS-GIN-660 25 January 2011 1

1.0 SCOPE

1.1. Identification.

This specification documents requirements for the GPS Information Network (GIN), formally known as the Communication Set, Satellite AN/FYN-1.

1.1.1. History.

1.1.1.1. The original design of the GPS Operational Control System (OCS) focused on long term maintenance of GPS performance in accordance with global specifications. Real-world operational experience in supporting the growing population of GPS users has demonstrated the need to more closely tie constellation management to changing user needs. It has also demonstrated the users’ need for better and timelier constellation status and performance information.

1.1.1.2. In 1998, the Air Force convened a panel to address the effectiveness of the support products and services being provided to military and civil GPS users. The panel recommended the creation of a user-oriented center to provide technical assistance, to conduct performance assessments, and to assist in anomaly detection and resolution. The Secretary of Defense, responding to real-world events and the findings of the review panel, tasked the Commander in Chief of U.S. Space Command (CINCSPACE) to take the lead. In response, United States Space Command (USSPACECOM (now United States Strategic Command [USSTRATCOM])) established a GPS Support Center (GSC). Responsibility for the GSC was subsequently transferred to 14th Air Force (14 AF) to provide more effective support. The GSC became the GPS Operations Center (GPSOC).

1.1.2. Operational Role. Presently, the GPSOC is the 2d Space Operations Squadron (2 SOPS) operational center for the operation, maintenance and exploitation of GPS. It brings together in one organization the expertise, data fusion, and visualization capabilities, security clearances, and performance information required to maintain, operate and employ GPS to produce a desired effect at any time or location for military, civil or allied users across the full spectrum of conflict. It brings together GPS operations, analysis, and Navigation Warfare (NAVWAR) capabilities to form a single effects-based center capable of supporting the national security strategy while complying with all national and international civil requirements.

1.1.3. Functions of the GPS Information Network. The GIN is the set of hardware, software and communications capabilities within the GPSOC needed to fulfill the GPSOC mission. The purpose of the GIN is to serve these needs as the primary tool for achieving desired GPSOC capabilities. The GIN provides nine basic types of electronic datasets: Performance Assessment Files (PAFs) Near-real time PAFs (NPAFs), Prediction Support Files (PSFs), Satellite Outage Files (SOFs), Near-real time SOFs (NSOFs), Almanacs, Navigation Message Replacement Files (NMRs), Predicted Ephemeris/State Vector Data Files (PREDs), and a Broadcast Navigation Message File (NAV).

2 25 January 2011 SS-GIN-660

1.1.3.1. The PAF provides cumulative daily instantaneous orbit and clock errors every 15 minutes for each operational GPS satellite and error rates to support short term prediction of errors. This information may be used to generate user instantaneous position/time error vector estimates for any user-specified time and location.

1.1.3.2. NPAFs are issued every 15 minutes, and contain one record of position/time error vector estimates for the associated epoch only.

1.1.3.3. The PSF provides orbit and clock error root mean square (RMS) values that may be used to compute predicted user position/time error statistics for any user-specified time and location.

1.1.3.4. The SOF provides a running history of all historical, current, and predicted satellite outages in a form that allows a user to easily determine constellation status at any time or location.

1.1.3.5. NSOFs are intended to give changes to satellite state of health between updates of SOFs. NSOF settings are based on the satellite subframe 1 health setting.

1.1.3.6. The GPSOC almanac provides the clock and ephemeris parameters and is a different file format than the Yuma and System Effectiveness Model (SEM) almanacs provided by the 2 SOPS. Differences include increased precision and a separate calculation of the user range accuracy (URA) index.

1.1.3.7. The NMR file provides a zero age of data replacement navigation message for the transmitted navigation message.

1.1.3.8. The PRED file provides predicted position and velocity vectors in Earth- Centered Inertial (ECI) coordinates, clock bias, clock drift and clock drift rate.

1.1.3.9. The NAV file contains a hexadecimal representation of the as-broadcast 50 bit per second navigation data message from each satellite. It only applies to the GPS satellites managed by the US Air Force, and thus does not reflect data from other Global Navigation Satellite Systems or augmentation satellites, such as those in the Wide Area Augmentation System (WAAS) and European Geostationary Navigation Overlay Service (EGNOS) constellations. NAV data is updated and posted to GPSOC GPSIS web sites at a rate determined by the GPSOC.

1.2. Document Overview.

This specification establishes performance, design, development, and test requirements for the GIN. It is a multi-purpose specification containing requirements for the mission software tools used to generate the data employed to support the GPSOC mission as well as a description of the existing GIN hardware and software

SS-GIN-660 25 January 2011 3 components presently implemented to accomplish GPSOC functions. The specification provides a baseline for future sustainment and improvement of the GIN.

1.3. Document Requirements Terminology and Use.

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

1.3.1. A “shall” is used to identify a requirement (or any portion thereof) which is being designed, built, and unless otherwise stated, tested. Each “shall” is uniquely numbered for identification and traceability. Each “shall” is allocated to system components, test phase, and a verification method.

1.3.2. A “must” is used to identify 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 and which the designer depends on. Each “must” is uniquely numbered for identification and allocation. Each “must” is only allocated to system components for design guidance (no traceability to lower-level specifications), but not to a test phase or verification method. A “must” is not traced to lower-level computer software configuration items (CSCIs) specifications. This version of the specification has no "musts.”

1.3.3. The conventional usage of “wills” for Government Furnished Equipment/Property (GFE/GFP), etc., is now handled herein 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. “Wills” are not further allocated to system components, test phase or verification method.

2.0. 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.1.1. Specifications.

2.1.1.1. Federal.

None.

2.1.1.2. Military.

None.

2.1.1.3. Other Government Activities.

4 25 January 2011 SS-GIN-660

Table 2.1. Authenticated Documents.

Designator/Issue Document Title

IS-GPS-200D

Current Issue

NAVSTAR GPS Space Segment/Navigation User Interfaces

ICD-GPS-410

Current Issue

NAVSTAR GPS Master Control Station/GPS-SISP Interface System (GSIS) Interfaces

SS-CS-600

Current Issue

System Specification for the Operational Control System of the NAVSTAR Global Positioning System

ICD-GPS-602

Current Issue

IRN-602A-002

27 July 2006

NAVSTAR GPS Operational Control System/Operational Support System Interfaces

IDD-GPSIS Version 16 December 2009

GPS Operations Center Interface Description Document (IDD)

2.1.2. Standards.

2.1.2.1. Federal.

None.

2.1.2.2. Military.

None.

2.1.2.3. Other Government Activities.

None.

2.1.3. Drawings.

None.

2.1.4. Other Publications.

2.1.4.1. Manuals.

SS-GIN-660 25 January 2011 5

Table 2.2. Manuals.

Designator/Issue Document Title

DoD 5220.22-M February 2006

National Industrial Security Program Operating Manual

DoDD 8500.01E.

24 October 1985

Information Assurance

NAVSTAR GPS SPG

1 August 1997

NAVSTAR Global Positioning System Protection Guide, Military Signal Development

31S1-2FYN1-1 Operations Instructions – Global Positioning System Information Network

31S1-2FYN1-2 Operations and Maintenance Instruction – Organizational Maintenance, Global Positioning System Information Network

31S1-2FYN1-06 Work Unit Code Manual – Global Positioning System Information Network

31S1-2FYN1-6WC-1 Work Cards – Scheduled Maintenance for Global Positioning System Information Network

2.1.4.2. Regulations.

2.1.4.3. Handbooks.

None.

2.1.4.4. Bulletins.

None.

2.2. Non-Government Documents.

The following documents of the exact issue shown form a part of this specification to the extent specified herein. In the event of conflict between documents referenced herein and the contents of this specification, the contents of this specification are considered superseding requirements.

2.2.1. Specifications.

None.

2.2.2. Standards.

None.

2.2.3. Drawings.

6 25 January 2011 SS-GIN-660

3.0. REQUIREMENTS.

3.1. Required States and Modes.

Table 3.1. States and Modes Requirements.

Identifier Requirement Description

GIN 001 The GIN CSCI shall have one state, the active state.

GIN 004 GIN applications shall have an operational-primary mode.

GIN 005 GIN applications shall have an operational-backup mode.

GIN 006 If the operational-primary GIN fails, the operational-backup shall assume the role of operational-primary and all processing associated with operational-primary.

GIN 008 Those GIN applications in the operational-backup mode will perform the same processing associated with operational-primary mode, but applications designated as operational-backup will not distribute their data to the network.

GIN 171 The GIN functionality shall be duplicated at the Alternate Master Control Station (AMCS).

3.2. GIN capability requirements.

3.2.1. GIN Control.

3.2.1.1. Initialization.

Table 3.2. Initialization Requirements.

Identifier Requirement Description

GIN 009 Upon initialization, GIN shall initialize based on predefined parameters.

GIN 010 Upon initialization, GIN applications shall report their status to the operator.

SS-GIN-660 25 January 2011 7

3.2.1.2. Failure and Recovery.

Failure conditions for GIN include:

a. a processor failure where GIN is running

b. a single GIN application failure.

Table 3.3. Failure and Recovery Requirements.

Identifier Requirement Description GIN 011 The GIN shall display error messages if program initialization fails.

GIN 016 GIN applications shall maintain an operational mode in the event of a single hardware or software failure.

GIN 017 Upon recovery from a failure condition, GIN shall recover a failed application to a previous known operational condition.

GIN 018 GIN shall advance a recovered application to the current system time.

GIN 026 No failure of other OCS non-GIN mission applications shall cause a failure of GIN components. "Mission applications" exclude infrastructure components such as the operating system, inference engine, database engine, X Window, Motif, etc.

3.2.1.3. Operator Controls and Displays.

Table 3.4. Controls and Displays Requirements.

Identifier Requirement Description

GIN 027 The GIN shall provide administrator controls for managing application operations, setting mission paths, modifying system editing criteria and setting exception handling conditions.

GIN 028 The GIN shall provide administrator controls that enable or disable incoming record acceptance, parsing and storage.

GIN 065 The GIN shall provide the capability for mission analysts to enter satellite status information.

GIN 126 The GIN shall provide the capability for analysts to edit and add to incoming intelligence data based on discussions with intelligence agencies and the Joint Navigational Warfare Center (JNWC).

GIN 136 The GIN shall provide the capability to create new catalog objects.

8 25 January 2011 SS-GIN-660

GIN 137 The GIN shall provide the capability to modify existing catalog objects.

GIN 147 The GIN's analysis tools shall provide the capability to save customized report templates for continued use.

GIN 158 The GIN shall provide the capability for the analyst to automatically exclude NMR data for a given satellite when the satellite is set unhealthy.

GIN 159 The GIN shall provide the capability for the analyst to automatically exclude PAF data for a given satellite when the satellite is set unhealthy.

GIN 160 The GIN shall provide the capability for the analyst to automatically exclude PAF data for a given satellite when the satellite fails a system-specified 4-sigma test.

GIN 162 The GIN shall provide the capability for the analyst to reset a satellite’s PSF data whenever a performance transient occurs or in the event of a major configuration change.

GIN 163 The GIN shall provide mission analysts with the capability to build a template and generate a custom report from data items in the GIN database.

3.2.1.4. Termination.

Table 3.5. Termination Requirement.

GIN 032 Upon request, GIN applications shall terminate.

SS-GIN-660 25 January 2011 9

3.2.2. GIN Services.

3.2.2.1. Constellation Status and Situational Awareness.

Table 3.6. Status and Situational Awareness Requirements.

Identifier Requirement Description

GIN 068 The GIN shall be capable of conducting sanity checks on new Notice Advisory to Navstar Users (NANUs) for items such as date, satellite identity, and type of NANU.

GIN 069 The GIN shall be capable of automatically updating its internal satellite status record based on reception of GPS navigation messages indicating a change in satellite health.

GIN 072 The GIN shall compute elevation and azimuth angles for each Space Vehicle (SV)-Monitor Station (MS) pair, coincident with a state update.

GIN 073 The GIN shall compute Precise Positioning Service (PPS) Estimated Range Deviation (ERD) values for each SV-MS pair when the satellite is above a mission analyst-specified mask angle, coincident with a state update.

GIN 074 The GIN shall compute the instantaneous difference between ERD/OCS Observed Range Deviation (ORD) pairs for each SV-MS pair.

GIN 075 The GIN shall compute the instantaneous difference between GIN ERD/ORD pairs for each SV-MS pair.

GIN 081 The GIN shall be capable of distinguishing between data transients due to internal OCS processing artifacts and true satellite service aberrations.

GIN 094 The GIN shall compute and generate GPS Zero Age of Data (ZAOD) navigation message sub-frames 1-3 in accordance with IS- GPS-200D at every current state estimate update.

GIN 096 The GIN shall compute current ZAOD navigation message fit statistics at every current state estimate update.

10 25 January 2011 SS-GIN-660

3.2.2.2. Global Performance Monitoring.

Table 3.7. Performance Monitoring Requirement.

Identifier Requirement Description GIN 100 The GIN's analysis tools shall be capable of displaying global real time PPS user position/time GIN error estimate values.

GIN 101 The GIN's analysis tools shall be capable of displaying global real time Standard Positioning Service (SPS) user position/time solution error estimate values.

3.2.2.3. Automated Performance and Status Checks and Alarms.

Table 3.8. Automated Performance and Status Checks and Alarms.

Identifier Requirement Description

GIN 029 The GIN shall provide a centralized Alarms, Warning and Events (AWE) tracking and display capability that allows any operations function to register AWEs for inclusion.

GIN 030 The GIN shall provide a mechanism to ensure alarms indicating a critical mission problem are easily identifiable by the mission analyst.

GIN 077 The GIN shall conduct threshold checks on each ORD value for each SV-MS pair, using analyst specified thresholds.

GIN 078 The GIN shall conduct threshold checks on each ERD value for each SV-MS pair, using analyst specified thresholds.

GIN 082 If any of the threshold checks fail, the GIN shall generate an alarm detailing the specific failure to the GPSOC mission analyst.

GIN 083 The GIN shall generate an alarm in the event that a satellite’s ORD is missing for all monitor stations in view above the specified mask angle.

GIN 172 The GIN shall monitor each incoming interface to assess the availability of required datasets, and generate AWEs positively indicating the status of expected incoming data.

SS-GIN-660 25 January 2011 11

3.2.2.4. Performance/Tactical Analysis and Visualization Tools.

Table 3.9. Performance/Tactical Analysis and Visualization Tool Requirements.

Identifier Requirement Description

GIN 098 The GIN's analysis tools shall be capable of running in real time mode using real time data products as inputs, in accordance with the current GIN Interface Design Description (IDD), and displaying instantaneous PPS user position/time solution error estimates as specified by the analyst on a global 1 degree x 1 degree map.

GIN 099 The GIN's analysis tools shall be capable of running in real time mode using real time data products as inputs and computing instantaneous SPS user position/time solution error estimates as specified by the analyst on a global 1 degree x 1 degree map.

GIN 103 Instantaneous Position, Navigation and Timing (PNT) error estimates, predicted error and Dilution of Precision (DOP) values generated by the GIN's analysis tools shall meet GPSOC tool output consistency standards when running a validated GPSOC “truth” scenario.

GIN 104 Daily DOP, PNT accuracy and prediction summary statistics generated by the GIN's analysis tools shall meet GPSOC tool output consistency standards when running a validated GPSOC “truth” scenario.

GIN 105 The GIN's analysis tools shall be capable of automatically inserting the correct health settings for the constellation based upon SOF and NSOF contents, while providing a mission analyst override if necessary.

GIN 106 The GIN's analysis tools shall be capable of executing at an analyst-specified time step from at least one second up to 15 minutes.

GIN 107 The GIN's analysis tool shall be capable of executing the following within 1 hour:

- 2 degree x 2 degree global grid

- All-in-view position solution

- One minute time step over 24 hours

- 5 degree mask angle 80cm RMS Pseudo-Range Residual (PRR) for a stationary receiver

12 25 January 2011 SS-GIN-660

GIN 108 The GIN's analysis tools shall be capable of completing the analysis cycle for a minimum of six Areas of Operation (AOOs) for a set of best-four satellite DOP and prediction runs within three hours, employing no more than 50% of processing capacity.

GIN 109 The GIN's analysis tools shall be capable of completing the analysis cycle for twelve AOOs for a set of six all-in-view and six best-four satellite PPS PNT error assessment runs within three hours, employing no more than 50% of processing capacity.

GIN 110 The GIN's analysis tools shall be capable of generating the (referenced) reports and plots, to include analyst controls for selection of colors, legends and specified text fields.

GIN 111 The GIN's analysis tools shall be capable of generating graphical images of analyst-selected performance parameters over a region and period of time, to include analyst controls for selection of colors, legends and specified text fields.

GIN 112 The GIN's analysis tools shall be capable of inserting a (planned or as-executed) satellite maneuver into an analysis scenario.

GIN 113 The GIN's analysis tools shall be capable of offsetting a current satellite slot by an analyst-specified Geographic Longitude of the Ascending Node (GLAN) value to support constellation rephasing decisions.

GIN 114 The GIN's analysis tools shall be capable of outputting raw data into an American Standard Code for Information Interchange (ASCII) format that can be imported into commercial off-the-shelf (COTS) or other external analysis tools.

GIN 115 The GIN's analysis tools shall be capable of retrieving and displaying archived scenario outputs from any workstation within the Operations Center (OC) (at the same security level).

GIN 119 The GIN's analysis tools shall be capable of evaluating Signal in Space (SIS) User Range Error (URE) and availability of signals for space borne users out to geosynchronous orbit.

GIN 120 The GIN shall provide the capability to visualize satellite coverage, visibility of satellites to OCS ground resources, and constellation visibility for any analyst-specified location.

SS-GIN-660 25 January 2011 13

GIN 128 The GIN's analysis tools shall support the development and integration of emitter catalog objects.

GIN 129 The GIN's analysis tools shall provide the capability to employ emitter catalog objects in theater support analyses.

GIN 131 The GIN's analysis tools shall provide the capability to use Digital Terrain Elevation Data (DTED) at any of the available levels of fidelity in theater supported analyses.

GIN 133 The GIN's analysis tools shall provide the capability to determine the effect of ground wave propagation on GPS satellite signals and in-band emitters.

GIN 135 The GIN shall provide the capability to maintain a catalog of objects that represent the key functional and performance attributes of GPS satellites, GPS receivers, GPS antenna and platforms that have GPS integrated into their system.

GIN 140 The GIN catalog object generation capabilities shall include the capability to model a Controlled Reception Pattern Antenna (CRPA).

GIN 141 The GIN's analysis tools shall provide the capability to model aided receivers and integrated user navigation systems.

GIN 142 The GIN's analysis tools shall be capable of generating a mission route based upon waypoints, velocity, orientation and platform attributes information provided by a theater user.

GIN 143 The GIN's analysis tools shall be capable of computing an estimate of instantaneous GPS performance for a point, a region or along a specified route in a theater of operations.

GIN 144 The GIN's analysis tools shall be capable of computing a service availability metric that ties to specific theater mission needs.

GIN 148 The GIN's analysis tools shall provide the capability to generate and display visual depictions of analysis results on a two-dimensional map.

14 25 January 2011 SS-GIN-660

GIN 150 The GIN's analysis tools shall provide the capability to generate contour plots for Jammer to Signal ratio (J/S) and Carrier to Noise ratio (C/No) information, with analyst-specified thresholds and plotting levels.

GIN 151 The GIN's analysis tools shall provide the capability to save analysis scenarios and edit them at a future time.

GIN 152 The GIN shall provide basic templates for conducting post-analysis evaluations of end-user mission effectiveness given the user’s mission success criteria.

3.2.2.5. Data Storage and Archive.

Table 3.10. Data Storage and Archive Requirements.

Identifier Requirement Description

GIN 014 The unclassified web site shall provide a directory structure and appropriate accesses that allows mission analysts to post standard and custom analysis products.

GIN 031 The GIN shall retain all incoming (and enabled) raw data records in temporary storage.

GIN 033

The GIN shall conduct automated checks with operator defined tolerance on selected data.

GIN 034

The GIN shall store and make accessible all parsed data in database raw data tables.

GIN 035

The GIN shall provide the capability to store and make accessible all edited data and analysis datasets generated by the solution.

GIN 036

The GIN shall provide the capability to automatically archive database contents to a long-term storage medium.

GIN 037

The GIN shall provide on-line storage sufficient to maintain a minimum of 180 days of operational data in the real-time operational system.

SS-GIN-660 25 January 2011 15

GIN 067 The GIN shall maintain a database of all previous, current and planned NANUs.

GIN 102 The GIN's analysis tool outputs for key parameters shall be demonstrated to meet threshold consistency standards.

GIN 127 The GIN shall maintain a library of known emitter characteristics as objects in an emitter catalog.

GIN 164 The GIN shall maintain a database of reported anomalies.

GIN 166 The GIN shall maintain a database of user-identified Radio Frequency Interference (RFI) sources.

3.2.2.6. Automated Report Generation.

Table 3.11. Automated Report Generation Requirements.

Identifier Requirement Description

GIN 087 The GIN shall be capable of displaying running 24 hour plots of every satellite’s PPS global RMS ERD.

GIN 116 The GIN's analysis tools shall be capable of automatically generating a series of outputs based upon a base scenario and a variational parameter specified by the mission analyst.

GIN 117 The GIN's analysis tools shall be capable of generating a summary report of results from a set of variational analysis runs.

GIN 145 The GIN's analysis tools shall provide the capability to build a custom report containing specific information required to respond to a specified analysis objective.

GIN 156 The GIN shall provide the capability to automatically generate all the reports identified in the GIN IDD.

GIN 161 The GIN shall generate daily global RMS ERD as well as Radial- Alongtrack-Crosstrack (RAC) orbital coordinate system and clock statistics based upon the the previous seven day interval, to support generation of the PSF.

16 25 January 2011 SS-GIN-660

GIN 165 The GIN shall provide the capability to search the anomaly tracking data base and generate reports based on the correlation of analyst-specified key variables.

3.2.2.7. Automated Data Report Transfers to Secret Internet Protocol Router Network (SIPRNET) Web Server.

Table 3.12. Data Report Transfers to SIPRNET Web Server Requirements.

Identifier Requirement Description

GIN 023 The GIN shall provide the capability to post Interface Specification records to a File Transfer Protocol (FTP) directory on the GIN’s SIPRNET web server.

GIN 024 The GIN shall provide the capability to dynamically generate appropriate directories on the SIPRNET web FTP server for posting of Interface Specification records.

GIN 025 The GIN shall provide the capability to automatically transfer GPSOC IDD records to the appropriate SIPRNET web FTP server directories.

3.2.2.8. Web Services.

Table 3.13. Web Services Requirements.

Identifier Requirement Description

GIN 013 The GIN shall include an unclassified Global Information Grid (GIG) compliant web site.

GIN 015 The unclassified web site shall provide a directory structure and appropriate accesses that supports an archive of past data for convenient access by service users.

GIN 019 The GIN shall include a secret-level GIG-compliant web site.

GIN 020 The secret-level web site shall provide a directory structure and appropriate accesses that allow mission analysts to post standard and custom analysis products.

SS-GIN-660 25 January 2011 17

GIN 021 The secret-level web site shall provide a directory structure and appropriate accesses that supports an archive of past data for convenient access by users.

GIN 022 The secret-level web site shall provide a directory structure and appropriate accesses that allows the GIN to automatically post near real-time and daily Information Service (IS) data.

GIN 168 The secret-level GIN located within the primary Master Control Station (MCS) shall incur no more than 30 minutes of downtime over any 24 hour interval as a threshold, given the primary MCS is in an operational state.

3.3. GIN Interface Requirements.

3.3.1. GIN External Interfaces.

Table 3.14. External Interface Requirements.

Identifier Requirement Description

GIN 003 The GIN shall have a real-time and continuous interface with the

GPS OCS.

GIN 007 The GIN shall have a real-time and continuous interface with national intelligence agencies.

GIN 012 The Interface Specification shall be the single source for documenting the automated data service interface between the GIN and GIG.

GIN 146 The GIN's analysis tools shall provide the capability to output data in an ASCII format suitable for use in external analysis tools.

3.3.2. GIN Internal Interface Requirements.

All internal interfaces of the GIN CSCI have been left to design.

18 25 January 2011 SS-GIN-660

3.3.3. GIN Internal Data Requirements.

All decisions about the internal data of the GIN CSCI have been left to design.

3.4. Adaptation Requirements.

This section is not applicable to this specification.

3.5. Safety Requirements.

This section is not applicable to this specification.

3.6. Security and Privacy Requirements.

Table 3.15. Security and Privacy Requirements.

Identifier Requirement Description

GIN 002 The GIN shall conform to the Certification and Accreditation package for the OCS.

3.7. GIN Environment Requirements.

The GIN shall operate in a standard office environment.

3.8. Computer Resource Requirements.

3.8.1. Computer Hardware Requirements.

The as-built GIN employs the following major equipment components in the quantities and locations specified below.

Table 3.16. GIN Major Equipment.

Product Model # Manufacturer Location Machine Name

Description Qty

PowerEdge 1950 Dell MCS CS1N1, CS1N2

Database Server

PowerEdge 1950 Dell MCS GWSRV1, GWSRV2

Gateway Server

SS-GIN-660 25 January 2011 19

PowerEdge 1950 Dell AMCS GWSRV1, GWSRV2

Gateway Server

PowerEdge

1950 Dell MCS MISCSRV Misc Server 1

PowerEdge 1950 Dell MCS GLEN-

GPSOCX1-

S, GLEN-

GPSOCX2-

S

Web Transfer Server

PowerEdge 1950 Dell MCS GLEN-

GPSOCW1-

S

SIPR FTP

Server

PowerEdge 1950 Dell MCS DC1, DC2 Domain Controller

PowerEdge 1950 Dell AMCS DC1, DC2 Domain Controller

PowerEdge 1950 Dell AMCS DBSRV1 Database Server

PowerEdge 1950 Dell AMCS FILESRV1 File Server 1 Rackmount

LCD/KVM

LCD

1U17-01

Synergy Global Technology

MCS KVM KVM

Workstation

Rackmount

LCD/KVM

LCD

1U17-01

Synergy Global Technology

AMCS KVM KVM

Workstation

APC

Smart-UPS

750 APC MCS APC UPS Uninterruptibl e Power Supply

APC

Smart-UPS

750 APC AMCS APC UPS Uninterruptibl e Power Supply

Dell/EMC AX150i Networked Storage System

AX150i Dell MCS SAN1, SAN2

Storage area network

Dell/EMC AX150i Networked Storage System

AX150i Dell MCS SAN1 Storage area network

20 25 January 2011 SS-GIN-660

Cisco 1841 Integrated Services Router

1841 Cisco MCS GIN-

MCS_RTR1

, GIN-

MCS_RTR2

Input Router 2

Cisco 1841 Integrated Services Router

1841 Cisco AMCS GIN-

MCS_RTR1

, GIN-

MCS_RTR2

Input Router 2

Cisco Router

1841 Cisco MCS SIPRXFER

1_RTR

SIPRNET

Router

Dell PowerVault 114T

114T Dell Tape Drive Tape Drive 1

Amp Interconne ct

Amp FIBER

PATCH

PANEL

Fiber Patch Panel

Switch

2724 Dell MCS GIN_SW1 Switch for storage area network

Switch

2724 Dell AMCS SAN_SW 1

Dell PowerCon nect Fast Ethernet Switch

3424 Dell AMCS GIN_SW1 Switch for

GIN LAN

Dell PowerCon nect Fast Ethernet Switch

3424 Dell MCS SAN_SW Switch for

GIN LAN

Pulizzi AMCS Pulizzi Power Strip 2

3.8.2. Computer Hardware Resource Utilization Requirements.

This section has been tailored out.

3.8.3. Computer Software Requirements.

The as-built GIN employs the following major software components in the various hardware items previously listed in 3.8.1.

SS-GIN-660 25 January 2011 21

Table 3.17. GIN Major Software Components.

Name/Nomenclature Version Notes Manufacturer Type (i.e., Operating

System [OS], Data Base

Management System [DBM], etc.)

Cisco IOS 12.4 (3C) Router software CISCO CISCO OS Windows XP Professional

SP3 Workstation software (15+ copies)

Microsoft OS

Office/Outlook Microsoft Productivity Windows 2003 Server

Server software Microsoft OS

Windows Server Ent Ed SP1

SP1 Server software-

MISCSRV1

Microsoft OS

Windows Server Ent Ed SP2

SP2 Server software Microsoft OS

MS SQL Server 2005 Enterprise database software

Microsoft DBM

GPS Interference and Navigation Tool

(GIANT)

4.0 GPS performance

analysis software

SMC/XRDA

(USAF)

GOTS

Realtime GIANT Nav Analyst Workstation

US Govt Analysis

Windows Routing and Remote Access Basic Firewall

SIPR terminal software

Microsoft Firewall

FootPrints Database software –

MISCSRV1,

SAN2

Numara DBM

Backup Exec Backups US Govt Utility

IIS (HTTP, SMTP) SAN1, GLEN-

GPSOCW-1S

US Govt Utility

Symantec MISCSRV Symantec Security MS Visual Studio Lab for Software

Development Microsoft Visualization

GIN Data Processor GIN Application software

US Govt Application

GIN File Mover I US Govt Utility

22 25 January 2011 SS-GIN-660

Name/Nomenclature Version Notes Manufacturer Type (i.e., Operating

System [OS], Data Base

Management System [DBM], etc.)

GIN File Mover II GLEN-GPSOCX1-

S, GLEN-

GPSOCX2-S

US Govt Application

GIN File Server US Govt Utility GIN Gateway Controller

Gateway Controller software

US Govt Communications

GIN Nav Analyst GIN Application software

US Govt Application

GIN Realtime ERD GIN Application software

US Govt Application

FLARE SAN1, SAN2 (Dell AX150i)

Dell Utility

3.8.4. Communications Requirements.

3.8.4.1. GIN Communications with the Master Control Station (MCS).

The GIN communicates with the MCS through a router to router connection at a continuous 100 Mbps data rate using the ICD-GPS-602A protocol providing a synchronous serial interface.

3.8.4.2. GIN Communications via SIPRNET.

The GIN interfaces to the SIPRNET via a SIPRNET web server which hosts the GPSOC classified web site and supports transmission of near real-time data to registered users. The web server is isolated from the GIN by a router, firewall and a SIPRNET terminal.

3.9. Software Quality Factors.

This section has been tailored out.

3.10. Design and Implementation Constraints.

SS-GIN-660 25 January 2011 23

3.10.1. Software required to integrate, communicate with or support COTS and/or Non- Developmental Items (NDI) software need not be developed in Ada.

3.10.2. COTS software must not be modified without prior government approval.

3.10.3. Approved modifications to COTS software written in another language need not be developed in Ada.

3.11. Personnel Related Requirements.

Design of the GIN will be such that the number of direct operation and maintenance personnel required will be minimized. The GIN equipment shall be designed so that all organizational maintenance can be performed by no less than Air Force skill level 5 personnel or civilian equivalent.

3.12. Training Related Requirements.

All operations and maintenance personnel involved with the GIN shall be fully trained and qualified in accordance with (IAW) AFI 36-2101, Classifying Military Personnel (Officer and Enlisted).

Each operator and maintainer shall be trained in the theory associated with his/her assigned skill and in its direct application to the GIN system.

3.13. Logistics Related Requirements.

The GIN logistics support shall achieve and sustain the required degree of readiness and plan to minimize life cycle cost through monitoring and integrating the logistic support requirements into the system design and operational concepts. Logistic support areas include reliability and maintainability, maintenance planning, support equipment, supply support, packaging, handling, storage and transportation, technical data, facilities, manpower requirements, personnel training and training support, logistics support resource funding, logistics support management information, computer resources support, energy management, survivability, and logistics follow-on test and evaluation.

3.13.1. Maintenance.

3.13.1.1. The GIN maintenance documentation shall include Maintenance Data Collection (MDC) reporting through Core Automated Maintenance System (CAMS), Integrated Maintenance Data System-Central Data Base (IMDS-CDB), or any other Air Force approved system. The GIN, where practical, shall design new system hardware to interface with CAMS to enable automated maintenance diagnostics data collection and reporting.

24 25 January 2011 SS-GIN-660

3.13.1.2. The GIN on-equipment and off-equipment maintenance tasks shall include the following:

3.13.1.2.1. Preventive maintenance--the scheduled, periodic servicing required to maintain equipment in an operational condition--including lubrication, cleaning, adjustment, alignment, and calibration.

3.13.1.2.2. Corrective maintenance--unscheduled services required to restore malfunctioning or deteriorated equipment to an operational status.

3.13.2. Supply.

The GIN supply concept shall be in consonance with the overall GPS maintenance concept. The GIN shall use supply management policies and procedures commensurate with Life Cycle Cost (LCC), mission effectiveness, and provisioning and repair level analyses policies/procedures. The GPS shall use the Standard Base Supply System (SBSS) IAW AFI 63-101, Acquisition and Sustainment Life Cycle Management.

3.14. Other Requirements.

This section is not applicable to this specification.

4.0. QUALIFICATION PROVISIONS.

4.1. Test Program.

4.1.1. Verification Method.

The contractor's test program will qualify each requirement in Table 5 Requirements Verification Cross Reference Matrix, by the specified verification method.

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.

SS-GIN-660 25 January 2011 25

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.0. REQUIREMENTS VERIFICATION MATRIX.

This appendix contains the traceability of software tool requirements to the corresponding test verification method(s).

Table 5.1. Requirements Verification Cross Reference Matrix.

Requirement Number Description Demon strate Test Analysis Inspection

GIN 001

One state, the active state X

GIN 002 Conform to SSAA X

GIN 003

Real-time continuous interface with OCS X

GIN 004

Have an operational-primary mode x

GIN 005

Have operational-backup mode X

GIN 006

If primary fails, backup shall be primary X

GIN 007

Real-time continuous interface with intelligence agencies

X

GIN 008

Applications in operational-backup will perform operational primary, but operational backup applications will not distribute data to network

X

GIN 009

Initialize based on predefined parameters X

GIN 010

Applications report status to operators X

GIN 011

Display error if program initialization fails X

26 25 January 2011 SS-GIN-660

Requirement Number Description Demon strate Test Analysis Inspection

GIN 012

Interface spec to the

GIG X

GIN 013 Unclas GIG web site X

GIN 014

Directory structure to support Mission analysts

X

GIN 015

Directory structure for archived data X

GIN 016

Maintain operations in case of single HW or SW failure

X

GIN 017

Recover failed applications to previous known operational condition

X

GIN 018

Advanced recovered application to current system time

X

GIN 019 Secret GIG web site X

GIN 020

Directory structure to support Mission analysts

X

GIN 021

Directory structure for archived data X

GIN 022

Directory structure for near real time data X

GIN 023

Capability to port IS to a FTP directory on a SIPRNET server

X

GIN 024

Capability to dynamically generate directories

X

GIN 025

Capability to provide IDD records to a SIPRNET FTP server

X

GIN 026

No non-GIN mission applications failure shall cause failure of GIN components

X

GIN 027

Admin controls for managing applications X

GIN 028

Enable/disable incoming records X

SS-GIN-660 25 January 2011 27

Number Description Demon strate Test Analysis Inspection

GIN 029

Centralized AWE tracking and display X

GIN 030

Ensure alarms are easily identifiable X

GIN 031

Retain all raw data records X

GIN 032

Upon request GIN applications terminate X

GIN 033

Conduct automated checks X

GIN 034

Store parsed data in raw data tables X

GIN 035

Store edited data and analysis X

GIN 036

Automatically archive DB content to long term storage

X

GIN 037

Provide on-line storage for 180 days of data X

GIN 065

Capability to enter satellite status info X

GIN 067

Maintain DB of all NANUs X

GIN 068

Capability to check

NANU DB X

GIN 069

Automatically update internal satellite status on reception of nav messages

X

GIN 072

Compute elevation/azimuth angles

X

GIN 073

Compute PPS ERD values X

GIN 074

Compute instantaneous difference between ERD/OCS ORD pairs

X

GIN 075

Compute instantaneous difference between GIN ERD/ORD pairs

X

GIN 077

Conduct threshold checks on each ORD value

X

28 25 January 2011 SS-GIN-660

Number Description Demon strate Test Analysis Inspection

GIN 078

Conduct threshold checks on each ERD value

X

GIN 081

Distinguish between data transients X

GIN 082

If checks fail, generate an alarm X

GIN 083

Generate alarm in the event a satellite ORD is missing

X

GIN 087

Display running 24 hour plots of PPS global

RMS ERD

X

GIN 094

Compute/generate ZAOD nav message subframes 1-3

X

GIN 096

Computer/generate ZAOD nav message fit statistics

X

GIN 098

Run in real-time mode using real time data products and displaying

PPS

X

GIN 099

Run in real-time mode using real time data products and computing

SPS

X

GIN 100

Display real time PPS user error estimate values

X

GIN 101

Display real time SPS user error estimate values

X

GIN 102

Outputs for key parameters shall meet consistency standards

X

GIN 103

PNT error estimates shall meet consistency standards

X

GIN 104

Daily DOP, PNT, predictions shall meet consistency standards

X

GIN 105

Automatically insert correct health settings X

SS-GIN-660 25 January 2011 29 strate Test Analysis Inspection

GIN 106

Execute analyst specified time steps, 1 second – 15 minutes

X

GIN 107

Execute within 1 hour: 2 degree global grid, AIV position solution, etc.

X

GIN 108

Complete analysis cycle for 6 AOOs for best-4 satellite DOPs

X

GIN 109

Complete analysis cycle for 12 AOOs for set of 6 AIV and 6 best-4 satellite PPS

X

GIN 110

Generate reports including analyst controls for colors, legends, etc.

X

GIN 111

Generate graphical images of analyst specified parameters

X

GIN 112

Insert satellite maneuver into analyst scenario X

GIN 113

Offset satellite slot by analyst- specified GLAN value

X

GIN 114

Output raw data into ASCII format X

GIN 115

Retrieve and display archived scenario outputs

X

GIN 116

Automatically generate a series of outputs based on a scenario

X

GIN 117

Generate a summary report from variational analysis runs

X

GIN 119

Evaluate SIS URE and availability of signals X

GIN 120

Visualize satellite coverage, visibility of satellites to OCS

X

GIN 126

Capability to edit and add to intel data X

30 25 January 2011 SS-GIN-660

Number Description Demon strate Test Analysis Inspection

GIN 127

Maintain a library of known emitter characteristics

X

GIN 128

Support development and integration of emitter catalog

X

GIN 129

Capability to employ emitter catalog in theater analysis

X

GIN 131

Use DTED at any available level of fidelity X

GIN 133

Determine effect of ground wave propagation on satellite signals

GIN 135

Maintain catalog of functional and performance attributes

GIN 136

Capability to create new catalog objects X

GIN 137

Capability to modify existing catalog objects X

GIN 140

Capability to model a

CRPA X

GIN 141

Capability to model aided receivers X

GIN 142

Generate a mission route based on waypoints

X

GIN 143

Compute an estimate of instantaneous GPS performance

X

GIN 144

Compute a service availability metric X

GIN 145 Build a custom report X

GIN 146

Output data in ASCII format X

GIN 147

Save customized report templates for continued use

X

GIN 148

Generate and display visual depictions X

GIN 150

Generate contour plots for J/S and C/No info X

SS-GIN-660 25 January 2011 31 strate Test Analysis Inspection

GIN 151

Capability to save scenarios and edit in the future

X

GIN 152

Prove templates for post analysis evaluation X

GIN 156

Capability to automatically generate reports in the GIN IDD

X

GIN 158

Capability to exclude NMR data X

GIN 159

Capability to exclude PAF data when the SV is unhealthy

X

GIN 160

Capability to exclude PAF data when the SV fails an analyst specified test

X

GIN 161

Generate global RMS, ERD, PAC and clock statistics

X

GIN 162

Capability to reset satellite PSF data X

GIN 163

Build templates and generate custom reports X

GIN 164

Maintain DB of anomalies X

GIN 165

Capability to search anomaly DB X

GIN 166

Maintain a DB of user RFIs X

GIN 168

Incur no more than 30 minutes downtime X

GIN 171

Duplicate functionality at

AMCS X

GIN 172

Monitor interfaces to assess availability X

32 25 January 2011 SS-GIN-660

6. REQUIREMENTS TRACEABILITY.

Requirements traceability between the GPS System Specification (SS-GPS-300) and other specifications and GIN Software Requirements Specification (SS-GIN-660) is contained in Table 6.

Table 6.1. Requirements Traceability.

SS-GPS-300

Number/Para

Number

SS-GPS-300

Requirement Description

SS-GIN-660

Requirements

3.1.5.2.15 The CS shall interface with the User

Support Community to provide notification of GPS outages, SS almanac data, and related GPS status information.

All

SS-GIN-660 25 January 2011 33

7.0. NOTES

7.1. Abbreviations and Acronyms.

2 SOPS 2d Space Operations Squadron 14 AF 14th Air Force AFB Air Force Base AFI Air Force Instruction AIV All In View AMCS Alternate Master Control Station AOO Area of Operations ASCII American Standard Code for Information Interchange AWE Alarms, Warnings, and Events C/No Carrier to Noise ratio CAMS Core Automated Maintenance System CO Colorado COMSEC Communications Security COTS Commercial Off-the-Shelf CPCI Computer Program Configuration Item CRPA Controlled Reception Pattern Antenna CSCI Computer Software Configuration Item DBM Database Manager/Management DNS Domain Name Server DoD Department of Defense DOP Dilution of Precision DTED Digital Terrain Elevation Data ECI Earth Centered Inertial EGNOS European Geostationary Navigation Overlay Service ERD Estimated Range Deviation FOUO For Official Use Only FTP File Transfer Protocol GFE Government Furnished Equipment GFP Government Furnished Property GIG Global Information Grid GIN GPS Information Network GLAN Geographic Longitude of the Ascending Node GOTS Government Off-the-Shelf GPS Global Positioning System GPSOC GPS Operations Center GSC GPS Support Center IAW In Accordance With ICD Interface Control Drawing/Document IDD Interface Design Document IIR Block II Replenishment IMDS-CDB Integrated Maintenance Data System-Central Database IS Information System

34 25 January 2011 SS-GIN-660

JNWC Joint Navigation Warfare Center J/S Jammer to Signal ratio MCS Master Control Station MDC Maintenance Data Collection MS Monitor Station NANU Notice Advisory to NAVSTAR User NAVSTAR Name of GPS program, sometimes shown as Navstar NDI Non-Developmental Item NMR Navigation Message Replacement files NPAF Near-Real Time PAF NSOF Near-Real Time Satellite Outage Files OCS Operational Control System ORD Observed Range Deviation ORMS OPSCAP Reporting and Management System OS Operating System PAF Performance Assessment Files PNT Position, Navigation and Timing PIRN Proposed ICD Revision Notice PPS Precise Positioning Service PRED Predicted Ephemeris/State Vector Data Files PRR Pseudo-Range Residual PSF Prediction Support File RAC Radial-Alongtrack-Crosstrack (coordinate system) RF Radio Frequency RFI RF Interference RMS Root Mean Square SBSS Standard Base Supply System SecDef Secretary of Defense SEM System Effectiveness Model SIPRNET Secret Internet Protocol Router Network SIS Signal In Space SISP Single Integrated Space Picture SOF Satellite Outage Files SPG System Protection Guide SPS Standard Positioning Service SS Space Segment or System Specification SSAA System Security Authorization Agreement STD Standard SV Space Vehicle URA User Range Accuracy URE User Range Error US United States USSPACECOM US Space Command USSTRATCOM US Strategic Command WAAS Wide Area Augmentation System ZAOD Zero Age of Data

6. REQUIREMENTS TRACEABILITY.