Maximize Scheduling
Effectiveness
Introduction
•
Looking at Forecasting and Scheduling
–
Truth Based Scheduling
–
Forecast your needs and react
Truth Based Scheduling
Getting Real Information to Schedule
Work and Resources
Standard Methodology for Scheduling
Work
•
Zones and Schedule Areas
•
Time Frames and Appointment Windows
•
What Availability do we have
What’s a job worth in terms of time?
•
Converting Time to Points
–
5 Minutes = 1 point (12 Points per Hour)
•
A job that takes 1 hour is assigned 12 Points
–
Drive Time is Averaged for the Purpose of
“Padding”
–
An Average Drive Time of 15 Minutes = 3
Additional Points
How is Availability Calculated?
•
Using points to…
– Calculate the time available based on the Technicians working that day
•
Total Technician Points are
loaded into a Quota
The Problem with Points
•
Chasing Points
–
Stretch Goals
–
Performance Goals
–
Over Booking for Cancellations
•
Unintended Results
–
Jobs are Rushed
–
Drivers are Speeding
How This Information is Used to
Schedule Appointments
•
Customer is given “first
available” time slot with
enough points to complete
the job
•
No evaluation of what’s
already scheduled
Time to Get the Job Done
•
WFM Platform routes jobs
in scheduled time frames
•
Optimizes Drive Time
– As the crow flies
– Turn by Turn
•
Optimization typically
1 0 12 pm
Traditional Routing
Tech 1: Planned schedule Tech 1: Actual schedule Tech 2: Planned schedule Tech 2: Actual schedule 8 am 5 pm A B C D A B D E F G H I E F HEnd of work day – job postponed 25% waste 45% waste Idle Idle
Tech late for job, location unknown Customer
not at home Job taking longer
than planned “Where is the technician?” Customer called to cancel Job shorter than planned Idle Idle
Truth Based Routing Changes
Everything!
•
No Quota Buckets
•
No Average Drive Time Inefficiencies
•
Real time Appointment Calculations that
Deliver the Best Appointment Window for
your Customer
•
Continually Optimized Routing Keeps Drive
Time to a Minimum
Graded Appointment Slots
Mon Tues Wed Thurs Fri
8:00 – 10:00 8:00 – 10:00 8:00 – 10:00 8:00 – 10:00 8:00 – 10:00 10:00 – 12:00 10:00 – 12:00 10:00 – 12:00 10:00 – 12:00 10:00 – 12:00 1:00 – 3:00 1:00 – 3:00 1:00 – 3:00 1:00 – 3:00 1:00 – 3:00 3:00 – 5:00 3:00 – 5:00 3:00 – 5:00 3:00 – 5:00 3:00 – 5:00 20 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
14
Measured Value
0 5 10 15 20 25 30
Worst Slot
Best Slot 16 Minutes / Task
24.4 Minutes / Task
34%
1 5 I M N N I J H G E I M F B AA B D E I M P F D C 8 am 5 pm Tech 1: Actual schedule Truth Based Schedule Tech 2: Actual schedule <5% waste 5-10% waste J K 12 pm K LL H H O B A D E F M J H I K L
Job taking longer than planned
All day window
Morning window Afternoon window Job shorter
than planned Customer calledto cancel
Customer not at home
What’s in it for you?
•
Improved optimization of Drive Time
–
Up to 25% improvement when you consider work
already in the field to suggest appointments to the
customer
•
Tighter route optimization
–
A 7% increase in resource utilization
•
Continuous Optimization
ADDITIONAL TOOLS TO IMPROVE
YOUR OPERATIONS
Forecasting your needs
You can’t get ahead of your
competition if you can’t get ahead
of yourself
Proactive is always better than
Reactive
•
Alignment
–
Marketing Activity
–
Construction Active
–
Seasonal Activity
•
Planning
–
Staffing appropriately
–
Contract Labor Supplement
Think Ahead
•
Forecasting Tools
–
Ability to Play “What If”
•
Add Projected Capacity Needs
•
Adjust Service Levels
•
Adjust Time Frames
–
Understand and React to Demand
•
Adjust Schedules
•
Add Contract Labor
Budget Planning
•
The effect of staffing when improving Service
Levels
•
The effect of scheduling or area changes
•
The effect of moving from 2 hour to 1 hour
time frames
•
Providing same day service for certain types of
work
•
The resources needed to complete long term
projects, on time and under budget
Managing Complex Work
•
Multi stage tasks (MST):
•
ClickSchedule allows the creation of resource (e.g. field inspector)
and time dependencies between each subtask of a multi-stage task
through out-of-the-box functionality.
•
Multi day tasks (MDT):
•
ClickSchedule supports tasks that can be scheduled over one or
more active time periods, such as nights, weekends,
non-availability assignments or non-working days in an
inspector/auditor’s calendar.
•
Multi person tasks (MPT):
•
ClickSchedule provides functionality to automatically schedule tasks
that have a requirement for more than one resource.
Multi Stage Tasks (MST)
•
ClickSchedule allows the creation of resource (e.g. field
inspector) and time dependencies between each subtask of a
multi-stage task through out-of-the-box functionality.
– The common types of Multi Stage Tasks are:
• Same Start: Task should start EXACTLY at the same minute as another task.
• Finish to Start: Task should start after another task finishes.
• Same Day: Task should start at the same DAY as another task.
• Same Resource: Task should be assigned to the same person as the related task.
– MST relation will always be between one task to another.
– There could be more than a single relation on a single task.
– ClickSoftware’s Optimization engine will consider the MST’s chain of related tasks before automatically assigning or optimizing the
Multi-day Tasks (MDT)
•
ClickSchedule supports tasks that can be scheduled over one or more non-active time periods, such as nights, weekends, availability assignments or non-working days in an inspector/auditor’s calendar.Bundled Tasks
•
The Bundler Service
– The Bundler Service is responsible for collecting selected tasks and “replacing” them, for scheduling purposes only, by a collective parent task. The bundler is responsible for the full “lifecycle” (creating,
maintaining and deleting) and logic of these mega tasks. In this scope it is responsible for decision making process that selects a subset of tasks from a given domain and “decides” they can be represented by a parent.
•
Mega Task
– A mega-task means a parent task which references (or “hosts”) a set of “child” tasks (constituent tasks). Mega-tasks are the processing result of the bundler, and actually, it can be claimed that the full life cycle of mega-tasks is maintained by the bundling module. The Mega Task can be transparent to the field resource, updates the individual tasks that make up the bundle.