Flight Hours management project

The customer is one of the world's leading aircraft manufacturers with activities in commercial and military segments.

In line with the evolving needs of its customers, this company has decided to develop Flight Hour Services (FHS) for Component Support. In this service solution it offers full component support on the basis of a pay as you use scheme; i.e. fixed price for each flight hour flown. The aim of this service is to enable airlines to reduce investments and increase aircraft availability thus increasing customer satisfaction. Line Replacement Unit’s (LRU’s) included in the FHS agreement will include Proprietary components, OEM/Supplier components or any combination thereof.
Some functionality necessary for the implementation of this service were already partially implemented in existing IT-Systems, but additional crucial functionalities (process event handling, monitoring, reporting, …) had to be implemented in a new component, the FHS Process Integrator. 2MoRO took part in this project from the Business Case (evaluate customer fleet revenue) to the Entry Into Service of the first airline.

The scope of the FHS solution

The overall FHS process can be split in 8 sub-processes :

Customer contracts: focusing on establishing and managing FHS contracts with this manufacturer's customers
OEM contracts : focusing on establishing and managing FHS contracts with OEMs
Forecasting
FHS operations : which are the day-to-day operations under company's responsibility (stock management, standard exchange management, repair management)
Invoicing
Warranty Management
Business control & Reporting : ensuring performance and business viability for the whole process
Cross functions

A complex IT applications landscape

The planned FHS platform is not a single system. A SAP driven integrated architecture, on which a lot of functionalities and business processes are implemented, was already in place. One of the project goals was to define the overall solution architecture and interconnections (application boundaries, interfaces, …).

The roadmap

The analysis led to define a roadmap for the solution development & implementation. This included :

The solution options in terms of a technical point of view
The solution development and implementation options in terms of planning split the whole scope of functionalities into three batches (“take-off” phase, “climb” phase, “cruise” phase)