Identifying schedules for repetitive procedures

Select the “Identify schedules for repetitive procedures” link in the “Identify Resolution Procedure” page.

The “Identify schedules for repetitive procedures” page appears.

The system displays the following fields:

Date Format

The format in which the date fields appears in this page. This format is displayed from the "User Preferences" business component based on the login user ID. In case the format is not defined, the system displays the date format from the “Enterprise Modeling” business component by default.

The system displays the following field in the “Maint. Report Details” group box:

Maint. Report #	The number identifying the maintenance report selected in the main page.
Applicability	The applicability of the maintenance report, which can be “Aircraft”, “Engine” or “Component”.
Maint. Report Class	The class to which the maintenance report belongs.
Maint. Report Description	The description of the maintenance report.
Record Status	The status of the discrepancy or maintenance report, which can be “Fresh”, “Pending” or “Pending deferral”.
Processing Status	The processing status of the discrepancy, which can be “None” or “Under Analysis”.
Tracking Status	The tracking status of the discrepancy.

The system displays the following field in the “Maint. Object Details” group box:

Aircraft Reg #	The registration number of the aircraft for which discrepancies have been reported.
Aircraft Model #	The model number of the aircraft for which discrepancies have been reported.
Component #	The component number for which discrepancies have been reported.
Part Serial #	The serial number of the part for which discrepancies have been reported.
Part #	The part number for which discrepancies have been reported.
Part Description	The textual description of the part number.

Enter the following fields in the “Schedule Basis” group box:

Schedule Type

Use the drop-down list box to select the schedule type for the discrepancy. The system lists the following options

“Usage Limited” – Select this option if the maintenance report has to be deferred till the value specified for the usage parameter is reached.

“Time Limited” - Select this option if the maintenance report has to be deferred based on the time specified.

“Usage & Time Limited” – Select this option if the maintenance report has to be deferred till the specified time as well as the specified parameter value is reached.

The system sets this field to “Time Based” by default.

Valid on transfer?

Use the drop-down list box and set the field to “Yes” to indicate that the schedule is applicable if the discrepancy is transferred to another maintenance object. Select “No” otherwise.

To define Time Based Schedules:

Enter the following fields in the “Time Based Schedule” group box:

Time Unit	Use the drop-down list box to specify the unit of measurement for the time schedule, which could be “Minutes”, “Hours” or “Days”. The system sets this field to “Days” by default.
Fixed Interval	The period after which the execution of the work unit must be repeated at a fixed time-gap (Numeric). Based on the time unit specified, the system would execute the work unit at the fixed interval specified. However, if you defer the execution at one period, the execution of the work unit will not get deferred for the next period. For example, if you have specified Fixed Interval as 30 days, the system will execute the work unit every 30 days, that is, on 1^st of August, 1^st of September, 1^st of October and so on. If the work unit is deferred in September and is executed only on the 10^th of September, the next work unit execution will take place as planned on the 1^st of October.
Floating Interval	The period after which the execution of the work unit has to be repeated (Numeric). In this case, the execution due date is calculated by adding the value entered here to the date on which the work unit was last executed. For example, if you have specified Floating Interval as 30 days, the system will execute the work unit every 30 days that is, on 1^st of August, 1^st of September, 1^st of October and so on. If the work unit is deferred during September and is executed only on the 10^th of September, the next work unit execution will be performed on the 10^th of October.
Terminating Time	The value after which the work unit need not be executed on the component (Numeric). For example, if you do not want to execute the work unit on the component after 200 days (from the date it was first executed), then enter the value ‘200’ here.
Positive Tolerance	The maximum value within which the work unit must be executed for a specific period (Numeric). Ensure that the value entered is a positive number. For example, if a particular work unit must be executed every 30 days on a component that is, on 1^st of August, 1^st of September, 1^st of October and so on, but you wish to allot an additional 3 days (beyond the 30 days) within which the work unit can be extended. The additional ‘3 days’ is considered as positive tolerance. Thus, as per the example stated, you must enter the value ‘33’ in this field.
Alert Time	The value at which an alert must be raised, indicating that the work unit is going to be executed on the component in the near future (Numeric). For example, if a particular work unit must be executed every 30 days on a component and you wish to be reminded of the execution of the work unit on the 20^th day, enter the value ‘20’ in this field. This indicates that you wish to raise a warning on the 20^th day.
Negative Tolerance	The minimum value from which the work unit can be executed for a specific period (Numeric). Ensure that the value entered is a positive number. For example, if a particular work unit must be executed every 30 days on a component, that is, on 1^st of August, 1^st of September, 1^st of October and so on, but you wish to start the execution of the work unit from the 25^th day itself, enter ‘25’ in this field. This is considered as the negative tolerance.

To define Usage based schedules:

Enter the following fields in the “Usage based schedules” multiline:

Parameter

The parameter of the component for which usage-based schedule must be defined (Alphanumeric, 40).

Help facility available.

Note: Parameters for a component are defined in the “Aircraft” business component.

The system displays the following:

Parameter type	The parameter type of the selected parameter.
UOM	The unit of measurement defined for the selected parameter.

Enter the following:

Fixed Interval	The value after which the execution of the work unit must be repeated at a fixed interval (Numeric). Based on the UOM, the system will execute the work unit at the interval specified. However, if you defer the execution at one interval, the execution of the work unit will not get deferred for the next interval. For example, if you have specified the Fixed Interval as ‘100 hours’ for the parameter “Flight Hours”, the system will execute the work unit every 100-flight hours that is, at 100 hours, 200 hours, 300 hours and so on. Let us assume that work unit was deferred and could be executed only at 210 flight hours. In spite of this, the next work unit execution will take place at 300 flight hours as planned.
Floating Interval	The period after which the execution of the work unit must be repeated (Numeric). In this case, the value at which the work unit must be executed is calculated by adding the value entered here to the value at which the work unit was last executed. For example, if you have specified floating interval as ‘100 hours’ for the parameter “Flight Hours”, the system will execute the work unit every 100-flight hours, that is, at 100 hours, 200 hours, 300 hours and so on. Let us assume that work unit was deferred and could be executed only at 210 flight hours. In this case, the next work unit execution will take place only at 310 flight hours.
Terminating Value	The value after which the work unit need not be executed on the component (Numeric). For example, if you do not wish to execute the work unit on the component after the completion of 1000 flight hours, then enter the value ‘1000’ here.
Positive Tolerance	The maximum value within which the work unit must be executed for a specific period (Numeric). Ensure that the value entered is a positive number. For example, if a particular work unit has to be executed every 100 flight hours on a component that is, at 100 hours, 200 hours, 300 hours and so on, but you wish to allot an additional 10 flight hours (apart from the 100 hours) within which the work unit can be executed. The additional ‘10 hours’ is considered as the positive tolerance. Thus, as per the example stated, you must enter the value ‘110’ in this field.
Negative Tolerance	The value from which the work unit can be executed for a specific period (Numeric). Ensure that the value entered is a positive number. For example, if a particular work unit must be executed every 100 flight hours on a component, that is, at 100 hours, 200 hours, 300 hours and so on, but you wish to start the execution of the work unit from 90 hours itself, enter the value ‘90’ here. This is considered as negative tolerance.
Alert Value	The value at which an alert must be raised, indicating that the work unit is going to be executed on the component in the near future (Numeric). For example, if a particular work unit must be executed every 100 flight hours for a component, and you wish to be reminded that work unit is going to be executed on the component, when the flight completes 80 hours, enter the value ‘80’ in this field. This indicates that a warning will be raised when the flight completes ‘80’ flight hours.

The system displays the following:

Parameter Description

The textual description of the parameter.

Check the box in the “Select” column of the multiline to select the parameter for deletion.
Click the Delete icon in the tool bar above the multiline, to delete the parameters selected in the multiline.
Click the “Record Schedules” pushbutton to store the schedule details entered.
Click the “Confirm Procedure” pushbutton to confirm the resolution procedure and the schedules identified.

Note: This action is workflow-enabled. Notification messages can be sent as per the settings you have defined in the "Workflow Management" business component.

The processing status of the maintenance report, as well as each discrepancy in the report, is updated to “Analyzed”.

Note: The system updates the analyzed date with the current date and the analyzed organization unit with the current organization unit.. The system retrieves all the consumption parameters, based on the option selected for the parameter (HHMM or Decimal Format) in the Aircraft business component while parameter creation.

If the discrepancy/maintenance report is applicable for a “Component”, the system updates the record status of the discrepancies associated to the maintenance report as “Pending”.

When the procedure is confirmed and the resolution type is “Repetitive”, the system does the following:

a) When the discrepancy/maintenance report is applicable for “Aircraft” or “Component”, on confirmation of the resolution procedure, the work units associated to the resolution procedure are appended to the work units existing in the aircraft maintenance program or component maintenance program. The system accepts these work units with only one standard procedure. The maintenance report number and maintenance report are updated as the reference document number and reference document type respectively.

b) when the discrepancy/maintenance report is applicable for a “Component”, the system considers only the floating interval value specified in the time-based and usage-based schedule details of the component maintenance program.

The system displays the following field in the “Record Statistics” group box:

Created By	The name of the user who created the schedule for the repetitive procedure.
Created date	The date on which the schedule was created.
Last Modified By	The name of the user who modified the schedule.
Last Modified Date	The date on which the schedule was last modified.

Identifying schedules for repetitive procedures – An overview

This page allows you to specify schedules for resolution procedures that have to be executed repeatedly at a regular time interval. You can specify a “time-based schedule” or a “usage-based schedule” for the component. You can specify the intervals at which the work unit must be executed. You can also specify the terminating time and alter the time for each schedule.

Prerequisite

“Identify Resolution Procedure” activity. The resolution procedure details must have been recorded in the “Identify Resolution Procedure” page.

What you can do in this page

Specify the schedule type

Define time-based schedule

Define usage-based schedule

Specify the schedule type

Set the “Schedule Type” field to “Usage based” if you want to set usage-based schedules.
Set the “Schedule Type” field to “Time based” if you want to set time-based schedules.