HSCG38-11-R-H00002 SSS

2 MB Posted Apr 14, 2011

Attached to: C-130H Segment II (A1U) COTS Electronic Flight Display System (EFDS)
Solicitation number: HSCG38-11-R-H00002
Issued by: Department of Homeland Security US Coast Guard

About this file

From the source

HSCG38-11-R-H00002 SSS ATTACHMENT 1

Text of this file

C-130H EFDS System/Subsystem Specification

Date: 23 March 2011

Prepared By:

Department of the Navy Naval Air Warfare Center, Aircraft Division

22347 Cedar Point Road Patuxent River, MD 20670-1161

HSCG38-11-R-H00002

ATTACHMENT 1

WARNING

This document (software) contains technical data which may be Restricted for export under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). Violations of these export laws may be subject to fines and penalties under the Arms Export Control Act (22 U.S.C. 2778).

WARNING

REVISION HISTORY

Document Title

REV. DATE REV. BY PAGES AFFECTED REMARKS

1.0 22 Mar 11 Fournier All Initial Release

Document Description Document Number None Title HC-130H EFDS System Subsystem Specification Document Date 23 March 2011 Software Acrobat 8.0, Excel 2003, Visio 2003, and Word 2003 File Name(s) Document Size Classification Unclassified Comments None

Page i

TABLE OF CONTENTS

1.0 SCOPE

1.1 IDENTIFICATION

1.2 SYSTEM OVERVIEW

1.3 TERMINOLOGY

1.4 DOCUMENT STRUCTURE

2.0 APPLICABLE DOCUMENTS

2.1 U.S. GOVERNMENT DOCUMENTS

2.2 NON-GOVERNMENT DOCUMENTS

3.0 SYSTEM REQUIREMENTS

3.1 SYSTEM MANAGEMENT

3.1.1 BIT

3.2 FLIGHT INSTRUMENT DISPLAY AND DATA MANAGEMENT

3.3 PRIMARY DISPLAY

3.3.1 Attitude Direction Indicator (ADI) Data

3.3.2 Barometric Altimeter

3.3.3 Radar Altimeter (ALT- 4000)

3.3.4 Airspeed Indicator

3.3.5 Vertical Speed Indicator (VSI)

3.3.6 Heading

3.3.7 Bearing Pointer

3.3.8 Course Deviation Indicator (CDI)

3.3.9 Receiver Autonomous Integrity Monitor (RAIM)

3.3.10 Distance To Go

3.3.11 Temperature, Speed, and Wind

3.3.12 Flight Plans & Waypoint Representation

3.3.13 Vertical Flight Representation

3.3.14 Range Scaling

3.3.15 Patterns/Procedures

3.3.16 Overlays

3.4 SECONDARY DISPLAY MANAGEMENT

3.5 ELECTRONIC IFR CHARTS AND DIGITAL MOVING MAPS

3.5.1 Instrument Flight Rules (IFR) Electronic Charts

3.5.2 Digital Maps

3.6 ADS-B (GDL-90)

3.7 CURSOR CONTROL DEVICES (CCD)

3.8 MISCOMPARE

3.9 DATA INTEGRITY

3.10 ADVISORY, CAUTION, AND WARNING SYSTEM (ACAWS)

3.11 CONTROL PANEL MANAGEMENT

3.12 COMPUTER RESOURCES AND HARDWARE

3.12.1 Memory/Processor Reserve

3.12.2 Receiver/Transmitter Address Selection

3.12.3 Interchangeability

3.12.4 Elapsed Time Indicator

3.12.5 Thermal Requirements

3.13 SAFETY

3.13.1 System Safety

3.13.2 Prohibited Materials

Page ii

3.13.3 Personnel Safety

3.13.4 Environmental Safety

3.13.5 Electrical Power Switches

3.14 ENVIRONMENTAL CONDITIONS

3.14.1 Low Pressure (Altitude)

3.14.2 Non-operating temperatures

3.14.3 Operating temperatures

3.14.4 Temperature Shock

3.14.5 Humidity

3.14.6 Vibration

3.14.7 Shock

3.14.8 Salt Fog

3.14.9 Fluid Contamination

3.14.10 Rapid Decompression

3.14.11 Explosive Atmosphere

3.14.12 Sand and Dust

3.14.13 Rain/Drip Proof

3.14.14 Fungus

3.15 ACCELERATION

3.16 ELECTROMAGNETIC INTERFERENCE AND COMPATIBILITY AND ELECTRICAL POWER

3.16.1 Electromagnetic Interference Requirements

3.16.2 Electromagnetic Compatibility Requirements

3.16.3 Specific Box Level EMI Testing Requirements

3.16.4 Power Requirements

3.17 COMMUNICATION SECURITY AND INFORMATION SECURITY

3.17.1 Red-Black Data Separation

3.17.2 TEMPEST Performance

3.18 RELIABILITY

3.18.1 Mean Time Between Failure

3.18.2 Operational Stability

3.18.3 Operational Service Life

3.18.4 Storage Life

3.19 MAINTAINABILITY

3.19.1 Preventive Maintenance

3.19.2 Adjustments

3.19.3 Panel Lamps

3.19.4 Peculiar Support Equipment

3.19.5 Organizational Level Maintenance

3.19.6 Packaging

3.20 HUMAN FACTORS

3.20.1 Training and Intuitive Design

3.20.2 Design for Maintainer

3.20.3 Environment

3.20.4 Controls and Displays

3.20.5 EFDS Keyboard and Panels

3.20.6 Displays

4.0 VERIFICATION

5.0 ACRONYMS

6.0 APPENDIX A

7.0 APPENDIX B

8.0 APPENDIX C

Page iii

Page iv

1.0 Scope

1.1 Identification

The avionics upgrade improves the HC-130H's worldwide military and civil operations capability in support of all USCG mission areas, as well as addresses flight safety, obsolescence and situational awareness issues for the aircrew. This document applies to the U.S. Coast Guard HC-130H Avionics Upgrade (A1U). It identifies the performance requirements to design and develop an Electronic Flight Display System (EFDS) and integrate it as part of the Flight Management System (FMS) to be incorporated it into the U.S. Coast Guard HC-130H Aircraft. This subsystem specification addresses the EFDS implementation into the system level FMS as defined in the FMS specification. As such it addresses all mechanical, electrical, and structural changes required to integrate the EFDS into the HC-130H aircraft but does not duplicate requirements set forth in the parent level document (See Figure 1). As an example, the environmental, electromagnetic interference, electrical power, and lighting requirements are defined in the FMS specification and as such will not be relisted in this document. There will be significant modifications to the Flight Deck. The Pilot and Co-Pilot stations will be modified with a new instrument panel and changes to the center console. Where appropriate other Pilot / Co-Pilot equipment will be relocated to improve the Human Machine Interface (HMI). The existing Navigator and Radio Operator’s stations will both undergo significant modifications to allow for improved crew coordination and distribution of crew responsibilities. The existing avionics bay under the flight deck will undergo rework to allow for the new avionics equipment to be installed. Where appropriate on the aircraft other equipment and antennas will be installed as necessary to support the new FMS.

The avionics upgrade provides for a CNS/ATM capability solution, a complete display system upgrade, and the consideration of HMI design to the HC-130H aircraft. The major components comprising the avionics upgrade are the CDU7000 based common cockpit FMS, Integrated Processing Computer (IPC), and the EFDS.

1.2 System Overview

The HC-130H aircraft must operate worldwide and fly in civilian controlled airspace. In order to ensure safe separation of military and civil air traffic and adherence to air traffic control clearances, the HC-130H aircraft must be capable of performing the following functions:

• Required Navigation Performance for Area Navigation (RNP RNAV)

• Barometric Vertical Navigation (Baro VNAV)

• Mode Select (Mode S) – elementary and enhanced surveillance

• Mode 5 Level 2

• 8.33 kHz VHF Channel Spacing

• TCAS

• TAWS

• Automatic Dependent Surveillance – Broadcast (ADS-B)

The system should also have growth capability to meet the following future requirements.

• Joint Precision Approach Landing System (JPALS)/Local Area Augmentation System

• Mobile User Objective System (MUOS)

The system will have an open and expandable architecture that can accommodate other pertinent flight information and permit growth to meet future global navigation and display requirements.

The design of all systems and equipment that are new to the vehicle and in some way interact with persons on board the aircraft should comply with, and will be evaluated against, guidelines found in the Joint Services Specification Guide – 2010-1 (JSSG-2010), Crew Systems, 30 October 1998. JSSG-2010 is a compilation of many human systems integration and human-machine interface documents that describe best practices, lessons learned, and research evidence that promote safe and effective design features of systems and equipment.

The detailed requirements are contained in section 3 of this specification.

1.3 Terminology

This document uses the following definitions:

• SHALL: Indicates a requirement. An approved design should comply with every requirement, which can be assured by inspection, test, analysis or demonstration.

• Must: Identifies items that are important and which may be duplicated somewhere else in the document as a “shall.”

• Will: Denotes a capability that is a surety or a fact.

• Should: Denotes a recommendation that would improve the equipment, but does not constitute a requirement.

• May: Denotes a recommendation that is optional.

1.4 Document Structure

This document is organized with the following sections:

• Section 1: Scope - Discusses the scope of the specification.

• Section 2: Referenced Documents - Contains references to the documents cited in this specification.

• Section 3: System Requirements - Contains the requirements of this specification.

• Section 4: Verification - Discusses the verification methods that will be used to validate that the system will meet the requirements of this specification.

• Section 5: Acronyms and Abbreviations - Lists the acronyms and abbreviations used within this specification

This document does not discuss any classified or proprietary material.

The Document Tree for this program is shown in Figure 1. The documentation tree in Figure 1 describes the requirements allocation process from the highest level, customer specifications, to the lowest level Computer Software Configuration Items (CSCIs). Description of documentation below the Software Requirement Specifications and Navigation Subsystem Requirements Document implies decomposition and design detail beyond the scope of this SSS, and is therefore approximate and provided for informational purposes only.

• Functional Requirements Documents (FRDs) - These documents are provided by the United States Navy and are considered the governing requirements documents.

They will be used as the basic customer requirement input documents for the electronic requirement traceability database that will be used for the engineering development process.

• System Subsystem Specification (SSS) - This developed requirements document is derived from the USCG ORD, US Navy FRDs, and customer input. It incorporates all threshold requirements from the provided USCG documents which are implemented into the A1U solution.

• Hardware Interface Design Document (HIDD) - The HIDD describes all the internal and external digital interfaces for the system.

• Integrated Master Test Plan (ITMP) - This document describes the test strategy and tests to be completed for the program.

• Requirements Verification Matrix (RVM) - This report is created following the SIT and Software Test Description (STD) tests. The RVM provides a summary of the completed testing and includes pass/fail status of all tests.

• Software Requirement Specification (SRS) / Subsystem Requirements Document (SRD)-These documents describe the software requirements / subsystem requirements of each individual CSCI.

• Software Design Document (SDD) - These documents describe the design of each individual CSCI.

• Software Test Description (STD) - These test documents contain the CSCI-level test procedure to be completed at FQT.

Figure 1

2.0 Applicable Documents

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

2.1 U.S. Government Documents

Document Number Date

Document Title

CNO FRD for RNP

RNAV REV A

17 April 2006

CNO Functional Requirements Document for Required Navigation Performance Area Navigation

MIL-HDBK-472 Maintainability Prediction MIL-HDBK-470A Designing and Developing Maintainable Systems, Volume I and II

MIL-E-5400T

9 May 1996

Electronic Equipment, Airborne, General Specification For (Amendment 2)

MIL-HDBK-454B

15 April 2007

Department of Defense Handbook General Guidelines for Electronic Equipment

MIL-L-85762A

26 August 1988

Lighting, Aircraft, Interior, Night Vision Imaging System (NVIS) Compatible

MIL-STD-464A

19 December 2002

Electromagnetic Environmental Effects Requirements For Systems

MIL-STD-704A

09 August 1967

Electric Power, Aircraft, Characteristics and Utilization Of

MIL-HDBK-704A Guide for assuring MIL-STD-704 compatibility.

MIL_STD-1787C Aircraft Display Symbology

MIL-STD-810G

30 October 2008

Department of Defense Test Standard for Environmental Engineering Considerations and Laboratory Tests

MIL-STD-882D

10 February 2000

Standard Practice For System Safety

MIL-STD-1472F

23 August 1999

Department of Defense Design Criteria Standard: Human Engineering

MIL-STD-1553B

15 January 1996

Digital Time Division Command/Response Multiplex Data Bus (Notice 4)

MIL-STD-2073-1D

10 May 2002

Standard Practice For Military Packaging (Notice 1)

MIL-C-14806A Coating, Reflection Reducing, for Instrument Cover Glasses and Lighting Wedges

JSSG-2000A

8 Oct 2002

Joint Service Specification Guide Air System

MIL-HDBK-217F

28 February 1995

Reliability Prediction of Electronic Equipment

MIL-PRF-49506

18 January 2005

Logistics Management Information

MIL-STD-203G

28 Dec 1973

Aircrew Station Controls and Display: Location, Arrangement and Actuation of, for Fixed Wing Aircraft

MIL-STD-411F

10 Mar 1997

Criteria Standard Aircrew Station Alerting Systems

MIL-STD-461F

10 Dec 2007

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

NAVAIRINST

5234.5 20 July 2005

Naval Air Systems Command Metrics for Software Intensive Programs

NAVAIRINST

4355.19C 10 April 2006

Naval Air Systems Command Systems Engineering Technical Review Process

2.2 Non-Government Documents

Document Number Date

Document Title

ARINC 424-15

11 February 2000

Navigation Systems Database

ARINC 429-P1-P17

September 1995

MK 33 Digital Information Transfer System (DITS) Part 1 Functional Description, Electrical Interface, Label Assignments and Word Formats

RTCA DO-160F

6 December 2007

Environmental Conditions and Test Procedures For Airborne Equipment\

RTCA DO-242A

25 June 2002

Minimum Aviation System Performance Standards for Automatic Dependent Surveillance Broadcast (ADS-B)

RTCA DO-185B

19 June 2008

Minimum Operational Performance Standards for Traffic Alert and Collision Avoidance System II (TCAS II)

3.0 System Requirements

This section discusses the EFDS system requirements. The EFDS as part of the FMS SHALL not degrade any existing capabilities, functions, or operations unless specifically described in this specification or approved by the U.S. Coast Guard. The EFDS should ensure redundancy exists for all integrated components and/or systems.

The EFDS will perform the following functions:

• Flight Instrument Display and Data Management

• Situation Awareness Management

The existing architecture is defined as that installed and operating in Block 1500 and 1700 series aircraft.

The architecture depiction in Appendix A of the FMS integrated into the HC-130H aircraft will be referenced by this specification.

The EFDS, as part of the A1U, architecture and system SHALL meet the applicable requirements of the CNO FRD for RNP RNAV.

The information contained in the following paragraphs is considered part of, addition, and /or delta to the required functional data of the specified CNO FRDs.

3.1 System Management

3.1.1 BIT

The EFDS SHALL have self contained Built In Test (BIT) capability.

All components of the EFDS SHALL include a Power-Up BIT, Continuous BIT (CBIT), and Initiated BIT (IBIT) to accomplish failure detection and isolation. Non-volatile memory should be used to store a history of BIT failures and should be readable at Organizational/Depot Level.

The EFDS SHALL be capable of storing a minimum of 100 BIT failures in history.

The EFDS Line Replaceable Units (LRUs) SHALL automatically detect no less than 95% of all faults in each component with a false alarm rate not to exceed 2% of all BIT reported anomalies.

The EFDS SHALL not affect normal system operation of the any system in the case of BIT component failure within BIT itself.

The EFDS SHALL provide BIT results in English language text.

3.1.1.1 Power-Up BIT

The EFDS SHALL detect any failures for any equipment upon power up.

The EFDS SHALL update the self-test and maintenance words, should any failure be detected upon power up.

The EFDS SHALL provide an indication of any detected failures during Power-Up BIT.

3.1.1.2 CBIT

The EFDS SHALL provide CBIT for all bus/discrete reported LRUs capable of providing CBIT status.

The EFDS SHALL provide a CBIT of all specified equipment, except during IBIT.

The EFDS SHALL provide an indication of an individual CBIT failure and automatically refresh current CBIT regardless of state change every two minutes.

The EFDS SHALL be capable of CBIT diagnostics operating preflight, post flight, and in-flight on a noninterference basis with crew selected mission or avionics functions.

The EFDS SHALL isolate failures to a specific LRU element.

3.1.1.3 IBIT

The EFDS SHALL provide IBIT for all bus/discrete reported LRUs capable of providing IBIT status.

The EFDS IBIT SHALL provide stimulation or operation to detect system failures more thoroughly than CBIT and to unambiguously isolate those failures without the use of external test equipment.

The EFDS SHALL not exceed three minutes reporting time of IBIT faults to operator.

Note: IBIT will generally be initiated before and after flight to check operational status and as a maintenance check.

The EFDS IBIT SHALL detect 95 percent of EFDS failures.

The EFDS IBIT SHALL be disabled in flight.

The EFDS SHALL display integrated flat panel display internal failures.

3.2 Flight Instrument Display and Data Management

The EFDS installation for the pilot and co-pilot consists of one Primary Display (PD) and one Secondary Display (SD) for each crew member as illustrated in Figure 2. Numbered accordingly in normal flight:

• #1 – Pilot Primary Display

• #2 – Pilot Secondary Display

• #3 – Co-Pilot Secondary Display

• #4 – Co-Pilot Primary Display

Figure 2

The EFDS SHALL, at a minimum, provide:

• Redundancy for each input/output signal to the maximum extent practical

• Reversionary Manual/Auto capability from same side PD to SD or pilot/copilot side switching (at a minimum, the Attitude Display Indicator (ADI) and Horizontal Situation Display (HSD) SHALL be present)

• Pilot and Co-Pilot selection of navigation source selects Pilot’s and Co-Pilot’s APS-85 navigation source.

• For primary and secondary flight displays, there SHALL be a 6.0 inch x 8.0 inch active display area.

• For primary and secondary flight displays, the overall dimensions of the display cannot interfere with aircraft structure or aircraft yoke movement, per NAVAIR HMI design layout included in Appendix B.

• Placement of the displays SHALL be no more than one-half (1/2) inch away from positions indicated in Appendix B.

• Weight of each individual display SHALL be less than 25lbs.

• Depth and volumetric constraints forward, side, and aft of the instrument panel SHALL be considered in the overall design of the EFDS.

The EFDS SHALL meet the requirements in MIL-STD-1472, MIL-STD-1787C, MIL-L-85762A.

The EFDS subsystems SHALL integrate with existing aircraft resources in order to produce all flight display formats and support modes of operation available.

The Advisory, Caution, and Warning System (ACAWS) SHALL be a standalone unit driven directly from the peripheral aircraft equipment and/or DCUs.

The EFDS SHALL support independent selection of all flight, navigation, sensor, and mission information on the pilot’s and co-pilot’s digital displays.

The EFDS SHALL provide for the receipt and display of available MX-20TS mission system target position information.

3.3 Primary Display

The PD format SHALL display at a minimum:

• Attitude Director Indicator (ADI) with aircraft symbology

• Flight Guidance, Horizontal and Vertical Deviations and/or Flight Director cues

• Air Speed Indication/Selection/Alerting

• Barometric Altitude Indication/Selection/Alerting

• Advisories Cautions, and Warnings to include:

o EGPWS o Windshear o IFF

The PD SHALL display (Horizontal Situation Indicator (HSI), HSI ARC, or ARC Map format as appropriate) HSD information, at a minimum:

• HSI Base format

• ARC format

• ARC Map format

• Navigation Reference Data

• Advisories, Cautions, and Warnings

• Selected navigation source

• Own ship position

3.3.1 Attitude Direction Indicator (ADI) Data

The ADI SHALL, at a minimum:

• Display a precise pitch scale merging to a qualitative scale at greater pitch attitudes

• Display a precise bank angle pointer merging to a qualitative scale at greater bank angles

• Display positive and negative chevron recovery symbology

• Display the computed dynamic (pitch and roll) Flight Director (F/D) steering command chevron

• Display the turn/slip indicator

• Display and flash unique marker beacon symbol

• Display lateral/vertical guidance of NAVAID and FMS information

• Display coordinated lateral scaling between ADI and HSD

The ADI SHALL include an “expanded horizon” extending full width of the Primary Display upper section.

The ADI SHALL have a “rising runway” symbol that:

• Displays on the lower portion of the ADI

• Serves as a lateral deviation pointer for valid primary navigation sources

• Displays when radar altitude is at or below 2500 feet above ground level (AGL)

• Rises toward airplane symbol when below 200 feet AGL, reaching maximum height at zero feet AGL

The ADI flight guidance SHALL remove vertical guidance when on back course.

3.3.2

3.3.3

Barometric Altimeter The barometric altimeter SHALL:

• Display in a tape format to the right of the ADI.

• Move down as the altitude increases and up as the altitude decreases

• Display feet as default and meters when selected

• Display negative altitudes

• Display current barometric altitude setting

• Numerically display the current altitude as computed by the Air Data Modules (ADM)

• Display minimum altitude alert o Display as only half when selected minimum altitude is not in view (off scale) and become default size and the bar SHALL move with the tape.

o Become yellow when the airplane descends below the selected BARO minimum altitude.

o Reset when altitude is 50 feet above selected barometric minimum altitude alert

Altitude alerter SHALL:

• Provide and activate a visual cue and an audible warning when the aircraft is at 1,000 and 200 feet of the preset altitude, or reactivate when departing the preset altitude by plus/minus 200 feet, and:

o Deactivate the aural cue after approximately two seconds o Have visual cue remain active until aircraft crosses within 200 feet of the preset altitude, at which time is removed

Manual altitude input for the altitude alerter SHALL:

• Be numerically displayed near the altitude indicator

• Indicate when altitude selection is in meters

• Mark on the altitude tape the corresponding selected altitude value

• Display half the marker when the selected altitude is off scale

The PD SHALL display altimeter setting (corrected barometric pressure), in either inches (IN) or hectoPascals (HPA) as selected.

Radar Altimeter (ALT- 4000) Radar Altimeter (RADALT) SHALL, at a minimum:

• Display numerically within the lower portion of the ADI when at and below 2500 feet AGL

• Display selected radar altitude o Display as yellow when below selected radar altitude Reset when above selected radar altitude

3.3.4

3.3.5

3.3.6

3.3.7

3.3.8

Airspeed Indicator The airspeed indicator SHALL, at a minimum:

• Be displayed in a tape format to the left of the ADI.

• Display numerically the current indicated airspeed as computed by the ADM

• Display target/command airspeed

• Display airspeed markers as either direct ADM data or as crew selected

• Display takeoff airspeed references

• Display maximum recommended airspeed

• Display approach airspeed references

• Display airspeed tape as moving down as aircraft speed increases or up as speed decreases

• Display speed trend vector indicating predicted airspeed within the next 10 seconds

Vertical Speed Indicator (VSI) The VSI SHALL, at a minimum:

• Display as a vertical indicator to the right of the Altitude Indicator

• Scale from zero to plus/minus 4000 fpm in 100 fpm increments from zero to 1000 fpm, 500 fpm increments from 1000 to 4000 fpm and numerically display greater than 4000 fpm

• Include a movable marker with affiliated colored tracker

• Display TCAS RA (resolution advisories) guidance commands

Heading The PD SHALL:

• Display a compass card

• Numerically display the current heading

• Display a selected heading marker

• Numerically display the heading marker selection

• Indicate heading reference source (magnetic or true)

• Display a track marker indicating aircraft track

Bearing Pointer The PD SHALL be capable of displaying two independent Bearing Pointers (BP).

The PD SHALL display bearing information from the following:

• DF-430

• ADF

• TACAN 1 and 2

• VOR 1 and 2

• FMS 1 and 2

The PD display of Bearing Pointers SHALL:

• Allow the operator to distinguish needle location to within one degree

• Provide means of determining location of needle head when it is not in view

• Navigation source identifier to include frequency/channel

Course Deviation Indicator (CDI) The PD SHALL, at a minimum:

• Display Course Deviation Indicator (CDI) for VOR, TACAN, FMS data in HSI, ARC Map, and

HSI ARC formats

• Numerically display course/desired track and label as applicable

• Display a To/From pointer

• Display a course arrow corresponding to selected course/desired track

• Display Back Course data using “front course sensing”

• Display RNP value associated with CDI full scale deflection for FMS data o Provide indication when RNP is manually entered o Provide indication when manual entry exceeds base RNP value

3.3.9

3.3.10

3.3.11

3.3.12

Receiver Autonomous Integrity Monitor (RAIM) The PD SHALL display:

• RAIM Unavailable, yellow “RAIM”

• RAIM WARNING, red “RAIM”

Distance To Go The PD SHALL be capable of simultaneously displaying, at a minimum:

• TACAN DME

• FMS distance to go to active waypoint

Temperature, Speed, and Wind The PD SHALL display:

• True Air Temperature (TAT)

• Static Air Temperature (SAT)

• Ground Speed (GS)

• True Airspeed (TAS)

• Wind angle and velocity (numerically)

• Wind vector arrow

Flight Plans & Waypoint Representation The PD SHALL be capable of displaying, at a minimum:

• Active flight plan

• Secondary flight plan

• Modified active flight plan

• Offset flight plan

• Modified offset flight plan

The PD SHALL display origin and/or destination airport with extended runway centerline if available.

The PD SHALL display waypoint data as follows:

• Waypoint symbol with affiliated annunciations for waypoint arrival

• Flashing waypoint upon waypoint approach

• Display waypoint identifier (up to 5 characters) and waypoint descriptor as appropriate (Initial Approach Fix, Final Approach Fix, Missed Approach Point)

• Unique symbology for fly-over, fly-by, final approach fix, missed approach waypoints

• Display altitude and altitude constraints if available

• Estimated Time of Arrival (ETA)

• Distance To Go

3.3.13

3.3.14

3.3.15

3.3.16

Vertical Flight Representation The PD SHALL display indications of vertical transitions using unique symbology and labels, if available:

• Top of Descent

• Bottom of Descent

• Top of Climb

• Bottom of Climb

Range Scaling The PD SHALL display range rings as follows:

• With exception of the outer ring, annotate range in nautical miles

Patterns/Procedures The PD SHALL at a minimum:

• Display the following patterns/procedures as transmitted from the FMS:

o Circle Pattern o Racetrack o Figure Eight o Closed Random Pattern (up to 9 waypoints) o Ladder Pattern o Sector Pattern o Expanding Square Pattern o Impromptu Patterns o Tactical Approach

• Attach the affiliated pattern using unique symbology to the waypoint

• Display the expanded pattern when the waypoint is the active waypoint

Overlays The PD SHALL, at a minimum, upon selection, display:

• Airports

• NAVAIDs using unique symbology

• EGPWS data

• Weather radar data (to include thunderstorms, air turbulence, and ground clutter)

• ETCAS data

• ADS-B data

• EPIRB location (with and without a moving map)

• Boundaries as provided by the CDU 7000 o Military Operating Areas o Special Use Airspace o User Defined Boundaries

Background symbology SHALL conform to DoD MIL-STD-1787C symbols.

3.4 Secondary Display Management

The SD SHALL, at a minimum, receive input and display:

• ARC format

• Own-Ship Position civil E-Chart with moving map overlay capability

• Digital Map Data

• Digital Video/Imagery

• Cautions, Warnings and Advisories

The SD SHALL display all navigation reference data, information, and overlays, as presented on the PD lower section.

The SDs SHALL provide an area for displaying free text information.

The SD SHALL be capable of displaying at least six communication radio frequency/identification fields, invalid/missing data dashes, and net number identification.

3.5 Electronic IFR Charts and Digital Moving Maps

The Situational Awareness (SA) display using digital maps SHALL consist of an underlay of chart, map, or images, and various data overlays.

The SA SHALL be capable of being displayed at both the pilot and co-pilot stations. All positions that have the SA selected for display will have the same rendering.

The position with control SHALL be capable of choosing which chart, map or image underlay, and which overlay(s) to display.

Overlays SHALL include:

• Flight plan route(s) (including SID, STAR, Approach, SAR pattern, etc.)

• Aeronautical information (airports, navaids, waypoints, special use airspace, etc.)

• eCHUM and/or manual CHUM

• Weather information (weather radar, saved weather picture, FIS-B, etc.)

• TCAS

• ADS-B,

• Altitude shading (DTED),

• User Boundaries

• User Points

• Track history

The position with control SHALL be capable of centering the SA display on own ship, in front of own ship on track, or offset to the cursor position. The EFDS SHALL support user defined waypoints by sending the cursor position to the CDU-7000. The position with control SHALL be capable of choosing the range scale.

3.5.1

3.5.2

Instrument Flight Rules (IFR) Electronic Charts

The EFDS SHALL integrate IFR Electronic Charts into the system for situational awareness. The EFDS SHALL receive own-ship position from the FMS and overlay it on the display. The EFDS SHALL provide graphical depiction of aeronautical charts including:

• Enroute charts

• Approach charts

• Departure procedures (SIDs)

• Arrival procedures (STARs)

• Airport Diagrams

The EFDS SHALL provide the capability to pan and zoom the display and provide an indication of off-screen own-ship position.

Digital Maps

The EFDS SHALL be equipped with a digital moving map system capable of storing and displaying a geographic area of 1,000,000 square miles using selected digital charts compatible with Digital Aeronautical Flight Information File (DAFIF) or Jeppesen databases.

The Digital Moving Map provides the aircrew with improved situational awareness and navigation.

The EFDS SHALL provide the capability to pan and zoom the display.

The EFDS SHALL provide the capability to display own-ship navigation and an indication of the location of the off screen own-ship position.

The EFDS shall support the selection of “North Up” and “Track Up” display options.

The EFDS SHALL support and display military map products, including all varieties of:

• Compressed ARC Digitized Raster Graphic (CADRG), to include:

o General Navigation Chart (GNC) o Jet Navigation Chart (JNC) o Operational Navigation Chart (ONC) o Tactical Pilotage Aeronautical Chart (TPC) o Joint Operations Graphic (JOG) aeronautical chart o Topographical Line Map (TLM) o City Graphics (CG)

• Digital Terrain Elevation Data (DTED)

• Controlled Image Base (CIB)

• Frame

• Raster Nautical Charts (Objective) {no cost both dollars and schedule}

• GeoCHIPS

3.6 ADS-B (GDL-90)

The A1U will support the integration of ADS-B. The GDL-90 transmits, receives and decodes ADS-B messages. The EFDS SHALL support the display of:

• TIS-B traffic

• TRF Services

• FIS-B Data to include:

o METAR (Generic Textual Data Product) o NEXRAD (Graphic product) o TAF (Generic Textual Data Product) o Other services as made available by the FIS-B product registry (Provisional – not a requirement)

3.7 Cursor Control Devices (CCD)

The EFDS SHALL provide interfaces to support cursor control devices for the pilot and co-pilot to the enable control of the IFR Chart and the Digital Map systems. The A1U will provide a pilot cursor control device and a co-pilot cursor control device.

3.8 Miscompare

The EFDS SHALL display miscompare annunciations, at a minimum, for the following:

• Pitch

• Roll

• Heading

• Indicated Airspeed

• Pressure Altitude

• Radar Altitude

• Flight Director Pitch and Roll Commands

3.9 Data Integrity

Primary and Secondary Display information must be dashed out, or have annunciation for invalid, missing or failure data which is received.

The Primary and Secondary Displays SHALL display, at a minimum, for:

• Reversionary switch mode o Attitude and heading o DCU o ADM

• Loss of control panel communication

• Operator activation of autopilot through flight director

• Deactivation of autopilot from flight director

• Receiver Autonomous Integrity Monitoring(RAIM)

• Status of Flight Director Modes and Functions

• TCAS status messages

• FMS messages

• RNP Steering Source Status

3.10 Advisory, Caution, and Warning System (ACAWS)

The ACAWS SHALL receive inputs from peripheral aircraft equipment.

The ACAWS SHALL be NVIS compatible and situated as depicted in NAVAIR HMI layout and shown in Appendix B.

The ACAWS SHALL at a minimum display the following:

• Advisories NO ICE – The No Ice light will illuminate during any phase of operation.

AIR DEF DOOR - The Air Deflector Doors Open Light will illuminate during any phase of operation.

• Cautions SEC FUEL - 1,2,3, & 4 Secondary Fuel Pump Pressure Lights are a NORMAL indication during engine starts. The MASTER CAUTION SHALL illuminate once weight is off the wheels during this condition.

GEN OUT - 1,2,3, & 4 Generator Out Lights are a NORMAL indication on the ground.