Embed Size (px)
Citation preview
DISPATCHINGMikey Plavins
Current dispatching algorithms
Closest Car (No-Location Algorithm)
Zone Layers & Plotting
Cover
Address Learning
How it works
How to correct errors
DISPATCHING
CLOSEST CAR SETTINGS
Applies if a booking is set to No Location Check
CLOSEST CAR SETTINGS
Applies if a booking is set to No Location Check
Can be automatic:
Attribute Priority > 5 (e.g. WAT or Maxi)
CLOSEST CAR SETTINGS
Applies if a booking is set to No Location Check
Can be automatic:
Attribute Priority > 5 (e.g. WAT or Maxi)
Fleet Settings
Prebookings
Driver-Created Bookings
Return Journeys
All Bookings
CLOSEST CAR SETTINGS
Applies if a booking is set to No Location Check
Can be automatic:
Attribute Priority > 5 (e.g. WAT or Maxi)
Fleet Settings
Auto-Escalation (Escalation Time 2)
The number of seconds a booking must wait in the cover queue before the 2nd escalation. At this point the booking will be marked as NO LOCATION DISPATCH which will dispatch the booking to the closest available car regardless of its location. 0=Disabled
CLOSEST CAR ALGORITHMA booking the enters the queue will find the ‘closest’ of
several vehicles
If difference is small (< 500m):
Same zone: lowest queue position wins
Different zones: vehicle vacant longest wins
A vehicle that becomes available doesn’t actually find the closest booking – it finds the highest ranked No Location Check booking in the order defined a few slides from now. This is how priorities are handled by the system.
ZONE LAYERS
ZONE LAYERS
ZONE LAYERS
ZONE ALGORITHM
These rules apply when deciding which of two jobs in the same zone will be offered first to an available vehicle
Should be consistent with the ordering in the dispatch client
Priority of Attributes
ZONE ALGORITHM
These rules apply when deciding which of two jobs in the same zone will be offered first to an available vehicle
Should be consistent with the ordering in the dispatch client
Priority of Attributes
‘High Priority’ set
ZONE ALGORITHM
These rules apply when deciding which of two jobs in the same zone will be offered first to an available vehicle
Should be consistent with the ordering in the dispatch client
Priority of Attributes
‘High Priority’ set
Prebooking Adjustment
Number of minutes to boost prebookings by in terms of prioritising the queue. 0 means equal to ASAP that has been waiting as long. A large number, e.g. 3600 = 6 hours, means prebookings will effectively always have priority over ASAP bookings if they are both in the queue
ZONE ALGORITHM
These rules apply when deciding which of two jobs in the same zone will be offered first to an available vehicle
Should be consistent with the ordering in the dispatch client
Priority of Attributes
‘High Priority’ set
Prebooking Adjustment
Pickup time (including release time)
ZONE ALGORITHM
These rules apply when deciding which of two jobs in the same zone will be offered first to an available vehicle
Should be consistent with the ordering in the dispatch client
Priority of Attributes
‘High Priority’ set
Prebooking Adjustment
Pickup time (including release time)
Earliest entered booking
COVER
COVER
COVER ALGORITHM
Applicable when a vehicle becomes vacant and is looking for the best match of cover jobs within any distance set, or a job enters the system and several vehicles are eligible
Several Bookings:
‘High Priority’ set (30 minutes)
Priority of Attributes (10 minutes per level)
Prebooking Adjustment (5 minutes per day)
How long in queue vs. How far away (5 minutes per Km)
Several Vehicles
How long vacant vs. How far away (5 minutes per Km)
REASONS FOR NOT GETTING A CERTAIN JOB
Obvious:
Attributes
Capacity
Manually assigned
REASONS FOR NOT GETTING A CERTAIN JOB
Less obvious:
Deselected attributes
Can be overridden by making it a No Location Check job if this fleet property is set to Y
REASONS FOR NOT GETTING A CERTAIN JOB
Less obvious:
Deselected attributes
Too many rejections/resubmissions
REASONS FOR NOT GETTING A CERTAIN JOB
Less obvious:
Deselected attributes
Too many rejections/resubmissions
Manual rejections
Applies to cover offers only
REASONS FOR NOT GETTING A CERTAIN JOB
Less obvious:
Deselected attributes
Too many rejections/resubmissions
Manual rejections
Blacklisting
PENALTIES
Encourage drivers to take work
Discourage ‘cherry-picking’
Questions?
DISPATCHING
LEARNINGA set of Streets and Areas provided on startup
Enter any additions & ‘Places’ via the F11 menu
Setting to learn directly new combinations from client
LEARNINGUnknown PLACE or STREET ADDRESS with a new prefix
LEARNINGUnknown PLACE or STREET ADDRESS with a new prefix
Google Lookup (saves a position in DB)
LEARNINGUnknown PLACE or STREET ADDRESS with a new prefix
Google Lookup (saves a position in DB)
Otherwise Default Zone of Area specified in F11 menu
Location not sent to vehicle for directions/compass
LEARNINGUnknown PLACE or STREET ADDRESS with a new prefix
Google Lookup (saves a position in DB)
Otherwise Default Zone of Area specified in F11 menu
Location not sent to vehicle for directions/compass
When the meter is switched on we learn from the GPS
LEARNINGUnknown PLACE or STREET ADDRESS with a new prefix
Google Lookup (saves a position in DB)
Otherwise Default Zone of Area specified in F11 menu
Location not sent to vehicle for directions/compass
When the meter is switched on we learn from the GPS
Save the last 10 GPS – an algorithm picks the best location from those which allows the system to
Learn over time if a location moves (e.g. a KFC) - or if the first locations are learned incorrectly
Minimises the effect of badly learned locations (for instance if the driver flashes the meter one bad point won’t override the last 9 good ones)
LEARNINGCan force learning of the new location with these Fleet Configuration options:
LEARNINGCan force learning of the new location with these Fleet Configuration options:
THANK YOU!
Questions?
