Basics of Flight – Essentials for an MRO ERP Consultant

Understanding the aircraft lifecycle isn't just nice-to-have—it's the foundation of your credibility.

The aviation industry runs on precision. When an aircraft is on the ground, airlines lose money—up to tens of thousands of dollars per hour for a wide-body jet. As an MRO (Maintenance, Repair, and Overhaul) ERP consultant, your job isn't just about configuring software modules. It's about understanding the operational heartbeat of aviation so you can design systems that keep planes flying safely and profitably.

Here's a guide to the aviation fundamentals every MRO ERP consultant needs to master.

1. The Core Objective: Airworthiness

In commercial aviation, everything revolves around one concept: airworthiness. This is the legal and operational requirement that an aircraft is safe to fly. As SAP's documentation for Aerospace & Defense states, "the primary objective is to ensure the airworthiness of technical objects" .

For an ERP consultant, this means:

• Every maintenance activity must be traceable

• Every installed part must be validated

• Every inspection must be documented for regulatory audits (like FAA or EASA)

Why this matters for ERP: Your system must provide a complete, auditable history of every maintenance action. If an auditor asks, "When was this engine last overhauled and who signed it off?", the ERP must answer instantly.

2. The Asset vs. Component Tracking Dichotomy

One of the biggest shifts for consultants coming from manufacturing or standard enterprise software is understanding how assets are tracked in aviation.

Serialized vs. Non-Serialized Parts

In typical ERP implementations, you track inventory by part number and quantity. In aviation MRO, you track individual serial numbers . A single engine (serial #ABC123) has its own maintenance history, flight hours, and life limits—completely independent of another identical engine (serial #XYZ789).

As one aviation ERP expert puts it, the system must track "parts and components during their entire life cycle, whether installed in an aircraft, stored in a warehouse, or serviced in a workshop" .

The "Rotables" Problem

Rotable components are high-value parts that can be repaired and reinstalled multiple times—like landing gear or auxiliary power units . These parts are removed, sent to a workshop for refurbishment, and returned to serviceable stock. The ERP must track:

• Serviceable vs. Unserviceable status (can this part be installed?)

• Life limits (how many more flight hours before mandatory retirement?)

• Configuration (which aircraft currently has this serial number installed?)

ERP implication: Your system needs robust serial number management and must handle complex "remove-repair-reinstall" workflows across multiple locations .

3. The Maintenance Planning Engine

Aircraft maintenance isn't random. It's driven by the Aircraft Maintenance Program (AMP), which schedules checks based on:

• Flight hours (e.g., every 500 hours)

• Flight cycles (e.g., every 1,000 takeoffs/landings)

• Calendar days (e.g., every 12 months)

UMP and VWP: The ERP's Planning Soul

Oracle's cMRO documentation defines two critical planning concepts :

• UMP (Unit Maintenance Plan): The predictive engine that calculates when each aircraft is due for its next maintenance based on usage data.

• VWP (Visit Work Package): The container that bundles all UMP requirements into a single, scheduled maintenance visit in a hangar bay.

Heavy Maintenance Events

When an aircraft enters a hangar for a C-check or D-check (heavy maintenance), it can be grounded for 1–6 weeks. Non-routine events—unexpected defects discovered during inspection—can account for over 50% of the workload .

ERP implication: Your system must handle both routine maintenance scheduling (predictable inspections) and dynamic, non-routine work orders that pop up when mechanics find a crack in a wing spar. This demands flexible work order management and real-time inventory visibility .

4. The Inventory Management Challenge

Aviation inventory is expensive and complex. A single engine can cost $10–30 million. Spares inventory optimization is a "giant mathematical problem" involving thousands of part numbers .

The Float Concept

The number of repairable parts needed to support fleet availability is called float—the buffer required to account for parts being in repair, in transit, or in the warehouse . Factors influencing float include:

• Number of aircraft

• Repair turnaround time (TAT)

• Failure rates (MTBE - Mean Time Between Events)

• Scrap rates

Pooling and PBH

Airlines often participate in pooling agreements—sharing rotable inventories with partners . Some use Power-by-the-Hour (PBH) programs where a supplier stocks parts for a fixed monthly fee .

ERP implication: Your inventory module must support multi-ownership tracking (which parts are owned, borrowed, or on exchange), manage repair-to-reuse workflows, and ideally integrate with specialized optimization algorithms .

5. Configuration Control: The Million-Piece Puzzle

An aircraft is built from millions of parts. When a component is removed and replaced with a different serial number, the aircraft's configuration changes.

Master Configuration vs. Unit Configuration

Oracle cMRO defines a crucial distinction :

• Master Configuration (MC): The "blueprint"—what this aircraft type should look like based on engineering specifications.

• Unit Configuration (UC): The "as-is" state—what this specific aircraft actually has installed right now.

Every maintenance action must reconcile these two. If the system shows a GE engine but the plane has a Pratt & Whitney engine installed (or vice versa), that's a configuration error that could ground the aircraft.

ERP implication: Your system must provide a configuration control workbench to instantly display the current, accurate configuration of any aircraft and track the interchangeability of parts .

6. Regulatory Compliance: The Non-Negotiable

Aviation is the most regulated industry in the world. Every component, every repair, and every signoff must comply with:

• ADs (Airworthiness Directives): Mandatory regulatory actions—if an AD is issued, every affected aircraft must comply by a deadline .

• SBs (Service Bulletins): OEM-recommended improvements or inspections.

• Life-Limited Parts (LLP): Parts with a hard retirement date—cannot be used past their cycle limit.

ERP implication: Your system must flag overdue ADs, manage life-limit tracking (often down to the serialized part level), and ensure that mechanics can only sign off on work if they are properly certified .

Your Role as an MRO ERP Consultant

You are not just a software configuration expert. You are an operational architect. The airlines and MROs you serve need a system that:

1. Talks to mechanics: It must support their workflows, from issuing task cards to scanning barcodes for parts .

2. Integrates with the ecosystem: Modern MROs use IoT sensors for predictive maintenance, mobile devices for line mechanics, and AI for forecasting .

3. Ensures safety above all: You are building the digital backbone that keeps aircraft airworthy.

Master the basics of flight operations and aircraft maintenance, and you'll move from being an ERP implementer to a trusted partner who actually helps airlines fly safer and more profitably.

Want to dive deeper? Explore how modules like Maintenance Planning, Inventory Management, and Configuration Control are configured in your specific ERP platform. Understanding the "what" and "why" of aviation logistics is the first step to mastering the "how" of system configuration.

Unleashing Features of QCPs to Extend Oracle Complex MRO (Oracle CMRO)

The day to day activities in the production floor of an aircraft maintenance hangar involves carrying out inspections, compliance of AMS tasks, compliance of AD/SB, replacing of components, rectification of the defects etc.  Depending on the type of aircraft and based on the type of servicing required on the aircraft, various maintenance data has to be recorded along with the maintenance activities and communicated to the engineering and planners.  The requirement varies from customer to customer and requires an extensible solution to meet their requirements.

Oracle e-business suite application, Oracle Complex Maintenance Repair and Overhaul (cMRO) has a provision to attach Quality Collection Plans (QCP) to the production jobs to meet the requirements in the production floor.  Quality Collection Plans if used judiciously in Oracle CMRO will provide the production planners and the engineers a platform to introduce robust processes.

Here in this blog, I am explaining functionality introduced for a civil aircraft maintenance facility to capture data required for Structural Damage Repair Reporting using QCPs.  The structural damages on the aircraft like dents, buckles, minor cracks etc. are a monitored throughout its life span.  This data is maintained and the defects are reported to the Engineering and Quality Assurance departments when a temporary/ permanent repair is done to bring the damage with in an acceptable limit.  Required reports and a workflow were created to introduce an approval workflow process for the damage repairs.  The complete Structural Damage Repair Reporting process has been implemented using QCPs, BI publisher reports and Oracle Workflows.

The below screenshot shows the QCP developed for the technician to enter data while executing his task.  This QCP was attached to an operation which is added to the non-routine created for repair of the structural damage.

The advantage of the QCP is that we can add additional fields without any coding effort.  Also, the user can upload files against the QCP records.  The documents generated as a part of damage inspection like photographs, damage sketch etc. can be uploaded as an attachment to the QCP.

 We can trigger an approval workflow from the QCP action by setting the action as “Launch a Workflow”.  The below screenshot shows the steps to to setup the QCP to launch the workflow.

The WF process sets the approvers to a role and sends approval notification to the approvers.  Once approved by the approver, after uploading the necessary documents into the QCP the damage report is generated and forwarded to Engineering and Quality.

The workflow process is shown below.  

The below figure shows the notification received by the approver.

The notification received by engineering will have the damage report (BI publisher report) generated as an attachment.  Also the uploaded damage chart etc. will be attached to this notification which can be readily downloaded from the notification itself (no need to submit the concurrent program to generate a report manually)

The notification received by the engineering is shown below with the attached documents.

Also, I could get an OA framework page developed quickly by our OA guru to search for the structural damages.  The page is shown below:

The edit button will lead the user to the QCP edit screen in edit mode where the production planner can edit the data/ upload attachments to the QCP.

Reliability Centered Maintenance

The traditional method adopted for aircraft maintenance was based on flying hours of the aircraft. In 1974 the United States Department of Defence initiated efforts to analyze techniques to be used by airline industries to develop cost effective maintenance programs. And the result is a radically different approach to aircraft maintenance called 'Reliability Centred Maintenance'.

This new methodology resulted in huge cost savings for the airlines. Not only are these cost savings immense, but they were achieved with no decrease in safety or dispatch reliability. To the contrary, safety and reliability actually improved in almost every instance when emphasis shifted from scheduled retirement-overhaul-replacement to on-condition maintenance.

The OEMs are responsible to determine the TBO of the components or the engine as a part of certification process with the regulator. The TBO is calculated after rigorous testing and analysis of the components. However the modern structural and thermal analysis software’s can predict the life of the components to a great extend. The most widely used statistical technique for reliability prediction is Weibull analysis as it is the best suited method for failure prediction of mechanical components. The well-known "bathtub curve" depicts the failure pattern with a high risk of failure when the item is first placed in service ("infant mortality"), the useful life and followed by a second high-risk “Wear out zone” when the item exceeds its useful life.

The criticality of the failure of a component to probability of failure is studied using Hazard Risk Index (HRI) to determine the safe life of the component. The components are released for this safe life operation if the failure analysis proves that the type of failure is under the safe zone. The TBO is determined by the OEMs based on this analysis.

The maintenance organizations usually calculate the MTBUR of the component to schedule the maintenance activities and to calculate the float levels. But the accuracy of this calculation is largely dependent on the techniques used for data collection. The modern ERP systems provide a framework to collect data required for accurate reliability analysis. For more information on this, please refer the white paper published in box.net  accessible through the below link.

http://www.box.net/shared/0qq0z61rva/Reliability Whitepaper.pdf

This white paper details the the reliability analysis solution developed on top of Oracle’s ERP system (the solution was built on top of eBiz suite application Complex Maintenance Repair and Overhaul).