Recording aircraft maintenance execution details

• Select the “Record Aircraft Maintenance Execution Details” link under the “Aircraft Maintenance Execution” business component.

The “Record Aircraft Maintenance Execution Details” page appears.

• Enter the following field in the “Execution Record Details” group box:

On entering the “Aircraft Reg #”, the “Open Items” section displays the total number of individual Execution References that are in “Planned”, "In-Progress” and “Completed” status for the specified aircraft.

For offline operations, system shall load the Open Items tree on page launch if an offline Aircraft Reg. # is defaulted in Exe. Details section.

To create a new Aircraft Maintenance Execution Reference

• Enter the following field:

The system displays the following, which you can edit, if required:

Display of Flying Hours and Flying Cycles of aircraft

The system displays the following:

Main Base Operations:

On ‘Enter’ or on clicking ‘Go’, the system displays ‘Flt. Hrs’ and ‘Flt. Cycles’ for the Aircraft Reg # and the Date & Time entered, or the defaulted Date & Time (if the parameter “Default Context Date?” is set as “Required” in the “Common Masters” business component).

Offline operations:

1. On launch of screen, if offline area is mapped to a single aircraft and if the parameter “Default Context Date?” is set as “Required”, the system displays the ‘Flt Hrs’ and ‘Flt. Cycles’ for the defaulted Aircraft Reg # and the context date / time.

2. If offline area is mapped to multiple aircraft, on entering Aircraft Reg # and invoke of ‘Go’, Flt Hrs. and Flt. Cycles will be displayed based on the Date & Time entered or defaulted.

Note: ‘Flt. Hrs’ and ‘Flt Cycles’ values are retrieved from the values of Aircraft parameters mapped to base parameters ‘Flying Hours’ and  ‘Flying Cycles’.

• Click the icon '' to recalculate and display the ‘Flt. Hrs’ and ’Flt. Cycles’ for the ‘Date & Time’ entered / defaulted and the Aircraft Reg #, for both main base and field base operations.

To search & sort Execution References

• Enter the following in the “Search Options” group box:

Note: Sorting is not applicable for the “Open log cards” tree structure.

• Click the “Go” pushbutton to retrieve the search and sort results.

Next Steps

In this section, you can view the list of possible actions to be carried out when performing each task in the page. Few examples are listed below:

‘Show Due Tasks’ Tree

• Click the ‘’ in the “Open Items” tab to view the tree structure displaying the due tasks as nodes with check boxes.

Note: The display of Tree structure is dependent on the definition of the process parameter "Restrict display of Package and Unprocessed Discrepancies in AME Tree based on access rights" under the entity type Package Type and the entity “All Packages“ in the Define Process Entities activity of Common Master in conjunction with the access to the system activity “Display Packaged and Unprocessed Discrepancies in AME Tree” activity” as illustrated in the table.

The “Show Due Tasks” tree structure displays the due tasks (tasks that are pending on an aircraft in a given time frame), overdue tasks, discrepancies and overdue discrepancies. The tree displays the following folders:

1. Routine: This node displays all the routine tasks. Tasks having ‘Prog. Item Type’ as “As Required” are also displayed under this node in ‘Blue’ color. All the Off-wing tasks associated to the CR task applicable for a component attached, are also retrieved are displayed under the CR task. These Off-wing tasks are displayed based on the due date. Tasks with earlier due dates are displayed first. Example.

2. Discrepancy: Discrepancies are displayed under the node.

The tree structure is as follows:

Aircraft Reg #

+   Routine

+   Discrepancy

Using the tree structure, you can perform the following:

1. You can select the tasks / discrepancies  in the tree and create a new package.

2. You can select the tasks / discrepancies in the tree and associate it to an existing package.

The tree is loaded with the Tasks (both Aircraft and Component Tasks) which are scheduled for the Aircraft and not yet complied. Tasks with following schedules are displayed.

• Schedule Date between the server date and the Horizon Date*.

• Schedule Date earlier than the server date. (i.e. Overdue tasks)

*Note: Horizon Date = Server Date + Planning Horizon (Days) defined for the Entity “All Packages” in the “Set Process Parameters” page of the “Common Masters” business component.

The tasks are sorted and displayed in the tree as follows:

• The tasks are displayed in the ascending order of their ‘Schedule Date and Time’. Task with the earliest 'Schedule Date and time' must be available in the top.

• Tasks having same Schedule Date are displayed based on their ATA #.

• Tasks having same Schedule Date and ATA #, are displayed based on Task #, in alphabetical order.

• The order in which the tasks to be displayed in Routine folder is as follows:

• 1. Over Due tasks in ‘Red’ color.

  2. As Required tasks in ‘Blue’ color.

  3. Tasks which are due on the current date.

  4.   Tasks which are due on the future date and time. 

Tree Structure:

If the task loaded in the tree has ‘Base-Block’ relationship with other tasks, the Block task is displayed as a parent node and the Base tasks are displayed as child nodes irrespective of the Schedule Date of the Block and Base tasks. For a task, its concurrent related task will not be displayed in the tree.

Note: When you select a parent node in the tree, the child nodes will be automatically selected. You can deselect the desired child nodes, without deselecting the parent node. On clicking the “AME Save” icon, only the selected tasks are assigned to the package.

For routine tasks, the tree structure is as follows:

Aircraft Reg #

            - T1 (Block Task)

                      - T11 (Base Task)

                      - T12 (Base Task)

           - T2 (Non-Block Task)

           - T3 (Non-Block Task)

           - T4 (Component Removal Task)

                    - T41 (Off-Wing Task)

                    - T42 (On-Wing Task)

 Tree Display Format:

1. 'Routine' folder:

The tasks of Job Type “Aircraft” are displayed in the following format:

<Lock Icon> ATA # :: Task # :: Task Desc. :: Trigg. Param. :: Rem. Value :: Sch. Date

The tasks of Job Type "On-wing", "Component Replacement" and "Off-Wing" in the following format:

<Lock Icon> ATA # :: Task # :: Task Desc. :: Trigg. Param. :: Rem. Value :: Sch. Date :: Part # :: Serial #

2. 'Discrepancy' folder:

The tasks of Job Type “Aircraft” are displayed in the following format:

<Lock Icon> ATA # :: Discrepancy # :: Discrepancy Desc. :: Trigg. Param. :: Rem. Value :: Sch. Date

The tasks of Job Type "On-wing", "Component Replacement" and "Off-Wing" in the following format:

<Lock Icon> ATA # :: Discrepancy # :: Discrepancy Desc. :: Trigg. Param. :: Rem. Value :: Sch. Date :: Part # :: Serial #

Note: The ‘Sch. Date’ in the tree structure indicates the Schedule Date converted to the time zone of the Station selected in the “Exe. Details” section.

Note: If the discrepancy is deferred to end of day i.e. the process parameter “Next Due computation logic” is set as ‘End of Day’ in “Common Master” business component, the due date / time of the discrepancies with UTC time ‘23:59’ will be displayed as ’23:59’ without converting to local time, irrespective of the Station selected.

Lock Icon:

Main Base operations:

If ‘Mode of Usage’ of Aircraft is "Offline" in the “Aircraft” business component), the Lock Icon ‘’ is displayed for all the routine tasks and discrepancies in the Main Base (i.e. process parameter 'Usage Mode' is set as "Online" in the 'Configurator' business component). "As Required" tasks will not have a lock icon on it.

Offline Base Operations:

All tasks and discrepancies shall be displayed as unlocked in Remote Base (i.e. 'Usage Mode' is set as "Offline" in the “Configurator” business component).

Creating package / associating task to package:

The system performs the following on creating a package or associating a task to the package by clicking the AME save icon '':

Predecessor Constrained check:

While creating a package and associating a task to the package if the selected Task (T1) have a 'Predecessor Constraint' relationship with any other Task (T2), then ensure that the Related Task (T2) is

• Complied at least once or

• The Related Task is allocated to any other Execution Document, such as Aircraft Maintenance Execution Ref. #, Hangar Work Order or Visit Package, for the same Aircraft.

Conflict Check:

Ensure that none of the selected tasks have ‘Conflict’ relation among them while creating a package. While associating a task to the package, ensure that none of the selected tasks have 'Conflict' relationship with the tasks which are already available in the package in either “Planned”, “In-Progress”, “In-Complete” or “Completed” status.

Duplicate Check:

On associating a task to the package, ensure that the selected task is not already available in the package in either “Planned”, “In-Progress”, “In-Complete” or “Completed” status.

Copy Details:

For the tasks that are added from the tree to the package, the system performs the following:

• Associates the task to the package and copies the task details like Task #, Task Description and ATA # to the “Work Information” section from the “Maintenance Task” business component. If the task that is added has execution relation with other tasks, the execution related tasks are also added to the package.

• Copies the Resource and Sign-Off requirements from the “Edit Resource & Sign-Off Requirements” page of the “Maintenance Task” business component.

• Copies the Part Requirements from the “Edit Part Requirements” page of the “Maintenance Task” business component.

• If the task that is added to the package from the tree is of Job Type “Component Replacement”, the system:

1. 1. adds a node under the “Pending Action Items” folder in the “Component Replacement” section, and updates the details such as Part #, Serial #, Position Code and Level Code.

   2. updates the ‘Source’ as “Remove” and ‘Object Type’ as “Component”.

• Copies parameter reading requirements and conditional evaluational details from the “Edit Parameter Reading / Eval. Form” page of the “Maintenance Task” business component.

• For Offline Aircraft on associating 'Off-Wing' Task (of component maintenance program) to package, the system updates the 'Job Type' as 'On-Wing' and copies the Part # and Serial # of the Component into the corresponding values in 'Component Details' section. For the Part # - Serial # combination, 'Position Code' is retrieved from the Aircraft Configuration if available.

Note: In case aircraft is Online, Off-Wing tasks when added to an A/C Maint. Exe. Ref. Document will have 'Job-Type' as "Off-Wing".

• Enter the following in the “Execution Record Details” group box:

The system displays the following in the “Execution Record Details” group box:

• Enter the following fields:

The system displays the following:

• Enter the following field:

• Enter the following field:

Note: During creation of the Execution RFef #, for the customer owned Aircraft, if only one Customer Order # is available in “Processed” status for the Customer # - Aircraft Reg # combination and if the Ownership of the Aircraft Reg # is “Customer’ then system will default that Customer Order # in the field above. Execution Ref # can be created on performing the following actions: (i) AME save in Execution Record details data cluster. (ii) Discrepancy save in Discrepancy data cluster. (iii) Work information save in Work Information data cluster.

Creation of new AME document:

During creation of a new AME document, if the ownership of the Aircraft Reg # entered is “Customer”, the system performs the following on saving the discrepancy and work information:

• If a Customer Order # is entered in the header, the system ensures that the entered Customer Order # is effective for the Aircraft Reg #.

• If the Customer Order # is not entered, the system pegs the Customer Order # effective for the Aircraft Reg #, if a valid contract # effective for the Aircraft Reg # exists. This pegged Customer Order # is used as reference for creating a new AME document.

• If an effective Customer Order # is not available for pegging, the system auto-generates a new 'Customer Order' based on the process parameter "Auto-Generate Customer Order ?" set for the 'Package Type', to create the AME document.

The following fields are displayed:

• Enter the following field:

The system displays the following:

• Click the “Save Log” icon '', to save the aircraft maintenance execution reference.

The number to the right of the “Open Log List” pushbutton is incremented by 1, to indicate that an additional execution reference has been created for the aircraft.

Note: The system restricts creation of new A/C Maint. Exe. Ref. Documents referring an Offline Work Center (i.e. Work Centers having 'Usage Mode' set as "Offline" in the 'Work Center' business component), if the process parameter ‘Usage Mode’ is “Online” in the “Configurator” business component.

The Doc. Class is updated as “Unplanned”.

The system ensures the following, if the aircraft maintenance execution reference has reference to a customer order to generate a material request with the modified values of “Work Center #” or “Execution Station” field:  

• The Part # - Stock Status combination  must be valid for the customer # defined in the “Customer” business component.

• The Part # - Warehouse combination must be valid for the customer # defined in the “Stock Administration” business component.

The system performs the following on saving the Aircraft Maintenance Execution Reference:

• If the Aircraft Maintenance Execution Reference has a Customer Order # reference and if any work unit is added to the Aircraft Maintenance Execution Reference, the system updates the work units that are part of the Aircraft Maintenance Execution Reference to the reference customer order #. The Customer Order Line # corresponding to each of the work unit # is retrieved and saved in the Aircraft Maintenance Execution Reference corresponding to each of the added work units.

• For each of the work unit # if the Job Type is “Component Removal”, then the system updates the corresponding component # in the “Replace Components” of the “Flight Log” business component.

• Ensure that the work unit details are not modified if the source of the work unit is other than “Direct”.

• If the “Sign Off?” drop-down list is set as “Sign Off” or “Void” and if the “Approval Reqd.?” for the task is set as “Yes” in the “Edit Resource/Sign-Off Requirements” page of the “Maintenance Task” business component, the system ensures the following:

1. 1. The certificates are valid for the Employee # as on execution date of the Execution Reference, for Work unit # - Maintenance object (Aircraft model #) combination as defined in the “Employee Personal Information” business component.

   2. The licenses are valid for Employee # as on execution date of the Execution Reference, for the Skill # - Maintenance Object (Aircraft model #) - work unit # combination as defined in the “Record Employee license information” activity of the “Employee Personal Information” business component.

• Ensure that the License # is in status other than “Suspended” / “Revoked”, as on the date of execution of the Aircraft Maintenance Execution Reference #, in order to void the Sign-off requirements.

• If the Job Type of the work unit is “Component Removal”, then on updating the Execution Status as “Completed” for the work unit, the system ensures that complete component replacement details are recorded for the component # associated with the work unit.

• If the option “COM Reqd?” is set as “Required” for the current Execution Ref # in the “Set Process Parameters” page of the “Common Masters” business component, the system ensures that at least one 'COM #' with the “CoM Type” as “Regular'’ and “Forced” is available in “Confirmed” status for that Execution Ref #.

• If all the Work Units are in “Planned” status, the system updates the status of the Execution Reference # as “Planned”.

• If at least one Work Unit is in “In-progress” status, the system updates the status of the Execution Reference # as “In-progress”.

• If all the Work Units are in any of the terminating statuses (“Cancelled”, “Deferred”, “Incomplete”, “Closed” & "Closed”), the system updates the status of the Execution Reference # as “Completed”.

• If the Doc. Status is selected as “Closed”, the system updates the document status of the Execution Reference # as “Closed”.

• Ensure that the Doc. Status is not set as “Cancelled” if any of the following conditions are satisfied:

1. 1.  Any issue of parts has happened.

   2. Whenever start clock is invoked (either from the current page or from the “Record Employee timesheet” page of “Aircraft Maintenance Execution” business component”)

   3. When Actual Start Date & Time / Actual End Date & Time / Actual Man hrs is updated.

   4. When employee code is entered against any sign-off requirement identified.

   5. When resource consumption is updated with the actual times.

   6. When employee time records are updated

   7.  When parameters values are updated.

   8. When Component Replacement is updated.

• If the Doc. Status is set as “Closed” and if all the tasks available inside the Execution Reference # is in terminated status ("Closed", "Completed", "Cancelled", "Deferred", "Incomplete", "Pre-closed"), the, the system updates the execution status as 'Closed' for those tasks having the current execution status as “Completed”.

• If a non-standard task is added against a Discrepancy # or a Maintenance Report # and if ATA # is not entered against the task, the system copies the ATA # identified against the discrepancy or the Maintenance Report as the ATA # of the task.

• For the selected Aircraft Maintenance Execution Reference-Task #-Sub task-Skill-Resource Group combination, if the sign-off comment exists, the system updates the Sign-Off comments into the Comments History.

Note: The system considers the sign off comments entered in the multiline. If however, no such comment is provided in the multiline, the system defaults the sign off comments provided in the “Default Details” group box.

• For the Work Unit, for all those sub task for which Employee # is valid and effective, the system updates the Last Modified by as the employee code of the Login User and Last modified Date as the execution date. The system also updates the sign-off comments for the work unit.

• If the Expense Type of the Aircraft maintenance Execution Reference is "Capital" and if the current business component interacts with the “Asset Planning” business component, the system updates the Total cost calculated for each Task # and the Execution Reference #, against the CAPEX Proposal # identified for the respective task # and the Execution Reference #.

• If the Execution Reference is in closed or cancelled, ensure that the material request for the remaining quantity is short-closed and the issue docs must be cancelled.

• If the Execution Reference is Package Type the parameter “Automatic pegging of Open Material Requests" is set as "Required" in the interacting Common Masters business component and if a task is added to the Aircraft Maintenance Execution document, the system automatically pegs the MR for that part # of the 'Task #', if the following conditions are satisfied:

• • For any of the part requirements, a Material Request exists with MR Class as "Maintenance" and MR Type as “Unplanned” or “Planned” for the 'Part # -Stock Status - Warehouse’ combination, having Aircraft Reg # same as the Aircraft Reg # of the AME document and not associated to any other execution document.

  • The Reference Doc Type must be identified as "A/c Maint. Exe. Ref #" and Execution Reference # must be left blank.

  • The warehouse to which the Material Request has been raised must be same as the Warehouse mapped to the Task Work Center - Part Type - Issue Warehouse.

  • Part # must be effective for the Aircraft.

• If the Execution Status of the task is updated to “Completed” / “Closed” / “Pre-closed”, the system updates the parameter values recorded against the Aircraft Maintenance Execution Reference, with Execution Ref. # / Line # / Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

• On creation of a new package, system copies the incomplete, overdue and due tasks into the package, based on the parameters set in the “Common Masters” business component. Refer to the section “Addition of Incomplete, Overdue and Due tasks on saving AME, discrepancy and work information” for more details.

• If hold is applied on AME document / Customer Order, and if the process parameter 'Stop A/C Maint. Execution ?' parameter is set as "Yes" for the Hold Code in the “Set Process Parameters” page of the “Common Master” business component, the system does not allow you to create or modify the AME document.

• The system sets Need Date of the material request on the basis of the AME Ref. # referenced task as illustrated in the table

In a situation in which multiple material requests are auto-generated by the system, the requests are consolidated on the basis of Need Date or the serviceable request warehouse of the task work center.

• 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.

• Transferred aircraft: You cannot create a package for an aircraft that has been transferred to another operating unit for maintenance. The system allows for package creation upon return of the aircraft.

Customer order creation

• The system creates a customer order in “Processed” status comprising the package, if the ownership of the aircraft is “Customer”. Further, based on attributes including A/C Reg #, A/C Model #, A/C MSN #, Customer PO # and Customer #, the system determines the relevant contract for the customer order.

• The stock status of the parts required by the package is set to the preferred stock status of the contract. However, if any part is covered by a PBH agreement, the stock status will be set to PBH.

• The warehouses for each of the parts will be the warehouse that is valid for the work center of the package and the part type of the part. However, customer order is automatically generated in Processed status only if the contract status is “Approved”, the contract stage is “Firm” and, the planned/start date of the package pertains to the effective period of the contract.  

Refer to the section “The system performs the following on saving the work information and Execution Reference” for more details.

When the aircraft maintenance execution reference and discrepancy are saved

On saving the Aircraft Maintenance Execution Reference and discrepancy, the system performs the following:

Creates material requests for part requirements of tasks and discrepancies in the package. However, if a deferred discrepancy is added to the package, the system undertakes the following,

• Shortcloses any “Authorized” material requests associated with the previous package for such discrepancies, if related stock issues have not been confirmed yet. The system does not shortclose those material requests, that have “Confirmed” stock issues. However, if the previous package was a log card, the system short closes the material request on the basis of the process parameter “Auto Short close of Open Material Request” set in the Common Masters component.

Auto- generation of material requests for deferred discrepancies

• The process parameter ‘Auto Generate MR on Discrepancy Allocation for Parts/Quantities previously issued against the Discrepancy?’ under the entity type Package Type and the entity All Packages in the Define Process Entities activity of Common Master ensures that a material request is generated only for the parts not requested in the previous package for a deferred discrepancy.  

Short closing material request for deferred discrepancy with log card reference

Copies the log item # as the Discrepancy #, if the “Discrepancy Numbering Type” is set as “Copy Log Item # as Discrepancy #” for the selected Doc. Type in the “Common Masters” business component. For other numbering types, the system generates a unique Discrepancy #.

Updates the Part #, Serial # and Component # details in the “Component Details” section, to the “Discrepancy Processing” component against the new discrepancy #, on updating the status of the discrepancy as “Transferred”. The system does not perform any validity check for the entered part # and serial #.

If there is any change either in the 'Corrective Action' or in the value selected in the “Action” drop-down list box, the system updates the following in the resolution history in the “Discrepancy Processing” business component: ‘Action’, ‘Performed date’, ‘Performed Time’, ‘Performed at Station’, ‘Corrective Action’, ‘Ref.Doc Type’, ‘Ref.Doc #’, ‘Rectified by / Rectifier Name’, ‘Inspected by / Inspector Name’, ‘Dual signoff by / Dual sign off by Name’, ‘Remarks’.

If the record status of the Discrepancy # is updated to “Pending Deferral” or “Deferred” and if no Maintenance Report # has been generated for that Discrepancy # before, then the system generates a new Maintenance Report # for that discrepancy # and copies the parameters of the deferral type set for the discrepancy from the “Common Masters” business component.

On successful generation of the Execution Reference #, the system copies the parameters of the selected Entity Type on which Execution Reference was generated from the “Common Masters” business component.

If the “Enforce Sign-off?” is set as “Yes” for the selected Doc. Type in the “Common Masters” business component and if any sign off is pending for the tasks or subtasks associated to the Discrepancy in the Execution Reference, then the system ensures that all the associated tasks / subtasks are signed off / voided, on updating the record status of that discrepancy as “Cancelled”, “Closed”, “Deferred” or “Transferred”.

If a Discrepancy is generated in the Execution Reference, the system auto-generates a Non-Standard Task (NST) with the source as the Discrepancy #, Discrepancy # as the NST # and Discrepancy description as the Non-Standard Task description. If a corrective action available for the discrepancy, it must be copied as the 1st subtask for the generated NST. The default task category defined for the respective Doc. Type must be considered as the Task Category for the generated NST #.

If an unprocessed discrepancy associated to the current Execution Reference #, does not have a NST associated to it, then the system generates a new NST # with the source as the Discrepancy #, Discrepancy # as the NST # and the discrepancy description as the NST description.

If a  Discrepancy associated to AME 2, has a source document AME 1 , then  all the status changes occurring in AME 2 are updated in AME 1.

On moving / associating a discrepancy to a different package, if the discrepancy has part requirements identified, then the part requirements are copied to the ‘Material Request’ page for the new package.

If the discrepancy being associated exists in any other package, the system performs the following:

• Short-closes the material requests that are generated in the previous package.

• Generates material requests for all the part requirements in the new package.

Note: Only those material requests whose “Issue” is not confirmed are short-closed. The part requirements which are not in “Confirmed” status in the previous package, must not be cancelled.

If the Discrepancy # is generated for the first time in the Execution Reference or associated to the Execution Reference, with any corrective action available, and if any of the sign off requirements check boxes (Mechanic /Inspector/ RII Sign off) is checked and a valid employee # is available in the respective sign off fields, then the system updates the sign off status of the NST associated to the discrepancy as “Signed off” and updates the record status of the discrepancy as explained below:

1. If the “Action” drop-down list box is left blank, the record status is updated as “Under Resolution”.

2. If the “Action” drop-down list box is set as “Close” and if “Recurring” is set as “No”, the record status is updated as "Closed".

3. If the “Action” drop-down list box is set as “Cancel”, the record status is updated as “Cancelled”.

4. If the “Action” drop-down list box is set as “Part Change-Close”, the record status is updated as “Transferred”.

5. If the “Action” drop-down list box is set as “Defer”, or “Close” with “Recurring” set as “Yes”, the record status is updated based on the option “Confirmation of Deferral? set in the “Common Masters” business component.

1. • If the “Confirmation of Deferral?” is set as “Not Required”, the record status is updated as “Deferred”.

   • If the “Confirmation of Deferral?” is set as “Required”, the record status is updated as “Pending Deferral”.

If the “Retrieval of Forecasted Work Units/Deferred Discrepancies” is set as “Deferred Discrepancies" or "None" for the selected Doc. Type in the “Common Masters” business component, then the system does not allow to copy the overdue workunits from the “Compliance Tracking & Control” business component.

For Offline Aircraft (i.e. 'Mode of usage' is "Offline" in the 'Aircraft' business component) in Main Base (i.e. 'Usage Mode' is "Online" in the 'Configurator' business component), the system does not allow the following:

• New reporting / addition (transfer across packages) / re-open of Discrepancies in the Main Base.

• Addition of due tasks / discrepancies in the Main Base.

For Offline Aircraft, the system ignores auto-addition of overdue tasks / discrepancies and incomplete tasks in the Main Base, regardless of process parameter setting available in the “Common Master” business component.

For Offline Field Base operations, the system does not allow application of Hold on Discrepancies, if the process parameter ‘Allow utilization of Holds for Offline Usage’ is set as "Not Allowed" in the 'Configurator' business component.

RII / Inspector / Mechanic Sign-off reversal logic

For a discrepancy #, if 'Mechanic & RII', 'Inspector & RII', 'Mechanic, Inspector & RII' or 'RII Sign off’ has been performed already, then on deletion of Employee # from the RII sign off field, the sign off status must be reversed to “Pending RII”.

If 'Mechanic, Inspector & RII' sign-off has been performed already, then on deletion of Employee #'s from the “RII & Inspector” sign off field, the sign off status must be reversed to “Pending Mechanic”. If the ‘Mechanic’ and ‘Inspector’ check boxes are unchecked along with the deletion, the sign off status must be updated as 'Signed off'.

If 'Mechanic, Inspector & RII' sign-off has been performed already, then on deletion of 'Employee #'s from all the three sign-off fields, the sign-off status must be reversed to “Pending Mechanic & Inspector”. If the three check boxes (Mechanic, Inspector, RII) are unchecked along with the deletion, then the sign off status must be updated as 'Not Required'.

For a discrepancy #, if ‘Mechanic & Inspector Sign-off’ has already been done then on deletion of Employee # from the “Inspector” sign-off field, the sign-off status must be reversed to “Pending Inspector”. If the check box is also unchecked along with the deletion, then the sign off status should be updated as 'Signed off'.

For a discrepancy #, if ‘Mechanic Sign-off’ has already been performed then on deletion of Employee # from the “Mechanic” sign off field, the sign-off status must be get reversed to “Pending Mechanic”. If the check box is also unchecked along with the deletion, then the sign-off status should be updated as “Not Required”.

Sign off status update

For a Discrepancy # reported / associated in the MED, if there is any corrective action available, then the system updates the sign-off status as follows:

1. If the sign-off status for a corrective action is “Pending Insp & Mechanic” and if employee # is available only for 'Mechanic' sign off, then the system updates the sign off status of the NST as 'Pending Inspector' and updates the record status of the discrepancy as “Under Resolution”.

2. If the sign off requirement for a corrective action is “Pending Mechanic” and if valid employee # is available for the 'Mechanic Sign off', the system updates the sign off status of the NST as “Signed off”.

3. If the sign off requirement for a corrective action is “Pending Inspector” and if valid employee # is available for the 'Inspector Sign off', the system updates the sign off status of the NST as “Signed Off”.

4. If the sign off requirement for a corrective action is “Pending Insp & Mechanic” and if a valid employee # is available for both 'Mechanic' & 'Inspector' sign off, the system updates the sign off status of the NST as “Signed off”.

5. If the sign off requirement for a corrective action is 'Pending Mechanic/ Pending Inspector/ Pending Insp & Mech' and if the 'RII sign off' check box is in checked condition, and a valid employee # is available for the respective sign off fields other than for 'RII sign off', the system updates the sign off status of the NST as “Pending RII”.

6. If the sign off requirement for a corrective action is 'Pending Mechanic/ Pending Inspector/ Pending Insp & Mech' and if the 'RII sign off' check box is in checked condition, and a valid employee # is available for the respective sign off fields including for 'RII sign off', then upate the sign off status of the NST as “Signed off”.

7. If the discrepancy requires only the RII Sign-off then Discrepancy (Task) Sign-off status will be updated as “Signed off” on completion of RII sign-off.

8. If the corrective action requires 'Mechanic Sign off/ RII Sign off/ Mechanic & RII Sign off' and if it is already signed off/ going to be signed off, if 'Inspector' check box is checked and a valid employee # for the inspector sign off field is available, then the system update the Inspector sign off information for the subtask for the resource group ‘Inspector’, and updates the sign off status as “Signed Off”.

9. If the corrective action requires 'Inspector Sign off/ RII Sign off/ Inspector & RII Sign off' and if it is already signed off/ going to be signed off and if 'Mechanic' check box is checked and a valid employee # for the mechanic sign off field is available, then the system updates the mechanic sign off information against the subtask for the resource group ‘Mechanic’ and update the sign off status as “Signed Off”.

If any subtask other than the subtask which is displayed to the user, is pending for sign off, then on updating the sign off status of the subtask displayed to the user as “Signed off” or “Not Required”, the system updates the sign off status as "Signed-Off" for all the other sub-tasks having the Sign off status “Pending” for any resource group.

Enforce Core Return

The system ensures that the parts are not pending for return for the Task # associated to the Discrepancy # in the current Execution document, if the following conditions are satisfied:

• If the “Action” is selected as "Close", "Part Change-Close" or "Cancel" in the ‘Discrepancy’ section.

• If the parameter "Associated Task Status on Discrepancy Closure" is set as "Closed" for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.

• If the parameter “Enforce Excess/Core Returns?” is set as "Yes" for the Package Type in the “Set Process Parameters” page.

Sing-off validation on closure of task

The Sign-off status of the task # associated to the Discrepancy must be "Not Required" or "Signed off", if the following conditions are satisfied:

• If the “Action” is selected as "Close", "Part Change-Close" or "Cancel" in the ‘Discrepancy’ section.

• If the parameter "Associated Task Status on Discrepancy Closure" is set as "Closed" for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.

• If the parameter “Enforce Sign-Off?” is set as "Yes" for the Package Type in the “Set Process Parameters” page.

MR short closure on Closure / Cancellation / Part Change - close of Discrepancy

If the “Action” is selected as "Closed", "Part Change-Close" or "Cancel" and if the parameter "Associated Task Status on Discrepancy Closure" is set as "Closed” in the “Common Masters” business component, then for any material Request # available in "Authorized" or "Partially Issued" status, MR short closure happens as follows:

• If the Material Request document has parts requirements identified only for the Task # associated to the Discrepancy, system automatically short closes the Material Request document.

• If the Material Request document has Part requirements identified for any other tasks, only the part requested against the Task # associated to the Discrepancy will get short closed.

Non Standard Task generation on Action change

The system performs the following, if the “Action” is changed from "Closed", "Part Change-Close" or "Cancel" to "Under resolution" or "Deferred" and if the status of the task # associated to the Discrepancy # is in "Closed" status:

• Adds the same task against the Discrepancy # with a new Sequence #.

• Updates the status of the task # as "In-progress".

• Copies all the part requirements and resource requirements for the task.

• Updates the Sign-off status for the newly added task based on the Sign-off status of the latest task # associated to the Discrepancy.

NST Status Update

The system updates the status of the Non Standard Task against the discrepancy based on the following conditions:

• If the parameter "Associated Task Status on Discrepancy Closure" is set as "Completed" for the selected Package Type in the “Common Masters” business component', and if the “Action” against the discrepancy is changed to "Close", "Cancel" or "Part Change - Close", the system updates the status of the Non Standard Task as "Completed".

• If the parameter "Associated Task Status on Discrepancy Closure" is set as "Closed" and if the “Action” against the discrepancy is changed to "Close", "Cancel" or "Part Change - Close", the system updates the status of the Non Standard Task as updated as "Closed".

• If the “Action” against the Discrepancy is changed to "Defer", the system updates the status of the Non Standard Task as "Completed".

Closure of child discrepancy on closure of the 'Source Discrepancy #'.

If the current discrepancy # has been referred as the 'Source Discrepancy #' for any of the Child Discrepancy # and “Recurring?” is set as “Yes” for that child discrepancy,  then on updating the records status of the parent discrepancy as “Closed”, “Cancelled”, “Deferred” or “Transferred”, the system updates the record status of the child discrepancy as follows:

1. If the record status of the parent Discrepancy is updated as “Closed” or “Transferred”, the system updates the record status of the child discrepancy as “Closed”.

2. If the record status of the parent Discrepancy is updated as “Pending deferral", "Deferred" or “Cancelled”, the record status of child discrepancy remains the same.

Execution Reference # Generation in “Planned” Status

On saving the aircraft maintenance Execution Reference, the system generates an Execution Reference in “Planned” status if the following conditions are satisfied:

1. If the user has not reported corrective action for any of the associated discrepancies.

2. If no action is saved against any of the associated Discrepancies.

3. If no Sign-off comment / sign-off status updates happen for Discrepancy # or Task #.

4. If no execution comment / execution status is updated for a Task #.

5. If any component removal / attachment / cannibalize / swap / replacement actions are saved against the Execution Reference.

6. If no material request is raised for any Task # / Discrepancy #. (The system also considers those items which are in Pending folder of 'MR Detailed Tree View”).

Execution Reference # Generation in In-progress Status & Update of Execution Reference Status from “Planned” to “In-progress”

The system generates an Execution Reference # in “In-Progress” status and updates the Execution Reference status from “Planned” to “In-progress” status, if the following conditions are satisfied:

1. If the user has reported corrective action for any of the associated discrepancies and not completely signed off.

2. For any of the associated discrepancies, if the record status has been updated as other than “Under Resolution”.

3. If the clock status in the ‘Sign off Requirements’ section is other than “Not Started” for any of the associated Task or Discrepancy # for that Execution Reference #.

4. If any sign-off status updates happen for a Discrepancy # or Task #.

5. If execution status has been updated other than “Pending” for any of the associated Task # for that Execution Reference #.

6. If any component removal / attachment / cannibalize / swap / replacement actions are saved against the Execution Reference.

7. If any material request is raised for any Task # / Discrepancy #. (The system also considers those items which are in Pending folder of 'MR Detailed Tree View” ).

Updating the Execution Reference Status from “Completed” to “In-progress”.

The system updates the Execution Reference status from “Completed” to “In-progress” on following conditions:

1. If the user reports any corrective action for any of the associated discrepancies.

2. For any of the associated discrepancies, if the record status has been updated as “Under Resolution”.

3. If the clock has been initiated for any discrepancy # or task # associated in the Execution Reference #.

4. If the sign-off status is updated from 'Signed off' to 'Pending Mechanic / Pending Inspector / Pending Mechanic & Inspector / Pending RII' for any of the associated discrepancy in that Execution Reference #.

5. If sign off is pending for any of the Task # associated to that Execution Reference #.

6. If execution status has been updated other than “Completed” or “Pre closed” for any of the associated Task # for that Execution Reference #.

7. If any component removal / attachment / cannibalize / swap / replacement actions are saved against the Execution Reference.

8. If any new material request raised for any Task #/Discrepancy #.

Execution Reference # Generation in "Completed" Status

The system generates an Execution Reference # in “Completed” status or modifies the Execution Reference to “Completed” status, if the option “Enforce closure of Logcards type of Package” is set as “Yes” in the “Common Masters” business component and if the following conditions are satisfied:

1. If all the tasks that are associated to the Execution Reference # are having the execution status as “Cancelled”, “Completed” or “Pre Closed”.

2. The record status of all the discrepancies associated to the Execution Reference # must be “Closed”, “Cancelled”, “Deferred” or “Transferred”.

3. There must not be any record under the “Pending Action Items” folder in the CR Tree interface folder.

4. There must not be any record under the “Request Pending” node in the “Material Request” detailed view tree interface.

Execution Reference # Generation in "Closed" Status

The system generates an Execution Reference # in “Closed” status or modifies the Execution Reference to “Closed”, if the option “Enforce closure of Log cards type of Package” is set as “No”, if the Doc. Type selected for that Execution Reference is “Log Card” and if the following conditions are satisfied:

1. If all the task(s) that are associated to the Execution Reference # are having the execution status as “Cancelled” or “Completed” or “Pre Closed”.

2. The record status of all the Discrepancies associated to the Execution Reference # must be “Closed”, “Cancelled”, “Deferred” or 'Transferred'.

3. There must not be any record under the “Pending Action Items” folder in the CR Tree interface folder.

4. There must not be any record under the “Request Pending” node in the “Material Request” detailed view tree interface.

5. There must not be any Excess / Core parts pending to be returned for that Execution Reference #.

Note: This is considered only if the option “Enforce Excess / Core Return” is set as “Required” for the selected Doc. Type.

Modification of sign-off requirements

The system allows modification of sign-off requirements based on the parameter “Allow modification of Task Sign-Off requirements” set for the package type of the current Execution Ref #, in the “Define Process Entities” activity of the “Common Masters” business component. Refer to the table below:

• Click the “New Log” icon '', if you want to create aircraft maintenance execution reference.

To edit an aircraft maintenance Execution Reference

• Select the “Open Log List” pushbutton in the left navigation pane, to edit an existing aircraft maintenance  Execution Reference.

The following icons are displayed in the “Open Items”, “Discrepancies”, “Work Information”, ‘Component Replacement” and “Material Request” trees, which allow you to perform various operations as explained in the table below:

Note: The system allows progressive loading of data in the “Component Replacement” tree and “Material Request” tree when you select a specific node in the respective tree. The system executes the search and filter operations on the nodes which are already open.

The total count of distinct Execution References that are in “Planned”, "In-Progress”, “Completed” and "Closed"  status for the specified Aircraft Reg #, and that are created in the Aircraft Maintenance Execution Reference, is displayed in the “Open Items” navigation pane.

The system displays the text “Open Items” at the top of the navigation pane. The navigation pane will display the tree interface as completely exploded. The tree will have the “Aircraft Reg #” as the parent node and the following first-level nodes:

“Log Cards”

“Package Defects”

“Unprocessed Discrepancies”

“Minor”

“Major”

1. Log Cards: The system displays the Log Items # / Discrepancies associated to the Aircraft Reg #, as the second-level node with the following values:

1. Under Resolution: Log Item # / Discrepancies having record status “Pending” and “Under Resolution”, and associated to the Execution Reference #s of Doc Type as “Log Cards” are displayed under this node.

2. Pending Deferral: Log Item # / Discrepancies having record status “Pending Deferral” and associated to the Execution Reference #s of Doc Type as “Log Cards” are displayed under this node.

3. Deferred: Log Item # / Discrepancies having record status “Deferred” and associated to the MED #s of Doc Type as “Log Cards” are displayed here.

4. Closed: Log Item # / Discrepancies having record status “Transferred”, “Cancelled” and “Closed” and associated to the Execution Reference #s of Doc Type as “Log Cards” are displayed under this node.

5. Job Cards: Execution References of Doc Type “Log Cards” and which do not have any discrepancies associated to it are displayed under this node.

Note: If the Log Item # is not available for the discrepancy, then the system displays the Discrepancy # in the tree interface.

2. Package Discrepancies: The system displays the Log Items # / Discrepancies associated to the Aircraft Reg # , as the second-level node with the following values:

1. Under Resolution: Log Item # / Discrepancies having record status “Pending” and “Under Resolution”, and associated to the Execution Reference #s of Doc Type as other than  “Log Cards” are displayed under this node.

2. Pending Deferral: Pending Deferral: Log Item # / Discrepancies having record status “Pending Deferral” and associated to the Execution Reference #s of Doc Type as other than  “Log Cards” are displayed under this node.

3. Deferred: Log Item # / Discrepancies having record status “Deferred” and associated to the Execution Reference #s of Doc Type as other than “Log Cards” are displayed here.

4. Closed: Log Item # / Discrepancies having record status “Transferred”, “Cancelled” and “Closed” and associated to the Execution Reference #s of Doc Type as other than “Log Cards” are displayed under this node.

3. Unprocessed Discrepancies: The system displays the Log Items # / Discrepancies associated to the Aircraft Reg # as the third-level node with the following values:

1. Pending: Log Item # / Discrepancies having record status “Pending” and not associated to the Execution Reference #s are displayed under this node.

2. Pending Deferral: Pending Deferral: Log Item # / Discrepancies having record status “Pending Deferral” and not associated to the Execution Reference #s are displayed under this node.

3. Deferred: Log Item # / Discrepancies having record status “Deferred” and not associated to the Execution Reference #s are displayed here.

Note: If the Log Item # is not available for the discrepancy, then the system displays the Discrepancy # in the tree interface.

4. Minor: The system displays all Execution References of Doc Type “Minor” with respective document statuses under this node.

1. Planned: Execution References of document status “Planned” are displayed here.

2. In-Progress: Execution References of document status “In-Progress” are displayed here.

1. Completed: Execution References of document status “Completed” are displayed here.

5. Major: The system displays all the Execution References of Execution Type “Major” with respective document statuses under this node:

1. Planned: Execution References of Execution Type “Major” and document status “Planned” are displayed.

2. In-Progress: Execution References of Execution Type “Major” and document status “In-Progress” are displayed.

3. Completed: Execution References of Execution Type “Major” and document status “Completed” are displayed.

Hold Status / Estimation Status:

Each record i.e. Package / Discrepancy must have 'Hold Status' and 'Estimation Status' information. If 'Hold' is applicable for a record, it must be represented by an Exclamatory Icon '’. If 'Hold' is not applicable for a record, the 'Hold Status Icon' is not displayed. The possible Estimation Status could be "Est. Not Required", "Pending Estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Pending Re-Estimates".

The system does not display the Hold Status and Estimation Status for the discrepancy records present under the 'Unprocessed Discrepancies' folder.

Lock Icon:

Main Base operations:

If the Process Parameter ‘Usage Mode’ is set as "Online" in the 'Configure Offline Parameters' activity of the “Configurator” business component and ‘Mode of Usage’ of Aircraft is defined as "Offline" in the “Aircraft” business component, the system displays the Lock Icon ‘’ for the following records:

1. All Log Card discrepancies, Unprocessed Discrepancies and Package Discrepancies listed in the 'Open Items' tree will remain locked in Main Base.

2. "Planned" / "In-Progress" packages (includes Job Cards) having 'Source' as "Offline" i.e. created from field base..

3. “Completed" packages having 'Source' set as "Offline" will be locked, if the process parameter 'Closure of Completed Packages' in the 'Configure Offline Parameters' activity is set as "Offline Base".

Offline Base Operations:

All discrepancies will remain unlocked for processing in Remote Base. Online Packages will be locked in Remote Base. If the Process Parameter ‘Usage Mode’ is set as "Offline" in the 'Configure Offline Parameters' activity, the system displays the Lock Icon ‘’ for the following records:

1. Log Card Discrepancies listed in 'Open Items' tree and Unprocessed Discrepancies shall be unlocked for processing in Remote Base. However, the following type of package discrepancies will be locked in the Remote Base:

1. • Discrepancies referring Online Packages (Package with 'Source' set as "Online")

   • Discrepancies referring Offline Packages (Package with 'Source' set as "Offline") with 'Data Transfd' flag set as "Yes" and Process Parameter 'Closure of Completed Packages' set as "Main Base".

2. Packages (including 'Job Cards') having 'Source' as "Online" will be locked for editing in Remote Base.

3. "Completed" packages having 'Source' set as "Offline" will be locked for editing in Remote Base, if the process parameter 'Closure of Completed Packages' is set as "Main Base" and 'Data Transfd' flag for Package is set as "Yes" (indicating that data transfer to Main Base has happened after package completion).

Note: The system displays an error message when you select a node which has a Lock Icon on it.

• Select the aircraft maintenance  execution reference to be modified in the tree interface.

The details of the selected aircraft maintenance execution reference are displayed, in the “Execution Reference Details” group box to the right.

On clicking of and Discrepancy # under the Log Card folder of the tree structure

1. If the right pane does not have ’Execution Reference #', then the system displays the Execution Reference # of the discrepancy which is currently associated along with the other details in the Execution Reference # Details section.

2. If the right pane has “Execution Reference #”  with document type as “Log Card” in the Execution Record section, then system refreshes the existing details in the right pane with the Discrepancy # selected and the associated Execution Reference # which the discrepancy is currently associated.

3. If the right pane has “Execution Reference #”  with document type as other than “Log Card” in the Execution Record section, then system associates the Discrepancy # selected to the Execution Reference #. available in the right pane.

On clicking of and Discrepancy # which is in other than “Deferred” status, under the Package Discrepancies folder of the tree structure:

1. If the right pane does not have ’Execution Reference #', then system displays the Execution Reference # of the discrepancy which is currently associated along with the other details in the Execution Reference # Details section.

On clicking of and Discrepancy # which is in “Deferred” status, under the Package Discrepancies folder of the tree structure:

1. If the right pane has “Execution Reference #”  with document type as “Log Card” in the Execution Record section, then system refreshes the existing details in the right pane with the Discrepancy # selected and the associated Execution Reference # which the discrepancy is currently associated.

• Edit the required details of this execution reference.

• Click the “Save Log” icon '' to save the modified details of the aircraft maintenance execution reference.

• Select the ‘’ icon, to view the details of the previous aircraft maintenance execution reference. Use the tree view as the reference.

• Select the ‘’ icon, to view the details of the next aircraft maintenance execution reference. Use the tree view as the reference.

The system retrieves the Execution Reference #s by traversing through all the nodes in one folder completely before moving to the next folder on executing the 'Next' or 'Previous' task.

• Select the ‘ ’ icon to perform manual completion of the AME document.

The system ensures the following on clicking the “Complete” icon mentioned above:

• The “Execution Ref #” must be available in status other than “Cancelled”, “Closed” and “Completed”.

• The tasks which are not having the Source as “Discrepancy”, must be in status other than “Planned” and “In-Progress”.

• The discrepancies within the package must have record status other than “Under Resolution” and “Pending Deferral”.

The system performs the following on clicking the “Complete” icon:

• If any configuration change has happened, the part program of the new part will be automatically inherited by the associated components.Updates the document status of the Execution Ref # as “Completed”.

• Updates the status log with 'Entity Changed', 'From Status', 'To Status', ‘Current Work Center’ and ‘Date & Time’.

• Updates the condition of the aircraft as “Under Maintenance” or “Operational”. Refer to the section “Aircraft Condition Update” for more details.

• The system does not allow completion of the AME document under following conditions:

1. 1. 'Stop A/C Maint. Execution ?' parameter is set as "Yes" for the 'Hold Code' corresponding to the 'A/C Maint. Exe. Ref. Document' / 'Customer Order'.

   2. The parameter 'Prevent Task Status Change ?’ is set as “Yes” for the hold code associated to the task, discrepancy or 'A/C Maint. Exe. Ref. Document' / 'Customer Order' and completion of the 'A/C Maint. Exe. Ref. Document' results in a change in ‘Execution Status’ of associated Tasks / Discrepancies.

   3. When completion of the 'A/C Maint. Exe. Ref. Document' results in a change in ‘Execution Status’ of an associated Task / Discrepancy and the respective Task / Discrepancy has a 'Hold Code' applied on it, with the process parameter 'Prevent Task Status Change ?' for the 'Hold Code', set as "Yes".

• Auto Return of parts on package completion:

If the parts are pending for return for the tasks inside a package, then system creates a Material Return document on completion of the package, if the parameter “Auto Return of Parts” is set as “Required” for the Package Type in the “Set Process Parameters” page of the “Common Masters” business component.

Scenario 1: Pending Return - Core

If core returnable parts and the parts which are removed from aircraft are available for return, then for the work center mapped to the corresponding task, the system creates the Return Document against the ‘Return Warehouse # - Cores’ associated to the Work Center.

Scenario 2: Pending Return - Excess

If excess return parts are available for return, the system creates the Return Document against the ‘Return Warehouse #’ associated to the Work Center.  Example.

Note: The Return Document creation happens only if the “Auto Return?” drop-down list box is set as “Required” for the Work Center - Part Type combination in the “Associate Warehouses” page of the “Work Center” business component.

To close an aircraft maintenance Execution Reference

After creating a new aircraft maintenance execution reference and recording the discrepancy, work information and component replacement details for it, you are to close the aircraft maintenance execution reference.

• Select the “” icon, in the “Execution Reference Details” group box to close the Aircraft Maintenance Execution Reference document

The following are carried out:

• The system updates the status of the Execution Ref # as “Closed”.

• The system ensures that the record status of the discrepancies within the package is other than “Under Resolution” and “Pending Deferral”.

• The system processes and updates the financial postings in the “ Finance Book Processing” business component from the “Account Group” business component and, if interaction exists, with the “Book Keeping” business component.

Note: The financial posting happens at task level only for those tasks which are in “Incomplete” or “'Deferred” status and for those tasks whose status is changed from “Completed” to “Closed”.

• The system calculates the actual cost for the aircraft maintenance execution reference as the sum of material cost, resource cost, employee cost, labour cost, facilities cost and miscellaneous cost.

• The system does not allow the user to close the Execution Ref #, if an employee has booked timesheet against the task associated to the Execution Ref # and started the clock, but not ended the clock.

• For a package type, If the parameter ‘Allow Closure of Package with Pending Replacements?' is set as “Not Allowed” in the “Set Process Parameters" page of the “Common Masters” business component, ensure that no Component Replacement is pending for confirmation in the “Component Replacement” section, before changing the status of the package to “Close”.

• The system does not allow closure of the AME document, under following conditions:

• 1. 'Stop A/C Maint. Execution ?' parameter is set as "Yes" for the 'Hold Code' corresponding to the 'A/C Maint. Exe. Ref. Document' / 'Customer Order'.

  2. The parameter 'Prevent Task Status Change ?’ is set as “Yes” for the hold code associated to the task, discrepancy or 'A/C Maint. Exe. Ref. Document' / 'Customer Order' and completion of the 'A/C Maint. Exe. Ref. Document' results in a change in ‘Execution Status’ of associated Tasks / Discrepancies.

  3. When completion of the 'A/C Maint. Exe. Ref. Document' results in a change in ‘Execution Status’ of an associated Task / Discrepancy and the respective Task / Discrepancy has a 'Hold Code' applied on it, with the process parameter :  'Prevent Task Status Change ?' for the 'Hold Code', set as "Yes".

• When completion of the 'A/C Maint. Exe. Ref. Document' results in a change in ‘Execution Status’ of an associated Task / Discrepancy and the respective Task / Discrepancy has a 'Hold Code' applied on it, with the process parameter  'Prevent Task Status Change ?' for the 'Hold Code', set as "Yes".

• For offline aircrafts (i.e. Mode of Usage for aircraft set as "Offline" in the “Aircraft” business component), the system allows closure of A/C Maint. Exe. Ref. Documents from Main Base (Usage Mode set as “Online” in the “Configurator” business component), irrespective of the value set for 'CoM Reqd?' parameter defined for the selected package type in the “Common Master” business component.

• The system does not allow closure of A/C Maint. Exe. Ref. Documents having 'Source' set as "Offline", in the Main Base, if the process parameter “Closure of Completed Packages’ is set as "Offline Base" in the “Configurator” business component.

• The system does not allow closure of A/C Maint. Exe. Ref. Documents having 'Source' set as "Offline", in the Offline Base, if the process parameter “Closure of Completed Packages’ is set as "Online Base" in the “Configurator” business component.

• Process parameter dependency for aircraft with empty mandatory positions: If the process parameter “"Allow closure of AME package when mandatory positions are empty for the aircraft?” under the entity type Package type and the entity - all user defined package types including 'Log Card' except '--All Packages--' is set as ‘1’/Yes in the Define Process Entities activity in Common Master, the users can close the package even if Assembly Status of the aircraft configuration is not “Complete”. On the contrary, if the value of the process parameter is 0/No, you cannot close packages against aircraft with Assembly Status as ‘No’.

• If the "Auto update Line status of Tasks in Short Term Escalation  as "Cancelled" in the Set Options activity of Compliance Tracking & Control is set as Required, the system performs the following:

If the Removed Date & Time of CR task is earlier than STE Approved Date & Time, the system automatically sets Status of the STE in the Request Short Term Escalations screen as ‘Cancelled’ and Line Status in the View Short Term Escalation Details screen as ‘Cancelled’ for the record. 

If the Removed Date & Time is later than STE Approved Date & Time, the system sets  Status of the STE in the Request Short Term Escalations screen as ‘Pending’ and Line Status in the View Short Term Escalation Details screen as ‘Processed’ for the record. In both the above scenarios, the system resets the schedules of the below-listed attributes based on the escalation limits.

o    NSV

o    NSD

o    Next Due Calc. On

o    Calc. Ref. Date / Value

o    Last Schedule Date / Value

o    Remaining Value

o    Short Term Esc. Ref #

To cancel an Aircraft Maintenance Execution Reference

• Select the aircraft maintenance execution reference to be cancelled from the tree interface.

The details of the selected aircraft maintenance execution reference are displayed, in the “Execution Reference Details” group box to the right.

• Click the “Cancel Log” icon '' in the “Execution Record Details” group box, to cancel the selected aircraft maintenance execution reference.

Note: You cannot cancel the package; 1) If the aircraft is customer owned, the customer order for the maintenance of the aircraft exists and, the stage of the contract stage is “Firm”. 2) If the “Task status change on Material Issue confirmation?” process parameter for the entity type “Package Type” of the entity “All Packages” in the “Define Process Entities” activity of Common Master is ‘0’ and, if stock issues have been confirmed or work actuals recorded against tasks/discrepancies in the package.

When the AME is cancelled, the system cancels the associated Customer Order # and updates the status as follows:

• Updates the status of the AME as "Cancelled".

• Updates the Latest Rev. # of the Customer Order as "Short Closed".

• Updates the Previous Rev. # of the Customer Order as "Revised".

To Print Material Movement Document

• Click the “Print Material Movement” icon ‘ ’ in the “Execution Record Details” group box to print all the material movement documents (MMD) for an Execution Ref #.

The following documents will be considered for printing the MMD:

1. The material requests with issue documents in “Fresh” status.

2. The material requests with “MR Priority” set as “AOG” and with no issue documents created.

If the MMD for the Material Request # is already printed, the system will alert the user that the document has been already printed and whether reprinting is required.

To print the package

• Click the “Print Package” icon ‘ ’ in the “Execution Record Details” group box to print all the Task Cards of  that package.

• Click the “Selective Print Package” icon ‘ ’ in the “Execution Record Details” group box to print the selected task cards  of that package.

To report a new discrepancy

• Select the aircraft maintenance execution reference for which a new discrepancy needs to be reported, from the tree interface.

• Select the “Discrepancies” pushbutton in the left navigation pane.  

• Enter the following fields in the “Discrepancy” group box:

The Log Item # for a discrepancy is derived based on the following logic:

1. If both log # and Log Item # are available, then the Log Item #is derived by concatenating the Log # with the entered Log Item # with '/' as the separator. For e.g. If the Log # is SN11255 and the Log item # is 01 then the Log Item # is derived as SN11255/01.

2. If only Log # is available, then Log Item # is derived by incrementing the latest Log Item # for the entered log # by 01.

3. If only Log Item # is available then the entered Log Item is saved.

4. If both Log # and Log Item # are not available, then the log item is derived by concatenating the Execution Reference # with the value incremented by 01 from the latest Log Item # available in the Execution Reference.

The system displays the following fields in the “Discrepancy Details” group box:

• Click the hyperlinked “Discrepancy #” to view the discrepancy information.

• Enter the following fields in the “Discrepancy Details” group box:

Example for Radio Communication:

The Pilot communicates the discrepancy to the Maintenance Operations Control (MOC) on Air and the MOC records the 'Radio Communication'.

If the Radio Communication is “PACK # 2 INOP”, the Discrepancy Description is displayed in the following format:

“Radio Com: PACK # 2 INOP”.

• Enter the following:

• Click the  icon next to the above field, to clear the description in the field.

• Click the  icon to view the corrective action history.

• Enter the following fields:

• Select the “Save Discrepancy” icon '' to save the discrepancy. Dual Authentication

The count to the right of the “Discrepancies” pushbutton is incremented by 1, to indicate that an additional discrepancy has been added.

Note: The aircraft maintenance execution reference details can also be saved by using the “Save” pushbutton in the “Discrepancy” group box.

Note: The system restricts creation of new A/C Maint. Exe. Ref. Documents referring an Offline Work Center (i.e. Work Centers having 'Usage Mode' set as "Offline" in the 'Work Center' business component), in Main Base (i.e. if the process parameter ‘Usage Mode’ is “Online” in the “Configurator” business component.

Discrepancy details cannot be modified, if the ‘Transient Status’ of the discrepancy is set as “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

If the Execution Status of the task is updated to “Completed” / “Closed” / “Pre-closed”, the system updates the parameter values recorded against the Aircraft Maintenance Log, with Execution Ref. # / Line # / Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

The system derives the 'Estimation Status' of the AME document as the lowest hierarchy value set for any of the Tasks / Discrepancies associated to the AME document. The 'Estimation Status' hierarchy is as follows: "Pending Estimates", "Pending Re-estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Not Required".

If a hold is applied on the selected ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order', the system does not allow you to create a new AME document or modify the existing AME document, if the parameter 'Stop A/C Maint. Execution?' is set as "Yes", for the 'Hold Code' corresponding to the ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.

On saving the discrepancy, the system updates the condition of the aircraft as “Under Maintenance” or “Operational”. Refer to the section “Aircraft Condition Update” for more details.

The system allows modification of sign-off requirements based on the parameter “Allow modification of Task Sign-Off requirements” set in the “Common Masters” business component. Refer to the section “Modification of sign-off requirements”.

The system creates a Material Return document, if the parts are pending for return. Refer to the section “Auto Return of parts on package completion” for more details.

On creation of a new package, the system copies the incomplete, overdue and due tasks into the package, based on the parameters set in the “Common Masters” business component. Refer to the section “Addition of Incomplete, Overdue and Due tasks on saving AME, discrepancy and work information” for more details.

Customer order creation

The system creates a customer order in “Processed” status comprising the package, if the ownership of the aircraft is “Customer”. Further, based on attributes including A/C Reg #, A/C Model #, A/C MSN #, Customer PO # and Customer #, the system determines the relevant contract for the customer order.

The stock status of the parts required by the package is set to the preferred stock status of the contract. However, if any part is covered by a PBH agreement, the stock status will be set to PBH.

The warehouses for each of the parts will be the Service Request warehouse that is valid for the work center of the package and the part type of the part. However, customer order is automatically generated in Processed status only if the contract status is “Approved”, the contract stage is “Firm” and, the planned/start date of the package pertains to the effective period of the contract.

Refer to the section “When the aircraft maintenance execution reference and discrepancy are saved" for more details.

• Click the “New Task” icon '' in the “Discrepancy” group box to create another discrepancy.

To defer a discrepancy

• Select the discrepancy to be deferred from the discrepancy tree interface.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• From the “Action” drop-down list box in the “Discrepancy” group box, select “Defer”.

If “Action” is selected as “Defer” and “Recurring?” drop-down list box is set as “Yes”, the system displays the following fields, which you are to enter:

Note: The deferral limits entered in the “Deferral Details” group box must be valid for the Deferral Type – Deferral Item combination.

When you defer a Discrepancy with a 'Deferral Item' having 'Defer Limit Type' as "As Entered", you must enter at least one deferral limit parameter (Usage Based / Calendar Based), i.e. you must enter FH / FC, ‘Other Parameters’ or ‘Calendar’.

You cannot defer a Discrepancy with a 'Deferral Item' having 'Defer Limit Type' set as "Deferral Not Allowed".

Note: The system retrieves the deferral limits for the parameters FH & FC, for the Calendar days and for any other consumption parameters defined from the “Configuration” business component, if the Deferral Item # specified is valid as defined in the “Common Masters” business component.

Note:  If an user defined Deferral Item # is available (i.e. the entered deferral item # is not defined in the Model Configuration of the current Aircraft reg #) for the Deferral Type selected, ensure that any one of the deferral limits such as Deferral Duration & Time, Deferral By (FH), Deferral By (FC) is entered, Deferral By other parameter and value and Deferral By calendar value with UOM.

For the Deferral Types “MEL” and “CDL”, if a valid Deferral Item # is entered, then ensure that the deferral limits entered do not exceed the standard “Deferral  Schedule” set for that Deferral Item #.

Deferral Till Date calculation

For first time deferral

On saving / confirming discrepancy, if the record status of the discrepancy # is updated to “Pending Deferral” or “Deferred”, the system calculates and updates the Deferral Till Date of the discrepancy, based on the logic mentioned in the table.

1. The formulae in the table are applicable if the discrepancy is deferred to exact time (i.e. if the process parameter “Next Due computation logic” is set as ‘Exact Date & Time'.)

2. if the process parameter “Next Due computation logic” is set as ‘End of Day’, the formulae mentioned in the table is applicable, except for the following:

• Conversion of Date/Time to UTC Time Zone is not required.

• Conversion of time to ‘23:59’ (without UTC conversion), is required for discrepancies deferred by ‘Calendar Months’ and ‘Other Params’ also.

For Repeat discrepancies

If the record status of the discrepancy # is updated to “Pending Deferral” or “Deferred” and if “Recurring?” is set as “Yes”, the system updates the Deferral Till Date / Time of the discrepancy # based on the following logic:

1. If deferral duration alone is given, the Deferral Till Date & Time =  Discrepancy Execution Date + Deferral duration.

2. FH is given, the Deferral Till Date & Time =  [(Threshold Value-Current FH )/ Avg. Utilization Value of FH] + Discrepancy Execution Date

3. If FC is given, then Deferral Till Date & Time =  (Threshold Value-Current FC )/ Avg. Utilization Value of FC) + Discrepancy Execution Date

4. If any one of the consumption parameter other than FH, FC and Calendar, the Deferral Till Date & Time =  Discrepancy Execution Date + (the parameter value as on the discrepancy reported date / Average utilization value for the parameter)

5. If both FH & FC are available, the Deferral Till Date is calculated separately for FH and FC and the earliest / latest date (based on the Deferral Limit Basis set) is updated as Deferral Till Date & Time.

6. If both calendar based date and user based FH and FC or any other usage-based parameters are available, the Deferral Till Date is calculated individually for the deferral duration, FH , FC, and for the other parameters as per the logic above. and the earliest / latest date (based on the limit basis set)  is updated as the Deferred Till Date & Time.

Note: The above formulae holds good if the process parameter “Next Due computation logic” is set as “Exact Date & Time”. If the process parameter is set as ‘End of Day’, conversion of time to’23:59’ is done.

Note: The system considers the Execution Date & Time  of the discrepancy as the ‘Reference Date & Time’ for the Repeat Scenario.

Note: The ‘Deferral Limit Basis’ option is not considered if the “Recurring?” drop-down list box is selected as “Yes”.

• Click the “Confirm Deferral” icon '' to save the deferred discrepancy

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

Deferral of the discrepancy cannot be confirmed, if the ‘Transient Status’ of the discrepancy is set as “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

The status of the discrepancy is updated from “Pending Deferral” to “Deferred”.

The system does not display the "Confirm Deferral" icon, if the following conditions are applicable:

1. The “Deferment of Discrepancies” is set as “Not Allowed” for the selected Doc. Type in the “Common Masters” business component.

2. The “Deferment of Discrepancies” is set as “Required” and “Confirmation of Deferral?” is set as “Not Required” for the selected Doc. Type.

After the Execution Reference # is successfully generated, the system copies the parameters of the selected Doc. Type on which Execution Reference was generated from the “Common Masters” business component.

After the discrepancy and Aircraft Maintenance Execution (AME) are saved, the system does not allow modification of any details of the discrepancy, except Corrective Action & Deferral Details (Deferral Item #, Deferral Type, Defer by days/ FH/ FC, UOM, Reason for Deferral), if the current record status of the discrepancy is “Pending Deferral” or  “Deferred” and if the Action is selected as “Defer”.

Note: A login user can modify deferral details only if he or she has the access rights to the “Revise Deferral Limits” activity of the “Discrepancy Processing” business component.

The system creates a Material Return document, if the parts are pending for return. Refer to the section “Auto Return of parts on package completion” for more details.

To resolve and close a discrepancy

• Select the discrepancy to be closed from the discrepancy tree interface.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• From the “Action” drop-down list box in the “Discrepancy” group box, select “Close”.

• Enter the corrective action.

• Select the “Save Discrepancy” icon. Dual Authentication

If you had entered the “Corrective Action” field, the system will create and display non standard task # in the “Task #” field.

To record “No Fault”

In instances where the PIREP has reported a discrepancy, but the MIREP records that there is no such fault / discrepancy in the aircraft, carry out the following:

• Select the discrepancy to be recorded as No fault from the discrepancy tree.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• From the “Action” drop-down list box in the “Discrepancy” group box, select “No Fault”.

• Enter the corrective action.

• Click the “Save Discrepancy” icon. Dual Authentication

The discrepancy is saved for future records.

To transfer a discrepancy  

While transferring a discrepancy, the system performs the following:

• The system saves the component details such as part #, serial # and position code attached to the aircraft, against the discrepancy.

• When the discrepancy is deferred, the saved component details will be referred by the planner in the “Plan Aircraft Maintenance” page of the “Aircraft Maintenance Planning” business component. 

• Select the discrepancy to be transferred from the discrepancy tree interface.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• From the “Action” drop-down list box in the “Discrepancy” group box, select “Part Change-Close” and enter the following details in the “Component Details” group box.

• Enter the corrective action.

• Select the “Save Discrepancy” icon. Dual Authentication

The system transfers the discrepancy details to the selected component.

The system updates the record status of the Discrepancy as “Transferred” and replaces the “Component Details” section with the “Component Replacement” section by copying the values of Part # and Serial # to Removed Part # and Serial # in the “Component Replacement” section.

To cancel a discrepancy      

• Select the discrepancy to be cancelled from the discrepancy tree interface.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• From the “Action” drop-down list box in the “Discrepancy” group box, select “Cancel”.

• Click the “Cancel Discrepancy” icon.

The system updates the record status of the discrepancy as “Cancelled”.

Note: If the “Task status change on Material Issue confirmation?” process parameter for the entity type “Package Type” of the entity “All Packages” in the “Define Process Entities” activity of Common Master is ‘0’, you cannot cancel a discrepancy, if a stock issue has already been confirmed or work actuals recorded against tasks/discrepancies in the package.

Holding / releasing discrepancy

• Enter the following in the “Hold / Release”section:

• Click the “Hold” pushbutton to hold the discrepancy.

A newly created discrepancy is considered to be on hold automatically, under following conditions:

• Customer Order # is on hold.

• Package is on hold

• Source Task # / Source Discrepancy #, is on hold. When creating a Discrepancy, the Task / Discrepancy specified in the ‘Source Type & No’ controls is considered as the corresponding Source Task / Source Discrepancy.

Note: Only those discrepancies that are in “Under Resolution”, “Pending Deferral” and “Deferred” statuses, can be put on hold.

When 'Hold' is applied on a 'Task' / 'Discrepancy', the system escalates and applies the 'Hold' for the 'A/C Maint. Ref. Document' / 'Customer Order', based on the value set for the process parameter ‘Escalation Level’ corresponding to the 'Hold Code' in the ‘Define Process Entities’ activity of the ‘Common Master’ business component.

For Offline Field Base operations, the system does not allow application of Hold on Discrepancies if the process parameter  "Allow utilization of Holds for Offline Usage" is set as "Not Allowed" in the ”Configurator” business component.

• Click the “Release” pushbutton to release the discrepancy.

Note: Ensure that the discrepancy is on hold for the selected ‘Hold Code’.

The discrepancy must be released from hold, only if the following conditions are true:

1. The process parameter 'Release Responsibility' must be set as "Execution” for the hold code in the “Define Process Entities" activity of the "Common Master" business component.

2. The process parameter 'Release Responsibility Roles' set for the hold code must match with the login role.

• Select the “Record Work Hold” link to the record the work hold details for the discrepancy.

Refer to “Work Monitoring and Control” online help for more details.

To edit a discrepancy

• Select the aircraft maintenance execution reference for which discrepancy details are to be modified in the tree structure.

The count of discrepancies recorded for the selected aircraft maintenance execution reference # is displayed alongside the “Discrepancies” pushbutton.

• Select the “Discrepancies” pushbutton in the left hand navigation pane, to modify an existing discrepancy.

The system displays the text “Discrepancies” at the top of the navigation pane. The navigation pane will display the tree interface as completely exploded. The tree will have the “Execution Reference #” and “Aircraft Reg #” as the parent nodes, with all the records displayed as per the defined format:

Note: If the Log Item # is not available for the discrepancy, then the system displays the Discrepancy # in the tree interface.

Execution Reference #: The system displays the Log Item # / Discrepancies associated to the selected Execution Reference # with document status “Planned”, “In-Progress” and “Completed”, as the first-level nodes with the following values.

1. Pending: Log Item # / Discrepancies with record status “Pending” and “Under Resolution” are displayed under this node.

2. Pending Deferral: Log Item # / Discrepancies with record status “Pending Deferral” are displayed under this node.

3. Deferred: Log Item # / Discrepancies with record status “Deferred” are displayed here.

4. Closed: Log Item # / Discrepancies with record status "Transferred", "Cancelled" and "Closed" are displayed under this node.

Aircraft Reg #: The system displays the Log Item / Discrepancies under two different nodes as follows:

1. Log Cards: For the specified Aircraft Reg #, the system displays the Log Item # / Discrepancies which are associated to the Execution References of Doc Type “Log Cards” and document status “Planned”, “In-Progress” and “Completed”, under different nodes as follows:

   1. Pending: Log Item # / Discrepancies with record status “Pending” and “Under Resolution” are displayed under this node.

   2. Closed: Log Item # / Discrepancies with record status "Transferred", "Cancelled" and "Closed" are displayed under this node.

   3. Pending Deferral: Log Item # / Discrepancies with record status “Pending Deferral” are displayed under this node.

   4. Deferred: Log Item # / Discrepancies with record status “Deferred” are displayed here.

Note: Each record in the tree must have 'Hold Status' and 'Estimation Status' information. If 'Hold' is applicable for a record, it must be represented by an Exclamatory Icon ‘’. If 'Hold' is not applicable for a record, the 'Hold Status Icon' is not displayed. The possible Estimation Status could be "Est. Not Required", "Pending Estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Pending Re-Estimates".

• Select the discrepancy to be modified in the tree structure.

The details of the selected discrepancy are displayed, in the “Discrepancy” group box to the right.

• Edit the required details of this discrepancy.

• Click the “Save Discrepancy” icon to save the modified details of the discrepancy. Dual Authentication

The system performs the following:

Updates the “Discrepancy Processing” business component with the modified Plan Start Date and Plan End Date against the Discrepancy #.

• Select the ‘’ icon, to view the details of the previous discrepancy. Use the tree view as the reference.

• Select the ‘’ icon, to view the details of the next discrepancy. Use the tree view as the reference.

Sign-off Requirements

• Click the icon in the “Sign-Off Requirements” group box, to start the clock.

Note: The system does not allow clock on of tasks and discrepancies in offline field base (Usage Mode set as “Offline” in the “Configurator” business component).

• Click the icon to reset the clock.

• Click the icon to end the clock.

Transient Status Check:

The clock cannot be started or stopped for the task, if one of the following conditions is true:

• ‘Transient Status’ of the task is “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

• ‘Transient Status’ is not "Hold", but the ‘Hold Status’ is “Open” and the process parameter "Prevent Time booking?” is set as “Yes” for the associated Hold Code.

• If the process parameter 'Stop Direct Clock Booking?' is set as "Yes".

• Enter the following fields “Sign-off Requirements” group box:

Logic for updating Actual Date & Time:

If the status of the discrepancy is changed to any of the terminating statuses mentioned above and the status of the task is changed to "Completed", "Closed", "Deferred", "Incomplete" or "Pre-closed", the ‘Actual Date & Time’ fields are updated as follows:

• If both ‘Actual Start Date & Time’ and ‘Actual End Date & Time’ are left blank, the ‘Actual End Date & Time’ is updated with server date and time and the ‘Actual Start Date & Time’ is updated with the date and time one hour less than the server date and time.

• If only ‘Actual Start Date & Time’ is available, the ‘Actual End Date & Time’ is updated with the server date and time.

• If only ‘Actual End Date & Time’ is available, the ‘Actual Start Date & Time’ is updated with date and time one hour less than the ‘Actual End Date & Time’.

Actual Start / End Date & Time update based on Execution Status of task

1. If ‘Actual Start Date & Time’ is not specified, the following statements are valid:

• The Execution Status of the task is changed to “In-Progress”.

• The system converts the ‘Date & Time’ available in the ‘Exe. Details’ section to the server equivalent date and time by considering the conversion factor defined for the ‘Station’, in the “Common Masters” business component.

• The resulting Date & Time must be earlier than or equal to the server date and time. Otherwise the system displays error message. Example.

2. If 'Actual Start Date & Time' is specified:

• The system converts the specified date and time to the server equivalent date and time by considering the conversion factor defined for the ‘Station’, in the “Common Masters” business component.

• The resulting Date & Time must be earlier than or equal to the server date and time. Otherwise the system displays error message.

3. ‘Actual End Date & Time’ - The logic explained above is also applicable for ‘Actual End Date & Time’, except that the ‘Execution Status’ of the task must be changed to "Completed", "Closed", "Deferred", "Incomplete" or "Pre-closed". Example.

Logic for updating Scheduled Date & Time:

If a work unit is added, and if the Sch. Start Date & Time / Sch. End Date & Time are left blank, the system copies the Exec. Date & Time in the header as the Sch. Start Date & Time and adds ‘Est. Elapsed Time' to the Exec. Date & Time to calculate the Sch. End Date & Time.

On creating a discrepancy or adding a non-standard task,

• During addition of the discrepancy, if both the Plan Start Date & Time and Plan End Date & Time are left blank'  then the Start Date & Time will be updated with the Current server Date & time. Scheduled End Date & Time is computed by adding 1 hour from Schedule Start Date & Time. (i.e. assuming 'Estimated Elapsed Time' as '1' hour)

• During addition of the non-standard task, if both the Schedule Start Date & Time and Schedule End Date & Time are left blank, then the Schedule Start Date & Time will be updated with the Date and time values available at the header. Scheduled End Date & Time is computed by adding 1 hour to Schedule Start Date & Time. (i.e. assuming 'Estimated Elapsed Time' as '1' hour)

• During the addition of the Standard task, if both the Schedule Start Date & Time and Schedule End Date & Time are left blank' then the Schedule Start Date & Time will be updated with the Date and time values available at the header. Scheduled End Date & Time is computed by adding Estimated elapsed time of the task to Schedule Start Date & Time.

• For a Discrepancy or Non standard task, if only the ‘Plan End Date & Time‘ is available, the ‘Plan Start Date & Time’ is computed by subtracting one hour from the ‘Plan End Date & Time‘.

• For a Discrepancy or Non standard task, if only the ‘Plan Start Date & Time‘ is available, the ‘Plan Date & Time’ is computed by adding one hour to the ‘Plan Start Date & Time‘.

• For a Standard task If only the ‘Plan Start Date & Time‘ is available then the ‘Plan End Date & Time’ is computed by adding Estimated elapsed time of the task to Schedule Start Date & Time.

• For a Standard task If only the ‘Plan. End Date & Time‘ is available then the ‘Plan Start Date & Time’ is computed by subtracting Estimated elapsed time of the task to Schedule End Date & Time.

Note: For a given work unit #, the system retrieves the Est. Elapsed Time from the “Maintenance Task” business component.

• Check one of the following boxes in the “Sign-Off Req.” field:

Note: These boxes must be checked and the corresponding employee # for the “Mechanic”, “Inspector” and “RII-Sign-Off” must be entered, only if the Corrective Action is entered in the “Discrepancy Details” group box. The boxes are checked only if the sign-off requirement is specified by the user.

Note: The resource group mapped for the employee must be effective for the current date for at least one skill, if the employee code is entered newly or existing employee code is modified.

Note: If a value is selected in the “Action” drop-down list box and if any of the check boxes is checked, then ensure that the employee code is entered in the respective editable fields. This is applicable only If the option “Enforce Sign-off?” is set as “Yes” in the “Set Process Parameters” page of the “Common Masters” business component.

Note: If the “Task Reporting” is set as “Assigned Employees” for the selected Doc. Type in the “Common Masters” business component, then ensure that the Employee # provided in the above fields is assigned for that Execution Reference # - Task # combination.

If a Non Standard Task # generated with the source as a Discrepancy # and if a corrective action is available for the discrepancy and if any of the check boxes 'Mechanic/ Inspector/ RII Sign off' is in checked condition without any Employee # available against the respective checked box, then the sign-off status for that Corrective Action is updated based on the logic explained in the following table:

Note: If none of the sign off check boxes is checked then the sign-off status is updated as “Not Required”.

The system displays the following fields:

• Enter the following fields:

• Click the “View File” link provided alongside to view the file.

Ensure the following on saving the work information and aircraft maintenance execution reference:

If the current execution status of the work unit is cancelled, then

1.  “Actual Start Date & Time” and / or “Actual End Date & Time” is not entered.

2.  “Actual Man Hrs. is not entered.

If the current execution status of the work unit is “Incomplete” or “Deferred”, then

1. “Actual Start Date & Time” and / or “Actual End Date & Time” is not entered.

2.  “Actual Man Hrs.” is not entered.

Ensure that the Sign Off requirement for 'Mechanic' or 'Inspector #' or 'RII' is not modified if the current execution status of the work unit is “Cancelled”, “Pre-closed”, “Completed”, “Closed”, “Deferred” or “Incomplete”.

If the Execution Status of the work unit is selected as “Cancelled”, “Deferred” or “Incomplete”, ensure that the Clock Status is not “Clock - Direct” or “Clock - Direct & Indirect” for any of the employee for the Work Unit # - Execution Reference # - Seq # combination.

To proceed, carry out the following:

• Select the “Edit Discrepancy Additional Information” link to edit the discrepancy additional information.

• Select the “Edit task Additional Information” link to edit the task additional information.

• Select the “Author Repair Procedure” link at the bottom of the group box to modify the non-standard task details.

Refer to the “Maintenance Task” online help for more details.

• Select the “Revise Deferral Limits” link to revise the deferral limits set for the discrepancy..

Refer to the “Discrepancy Processing” online help for more details.

• Select the “View MEL/CDL Item Details” at the bottom of the page to view the deferral item details.

Refer to the “Discrepancy Processing” online help for more details.

• Select the “View Discrepancy Dates & References” link to view the task / discrepancy date and reference details.

Refer to the “Compliance Tracking & Control” online help for more details.

• Select the “Upload Documents” link to upload the documents.

Refer to the “Object Attachments” online help for more details.

• Select the “View Associated Doc. Attachments” link to view the associated document attachments.

Refer to the “Object Attachments” online help for more details.

• Select the “Record Part Consumption & Return” link to record the part consumption details.

To edit work information

• Select the aircraft maintenance execution reference for which work information is to be edited in the tree structure.

The count of work unit(s) that is associated to the aircraft maintenance execution reference # is displayed alongside the “Work Information” pushbutton.

• Select the “Work Information” pushbutton in the navigation pane. 

The system displays the text “Work Information” at the top of the navigation pane.

The left navigation pane will display the tree interface, in completely exploded form.

The selected “Aircraft Maintenance Execution Reference #” will be the parent node in the tree, and ”Task Cards” will be the first-level node. The tree displays only those tasks with process parameter ‘Execution Operations?’ set as “Yes” in the “Common Master” business component. Tasks which are transferred to sub-assembly Work Orders / Repair Orders, will have the 'Execution Status' set as "Routed for Repair". These tasks are shown in a separate folder "Routed for Repair" in the tree.

The system displays the work units associated to the Execution Reference # under different nodes, based on the value selected in the “Search By” drop-down list box in the “Search Options” group box: Refer to the topic “Tree Interface display logic” for more details.

The tree structure is as follows:

Aircraft Maintenance Exe Ref  #

Task Cards:

1. 1. Planned

   2. In-Progress

   3. In-Complete

   4. Completed

   5. Pre-Closed

   6. Closed

   7. Deferred

   8. Cancelled

   9. Routed for Repair

   10. Duplicate

On clicking any ‘Work Unit #’ node under the ‘Task Cards’ folder of the tree structure,

• the system retrieves the related details of the respective work unit, such as Work Unit #, Work Unit Description, ATA, Job Type, Sign off information, actual start date, end date, schedule start date, end date, actual man hrs, employee codes etc. and displays into the respective fields.

• If the Job Type of the task # is “Component Removal”, the system retrieves the task #, task description, and other related details including the sign-off requirements in the right pane, and also replaces the “Component Details” section with the “Component Removal” section, by copying the part # and serial # in the 'Removed Part #' and 'Removed Serial #' fields.

Note: Each record must have 'Hold Status' and 'Estimation Status' information. If 'Hold' is applicable for a record, it must be represented by an Exclamatory Icon ‘’. If 'Hold' is not applicable for a record, the 'Hold Status Icon' is not displayed. The possible Estimation Status could be "Est. Not Required", "Pending Estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Pending Re-Estimates".

Note: If any information about the work unit is not available, the system indicates it by displaying [NA] in the tree node.

• Select the work information to be modified in the tree interface.

The selected work information is displayed, in the “Work Information” group box to the right.

• Edit this work information, if required.

• Click the “Save” icon in the “Work Information” group box, to save the modified details of the work unit. Dual Authentication

• Select the ‘’ icon, to view the previous work information. Use the tree view as the reference.

• Select the ‘’ icon, to view the next work information. Use the tree view as the reference.

To record new work information

• Select the aircraft maintenance execution reference for which new work information is to be added from the tree interface.

• Select the “Work Information” pushbutton in the left navigation pane.  

• Click the “New Task” icon in the “Work Information” group box to record new work information.

• Enter the following fields in the “ Work Information” group box:

The system displays the following:

• Enter the following in the “Work Information” group box:

Note: You must specify either Work Center # or Repair Agency #, if the Job Type is selected as “Off-Wing”.

On saving AME and work information, when a task is added to the AME Document, if the Job Type is “Off-Wing”, the system copies the Work Center #, Repair Agency # and Component Details to all the associated child tasks.

If the Work center change is allowed then system performs the following function:

1. Updates the Work center of the Tasks for which the Material Issue has not been confirmed and which are in status “Planned” or “In-progress”.

2. Short Closes the Material Request

If the material requests are available in “Authorized”, “Fresh” or “Draft” status and the material issues are available in “Fresh” status for the tasks associated to the A/C Maint. Exe. Ref. #, then

1. if the issue warehouse of the modified work center is same as the issue warehouse of the existing work center of the tasks, then the Material requests that have been already created for the tasks must be retained.

2. if the Issue warehouse of the modified work center is different from the issue warehouse of the existing work center of the tasks, then the system

• • Short-closes the material requests and cancels the material issues that have been created for the task.

  • Updates the work center for the Aircraft Maint. Exe. Ref. # and the tasks.

  • Creates a new material requests for the short closed quantity from the issue warehouse of the modified work center for the task for the Aircraft Maint. Exe Ref. #.

• Click the icon next to the above field, to clear the execution comments.

• Click the icon provided next to the ‘Execution Comments” field to view the execution comments history.

The system displays the following:

• Click the “Save” icon to save the work information. Dual Authentication

Note: The system does not allow completion / closure of a task, if the Execution Status of all the associated Child Tasks is one of the following: “Cancelled”, “Pre-Closed”, “Deferred”, “In-Complete” or “Duplicated”.

The number to the right of the “Work Information” pushbutton is incremented by 1, to indicate that an additional work unit has been added for the Execution Reference.

Note: The system restricts creation of new A/C Maint. Exe. Ref. Documents referring an Offline Work Center (i.e. Work Centers having 'Usage Mode' set as "Offline" in the 'Work Center' business component), in Main Base (if the process parameter ‘Usage Mode’ is “Online” in the “Configurator” business component.

If “Work Unit Type” is selected as “New Task”, then the system generates a non standard task.

When no Execution Ref # is available in the header for the entered Aircraft Reg # and if all the mandatory task  details and Execution ref # are available then on invoke of the work information save, the system generates the Execution Ref #.

When the Execution Ref # is created, the system retrieves and copies the Maintenance Event Information against the Execution Ref #.

On successful generation of the Execution Reference #, the system copies the parameters of the selected Doc. Type on which Execution Reference was generated from the “Common Masters” business component.

For Offline Aircraft (i.e. 'Mode of usage' is "Offline" in the 'Aircraft' business component, the system:

• Ignores auto-addition of overdue tasks / discrepancies and incomplete tasks in the Main Base, regardless of process parameter setting available in the “Common Master” business component.

• During offline field base usage, restricts addition of task if one of its child tasks in repair scheme is to be performed in a Repair Agency #, if the process parameter ‘Allow addition of Repair station tasks for Offline Usage’ is set as “Not Allowed” in the 'Configurator' business component.

• On task addition into package based on repair scheme definition, the system sets the package work center available in the 'Exe. Details' section, as the task execution work center.

When the primary task attains any of the terminating statuses such as “Closed”, “Incomplete”, “Pre-Closed” or “Deferred” or when the task is deleted, the system saves the details entered and displays a pop-up warning message if there exists any execution related task in the current Execution Ref #. The relationship between the primary task and the related task must be either “Concurrent-Group” or “Concurrent-Specific” as defined in the “maintenance Task” business component.

When a task is added, the system creates the Execution reference document in following statuses:

• If the task is added in any one of the following statuses: “Planned”, “Cancelled”, “Deferred”, “Incomplete”, “Pre-closed”,  the Execution Ref # is created in “Planned” status.

• If the task is added in “In-Progress” status, the Execution Ref # is created in “In-Progress” status.

• If the Task is added in “Completed” or “Closed” status, the Execution Ref # is created in “Completed” status.

If a task is added to the Aircraft Maintenance Execution document and for any of the part requirements if a Material Request exists with MR Class as “Maintenance” for the 'Part # -Stock Status - Warehouse’ combination, having Aircraft Reg # same as the Aircraft Reg # of the AME document and not associated to any other execution document, then the system automatically pegs the MR for that part # of the 'Task #'.

When a task is added to Execution Ref #, if there exists any 'Conflict' relationship for the task in the “Maintenance Task” business component, the system ensures that none of the related tasks are available in the Execution Ref # in status other than “Cancelled”, “Closed”, or “Pre-closed” status.

If the Execution Status of the task is updated to “Completed” / “Closed” / “Pre-closed”, the system updates the parameter values recorded against the Aircraft Maintenance Execution Reference, with Execution Ref. # / Line # / Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

If the execution status of the standard task is changed to “Completed” or “Closed”, the system updates the compliance details, last performance date / value and the next schedule value / date for the un-forecast work units, in the Aircraft Maintenance Program and Component Maintenance Program.

If an employee has signed-off for an ‘On-wing’ or a ‘Component Removal’ job identified for an ETOP position code, the system does not allow the same employee to sign-off for a different ‘On-wing’ or ‘Component Removal job identified for the ETOP position code identified as reference to the previous ETOP position code.

The system updates the parameter values for tasks during the completion. This is applicable only for the tasks for which parameter details have been updated.

The system creates a Material Return document, if the parts are pending for return. Refer to the section “Auto Return of parts on package completion” for more details.

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.

Unplanned Task Addition:

When a Task is added to a package, if the Task is available in the ”Review Fleet Maintenance Plan” page of the “Aircraft Maintenance Planning” business component, without being assigned to any other Package (Aircraft Maint. Exe. Ref. #), then the Package # will be updated back to the Task in the ”Review Fleet Maintenance Plan” page.

Note: The above updates do not happen, if ’Long Term?’ is set as ”Yes” or ”No” (other than ‘Not Applicable’) for the Task in the Maintenance Program of the Aircraft, and its ‘Instance’ in the ”Review Fleet Maintenance Plan” page is greater than 1.

Addition of Incomplete, Overdue and Due tasks on saving AME, discrepancy and work information:

On creation of a new package, the tasks that are pending for compliance on the aircraft, are automatically to the Package. This happens based on the parameters set in the “Set Process Parameters” page of the “Common Masters” business component.

Incomplete Tasks

If the parameter “Auto Inclusion of Incomplete Tasks” is set as “Required”, the system does the following.

• Copies the incomplete tasks with 'Actual Start Date & Time' earlier than the 'Planned Start Date & Time' of the package.

• Copies all the part requirements, component removal details, resource requirements and parameter reading requirements of the task and also its 'Concurrent' related tasks.

• Updates the 'Execution Status' of the task in the package as “Planned”.

Overdue tasks:

If the parameter “Auto Inclusion of Overdue Tasks” is set as “Required”, the system performs the following:

• Copies the tasks with 'Schedule Date' earlier than the Server Date, into the package.

• Copies all the sub tasks, sign-off requirements, part requirements, component removal details, resource requirements and parameter reading requirements of the task and also its 'Concurrent' related tasks.

Due Tasks:

For the parameter “Basis for Auto Inclusion of Due Tasks”, the system performs the following.

• Copies the tasks with the 'Plan Date' equal to the Server Date, if the parameter is set as “Planned Start Date”.

• Copies the tasks with the 'Schedule Date' equal to the Server Date, if the parameter is set as “Schedule Start Date”.

• Copies the tasks with the 'Plan Start Date’ or ‘Schedule Date ' equal to the Server Date, if the parameter is set as “'Planned Start Date & Schedule Start Date”.

• Copies all the sub tasks, sign-off requirements, part requirements, component removal details, resource requirements and parameter reading requirements of the task and also its 'Concurrent' related tasks.

Note: In all the cases mentioned above, tasks having ‘Conflict’ relationship among them may not be copied.

Tasks having ‘Predecessor Constrained’ relationship and that are not complied for the aircraft at least once, will get added to the Package.

Aircraft Condition Update:

The system updates the condition of the aircraft to “Under Maintenance”, if the condition of the aircraft is saved as “Operational” and if the following conditions are satisfied:

1. If the parameter “Aircraft Condition Change” is set as “Required” for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.

2. If the status of the Execution Ref # is set as “In-Progress”.

The system updates the condition of the aircraft to “Operational”, if the condition of the aircraft is saved as “Under Resolution” and if the following conditions are satisfied:

1. If the parameter “Aircraft Condition Change” is set as “Required” for the selected Package Type in the “Set Process Parameters” page of the “Common Masters” business component.

2. If the status of the Execution Ref # is set as “Completed”.

3. If the parameter “CoM Required” is set as “Not Required” for the current Package #.

Work Center Update:

The system updates the Work Center of the Discrepancy NST task with the Work Center specified in the header, if the Discrepancy is moved from one package to another and the Work Center of the NST and Discrepancy NST task are different.

If the Option “Allow Package execution across multiple primary Work Centers” is set as “Yes” in the “Set Process Parameters” page of the “Common Masters” business component, then the system updates the work center as follows:

1. Update the Work Center of the task created for the Discrepancy on every update of the context work center in the header. The update is done only to the Discrepancy (NST Task of the Discrepancy).

2. On creation of the task, the system updates the context work center in the header as the work center for the task if not provided by user. If user selects a value at the task level work center, the same must beis retained.

3. On creation of the discrepancy, the system updates the work center in the header as the work center for the NST task created for the discrepancy.

4. Updates the work center of the task only if the Context work center ins the header is different from the Originating Work Center.

Conditions for deletion of work unit:

The system does not allow deletion of work unit from the Aircraft Maintenance Execution reference document on following conditions:

1. If the planning type for the work unit is “Planned”.

2. If time booking has been recorded.

3. If parameter update has been recorded for that work unit.

4. If issue has been raised for that work unit.

5. If Component replacement # is generated for that work unit.

6. If any sign-off comments has been updated

7. If any sign-off has happened for that work unit.

8. If any resource booking is done for that work unit.

9. If the execution status of the work unit is other than “Planned”.

Deletion of task:

On deletion of the task, the system performs the following:

• Removes the Resource estimates available against the task.

• Removes the Part Requirement available against the Task.

• Re-calculate the estimated Resource Cost and Material Cost by reducing the amount of the removed resources and parts.

• Short closes any Open Material Requests against the Task which are available in “Authorized”, “Fresh” or “Draft” status.

• Cancels the issue document if issue is available against the MR in “Fresh” status.

• Hard-Deletes the task from the package.

• Updates the status of the task from “Allocated” to “Pending” in the Pending Tray.

Customer order creation

The system creates a customer order in “Processed” status comprising the package, if the ownership of the aircraft is “Customer”. Further, based on attributes including A/C Reg #, A/C Model #, A/C MSN #, Customer PO # and Customer #, the system determines the relevant contract for the customer order.

The stock status of the parts required by the package is set to the preferred stock status of the contract. However, if any part is covered by a PBH agreement, the stock status will be set to PBH.

The warehouses for each of the parts will be the Service Request warehouse that is valid for the work center of the package and the part type of the part. However, customer order is automatically generated in Processed status only if the contract status is “Approved”, the contract stage is “Firm” and, the planned/start date of the package pertains to the effective period of the contract.

Task / Document Status Update:

Ensure that only those tasks which are in “Fresh” or “Planned” status are modified to “Cancelled” status.

Ensure that the task details are not modified if the task is in “Cancelled”, “Pre-closed”, “Closed”, “Incomplete” or “Deferred” status.

Ensure that tasks which are in “Incomplete” or “Deferred” status are modified to “In-progress” status.

If the Task that is being complied is having the previous instance in “Allocated” or “Pending” status, then status of the task cannot be modified to “Completed” or “Closed”.

The task status cannot be modified from “In-progress” to “Planned”, “Cancelled” or “Deferred” and from “Completed” to “In-Compete”, “Pre-closed”, “Deferred”, “Cancelled” or “Completed”.

Ensure that the clock is not available in Start mode for the task, if the task is in “Completed”, “Pre-closed”, “Closed”, “In-complete” or “Deferred” or if the Execution Reference Status is changed to “Completed” or “Closed”.

Ensure that there is no Sign-Off pending for the task, if the status of the task is changed to “Completed”, “Pre-closed” or “Closed”, or if the Execution Reference Status is changed to “Completed” or “Closed”.

Ensure that no Pending Return Qty is available for the task, if the task status is changed to “Pre-closed”, “Closed” or if the Execution Reference Status is changed to “Closed”. This is applicable only if the parameter “Enforce Excess / Core Returns” against the package is set as “Yes” in the “Set Process Parameters” page of the “Common Master” business component.

On changing the task status to “Closed”, “Pre-closed” or “Cancelled”,  or Execution Status to “Closed” / “cancelled”, the system short closes all the Material Requests that are in “Draft”, “Fresh”, or “Authorized” status. If any of the material requests is available in partial issued status short-closure must be done at line level by reducing the Pending requested quantity to zero.

The system updates the Pending Tray Status back to “Allocated” on update of task status to from “Deferred” or “Incomplete” to “In-progress”. Also the Execution date and Time is updated as the Actual start date and Time, if already not available for the task.

When a work unit which is having the forecast reference # associated to it, is modified to “Deferred” or “Incomplete”, the system updates Transient Status as “Null” and Job Status as “Pending” in the 'Aircraft Pending Tray' of the “Compliance Tracking & Control” business component.

Ensure that the Aircraft Maintenance Execution Reference Status cannot be modified from “In-progress” or “Completed” to “Planned” or Cancelled”. The details of the Aircraft Maintenance Execution Reference in “Closed” or “Cancelled” status cannot be modified.

The Aircraft Maintenance Execution Reference status is cannot be modified to Cancelled if any of the task is in status other than “Cancelled”.

Task Status Change

The modification of Task Status change combination and the parent / child task change behavior for various combinations of task status, are as shown in the matrices below:

1. Matrix 1: Task Status Change Combinations.

2. Matrix 2: Parent Task Status Change behavior for various combinations of First Child Task Status Change.

3. Matrix 3: Parent Task Status Change behavior for various combinations of Last Child Task Status Change.

4. Matrix 4: Child Task Status Change behavior for various combinations of Parent Task Status Change.

Note: If both the Parent Task and the Child Task have Operational properties (i.e. ‘Execution Operations’ flag is set as “Yes” corresponding to their respective WBS Codes), the Task auto-status change mentioned above, is not applicable.

Example: Consider a Parent Task (P1) and a Child Task (T1) both having Operational Properties. Status change of Task "T1" will not affect the Status change of Task "P1" and vice versa.

Discrepancy NST status Update:

On Creation of discrepancy, the associated task is created in “Planned” status.

The status of the NST Task against the discrepancy is updated to “Completed” if the Discrepancy status is changed to “Closed” or “Deferred”.

The system updates the status of the NST Task against discrepancy as follows on movement of discrepancy to another Exe Reference #:

1. Updates the status of the NST task to “Planned” if no modification is done and no Action is selected and the status of the Discrepancy is “Under resolution”.

2. Update the status to “In-Progress” if following conditions are satisfied:

1. • On issue of parts (when consumption is updated)

   • Whenever start clock is invoked (both from current business component or from “Record Employee Timesheet page of the “Aircraft Maintenance Execution” business component)

   • When Actual start date & time / Actual End date & time / Actual Man hrs is updated.

   • When employee code is entered against any sign-off requirement identified.

   • When resource consumption is updated with the actual times.

   • When employee time records are updated

   • When parameters values are updated.

   • When Component Replacement is updated.

3. Updates the NST status to “Completed” if the discrepancy status is “Deferred” or Closed”.

Task Transient Status Check

If the 'Transient Status' of the task is “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component, ensure that none of the following is modified: (a) Execution Status, (b) Work Center, (c) Job Type, (d) Component Details, (e) Plan Start / End Date & Time, (f) Actual Start / End Date & Time, (g) Est. / Actual Man. Hrs, (h) Sign-Off Requirements.

If the ‘Transient Status’ is not "Hold" and if ‘Hold Details’ are available for the task with ‘Hold Status’ as “Open” on current date and time in the “Record Work Hold” page, ensure that the Execution Status of the task is not modified. This is true only if the process parameter “Prevent Task Status Change?” is set as “Yes” for the associated Hold Code in the “Set Process Parameters” page of the “Common Masters” business component.

Modification of sign-off requirements:

When the user adds / modifies the task and clicks the “Save” icon, the system saves the task either with the sign-off requirements defined for the task at task level or with the user selected sign-off requirements, based on the parameter “Allow modification of Task Sign-Off requirements” for the package type of the current Execution Ref #, set in the “Set Process Parameters” activity of the “Common Masters” business component. Refer to the table.

Operator Effectivity on task addition:

When a new task is added to a package, the following statements are true:

1. The newly added task must be effective to the Maintenance Operator # defined for the Aircraft Reg # entered in the current page.

2. The Task # irrespective of its effectiveness, can be added to Aircraft Reg # which does not have a Maint. Operator.

3. If the Task # does not have operator effectivity, it can be added to the package of any Aircraft Reg #, irrespective of the effectiveness of the task.

Note: Effectivity must be checked for the Task # - Base Model # combination, if the Task applicability is Aircraft. If the Task applicability is "Component" or "Engine", the effectivity must be checked for Task # only.

Completed Package Status change validation:

On saving the discrepancy and work information, for internal packages, the system allows you to change the status of the package / task from “Completed” to “In-progress”, only if:

• The process parameter  'Allow re-opening of completed packages / tasks?' is set as “Allowed” for the Package Type in the “Set Process Parameters” page of the “Common Master” business component.

For external packages, you can change the status of the package / task from “Completed” to “In-progress” if:

• The process parameter  'Allow re-opening of completed packages / tasks?' is set as “Allowed” for the Package Type in the “Set Process Parameters” page of the “Common Master” business component, and if:

• Invoice is not raised against that AME #.

When the work information and Execution Reference are saved

The system performs the following on saving the work information and Execution Reference:

• If “Allow sign-off entry by different employee?” is set as “Not Allowed” for the selected Doc Type in the Set Process Parameters” page of the “Common Masters” business component and if any of the check boxes (Mechanic or Inspector or RII Sign off) in the “Sign-Off Requirements” group box is in checked condition, the system ensures that the Employee # removed from the respective editable boxes is same as the 'Employee # mapped to the login user.

• If the “Permit Dual Sign-off by the employee?” is set as “No” for the selected Doc. Type in the “Set Process Parameters” page of the “Common Masters” business component, the same Employee # must not be available against the ‘Mechanic' and 'Inspector' editable boxes.

• If the “Permit Dual Sign-off by the employee?” is set as “Allowed for Flight Ops” for the selected Doc. Type in the “Set Process Parameters” page, then ensure that the same Employee # is not available against 'Mechanic' and 'Inspector' editable boxes. This is applicable only if the “Operations Type” for the referenced document # is set as “Repair Station”.

• Ensures that an Employee # is available in the 'Mechanic' Sign-off editable box, if an Employee # is available in 'Inspector' or 'RII-Sign off' editable box. This is applicable only if the sign-off requirement for the discrepancy has been identified as 'Pending Inspector and Mechanic', and 'Mechanic' sign off has already been performed.

• Ensures that an Employee # is available in the 'Inspector' Sign-off editable box, if an Employee # is available in 'RII-Sign off' editable boxes. This applicable only if the sign-off requirement for the discrepancy has been identified for 'Pending Insp & Mech' and 'Pending RII Sign off' (or) 'Pending Inspector' and 'Pending RII Sign off', and 'Inspector' sign off has already been performed.

• Ensures that the Employee # entered in the Mechanic / Inspector / RII editable boxes in “Task Sign-Off Details” / “Default Options” group box has a valid license / certificate to sign-off  the task / Sub-Task based on the following conditions:

1. 1. If a “Sub task-Skill”  combination having the “Sign-Off ?” flag set as "Yes", also has  the “Approval Reqd. ?” flag set as "Yes" in the “Edit Resource / Sign-Off Requirements” screen  in the "Maintain Activated Tasks” activity of the “Maintenance Task” business component.

   2. If for  the row selected in the “Task Sign-Off Details” multiline, the value "Sign Off" or "Void" is selected in the “Sign-Off Action” drop-down list box.     

• Considers an Employee  to have a valid License for Sign-Off based if the following conditions are true:

1. 1. For sign-off at Task level: License requirements have to be satisfied for all applicable “Sub-Task-Skill” combinations, having ‘Sign-Off’ and ‘Approval Reqd. ?’ flags set as “Yes” in the “Edit Resource / Sign-Off Requirements” page in the “Maintain Activated Tasks” activity of the “Maintenance Task” business component.  

   2. For sign-off at Sub-Task level: License requirements have to be satisfied for all Skill Resources mapped to the Sign-Off Sub-Task, having ‘Sign-Off’ and ‘Approval Reqd.?’ flags set as “Yes”.

   3. For sign-off of skill resource:  License requirement have to be satisfied for the combination:  Skill Code- Aircraft Model # - License #, in the interacting “Record Employee License Information” page in the ”Record Personal Information” activity of the “Employee Personal Information” business component.

• Verifies if there is a valid Certificate for Sign-Off in the case of Employees without a valid License.

• Considers an employee to have a valid certificate for sign-off if the following conditions are true:  

1. 1. Certificates having the following mapping will be deemed as valid for the Task Sign-Off : Certificate – Work Unit – Aircraft Model. Here, Work Unit could refer to either: Sign-Off Task / Parent Task of Sign-Off Task) / Root Task of Sign-Off Task. More.. The employee to Certificate mapping can be done in the "Edit Certificate Effectivity Information" page in the “Maintain Certificate Information” activity of the “HR General Information” business component".

   2. The employee has at least one Certificate as mentioned in point (i) above, in “Active” status for the given Sign-Off date. The Employee to Certificate mapping can be done in the "Record Employee Certificate Information" page in the "Record Personal Information" activity of the      "Employee Personal Information" business component.

The Execution Status for a work unit is selected based on the current execution status:

• The Execution Status of the work unit is selected as “Cancelled” only if the current execution status of the work unit is “Planned” and if the planning type of the work unit is “Unplanned”.

• The Execution Status of the work unit is selected as “Incomplete” or “Deferred”, only if the current execution status of the work unit is either “Planned” or “In-Progress”.

• The Execution Status of the work unit is selected as “Pre-closed” only if the current execution status of the work unit is “In-Progress”. The execution status of all the tasks associated to the work unit is updated as “Pre Closed” in this case and the tree is refreshed by moving the task from ‘Planned  / In-progress’ folder to ‘Pre-closed’ folder.

• The Execution Status of the work unit is not selected as “In-Progress” if the current execution status of the work unit is in “Closed” or “Pre-closed” or “Cancelled”.

• The Execution Status of the work unit is not selected as “Completed” under the following conditions:

1. if the current execution status of the work unit is in “Closed” or “Pre-closed” or “Cancelled” or “Deferred”.

2. if any sign off (Mechanic/ Inspector / RII sign off) is pending for any of the work unit.

• The Execution Status of the work unit is not selected as “Closed” under the following conditions:

1. if the current execution status of the work unit is in “Pre-closed”,  “Cancelled” or “Deferred”.

2. if any sign off (Mechanic/ Inspector / RII sign off) is pending for any of the work unit.

3. if for any record, “Start Date & Start Time” is specified and “End Date &  End Time” is not specified for the work unit # - Execution Reference #  combination across all the employees  in the “Record Employee Time sheet” page of the “Aircraft Maintenance Execution” business component.

4. if both “Actual Start Date & Time” and “Actual End Date & Time” are not available or if one of them  is available with “Actual Man Hours” field left blank.

5. if the options “Enforce Excess Core Return” is set as “Yes” and “Auto Return on” is set as “Not Required” for the selected Doc. Type in the “Set Process Parameters” page of the “Common Masters” business component and if the 'Pending Return Quantity' is greater than zero for any records in the “Parts Consumptions Details” table.

If the work unit having Forecast reference # associated to it and Planning Type as “Planned”, is changed from “Deferred” or “In-Complete” status to “In-Progress” status, then ensure that the same instance of the Work Unit # is not in “Allocated” status with the Reference Doc # other than the current Execution Reference #.

If the work unit having forecast reference # associated to it, is changed from the “Deferred” status or “Completed” status to “In-Progress” status, the system updates the Execution Status of all the tasks associated to the work unit as “In-Progress” in the Execution Reference document.

The system performs mechanic or inspector sign-off all the subtasks in that work unit, which are pending for mechanic or inspector sign off. The RII Sign-off must be maintained at Work Unit level.

Task Sign-Off cannot be done by either Mechanic / Inspector / RII, if the current Execution Status of the task is "Cancelled" or "Routed for Repair" or if the Job Type is “Off-Wing”.

The system updates the Execution Status of the Work Unit to “Completed”, when the sign-off status is updated as “Signed-off”.

When a work unit is added to the Execution Reference # and if the “Execution Status” drop-down list box is selected as “Planned”, then the system updates the execution status as of all the tasks associated to that Work Unit # as “Planned”.

If the Execution Status of the Work Unit # is changed to “In-Progress”, the system updates the Total Estimated Cost for that Work Unit # against the CAPEX Proposal # of that work unit #, in the interacting “Asset Planning business component. This update happens only if the Expense Type of the Work Unit # is “Capital”.

When a task is added to the Execution Reference, the system retrieves and displays the part requirement details at task level in the “Material Request” section.

The system does not allow you to modify the ‘Job Type’ of the task, if the Execution Status of the task is other than “Planned”.

The system derives the 'Estimation Status' of the AME document as the lowest hierarchy value set for any of the Tasks / Discrepancies associated to the AME document. The 'Estimation Status' hierarchy is as follows: "Pending Estimates", "Pending Re-estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Not Required".

• On compliance of the task, if Maintenance Type is ‘Retire’, the system automatically sets the component condition to ‘Phased Out’ and Record Status to ‘Inactive’ under the following conditions:

• • The component is not currently attached to any aircraft  or NHA

  • The warehouse allows components in Phased Out condition

Addition of tasks to AME:

A task can be added to the AME, only if the process parameter 'Workscoping Element ?' is set as "Yes" for the 'WBS Code' associated to the Task, in the “Common Master” business component .(i.e. only Workscoping Tasks can be added to the A/C Maint. Exe. Ref. Document).

The system allows addition of non-routine tasks to AME, only if a default WBS Code is available for Non-Routine Task generation in the “Common Master” business component.

A task can be added to the AME, only if at least one of the following conditions is satisfied:

1. • The process parameter ‘Execution Operations?' must be set as "Yes" for the 'WBS Code' associated to the Task.

   • The task must have at least one Operational-Level Task mapped under it, in its Repair Scheme Definition.

On saving AME, Discrepancy and Work Information, the system does not associate tasks (Perpetual, Event Driven or Overdue Tasks) present in the ‘Aircraft Maintenance Program’ to the AME document, if any of the following is true:

1. • For the 'Hold Code' corresponding to the ‘AME document’ / 'Customer Order', if the process parameter 'Stop A/C Maint. Execution ?' parameter is set as "Yes" in the “Common Master” business component.

   • For the 'Hold Code' corresponding to the ‘AME document’ / 'Customer Order', if the process parameter 'Stop A/C Maint. Execution ?' parameter is set as "Till Estimation Confirmation", the system associates only those tasks which does not have any Estimation Requirements identified.

   • For the 'Hold Code' corresponding to the ‘AME document’ / 'Customer Order', if the process parameter 'Prevent New Tasks Addition ?' parameter is set as "Yes".

On saving AME, Discrepancy and Work Information, when tasks get associated to AME document from Repair Scheme Definition, the system updates the ‘Execution Action’ of the task as “Duplicate” if following conditions are satisfied:

1. • If Task # - Seq # combination is already available in the AME document.

   • If the details available in the “Component Details” corresponding to Task, are same as details of the existing task available in AME document.

Note: When adding a new task, if the ‘Execution Action’ is not updated based on the conditions mentioned above, the system performs the following:

• Displays an error message, if Seq # specified is already available in the AME document.

• Update the 'Execution Action' of the newly added Task as "Execute", if Seq # is left blank or if not available in the AME document.

The system does not allow you to create a new task or modify the details of the existing task with Execution Status as "Routed for Repair".

The system does not allow you to modify the Execution Status of the task to a value other than "Cancelled", if the Job Type of the task is "Off-Wing".

Hold Status Validation:

In case an A/C Maint. Exe. Ref. Document is on hold, the system allows you associate a new task to an AME document, only if the process parameters:

1. • 'Stop A/C Maint. Execution ?' is not set as "Yes" for the 'Hold Code' corresponding to the ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.

   • 'Prevent new Tasks addition ?' is not set as "Yes" for the 'Hold Code' corresponding to the ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.

In case an A/C Maint. Exe. Ref. Document is on Hold, the system allows you to modify the existing task details, only if the process parameters:

1. • 'Stop A/C Maint. Execution ?' is not set as "Yes" for the 'Hold Code' corresponding to the ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.

   • 'Prevent Task Status Change ?' is set as "Yes" for the 'Hold Code' corresponding to the ‘A/C Maint. Exe. Ref. Document’ / 'Customer Order'.

Task Deferral:

The allows you to defer the planned tasks, only if the process parameter "Allow Deferral of Planned Tasks ?" is set as "Yes" for the 'Package Type'.

Note: Applicable 'User Roles' for each 'Package Type', can be identified using the 'Deferral Responsibility Roles' process parameter set in the “Common Master” business component. The system allows Task deferral only for users belonging to these defined User Roles.

Closure of Child Discrepancies for task closure:

If the process parameter "Mandate completion of related Discrepancies before closure of Inspection Tasks ?” associated to the 'Package Type' of the 'A/C Maint. Exe. Ref. Document' is set as "Yes", the system allows completion / closure of the task, only if all the child discrepancies associated to the Task are in terminating statuses i.e. "Closed", "Transferred", "Deferred" or "Cancelled".

If the process parameter mentioned above is set as "No", the system allows completion / closure of the task, irrespective of the status of the child discrepancies associated to the task.

Note: If a Discrepancy has a Task specified against it in the ‘Source Type & No’ control (Discrepancy section), the Discrepancy is considered as the Child Discrepancy of the specified Source Task.

The system updates the status of all the tasks associated to the work unit # as “In-progress” and updates the Execution Status and the document status of the Execution Reference # to “In- Progress”, on satisfying any of the following conditions:

1. On issue of parts

2. Whenever start clock is invoked (either from the current page or from the “Record Employee timesheet” page of “Aircraft Maintenance Execution” business component”)

3. When Actual Start Date & Time / Actual End Date & Time / Actual Man hrs is updated.

4. When employee code is entered against any sign-off requirement identified.

5. When resource consumption is updated with the actual times.

6. When employee time records are updated

7. When parameters values are updated.

8. When Component Replacement is updated.

If the Execution Status of a task is set as “Cancelled”, the system checks for the existence of a duplicated task associated to the AME document, whose corresponding ‘Duplicated Task-Tracking # matches with the Tracking # of the cancelled task.

• If one such task exists, the system updates its Execution Status as “Planned”.

• If more than one such task exist, the system updates the Execution Status of the first task (taken as per order of Tracking #) as “Planned”. The Execution Status of the remaining tasks will be retained as “Duplicated”.

Note: ‘Duplicated Task Tracking #’ refers to the Tracking # of the Task which had caused the duplication. The above update happens only if the 'Parent Task' associated to the 'Duplicate Task' has Execution Status set as "Planned" or "In-Progress".

If the Job Type of the work unit is “Component Replacement'”, then on update of Execution Status as “Completed” for that work unit, the system replaces the “Component Details” section with the “Component Replacement” section by copying the values of Part # and Serial # to Removed Part # and Serial # in the “Component Replacement” section.

If the status of the tasks is changed from “In-Progress” to “Pre-closed” / “Completed” and if all the tasks in that Execution Reference # are in “Completed” or in any other terminating statuses such as “Cancelled”, “Deferred”, “In-complete”, “Closed” or “Pre-Closed”, then the system updates the status of the Execution Reference in the header as “Completed”.

The system updates the status of the Execution Reference as

• “Planned”, if the work units are in “Planned”, “Deferred” or “Cancelled” status.

• “In-Progress”, if at least one work unit is in “In-progress” status.

• “Completed”, if all the work units are in any of the terminating statuses such as “Cancelled”, “Deferred”, “Incomplete”, “Closed” or “Pre-Closed”.

The system updates the compliance history, if the execution status of the task is changed to “Pre-closed” / “Completed" / "Closed" status.

If any discrepancy is associated to the work unit, if the Execution Status is set as “Pre-closed” / “Completed” and if the option “Auto closure of Discrepancy on completion of associated Task” is set as “Yes” for the selected Doc. Type in the “Set Process Parameters” page of the “Common Masters” business component, then the system updates the record status of the discrepancy as “Closed”. The system also updates the resolution history with the station, sign-off information, record status, latest corrective action for that discrepancy # and other information in the “Discrepancy Processing” business component.

Impact of Execution Status of work unit on Execution Status of tasks:

• If the Execution Status of the work unit is selected as “Completed” then the system updates the execution status of all the tasks associated to the work unit as “Completed”. The ‘Work Information’ tree is refreshed by moving the task from ‘Planned / In-progress’ folder to “Completed” folder.

• If the Execution Status of the work unit is selected as “Closed”, the system updates the execution status of all the tasks associated to the work unit as “Closed”. The ‘Work Information’ tree is refreshed by moving the task to ‘Completed’ folder.

• If the Execution Status of the work unit is selected as “Cancelled” the system updates the execution status of all the tasks associated to the work unit as “Cancelled”. The tree is refreshed by moving the task to ‘Cancelled’ folder.

• If the Execution Status of the work unit is selected as “Pre-closed” then the system updates the execution status of all the tasks associated to the work unit as “Pre-Closed”. The tree is refreshed by moving the task from ‘Planned’ / ‘In-progress’ folder to ‘Pre-closed’ folder.

• If the Execution Status of the work unit is set as “Deferred” the system updates the execution status of all the tasks associated to the work unit as “Deferred”. The tree is refreshed by moving the task to ‘Deferred’ folder.

• If the Execution Status of the work unit is set as “Incomplete” the system updates the execution status of all the tasks associated to the work unit as “Incomplete”. The tree is refreshed by moving the task to ‘Deferred’ folder.

For every change in the status of the task / Execution Ref. #, system updates the status log with 'Entity Changed', 'From Status', 'To Status', ‘Performed At’ (Station), ‘Changed by’ (Employee Name) and ‘Changed Date & Time’.

Related Task Addition:

If the aircraft is customer-owned, when a package is created or when a task is added to the package, the system adds the related tasks of the selected tasks to the package, as follows:

Case1:

If the ‘Maintenance Program’ of the aircraft is in “Active” status, the system copies the following:

1. Tasks that are available in the program with 'Prog. Item Type' as "Base" and share 'Block Schedule' relationship with the selected Task.

2. Tasks that share any of the following relationships with the selected Task:

• Concurrent Exec. – Specific

• Concurrent Exec. – Group

• Concurrent Exec. – Conditional

Case2:

If ‘Maintenance Program’ of the aircraft is not available / not available in 'Active' status, then system copies the tasks that share any of the following relationships with the selected Task:

• Block Schedule (System will not check for the existence of Primary and Related Tasks in the Maintenance Program)

• Concurrent Exec. – Specific

• Concurrent Exec. – Group

• Concurrent Exec. - Conditional

Auto Reconcile Update:

When the ‘Execution Status’ of a task / package is changed to “Closed”, if the ‘Issue Cost’ of the component pending for return is zero, and if it is attached to an aircraft / component or available in one of the documents, the system updates the “Reconcile Qty Core’ in the “Record Part Consumption & Return” page of the “Aircraft Maintenance Execution” business component, as follows:

Reconcile Qty Core = Current value of Reconcile Qty Core + Pending Return Qty Core.

The above update happens only if the following attributes are defined for the Package Type of the A/C Maint. Exe. Ref # in the “Define Process Entities” page of the “Common Masters” business component

• “Enforce Excess/ Core Returns?' is set as "Yes".

• “Auto Reconciliation of Components” is set as "Required - On Task Closure".

Note: If the reconcile update happens, the system performs the following:

1. Updates the 'Pending Return Qty - Core' column as zero (i.e. the component that was pending for return will no longer be pending for return).

2. Updates the “Remarks” field in the “Record Parts Consumption” page against the Execution Ref. # -Task # - Part # combination with the text "Auto Reconcile Update on Task Closure".

Holding / releasing task

• Enter the following in the “Hold / Release” section:

• Click the “Hold” pushbutton to hold the task.

Note: Only those tasks that are in “Planned” or “In-Progress” status, can be put on hold. The system updates the Hold Status of the AME document and Customer Order based on the value of the process parameter ‘Hold Escalation Level’ set for each Hold Code in the “Common Master” business component.

Offline Field Base operations: System shall restrict application of Hold on Tasks if process parameter - "Allow utilization of Holds for Offline Usage" is set as "Not Allowed" in the interacting 'Configurator' business component.

• Click the “Release” pushbutton to release the task that is held.

Note: Ensure that the task is on hold for the selected ‘Hold Code’.

The discrepancy / task must be released from hold, only if the following conditions are true:

1. The process parameter 'Release Responsibility' must be set as "Execution” for the hold code in the “Define Process Entities" activity of the "Common Master" business component.

2. The process parameter 'Release Responsibility Roles' set for the hold code must match with the login role.

• Select the “Record Work Hold” link to view / record work hold details for the task.

Refer to “Work Monitoring and Control” online help for more details.

Recording sign-off and work completion details

• Click the  icon in the “Work Information” section.

 The “Record Sign-Off & Work Completion” page appears. The sign-off details are displayed either at Task level or sub task level.

Note: This page can be invoked only for tasks with the 'Execution Status' set as "Planned", "In-Progress", "In-Complete", "Completed" or "Deferred" and tasks whose Job Type is other than “Off-Wing”.

To cancel work information

• Select the work information to be cancelled from the tree structure.

The selected work information is displayed, in the “Work Information” group box to the right.

Note: You can cancel the work units whose statuses are “Pending” and for which “Sign- Off” is not available.

• Click the “Cancel” icon '' in the “Work Information” group box to cancel the selected work information.

You cannot delete the task, if the Transient Status of the task is “Hold”.

The system does not allow cancellation of the work unit on following conditions:

• If the Planning Type of the work unit is “Planned”.

• If time booking has been recorded.

• If parameter update has been recorded for the work unit.

• If material request has been raised for the work unit.

• If Component replacement # is generated for the work unit.

• If any sign-off comments have been updated.

• If any sign-off has happened for the work unit.

• If any resource booking is done for the work unit.

• If the Execution Status of the work unit is other than “Planned”.

Note: If the “Task status change on Material Issue confirmation?” process parameter for the entity type “Package Type” of the entity “All Packages” in the “Define Process Entities” activity of Common Master is ‘0’, you cannot cancel a task, if a stock issue has already been confirmed or work actuals recorded against the task.

During deletion of a task which is held, the system revokes the 'Hold' applied on the task, and allows deletion of the task. If the 'Hold' applied on the task, was escalated to the 'A/C Maint.Exe. Ref.' / 'Customer Order', the same must also be revoked.

You can delete only those tasks whose Execution Status is “Planned”, “Cancelled” or “Duplicated”. When a rask is deleted from an AME document, the system deletes all the associated child tasks from the AME documents.

When a task is deleted from an AME document, system checks for the existence of tasks associated to the AME document, which has the 'Duplicated Task Tracking #', matching with that of the deleted task's 'Tracking #'.

• If such a task exists, the system updates the ‘Execution Status’ of that task as “Planned”.

• If more one such task exist, the system update the ‘Execution Status’ of the first task (considered in the order of ‘Tracking #’) as “Planned”. The Execution Status of the remaining tasks will remain as “Duplicated”.

Note: ‘Duplicated Task Tracking #’ refers to the Tracking # of the Task which had caused the duplication. The above mentioned rule is applicable only if the 'Parent Task' (if exists) associated to the 'Duplicate Task' has ‘Execution Status’ set as “Planned" or "In-Progress".

To print Task Card:

• Click the “Print Task Card” icon ‘ ’ in the “Work Information” group box, to print the task card details.

To proceed, carry out the following:

• Select the “Edit task Additional Information” link to edit the task additional information.

• Select the “Author Repair Procedure” link to modify the non-standard task details.

Refer to the “Maintenance Task” online help for more details.

• Click the “Perform Opportunity Maintenance” link to perform opportunity maintenance details.

Refer to the “Compliance Tracking & Control” online help for more details.

• Select the “Record Parameter Reading / Cond. Eval. Form” link to record the parameter values and conditional evaluation details of the parameters.

• Select the “View Comments Information” link to view comments.

Refer to the “Flight Log” online help for more details.

• Click the “View Task” link to view task details.

Refer to the “Maintenance Task” online help for more details.

• Select the “View Task Dates & References” link to view the task / discrepancy date and reference details.

Refer to the “Compliance Tracking & Control” online help for more details.

• Click the “View AMM Reference” link to view the aircraft maintenance manual (AMM) reference details.

Note: The system launches a PDF file containing the AMM content for the task.

Refer to the “Technical Document Interface” online help for more details.

• Select the “Upload Documents” link to upload the documents.

Refer to the “Object Attachments” online help for more details.

• Select the “View Associated Doc. Attachments” link to view the associated document attachments.

Refer to the “Object Attachments” online help for more details.

• Select the “Record Part Consumption & Return” link to record the part consumption details.

To create a new component replacement

• Select the aircraft maintenance execution reference for which new component replacement is to be added from the tree.

• Select the “Component Replacement” pushbutton in the navigation pane. 

Note: The system ensures that at least one task or discrepancy is created against the Execution Ref. # on clicking this pushbutton, if no such task or discrepancy already exists in the Execution Reference document.

The Component Replacement section can be invoked from “Discrepancy section” or “Work Information” section, with the Discrepancy # or Task # available in the respective sections.

• Enter the following fields in the “Component Replacement” section:

On saving the component replacement, the system allows the user to select the “Object Type” and allows force part change of the part, based on the type of the part being replaced and the availability of the part in the configuration of the aircraft. Refer the table below:

If “Source” is selected as “Swap” or “Cannibalize”, the system displays the following fields, which you are to enter:

• Enter the following:

Note: The system does not display the above field, if “Source” is selected as "Attach”.

Note: The system displays the "Ex - A/C Level #” and Ex-A/C Position #" only if the "Installed Part #" and "Installed Serial #" fields are defined in the "Aircraft" business component, when the “Source” is set as "Cannibalize". Ensure that the level # / position # of the current aircraft is empty, if the Source is set as “Attach”.

If the Object Type set as “Component” and if the Source is set as “Swap”, ensure that the position code and level code entered are valid for that Ex-Aircraft's Configuration as defined in the “Configuration” business component.

Note: The system does not display the fields above, if “Source” is selected as “Attach”, "Replace” or “Remove”.

The system displays the following field:

• Enter the following:

The system displays the following field:

Note: Ensure that either Work Center # or Repair Agency # is available for replace and remove transactions.

The system defaults Work Center # and Repair Agency # only if removal details are entered, based on the following logic:

1. For the 'Removed Part #' / 'Removed Serial #' / ‘A/C Position #’ entered, if any task(s) exists in “Open” status in the AME reference document with matching: (1) Part #/Serial # combination (or) Part # / Position Code combination  and (2) Job Type as “Off-wing”, the system defaults Work Center # / Repair Agency # available for the first task in the sequence (in case multiple Tasks exist).

2. Else, the system defaults the Work Center # (Maint. / Resp. Work Center #) / Preferred Repair Agency identified in the “Maintain Maintenance Info. for Part” page of the “Aircraft” business component. In this case, the system defaults the Work Center from the "Maintain Maintenance info for Part" page only if the Work Center belongs to the same Station where the A/ C Maint. Execution is performed. If the Work Center # specified in the "Maintain Maintenance Info for Part" page is of ‘Work Center Class’ – “Reference”, the system defaults an Execution Work Center mapped to this Reference Work Center (in the "Edit Exe. Org. Unit Level Work Center Details" activity of the "Work Center" business component).

• Enter the following fields:

You can view the following fields, only if Source is “Remove”, “Replace” or “Cannibalize” and if the Object Type is “Component” or “Other Parts”.

The system displays the following field:

The system displays the following field:

• Click the “Save” icon '' to update the component replacement transaction.

Note: 1) Component Replacement records cannot be created or modified against the task, if the ‘Transient Status’ of the task is set as “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

2) You cannot attach or replace a serialized part that is associated with another SWO, package or CR, if:

• The process parameter "Allow attachment of serialized Parts issued/removed against a different Package?" under the entity type Shop Work Order Type in Common Master is 0 (No).

3) The system does not allow removal/attachment, if the part/component is a restricted part with a restriction code that has the process parameter “Allow Component Attachment” under the entity type Stock Restriction Code in the Define Process Entities activity set as 0/No during the restriction effective period.

In Main Base (ie, if Usage Mode is set as “Online” in Configurator business component), component replacement details cannot be saved for offline aircraft (Aircraft with 'Mode of usage' set as "Offline" in the “Aircraft” business component).

On saving / confirming component replacement, ensure the following, if Installed Part # / Installed Serial # is entered and ‘Auto Issue’ check box is checked:

• For the task / discrepancy Work Center - Installed Part #'s part type combination, 'Back Flushable' option must be set as “Yes” in the “Associate Warehouse” page of the “Work Center” business component.

• Installed Part must have 'Back Flushing Required' option enabled in the “Part Administration” business component.

• Issue Basis corresponding to the Installed Part # must be set as "Non-Returnable" / "Core Returnable" in the “Part Administration” business component.

• ‘Serv. Request Warehouse’ identified for the combination of task / discrepancy work center and Part Type of Installed Part:

1. Must have 'Allow Backflushing' option enabled in the “Storage Administration” business component.

2. Is mapped to the login user and also mapped for Material Request transaction in the “Storage Administration” business component.

• For aircraft of Ownership – “Internal”, Stock Status corresponding to the part / serial combination is:

1. same  as the aircraft preferred stock status identified in the “Aircraft” business component (or)

2. a direct alternate of the aircraft preferred stock status identified in the “Aircraft” business component (or)

3. ‘PBH’ with valid Aircraft agreement or Component Agreement (or)

4. ‘Consignment’

• For aircraft of Ownership – “Customer”, Stock Status corresponding to the part / serial combination is valid as per customer contract corresponding to Exe. Ref. #.

• Installed Part / Serial combination must be available in the ‘Serv. Request Warehouse’ corresponding to the combination of task / discrepancy work center and Part Type of Installed Part, as defined in the “Work Center” business component.

• For external aircraft, the installed Part # must have 'PMA ?' option set as "No" in the “Aircraft” business component, if 'Usage of PMA Parts' is set as "Not Allowed" in the customer contract corresponding to Exe. Ref. # document.

• For external aircraft, if the installed part # has part type as "Component", ensure that 'Deviated?' flag is set as "No" for the component record (in the “Aircraft” business component), if 'Usage of Deviated Parts' is set as "Not Allowed" in the customer contract corresponding to Exe. Ref. document.

Note: The 'Usage of PMA Parts' and the 'Usage of Deviated Parts' options are defined in the “Sale Contract” business component.

The system allows update of the component replacement transactions based on the following conditions:

1. If the “Config. Control Basis” drop-down is set as “Config. Rules” in the “Build Aircraft Configuration” activity of the “Configuration” business component, then system will ensures the following:

   1. The part number is a valid alternate part number defined in the “Maintain Alternate Part Information” activity of the Part Administration business component.

   2. The part number is a valid interchangeable part number defined in the “Build Aircraft Configuration” activity of the “Configuration” business component.

   3. The part number is a valid intermixable part number as defined in the “Build Aircraft Configuration” activity of the “Configuration” business component.

   4. The Installed Serial # is a permitted serial # as defined in the “Build Aircraft Configuration” activity of the “Configuration” business component.

   5. The part number and its lower assemblies are effective to the higher assemblies, aircraft and aircraft model as defined in the “Maintain Part Effectivity” activity of the “Aircraft” business component.

2. If the “Config. Control Basis” drop-down is set as “Part Effectivity” in the “Build Aircraft Configuration” activity of the “Configuration” business component, then system will check only whether the part number and its lower assemblies are effective to the higher assemblies, aircraft and aircraft model as defined in the “Maintain Part Effectivity” activity of the “Aircraft” business component.

Note:  The above conditions are valid only if the following statements are true:

• 'Source’ is specified as other than “Remove”.

• 'Object Type’ is specified as “Component”.

• 'Record Mode' is specified as “Normal”.

• Part number specified in the Installed Part # field is other than the Position Part # of the position code, then for the specified component replacement details.

When you save and confirm the component replacement, the system performs the following:

If the Object Type is “Component”, Serial # Type is “New” and Attachment Status of the Position Code is “Unknown”” or “Error”, the system generates a new serial # as per the serial # generation logic identified for the removed part in the “Part Administration” business component.

The system ensures that the Execution Ref # is in status other than “Fresh”, “Cancelled” or “Closed” and that the execution status of the task is other than “Closed”, “Cancelled” or “Pre-closed”.

If the Object Type is selected as “Component” and if the Removed Part # specified is of type other than “Component”, then on saving the component replacement, the system updates the Object Type as “Others”.

If a CR # is generated, Object Type is “Others” and if the current working Task # is in “Planned” status, then the system updates the execution status of the task # and the status of the Execution Ref # document to “In-Progress”.

For a CR # with 'Object Type' set as "Others", if the source is selected as “Attach”, the 'Installed Part #' and 'Installed Serial #' are issued against the current 'Execution Ref #, and if the 'Reconcile Qty - Core' column' in the “Record Part Consumption & Return” page is '0' for the 'Issued Part #' and 'Issued Serial #', then the 'Reconcile Qty - Core' is updated as '1'.

If the CR transaction date & time is earlier than the Actual start date & time of the task / package, then the system updates the Actual start date & time of the task / package with the CR transaction date & time. Similarly if the CR transaction date & time is later than the Actual start date & time of the task / package, then the system updates the Actual start date & time of the task / package with the CR transaction date & time.

Example:

Actual start date & time of task / package : 25-01-2008 09:00:00

Actual end date & time of task / package : 25-01-2008 10:00:00

If the CR transaction date & time is 25-01-2008 08:00:00, Actual start date & time of task / package is updated as 25-01-2008 08:00:00

If the CR transaction date & time is 25-01-2008 11:00:00, Actual start date & time of task / package is updated as 25-01-2008 11:00:00

In case of Customer Owned Aircraft, when a part removed from an aircraft is dispositioned with SWO/RO generation, the system ensures that the Contract # and Effectivity # of the removed part matches with the Contract # and Effectivity # of the aircraft from which the part is removed. i.e, if a Part Removal results in setup of a Child Shop Work Order / Repair Order, system ensures that the Removed Part is effective for the Contract associated to the A/C Maint. Exe. Ref. Document.

The system does not allow part removal / attachment against a Task / Discrepancy, if:

• Task / Discrepancy / A/C Maint. Exe. Ref. Document / Customer Order is on hold.

• Process parameter ‘Stop A/C Maint. Execution?’ is set as “Yes” for the associated Hold Code in the “Common Master” business component.

If the ‘Removed Part #” or ‘Installed Part #’ specified is a Component part and if Object Type selected is other than “Component”, the system allows Component Replacement transaction only if the process parameter “Allow Component Replacement transaction for Component Part with Object Type selection other than Component?” is set as “Allowed” in the “Define Process Entities” activity of the “Common Master” business component.

The system does not allow Component Replacement transaction, if the following are true:

• If the attribute ‘Allow Component Replacement transaction for Object Type other than Component with availability of Part - Serial in Stock?’ is set as “Not Allowed”.

• Part # / Serial # avaliable in Installed Part # / Installed Serial # (or Removed Part # / Removed Serial #) is also avaliable in Stock with quantity as 1.

If the process parameter "Work Order Description for auto generated Shop Work Order?" under the Entity Type "Disposition Code" is:

• 0, the SWO created on confirmation of CR takes the work order description from the ‘Reason’ field.

• 1, the SWO created on confirmation of CR takes the work order description from the “Removal Remarks” field.

• Select the “New” icon '' in the “Component Replacement” group box, to create another new component replacement. 

• Click the “Confirm” icon '', to confirm  the component replacement

Note: 1) Component Replacement records cannot be created or modified against the task, if the ‘Transient Status’ of the task is set as “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

2) You cannot attach or replace a serialized part that is associated with another SWO, package or CR, if the process parameter "Allow attachment of serialized Parts issued/removed against a different Package?" under the entity type Shop Work Order Type in Common Master is 0 (No).

3) The system does not allow removal/attachment, if the part/component is a restricted part with a restriction code that has the process parameter “Allow Component Attachment” under the entity type Stock Restriction Code in the Define Process Entities activity set as 0/No during the restriction effective period.

Process Parameter dependency: If the process parameter “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 1 for Yes under the entity type “Tech. Records Process Ctr” and the entity “Part Prog in the “Define Process Entities” activity of Common Master, the system automatically activates Schedule Status of the tasks mapped to the maintenance operator associated with the removed / attached component in the maintenance program. Further, Schedule Status of the tasks not related to the maintenance operator will be set as Inactive in the component maintenance program. However, if “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 0 for No, Schedule Status of the tasks will not be dependent on the maintenance operrator.

The system generates a Component Replacement Record either in “Removed” or “Replaced’ status as follows:

a) If Source is specified as “Cannibalize”:

i) Only Source Aircraft or if both Source Aircraft and Source Component numbers are specified or only Source Component attached to an  Aircraft Reg # is specified:

1. • The system creates a Component Replacement Record in “Removed” status for the Installed Part # - Serial # for the Source Aircraft # and / or its Next Higher Assembly component ( If Source Component # is entered) specified.

   • The system creates a Component Replacement Record in “Replaced” status for the Removed / Installed Part # - Serial # for the current Aircraft Reg # specified in the header.

ii) Only Source Component # not attached to an  Aircraft Reg # is specified:

1. • The system creates a Component Replacement Record in “Removed” status for the Installed Part # - Serial # for Next Higher Assembly of the Installed Part - Serial #.

   • The system creates a Component Replacement Record in “Replaced” status for the Removed / Installed Part # - Serial # for the current Aircraft Reg # specified in the header.

b) If Source is specified as “Swap”:

i) Only Source Aircraft # or if both Source Aircraft and Source Component numbers specified or only Source Component # attached to an  Aircraft Reg # is specified:

1. • The system creates a Component Replacement Record in “”Replaced” status for the Removed / Installed Part # - Serial # for the Source Aircraft # and / or its Next Higher Assembly component ( If Source Component # is entered) specified.

   • The system creates a Component Replacement Record in “Replaced” status for the Removed / Installed Part # - Serial # for the current Aircraft Reg # specified in the header.

ii) Only Source Component # not attached to an  Aircraft Reg # is specified:

1. • The system creates a Component Replacement Record in “Replaced” status for the Installed Part # - Serial # for the immediate Next Higher Assembly of the Installed Part - Serial #.

   • The system creates a Component Replacement Record in “Replaced” status for the Removed / Installed Part # - Serial # for the current Aircraft Reg # specified in the header.

A unique number is generated and displayed alongside the “Component Replacement #”.

Note: Component replacement # is generated only if the “Object Type” is “Component”.

You cannot modify a CR which is in “Confirmed” status.

The count of component replacements recorded for the selected aircraft maintenance execution reference # is increased, and displayed alongside the “Component Replacements” pushbutton.

In Main Base (ie, if Usage Mode is set as “Online” in Configurator business component, component replacement details cannot be confirmed for offline aircraft (Aircraft with 'Mode of usage' set as "Offline" in the “Aircraft” business component).

For the parts removed in ‘Serviceable’ condition, the system updates the “SOS Disposition” field as blank in the “Component Replacement” business component.

For the parts removed in 'Unserviceable' condition, the system updates the “SOS Disposition” as “Not Applicable” in the “Component Replacement” business component, if the "SOS Program Applicability" is set as “Not Applicable” in the “Set Options” activity of the “Common Masters” business component.

For the parts removed in the 'Unserviceable' condition and "SOS Program Applicability" set as “Applicable” in the “Common Masters” business component, the system updates “SOS Disposition” in the “Component Replacement” business component, based on the combination of values in the “Confirmed Failure” drop-down list and “SOS Applicability” set at part level in the “Maintain Maintenance Info for Part” activity of the “Aircraft” business component, as represented in the below table:

Note: All the above updates happen only if the “Object Type” is “Component” or “Others.

Note: If the SOS Disposition is updated as “Suspected Failure”, the system updates the ‘Quarantine’ flag as “Yes” in the Stock Maintenance table and updates the Reference Document as CR and Reference Document # as CR # in the “Component Replacement” business component. If the SOS Disposition is updated as “Confirmed Failure”, the system updates the ‘Quarantine’ flag as “No”.

If the CR details are updated for a task #, the system updates the Execution status of that task # from “Planned” to “In-Progress” and updates the Aircraft Maintenance Execution document status to “In-Progress”. If the current CR section is having the discrepancy context, then the system updates the Execution status of the latest task # of the associated discrepancy # and the Aircraft Maintenance Execution document status to “In-Progress”.

If the removed part # is a valid part # and the Component Condition is set as "Phased Out", then on confirming the CR, the system generates a purchase request, if the following conditions are satisfied:

1. If the Ownership of the aircraft is “Owned”.

2. If the Ownership of the component is “Owned”.

3. If “Action on Phase Out” drop-down list box is set as “'Generate PR“ in the “Maintain Planning Information" activity of the “Part Administration” business component.

4. If the Phase Out Policy has been defined for the selected Work Center # in the “Maintain Maintenance Info. for Part “ page of the “Part Administration” business component.

Note: The system generates purchase request for the 'Scrapped Part' / 'Prime Part', based on the parameter ‘PR generation option for scrapped part’ set as “Prime Part’ or ‘Scrapped Part’ for the Category ‘Scrap Note’ in the “Set Inventory Process parameter” page of the “'Logistics Common Master” business component.

If the Source is set as “Remove” then on confirming the CR, the system generates a CR is “Removed” status and updates the Attachment Status in the “Configuration” business component as “Removed”. If the Source is other than “Remove” the system generates a CR in “Replaced” status and updates the Attachment Status in the “Configuration” business component as “Attached”.

For the removed Position - Level code whose Attachment Status is “Unknown”, on confirmation of CR, the system updates the Attachment Status as 'Removed' in the “Configuration” business component, for the Aircraft Reg # avaliable in the Header.

For a CR # with 'Object Type' set as "Component", if the source is selected as “Attach”, the 'Installed Part #' and 'Installed Serial #' are issued against the current 'Execution Ref #, and if the 'Reconcile Qty - Core' column' in the “Record Part Consumption & Return” page is '0' for the 'Issued Part #' and 'Issued Serial #', then the 'Reconcile Qty - Core' is updated as '1'.

If Record Mode is selected as “Force Part Change” and if there is no error in the Component Replacement transaction, the system updates “No Errors” as Error Description in the Error Log and updates the status of the Error Log as “Closed”.

The system creates a shop work order, if following conditions are true:

1. For the disposition selected in the 'Rem. Disposition / Codn.' drop-down list box, if the process parameter ‘Create Order on disposition ?’ is set as "Execution Order" in the “Common Master” business component.

2. If a Work Center # is defaulted by the system in the ‘Work Center #’ control available in the ‘Component Replacement’ section (or) if system is able to peg a Work Center for the Removed Part.

Note: For the shop work order generated, if tasks having ‘Job-Type’ set as “Off-Wing”, are available in “Planned” status for the Removed Part # - Removed Serial # combination (or) Removed Part # - Position Code combination in the AME document, those tasks must be moved from the current AME # to the newly created Shop Work Order #.

The system creates a repair order, if following conditions are true:

1. For the disposition selected in the 'Rem. Disposition / Codn.' drop-down list box, if the process parameter ‘Create Order on disposition ?’ is set as "Execution Order".

2. System is not able to derive a ‘Work Center #’, but is able to derive a ‘Repair Agency #’ for the Removed Part.

 Note: The system derives the ‘Work Center #’ and ‘Repair Agency #’ based on the following logic :

1. For the 'Removed Part #' / 'Removed Serial #' / ‘A/C Position #’ entered, if any task(s) exists in “Open” status in the AME reference document with matching : (1) Part #/Serial # combination (or) Part #/Position Code combination  and (2) Job Type as “Off-wing”, the system defaults Work Center # / Repair Agency # available for the first task in sequence (in case multiple Tasks exist) .

2. Else, the system defaults the Work Center # (Maint. / Resp. Work Center #) / Preferred Repair Agency identified in the “Maintain Maintenance Info. for Part” page of the “Aircraft” business component. In this case, the system defaults the Work Center from the "Maintain Maintenance info for Part" page only if the Work Center belongs to the same Station where the A/ C Maint. Execution is performed. If the Work Center # specified in the "Maintain Maintenance Info for Part" page is of ‘Work Center Class’ – “Reference”, the system defaults an Execution Work Center mapped to this Reference Work Center in the "Edit Exe. Org. Unit Level Work Center Details" activity of the "Work Center" business component.

For component replacements having Object Type as "Component" or “Other Parts”, on auto issue of Installed Part (ie, if the Auto Issue box is checked), the system generates a material request (with ‘MR Class’ as “Maintenance” and ‘MR Type’ as “Unplanned” for the Installed Part) and a corresponding Material Issue document in “Closed” & “Confirmed” statuses respectively.

The system generates a material return document in ‘Draft’ / ‘Fresh’ / ‘Confirmed’ status for the removed part, if the following conditions are satisfied:

1. Source is set as "Remove", “Replace” or "Cannibalize".

2. ‘Auto Return of Parts on Removal’ under the entity type Package Type is set as “Required” for the package type and 'Auto Return of Parts on Removal' under the entity type Disposition Code is set as ‘Required’ for the disposition code in the “Common Master” business component.

3. ‘Create Order on Disposition’ is set as “Not Required” (or) 'Create Order on Disposition' for the Rem. Disposition / Codn. is set as "Execution Order" and Removed Part # is not to be routed for internal repair.

Note: The system generates a material return document for the removed core in “Confirmed” status if “Auto Confirmed-Mnt Return” transaction is mapped for the return warehouse.

Separated tasks movement:

On removal of a part from an aircraft that has reference to AME document, the system transfers the tasks having ‘Jon-Type’ set as “Off-Wing”, from the host AME document to the Child Work Order that is getting created during removal, if following conditions are satisfied:

1. 1. 'Part #' and 'Serial #' corresponding to the Task, match with the 'Removed Part #' and 'Removed Serial #'.

   2. 'Part #' and 'Position Code' corresponding to the Task, match with the 'Removed Part #' and removed 'A/C Position #'.

Note: In the above conditions, the Part # specified corresponding to Task could also be a Direct Alternate Part of the Removed Part, as defined in the ”Part Administration” business component.

When moving Tasks to the Child Shop Work Order, system also moves all the associated Child Tasks available in the AME, if (i) 'Part #', 'Serial #' and 'Position Code' details available in the 'Component Details' section of the Child Task match with the component details of the Parent Task and (ii) Status of the Child Task is "Planned".

On movement of the tasks, the system copies their 'Part Requirements', 'Resource Requirements', 'Sign-Off Requirements' and 'Parameter Requirements' from the AME document to the Child Work Order.

The system updates the status of the tasks that were moved from the AME document to SWO created during removal of child parts, as "Routed for Repair".

Whenever a lot controlled part is removed in the “Component Replacement” section, system generates a new Mfr. Lot # which will in turn be used to generate a New Lot # for the Removed Part.

For the selected "Rem. Disposition", if the process parameter ‘Removed Core Condition?’ is set as "Phased Out" and if the parameter ‘Salvage Action  - Internal Stock’ (in case of Customer Owned Aircraft) or ‘Salvage Action  - External Stock’ is set as "Return to Warehouse" in the "Define Process Entities" activity of “Common Master” business component, the system creates auto return for the removed core in “Fresh” status.

The system generates a Material Request, if for the selected "Rem. Disposition" the process parameter ‘Replenishment of Core ?’ is set as "Auto". This is not applicable for offline operations.

Scrap Note generation:

The system generates scrap note for the removed part, if

1. The process parameter ‘Recommendation for Phase Out’ is set as “Yes” in the “Set Process Parameters” page of the “Common Master” business component.

2. ‘Scrap Note Process’ is set as “Auto-Initiation” for the Removed Part, in the "Maintain Planning Information" activity of the "Part Administration" business component.

The scrap note generation process varies depending on the ownership of the part, as explained in the table below:

Note: If the process parameter ‘Recommendation for Phase Out’ is set as “Yes” for the ‘Entity Type’ selected as “Disposition Code”, you are allowed to select the parameter ‘Removed Core Condition?’ as “Unserviceable” only.

Part Ownership – Internal

Part Ownership - Customer

The parameters mentioned in the table are defined in different business component, as explained below:

• Parameters ‘Salvage Action – Internal Stock’, ‘Salvage Action – External Stock’ & ‘Removed Core Condition’ - - > “Common Master” business component - - > “Define Process Entities” activity - - > “Set Process Parameters” page --> Entity - "Disposition Code"..

• ‘Scrap Note Process’ - - > “Part Administration” business component - - > “Maintain Planning Information” page.

• ‘Salvage Action’ - - > “Sale Contract” business component - - > “Manage Customer Contract” activity - - > “Edit Terms of Execution” page - - > “Part Handling Details” tab.

Refer to the section “On saving and confirming the component replacement, the system ensures the following”, for further details.

The system retains user-specified NSD/NSV of attached components during inheritance of the position based schedules on the basis of the process parameter ‘Retain manually corrected Next Due Date & Value for the component task when the position based schedule is inherited if LPD & LPV is not available' defined under  the entity type “Next Due Computation Logic” and entity "Maint. Program and Forecasting Options" in the Define Process Entities activity of Common Master. The impact of the process parameter during inheritance is explained here:

To edit a component replacement

• Select the aircraft maintenance execution reference for which component replacement details are to be edited in the tree structure.

The count of component replacements recorded in the selected aircraft maintenance execution reference # is displayed alongside the “Component Replacements” pushbutton.

• Select the “Component Replacement” pushbutton in the navigation pane. 

The navigation pane will display 3 tree interfaces as shown below:  

1. Aircraft Configuration

2. Component Replacement

3. Issued Part List

Aircraft Configuration Tree:

• Select the ‘Show aircraft configuration’ icon '' to view the aircraft configuration details.

For the aircraft registration number specified, the system displays the latest active configuration, in the tree. The sub components are also displayed as folders.

The Piece Part List defined for the referenced Aircraft as well as for all the applicable child parts are displayed under the "Piece Parts" folder in the Configuration tree. If Piece Parts are defined for both the Aircraft and child parts, then the respective 'Piece Parts' folder should be displayed under 'Aircraft' as well as 'Child Parts' till the applicable leaf level.

For example, assume that an A/C Reg # 'A/C1' has 2 child parts 'P1/S1/C1' and 'P2/S2/C1' in position codes ‘P-1’ and ‘P-2’. Piece Parts are defined for A/C1, P1/S1 and P2/S2. The representation in the aircraft configuration tree is as follows:

- A/C1

 P-1 :: P1 :: Part Desc. for P1 :: S1 :: C1

         + Piece Parts

 P-2 :: P2 :: Part Desc. for P2 :: S2 :: C2

             + Piece Parts

 + Piece Parts

Component Replacement Tree:

• Select the ‘Show component replacements’ icon '' to view the component replacement details.

The selected “Aircraft Maintenance Execution Reference #” will be the parent node in the tree. The task # is displayed as the first-level node. Cancelled tasks will not be listed in the ‘Component Replacement’ tree.

The subsequent component replacements reported for the aircraft maintenance execution reference such as “Pending Action Items”, “Only Removals”, “Only Installs”, “Replaced Items, “Swapped Items” and “Cannibalized Items” will be the second level nodes. A tool tip displays the information available for the component replacement as Part #/ Part Description/ Serial #/ Position Code/ CR #.

1. Pending Action Items: The records with Object Type “Component” and which do not have CR # generated are displayed under this node.

2. Only Removals: The CR records with status “Removed” or 'Error Removed', Object Type set as “Others” or “Miscellaneous” and Source set as “Removed”, are displayed under this node.

3. Only Installs: The CR records with status “Replaced” or “Error Replaced”, Source set as “Attach” and Object Type set as “Others” or “Miscellaneous”, are displayed under this node.

4. Replaced Items: The CR records with status “Replaced” or “Error Replaced”, Source set as “Replace” and Object Type set as “Others” or “Miscellaneous”, are displayed under this node.

5. Swapped Items: The CR records with status “Replaced”, Source set as “Swap” and Object Type set as “Others” or “Miscellaneous”, are displayed under this node.

6. Cannibalized Items: The CR records with status “Replaced”, Source set as as “Cannibalize” and Object Type set as “Others” or “Miscellaneous”, are displayed under this node.

The Shop Work Order # / Repair Order # is displayed at the end of each Component Replacement record, under the ‘Only Removals’ and ‘Replaced Items’ folders. Each Task # / Discrepancy # folder of the CR tree will have the corresponding ‘Tracking #’ information concatenated to it.

On clicking the node 'Click for New CR' in the tree interface, based on the Parent Task under which the current node is displayed, the right pane is refreshed with the ‘Discrepancy’ or ‘Workunit Information’ section and the work unit or discrepancy details are transferred accordingly.

Note: The AME / tasks / discrepancies for which 'Hold' is applicable, are highlighted with the Exclamatory Icon ‘’, in the tree structure.

If any information about the component replacement is not available, the system indicates it by displaying <NA>in the format.

• Select the component replacement to be modified in the tree interface.

The details of the selected component replacement are displayed, in the “Component Replacements” group box to the right.

• Edit the required details of this component replacement.

Issued Part List Tree

• Select the ‘Show issued part list’ icon '' to view the details of the parts issued for the aircraft maintenance execution reference.

The selected Aircraft maintenance Execution Reference # will be the parent node in the tree. All the parts (Components / Non Components and Serial / Lot / Non Controlled) issued for the particular aircraft maintenance execution reference are displayed under this node.

All the serial controlled parts listed under Issued Parts List are displayed in the following format: Part #/ Part Description/ Serial #.

All the lot controlled parts listed under Issued Parts List are displayed in the following format: Part # / Part Description.

• Click the “Save” icon in the “Component Replacement” group box, to save the modified details of the component replacement.

Note: The system does not approve component attachment, if the part/component is a restricted part with a restriction code that has the process parameter “Allow Component Attachment” under the entity type Stock Restriction Code in the Define Process Entities activity is 0/No.

• Select the ‘’ icon, to view the details of the previous component replacement. Use the tree view as the reference.

• Select the ‘’ icon, to view the details of the next component replacement. Use the tree view as the reference.

To cancel a component replacement

• Select the component replacement to be cancelled from the tree structure.

The details of the selected component replacement are displayed, in the “Component Replacement” group box to the right.

• Click the “Cancel” icon '' in the “Component Replacement” group box, to cancel the selected component replacement.

Note: You can cancel a component replacement for which CR # is not generated.

Ensure that the component replacement record cannot be deleted on following conditions:

• If the Job Type of the associated task is “Component Removal”.

• If the record status of the associated discrepancy is “Transfer”.

• If the maintenance return document is available against the part # - serial # combination in “Draft”, “Fresh” or “Confirmed” status.

• If a new serial # is generated for that record.

Note: Ensure that a task or discrepancy is specified for the Execution Reference selected for modifying component replacement details.

However, you can cancel 'Confirmed' component replacements under the following conditions:

• Involved Part is Lot-Controlled

• Object Type is “Other Parts”

• No CWO / Repair Order generated yet

• No Stock Return generated in Confirmed status

The status of such component replacements will change to ‘Cancelled’ and, such cancelled records will appear in a new tree folder called ‘Cancelled’ in the above-said screen

Any pending returns for the removed Lot-Controlled parts (retrieved n the Return Cores tab of the Record Part Consumption & Return page) will be deleted / knocked off on cancellation

In Main Base (ie, if Usage Mode is set as “Online” in Configurator business component, component replacement details cannot be cancelled for offline aircraft (Aircraft with 'Mode of usage' set as "Offline" in the “Aircraft” business component).

To proceed, carry out the following:

• Select the “Print Tag for Removed Object” link to print the tag for removed object.

Note: 1) Part Tag report is launched without a CR #, if the process parameter ‘Allow generation of part tag before confirmation of component replacement?' under the Entity '--All Packages--' of the Entity Type 'Package Type' is set as “Allowed” in the “Common Master” business component. This rule is applicable only for Object Type 'Component' and 'Other Parts' and for Force Part Change and New Serial Removal. Part Tag report cannot be generated for Lot controlled parts before confirmation of Component Replacement.. 2) The process parameter ‘Print Work Requested in Removal Reason section?’ determines the display of “Work Requested” details recorded against the CR # in the Removal Reason section of the Part Tag report. If the process parameter “Print Work Requested in Removal Reason section?” defined under entity type ‘Reports’ and entity ‘Part Tag Report’ in the Define Process Parameters activity of Common Master is ‘1’, the Removal Reason section displays the Work Requested details. Conversely, if the ‘Print Work Requested in Removal Reason section?’ is ‘0’, the Removal Reason section remains blank. 

• Select the “Record Part Consumption & Return” link to record the part consumption details.

• Select the “Route Unserviceable to Repair” link to route the unserviceable components to repair.

• Select the “Update Removed Component Assembly” link at the bottom of the group box to update the component maintenance details for removed components.

Refer to the “Component Replacement” online help for more details.

• Select the “Update Installed Component Assembly” link at the bottom of the group box to update the component maintenance details for installed components.

• Select the “Inquire Stock Balance” link to retrieve information pertaining to the stock balance.

Refer to the “Stock Maintenance” online help for more details.

• Select the “Create New Part Request” link at the bottom of the page to create a new part request.

Refer to the “Part Administration” online help for more details.

• Select the "Inquire New Part Request Status” link at the bottom of the page to retrieve the part request status details.

Refer to the “Part Administration” online help for more details.

• Select the “Help on Non-Comp Removed Serial #” link at the bottom of the group box to view the list of the Non-Component removed serial numbers.

Refer to the “Stock Maintenance” online help for more details.

• Select the “Help on Non-Comp Installed Serial #” link at the bottom of the group box to view the list of the Non-Component installed serial numbers.

Refer to the “Stock Maintenance” online help for more details.

• Select the “View Maintenance Info. for Installed Part” link to view the maintenance information such as part description, base part, component type, part effectivity, ATA chapter to which the part belongs and the status of the installed part.

Refer to the “Aircraft” online help for more details.

• Select the “Generate Serviceable Certificate” link to open the Issue Certificates activity for generating CoM document for the removed part # - serial #.

• Select the “Plan Work Order” link to proceed with the creation and release of the SWO for the removed part # - serial #.

To create a new material request

• Select the aircraft maintenance execution reference for which a new material request is to be added from the tree.

• Select the “Material Request” pushbutton in the navigation pane.

Note: The system ensures that at least one task or discrepancy is created against the Execution Ref. # on clicking this pushbutton if no such task or discrepancy already exists in the Execution Reference document. 

• Enter the following:

• Click the “Check Availability” icon '' to launch the “Check Part Availability” screen which indicates the availability of parts across warehouses.

• Enter the following details of the material request.

• If “Substitute Type” is selected as “NHA” or “Specific Alternate”, the system displays the following field, which you are to enter:

Note: The system does not display the ‘Substitute Part #” field If “Substitute Type” is selected as “Not Allowed”.

• Enter the following:

• Click the “Save” icon '' to save the material request.

Note: Ensure that the Execution Reference is in status other than “Fresh” or “Closed” and the task in status other than “Closed”, “Cancelled” or “Pre-closed”.

The system performs the following on saving the material request.

• Updates the remaining quantity as 'Pending Return Qty- Excess', if the Used Qty is reduced for a non-returnable and none controlled part.

• Mandates the Used Quantity update against each serial # in the “Record Part Consumption & Return” page of the current business component, if the Used Qty is reduced / increased for a non-returnable / Core-returnable serial controlled part and if the issued quantity is more than one.

• Updates the remaining quantity as 'Pending Return Qty- Excess', if the Used Qty is reduced for a non-returnable / Core-returnable serial controlled part and if the issued quantity is one.

•  If the part is ‘Not Effective’ to Aircraft, then the node corresponding to the part requirement in the tree is colored as red.

• Mandates the Used Quantity against update each Lot # in the “Record Part Consumption & Return” page,

1. if the Used Qty is reduced / increased for a non-returnable / Core-returnable Lot controlled part and if the issued quantity has reference to more than one lot #.

2. If Used Qty is reduced for a non-returnable / Core-returnable Lot controlled part and if the issued quantity is against only one Lot #.

Note: If the Return is created for the Part # - Serial # or Part # - Lot # combination in Confirmed status and if CR transaction exists for the combination, then the system ensures that the used quantity is not reduced below the total quantity.

• The system allocates and pegs the MR quantity if the Need Frequency is set as “Always” and if the part requested is effective to the aircraft, based on the following parameters:

1. Matching Part #

2. Matching Stock status

3. Matching Warehouse

4. Checks that the Ref. Doc Type is "Execution Reference".

5. Checks that the Ref.  Doc # is either same or is not available in the Material Request.

6. Checks that the Material Request is for same Aircraft Reg #.

7. Checks that the Line Item of the Material request which is applicable for all the above condition is not already issued and is in Authorised Status

8. If there are multiple material requests available, the MR with the earliest need date is considered for pegging. If Multiple MRs exist with the same need date, the system checks for the Earliest Transaction # for pegging. The system picks the MR with the Quantity closest to the Requested quantity.

• On moving / associating a discrepancy to a different package, if the discrepancy has part requirements identified, then the part requirements are copied to the ‘Material Request’ page for the new package.

• In Main Base (if Usage Mode is set as “Online” in Configurator business component), part requirement details cannot be saved, if the 'Originating Work Center' of the selected package is set as "Offline" in the “Work Center” business component.

• Material Request records cannot be created or modified against the task, if one of the following conditions is true:

1. ‘Transient Status’ of the task is “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

2. ‘Transient Status’ is not "Hold", but if the ‘Hold Status’ of the task is “Open” and the process parameter “Prevent Material Request?” is set as “Yes” for the associated Hold Code. The process parameter is set in the “Set Process Parameters” page of the “Common Masters” business component.

• If the Task / Discrepancy / Aircraft Maint. Exe. Ref. Document / Customer Order, has a 'Hold' applied, the system does not allow the following:

1. Save of Material Request details, if the process parameter ‘Stop A/C Maint. Execution ?' is set as "Yes" for the ‘Hold Code’ corresponding to the Task / Discrepancy / Aircraft Maint. Exe. Ref. Document / Customer Order.

2. Material Requisition, if the 'Prevent Material Request ?' parameter is set as "Yes" for the ‘Hold Code’ corresponding to the Task / Discrepancy / Aircraft Maint. Exe. Ref. Document / Customer Order.

If the Material Request # is generated for the Part #, the system displays the following fields:

Note: If a “Material Request #” is not generated for the Part #, the system does not display the fields above.

• Enter the following fields:

The system displays the following field:

• Click the “New” icon '' in the “Material Request and Consumption” group box, to create another material request.

Note: Ensure that at least one task or discrepancy is created against the Execution Ref. #.

To edit a material request

• Select the aircraft maintenance execution reference for which material request details are to be edited in the tree interface.

The count of material requests recorded for the selected aircraft maintenance execution reference # is displayed alongside the “Material Request” pushbutton.

• Select the “Material Request” pushbutton in the navigation pane. 

The system displays the text “Material Request Consumption'” at the top of the navigation pane.

The lower half of the navigation pane will display the tree interface, in completely exploded form.

The system displays by default the following, if Task # or Discrepancy # is not selected in the Work Information section / Discrepancy section:

a. The first available Task # / Discrepancy # in the Work Information section / Discrepancy section.

b. The material requirements of that particular Task # / Discrepancy # in the Material Request tree section.

The selected “Execution Reference #” will be the parent node in the tree. Under the parent node Task # and the corresponding Tracking # is displayed as the child-level node as ‘Task #::Tracking #’. Cancelled tasks will not be listed in the ‘Material Request’ tree. The tree structure is as follows:

Execution Reference #

Task #

1. 1. “As Required”: All the parts for which the Need Frequency is set as “As Required” and for which no material request is created, are displayed under this node.

   2. “Pending Request”:  All the parts which are not yet requested and for which the Need Frequency is set as “Always” are displayed under this node. On clicking this node, the system retrieves the Part #/ Part Description/ Qty required and UOM values.

   3. “Request Generated”: All the parts for which requests are generated are displayed under this node. The Material Request and Material Issues along with the quantities are also displayed under this node.

   4. “Issued / Consumed”: The Issued Transactions along with the issued and used quantity are displayed under this node.

On clicking any part # in the left pane in the tree interface, the corresponding task and the part details are transferred into the right pane. Also if a node having parts with discrepancy as a reference is clicked, the right pane is refreshed with the ‘Discrepancy section’ instead of the ‘Work Unit Section’.

Note: Each record must have 'Hold Status' and 'Estimation Status' information. If 'Hold' is applicable for a record, it must be represented by an Exclamatory Icon ‘’. If 'Hold' is not applicable for a record, the 'Hold Status Icon' is not displayed. The possible Estimation Status could be "Est. Not Required", "Pending Estimates", "Pending Confirmation", "Confirmed Estimates", "Released Estimates" and "Pending Re-Estimates".

If any information about the material request is not available, the system indicates it by displaying <NA>in the format.

• Select the material request to be modified in the tree interface.

The details of the selected material request are displayed, in the “Material Request & Consumption” group box to the right.

• Edit the required details of this material request.

• Click the “Save” icon in the “Material Request and Consumption” group box, to save the modified details of the material request.

If the requested material is issued, the part is moved from the “Request Pending” node to the “Request Generated” node in the “Material Request” tree interface.

If the Need Frequency for the part is set as “As required”, the part details are moved to the “As Required” node in the tree interface.

If the Need Frequency for the part is set as “Always”, the part details are moved to the “Pending Request” node in the tree interface.

If 10 items have been issued against a material request for a part and all the 10 parts have been consumed, the part reference is removed from the “Issued Part List” tree interface.

If 10 items have been issued against a material request for a part and only 8 parts have been consumed, the part reference reappears in the “Issued Part List” tree interface.

• Select the ‘’ icon, to view the details of the previous material request. Use the tree view as the reference.

• Select the ‘’ icon, to view the details of the next material request. Use the tree view as the reference.

• Click the “Confirm” icon '' to confirm the material request.

Note: The part details are moved “Pending Request” node or “As Required” node to the “Request Generated” node irrespective of the Need Frequency, on direct MR generation.

Material Request records against the task cannot be confirmed, if one of the following conditions is true:

• ‘Transient Status’ of the task is “Hold” in the “Record Work Hold” page of the “Work Monitoring and Control” business component.

• ‘Transient Status’ is not "Hold"’, but the ‘Hold Status’ of the task is “Open” and the process parameter “Prevent Material Request?” is set as “Yes” for the associated Hold Code. The process parameter is set in the “Set Process Parameters” page of the “Common Masters” business component.

When you save / confirm material request:

On saving / confirming the material request, the system does not allow you to generate material request, if the following statements are true:

• Task is on hold and if the process parameter ‘Stop A/C Maint. Execution ?' is set as "Yes" for the ‘Hold Code’ corresponding to the Task.

• Task is on hold and if the process parameter 'Prevent Material Request ?' parameter is set as "Yes" for the ‘Hold Code’ corresponding to the Task.

For offline aircraft, Material Request cannot be generated in Offline Base (‘Usage Mode’ set as “Offline” in “Configurator” business component), if the Requested Quantity is not available in the request Warehouse #.

 The system sets Need Date of the material request on the basis of the AME Ref. # referenced task as illustrated in the table

·        In a situation in which multiple material requests are auto-generated by the system, the requests are consolidated on the basis of Need Date or the serviceable request warehouse of the task work center.

To short close a material request

• Select the material request to be short closed from the tree interface.

The details of the selected material request are displayed, in the “Material Request and Consumption” group box to the right.

• Click the “Short Close” icon '' in the “Material Request and Consumption” group box, to short close the selected material request and update the status based on the issued quantity.

Note: Short closing is done for the difference between MR quantity and issued quantity.

Process Parameter Dependency: If the process parameter “Delete Part Requirements on short closure of Material Request?" is set as '1' for 'Yes' under the entity type Package Type and the entity “All User Defined Package Type including Log Card” in the “Define Process Entities” activity of Common Master, on short close of a part request, the system cancels the part request against the task / discrepancy.

Selective MMD printing

• Click the “Print Selective Material Movement Document” icon ‘’ to print the selected material movement document (MMD) for a material request.

The following documents will be considered for printing the MMD:

1. The material requests with issue documents in “Fresh” status.

2. The Material requests with “MR Priority” set as “AOG” and with no issue document created.

If the MMD for the Material Request # is already printed, the system will alert the user that the document has been already printed and whether reprinting is required.

To proceed, carry out the following

• Select the “Request Preferred Serial #/ Lot # Information” link at the bottom of the group box to request the preferred serial and lot number details for the part.

Refer to “Flight Log” online help for more details.

• Select the “Confirm Issue” link to confirm the stock issue.

Refer to the “Stock Issue” online help for more details.

• Select the “Inquire Stock Balance” link to retrieve information pertaining to the stock balance.

Refer to the “Stock Maintenance” online help for more details.

• Select the “View Parts Information” link to view the part details.

Refer to the topic “View Parts Information – A summary of the activity” in the “Part Administration” business component for more details.

• Select the “Create Maintenance Return” link to create a maintenance return document for returning excess stock or core-returnable, if any.

Refer to the “Stock Return” online help for more details.

• Select the “View Material Request” link to view the material request details.

Refer to the “Material Request” online help for more details.

• Select the “Inquire New Part Request” link to retrieve the part request details.

Refer to the “Part Administration” online help for more details.

• Select the “Record Part Consumption & Return” link to record the part consumption details.

• Select the “View Maintenance Info. for Part” link to view the maintenance information such as part description, base part, component type, part effectivity, ATA chapter to which the part belongs and the status of the part.

Refer to the “Aircraft” online help for more details.

Parameter value update

The system updates the parameter values for every sign off of the task or subtask This is applicable only if the “Parameter Recording” drop-down list box is selected as “Mandatory” in the “Edit Parameter Reading Requirements” page of the “Maintenance Task” business component.

Note: If the “Sign-Off Status” is set as “Not-Required” for any of the task or sub task associated to the unplanned work unit, then the system will validate the above mentioned logic on confirmation of aircraft maintenance execution reference.

If parameter values are recorded against the Aircraft Maintenance Execution Reference and if the status of the task / package is changed to “Completed” or “Closed”, the system updates the parameter values available against all the tasks with Execution Ref. # / Line # / WorkUnit #/ Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

Update of compliance history for work units

If the “Enforce Excess/Core Returns?” field in the “Set Options” activity is set as “No”,  the aircraft maintenance execution reference gets confirmed without checking for the pending return qty.

The system will short close the material requests associated to the aircraft maintenance execution reference, which are in “Authorized” or “Partially Issued” status. While short closing a material request, Issue or Stock Transfer Issue documents, if any, created in “Fresh” status for those material requests, will be canceled. . Stock Transfer documents associated with such canceled Stock Transfer Issue documents will also be short-closed.

If the work units have been retrieved from the “Opportunity Maintenance” page of the “Compliance Tracking & Control” business component and the execution status of these work units are “Completed”, the system updates the job status of these work units as “Completed” in the “Compliance Tracking & Control” business component.

The system ensures that component replacement details are recorded for the completed replacement work units reported in the 'Record Work and Sign-Off Information' page.

If component replacement details are available, the system updates them before confirming the aircraft maintenance execution reference.

Note: You cannot confirm a aircraft maintenance execution reference when the component replacement records, with the “Source” set as “Remove”, “Attach” or “Swap”, are not confirmed in the “Replace Components” page.

The system performs the following if component replacement details are available:

• If the component that is getting attached, or any of the child components, has some calender-based schedules and the updation is based on the date of attachment, the system adds the interval to the current replacement date. This date is updated as the next schedule date, in the “Component Maintenance Program” business component, when the next schedule date is blank.

• If the installed component, or any if its child components, has position-based schedules, the system checks if the current aircraft model, configuration class and attached position or its child component has a defined position- based schedule. If so, the system adds the position-based interval to the last schedule date of the work unit for the respective component in the “Component Maintenance Program” business component.

• Ensures that the removed component is attached to the aircraft.

Discrepancy Status

• The cancelled, no fault and closed discrepancies, all of which were in “Under Resolution” status, will be updated to “Cancelled”, “No Fault Found”, “Closed” status in the “Discrepancy Processing” component. 

• The transferred discrepancy which is in “Under Resolution” status, will be updated to “Transferred” and a new discrepancy is generated for the component.

• The discrepancies in ”Pending Deferral” and “Deferred” status will be dynamically updated with the same status to the “Discrepancy Processing” component. This update takes place even before confirmation in the current business component.

Important Dates

• Enter the following fields:

To proceed, carry out the following:

• Select the “Check Part Availability” link to check the availability of the parts across warehouses.

Refer to “Stock Maintenance” online help for more details.

• Select the “Bulk Material Request” link to plan for the material required for executing the work unit.

Refer to the “Compliance Tracking & Control” online help for more details.

• Select the “Create Engg. Service Request” link to create an engineering service request.

Refer to “Engineering Service Request” online help for more details.

• Select the “Record Part Consumption & Return” link to record the part consumption details.

• Select the “Record Employee Timesheet” link to update employee timesheet information.

• Select the “Report Resource Estimates / Actuals” link to update resource actual information.

Refer to the “Flight Log” online help for more details.

• Select the “Record Parameter Reading / Cond. Eval. Form” link to record the parameter values and conditional evaluation details of the parameters.

• Select the “Report Fuel / Oil Log” link in the “Links” section to enter the fuel and oil consumption details.

Refer to the “Flight Log” online help for more details.

• Select the “Issue Certificate of Maintenance” link to issue the certificate of maintenance (CoM) for the Execution Ref #.

• Select the “Upload Documents” link in the ‘main links’ section to upload the documents.

Refer to the “Object Attachments” online help for more details.

• Select the “Edit Package Additional Information” link to edit the additional information of the package.

• Select the “Edit References” link to edit reference document details for the aircraft maintenance execution reference.

Refer to the “Flight Log” online help for more details.

• Select the “View Aircraft Maintenance Log” link to view the aircraft maintenance log.

Refer to the “Aircraft” online help for more details.

• Select the “View Associated Doc. Attachments” in the ‘main links’ section to view the associated document attachments.

Refer to the “Object Attachments” online help for more details.

• Select the “View Engg. Advice Note” link to view the engineering advice note.

Refer to “Engineering Service Request” online help for more details.