Details and Examples: Manual Move Fields Data Set
The Manual Move Fields data set contains values of the fields related to activities that were manually moved in the application during the extraction period.
Depending on the requirements of the company, you can change the list of exported properties and fields at any time by removing or adding certain fields.
| Field | Label | Description |
|---|---|---|
| Action ID | appt_move_log.action_id | Unique numerical identifier of the move action |
| Action time | appt_move_log.action_time | Date/time of the move action. |
| Activity ID | appt_move_log.aid | Unique numerical identifier of the activity |
| Auto-routed to Date | appt_move_log.autorouted | The date the activity was scheduled for during the latest Routing run. |
| Move Reason ID | appt_move_log.move_reason_id | ID of move reason which the activity was moved. |
| Move Reason Label | appt_move_log.move_reason_label | Label of the move reason for which the activity was moved. |
| Move Reason Name | appt_move_log.move_reason_name | Name of move reason which the activity was moved. |
| Move from Date | appt_move_log.move_from_date | Date/time when the activity was moved from. |
| Move from Provider ID | appt_move_log.move_from_provider | Provider ID that activity was moved from. |
| Move to Date | appt_move_log.move_to_date | Date/time when the activity was moved to. |
| Move to Provider ID | appt_move_log.move_to_provider | Provider ID that activity was moved to. |
| Move Condition | appt_move_log.move_reason_condition | Name of move reason condition of the move action |
| User Name | appt_move_log.uname | Name of the user who performed manual move |
| User ID | appt_move_log.uid | Unique user ID |
| Work Skill Mismatch | appt_move_log.ws_mismatch | Status of Work Skill Mismatch violation |
| Work Zone Mismatch | appt_move_log.wz_mismatch | Status of Work Zone Mismatch violation |
Benefits - Use Cases
You can adopt this functionality to achieve these goals (examples):
- Measure dispatchers work - available without Move Reasons configuration
- Analyze manual assignment patterns and define required education for dispatchers
- Improve routing results
- Reduce travel time by tuning Work Zones configuration
- Monitor proper Work Zones/Work Skills configuration
- Improve time window compliance
- Improve capacity management
Measure dispatchers work - available without Move Reasons configuration
Now you can quantitatively measure a dispatchers work. By analyzing the number of manual activity assignments made by dispatchers you can:
- measure jeopardy management
- analyze a dispatchers workload by days/hours
- compare dispatchers, departments, and geographical areas
- understand how often activities are moved after Routing runs
- understand how often activities are moved with work zones/work skills violations
- understand how often activities are rescheduled
- understand how often activities are moved from resource to resource and from bucket to resource,
- Move reason examples: any move reason available without enabling the feature
Follow these steps to use this functionality:
- Run Manual Assignment by User report for different resource areas.
- If the feature isn't enabled, manual moves are displayed as No move reason selected.
- Check Daily Extract data for move attributes such as, work zone violations and type of move.
Analyze manual assignment patterns and define required education for dispatchers
Now you can break down why dispatchers are performing manual interventions. By comparing dispatchers behaviors, you can understand who requires additional education.
Move reason examples: any reasons applicable for your business
Follow these steps to use this functionality:
- Run Manual Assignment by Users report or use Daily Extract data to compare the number of moved activities by reasons for different dispatchers.
- You can estimate the average number of moved activities for department/geographical area/line of business.
- Dispatchers that exceed the average manual moves by specific reasons may require attention.
Improve routing results
With this functionality you can improve the percentage of auto-routed activities. Use move reasons to understand which routing plans require configuration review.
Move reason examples: Not Assigned by Routing, Activity Emerged During Working Day, Assigned to Incorrect Mobile Worker, Several Mobile Workers on the Same Address, Zigzagging, Assigned with SLA Overdue and Assigned with Late Arrival.
Follow these steps to use this functionality:- Check Daily Extract data for buckets with large numbers of activities not assigned by Routing.
- Select activities moved from this bucket.
- Check if the activity is present in routing plan activity and resource filters, cost of not assigning an activity.
- Review travel limitation, Home Zone center configuration, Home Zone radius overstep weight parameters.
- Check the bundling keys.
Reduce travel time by tuning Work Zones configuration
It's possible that an activity found nearby a resource's route isn't auto-routed to this resource because it relates to another work zone.
Now you can track those cases and respond accordingly.
Move reason examples: Assist in Nearby Area, Resource in Nearby Location
Follow these steps to use this functionality:- Monitor corresponding Move Reasons in the Manual Assignment Trends report.
- This area requires attention if the number of moved activities is relatively large or growing.
Here are the action items:
Increase the area where a mobile worker operates; configure Home Zone center parameters with smaller ratio to resources
Monitor proper Work Zones/Work Skills configuration
Activities aren't getting auto-routed when resource work zones or work skills are configured improperly.
Move reason examples: Resource has Required Skills, Incorrect Work Zone.
Follow these steps to use this functionality:
- Monitor corresponding Move Reasons in reports or exported data.
- From exported data define which resource requires Work Zones or Work Skills review.
Improve time window compliance
An activity that takes longer than expected to perform might jeopardize next activities along the route. This might cause multiple activities move trying to fit time window. Now you can measure the impact - how many other activities are moved and how many routes are affected by this action.
Move reason examples: Resource off Shift, Call-in Sick, Vehicle Issues, SLA Overdue, Time Slot Overdue, Incorrect Work Type Requested, Work Took Longer, Extra Work on Site, Requested by Field Manager, Requested by Mobile Worker , Requested by Mobile Worker - missing inventory.
Follow these steps to use this functionality:
- Lets consider Move Reasons that might be applied in your business.
- When the number of moved activities with these reasons is increasing or relatively
high (e.g. 10% of total manual moves), you can adopt the suggested improvements:
-
Resource off Shift/Call-in Sick
This shows how many activities were moved because the mobile worker reported that they are off-shift. If the resources calendar is updated often throughout the day, it’d be beneficial to explore running the routing plan(s) multiple times during the day.
-
Vehicle Issues
High occurrence of this reason shows that the vehicle fleet requires better maintenance. You can measure the impact of implemented improvements by comparing the number of activities with this Move Reason before and after.
-
Work Took Longer
If this reason is common in the Move Reason reports, perhaps some aspects aren't being considered for activity duration estimations. You can configure additional properties to activity duration keys.
For example adding a new field such as Numbers of TV installed will let you've different durations for the same activity type, potentially resulting in future routes planning being more precise.
-
Improve capacity management
Move reason examples: Overloaded Area/Overbooking, Assist in Other Area.