Specification_for_MSFC-SLS_GPS_Simulator_Procurement_TFreestone_11Feb18.pdf

NASA Space Launch System MSFC Systems Integration Laboratory & Systems Integration Test Facility

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Revision: 4

Effective Date: 11 February 2018 Page 1 of 76

The image part with relationship ID rId8 was not found in the file.

SLS-MSFC-SIL-GPS-001

National Aeronautics and PRELIMINARY Space Administration EFFECTIVE DATE: 11 Feb 2018

George C. Marshall Space Flight Center Marshall Space Flight Center, Alabama 35812

Space Launch System System Integration Laboratory

Global Navigation Satellite System Radio Frequency Satellite Signal Simulator

(GNSS Simulator) Procurement Specification

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Revision: 4

Effective Date: 11 February 2018 Page 2 of 76

Document History Log

Status (Baseline/ Revision/ Canceled)

Document Revision

Effective Date

Description

Draft

07 Jun 2017

Initial Draft of Procurement Specification

Revision

01 Dec 2017

Revised Draft Procurement Specification

Baseline

2 21 Dec 2017 Baseline Procurement Specification

Release

3 08 Jan 2018 Released Procurement Specification. Clarified Options vs. Requirements.

Update 4 11 Feb 2018 Removed 53 instances of “etc.”

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 3 of 76

NASA / MSFC

SLS SIL

GNSS Radio Frequency Satellite Signal Simulator

Procurement Specification

Signature Page

SUBMITTED BY:

_______________________________________ __20 December 2017____ Todd Freestone Date GNSS Engineer, Radio Frequency Communications Team NASA / MSFC / ES45 Telemetry & Electromagnetic Effects Branch

CONCURRENCE BY:

_______________________________________ __20 December 2017____ Donna Hardage Date Chief, Telemetry & Electromagnetic Effects Branch NASA / MSFC / ES45 Telemetry & Electromagnetic Effects Branch

_______________________________________ __21 December 2017____ Darrell Bailey Date SLS Integrated Avionics Test Facilities Lead Engineer

NASA / MSFC / ES50

APPROVED BY:

_______________________________________ __21 December 2017____ Daniel Mitchell Date SLS Integrated Avionics and Software Discipline Lead Engineer

NASA / MSFC / ES01

<<minor editorial modifications made by Todd Freestone on 08-Jan-2018>>

<<Digitally Signed by Todd Freestone on 20-Dec-2017>>

<<Digitally Signed by Donna Hardage on 20-Dec-2017>>

<<Digitally Signed by Darrell Bailey on 21-Dec-2017>>

<<Digitally Signed by Daniel Mitchell on 21-Dec-2017>>

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 4 of 76

Table of Contents

1 Introduction

1.1 Purpose & SLS Program Overview

1.2 Scope & Simulator Application, and System Compatibility

1.3 Convention and Notation

2 Documents

2.1 Applicable Documents

2.1.1 United States Government Documents

2.1.2 Foreign Government Documents

2.1.3 Reference Documents

2.1.4 Order of Precedence

3 Requirements

3.1 GNSS Simulator System Design Requirements

3.1.1 Number of Radio Frequency Outputs

3.1.2 Simulation Scenario File(s)

3.1.3 Number of Modelled Vehicles per Scenario

3.1.4 Antenna-to-Vehicle Assignment Flexibility

3.1.5 Multiple Satellite Navigation Constellations

3.1.6 Graphical User Interface (GUI)

3.1.7 Future Upgradability

3.1.8 Almanac and Ephemeris Input Options

3.1.9 Satellite Orbital Parameter Propagation

3.1.10 Operational Modes & Capabilities

3.1.11 Bit-Level Satellite Signal Control

3.1.12 RF Interference Simulation Capability

3.1.13 Data Logging Capability

3.1.14 Data Streaming Capability

3.1.15 Data Display Capability

3.1.16 Data Plotting Capability

3.1.17 System Message/Error Logging Capability

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 5 of 76

3.1.18 Multipath Simulation Capability

3.1.19 Independent Satellite/Channel RF Signal Power Control

3.1.20 Signal Modulation and Code Control

3.1.21 User Motion Models

3.1.22 Antenna Locations, Orientations, Patterns & Lever-Arm Capabilities

3.1.23 Troposphere and Ionosphere effects & Ionospheric Scintillation

3.1.24 Differential GPS Corrections

3.1.25 Leap-second and week roll-over event testing

3.1.26 User-Actions File Recording & Playback (Repeatability)

3.1.27 Output/Post-Processing Capability

3.2 GNSS Simulator System Functional Requirements

3.2.1 GNSS Simulator System User Interface Requirements

3.3 GNSS Simulator System Interface Requirements

3.3.1 User-Interface GUI Display Monitor

3.3.2 User Interface Keyboard & Mouse

3.3.3 Simulator System Interconnection Cables & Terminations

3.3.4 Ethernet Interface

3.3.5 SCRAMNet Interface

3.3.6 InfiniBand Interface

3.3.7 RS-232 Serial Port Interface

3.3.8 USB Interfaces

3.3.9 GPIB/HPIB Interface for Jammer/Interference Generator

3.3.10 Reference Oscillator Input

3.3.11 Reference Oscillator Output

3.4 GNSS Simulator Performance Requirements

3.4.1 Simulator Hardware Update Rate

3.4.2 Simulator Hardware Latency

3.4.3 Pseudorange Velocity & Accuracy

3.4.4 Radio Frequency Performance Characteristics

3.4.5 Built-In Test Coverage

3.5 GNSS Simulator System Environmental Requirements

3.5.1 Equipment Operating Temperature / Environment:

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 6 of 76

3.5.2 Equipment Operating Humidity / Environment:

3.5.3 Electromagnetic Environmental Requirements

3.6 GNSS Simulator System Physical Requirements

3.6.1 Standard 19” Rack-Mountable Compatibility

3.6.2 Port & Connector Labels

3.6.3 Power Connectors and Cords

3.6.4 RF Connector Types

3.6.5 Front-Panel DC-Blocks

3.7 GNSS Simulator System Electrical Requirements

3.7.1 Power Supply

3.7.2 No Damage from Under-Voltage conditions

3.8 GNSS Simulator System Documentation Requirements

3.9 GNSS Simulator System Calibration, Maintenance, Support & Warranty Requirements

3.9.1 GNSS Simulator System Calibration

3.9.2 GNSS Simulator System Maintenance

3.9.3 GNSS Simulator System Support & Warranty

4 Schedule

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 7 of 76

Single-Page Procurement Summary

NASA’s SLS Program requires a GNSS Simulator with the following capability:

(1) Four (4) RF Outputs, minimum. Each RF Output must support at least the following frequencies and signals

a. 16 Channels of GPS L1 Frequency with GPS Codes (C/A, P(Y)-, M-, and

L1C Codes)

b. 16 Channels of GPS L2 Frequency with GPS Codes (P(Y) + L2C-, and M-

Codes)

c. 16 Channels of GPS L5 Frequency with GPS Codes & Signals (Sol Data &

Pilot)

d. 16 Channels of Galileo E1 Frequency with Galileo Codes & Signals (Open

Service Data & Pilot, and PRS)

e. 16 Channels of Galileo E5 Frequency with Galileo Codes & Signals (I & Q)

(2) Functionality to properly simulate Terrestrial, Spacecraft, and Launch Vehicle (i.e., smooth transition from Terrestrial to Spacecraft modes) Simulations.

(3) [ScramNet GT200 or InfiniBand 10Gbps+], and Ethernet Interfaces to integrate the GNSS Simulator into a Real-Time, Closed-Loop, Hardware-in-the-Loop simulation, where NASA’s simulation control computer sends 1000 Hz State ‘Truth’ Data to the GNSS Simulator, for any combination of 4 vehicles / 4 antennas.

(4) Unclassified System, with the capability of being upgraded later to transmit the full, classified GPS Y-Code and/or GPS M-Code, without need to send the hardware back to manufacturer for modification.

(5) Assuming there is more than one hardware chassis required to provide the above functionality, the ability to split the various simulator chassis into separate, standalone units for operation in different physical locations. This means the system will need to be delivered with multiple control computers and complete cable interconnection sets to properly separate the multiple chassis units into independent, standalone systems when required.

The following are OPTIONS, not included in this procurement:

(6) Ability to add new GNSS Satellite Constellations (GLONASS, BeiDou, QZSS, and IRNSS) later, as an upgrade, without need for sending hardware back to the manufacturer for modification.

(7) Ability to integrate a Radio Frequency Interference generator, comprised of at least

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 8 of 76

Continuous Wave, Pulsed, and Broadband noise generation capability, and must be capable of dynamically-modeling and manipulating the interfering signal strength according to simulated jammer position and antenna characteristics.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 9 of 76

1 INTRODUCTION

The National Aeronautics and Space Administration (NASA), George C. Marshall Space Flight Center (MSFC) is seeking to procure a Global Navigation Satellite System (GNSS) Radio Frequency (RF) Satellite Signal Simulator System (SSSS) to enable functional testing of various GNSS Receivers for suitability onboard NASA’s Space Launch System (SLS) launch vehicle.

This Procurement Specification establishes the procurement requirements for the subject GNSS SSSS, which will reside at NASA’s George C. Marshall Space Flight Center (Huntsville, Alabama) in the SLS Systems Interface Laboratory.

The requirements herein represent the decomposition and allocation of requirements for the GNSS SSSS component to perform its defined functions and test capabilities in support of the SLS Launch Vehicle Design Reference Missions (DRMs). The subject SSSS will be used to test GNSS Receivers on multiple different functional elements of the SLS Launch Vehicle, including Core Stage, Booster Stages, Exploration Upper Stage, Interim Propulsion Stages, Orion Multipurpose Crew Vehicle, Launch Abort System, and various Spacecraft Payloads, and thus this document represents functional and test requirements taken from a multitude of elements across the SLS Program.

While certain Elements of SLS (i.e., Core Stage, Boosters, Upper-Stage, Multi-Purpose Crew Vehicle (Orion)) may use single-service Global Positioning System (GPS) Receivers, others may use multi-service Global Satellite Navigation Systems (GNSS), such as GPS, Galileo, GLONASS, Beidou, QZSS, IRNSS, and other regional systems, and various combinations thereof. Thus, the requested GNSS SSSS must support modeling and generation of satellite signals from multiple satellite-based navigation systems, either at initial purchase, or through subsequent system upgrades.

SLS flights are in support of NASA’s overall Exploration Program, and various elements of the SLS are required to navigate throughout multiple different types of mission phases, including Ground Alignment, Ascent, Earth Orbit, Cis-Lunar Transit, Lunar Orbit, and Entry, Descent, and Landing (EDL). As such, the required GNSS Simulator System must allow simulation of a wide variety of different static and dynamic conditions.

GNSS Receiver functionality onboard these various SLS vehicle stages and elements will be used in support of Range Safety Metric Tracking, Ascent Navigation, Orbital Navigation, Spacecraft Timing, Staging and Recovery Systems functions, EDL functions, and Crew and Payload Safety, among other duties and purposes. Because many of these functions are safety-critical and/or mission-critical, it is imperative that the candidate GNSS receivers be tested in realistic but simulated conditions before actual flight, to accurately characterize and understand their behavior.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 10 of 76

1.1 Purpose & SLS Program Overview

NASA’s Space Launch System, or SLS, is an advanced launch vehicle for a new era of exploration beyond Earth’s orbit. SLS will launch astronauts in the agency’s Orion spacecraft on missions to an asteroid and eventually to Mars, while opening new possibilities for other payloads including robotic scientific missions to places like Mars, Saturn, and Jupiter. Offering an unprecedented amount of payload mass and volume capability and energy to speed missions through space, SLS is designed to be flexible and evolvable, to meet a variety of crew and cargo mission needs.

The primary purpose for the GNSS Receivers aboard the various SLS Elements is to receive, track, and process satellite-based navigation signals (such as the NAVSTAR GPS, Galileo, GLONASS, BeiDou, QZSS, and IRNSS) and provide resulting estimates of position, velocity, GNSS line-of-sight measurements, and time data to support vehicle state-vector determination within the various elements of the Space Launch System architecture. As mentioned above, the GNSS Receiver data is a primary source of vehicle tracking, timing, and navigation data across multiple SLS elements, and is used in support of Range Safety Metric Tracking, Ascent Navigation, Orbital Navigation, Spacecraft Timing, Staging and Recovery Systems functions, Entry/Descent/Landing (EDL) functions, parachute deployment, descent management, stage disposal operations, and Crew and Payload Safety.

The purpose of the GNSS RF Satellite Signal Simulator System is to allow NASA personnel to functionally- and performance-test the various GNSS Receivers by generating realistic simulated radio frequency satellite signals, which will cause the GNSS Receivers being tested to think they are flying their intended missions and behave as they would during the flight mission. As such, the simulator system must be able to reproduce a wide variety of satellite signals, frequencies, navigation codes, and navigation messages, across all of the various mission segments, including Ground Alignment, Ascent, Earth Orbit, Cis-Lunar Transit, Lunar Orbit, and Entry, Descent, and Landing (EDL) scenarios.

1.2 Scope & Simulator Application, and System Compatibility

The requirements defined in this specification apply to the GNSS Radio Frequency Satellite Signal Simulator System that NASA/MSFC is seeking to procure. This specification defines the characteristics and requirements of functional, physical and operational capabilities for the GNSS Simulator.

Although this GNSS Simulator System will reside inside NASA/MSFC’s System Integration Laboratory (SIL), the SIL and associated SLS hardware components with which this GNSS Simulator System will be integrated, is not within the scope of this

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 11 of 76 specification. The SIL is a NASA-furnished design with Government-furnished hardware and software which is planned for use in various stages and types of vehicle simulations but is not specified within this document. Government-supplied SIL Simulation Control Computers will routinely feed real-time trajectory information into the GNSS Simulator to ensure time-synchronous simulation with other SIL Simulation Systems. Requirements from the external SIL Test System have been flowed down to the GNSS Simulator System to ensure functional, mechanical, and electrical compatibility between the GNSS Simulator and the external SIL Test System.

1.3 Convention and Notation

The conventions used in this document which indicate requirements, statements of facts, and goals is as follows:

“Shall” – Used to indicate a requirement which must be implemented, and its implementation will be verified.

“Will” – Used to indicate a statement of fact and is not verified.

“Should” – A “Capability” requirement and Design Goal which, if not met, will not prevent a GNSS Simulator system from being formally accepted, but that will enhance the technical value, expansion features, performance margins, and/or future mission utility.

(i.e., these are “nice-to-have’s”, and not a formal requirement.)

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 12 of 76

2 DOCUMENTS

2.1 Applicable Documents

2.1.1 United States Government Documents

The following Table 1 lists the applicable Government documents of the issue shown (or latest version, as applicable) that form a part of this specification to the extent specified herein. In case of conflict between this document and the document cited, this document has precedence.

Table 1: Applicable United States Government Documents

Document # Document Title Version Date IS-GPS-200H Navstar GPS Space Segment/Navigation User Interfaces H 28 Jul 2016 IS-GPS-705D Navstar GPS Space Segment/User Segment L5 Interface D 24 Sep 2013 IS-GPS-800D Navstar GPS Space Segment/User Segment L1C Interface D 24 Sep 2013 GPS-SPS-PS GPS Standard Positioning Service Performance Standard 4 01 Sep 2008 GPS-PPS-PS GPS Precise Positioning Service Performance Standard 1 23 Feb 2007 GPS-WAAS-PS GPS Wide Area Augmentation System Performance Standard 1 31 Oct 2008 SS-GPS-001 GPS Selective Availability, Anti-Spoofing Module Specification A 27 Sep1999 CZE-93-295 GPS Precise Positioning Service Simulator Security

Requirements 1 28 Jul 1997

ICD-GPS-226 (S) GPS Precise Positioning Service Simulator Design Requirements (S)

A 10-Dec-1995

MIL-STD-461G Requirements for Control of EMI of Subsystems and Equipment G 11-Dec-2015

2.1.2 Foreign Government Documents

The following Table 2 lists the applicable Non-Government documents of the issue shown (or latest version, as applicable) that form a part of this specification to the extent specified herein. In case of conflict between this document and the document cited, this document has precedence.

Table 2: Applicable Foreign Government Documents

Document # Document Title Version Date Galileo-OS-ICD European Union Galileo Open-Service Signal-in-Space ICD I1R3 01Dec 2016 GLONASS-ICD Russian GLONASS Interface Control Document for L1, L2 5.1 2008

IS-QZSS-ONT-

Japanese Quazi-Zenith Satellite System Interface Specifications 1.7 28 Mar 2017

IRNSS-ICD India IRNSS SPS Signal-in-Space ICD 1.1 18-Aug-2017 BeiDou-SIS-ICD Chinese BeiDou Satellite System Open Service Signal-In-Space

ICD

2.0 Dec 2013

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 13 of 76

2.1.3 Reference Documents

<none>

2.1.4 Order of Precedence

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 14 of 76

3 REQUIREMENTS

NASA, George C. Marshall Space Flight Center is seeking to procure a Global Navigation Satellite Signal (GNSS) Radio Frequency (RF) Simulator System, that will allow the testing of various GNSS Receivers in simulated mission-like scenarios, as part of a navigation receiver test & evaluation program for NASA’s Space Launch System (SLS).

This procurement specification document establishes the Design, Functional, Interface, Environmental, Physical, Electrical, Documentation, and Maintenance, Support & Warranty requirements of the required GNSS RF Satellite Signal Simulator System.

3.1 GNSS Simulator System Design Requirements

When this procurement specification was initially being drafted, it started out as a specification for a ‘GPS Simulator System’. However, as SLS Navigation Receiver needs have evolved and matured, and as the sensors under consideration are using more than just GPS signals for their operation, it became apparent that a multi-constellation (not just GPS) simulator system was needed to fully-test the candidate satellite navigation receivers that SLS may use. Thus, the Specification changed from a ‘GPS Simulator’ specification to a ‘GNSS Simulator’ specification.

As such, the requested GNSS RF Simulator System must provide for the configuration and generation of both USA’s GPS Constellation and Europe’s Galileo Constellation.

Additionally, the requested GNSS RF Simulator System must be upgradeable to include the configuration and generation of additional constellations of Navigation satellites including Russia’s GLONASS, China’s BeiDou, and India’s QZSS constellation systems1, among others. It must allow the Simulator user to specify a user-receiver trajectory and satellite signal parameters to ‘fool’ the receiver under test into thinking that it is flying the intended trajectory/scenario. It must allow the user to specify host-vehicle and antenna characteristics salient to the simulation scenario. It must allow the user sufficient flexibility in configuring the many operational parameters such that both nominal and off-nominal conditions may be simulated, under varying static and dynamic conditions, while testing various Satellite Navigation Receiver candidates. And it must allow the user to send real-time, closed-loop, hardware-in-the-loop motion messages as part of a larger vehicle simulation system. The specific GNSS Simulator System requirements follow.

3.1.1 Number of Radio Frequency Outputs

The GNSS Simulator shall provide at least four (4) independent Radio Frequency Antenna Signal outputs, each with DC-Blocked coaxial type “N” female connectors. The DC Blocking characteristic is required so that the simulator will be compatible with GNSS

1 This specific procurement requires GPS and Galileo signal generation, but System should be upgradeable to GLONASS, BeiDou, QZSS, and other GNSS systems, at a later time.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 15 of 76

Receivers that provide DC power to their antennas via their coaxial cable connector. The DC Block will serve both to protect the GPS Simulator, as well as the receiver under test.

3.1.2 Simulation Scenario File(s)

The GNSS Simulator shall offer the user the ability to save all of the specific scenario configuration details, options and parameters to a non-volatile storage media (i.e., hard disk), with a user-specified file name(s). Multiple configuration files may be used, but ultimately, the user must be able to recall the entire scenario via specification of one master scenario configuration filename (like a hierarchical file tree, for example).

3.1.3 Number of Modelled Vehicles per Scenario

The GNSS Simulator shall offer the user the ability to simulate a number of independent Vehicles equal to the number of Radio Frequency Outputs. In this specific procurement case, since four (4) independent RF outputs are required, then the GNSS Simulator must allow the user the ability to specify up to four (4) different user host vehicles, each with their own set of independent motion/trajectories, parameters and settings.

3.1.4 Antenna-to-Vehicle Assignment Flexibility

The GNSS Simulator shall offer the flexibility to specify the number of assigned antennas (RF Outputs) per vehicle, up to the maximum number of RF outputs that the GNSS Simulator Supports. For example, for a four-RF-output GNSS Simulator, if the user specifies a two-vehicle scenario, the GNSS Simulator must allow the user to specify the following possible configurations:

(a) Vehicle 1 with 1 Antenna, & vehicle 2 with 1 Antenna (2 RF outputs not used)

(b) Vehicle 1 with 2 Antennas, & Vehicle 2 with 1 Antenna (1 RF output not used)

(c) Vehicle 1 with 1 Antenna, & Vehicle 2 with 2 Antennas (1 RF output not used)

(d) Vehicle 1 with 2 Antennas, & Vehicle 2 with 2 Antennas (all 4 RF outputs used)

(e) Vehicle 1 with 3 Antennas, & Vehicle 2 with 1 Antenna (all 4 RF outputs used)

(f) Vehicle 1 with 1 Antenna, & Vehicle 2 with 3 Antennas (all 4 RF outputs used)

3.1.5 Multiple Satellite Navigation Constellations

At time of delivery, the GNSS Simulator shall offer the user the flexibility to specify (per individual RF output) American GPS (L1, L2 and/or L5) signals and/or European Galileo Satellite Signals (E1 and/or E5), for each user-defined scenario.

For GPS L1, the GNSS Simulator shall support generation of the C/A Code, L1C Data, L1C Pilot, P-Code, Quasi-M, and Quasi-Y, where Quasi-M is a spectrally-representative M-Code signal from each satellite and Quasi-Y is generated through unclassified encryption of P-Code to support “L1 Squaring” (or Z-Tracking).

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 16 of 76

For GPS L2, the GNSS Simulator shall support generation of the L2C Code, P-Code, Quasi-M and Quasi-Y.

For GPS L5, the GNSS Simulator shall support generation of both the I-Channel and the Q-Channel data streams.

For Galileo E1, the GNSS Simulator shall support generation of the OS Data and OS Pilot signals, and PRS Noise.

For Galileo E5, the GNSS Simulator shall support generation of the Pilot, and 8PSK Data (E5a-I, E5a-Q, E5b-I, and E5b-Q.)

3.1.6 Graphical User Interface (GUI)

The GNSS Simulator System shall include a GUI to allow the user to set/configure the necessary simulation parameters and options, as well as to monitor the real-time status and progress of the simulation and manipulate parameters in real-time. Additional specific requirements are as follows:

3.1.6.1 GUI Time/Duration Display

The GNSS Simulator System’s GUI shall include a window (or portion of a window) that display’s the current simulated date/time, scenario duration (days, hh:mm:ss), simulation elapsed time, GPS Week#, and GPS Rollover Number.

3.1.6.2 GUI Ground Track & Position Map

The GNSS Simulator System’s GUI shall include the ability to display real-time (and past/future) user ground track map (world map), indicating current user position and all GNSS satellites in their proper georeferenced position relative to the map and user position. Visible GNSS satellites shall be colored green (or similar color highlight) and non-visible satellites shall be colored red (or some contrasting-color highlight).

3.1.6.3 GUI Satellite Sky-View Plot

The GNSS Simulator System’s GUI shall include a window showing all of the visible GNSS satellites (relative to one of the user vehicle’s position), where the GNSS positions represent relative azimuth and elevation angles. (Sky View Plot).

3.1.6.4 GUI Overall Status / Info Display

The GNSS Simulator System’s GUI shall include an overall status bar or window(s) indicating simulated date/time, hardware status, simulation status, data logging status, Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 17 of 76 channel status, system configuration, classification status, and any other relevant system-level status information that the user/operator would need to know to help characterize, diagnose, and troubleshoot a system problem or malfunction.

3.1.6.5 GUI System & Error Messages Display

The GNSS Simulator System’s GUI shall include a status window that shows real-time system and error messages on hardware and software status with time-of-event, for troubleshooting & debugging purposes.

3.1.6.6 GUI User Motion Display Window

The GNSS Simulator System’s GUI shall include a status window that shows user position(s) in LLA (in decimal degrees or DMS) and ECEF XYZ (in meters), user speed (meters/sec or MPH), user velocity in XYZ-dot (in meters/sec), user attitude (Heading Elevation Bank, in degrees), ideal GDOP, PDOP, HDOP, VDOP, TDOP, and Figure of Merit.

3.1.6.7 GUI Hardware Channel Status & Control Window

The GNSS Simulator System’s GUI shall include a Real-Time Power-Adjustment window that shows hardware channel, assigned SVID, and dB power level out, and which lets the user adjust the output power, for each individual signal/channel, from at least -20 to + 20 dB, absolute or relative, including the ability to turn individual signals/channels ON or

OFF.

3.1.6.8 GUI Signals Received Display

The GNSS Simulator System’s GUI shall include a Signals-Received window showing Hardware Channel #, Signal Type (GPS L1, L2, L5, Galileo E1, E5, and any others the simulator is capable of generating), SVID#, Azimuth angle, Elevation angle, Tropospheric Delay, Ionospheric Delay, Pseudorange, PR Rate, and RF Power Level at Simulator Output.

3.1.6.9 GUI Vehicle Dynamics & Status Display

The GNSS Simulator System’s GUI shall include a vehicle dynamics window(s), showing speedometer, artificial horizon, vehicle attitude (Heading, Elevation, and Bank), compass heading, numeric tabular altitude, speed, in both graphical and tabular formats, for situational awareness of simulated user-vehicle(s) status.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 18 of 76

3.1.7 Future Upgradability

3.1.7.1 Upgrade to Other Satellite Constellations

The GNSS Simulator shall have the option of being upgraded after initial delivery, as SLS needs mature and grow, to include other Satellite-Based Navigation System Signals, including, but not limited to, GLONASS and BeiDou, as well as augmentation systems, such as SBAS, IRNSS, and QZSS, as listed below, without need for being returned to the manufacturer.

(A) GPS L1 – Already included/requested/required in this procurement

(B) GPS L2 – Already included/requested/required in this procurement

(C) GPS L5 – Already included/requested/required in this procurement

(D) Galileo E1 – Already included/requested/required in this procurement

(E) Galileo E5 – Already included/requested/required in this procurement

(F) Galileo E6 (CS Pilot, CS Data, and Quasi-PRS [a noise-like representation])

(G) SBAS [WAAS, EGNOS, MSAS, GAGAN] L1 (C/A Code)

(H) SBAS [WAAS, EGNOS, MSAS, GAGAN] L5 (I-Channel)

(I) GLONASS L1 (C/A Code and P-Code for Channel Numbers -7 to +6)

(J) GLONASS L2 (C/S Code and P-Code for Channel Numbers -7 to +6)

(K) QZSS L1 (SAIF, C/A Code, and L1C Code)

(L) QZSS L2 (L2C Code) (M)QZSS L5 (both I and Q Channels)

(N) BeiDou-2 B1 (B1I Code)

(O) BeiDou-2 B2 (As B1I Code)

3.1.7.2 Upgrade to Classified/Encrypted Constellation Signals

The GNSS Simulator shall have the option of being upgraded, after delivery, as SLS needs mature and grow, to include simulation and generation of classified (or encrypted) satellite signals and codes, such as GPS SA/AS Y-Code, GPS M-Code, Galileo Safety of Life Service and Commercial Service, Galileo Public Regulated Service, Galileo Search & Rescue Service, GLONASS P-Code, and BeiDou/Compass Encrypted Signals, without need for being returned to the manufacturer.

3.1.8 Almanac and Ephemeris Input Options

The GNSS Simulator System shall accept manual (keyboard) input of Almanac and Ephemeris parameters, as well as accept input of complete SEM- and YUMA-format almanacs and ephemerides files from Internet sources.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 19 of 76

3.1.9 Satellite Orbital Parameter Propagation

The GNSS Simulator System shall use its constellation Almanac Data and Ephemeris Data to dynamically generate precise satellite orbital data, including fully-automatic satellite position/velocity/attitude propagation versus time. This shall apply to both GNSS Satellite Vehicles as well as to User Spacecraft.

3.1.10 Operational Modes & Capabilities

The GNSS Simulator shall be capable of both standalone operation, as well as operation as part of a larger overall vehicle-level system simulation, as specified in the following paragraphs.

3.1.10.1 Standalone Operational Capability

The GNSS Simulator shall be able to operate as a standalone entity, without need for additional simulation computers, trajectory servers, accessories, or other systems. It should be shipped as a complete standalone system, with all the computers, hardware and software needed to run standalone GNSS simulations and tests. Users should have the capability to input all necessary operating parameters and configurations into a local console and start/stop/configure the simulation locally, as a standalone system, when desired.

3.1.10.2 Real-Time Closed-Loop Hardware-In-The-Loop Capability

The GNSS Simulator shall be able to operate as part of a larger vehicle-level simulation system (which is not part of this procurement), such that it accepts, in real-time, 6-Degree-of-Freedom vehicle state/motion and simulation control messages, at not less than 1000 Hz, from an external computer system, via Ethernet and/or SCRAMNet and/or InfiniBand interfaces (delivered system must have all three real-time interfaces.)

The real-time 6 Degree-of-Freedom (6DOF) data shall consist of time, vehicle position, velocity, acceleration, attitude, and attitude rates, in all three axes, for each simulated vehicle. For cases where this 6DOF data is supplied at update rates less than 1000 Hz, the GNSS Simulator shall interpolate data points using not less than a second-degree polynomial spline. Using this continuously-input 6DOF data, the GNSS Simulator System modifies its four RF output signals in real-time2, accordingly, so that the simulation is synchronized among multiple avionics components as part of an integrated test suite.

2 For Real-Time Latency requirements, please see Paragraph 3.4.2, Simulator Hardware Latency Requirements.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 20 of 76

3.1.10.3 Remote-Control Mode Capability

The GNSS Simulator System shall accept remote operating commands, either from a local data file, and/or from a customer-supplied external computer via RS-232 serial, USB, SCRAMNet, InfiniBand, and/or Gigabit Ethernet interface, to configure simulation parameters and to remotely start/stop various simulations.

3.1.10.4 No-Hardware Simulation Mode Capability

The GNSS Simulator System shall allow the user to initiate one or a series of GNSS simulations which do not require simulator signal-generation hardware to be present and/or connected. This mode is very useful for Monte-Carlo type statistical simulations, or for troubleshooting. In this mode, the GNSS Simulator shall allow for either real-time, or faster-than-real-time simulations, at the user’s discretion.

3.1.10.5 Unattended/Remote Simulation Mode Capability

The GNSS Simulation System shall have the ability to operate while unattended and running from a pre-built simulation script, or via remote simulation commands. This mode of operation shall include a method by which to disable pop-up message windows which require user-intervention, so that it can operate/simulate autonomously while unattended (so a user does not need to be present to dismiss a message pop-up or dialog box, for example).

3.1.10.6 Single-Channel Mode

The GNSS Simulator System shall allow for a Single-Channel mode of operation in which the user has complete user-control over signal characteristics and properties, such as pseudorange, velocity, RF output on each frequency, Doppler, Codes on/off for each frequency, Data on/off for each frequency, carriers on/off, signal strength, and signal strength modeling with separation distance.

3.1.10.7 Split-Apart Capability

If the GPS Simulator System is delivered in a multiple-chassis configuration, it shall have the capability to be ‘broken down’ into multiple smaller standalone units for independent operation. For example, if two dual-RF-output chassis are delivered to fulfill the four-output requirement, then additional control computers shall be provided as well, to enable the end-users to break down the system into two separate & independent dual-output chassis configurations, for periods where 4-output simulation capability is not required.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 21 of 76

3.1.11 Bit-Level Satellite Signal Control

The GNSS Simulator System shall allow for bit-level control of all broadcast data, such that the user can force a One, a Zero, a bit-flip, or a ‘don’t care’ condition on one or any number of bits, for any constellation type, any specific (or set of) satellite(s), any specific (or set of) frequency(s), and any navigation data stream.

3.1.12 RF Interference Simulation Capability

3.1.12.1 RF Interference Source Integration

The GNSS Simulator System shall be capable of being integrated with an external RF Signal generator which acts as an RF Interference or Jamming source. To effect this, it shall incorporate the following two interfaces:

1. An Auxiliary RF Input (N-Female Coaxial connector) with an internally-fitted RF broadband Combiner, to mix externally-supplied interference signals with internally-generated GNSS signals, and route that combination to the front-panel main RF output connector, for Jamming / Interference testing, and

2. A GPIB/HPIB (or USB) control buss, for communication with and control of the external signal generator.

3.1.12.2 RF Interference Source Functionality

The GNSS Simulator System shall be able to effectively place the interference/jamming source at a fixed geographical location, and dynamically adjust the RF Interference source power such that received signal levels are correctly modeled for distance and antenna reception pattern attitudes.

Additionally, the simulator shall provide for user-selection of various broadcast interference signal types, including (but not necessarily limited to) Continuous Wave, Pulsed, and Broadband noise.

3.1.13 Data Logging Capability

The GNSS Simulator System shall be capable of logging a wide variety of simulated and truth-data parameters to non-volatile (disk-based) storage, including parameters such as (but not necessarily limited to) signal characteristics (ranges and range-rates), time, signal levels, vehicle and trajectory data, including the parameters below:

1. The GNSS Simulator System shall allow the user to choose the type(s) of information to be recorded to disk, with not less than the following choices:

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 22 of 76

a. Satellite Constellation Parameters (SV Locations vs. time), Visible Sats, Az/El to each satellite, signal strength, including a graphical map indicating SV positions [azumith & elevation angles] relative to the user vehicle’s simulated position.

b. User Vehicle Motion parameters (Position, Velocity, Attitude, Attitude Rates, Speed, and Height, )

c. User Vehicle Antenna Motion parameters (Position, Velocity, Attitude, Attitude Rates, and Position offset from C.G.)

d. Satellite Pseudoranges/Rates

e. Satellite RF Signal Levels

f. Simulated Ionospheric & Tropospheric Delays for each satellite

2. The GNSS Simulator System shall allow the user to choose the Rate at which the above information is saved to disk, with rates covering at least from once every 1 mSec to once every 60 seconds.

3. The GNSS Simulator System shall allow the user to specify the times that the specified information shall be recorded to disk, as follows:

a. Continuous Recording, from Start of Simulation through End.

b. Custom Recording times, where the user specifies a Start-Recording Time and an Stop-Recording time, in simulation elapsed time.

c. In cases where the user choses to specify custom recording times, the

GNSS Simulator System shall allow the user to specify no less than 10 different sets of Start/Stop recording time pairs.

4. The GNSS Simulator System shall allow the user to specify the type of time-tag that should be appended onto recorded data, with not less than the following choices:

a. Simulator Elapsed Time, in mSec

b. Simulation Time, in mSec

c. Real Wall-Clock Time, as read from the Simulation Host Computer’s Clock

5. The GNSS Simulator System shall allow the user to choose the Format in which the above information is recorded: ASCII Text, CSV Text, or Binary (to minimize file size). For Binary format, there shall be a user guide to allow proper decoding of the saved binary data.

Once the Data Logging Parameters have been properly configured, the GNSS Simulator System shall allow the user to save a configuration file containing the Data Logging Parameter Setup/Configuration Information, for loading in future simulations.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 23 of 76

3.1.14 Data Streaming Capability

The GNSS Simulator System shall be capable of streaming a wide variety of real-time, simulated and truth-data parameters over Ethernet, Serial, USB, SCRAMNet, and/or InfiniBand interfaces, including parameters such as (but not limited to) signal characteristics (ranges and range-rates), time, signal levels, vehicle and trajectory data, satellite position and signal characteristics data, and Ionospheric and Tropospheric Delays.

1. The GNSS Simulator System shall allow the user to choose and configure the type(s) of electronic interface over which the selected data will be streamed.

Choices shall include, but not be limited to, the following:

a. RS-232 Serial. User shall be able to specify

i. COM Port Number

ii. Baud Rate (9600, 115,200, etc)

iii. Parity bit (Yes / No)

iv. Number of Data bits (7, 8, 9)

v. Number of Stop bits (0,1,2)

vi. Flow Control Method (None, Software XON/XOFF, and Hardware

RTS/CTS)

b. Ethernet (TCP or UDP)

i. Network Adapter to use (when more than one is installed in GNSS Simulator control computer)

ii. Protocol: UDP or TCP

iii. Broadcast address

iv. IP Socket to connect to on remote PC

v. Port Number for awaiting connection from external computer

vi. Data Rate

vii. Message Formatting Options (Header Size, Frame Format and

Frame Size)

c. USB

i. USB Port to use

ii. Data Rate

iii. Message Formatting Options (Sync Field, Packet ID, Address Field, Endpoint Field, CRC, and End of Packet)

d. SCRAMNet GT200 or faster

e. InfiniBand, at not slower than a 1X Link at 10 Gbit/second or faster

2. The GNSS Simulator System shall allow the user to choose the type(s) of information to be Streamed, with not less than the following choices:

a. Satellite Constellation Parameters, includingSV Locations vs. time, Visible

Sats, Az/El to each satellite, PDOP, GDOP, HDOP, VDOP, TDOP, FOM, Signal Strengths, Almanac Parameters and Ephemeris Parameters.

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 24 of 76

b. User Vehicle Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, Speed, Heading, Antenna Lever Arm(s), and Antenna Orientation vector(s))

c. User Vehicle Antenna Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, and Pattern Number(s))

d. Satellite Pseudoranges/rates

3. The GNSS Simulator System shall allow the user to choose the Rate at which the above information is Streamed, with rates covering at least from once every 1 mSec to once every 60 seconds.

4. The GNSS Simulator System shall allow the user to specify the type of time-tag that should be appended onto Streamed data, with not less than the following choices:

a. Simulator Elapsed Time, in mSec

b. Simulation Time, in mSec

c. Real Wall-Clock Time, as read from the Simulation Host Computer’s Clock

5. The GNSS Simulator System shall allow the user to choose the Format in which the above information is Streamed: ASCII Text, CSV Text, or Binary (to minimize file size). For Binary, there shall be a user guide to allow proper decoding of the saved binary data.

Once the Data Streaming Parameters have been properly configured, the GNSS Simulator System shall allow the user to save a configuration file containing the Data Streaming Parameter Setup/Configuration Information, for loading in future simulations.

3.1.15 Data Display Capability

The GNSS Simulator System shall be capable of displaying, on the user-interface screen, a wide variety of simulated and truth-data parameters, including parameters such as (but not limited to) signal characteristics (ranges and range-rates), time, signal levels, vehicle and trajectory data, simulator status and readiness, error and diagnostic information, configuration details, calibration ststus and other system information necessary for simulator operations. The system shall be capable of displaying multiple parameters simultaneously in tabular/list format.

information to be displayed on screen, with not less than the following choices:

a. Satellite Constellation Parameters, including SV Locations vs time, Visible Sats, Az/El to each satellite, PDOP, GDOP, HDOP, VDOP, TDOP, FOM, Signal Strengths, Constellation Selection (GPS, Galileo, GLONASS, Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 25 of 76

BeiDou, QZSS, IRNSS, or any combination, including ALL)

b. User Vehicle Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, Speed, Heading, Antenna Lever Arm(s), and Antenna Orientation vector(s))

c. User Vehicle Antenna Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, and Pattern Number(s))

d. Satellite Pseudoranges/rates above information is updated on screen, with rates covering at least from once every 100 mSec to once every second.

Once the Data Display Parameters have been properly configured, the GNSS Simulator System shall allow the user to save a configuration file containing the Data Display Parameter Setup/Configuration Information, for loading in future simulations.

3.1.16 Data Plotting Capability

The GNSS Simulator System shall be capable of plotting, on the user-interface screen, graphical representations of a wide variety of simulated and truth-data parameters, including parameters such as (but not limited to) signal characteristics (ranges and range-rates), time, signal levels, vehicle and trajectory data, simulator status and readiness, error and diagnostic information, configuration details, calibration ststus and other system information necessary for simulator operations. The system shall be capable of displaying multiple parameters simultaneously, while dynamically auto-scaling them to properly fit on their respective graph plots.

information to be plotted/graphed on screen, with not less than the following choices:

a. Satellite Constellation Parameters, includingSV Locations vs time, Visible Sats, Az/El to each satellite, PDOP, GDOP, HDOP, VDOP, TDOP, FOM, Signal Strengths, Almanac Parameters and Ephemeris Parameters.

b. User Vehicle Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, Speed, Heading, Antenna Lever Arm(s), and Antenna Orientation vector(s))

c. User Vehicle Antenna Motion parameters (Such as Position, Velocity, Attitude, Attitude Rates, and Pattern Number(s))

d. Satellite Pseudoranges/rates

Title: NASA SLS, MSFC SIL/SITF GNSS Radio Frequency Satellite Signal Simulator Procurement Specification

Document #: SLS-MSFC-SIL-GNSS-001 Author: NASA / MSFC / ES45 / T. Freestone

Effective Date: 11 February 2018 Page 26 of 76 above information is updated on screen, with rates covering at least from once every 100 mSec to once every minute.

Once the Data Plotting Parameters have been properly configured, the GNSS Simulator System shall allow the user to save a configuration file containing the Data Plotting Parameter Setup/Configuration Information, for loading in future simulations.

3.1.17 System Message/Error Logging Capability

The GNSS Simulator System shall be capable of logging System Messages and Errors to disk, for later diagnosis. The user shall have the ability to enable or disable the various types of messages which are logged to disk, such as Info Only, Warning Message, Error Message, Fatal Error Message, and System Messages.

Once the System Message/Error Logging Parameters have been properly configured, the GNSS Simulator System shall allow the user to save a configuration file containing the System…