Innovative Solutions for Commercial Airline Operators
Image 1 Image 2 Image 3 Image 4
efos:efb

EFOS:Efb is a "smart client" application on a laptop or Tablet PC (for which it is optimised). EFOS:Efb allows the user to read manuals and complete various training and data reports in an unconnected state. These items are then synchronised with the main EFOS database when the device is next connected.  EFOS also handles the process of updating various third party programs such as performance software.

Additionally EFOS:Efb gives cabin crew tools that help them to deal with safety issues and offer superior passenger service.

Electronic Documentation

EFOS:EFB Software running on a Tablet PCEFOS:Efb provides automatic synchronisation of electronic libraries with the EFOS main system. EFOS also validates version information, rebuilds damaged libraries, provides an audit system and highlights changes. Users are warned of out-of-date (caution) or missing files (warning) and summaries of new changes are distributed to each user. The library module of the EFOS:Efb application is also available as a standalone product.

Flight Planning and Logging

This tool uses existing company data about schedule information, crew records and weather to populate an electronic flight report. Forecast weather or plotting charts can be annotated using digital ink and these annotations saved and archived with the rest of the flight report. By collecting pilot input in an ordered way the EFOS:Efb is able to export data to back-office systems which then use this information for analysis to improve business intelligence and knowledge.

Quality Reporting, Accountability and Audit Tracking

The EFOS:Efb enables the pilot or crew member to record details concerning service quality or procedures. Feedback and reports are automatically delivered, for comment or action, to the manager accountable for that part of the operation. Office based managers will be alerted to new items requiring their attention and will be directed to EFOS:Web to review and act upon the details within the flight report.

Company Communications

All airlines issue a profusion of internal communications and other media such as newsletters, intranets, safety leaflets, crew notices, company e-mail etc. Through a synchronisation procedure similar to that used for electronic manuals, all forms of company communication will be delivered whenever the user logs on.

Electronic Journey Log

EFOS:Efb includes a module for recording aircraft block times, fuel usage, OTP, flight duty periods and minimum rest requirements; errors are eliminated by the use of a rules database and time/date validation. The software automatically generates discretion reports (if needed) and acts as a pilot's personal log book by recording consecutive flight information. Data collected this way is structured, validated and available for intelligent data analysis.

Training Tools, Forms and Records

The EFOS:Efb can be used to deliver training forms and packages directly to training Captains and line instructors. EFOS:Efb features a training library for quick reference whenever the crew so wish to revise any particular topic.

Flight Safety and Incident Reporting

A series of flight or passenger safety reports (for example, mandatory ASR, TCAS event, Bird Strike, Airprox, Wake Turbulence, Injury, Disruptive Passenger, Medical Assistance and other internal reporting forms) are available on EFOS:Efb. EFOS:Efb thereby forms an integral, significant and vital part of an airline’s safety, quality and risk management systems.

background information on electronic flight bags

efb hardware classes

class one

A controlled portable electronic device (PED) issued to flight crew and subject to administrative control by the airline. Class One devices do not require airworthiness approval however they may connect to aircraft power through a certified power source.

class two

A PED subject to administrative control by the airline that takes an electrical charge from the aircraft and which may be stowed or mounted on the physical structure of the aircraft. Data feeds from ACARS and GPS are permitted. A Class 2 EFB requires an airworthiness approval; this approval is limited in scope to the mounting device, crashworthiness, data connectivity and EFB power connection.

class three

An electronic device which is powered by the aircraft and communicates directly with other avionic systems; Class Three systems are considered installed equipment and therefore require airworthiness approval.

Evoke Systems Ltd’s EFOS:Efb is designed to conform to the requirements of a Class Two device.

efb software types

type a

Type A software applications include pre-composed, fixed presentations of data currently presented in paper format.

type b

Type B software applications include dynamic, interactive applications that can manipulate data and presentation. Type B software includes performance calculations, electronic aeronautical charts and electronic checklists.

Type A and B software applications do not require airworthiness approval, but should be approved through an operational approval process.

Note on applications ineligible for Type A or Type B EFB classification:

Unlike FAA AC120-76A, JAA guidance does not include a Type C software application classification. The JAA policy is that any software application not falling within the scope of Type A or Type B should undergo a full airworthiness approval.

EFOS and EFB software contains a mix of Type A and B software applications. The operational approval process will usually be determined by the National Flight Operations Inspectorate (FOI).


FAA Advisory Circulars External Link

FAA AC120-76A Guidelines for the Certification, Airworthiness, and Operational Approval of Electronic Flight Bag Computing Devices PDF Link External Link

JAA Operations Division External Link (with links to New and Amended TGLs)

JAA TGL 36 (EFB) Approval of Electronic Flight Bags (EFBs) PDF Link External Link