Reporting discrepancy
You can create a discrepancy against another discrepancy or a task and record the details in this window.
Click the “Report Discrep.” pushbutton.
The Manage Discrepancy window appears.
The window displays the following:
Source Task / Discrep. # |
The task / discrepancy that caused the discrepancy. |
Source Desc. |
The description of the task / discrepancy that caused the discrepancy. |
Enter the following details of the discrepancy.
Type |
Use the drop-down list box to select the type of the discrepancy. The drop-down list box displays the following: MIREP, PIREP, Cabin and Non Routine. Process Parameter Dependency: The process parameter 'Default Discrepancy Type in Work Reporting Hub?' under the entity type Package Type and the entity All Packages in the Define Process Entities activity of Common Master defaults the type for a discrepancy based on the defined value as illustrated in the following table:
|
|||||||||||||||||||||||
Log item # |
The log leaf number of the discrepancy in the reference document, such as A/c Maint. Exe. Ref. |
|||||||||||||||||||||||
ATA # |
The ATA chapter associated with the discrepancy. Help facility available |
|||||||||||||||||||||||
Reported By |
The employee who reported the discrepancy. Help facility available. |
|||||||||||||||||||||||
Reported Date |
The date on which the discrepancy was reported. |
|||||||||||||||||||||||
Reported Time |
The time at which the discrepancy was reported. |
|||||||||||||||||||||||
Description |
The description of the discrepancy. Process parameter dependency: the users can modify the description and ATA # of non-standard tasks and discrepancies based on the definition of the new process parameter ‘Allow modification of Description & ATA # of open Non Routines?’ defined in the Define Process Entities activity of Common Master.
Note: The system copies the radio communication to the Description field, if you do not enter description for the discrepancy. |
|||||||||||||||||||||||
Radio Communication |
The possible action to resolve the discrepancy suggested by the user who reported the discrepancy. Generally, the reported user enters the suggestive action at the time of creating / reporting the discrepancy itself. The mechanic conveys details of the discrepancy / corrective action through radio communication. |
Enter the following in the “More Info” group box.
Parts Required? |
Use the drop-down list box to indicate whether more parts are required for the execution of the discrepancy task. The drop-down list box displays Yes and No. |
||||||
Corrosion Related? |
Use the drop-down list box to indicate whether the discrepancy was caused by corrosion of parts. The drop-down list box displays Yes and No. |
||||||
Major Item? |
Use the drop-down to indicate whether the discrepancy involves a major or a minor item. |
||||||
Category |
Use the drop-down list box to select the user-defined category of the discrepancy. The drop-down list box displays the ‘Active’ attributes of type “Discrepancy Category”, as defined in the “Maintain Discrepancy / CR Attributes” activity of the “Common Master” business component. Process Parameter Discrepancy: This field is mandatory for the creation of the discrepancy, if the process parameter ”Mandate Discrepancy Category on Discrepancy Reporting?” under the entity type Package Type and the entity “All user defined package types including Log Card” in the Define Process Entities activity of Common Master is set as 1 for the package type. However, if ”Mandate Discrepancy Category on Discrepancy Reporting?” is set as 0, you may not specify the category of the discrepancy. |
||||||
Repair Class. |
Use the drop-down list box to select the repair classification for the discrepancy. The drop-down list box displays the quick codes defined under the quick code type Repair Classification in the Create Quick Codes activity of Maintenance Task. Process parameter dependency: If the process parameter "Mandate Repair Classification for Discrepancies during Maintenance Execution?" under the entity type Package Type and the entity All Packages is set as 1 for Yes in the Define Process Entities activity of Common Master, this field is mandatory for a discrepancy at the time of creation. |
||||||
Repeat? |
Use the drop-down list box to indicate whether the discrepancy is frequent in nature. The drop-down list displays “Yes” and “No”. |
||||||
Skill # |
The skill required by the employee for executing the discrepancy. Help facility available |
||||||
Zone # |
The zone where the discrepancy task is scheduled for execution. Help facility available |
||||||
Work Area # |
The work area where the discrepancy task is scheduled for execution. Process Parameter dependency: This field is mandatory, if the process parameter "Mandate Work Area # for Discrepancies during discrepancy reporting?" under the entity type Package Type and the entity “All user defined package types including “Log Card” excluding “All Packages”” is set as 1 for Yes. Help facility available |
||||||
Est Man Hrs |
The estimated elapsed time for execution of a task. (Integer). For a non-standard task / discrepancy #, ensure that a positive integer is entered here. For each task # if this field is left blank, the system updates 'Estimated Man hours' saved earlier for that task #. If the 'Estimated Man Hours' is not saved for that Task #/ Discrepancy #, the system performs the following:
Process parameter dependency: Based on the process parameter ”Est. Man Hrs. level for Discrepancies?” set under the entity type package Type and the entity All user defined package types including “Log Card” excluding “All Packages”, you must specify estimated man hours at the discrepancy level or corrective action level.
If multiple corrective actions have been recorded against the discrepancy, this field will display the sum of the estimated man hours recorded against all the corrective actions. |
||||||
Exe. Phase |
Use the drop-down list box to specify the execution phase of the task. The system lists the following values along with all the active quick codes defined for the Quick Code type “Execution Phase” in the “Maintenance Task” business component:
By default, the system displays the value saved against the respective Task # - Seq # combination. |
||||||
Exec. Category |
Use the drop-down list box to specify the execution category of the task. The system lists all the ‘Active’ values defined for the Quick Code Type “Execution Ref # Category” in the “Create Quick Codes” activity of the “Flight Log” business component. By default, the system displays the previously saved value for the Task #, Seq # combination. If this field is left blank, the system updates Doc. Category as the Execution Category of the task. |
||||||
Work Center # |
Use the drop-down list box to select the work center in which the discrepancy task must be executed by the mechanic. The drop-down list box displays all the Active work centers for which the login user has the access privileges. Note: By default, the work center for the Source Task / Discrepancy # is displayed in the Work Center # field . However, if the Source Task #/ Discrepancy # is not specified for the discrepancy, the work center for the package is defaulted in the field. |
Enter the following in the Corrective Action group box.
Corrective Action |
Comprehensive details of the corrective action undertaken to resolve the discrepancy. Process Parameter dependency: Corrective Action is mandatory for a discrepancy to be deferred (Action = Defer), if the process parameter “Mandate Corrective Action during discrepancy deferral?” under the entity type Package Type and the entity All User-Defined Package Types in the Define Process Entities activity of Common Master is 1 / Yes. |
||||||
CA Est. Man Hours |
The estimated elapsed time for resolution of the discrepancy. Process parameter dependency: Based on the process parameter ”Est. Man Hrs. level for Discrepancies?” set under the entity type package Type and the entity All user defined package types including “Log Card” excluding “All Packages”, you must specify estimated man hours at the discrepancy level or corrective action level.
If multiple corrective actions have been recorded against the discrepancy, this field will display the sum of the estimated man hours recorded against all the corrective actions. |
||||||
Skill # |
The skill required for the resolution of the discrepancy. |
Select the following under Sign Off Requirement.
Note: On launch of the Discrepancy Actions window (on click of the Discrepancy Action pushbutton) or on selection of the corrective action in the Discrepancy Actions window, the Mechanic field in the Sign Off Details group box automatically displays the employee code of the login user under the below-fulfilled conditions:
1. The process parameter 'Default Sign Off Details in the Task/Discrepancy Action popup in the Work Reporting Hub?' under the entity type 'Package Type' and entity Log Card and User-Defined Packages is is ‘1’/ Yes in the Define Process Parameters activity of Common Master.
2. The Sign off status is 'Pending Mechanic' or 'Pending Mech&Insp', the login user belongs to 'Mechanic', 'Mechanic & Inspector' resource group and has the requisite skills to Sign Off the discrepancy as an Mechanic and Inspector
3. The Sign off status is either 'Pending Inspector' or 'Pending Mech&Insp', the login user belongs to either 'Inspector' or 'Mechanic & Inspector' resource group and has the requisite skills to Sign Off the discrepancy as an Inspector.
For more details, refer to the section "Defaulting of Sign Off Requirement for discrepancies".
Mechanic Sign Off |
Select the check box to indicate mechanic sign off is mandatory for validating the action carried out on the discrepancy. |
Mech Skill # |
The skill that the mechanic must possess to sign-off the corrective action/discrepancy. Help facility Available. |
Inspector Sign Off |
Select the check box to indicate inspector sign off is mandatory for validating the action carried out on the discrepancy. |
Insp Skill # |
The skill that the inspector must possess to sign-off the corrective action/discrepancy. Help facility Available. |
RII Sign Off |
Select the check box to indicate either inspector sign off or mechanic sign off is mandatory for validating the action carried out on discrepancy. |
RII Skill # |
The skill that the mechanic/ inspector must possess to sign-off the corrective action /discrepancy. Help facility Available. |
Enter the following under the Status & Sign Off group box.
Action |
Use the drop-down list box to select the action carried out on the discrepancy. The drop-down list box displays the following: Close, Defer, Part Change – Closure and Cancel. |
Mechanic |
The employee code of the mechanic who has signed off the action on the discrepancy, if you have selected the Mechanic check box. Help facility available |
Inspector |
The employee code of the inspector who has signed off the action on the discrepancy, if you have selected the Inspector check box. Help facility available |
Enter the following under the Component Details group box.
Part # |
The part in which the discrepancy was found. Help facility available |
Serial # |
The serial of the part in which the discrepancy was found. Help facility available |
Position Code |
The position in which the part – serial associated with the discrepancy was attached in the NHA or aircraft. Help facility available |
Select the following under the Actual Date Time group box.
Start |
The date on and time at which the task to resolve the discrepancy commences. |
End |
The date on and time at which the task to resolve discrepancy concludes. |
Click the “Report Discrepancy” pushbutton. Dual Authentication
Defaulting of Sign Off Requirement for discrepancies:
The Mechanic / Inspector check boxes for new 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 wil remain selected |
|
3" for Mech. & Insp. |
Both, Mechanic and Inspector will remain selected |
4 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.
4 Note: The sign-off requirements for the corrective action will be defaulted as set for the discrepancy at the time of its creation.
Automatic assignment of the new discrepancy on creation
Based on the process parameter “Auto assign discrepancies reported against an assigned task during discrepancy creation?” under the entity type “Package Type” and the entity “including Log Card” and excluding “All Packages” defined in the Define Process Entities activity of Common Master, the just reported discrepancy is automatically assigned to specific employee for resolution in the following way:
Process Parameter: “Auto assign discrepancies reported against an assigned task during discrepancy creation?”*: value |
Impact on discrepancy assignment |
0 for No |
The discrepancy must be explicitly assigned to specific login user/employee for resolution. |
1 for Parent |
The discrepancy is automatically assigned to the login user/employee who reported the parent task of the discrepancy |
2 for Discrepancy Reporter |
The discrepancy is automatically assigned to the login user/employee who reported the discrepancy |