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
Serial Initialization/Interval
Maintenance tab displays all possible maintenance activities, not
only those for which maintenance events have been created. The maintenance plan
controls what is visible for each selected serial. For more information, refer
to the online help file
Interval
Based Maintenance Programs. Note: It is important to be careful when
registering a start or updated value for a serial, since these values are important
for result calculations like the due date calculation of interval maintenance.
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
Serial Initialization
page.
The different ways of entering performed interval based maintenance depending
on how the maintenance plan has been set up, is described in the following subsections.
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:
Common steps relevant for all subsections
- Open the Serial
Initialization page, and search for the necessary serial structure.
- Click the Interval Maintenance
tab, and observe the maintenance codes that appear automatically.
- For the maintenance event to be logged, enter a value in the Value
At Maintenance field for the primary operational parameter in the upper
list.
- In the lower list, enter a value in the Value At Maintenance
field for the other operational parameters.
- Repeat steps 3 and 4 for other maintenance events to be logged.
Common information used by all subsections
- Valid operational parameters:
Operational Parameter |
Description |
Average Value (per month) |
FHR |
Flight Hours |
50 |
LDG |
Landings |
20 |
- Maintenance Plan (all maintenance codes have 10 days forewarning):
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
A |
200 |
FHR |
- |
- |
200 |
- |
- |
Inspection |
No Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
April 10th 2019 |
3190 FHR |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code A.
- Enter the maintenance date into the Maint Date field.
- In the Value at Maintenance field enter 3190 (which is the
value when the maintenance was performed).
- In the Value Total field enter 3190 (which is the value when
the maintenance was performed).
- 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.
- Save the record.
- Expected output when the due calculation is executed June 17th
2019 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.):
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
A |
3400 |
FHR |
September 15th 2019 |
September 15th 2019 |
September 16th 2019 |
Interval |
A |
3600 |
FHR |
January 13th 2020 |
January 13th 2020 |
January 14th 2020 |
Interval |
- Maintenance Plan (all maintenance codes have 10 days forewarning). Observe
that intervals and operational parameters are entered in the lower list
of the
Maintenance
Plan/Intervals tab as this is a secondary operational parameter:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
A1 |
160 |
LDG |
- |
- |
160 |
- |
- |
Inspection |
No Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
February 10th 2019 |
1450 LDG 3050 FHR
|
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code A1.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance (for operational parameter FHR)
field enter the actual value at the time the maintenance was performed,
for instance 3050.
- In the Value Total field enter the actual value at the time
the maintenance was performed, for instance 3050.
- Save the record.
- Find Oper Param LDG in the lower list.
- In the Value at Maintenance field enter 1450 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1450 (which is the value when
the maintenance was performed).
- 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 2019
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.):
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
A1 |
1600 |
LDG |
August 16th 2019 |
August 16th 2019 |
August 17th 2019 |
Interval |
A1 |
1760 |
LDG |
April 13th 2020 |
April 13th 2020 |
April 14th 2020 |
Interval |
- Maintenance Plan (all maintenance codes have 10 days forewarning):
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
A2 |
- |
- |
150 |
Days |
- |
150 |
Days |
Inspection |
No Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
March 3rd 2019 |
3125 FHR |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code A2.
- Enter the maintenance date into the Maint Date field.
- In the Value at Maintenance (for operational parameter FHR)
field enter the actual value at the time the maintenance was performed,
for instance 3125.
- In the Value Total field enter the actual value at the time
the maintenance was performed, for instance 3125.
- In the Calendar Interval field use the List of Values to
select value 150 d. Observe that Calendar Unit is automatically
populated.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
A2 |
3320 (approx.) |
FHR |
July 31st 2019 |
July 31st 2019 |
August 1st 2019 |
Calendar |
A2 |
3570 (approx.) |
FHR |
December 28th 2019 |
December 28th 2019 |
December 29th 2019 |
Calendar |
- 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 list of the
Maintenance
Plan/Intervals tab:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
A3 |
200 |
FHR |
150 |
Days |
200 |
150 |
Days |
Inspection |
No Cycle |
- |
- |
|
80 |
LDG |
- |
- |
80 |
- |
- |
- |
- |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
April 7th 2019 |
3170 FHR 1517 LDG
|
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code A3.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance field enter 3170 (which is the
value when the maintenance was performed).
- In the Value Total field enter 3170 (which is the value when
the maintenance was performed).
- 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).
- In the Calendar Interval field use the List of Values to
select value 150 d. Observe that Calendar Unit is automatically
populated.
- Save the record.
- Find Oper Param LDG in the lower list.
- In the Value at Maintenance field enter 1517 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1517 (which is the value when
the maintenance was performed).
- Ensure that value 1520 is automatically populated in the Maint
Interval field.
- Expected output when the due calculation is executed June 17th 2019
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.):
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
A3 |
1600 |
LDG |
August 16th 2019 |
August 16th 2019 |
August 17th 2019 |
Interval |
A3 |
1680 |
LDG |
December 14th 2019 |
December 14th 2019 |
December 15th 2019 |
Interval |
- Maintenance Plan (all maintenance codes have 10 days forewarning):
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
B |
200 |
FHR |
- |
- |
200 |
- |
- |
Inspection |
No Cycle |
10% |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
April 8th 2019 |
3175 FHR |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code B.
- Enter the maintenance date into the Maint Date field.
- In the Value at Maintenance field enter 3175 (which is the
value when the maintenance was performed).
- In the Value Total field enter 3175 (which is the value when
the maintenance was performed).
- 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.
- 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.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B |
3375 |
FHR |
August 31st 2019 |
August 31st 2019 |
September 1st 2019 |
Interval |
B |
3575 |
FHR |
December 29th 2019 |
December 29th 2019 |
December 30th 2019 |
Interval |
- Maintenance Plan (all maintenance codes have 10 days forewarning). Observe
that intervals and operational parameters are entered in the lower list
of the
Maintenance
Plan/Intervals tab as this is a secondary operational parameter:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
B1 |
160 |
LDG |
- |
- |
160 |
- |
- |
Inspection |
No Cycle |
10% |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
January 5th 2019 |
1420 LDG 2950 FHR
|
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code B1.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance (for operational parameter FHR)
field enter the actual value at the time the maintenance was performed,
for instance 2950.
- In the Value Total field enter the actual value at the time
the maintenance was performed, for instance 2950.
- Save the record.
- Find Oper Param LDG in the lower list.
- In the Value at Maintenance field enter 1420 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1420 (which is the value when
the maintenance was performed).
- 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.
- 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 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B1 |
1580 |
LDG |
July 17th 2019 |
July 17th 2019 |
July 18th 2019 |
Interval |
B1 |
1740 |
LDG |
March 14th 2020 |
March 14th 2020 |
March 15th 2020 |
Interval |
- Maintenance Plan (all maintenance codes have 10 days forewarning).
Maintenance Code |
Calendar Interval |
Calendar Unit |
Recurring Calculation |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calendar Interval - Adjust if done early |
Calendar Interval - Adjust if done late |
Calculation Rule |
Cycle |
B2 |
150 |
Days |
Yes |
150 |
Days |
No |
Yes |
Inspection |
No Cycle |
B3 |
150 |
Days |
Yes |
150 |
Days |
Yes |
Yes |
Inspection |
No Cycle |
B4 |
150 |
Days |
Yes |
150 |
Days |
No |
No |
Inspection |
No Cycle |
B5 |
150 |
Days |
Yes |
150 |
Days |
Yes |
No |
Inspection |
No Cycle |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
February 1st 2019 |
3000 FHR |
Combination 1 - How to enter performed interval maintenance for maintenance
plans that have the Cal Int. - Adjust if done Late option is enabled:
- Locate the record with Maint Code B2.
- In the Maint Date field, enter the maintenance date.
- In the Value at Maintenance field, enter 3000 (which
is the value when the maintenance was performed).
- In the Value Total field, enter 3000 (which is the
value when the maintenance was performed).
- In the Calendar Correction field, enter -10. Note
that this value should always be a negative value since the maintenance
has been done late.
- Save the record.
- Expected output when the due calculation is executed on June 17th 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B2 |
3255 |
FHR |
June 20th 2019 |
June 20th 2019 |
June 21sr 2019 |
Calendar |
B2 |
3505 |
FHR |
November 17th 2019 |
November 17th 2019 |
November 18th 2019 |
Calendar |
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 options enabled:
- Locate the record with Maint Code B3.
- In the Maint Date field, enter the maintenance date.
- In the Value at Maintenance field, enter 3000 (which
is the value when the maintenance was performed).
- In the Value Total field, enter 3000 (which is the
value when the maintenance was performed).
- In the Calendar Correction field, enter 10 and/or
-10.
- Save the record.
- Expected output when the due calculation is executed on June 17th 2019:
(Note: The following tables display the expected output when maintenance
is done 10 days early and 10 days late respectively.)
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B3 |
3282 |
FHR |
July 7th 2019 |
July 7th 2019 |
July 8th 2019 |
Calendar |
B3 |
3532 |
FHR |
December 7th 2019 |
December 7th 2019 |
December 8th 2019 |
Calendar |
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B3 |
3255 |
FHR |
June 20th 2019 |
June 20th 2019 |
June 21st 2019 |
Calendar |
B3 |
3505 |
FHR |
November 17th 2019 |
November 17th 2019 |
November 18th 2019 |
Calendar |
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 options enabled:
- Locate the record with Maint Code B4.
- In the Maint Date field, enter the maintenance date.
- In the Value at Maintenance field, enter 3000 (which
is the value when the maintenance was performed).
- In the Value Total field, enter 3000 (which is the
value when the maintenance was performed).
- 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.
- Save the record.
- Expected output when the due calculation is executed on June 17th 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B4 |
3271 |
FHR |
June 30th 2019 |
June 30th 2019 |
July 1st 2019 |
Calendar |
B4 |
3521 |
FHR |
November 17th 2019 |
November 17th 2019 |
November 18th 2019 |
Calendar |
Combination 4 - How to enter performed interval maintenance for maintenance
plans that have the Cal Int. - Adjust if done Early option enabled:
- Next, locate the record with Maint Code B5.
- In the Maint Date field, enter the maintenance date.
- In the Value at Maintenance field, enter 3000 (which
is the value when the maintenance was performed).
- In the Value Total field, enter 3000 (which is the
value when the maintenance was performed).
- In the Calendar Correction field, enter 10. Note that
this value should always be a positive value since the maintenance has
been done early.
- Save the record.
- Expected output when the due calculation is executed on June 17th 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B5 |
3282 |
FHR |
July 7th 2019 |
July 7th 2019 |
July 8th 2019 |
Calendar |
B5 |
3532 |
FHR |
December 7th 2019 |
December 7th 2019 |
December 8th 2019 |
Calendar |
- 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 list of the
Maintenance
Plan/Intervals tab:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
B6 |
200 |
FHR |
150 |
Days |
200 |
150 |
Days |
Inspection |
No Cycle |
10% |
- |
|
80 |
LDG |
- |
- |
80 |
- |
- |
- |
- |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Date |
Value |
March 25th 2019 |
3152 FHR 1502 LDG
|
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code B6.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance field enter 3152 (which is the
value when the maintenance was performed).
- In the Value Total field enter 3152 (which is the value when
the maintenance was performed).
- 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).
- 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).
- In the Calendar Interval field use the List of Values to
select value 150 d. Observe that Calendar Unit is automatically
populated.
- Save the record.
- Find Oper Param LDG in the lower list.
- In the Value at Maintenance field enter 1502 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1502 (which is the value when
the maintenance was performed).
- Ensure that value 1520 is automatically populated in the Maint
Interval field.
- 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 2019:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
B6 |
1582 |
LDG |
July 20th 2019 |
July 20th 2019 |
July 21st 2019 |
Interval |
B6 |
1662 |
LDG |
November 17th 2019 |
November 17th 2019 |
November 18th 2019 |
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):
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
C |
1000 |
FHR |
- |
- |
- |
- |
- |
Inspection |
No Cycle |
- |
- |
OH |
4000 |
FHR |
- |
- |
- |
- |
- |
Overhaul |
Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Maintenance Code |
Maintenance Date |
Value |
Comment |
C |
June 1st 2014 |
1000 FHR |
|
OH |
January 1st 2013 |
0 FHR |
This maintenance has never been performed. A starting
point must be set. |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code C.
- Enter the maintenance date into the Maint Date field.
- In the Value at Maintenance field enter 1000 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1000 (which is the value when
the maintenance was performed).
- 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.
- Find the record with Maint Code OH.
- Enter the maintenance date into the Maint Date field.
- In the Value Total field enter 0.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019
is available below. This maintenance is due 1000 FHR after the next OH:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
OH |
4000 |
FHR |
September 10th 2020 |
September 10th 2020 |
September 11th 2020 |
Interval |
C |
1000 |
FHR |
May 3rd 2022 |
May 3rd 2022 |
May 4th 2022 |
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 list
of the
Maintenance
Plan/Intervals tab as this is a secondary operational parameter:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
C2 |
500 |
LDG |
- |
- |
- |
- |
- |
Inspection |
No Cycle |
- |
- |
OH |
4000 |
FHR |
- |
- |
- |
- |
- |
Overhaul |
Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Maintenance Code |
Maintenance Date |
Value |
Comment |
C2 |
June 1st 2015 |
500 LDG 1200 FHR
|
|
OH |
January 1st 2013 |
0 FHR |
This maintenance has never been performed. A starting
point must be set. |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code C2.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance (for operational parameter FHR)
field enter the actual value at the time the maintenance was performed,
for instance 1200.
- In the Value Total field enter the actual value at the time
the maintenance was performed, for instance 1200.
- Save the record.
- Find Oper Param LDG in the lower list.
- In the Value at Maintenance field enter 500 (which is the
value when the maintenance was performed).
- In the Value Total field enter 500 (which is the value when
the maintenance was performed).
- 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.
- Save the record.
- Find the record with Maint Code OH.
- Enter the maintenance date into the Maint Date field.
- In the Value Total field enter 0.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019
is available below. This maintenance is due 500 LDG after the next OH:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
OH |
4000 |
FHR |
September 10th 2020 |
September 10th 2020 |
September 11th 2020 |
Interval |
C2 |
500 |
LDG |
September 10th 2022 |
September 10th 2022 |
September 11th 2022 |
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):
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
C3 |
- |
- |
1000 |
Days |
- |
- |
- |
Inspection |
No Cycle |
- |
- |
OH |
4000 |
FHR |
- |
- |
|
- |
- |
Overhaul |
Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Maintenance Code |
Maintenance Date |
Value |
Comment |
C3 |
September 27th 2015 |
1300 FHR |
|
OH |
January 1st 2013 |
0 FHR |
This maintenance has never been performed. A starting
point must be set. |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code C3.
- Enter the maintenance date into the Maint Date field.
- In the Value at Maintenance field enter 1300 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1300 (which is the value when
the maintenance was performed).
- In the Calendar Interval field use the List of Values to
select value 1000 d. Observe that Calendar Unit is automatically
populated.
- Find the record with Maint Code OH.
- Enter the maintenance date into the Maint Date field.
- In the Value Total field enter 0.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019
is available below. This maintenance is due 1000 days after the next OH:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
OH |
4000 |
FHR |
September 10th 2020 |
September 10th 2020 |
September 11th 2020 |
Interval |
C3 |
1667 (approx.) |
FHR |
June 6th 2023 |
June 6th 2023 |
June 7th 2023 |
Calendar |
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 list of the
Maintenance
Plan/Intervals tab:
Maintenance Code |
Maintenance Interval |
Operational Parameter |
Calendar Interval |
Calendar Unit |
Recurring Interval |
Recurring Calendar Interval |
Recurring Calendar Unit |
Calculation Rule |
Cycle |
Lower Tolerance |
Upper Tolerance |
C4 |
2000 |
FHR |
30 |
Months |
- |
- |
- |
Inspection |
No Cycle |
- |
- |
|
900 |
LDG |
- |
- |
|
- |
- |
- |
- |
- |
- |
OH |
4000 |
FHR |
- |
- |
- |
- |
- |
Overhaul |
Cycle |
- |
- |
- Last Operational Logging:
Operational Parameter |
Last To Date |
Value After Overhaul |
Value Total |
FHR |
May 1st 2019 |
3250 |
3250 |
LDG |
May 1st 2019 |
1560 |
1560 |
- Last Performed Maintenance for the maintenance code in this example:
Maintenance Code |
Maintenance Date |
Value |
Comment |
C4 |
June 19th 2015 |
1230 FHR 507 LDG
|
|
OH |
January 1st 2013 |
0 FHR |
This maintenance has never been performed. A starting
point must be set. |
- How to enter performed interval maintenance for this case:
- Find the record with Maint Code C4.
- Enter the maintenance date into the Maint Date field.
- 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.
- In the Value at Maintenance field enter 1230 (which is the
value when the maintenance was performed).
- In the Value Total field enter 1230 (which is the value when
the maintenance was performed).
- 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.
- In the Calendar Interval field use the List of Values to
select value 30 months. Observe that Calendar Unit is automatically
populated.
- Save the record.
- Find Oper Param LDG in the upper list.
- In the Value at Maintenance field enter 507 (which is the
value when the maintenance was performed).
- In the Value Total field enter 507 (which is the value when
the maintenance was performed).
- Ensure that value 900 is automatically populated in the Maint
Interval field.
- Save the record.
- Find the record with Maint Code OH.
- Enter the maintenance date into the Maint Date field.
- In the Value Total field enter 0.
- Save the record.
- Expected output when the due calculation is executed June 17th 2019
is available below. This maintenance is due 30 months after the next OH:
Maintenance Code |
Planned Value |
Operational Parameter |
Due Date |
Planned Date From |
Planned Date To |
Calculation Type |
OH |
4000 |
FHR |
September 10th 2020 |
September 10th 2020 |
September 11th 2020 |
Interval |
C4 |
1500 (approx.) |
FHR |
February 27th 2023 |
February 27th 2023 |
February 28th 2023 |
Calendar |
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.