Steps in the screenshots correspond to the numbers in the headings.
Task Statuses can be further modified by a Task Status Reason. This isn't always the case - many times you will find the Task Status to without a reason, as is the case when the Task is new.
Task Statuses Include:
- New: Task has been received by maintenance and is waiting for either the supervisor to assign as reactive work or for the P/S to begin planning.
- In Planning: For non-MRCT breakdown Tasks: Work order is received, P/S assigns an initial priority and estimated duration, sets status to In Planning.
- Ready for Execution: This would be used to indicate that the task has been scheduled with the customer, assigned to a technician, is ready to be completed.
- In Progress: Any task that a technician is working on.
- Hold: This would be used when the customer wants to defer the cost or execution to a later date or contemplating the real need to be completed.
- Completed: Task is complete and waiting for review.
Most of the Task Statuses have Status Reasons to define them. In every case, you have the option to leave the status reason blank.
Task Status Reasons include:
- Kitted: When all parts have been gathered and grouped for the Task, it can be marked with the status reason Kitted. (USED WITH IN PLANNING)
- Waiting on Service: This status reason is used if we are waiting on an outside service company to come in and do the work. (USED WITH IN PLANNING & HOLD)
- Waiting on Materials: This status reason is used when the work is delayed because parts are not available to do the job. (USED WITH IN PLANNING & HOLD)
- Waiting on Production: When you cannot do the work because Production can’t stop to give us the machine, you would use this status reason. (USED WITH IN PLANNING & HOLD)
- Planning Complete/Ready for Scheduling: Once the P/S has finished Planning, they would mark the Task with the status reason Planning Complete/Ready for Scheduling. All the Portal views show this Status Reason as Ready for Scheduling, while the CLIENT shows it as Planning Complete. (USED WITH IN PLANNING) It should also be mentioned that there is built-in functionality with the Planner Portal that triggers this status reason automatically when a task exits the Planning Wizard.
- Scheduling Complete: Some sites will use this when the Task has been scheduled. (USED WITH IN PLANNING)
- Accepted: Some sites use this when the Tech acknowledge that s/he is going to do the work. (USED WITH IN PROGRESS & REVIEWED)
- Arrived: Used by Traveling Techs and larger sites to indicate they are at the site or at the machine. (USED WITH IN PROGRESS)
- En-route: Used by Traveling Techs to indicate when they are en-route to the site. (USED WITH IN PROGRESS)
- Carryover: This status reason is used when the task that cannot be completed by the current technician. (USED WITH IN PROGRESS)
- Rework Required: The system automatically assigns this status when the supervisor reopens a task during the WO Review Process. (USED WITH IN PROGRESS)
- Assigned: Task has gone through the planning/scheduling process and technician is assigned. Work is ready to be carried out. (USED WITH READY FOR EXECUTION)
Mobile App
Notice that the Task Status and Task Status Reason are displayed in the Grid as well as the Task Summary Panel.
As a Technician, the vast majority of the time, the Status/Status Reason and even Task Activity Sub-Types will be set through the planning and scheduling process by a member of your management team. There could be times where you will need to manually set a status &/or status reason.
In our example, the task is ready for execution, but upon arrival to do the task, you find that that you need to return in two hours. Production will be using the area until then.
1. By default, the Home screen view will load for the Technician. Click the MY WORK button at the bottom. This screen will show all the Tasks that have been assigned to the Tech for the day.
3. If you click on the Task line that Task will populate.
4. Click on the Summary icon to bring up the Details.
The Pop-Up box will show the details of the Task.
0 Comments
Add your comment