SEATTLE AIRCRAFT EVALUATION GROUP

 

OPERATIONAL SUITABILITY REPORT

 

Revision 3

 

 

Jeppesen

 

Electronic Flight Bag (EFB)

Application Software Ver 1.0, 1.1, 1.5, and 2.0

 

 

 

 

 

 

 

 

 

 

 

 

 

Report

Approved:

s/Michael F. Garrett

 

DATE: 

 

12/08/2008

Michael F. Garrett

Seattle Aircraft Evaluation Group

 

 

Federal Aviation Administration

Seattle Aircraft Evaluation Group (SEA AEG)

1601 Lind Ave NW

Renton , Washington 98055

Telephone:  (425) 917-6600

FAX:  (425) 917-6638


Table of Contents

 

1.

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Appendix 1

Appendix 2                                                                                                          9

Appendix 3                                                                                                        10

 

 

 

 


Highlights of Change

 

2. EFB Description

 

 

2.3 Configuration Files

 

 

2.3.4  The following configuration files were validated Version 2.0

 

Replace Terminal Charts application part number JEP34-CH1P-0001 with part number JEP37-CH1P-0002. New part number fixes an anomaly where, under certain conditions, the application would present a superseded version of a chart, rather than the most current version.

 

 

2.5 Applications

 

 

2.5.2 Type B Applications

 

 

2.5.2.1 “Type B” applica-tions (and version for each applica-tion) evaluated and found acceptable for this report.

Replace Terminal Charts application part number JEP34-CH1P-0001 with part number JEP37-CH1P-0002. New part number fixes an anomaly where, under certain conditions, the application would present a superseded version of a chart, rather than the most current version.

 

 


1.

1.1                The purpose of this report is to establish the Operational Suitability of the Jeppesen Application Manager Electronic Flight Bag software package. This report does not approve the operational use of this software. Operators must apply to their assigned operations authority for applicable operational use authorization.

 

1.1.1              Three Operations Aviation Safety Inspectors from the Seattle Aircraft Evaluation Group (AEG) performed the original Operational Suitability Evaluation in accordance with AC 120-76A of Jeppesen EFB ™ Version 1.0.

 

1.1.2              Two Operations Aviation Safety Inspectors from the SEA AEG performed the Operational Suitability Evaluation on Version 1.1 using the checklist contained in Appendix 3 to this report. All functions of the software are virtually identical to Version 1.0 with the addition of the ARINC/Jeppesen DocViewer.

 

1.1.3              Two Operations Aviation Safety Inspectors from the SEA AEG performed the Operational Suitability Evaluation on Jeppesen EFB ™ Ver 1.5. This version added Jeppesen’s PDF ChartViewer with rotation functionality.

 

1.1.4              Two Aviation Safety Inspectors, one operations and one avionics, from the AEA AEG performed the Operational Suitability Evaluation on Jeppesen EFB ™ Ver 2.0. This version added;

 

·          Ability to transfer individual charts and chart clips from one position to the other,

·          Overlap effectivity periods of databases,

·          Enhanced Night-Mode colors,

·          Terminal Charts simplified flow,

·          ARINC 665 Dataloading,

·          Enhanced to use Jeppesen Data Server (JDS) v 2.0.0.3 as well as the legacy JIT database format.

1.2                The Jeppesen Operational Suitability Report, Revision 2, dated 1/9/2008, is rescinded.  

1.3                This report addresses Jeppesen Application Manager Electronic Flight Bag (EFB) Version 1.0, changes and upgrades available in Jeppesen Application Manager Electronic Flight Bag Versions 1.1 and 1.5, and upgrades available in Version 2.0 for Class 1 or Class 2 Electronic Flight Bag operations under applicable 14 CFR.

1.4                Provisions of this report are consistent with the guidance defined in FAA Advisory Circular 120-76A and assume that appropriate airworthiness certification for installation of the EFB hardware is accomplished.  The following information related to operational suitability is included:

o              A general description of the EFB application evaluated for this report, including:

§        A list of major configuration files within the EFB application

§        The applicable operating system(s)

§        A list of the applications evaluated.

o              Typical acceptable procedures for EFB use during all phases of flight

o              A revision process procedure/method that ensures appropriate database accuracy and currency

o              Specifications for training and typical acceptable training course description

o              Specifications for Checking including those checks that must be administered by FAA or operators

o              Specifications for Currency

o              Changes to the Operating System

o              Configuration Control – including procedures govern ing the distribution of updates to the EFB configuration .

o              Compliance Checklist

o              Specifications for Devices and Simulators

o              List of documents to meet the requirements of AC120-76A for operational use and continued airworthiness. (Appendix 1)

o              List regulatory compliance status (compliance checklist) for pertinent parts of 14 CFR (Appendix 2)

2.                            EFB Description

The Electronic Flight Bag (EFB) application provides electronic flight deck displays that may be used to depict Jeppesen airport diagrams, departure, arrival, and approach charts traditionally provided in paper form.  The application is applicable to either a Class 1 or Class 2 EFB system. Charts, as well as Text oriented material, are provided for departure, arrival, and approach phases.

 

The ARINC/Jeppesen DocViewer provides the capability to read the textual contents that accompany Jeppesen charts and provide information as to their content and format. Furthermore, Jeppesen PDF Chart Viewer enhances the ability for placing and using other documents (e.g. Flight Crew Operations Manual, Minimum Equipment List, etc.) in an Electronic Flight Bag.

 

span style='font-size:11.0pt;font-weight:normal; font-style:normal'

This software is manufactured by Jeppesen.

span style='font-size:11.0pt;font-weight:normal; font-style:normal'

The application is suitable for use on all models and classes of electronic flight bag hardware operating under MicroSoft™.

           

span style='font-size:11.0pt;font-weight:normal; font-style:normal' nfiguration Files

 

2.3.1              The following configuration files were validated for Version 1.0:

 

PART NUMBER

DESCRIPTION

JEPT1-SMCS-0008

S MC Supplier Configuration file

JEPT1-SMCC-0002

SMC User Configuration file

JEPT1-DLCS-0002

RCDL Supplier Configuration file

JEPT1-DLCC-0004

RCDL User Configuration file

JEPT1-ADCC-0005

EFB Application Configuration file

JEPT1-ADCS-0002

ADC Supplier Configuration file

JEPT1-ADCS-0002

SMC Supplier Configuration file

JEPT1-SMCC-0002

SMC User Configuration file

JEPT1-DLCS-0002

RCDL Supplier Configuration file

JEPT-DLCC-0004

RCDL User Configuration file

JEPT1-CHCS-0002

Terminal Charts Supplier Configuration file

 

2.3.2              The following configuration files were validated Version 1.1:

 

PART NUMBER

DESCRIPTION

JEPT1-ADCP-0001

ADC Application

JEPT1-ADCS-0003

ADC Supplier Config

JEPT1-SMCP-0001

SMC Application

JEPT1-SMCS-0009

SMC Supplier Config


JEPT1-DTLP-A001

EFB Dataloader Application

JEPT1-DLCS-0003

EFB Dataloader Supplier Config

JEPT1-DLCR-0001

EFB Dataloader Restart

V1.1

EFB Stand Alone Dataloader Application – Installed through EFB Integrated Installer (therefore, no unique part number)

V1.1

EFB Stand Alone Dataloader Supplier – Installed through EFB Integrated Installer (therefore, no unique part number)


JEPT1-C0MP-0001

EFB Common (Wrappers, EFB API, and JIT-eDocs API)

JEPT1-CHTP-0015

Terminal Charts Application

JEPT1-CHCS-0003

Terminal Charts JIT Supplier Config

JEPT1-CHCS-0004

Terminal Charts JID Supplier Config


JEPT1-DMCP-0001

Data Management Common

JEPT1-JDXP-0001

JDX-CDM (Client Data Manager) Application

JEPT1-JUMP-0001

JUM (Jeppesen Update Manager) Application

JEPT1-JUMS-0001

JUM (Jeppesen Update Manager) Supplier Config

JEPT1-RDLP-0001

Remote Client Data Loader (RCDL) Application

JEPT1-RDLS-0001

Remote Client Data Loader (RCDL) Supplier Config


JEPT1-D0CS-0001

JIT-eDocs Supplier Config

JEPT1-DDMP-0001

DDM Client Application

JEPT1-DJMP-0001

DJIM Application

JEPT1-JDSP-0001

JDS API Application

 

 

2.3.3              The following configuration files were validated Version 1.5:

 

 

PART NUMBER

DESCRIPTION

JEPT1-ADCP-0002

ADC Application

JEPT1-ADCS-0003

ADC Supplier Config

JEPT1-ADCC-0030

ADC Customer Config

JEPT1-SMCP-0002

SMC Application

JEPT1-SMCS-0010

SMC Supplier Config

JEPT1-DTLP-A002

EFB Dataloader Application

JEPT1-DLCS-0003

EFB Dataloader Supplier Config


JEPT1-DLCR-0001

EFB Dataloader Restart

 

EFB Stand Alone Dataloader Application – Installed through EFB Integrated Installer

 

EFB Stand Alone Dataloader Supplier – Installed through EFB Integrated Installer

JEPT1-C0MP-0002

EFB Common (Wrappers, EFB API, and JIT-eDocs API)

JEPT1-CHTP-0016

Terminal Charts Application

JEPT1-CHCS-0003

Terminal Charts JIT Supplier Config

JEPT1-CHCS-0004

Terminal Charts JID Supplier Config

JEPT1-DMCP-0002

Data Management Common

JEPT1-JDXP-0001

JDX-CDM (Client Data Manager) Application

JEPT1-JUMP-0002

JUM (Jeppesen Update Manager) Application

JEPT1-JUMS-0001

JUM (Jeppesen Update Manager) Supplier Config

JEPT1-RDLP-0002

Remote Client Data Loader (RCDL) Application

JEPT1-RDLS-0001

Remote Client Data Loader (RCDL) Supplier Config

JEPT1-D0CS-0001

JIT-eDocs Supplier Config

JEPT1-DDMP-0001

DDM Client Application

JEPT1-DJMP-0001

DJIM Application

JEPT1-CVPB-0007

PDF Chart Viewer

 

2.3.4              The following configuration files were validated Version 2.0

 

PART NUMBER                

DESCRIPTION

JEP3A-AD1P-0001

ADC Application

JEP39-AD1S-0001

ADC Supplier Config

JEP21-SM1P-0001

SMC Application

JEP22-SM1S-0001

SMC Supplier Config

JEP2F-DT1P-0001

EFB Dataloader Application

JEP34-DL1S-0001

EFB Dataloader Supplier Config [DTL Supplier Config]

JEP35-DL1R-0001

EFB Dataloader Restart [DTL Restart Config]

v2.0.0

EFB Stand Alone Dataloader Application - Installed through EFB Integrated Installer

v2.0.0

EFB Stand Alone Dataloader Supplier - Installed through EFB Integrated Installer

JEP4C-C01P-0001

EFB Common (Wrappers, EFB API, and JIT-eDocs API)

JEP37-CH1P-0002

Terminal Charts Application

JEP34-CH1S-0002

Terminal Charts JIT Supplier Config

JEP37-CH1S-0001

Terminal Charts JID Supplier Config

JEP36-DM1P-0001

Data Management Common

JEP2D-JX1P-0001

JDX-CDM (Client Data Manager) Application

JEP20-JU1P-0001

JUM (Jeppesen Update Manager) Application

JEP23-JU1S-0001

JUM (Jeppesen Update Manager) Supplier Config

JEP29-RD1P-0001

Remote Client Data Loader (RCDL) Application

JEP2A-RD1S-0001

Remote Client Data Loader (RCDL) Supplier Config

JEP4E-DJMP-0001

CDAJ Application

JEP4D-DJMS-0001

CDAJ Supplier Config

JEP31-JD1P-0001

JDS API Application

 

 

span style='font-size:11.0pt;font-weight:normal;font-style:normal'

Jeppesen’s EFB application was validated using MicroSoft™ Windows XP® and Windows 2000® operating system software.

 

2.4.1              Version 2.0 was evaluated for MicroSoft™ Windows XP® only. It’s capability to perform using other MicroSoft™ operating systems may be evaluated at the local FSDO/CMO level.

2.5                          Applications

The following applications supplied by Jeppesen have been validated and found suitable for use Class 2 EFB hardware.

2.5.1              “Type A” Applications

2.5.1.1  No “Type A” applications were evaluated under this FSB Report.

2.5.2              “Type B” Applications

2.5.2.1  “Type B” applications (and version for each application) evaluated and found acceptable for this report:

 


§          Terminal Charts Application – JEPT1-CHTP-001 4 & JEP37-CH1P-0002.

§          The evaluations by the SEA AEG substantiated that Jeppesen EFB ™ and Terminal Charts Application are Category B applications as defined in AC 120-76A. Also, that the above part numbers, see paragraph 2.3, are acceptable for Class 1 and Class 2 electronic flight bag installations without further application suitability evaluations by the FAA unless there are significant changes or revisions to the software.

§          ARINC/Jeppesen Integrated Solution software loadable program “DocViewer 6.7” was evaluated in conjunction with Application Manager 1.1.

§          PDFChartViewer

2.5.3              “Type C” Applications

2.5.3.1  No “Type C” applications were evaluated under this FSB Report.

 

3.

3.1       Not applicable to this report.

4.

4.1        Not applicable to this report.

5.

5.1       Descriptions of specific applications are contained in a “user guide” supplied by Jeppesen.

5.2                          There are no Non-Normal procedures associated with the EFB.

6.

6.1                          A data revision process developed by Jeppesen and available through a secure internet connection include the capability of using CD, Memory Stick, and/or an established secure data distribution network (i.e. WiFi, LAN, etc.). EFB Data will be loaded to hardware using procedures specified by the hardware manufacturer.  An operator’s data distribution system must include the procedures to protect the Jeppesen EFB from virus infection and other threats to the operating system. The system must also include a process by which it confirms to the operator delivery and installation of the updates.

7.

7.1                          Programs Crediting Previous EFB Experience.   Training programs for the EFB may take credit for previous EFB experience. For example, previous experience using a Class 1 or 2 charting application using similar software may be credited toward EFB training.  Principal Inspectors for operators initially introducing a new EFB system may approve programs consistent with programs previously approved for other operators.  For information regarding previously approved programs or programs crediting previous EFB experience, FAA Principal Inspectors for other operators may be consulted.

7.2                          Initial Training.   Pilots should be trained to proficiency using Level C training as defined in AC120-53 (i.e. classroom instruction, pictures, videotape, ground training devices, computer-based instruction and static aircraft training). Jeppesen’s Electronic

7.2.1              Flight Bag Computer Based Training .

7.2.1.1  Jeppesen Electronic Flight Bag Computer-based Training Class 1 & 2, Version 2.0 – July 2005 program evaluated by the AEG is an acceptable initial training method for EFB Version 1.0.

7.2.1.2  Jeppesen Electronic Flight Bag Computer-based Training v2.1, August 2006, is an acceptable initial training method for either EFB Version 1.0 or 1.1.

7.2.1.3  Jeppesen Electronic Flight Bag Computer-based Training v 3.0.1, August 2007 is an acceptable initial training method for either EFB Version 2.0.

 

 

 

7.2.2              Areas of Emphasis Operators must emphasize during initial line operating experience, the need to avoid fixation on the display during critical phases of flight, including taxi operations.

7.3                          Recurrent Training.   Recurrent training specific to Jeppesen’s application is not required provided the functions are used regularly in line operations. Operators should include use of the application as a component of simulator recurrent training consistent with other normal and non-normal procedures training.

8.

8.1                          Checking.   Pertinent knowledge and procedures for EFB use should be checked following initial training, annual proficiency checks (or LOFTS) and line checks.  This checking may be accomplished as an automated component of EFB computer-based training.

8.2                          Areas of emphasis.   The following areas of emphasis should be addressed during checks:

§          Proficiency with use of EFB application,

§          Proper outside visual scan without prolonged fixation on EFB operation, and

§          Proper use of the chart function.

§          Proper use of DocViewer, specifically acquiring correct document and searching for specific information

9.

9.1                          No unique currency provisions apply to the EFB.

10.

10.1                  Not applicable to this report.

11.

11.1                  Not applicable to this report.

12.

12.1                  Changes that allow the EFB to run under another operating system(s) other than those identified in paragraph 2.4 may require an additional Operational Suitability evaluation by the Seattle Aircraft Evaluation Group. The SEA AEG will determine, on a case by case basis, any need for an evaluation.

13.

13.1                  Significant changes to the configuration files (see paragraph 2.3) will require an additional Operational Suitability evaluation by the Seattle Aircraft Evaluation Group. Minor updates and “bug fixes” that alter the part numbers will require coordination through the SEA AEG; however, an Operational Suitability evaluation should not be necessary. The SEA AEG will determine, on a case by case basis, any need for an evaluation.

14.

14.1                  Not applicable to this report.

15.

15.1                  Compliance checklists (see Appendix 2) are provided as an aid to identify those specific rules or policies for which compliance has already been demonstrated to FAA.  The checklist also notes rules or policies which must be demonstrated to CHDOs by the operator.  Not all rules or policies or variants are necessarily listed or addressed.

16.

16.1                  Training Device. The EFB must be taught on a commercial over the shelf (COTS) computer or the actual hardware planned for use by flight crews.

16.2                  Simulator.  For “paperless” cockpit operations th e EFB must be available in simulators used for training unless aircraft training or supervised flight segments are included in the operator’s training program.


Appendix 1

 

The following documents have been reviewed and evaluated by the SEA AEG during the determination of this report.

 

Electronic Flight Bag Computer Based Training Class 1 & 2, Version 2.0 – July 2005

 

Class 1 and Class 2 Electronic Flight Bag User’s Guide, v2.0

 

Electronic Flight Bag Computer Based Training Class 1 & 2, Version 2.1 – August 2006

 

Electronic Flight Bag Computer Based Training Class 1 & 2, Version 3.0.1 – August 2007

 

Jeppesen EFB User’s Guide, Version 2.3, July 2007

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Appendix 2

Compliance Checklist

 

1. TITLE 14 OF THE CODE OF FEDERAL REGULATIONS (14 CFR).

 

The following regulations apply:

 

(1) Title 14 CFR §§ 91.103(b), 91.175(a), 91.503(a)(4).

 

(2) Title 14 CFR § 121 – 121.97(b), 121.97(c), 121.117(b), 121.117(c), 121.135(a), 121.135(b)(8)(i) / (iv) / (v).

 

(3) Title 14 CFR §§ 125 – 125.215(a)(4).

 

(4) Title 14 CFR §§ 135.23(r), 135.83(a)(4).

 

 

2. FEDERAL AVIATION ADMINISTRATION (FAA) ADVISORY CIRCULARS (AC), ORDERS, POLICY STATEMENTS, AND TECHNICAL STANDARD ORDERS (TSO).

        a. ACs (current version)

 

AC-120-76A

 

        b. FAA Orders, Policy Statements, and TSOs (current version).

 

Order 8400.10     CHDO

Order 8300.10     CHDO


b

Suitability Evaluation Checklist

 

1.1                        User Interface—General Design

a)        Is the organization of the software adequate?  YES

¾      For example, are the user interface, functions, function labels, and functional and navigation logic consistent with established user interface conventions for similar systems?

¾      Is any information expected by the crews missing or in a different place?

b)        Was the layout of information on the screens adequate?  YES

¾      For example, are similar or related fields, indicators, or controls located near each other? Are controls separated adequately if using the wrong one unintentionally has significant consequences?

c)        Are common actions and time-critical functions easy to access?  YES

1.2

a)        Are red and amber/yellow used?  NO If so, are they used appropriately? Red should be used only for warnings and amber/yellow only for cautions.

b)        If multiple colors are used, can they all be seen and distinguished under the various lighting conditions in which the EFB will be used?  YES

c)        If colors can be customized, are there procedures or built-in limits that prevent defining color schemes that conflict with flight deck color conventions?  N/A

1.3

a)        Are symbols (e.g., graphical objects on an electronic chart) and icons (graphical controls) clearly depicted on the screen in all viewing conditions? That is, are the symbols and icons legible?  YES

¾      Are their functions obvious?  YES

¾      Are the symbols and icons distinguishable from one another?  YES

b)        Are any icons confusing? NO  Is training necessary to ensure that the icons are understood?  YES  

¾      Does the initial EFB training adequately address icon meanings?  YES

¾      Does the system provide information that explains each icon's meaning (e.g., a text label)?  NO

c)        Are the EFB icons and symbols compatible with those depicted on paper equivalents?

1.4 s, Typeface, Size, Width, and Spacing

Is the text easily readable?  YES

¾      Do the characters stand out against the screen background?  YES

¾      Are upper case and italic text used infrequently?  YES

¾      Are the characters sufficiently large for normal viewing conditions?  YES

¾      Is information that will be used in low-visibility conditions (e.g., emergency checklists) presented in text that is especially large and easy to read?  N/A

¾      If the text is too small to be read easily, it is it easy to zoom in on it to make it legible?  YES

¾      Is the spacing between characters appropriate?  YES

¾      Is the vertical spacing between lines appropriate?  YES

1.5                              Multi-Tasking

d)        Is it easy to tell which application is currently open?  YES

e)        Can the pilot switch between applications easily?  YES

  f)        Is an extra acknowledgement required to open applications that are not flight related?  N/A

g)        Do all applications that are open at the same time function as intended on an individual basis?  N/A

1.6

a)        Does the system respond immediately to user inputs, e.g., by providing feedback? YES

¾      If processing is delayed, are busy indicators and/or progress indicators displayed?  YES

¾      Are the indicators clear and useful to the pilot?  YES

b)        Does the system processing ever slow down to the point where normal use is impaired?  NO

1.7

a)        For installed systems, do EFB alerts and reminders meet the requirements in the appropriate regulations (specifically §§ 23.1322 or 25.1322, as noted in FAA AC 120-76A, Par 10)?  N/A

b)        Is there an overall scheme for generating alerts/reminders (e.g., when will they appear, how are they prioritized)? N/A

¾      Is it adequate/appropriate?

c)        Are distracting flashing symbols avoided?  YES

d)        Are EFB messages inhibited during high workload phases of flight unless they pertain to the failure or degradation of the current EFB application?  N/A

1.8 Status

a)        Are partial or full failures of the EFB clearly indicated with a positive indication, not lack of an indication?  N/A

b)        Is the immediacy of the failure annunciation appropriate to the function that is lost or disabled? (For example, failures of low-criticality functions should not produce intrusive alerts.)  N/A

1.9 and Video

¾      Does the EFB support audio and/or video that are not associated with alerts, cautions or other critical system information?  NO

1.10

Is there a procedure for ensuring that data in use is approved for use in flight?  Currency of database checked by program at start up.

¾      Is the procedure for checking the EFB data approval consistent with standard operating procedures?  YES

¾      Can the crew request revision information from the EFB? Is the revision information presented clearly?  YES

¾      Are procedures in place so pilots know what to do if the database is not approved for use in flight?  N/A

1.11

Is access to related information supported?

¾      Are similar types of information accessed in the same way?  YES

¾      Is it easy to return to the place where the user started from?  YES

1.12  

a)        If the crew (i.e., end-user) can customize the appearance of the EFB (not related to panning/zooming), is it easy to reset all parameters to their default values?  Unable to customize this application.

¾      Is there a procedure or checklist item to ensure that crews clear all customized values?

¾      Does the EFB auto-reset to default values upon shutdown so that the system starts up in a predictable state?

¾      Does any customization have an adverse affect on items in Section 1.1, General Considerations? 

b)        Is the operator capable of customizing the appearance of the EFB? Unable to customize this application.  

¾    If yes, is the customization controlled through an administrative process ?

¾    Does any customization have an adverse affect on items in Section 1.1, General Considerations?