Recording schedule information
In this tab, you can define schedules for an engineering document either at applicability / task level or document level. Next Schedule Date / Next Schedule Value (NSD / NSV) computation is done based on ‘Effec. from Date’ of the engineering document. You can also set the ‘Update Basis’ for engineering document task in this tab.
Select the “Schedules” tab in the “Manage Eng. Document” page.
Schedule Details
Enter the following details in the “Schedule Details” section:
Effec. from Date |
The date from which the engineering document is effective. This field must not be left blank. |
Note: This field will be disabled if 'Effective From Date' is applicable at 'Maint. Object Level'.
Select one of the following radio buttons:
Schedule Control Level |
Select one of the following radio buttons to define schedule details for the engineering document:
On selecting “At Eng. Document”, schedules must not be available for “At App. Group” level. By default, the radio button “At App. Group” appears selected. |
Task Identifier
Note: This group box is disabled, if ‘Schedule Control Level’ is set as ‘At Eng. Document”.
Enter the following details in the “Task Identifier” section:
Task # / App. Group # |
The code identifying the task / applicability of the Eng. Doc. #. Mandatory. The system lists the following values in the format ‘Task # :: App. Group #’:
The system defaults the first ‘Task / App. Group #’ value listed in the drop-down box. The system defaults the first ‘Task/App. Group #’ having schedules defined. If no schedules are defined, the system defaults the first value. |
The system displays the following field:
Description |
The textual description of the task. |
Effectivity List |
The system displays all the ‘Active’ 'Maintenance Object' defined for the applicability group #, with 'Applicability' set as "Yes". |
Calendar Schedules
Note: You must define either Calendar Schedules or Usage Schedules.
Enter the following details in the “Calendar Schedules” section:
Time Unit |
Use the drop-down list box to specify the time unit for ‘Threshold’, ‘Repeat Interval’ and ‘Terminating Value’ of date based schedules The system lists the values “Days”, “Months”, “Month End” and “Years”. By default, the system displays “Days”. |
Update Basis |
The mode by which the due dates for executing the task is calculated. The system lists the options “Actual Completion”, “Time Window” and “Schedule”. By default, the system displays “Actual Completion”. This option is not available for Component / Engine applicable engineering documents. |
Alert Value |
The number of days by which the alert date of the engineering document is deferred (Integer). A positive value less than or equal to the Negative Tolerance, must be entered here. |
Threshold |
The interval at which the selected engineering document must be performed (Decimal). A positive value is entered here. |
Threshold Date |
The date on which the engineering document must be performed, in the case of one-time engineering document. (Decimal). If Threshold Date is not available, the system computes it as follows: Threshold Date = Effective from Date + Threshold Value |
Repeat Interval |
The interval in which the task has to be repeated. The repeat interval must be positive and must be equal to or greater than the sum of Positive and Negative Tolerances. |
Positive / Negative Tolerance |
The upper / lower limit within which the engineering document is to be performed (Decimal). Ensure that the number entered in this field is positive. |
Terminating Value |
The terminating value specified for the execution of task. The Terminating Value must be greater than sum of Threshold and Positive Tolerance. |
Terminating Date |
The terminating date specified for engineering document execution. If Terminating Date is not available, the system computes it as follows: Terminating Date = Eff. from Date + Terminating Value. |
Note: Terminating Value or Terminating Date must not be entered for ‘One Time’ schedules.
You must enter 'Threshold' / 'Threshold Date' or 'Repeat Interval', if 'Alert Value', 'Positive / Negative Tolerance', or ‘Terminating Value/ Terminating Date is entered.
If for effectivity Update model program is selected and for corresponding tasks, only Threshold interval is provided for usage based schedules, the system will not allow the user to save data.
Usage Schedules
Note: You must define either Calendar Schedules or Usage Schedules.
Enter the following details in the “Usage Schedules” multiline:
Parameter |
A number that identifies the consumption parameter in the aircraft or its component (Alphanumeric, 40). The system lists all the ‘Active’ Consumption parameters defined in the “Create Parameters’ activity of the “Aircraft” business component. The schedule of the task will be decided based on the values of the consumption parameters. By default, the system leaves the field blank. |
Threshold Interval |
The interval from Eff. from date of engineering document at which the engineering document must be executed for the consumption parameter. Ensure that the number entered here is positive. |
Threshold |
The maximum number of days or hours within which, the engineering document for the consumption parameter, is to be carried out (Decimal). |
Note: 'Threshold' or 'Interval' must be entered, if 'Parameter' is available and vice-versa.
Repeat |
The interval in which, the engineering document for the consumption parameter must be repeated (Decimal). A positive number equal to or greater than the sum of Positive and Negative Tolerances must be entered here. |
Positive |
The upper limit within which the engineering document is to be performed (Decimal). Ensure that the number entered in this field is positive. |
Negative |
The lower limit within which the engineering document is to be performed (Decimal). Ensure that the number entered in this field is positive. |
Alert |
The number of days by which the alert date of the engineering document is deferred. A positive value less than or equal to the Negative Tolerance, must be entered here. |
Terminating |
The terminating value specified for the execution of task. A positive value must be entered here. You must not enter Terminating Value for ‘One Time’ schedules. |
Enter the following below the multiline:
Revision Comments |
Any remarks entered during revision of the engineering document. You must enter the revision comments, if the selected Eng. Doc. # is in 'Released' status and the screen is in 'Revise' Mode. |
To proceed
Click the “Save” pushbutton to update the schedules details for the engineering document.
Note: The system displays an error message, if any concurrent user attempts to modify the schedules of Eng. Doc. # and Revision #.
The system performs the following on clicking the “Save” pushbutton.
If the 'Schedule Control Level' is set as ''At App. Group'', the system saves all the schedule details at "Task # / App. Group #" level for the Engineering order #- revision # combination in header.
If the 'Schedule Control Level' is set as ''At Eng. Document'', the system copies schedules and all available attributes to applicable Task # - Applicability group # level.
Allows the user save the schedule details based on the screen mode (Create / Edit / Revise) and the status of the Eng. Doc. This explained in the table below:
Screen Mode |
Status of Eng. Doc. # - Rev. # |
The system performs the following: |
Edit |
Fresh |
Allows the user to save the schedules details. |
Released |
Does not allow the user to save the schedules details. |
|
Revise |
Fresh |
Does not allow the user to save the schedules details. |
Released |
Allows the user to save the schedules details. Note: On successful save, the system increases the revision # of the document by 1 and flips the radio button to "Edit". |
Impact of schedule modification of already initialized tasks in the Initialize Eng. Doc. Schedules activity is decided by the process parameter “Allow Initialized Schedule Update from Schedules tab“ under entity “All Eng. Doc.” of the entity type Eng.Doc. Type” in the Define Process Entities activity. if the revision of the eng. document is Zero and, if the task has already been initialized, the system behavior would be as explained below:
Process Parameter value |
System behavior |
0/No |
Does not update task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
1/Yes |
Updates task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
Further, the system behavior in various scenarios in conjunction with Action on Revision is illustrated in the below table.
Process Parameter value |
Action on Revision |
Schedule Type |
Complied? |
System behavior |
0/No |
Carry over compliance |
One Time |
Yes/No |
Does not update task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
1/Yes |
Carry over compliance |
One Time |
Yes |
Does not update task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
1/Yes |
Carry over compliance |
One Time |
No |
Updates task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
0/No |
Carry over compliance |
Recurring |
Yes/No |
Does not update task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
1/Yes |
Carry over compliance |
Recurring |
Yes/No |
Updates task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
0/No |
Re-comply |
One Time/Recurring |
Yes/No |
Does not update task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
1/Yes |
Re-comply |
One Time/Recurring |
Yes/No |
Updates task schedule changes in the “Initialize Eng. Doc. Schedules” activity. |
Click the ‘Delete’ icon in the multiline to delete the records in the multiline.
Select the “Initialize Eng. Doc. Schedules” link to initialize engineering document schedules.
To proceed further
Select the “Main” tab to create / edit revise an engineering document.
Select the “Effectivity” tab to defined effectivity details.
Select the “Tasks” tab to define task details.
Select the “References” tab to define reference details.
Select the “More Information” tab to record additional details like cost details, warranty details for the engineering document.