Processing discrepancies

In this page , you can process the discrepancies. Tell me more

Select the “Process Discrepancies” link at the bottom of the “Create Visit Package” or "Edit Visit Package Details" page.

The “Process Discrepancies” page appears.

The system displays the following field:

Date Format

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

The system displays the following field in the “Visit Package Details” group box:

Visit Package #	The visit package number for which the discrepancy s must be associated.
Revision #	The latest revision number of the visit package. The system leaves the field blank if the visit package has not been revised.
Aircraft Reg #	The aircraft registration number for which the visit package is applicable.
Aircraft Model #	The model to which the aircraft belongs.

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

Customer #	The number identifying the customer, who owns the aircraft.
Customer Name	The name of the customer owning the aircraft.
Customer Order #	The number identifying the order placed by the customer.
Aircraft Release Date	The date on which the aircraft was released to the customer.

Note: The “Customer #” and “Customer Name” fields are applicable only when the aircraft is not self-owned and the customer details are recorded in the system.

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

Note: The system retrieves all the discrepancies for the aircraft with "Pending" and Deferred’ record status, which are not associated with any execution document from the “Discrepancy Processing” business component.

Discrepancy #	The number identifying the discrepancy for which the details are to be processed.
Select the hyperlinked discrepancy number to view the discrepancy information.
Discrepancy Description	The textual description of the discrepancy .
Created At Org. Unit #	The organization unit where the discrepancy is created.
Deferred Till Date	The date till which the discrepancy has been deferred.
ATA #	The ATA chapter on which the discrepancy is observed.
Fault #	The fault code identified for the discrepancy.
Cause #	The cause code identified for the discrepancy.
Off Part #	The part on which the discrepancy is observed.

Enter the following field:

Work Center #

Use the drop-down list box to select the work center or place where the discrepancy has to be processed. If the “Work Center Hierarchy Check” field is set to “No” in the “Set Options” activity, the system lists the work centers that are associated to the organization unit. Otherwise, the system lists the primary work centre along with the child work centers associated to the primary work center of the visit package.

The system displays the following fields in the multiline:

Off Part Serial	The serial number of the part.
Tracking Status	The tracking status of the discrepancy .
Record Status	The record status of the discrepancy , which can be “Pending”, “Pending Deferral”, “Deferred”, “Retired”, “Transferred”, “Planned” or “No Fault Found”.

To proceed, carry out the following,

Select the “Revise Deferral Limits” link at the bottom of the page to revise the deferral limits that are defined.
Click the “Assign To Visit Package” pushbutton, to associate the discrepancies to the visit package.

The system adds tasks associated with the discrepancy to the visit package and sets the “Processed (Y/N)” field to “Yes” in the “Discrepancy Processing” business component. Further, the part and resource requirements of the tasks are also incorporated into the visit package.
The “Confirmed” status visit package is set to “Fresh” and the “Approval Status” is set to “Pending Approval”, if the visit package approval status is “Approved” or “Returned”.
For a visit package of the “Released” or “Partly Released” status, the system updates the resource requirement and sets the visit package to “Fresh” status.
If approval required option is set as “Yes” in option settings, the approval status of the “Fresh” visit package is set to “Pending Approval”.

What you can do in this page

Indicate the place where the discrepancy must be processed

You can select the work center to indicate the place where the discrepancy is to be processed.

Use the “Work Center #” field in the multiline, to select the place of execution of the discrepancy.

Processing deferred discrepancies – An overview

You can process the discrepancies that are deferred for the aircraft in this page. Discrepancies are typically the symptoms of the problem, which are observed by the person in charge, like pilot, mechanic or the cabin crew and are recorded in the flight log or in the hangar work order.

The rectification may not be carried out as and when the discrepancies are identified so the mechanic may defer the maintenance work on faulty part due to reasons such as non-availability of spares, under equipped maintenance station, or to save operation time. In such cases the discrepancy is called is termed as “Carried forward”.

In this page, those confirmed deferred and pending discrepancies that are not processed for the aircraft are displayed in the multiline. The details such as discrepancy number, its description, ATA on which the discrepancy is observed, fault, cause and part on which the discrepancy is found are displayed. You can select the discrepancy and associate to the visit package for processing. You can also specify the work center where the discrepancy has to be processed.

The system inherits all the work units defined for the discrepancy and updates the “Processed (Y/N)” field in the “Discrepancy Processing” component to “Yes”.