1

EFB POLICIES AND

PROCEDURES MANUAL
Copyright Statement:
This document is confidential and proprietary, and may not be reproduced, copied
(electronically, optically or otherwise), or transmitted in whole or in part without the express
prior written permission of the Accountable Manager of FlyZeJet. Users are to ensure that
current versions/issues/revisions or extracts are used or referred to when carrying out duties
and responsibilities.
 0.GENERAL

0.1 Introduction

This Manual provides the workflows associated with the administration of the FlyZeJet. This
Manual applies to FlyZeJet with Embraer application hosted on iPad. In this document, “manuals”
refer to FOM, GOM, SM, SQM, ACM and operator’s own manuals.

The manual also provides a lay out and guidance as to the usage and implementation of the
Electronic Flight Bag (EFB) system in use as well as the policies and procedures contained there to
and to ensure adherence to the prescribed usage and/or utilization thereof.

All aircraft are equipped with EFB devices and there recharging plug. These devices must be
maintained and charged properly.
Prior to start a flight, each pilot must ensure that both their EFB device are fully charged, and
their recharging device are operative. Where this is not possible, a minimum charge level compliant
with EFB SOP must be fulfilled.
Furthermore, the flight crew must check that both of their EFB are updated prior to reporting
time to ensure the latest manual revisions have been incorporated, Jeppesen Navigational charts are
current, and performance and W&B software are current.

2
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

0.2 Definitions

The Electronic Flight Bag (EFB): is an electronic logbook, a paperless

flight deck systems used by flight crews for an efficient and effective flight management.

HARDWARE:
Portable: EFB host platform, used on the flight deck, which is not part of the certified aircraft
configuration. It can be operated inside or outside the aircraft. A portable EFB hosts software
applications. It may be provided with aircraft power through a certified power source.
Installed: EFB host platform installed in the aircraft and considered as an aircraft part, covered,
thus by the aircraft airworthiness approval. An installed EFB is managed under the aircraft type design
configuration. In addition to hosting Type A and B applications, an installed EFB may host certified
applications, provided the EFB meets the certification requirements for hosting such applications,
including assurance that the non-certified software applications do not adversely affect the certified
application(s).

Applications Type A: EFB applications whose malfunction or misuse

would have no adverse effect on the safety of any flight operation including pre-composed,
fixed presentations of data currently presented in paper format.

Applications Type B: EFB applications whose malfunction or misuse is

classified as minor failure condition or below and which neither replaces nor duplicates any
system or functionality required by airworthiness regulations or operational rules.

Applications miscellaneous: software applications that are non-EFB

applications, supporting function(s) not directly related to operations conducted by the flight
crew of the aircraft. Examples of miscellaneous software applications are web browser, email
client, picture management application, or even applications used by ground crews (e.g., for
maintenance purposes).

3
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

0.3 Aim

The aim of this manual is to provide guidance on the use of the Electronic Flight Bag and
system, to increase efficiency and situational awareness.

0.4 Applicability

The system shall apply to all cockpit crew employed by Air Namibia in relation to line flying
and simulator training/assessment on all our fleet.

0.4.1 EFB Applications

Type A Type B Miscellaneous

Name Used for Name Used for Name Used for
Web Manuals Library Jeppesen/Lidl Navigation charts display Web Internet
synchronization & synchronization and view Browser research
view (no contextual
access)
GoodReader PDF Reading CyberJet Flight preparation and E-mail client Mail sending
Flight package and receiving
Microsoft Meeting E-Perf Takeoff and landing Zenith-TTI Client
Teams performance booking
IQSMS Send messages to
Quality & Safety

0.4.2 EFB Hardware

EFB

Hardware Manufacturer Apple Inc (USA)

iPad 8th Generation IoS 15.4.1 64GB No
Type of device used: SIM-WIFI

Mounting device storage

Hardware Manufacturer RAM Mounts

Device : TBC

4
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

External Battery (Power Connector) TBC

Hardware Manufacturer Any

Device : Capacity 20 000mAh minimum

1.Responsibilities

The company FlyZeJet responsibility commenced with the appointment of personnel who will
be accountable for the administration of the Electronic Flight Bag system and ensure the most recent
up-to-date documentation and procedures, as applicable, will be made readily available to EFB users.

1.1 OPS Staff on Duty:

Whereas pilots in duty have final responsibilities they may delegate to Ops staff some EFB task:

To issue fully charged EFB units to the Flight Crews when starting flight.
To accept the EFB units from the Flight Crews when finishing flight.
To ensure safe and secure storage of the EFB units in the OPS.

1.2 Flight Crew Member

His EFB related duties and responsibilities are:

1. When accepting a Portable EFB unit:

To check the EFB unit for any obvious signs of damage.

To check the power cord for condition on each flight, and if any wear is noted, advise
the OPS for replacement.
To check the Jeppesen Mobile FD database validity and update it, as necessary.
To check the Documentation Library status and update it, as necessary.
To check the Performance and W&B software validity and update it, as necessary.
To assume responsibility for the security and physical integrity of the EFB.
To check and assure that the EFB units are charged before commencing Flight Duty.

5
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

2. When using Portable EFB unit:

To use the EFB according to the requirements stated in the OM.

Not to leave the Portable EFB unit unattended.
To apply the overheat prevention measures as described in OM.
Not to leave a Portable EFB unit exposed to extreme environmental conditions.
To handle the Portable EFB unit with care.
To report any fault or operational irregularity of a Portable EFB unit using the
EFBIR.
To report any CRM problem caused using a Portable EFB via the ASR.

3. When transferring responsibility over Portable EFB unit to another Flight Crew Member:

To remind them of any fault or operational irregularity of the Portable EFB system
(if applicable); To clean the unit’s touch screen by using the appropriate means.

1.3. EFB Administrators

The role of the EFB Administrator is a key factor in the management of the EFB system.
Complex EFB systems may require more than one individual to conduct the administration process,
hence the role of a back-up nominee appointed to assist the designated EFB Administrator. The
Administrator is responsible for the management of the EFB system with appropriate authority within
the Air Namibia management structure.

6
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

The Administrator is the person in charge of the overall EFB system and is responsible for
ensuring that all the hardware conforms to the required specification and that no unauthorized software
is installed. He is also responsible for ensuring that only the current version of the application software
and data packages are installed on the EFB system.

The Administrator is responsible:

a) For all the applications installed and for providing support to the EFB users on these
applications.
b) To check potential security issues associated with the application installed.
c) For hardware and software configuration management and for ensuring that no
unauthorized software is installed.
d) For ensuring that only a valid version of the application software and current data
packages are installed on the EFB system.
e) For ensuring the integrity of the data packages used by the applications installed.
Appendix 1 has the names of the persons within FlyZeJet that are responsible for the
management of the EFB system.

NOTE: EFB forms part of the Flight Operations department therefore the accountability of the
functions and management of the EFB system is overseen by the General Manager Flight Operations.

7
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

2.EFB Policy

2.1 General

FlyZeJet has chosen the iPad as the device for its Class 1 (portable installation) EFB with type
B applications to reduce cost and to improve safety and efficiency and to simplify access to
operational information. The iPad will be loaded with, but not limited to, the following Applications
(Applications) provided by FlyZeJet:
1. Pre-flight information retrieval e.g., SITA flight plans, Weather and NOTAMS
2. Performance calculations
3. Aircraft Manuals
4. Company manuals and briefings
5. Jeppesen
6. Goodreader

The EFB may be used during all phases of flight during normal and abnormal operation with the
proviso that the device is either stowed or placed in the FlyZeJet/CCAA approved holder for take-off,
landing and periods of severe turbulence, further „Airplane Mode‟ must be selected ON before take-
off and must remain as such until after landing.

A minimum of two up to date and serviceable devices are required when departing from base,
and at least one when returning to base. Should only one device be available on the return leg, the
required charts shall be printed from the link provided on the intranet.

2.2 System of amendment and control

The FlyZeJet EFB is a controlled company device and will be managed and maintained by the
EFB Administrator. The EFB Administrator is responsible for the physical control of the EFB and the
associated software the activation of amendments to the hardware and software.

Crew are required to ensure that all operational data contained within in the various
Applications are up to date before departing from base. This is done through the upgrade updates of
the iPad when notification is received from the Administrator of available updates.

8
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

2.3 Mitigation Strategies against the effects of a

Failure or Malfunction of the EFB

Two Portable Electronic Devices (Either iPad or cPED) are normally carried and one device
serves as a backup to the other. In exceptional circumstances flights returning to base may operate
with one device.
a) Crew are required to carry their updated company issued device and shall be used as a
backup to the C-PED under exceptional circumstances.
b) Crew are required to carry the company supplied battery charger, and to charge the
device timeously to ensure continued use.
c) Any calculation or data anomaly and/or hardware failure shall be reported to the EFB
Administrator via the Captain’s Flight Report.
d) The Flight Technical Department must be called to assist in verifying performance
data in cases of output data disagreement.
e) In the event of an unserviceable device, the return flight to base may still be
commenced provided:
i. independent calculations by each crew member with the single iPad that matches
output.
ii Required navigational and approach charts are printed using facilities provided by the
chart issuing service.
iii. A link for printing of the navigational charts shall be available on the company
intranet.

2.5. Flight Dispatch Procedure

The C-PED‟s will be kept at Flight Dispatch for safeguarding.

a) Flight Dispatch will charge the device and will check for updates on Jeppesen and
Performance Software. The Administrator/Library will, however, inform all new
updates.
b) Flight Dispatch will hand the charged and updated C-PED‟, only when the issued
devices are not available.
c) Flight Crews during night stop’s away from base will safeguard the C-PED‟s.

9
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

d) Flight Crews will after their flight return the devices and report any deficiencies to
Flight Dispatch and Administrator.
e) When due to operational requirements it becomes necessary that that C-PED‟s need to
be handed over to a swop crew, then it will be indicated and recorded at Flight
Dispatch and crews will be informed.

2.6 Training

All crew will undergo compulsory training on the EFB as detailed in the FlyZeJet- FOM Part D
(EFB Training Syllabus). Such training will cover the hardware functions of the device as well as the
operational use of the company supplied applications and its updating processes.

2.7 Emergencies

In the event of a device battery overheat (thermal runaway) or fire the following procedure must
be followed:
a) If EFB unit feels hotter than normal or producing any fumes, the unit must be shut off
and not restarted until the cause has been fully investigated. iPad EFB unit has an
overheat protection. It will shut itself down and stay shut down until it cools off. It will
shut itself down and stay shut down until it cools off.
b) Cabin crew (if carried) must be notified as soon as possible, by using the “ALERT”
call
c) Cabin crew (if carried) are required to report to the flight deck immediately and
remove the device and take all possible measures to prevent a fire or to fight an
existing fire.

10
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

2.8 Application ‘White List’ Control

Only applications that meet the following criteria will be considered for inclusion in the
whitelist by the EFB administrator.
1. The application aids the pilot in his work and/or assists him managing his life when
away from home.
2. The application does not contravene the individual usage agreement or broader
FlyZeJet IT policy.
The EFB administrator will consult with the General Manager Flight Operations (or his
designee) if doubt exists to determine if criteria no 1 is met, and with the IT Manager (or his
designate) if criteria no 2 is met.

Pilots are required to forward their application requests via email to the EFB administrator for
consideration.

11
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

3.WORKFLOWS

3.1 EFB Application Upgrade

Step # Activity Actors Tools Main Description

Output
1 Inform 3rd party Email Notification e- The EFB Administrator receives an email from
Custome provider mail the provider informing the availability of a
rs new standard of the application for iPad

2 Get New EFB Apple New software The EFB Administrator updates iTunes
EFB Administr Store application library by downloading the new EFB
Software ators iTunes software from the iTunes Store. The EFB
Administrator checks that the content of the
delivery complies with provider release note
and archives the delivery.

3 Install EFB EFB Apple EFB software After reading the documentation provided
Software Administr Store updated on (release note, limitations note), the EFB
ators iTunes representative Administrator installs the new EFB software on
iPad a representative iPad, directly from Apple
Store, or by synchronizing the representative
iPad with iTunes.

4 Install EFB IT Apple EFB software The EFB Administrator notifies IT managers
Software Managers Store updated on that a new standard of the application for iPad is
iTunes documentation released. The IT admins install the new
Internal and standard on their representative iPads and
Database performance synchronize their iPad with the database.
iPads

12
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5 Check IT Internal Compatibility The IT Managers check the compatibility of

compatibilit Managers Database assessment the current data with the new EFB software.
y new with current
software / data
data

6 Optional: IT EFB New data In some cases, the new EFB software could
Generate new Managers Administr delivered to the lead to a new generation of compatible EFB
data ators EFB data. In that case, the IT Manager must generate
Administrator new data relevant for their domain. Each IT
Manager builds the ARINC 665 loads delivers
them to the EFB Administrator.
7 Validate / EFB Internal New EFB The EFB administrator creates, on the Internal
Ensure Administr Database software + new Database, a release with new EFB data. While
traceability ator data validated this release is not published, only the tests
Domain profiles can load it. Any data that has been
Administra altered since its creation is rejected by the
tors Database (ARINC 665 integrity check). The
EFB administrator requests the IT Manager
to synchronize their representative iPad with the
Internal Database (test profile), and to
perform some global tests to verify that
software for iPad is working consistently. If
the validation shows no issues, the EFB
Administrator can dispatch the new software
and data.
The EFB Administrator logs:
- The availability date of the new software and
data
- The validity period of the new software and
data
The changes included in the new software and
data.
8 Publish EFB Internal Availability of The EFB Administrator publishes, on the
Administr Database new EFB Internal database, the release with
ator software & data new EFB data. The release is associated with
notified to end an
users EFB version. The EFB Administrator sends a
notification to the end users to inform that a
new EFB software and new EFB data are
available.
9 Install new End users Internal End user iPad
End user installs new EFB software:
software Database updated
- Directly from Apple Store, or
Apple
- By downloading the applications on iTunes
Store
and synchronizing his/her iPad.
iTunes
10 Synchronize End users Internal End user iPad
End user synchronizes his iPad with the
iPad with the Database updated
database.
FlySmart
with Airbus
Gateway
11 Follow up EFB Internal Traceability tool
For each iPad, the EFB Administrator monitors
fleet Administr Database updated with
the configuration reports on the internal
configuration ator configuration
database. The EFB Administrator keeps track of
reports
the iPads that are up-to-date and of those that
have still to be updated.

13
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

3.2 Airport data update

14
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Step # Activity Actors Tools Main Output Description

1 Inform Airport E-mail Notification e- The Performance Administrator receives an e-mail
customers database mail informing the availability of new airport database.
provider

2 Get new airport Performance Provider New airport New Performance data delivered to EFB
database Administrator Portal CD / database Administrator
DVD

3 Import new data Performance PA ADMIN Performance tools The Performance Administrator imports the new
into PA ADMIN Administrator updated with new airport data into Airport Manager of PA ADMIN.
airport database

4 Generate new Performance PA ADMIN Performance The Performance Administrator builds the ARINC 665
data Administrator data delivered to load and delivers it to the EFB Administrator.
EFB
Administrator
5 Validate / EFB Internal New The EFB administrator creates, on the internal database, a
Ensure Administrator database performance release with new EFB data. While this release is not
traceability Performance data published, only the tests profiles can access it. Any data
Administrator validated that has been altered since its creation is rejected by the
internal database (ARINC 665 integrity check). The
EFB administrator requests the Performance
Administrator to synchronize his representative iPad with
the internal database (test profile), and to perform some
global tests to verify that software is working
consistently. If the validation shows no issues, the
EFB Administrator can dispatch the new performance
data.
The EFB Administrator logs:
- The availability date of the new software and
data
- The validity period of the new software and data
The changes included in the new software and data
6 Publish EFB Internal Availability of The EFB Administrator publish with Airbus Gateway,
Administrator database new performance the release with new EFB data.
data notified to The release is associated with an EFB version. The
end users EFB Administrator sends a notification to the end
users to inform that new EFB performance data is
available.
7 Synchronize End users Internal End user iPad End user synchronizes his iPad with the internal database
iPad with the database updated
internal
database

8 Follow up fleet EFB Internal Traceability tool For each iPad, the EFB Administrator monitors the
configuration Administrator database updated with configuration reports on the internal database. The
configuration EFB Administrator keeps track of the iPads that are up-
reports to-date and of those that still must be updated.

15
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

3.3 EFB Documentation update

16
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Step # Activity Actors Tools Main Output Description

1 Customize flight Documentation FODM or New revision of The Documentation Administrator modifies the
ops manuals into Administrator ADOC the operator operator customization.
FODM or ADOC customized
manual

2 Generate new Documentation FODM or New the ARINC The Documentation Administrator builds the
data Administrator ADOC 665 loads and ARINC 665 loads and delivers them to
delivers them to the EFB Administrator.
the EFB
Administrator.
3 Validate / EFB Internal New The EFB administrator creates, on the
Ensure Administrator database documentation Internal database, a release with new EFB
traceability Documentation (test profile) data validated data. While this release is not published, only
Administrator the tests profiles can access it. Any data that has
been altered since its creation is rejected by
the internal database (ARINC 665 integrity
check). The EFB administrator requests the
Documentation Administrator to synchronize
his representative iPad with the internal
database (test profile), and to perform some
global tests to verify that software is working
consistently. If the validation shows no
issues, the EFB Administrator can dispatch the
new documentation data.
The EFB Administrator logs:
- The availability date of the new software
and data
- The validity period of the new software
and data
The changes included in the new software and
data.
4 Publish EFB Internal Availability of The EFB Administrator publishes, on the
Administrator database new Internal database, the release with new EFB
documentation data. The release is associated with an EFB
data notified to version. The EFB Administrator sends a
end users notification to the end users to inform that
new EFB documentation data is available.
5 Synchronize End Users Internal End user iPad End user synchronizes his iPad with the
iPad with the database updated Internal database.
internal database
6 Follow up fleet EFB Internal Traceability tool For each iPad, the EFB Administrator
configuration Administrator database updated with monitors the configuration reports on the
configuration Internal database. The EFB Administrator
reports keeps track of the iPads that are up-to-date
and of those that still have to be updated.

17
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

3.4. PERFORMANCE CUSTOMIZATION UPDATE

Step # Activity Actors Tools Main Output Description

1 Customize new Performance PA ADMIN New The Performance Administrator modifies the
data into PA Administrator performance customization. For example, he/she can add a
ADMIN (new data tail number if the operator receives a new
A/C, aircraft with the same aircraft database or
performance modifies the operator policy.
parameters
…)

2 Generate new Performance PA ADMIN New Performance The Performance Administrator builds the
data Administrator data delivered to ARINC 665 loads and delivers them to the
the EFB EFB Administrator.
Administrator

3 Validate/Ensure EFB Internal New performance The EFB administrator creates, on the
traceability Administrator database E- data validated Internal database, a release with new EFB
Performance Perf for data. While this release is not published, only
Administrator iPad the tests profiles can access it. Any data that has
been altered since its creation is rejected by
the Internal database (ARINC 665 integrity
check). The EFB administrator requests the
Performance Administrator to synchronize his
representative iPad with the Internal database
(test profile), and to perform some global

18
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Step # Activity Actors Tools Main Output Description

tests to verify that E-Perf for iPad is working
consistently. If the validation shows no
issues, the EFB Administrator can dispatch the
new performance data.

The EFB Administrator logs:

- The availability date of the new software
and data
- The validity period of the new software
and data
The changes included in the new software and
data.
4 Publish EFB Internal Availability of The EFB Administrator publishes, on the
Administrator database new EFB Internal database, the release with new EFB
data notified to data. The release is associated with an EFB
end users version. The EFB Administrator sends a
notification to the end users to inform that
new EFB performance data is available.

5 Synchronize End Users Internal End user iPads End user synchronizes his iPad with the
iPad database updated Internal database.
with the Internal
database

6 Follow up fleet EFB Internal Traceability tool For each iPad, the EFB Administrator
configuration Administrator database updated monitors the configuration reports on the
with configuration Internal database. The EFB Administrator
reports keeps track of the iPads that are up-to-date and
of those that still have to be updated.

19
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

3.5 Flight Operations Manuals Revision

Step # Activity Actors Tools Main Output Description

1 Inform Embraer E-mail Notification e-The Documentation Administrator receives an
customers mail e-mail from Embraer informing the
availability of a new flight operations
manual release. The flight operations
manuals that Embraer delivers are :
- OM Part A General / Basic;
- OM Part B Airplane Operation;
- OM Part C Route and Aerodrome
Instructions and Information
- FCOM (Flight Crew Operating
Manual)
- MEL (Minimum Equipment List)
- AFM (Aircraft Flight manual)
- QRH (Quick Reference Handbook)
- FCTM (Flight Crew Training Manual)
- WBM (Weight and Balance Manual).
- Jeppesen documentation;
2 Get new Documentation Embraer Web New Embraer The Documentation Administrator
manual Administrator Portal revision downloads the new flight operations manual
revision CD / DVD revisions from Embraer Web Portal/TDD
(Technical Data
Download) or receives them by CD/DVD.

20
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Step # Activity Actors Tools Main Output Description

3 Import new Documentation FODM or Embraer revision The Documentation Administrator imports the
manual Administrator ADOC loaded manual into FODM or ADOC (depending on the
into FODM or into authoring tool that the operator selected).
ADOC tool

4 Do the revision Documentation FODM or Embraer revision In FODM/ADOC, the Documentation

management / Administrator ADOC integrated intoAdministrator customizes operator
Get the Approval operator documentation based on new Embraer
customized manual revision, and requests approval from the
National Authority, if necessary.
5 Generate new Documentation FODM or New The Documentation Administrator builds the
data Administrator ADOC documentation ARINC 665 loads and delivers them to the
data delivered to EFB Administrator.
the EFB
Administrator

6 Validate / EFB Internal New The EFB administrator creates, on the

Ensure Administrator database documentation Internal database, a release with new EFB
traceability Documentation data data. While this release is not published, only
Administrator validated the tests profiles can access it. Any data that
has been altered since its creation is rejected
by the Internal database (ARINC 665 integrity
check). The EFB administrator requests the
Documentation Administrator to synchronize
his representative iPad with the Internal
database (test profile), and to perform some
global tests to verify that application is
working consistently. If the validation shows
no issues, the EFB Administrator can dispatch
the new documentation data.
The EFB Administrator logs:
- The availability date of the new software
and data
- The validity period of the new software
and data
The changes included in the new software and
data.
7 Publish EFB Internal Availability of The EFB Administrator publishes, on the
Administrator database new Internal database, the release
documentation with new EFB data. The release is associated
data notified with an EFB version. The EFB Administrator
to end users sends a notification to the end users to
inform that new EFB documentation data is
available.

8 Synchronize End Users Internal End user iPad End user synchronizes his iPad with the
iPad with the database updated Internal database.
Internal database
9 Follow up fleet EFB Internal Traceability tool For each iPad, the EFB Administrator
configuration Administrator database updated with monitors the configuration reports on the
configuration Internal database. The EFB Administrator
reports keeps track of the iPads that are up-to-date and
of those that still have to be updated.

21
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

4.DISPATCH CONSIDERATIONS

4.1 Introduction

The Dispatch Considerations document provides operational mitigation means proposed by

Embraer to cope with EFB failures prior to dispatch combined with a subsequent failure with
operational impact in flight and their associated impact on operations.

For A319/332 (Put Embraer Reference) aircraft, the QRH remains available on-board the
aircraft.

4.2 Scope

The proposed operational mitigation means are only Embraer recommendations and may be
partially or completely modified by the airlines upon acceptance by their Department of Civil Aviation
Authorities, especially regarding the use of backup/alternate means.
In any case, airlines can define dispatch considerations in accordance with their own policy
provided that they are accepted by their Department of Civil Aviation. Airlines can replace any/all
mitigation means by their own, upon acceptance by their Department of Civil Aviation.

4.3 Applications

The E-Perf applications suite includes the following applications:

• Ops Library Browser (OLB), documentation viewer
• Take-off performance module (T.O PERF)
• Landing performance module (LDG PERF)
• Electronic Flight Folder (FLT FOLDER)

22
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5.FAILURE CASES AND MITIGATION MEANS

5.1 Flight Operation Applications

5.1.1 Failure of Ops Library Browser on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of Ops Library Browser on one side. OpsLibrary Browser is available offside. Use OIS XFR
/ VIEW OFFSIDE to consult Ops Library Browser
(when available).

In-flight failure with operational impact Proposed Operational Mitigation Means

Loss of Ops Library Browser on both sides. - Use Operator’s backup, or

- Use alternate procedure.

Note: View offside EFB puts the display (XFR) mode in order to view the content of the other
EFB display. While in this mode the display cannot be manipulated.

23
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5.1.2 Failure on take-off on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of Take-off on one side. Ops Library Browser is available offside. Use OIS XFR
/ VIEW OFFSIDE to consult Ops Library Browser (when
available).Take-offis available offside.

The pilot offside performs the computation, notes the

results then clears the computation. The pilot offside
gives his PED to the pilot onside. The pilot onside
performs the computation.

Both pilots crosscheck the results indicated on the PED

with the results noted by the pilot offside.
OR
The pilot offside performs the computation. The pilot
onside uses the Operator’s backup.

Both pilots crosscheck the results.

In-flight failure with operational impact Proposed Operational Mitigation Means

Not Applicable. Not Applicable.

24
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5.1.3 Failure of landing on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of Landing on one side. Landing is available offside.

The pilot offside performs the computation, notes the

results then clears the computation. The pilot offside
gives his PED to the pilot onside.

The pilot onside performs the computation. Both pilots

crosscheck the results indicated on the PED with the
results noted by the pilot offside.
OR
The pilot offside performs the computation. The pilot
onside uses the Operator’s backup.

Both pilots crosscheck the results.

In-flight failure with operational impact Proposed Operational Mitigation Means

Loss of Landing on both sides. Use the Operator’s backup, or
Use alternate procedure (e.g. ask ground for a computation
in flight).

25
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5.1.4 Failure of Load sheet on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of Loading on one side. Loadsheet is available offside.
The pilot offside performs the computation, notes the
results then clears the computation.

The pilot offside gives his PED to the pilot onside.

The pilot onside performs the computation. Both pilots

crosscheck the results indicated on the PED with the
results noted by the pilot offside.
OR
The pilot offside performs the computation. The pilot
onside uses the Operator’s backup.

Both pilots crosscheck the results.

In-flight failure with operational impact Proposed Operational Mitigation Means

Not Applicable. Not Applicable.

5.1.5 Failure of In-Flight on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of In-Flight on one side. In-Flight is available offside.

The pilot offside performs the computation. The pilot

onside checks input/output parameters of the
computation (use OIS XFR / VIEW OFFSIDE when
available).

In-flight failure with operational impact Proposed Operational Mitigation Means

Loss of In-Flight on both sides. Use Operator’s backup, or
Use alternate procedure (e.g. ask ground for a computation
in flight).

26
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

5.1.6. Failure of Electronic Flight Folder on one (CM1 or CM2) side

Consequence Proposed Operational Mitigation Means

Loss of Electronic Flight Folder on one side. Electronic Flight Folder is available offside. Use OIS
XFR / VIEW OFFSIDE to consult Electronic
Flight Folder (when available).

In-flight failure with operational impact Proposed Operational Mitigation Means

Loss of Electronic Flight Folder on both sides. Use Operator’s backup, or
Use alternate procedure (e.g. ask ground for flight
support).

5.2 Loss of EFB function on CM1 or CM2 SIDE

Consequence Proposed Operational Mitigation Means

Loss of FLT OPS applications on one side. The following Ops Library Browser, Electronic Flight Folder
applications are lost: • When required, CM1 uses CM2 PED or vice-
Ops Library Browser Take-off versa.
In-Flight Landing Loadsheet In-Flight performancecomputation
Electronic Flight Folder CM2 computes the performance data on his PED.
• CM1/CM2 checks input/output parameters
of the computations on the the PED in function.
Take-off, Landing and Loadsheet performance computation
• CM1/CM2 performs the computation on
his PED, notes the results then clears the
computation.
• CM1/CM2 gives his PED to the other pilot.
• CM1/CM2 performs the computation.
• Both pilots crosscheck the results
indicated on the PED with the results noted by
CM2.

OR

• CM2 computes the performance data on

his PED.
• CM1 uses the Operator’s backup or vice-
versa

Both pilots crosscheck the results.

Additionally, a trip may proceed if one set of charts for

departure, departure alternate, enroute alternate, destination
and destination alternate airports are available in paper
format. They must be provided before the flight.

EFB administrator shall be informed immediately in order to

arrange a shipment for replacement.
In-flight failure with operational impact Proposed Operational Mitigation Means

27
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Consequence Proposed Operational Mitigation Means

Complete loss of EFB function on one side. Use Operator’s backup (an Ipad backup or documents
in paper format), or
Use alternate procedure (e.g. asks ground for
performance computation in flight, ask ground for
flight support).
Out of Date, corrupt or Erroneous Jeppesen Proposed Operational Mitigation Means
Database
Out of date database A trip may commence for up to 14 days beyond the
valid date of the revision, provided FMS database is
current and the following contingency procedures are
followed:
1. For expired terminal charts the Captain and
OPS shall determine if intended airports of use are
affected by the latest revision. If affected, the flight
crew shall obtain paper versions prior to flight for
affected airports.
2. For expired enroute charts the Captain and
OPS shall determine if planned routes are affected. If
so, changes shall be noted on the OFP prior to flight
through affected areas.
3. If EFB units disagree with other flight deck
systems (FMS database) the crew shall carefully
evaluate the erroneous source before using and use the
source, which has been verified correct. The error has
to be reported to the EFB Administrator via EFBIR.

Note: In some cases, Jeppesen update may present an

error the day of AIRAC publication. This is a known
issue that is due to servers’ upgrade propagation. At
11am, new update try will be successful.

5.3 Hardware malfunction

Consequence Proposed Operational Mitigation Means

Unit malfunction Any time Portable EFB unit is considered to be
malfunctioning, the following shall be
accomplished:
1. Unit reset: Press and hold both Sleep/ Wake
(top) and Home buttons simultaneously. Release
when the white Apple logo is

shown. Wait for Power-up and check EFBs

normal functionality. If unsuccessful:
2. Disable the unit by removing power source and
stow the unit;
3. Report the malfunction.
Emergency equipment on board Proposed Operational Mitigation Means

28
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Consequence Proposed Operational Mitigation Means

Battery Risk Management System The Aircare FireSock™ is used to safely contain
the appliance after the incident so that the crew
can focus on emergency procedures surrounding
the event.

System Overheat Proposed Operational Mitigation Means

EFB unit feels hotter than normal or producing any The unit must be shut off and not restarted until the
fumes cause has been fully
investigated. iPad EFB unit has an overheat
protection. It will shut itself down and stay shut down
until it cools off. It will shut itself down and stay shut
down until it cools off.
No EFB unit available in Flight Proposed Operational Mitigation Means
Current paper products are not available Perform approach procedure:
1. By utilizing data from previously completed
Approach Preparation Form (see applicable form), if
available;
2. By utilizing FMS data and requesting
appropriate information from ATC;
3. If time permits perform EFB unit reset;
4. Landing performance computation is made by
both pilots using paper QRH.
Mounting Device Becomes unserviceable or Proposed Operational Mitigation Means
broken
Mounting device becomes unserviceable 1. If Mounting device becomes unserviceable on
PF side immediately transfer airplane control to PM.
2. Do not try to fix mounting device in high
workload phases of flight.
3. If possible, during low workload phases, try to
repair the support (Maybe one part to be tighten)
4. Report mounting device failure using EFB IR
and/ or ASR.

Note: EFB administrator shall be informed immediately to arrange a shipment for replacement.

29
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.iPad CONFIGURATION

6.1 General Configuration Options

The following general configuration options shall be observed per iPad.

Option Configuration Description

Settings Bluetooth Bluetooth shall be disabled

Settings General
• About Name Name will be the name of the iPad as defined by the EFB
administrator on a per user basis. The name shall comprise
the 3LC of the crew member to whom the iPad will be
issued
• Lock Rotation Lock rotation shall be enabled
• Auto Lock 5 Minutes shall be enabled

Settings Wallpaper Wallpaper will be selected from the wallpaper

generated as per Annex G. Wallpaper shall be assigned to
Lock Screen and Home Screen

Settings Privacy Location Services shall be enabled

Settings Keyboard Auto-Capitalization disabled

Auto-Correction disabled
Check Spelling disabled
Enable Caps Lock enabled
Predictive disabled
Split keyboard enabled
“.” Shortcut enabled
Enable dictation disabled

30
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.2 Wi-Fi Configuration Options

The following general configuration options shall be observed per iPad.

Option Configuration Description

SSID @ZeJet.wyfy

Passphrase As per received details on issuance of iPad

6.3 Software Configuration Options

6.3.1 ePerf

The following general configuration options shall be observed per iPad. Settings are managed
from ePerf.

Option Configuration Description

Address ftp://

Username As per received details on issuance of iPad

Password As per received details on issuance of iPad

Ensure a connection successful is observed when Check is clicked.

31
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.3.2 GoodReader

The following general configuration options shall be observed per iPad.

Option Configuration Description

FTP Server

Readable Title EFB Library

URL-address Ftp://

User As per received details on issuance of iPad

Password As per received details on issuance of iPad

Encoding UTF8

Library Select

Sync Select

Destination Main directory of GoodReader

6.3.3 Software/Load Updating

Software and load updating shall commence well in advance before a flight. An update is
indicated with a red numeral, ie. next to the icon of the application where an update has been detected.
The numeral indicates the number of new updates available.
Although great care has been taken on providing a general guide on updating software/loads,
this document cannot cater for all scenarios. Should a problem be experienced, and the results can be
duplicated, a details report shall be sent to the EFB administrator with the following included:
i. Detailed step-by-step description of events leading to the occurrence
ii. Screenshot of the result
iii. iOS version
iv. Application Version
The report shall be sent by email to efb.admin@flyzejet.com
For any updates an active internet connection is required. However, during flight, the iPad shall
be placed in flight mode.

32
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.3.4 Flight Mode

To enable flight mode, swipe from the home button towards the top of the device. Click on:
Flight Mode Selector

Flight mode shall be confirmed by a symbol, located top left of the iPad, before the aircraft is
boarded by crew. Symbol shall appear as follows:

Flight Mode active

6.3.5 iOS

iOS updates will be indicated with a red numeral next to the settings icon.

MAJOR updates are not allowed without explicit permission from the EFB
Administrator. Updates are considered major when version numbers increase in a
one-step increment after the initial version indication, eg. iOS 8.4 to iOS 8.5

MINOR updates are allowed without permission from the EFB

Administrator, unless otherwise indicated. Updates are considered minor when
version numbers increase in one step increment, after the second numeral, eg. iOS
8.4 to iOS 8.4.1 or iOS 8.4.1 to iOS 8.4.2.

In order to update, proceed as follows:

33
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Description/Icon E
vent
ACTION

C
lick
Instal C
l Now lick
OBSERV
ATION

Click (A standard software

agreement and acceptance of terms will be
shown) The terms shall be accepted.

Indicates that the update is being

prepared. After installation, a restart may
be required.

34
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.3.6 Software

Software updates will be indicated with a red numeral next to the AppStore icon.

AppStore Icon
In order to update software, proceed as follows:
Description/Icon Event
ACTION

Click

Click

Click
(For a single application update)
OR
Click
(For a multiple applications update)
OBSERVATION

Indicating that the download of

the application is in progress

The application(s)‟s icon(s) will change

indicating the progress of the update.

The steps above shall be used to update all applications on the iPad, whenever required
to do so.

35
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

6.3.7 Load Updating

6.3.7.1 E-Perf Load Update

E-Perf load updates needs to be done whenever a new load is available.

ePerf Icon

Description/Icon Event

Indication of a new load available on the server.

AND/OR

Indication of unread emails, with possible

indication of availability of a new load for
ePerf

ACTION

Click

Click

OBSERVATION
Indication of Database files in settings

36
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Indication the server is used as source for

update
Indication of load on server.

Indicates file name, date and

time

New update is available on

server

Missing file

File is up-to-date

Not in use but available

File being used

ACTION

Click*

Click

37
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

OBSERV
ATION

Date & Time

underneath all files will
change.

File is up-to-date

AND

File being used

*Delete all recommended as anomalies have been observed with ePerf not correctly indicating
new update date and time.

6.3.7.2 GoodReader Load Update

GoodReader load updates needs to be done whenever a new load is available.

Automatic scheduling has been enabled, however, this procedure described below is for

manual syncing.
Good Reader

38
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

Description/Icon Event

Indication of unread emails, with possible

indication of availability of a new load for
GoodReader

ACTION

Click

Click

OBSERVE

Update syncing library from

server to device

39
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
GoodReader Manual Structure
8 OPERATING PROCEDURES Rev :

FlyZeJet Operations Manuals

A/C Lease Agreements

Flight Operations Ground Operations Security Safety & Quality Aircraft A/C N/A

A/C Maintenance
Maint. Planning Programs (AMP)
(CAME)
Misc Work Instructions Gnd Ops Manual AvSec Program Safety Management Emer Resp Plan
OM Part A
Chapter 1-15 (AOSP) Reliability
Opr. Control (WI) (GOM) System (ERP)
Program

Gnd Handling Health, Safety & Fit Folio/Tech

OM Part B A/C SOP Cabin Crew Manual Manual (GHM) Environment Log
(HSE) Maintenance
Gen SOP Control Manual
(MCM) Deferred Defect
Line Station QA System Doc Control
Type Specific Record
GlareShield Package Manuals (LSM) (QASM) Program (DCP)
CCM
Maintenance
Agreements
Medivac SOP Communicable Gnd Ops Work Flight Support Aircraft Library
Diseases Instructions (WI) Manual
SOP

EFB Manual
RVSM Emergency QRH
OM Part C
Routes & Non-Scheduled Ops
Aerodromes Dangerous Goods
Dispatch Manual RNAV/PBN
Manual Normal C/L
(DM)
Scheduled Ops
Human Resources
Manual LOPA AFM QRH

Jeppesen
Safety Card AOM ETOAS Tables/
(PBC) (Volume 1&2) E-Perf

COA COR Operational Ref

Guide (ORG)

Minimum Disp. Deviation

Equipment List Procedures
OM Part D
Syllabi Forms Training Work (MEL) (DDPM)
Training
Instructions (WI)

Radio License Insurance

Initial
A/C Type Ratings

Recurrent
Enhancement
Courses
Initial
40
Cabin Crew

Recurrent

Other
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

7.EFB Forms
These forms are onboard in the EFB bag.

7.1 SOPs

EFB SOP
Dispatch Procedures
1 EFB #1 & #2 POWER ON
2 CHECK CHARGE #1 & #2 EFB %CHECK
3 TIME & DATE CHECK COMPLETED
4 WIFI #1 & #2 EFB ON
5 JEPPFD APPLICATION #1 & #2 EFB TEST(2)
6 JEPPFD DATABASE #1 & #2 EFB UPDATE(3)
7 DOCUMENT LIBRAIRIES #1 & #2 EFB UPDATE(3)
8 WIFI #1 & #2 EFB OFF
9 AUTO LOCK #1 & #2 EFB OFF
10 MUTE #1 & #2 EFB CHECK MUTE
11 AUTO BRIGHTNESS #1 & #2 EFB CHECK OFF
12 RUNNING APPS #1 & #2 EFB CHECK
13 POWER #1 & #2 EFB STDBY MODE
Preflight Procedures
1 MOUNTING DEVICE #1 & #2 ATTACH & ADJUST
2 POWER #1 & #2 EFB ON
3 EFB DISPLAY ROTATION LOCK
4 PF EFB SETUP SET FOR DEPARTURE(4)
5 PNF EFB SETUP SET FOR DEPARTURE(4)
During Taxing
Only FO shall actively operate manipulate the touch screen) onside EFB during taxing.
Before Take-Off
From Line Up position on the runway until passing FL 100 only PNF (FM) shall operate his EFB.
Climb (above FL 100)/Cruise/Descent (above FL 100)
Only one pilot at the time should use the EFB to avoid “both heads down” situation.
Reviewing of text data or Company manuals shall be performed only by the PNF
1 PF EFB SETUP SET FOR DESCENT (5)
2 PNF EFB SETUP SET FOR DESCENT (5)

Descent (below FL 100)/Approach/Landing

Below FL 100 only PNF (PM) shall operate his EFB.
PNF shall observe and manipulate EFB unit in almost conservative manner.
After Landing

41
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

1 BATTERY CHARGE CHECK(6)

2 AUTO LOCK #1 & #2 EFB ON
3 POWER #1 & #2 EFB OFF

7.2 EFBIR

EFB IRREGULARITY REPORT

NAME FLIGHT NUMBER

DATE A/C REGISTRATION

Request EFB Administrator's Reply: YES NO

EFB UNIT:

Narrative Description of observed EFB Operational Irregularity :

Reporter's Signature :

EFB Manager
PILOTS (FLIGHT Enveloppe) ODC (Scan and send by mail)
efb.admin@flyzejet.com

EFB IRREGULARITY REPORT PROCESSING

42
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

EFB IRREGULARITY REPORT

EFBIR received on : EFBIR credible : YES NO

EFBIR classified as: information only observation Non-Compliance Safety Hazard

Description of Corrective Action taken :

EFB Administrator's signature :

EFB IRREGULARITY REPORT PROCESSING

43
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

8.Operational Approval

8.1 Use of EFBs

(CAT.GEN.MPA141)
Where an EFB is used on board an aircraft, ZEJET shall ensure that it does not adversely affect
the performance of the aircraft systems or equipment, or the ability of the flight crew member to
operate the aircraft.

8.2 Operational approval of EFB

(CAT.GEN.MPA.141) (SPA.EFB.100)
ZEJET shall not use a type B EFB application unless it is approved in accordance with the
following requirements contained in Subpart M of Annex V (Part-SPA.EFB.100).

(a) ZEJET shall only use a type B EFB application if it has been granted an approval by
the authority for such use.

1. To obtain an operational approval from the authority for the use of a type B EFB
application, ZEJET shall provide evidence that:

2. A risk assessment related to the use of the EFB device that hosts the application and
to the EFB application and its associated function(s) has been conducted, identifying the
associated risks, and ensuring that they are appropriately managed and mitigated.

3. The human–machine interfaces of the EFB device and the EFB application have been
assessed against human factors principles.

44
 Page :
UNCONTROLLED DOCUMENT
Date:
OMA-8 OPERATING PROCEDURES
8 OPERATING PROCEDURES Rev :

4. It has established an EFB administration system and that procedures and training
requirements for the administration and use of the EFB device and the EFB application have
been established and implemented; these shall include procedures for:
Operating the EFB ;
The management of changes to the EFB.
The management of EFB data.
EFB maintenance ; and
EFB Security ;

5. The EFB host platform is suitable for the intended use of the EFB application.
This demonstration shall be specific to the EFB application and the EFB host platform on
which the application is installed.

The company EFB Policy and Procedures manual details the procedure for the approval of EFB
Applications.

During the evaluation period, the monitoring protocol is as follow by the EFB Administrator:

Bi-Monthly monitoring of Jeppesen charts update through Jeppesen web-based interface.

Monthly monitoring of Documents updates through individual request
Monthly monitoring of apps updates and IOS update
Monthly survey addressed to crews for general feedback of the system
Close monitoring of EFBIR and any reports

45