Recording historical maintenance

You can capture historical maintenance by recording or editing technical incidents and faults after they have occurred, or by recording tasks and work packages after completion.

Recording historical tasks

You can record maintenance tasks after they have been completed using one of the following methods:

  • Create a work package and assign the tasks to the work package. Then, carry out all required steps for its completion:
    • Schedule the work package
    • Start the work package
    • Complete the tasks
    • Complete the work package
  • Use the Package and Complete functionality which automatically creates a work package, adds the selected tasks to the work package, and completes both the tasks and the work package, unless there are conditions that prevent the completion. This functionality provides a fast way to complete open tasks. Also, you do not have to assign labor to each labor line on a job card, and then complete each labor line for each task.

  • Use the Create Historical Task functionality to create a historical task and assign the task to a work package. When you are creating historical tasks, applicability rules and transformation rules are enforced for tasks based on part numbers and are ignored for tasks based on configuration slots.

With each of these methods, you must specify the date and usage of the performed work package. There are two ways to record this information:

  • Using the Start Work Package button or the Package and Complete button, you can open the relevant tabs and enter a start date without specifying usage at completion. In this case, Maintenix automatically calculates the usage on the work package, and every task within the work package. In addition, Maintenix automatically calculates the correct usages on the components that were installed and removed during the work package. Removed components' usage is rolled back, and installed components' usage is rolled forward, if the aircraft took flight between the time the work was completed and the time each task was recorded. This includes test flight and bench test usage accruals that occur within the life of the work package.
  • Using the Start Work Package and Enter Usage button or the Package and Complete and Enter Usage button, you can enter the start date and manually enter the usage at the time of repair of the inventory item (the usage is defined as hours and cycles for the root assembly and any sub-assemblies). Components removed and installed will have usage adjustments according to these values. For future out-of-sequence usage accruals, Maintenix will not adjust the usage for the work package or the tasks in it. To indicate that these usage values will not be automatically adjusted in the future, Maintenix adds a comment to the completed task and work package usage snapshots stating that the usage values were manually entered.

Editing the details of technical incidents

Any action taken in the case of a reported or observed failure or malfunction of an airframe, engine, propeller, or appliance that is critical to the safety of a flight must be recorded in the aircraft's maintenance log. You can record these actions in Maintenix as a flight safety impact either at the time when you create the fault for the technical incident (on the Raise Fault page) or at a later date, when the fault has been in the system for some time.

You can also edit some of the details of an existing fault. For example, you can specify an ATA chapter different from the chapter that was originally recorded as a resolved system.