ost field service optimisation vendors argue that their tools offer the best software to improve field operations. Simply asking a few well-placed questions can highlight exactly how powerful their field service optimisation is. It's soon clear that some platforms are only designed to solve one or two parameters, such as travel time or shift costs. Worse, light weight scheduling systems often rely on customer service rekeying, or only consider filling appointment windows and producing routes and tours via out-dated public-ready maps.
With thirty years of experience in the development of real-time field service software, we've complied a shortlist of questions to assist you in determining an authentic field service solution—and away from inferior optimisation.
WHAT IS FIELD SERVICE OPTIMISATION?
Defined as 'the action of making the best or most effective use of a situation or resource'. Translated to field service, it specifically describes a software that continually produces the best outcome across appointment scheduling and route planning according to your specific parameters. Authentic optimisation will consider and calculate instructions using millions of data points, including any SLA/KPI.
It will not force a head office to choose from a 'pick list' of outcomes; nor will it require manual intervention if conditions change in-shift.
WHAT IS 'REAL TIME'?
The proliferation of terms such as 'real time', 'dynamic', and 'always on' leaves the field software market saturated with look-alike products. Real time really means 'live', as in 'simultaneous' or 'right now'. Authentic real-time optimisation continuously tracks and manages sources including scheduling and appointment generation/booking, route and tour planning, two-way digital connection with field operatives, self-service web portals, and customer engagement. It should produce outcomes recognising intervention factors such as location, traffic, weather, resource skills, time-of-day (and many more).
If the solution only offers 'batched or overnight' optimisation, then the solution is not 'real time'.
TELL ME ABOUT ALGORITHMS
At the heart of a scheduling system is an algorithm. Simply put, this is the set of instructions that works in the background to simulate and solve complex field service scheduling. You don't have to understand the world of data science to gain an insight into the quality of an algorithm. It's obvious that for true optimisation it must configurable and can handle unlimited complex rules in real time. Question if it was built and remains 'owned' by the field software developer. Ask for examples about how it continues to develop and how its machine learning capability offers optimisation unique to your workflows. Consider this example; geolocation data determines a field resource must walk 10 flights of stairs to a regular customer's site.
If the algorithm cannot determine that this appointment type always takes longer than 'gantt chart filling' allows, then it is likely out-dated and the provider may a lack modern development approach.
HOW DO YOU SOURCE LOCATION DATA?
The advantage of a system's mapping data may be graded in one word: accuracy. This is; the quality of precision and the age of the data. With the trillions of data strings required to create authentic optimisation value, the results are degraded without geolocation. A system that considers these dimensions should therefore calculate the fastest outcome, not the shortest. Identifiers such as side of street, one-way streets, junctions, and time-of-day driving data for trillions of journeys all contain geocode elements and should be considered in the routes produced. Further data-driven positions power optimised results, such as factoring ongoing roadworks.
A system without geolocation cannot for instance, schedule against genuine distances, travel times, or track a resource to announce a time of arrival.