Impact on part and component maintenance programs of limited life parts of type component based on retire task
Scenario1: Part program exists for the part
If maintenance program exists for a part without a retire task, the system updates the part program with the retire task details in the following way:
If the part program exists in “Fresh” status, the latest revision of the part program is updated with the retire task details an, the program retains its status.
If the part program exists in “Active” status, the retire task details are updated in the next/new revision of the part program. The new version of the part program is then activated automatically by the system.
If the part program exists in both “Fresh” and “Active” statuses, the retire task details are updated in both revisions of the part program.
The attributes of the part program are updated as follows
Work Unit#: Retire Task#
Maintenance Type: Retire
Program Item Type: Non-Block
Initiated/Reset By: Self Compliance
Schedule Status: Active
Execution Facility: as specified in the Maintenance info for Part page.
Work Center #: as specified in the Maintenance info for Part page.
Time Unit: UOM specified for the "Retire Task #" in the Maintenance Task component
Est. Duration : Est. Elapsed Time specified for the "Retire Task #" in the Maintenance Task component
On-Wing: No
Comments: "Auto Retire Task”
Based on the details of parameters set as life parameters and/or Ultimate Life (Days), the system updates the component maintenance program in the following way:
Creates usage-based schedules for those parameters that are set to Life Parameter = “Yes”.
Sets Schedule Type to “One Time”
Sets Threshold Value to “Ultimate Life Value”
Creates-date-based schedule, if Ultimate Life (Days) is available.
Sets Schedule Type to “One Time”
Sets Threshold Value to “Ultimate Life (Days)”
Sets UOM to "Days".
Note: If no parameter is set to be life parameter, the system does not generate any usage-based schedule. Similarly, if Ultimate Life (Days} is not specified, date-based schedule is not created for the task in the component maintenance program
Scenario2: Part program does not exist for the part
However, if a part program does not exist for the part, the system creates a program with the attributes of the retire task as explained in Scenario1. In addition, the system sets the following attributes in the part program.
Parent Removal as "Not Required".
ATA#, Maintenance Process and Replacement Type for the part as defined in the Part Administration
On creation, the status of the part program is updated as follows:
“Fresh”, if “Restoration” task is not available for the part
“Active”, if “Restoration” task is available for the part
The system also creates component maintenance program in “Authorized” status for all components of the part based on the part program, if its status is “Active”. Date-based and usage-based schedules are created in the component maintenance program in the same way as explained in Scenario1.