Selecting tasks for performing opportunity maintenance and assigning them to an execution document
In this page, you can select the tasks for performing opportunity maintenance in a visit package. Tell me more
Select the “Select Tasks for Perform Opportunity Maintenance” link in any of the following pages
Record Aircraft Maintenance Execution Details page in the Aircraft Maintenance Execution.
Review Aircraft Maintenance page in the Aircraft Maintenance Planning component.
The system displays the following:
Date Format |
The format in which the date fields are displayed, 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 “Aircraft Details” group box:
Aircraft Reg # |
The registration number of the aircraft. |
Aircraft Model # |
The model number to which the aircraft belongs. |
Execution Doc. Type/Ref. |
The type of the execution document, which could be "Aircraft Maintenance Execution (AME)”, “Component Work Order” or “Hangar Work Order”. |
Primary Work Center # |
The code identifying the work center where the visit package is executed. |
Enter the following fields in the “Search Criteria” group box, to search for the pending tasks.
Maintenance Item |
Use the drop-down list box to retrieve specific tasks for which you want to initiate opportunity maintenance. The drop-down list box displays the following: Block Items, Non-Block Items, Scheduled Items, Component Removal, Discrepancies, Eng. Docs, Planning Drop-Outs, Exe. Drop-Outs and, Short Term Esc. Enter the task # in the field located alongside to retrieve details of a specific task alone. You can also specify multiple values in the input box using separators, such as “,”, “;” and ”*”. |
Date From/To |
The start date of the period for which you want to retrieve tasks Date Format) in the first input box (Date Format). The end date of the period for which you want to retrieve in the second input box (Date Format). The system retrieves those forecasted tasks with “Pending” job status that are planned or scheduled in the period between these two dates. By default, Date From/To dates appear as follows,
The system gives precedence to the planned date of task over its schedule date. This implies that the scheduled date of a task is taken into consideration only if the planned date of the task is not available. |
Note: Ensure the value entered is greater than the “Date From” value. The dates are considered, either in GMT or local time, based on the options set in the “Time Zone” systems parameter.
Rem. Value<= |
The remaining days/ flight hours/ flight cycles for forecasted tasks for execution on the aircraft. Ensure that the value entered here is positive. Use the drop-down list box to select the unit of measurement, which is provided alongside. The drop-own list displays “Days” as well as all pre-defined consumption parameters. The system retrieves all those forecasted but pending tasks with the remaining days/ flight hours/ flight cycles less than or equal to what you specify here. |
Part # |
Use the drop-down list box to select the part type of the component on which maintenance must be done. The system displays the following options: “Engine", "APU", “Landing Gear" and "Others". You can type the part number reference of the component in the box provided alongside. The part number must match with the selected part type. The system retrieves tasks with the “Job Type” as “Component Removal”, “On-Wing”, or “Off-Wing”. All “Pending” and “Deferred” for the components of the part you select here. Discrepancies associated with components with the part reference are also retrieved by the system. |
Search On |
Use the drop-down list box to select the basis for searching tasks for opportunity maintenance. The drop-down list box displays the following: Task Desc., Trig. Param, Zone #, Position Code, Serial #, MCR#, ATA#, Elapsed Time (Hrs.) <= and, Deferral Type. |
Additional Search By |
Use the first drop-down list box to select the additional basis of identifying tasks for opportunity maintenance. The drop-down lit box displays Task Type, Task Category, Exe. Phase, Exe. Type, Eng. Doc Type and Work Center #. |
Select the following check boxes under “Include”.
All |
Select the check box to display all the “Maintenance Events” in all the Active maintenance programs of the aircraft reg #. |
As Required |
Select the check box to display the Tasks which are identified with “Program Item Type” as “As Required” in all the Active Maintenance Programs of the Aircraft Reg # and attached components. |
Click the “Search” pushbutton, to retrieve all the tasks based on the search criteria.
The system displays the following in the “Unassigned Work Unit Details” multiline:
Task # |
The work unit retrieved by the system. |
Part # |
The part number of the component on which the maintenance activity to be performed |
Serial # |
The serial number of the component on which the maintenance activity to be performed. |
Position Code |
The position in the aircraft where the maintenance activity is performed. |
Job Type |
The job type of the work unit such as “Component Removal”, “Aircraft” “On Wing” etc. |
Maintenance Type |
The type of the maintenance work, such as overhaul, repair, inspection and others, to be performed on a component. |
Schedule Date |
The date / time at which the maintenance activity is scheduled on a component. |
Latest Schedule Date |
The latest date / time beyond which the maintenance activity cannot be postponed. |
Est. Elapsed Time |
The estimated elapsed time of the work unit. |
Time Unit |
The unit of measurement for the elapsed time, which could be “Minutes”, “Hours” or “Weeks”. |
Parent Task # |
The initiating task that triggers the task. Typically, a parent task is the task with which another task shares Block, Concurrent Execution – Group, Concurrent Execution – Specific or Concurrent Execution – Conditional relationship. |
Relationship Type |
The type of relationship of the task with the parent task, such as Block, Concurrent Execution – Group, Concurrent Execution – Specific, Concurrent Execution - Conditional. |
Part Available Qty |
The total number of the part In serviceable condition at warehouses. This field is relevant for component replacement jobs only. |
Work Center # |
The code identifying the work center where the maintenance activity is to be performed. |
Est. Man Hrs. |
The estimated time, in man hours, for performing the work unit. |
ATA # |
The ATA # of the task or discrepancies. |
Rem. Days |
The number of days remaining before the forecasted arising of the pending tasks. Remaining Days = Scheduled Date – Current Server Date The Remaining Days is displayed based on the Process Parameter “Next Due computation logic” defined in the “Define Process Entities activity of the “Common Master” business component. For example, consider that the difference of the NSD and Current Date & Time is 2 days, 2 hrs and 15 min.
|
Rem. FH |
The number of flying hours remaining before starting the scheduled maintenance activity. The system displays the number of remaining flying hours based on the value selected in the “Time Display Format” field, in the “Aircraft” business component. For example, if the Time Display Format is selected as “HHMM” and if the stored value is 2.50, the system automatically converts the value from 2.50 to 2.30 and displays the value as 2.30. |
Rem. FC |
The number of flying cycles remaining before starting the scheduled maintenance activity. |
Triggering Parameter |
The code identifying the parameter, which triggers the scheduled maintenance activity. |
Rem. Value |
The triggering parameter value remaining before the forecasted arising of the pending task. Remaining Value = Scheduled Value – Current Value |
Plan Start Date |
The starting date / time planned for the scheduled maintenance activity. |
Plan End Date |
The ending date / time planned for the scheduled maintenance activity. |
Source |
The origin of the task, which could be Aircraft Forecast, Component Forecast, Eng. Doc. or Discrepancy. |
Eng. Doc. # |
The engineering document reference of the task. |
MCR # |
The MCR reference of the task. |
Task Desc. |
The short name/description of the task. |
Work Center Description |
The textual description of the work center. |
Component # |
The code identifying the component on which the maintenance is to be performed. |
Execution Type |
The execution type of the work unit, which can be “Major” or “Minor”. The system retrieves all the records with execution type as “Minor”, if the “Job Type” field is selected as “Component Replacement” |
Forecast # |
The number of the forecast based on which the work unit is forecasted. |
Short Term Esc. # |
The short term escalation number for the task, if it has been escalated. |
Select the following.
Work Center Capability Check |
Use the drop-down list box to specify whether work center capability check for executing the task is required or not. The system lists the options, “Required” and “Not Required”.
The system allows you to assign the task to the execution document only if one of the above is true. The system displays “Not Required”, by default. |
Check the box in the “Select” column of the multiline, to select the work unit to assign it to a visit package/ component work order/ hangar work order/aircraft maintenance execution.
Click the “Assign To Execution” pushbutton, to assign the tasks selected in the multiline to the visit package/ component work order/ hangar work order/aircraft maintenance execution.
Note: The execution documents must be in the following status, if you are to assign tasks and discrepancies .to them:
1. Visit package status: "Draft", "Fresh", "Confirmed", "Released" or "Partly Released”"
2. Hangar Work Order status: "Fresh", "Scheduled" or "In-progress"
3. Aircraft Maintenance Execution status: " Fresh", "Planned”, "In-progress" or "Completed”
If the visit package is in “Released” status, then on assignment of the tasks, the visit package gets revised with its revision number incremented by one and all the latest assignments available. The status of the previous visit package is updated as ‘Revised’.
The system assigns the selected tasks to the visit package/ component work order/ hangar work order/aircraft maintenance execution and changes the status of the tasks to “Assigned” from “Pending” in their respective sources.
The system adds all the related tasks under the Relationship Category-“Execution” to the visit package/ component work order/ hangar work order/aircraft maintenance execution. However, if such a task has already been allocated to the execution document, it does not add the task to the execution document to avoid duplication of the task. A task is also not added to an execution document, if it is in a Conflict relationship with another task already allocated to the execution document.
The system does not associate a task to an execution document, if the task is found in the execution document to avoid duplication. However, such tasks will be added to the execution document, if instances of them exist in"Completed" or Closed" status.
The system allows a predecessor-constrained task to be added to an execution document only if the predecessor/precursor task is in “Allocated” status or already compiled with as indicated in the Compliance History.
If the “Visit Package Approval” parameter is set as “Yes” in the “Set Options” activity of the “Visit Package” business component, the following status change takes place:
If the status of the visit package is “Fresh”, the system retains the status of the visit package and changes the approval status to “Pending Approval”.
If the status is “Confirmed” and the approval status is “Approved”, the system updates the status to "Fresh" and approval status as “Pending Approval”
If the status is “Confirmed” and the approval status is “Pending Approval”, the system updates the status to “Fresh” and the approval status as “Pending Approval”.
If the status is “Partly Released” and the approval status is “Approved”, the system updates the status to “Fresh” and the approval status as "Pending Approval"
If the status is “Released” and the approval status is “Approved”, the system updates the status to "Fresh" and the approval status as “Pending Approval”.
If the “Visit Package Approval” parameter is set as “No”, the system changes the approval status to “Approval Not Required” in the “Visit Package” business component.
If the execution document type is “Hangar Work Order”, the system ensures that,
The job type of the tasks assigned through the opportunity maintenance is the same as that of the tasks already present in the work order, and
The work center associated with the work unit being assigned through Opportunity Maintenance is same as that of work center associated with the hangar work order, or its constituent tasks.
Also, if the job type of the work unit assigned through the opportunity maintenance is “On-Wing” or “Component Removal”, the system ensures that it is for the same component number associated to the work order.
For Off-wing component tasks added to the execution document (visit package/ component work order/ hangar work order/aircraft maintenance execution), the system sets,
The Job Status to “Allocated”.
The Planning Type as “Planned”.
The Job Type to "On-Wing".
For related tasks added to the execution document (visit package/ component work order/ hangar work order/aircraft maintenance execution), the system sets,
The Work Source to “Direct” and Maintenance Type to “Others”, if they are not found in the aircraft/component aircraft/maintenance pending tray.
The Schedule Date, Work Center and Execution Priority as specified in the aircraft/component maintenance program. However, if not specified, values for these attributes are inherited from the parent task.
If the execution document has a customer order reference, updates the customer order with any new task and sets its Planning Status to “Unplanned”.
Restricting ‘Off Wing’ tasks in packages: You can add tasks with job type ‘Off Wing’ to a package, if the process parameter ‘Allow Off Wing Jobs?' under entity type ‘Package Type’ and entity User-Defined Packages or Log Cards in the Define Process Entities activity in Common Master is 1/Yes for the package type. However, the system does not allow for Off Wing tasks in a package, if ‘Allow Off Wing Jobs?' is 0/No.
To proceed, carry out the following
Select the "View Task / Discrepancy Dates & References" link at the bottom of the page, to view details of the work unit selected in the multiline.
Selecting tasks for performing opportunity maintenance – An overview
In this activity, you can associate forecasted pending tasks associated with an aircraft to an execution document. An execution document could be a visit package, a hangar work order or an aircraft maintenance execution. You can also allocate discrepancies that are in “Pending” or “Deferred” status to an execution document.
You may use this activity to perform additional maintenance on an aircraft that is grounded for scheduled maintenance check or unexpected emergency. You may assign related and imminent tasks to an execution document created for regular maintenance to utilize grounding time to the fullest extent. For example, planners /mechanics can add component removals and discrepancies to regular maintenance to an execution document for an aircraft.
You can search for the tasks based on precise filters, such as remaining days before the forecasted arising of the work unit, the execution type of the work unit, short term escalation reference #, block and non-block tasks, execution phase and execution type. You can also use filters, such as work center, execution document and task attribute to retrieve tasks that you want. You can then choose from among the retrieved tasks and assign them to an execution document.
The forecasted tasks that you can assign to execution documents include,
Aircraft tasks
On-wing and Off-wing tasks
Component removal tasks
Note: You can assign component tasks to an execution document only if the component is currently attached to the aircraft.