Requirement definitions
Requirements are the standard task definitions used to model maintenance activities. Requirements contain scheduling information, except for requirements created for replacement activities and troubleshooting, which do not require scheduling because they are used only when needed rather than at specific intervals.
You can put the execution steps, part, tool, and labor requirements into one or more job card definitions you associate with the requirement. Alternatively, you can create requirement definitions that include all necessary execution information and that do not have job cards; these are called executable requirements.
When you create a requirement, you select a class. In addition to the following, standard requirement definition classes provided in Maintenix, your organization can create custom classes.
While a requirement is in build status, you can change its class if the requirement has the REQ class or a custom class. You can change the class to a custom class or to REQ class. This is useful if you are duplicating and revising definitions, or for correcting errors made during the build phase.
| Class | Description |
|---|---|
| Replacement (REPL) | Used for the removal of a component, and the installation of another component to replace it, for example, during an overhaul. Replacement tasks change the inventory condition of the removed part, and can change the aircraft configuration information. |
| Part Transformation (MOD) | A non-recurring requirement that involves the modification of a target part group. The part number changes as a result of the modification. |
| Overhaul (OVHL) | A complex series of maintenance tasks that are completed off wing. This is a routine and recurring requirement that resets the Time Since Overhaul (TSO) value of the component on completion. |
| Corrective Action (CORR) | Represents a troubleshooting task associated with a specific fault. The CORR requirement groups all the possible corrective actions to try when attempting to resolve the fault. |
| Discard (DISCARD) | A routine, non-recurring requirement that causes a certificate of destruction to be issued for the target component, which has become unserviceable because it has reached a certain age. Maintenix sets the inventory condition to SCRAP, and does not allow any more work to be performed on the discarded inventory. |
| Repair reference (REPREF) | Represents a repair that can be done by a technician. Repair references are used to model one-time repairs such as EA (Engineering Authorizations) as well as re-usable repairs such as those found in the SRM (Structural Repair Manual) or re-usable EAs. |
| Follow-on (FOLLOW) | Describes work (such as an inspection) that must be performed after a fault is deferred or repaired. Added as Following Tasks on repair or deferral references and initialized when faults are deferred or repairs are completed. |
| Requirement (REQ) | Any type of maintenance requirement that does not fall into the other requirements classes—one that is not a replacement, part transformation, overhaul, corrective action, or discard. This class can be used to group routine and recurring tasks, or unplanned on-condition tasks, such as those required after a lightning strike. |