Aviation MRO Overview

MRO = Maintenance, Repair, and Overhaul. An MRO is the industry layer sitting between aircraft operators (airlines, cargo carriers, charters) and aircraft manufacturers. Every commercial aircraft in the world generates a continuous stream of maintenance demand — scheduled inspections, unscheduled defect rectification, component repairs, overhauls, mandatory service bulletins. MROs answer that demand.

What an MRO actually does

Four operating domains sit on top of the same fleet:

Line Maintenance. Fixes done between flights, usually at the gate or on an overnight stop. Think: replace a tire, top off hydraulic fluid, sign off a discrepancy the pilot wrote up, release the aircraft back to service within the turn time. In this database that's the FLOG_* tables — tech logs, discrepancies, sign-offs, part consumption. The unit of work is the AMEPackage (Aircraft Maintenance Execution package).
Base Maintenance. Heavy scheduled checks performed in a hangar — A-checks (monthly), C-checks (every 18–24 months, ~1–3 weeks in the hangar), D-checks (every 6–10 years, 3–6 weeks, full strip-down). This lives in the visit tables — VisitPackage and friends. Base visits bundle hundreds of tasks across multiple days.
Component Maintenance. Off-wing repair. When a line or base mechanic removes a landing gear, an engine component, an avionics box — that component gets routed to a repair shop with a ShopWorkOrder. The shop repairs it, tests it, certifies it, returns it to stock. The serialised part lifecycle lives in ComponentID and the repair detail in the 80+ SWO_* tables.
Engineering and Planning. Above the operational layer sit task masters (TaskMaster, TaskDetails), MEL/CDL configurations (MELCategory, MELConfig), model effectivity rules (ModelEffectivity), and reliability tracking.

The hero metric

Aircraft availability. An aircraft on the ground costs an airline between $10,000/hour (regional jet) and $150,000/hour (widebody). The whole MRO discipline exists to get aircraft back to the gate as fast as possible while keeping them airworthy. Every record in this database ultimately traces to a decision about whether an aircraft is released to fly or held for more work.

Where Ramco Aviation sits

Ramco Aviation is the ERP that runs all four domains on a single data model. The operator or MRO logs in, records work, consumes parts, signs off tasks, issues certificates. Everything interconnects through the aircraft reg, the task/work-unit track ID, and the shop work-order number.

The data in this Brain is an actual operator's extract — 1,025 aircraft (125 distinct models), 6,683 tech logs, 10,663 discrepancies, 25,192 shop work orders, over 10 million transaction rows. Real operational scale.

What makes it hard

Regulatory. Every maintenance action against a flying aircraft is subject to FAA / EASA / DGCA oversight. Every sign-off is potentially auditable decades later.
Traceability. Serialised parts (engines, landing gear, avionics) must be traceable from manufacture to scrap, across every aircraft they touch.
Deferability. Not every defect grounds an aircraft. The Minimum Equipment List defines what can be deferred and for how long. The Discrepancy Lifecycle page walks through this.
Configuration management. "Aircraft 1132" isn't just one static thing — it has a configuration that changes every time a component is swapped. ComponentID and AircraftPart track this.
Multi-tenancy. An MRO serves multiple airline customers simultaneously. Every transaction is scoped by OrganizationUnit (OU) to keep customer data logically separated on the same platform.

How to use this Brain