Record Shop Execution Details
This section describes the Shop Work Order business component and its activity Record Shop Execution Details.
Record Shop Execution Details – A summary of the activity[k1]
This is a one-stop screen for executing shop work orders, including performing all execution level operations, recording timesheets for the execution of the tasks, booking in-direct hours, sign-off of tasks, record part receipt details and hold / release a task.
Shop work order can be created under different scenario, e.g. when creating customer order, while routing the parts, etc.
You can record observations and discrepancies that are found during execution of tasks.
What you can do in this activity
Recording work actual details
You can perform all execution level operations.
Report findings
You can record observations and discrepancies that are found during execution of tasks.
Disassemble and assemble core
You can attach, remove and replace components and spare parts with respect to the main core component.
Initial Workscoping
You can define workscope for the execution of tasks in a shop work order.
Material Request
You can raise material requests for the tasks and discrepancies.
Record Shop Execution Details
Hlpsworecshpexe_sworecshpexemn.htm
Ø Select the “Record Shop Execution Details” activity under the “Shop Work Order” business component.
The “Record Shop Execution Details” page appears.
To Search for shop work orders
In this section, you can search for Shop Work Orders based on different ‘Search On’ options.
Ø Enter the following field in the “Search On” group box:
Search On |
Use the drop-down list box to select one of the following values. Based on the values selected, shop work order details will be retrieved and displayed in the corresponding tree interface. § Part # / Serial # § Facility Object # § Component # § Event Id § Employee Name § Removed from A/C # § Customer # § Operator # § Contract # § Work Center # § Customer Order # § Shop Work Order # § WO Description § WO Category By default the system displays “Part # / Serial #”. |
|
In the edit boxes provided alongside, enter a value corresponding to the “Search On” value selected for which you wish to retrieve matching Shop Work Orders. Mandatory. You can enter the value in full or specify it partially using the “*” character. The system retrieves all shop work order numbers that are similar to the number entered here. |
Date & Time |
The date and time at which the shop work order is executed. (Date & Time Format). |
Ø Click the “Go” pushbutton or press “Enter” to retrieve the search results.
Ø Click the “Work Actual” tab to record the actual task execution details.
Ø Click the “Report Findings” tab to
Ø Click the “Disassemble & Assemble Core” tab to
Ø Click the “Initial Workscoping” tab to
Ø Click the “Material request” tab to
Ø Click the “Correspondences” tab to
Recording work actual details
Hlpsworecshpexe_sworecshpexemn_wrkactual.htm
You can record the actual work execution details of the task in this tab page. The details of all the tasks under any shop work order, displayed at task level or sub-task can be recorded. Using this tab, you can perform the following:
4 You can record details such as hold status of the task, clock information, sign-off status of the task, start date / time and end date / time of the task.
4 Perform Mechanic / Inspector / RII sign-off of the task.
4 You can specify whether the task is mandatory.
4 Perform timesheet booking for the execution of the tasks.
4 You can book timesheet for the in-direct hours clocked by the employee.
4 Acknowledge the receipt of parts for execution of the task on the receieved part.
4 Hold the task or release the task which is held.
Ø Select the “Work Actual” tab in the “Record Shop Execution Details” page.
This tab page is selected by default, on launch of the page.
“Work Actual” tree default display details
A tree structure is displayed in the left pane, with “Shop Work Order” as the parent node, and the “SWO #” and task status as the child nodes. The tree displays all the shop work orders and the associated tasks, based on the based on the process parameter “Allow Task Reporting by?” set in the “Set Process Parameter” page of the “Common Master” business component, as follows:
· If the parameter “Allow Task Reporting by?” is set as “All Employee”, the “Work Actual” tree displays all the shop work orders with all the tasks for which the employee mapped to the login user, has clock running for at least one task.
· If the parameter is set as “Assigned Employee”, the tree displays all the shop work orders with only the task for which the employee mapped to the login user, has clock running.
Tree Structure:
- Shop Work Order
- SWO #1
- Planned
ATA # :: Task # :: Task Desc. :: Part # :: Serial # :: Work Center #:: Part Desc
+ In-Progress
+ Completed
+ Ext. Routed
+ Pre-Closed
+ Closed
- SWO #2
- SWO #3
On clicking “Go”
When a value e.g. “Part # / Serial” # is selected in the ‘Search On’ drop-down list box, and a part number and a serial number are entered in the editable boxes provided alongside, on invoking “Go”, the system performs the following:
a. The system retrieves refreshes the tree and retrieves and displays all the shop work orders belonging to the entered part # / serial # combination in the tree.
b. The “Task Details” multiline is refreshed to display the search results at either task level or subtask level.
On clicking the SWO # in the tree, the tree is expanded to display all the available task status as child nodes. The selected node is highlighted is the tree.
Transfer of task details
Ø In the right pane, select one of the following radio buttons above the multiline:
Display By |
Indicates whether the work orders are displayed at task level or subtask level. The system displays the following radio buttons for you select: · Task – Select this radio button to retrieve the task details under the shop work orders, at task level. · Subtask – Select this radio button to retrieve the task details under the shop work orders, at subtask level. Note: The button “Subtask” appears selected by default, if the process parameter “Enable Sub-task level sign-off?” is set as “Required” for the Entity Type “Shop Work Type” in the “Set Process Parameter” page of the “Common Master” business component. If the said parameter is set as “Not Required”, the “Task” radio button appears selected by default and the “Subtask” button is disabled. |
Ø
Click the ‘’ icon to transfer the task details
from the “Work Actual” tree to the multiline.
§ If the ‘Display By’ is set as “Task”, the system displays all the tasks selected in the tree under any shop work order, along with the existing the tasks in the “Task Details” multiline.
§ If the ‘Display By’ is set as “Subtask”, the system displays all the tasks selected in the tree under any shop work order, along with the existing the sub-tasks in the “Task Details” multiline, at sub-task level.
Retrieval of task details in the multiline
The system displays the following fields in the “Task Details” multiline:
M (Mandatory) |
Indicates whether the task is mandatory or not. The system displays the value “M” which refers to ‘Mandatory’. |
HS (Hold Status) |
The hold / release status of the task. The system displays the value “H” which indicates ‘Hold’. |
CI (Clock Info) |
The clock information of the task, which could be “D” (Clock-Direct) or “M” (Manual-Direct). |
SS (Sign-Off Status) |
The sign-off status of the task, which could be one of the following: M (Mechanic) – Indicates that the task requires mechanic sign-off. I – Indicates that the task requires inspector sign-off. M&I – Indicates that the task requires sign-off by both mechanic and inspector. SO – Indicates that the task is signed-off. NR – Indicates that the sign-off of the task is not required. |
PRT (Material Planning Status) |
The material planning status for the task. |
Ø Enter the following fields:
SWO # |
The code identifying the shop work order for which the details are retrieved. (Alphanumeric, ). Mandatory. The status of the shop work order number entered must be “Planned”, “In-Progress” and “Completed”. Help facility available. |
Seq # |
The sequence number of the task. (Integer). The sequence number entered must be valid for the SWO-Task # combination. You must enter the sequence number, if the same task number is available more than once for the same shop work order. |
The system displays the following field only when the “Task” radio button is selected:
Task Desc. |
The textual description of the task. |
Ø Click the hyperlinked task description to view the task additional details.
Ø Enter the following fields:
Task # |
The unique code identifying the task. (Alphanumeric, ). You must enter the task number, if the sequence number is not entered for the shop work order. The task number entered must be mapped to the shop work order number in the multiline, and the status of the task must be in status other than “Cancelled”, “Closed” or “Pre-closed”. If the parameter “Allow Task Reporting by?” is set as “Assigned Employee” in the “Common Master” business component, the task entered must be assigned to the employee in the “Work Monitoring and Control” business component. Help facility available. |
Note: Ensure that the task number and the shop work order entered cannot be modified.
Start Date & Time |
The start date and time of execution of the task. (Date & Time Format). When the clock is ‘On’, ensure that the start date and time is entered, if the process parameter “Employee Time Sheet Update Mode” is set as “Manual” in the “Set Process Parameter” page of the “Common Master” business component. If the parameter is set as “Clock”, this field must be left blank. The difference of days between the server date and time and the start date and time must be earlier than or equal to the value of the “Backdated reporting Time Limit (in days)” defined in the “Set Process Parameter” page of the “Common Master” business component. The system does not allow the employee to record actual working hours and in-direct working hours for the same start date and time specified here. |
End Date & Time |
The end date and time of execution of the task. (Date & Time Format). When the clock is ‘Off’, ensure that the end date and time is entered, if the process parameter “Employee Time Sheet Update Mode” is set as “Manual” or “Clock & Manual” in the “Set Process Parameter” page of the “Common Master” business component. If the parameter is set as “Clock”, this field must be left blank. The end date and time must be later than or equal to the start date and time. |
Note: Ensure that the employee has not booked indirect working hours against the ‘Start Date & Time’ and ‘End Date & Time’ entered.
Note: If an employee’s leave is in “Approved” status during the period of ‘Start Date & Time’ and ‘End Date & Time’ entered, the system does not allow the employee to record the timesheet for the ‘Start Date & Time’ and ‘End Date & Time’.
Example:(Pop-up)
a. Consider that an employee has taken leave from 10-Feb-2011 to 12-Feb-2011. If the timesheet is recorded from 9-Feb-2011 to 14-Feb-2011, system does not allow this operation. He can split this into two records i.e. assignment-1 will be from 9-Feb-2011 to 9-Feb-2011 and assignment-2 will be from 13-Feb-2011 to 14-Feb-2011.
b. Consider that the employee has taken leave from 10-Feb-2011, 12:30 AM to 10-Feb-2011, 04:00 PM. If timesheet is recorded from 10-Feb-2011, 07:30 AM to 10-Feb-2011, 04:00 PM, the system does allow this operation.
Atten. Type |
Use the drop-down list to select the attendance type of the employee. The system lists the value “Normal” along with all the ‘Active’ values defined for the quick code “Additional Attendance Type” in the “Create Quick Codes” activity of the “Work Center” business component. The system leaves the field blank, by default. |
Employee Comments |
Any comments entered by the employee, at timesheet level. (Alphanumeric, ) |
Repair Classification |
Use the drop-down list box to specify the repair classification in order to differentiate the tasks which are over and above the contract (COA - Contract Over and Above) between the operator and the MRO. The system lists all the ‘Active’ quick codes of type “Repair Classification” defined in the “Maintenance Task” business component. The system leaves the field blank, by default. |
Execution Comments |
Any comments entered by the employee, at task level. (Alphanumeric, ) |
The system displays the following fields:
Rev. # |
The revision number of the task. |
Sub-Task Desc. |
The textual description of the sub task. This field is displayed only if the process parameter “Enable Sub-task level sign-off?” is set as “Required” in the “Common Master” business component. |
AMM / CMM Item # |
The Aircraft Maintenance Manual (AMM) or the Component Maintenance Manual (CMM) item number given for the task in the respective manuals. (Alphanumeric, 40). |
Status |
The status of the task, which could be “Planned”, “In-Progress”, “Complete”, “Closed”, “Pre-closed”, “Cancelled”, “External Routed” or “Duplicate”. |
Work Center # |
The code identifying the work center at which the task is executed. |
Other Logons |
The names of all the employees are displayed, separated by ‘colon’, if timesheet is booked by more than one employee for a task. |
Part # |
The code identifying the part on which the task is executed. |
The system displays the “Mfr. Part #” and “Mfr. #” fields, and hides the “Part #” field above, if the parameter “Enable Manufacturer Part # control in transaction” under the Category ‘Manufacturer Part #’ is set as “Yes” in the “Set Inventory Process Parameters” activity of the “Logistics Common Master” business component. If the parameter is set as “No”, the system displays only the “Part #”.
Mfr. Part # |
The number assigned to the part, by the manufacturer of the part. |
Mfr. # |
The code identifying the manufacturer of the part. |
Serial # |
The serial number of the part. |
Part Desc. |
The textual description of the part. |
Ø Click the hyperlinked part description to view the part details.
WBS Code |
The Work Breakdown Structure (WBS) code indicating the attributes that identify whether the task is executed for planning purpose or execution purpose. |
Root Task # |
The code identifying he parent task. |
Ø Click the hyperlinked root task number to view the details of the parent task.
Routing Status |
The routing status of the part, which could be one of the following: · Pending Movement – Indicates that the part is not yet moved to the destination warehouse. · Moved – Indicates that the part is moved to the destination warehouse, but not received by the mechanic for execution of the task. · Received – Indicates that the part is received by the mechanic for execution of the task.
|
Location |
The information identifying the location of the part. |
Note: Ensure that at least one record is selected in the multiline.
Timesheet details
Ø In the “Timesheet” group box, perform the following:
Ø Click the “Clock On” pushbutton to start the clock for recording the actual working hours of the employee.
The system ensures the following on clicking the “Clock On” pushbutton:
4 The employee must be asigned to the service area of the work center.
4 The routing status of the part must be “Received” for a part # - serial # associated to the task, if the process parameter “Enforce Acknowledge Receipt?” is set as “Yes” for the SWO type in the “Common Master” business component.
4 On successful start of the clock, for every change in the status of the SWO # / Task #, the system updates the status log with 'Entity Changed' (SWO or Task), 'From Status', 'To Status', ‘Performed At Station’, ‘Performed At work center’, ‘Changed by’ (Employee Name) and ‘Changed Date & Time’.
4 The clock cannot be started, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order, with the process parameter “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” in the “Common Master” buisness component.
4 The clock cannot be started for the task belonging to the shop work order, if one of the following conditions is true:
a. If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
b. If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the “Common Master” business component.
c. If the process parameter “End Running Clock Bookings automatically?” (Is this the option? Given as Stop Direct Clock Booking" in FID 62.) is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
Ø Click the “Clock Off” pushbutton to stop the clock for terminating the actual working hour reporting.
The system ensures the following on clicking the “Clock Off” pushbutton:
4 The routing status of the part must be “Received” for a part # - serial # associated to the task, if the process parameter “Enforce Acknowledge Receipt?” is set as “Yes” and the process parameter ‘Employee Time Sheet Update Mode’ is set as “Manual” or “Clock & Manual” for the SWO type in the “Common Master” business component.
4 On successful end of the clock, for every change in the status of the SWO # / Task #, the system updates the status log with 'Entity Changed' (SWO or Task), 'From Status', 'To Status', ‘Performed At Station’, ‘Performed At work center’, ‘Changed by’ (Employee Name) and ‘Changed Date & Time’.
4 The clock cannot be stopped, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order. This is true only if the following process parameters are set in the “Common Master” buisness component.
· “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” for the SWO Type.
· ‘Employee Time Sheet Update Mode’ is set as “Manual” or “Clock & Manual” for the SWO type.
4 The clock cannot be stopped for the task belonging to the shop work order, if one of the following conditions is true:
a. If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
b. If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
c. If the process parameter “End Running Clock Bookings automatically?” (Is this the option? Given as Stop Direct Clock Booking" in FID 62.) is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
The worked hours for each task is computed based on the number of tasks the employee has simultaneously worked on.
· If the employee has worked on only one task for the given date and time range, the difference between the 'End Date & Time' and 'Start Date & time' is calculated as the “Worked Hours.
· If employee has simultaneously worked on more than one task, the total duration spent (after excluding break and indirect hours, if they are falling in the same range) must be apportioned to each task, depending on the estimated elapsed time identified for each task.
The system calculates the labor cost for ‘Normal’ and ‘Overtime’ hours as follows:
· If the job rate mapped to the employee is identified, the labor cost for timesheet records booked with Attendance Type “Normal” is calculated using the normal rate. Similarly, the labor cost for timesheet records booked with Attendance Type other than “Normal” is calculated using the overtime rate.
· If the job rate is not identified, the system calculates the normal and overtime rates as per the rates defined for the Primary Skill # in the “Unit Structure” business component, to calculate the labor cost for normal and overtime hours.
The system updates the timesheet status based on the option ‘Authorization of Timesheet Records” set in the “Set Process Parameters” page of the “Common Master” business component.
· If the ‘Authorization of Timesheet Records’ is set as “Not Required”, the timesheet status is updated as “Fresh”.
· If the ‘Authorization of Timesheet Records’ is set as “Required”, the timesheet status is updated as “Authorized”.
Note: Timesheet details cannot be modified for the timesheet records for which the timesheet status is “Authorized”.
Ø Check the following box:
Parts Returned? |
Check this box to specify that there is no part pending for return to any warehouse. This box appears checked by default, if the process parameter “Enforce Excess/Core Returns on order closure?” is set as “Yes” for the Entity Type “Shop Work Order Type” in the “Set Process Parameter” page of the “Common Master” business component. |
Ø Click the “Reset” pushbutton to reset the clock.
The system ensures the following on clicking the “Reset” pushbutton:
4 The employee must be assigned to the service area of the work center.
4 On successful start of the clock, for every change in the status of the SWO # / Task #, the system updates the status log with 'Entity Changed' (SWO or Task), 'From Status', 'To Status', ‘Performed At Station’, ‘Performed At work center’, ‘Changed by’ (Employee Name) and ‘Changed Date & Time’.
4 The clock cannot be reset, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order, with the process parameter “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” in the “Common Master” buisness component.
4 The clock cannot be reset for the task belonging to the shop work order, if one of the following conditions is true:
a. If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
b. If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
c. If the process parameter “End Running Clock Bookings automatically?” (Is this the option? Given as Stop Direct Clock Booking" in FID 62.) is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
Ø Click the “Complete” pushbutton to complete the execution of the task.
The system displays a pop-up screen “Manage Intershop Routing” if the status of the task in the Shop Work Order is updated as “Completed” and if the parameter 'Routing required?' is set as “Yes” in ‘SWO Task Details’ table and ‘Routing Details’ table.
The system ensures the following on clicking the “Complete” pushbutton:
4 The system updates the status of the task to “Completed”, if the ‘Display By’ is set as “Subtask” and if all the subtasks of the task have sign-off status as ‘Signed-off”, “Void” or “Rejected”.
4 The system updates the status of the Shop Work Order as “Completed”, if the task whose status is changed as “Completed” is the last task in the work order and the other tasks in the work order are already completed.
4 The employee must be assigned to the service area of the work center.
4 The routing status of the part must be “Received” for a part # - serial # associated to the task, if the process parameter “Enforce Acknowledge Receipt?” is set as “Yes” and the process parameter ‘Employee Time Sheet Update Mode’ is set as “Manual” or “Clock & Manual” for the SWO type in the “Common Master” business component.
4 The Sign-Off status of the tasks and subtasks of the Shop Work Order is updated as “Signed-Off” or “Not Required”, if the Process parameter “Enforce Sign-Off?” is set as “Yes” in the “Common Master” business component.
4 The sign-off details cannot be modified if the task / subtask is ‘Sign-off’, ‘Void’ or ‘Rejected’.
4 The task cannot be completed, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order. This is true only if the following process parameters are set in the “Common Master” buisness component.
· “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” for the SWO Type.
· ‘Employee Time Sheet Update Mode’ is set as “Manual” or “Clock & Manual” for the SWO type.
Note: The system displays an error message if any concurrent user attempts to modify the timesheet details.
4 On successful completion of the task, for every change in the status of the SWO # / Task #, the system updates the status log with 'Entity Changed' (SWO or Task), 'From Status', 'To Status', ‘Performed At Station’, ‘Performed At work center’, ‘Changed by’ (Employee Name) and ‘Changed Date & Time’.
4 Parameter Recording check:
· Task level: Parameter must be updated for the selected work unit, if the ‘Parameter Recording?’ drop-down list box is set as “Mandatory” in the “Edit Parameter Reading Requirements” page of the “Maintenance Task” business component.
· Subtask level: If the ‘Display By’ radio button is set as “Subtask”, and if the said ‘Parameter Recording?’ drop-down list box is set as “Mandatory” at subtask level, for every last sign-off of the individual sub-task#, the system updates the parameter against that subtask.
4 Task Transient Status check:
· If the Transient Status of the task is “Hold”, the entities such as ‘Status’, ‘Work Center’, ‘Start / End Date & Time’, ‘Sign-Off Status’ and ‘Atten. Type’ cannot be modified.
· If the Transient Status is not specified and hold details are available for the task, with 'Hold Status' as 'Open' as of current date & time in the “Record Work Hold” page of the “Work Monitoring & Control” business component, the status of the task cannot be changed. This is applicable only if the process parameter 'Prevent Task Status Change?' is set as "Yes" for the associated 'Hold Code', in the “Common Masters” business component.
4 Refer to “Worked Hour Computation”, “Labor Cost Calculation” and “Timesheet Status Update” sections for more details.
Sign-off details
Ø Enter the following in the “Sign-Off Details” group box:
Mechanic |
The employee code of the mechanic who performs sign-off the task / subtask. (Alphanumeric, ). The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. |
Inspector |
The employee code of the inspector who performs sign-off of the task / subtask. (Alphanumeric, ). The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. |
RII |
The code of the employee who performs RII sign-off of the task / subtask. (Alphanumeric, ). The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component. |
Skill |
Use the drop-down list box to select the code identifying the skill of the employee. The system lists the following values based on the process parameter “Allow sign-off entry by different employee” set in the “Set Process Parameter” page of the “Common Master” business component, as follows: · If the parameter is set as “Yes”, the system lists all the ‘Active’ skills defined in the “Employee Personal information” business component. · If the parameter is set as “No”, the system lists all the ‘Active’ skills mapped to the login user in the “Employee Personal information” business component. The system leaves the field blank, by default. |
Addl. Sign-Off |
The code of the employee who performs additional sign-off of the task / subtask. (Alphanumeric, ) |
Comments |
Any additional comments related to the sign-off of the task / subtask. (Alphanumeric, ) |
Note: The sign-off details cannot be modified, if a task or a subtask is already ‘Signed-Off”, ‘Void’ or ‘Reject’, and if skill # and employee code are entered in any of the ‘Mechanic’, ‘Inspector’ or ‘RII’ fields.
The system performs the following check on Sign-off, completion, void and rejection of the task:
Different Employee Sign-Off permission check:
If the user selects multiple tasks from the multiline and specifies Skill #, ensure that the employee # available in the Mechanic / Inspector / RII field is same as the employee mapped to the login user, if the following conditions are satisfied:
· If the sign-off status of the task is “Not Required” or any one of the relevant options such as "Pending Mechanic", “Pending Mechanic & Inspector", "Pending Mechanic & RII", "Pending Mechanic, Inspector & RII", "Pending Inspector", "Pending Inspector & RII", “Pending RII”.
· If the process parameter “Allow sign-off entry by different employee?" is set as "No" for the Shop Work Order Type, in the “Set Process Parameter” page of the “Common Masters” business component.
Dual Sign-Off permission check:
If the user selects multiple tasks and specifies Skill #, ensure that the same employee # is not entered in the Mechanic and inspector fields, if the following conditions are satisfied:
· If the Sign-Off status of the task is "Pending Mechanic & Inspector" or "Pending Inspector" or “Not Required”
· If the parameter “Permit Dual Sign-off by the employee?" is set as "No" for the Shop Work Type in the “Common Masters” business component.
Employee # - Skill Mapping:
If the user selects multiple tasks and specifies Skill #, ensure that for the corresponding sign-off status of the task, the employee code entered in the Mechanic / Inspector / RII field is mapped to the Skill # identified for sign-off requirement of the subtask, for the current date. The skill mapping is defined in the “Employee Personal Information” business component.
Employee # - Skill – Resource Group Mapping:
If the user selects multiple tasks and specifies Skill #, ensure that for the corresponding sign-off status of the task, the employee code entered in the Mechanic / Inspector / RII field, must have resource group “Inspector” or “Mechanic & Inspector” mapped to the Skill # for the current date in the “Employee Personal Information” business component.
Certificate / License validity check:
If the option “Approval Reqd.?” for the task is set as “Yes” in the “Edit Resource/Sign-Off Requirements” page of the “Maintenance Task” business component, the system considers that the employee possesses valid Certificate or License for the sign-off of the task, only if the following conditions are satisfied:
· The Certificate # / License # must be mapped to the Employee # and Skill # available for the task / sub task, as defined in the “Employee Personal Information” business component.
· Certificate # / License # must be valid for the current date.
· The task # must be identified as Work Unit effectivity for the Certificate # / License #.
Ø Click the “Sign-Off” pushbutton to perform sign-off of the task.
The system ensures the following on clicking the “Sign-Off” pushbutton:
4 The employee must be assigned to the service area of the work center.
4 The task cannot be signed-off, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order, with the process parameter “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” in the “Common Master” buisness component.
4 The system does not allow sign-off of the task, if one of the following conditions is true:
· If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
· If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the “Common Master” business component.
4 If the process parameter “End Running Clock Bookings automatically?” (Is this the option? Given as Stop Direct Clock Booking" in FID 62.) is set as “Yes” for the associated ‘Hold Code’ in the Common Masters business component.
4 Refer to “Worked Hour Computation”, “Labor Cost Calculation” and “Timesheet Status Update” sections for more details.
Ø Click the “Void” pushbutton to void the task.
The system ensures the following on clicking the “Void” pushbutton:
4 The employee must be assigned to the service area of the work center.
4 The task cannot be void, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order, with the process parameter “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” in the “Common Master” buisness component.
4 The system does not allow void of the task, if one of the following conditions is true:
· If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
· If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the “Common Master” business component.
4 Refer to “Worked Hour Computation”, “Labor Cost Calculation” and “Timesheet Status Update” sections for more details.
Ø Click the “Reject Task” pushbutton to reject the task.
4 The task cannot be rejected, if the task and the work order are changed to “In-Progress’ status and if the main core is not issued to work order, with the process parameter “Prevent Order Exec. with Main Core Not Issued”? set as “Yes” in the “Common Master” buisness component.
4 The system does not allow rejection of the task, if one of the following conditions is true:
· If the Transient Status of the task is “Hold” in the “Work Monitoring and Control” business component.
· If the Transient Status is not specified, if the ‘Hold Status’ is set as “Open” in the “Work Monitoring and Control” business component, and if the process parameter “Prevent Time booking?” is set as “Yes” for the associated ‘Hold Code’ in the “Common Master” business component.
4 Refer to “Worked Hour Computation”, “Labor Cost Calculation” and “Timesheet Status Update” sections for more details.
In-direct details
Ø Enter the following in the “In-Direct Details” group box:
In-Direct Cat. |
Use the drop-down list box to select the quick codes defined for the type “In-Direct Category” in the current business component. The system leaves the field blank, by default. |
Start Date / Time |
The date and time at which the clock is started for recording the indirect work hour details for the employee. (Date & Time Format). If the process parameter “Employee Time Sheet Update Mode” is set as “Manual” in the “Set Process Parameter” page of the “Common Master” business component, the start date and time must be entered and must be earlier than or equal to the current date and time. The difference of days between the server date and time and the start date and time must be earlier than or equal to the value of the “Backdated reporting Time Limit (in days)” defined in the “Set Process Parameter” page of the “Common Master” business component. |
End Date / Time |
The date and time at which the clock is stopped for terminating the indirect work hour reporting. (Date & Time Format). If the process parameter “Employee Time Sheet Update Mode” is set as “Manual” in the “Set Process Parameter” page of the “Common Master” business component, the end date and time must be entered and must be earlier than or equal to the current date and time. The difference of days between the server date and time and the end date and time must be earlier than or equal to the value of the “Backdated reporting Time Limit (in days)” defined in the “Set Process Parameter” page of the “Common Master” business component. |
Note: If an employee’s leave is in “Approved” status during the period of ‘Start Date & Time’ and ‘End Date & Time’ entered, the system does not allow the employee to record the timesheet for the ‘Start Date & Time’ and ‘End Date & Time’.
Example:(Pop-up)
a. Consider that an employee has taken leave from 10-Feb-2011 to 12-Feb-2011. If the timesheet is recorded from 9-Feb-2011 to 14-Feb-2011, system does not allow this operation. He can split this into two records i.e. assignment-1 will be from 9-Feb-2011 to 9-Feb-2011 and assignment-2 will be from 13-Feb-2011 to 14-Feb-2011.
b. Consider that the employee has taken leave from 10-Feb-2011, 12:30 AM to 10-Feb-2011, 04:00 PM. If timesheet is recorded from 10-Feb-2011, 07:30 AM to 10-Feb-2011, 04:00 PM, the system does allow this operation.
Ø Click the “Clock On” pushbutton to start the clock for recording in-direct working hours of the employee.
Ø Click the “Clock Off” pushbutton to stop the clock for terminating the indirect work hour reporting.
The login user must be mapped to an employee, and the mapping must be valid for the current date and time.
The employee is not allowed to book in-direct hours against any ‘In-Direct Category’, if in-direct hours have been already booked for that period against any other ‘In-Direct Category’.
The worked hours for each task is computed based on the number of tasks the employee has simultaneously worked on.
Worked Hour calculation:
· If the employee has worked on only one task for the given date and time range, the difference between the 'End Date & Time' and 'Start Date & time' is calculated as the “Worked Hours.
· If employee has reported any indirect hours, the indirect hours is determined as Indirect hours = Indirect End date/time - Indirect Start date/time
· If 'break hours' are specified between the entered date and time range, for the work center on which the SWO / task is created, the system calculates the ‘Actual Work Duration’ as follows:
Actual Work Duration = (End Date / Time - start Date/ Time)-Indirect Hours- Break Hours.
Worked Hour apportion logic:
· If employee has simultaneously worked on more than one task, the total duration spent (after excluding break and indirect hours, if they are falling in the same range) must be apportioned to each task, depending on the estimated elapsed time identified for each task.
Ø Click the “Reset” pushbutton to reset the clock.
Receive part details
Ø Enter the following in the “Receive Part” group box:
Primary Work Center # |
Use the drop-down list box to specify the primary work center in which the work order is executed. The system lists the values based on the process parameter “Allow Task Reporting by?” set in the “Set Process Parameter” page of the “Common Master” business component, as follows: · If the parameter “Allow Task Reporting by?” is set as “All Employee”, the system lists all the work centers that are in ‘Active’ status. · If the said parameter is set as “Assigned Employee”, the system lists all the ‘Active’ work centers to which the login user has access privilege from the “Work Center” business component. Note: In either cases above, the ‘Execution Capability’ of the work center must be set as “All” or “Shop” and ‘Work center Class’ must be set as “Execution” in the “Work Center” business component. The system leaves the field blank, by default. |
Ø Click the “Ack. Receipt” pushbutton to acknowledge the receipt of parts.
The system performs the following on clicking the pushbutton above:
4 If the process parameter “Enforce Acknowledge Receipt?” is set as “Yes” in the “Common Master” business component, for a part #-serial # combination associated to the task selected multiline, ensure that the ‘Routing Status’ of the part is other than "Pending Movement".
4 If the process parameter “Enforce Acknowledge Receipt?” is set as “No”, for a part #-serial # combination associated to the task selected in the multiline, if the ‘Routing Status’ of the part is "Moved", the system updates the 'Routing Status' as "Received".
4 If the process parameter “Enforce Acknowledge Receipt?” is set as “Force Receipt”, for a part #-serial # combination associated to the task selected in the multiline, if the ‘Routing Status’ is either "Pending Movement" or 'Received” at a workcenter other that the workcenter specified in the multiline, the system updates the 'Routing status' as “Force Routed”.
Task Hold / Release details
Ø Enter the following in the “Hold / Release Details” group box:
Hold Code |
Use the drop-down list box and select the hold code associated to the ’hold’ of the task. Mandatory. The system lists all the ‘Active’ hold codes for which the “Initiation Level” is set as “Execution” in the “Set Process Parameters” page of the “Common Master” business component. The system leaves the field blank, by default. |
Comments |
Any comments related to the tasks that are on hold. (Alphanumeric, 20). Mandatory. |
Ø Click the “Hold” pushbutton to hold the task.
The system performs the following on clicking the “Hold” pushbutton:
4 Ensures that the employee is assigned to the service area of the work center.
4 Updates the hold details only for those tasks that are in “Planned” and “In-Progress” statuses.
4 Updates the Transient Status of the task as “Hold”, if the process parameter “Stop Shop Work Order Execution” is set as “Yes” for the associated ‘Hold Code’ in the “Common Master” buisness component.
4 If the ‘Clock Info.’ is “Clock-Direct” or “Manual-Direct” and if the task is put on hold, the system performs the following:
· Ends the clock.
· Updates the current date and time as ‘End Date & Time’.
· Updates the ‘Clock Info.’ as “Not Started”.
Ø Click the “Release” pushbutton to release the held task.
The system ensures the following on clicking the “Release” pushbutton:
4 The task cannot be released if the Transient Status of the task is not specified, and if the ‘Hold Status’ is “Closed” for the ‘Hold Code’ selected.
4 The employee must be assigned to the service area of the work center.
Ø Click the “Record Work Hold” link to hold or release the task.
The system displays the following:
Message Center |
All error and success messages for all the validations. |
Report Findings
Hlpsworecshpexe_sworecshpexemn_reportfindings.htm
In this tab page, you can record observations and discrepancies that are found during execution of tasks. Any observation made during the execution of task and the discrepancies reported by the mechanic against the task, can be recorded. Observations, generally do not have impact on the maintenance operations. But the discrepancies affect the maintenance operations, hence a corrective action need to the specified to resolve the discrepancies reported against a task. You can perform the following using this tab:
4 You can update the observation and discrepancy details during execution of the task.
4 You can specify the reference task against which the discrepancy is reported.
4 You can specify the corrective action to be taken to resolve the discrepancy.
4 You can record new observations and discrepancies in a shop work order.
4 You can specify the part disposition details.
4 You can specify the estimated / actual start date and end date for a discrepancy.
4 You can also transfer the discrepancy from one component to another, by specifying the part number and serial number details.
Ø Select the “Report Findings” tab in the “Record Shop Execution Details” page.
A tree structure is displayed in the left pane, with “Shop Work Order” as the parent node, “SWO #” as the first-level node and the following second-level nodes:
1. Observation: The system displays the observations recorded in the SWO # in this node.
2. Discrepancy: Discrepancies reported against the task in the SWO # are displayed in this node. The system displays the following values under this node.
a. Under Resolution: Discrepancies available in “Under Resolution” status are displayed here.
b. Cancelled: Discrepancies available in “Cancelled” status are displayed here.
c. Closed: Discrepancies available in “Closed” status are displayed here.
d. Transferred: Discrepancies available in “Transferred” status are displayed here.
e. No Fault Found: Discrepancies available in “No Fault Found” status are displayed here.
3. Unprocessed Discrepancies: Any unprocessed discrepancies which are in “Pending” status during closure of the work order, are displayed under node.
The tree structure is as follows:
Tree Structure:
- Shop Work Order
- SWO #1
- Observation
<ATA #>:: <Desc>:: <Source Task #>
- Discrepancy
- Under Resolution
ATA # :: Log Item # :: Disc. Desc. :: Source Task
+ Closed
+ Transferred
+ No Fault Found
+ Cancelled
+ Unprocessed Discrepancies
- SWO #2
- SWO #3
On clicking “Go”
When a value e.g. “Part # / Serial” # is selected in the ‘Search On’ drop-down list box, and a part number and a serial number are entered in the editable boxes provided alongside, on invoking “Go”, the system performs the following:
a. The system retrieves refreshes the “Report Findings” tree and retrieves and displays all the shop work orders belonging to the entered part # / serial # combination in the tree.
b. On clicking the SWO # in the tree, the tree is expanded to display all the available observations and discrepancies in shop work order, as child nodes. The selected node is highlighted is the tree.
On clicking a node in the “Report Findings” tree:
When you select the “Observation” / “Discrepancy” node in tree, the system performs the following:
· Retrieves and displays the details of the shop work order to which the selected observation / discrepancy belong, in the “Execution Details” and “Main Core Details” group boxes.
· Enables the corresponding observation / discrepancy radio button.
· Displays the observation / discrepancy details in the respective sections.
Execution details
In the right pane, the system displays the following in the “Execution Details” group box:
SWO # |
The number identifying the shop work order for which the observation / discrepancy details are retrieved. |
Event ID # |
The event number identified for grouping the shop work order. |
Primary Work Center |
The primary work center in which the shop work order is executed. |
Status |
The status of the shop work order, which could be “Planned”, “In-Progress” or “Completed”. |
Job Type |
The job type of the shop work order, which can be “Component”, “Piece Part”, “Facility”, “Engine”, “Make”, “Project” and “Miscellaneous”. |
Main Core details
The system displays the following in the “Main Core Details” group box:
Part # |
The code identifying the part for which the observation / discrepancy details are recorded. |
Serial # |
The serial number of the part. |
Mfr. Part # |
The number assigned to the part, by the manufacturer of the part. |
Mfr # |
The code identifying the manufacturer of the part. |
Lot # |
The lot number of the part. |
Qty. |
The quantity of the part. |
Mfg. Serial # |
The serial number issued by the manufacturer of the part. |
Mfg. Lot # |
The lot number issued by the manufacturer of the part. |
Facility Object # |
The code identifying the facility object. A facility object refers to a facility that is already defined in the Work Center business component or a part that is already defined in the “Part Administration” business component. (Pop-up) |
Facility # |
The code identifying the facility. A facility is a tool or equipment used to execute maintenance jobs on aircraft and aircraft-related components. |
Description |
The textual description of the facility. |
Component # |
The code identifying the component to which the part belongs. |
Multiple Cores? |
Indicates whether multiple parts are associated to the same work order. The system displays the options “Yes” or “No”. |
Main Core Status |
The status of the main core component, which could be “Not Applicable”, “Pending Issue”, “Issued”, “Ext. Routed”, “Ext. Routed BER” or “Ext. Routed Exchange”. |
Part Disposition
Ø Enter the following fields:
Final Rep. Disp? |
Use the drop-down list box to specify the type of the repair work to be performed on the component, after work order generation. The system lists the following values: · Exchange – Select this option to specify that the component needs to be exchanged. · Missing – Select this option to specify that the component is not available for execution of the work order. · Repair – Select this option to specify that the component needs to be repaired. · Replace – Select this option to specify that the component needs to be replaced. By default, the system displays “Exchange”. |
Disposition Remarks |
Any additional comments related to disposition. (Alphanumeric, 2000). |
NFF? |
Use the drop-down list box to specify whether any fault is found during inspection of the part. The system lists the values “Yes” and “No”. By default, the system displays “No”. |
The system displays the following field:
BER? |
Indicates whether the servicing of the component is beyond economic repair (BER) or not. The system displays “Yes” or “No”. |
Ø Enter the following field:
Findings Summary |
Any comments or summary related to the work order. (Alphanumeric, 2000). |
Report Findings
Ø In the “Report Findings” section, select one of the following radio buttons:
Observation |
Select this radio button to record the observation details. If you select this button, only the “Observation” group box is visible. The other sections in the “Report Findings” group become disabled. |
Discrepancy |
Select this radio button to record the discrepancy details. If you select this button, the “Observation” group box is disabled and all the other sections are enabled. |
Ø Enter the following fields:
Reference Task # |
The code identifying the task against which the discrepancy is reported. (Alphanumeric, 20). The task number entered here must be ‘Active’ as defined in the “Maintenance Task” business component, and must be in status “Planned”, “In-Progress” and “Completed”. Ensure that the task entered here belongs to the shop work order selected in the tree. Help facility available. |
Observation details
In the “Report Findings” section, the “Observation” group box is enabled only if the “Observation” radio button is selected.
Ø Enter the following fields in the “Observation” group box:
Description |
The textual description of the observation recorded. (Alphanumeric, 2000). Mandatory. |
Reported by |
The employee code of the user who reported the observation. (Alphanumeric, 20). The employee code entered here must be valid as defined in the “Employee Personal Information” business component. The employee entered must be mapped to the login user, If the parameter “Allow Task Reporting by?” is set as “Assigned Employee” in the “Set Process Parameter” page of the “Common Master” business component. Help facility available. |
Date & Time |
The date and time at which the observation was reported (Date & Time Format). This field must not be left blank, if the date and time is not specified in the header. The date and time entered must be earlier than or equal to the current date and time. |
The system displays the following fields:
Discrepancy # |
The code identifying the discrepancy reported on the aircraft. |
Record Status |
The current record status of the discrepancy is displayed here. The possible statuses are “Under Resolution”, “Closed”, “Transferred”, “No Fault Found” and “Cancelled”. |
Sign-Off Status |
The sing-off status of the task associated to the discrepancy, which could be “Not Required”, “Pending Mechanic”, “Pending Inspector”, “Pending Mechanic & Inspector” or “Signed-Off”. |
Discrepancy details
In the “Report Findings” section, the “Discrepancy” group box is enabled if the “Discrepancy” radio button is selected. You can enter the following in this group box:
Description |
The textual description of the discrepancy. (Alphanumeric, 2000). Mandatory. |
Type |
Use the drop-down list box to select the type of discrepancy that has been reported on the aircraft, The system lists the following values: · PIREP – Select this option to indicate that the discrepancies are reported by the pilot. · MIREP – refers to the discrepancies reported by the mechanics. · Non-Routine - refers to the non-routine discrepancies reported by the mechanics. The system displays “MIREP”, by default. |
ATA # |
The ATA chapter on which the discrepancy is reported (Alphanumeric, 16). Mandatory. The ATA chapter must 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. |
Action |
Use the drop-down list box to specify the action taken against the discrepancy. The system lists the following values: · Closed – Select this option to indicate that the discrepancy is closed. · Part Change Closed – Select this option to indicate that the discrepancy is closed by performing the part change and transferred to the Part –Serial # combination. · No fault Found – Select this option to specify that no fault is found against the discrepancy. · Cancelled – Select this option to specify that the discrepancy is cancelled. The system leaves the field blank, by default. This field must be left blank, while recording a new discrepancy. While recording observations and discrepancies, the above values can be selected, only if the following statements are true: · The status of the discrepancy is “Under Resolution”. · The process parameter “Enforce Excess / Core Returns?” is set as “Yes” for the “Shop Work Order Type” in the “Common Master” business component. · If 'Pending Return Qty.' or 'Pending Return Qty. - Core' of the part is greater than zero for the Shop Work Order # - Task # combination, in the “Parts Consumptions Details” page of the current business component, |
Reported by |
The employee code of the user who reported the discrepancy. (Alphanumeric, 40). Mandatory. The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component, if the parameter “Allow Task Reporting by?” is set as “Assigned Employee” in the “Common Master” business component. Help facility available. |
Date & Time |
The date on which the discrepancy was reported (Date & Time Format). This field must not be left blank, if the date and time is not specified in the header. The date and time entered must be earlier than or equal to the current date and time. |
Reference # |
The reference number of the discrepancy. (Alphanumeric, 20). |
Corrective action details
In the “Report Findings” section, under the “Corrective Action” group box,
Ø Click the “New” icon to record the new corrective action details.
Ø
Click the “” icon to view the details of
the previous corrective action.
Ø
Click the “” icon to view the details of
the next corrective action.
Ø Enter the following fields:
Corrective Action |
A description of the corrective action to be taken, to resolve the discrepancy (Alphanumeric, 2000). Ensure that at least one corrective action is available. Corrective action must be specified, if the ‘Action’ is set as “Closed”, “Part Change Closed” or “No Fault Found”. |
Ø Select the “View All” link to
Date & Time |
The date and time at which the corrective action was reported. (Date & Time Format). Mandatory. The date and time which is earlier than or equal to the current date and time, must be entered in this field, if a corrective action is entered and if the date and time is not specified in the header.
|
Reported by |
The employee code of the user who reported the corrective action. (Alphanumeric, 40). Mandatory. The employee code entered here must be in “Active” status as defined in the “Employee Personal Information” business component, if the parameter “Allow Task Reporting by?” is set as “Assigned Employee” in the “Common Master” business component. This field must not be left blank, if the employee is not mapped to the login user. Help facility available. |
Repair Task # |
The code identifying the task that needs to be executed to rectify the discrepancy. (Alphanumeric, 30). The task number entered here must be ‘Active’ as defined in the “Maintenance Task” business component. Help facility available. |
Sing-off details
In the “Report Findings” section, enter the following fields under the “Sign-off” group box:
Mechanic |
Check the box, to indicate that the task require mechanic sign-off. Enter the employee code of the mechanic in the editable field provided alongside. (Alphanumeric, 30). The employee code entered here must be in “Active” status and mapped with the resource group “Mechanic” for at least one skill in the “Employee Personal Information” business component. The mapping must be effective for the current date. An employee code must be specified for the mechanic, if the following are true: · If the ‘Mechanic’ check box is checked. · If either ‘Inspector’ or ‘RII’ check box is checked, with respective employee code available. |
Inspector |
Check the box, to indicate that the task require inspector sign-off. Enter the employee code of the inspector in the editable field provided alongside. (Alphanumeric, 30). The employee code entered here must be in “Active” status and mapped with the resource group “Inspector” for at least one skill in the “Employee Personal Information” business component. The mapping must be effective for the current date. An employee code must be specified for the inspector, if the following are true: · If both the ‘Inspector’ and ‘RII’ check boxes are checked. · Employee code is available for RII. |
RII |
Check the box, to indicate that the task require RII sign-off. Enter the code of the employee who performs RII sign-off in the editable field provided alongside. (Alphanumeric, 30). The employee code entered here must be “Active” status and mapped with the resource group “Inspector” for at least one skill in the “Employee Personal Information” business component. The mapping must be effective for the current date. |
Addl Sign-Off |
The code identifying the employee who performs additional sign-off. (Alphanumeric, 255). |
Remarks |
Any additional comments related to the sign-off of the task. (Alphanumeric, 2000) |
Different Employee Sign-Off permission check:
Ensure that the employee # available in the Mechanic / Inspector / RII editable field is same as the employee mapped to the login user, if the corresponding boxes are checked and if the process parameter “Allow sign-off entry by different employee?" is set as "No" for the Shop Work Order Type, in the “Set Process Parameter” page of the “Common Masters” business component.
Dual Sign-Off permission check:
The same employee # must not be not entered in more than one editable fields (i.e. Mechanic, inspector and RII fields), if the parameter “Permit Dual Sign-off by the employee?" is set as "No" for the Shop Work Type in the “Common Masters” business component.
Estimation details
In the “Report Findings” section, enter the following fields under the “Estimates” group box:
Start |
The estimated start date and time for the execution of the task against the discrepancy. (Date & Time Format). |
End |
The estimated end date and time for the execution of the task against the discrepancy. (Date & Time Format). |
Est. Man Hrs. |
The man hours estimated to complete the task against the discrepancy. A positive integer is entered here. |
Actual details
In the “Report Findings” section, enter the following fields under the “Actual” group box:
Start |
The estimated start date and time for the execution of the task against the discrepancy. (Date & Time Format). The date and time entered must be less than or equal to current date and time. The actual start date and time must be entered, if the 'Action' is set to any value, and 'Date & Time' in the header is not available or if it is available, but greater than current date & time. |
End |
The estimated end date and time for the execution of the task against the discrepancy. (Date & Time Format). The date and time entered here must be equal to or later than the “Start” date and time, and less than or equal to current date and time. |
Man Hrs. |
The man hours estimated to complete the task against the discrepancy. A positive integer is entered here. |
File Name |
The name of the file related to the execution of the task. (Alphanumeric, 2000). Help facility available. |
Ø Click the “View File” link to view the details of the attached file.
Transfer details
The “Transfer Details” will display the following fields for you to enter on selecting “Part Change Close” as the “Action”.
Part # |
The code identifying the part to which the discrepancy has to be transferred. (Alphanumeric, 40). The part number if entered, must be a valid part with ‘Reference Status’ defined as “Active” in the “Part Administration” business component. The part number must be entered here if following conditions are satisfied: · if the parameter “Enable Manufacturer Part # control in transaction” for the Category ‘Manufacturer Part’ is set as “No” in the “Set Inventory Process Parameters” activity of the “Logistics Common Master” business component. · ‘Action’ is set as “Part Change Close”. · Component # is not specified. Help facility available. |
Serial # |
The serial number of the part to which the discrepancy has to be transferred. (Alphanumeric, 40). The serial number must be entered, if component number is not provided. The serial number entered must be valid for the part number entered and the part # - serial # combination must be in ‘Active’ as defined in the “Aircraft” business component. Help facility available. |
Mfr. Part # |
The number assigned to the part, by the manufacturer of the part. (Alphanumeric, 40). The manufacturer part number if entered, must be a valid part with ‘Reference Status’ defined as “Active” in the “Part Administration” business component. The manufacturer part number must be entered here if following conditions are satisfied: · if the parameter “Enable Manufacturer Part # control in transaction” for the Category ‘Manufacturer Part’ is set as “Yes” in the “Logistics Common Master” business component. · Component # is not specified. Help facility available. |
Serial # |
The serial number issued by the manufacturer of the part. (Alphanumeric, 40). The serial number must be entered if component number is not provided. The serial number entered must be valid for the part number that corresponds to the Manufacturer Part # - Manufacturer # combination, and this part # - serial # combination must be in ‘Active’ as defined in the “Aircraft” business component. Help facility available. |
Comp # |
The code identifying the component to which the part belongs. (Alphanumeric, 40). The component number entered must be in ‘Active’ status as defined in the “Aircraft” business component. The component number entered must be same as the component number that corresponds to the entered part # - serial # combination and available in the “Aircraft” business component. Help facility available. |
Ø Click the “New Findings” pushbutton to record new observations and discrepancies for the shop work order.
Ø Click the “Update Findings” pushbutton to update the observation and discrepancies.
The system performs the following on clicking the pushbutton above:
4 Updates the record status of the discrepancy as “Under Resolution” if the “Action” is not specified.
4 On recording a new discrepancy,
· if a “Corrective Action” is not specified for discrepancy in the “Corective Action” section, the system saves the discrepancy without any corrective action and displays the ‘Sign-off Status’ as “Not Required”.
· if a “Corrective Action” is specified, the system saves the description along with “Reported by”, “Date & Time”, 'Repair Task#' (if provided) against that discrepancy, and copies the sign-off requirements, based on the value of process parameter “Default Sign-off requirement for Non-Routines” for a 'Shop Work Order' type in the “Common Master” business component.
4 Updates the Record Status of the discrepancy from “Under Resolution” to “Closed”, “Transferred”, “No Fault Found” and “Cancelled” when ‘Action’ is changed to “Closed”, “Part Change Closed”, “No Fault Found” and “Cancelled”, respectively.
To proceed carry out the following:
Ø Select the “Edit Discrepancy Addl. Info.” link at the bottom of the page to modify the task / discrepancy details.
Ø Select the “Upload Documents” link to upload the documents.
Refer to the “Object Attachments” online help for more details.
Ø Select the “View Associated Doc. Attachments” link in the ‘main links’ section to view the associated document attachments.
Refer to the “Object Attachments” online help for more details.
Ø Select the “Review Discrepancy History” link to view the discrepancy details.
Refer to the “Discrepancy Processing” online help for more details.
Ø Select the “Create Eng. Service Request” link to create an engineering service request.
Refer to “Engineering Service Request” online help for more details.
The system displays the following:
Message Center |
All error and success messages for the validations. |
[k1]This section will be completed later