← AI Assisted Solver / MRO case study

A worked example using synthetic data estimated from public information. It does not show any specific airline's actual plans or figures.

日本語

Engine planning dashboard

The entry point: annual plan versions and monthly decisions laid over one calendar, with the screen that answers each question. As of 2026-09-28. Figures are synthetic data (unless marked as actual data).

PDCA and OODA: two loops and their screens

PDCA, the planning loop, looks far ahead: it runs the plan and the decision rules through annual plan versions and the monthly meeting. OODA, the response loop, follows the facts and updates the plan only as far as the evidence supports: it acts on the spot through standing rules, without waiting for the meeting. What OODA decided, what it gained or cost, and how long it took to notice are reviewed in the monthly meeting and fed back into the next version’s assumptions and rules. Items without links are screens of the full report that are not in this public version.

Mapping the annual plan to the monthly plan

Bar = period covered by an annual plan version (dark = current version, light = next version). ● = monthly meeting held (grey = scheduled). Number = decision deadlines falling in that month (dark red = 3 or more); Shop visits = engines inducted that month. ◇ = lease return, ▲ = new aircraft delivered (1 aircraft retired). Background shading marks peak seasons and fiscal-year boundaries.

By topic

Assumptions, findings, actions, exceptions and triggers sorted by topic. The meeting runs topic by topic. Colour shows the worst status (red = act now, amber = decide at the meeting, grey = information, green = no issue).

Pages in this report

Screens