Teardown Report #43: Flybe Chooses Amos Software

RSS

Hello, readers! Welcome to this week’s Teardown Report.

The transitioning of legacy IT systems is one thing that we have brought up time and time again, and it continues to be a pain point for MROs with large fleets and large, established engineering operations. Swiss AviationSoftware says it is going to try to repair some of those issues by implementing its Amos software at Flybe Aviation Services. “It will replace Flybe’s current and somewhat fragmented in-house built legacy system and leverage greater efficiencies and cost savings,” said the software provider in its May newsletter.

 Why is the legacy system "somewhat fragmented?" Well, John Palmer, managing director, Flybe Aviation Support, says in the release that there are 20 divisional units within Flybe's MRO engineering department. That could be one of the reasons. Having a large organization like this poses a coordination challenge for any company, one that I'm sure engineers are eager to ease with the new software.

The implementation is slated to take between 12 to 15 months. Swiss says that some of the Amos features will include “business process mapping, gap analysis, data migration, key-user workshops and key and end-user staff training for 600 potential users.” As you can see,  the scope of this implementation is wide.

Flybe has a fleet of 80 aircraft, including Q400 turboprops, the Embraer 195/175. Flybe Aviation Services takes care of the line and base maintenance of the fleet, and serves third party operators. At the beginning of 2012,  Palmer told O&M that the MRO intends to focus on bolstering its regional capabilities, and it has now added ATR-72/-42 capabilities to its list of line and base maintenance. Building on that, Flybe is now a Bombardier-approved authorized service facility for Bombardier CRJ jets.

What are your thoughts on the implementation? Do you think the software is going to help Flybe when it comes to adding on to its regional expertise? 

Please or Register to post comments.

Blog Archive

Sponsored Introduction Continue on to (or wait seconds) ×