Enter Performed Interval Based Maintenance

Explanation

This activity is used to enter interval based maintenance activities that have been previously performed on the serial structure, but not yet been logged in the system. You can enter this information for both components that have not been logged in the system before, and components that have existing, but not complete, historical data in the system. It is possible to adjust the values that were recently entered so that several records do not appear in the log by mistake. The Component Life/Interval Maint tab displays all possible maintenance activities, not only those for which maintenance events have been created. The maintenance plan controls what is visible in this window for each selected serial. For more information, refer to the online help file Interval Based Maintenance Programs.

You cannot record an overhaul that has occurred between existing operational log records or where the latest operational loggings have not been completed. However, as an exception, you will be allowed to report an overhaul prior to all the recorded operational loggings. It is necessary for all the logging dates of the latest logging to be the same for all operational parameters of the serial before you can report and overhaul from the Component Life window.

Prerequisites

• Interval based maintenance (the maintenance plan) must have been set up for all maintenance groups valid for the part number.

System Effects

• Records are updated as if the maintenance activity had been signed off through a work order, but without work orders being generated.
• An entry will be created for the serial in the interval maintenance history.
• An entry in the serial order history will be added to store the operational values according to ordinary data entry. If this is ordinary maintenance, a record will be added to the maintenance log for the serial. If the maintenance is an overhaul, records will be added in both the maintenance log and the operational log. 

Window

Component Life

Related Window Descriptions

Component Life/Interval Maint

Procedure

This section is divided into different subsections in order to describe the different ways of entering performed interval based maintenance depending on how the maintenance plan has been set up. Each subsection will have a defined scenario containing at least what the maintenance plan looks like. In addition to the maintenance plan, the average operational values (per month) and the current operational log values will influence the result of entering the performed interval based maintenance.

All the different subsections are referred to as different cases:

• Case: Enter Values for Recurring Primary Operational Parameter Interval - No Tolerances
• Case: Enter Values for Recurring Secondary Operational Parameter Interval - No Tolerances
• Case: Enter Values for Recurring Calendar Interval
• Case: Enter Values for Recurring Combined Operational Parameter and Calendar Interval - No Tolerances
• Case: Enter Values for Recurring Primary Operational Parameter Interval - Tolerances Defined
• Case: Enter Values for Recurring Secondary Operational Parameter Interval - Tolerances Defined
• Case: Enter Values for Recurring Calendar Interval - Tolerances Defined
• Case: Enter Values for Recurring Combined Operational Parameter and Calendar Interval - Tolerances Defined
• Case: Enter Values for non-recurring Primary Operational Parameter Interval
• Case: Enter Values for non-recurring Secondary Operational Parameter Interval
• Case: Enter Values for non-recurring Calendar Interval
• Case: Enter Values for non-recurring Combined Operational Parameter and Calendar Interval

Common steps relevant for all subsections

1. Open the Component Life window, and query (F3) for the necessary serial structure.
2. Click the Interval Maint tab, and observe the maintenance codes that appear automatically.
3. For the maintenance event to be logged, enter a value in the Value At Maintenance field for the primary operational parameter in the upper part of the window.
4. In the lower part of the window, enter a value in the Value At Maintenance field for the other operational parameters.
5. Repeat steps 3 and 4 for other maintenance events to be logged.

Common information used by all subsections

• Valid operational parameters:

Case: Enter Values for Recurring Primary Operational Parameter Interval - No Tolerances

• Maintenance Plan (all maintenance codes have 10 days forewarning):

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example: 

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code A.
2. Enter the maintenance date into the Maint Date field.
3. In the Value at Maintenance field enter 3190 (which is the value when the maintenance was performed).
4. In the Value Total field enter 3190 (which is the value when the maintenance was performed).
5. Ensure that value 3200 is automatically populated in the Maint Interval field. This value tells the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
6. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004 is available below. No tolerances have been defined for this maintenance code, which means that all due values are presented from the nominal values from the maintenance plan (in this case 200, 400, 600, etc.):

Case: Enter Values for Recurring Secondary Operational Parameter Interval - No Tolerances

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab as this is a secondary operational parameter:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example: 

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code A1.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's interval defined in a secondary operational parameter, but since the serial also have a value for the primary operational parameter at the time of the maintenance, this must be entered.
4. In the Value at Maintenance (for operational parameter FHR) field enter the actual value at the time the maintenance was performed, for instance 3050.
5. In the Value Total field enter the actual value at the time the maintenance was performed, for instance 3050.
6. Save the record (F12).
7. Find Oper Param LDG in the lower table of the window.
8. In the Value at Maintenance field enter 1450 (which is the value when the maintenance was performed).
9. In the Value Total field enter 1450 (which is the value when the maintenance was performed).
10. Ensure that value 1440 is automatically populated in the Maint Interval field. This value "tells" the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.

• Expected output when the due calculation is executed June 17th 2004 is available below. No tolerances have been defined for this maintenance code, which means that all due values are presented from the nominal values from the maintenance plan (in this case 160, 320, 480, etc.):

Case: Enter Values for Recurring Calendar Interval

• Maintenance Plan (all maintenance codes have 10 days forewarning):

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code A2.
2. Enter the maintenance date into the Maint Date field.
3. In the Value at Maintenance (for operational parameter FHR) field enter the actual value at the time the maintenance was performed, for instance 3125.
4. In the Value Total field enter the actual value at the time the maintenance was performed, for instance 3125.
5. In the Calendar Interval field use the List of Values to select value 150 d. Observe that Calendar Unit is automatically populated.
6. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004:

Case: Enter Values for Recurring Combined Operational Parameter and Calendar Interval - No Tolerances

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters for the secondary operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example: 

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code A3.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's intervals defined in multiple parameters (including calendar time) which means that a value has to be entered for all the intervals using the nominal value. In this particular case it was the LDG interval that triggered the execution of the maintenance.
4. In the Value at Maintenance field enter 3170 (which is the value when the maintenance was performed).
5. In the Value Total field enter 3170 (which is the value when the maintenance was performed).
6. Observe that value 3200 is automatically populated in the Maint Interval field. Change this value to 3800 which is equivalent to the 1520 LDG interval that will be entered later (19 times the initial interval).
7. In the Calendar Interval field use the List of Values to select value 150 d. Observe that Calendar Unit is automatically populated.
8. Save the record (F12).
9. Find Oper Param LDG in the lower table of the window.
10. In the Value at Maintenance field enter 1517 (which is the value when the maintenance was performed).
11. In the Value Total field enter 1517 (which is the value when the maintenance was performed).
12. Ensure that value 1520 is automatically populated in the Maint Interval field.

• Expected output when the due calculation is executed June 17th 2004 is available below. No tolerances have been defined for this maintenance code, which means that all due values are presented from the nominal values from the maintenance plan (in this case 80, 160, 240, etc.):

Case: Enter Values for Recurring Primary Operational Parameter Interval - Tolerances Defined

• Maintenance Plan (all maintenance codes have 10 days forewarning):

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code B.
2. Enter the maintenance date into the Maint Date field.
3. In the Value at Maintenance field enter 3175 (which is the value when the maintenance was performed).
4. In the Value Total field enter 3175 (which is the value when the maintenance was performed).
5. Observe that the value -25 is automatically populated in the Correction Value field. The reason for this is that tolerances are defined, and the maintenance is performed outside the tolerances (20 FHR). This value will ensure that the next occurrence of this maintenance code is due 25 FHR earlier.
6. Ensure that value 3200 is automatically populated in the Maint Interval field. This value "tells" the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
7. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004:

Case: Enter Values for Recurring Secondary Operational Parameter Interval - Tolerances Defined

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab as this is a secondary operational parameter:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example: 

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code B1.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's interval defined in a secondary operational parameter, but since the serial also have a value for the primary operational parameter at the time of the maintenance, this must be entered.
4. In the Value at Maintenance (for operational parameter FHR) field enter the actual value at the time the maintenance was performed, for instance 2950.
5. In the Value Total field enter the actual value at the time the maintenance was performed, for instance 2950.
6. Save the record (F12).
7. Find Oper Param LDG in the lower table of the window.
8. In the Value at Maintenance field enter 1420 (which is the value when the maintenance was performed).
9. In the Value Total field enter 1420 (which is the value when the maintenance was performed).
10. Ensure that value 1440 is automatically populated in the Maint Interval field. This value "tells" the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
11. Observe that the value -20 is automatically populated in the Correction Value field. The reason for this is that tolerances are defined, and the maintenance is performed outside the tolerances (16 LDG). This value will ensure that the next occurrence of this maintenance code is due 20 LDG earlier.

• Expected output when the due calculation is executed June 17th 2004:

Case: Enter Values for Recurring Calendar Interval - Tolerances Defined

• Maintenance Plan (all maintenance codes have 10 days forewarning).

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

Combination 1 - How to enter performed interval maintenance for maintenance plans that have the Cal Int. - Adjust if done Late check box selected:

1. Locate the record with Maint Code B2.
2. In the Maint Date field, enter the maintenance date.
3. In the Value at Maintenance field, enter 3000 (which is the value when the maintenance was performed).
4. In the Value Total field, enter 3000 (which is the value when the maintenance was performed).
5. In the Calendar Correction field, enter -10. Note that this value should always be a negative value since the maintenance has been done late.
6. Save the record (F12).

• Expected output when the due calculation is executed on June 17th 2004:

Combination 2 - How to enter performed interval maintenance for maintenance plans that have both the Cal Int. - Adjust if done Early and Cal Int. - Adjust if done Late check boxes selected:

1. Locate the record with Maint Code B3.
2. In the Maint Date field, enter the maintenance date.
3. In the Value at Maintenance field, enter 3000 (which is the value when the maintenance was performed).
4. In the Value Total field, enter 3000 (which is the value when the maintenance was performed).
5. In the Calendar Correction field, enter 10 and/or -10.
6. Save the record (F12).

• Expected output when the due calculation is executed on June 17th 2004: (Note: The following tables display the expected output when maintenance is done 10 days early and 10 days late respectively.)

Combination 3 - How to enter performed interval maintenance for maintenance plans that do not have the Cal Int. - Adjust if done Early and Cal Int. - Adjust if done Late check boxes selected:

1. Locate the record with Maint Code B4.
2. In the Maint Date field, enter the maintenance date.
3. In the Value at Maintenance field, enter 3000 (which is the value when the maintenance was performed).
4. In the Value Total field, enter 3000 (which is the value when the maintenance was performed).
5. Note that you cannot enter a value in the Calendar Correction field since settings for tolerances (i.e., adjustments when maintenance is performed early or late) has not been defined on the maintenance plan.
6. Save the record (F12).

• Expected output when the due calculation is executed on June 17th 2004:

Combination 4 - How to enter performed interval maintenance for maintenance plans that have the Cal Int. - Adjust if done Early check box selected:

1. Next, locate the record with Maint Code B5.
2. In the Maint Date field, enter the maintenance date.
3. In the Value at Maintenance field, enter 3000 (which is the value when the maintenance was performed).
4. In the Value Total field, enter 3000 (which is the value when the maintenance was performed).
5. In the Calendar Correction field, enter 10. Note that this value should always be a positive value since the maintenance has been done early.
6. Save the record (F12).

• Expected output when the due calculation is executed on June 17th 2004:

Case: Enter Values for Recurring Combined Operational Parameter and Calendar Interval - Tolerances Defined

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters for the secondary operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code B6.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's intervals defined in multiple parameters (including calendar time) which means that a value has to be entered for all the intervals using the nominal value. In this particular case it was the LDG interval that triggered the execution of the maintenance.
4. In the Value at Maintenance field enter 3152 (which is the value when the maintenance was performed).
5. In the Value Total field enter 3152 (which is the value when the maintenance was performed).
6. Observe that value 3200 is automatically populated in the Maint Interval field. Change this value to 3800 which is equivalent to the 1520 LDG interval that will be entered later (19 times the initial interval).
7. Enter value -648 in the Correction Value field. The reason for this is that tolerances are defined, and the maintenance is performed outside the tolerances (20 FHR).
8. In the Calendar Interval field use the List of Values to select value 150 d. Observe that Calendar Unit is automatically populated.
9. Save the record (F12).
10. Find Oper Param LDG in the lower table of the window.
11. In the Value at Maintenance field enter 1502 (which is the value when the maintenance was performed).
12. In the Value Total field enter 1502 (which is the value when the maintenance was performed).
13. Ensure that value 1520 is automatically populated in the Maint Interval field.
14. Observe that the value -18 is automatically populated in the Correction Value field. The reason for this is that tolerances are defined, and the maintenance is performed outside the tolerances (8 LDG). This value will ensure that the next occurrence of this maintenance code is due 18 LDG earlier.

• Expected output when the due calculation is executed June 17th 2004:

Case: Enter Values for Non-recurring Primary Operational Parameter Interval

In this case the use of an overhaul (with cycle) is used. The reason for this is that non-recurring maintenance will only be executed once if not combined with an overhaul in the maintenance plan. Entering values for performed interval maintenance, with or without an overhaul, is exactly the same with the exception that without an overhaul there will not be any due dates calculated.

• Maintenance Plan (all maintenance codes have 10 days forewarning):

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code C.
2. Enter the maintenance date into the Maint Date field.
3. In the Value at Maintenance field enter 1000 (which is the value when the maintenance was performed).
4. In the Value Total field enter 1000 (which is the value when the maintenance was performed).
5. Ensure that value 1000 is automatically populated in the Maint Interval field. This value tells the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
6. Find the record with Maint Code OH.
7. Enter the maintenance date into the Maint Date field.
8. In the Value Total field enter 0.
9. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004 is available below. This maintenance is due 1000 FHR after the next OH:

Case: Enter Values for Non-recurring Secondary Operational Parameter Interval

In this case the use of an overhaul (with cycle) is used. The reason for this is that non-recurring maintenance will only be executed once if not combined with an overhaul in the maintenance plan. Entering values for performed interval maintenance, with or without an overhaul, is exactly the same with the exception that without an overhaul there will not be any due dates calculated.

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab as this is a secondary operational parameter:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code C2.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's interval defined in a secondary operational parameter, but since the serial also have a value for the primary operational parameter at the time of the maintenance, this must be entered.
4. In the Value at Maintenance (for operational parameter FHR) field enter the actual value at the time the maintenance was performed, for instance 1200.
5. In the Value Total field enter the actual value at the time the maintenance was performed, for instance 1200.
6. Save the record (F12).
7. Find Oper Param LDG in the lower table of the window.
8. In the Value at Maintenance field enter 500 (which is the value when the maintenance was performed).
9. In the Value Total field enter 500 (which is the value when the maintenance was performed).
10. Ensure that value 500 is automatically populated in the Maint Interval field. This value "tells" the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
11. Save the record (F12).
12. Find the record with Maint Code OH.
13. Enter the maintenance date into the Maint Date field.
14. In the Value Total field enter 0.
15. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004 is available below. This maintenance is due 500 LDG after the next OH:

Case: Enter Values for Non-recurring Calendar Interval

In this case the use of an overhaul (with cycle) is used. The reason for this is that non-recurring maintenance will only be executed once if not combined with an overhaul in the maintenance plan. Entering values for performed interval maintenance, with or without an overhaul, is exactly the same with the exception that without an overhaul there will not be any due dates calculated.

• Maintenance Plan (all maintenance codes have 10 days forewarning):

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code C3.
2. Enter the maintenance date into the Maint Date field.
3. In the Value at Maintenance field enter 1300 (which is the value when the maintenance was performed).
4. In the Value Total field enter 1300 (which is the value when the maintenance was performed).
5. In the Calendar Interval field use the List of Values to select value 1000 d. Observe that Calendar Unit is automatically populated.
6. Find the record with Maint Code OH.
7. Enter the maintenance date into the Maint Date field.
8. In the Value Total field enter 0.
9. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004 is available below. This maintenance is due 1000 days after the next OH:

Case: Enter Values for Non-recurring Combined Operational Parameter and Calendar Interval

In this case the use of an overhaul (with cycle) is used. The reason for this is that non-recurring maintenance will only be executed once if not combined with an overhaul in the maintenance plan. Entering values for performed interval maintenance, with or without an overhaul, is exactly the same with the exception that without an overhaul there will not be any due dates calculated.

• Maintenance Plan (all maintenance codes have 10 days forewarning). Observe that intervals and operational parameters for the secondary operational parameters are entered in the lower part of the Maintenance Plan/Intervals tab:

• Last Operational Logging:

• Last Performed Maintenance for the maintenance code in this example:

• How to enter performed interval maintenance for this case:

1. Find the record with Maint Code C4.
2. Enter the maintenance date into the Maint Date field.
3. This maintenance code has it's intervals defined in multiple parameters (including calendar time) which means that a value has to be entered for all the intervals using the nominal value. In this particular case it was the LDG interval that triggered the execution of the maintenance.
4. In the Value at Maintenance field enter 1230 (which is the value when the maintenance was performed).
5. In the Value Total field enter 1230 (which is the value when the maintenance was performed).
6. Observe that value 2000 is automatically populated in the Maint Interval field. This value "tells" the application where in the maintenance plan the serial is currently located, and will be the basis for the value of the next maintenance.
7. In the Calendar Interval field use the List of Values to select value 30 months. Observe that Calendar Unit is automatically populated.
8. Save the record (F12).
9. Find Oper Param LDG in the lower table of the window.
10. In the Value at Maintenance field enter 507 (which is the value when the maintenance was performed).
11. In the Value Total field enter 507 (which is the value when the maintenance was performed).
12. Ensure that value 900 is automatically populated in the Maint Interval field.
13. Save the record (F12).
14. Find the record with Maint Code OH.
15. Enter the maintenance date into the Maint Date field.
16. In the Value Total field enter 0.
17. Save the record (F12).

• Expected output when the due calculation is executed June 17th 2004  is available below. This maintenance is due 30 months after the next OH: