IMPLEMENTATION OF ELECTRONIC FLIGHT BAG (EFB) ON AIRBUS A330 FLEET November 2013

Author : QXO, QXA

TABLE OF CONTENT

What is EFB ?

EFB Project Overview EFB Architecture Overview EFB Technology Requirement EFB Time Frame

2

EFB Concept

An electronic information management device that helps flight crews perform flight management tasks easier and more efficient, in a less-paper environment

3

EFB COMPONENT EFB Hardware EFB Software (o/s- Windows, Linux, application) Communication System (during flight-Satellite, on ground- Bluetooth, USB, Wi Fi, 3G)

Class 1 • Portable in cockpit •Standalone • Stowed during critical phases (t/o & l/d)

Class 2 • Portable mounted in cockpit •Power supply from aircraft • All flight phases • requires airworthiness approval (mounting device)

Ref : FAA AC 120-76A & JAA (JAR OPS) 4

Class 3 • Display integrated into Cockpit/ FMS • Power supply from aircraft • All flight phases • requires full airworthiness approval

EFB S/W TYPE Class A : “…pre-composed, fixed presentations of data currently represented in paper format” Document/manuals, Technical/operations logs, Maintenance sign-offs, Aircraft performance data, (fixed, non-interactive for planning purposes), Captain’s reports and special reporting forms Class B : “…dynamic, interactive certification applications that can manipulate data and presentation” Master flight plan/updating, Weather (non-interactive), Performance and weight & balance calculations, Interactive electronic charts, Electronic checklists Class C : Require aircraft “…dynamic, interactive certification Charts with aircraft, own-position (in-flight), Checklists linked to aircraft systems, System monitoring, Controller-pilot data link Software

Class A

Class B

Class C

Hardware

Class 1

Class 2

Class 3

Operational approval

Ref : FAA AC 120-76A & JAA (JAR OPS) 5

Airworthiness approval

EFB PROJECT OVERVIEW

A330-200/300

Airbus e-Performance

e-AML

Providing digitalization of performance calculation

Providing digitalization of Aircraft Maintenance Log data

Jeppesen e-Charts

e-AFL Providing digitalization of post flight data (Aircraft Flight Log)

e-Viewer EFF Providing digitalization of briefing package and other flight docs. (Electronic Flight Folder)

6

Providing digitalization of all flight manuals and documents

Providing digitalization of navigation charts

SCOPE PENGADAAN EFB (ONE PACKAGE SOLUTION) HARDWARE

“EFB FOR AIRBUS FLEET (2013 – 2015)”

Certification : EFB Class 2, Windows Based Requirement : - Has been used by other airlines - Has STC - Connected to avionic (read data) - Connected to ACARS INTEGRATOR

Fleet A330

2013 2014 2015 0 17 9

1 Simulator & 4 back up (TOTAL 31 SET)

Requirement : - To integrate on-board EFB softwares - To integrate EFB ground systems - To integrate Garuda existing system with EFB system

SOFTWARE Requirement : - e-AFL (Aircraft Flight Log) - e-AML (Aircraft Maintenance Log) - e-Viewer - e-FF (Flight Folder) Note : e-Chart & e-Perf. Calculation procured separately 7

SCOPE OF EFB PROCUREMENT SITA scope as mention at slide nbr 3 : 1. EFB Hardware : Goodrich – UTAS 2. EFB Software : Flightman 3. EFB Ground System : hosting at SITA data center 4. EFB Integrator : using EFB integrator to Aircomserver Non-SITA scope : 1. e-chart : using Flight Deck Pro, provider Jeppesen -> Budget JKTOS. 2. e-Perf. Calculation : using Flysmart, Povider Airbus -> Budget JKTOS 3. IT Infrastructure and Manage Service : network, on premise server & storage, integration/ ESB development -> Budget JKTQX

8

EFB HIGH LEVEL ARCHITECTURE EFB System

3G, WiFi, USB

VHF, Satcom DL

Manual docs, chart

EFB Ground System Server

IOCS

xml

Garuda ESB

EFB Integrator

MRO FATA

Aircomserver

9

Jeppesen

Post Flight Data (on premise)

DB

EFB ARCHITECTURE 1

10

EFB ARCHITECTURE 2

11

EFB ARCHITECTURE 2 3rd Party App Jeppesen (Manual, Chart) • Chart • Manual • CRS

EFB Admin Dispatch er

OPS Eng

Jeppesen (Flight Planning Sys)

Flysmart (FSA, A/C Performance)

• Flight planning • Flight time • NOTAM • Weather

A/C perf data ACARS

EFB Integrator Function On demand EFB server access (Web server)

AIRCOMServ er (incl EFB Int module)

Flightman Ground System

A/C Mtc

EFB Platform

DSP (ACARS network)

ACARS message

Public/ Private network

EFB Ground Communication

A/C manual, PIREP, e-Logbook, MEL/CDL, other, etc

Garuda Back Office System DMS

12

NL/ Ops

MRO

Healthy Mgt Sys

NL/ Crew

PSS

Other back office

DB

• User credential • Journey log • Technical log • Crew data • etc

EFB ARCHITECTURE 3

13

NETWORK REQUIREMENTS

1. Connection between EFB ground system and Garuda user, such as OS, OF, OG and MQ/ GMF. 2. Internet (3G/ 4G), Wifi connection between Aircraft and EFB ground system. 3. Connection between EFB ground system server and Garuda System. Note : detail requirement will be verified after Project KickOff

14

ON PREMISE DATA CENTER REQUIREMENTS 1. Post flight data stores : journey log, tech log, others please specify 2. Frequency of data synchronization : daily (at midnight) 3. Method of data transfer : automatic, file (xml/ text) parse and store to database (SQL/ Oracle) 4. Capacity planning : initial data, data growth, retention period, etc 5. Archive period 6. Backup frequency : daily (after data synchronzation) 7. Data migration, if any Note : detail requirement will be verified after Project KickOff

15

INTEGRATION REQUIREMENTS 1. Integration with Garuda applications : a. NL/ Ops : Flight schedule, A/C rotation b. NL/ Crew : Crew schedule c. Jeppesen flight plan : flight folder (DR, flight plan, weather, NOTAM, etc) d. MRO : e-AML e. FATA : e-AFL 2. Using Garuda ESB as integration method Note : detail requirement will be verified after Project KickOff

16

TIME FRAME 2013 NO

2014

ACTIVITIES DES

1

Agreement

2

Pembentukan tim implementasi

3

Validasi DKUPPU

4

Project Kick Off, Workshop & Training

5

Ground system set up

6

Installation

JAN

SIM

17

7

Testing

8

Go Live

FEB

MAR

1ST A/C

APR

MEI

JUN

18