Modifying discrepancy details

Editing technical log information - An overview

Glossary

Basics of using a typical web page

Using Online Help

You can modify the PIREP and technical log-reported discrepancy details. You can also specify the deferred discrepancy resolution details.

Default Action

Use the drop-down list box to select a default action, which will be applicable to all the discrepancies selected in the “PIREP & Tech Log Reported Discrepancy Details” multiline. In other words, if the action for all the rows in the multiline is the same, you can specify it here, instead of repeating it for each and every row.

The system displays the following options: “No Fault”, “Defer”, “Transfer”, “Close” and “Cancel”. By default, the system leaves this field blank.

The system displays the following fields in the “PIREP & Tech Log Reported Discrepancy Details” multiline:

Discrepancy Type

The type of discrepancy that has been reported on the aircraft, which can be “PIREP” or “MIREP”.

  • PIREP – refers to discrepancies reported by the pilot or the cabin crew in the journey log.

  • MIREP – refers to the discrepancies reported by the mechanics in the work orders.

Discrepancy #

The number identifying the discrepancy reported on the aircraft (Alphanumeric, 40).

Help facility available.

Under the following circumstances, the system allows you to confirm a technical log, only if a record with "Discrepancy Type" as "MIREP" is available:

Note: Discrepancy details recorded in the “Record Pilot Reported Discrepancies” page of the journey log are displayed in this multiline. The system retrieves details of the maintenance report that is associated to the discrepancy.

Also, the system retrieves the details of all the discrepancies associated to the line package in the “Line Planning and Control” business component.

Note: The system retrieves the above details only if the “Operations Type” is set as “Flight Operations”, irrespective of the value set in the back end option “Retrieval of Forecasted Work Units/Deferred Discrepancies”.

Discrepancies that are part of the pilot defect report (reported in the journey log) are of type “PIREP”. However, the status of the other discrepancies, that are not part of the journey log, will be of type “MIREP”.

Discrepancy Description

The textual description of the discrepancy (Alphanumeric, 125). Mandatory.

Help facility available.

ATA #

The ATA chapter on which the discrepancy is reported (Alphanumeric, 16). Mandatory.

The ATA chapter should have already been defined in the “Create ATA Chapter” activity of the “Aircraft” business component and the status of the ATA chapter must be “Active”.

Help facility available.

Log Leaf #

The number identifying the log leaf, which contains the discrepancy details (Alphanumeric, 40). The system mandates the value in this field, if ‘Log Leaf Validation Basis’ is kept at ‘Discrepancy Level’ or ‘Technical Log Level & Discrepancy Level’. However, if Log leaf validation is set as ‘Optional’, then the system does not mandates value in the field.

The system displays the following fields:

Processing Status

The processing status of the discrepancy, which can be “None”, “Under Analysis” or “Analyzed”. 

Record Status

The status of the discrepancy or maintenance report, which can be “Fresh”, “Pending” or “Pending deferral”.

Tracking Status

Use the drop-down list box to modify the tracking status of the discrepancy. The system displays all the active codes that are defined under the “Tracking status” attribute in the “Maintain Discrepancy Attribute” activity of the “Common Masters” component.

Action

Use the drop-down list box to modify the action specified for the technical log. The system displays the following options: “No Fault”, “Defer”, “Transfer”, “Close” and “Cancel”.

Data selection in this field is mandatory.

Note: If the discrepancy in the multiline is a part of a maintenance report whose status is “Pending deferral” or “Deferred”, then you can only select the “Defer” action for such discrepancies. The action specified should be the same for discrepancies belonging to the same maintenance report.

The system will not allow you to confirm a technical log, if the “Action” is set to “Cancel” for a discrepancy of type “PIREP”.

If a value is available in the “Transfer to : Part #”, “Transfer to : Serial #” and “Transfer to : Component ID” fields, then the “Action” field can be set to “Transfer” only.

Note: The system sets the “Action” as “Defer” if the “Defer?” field in the “Record Pilot Report Discrepancies” page of the “Journey log” activity is set as “Yes” for the journey log number entered in the “Journey Log#” field.

Remedial Action Taken

The action taken to remedy the discrepancy (Alphanumeric, 2000).

This field must be entered, when no work units are defined under the selected discrepancy and the “Action” selected is “Closed”.

Task #

The number identifying the task that must be executed to process the discrepancies (Alphanumeric, 30).

Help facility available.

Note: Ensure that either “Remedial Action” or “Task #” is entered, if the “Action” is set as “Close”, “No Fault Found” or “Transfer”. 

Caused Delay?

Use the drop-down list box and set the field to “Yes”, if the discrepancy has a caused a delay in the flight. Select “No” otherwise. The system default this field to “No”.

Transfer To: Part #

The part number of the component to which the discrepancy has been transferred (Alphanumeric, 40).

Help facility available.

Transfer To: Serial #

The serial number of the part to which the discrepancy has been transferred (Alphanumeric, 40).

Help facility available.

The system displays the following field:

Maint. Report #

The number of the maintenance report that has been raised against the component for which discrepancies have been reported.

Reference #

The number of the document where the discrepancy was identified (alphanumeric, 40).

Fault #

The code identifying the fault in the aircraft (Alphanumeric, 25). Data entry in this field is mandatory if the “Cause #” field is entered. The fault code should have already been defined in the “Create Fault Codes” activity of the “Fault Isolation Manual” business component and the status of the fault code must be “Active”.

Help facility available.

Remarks

Any remarks about the fault code (Alphanumeric, 255).

Reported By

The code of the employee who has reported the discrepancy (Alphanumeric, 20).  The employee code must be valid as defined in the “Employee Information” component and should be in “Active” status.

Help facility available.

Rectified By

The name of the employee who has rectified the discrepancy (Alphanumeric, 20). The employee code must be valid as defined in the “Employee Information” component and should be in “Active” status. By default, the system displays the name of the login user.

Help facility available.

This field must be entered, when no work units are defined under the selected discrepancy and the “Action” selected is “Closed”.

Inspected By

The name of the employee who has inspected the discrepancy (Alphanumeric, 20). The employee code must be valid as defined in the “Employee Information” component and should be in “Active” status. By default, the system displays the name of the login user.

Help facility available.

Note: If the “Validate for employee presence as per ARS” option is set to “Yes” in the “Set Options” activity, then the system checks whether the employee was present during the reporting date and time at the execution station specified.

If the “Allow extra hour reporting without authorization” option is set to “No”, the system ensures that the employee has duty (normal or extra authorized) as per the rota schedule at the reporting date and time at the execution station.

Transfer To: Component ID

The ID of the component to which the discrepancy has been transferred (Alphanumeric, 90).

Help facility available.

File Name

The name of the file relating to the discrepancy or maintenance report (Alphanumeric, 50).

Help facility available.

The system displays the following:

Engg Service Req #

The number identifying the engineering service request, which refers to this maintenance report.

Engg Advice Note #

The number identifying the engineering advice note, which is a response to the problem reported in the engineering service request (Alphanumeric, 40).

Help facility available.

The system displays the following:

Chapter Description

The textual description of the ATA chapter for which the discrepancy has been raised.

Fault Description

The textual description of the fault code.

Discrepancy Category

Use the drop-down list to specify the discrepancy category. The system lists all active discrepancy categories defined in the ”Maintain Discrepancy/CR Attributes” activity of the “Common Masters” business component.

By default, the system displays the discrepancy category saved against discrepancy number. 

Note: If the “Automatic Closing of Discrepancy #” option in “Set Options” activity is set to “No”, then the system will not allow you to confirm the technical log if the record status of a discrepancy is “Fresh”, “Pending” or “Under Resolution”.

Refer to the “Maintenance Task” business component for more details.

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

Refer to the “Engineering Service Request” online help for more details.

Note: Discrepancies associated to the journey log cannot be deleted.

Note: You can only delete discrepancies that are newly entered.  

Default Action

Use the drop-down list box to select a default action, which will be applicable to all the maintenance reports selected in the “Deferred Discrepancy Resolution Details” multiline. In other words, if the action for all the rows in the multiline is the same, you can specify it here instead of repeating it for each and every row.

The system displays the following options: “No Fault”, “Defer”, “Transfer”, “Close” and “Cancel”. By default, the system leaves this field blank.

Maint. Report #

Enter the number of the maintenance report that has been deferred (Alphanumeric, 40). Mandatory.

Help facility available.

Note: On clicking the “Get Details” pushbutton in the main page, the system retrieves all the maintenance reports whose record status is “Deferred”, from the “Discrepancy Processing” business component. The system retrieves the details only if the operation type is “Flight Operation” and the value set in the back end set option “Retrieval of Forecasted Work Units/Deferred Discrepancies” is set to “Forecasted/Overdue Work Units.

The system displays the following:

Maint. Report Description

The textual description of the maintenance report.

ATA #

The ATA chapter against which the maintenance report has been raised.

Processing Status

The processing status of the maintenance report, which can be “None”, “Under Analysis” or “Analyzed”.

Record Status

The record status of the maintenance report.

Tracking Status

User the drop-down list box to specify the tracking status of the maintenance report. The system displays all the active codes that are defined under the “Tracking status” attribute in the “Maintain Discrepancy Attribute” activity of the “Common Masters” component. By default, the system leaves this field blank.

Action

Use the drop-down list to select the  action to be performed on the maintenance report. The system displays the following options: “No Fault”, “Defer”, “Transfer”, “Close” and “Cancel”.

Data selection in this field is mandatory.

Remedial Action Taken

The details of the action taken to remedy the discrepancies in the maintenance report (Alphanumeric, 2000).

Task #

The number identifying the task to process the maintenance report (Alphanumeric, 30).

Transfer To: Part #

The part number of the component to which the maintenance report has been transferred (Alphanumeric, 40).

Help facility available.

Transfer To: Serial  #

The serial number of the part to which the maintenance report has been transferred (Alphanumeric, 40).

Help facility available.

The system displays the following:

Fault #

The fault code defined in the “Fault Isolation Manual” business component that is applicable to the discrepancy being reported.

Hold Item #

The tracking number of the deferral against which the discrepancy is reported. The system displays the hold item number defined in the “Discrepancy Processing” business component.

Remarks

Any remarks about the fault code (alphanumeric, 255).

Rectified By

The name of the employee who has rectified the discrepancies in the maintenance report (Alphanumeric, 20). By default, the system displays the name of the login user.

Help facility available.

Inspected By

The name of the employee who has inspected the rectification of the discrepancy (Alphanumeric, 20).  By default, the system displays the name of the login user.

Help facility available.

Transfer To: Component ID

The component ID to which the maintenance report has been transferred (Alphanumeric, 90).

Help facility available.

Note: If the transfer is successfully completed, then the status of the above discrepancy is updated as “Transferred”. A new discrepancy number is generated for the discrepancy that has been transferred to the new component.

The system displays the following fields:

Engg Service Req #

The number identifying the engineering service request, which refers to this maintenance report.

Note: If the maintenance report is referred in multiple engineering service requests, then the system displays the latest ESR number in this field.

Engg Advice Note #

The number identifying the engineering advice note, which is a response to the problem reported in the engineering service request.

Chapter Description

The textual description of the ATA chapter against which the maintenance report has been raised.

Fault Description

The textual description of the fault code.

Note: The system will not allow you to confirm the technical log if the record status of the maintenance report is “Fresh”, “Pending Deferral” or “Under resolution”.

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

Note: Discrepancies associated to the journey log cannot be deleted. Only newly-entered discrepancies can be deleted.

The system performs the following:

The system updates the record status of a discrepancy to “Under Resolution” if it satisfies the following conditions:

The system updates the “Record Status” as explained below:

‘Record Status’ in the “PIREP & Tech Log Reported Discrepancy Details” multiline, when the discrepancy type is ‘PIREP’:

Note:  If the “Action” is set as “Close”, “No Fault Found” or “Transfer”, and if the “Task #” is not entered, the system generates a non-standard task with the description of the remedial action.

‘Record Status’ in the “PIREP & Tech Log Reported Discrepancy Details” multiline, when the discrepancy type is “MIREP” and there is no maintenance report reference:

‘Record Status’ in the “Deferred Discrepancy Resolution Details” multiline, when the discrepancy type is “PIREP”:

To proceed, carry out the following