The Scope Maintenance Visit process consists of the sub processes Perform Due Calculations and Define Maintenance Visit. Following is a description of each sub process:
This sub process handles the different types of due calculations that can be performed. The following activities are included in this sub process:
The calculation of the average historical value is based on the last two months. To avoid unwanted changes to the new historical average, the average for the last two months is then weighted against the previous average by calculating the average of the two. The calculation of the average planned value is based on the month following the average value calculation. Note that the average planned value is only calculated for the primary releasing operational parameter. The calculation of average values for operational parameters will be performed by default on the first day of every month. This will be handled through a background job. It is also possible to manually start the calculation as needed.
This is used to perform the due calculation for the interval maintenance of a given serial. The calculation will be done for the serial, based on the registered average operational value per month and the defined maintenance plan. In addition, the due calculation will create a maintenance event, and calculate the remaining life and drop dead date, for the given serial provided the serial part number is defined as a life limited part and it has reached the days of the forewarning period. The due calculation for a serial will only be done for a maintenance plan connected to an active maintenance program. For a calendar based maintenance plan, where no average operational values exists for the primary operational based parameter, under certain circumstances, there will be only one record calculated for recurring items.
This is used to calculate the due date of the modification or inspection that is to be performed on an assigned serial. The due calculation is performed for each serial based on the average operational value per month, the effective date and the execution intervals (i.e., initial inspections, continued inspections and terminating action) which are defined on the modification.
This is used to view any failed transactions, i.e., when performing due date calculations, caused by background calculations or data transfer.
This is used to change/reset an interval maintenance presented from the due calculation. Either the calendar due date or the due value can be changed. There can be different reasons for changing the due date of a maintenance event. The most common reason is that an event cannot be performed by the calculated due date or value, e.g., due to lack of required materials. In such cases, the authorities can grant a concession for extending the operation for a given period of time. When resetting, the scheduled maintenance event that was manually changed will be retained. When the event is recalculated, the event calculation provides a due date and a due value according to the entry in the maintenance plan for the serial.
This sub process is used to define a maintenance visit prior to the actual visit occurring. During the planning stage of the visit, a maintenance slot can be defined in the system and then as the needs and requirements for the visit are firmed up and established, events can be added and removed from the maintenance order (work package).