Alarm codes as first-class records
Alarm codes can be imported per technology and validated before they enter the library, so a company works from a reviewed set of codes rather than whatever document happened to be on a shared drive. Each code is linked to its system, subsystem and component, which is what makes the rest of the chain useful.
An incident keeps its alarm reference. When an incident becomes a work order and the work order becomes a maintenance session, the alarm context travels with it, including manufacturer, model, technology and the fault description.
- Alarm library scoped by manufacturer, technology and turbine model
- Import with a validation and review step before codes are published
- System, subsystem and component mapping for each code
- Fault descriptions preserved through incident, work order and session
Diagnosis recorded, not remembered
A maintenance session follows the phases safety, diagnosis, repair, verification, report and knowledge. Diagnostic steps record what was checked, what was measured and what was concluded — including the measurements and photographic evidence that supported the conclusion.
That structure is what makes a resolution reusable. A second technician facing the same alarm on another turbine can read the steps that resolved it, rather than starting from the manual again.
Knowledge that stays with the company
Findings from completed work can be submitted for review and turned into knowledge articles. Knowledge stays company-scoped, alongside engineering documentation and structured knowledge extracted from uploaded documents.
Aerokasix assists the technician here; it does not replace engineering judgement, OEM requirements or approved safety procedures. Safety-critical steps remain governed by the approved procedures and authorised personnel.