Skip to content

Forward/Line Maintenance (FLM) ConfigurationΒΆ

Overview

Forward/Line Maintenance enables forward/line maintenance teams to perform maintenance activities from preparing for aircraft arrival, recording maintenance and deferring faults, to releasing an aircraft, via the IFS Aurena and IFS Aurena Native app user interfaces.

The Forward/Line Maintenance solution comprises of:

  • Maintenix - The solution relies on an installation of Maintenix during IFS Cloud installation and co-located installation of the Maintenix and IFSApps databases. Installation and configuration tasks for Maintenix must be complete before you install and configure the Forward/Line Maintenance components below. See Maintenix (MXCORE).

  • Forward/Line Maintenance components in IFS Cloud: The solution also relies on an installation of the Forward/Line Maintenance components in IFS Cloud.

The Forward/Line Maintenance components in IFS Cloud are as follows:

  • ADCOM - This consists of web pages, used by administrators to verify that information related to Forward/Line Maintenance has been migrated and synced from Maintenix, and to define settings related to the display of information for technicians.
  • ADMON - This consists of web pages used by administrators to monitor communication, notably the status of the synchronization of requests between the Forward/Line Maintenance applications and Maintenix.
  • FLMEXE - This consists of web pages used by line technicians and maintenance supervisors.
  • FLM- This consists of pages on the mobile Forward/Line Maintenance application, which is used by technicians. For information related to .

Configuration tasks

The table below details the list of tasks to be executed to configure FLM for use.

Task Instructions
Set up user as an administrator of Forward/Line Maintenance information Set up user as an Administrator
Set up user as a technician Set up user as a Technician
Set up user as a supervisor Set up user as a Supervisor
Install and set up Aurena Native Apps Aurena Native Apps
Set up the Mobile Forward Line Maintenance application and configure mobile app users IFS Mobile Forward/Line Maintenance
Enable the entity sync of Forward/Line Maintenance entities Enable FLM entity sync
Migrate Maintenance Data - To work with Forward/Line Maintenance and integrate it with Maintenix, customers with existing Maintenix records must migrate data. This is done as part of configuring Maintenix. Migrate Maintenance Data
Apply Database Execution Grants to API Packages - During installation, the Mx_Data_Sync_Util_API package is added to Apps-Mtx IFS Packages. Depending on the order in which you install the co-located databases, you might need to apply grants to the Mx_Data_Sync_Util_API package. Apply Database Execution Grants to API Packages
Configure IFS Connect for Forward/Line Maintenance Set up IFS Connect for Forward/Line Maintenance integration with Maintenix
Set Defer on Approval parameter to False - If technicians are required to sign off on deferrals, after MOC approval of a deferral request and before the fault status is set to Deferred, you must set the Defer on Approval parameter to False in Maintenix. You may skip this setting, if technicians are not required to sign for the deferral after MOC approval. Set the Defer on Approval parameter to False in Maintenix.
Enable the IFS Cloud tooling solution for Forward/Line Maintenance, rather than the default tooling solution from Maintenix Enable the IFS Cloud tooling solution
Enable a line technician or supervisor to add and view attachments on a fault Configure the use of attachments on faults
Set up the use of digital signatures for the Forward/Line Maintenance solution IFS Signature Service
Configure remote assistance on installation Remote Assistance Configuration
Configure users and user groups for remote assistance Remote Assistance
Enable a technician to be able to raise a fault from the Forward/Line Maintenance applications Enable the Raise Fault permission for the IFS Connect role in Maintenix.
Enable a line technician to request for parts from part groups unrelated to those defined on the task or fault Allow part requirements for unrelated part groups in Maintenix