Recording work actual details
You can record the actual work execution details of the task in this tab page. Using this tab, you can perform the following:
You can book timesheet against the tasks.
You can perform Mechanic / Inspector / RII sign-off of the task. You can void / reject tasks as well.
You can book timesheet for in-direct hours like ‘Meeting’.
You can pre-close and complete the tasks.
Acknowledge the receipt of moved parts.
Hold tasks or release the tasks which are 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.
On page launch “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 / discrepancy status as the child nodes. The tree displays all the shop work orders and the associated tasks / discrepancies, 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 / discrepancies for which the employee mapped to the login user, has clock running for at least one task / discrepancy.
If the parameter is set as “Assigned Employee”, the tree displays all the shop work orders with only the tasks / discrepancies for which the employee mapped to the login user, has clock running and only the tasks / discrepancies for which the employee is assigned.
If the process parameter ‘Hierarchical display of Root, Intermediate and Leaf level tasks in Tree in RSED screen?’ under the entity type 'Shop Work Order Type' for the entity ‘All Work Order’ is ‘Not Required’, the tree structure in the left pane of the 'Record Shop Execution Details' page displays only Operational tasks of retrieved shop work orders. Illustration next.
Tree Structure:
[-] Shop Work Order
[-] CWO-xxxxx-xxxx
[-] Task
[-] Planned
[] Operational 5
[-] In-Progress
[] Operational 1
[] Operational 2
[] Operational 3
[-] Completed
[] Operational 4
The work order tree displays the context work order alone expanded till the leaf level. The other work orders, if applicable, are not expanded. Task / Discrepancy nodes in tree are displayed in different colors as given below:
If the task / discrepancy is assigned to the employee mapped to the login user, then the task / discrepancy is displayed in 'Brown' color.
If for the task / discrepancy, clock is started by the employee mapped to the login user, then the task / discrepancy is displayed in 'Blue' color.
If for the task, clock has been ended by the employee mapped to the login user, then the task / discrepancy is displayed in 'Dark green' color.
If the process parameter ‘Hierarchical display of Root, Intermediate and Leaf level tasks in Tree in RSED screen?’ under the entity type 'Shop Work Order Type' for the entity ‘All Work Order’ is ‘Required’, the tree structure in the left pane of the 'Record Shop Execution Details' page displays three levels of grouping: Root, Intermediate and Operational tasks. These tasks are in turn segregated planning status-wise: Planned, In-Progress and Completed. Illustration follows.
Tree Structure
[-] ShopWorkOrder
[-] CWO-xxxxx-xxxx
[-] Task
[-] Planned
[ ] Root_Task_1
[ ] Intermediate_Task_2
[ ] Operational Task 1
[ ] Operational Task 2
[ ] Intermediate_Task_3
[ ] Operational Task 4
[-] In-Progress
[ ] Root_Task_1
[ ] Intermediate_Task_2
[ ] Operational Task 3
[ ] Root_Task_2
[ ] Intermediate_Task_4
[ ] Operational Task 5
[ ] Operational Task 6
[-] Completed
[ ] Root_Task_3
[ ] Intermediate_Task_5
[ ] Operational Task 7
[ ] Operational Task 8
[ ] Operational Task 9
Note: The Root or Intermediate tasks can appear under one or more nodes in the tree (Planned, In-progress and Completed) depending upon the status of the operational tasks.
Tree Search:
You can perform various operations like expanding nodes in the tree, collapsing the nodes and other search operations, using various icons displayed in the left pane. These icons are explained in the table:
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:
The system refreshes the tree and retrieves and displays all the shop work orders belonging to the entered part # / serial # combination in the tree.
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.
Display By
In the right pane, select one of the following radio buttons above the multiline:
Display By |
Indicates whether the tasks are displayed at task level or subtask level. The system displays the following radio buttons for you select:
|
Transfer of task details
Click the '’
icon to transfer the task / discrepancy details from the “Work Actual”
tree to the multiline.
Check the following box above the tree:
Append |
Check this box to transfer the selected records from the tree to the multiline. If this box is not checked, the system clears the existing records (only the tasks/Discrepancies for which clock is not On) from the multiline and transfers the selected records from the tree to the multiline. |
Retrieval of task details in the multiline
The system displays the following fields in the “Task Details” multiline:
Note: If the “Record Shop Execution Details” screen is launched with a context work order reference or if only one work order is fetched in the tree, all the tasks and discrepancies retrieved in the tree under the work order are transferred and displayed in the multiline.
This happens only if the process parameter "Auto-populate task details in work actual tab on search" is set as "Yes" in the “Common Master” business component.
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 one of the following values:
|
CI (Clock Info) |
The clock information of the task, which could be one of the following:
|
SS (Sign-Off Status) |
The sign-off status of the task, which could be one of the following:
|
ES |
The estimation status of the task, which could be one of the following:
|
Enter the following fields:
SWO # |
The code identifying the shop work order for which the details are retrieved. 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 in the context shop work order. (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. You must enter the task number, if the sequence number is not entered for the shop work order. The task number entered must be available in the shop work order number in the multiline, and the status of the task must be in status other than "Fresh", “Cancelled”, "Duplicate", “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.
Clock Start Date & Time |
The start date and time of execution of the task as in the time zone of the work center and station defined for the task. (Date & Time Format). It operates based on the value set for the process parameter “Employee Time Sheet Update Mode” in the “Set Process Parameters” page of the “Common Master” business component, as follows:
If entered manually, the difference of days between the time zone 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 clock on if indirect timesheet clock is running for you. The start date and time entered must be same for all the sub tasks belongs to a task, during start / reset of clock. |
Clock End Date & Time |
The end date and time of execution of the task as in the time zone of the work center and station defined for the task. (Date & Time Format).
The end date and time must be later than or equal to the start date and time. The end date and time entered must be same for all the sub tasks belongs to a task, during clock-off / completion / sign-of / rejection / void of task. The “End Date & Time” must be entered, if status of the task is changed to “Completed” or “Pre-Closed”. Both “Start Date & Time” and “End Date & Time” must be entered, if the status of the task is changed from “Planned” to “Completed” / “Pre-Closed”. |
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
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, if Component Interaction Model (CIM) interaction does not exist between “Time Management” and “Shop Work Order” business components. If CIM interaction exists between “Time Management” and “Shop Work Order” business components, the system lists “Normal” along with all the ‘Active’ values defined for the quick code “Attendance Type” in the “Time Management Master” business component. The system displays “Normal”, by default. |
Employee Comments |
Any comments entered by the employee, regarding timesheet booking. |
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 Repair Classification selected must be same for all the subtasks belonging to a task. On clicking “Clock On”, “Clock Off”, “Reset”, “Complete”, “Sign-off”, “Reject” and “Void” pushbuttons, the system performs the following when Repair Classification is modified for a task / subtask:
The system leaves the field blank, by default. |
Execution Comments |
Any comments entered by the employee, regarding execution of the task. |
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. |
Skill |
The skill that is required for the sign-offs that are pending on the task. Skill is displayed along with Resource Group of the pending Sign-Off requirements. |
Note: The system displays the “Sub-Task Desc”. and “Skill” fields along with relevant details and respective sign-off status in the multiline, only if the ‘Subtask’ radio button is selected. |
|
Maint. Manual Ref. # |
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 execution 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 in which the task is executed. |
Other Logons |
The employee # of all the employees who have clock running for the same task are displayed, separated by ‘colon’. |
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 component on which the task is executed. |
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 the root task of the context 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:
|
Location |
The information identifying the location of the part. |
The system displays the following fields:
Customer Order # |
The unique code identifying the customer order associated to the shop work order. |
Customer # |
The customer code associated to the shop work order. |
Exchange Order # |
The exchange order number applicable to the shop work order if the shop work order is initiating document of the exchange order. |
Final Movement |
The location where the main core of the shop work order must be returned after the entire work is completed. The system displays one of the following options concatenated with the location (i.e. Work Center # / Warehouse #) to which the main core is to be returned:
|
Prom. Del. Date |
The promised delivery date in the customer order. |
Request / Issue Status |
Indicates the material planning status for the task. The system displays one of the following values:
If more than one planning status exists for a task, the system displays the lowest in the hierarchy. For example, if for a task, material has been 'Requested' and if the material has been 'Partially Issued', the system displays the material planning status as “Partially Issued”. |
Note: Ensure that at least one record is selected in the multiline.
Timesheet details
In the “Timesheet” group box, you can perform the following:
Click the “Clock On” pushbutton to start the clock on the task.
The system ensures the following on clicking the “Clock On” pushbutton:
The employee must be assigned to the service area of the work center.
The clock cannot be started, 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” business component.
The clock cannot be started for the task belonging to the shop work order, 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.
The execution status of a task / shop work order can be changed from “Completed” to “In-Progress”, if the process parameter 'Allow re-opening of completed orders / tasks?' is set as “Allowed” for the individual SWO Type in the “Common Master” business component. This happens only if the following conditions are satisfied:
Internal work order:
Part # / Serial # change has not happened in the work order.
“Job Type’ of the Shop Work Order must be other than “Make”.
External work order:
Invoice is not raised against that work order #.
Part # / Serial # change has not happened in the work order.
“Job Type’ of the Shop Work Order must be other than “Make”.
Timesheet reporting on a discrepancy is allowed, only if the process parameter 'Allow time reporting on discrepancies?' is set as 'Allowed' for individual SWO types.
Sequence Control check:
During “Clock on” of a task, if the Part # / Mfr. Part # - Mfr. Part # and the Task are available in the same “Seq Control #”, the system allows clock-on based on the values selected in the 'Seq. Control?' drop-down list box in the “Manage Unified Task Sequence” page of the “Maintenance Task” business component. See table.
Refer to the topics "Task Status Modification", "Acknowledge Receipt" for more details.
Click the “Clock Off” pushbutton to stop the running clock.
The system ensures the following on clicking the “Clock Off” pushbutton:
The clock cannot be stopped for the task belonging to the shop work order, 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 Masters business component.
The execution status of a task / shop work order can be changed from “Completed” to “In-Progress”, if the process parameter 'Allow re-opening of completed orders / tasks?' is set as “Allowed” for the individual SWO Type in the “Common Master” business component. This happens only if the following conditions are satisfied:
Internal work order:
Part # / Serial # change has not happened in the work order.
“Job Type’ of the Shop Work Order must be other than “Make”.
External work order:
Invoice is not raised against that work order #.
Part # / Serial # change has not happened in the work order.
“Job Type’ of the Shop Work Order must be other than “Make”.
Timesheet reporting on a discrepancy is allowed, only if the process parameter 'Allow time reporting on discrepancies?' is set as 'Allowed' for individual SWO types.
On successful end of the clock, if timesheet entry exists for an employee, the system updates the cost center in the Employee Actuals details, if the Accounting Process Parameter ‘Cost Center basis for Resource Adjustment is set as 'Base CC'’ in the “Set Options” activity of the “Account Group” business component.
Note: The employee cost center is derived from the Department-Cost Center mapping defined for an employee in the “Organization Structure” business component.
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 checks 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 "Confirmed". The booked timesheet have to be authorized through ‘Work Monitoring and Control’ business component.
Note: Modifications cannot be done to the timesheet records that are in ‘Authorized’ status.
When timesheet is reported for a task, during end of the clock, the system determines the Skill of the reporting employee for the particular timesheet record as shown is the table below:
Sign-Off status of Task |
Skill determination for timehseet |
|
Not Signed-Off |
‘Primary Skill’ mapped to the reported employee is considered for timesheet. |
|
Signed-Off |
Without selection of specific skill |
‘Primary Skill’ mapped to the reported employee is considered for timesheet. |
With selection of a specific Skill |
Selected skill is considered. |
|
With different Skills selected for different Sub-Tasks |
Skill selected for the last Sub-Task is considered. |
Sequence Control check:
If the ‘Timesheet Update Mode’ is “Manual”, and if ‘Start Date & Time’ and ‘End Date & Time’ are manually provided, then system checks sequence control as follows::
During “Clock off”, if the Part # / Mfr. Part # - Mfr. Part # and the Task are available in the same “Seq Control #”, the system allows clock-off of the task based on the values selected in the 'Seq. Control?' drop-down list box in the “Manage Unified Task Sequence” page of the “Maintenance Task” business component. See table.
Refer to the topics "Task Status Modification", "Acknowledge Receipt" for more details.
Check the following box:
Parts Returned? |
Check this box to specify that there are no parts pending for return again the selected task. Task cannot be pre-closed if there are parts pending for return against it and if the 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. This box appears checked by default, if the above mentioned process parameter is set as “Yes”. |
Click the “Reset” pushbutton to reset the clock.
The system ensures the following on clicking the “Reset” pushbutton:
The employee must be assigned to the service area of the work center.
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.
Refer to the topic “Acknowledge Receipt” for more details.
Click the “Pre-Close” pushbutton to pre-close the task.
Note: The system displays an error message if any concurrent user attempts to modify the timesheet details.
The system does not allow modification of execution status of the task,
From “Completed” to “Pre-Closed”.
From any status to “Pre-Closed” if task is on 'Hold' against a hold code for which process parameter 'Prevent Task Status Change?' is set as “Yes”.
From any status to “Pre-Closed”, if task is on 'Hold' against a hold code for which process parameter 'Stop existing shop maintenance execution?' is set as “Yes”.
For a SWO-Task combination, the execution status of the task cannot be changed to “Pre-Closed”, if the clock is running for that task against any employee.
If the process parameter 'Enforce Excess/Core Returns on order closure ? is “Yes” for the 'Shop Work Order Type' of the current SWO, ensure that part(s) are pending for return against the task.
The Work Center to which the SWO# / Task# / Seq# is assigned, must be part of the service area defined for the employee.
If the status of the parent work order is getting changed to “Pre-Closed, ensure that the all the child work orders associated to the parent work order are in terminating status.
If the forecasted task status is changed to 'Pre-closed', then the current scheduled instance of the task will still be pending for execution. (The current instance of the schedule is not updated as ‘Complied’).
The system performs the following on pre-closing the task:
If the task for which the status is changed as "Pre-Closed", is the last task in the workorder and if all the other tasks in the workorder are already in "Pre-Closed" status, the system updates the status of the shop work order as "Pre-Closed".
Short-closes the material request, if any, that is not closed yet, against the.task.
The system displays a pop-up screen “Manage Intershop Routing” if for the task, the parameter 'Routing required?' is set as “Yes” in the shop work order.
Updates account details the finance books.
Updates Capital Expenditure (CAPEX ) details for the SWO.
Refer to “Labor Cost Calculation” for more details.
Conscious pre-closure of tasks/work order that have already consumed parts
Pre-Close Action |
Prerequisite process parameter definition in the Define Process Parameters activity in Common Master |
Warning message displayed? |
If selected Yes after warning? |
If selected No after warning?
|
For Task: Select “Pre-Close” as Exe. Action in the “Task Details” multiline |
Process parameter "Display warning message during pre-closure of tasks having part consumption?" under entity “All Work Order” of entity type “Shop Work Order Type must be 1. |
Yes |
The system pre-closes the task even though parts have been issued for the task |
The system prevents pre-closure of the task. |
Pre closes a Component Replacement task against which part return is pending, on the basis of the process parameter “Enforce Excess/Core Returns on order closure ?”defined under the entity type Shop Work Order and the entity User-Defined in the Define Process Entities activity of Common Master as illustrated in the next table
Process parameter value |
Impact on task closure |
1 / Yes |
The system does not allow pre closure of the task, if the task has executed a component replacement transaction and part return is pending against the task. |
0 / No |
The system pre-closes the task even if the task has executed a component replacement transaction and part return is pending against the task. |
Click the “Complete” pushbutton to complete the execution of the task.
The system performs the following on clicking the “Complete” pushbutton:
Refer to Electronic Signature Feature.
The system performs the following on clicking the “Complete” pushbutton:
The system updates the status of the task to as “Completed”.
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 and discrepancies in the work order are in terminating status.
The system displays a pop-up screen “Manage Intershop Routing” if the task has the parameter 'Routing required?' set as “Yes” in the shop work order.
If the routing pop-up is not displayed automatically on completion of the task, the system creates a return document for the main core, on clicking the “Complete” pushbutton, if
Main Core is pending for return.
‘Final Movement’ of main core for the shop work order is "Return to W/H".
On completion of the SWO, if Repair Process Code is mapped to Maintenance Type ‘Retire’, the system automatically sets the component condition to ‘Phased Out’ and Record Status to ‘Inactive’ under the following conditions:
The component is not currently attached to any aircraft or NHA
The warehouse allows components in Phased Out condition.
Adjust Actual Cost is not ‘Condition Based’, if the component is available in the warehouse
Salvage Action – Internal Stock is Not Applicable for Final Rep. Dis. Code (if component is internally owned)
Salvage Action – External Stock is Not Applicable for Final Rep. Dis. Code (if the component is is owned by supplier or customer)
The system ensures the following on clicking the “Complete” pushbutton:
If the task does not have timesheet booking, the system does not allow the user to change the status to “Completed”.
The employee must be assigned to the service area of the work center.
For the same Task, clock should not be running for any other employee.
The Sign-Off status of the tasks and subtasks of the Shop Work Order should be either “Signed-Off” or “Not Required”, if the Process parameter “Enforce Sign-Off?” is set as “Yes” in the “Common Master” business component.
If the task is being completed directly by entering ‘Start Date & Time’ and ‘End Date & Time’ manually in one go, then 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”.
The sign-off details cannot be modified if the task / subtask is ‘Signed-off’, ‘Voided’ or ‘Rejected’.
Note: The system displays an error message if any concurrent user attempts to modify the timesheet details.
Parameter Recording check:
For the selected task, if ’Mandatory’ parameters are pending for update, then the same needs to be updated using ‘Record Parameter Reading’ link before completing the task.
If the ‘Display By’ radio button is set as “Subtask”, then for the selected subtask, if ’Mandatory’ parameters are pending for update, then the same needs to be updated using ‘Record Parameter Reading’ link before completing the subtask.
Task Transient Status check:
Task cannot be completed if the Transient Status of the task is “Hold”.
Task cannot be completed, if the 'Hold Status' of the task is 'Open' as of current date & time with the parameter 'Prevent Task Status Change?' set as "Yes".
Sequence Control check:
If the task is being completed directly by manual entry of ‘Start Date & Time’ and ‘End Date & Time’ in one go, then system performs the sequence control check as given below::
If the Part # / Mfr. Part # - Mfr. # and the Task are available in the same “Seq Control #”, the system allows completion of the task based on the values selected in the 'Seq. Control?' drop-down list box in the “Manage Unified Task Sequence” page of the “Maintenance Task” business component. See table.
Refer to “Labor Cost Calculation”, “Timesheet Status Update”, "Task Status Modification", "Acknowledge Receipt" and "Employee Skill determination for Timesheet" sections for more details.
Part Program Inheritance
On completion of the work order, if any configuration / part # / part # and serial # change has happened, the component maintenance program automatically inherits the maintenance program of the new part.
Sign-off details
Enter the following in the “Sign-Off Details” group box:
Mechanic |
The employee code of the employee who performs mechanic 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. The employee should have ‘Mechanic’ resource group mapped with the skill that is required to sign-off the task/ subtask. |
Inspector |
The employee code of the employee who performs inspector 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. The employee should have ‘Inspector’ resource group mapped with the skill that is required to sign-off the task/ subtask. |
RII |
The employee 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. The employee should have ‘Insepctor’ resource group mapped. |
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:
During ‘Mechanic’ and ‘Inspector’ sign-off, if task/ subtask has multiple skill requirements, you must select a value in this field. The system leaves the field blank, by default. |
Addl. Sign-Off |
The employee 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. Process Parameter dependency: The Sign-Off comments is mandatory:
|
Note: The sign-off details cannot be modified, if a task or a subtask is already ‘Signed-Off”, ‘Voided’ or ‘Rejected’.
The system performs the following check on Sign-off, completion, void and rejection of the task:
Different Employee Sign-Off permission check:
During Sign-Off, system ensures that the employee # available in the Mechanic / Inspector / RII field is same as the employee mapped to the login user, 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:
During Sign-Off, system ensures that the same employee # is not entered in the Mechanic and inspector fields, if the 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 – Resource Group Mapping:
During ‘Mechanic’ sign-off, system ensures that the employee has ‘Mechanic’ resource group mapped with the skill that is required to sign-off the task/ sub task.
During ‘Inspector’ sign-off, system ensures that the employee has ‘Inspector’ resource group mapped with the skill that is required to sign-off the task/ sub task.
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, then system ensures that the employee possess valid Certificate or License for the sign-off / void / rejection of the task if the following is true:
For the Employee # entered in Mechanic/Inspector/RII fields, License # must be available in ‘Active’ status, and 'Valid Till’ date and ‘Revoke/Suspension date’ must be greater than or equal to time zone date as defined in the “Record Employee License Information” page of the “Employee Personal Information” business component.
Base part # mapped to the Employee must match with the work orders Top assembly part # or Base part # of the Work Orders Top assembly part # defined in the “Part Administration” business component.
If the above conditions are not met, the system checks for the following, for sign-off / void / rejection of the task.
Work unit # / Parent Work unit # / Root Work unit # of the work order must be mapped to the certificate defined in 'Active' status in “Record Certificate Information” page of the “Employee Personal Information” business component.
Base part # mapped to that Certificate must match the Work orders Top assembly part # or prime part # of the Work Orders Top assembly part # defined in the “Part Administration” business component.
Click the “Sign-Off” pushbutton to perform sign-off of the task.
Click the “Void” pushbutton to void the sign-off of the task.
Click the “Reject” pushbutton to reject the sign-off of the task.
Note: If the process parameter “Validate Employee Certificate/License availability during Sign-off/ Reject/ Void of Non-Routines?” under the entity type Shop Work Order Type and the entity User- Defined in the Define Process Parameters activity is 1, the system allows the employee to sign-off, void or reject a task only if the following attributes of the task/ Non-standard task and the License attributes of Employee # in HRMS business component (Record License Information screen) are identical:
a. Base Part # of Part # in Associated Cores of Work Order
b. Part Group of Part # in Associated cores of Work Order
c. Station of Work Center of Task/ NST
d. Resource Group of Task/ NST
The system performs the following on clicking the “Sign-Off’, ‘Void’ and ‘Reject’ pushbuttons:
Refer to the "Electronic Signature Feature" section.
Signs-off/ voids/ rejects the tasks/ subtasks.
Completes the tasks if no more sign-off is pending for the task.
Completes the shop work order if the task being signed-off/ voided is the last task in the shop work order and the parameter ‘Allow Order Completion / Closure ?’ is set as “Allowed” for the Final Disposition of the shop work order. The parameter for the disposition is set in ‘Common Masters’ business component.
If a task is rejected and if it’s the last task in the shop work order, the status of the task is updated as "Completed", but the status of the work order is retained as "In-progress".
On completion of task during sign-off/ void / reject, system displays a pop-up screen “Manage Intershop Routing” if for the task, the parameter 'Routing required?' is set as “Yes”, in ‘the shop work order.
If the routing pop-up is not displayed automatically on completion of the task, the system creates a return document for the main core, on clicking the “Sign-Off” pushbutton, if
Main Core is pending for return.
‘Final Movement’ of main core for the shop work order is "Return to W/H".
The system ensures the following on clicking the “Sign-Off”, “Void” and “Reject” pushbutton:
The employee must be assigned to the service area of the work center.
If sign-off or void or reject of first task of the shop work order is attempted by manual entry of ‘Start Date & Time’ and ‘End Date & Time’, system will not allow sign-off, if the process parameter “Prevent Order Exec. without Main Core Issue”? is set as “Yes” in the “Common Master” business component and the main core is not yet issued to the shop work order.
The system does not allow sign-off / void / 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.
For the selected task / subtask, if ’Mandatory’ parameters are pending for update, then the same needs to be updated using ‘Record Parameter Reading’ link before signing-off the task / subtask. Pending ‘Mandatory’ parameter updates are not checked on ‘Void’ and ‘Reject’.
Sequence Control check:
If the task is being signed-off / voided / rejected directly by manual entry of ‘Start Date & Time’ and ‘End Date & Time’ in one go, then system performs the sequence control check as given below::
If the Part # / Mfr. Part # - Mfr. Part # and the Task are available in the same “Seq Control #”, the system allows sign-off of the task based on the values selected in the 'Seq. Control?' drop-down list box in the “Manage Unified Task Sequence” page of the “Maintenance Task” business component. See table.
Refer to “Labor Cost Calculation”, “Timesheet Status Update” "Task Status Modification", "Acknowledge Receipt" and "Employee Skill determination for Timesheet" 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 to specify the category of the indirect timebooking. The system lists all the quick codes defined for the type “In-Direct Category” in the current business component, if Component Interaction Model (CIM) interaction does not exist between “Time Management” and “Shop Work Order” business components. If CIM interaction exists between “Time Management” and “Shop Work Order” business components, the system lists all the quick codes defined for the type “In-Direct Category” in the “Time Management Master” 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). The date and time will be considered as in the time zone of the work center and station defined for the task. 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 manually, and must be earlier than or equal to the current date and time. During manual update mode, the difference of days between the time zone 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). The date and time will be considered as in the time zone of the work center and station defined for the task. 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 manually, and must be earlier than or equal to the current date and time. During manual update mode, the difference of days between the time zone 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 in-direct timesheet for the ‘Start Date & Time’ and ‘End Date & Time’. Example
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 system ensures the following on clicking the ‘Clock On’, ‘Clock Off’ and ‘Reset’ pushbuttons in the ‘In-Direct’ section:
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’.
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 work center in which the part is received. Mandatory. 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:
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, based on the process parameters ‘Acknowledge Receipt’ and ‘Allow receipt to different work center ?’ defined in the “Set Process Parameters” page of the “Common Master” business component:
If the part #-serial # is in a work center ‘WC1’ and if the task must be executed in work center ‘WC2’, the part is routed automatically to the work center ‘WC2’ for execution and the Routing Status of the part is updated as “Received”, if the process parameter ‘Acknowledge Receipt’ is set as “Automatic” and ‘Allow receipt to different work center ?’ is set as “Allowed”.
If the process parameter ‘Acknowledge Receipt’ is set as “Manual”, you must acknowledge the receipt of part in the moved work center, by clicking the “Ack. Receipt” pushbutton. The system updates the Routing Status of the part as “Received”.
If the process parameter ‘Allow receipt to different work center ?’ is set as “Not Allowed”, part cannot be received in a work center that is different from the work center to which the part is moved.
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 regarding the task being put on hold or being released. (Alphanumeric, 20). Mandatory for both ‘Hold’ and ‘Release’. |
Click the “Hold” pushbutton to hold the task.
The system performs the following on clicking the “Hold” pushbutton:
Ensures that the employee is assigned to the service area of the work center.
Updates the hold details only for those tasks that are in “Planned” and “In-Progress” statuses.
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” business component.
Ends the clock, if clock is running.
Updates the current date and time as ‘End Date & Time’.
Click the “Release” pushbutton to release the held task.
The system ensures that the employee is 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 are displayed here. |
Additional links in left pane
Select the "Record Missing Parts List" link to record the details of the parts that are missing from a component during execution of a shop work order.
Select the "Record Part Deviation List" link to record the details of the pats that are deviating from the component.
Refer to "Aircraft" online help for more details.
Select the "Report Resource Actual" link to report or update the actual resource consumption as against the estimation made.
Select the "Record Parameter Reading" link to record the parameter reading details and conditional evaluation details for the task.
Select the "Route Parts" link to route a part from one work center to another work center or a repair agency.
Select the "Record Parts Consumption" link to record the part consumption details.
Select the "Track Response" link to record details of any request raised by an employee and track the response to the requests.
Refer to "Common Masters" online help for more details.
Select the "Manage Teardown Information" link to record teardown information of the part.
Select the "Record Part # / Serial # Change" link to record the part # - serial # change details.
Refer to “Stock Maintenance” online help for more details.
Select the “Edit Work Estimates” link in the left pane to estimate, update and confirm the part and resource requirements for a shop work order.
Refer to the “Work Monitoring & Control” online help for more details.
Select the "Plan Work Order" link to create / modify the shop work order.
Select the "Generate Sub-Work Order" link to generate sub-work order.
Select the "Manage Work Assignments and Reporting" link to manage work for the employee.
Refer to the “Work Monitoring & Control” online help for more details.
Select the “Create Engg. Service Request” link to create an engineering service request.
Refer to “Engineering Service Request” online help for more details.
Select the Inquire Engg. Service Request” link to create an engineering service request.
Refer to “Engineering Service Request” online help for more details.
Select the “Edit Work Order Addl. Info." link to modify the work order additional information.
Select the "Edit Task Addl. Info." link to modify the task additional information.
Select the “Upload Documents” link in the ‘main links’ section to upload the documents.
Refer to the “Object Attachments” online help for more details.
Select the “View Associated Doc. Attachments" link to view the attached documents.
Refer to the “Object Attachments” online help for more details.
Select the “View Work Orders" link to view the work order details.
Select the “Issue Certificate of Maintenance" link to view the attached documents.
Select the “Manage Part Serial Mod Details” link to record / manage the Part – Serial level MOD details.
To proceed carry out the following
Click the “Report Findings” tab to record observations and discrepancies that are found during execution of tasks.
Click the “Disassemble & Assemble Core” tab to attach, remove and replace components and spare parts with respect to the main core component.
Click the “Initial Workscoping” tab to define workscope for the execution of tasks in a shop work order.
Click the “Material Request” tab to record the material request details.
On clicking the “Sign-Off’, ‘Void’, ‘Reject Task’ and ‘Complete’ pusbuttons, the system displays the "User Authentication Web Dialog" screen.
Insert the smart card into the smart card reader and enter your Personal Identification Number (PIN) in the "User PIN” field.
Following are the prerequisites for using Electronic Signature:
The Smart Card Interface Client installation must have been completed and configured on this computer.
A Smart Card Reader must be connected to this computer and configured.
Electronic signature authentication must have been enabled for this business component or function in the “Smart Card Interface” business component.
The person who will be using the Electronic Signature feature, must have been enrolled as a smart card user and issued a card in the "Smart Card Interface” business component. The card must be active and valid for the current date.
Click the “OK” pushbutton.
The system authenticates the entered PIN value against the user's PIN value stored in the smart card.
If an invalid PIN is entered, the system displays the error message “Incorrect Secret Code Submission” and the Electronic signature cannot be completed.
On successful authentication, the system executes the ‘Sign-Off’, ‘Void’, ‘Reject’ and ‘Complete’ validations.
Note: The smart card will get into "Locked" status, if the number of continuous invalid PIN entries exceeds the maximum number of invalid PIN entries defined in the “Smart Card Configuration” activity in the "Smart Card Interface” business component. Contact the administrator for unlocking the card and to use the smart card again for Electronic signature.