The engine behind Faultwise | hello@corva.uk
Case study

Faultwise, built on Corva.

Faultwise is a field-service fault-diagnosis workbench for aircraft SATCOM, datalink and cabin-comms — for the engineer on the ramp and for whole operators. It's not integrated with Corva; it is Corva, pointed at avionics. Here's the mapping.

Capability → feature

The same engine, in avionics clothing

Capture → Diagnose

An engineer enters a tail, picks the affected service and LRU, and describes the snag as the crew reported it plus their own read. It's logged under an FW- reference — Corva's capture.

Grounded AI → the diagnosis

Corva retrieves from the operator's own uploaded manuals first, returns ranked causes with confidence, the checks to work in order and suspect LRUs with part numbers — every claim cited. Quick, Partial or Full depth.

Learns → the Log Book

Close a squawk with the real fix and it's embedded into the fault library, weighted above the manuals — the next matching fault is diagnosed from proven history. The Log Book becomes the fleet's memory.

Records → Aircraft & Equipment

The fleet registry ties each diagnosis to a specific airframe; the equipment taxonomy (manufacturers → systems → LRUs, part numbers, services) is the ground truth every answer inherits.

Libraries → Manuals, Software, Screenshots

Per-operator libraries for the PDFs the diagnosis reads first, plus installers, presentations and BITE-screen captures — access-controlled to the right people.

Scope → operators & groups

Each engineer, company or division sees only its own fleet, equipment and fault history; the administrator sees everything. Strict isolation, one platform.

Point the same engine at a support desk, a maintenance operation, a project office or an asset registry, and the features change while the engine doesn't.

What would Corva be, pointed at your work?

If you can describe how your team captures work and what it should reason over, we can shape Corva around it.