MxOne runs the maintenance side of an airline in a single application: defects and deferrals, the maintenance programme and its due list, tracked components, stores, purchasing, quality and reliability — with every sign-off tied to the person, the station and the authorisation behind it.
Most maintenance software is either a large suite that takes a year to fit to an operator, or a set of separate tools that never quite agree. MxOne is one application on one database: the mechanic, the maintenance controller, the storekeeper, the buyer, the planner and technical records all work on the same record.
It is designed around how the work actually moves through a station — who writes the defect, who performs and signs the action, who certifies, who reviews and closes — and it checks the authorisation at the moment of signing, not afterwards in an audit.
Follow a defect through the systemFlight legs from the operations feed or entered by hand, tech log pages, oil and hydraulic uplifts. Posting a leg moves the hours and cycles of the aircraft and of every unit fitted to it.
Pilot, maintenance and cabin reports become work cards. Actions, part changes, independent inspections and MEL, CDL and NEF deferrals with their limits, placards and extensions.
The fleet at a glance: serviceability, open and deferred items coming due, aircraft on ground, parts awaited. Maintenance control reviews certified work and closes it.
Every tracked unit with its times since new and since overhaul, where it is fitted and where it has been. Assemblies with the units inside them, life limits, and the compliance record of each task.
Programme tasks with limits in hours, cycles, days and calendar months, check packages, phased tasks with outcomes, task parts, tools and manpower, and programme revisions.
The due list projected from each aircraft's utilisation, bands for what is due in 30 and 90 days, and work packages built from it — a check, or whatever fits the next ground time.
Stores, bins, quarantine and unserviceable stock at every station. Serialized units, batches with shelf life, transfers, mass moves, kits, cycle counts and reservations, on an append-only stock ledger.
Demand classified from usage history, suggested safety stock and reorder points per station, and parts needed by the tasks that are about to fall due — before the aircraft arrives.
Purchase, repair, exchange and loan orders with approval limits, item suppliers and lead times. Receiving with inspection and certificates, cores, and receipts confirmed at a remote MRO facility.
Licences and company authorisations by aircraft type and station, vendor approval and its expiry, audits, findings and corrective actions, training courses and records.
Delays and cancellations, reportable events, removals and defects by ATA chapter, alert levels, and the monthly tables and meeting record of a continuing analysis and surveillance programme.
People, shifts and skills; roles and permissions per station; parameters, numbering and reference lists; handbooks inside the application; and a guided set-up for an aircraft joining the fleet.
Each step belongs to a role, and the system knows which one. A small station can give one person more than one step; a large one keeps them apart.
The defect is written against the aircraft and its log page, with the ATA chapter and the station. It appears on the fleet status of maintenance control at once.
Actions are added with their manual reference; parts are requested from stores and fitted, moving the removed unit to unserviceable stock. If the item is deferred, the MEL item sets the category, the limit and the due date.
Each action is signed with a personal PIN. MxOne checks that the person holds a valid authorisation for this aircraft type and station, and for certifying staff that the licence was issued by the regulator the aircraft is registered under.
The card is certified once every action is signed, required inspections are done and part changes are posted. The time of certification is the time of compliance.
Maintenance control reviews the certified card and closes it, or returns it for correction with a reason. Closing updates the task tracking, the component history and the reliability figures in the same step.
MxOne refuses what should not happen and records what did. These are properties of the database and its packages, so they hold whichever screen or interface the change comes from.
Type, station, validity, licence status and regulator are checked when the PIN is entered. If the check fails, the message says exactly why.
Stock movements, sign-offs and line check records are append-only. A mistake is corrected by a new entry that says who corrected it and why.
Who changed which field, from what to what, and when — for aircraft, components, tasks, orders, vendors, roles and parameters.
A role is given for a station. A storekeeper at one base cannot issue stock at another unless that role is given there too.
Performing, inspecting, certifying and closing are separate permissions, and an independent inspection cannot be signed by the person who did the work.
Next due follows from the last accomplishment, the limits of the task and the aircraft's own counters. Posting a flight recalculates what it affects.
MxOne is an Oracle APEX application on Oracle Database, hosted on Oracle Cloud Infrastructure. The business rules live in PL/SQL packages next to the data, so the browser, a tablet on the ramp and an integration all go through the same checks.
Moving maintenance data is where most implementations stall. MxOne treats it as part of the product: templates per data area, cleaning and validation with the problems listed row by row, and a load you confirm only when you have seen the result.
Legacy stock, open orders, usage and the last accomplishment of every programme task come across, so the due list and the stock position are right on the first day — and comparable with what the old system said.
Prefer to look before you commit? A demo environment with a small Boeing 767 fleet, a full maintenance programme, stores at several stations and three months of flying is available to try with your own team.
Ask for access to the demoTell us your aircraft types, the number of stations and what you run today. We will show you the same work in MxOne — from a pilot report to a closed card, and from a part falling below minimum to a received order.