Setting up execution inheritance rules for tasks
|
|
|
Select the “Execution Inheritance Rules for Tasks” link in the “Edit Component Maintenance Program Information” page.
The “Execution Inheritance Rules for Tasks” page appears.
The following details are displayed from the previous page.
Eng. Doc. # / Rev. # |
The identification # and revision # of the engineering document comprising the task for which you want to set inheritance rules to be followed during execution. |
Applicability |
The applicability of the engineering document, such as Aircraft or Component. |
EO Status |
The status of the engineering document, such as Fresh, Released, or Returned. |
CMP Revision # |
The revision # of the maintenance program to be executed on the component. |
Status |
The status of the maintenance program to be executed on the component |
Under the “Inheritance Options” group box, select the following:
Rules for |
Use the drop-down list box to select the task for which you want to set rules to be followed during execution. The drop-down list box displays all the Work Unit # from the engineering document. |
The multiline displays the following:
Category |
The category of the inheritance rule. |
Inheritance Option |
The option for the inheritance rule. |
Permitted Value |
The values for the inheritance option from among which you have to select one value. |
Enter the following:
Value Selected |
The value for the inheritance option. |
Error |
A message indicating error in the value specified for the inheritance option. |
Click the “Save” pushbutton to save the rules against the task.
Inheritance Rules Table
Category |
Inheritance Rule |
Permitted Values |
Default Value |
Inheritance of Engineering Tasks |
Auto Inherit Tasks based on rules |
Enter '0' for 'Yes' , '1' for 'No' |
'1' for 'No' |
Auto Inherit task based on Negative Tolerance / Alert values |
Enter '0' for 'Yes' , '1' for 'No |
1' for 'No' |
|
Inherit tasks for parts removed with Removal Type |
Enter '0' for 'Yes' , '1' for 'No |
'1' for 'No' |
|
Inherit tasks for parts removed with Removal condition |
Enter '0' for 'Scheduled' , '1' for 'Unscheduled' , '2' for 'Both' |
'1' for 'Unserviceable |
|
Inherit tasks for parts removed with Removal Reason |
Enter '0' for 'Serviceable' , '1' for 'Unserviceable' , '2' for 'Both' |
'1' for 'Unserviceable |
|
Inherit as One-time task |
Enter '0' for 'Yes' , '1' for 'No' |
'1' for 'No' |
Note: The rest of the Inheritance rules can be set to ‘0’ for ‘Yes’ only if the first rule 'Auto Inherit task based on rules' is set as '0’ for ‘Yes'.
During execution of the Mod engineering tasks on applicable components, their schedules may have to be fixed based on specific attributes of main core parts, such as tolerance and alert values.
The “Execution Inheritance Rules for Tasks” page enables you to set up inheritance rules at specific task level in an engineering document. These rules will empower the system to automatically include sub tasks into maintenance programs on release of the engineering document based on the inheritance rule defined for the task. These rules are most relevant for Mod tasks to be executed on components.