INTRODUCTION
The Electronic Flight Bag (EFB) is a general avionic computingplatform that continues to grow and mature. EFB manufacturers offera wide variety of systems ranging from Class 1 (portable) to Class3 (fully integrated). The functionality delivered with any givenplatform varies greatly.
EFBs are marketed as open software platforms, and softwaredevelopers continue to add applications that deliver newfunctionality. In avionics, the EFB is a unique platform in thatsignificant functionality changes occur without the need of a newhardware platform.
As the EFB Market continues to grow it has become clear thatintegrating applications onto EFB systems with proprietaryinterfaces is difficult, time consuming, and costly. The solutionis to abstract the applications from the EFB platform by providingstandardized interfaces.
The first step toward the goal of standardized interfaces wastaken by the adoption of ARINC Specification 834. ARINCSpecification 834 enables applications to receive flight phase andavionic data from any platform that supports the specification.ARINC Specification 840 takes the next step by describing the role,but not necessarily the functionality of an application manager byproviding a protocol for software applications to interact with themanagement software.
Software applications are defined as software that provides theoperator with a specific set of functionality and allows userinteraction. Such software applications may be developed by a widevariety of companies depending on the needs of the customer. Sinceit is unlikely that all of the applications installed on an EFBwill be developed by a single provider, it is the goal of thisspecification to ease the integration of applications created bymultiple providers.
- Edition:
- 12
- Published:
- 11/20/2012
- Number of Pages:
- 123
- File Size:
- 1 file , 970 KB
Reviews
There are no reviews yet.