Create part transformation (MOD) requirement definitions

Part transformation (MOD) requirement definitions are non-routine, non-recurring requirement definition used to model the work required to modify a part.

1. On your to-do list, click Create Requirement.
2. On the Create Requirement page, provide the required information. Note the following:
   • In the Requirement Type area, select Config Slot if the part transformation applies to a specific configuration slot. Select Part Number if the part transformation applies to all inventory of a specific part number.
   • If you selected Config Slot, select the Assembly and click Select Config Slot to find the appropriate configuration slot.
   • If you selected Part Number, click Select Part to find the appropriate part number.
   • Organization: Select the organization whose users are allowed to modify the requirement.
3. In the Classification area, provide the required information. Note the following:
   • Class: Select MOD (Part Transformation).
   • Workscope: If execution information will be provided in job cards, select This requirement requires a job card for execution. If you plan to include all execution information in the requirement, select This requirement will contain execution information and will not have job cards.
4. In the Scheduling Details area, provide the required information. Note the following:
   • Recurring: Leave this check box blank.
   • Schedule From: Select whether Maintenix is to schedule the requirement starting from the manufactured date of the inventory, the received date of the inventory, or from an effective date. If you select effective date, specify the Effective From Date.
   • Due Date: If you selected an effective date for the requirement, you can optionally set a specific due date.
   • Use Manufactured Date If Later: This check box is visible only for task definitions that are scheduled from the effective date. Select it if you want Maintenix to schedule the tasks based on the manufactured date for inventory that is manufactured after the specified effective date.
   • Min Usage for Release: For part number requirements and those based on a tracked configuration slot, type the percentage value that the usage must exceed before the inventory item, when loose, can be released from maintenance without seeing a warning.
   • Schedule To Latest Deadline: If the requirement has multiple deadlines, you can select this to have Maintenix schedule the requirement at the latest of the deadlines.
   • Min Forecast Range: Type the number of days into the future Maintenix should forecast tasks based on this requirement. Maintenix initializes tasks that are due within their forecast range.
   • Soft Deadline: Select this if the deadline of the tasks based on this requirement can be exceeded without making the tasks overdue in Maintenix.
   • Create/Cancel on Install: Specify whether Maintenix should create a task based on this requirement, or cancel an existing task, when the applicable inventory is installed on an aircraft, or installed on a component other than an aircraft, for example, an engine.
   • Must Be Removed: This option is only visible for requirements defined on a tracked or sub-assembly configuration slot. You select whether the component must be removed for the part transformation work to be completed.
     • If the component does not need to be removed, select N/A.
     • If the component must be removed from its parent component, select Off-Parent.
     • If the component must be removed from its highest assembly, select Off-Wing.
   • Next Shop Visit: This option is visible only when you select both Soft Deadline and either Off Parent or Off Wing. Select Next Shop Visit if the task is one that should not prevent the component from going back into service if the task is not completed by its due date. Maintenix does not automatically create component work packages or create replacement tasks for tasks that have this option selected.
   • Allow Manual Scheduling: Select this check box to allow authorized users to edit the scheduling interval manually on tasks based on this requirement definition, therefore change the tasks due date.
5. In the Applicability area, provide the information requested if you want to restrict the inventory to which this requirement applies:
   • Applicability Range: Type the applicability range—the range or collection of applicability codes that, when assigned to inventory items of an inventory class of aircraft or assembly, make this requirement applicable to the inventory.
   • Applicability Rule: Type the applicability rule. The applicability rule is used for more complex filters.
6. In the Planning Details area, provide the required information. Note the following:
   • On Condition: Select this option if you do not want Maintenix to create tasks based on this requirement, but want the tasks to be created by users only when they are needed.
   • Review on Receipt: This option is visible when you select On Condition. Select this check box if this on-condition requirement should reviewed—to assess whether it should be executed or not—when a new component or aircraft is inducted.
   • Enforce Workscope Order: Select this check box to specify that the job cards included in this requirement must be performed in the sequence in which they are listed in the requirement definition.
7. Provide the information requested in the remaining areas of the Create Requirement page, and click OK.