Maintaining discrepancy information

This page enables you to edit the deferment details already specified for a work unit. Tell me more

Select the “Maintain Discrepancy Information” link under the “Compliance Tracking & Control” business component.

The “Maintain Discrepancy Information” page appears.

The system displays the following field:

Date & Time Format

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

To update details of existing discrepancies, specify values in the “Search Criteria” group box. The system retrieves the discrepancies that satisfy the search criteria in the “Discrepancy Details” multiline. You can proceed with the changes to the attributes of the discrepancy in the multiline. However, to create a new discrepancy, start by specifying values in the “Discrepancy Details” multiline

Select one of the following radio buttons:

Create / Update Discrepancy	Select this radio button to create / update discrepancy.
Upload Discrepancy	Select this radio button to upload discrepancy details.

Creating / Updating discrepancy

Select the “Create / Update Discrepancy” radio button.
Select the “Primary Search Criteria” tab to find the discrepancies that you want to update/modify.
Select the “Additional Search Criteria” tab to find the discrepancies that you want to update/modify.
Select the “Search” pushbutton.
Enter/modify the following in the “Discrepancy Details” multiline.

Note: You cannot modify the details of a discrepancy, which is in “Pending Deferral” status.

Aircraft Reg #	The registration number of the aircraft (Alphanumeric, 30). The aircraft reg. # is mandatory, if you wan to record a discrepancy against an aircraft. Help Facility available
Component #	The component for which the discrepancy is reported (Alphanumeric, 90). The system automatically displays the component when you specify a valid part # and serial #. Help Facility available
Part #	The part # of the component for which the discrepancy is reported (Alphanumeric, 40). Help Facility available
Serial #	The part serial number of the component for which the discrepancy is reported (Alphanumeric, 40). Help Facility available
Note: You must specify either component # or part # and serial #, if you want to record a discrepancy against a component.
Discrepancy Type	Use the drop-own list box to select the type of discrepancy. The system displays the following; PIREP– discrepancies reported by the pilot. MIREP – discrepancies reported by the mechanic. Cabin - discrepancies reported by the cabin crew and flight attendants. Non-Routine - any other non-routine discrepancies reported by the mechanics at the time of execution. By default, the system displays “MIREP”. However, if you have specified part # as well as the serial #, the discrepancy must be of type “PIREP” only. Further, the system does not allow the change of discrepancy type, if the source document from which the discrepancy is retrieved is a journey log or an occurrence report. Note: If the reference document is a shop work order, you cannot change the type of the discrepancy to “Cabin”.

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

Discrepancy #

The number identifying the discrepancy.

Continue to enter the following fields in the “Discrepancy Details” multiline:

Discrepancy Description	The textual description of the discrepancy. (Alphanumeric, 150). Data entry in this field is mandatory for all discrepancies except those that are have been deferred. The system sets the description of a deferred discrepancy to its deferral item description, if you do not provide the description.. Help facility available.
Log Item #	The log item number of the discrepancy in the reference document, such as A/c Maint. Exe. Ref. (Alphanumeric, 20). The log Item # entered must be unique in the multiline. If you do not specify the log term #, the system sets this field to the discrepancy #.
Deferral Type	Use the drop-down list box to select the type of deferral, type of the discrepancy, if it has been deferred. The drop-down list box displays, CDL MEL All those deferral types defined in "Configure Document Attributes" activity of the Common Masters component that have the Attribute Flag set to "Yes The deferral type is mandatory, if Action of the discrepancy is: “Defer” “Closed" and the “Repeat” attribute is “Yes”. By default, the discrepancy type displays MIREP.
Deferral Item #	The number, which identifies the deferral item against which the discrepancy was reported (Alphanumeric, 150). Data entry in this field is mandatory, if ; The Action is set as “Defer” The Action is set to “Closed” and the Repeat is set to “Yes”. The deferral item # you specify must be valid for the deferral type as defined in the latest revision of the aircraft model configuration. Help facility available.
ATA #	The number that identifies the ATA chapter in which maintenance task is executed (Alphanumeric, 16). The ATA chapter must be in “Active” status and as defined in the “Aircraft” business component. Help facility available.
Action	Use the drop-down list box to select the action to be performed. The system lists the options: “Close”, “Defer”, “No Fault Found” and “Pending”. You can modify the values in the “Action” field, if the Discrepancy # is in “Deferred” status. Know the conditions for setting the action of a discrepancy
Corrective Action	The details of the Corrective action taken for the discrepancy reported. (Alphanumeric, 255). Data entry in this field is mandatory, if the “Action” field is set as “Closed”. Note that when you change the action of a discrepancy from “Defer” to “Close”, you cannot modify any attribute of a discrepancy except corrective action. You can modify the Corrective Action, if the Discrepancy # is in “Deferred” status and the “Action” is set as “No Fault Found” or “Closed”.
Repeat	Use the drop-down list box to indicate whether the discrepancy is frequent in nature. The drop-down list displays “Yes” and “No”.
Source Type	Use the drop-down list box to select the type of the source of the discrepancy. The drop-down list box displays Discrepancy, Task and all the Active codes defined under the attribute 'Source Type' in Maintain Discrepancy/ CR Attributes page of Common Master. Note: For a new discrepancy, Source Type is mandatory, if you have specified Source #.
Source #	The ID number of the task or discrepancy against which the discrepancy was reported. You must specify Task/Discrepancy # that is valid and Active as defined in Maintenance Task / Discrepancy Processing. Note: 1) For a new discrepancy, Source # is mandatory, if you have specified Source Type. 2) You cannot add discrepancies to any source task from AME Ref. # that exists in Completed, In-Complete, Closed, Pre-Closed, Cancelled or Duplicate status, if the process parameter ‘Allow discrepancy reporting against tasks in Completed, In-Complete, Closed, Pre-Closed, Cancelled or Duplicate statuses?’ for the package type is 0/No in the Define Process Entities activity of Common Master.

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

Source Tracking #	The tracking # of the source task/discrepancy # against which you wish to record discrepancy information. (The tracking # is generally found in AME Ref.# or SWO).
Record Status	The record status of the discrepancy could be 'Fresh', 'Pending', 'Under Resolution', 'Pending Deferral', 'Deferred', 'No Fault Found', 'Closed', 'Transferred', 'Cancelled', 'Retired' or 'Planned'.

Enter the following fields in the “Discrepancy Details” multiline:

Tracking Status	Use the drop-down list box to select the tracking status of the discrepancy. The system lists all the ‘active’ attributes of type “Tracking Status”, as defined in the “Maintain Discrepancy / CR Attributes” activity of the “Common Master” business component. By default, the system leaves the field blank.
Ref.Doc #	The reference document for the discrepancy (Alphanumeric, 40).
Authorization Ref. #	The authorization reference # of the discrepancy. This field is mandatory, if the Action is “Defer” and the “Mandate Authorization Reference #?”' is set as “Yes” for the specified deferral type.
Caused Delay ?	Use the drop-down list and select “Yes” or “No” to indicate whether the discrepancy caused a delay in the aircraft schedule or not.
Delay Ref #	The reference number identifying the delay.
Delay Notes	Any additional note related to the delay.
Incident Reported ?	Use the drop-down list box to indicate whether any incident has been reported against the discrepancy. The system lists the options “Yes” or “No”.
Incident Type	The type of accident or incident. The types could be a bird hit, lightning strike, hard landing, overweight landing, high energy stop etc.
Incident Ref #	The reference number of the incident.
Incident Notes	Any additional noted related to the incident.
AOG ?	Use the drop-down list and select “Yes” or “No” to indicate whether the aircraft is on ground or not.
Investigation Findings	The findings recorded on investigating the flight delay.
Investigation Conclusion	The conclusion recorded on investigating the flight delay.
Hold Item #	The hold item # of the discrepancy (Alphanumeric, 40).
Fault #	The number identifying the fault for the ATA # (Alphanumeric, 25). For old discrepancies, the fault number must be defined for the ATA # in the “Fault Isolation Manual” business component with “Active” status. For the newly recorded discrepancies, if you are specify both “ATA #” and “Fault #”, the fault number must be associated with the model of the aircraft in the “Fault Isolation Manual” business component.. Leave the field blank, if the Maintenance Object is selected as “Component”. Help facility available.
Reported By	The login ID of the user who reported the discrepancy (Alphanumeric, 20). Ensure that the login ID entered is in “Active” status and as defined in the “Employee” business component. Help facility available.
Reported Date	The date (as per the time zone of the station in which the package is executed) on which the discrepancy was reported. Date Format.
Reported Time	The time (as per the time zone of the station in which the package is executed) at which the discrepancy was reported. Date Format.
Note: (1) If you do not specify the reported date and time, the system sets the reported date and time of the discrepancy to the current server date and time. (2) You cannot change the reported date and time of a discrepancy, which is in “Pending” status”.
Closed Date	The date (as per the time zone of the station in which the package is executed) on which the discrepancy was closed. This is mandatory, if the Action is changed to “Closed”.
Closed Time	The time (as per the time zone of the station in which the package is executed) at which the discrepancy was closed. This is mandatory, if the Action is changed to “Closed”.
Ref. Total FH	The reference value of the aircraft. Leave this field blank for the system to consider the current value as the flying hours. The system displays the value you specify based on the Time Display Option set in the Create Parameters activity of the Aircraft component.
Remarks	Additional information pertaining to the discrepancy (Alphanumeric, 255). You must enter remarks for the modified records selected in the multiline, if the process parameter 'Mandate Remarks for modified records in Maintain Discrepancy Information?' is set as “Yes” under the Entity 'Discrepancy' of the Entity Type 'Discrepancy Management' in the “Common Master” business component. The remarks entered must be different from the last entered remarks.
Discrepancy Category	Use the drop-down list box to select the category of the discrepancy. The system lists all the ‘active’ attributes of type “Discrepancy Category”, as defined in the “Maintain Discrepancy / CR Attributes” activity of the “Common Master” business component. By default, the system leaves the field blank.

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

Fault Description

The textual description of the fault.

Note: The attributes of a discrepancy including Discrepancy Description, ATA, Corrective Action, Fault #, Discrepancy Category, Tracking Status, Reported by, Remarks, Deferral Type, Deferral Item #, Log Item #, Authorization Ref #, Reported Date, Reported Time, Closed Date and Closed Time can be modified based on back-end Set Options. Contact the System Administrator for more information.

Record the following:

Defect Type	Use the drop-down list box to select the defect type of the discrepancy. The drop-down list box displays the Active entities under the entity type “Defect Type” from the Define Process Entities activity of Common Master. Note: This field is mandatory if you intend to select an affected function for the discrepancy.
Affected Function	Use the drop-down list box to select the affected function of the discrepancy. The drop-down list box displays the Active codes defined the attribute “Affected Function” from the Maintain Discrepancy/ CR Attributes activity of Common Master. Note: The selected affected function must be valid for the defect type meaning the affected function must be mapped to the defect type in the activity.
Confirmed?	Use the drop-down list box to indicate whether confirmation from a higher authority is required in order to initiate corrective action. The drop-down list box displays Yes and No.
Safety Related?	Use the drop-down list box to indicate whether the discrepancy could injure passengers. The drop-down list box displays Yes and No.
Pax. Abuse?	Use the drop-down list box to indicate whether the discrepancy was caused as result of misuse/mishandling by the passenger. The drop-down list box displays Yes and No.
Cabin Position #	The cabin position # against which the discrepancy was reported.
No Of Channels	The number of channels available in the IFE monitors attached to the cabin position #.
Equipment Category	The equipment category of the cabin equipment attached to the cabin position # against which the discrepancy was reported. You can also enter multiple equipment category separated by commas. Note: The equipment category is mandatory for the discrepancy, if the process parameter “Display & enforce Equipment Category for discrepancies & tasks?" under the entity type Package Type and the entity: All Package Types and Log Card in the Define Process Entities activity of Common Master is 1 (Yes).
Reported Station	The station at which the discrepancy was reported. Note: The station you specify here must be in Active status as defined in Common Master. Help facility available
Closed Station	The station at which the discrepancy was corrected and resolved. Note: The station you specify here must be in Active status as defined in Common Master. Help facility available

Click the “Maintain Discrepancy Information” pushbutton, to record and update the discrepancy details.

Note: The “Maintain Discrepancy Information” pushbutton is visible, only if the ‘Create / Update Discrepancy’ radio button is selected.

The system performs the following on click of the “Maintain Discrepancy Information” pushbutton:

Generates a discrepancy number for all newly reported discrepancies, based on the “Default Numbering Type” set for the “Discrepancy Processing” transaction in the “Document Numbering Class” business component.
Updates the source document type as “Manual Compliance” and discrepancy type as “MIREP” in the “Discrepancy Processing” business component. If the valid aircraft reg #, component #, part # and serial # are provided by the user, the system generates the new discrepancy with Applicability set to “Aircraft”. However, if only component #, part # and serial # are provided, the system sets the Applicability of the discrepancy to “Component”.
Displays the “Ref. Total FH” field with the parameter value from the associated discrepancy based on the value selected in the “Time Display Format” field in the “Aircraft” business component. For example, if the Time Display Format is selected as HHMM and if the stored value is 2.50, the value is automatically converted from 2.50 to 2.30.

Updates the source/reference document whenever attributes of a discrepancy are modified in this page.
Updates the discrepancy details only if the discrepancy has not been published in the Reliability Analysis component.
Updates the Record Status of a discrepancy on the basis of Action and Repeat.

When the Repeat is set to “No”: the Record Status becomes “Pending”, if the Action is selected as “Pending”; and the Record Status is updated to “Close”, if the Action is changed to “Closed”.
When the Repeat is set to “No”: the Record Status becomes “Deferred”, if the Action is changed to “Closed” and Repeat is set to “Yes”.
When the Action of a discrepancy is set to “Close”, the Record Status of the discrepancy is reset to “Closed” and the Status of the non-standard task is set to “Completed”. The system also closes any log card that exists for the discrepancy.

However, an exception arises when the Action is changed to “Defer” as explained next.

1. For discrepancies of Deferral Types MEL and CDL, if the deferral item # you specify is valid, the system sets the Record Status to “Deferred”. However, if the deferral item # for the discrepancy is invalid, the system sets the Record Status to “Pending Deferral”.
2. Generates the Deferred Till Date for the discrepancy task, if the Action is modified to “Defer”. More details with example

If the Action is set to “Defer” and if the '”Addl. Approval Required?'” is set to “Yes” for the Deferral Type in the Configure Document Attributes” activity of the Common Masters component, updates the “Addl. Approval Required” for the discrepancy as “Required”.

To proceed

Select the “Create Material Request” link to create a material request to resolve the discrepancy reported against the specified aircraft.
Select the “Edit Deferral Report” link to modify the discrepancy for the specified aircraft.
Select the “Revise Deferral Limits” link, to revise the defer limits for the specified discrepancy.
Select the “Manage Discrepancy Resolution History” link to see the resolution details for the discrepancy.
Select the “View Associated Discrepancies” link, to see the discrepancies associated with the specified aircraft.

Uploading discrepancy

Select the “Upload Discrepancy” radio button.
Enter the following in the “Update Discrepancy Details” multiline:

Execution Ref #

The execution reference number against which the discrepancy is reported. Mandatory. The execution reference number entered is a valid Aircraft Maintenance Execution Reference # and must not be in “Draft”, “Fresh” or “Cancelled” status.

Help facility available.

The system displays the following:

Aircraft Reg #

The aircraft registration number against which the discrepancy is reported.

Enter the following fields:

Log Item #

The log leaf number of the discrepancy in the reference document, such as A/c Maint. Exe. Ref. Mandatory. The log Item # entered must be unique in the multiline.

Discrepancy Type

Use the drop-own list box to select the type of discrepancy. The system displays the following;

MIREP – discrepancies reported by the mechanic.
Non-Routine – any other non-routine discrepancies reported by the mechanics at the time of execution.
PIREP– discrepancies reported by the pilot.
Cabin - discrepancies reported by the cabin crew and flight attendants.

Note that only based on the following two set options, the system lists the options "PIREP" and "Cabin" in this field:

The set option “Allow upload of PIREP and CABIN discrepancies in Maintain Discrepancy Information?” in the “Define Process Entities” activity of the “Common Master” business component must be set as “Yes”.
The “Process Parameter Defined? column as defined for the Entity Type “Package Type” in the “Define Process Parameters” activity in the "Set Process Parameters" page of the “Common Master” business component must be set as “Yes”.

By default, the system displays “Non-Routine”.

The system displays the following:

Discrepancy No

The number identifying the discrepancy.

Enter the following fields:

Discrepancy Description	The textual description of the discrepancy. Mandatory. Help facility available.
ATA #	The number that identifies the ATA chapter in which maintenance task is executed (Alphanumeric, 16). Mandatory. The ATA chapter must be valid as defined in the “Aircraft” business component. Help facility available.
Action	Use the drop-down list box and select the action to be performed, Mandatory. The system lists the option “Close”. You must not leave this field blank, if the Execution Ref # is in ‘Closed’ status. By default, the system displays “Close”.
Corrective Action	The details of the corrective action taken for the discrepancy reported (Alphanumeric, 255). Data entry in this field is mandatory, if the “Action” field is set as “Closed”.
Part Required?	Use the drop-down list box and select “Yes” or “No” to specify whether parts are required to close the discrepancy or not. By default, the system displays “No”.
Corrosion Related?	Use the drop-down list box and select “Yes” or “No” to indicate whether the discrepancy reported is related to corrosion. By default, the system displays “No”.
Major Item?	Use the drop-down list box and select “Yes” or “No” to indicates whether the item on which discrepancy is reported, is a major item or not. By default, the system displays “No”.
Source Type	Use the drop-down list box to select the source type of the discrepancy. The drop-down list box displays Discrepancy, Task and all the Active codes defined under the attribute 'Source Type' in Maintain Discrepancy/ CR Attributes page of Common Master.
Source #	The code identifying the source of the discrepancy. If the Source Type is selected as “Task”, the source number entered here must be a valid task in “Open” status, as available in the Aircraft Execution Document # entered in the Execution Ref # field. If the Source Type is selected as “Discrepancy”, ensure that the Discrepancy # entered does not belong to any other aircraft. You must enter the Source #, if Source Type is selected.

Note: You must specify the Source Type and Source #, if:

Discrepancy Type is selected as “Non-Routine” and the process parameter ‘Mandate Source Document details on Discrepancy reporting?’ is set as "Required” for Non-Routine Discrepancies or for all Discrepancy types for the package type of the entered Execution Ref #.

(or)

Discrepancy Type is selected as “MIREP” and the process parameter ‘Mandate Source Document details on Discrepancy reporting?’ Is set as “Required” for PIREP, MIREP and Cabin Discrepancies or for all Discrepancy types for the package type of the entered Execution Ref #.

Reported By	The employee code of the user who reported the discrepancy (Alphanumeric, 20). Mandatory. Help facility available.
Reported Date	The date (as per the time zone of the station in which the package is executed) on which the discrepancy was reported. Mandatory. The ‘Reported Date’ must be earlier than or equal to the ‘Completed By Date’ / ‘Execution Ref # closure date’ / current date. Help facility available.
Mechanic	The employee code of the employee who performs mechanic sign-off against the discrepancy. A valid employee code mapped to the Resource Group ‘Mechanic’ or ‘Insp & Mech’ must be entered here. Data entry in this field is mandatory, if Action is selected as “Close” Process parameter ‘Default Sign-off Requirement for Non Routines’ is set as “Mechanic” or “Mech. & Insp.” in the “Set Process Parameters” page of the “Common Master” business component for the package type of the entered Execution Ref #. Help facility available.
Inspector	The employee code of the employee who performs inspector sign-off against the discrepancy. A valid employee code mapped to the Resource Group ‘Inspector’ or ‘Insp & Mech’ must be entered here. Data entry in this field is mandatory, if Action is selected as “Close” Process parameter ‘Default Sign-off Requirement for Non Routines’ is set as “Inspector” or “Mech. & Insp.” in the “Set Process Parameters” page of the “Common Master” business component for the package type of the entered Execution Ref #. Help facility available.
Note: The employee code entered in the ‘Mechanic’ and ‘Inspector’ fields must not be same, if the process parameter 'Permit Dual Sign-off by the employee?' is set as “No” in the “Set Process Parameters” page of the “Common Master” business component for the package type of the entered Execution Ref #.
RII Sign-Off	The employee code of the employee who performs RII sign-off against the discrepancy. A valid employee code mapped to the Resource Group ‘Inspector’ or ‘Insp & Mech’ must be entered here. Help facility available.
Addl. Sign-Off	The employee code of the employee who performs additional sign-off against the discrepancy. Help facility available.
Actual Man Hrs	The man hours required for completing the discrepancy.
Est Man Hrs	The estimated man hours for completing the discrepancy.
Completed By Date	The date on which the discrepancy was completed.
Completed By Time	The time at which the discrepancy was completed.
Note: The ‘Completed By Date’ / ‘Completed By Time’ must be entered, if ‘Action’ is set as “Close” and must be earlier than or equal to the ‘Execution Ref # closure date’ / current date.
File Name	The name of the file containing the discrepancy details. Help facility available.
Exceptions	Any exception occurring while uploading discrepancy.

Defect Type	Use the drop-down list box to select the defect type of the discrepancy. The drop-down list box displays the Active entities under the entity type “Defect Type” from the Define Process Entities activity of Common Master. Note: This field is mandatory if you intend to select an affected function for the discrepancy.
Affected Function	Use the drop-down list box to select the affected function of the discrepancy. The drop-down list box displays the Active codes defined the attribute “Affected Function” from the Maintain Discrepancy/ CR Attributes activity of Common Master. Note: The selected affected function must be valid for the defect type meaning the affected function must be mapped to the defect type in the activity.
Confirmed?	Use the drop-down list box to indicate whether confirmation from a higher authority is required in order to initiate corrective action. The drop-down list box displays Yes and No.
Safety Related?	Use the drop-down list box to indicate whether the discrepancy could injure passengers. The drop-down list box displays Yes and No.
Pax. Abuse?	Use the drop-down list box to indicate whether the discrepancy was caused as result of misuse/mishandling by the passenger. The drop-down list box displays Yes and No.
Cabin Position #	The cabin position # against which the discrepancy was reported.
No Of Channels	The number of channels available in the IFE monitors attached to the cabin position #.
Equipment Category	The equipment category of the cabin equipment attached to the cabin position # against which the discrepancy was reported. You can also enter multiple equipment category separated by commas. Note: The equipment category is mandatory for the discrepancy, if the process parameter “Display & enforce Equipment Category for discrepancies & tasks?" under the entity type Package Type and the entity: All Package Types and Log Card in the Define Process Entities activity of Common Master is 1 (Yes).
Reported Station	The station at which the discrepancy was reported. Note: The station you specify here must be in Active status as defined in Common Master. Help facility available
Closed Station	The station at which the discrepancy was corrected and resolved. Note: The station you specify here must be in Active status as defined in Common Master. Help facility available
Reported Time	The time (as per the time zone of the station in which the package is executed) at which the discrepancy was reported, Mandatory.

Click the “Validate” pushbutton to process and validate the discrepancy records in the multiline.

Click the “Upload Discrepancy Information” to upload the discrepancy details.

The system uploads the discrepancies against the Execution Ref #. The discrepancies are uploaded only if exceptions are not identified for any of the records in the multiline.
On successful upload of discrepancies, siscrepancy is created in “Under Resolution” status, if the ‘Action’ drop-down is left ‘Blank’, and in “Closed” status, if the ‘Action’ is set as “Close”. The Discrepancy # / Log Item # is displayed in the multiline.
The status of the Execution Ref. # is changed from “Planned” to “In-Progress”, on successful upload of discrepancy if corrective action is available for the entered discrepancy.

Defaulting of Sign Off Requirement for discrepancies:

4 The Mechanic / Inspector fields for the discrepancy upon save will be defaulted depending on the values set for the two process parameters "Allow Identification of Sign Off Requirement without Corrective Action for Discrepancies?" and “Default Sign Off Requirements for Non-Routines?” under the entity type Package Type and the entity “All User-Defined Package Types including Log Card” in the Define Process Entities activity in Common Master as illustrated in the next table. However, manually specified sign off requirement for the discrepancy by the user in the “Sign-Off Requirements” section will override the default sign off requirement as arrived by the system based on the above-explained process parameters.

Process Parameter: "Allow Identification of Sign Off Requirement without Corrective Action for Discrepancies?"	Process Parameter: “Default Sign Off Requirements for Non-Routines?”	Sign Off Requirements section for new discrepancy will be defaulted as
Allowed	0" for 'Not Required'	Mechanic and Inspector check boxes will remain deselected
	"1" for Mechanic'	Mechanic will remain selected
	"2" for Inspector'	Inspector will remain selected
	3" for Mech. & Insp.	Both, Mechanic and Inspector will remain selected

The sign off requirements defaulted for the corrective action will be similar to that of the discrepancy as set at the time of its creation.

To proceed carry out the following:

Select the “Edit Discrepancy Additional Information” link to edit the additional attributes of the package.

Refer to "Aircraft Maintenance Planning" online help for more details.

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

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

Maintain Discrepancy Information – Page overview

The “Maintain Discrepancy Information” page enables planners to record / update discrepancies as well as plan for their resolution from the same source. You can record and update the discrepancies and snags reported against the aircraft or the component. In this page, you can process the discrepancies that are reported for the aircraft or component, which are observed by the MROs or third party service providers (typically the mechanic or the maintenance operators) while executing the maintenance job. You can enter the discrepancy details along with the action performed for rectifying the reported discrepancies.

On recording or updating, based on the ‘action’ selected, the system updates the recording status of the discrepancy as “Pending”, “No Fault Found” or “Closed”.

Field availability based on process parameter definition in the Define Process Entities activity of Common Master

Process Parameter	Value	Fields not available in the Discrepancy Details multiline
Display Cabin Defect Attributes in Maintain Discrepancy Information?	0/No	· Defect Type · Affected Function · Safety Related? · Pax. Abuse? · No. of Channels
Display 'Equipment Category' in Maintain Discrepancy Information?	1/Yes
Process Parameter	Value	Fields not available in the Discrepancy Details multiline
Display Cabin Defect Attributes in Maintain Discrepancy Information?	1/Yes	· Equipment Category
Display 'Equipment Category' in Maintain Discrepancy Information?	0/No	· Equipment Category
Process Parameter	Value	Fields not available in the Discrepancy Details multiline
Display Cabin Defect Attributes in Maintain Discrepancy Information?	0/No	· Defect Type · Affected Function · Safety Related? · Pax. Abuse? · No. of Channels · Equipment Category
Display 'Equipment Category' in Maintain Discrepancy Information?	0/No
Process Parameter	Value	Fields not available in the Discrepancy Details multiline
Display Cabin Defect Attributes in Maintain Discrepancy Information?	1/Yes	NA
Display 'Equipment Category' in Maintain Discrepancy Information?	1/Yes	NA

What you can do in this page

Specify the action to be performed to rectify the discrepancy.

Set the “Action” field to “Pending”, if the discrepancies are yet to be processed.

Note: The system updates the record status of the discrepancy as “Pending”.

Set the “Action” field to “No Fault Found”, if no faults were reported against the discrepancy.

Note: The system updates the record status of the discrepancy as “No Fault Found”.

Set the “Action” field to “Closed”, if the discrepancies must be closed.

Note: The system updates the record status of the discrepancy as “Pending”.

Deferred Till Date computation

For first time deferral

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 below table.

The formulae in the table below 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’.

Discrepancy Deferred by	‘Deferral Limit Basis for calendar day / flight day computation’ set for the selected Deferral Type in “Common Masters” business component	Deferral Till Date
Calendar Days	Include Reporting Date	Deferral Till Date / Time = Reported Date (Local) + Deferral Duration – 1 Day Convert Time to 23:59 ---> Convert Date/Time to UTC Time Zone and save
	Exclude Reporting Date	Deferral Till Date / Time = Reported Date (Local)) + Deferral Duration Convert Time to 23:59 ---> Convert Date/Time to UTC Time Zone and save
	Not Applicable	Deferral Till Date / Time = Reported Date / Time (UTC) + Deferral Duration
Calendar Hours	-	Deferral Till Date / Time = Reported Date / Time (UTC) + Deferral Duration
Calendar Months	-	Deferral Till Date / Time = Reported Date / Time (UTC) + Deferral Duration
Flight Day	Include Reporting Date	Deferral Till Date / Time = Server Date (Local) + [(Param value as of Reporting Date with time set as 00:00 (Local) + Deferral Duration) - Current Param value] Convert Time to 23:59 ---> Convert Date/Time to UTC Time Zone and save
	Exclude Reporting Date	Deferral Till Date / Time = Server Date (Local) + [(Param value as of Reporting Date with time set as 23:59 (Local) + Deferral Duration) - Current Param value] Convert Time to 23:59 ---> Convert Date/Time to UTC Time Zone and save
	Not Applicable	Deferral Till Date / Time = Server Date (UTC) + [(Param value as of Reporting Date & Time (UTC) + Deferral Duration) - Current Param value]
Other Params	-	Deferral Till Date / Time = Server Date (UTC) + [(Param value as of Reporting Date & Time in UTC + Deferral Duration) - Current Param value] / Avg Daily Utilization

if the process parameter “Next Due computation logic” is set as ‘End of Day’, the formulae mentioned in the above 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:

If deferral duration alone is given, the Deferral Till Date & Time = Discrepancy Execution Date + Deferral duration.
If FH is given, the Deferral Till Date & Time = [(Threshold Value-Current FH )/ Avg. Utilization Value of FH] + Discrepancy Execution Date
If FC is given, then Deferral Till Date & Time = (Threshold Value-Current FC )/ Avg. Utilization Value of FC) + Discrepancy Execution Date
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)
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.
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.

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

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