Repair management

Engineers create requirements that are used to repair faults and to manage ongoing maintenance related to repaired faults.

Maintenance organizations use the terms non-routine, finding, and discrepancy to describe the discovery of a problem. These problems might be found at different times:
  • During inspections.
  • By the flight crew.
  • While other repairs are being performed.
Maintenix uses the term fault as a synonym of these terms. While faults are not necessarily expected, many of them are known problems that are encountered frequently within a fleet. As maintenance technicians or inspectors find problems, or receive logbook entries from the flight crew, they must raise them in Maintenix as faults, so that the problem can be monitored and resolved.

To resolve a fault, a technician performs a repair. Maintenix allows engineers to define repair procedures, including the various follow-on inspections and/or permanent repairs that will be required. These repairs can be used for both one-time repairs such as an EA (Engineering Authorization), or for frequently used repairs such as those found in the SRM (Structural Repair Manual).

To ensure that follow-on tasks are kicked off after a repair is complete, use the following workflow:
  1. Create a repair reference requirement (REPREF) for a configuration slot.
  2. Create a requirement with the FOLLOW class for the same assembly or for a tracked sub-assembly.
  3. Return to the repair reference. On its Scheduling tab, add one or more Following Tasks. These follow-on tasks have the CRT (Create New) Action on Completion.
When a technician works on a fault with a REPREF selected, if the REPREF links to follow-on tasks, these are displayed when work is captured. When the repair is completed, the specified follow-on tasks are initialized.

For faults that occur frequently, engineers can create non-routine baselines, known as a fault definitions. These fault definitions contain the proper labeling and categorization, as well as links to relevant troubleshooting and corrective actions.

Finally, in integrated systems that use Maintenix and the Diagnostics API, possible faults can be detected by systems on the aircraft and raised automatically in Maintenix so that they are reviewed and addressed by maintenance personnel.