Entering discrepancy details for technical log

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

Select the “Discrepancy Details” tab in the main page.

Enter the following field in the “PIREP & Tech Log Reported Discrepancy Details ” group box:

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.

Enter 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. The system lists the following values:

PIREP – refers to discrepancies reported by the pilot in the journey log.
MIREP – refers to the discrepancies reported by the mechanics in the work orders.
Cabin - refers to the discrepancies reported by the cabin crew and Flight Attendants.
Non-Routine - refers to the non-routine discrepancies reported by the mechanics at the time of execution.

Discrepancy #

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

Help facility available.

Note: Discrepancy details recorded in the “Record Pilot Reported Discrepancies” page of the journey log are displayed in this multiline. The system also retrieves the details of the maintenance report that is associated to the discrepancy.The system also 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 Ops”.

Discrepancies that are part of the “Record Pilot Reported Discrepancies” page are of type “PIREP”. However, the status of the other discrepancies, that are not part of the journey log, will be of type “MIREP”.

The system allows you to confirm a technical log only if a record with "Discrepancy Type" as "MIREP" or "PIREP" is available in the "Pirep and Tech Log Discrepancy Details" multiline, under the following circumstances:

The "Enforce Sign Off ?" field in the "Set Options" activity is set as "Yes".
Any row of the "Discrepancy?" field in the "Sub-Task Information" multiline of the "Record Work & Sign-off information" page, is set as “Yes”.

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 ‘Technical Log 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”.

Enter the following fields:

Tracking Status

Use the drop-down list box to specify 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 select the action to be performed on reporting the discrepancy. 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”.

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

Task #

The number identifying the task that must be executed to process the discrepancy (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.

Note: Ensure that the “Transfer to: Part#” and “Transfer to: Serial#” fields are entered if the “Action” selected is “Transfer”.

Note: The "Transfer to Part#" and "Transfer to Serial#" must be identified by a position code and level code that is "Active" in the "Build Aircraft Configuration" activity in the "Configuration" business component.

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

Enter the following fields:

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. Help facility available.
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. 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.

Select the “View File” link provided below the multiline, to view contents of the file.

The system displays the following:

Engg Service Req #

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

Enter the following field:

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.

Enter the following:

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 leaves the field blank.

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

If the “Journey Log#” field is left blank, the system retrieves all discrepancies corresponding to the aircraft registration number from the "Discrepancy Processing" business component, if:

Record status is "Pending"
“Discrepancy Type” is set as "MIREP"
Document type is not journey log

Note: The system retrieves discrepancies related to the "Journey Log#", if the journey log number is entered.

The system retrieves the above details only if the “Operations type” is set as “Flight Ops”.

Check the box in the “Select” column of the multiline, to mark the discrepancy to be processed.
Select the “Author Repair Procedure” link to modify the non-standard task details.

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

Select the “Record Work & Sign-off Information” link to update work information.
Select the “Create Engg. Service Request” link to create an engineering service request for the selected discrepancy.

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

Select the “Identify Resolution Procedure” link to identify the resolution procedure for the selected discrepancy.

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

Click the Delete icon in the tool bar above the multiline, to delete a selected discrepancy record.

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

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

Enter the following field in the “Deferred Discrepancy Resolution Details ” group box:

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.

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

Maint. Report #

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

Help facility available.

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.

Enter the following fields:

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	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 field:

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.

Enter the following fields:

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). Help facility available.
Inspected By	The name of the employee who has inspected the rectification of the discrepancy (Alphanumeric, 20). 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”.

Note: The system displays maintenance reports reported on the aircraft registration number, whose status is “Deferred”, from the “Discrepancy Processing” business component.

The system does not retrieve the above mentioned maintenance reports if the “Operation Type” drop-down list box is set to “Reporting Station”, irrespective of the value set in the back end set option “Retrieval of Forecasted Work Units/Deferred Discrepancies”.

Check the box in the “Select” column of the “Deferred Discrepancy Resolution Details” multiline, to mark the maintenance report for revising the deferment details.
Click the Delete icon in the tool bar above the multiline, to delete a discrepancy record.

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

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

Click the “Create Technical Log” pushbutton in the main page, to create technical log with the discrepancy details.

The system performs the following:

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. Defaults the resource group for non-routine task based on the values set in the “Set Options” page of the “Maintenance Task” business component for the Technical Log execution document. Also the system updates both the Task Master & Execution document with the Task attributes & Resource Sign Off Population information.
If the “Action” is set as “Defer”, “Transfer”, “No Fault found” or “Close”, then the system updates the record status of all the deferred maintenance reports to “Under resolution”.

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

the record status of the discrepancy is “Planned”,
action is specified as “Defer”, “Transfer”, “No fault found” or “Close” and
there is no maintenance report reference.
Click the “Confirm Tech Log” pushbutton in the main page, to confirm the technical log with the discrepancy and maintenance details.

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.

If the “Automatic Confirmation of Maint. Report” option is set to “Yes” in the “Set Options” activity, then the status of the maintenance report is automatically set to “Confirmed” on confirmation. The system also checks whether the login user has been assigned the rights to confirm a maintenance report in the “Discrepancy Processing” component. If the login user does not have the required rights, then the status of the maintenance report will not be automatically confirmed even when the “Automatic Confirmation of Maint. Report” option is set to “Yes” in the “Set Options” activity.

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’

The ‘Record Status’ is set as “Closed”, if the “Action” field is blank, the present record status is “Under Resolution” and the option setting for “Automatic Closing of Discrepancy #” is set to “Yes”.
The record status is set as “Deferred”, if the “Action” field is set to “Defer” and the present record status is “Under Resolution”, “Pending Deferral” or “Deferred” .
The record status is set as “Transferred”, if the “Action” field is set to “Transfer” and the present record status is “Under resolution”.
The record status is set as “No fault found”, if the “Action” field is set to “No fault found” and the present record status is “Under resolution”.
The record status is set as “Closed”, if the “Action field is set to “Close” and the present record status is “Under resolution”.

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

The record status is set as “Closed”, if the “Action” field is blank and the present record status is “Under resolution”.
The record status is set as as “Deferred”, if the “Action” field is “Defer” and the present record status is “Under resolution” or “Pending deferral”.
The record status is set as “Transferred”, if the “Action” field is “Transfer” and the present record status is “Under resolution”.
The record status is set as “No fault found”, if the “Action” field is “No fault found” and the present record status is “Under resolution”.
The record status is set as “Closed”, if the “Action” field is “Close” and the present record status is “Under resolution”.
The record status is set as “Cancelled”, if the “Action” field is “Cancel” and the present record status is “Under resolution”.

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

The record status is set as “Closed”, if the “Action” field is left blank, the present record status is “Deferred” or “Under resolution” and the option setting for “Automatic Closing of Discrepancy #” is set to “Yes”.
The record status is set as “Deferred”, if the “Action” field is set to “Defer” and the present record status is “Deferred” or “Under resolution”.
The record status is set as “Transferred”, if the “Action” field is set to “Transfer” and the present record status is “Deferred” or “Under resolution”.
The record status is set as “No fault found”, if the “Action” field is set to “No fault found” and the present record status is “Deferred” or “Under resolution”.
The record status is set as “Closed”, if the “Action” field is set to “Close” and the present record status is “Deferred” or “Under resolution”.
Click the “Cancel Tech Log” pushbutton in the main page, if you wish to cancel the technical log.

To proceed, carry out the following

Select the “Record Work & Sign-off Information” link to update work information.
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 “Inspector / Mechanic Information” tab in the "Create Technical Log" page, to record additional information for the technical log.
Select the “Cost & Additional Information” tab in the “Create Technical Log” page, to record additional information and cost details incurred on the technical log.