AMC1 SPA.EFB.100(b)(3) Use of electronic flight bags (EFBs) – Operational approval    

CAA ORS9 Decision No. 1

EFB ADMINISTRATOR

The operator should appoint an EFB administrator responsible for the administration of the EFB system within the operator’s organisation. The EFB administrator is the primary link between the operator and the EFB system and software suppliers.

The EFB administrator function may be contracted to an external organisation in accordance with ORO.GEN.205.

Complex EFB systems may require more than one individual with appropriate authority within the operator’s management structure to perform the administration process, but one person should be designated as the EFB administrator responsible for the complete system.

The EFB administrator is the person in overall charge of the EFB system, and should be responsible for ensuring that any hardware conforms to the required specification, and that no unauthorised software is installed. They should also be responsible for ensuring that only the current versions of the application software and data packages are installed on the EFB system.

The EFB administrator should be responsible:

    (a) For all the EFB applications installed, and for providing support to the EFB users regarding these applications;

    (b) For checking potential security issues associated with the applications installed;

    (c) For hardware and software configuration management of the EFBs, and, in particular, for ensuring that no unauthorised software is installed.

    The EFB administrator should ensure that miscellaneous software applications do not adversely impact on the operation of the EFB and should include miscellaneous software applications in the scope of the configuration management of the EFB.

    This does not preclude EFB devices from being allocated to specific flight crew members.

    In those cases where it is demonstrated that miscellaneous software applications run in a way that is fully segregated and partitioned from the EFB or avionics applications (e.g. on a separate operating system on a distinct ‘personal’ hard drive partition that is selected when the EFB boots up), the administration of these miscellaneous software applications can be exercised by the flight crew members instead of by the EFB administrator.

    (d) For ensuring that only valid versions of the application software and current data packages are installed on the EFB system; and

    (e) For ensuring the integrity of the data packages used by the applications installed.

    The operator should make arrangements to ensure the continuity of the management of the EFB system in the absence of the EFB administrator.

    Each person involved in EFB administration should receive appropriate training for their role and should have a good knowledge of the proposed system hardware, operating system and relevant software applications, and also of the appropriate regulatory requirements related to the use of EFBs. The content of this training should be determined with the aid of the EFB system supplier or application supplier.

    The operator should ensure that the persons involved in EFB administration keep their knowledge about the EFB system and its security up to date.