MAINTENANCE
From the maintenance requirement to the release to service.
One data graph carries airworthiness, planning, execution and logistics. Nothing is bolted on through an interface: what airworthiness decides blocks the release to service, and what a work order consumes leaves the stock.
The aircraft comes back from a sortie. Its counters have moved on: the wing counts in cycles, the engine in hours, the rest by calendar. One limit has just fallen.
- WingStructural life: it runs for the life of the part and never reopens.cycles1,480 cyclessince entry into service
- Canard foreplaneTwo limits run in parallel. The last flight used up the hours, and that is the one that rules.flight hourslimit reachedsince last accomplishmentcalendar9 monthssince last accomplishment
- EngineA serialised component: it carries its counters and its due date from one aircraft to the next.flight hours310 hsince last shop visit
What is due becomes a work package, and the package becomes orders: a preventive one from the programme, a corrective one entered by hand. The rest waits its turn.
- Work packageReferenceWP-2026-0147AircraftRafale B — 301KindMixed: preventive and correctiveWorkshopHangar 2Planned date14 April
- 1.00 mRadomenot taken · 4 months leftIts calendar limit is not due. It stays on the due list: a package is a decided scope, not everything that is coming up.
- 5.85 mCanard foreplaneWO-241 · preventiveThe reached limit becomes a dated task. Its operations and materials are copied from the programme, then frozen.
- 13.69 mEngineWO-242 · correctiveUnscheduled work, entered by hand: the order has no originating task. Its own 310 h limit has nothing to do with it.
- Material forecastWO-241 · preventive6 part numbers, 2 toolsWO-242 · corrective3 part numbers, 1 toolIn the package9 part numbers, 3 tools. Copied from the programme rather than pointing at it: revising it tomorrow does not rewrite today’s work.
The work happens at the bench. Operations are signed off one by one, materials leave the stock, and every action carries its author and its timestamp.
- At the benchOrder in progressWO-242Operations7 signed off out of 9Time booked11 h 20SignatureEvery sign-off carries its author and its timestamp.
- 1.00 mRadomegrounded · calendar runs onThe aircraft is not flying: the hours stop running, the calendar limit does not. On the ground the two kinds diverge.
- 5.85 mCanard foreplaneWO-241 · part removedThe removal is recorded. The component leaves with its counters and its history: they belong to the individual item, not to the position.
- 13.69 mEngineWO-242 · in progressOperations are signed off one by one. Each carries its author and its timestamp, and time spent is booked against the order.
- What movedMaterials6 part numbers left the stock, in the same write as the sign-off. No interface, no overnight batch.Tooling3 checked out, 1 returned — with no stock movement. A tool is not a consumable.RemovalThe canard foreplane returns to stock as repairable.
Before signature the verdict is computed: no obligation open and overdue. The release to service is signed, the counters read at closure, and the aircraft goes back on line.
- Fitness verdictOpen obligationsNoneDerogationNoneWhat would blockAn open, overdue obligation. It must be cleared, or covered by a traced derogation.SignatureRelease to service — 14 April, 17:40
- 1.00 mRadomenot taken · 4 months leftIt is still on the due list. A package consumes only what it took on.
- 5.85 mCanard foreplaneWO-241 · closed · limit reopenedThe accomplished task reopens its due date. It restarts from the counters captured when the package closed — and the cycle begins again.
- 13.69 mEngineWO-242 · closed · limit untouchedThe corrective order is closed. Its 310 h limit has not moved: the package never took it on.
- Back on the lineCountersCaptured at closure. Due dates restart from that snapshot, not from today's date.PackageClosed. The orders it carried are cleared.AircraftRafale B — 301, fit for service.
WHAT THE MODULE COVERS
Six domains, one data model.
Airworthiness
Airworthiness directives, service bulletins, modifications and supplementary maintenance directives share a single pivot. Applicability is resolved per aircraft, and compliance tracked through to closure.
DocumentationFitness for service
Before signature, the workbench shows the verdict: every open and overdue obligation is flagged as blocking. It must be cleared, or covered by a traced derogation.
DocumentationMaintenance programme
Periodic tasks, life limits and calendar deadlines. Due dates are computed at aircraft and installed-component level, and materialised on write rather than recomputed on display.
DocumentationPlanning and execution
Due dates feed work preparation; execution happens at the bench. Work orders and repair orders share the same operation mechanics: materials consumed leave the stock, tooling is reserved, time is booked against the job.
DocumentationComponent lifecycle
Removal, installation, breakdown of an assembly, applied configuration. A serialised component carries its history and its counters from one aircraft to the next.
DocumentationFleet status
Situation of each aircraft, upcoming deadlines, groundings. Equipment is tracked by an equipment number that stays fixed for the whole life of the item.
Documentation
NEXT STEPS
Let's see what it looks like on your fleet.
A 90-minute demo over video: product walkthrough, technical Q&A, review of your constraints. Tell us your context and we will tailor the session to it.
Or write to us directlycontact@envergure.cloud