ARCHIVE FOR THE ‘service-engineer’ CATEGORY

In today’s society whereas consumer’s we are becoming increasingly used to and expectant of instant results is an obvious challenge for field service organisations but can remote services help bridge the gap? Manuel Grenacher, CEO, Coresystems discusses...

With the pervasiveness of the Internet of Things (IoT), everything from device performance to customer interactions has become faster and more connected. Devices that require maintenance and repair now operate on an accelerated timeline of immediately notifying the user when service is needed. Because of this, customers expect real-time responses, leaving little to no time for a field service technician to travel to the site, troubleshoot the issue and fix the device. Therefore, to maintain and improve customer satisfaction, technicians are exploring ways to provide the same level of onsite, but while remote.

The idea behind remote technicians stems from the technician’s ability to diagnose a problem, determine possible solutions, and lay out a plan for issue resolution - all before they take one step onto the worksite. In a perfect world, remote technicians essentially only have to leave their workstations once to perform tasks that require a high level of skill, or perhaps not at all for routine maintenance and repair. Naturally, this drastically cuts down the amount of travel cost and time and total project duration needed to solve an issue with a customer’s device, streamlining the entire service request from issue detection to resolution.

Field service technicians no longer need to blindly infer what is happening on the broken device based on descriptions from less experienced users, nor do they need to fumble through repair instructions over the phoneField service technicians no longer need to blindly infer what is happening on the broken device based on descriptions from less experienced users, nor do they need to fumble through repair instructions over the phone. Indeed, the remote technician takes full advantage of tools such as augmented reality, artificial intelligence, and even the IoT itself to deliver the same experience as a technician standing in front of the customer would.

So how does it work? It starts with putting the proper infrastructure in place to allow technicians to troubleshoot issues on devices and machines from afar. Taking issue detection as an example, remote technicians can use augmented reality to share a mobile phone screen with a customer for a visual walkthrough of the issue. From there, the remote technician can schedule an onsite appointment if needed and manage the parts orders needed for specific projects, ensuring all the necessary assets are in place well in advance.

To be fair, managing a workforce of remote technicians is no easy task. In order to optimize your field service operations, it is extremely beneficial to be able to automatically assign the most qualified and available technician for respective service requests, taking into account expertise, location, and availability. As a fail-safe, the onsite technicians should have easy access to online product specifications and other assets needed to complete service requests. Additionally, similar to how remote technicians use augmented reality to connect to the customer for issue detection, on-site technicians can connect to more experienced journeyman technicians back at headquarters to troubleshoot unforeseen issues. This creates a network of knowledge that will keep project duration to a minimum, improving efficiency for the technician while onsite.

The way in which field service technicians work has evolved and is continuing to do so. The next generation of technicians are prioritizing independence, autonomy, and flexibility, on top of foundational knowledge and customer service experience. As the IoT continues to grow, so will the need for remote technicians, and the field service industry assuredly has the infrastructure to maintain the high level of customer satisfaction that we strive for today.

What are your experiences experimenting with a more remote field service workforce? Feel free to share your thoughts in the comments section below!

Be social and share

The blend of GPS, real-time traffic information and latest workforce scheduling can yield previously unknown levels of efficiency for field service delivery. Jeremy Squire, Managing Directo, FLS, Fast Lean Smart explains how... 

The convergence between field force scheduling and vehicle tracking is not something on the horizon, it has already arrived - and with precise arrival times now offered by private car hire and delivery companies such as Uber, DPD, IKEA and Amazon, customers are already expecting the same for field service appointments and anything less may be perceived as poor service. It is fast becoming a necessity for field service companies to both realise and embrace this as essential to achieve.

At FLS, Fast Lean Smart, we specialise in scheduling and route optimisation solutions and our customers are increasingly interested in this convergence of technologies. I believe it is vital for most field service companies to consider this and let’s take a moment to look at both how and why you should be doing likewise.

If live GPS location coordinates are provided to FLS VISITOUR, our leading scheduling technology, we can re-plan your engineer job schedules based on exactly where they are in their current route rather than wait until a confirmation of arrival from their mobile app.

The system could be configured to automatically re-optimise the rest of the day ‘real-time’ for engineers based on the location updates. This might enable additional jobs, highlight where an SLA or appointment slot will be missed and optionally remove lower priority jobs from the schedule unless overtime is approved.

[quote float="left"]With the convergence of these technologies and capabilities, there really has been no better opportunity to enrich the profitability of your business whilst achieving happier engineers and happier customers[/quote]Many service operations, however, decide against this level of fluidity for their engineer’s day and therefore might choose to lock the next jobs or even the whole day and only make changes in exceptional circumstances and under the control of a planner. This is particularly true for tasks which require the engineer to have parts or for appointments that require preparation.

What is certain, however, is that knowing issues with the current plan in the back office is key for customer service and engineer welfare, therefore the more accurate this is the better. The driving durations used by the scheduling algorithm are also very important to achieve this objective and at FLS we use actual average drive speeds for each road segment according to time of day for pre-planning. Variable traffic congestion is a severe issue in some areas, therefore, we also use a real-time feed of current traffic to optimise during the day. With this combination, drive durations are as accurate as we have all become accustomed to when using TomTom Live or Google Navigation on our smartphones.

It requires this high level of accuracy to enable reliable automated messaging to customers with the refined time of arrival for engineers. However, combining GPS location data in the FLS VISITOUR scheduling system also enables our FLS Customer Portal which can be accessed via a URL in the arrival time message and for your customers to track the arrival of the engineer from the previous job on a map, Uber style! (no more ’Where’s my engineer?’ calls.)

This capability has now become the goal of almost every field service provider we speak with, not just  B2C, and whilst currently a USP we can expect it will increasingly become the norm.

Of course, all this has terrific benefits for the service provider as well as the customer.

Maximising productivity and minimising cost in the field whilst giving good service (right engineer with the right parts etc) is a standard desire for everyone, however, with the convergence of these technologies and capabilities, there really has been no better opportunity to enrich the profitability of your business whilst achieving happier engineers and happier customers.

To deliver this level of performance and customer excellence, integrating engineer tracking is essential and there is an answer for every circumstance; a vehicle telematics system, a low-cost GPS cigarette lighter tracker or a phone/tablet app such as FLS MOBILE.

The days of customers waiting blindly for an engineer to arrive are on the way out and field service companies must adapt to these new expectations swiftly to avoid being seen as outdated and uncompetitive. The good news is that the solutions are already available - it is just a case of connecting the dots - and FLS VISITOUR is a solution that allows you to do just that.

[hr]

Be social and share...

It seems there has been something of a convergence between the worlds of rugged manufacturers and their consumer peers across the last few years. In the past, the two occupied very separate worlds.

Rugged was very much the world of heavy, chunky, and robust devices, whilst the consumer equivalents were sleeker, more refined and more likely to break if they got dropped.

Today, however, the line has certainly blurred substantially in the middle. Take Xplore’s R12, a fully rugged tablet that smartly converts into a two-in-one powerful enough to be a more than adequate replacement for a desktop let alone a laptop.

Now, whilst the R12 may still look like a heavyweight lining up against a featherweight if put alongside a Microsoft Surface, which would be its most suitable comparison within the consumer realm, it by no means fits the traditional image of a rugged device - i.e. cumbersome, bulky and awkward. It is a sleek looking and excellently engineered device whose lightweight feel belies its robust rugged credentials.

Of course, this is not a one-way street either.

 

"Consumer devices are increasingly likely to have higher certifications that we previously only would have seen in a rugged spec..."

 

Consumer devices are increasingly likely to have higher certifications that we previously only would have seen in a rugged spec sheet.

Take for example Samsungs current flagship smartphone the Note 8.

Not only does have an impressive 6GB RAM on an 1.7GHz octa-core processor making it an exceptionally fast device, but it also has its own Dex docking station that essentially turns it into a mobile desktop by allowing you to plug into a TV or Monitor via HDMI - something that could be hugely useful for the field engineer who needs to give a presentation whilst on the road for example.

Then when we add into the equation that the Note 8 is certified at IP68 (meaning it is essentially impervious to both water and dust ingress) could an argument could be made for it being a strong device for field service use.

We recently hosted a fieldservicenews.com exclusive webcast with rugged specialists Xplore Technologies and the topic of what defines rugged manufacturers against this backdrop of blurring lines was a major talking point within the session.

Our panel consisted of Steve Priestly and Cliff Adams, VP International Sales and Product Marketing for Xplore respectively as well as Bob Ashenbrenner, President of Durable Mobile Technologies.

 

"With the lines beginning to blur between rugged and consumer mobile devices, is there more to why an organisation should choose to work with a rugged manufacturer other than just the specs these days?"

 

The question was put to the panel ‘With the lines beginning to blur between rugged and consumer mobile devices, is there more to why an organisation should choose to work with a rugged manufacturer other than just the specs these days?’

Priestly was the first to respond “I think you raise a very good point in terms of the lines becoming more blurred. At Xplore, where we have more than 20 years worth of experience, we would say that maybe the words are blurred but the principals of building a rugged device are not blurred at all - they a very common.”

“We have built rugged devices from the ground up, with the most rugged of architectures to support all the elements of rugged mobile working.”

 

"I think one of the areas that people get most confused is IP68 - well what does that mean in a rugged environment?"

 

“I think one of the areas that people get most confused is IP68 - well what does that mean in a rugged environment?”

“What is most important in the enterprise environment is for us to be able to demonstrate that we are rugged, we are classified in the industry standard specifications but our product still has all of the appropriate I/O, accessories and capabilities to be able to run the workflow of the mobile worker.”

“That has to be the same across all of our devices and whilst we may share some common specifications with a consumer manufacturer,  but that doesn’t mean they are as rugged as the products we provide”

Ashenbrenner also concurred with Priestly’s sentiments further adding:

“A lot of consumer devices have very little I/O [input/output]and in an enterprise environment having the right amount of I/O  is really, really important,” he explained.

“Now, without I/O it is fairly easy to make an IP68 device - there are very little openings for water or dust to get in. So these consumer manufacturers have sort of stumbled upon an IP68 rating and have thought they that’s one of the things the rugged guys talk about, let’s declare that we’re rugged -well that’s not how it works.”

 

"IP68 is just one feature. It doesn’t cover knocks, it doesn’t cover drops, it doesn’t cover other abuses such as vibrations and such..."

 

“IP68 is just one feature. It doesn’t cover knocks, it doesn’t cover drops, it doesn’t cover other abuses such as vibrations and such. So my advice to field service organisations is don’t be fooled by that one rating they accidentally got when that is only part of the bigger picture.”

“One thing I would just add is that one thing the IP rating doesn’t give you in terms of dealing with a rugged environment is the ability to operate within a wide range of temperatures,” Adams commented.

“If you are going to be operating out direct sunlight or if you are going to operate in a location where there are extremely cold climates, that wide temperature range is something that you will not find on a consumer device. If you need to perform in such conditions then a rugged device has to be the obvious choice there.”

“This is especially true when it comes to tablet devices, where you are running full feature software applications that consume a lot of processing power. A sealed consumer tablet will not have a fan, something which is critical to maintaining the full power of the CPU in those hot environments.”

[quote float="left"]The Xplore range of tablets have internal fans that are isolated from the elements so they can still  have a high IP rating whilst being able to dissipate that heat and maintain that processing power[/quote]“For example, the Xplore range of tablets have internal fans that are isolated from the elements so they can still  have a high IP rating whilst being able to dissipate that heat and maintain that processing power.”

It is of course, these often nuanced details that can get overlooked when we are looking at spec sheets, especially when as is often the case, the purchasing decision is largely driven by either by members of the field service operations team who may not have the deep technical knowledge to be able to fully compare the two devices, or alternatively IT professionals who perhaps do not have the operational experience to fully understand the complexities of the various operating environments the devices will be utilised within.

Another major difference between rugged manufacturers who are serving the enterprise market and more consumer-focused manufacturers is the frequency with which they update their devices - with consumer devices generally going through an upgrade cycle far more regularly than a rugged equivalent.

Whilst, in the consumer world this ongoing arms race between manufacturers to produce devices that can outperform their competitors is one sense advantageous in that it drives continuous innovation and technological advancement, in an enterprise environment such constant change can actually be a negative.

 

"One of the key requirements for a device used by field service engineers is reliability..."

 

One of the key requirements for a device used by field service engineers is reliability - so it is, therefore, essential that the devices a service organisation deploy to the field are stable.

In addition to this in today’s world where security of data is paramount and the threat of cyber attacks something all companies must be vigilant Mobile Device Management (MDM) is a major consideration - something that can become a significant headache for companies that are tied into the faster pace cycle of device and OS upgrades of consumer devices.

So the longer shelf life of rugged devices designed specifically for use within a business environment is another major plus in their favour - but even then there must be a balance between stability and ensuring the tools you provide your field engineers with are sufficiently up to date to deal with the demands of the software they are using.

This leads us to a critical question - just how long should we wait before we roll out new devices to our field workers? And how should a field service organisation assess the decision of whether it is time for them to invest in new devices for their field engineers?

Most companies when they are deploying tablets and begin a project they think about a three-year time frame,” Ashenbrenner states.

 

"Three years is a good time frame to roll to new technologies and have an R.O.I (return on investment). However, the real issue is 'does it still do the job?'"

 

“That is because three years is a good time frame to roll to new technologies and have an R.O.I (return on investment). However, the real issue is 'does it still do the job?' and most of that comes down to software.”

“If the original device has enough processing power and memory to handle the software you are using - especially the updates that are pretty frequent, and also when new capabilities are being added that is when you tend to see people saying ‘hey this is still working, I can upgrade my software’ and this is when you can see the longer uses in the field - sometimes five years, sometimes even seven years,” he adds.

Adding a slightly different take on the question Priestly commented:

“To my mind, there are a few different things that come into the equation. Firstly, there is a financial discussion which says how long will the equipment be depreciated within the companies financial statements - and typically three years is a good answer to that. It fits well with other technologies and it allows them to look at it in a common way”

“But that doesn’t describe how it is used in the field. The challenge that Xplore faces is that things will dictate outside of this what the life cycle of the device is. It could be something as simple as data security that causes a change in equipment to drive an additional set of features.”

“Or alternatively it could be that everything is fine after the three years and they are getting free use from the devices for as long as they need to.”

 

"One of the things that Xplore would point to is that is in our longest running platform we reiterated the device to stay on top of the processing and memory requirements of the device and were able to do that for seventeen years..."

 

“One of the things that Xplore would point to is that is in our longest running platform we reiterated the device to stay on top of the processing and memory requirements of the device and were able to do that for seventeen years.”

“That is seventeen years within a single eco-system that an enterprise could get around. Yes, the device changed over time, but it remained the same form factor and enabled an enterprise to be stable within its use.”

“Whether that enterprise is a government facility, military would be a good example or perhaps a pharmaceutical clean room environment where the absolute top end of the specification is required - that is the type of thing that Xplore looks to - being on top of the changes in terms of the technical and customer requirement, whilst being able to provide stability for a long period of time both in our service and in our product capabilities.”

“That is a great point and something that must be considered,” Adams adds.

“Especially when we see consumer devices that come out that each have a slightly different form factor because they are really going for those aesthetic changes. A rugged device is really tailor-made for enterprise environments.”

 

"A rugged device is really tailor-made for enterprise environments..."

 

“Change isn’t necessarily good in such environments, stability is something can enable companies to keep costs lower and devices deployed longer and at Xplore, we understand that so we build our chassis so they can be upgraded over the years but still maintain common accessory eco-system over those generational upgrades.”

This is, of course, another hugely important consideration that is often overlooked within discussion around device selection for field service organisations - the range of accessories available. Most rugged manufacturers provide accessories such as vehicle mounts that are designed specifically to fit their devices and to ensure that issues like vibration don’t impact upon the device.

By maintaining the same form factor and chassis, rugged manufacturers such as Xplore are able to help their clients avoid the additional costs of new accessories each time they invest in new devices - something that can stack up to quite a considerable additional cost if you have a large field workforce.

Something that we’ve discussed a number of times in Field Service News that was also reflected within the webcast was that companies must have an understanding of the workflow of their engineers and then select their devices accordingly.

However, for many organisations there will be varying different roles being carried out within the field so how should field service organisations decide just how many different devices and form factors they should deploy to find a balance between equipping their varying types of field workers with devices suitable for their requirements and having to types of devices deployed - which again can cause problems when it comes to MDM?

 

"It is important to have the right device for the person and for the right workflow..."

 

“It is important to have the right device for the person and for the right workflow,” comments Adams.

“At Xplore, we offer an array of device form factors, but also within those form factors, we have an array of different computing options. So you could get an entry-level CPU if that works for the user and they don’t need a top of the line processor we can offer that, but then we also offer within the same form factor high performance options or even different I/O options - so there is a way an organisation can still manager a smaller number of devices and still provide a choice to the user so they are putting the right device in front of the right worker at the right time.”

“To add to that one of the things that should also be considered is the definition of the software to support the workflow you are trying to automate in the hands of the worker,” Priestly adds.

“That will dictate the type of data that needs to be input, the type of data that needs to be viewed and the type of data that any business information is driven from often dictates the type of device that will need to be used.”

“If there is a lot of form filling or repetitive tasks such as barcode scanning a handheld fits that bill very well. Then as you move between that and a larger device such as our twelve-inch tablet very much that is dictated to by the workflow itself.”

“Let me add a few real-life examples,” added Ashenbrenner as the discussion drew to a close.

“In utilities, you will tend to see all of the repair workers will use one type of device but meter workers and meter repair is a whole different area and so you will likely see handhelds being used in that situation.”

 

"Where beat officers on the front line might be using a tablet, detectives in the same police department tend to gravitate towards two-in-ones..."

 

“Another example might be in law enforcement, where beat officers on the front line might be using a tablet, detectives in the same police department tend to gravitate towards two-in-ones.”

Indeed, Ashenbrenner’s final point in the discussion is an important one that highlights just how many variables must be considered when selecting the right devices for your field workforce.

However, one thing that remains clear is that whilst on the surface it may appear that the lines between rugged and consumer devices are blurring, the reality is that for companies seeking to maximise their R.O.I from the mobile devices they use, there are far deeper considerations than headline tech specs - and this is where working with dedicated manufacturers such as Xplore can truly bring additional value to the table via their understanding and insight of how organisations will be utilising the devices in the field, how to extend the life of those devices where possible and of course how to roll out new devices whilst avoiding significant disruption to day-to-day field service operations.

The ball for the time being then remains firmly in the rugged court.

 

---

Be social and share...