From the tech log to the records, one system.

What the controller does in MxOne

1. 1Start the shift from the fleet board: AOG, unserviceable, restricted, in check, stored
2. 2Run an AOG event from opening to return to service, with ETR and parts status
3. 3Approve or reject material requests before stores or buyers spend anything
4. 4Record a technical delay against its defect and flight, feeding dispatch reliability
5. 5Hand over the shift with open items inserted for you, acknowledged by the next controller
6. 6Run a recovery as an MCC event with milestones, target against actual, and e-mail updates
7. 7Watch deferral warnings and line checks falling due on the board

Rules MxOne enforces, and why

• AOG is never picked from a list; it comes from an AOG event.A grounding without a start time, reason and owner cannot be measured or handed over.
• One open AOG event per aircraft.Two clocks on one grounding would double the hours on ground.
• The start time and reason cannot be edited after opening.They are the facts the hours on ground and later analysis rest on.

What the mechanic and inspector do in MxOne

1. 1Take a pilot report from write-up to closed, with material, part change and PIN sign-off
2. 2Defer under the MEL (DMI) and bring it back; extend a deferral with approval
3. 3Work an aircraft on ground with Maintenance Control watching
4. 4Swap two units to find a fault, or take a part from another aircraft
5. 5Work a scheduled task card on the line, signing steps and template actions
6. 6Handle one card with several defect lines, each with its own ending
7. 7Book time on a card; do a line check without a work card

Rules MxOne enforces, and why

• An inspector cannot inspect their own work.An inspection is only worth something if it is independent.
• Steps are signed in order: mechanic, inspector, duplicate inspector.Nobody inspects work that is not signed as done.
• A defect cannot be closed with unsigned actions or open steps.Every line of the record must have an owner.

What flight log clerks and records do in MxOne

1. 1Enter a flight leg by hand from the paper log
2. 2Work a whole flight log page: legs, engine readings, defects
3. 3Load the Flight Ops feed and read what happened to each flight
4. 4Correct or cancel a leg, and correct the totals with approval
5. 5Enter oil and fluid uplifts; get the consumption alert
6. 6Read the utilisation report and the defect log by page number

Rules MxOne enforces, and why

• A leg is posted the moment it is saved.Aircraft totals must never be behind the flying, because due dates are computed from them.
• Only components fitted for the whole leg get its hours.A unit must not collect hours of a flight it was not on.
• An aircraft cannot have two legs at the same time.The same flight counted twice makes everything fall due too early.

What fleet and records staff do in MxOne

1. 1Run the New Aircraft Setup checklist from start to sign-off, with bulk loads of units and last-done data
2. 2Change a registration from a given date, keeping the old one on old records
3. 3Set up positions and capabilities (ETOPS, RVSM, Cat III)
4. 4Read the aircraft dashboard and the aircraft record
5. 5Store, retire or sell an aircraft

Rules MxOne enforces, and why

• MSN and fleet number are unique; a registration is current on one aircraft only.One airframe, one record, one history.
• The aircraft type cannot change once the aircraft exists.The type decides the programme, the MEL and the positions.
• A bulk load is checked first and loads all lines or none.An aircraft must never be left half loaded.

What the records team does in MxOne

1. 1Work the daily queue: part changes to verify, compliance to post, log pages to post
2. 2Build assemblies and see what is fitted inside each one
3. 3Track life limits and print the disk sheet for life-limited parts
4. 4Follow a component through its installations and correct one when needed
5. 5Correct aircraft hours and cycles, with a second person's approval
6. 6Receive units back from repair with the work done at the vendor
7. 7Print the aircraft record: parts by ATA, AD / SB compliance, history

Rules MxOne enforces, and why

• A part change is verified by someone other than the person who recorded it.The records check is a second pair of eyes.
• Compliance is posted by someone other than the person who certified the card.The person who released the work must not also reset its clock.
• A log page cannot be posted while a defect on it is open or a leg is not posted.A posted page is a finished page, and its hours must be in the totals.

What planners and engineers do in MxOne

1. 1Set the utilisation rate and read the due list in bands: overdue, 30 days, 90 days, later
2. 2Run and print a forecast per aircraft
3. 3Build a work package from the due list through to release to service, with the tally sheet
4. 4Check readiness for parts, tools and manpower before the aircraft arrives
5. 5Build a programme task completely, including phases for an AD
6. 6Build a check package with its own task and member tasks; adopt MPD tasks

Rules MxOne enforces, and why

• An active task is tracked on every applicable aircraft as soon as it is saved.Nothing half built reaches the due list, and nothing approved is forgotten.
• The earliest limit is the due date, unless the task says whichever comes later.A task is overdue as soon as any one limit is passed. The exception is chosen on purpose.
• Days from hours and cycles are rounded down.A projection must never promise more time than there is.

What the reliability engineer does in MxOne

1. 1Complete the month: the figures are built from the operational modules, not typed
2. 2Investigate an ATA chapter in alert and its repeaters
3. 3Prepare, freeze and print the CASS report with its charts
4. 4Follow an action item from the meeting to closure
5. 5Keep reportable events, special inspections, escalations and APU in-flight starts

Rules MxOne applies, and why

• Only unscheduled removals count as premature.Scheduled, convenience and robbery removals say nothing about the reliability of the unit.
• An alert needs at least 2 events and 6 months of history.One event or a short history is not a trend.
• The month under test is not in its own mean.A bad month must not hide itself by raising its own limit.

What the planner does in MxOne

1. 1Review the daily MRP worklist and accept or reject each proposal
2. 2Let scheduled maintenance drive the plan: parts that are always replaced count as demand
3. 3Keep min and max in line with demand, with suggested levels per station
4. 4Move surplus between stations on a company flight, by courier or by hand carry for AOG
5. 5Set part criticality (no-go, go-if, go) so bases keep a floor of essential stock

Rules MxOne applies, and why

• Nothing is ordered automatically.A planner accepts each proposal; then it becomes a draft order or a planned transfer.
• Required is the larger of known demand and the forecast, plus the minimum.Adding both would count the same demand twice.
• A transfer is proposed only when it is worth it.Shipping a 12-dollar seal by courier for 75 dollars is waste, except when an aircraft is on the ground.

What stores staff do in MxOne

1. 1Issue parts to a defect from the stores queue
2. 2Ship a stock transfer to another station for a waiting request
3. 3Take back an unused part, or reverse a wrong movement
4. 4Adjust or scrap stock, with a second person over the threshold
5. 5Control shelf life and quarantine; trace a serial back to its receipt
6. 6Run stock counts and an ABC cycle counting programme with blind counts
7. 7Reserve parts, handle accompanying parts, loans, borrows and sales

Rules MxOne enforces, and why

• Parts are issued only from a serviceable, issuable location.Unserviceable and quarantined stock must never reach an aircraft.
• An expired batch cannot be issued; otherwise the batch that expires first goes out.Shelf-life control, oldest usable stock first.
• A serial in stock or installed cannot be received again.One physical unit, one record. A second receipt points to a wrong tag or a suspect part.

What buyers do in MxOne

1. 1Take a new vendor from first contact to approved by Quality
2. 2Work the buyer board, from a request to a part on the shelf
3. 3Ask for quotes and accept one
4. 4Run a repair order, and an exchange order with its core return
5. 5Receive a delivery and release the requests waiting for it
6. 6Enter a vendor invoice and post it through the 3-way match
7. 7Print the order, the goods receipt and the ATA-106 form

Rules MxOne enforces, and why

• Only approved, active vendors within their approval date can be on an order.Parts and repairs must come from evaluated sources.
• Only Quality sets a vendor's approval.The approval is a Quality decision, with an expiry date.
• Lines change only while the order is a draft.The approver agreed to a fixed content.

What Quality does in MxOne

1. 1Add a new mechanic with training and licence
2. 2Grant a company authorization with prerequisite checks
3. 3Suspend, lift and renew an authorization
4. 4Issue a one-time authorization to a contract mechanic
5. 5Watch the two expiry warnings before signing stops
6. 6Raise an audit finding, have its owner answer, and close it

Rules MxOne enforces, and why

• The authorization is checked at every signature, not at login.Entitlement changes; the signature must be true at the moment it is made.
• A suspended, revoked or expired authorization stops signatures at once.No gap between Quality's decision and its effect.
• A certifying licence from another regulator than the aircraft's does not pass.A release is made under the rules of the state of registry.

What supervisors and planners do in MxOne

1. 1Build and publish a station roster from repeating patterns
2. 2Take a leave request from request to approval, and see the gap in the roster
3. 3Record attendance in UTC, with worked hours and overtime
4. 4Check who is on shift and whether they can do the work
5. 5Read labour hours from work cards and utilisation

Rules MxOne enforces, and why

• One shift per person per day.A person cannot be counted in the cover of two shifts or two stations.
• Nobody can be rostered on a day of approved leave.The roster must never promise a person who is absent.
• Leave type and reason are shown only to the person and to approvers.The roster needs the absence, not its cause.

What the administrator does in MxOne

1. 1Set up a new employee with roles scoped to their station
2. 2Handle a forgotten password, a locked account or a forgotten sign-off PIN
3. 3Remove a leaver, and bring someone back with access decided again
4. 4Issue an API token for another system
5. 5Change a parameter and see what it does
6. 6Find out why a job or an interface message did not run

Rules MxOne enforces, and why

• Administrators cannot remove their own administrator role or lock themselves out.The last administrator must not lock everybody out with one click.
• A role that people hold cannot be deleted.Nobody loses access without a decision per person.
• A reactivated user gets no role back.Access is decided again, role by role.