Entering schedule information for the task
|
|
|
|
This page enables you to enter the schedule information for the selected task. Tell me more
Select the “Edit Schedule Details” link at the bottom of the main page.
The “Edit Schedule Information” page appears.
The system displays the following fields in the “Task Details” group box:
|
Task # |
The task for which the schedule details are to be defined. |
|
Revision # |
The revision number of the task for which the schedule details are to be defined. |
|
Task Applicability |
Indicates whether the task is applicable for “Aircraft”, “Engine” or “Component”. |
|
Base Aircraft Model # |
The number identifying the base aircraft model on which the task can be performed |
|
Task Description |
The textual description of the task. |
|
Schedule Type |
Use the drop-down list box to specify whether the task has to be performed on a “One-Time” or “Recurring” basis. |
Enter the following fields in the “Date Based Schedules” group box:
|
Threshold (Days) |
The maximum number of days within which the selected task has to be performed (Decimal). For a task with both date-based and usage-based schedules, you can specify one of the below-listed,
|
|
Repeat Interval (Days) |
The interval in which the task has to be repeated, in the case of recurring tasks (Decimal). However, for a task with both date-based and usage-based schedules, you can specify one of the below-listed,
|
|
Terminating Value (Days) |
The terminating value specified for the execution of task in terms of days (Decimal). |
|
Limit Basis |
Use the drop-down list box to select the limit basis for picking the Next Schedule Date (NSD) for a task that has multiple NSDs. This situation occurs either when a task has date-based and usage-based schedules or when the usage-based schedule comprises multiple parameters. You must note that the Next Schedule Value (NSV) of each parameter is eventually converted into NSD based on the daily average utilization for scheduling of a task. You must specify the limit basis, if the Schedule Type is “Recurring” for tasks with both date-based and usage-based schedules or if usage-based schedule includes more than one parameter. |
Enter the following in the “Usage-Based Schedules” multiline:
|
Parameter |
A number that identifies the consumption parameter in the aircraft or its component (Alphanumeric, 40). This parameter must be of type “Consumption” 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. Help facility available |
The system fills in the following fields on clicking the “Edit Schedule” pushbutton:
|
Parameter Description |
The description of the parameter. |
|
UOM |
The unit of measurement of the parameter. |
Enter the following fields:
|
Threshold Value |
The maximum number of days or hours within which, the task for the consumption parameter, is to be carried out (Decimal). If the usage-based schedule for a task comprises of many parameters, you can specify threshold value for a minimum of one of the parameters. For a task with both date-based and usage-based schedules, you can specify one of the below-listed,
|
|
Repeat Interval |
The interval in which, the task for the consumption parameter is to be repeated (Decimal). If the usage-based schedule for a task comprises of many parameters, you can specify repeat interval for a minimum of one of the parameters. For a task with both date-based and usage-based schedules, you can specify one of the below-listed,
|
|
Terminating Value |
The value of the consumption parameter based on which the task will be terminated (Decimal). |
Enter the following in the “Notes” group box.
|
Failure Effect |
The effect/result of failure of the task. |
|
Failure Effect Description |
Any additional information on consequences of failure of the task. |
|
Special Frequency Notes |
Any additional remarks or notes pertaining to the periodicity. You can provide supplementary information regarding task frequency when standard frequency or monitoring methods needs additional information. You can also include information to clarify frequency requirements other than a simple parametric or letter check limit. You can also define method of compliance for conditional tasks, shop accomplished tasks, and crew accomplished tasks. |
|
Access Notes |
Any additional information on accessibility of the task. |
|
Aircraft Notes |
Any additional information on the execution of the task on an aircraft. |
|
Engine Notes |
Any additional information on the execution of the task on an engine. |
|
Interval Notes |
Any additional information on repeat interval set for the task. |
Specify the following in the “Update Options” group box.
Note: The “Update Options” group is relevant and hence available only if the Maint. Program Modification” is set to “Allowed” or “With Revision” in the “Set Options” activity.
|
Inherit Schedules to Program? |
Use the drop-down list box to indicate whether task schedules must be updated in the maintenance programs associated with aircraft/components when schedules for the task are modified.
By default, this field is set to “No”. |
|
Inherit Schedules to Program Template? |
Use the drop-down list box to indicate whether task schedules must be updated in the maintenance programs of part/aircraft model when schedules for the task are modified.
By default, this field is set to “No”. |
Check the box in the “Select” column of the multiline to mark the schedule detail for deletion.
Click the Delete icon in the tool bar above the multiline, to delete the schedule details selected in the multiline.
Click the “Edit Schedule” to add or modify the schedule details.
Note the following exceptions
1) If you modify the schedule information of a task in ““Return” status, the system changes the status of the task to “Fresh”.
2) The schedules of tasks are updated in the maintenance programs only if the Prog. Item Type of tasks are Block, Base, Non-Block or To Be Decided.
3) The Schedule Status is reset in the maintenance programs of only those parts, components, aircraft models and aircraft effective for the task.
4) Further, the system resets the Schedule Status only if these maintenance programs are in Fresh, Active or Inactive Status.
Entering schedule information for the task – An overview
This page enables you to enter the schedule information for the selected task. The schedule decides the optimum limits within which the task is to be performed. Schedule can be fixed in terms of calendar duration and or on the basis of one or more consumption parameters (like flight hours / flight cycles). This becomes very important especially for MPD type and CMM tasks.
You can define the schedules based on dates as well as parameters. The schedules could be both one-time as well as recurring. In case one-time date based schedules, you can specify the maximum number of days within which the task has to be executed. In case recurring date based schedules, you can specify the repeat interval in days. In case one-time parameter based schedules, you can specify the maximum value within which the task has to be executed. In case recurring parameter based schedules, you can specify the repeat interval value. Both date based and parameter-based schedules can be defined.
You can also specify the terminating value of task execution in terms of days.
You can also modify the schedules for tasks anytime in future. Further, you can also specify whether changes made to the task must be incorporated in the part/model maintenance programs and component/aircraft maintenance program as well. The system updates the schedule details in the relevant programs and sets the last modified date to the server date.
The system computes the Next Schedule Date and Next Schedule Value for tasks and updates them in the maintenance programs.
Scenario-wise illustration of NSD and NSV
More details on “Inherit Schedules to Program?” and “Inherit Schedules to Program Template?” setting
When the Maint. Program Modification is set to “Allowed” in Set Options activity and “Inherit Schedules to Program?” as “Yes”
If the schedules of tasks applicable to component/engine are modified, the system automatically,
Updates schedules of these tasks in the maintenance programs of those components that are effective for the task and which are in Fresh, Authorized or Inactive Status. However, if the latest revision of a maintenance program is in "Fresh" or "Inactive" Status, the latest as well as the immediate previous revision is updated. If the latest revision is in "Authorized" Status, the system updates the schedule of the task in the latest revision alone.
Updates schedules of these tasks with Job Type as "On-Wing" in the maintenance programs of those aircraft that are effective for the task. However, these maintenance programs must necessarily be in "Fresh", "Confirm", "Return", "Active" or "Inactive" Status. However, if the latest revision of a maintenance program is in "Fresh" or "Inactive" Status, the latest as well as the immediate previous revision is updated. If the latest revision is in "Authorized" Status, the system updates the schedule of the task in the latest revision alone.
If the schedules of tasks applicable to aircraft are modified, the system automatically,
Incorporates the schedule changes of these tasks in maintenance programs of those aircraft, which are effective for the task an which are in Fresh, Authorized or Inactive Status. However, if the latest revision of a maintenance program is in "Fresh" or "Inactive" Status, the latest as well as the immediate previous revision will be updated. If the latest revision is in "Authorized" Status, the system updates the schedule of the task in the latest revision alone.
When the Maint. Program Modification in the Set Options activity is set to “Allowed” in Set Options activity and “Inherit Schedules to Program Template?” as “Yes”
For tasks applicable to component/engine, the system updates schedules in;
Maintenance programs with revision in Fresh, Authorized or Inactive Status of those parts that are effective for the tasks
Maintenance programs with revision in Fresh, Return, Confirm, Active or Inactive Status of those aircraft models that are effective for tasks with Job Type as “On Wing”.
For tasks applicable to aircraft, the system updates the schedules in
Maintenance programs and revision of all aircraft models, which are effective for the task and, which exist in Fresh, Return, Confirm, Active or Inactive status.
When the Maint. Program Modification in the Set Options activity is set to “With Revision”and “Inherit Schedules to Program Template?” as “Yes”
For tasks applicable to component/engine, the system
Creates new revision of maintenance programs of all parts effective for the task with the modified task schedules, if maintenance programs with the latest revision exist in “Active” status. The new revision of maintenance programs are created in “Fresh” Status. Conversely, updates the task schedules in programs with the current revision, if the status of the revisions is "Fresh", "Return", "Confirm" or "Inactive" for all parts effective for the task.
Creates new revision of the maintenance programs with the latest task schedules for all aircraft models effective for the task with Job Type as “On-Wing”, if the status of the latest revision of the maintenance programs is “Active”. The new revision of maintenance programs are created in “Fresh” Status. Updates the schedules of tasks with Job Type set to “On-Wing” in the current revision of aircraft-model maintenance programs, if the status of the revision is one of the following: "Fresh", "Return", "Confirm" or "Inactive".
Similar procedure is followed for tasks applicable to aircraft whenever changes occur in schedules. A new revision of the model maintenance program with the modified task schedules in “Fresh” status is created, if maintenance program with the latest revision exists in “Active” status. However, the system updates the task schedules in the aircraft model maintenance programs with the current revision, if the status of the latest revisions is one of the following: Fresh, Return, Confirm or Inactive.
When the Maint. Program Modification in the Set Options activity is set to “With Revision” and “Inherit Schedules to Program?” as “Yes”
For tasks applicable to component/engine, the system updates
The task schedules in component maintenance programs with the current revision, if the status of the revision is "Fresh", "Return", "Confirm" or "Inactive". Conversely, if the Status of the maintenance programs is "Active", the system creates the nest revision for the task in "Fresh" Status with the schedule updates.
The schedules of tasks with Job Type “On-Wing” in the current revision of aircraft-specific maintenance programs, if the status of the revision is one of the following: "Fresh", "Return", "Confirm" or "Inactive". Conversely, if the Status of the maintenance programs is "Active", the system creates the nest revision in "Fresh" Status with the schedule updates.
For tasks applicable to aircraft, the system uses the same reasoning an updates
The schedules of tasks in the current revision of aircraft-specific maintenance programs, if the status of the revision is one of the following: "Fresh", "Return", "Confirm" or "Inactive". Conversely, if the Status of the maintenance programs is "Active", the system creates the nest revision in "Fresh" Status with the schedule updates.
Scenario-wise illustration of NSD and NSV
Scenario 1: “Initiated/Reset by” = “Self-Compliance” (Please explain the scenario)
The Next Scheduled Date (NSD) computation for date-based schedule tasks
|
Last Performed Date |
Repeat Interval (Fixed or Floating) |
Threshold Interval |
Next Scheduled Date (NSD) |
|
Available |
Available |
Not Available |
Last Performed Date + Repeat Interval |
|
Not Available |
Available |
Not Available |
System Date + Repeat Interval |
|
Not Available |
Not Available |
Not Available |
Blank |
The Next Scheduled Value (NSV) computation for usage-based schedule tasks
|
T1-Parameter |
Last Performed Value |
Repeat Interval (Fixed or Floating) |
Threshold Interval |
Next Scheduled Value (NSV) |
|
FH |
Available |
Available |
Not Applicable |
Last Performed Value + Repeat Interval |
|
FC |
Not Available |
Not Available |
Not Available |
Blank |
|
EH |
Not Available |
Not Available |
If available and greater than Current Parameter Value |
Threshold Value |
|
LC |
Not-Available |
Available |
If available and less than Current Parameter Value |
Blank |
If “Initiated/Reset by” is set to “Related Task”, the system computes the Next Scheduled Date (NSD) as shown in the table below.
Scenario 2: “Initiated/Reset by” = “Related Task”
Note that when the “Initiated/Reset by” is set to “Related Task” for a task, the system computes the NSD and NSV on the basis of the Last Complied Date of the related task. However, if a task has multiple related tasks sharing “Initiate Schedule” relationship, the Last Complied Date of the task that is the latest forms the base for arriving at the NSD or NSV of the task. This is elucidated in the following tables.
Computation of NSD: Main Task: T1, Related Task: T2, Relationship: “Initiate Schedule”
Let us assume that from among the several tasks that share “Initiate Schedule” relationship with T1, T2 has the latest compliance date and hence T2 is used to initiate T1.
|
Repeat Interval (Fixed or Floating) |
Last Complied Date |
Next Scheduled Date (NSD) |
|
Available |
Available |
Last Performed Date of T2 + Repeat Interval |
|
Not Available |
Not Applicable |
Blank |
Computation of NSV: Main Task: T1, Related Task: T2, Relationship: “Initiate Schedule"
|
T1-Parameter |
Last Performed Value |
Repeat Interval (Fixed or Floating) |
Threshold Interval |
Next Scheduled Value (NSV) |
|
FH |
Available |
Available |
Available |
Parameter Value as on Last Complied Date of T2 + Repeat Interval |
|
FC |
Not Available |
Not Applicable |
Available |
Blank |
Scenario 3: Task with a Short term escalation request
Computation of NSD: “Schedule Reset Basis” = “Deferred Value”
|
Last Performed Date |
Due Date |
Repeat Interval (Fixed or Floating) |
Next Scheduled Date (NSD) |
|
Available |
Not Applicable |
Available |
Last Performed Date + Repeat Interval |
|
Not Available |
Not Applicable |
Available |
Blank |
Computation of NSV: “Schedule Reset Basis” = “Deferred Value”
|
T1-Parameter |
Due Date |
Last Complied Value |
Repeat Interval (Fixed or Floating) |
Next Scheduled Value (NSV) |
|
FH |
Not Applicable |
Available |
Available |
Parameter Value as on Last Complied Date of T2 + Repeat Interval |
|
FC |
Not Applicable |
Not Available |
Available |
Blank |
Computation of NSD: “Schedule Reset Basis” = “Actual Schedule Value”
|
Last Performed Date |
Due Date (NSD defined for the task in Aircraft/Component Maintenance Program component) |
Repeat Interval (Fixed or Floating) |
Next Scheduled Date (NSD) |
|
Not Applicable |
Available
|
Available |
Due Date + Repeat Interval |
|
Not Applicable |
Not-Available
|
Available |
Blank |
Computation of NSV: “Schedule Reset Basis” = “Actual Schedule Value”
|
T1-Parameter |
Due Date (NSD defined for the task in Aircraft/Component Maintenance Program component) |
Last Complied Value |
Repeat Interval (Fixed or Floating) |
Next Scheduled Value (NSV) |
|
FH |
Available |
Not Applicable |
Available |
Last Complied Value + Repeat Interval |
|
FC |
Not-Available |
Not Applicable |
Available |
Blank |
Scenario 4: Task with Update Basis (as defined in maintenance programs)
Computation of NSD; Update Basis = “Actual”, “Schedule” or “Time Window”
|
Repeat Interval (Fixed or Floating) |
Last Complied Date |
Next Scheduled Date (NSD) |
|
Available |
Available |
Last Performed Date + Repeat Interval |
|
Available |
Not Available |
Blank |
Computation of NSV; Update Basis = “Actual”
|
T1-Parameter |
Last Complied Value |
Repeat Interval (Fixed or Floating) |
Next Scheduled Value (NSV) |
|
FH |
Available |
Available |
Last Complied Value + Repeat Interval |
|
FC |
Available |
Not Available |
Blank |
Computation of NSV; Update Basis = “Schedule”
|
T1-Parameter |
Last Complied Value |
Repeat Interval (Fixed or Floating) |
Actual Compliance Value |
Next Scheduled Value (NSV) |
|
FH |
Complied before negative tolerance limit or after NSV |
Available |
Available |
Actual Complied Value + Repeat Interval |
|
FC |
Available |
Complied between negative tolerance limit or after NSV |
Available |
Last Complied Value + Repeat Interval |
|
EH |
Available |
Available |
Not-Available |
Blank
|
Computation of NSV; Update Basis = “Time Window”
|
T1-Parameter |
Last Complied Value |
Repeat Interval (Fixed or Floating) |
Actual Compliance Value |
Next Scheduled Value (NSV) |
|
FH |
Complied within negative tolerance and or positive tolerance limits |
Available |
Available |
Actual Complied Value + Repeat Interval |
|
FC |
Available |
Complied beyond negative tolerance an positive tolerance limits |
Available |
Last Complied Value + Repeat Interval |
|
EH |
Available |
Available |
Not-Available |
Blank
|