SRD_Version_3.1.pdf

For Official Use Only (FOUO) - v3.1 - 20 July 2018 iii

CHANGE HISTORY

Change Version Date Original Un-Modified 1.0 September 1997 Baseline Modified 2.0 1 July 2015 Initial release to contractors 2.0.1 29 July 2015 All 1st Gov. comments incorporated 2.0.3 22 September 2015 All 1st Gov. and contractor comments

2.1 27 November 2015

All 2nd Gov. and contractor comments

2.2 15 July 2016

All 3rd Gov. and contractor comments

2.3 20 October 2016

All 4th Gov. and contractor comments

2.4 16 June 2017

All 5th Gov. and contractor comments

2.5 13 December 2017

All 6th Gov. and contractor comments

3.0 17 January 2018

All 7th Gov. and contractor comments

3.1 20 July 2018 iv

THIS PAGE INTENTIONALLY BLANK

v

Table of Contents

1. SCOPE

1.1 System Identification

1.2 System Overview

1.3 System Requirements Document Overview

2. APPLICABLE DOCUMENTS

2.1 General

2.2 Government documents

2.2.1 Specifications, Standards, and Handbooks

2.3 Non-Government Publications

2.4 Order of Precedence

3. REQUIREMENTS

3.1 System Interface Requirements

3.1.1 MIL-STD-1553B

3.1.2 Gigabit Ethernet

3.1.3 ARINC 429

3.1.4 RS-422 Serial Interfaces

3.1.5 RS-232 Serial Interface

3.1.6 Discrete Interfaces

3.1.7 Precise Time and Time Interval

3.1.8 Power

3.1.9 Key Loader Interface

3.1.10 GPS Antenna Interface

3.1.11 Antenna Electronics

3.2 Embedded GPS Receiver Requirements

3.2.1 Acquisition and Tracking Modes

3.2.2 Space Based Augmentation System - Use Permitted

3.2.3 EGR Receiver Status Messages

3.2.4 Complementary Navigation Message

3.3 Performance Requirements

3.3.1 Inertial Alignment Modes

3.3.2 Navigation Solutions

3.3.3 Aiding and Processing

vi

3.4 System Capability Requirements

3.4.1 Anti-Spoofing

3.4.2 Security

3.4.3 Key Loading

3.4.4 Monitoring and Maintenance

3.4.5 OMS Interface/Critical Abstraction Layer

3.4.6 Weapons Initialization (and Data Transfers)

3.4.7 Global Airspace Access

3.4.8 Alternate Time Source (Internal)

3.4.9 EGI-M Startup

3.5 Environmental Requirements

3.5.1 Temperature and Cooling

3.5.2 Altitude

3.5.3 Vibration

3.5.4 Shock

3.5.5 Humidity

3.5.6 Salt Fog

3.5.7 Explosive Atmosphere

3.5.8 Sand and Dust

3.5.9 Fungus

3.5.10 Acoustic Noise

3.5.11 Rain

3.5.12 Electromagnetic and Electrical Environment

3.5.13 Structural Design Loads

3.5.14 Acceleration

3.5.15 Rapid Decompression

3.6 Design and Construction Constraints

3.6.1 Hardware Design and Service Life

3.6.2 Computer Processing and Utilization

3.6.3 Software Design

3.6.4 Modular Open Systems Architecture and Adaptability

3.6.5 Mechanical

3.6.6 Size, Weight, and Power

3.6.7 System Safety

vii

3.6.8 Human System Integration

3.7 Reliability and Maintainability Requirements

3.7.1 Mean Time between Failure

3.7.2 Mean Time to Replace

3.7.3 BIT Qualitative Requirements

3.7.4 Calibration

3.7.5 Item Unique Identification

4. VERIFICATION

4.1 Verification Provisions

4.1.1 Philosophy of Verification

4.1.2 Location of Verification

4.1.3 Responsibility for Verifications

4.1.4 Verification Cross Reference Matrix

4.2 Verification Methods

4.2.1 None (N)

4.2.2 Inspection (I)

4.2.3 Analysis (A)

4.2.4 Demonstration

4.2.5 Test

4.3 Requirements Verification

5. ACRONYMS AND ABBREVATIONS

6. APPENDICES

Appendix 10 F-22

Appendix 20 F/A-18E/F

Appendix 30 B-1B

Appendix 40 E-2D

Annex A Recorded Maintenance Data .................................................................................... i

A.1 Deactivation Condition .............................................................................................. i A.2 Data Collection Method ............................................................................................. i A.3 Data to be Collected .................................................................................................. i viii

List of Figures

Figure 1: Cooling Air Flow Figure 2: Random Vibration Endurance Level (exposure time 1 hour per axis) Figure 3: Random Vibration Functional Level (exposure time 1 hour per axis) Figure 4: Sinusoidal Vibration Functional Test Level Figure 5: Acoustic Noise Spectrum

List of Tables

Table 1: Specifications Table 2: Standards and Handbooks Table 3: Other Publications Table 4: Other Government Documents, Drawings, and Publications Table 5: Non-Government Publications Table 6: SINS Input Discrete Electrical Characteristics Table 7: Alignment Modes and Inertial Performance Table 8: Maximum Dynamic Rates (INS Only and GPS/INS Blended) Table 9: GPS/INS (Blended) Performance Table 10: Zeroize Implementation Table 11: EGI-M Size, Weight and Power Options Table 12: LDC (28VDC) Worst Case Requirements Table 13: Verification Cross Reference Matrix Table

1. SCOPE

The Department of Defense (DoD) is updating its family of legacy Enhanced Global Positioning/Inertial (EGI)s to adapt to the evolving and challenging environment of modern day warfare. This system will be referred to as ‘EGI-M’, M is for modernized, throughout this document. The EGI-M has potential application to Air Force, Army, Navy, Marines, and Coast Guard platforms.

The EGI-M system will leverage the results of the Military Global Positioning System (GPS) User Equipment (MGUE) Increment 1 Program, which developed an airborne form factor, Military (M-Code) capable, Embedded GPS Receiver (EGR) based on CI-MGUE/AV-861E Technical Requirements Document (TRD), as well as leverage existing EGI technology lessons learned. The EGR functional and performance requirements in the CI-MGUE/AV-861E TRD will serve as a baseline set of reference EGR requirements for this System Requirements Document (SRD).

The EGI-M system will be developed based on the theoretical tenets of a Modular Open Systems Architecture (MOSA), and directly leverage lessons learned from Open Systems Architecture initiatives such as Open Mission Systems (OMS) and Future Airborne Capability Environment (FACE).

The EGI-M system will incorporate common interfaces (MIL-STD-1553B, Aeronautical Radio Inc (ARINC) 429, and Ethernet) between the system and host platform IAW Interface Specification

(IS)-EGI-179.

The EGI-M system will also apply necessary Diminishing Manufacturing Sources Refresh and Obsolescence Upgrades to ensure sustainability and reliability.

All of these enhancements move the system towards the next iteration improved ‘Assured PNT’ vision.

1.1 System Identification

This SRD applies to the modernization of the Honeywell Aerospace H-764, H-764 Legacy, and Future Airborne Lightweight Navigator (FALCN); as well as the Northrop Grumman LN-100G, LN-251 and LN-260 family of EGIs.

1.2 System Overview

The EGI-M will be a self-contained navigation system providing PNT solutions to meet warfighter mission requirements specified in this SRD. EGI-M development intends to maintain as much common hardware and software as practicable across the entire EGI-M family. In addition to the existing EGI specifications, the body of this SRD represents the baseline functional, performance, and system requirements that must be met by the EGI-M.

1.3 System Requirements Document Overview

This SRD establishes functional, performance, and system requirements of the EGI-M system.

Section 3 ‘shall’ statements represent minimum mandatory or threshold requirements. Section 3 ‘should’ statements represent non-mandatory or objective requirements. These non-mandatory requirements are selectable by the contractor to become ‘shall’ statements in their contractual System Specifications. Section 3 ‘will’ statements represent a statement of fact or declaration of purpose that are not subject to verification. Terms ‘shall’ and ‘should’ herein are immediately followed by a requirement number within italicized square brackets that align with notation in the Verification Cross Reference Matrix (VCRM), Table 13. In addition, Section 3 associated verification methods (abbreviations) are located in the right-hand margin across from each requirement ‘shall/should.’ These method abbreviations are defined in Section 4. Definitions, along with Acronyms and Abbreviations, are considered part of the requirements that utilize them. Appendices are part of this document and contain requirements that are unique to specific configurations. Notes are considered additional clarification or guidance, and are therefore not requirements.

2. APPLICABLE DOCUMENTS

2.1 General

2.2 Government documents

The following documents (versions and issue dates) form a part of this document to the extent specified herein.

2.2.1 Specifications, Standards, and Handbooks

2.2.1.1 Specifications

MIL-PRF-39012F 24 Nov 2014 Performance Specification - Connectors, Coaxial, Radio Frequency, General Specification

MIL-PRF-ADAP-AE-

401F

Performance Specification Item for the Antenna Electronics (AE) Navstar Global Positioning System Advanced Digital Antenna Production

(ADAP)

Table 1: Specifications

2.2.1.2 Standards and Handbooks

MIL-STD-130N,

Change 1

16 Nov 2012 Department of Defense Standard Practice, Identification Marking of U.S. Military Property

MIL-STD-461G 11 Dec 2015 Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-STD-704A, B, C,

D, E, F

11 Apr 1973 (A) 17 Nov 1975 (B) 30 Dec 1977 (C) 31 Mar 1988 (D) 1 May 1991 (E) 12 Mar 2004 (F)

Aircraft Electrical Power Characteristics

MIL-HDBK-704-8 09 Apr 2004 Guidance for Test Procedures for Demonstration of Utilization Equipment Compliance to Aircraft Electrical Power Characteristics 28Volts Direct Current (VDC)

MIL-HDBK-781A,

Notice 1

30 Jan 2015 Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production

MIL-STD-810G,

Change 1

15 Apr 2014 Department of Defense Test Method Standard:

Environmental Engineering Considerations and Laboratory Tests

MIL-STD-882E 11 May 2012 System Safety MIL-STD-1472G 11 Jan 2012 Human Engineering MIL-STD-1553B 15 Jan 1996 Digital Time Division Command/Response

Multiplex Data Bus

MIL-STD-464C

1 Dec 2010

Electromagnetic Environmental Effects Requirements for Systems

MIL-STD-2217, Notice

4 Nov 2014 Memory Loader/Verifier Multiplex Bus Interface with Avionics Systems, requirements for

MIL-HDBK-2084,

Notice 3

22 Apr 2014 General Requirements for Maintainability of Avionics and Electronic Systems and Equipment

MIL-HDBK-5400,

Notice 1

22 Apr 2014 Electronic Equipment, Airborne, General Requirements for

MIL-HDBK-454B

15 Apr 2007 Department of Defense Handbook General Guidelines for Electronic Equipment

MIL-HDBK-310 23 Jun 1997 Global Climate Data for Developing Military Products

Table 2: Standards and Handbooks

2.2.1.3 Other Publications

ADS-37A 28 May 1996 Electromagnetic Environmental Effects Management, Design, and Test Requirement

CI-FRPA-3070A, Part I

11 Nov 1987 Critical Item Development Specification for the AS- 3822/URN Fixed Reception Pattern Antenna 3 (FRPA-3) of the Navigation Satellite (or Signal) Timing & Ranging (NAVSTAR) GPS

ICD-GPS-060B 12 Feb 2002 Precise-Time and Time-Interval (PTTI) Interface

IS-GPS-099H 24 Nov 2014 Interface Specification for the NAVSTAR Global Positioning System ADAP

CI-GAS1/AE-300C

Addendum 3

30 May 2014 Critical Item Development Specification For the Antenna Electronics (AE) Line Replaceable Unit (LRU) of the N Global Positioning System Antenna System - 1 (GAS-1)

CI-GAS1/CRPA-300A

Appendix II

24 Apr 1998 Critical Item (CI) Development Specification for Appendix II to the Controlled Reception Pattern Antenna (CRPA) SS-GAS1-300A Line Replaceable Unit (LRU) of the NAVSTAR Global Positioning System Antenna System (GAS)- 1

IS-GPS-200H 17 Apr 2012 Navstar GPS Space Segment/Navigation User Interfaces

ICD-GPS-700D Navstar GPS Military-Unique Space Segment/User Segment Interfaces

IS-GPS-703F

IRN-IS-GPS-703F-001

Navstar GPS Military-Unique Space Segment/User Segment Interfaces (Secret)

DoDI 5200.39 May 28 2015 Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E)

IS-GPS-177A

(PIRN-001)

13 Feb 2015 (12 Nov 2015)

NAVSTAR GPS Military-Unique User Equipment Interface Specification for the Modernized Y-code/M-code/Coarse-Acquisition (YMCA) Receiver Dual-Port Random Access Memory Bi-Directional Data Port

IS-GPS-179

27 Jul 2016 GPS User Equipment Interface Specification for the MIL-STD-1553 Multiplex Bus Interface of Modernized DoD Standard GPS UE Radio Receivers

IS-EGI-179 19 Jan 2018 Universal ICD IS-EGI-179

MSID-001A 23 Feb 2015 MGUE Serial Interface Document (MSID) GPS Security Classification Guide

(SCG)

2 Dec 2015 GPS Security and Declassification Classification Guide, Appendix J

GPU-PRD-705, Version 2.8

15 Aug 2017 GPS Modernized Precise Positioning Service (PPS) User Equipment Security Approval Process Requirements Document (PRD)

GPU-PRD-711, Version 4.0c

GPS Security Certification PRD

SNU- 84 Rev D

21 Sep 1992 Specification for United States Air Force (USAF) Standard Form, Fit, and Function Medium Accuracy Inertial Navigation Unit

CI-MGUE/AV-861E

(PSCN-002)

13 Feb 2015

(12 Nov 2015)

MGUE Aviation Form Factor Requirements

AR-57A 3 May 1971 Shipboard Data Link System Requirement for Aircraft Inertial Navigation Systems Alignment (Confidential)

MSO-C145b 12 Aug 2016 Airborne Navigation Sensors using the Global Positioning System (GPS) / PPS for Area Navigation (RNAV) in Required Navigation Performance (RNP) Airspace and for Automatic Dependent Surveillance- Broadcast (ADS-B)

ASCC AIR STD 70/16B Oct 2002 Specification for evaluation for the accuracy of hybrid navigation systems

PL-IDD-20110923 23 Sep 2011 Interface Design Description for Program Loader

AAVSP-02, Edition A, V1 (STANAG 7221)

12 May 2015 North Atlantic Treaty Organization (NATO) Standardization Agreement, Broadband Real-time Data Bus

Table 3: Other Publications

2.2.1.4 Other Government Documents, Drawings, and Publications

FAA Advisory Circular 20-165B

7 Dec 2015 Airworthiness Approval of ADS-B Out Systems

14 CFR 91.225 24 Jan 2011 ADS–B Out equipment and use

14 CFR 91.227 24 Jan 2011 ADS-B Out equipment performance requirements

14 CFR Part 121, Appendix G, Section 3(b)

19 Mar 2013 Doppler Radar and Inertial Navigation System (INS)

NOAA Technical Report

NESDIS/NGDC

15 Dec 2014 The US/UK World Magnetic Model for 2015-2020

NIMA TR8350.2

3rd Edition, Amendment 1

3 Jan 2000 Department of Defense World Geodetic System 1984: Its Definition and Relationships with Local Geodetic Systems

EGM 2008 Jul 2008 Earth Gravitational Model 2008: WGS 84 Version

TSO-C145d 20 Dec 2013 Airborne Navigation Sensors Using the Global Positioning System Augmented by the Satellite Based Augmentation System (SBAS)

OMS 1.2 OMS Definitions and Documentation (D&D) version 1.1

Table 4: Other Government Documents, Drawings, and Publications

2.3 Non-Government Publications

AS9100C 15 Jan 2009 Quality Systems for Aerospace Manufacturers ASN-157 ASN-157 Doppler Navigation Set Interface

Specification

ARINC 407-1 Jun 1961 ARINC Synchro System Manual

RTCA/DO-178C 13 Dec 2011 Software Considerations in Airborne Systems and Equipment Certification

RTCA/DO-254 19 Apr 2000 Design Assurance Guidance for Airborne Electronic Hardware

RTCA/DO-229D,

Change 1

1 Feb 2013 Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System Airborne Equipment

ARINC Characteristics 743A-5 GNSS Sensor

29 May 2009 Global Navigation Satellite System (GNSS) Sensor

ARINC Characteristics 743B GNSS Landing System Sensor Unit

29 May 2009 GNSS Landing System Sensor Unit (GLSSU)

ARINC Specification 429P1-18

29 Nov 2012 Digital Information Transfer System (DITS), Part 1, Functional Description, Electrical Interfaces, Label Assignments and Word Formats

ARINC Specification 429P2-16

17 Dec 2004 Mark 33 DITS, Part 2 - Discrete Data Standards

ARINC Specification 429P3-19

25 Jun 2009 Mark 33 DITS - Part 3 - File Data Transfer Techniques

C145 May 2014 FACE Technical Standard Edition 2.1

FACE Shared Data Model

15 Apr 2015 FACE Shared Data Model 2.1

IEEE 802.3ab

1999 Institute of Electrical and Electronics Engineers (IEEE) Standard for Information Technology - Telecommunications and information exchange between systems - Local and Metropolitan Area Networks - Part 3: Carrier Sense Multiple Access with Collision Detection Access Method and Physical Layer Specifications - Physical Layer Parameters and Specifications for 1000 Mb/s Operation over 4 pair of Category 5 Balanced Copper Cabling, Type 1000BASE-T (Gigabit Ethernet)

IEEE 802.3 2012 IEEE Standard for Ethernet IEEE 1588 2008 IEEE Standard for Precision Time Protocol (PTP)

Table 5: Non-Government Publications

2.4 Order of Precedence

In cases of conflict between the requirement(s) in this SRD and the requirement(s) contained in the references cited herein, the requirement(s) in this SRD document shall take precedence.

Nothing in this document shall supersede applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

Requirements for Electronic Equipment should [1] follow the guidelines of MIL-HDBK-454B (Objective).

3.1 System Interface Requirements

The interfaces outlined in this section shall [1] meet the tenets of MOSA with all open systems host platform sub-systems.

The MIL-STD-1553B, ARINC 429, and Gigabit Ethernet buses, inclusively, are referred herein as the Digital Navigation I/O buses.

3.1.1 MIL-STD-1553B

The EGI-M shall [1] have two (2) MIL-STD-1553B high speed, dual-redundant multiplex buses.

The EGI-M MIL-STD-1553B interface shall [2] support transformer coupling.

The EGI-M shall [3] provide time tagging transmitted data to a resolution of either 50 microseconds or (not simultaneously) 64 microseconds.

The EGI-M shall [4] provide high rate motion compensation data to external sensors at either a minimum of 200 Hz (for multiples of 10 decimal applications) or alternatively 256 Hz (for powers of 2 applications).

The EGI-M shall [5], via software changes alone, compute, output, and receive data at rates in either a power of 2 format (e.g., 2 Hz, 64 Hz, 128 Hz, 256 Hz) or in a multiple of 10 format (e.g., 10 Hz, 50 Hz, 200 Hz).

The EGI-M MIL-STD-1553B interface shall [6] process and compute all input and output parameters IAW with IS-EGI-179.

3.1.2 Gigabit Ethernet

The EGI-M shall [1] have two (2) Gigabit Ethernet 802.3ab (backward-compatible with 10/100 Fast Ethernet 802.3) interfaces.

The EGI-M Ethernet interface shall [2] process and compute all input and output parameters IAW with IS-EGI-179.

3.1.2.1 Precise Time Protocol (PTP)

The EGI-M shall [1] implement Precision Time Protocol IAW IEEE 1588 and provide it as an input/output for time synchronization with the host.

The EGI-M shall [2] allow for enabling and disabling the IEEE 1588.

The EGI-M shall [3] allow for the selection of the EGI-M to be master or slave.

3.1.3 ARINC 429

The EGI-M shall [1] have six (6) ARINC 429 High Speed interfaces.

The EGI-M shall [2] provide for configurable selection of input, output, or disabled for each ARINC 429 interface.

The EGI-M shall [3] process all ARINC 429 messages IAW with IS-EGI-179.

3.1.4 RS-422 Serial Interfaces

3.1.4.1 EGR Auxiliary Serial Interface

The EGI-M shall [1] provide external access to the EGR RS-422 auxiliary serial interface.

3.1.4.2 Laboratory Testing Interface

The EGI-M shall [1] have one (1) RS-422 interface for the purpose of EGI-M laboratory simulation and testing using a GPS satellite signal generator system.

The EGI-M LTI shall [2] provide for the EGI-M to accept simulated inertial data inputs synchronized with the dynamic profile utilized by the GPS satellite signal generator.

The EGI-M LTI shall [3] only be available when the EGI-M is commanded into laboratory test mode.

The EGI-M laboratory test mode shall [4] provide for the same I/O availability as the normal operating mode.

The EGI-M shall [5] provide a discrete to enable/disable INS aiding to the EGR.

The EGI-M shall [6] provide a discrete to enable/disable GPS updates to the GPS/INS navigation solution.

The EGI-M shall [7] provide a discrete to enable/disable zero velocity updates to the GPS/INS navigation solution.

The EGI-M shall [8] provide for external access to interfaces required to "disconnect" the transfer of internal inertial data and to substitute simulated inertial data.

Note: Interface requirements and special processing requirements are to be provided for Government and third-party use.

The EGI-M shall [9] include measures to prevent the unintentional activation of the laboratory testing interface.

Note: The definition of the interface quantities will need to be related to a description of an arbitrary platform dynamic profile noting any assumptions and algorithms relative to sampling rates, angular commutativity, and scaling corrections.

Note: Quantitative navigation solution accuracy requirements do not apply for this testing.

3.1.4.3 User Configurable Interface

The EGI-M shall [1] have one (1) user defined RS-422 interface reserved for future integration requirements.

3.1.5 RS-232 Serial Interface

The EGI-M shall [1] provide external access to the EGR RS-232 auxiliary serial interface.

3.1.6 Discrete Interfaces

3.1.6.1 On-Off

The On-Off discrete shall [1] consist of a minimum of two pins, HI and LO.

The EGI-M shall [2] shutdown when the discrete HI is shorted to LO.

The EGI-M shall [3] startup when the discrete HI is disconnected from LO, assuming primary power is available as described in paragraph 3.6.6.1 herein.

3.1.6.2 Zeroize

(FOUO) The zeroize discrete, when activated, shall [1] perform the zeroization as defined in paragraph 3.4.2 herein.

3.1.6.3 Shipboard INS Interrupt

The Shipboard INS (SINS) Interrupt Discrete signal shall [1] be utilized to determine the time of validity of SINS 1553B input data.

The SINS Interrupt Discrete signal shall [2] be a differential signal with the characteristics shown in Table 6.

Table 6: SINS Input Discrete Electrical Characteristics

3.1.6.4 Weight-On-Wheels

The EGI-M shall [1] accept a transistor-to-transistor Logic (TTL), active low discrete from the host platform for Weight-on-Wheels (WOW) state.

3.1.6.5 Parking Brake

The EGI-M shall [1] accept a TTL, active low discrete from the host platform for parking brake state.

3.1.7 Precise Time and Time Interval

3.1.7.1 1 Pulse Per Second Interfaces

The EGI-M shall [1] have an external connection for one (1) 1PPS input pulse with characteristics as specified in CI-MGUE/AV-861E, paragraph 3.1.1.5.

The 1PPS input interface time of the leading edge shall [2] be provided by the Digital Navigation I/O buses.

The EGI-M shall [3] have an external connection for three (3) 1PPS output pulses with characteristics as specified in CI-MGUE/AV-861E, paragraph 3.1.1.5.

The 1PPS output interfaces time of the leading edge shall [4] be provided by the Digital Navigation I/O buses.

The EGI-M shall [5] time tag the leading edge signal pulse with Universal Coordinated Time

(UTC).

3.1.7.2 Time Mark Input/Output

The EGI-M shall [1] provide Time Mark interfaces for transferring precision time data to and from the EGR, as specified in CI-MGUE/AV-861E, paragraph 3.1.1.6.

The EGI-M Time Mark data shall [2] be provided by the Digital Navigation I/O buses.

3.1.7.3 Have Quick

The EGI-M shall [1] provide one (1) HAVE QUICK interface defined IAW CI-MGUE/AV-861E, APPENDIX XII.

Note: The HAVE QUICK Time-Of-Day (TOD) loading is characterized as having an input impedance of not less than 5,000 ohm resistive.

3.1.8 Power

The EGI-M will meet all power interface requirements as defined in paragraphs 3.6.6.1 and

3.6.6.2 herein.

3.1.9 Key Loader Interface

(FOUO) The EGI-M shall [1] include a DS-101 conformant key loader interface that accepts GPS crypto-variables (CVs) for point-to-point transfer via the key material input paths specified in CI-MGUE/AV-861E, paragraph 3.1.1.4.1 and subparagraphs.

3.1.10 GPS Antenna Interface

The EGI-M shall [1] meet the interface requirements for the EGR when interfaced to either a Fixed Reception Pattern Antenna (FRPA) or CRPA and AE subsystems, as specified in CI- MGUE/AV-861E, MIL-PRF-ADAP-AE-401F, CI-GAS1/CRPA-300A Appendix II, and CI-FRPA- 3070A, Part I.

The EGI-M shall [2] have a maximum attenuation of 1decibel(dB) between the EGR Radio Frequency (RF) input and the EGI-M external RF antenna input.

A signal level of -30dBW at any frequency between 30 Hz and 33GHz, but excluding the frequency bands within ±75Megahertz (MHz) of Link 1 (Frequency Signal) (L1) and Link 2 (Frequency Signal) (L2), shall [3] not cause more than 1.0dB degradation in effective receiver tracking state performance.

The EGI-M shall [4] incorporate one (1) RF antenna input and one (1) configurable RF/digital antenna input.

The RF and digital signal types shall [5] operate independently.

The EGI-M (including EGR), integrated with a beam-steering digital antenna electronics DAE unit, shall [6] operate in a combined beam-steering plus nulling mode.

The EGI-M shall [7] provide burn-out protection to prevent permanent damage to the receiver, as specified in CI-MGUE/AV-861E paragraph 3.4.1.4.4, at the EGI-M GPS RF input terminal.

3.1.11 Antenna Electronics

The EGI-M AE interface shall [1] provide and accept Control, Status, and Test signals to and from the AE units for both the AE discrete and serial port interfaces, as specified in IS-GPS-099, CI-GAS-1/AE-300C, Appendix I to SS-GAS1-300C.

The EGI-M shall [2] provide for interfacing to the EGR RS-422 beam-steering digital antenna control signals.

3.2 Embedded GPS Receiver Requirements

In addition to the EGR requirements specified in this section, the EGI-M EGR shall [1] meet all requirements as specified in CI-MGUE/AV-861E.

The EGI-M EGR shall [2] meet the requirements of Radio Technical Commission for Aeronautics (RTCA)/DO-254, at a Design Assurance Level (DAL) of ‘C’ or better.

The EGI-M EGR shall [3] meet the requirements of Radio Technical Commission for Aeronautics / Document (RTCA/DO)-178, at a DAL of ‘C’ or better.

The EGI-M EGR shall [4] incorporate an MGUE application-specific integrated circuit and its security certified module IAW GPU-PRD-711.

The EGI-M EGR shall [5] achieve compatibility certification and security approval IAW

GPU-PRD-705.

The EGI-M EGR shall [6] provide 2 Hz rate pseudo-range measurements and carrier phase measurements synchronized with GPS epoch to within ±100ns based on L1(M), L2(M) processed in accordance with ICD-GPS-700.

The EGI-M EGR shall [7] provide 2 Hz rate pseudo-range and carrier phase data synchronized with GPS epoch to within ±100ns based on L1(Y), L2(Y) processed in accordance with IS-GPS- 200.

The EGI-M shall [8] accept inputs over the Digital Navigation I/O buses for commanding the

EGR.

3.2.1 Acquisition and Tracking Modes

The EGI-M EGR default acquisition and tracking mode shall [1] be M-Code Only.

The EGI-M shall [2] only allow Mixed Mode to be commanded when in the EGI-M laboratory test mode.

The EGI-M EGR shall [3] not acquire GPS satellites until commanded by the host vehicle.

The EGI-M shall [4] provide a Direct-Y and Direct-M acquisition for up to 72 hours of continuous off time (absence of prime power) when no initial time estimate is inputted to the EGI-M in accordance with the performance requirements of CI-MGUE/AV-861E Table VII and VIII, given previous time figure of merit (TFOM), Position, Velocity, and Time (PVT) uncertainty, dynamics, and jamming environment conditions detailed in these tables.

The EGI-M shall [5] accept a command from the Digital Navigation I/O buses to enable/disable PPS Lockout (PPS-LO) mode, overriding PPS acquisition/tracking modes, as specified in Military Stand Order (MSO) C-145b Section 2.1.1.2.2.

3.2.1.1 GPS Signal Reacquisition

If operating in MY-CODE, M-CODE ONLY, or Y-CODE ONLY mode, and GPS signal track is lost, the EGI-M shall [1] reacquire either the M-code or Y-code; M-code; or Y-code, respectively, without resorting to hand-over techniques from unencrypted codes, for a loss period of up to 1,800 seconds in accordance with the performance requirements of CI-MGUE/AV-861E Tables X and XI, given the PVT uncertainty, dynamics, and jamming environment conditions detailed in these tables.

If reacquisition is unsuccessful after 1,800 seconds under the above conditions, then the EGI-M shall [2] provide for hand-over techniques from unencrypted codes to obtain signal reacquisition.

The EGI-M shall [3] not use hand-over techniques from unencrypted codes for signal reacquisition if a Direct-M or Direct-Y acquisition was previously commanded for the current operating cycle.

If reacquisition is not possible within the required time given this constraint, the EGI-M shall [4] provide an alert through the Digital Navigation I/O buses that reacquisition is not possible.

3.2.2 Space Based Augmentation System - Use Permitted

The EGI-M Satellite Based Augmentation System - Use Permitted (SBAS-UP) sub-mode shall [1] be OFF by default to ensure no processing/computations are affected by this input and also to ensure that no SBAS information is stored to memory locations.

The EGI-M shall [2] accept a command over the Digital Navigation I/O buses to enter/exit the SBAS-UP sub-mode.

The EGI-M SBAS-UP sub-mode shall [3] only operate when the EGR is in PPS-LO Mode.

The EGI-M shall [4] remain in PPS-LO Mode when leaving SBAS-UP sub-mode.

3.2.3 EGR Receiver Status Messages

The EGI-M shall [1] continuously monitor, provide operational status, and output over the Digital Navigation I/O buses Receiver Status messages and alerts specified in paragraph 3.2.8 of

CI-MGUE/AV-861E.

The EGI-M shall [2] continuously monitor and provide operational status, monitor performance, and compute, maintain, and make available for output over the Digital Navigation I/O buses, Figures of Merit (FOM) information as specified in paragraph 3.2.9 of CI-MGUE/AV-861E.

3.2.4 Complementary Navigation Message

The EGI-M shall [1] provide through the Digital Navigation I/O buses a complete set of Complementary Navigation Message (CNM) data for all SV in view as specified in IS-GPS-227.

A maximum of eight (8) sets of CNM data as well as a count of the number of data sets shall [2] be provided.

Note: Mission Constellation is always active. Mission Constellation details are specified in ICD-GPS-224E.

The EGI-M shall [3] output a CNM update status over the Digital Navigation I/O buses after the initial CNM is demodulated from the GPS Navigation Message and following receipt of each new CNM.

The EGI-M shall [4] output CNM data only if it is confirmed that the new CNM data collection is valid, and if the age of the CNM data is (1.0) hour old or less.

Note: Exceptions may be required to allow attempted CNM data transfer after short-term power off period.

The EGI-M shall [5] make available through the Digital Navigation I/O buses a complete set of CNM data for all SV in view to support data transfer to weapons (for weapons GPS initialization) and interface information on the status of each EGR tracking channel.

The EGI-M shall [6] supply the CNM for all Y-Code tracking channels to the platform IAW IS-

GPS-169.

3.3 Performance Requirements

3.3.1 Inertial Alignment Modes

The EGI-M shall [1] output an Inertial Only Navigation (NAV) ready indication on the Digital Navigation I/O buses when the INS can provide full performance in accordance with Table 7.

The EGI-M shall [2] output the current time spent in alignment in one (1) second increments on the Digital Navigation I/O buses.

The EGI-M shall [3] allow for selection of INS alignment modes.

3.3.1.1 Gyrocompass

At all latitudes south of 60° N and north of 60° S, the EGI-M shall [1] meet the performance specified in Table 7 after completion of gyrocompass (GC) alignment.

Between latitudes of 60° and 80°, inclusive, the EGI-M shall [2] meet the performance specified In Table 7 using an alignment time defined by the following equation:

Align time (minutes) = 4.0 * cosine (60.0°) * secant (Latitude degrees)

In the GC alignment mode, alignment shall [3] be performed with host provided present position.

If host provided present position is not supplied, alignment shall [4] be performed in order of precedence; GPS present position, valid previously stored present position.

When alignment quality is 5.0 Nautical Miles (NM)/hr Circular Error Probability (CEP) or better, any interruption of the GC alignment shall [5] not prolong the alignment time more than the period of alignment suspension plus 20.0 seconds per interruption.

3.3.1.2 Stored Heading Alignment

The EGI-M Stored Heading (SH) Alignment mode shall [1] level to local vertical and initialize heading to the value at the last shutdown.

Inertial navigation performance shall [2] meet the performance specified in Table 7 after a SH alignment.

Note: Specified performance in this mode assumes that a full GC alignment has been successfully completed on the last turn off, and the vehicle was not moved since the GC alignment completion.

3.3.1.3 Enhanced Interrupt Alignment

The EGI-M shall [1] incorporate an Enhanced Interrupted Alignment (EIA) capability to enhance the functional operation of GC alignment.

The EGI-M EIA capability shall [2] provide for an alignment process that begins with a complete normal (4.0 minute) GC alignment, transitions to NAV mode with movement of the aircraft to a new heading (change of between 70° and 90°), and then completes another alignment period of

6.0 minutes or less.

After completing this alignment, navigation performance shall [3] be 0.6 NM/hr CEP or less for at least 1.0 hour.

3.3.1.4 Shipboard-At Sea Alignment

3.3.1.4.1 Ship Inertial Navigation System

The EGI-M shall [1] complete SINS alignment, with performance specified in Table 7, utilizing SINS reference data per AR-57A.

3.3.1.4.2 Manual Shipboard Alignment

For shipboard manual alignments, the EGI-M shall [1] achieve the performance of Table 7, utilizing manually entered the ship’s latitude, longitude, and heading; while the ship maintains a constant speed (± 1.0 knot) and a heading change of up to 10° during the alignment period.

3.3.1.4.3 Stored Spotting Angle Alignment

After a successful completion of SINS alignment, the EGI-M shall [1] store the aircraft’s spotting angle (angle between ship and aircraft longitudinal axes) at aircraft shutdown.

At the next alignment with the aircraft not moved since, the EGI-M shall [2] complete successfully the Stored Spotting Angle Alignment with performance specified in Table 7.

0.8 NM/hr (Threshold)

0.6 NM/hr (Objective)

CEP

3 NM/hr

CEP

5 NM/hr

CEP

Ground Alignments Gyro-Compass Align 4.0 min 2.0 min 1.5 min Stored Heading Align 0.5 min -- --

At-Sea Alignments (on Ship) SINS Align 5.0 min 3.0 min 2.0 min Stored Heading Align 4.0 min 2.0 min 1.0 min Manual/Hand Set Align -- -- 10.0 min

In Motion Alignments (IMA) GPS IMA (on Ground, on Ship, or in-Flight) 10.0 min 7.0 min 5.5 min

Parameters (3x RMS) North and East Velocity 7.5 ft/sec 15.0 ft/sec 22.0 ft/sec North and East Acceleration 0.2 ft/sec2 0.2 ft/sec2 0.2 ft/sec2 Baro-Inertial Altitude 150 ft 150 ft 150 ft Vertical Velocity 6.0 ft/sec 9.0 ft/sec 12.0 ft/sec Vertical Acceleration 0.2 ft/sec2 0.2 ft/sec2 0.2 ft/sec2 True Heading 0.22° 0.7° 1.25° Pitch and Roll Attitude 0.13° 0.23° 0.34°

1. Reaction time measured in minutes from a -40°C start up. If equipment turn-on is at ambient temperature below -40°C, a 2 second warm up time for each 1°C below -40°C is allowed.

2. Reaction times and navigation accuracies are those achieved at 60° latitude (North and South).

3. In-Air alignment reaction times: Heading and variation input accuracy of +2.5° is assumed, but heading initialization shall not be required for either GPS/IFA or for CVA/GPS alignments.

4. Navigation accuracy is present position accuracy determined by alignment sub mode and reaction time.

5. Navigation parameters are 3x RMS, unless noted otherwise.

6. All values are applicable for flights up to 8 hours except as noted (there shall be no software limitations that would preclude continuous operations up to one year in length).

7. North and East velocities are for the first two hours of flight. Add 6 ft/sec (3 SIGMA) for flights over 2 hours.

8. True heading accuracy is for initial alignment. Add 0.03 deg/Hr (3 SIGMA) drift rate.

Table 7: Alignment Modes and Inertial Performance

3.3.1.5 In-Motion Alignment/Update

The EGI-M shall [1] perform in-motion alignments of the INS under all operating conditions.

Using GPS inputs, the EGI-M IMA navigation performance shall [2] meet the performance specified in Table 7.

Following a completed stationary coarse alignment (5.0 NM/hr CEP or less), the EGI-M shall [3] complete the PPS IMA, within five (5.0) minutes, providing there has been continuous GPS coverage with a Horizontal Dilution-of-Precision (HDOP) of less than or equal to 2.0.

Without the benefit of a stationary coarse alignment, the EGI-M shall [4] complete the PPS IMA within 10 minutes, providing there has been continuous GPS coverage with an HDOP of less than or equal to 3.5.

Following a complete stationary coarse alignment, the EGI-M shall [5] complete the Standard Positioning Service (SPS) IMA within 10 minutes, providing there has been continuous GPS coverage with a HDOP of less than or equal to 2.0.

Note: SPS performance based upon L1 only Course Acquisition (C/A)-Code tracking with Selective Availability (SA) set to “0.”

Without the benefit of a stationary coarse alignment, the EGI-M shall [6] complete the full SPS IMA within 15 minutes, providing there has been continuous GPS coverage with an HDOP of less than or equal to 3.5.

Note: SPS performance based upon L1 only C/A-Code tracking with SA set to “0.”

3.3.1.6 Navigation Alignment Refinement Feature

The EGI-M shall [1] include a Navigation Alignment Refinement Feature (NARF), that will be mechanized during normal ground operations to include taxiing, turning and then stopping, to refine the inertial sensor tilt and bias errors while the INS is in NAV mode.

The EGI-M shall [2] continue to update the INS Only and blended navigation solutions with zero velocity updates whenever no motion is detected up to the point at which the aircraft exceeds an 80 knot threshold or when WOW is set to “Off-Wheels.”

When the 80 knot threshold, or when WOW is set to “Off-Wheels”, NARF shall [3] be disabled for the remainder of the current operating cycle.

The NARF shall [4] not prevent the execution of normal alignment and navigation functions.

The EGI-M INS alignment time shall [5] not be incremented while in NARF mode.

The EGI-M shall [6] accept a command from the Digital Navigation I/O buses to disable NARF for the remainder of the current operating cycle.

3.3.2 Navigation Solutions

The EGI-M shall [1] generate GPS Only, GPS/INS (blended), and INS Only navigation solutions.

The EGI-M shall [2] also provide information on the merit of each navigation solution at all times.

The EGI-M shall [3] only allow the use of P-Code when in the EGI-M laboratory test mode.

The EGI-M shall [4] not process data inputs from satellites identified by the EGI-M’s integrity function as being erroneous.

For the limited condition when the EGI-M’s integrity function identifies a satellite is providing erroneous measurements, but not able to identify the source of the erroneous measurement, then the EGI-M shall [5] suspend processing of GPS data inputs until such time that EGI-M’s integrity function no longer identifies an integrity issue, and alternatively when additional satellite(s) are acquired and tracked allowing the integrity function to isolate the issue to a given satellite.

With PPS-LO enabled, under no circumstance shall [6] encrypted GPS data be used to generate an output navigation solution.

The EGI-M shall [7] provide automatic entry into the INS attitude mode when INS Navigation mode has been commanded while current alignment quality indicates the projected Inertial Only (“free” inertial) navigation performance is greater than 5.0 NM/hr CEP.

Parameter Roll Pitch Yaw Angular Rate ±420o/sec ±420 o/sec ±420 o/sec Angular Acceleration ±1,500 o /sec/sec ±1,500 o/sec/sec ±1,500 o/sec/sec

Note: All three axes can maneuver through any angle Parameter X Y Z

Linear Velocity ±3,937 ft/sec ±3,937 ft/sec ±3,937 ft/sec Linear Acceleration ±322 ft/sec/sec ±322 ft/sec/sec ±322 ft/sec/sec Jerk ±328 ft/sec/sec/sec ±328 ft/sec/sec/sec ±328 ft/sec/sec/sec

Note: Navigation Frame (X,Y,Z) as defined in SNU 84-1/F-16

Table 8: Maximum Dynamic Rates (INS Only and GPS/INS Blended)

3.3.2.1 GPS Only Navigation Solution

After EGR initialization, acquisition, and track are successfully accomplished, the EGI-M shall [1] output the GPS Only Navigation Solution at all times on the Digital Navigation I/O buses.

The EGI-M shall [2] output the GPS Estimated Horizontal Error (EHE) and Estimated Vertical Error (EVE) position uncertainty values (1-sigma confidence) on the Digital Navigation I/O buses.

Aiding data from the INS and other aiding sensors shall [3] be used to aid the GPS Only solution for generation of the GPS high rate foreground navigation solution and background PVT solutions, IAW paragraph 3.3.3.4 of CI-MGUE/AV-861E.

3.3.2.2 GPS/INS (Blended) Navigation Solution

The EGI-M shall [1] use both GPS and inertial data to output a blended navigation solution at all times after INS alignment and GPS initialization on the Digital Navigation I/O buses IAW

IS-EGI-179.

The blended navigation solution output shall [2] be the best estimate of position, velocity, time, and attitude, based on a combination of GPS, INS, and pressure altitude aiding.

The EGI-M shall [3] include a Blended Integrity Algorithm.

(FOUO) The EGI-M blended integrity algorithm shall [4] have provisions for updating countermeasures to mitigate threats.

The EGI-M blended navigation solution performance shall [5] be the same or better than the INS Only solution performance.

The blended navigation solution shall [6] prioritize the use of GPS measurements based on signal assurance status, where “assured” measurements are prioritized over “usable” measurements.

The EGI-M shall [7] accept a command from the Digital Navigation I/O buses to use only “assured” measurements for navigation solutions and INS alignments where GPS data is used.

The EGI-M shall [8] output the blended navigation solution integrity status on the Digital Navigation I/O buses, including when GPS data used to form the Blended Navigation Solution was collected when satellite signal availability precluded an integrity function.

The statistical methods of Air Standardization Coordination Committee (ASCC) AIR STD 70/16B shall [9] be used for the definition of the EGI-M blended navigation solution performance characteristics.

During periods when encrypted GPS data is available, the EGI-M shall [10] use GPS altitude and calculate a pressure altitude correction bias for use during GPS non-availability.

When GPS is not available, the EGI-M shall [11] use valid pressure altitude with the calculated pressure altitude correction bias input to provide barometrically damped inertial altitude.

When pressure altitude input is determined invalid and GPS is not available, for the first 5 minutes, the EGI-M shall [12] use inertial data to determine altitude.

For times longer than 5 minutes, the EGI-M shall [13] use the altitude calculated at the 5 minute mark until pressure altitude input is determined to be valid.

The blended navigation solution performance of the EGI-M shall [14] not be degraded during maneuvers up to the maximum limits specified in Table 8.

The EGI-M blended navigation solution shall [15] meet the performance requirements in Table 9, without external Deflection of Vertical (DOV) aiding.

While operating with GPS aiding and the subsequent loss of GPS, the EGI-M blended navigation solution Free INS coasting performance shall [16] meet or exceed the requirements in Table 7

PVT Accuracies Parameter 1, 3

PPS

Performance2

SPS

Performance 5

3D Position (SEP), C/A code (m) N/A 17 3D Position (SEP), P(Y) code (m) 7.0 N/A 3D Position (SEP), M code (m) 7.0 N/A

Velocity (RMS), (m/sec) 4 0.10 0.10

Pitch, Roll (rms) 0.050° 0. 050° Platform Azimuth (rms) 0.050° 0. 050° True Heading (rms) 0.050° 0.050° Notes:

1 Based on the conditions specified in CI-MGUE/AV-861E for space, control and user equipment segment errors and dilution of precision

2 PPS performance based upon L1/L2 P(Y) and M-Code tracking

3 Performance applies when all GPS receiver channels in use are operating in state 5

4 Velocity uncertainties per axis

5 SPS performance based upon L1 only C/A-Code tracking with selective availability set to “0”

Table 9: GPS/INS (Blended) Performance

3.3.2.2.1 Blended Navigation Solution Integrity / Anti-Spoofing Functionality

The EGI-M shall [1] compute the blended navigation solution using only the measurements of healthy satellites that meet EGR RAIM requirements and are not deselected by the host through the satellite selection commands.

The EGI-M blended integrity algorithm shall [2] at a minimum use the Pseudo Range and Carrier Phase measurements from the EGR and inertial data.

The EGI-M blended integrity algorithm shall [3] output on the Digital Navigation I/O buses the probability of missed detection and time to alert for the scenario(s) provided by the government.

The EGI-M blended integrity algorithm shall [4] reject measurements that do not pass integrity checks.

The EGI-M blended integrity algorithm shall [5] output on the Digital Navigation I/O buses whether the blended navigation solution is usable or assured.

The EGI-M blended navigation solution shall [6] be assured when the measurements used are assured and passed blended integrity checks.

The EGI-M blended navigation solution shall [7] be useable when the measurements used are useable and passed blended integrity checks.

3.3.2.3 INS Only Navigation Solution

The EGI-M shall [1] provide the INS only navigation solution, as well as platform pitch, roll, azimuth, body rates, and acceleration information, at all times on the Digital Navigation I/O buses IAW IS-EGI-179.

The EGI-M INS only navigation solution shall [2] meet the performance requirements specified in Table 7, without external DOV aiding.

The only source of external aiding information for the INS only navigation solution shall [3] be pressure altitude.

The EGI-M shall [4] use valid pressure altitude input to provide barometrically damped inertial altitude.

When pressure altitude input is determined invalid, for the first 5 minutes, the EGI-M shall [5] use inertial data to determine altitude.

For times longer than five (5) minutes, the EGI-M shall [6] use the altitude calculated at the five

(5) minute mark until pressure altitude input is determined to be valid.

The EGI-M INS only navigation solution performance shall [7] not be degraded during maneuvers up to the maximum limits specified in Table 8

The statistical methods of ASCC AIR STD 70/16B shall [8] be used for the definition of the EGI-M INS Only navigation solution performance characteristics.

3.3.2.4 Alternate PNT Navigation Solution

The EGI-M shall [1] provide for the Digital Navigation I/O buses all outputs associated with the third-party application defined in paragraph 3.6.4.

3.3.3 Aiding and Processing

3.3.3.1 Gravity Deflection of Vertical Aiding

EGI-M shall [1] apply internally stored DOV corrections IAW National Geospatial Agency (NGA) Earth Gravitational Model (EGM) 2008.

EGI-M shall [2] accept and apply externally supplied DOV corrections IAW NGA EGM 2008.

The EGI-M shall [3] remain unclassified while processing DOV corrections.

3.3.3.2 Velocity Reference Aiding

The EGI-M shall [1] accept ASN-157 Doppler velocity data from the MIL-STD-1553B data bus to aid the blended navigation solution.

3.3.3.3 Magnetic Variation

The EGI-M shall [1] derive magnetic variation (MV) via a real-time algorithm.

The EGI-M shall [2] allow for selection between the use of internal or external MV.

When available, the EGI-M shall [3] accept and use an externally provided MV with a range of plus or minus 180°.

The EGI-M shall [4] use the most current version of the World Magnetic Model available at the time the EGI-M is produced.

3.3.3.4 Lever Arm Corrections

When attitude and heading are available, the EGI-M shall [1] reference the INS only, GPS only, and blended navigation solutions to a Guidance Control Point (GCP) identified by stored lever arm information.

The GCP to GPS lever arm shall [2] define the position of the GPS antenna relative to the GCP.

The EGI to GCP lever arm shall [3] define the position of the GCP relative to a point on the EGI- M to be identified in EGI-M installation drawings.

The EGI-M shall [4] accept and store five (5) sets of GCP to GPS antenna lever arms in non-volatile memory.

The EGI-M shall [5] accept and store five (5) sets of EGI to GCP lever arms in non-volatile memory.

The default GCP to GPS and EGI to GCP lever arm values shall [6] be zero.

3.3.3.5 Coordinate Systems

The EGI-M shall [1] implement WGS-84 in accordance with NGA.STND.0036_1.0.0_WGS84.

The EGI-M shall [2] use WGS-84 as the default horizontal datum for all solutions.

The EGI-M shall [3] use the WGS-84 EGM 2008 geoid as the default vertical datum for all solutions which report altitude above mean sea level.

The EGI-M shall [4] use the WGS-84 ellipsoid as the default vertical datum for all solutions which report altitude as height above ellipsoid.

The EGI-M shall [5] perform datum transformations in accordance with

NGA.STND.0036_1.0.0_WGS84.

The EGI-M shall [6] provide for position definitions in, and transformations between Horizontal angular quantities referenced to true, grid, and magnetic north and Military Grid Reference System.

The EGI-M shall [7] provide for position definitions in and transformations between the map datum identified in IS-EGI-179.

The EGI-M shall [8] output data in the Navigation reference system frames (X, Y, and Z) as defined in Specification for Navigation Unit (SNU) 84-1/F-16B.

3.4 System Capability Requirements

3.4.1 Anti-Spoofing

(FOUO) The EGI-M shall [1] protect all navigation solutions and timing outputs against spoofing signal threats as specified in CI-MGUE/AV-861, Attachment A (Protection Profile MGUE Aviation Form Factor Requirements), Appendix A (Classified Anti-Spoofing Requirements)

(FOUO) The EGI-M unaided and aided spoofing environment PVT accuracies, resolution, and computational rates shall [2] be as specified in CI-MGUE/AV-861E, paragraph 3.3.3, based on the conditions of CI-MGUE/AV-861E, Attachment A.

The EGI-M shall [3] output Anti-Spoofing status and assurance on the Digital Navigation I/O buses.

3.4.2 Security

The EGI-M shall [1] be Unclassified when keyed.

Note: Determination of unclassified information is based on the…