Hangar Maintenance Execution

Hangar Maintenance Execution enables aviation maintenance teams to perform routine maintenance activities from preparing for aircraft arrival at the hangar, recording maintenance, and raising non-routines, to releasing an aircraft, via the IFS Cloud Web user interfaces.

IFS Cloud Hangar Maintenance Execution consists of:

 IFS Cloud Hangar Maintenance Execution can be deployed integrated with Maintenix as the primary Maintenance and Engineering (M&E) system, or as a standalone maintenance execution system.

Setting up Basic Data and Requirements and Operational Data

Where options exist an administrator can choose to create or update basic data and requirements (BDRs) for aviation maintenance workflows via pages in Aviation Maintenance/Basic Data or choose to load data via data loading and migration processes.

Similarly in the case of aircraft configuration, an administrator can load aircraft configuration data via data loading and migration processes. Refer to the IFS Cloud Technical Documentation on Hangar Maintenance Execution for information on how to migrate maintenance data and load aircraft configuration.

Hangar planners can upload work packages and their contents using the Hangar Maintenance Work Package Loader. If Hangar Maintenance Execution is not integrated with a flight following system, hangar supervisors can create and update flights, as needed.

Information is then ready to be utilized by mobile aviation maintenance teams to perform maintenance activities.

Activities Supported by the Hangar Maintenance Execution Applications

The Hangar Maintenance Execution applications enable mobile aviation maintenance teams to handle the following maintenance activities that occur until the aircraft is released as serviceable:

Maintenance Activity Description Executable only when Hangar Maintenance Execution is integrated with Maintenix
Assign resources Hangar supervisors/crew leads can assign resources such as technicians to tasks and tools/equipment to tasks. No
Raise and package non-routines New non-routines identified on an aircraft can be recorded by a technician so they can be addressed. These non-routines, other open non-routines and deferred non-routines, which have not been assigned to a work package can be packaged to a suitable work package. No
Add parts, tools, skills and measurements to task/non-routines requirements If all the required parts, tools, skills and measurements needed to complete work on tasks or non-routines have not been specified, a technician can add them prior to maintenance execution to record their use and values during work capture. No
Find and reserve inventory Hangar technicians can find and reserve inventory in Maintenix for part changes that must be carried out as a result of performing maintenance on a task using the Hangar Maintenance Execution application. Yes
Start work Hangar technicians can start work on task or non-routine, to change the status of the task from Active to In Work. No
Initiate and receive remote assistance Hangar technicians can call experts or experts groups and receive remote assistance using augmented video. No
Record work Hangar technicians can record the status of steps, actions taken, part changes, tool use and measurement values on work tasks. They can also complete a task or close a non-routine. No
Inspect work Hangar technicians or supervisors can inspect work done by another technician and mark the status of steps that are awaiting inspection as approved or rejected. No
Request deferral Hangar technicians can request to defer an open non-routine, which adds it to a list of non-routines to be deferred by a maintenance operations controller (MOC). No
Review non-routine to be deferred Maintenance operations controllers can review the non-routines for which deferrals have been requested by hangar technicians. No
Initiate deferral Maintenance operations controllers can initiate the deferral of a non-routine from the Hangar Maintenance Execution web application. They can then authorize the deferral of the non-routine in Maintenix, while providing the deferral authorization number to a technician to defer the non-routine in Hangar Maintenance Execution. If rejected, the technician must go on to fix the non-routine in Hangar Maintenance Execution. Yes
Mark non-routine as reviewed Once a non-routine has been reviewed, it can be marked as reviewed by a maintenance operations controller, so it no longer appears on the non-routines to be deferred list. It is then displayed in the Reviewed Faults list. No
Defer faults Hangar technicians can defer open non-routines in a work package, using deferral information as supplied by MOC, record deferral actions, and sign for the deferral. No
Record and review fluid servicing Hangar technicians can record fluid uptakes, which hangar supervisors can then go on to review to monitor the rate of fluid consumption. No
Review aircraft compliance and release aircraft to service. Hangar technicians can view any open non-routines on the aircraft and open tasks in the work package, which prevent aircraft release. They can also view if any configuration warnings that have been issued by the Configuration Management Service (CMS). Release an aircraft to service provided no open non-routine or open tasks exist. Complete the work package for the aircraft turn and update the status of the turn to Released. No. Yes to view configuration warnings by the CMS.