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.