ARCHIVE FOR THE ‘service-management-technology’ CATEGORY

Kris Oldland, Editor-in-Chief welcomes back Kevin McNally, Sales Director of Asolvi as they look through five key considerations to factor in when trying to build a case for investment within a field service management solution including, definable return on investment, health and safety compliance, increasing customer engagement, reducing staff turnover and avoiding a competitive disadvantage....

 

---

Is building a case for investment in FSM a key topic for you?! There is a full white paper on this topic available to fieldservicenews.com subscribers. Click the button below to get fully up to speed!

---

Sponsored by:

---

Data usage note: By accessing this content you consent to the contact details submitted when you registered as a subscriber to fieldservicenews.com to be shared with the listed sponsor of this premium content who may contact you for legitimate business reasons to discuss the content of this content.  

---

 

Be social and share... 

A recent survey has revealed that 88% of field engineers see no opportunity to progress in their careers.

This less than favourable statistic comes from specialist field engineering recruitment consultancy, Concept Resourcing’s latest Field Engineering Salary and Engagement Survey where they delved into average salaries across the industry as well as fluctuations and expectations in pay, employee happiness and ranked the most desirable perks and benefits.

Engineer’s reports of a lack of career progression were backed up by the fact that 81% of Concept’s respondents reported having more than 10 years’ experience in the industry, and yet 75% of them were still in the same role. Not only does this pose a problem for those who are feeling stagnant in their career, but it does very little to help draw the next generation of engineers into the sector, with progression seemingly curbed.

Between an ongoing battle with the STEM skills shortage and burgeoning concerns over an ageing workforce, some would say the field engineering industry has its work cut out when it comes to attracting new talent. When we look at how the sector has changed in recent years, from advancements in innovation - such as automation and augmented reality, to a natural increase in customer demand for instant resource in the digital age - it comes as no surprise that the sector is crying out for new talent.

Aside from attracting individuals into the industry, retention of existing skilled employees is equally as crucial. Particularly to facilitate knowledge transfer to new starters to ease the pressure on the ageing workforce. With that in mind, it comes as something of a surprise that the survey revealed that 44% of field engineering professionals are feeling undervalued at work.

 

Retaining your field service engineers

It’s easy to assume that field service organisations would be desperate to retain their existing workforce and would be bending over backwards for them as a result. This may well be the case, but if employers are concentrating their efforts in the wrong places – their engineers simply won’t reap the benefits.

Of course, salary is always going to be a big factor to employee happiness, but with a whopping 79% of field engineers stating that they were dissatisfied with their salaries, the industry may well have a problem on its hands.

 

"Just 9% of those who requested a pay rise were successful, and of those, 62% were still dissatisfied with their salaries, an indication that perhaps the salary increases weren’t significant enough..."

 

Just 9% of those who requested a pay rise were successful, and of those, 62% were still dissatisfied with their salaries, an indication that perhaps the salary increases weren’t significant enough.

A potential reason for this could be the commoditisation of traditional field engineering sectors and the skillsets of engineers becoming increasingly focused on replacement over repair, meaning salaries have been driven down.

It seems as though the sector as a whole is missing the mark when it comes to giving their workforce what it wants, not through lack of trying – but simply through not knowing what they truly value where non-financial benefits and rewards are concerned.

Thankfully for employers, it’s not all about money. Feeling valued at work can overshadow a less than desirable salary. However, it’s worth noting that it works both ways, 80% of those who said they didn’t feel valued at work were actively looking to leave the company within the next 2 years.

 

Making your workforce feel more valued

Whilst salary naturally came out as the most important factor when choosing a job, company culture-related factors such as job security, work-life balance and a good work environment all followed.

When asked which benefits made the most difference to their happiness at work, field engineers ranked having a generous annual leave package, access to a good pension plan, a company vehicle and fuel card as their top priorities.

We saw a direct link between employee happiness and training. While only 6% of respondents felt that they didn’t have the necessary skills for their role, the gesture of being supported with personal or professional development clearly had a positive impact. Of those who said they were ‘happy’ and ‘very happy’ at work, 94% had been on a training course in the last 12 months.

Dan Sholl, Concept Resourcing’s Business Development Director for the field engineering division had this to say, “The results of the salary survey have been really eye-opening, to say the least. It’s clear that the sector has some work to do when it comes to both employee retention and attracting new talent.”

“Not every organisation has the budget to be able to provide regular substantial pay increases, but there’s a lot that can be done to make field engineering employees feel valued and happy at work. In our experience as a field engineering specialist recruiter, we often advise our clients on the significant impact that things like regular training can have on engineers and their happiness. Evidently, it’s these additional benefits and perks that can make all the difference when it comes to bringing the next generation of field engineers into the sector.”

If you’re interested in learning about average salaries in field engineering, or if you’re working on your hiring strategy for the year and would like some extra insight, read the rest of Concept’s Field Engineering Salary and Engagement Survey here.

 

---

Be social and share... 

Adopting IoT as part of the greater service and business environment involves keeping up with industry changes as they take place. That means incorporating better measures when needs arise in any business area and keeping cost-effective solutions in mind for the future progress of the company as a whole...

Already, 76% of companies are using IoT data analytics to establish product and/or process quality imperatives. Their decision makers can analyze IoT data to improve solution recommendations, feedback on installations, demonstrations, specific services, and others.

IoT also serves as a signifier for opportunities to improve more processes, such as identifying popular products and managing inventory.

Respondents to a recent research project undertaken by WBR and commisioned by Astea believe data should be usable in decision making at a variety of business levels. In every case, a majority of companies have either adopted IoT for specific business functions or plan to do so in the next 24 months. But companies prioritize customer-facing initiatives—service, products, and satisfaction—over internal functions such as business projections and aligning service data with financials.

 

---

Is IoT adoption a key issue for you?! The full white paper is available to fieldservicenews.com subscribers. Click the button below to get fully up to speed now! 

---

sponsored by: 

 

  

---

Data usage note: By accessing this content you consent to the contact details submitted when you registered as a subscriber to fieldservicenews.com to be shared with the listed sponsor of this premium content who may contact you for legitimate business reasons to discuss the content of this content.  

---

 

Customer Satisfaction & Loyalty:

73% of companies have incorporated IoT (42%) or plan to do so within 24 months (31%) for the purpose of customer satisfaction and loyalty. More companies have incorporated IoT for this purpose than for any other measured in the study.

With connected data, companies are able to understand and fulfil customer demands better thanks to improved communication. In this way, minor technological improvements can be made without delay or other consequences.

 

Service Processes & Optimization

Respondents agree that connected data and IoT have helped streamline processes across departments. By leveraging IoT data, they can measure efforts for overall growth through set channels, be they internal or service-driven.

Now, 41% of companies have incorporated IoT for process optimization, a close second to customer satisfaction and loyalty. Thirty-six percent have already incorporated IoT with service processes; more companies plan to do so within 24 months (37%) than with any other business function measured.

 

Product Uptime

Companies’ attention to customer experiences carries over to product support, where one respondent cites “notable improvements” to uptime in both industrial and consumer-driven channels. One healthcare executive says IoT helps them sustain products “during times of higher demands, especially due to the fact that these are used during medical procedures.”

More than one-third of companies have incorporated IoT for product uptime (34%); more than one-quarter of companies have plans to incorporate IoT with product uptime (30%) within 24 months.

 

Business Projections & Decisions

IoT data can be applied to various business requirements and provide essential statistics to support managerial functions. Derivations from reliable signals allow for better judgements when making business projections and decisions.

Over one-third of companies have incorporated IoT for business projections and decisions (35%); more than one-quarter of companies have plans to incorporate IoT with business projections and decisions (27%) within 24 months.

 

Predictive Maintenance

Respondents’ ambitions for better response to maintenance needs extends to real-time automated reporting, a better understanding of their products’ “general maintenance structure,” and even signals for customers to be proactive—to seek out maintenance themselves.

Several respondents cite their use of predictive reporting for scheduling, sustainability, and research methods, among others. Only 32% of companies have leveraged IoT for predictive maintenance; however, 29% plan to do so within 24 months.

 

Aligning Service Data with Financials

Fewer companies have incorporated IoT to align service data with financials (26%) than any other business function in the study. But the data suggests this is a growth area. More companies (61%) are either planning to incorporate IoT in this way within 24 months or are interested in incorporating IoT in this way than with any other business function.

Despite the prioritization of functions that drive customer success, it is in business projections, business decisions, and aligning service data with financials that companies take an increasing interest in incorporating IoT.

At least one-quarter of companies have already incorporated IoT for each of these purposes. Have you?

 

---

Want to know more?! The full white paper is available to fieldservicenews.com subscribers. Click the button below to get fully up to speed now! 

---

sponsored by: 

 

  

---

Data usage note: By accessing this content you consent to the contact details submitted when you registered as a subscriber to fieldservicenews.com to be shared with the listed sponsor of this premium content who may contact you for legitimate business reasons to discuss the content of this content.  

---

  

Be social and share... 

Artificial Intelligence has increasingly become a key discussion in all industries and its impact in field service management is predicted to be hugely significant, but how should field service organisations leverage this powerful twenty-first-century technology? In the first of a two-part feature, Marne Martin, President Service Management IFS, offers her expert insight... 

 

 

---

Is AI a key topic for you?! There is a full white paper on this topic available to fieldservicenews.com subscribers. Click the button below to get fully up to speed!

---

Sponsored by: 

 

 

---

Data usage note: By accessing this content you consent to the contact details submitted when you registered as a subscriber to fieldservicenews.com to be shared with the listed sponsor of this premium content who may contact you for legitimate business reasons to discuss the content of this content.  

---

 

Artificial Intelligence (AI) will impact every industry and every business discipline—including field service management. But how quickly will practical solutions be available that enable the typical medium to large field service organization to take advantage of AI? And by practical solutions, I mean AI that delivers knowledge efficiently, processes solutions to complex data sets, and automates repetitive activities to allow human workers to focus on personalized service, solving complex problems and escalations, i.e. what people do best.

In some cases, these easily applied solutions are still on their way to market. In three specific areas, however, practical AI applications for field service are already commercially available as proven, commercial off-the-shelf software delivering real business value.

 

AI For Customer Interaction

First impressions matter. And unfortunately, the first interaction a customer has with your service organization often involves several missteps. Chief among these are long wait times on hold due to high call volumes. And then, as a customer attempts to reach out through multiple channels including email, chat and phone, the resulting data stream goes into separate siloes that are disconnected from each other, resulting in disjointed communication.

 

"Today, AI solutions can solve both these problems, but it requires more than “just” chatbots..."

 

Today, AI solutions can solve both these problems, but it requires more than “just” chatbots. Commercially available AI software that ties into chatbots is capable of learning which answers posed in a chat are appropriate for each question and automating a significant majority of chat interactions. A chatbot can be taught to answer commonly encountered questions, like inquiries about when a technician is scheduled to arrive. Of course, at some point, the AI chatbot may get stuck when personalized service is required, and a human agent takes over the discussion thread without missing a beat. This should be seamless not only to the customer but for the internal customer service, ticketing and support systems as well. The chatbot—regardless of whether driven at a given moment by AI or a human agent—should update the same customer record as other channels including social media, phone and email.

And from interactions, the AI functionality learns from answers provided by human agents and gets better and better at answering questions through learning processes. A truly advanced AI chatbot will also seamlessly hand off the chat to a human agent when the extent of its learning is overtaken. Only then can the entire customer experience be unified and consistent, even with a static number of agents handling a rapidly growing fluctuating volume of customer interactions.

AI-based chatbots, for instance, can enable a good agent to handle up to five or more chats at a time. It can capture Facebook messages and tweets and direct them to an agent or to AI for intervention. AI alone can handle, typically, between 50 and 60 percent of requests, freeing up human capacity or lowering staffing levels required to handle a given volume of activity.

 

Enables Management By Exception

In the case of AI applications for the service organization, a primary driver for ROI is that it enables humans to manage by exception. A high volume of activity can be automated, and humans intervene primarily when a situation falls outside the business rules or logic built into service management software. AI doesn’t eliminate the need for human interaction—it makes the human interaction more focused on what humans do best—handle escalations and complex decision making for unique cases.

At one IFS customer, an AI chatbot handles about 50 percent of interactions— primarily those reaching out to cancel their service after a free three-month trial period. Interactions cancelling a free subscription are handled entirely through automation. But if a longer-standing customer is cancelling their service, the interaction gets routed to an agent dedicated to saving the account.

Some interactions are by default easily handled by AI. If 30 percent of inbound contacts are requesting information on the arrival time of a field service technician, it may be possible to automate 90 percent of that 30 percent of contacts. But it is also important to consider the demographics of the customer base. Millennials are more likely to communicate via chat or social media, so if a significant percentage of customers are under 40, heavier reliance on chatbots and AI may help you increase engagement by streamlining your customers’ preferred method of interaction.

 

"Management by exception is also more successful when an AI application has access to extensive information about each customer..."

 

Management by exception is also more successful when an AI application has access to extensive information about each customer. So full integration with enterprise resource planning, field service management and other enterprise tools is essential. AI tools can be more effective if they have more rather than less information on the status of the customer’s account, including their maintenance or service history and warranty or service level agreement entitlements.

Integration between an AI chatbot, email, voice, social and enterprise applications is important for another reason. It enables one version of the customer record. Lacking this, a customer can send an email, and get no response. They send a direct message through Twitter. Then call and sit on hold. Then initiate a chat. All these interactions may not appear in a central customer record, but there have been three attempts to contact the company. Right from the first contact by email, the clock started ticking on a service level agreement.

Full integration can also enable a customer service team, once a customer request is resolved, to close off all queuing activations at the same time for the various contact methods associated with a customer case. Failing this, a service organization may spend a significant amount of time chasing customer requests that have already been resolved.

 

---

Want to know more? There is a full white paper on this topic available to fieldservicenews.com subscribers. Click the button below to access it instantly...

---

Sponsored by: 

 

 

---

Data usage note: By accessing this content you consent to the contact details submitted when you registered as a subscriber to fieldservicenews.com to be shared with the listed sponsor of this premium content who may contact you for legitimate business reasons to discuss the content of this content.  

---

 Be social and share... 

John Hunt outlines why when it comes to digitalisation, the focus should be on the end goals, not the technology...

There is a common thread being pulled by executive boards across the globe at the moment both in the field service sector and far beyond.

That is, of course, digitalisation.

In my role here at Astea, it’s a topic that our customers and new prospects are keen to talk to us about – almost every company I’ve spoken to in the last 12 months has broached it in one form or another.

However, there is a fundamental point I believe is often being overlooked by companies as they dive head first into weaving the digitalisation thread into their strategy – that is that digitalisation itself should be seen as an on-going process continuously woven in your field service tapestry rather than a one-time project, or a mere stitch in time.

 

An opportunity to redefine workflows

To start, let’s look at what digitalisation shouldn’t be.

Digitalisation shouldn’t be simply taking all of the previous steps your field service engineers used to undertake manually with good old pen and paper and dumping them onto a mobile device. Digitalising their workflow is an opportunity to re-evaluate some of these processes, re-order some things, maybe even remove others entirely all in the spirit of making your customer ambassadors happier and more efficient and effective. That happiness, efficiency, and effectiveness translates into better top and bottom line performance and most importantly, happier and more loyal customers.

 

"Those companies that get the most success from the implementation of a Field Service Management (FSM) solution are those who bring a selection of their engineers into the implementation process..."

 

Invariably, those companies that get the most success from an implementation of a Field Service Management (FSM) solution are those who bring a selection of their engineers into the implementation process. Just like product marketers use focus groups of prospective customers to fine-tune their product offering to maximise demand, so should you leverage a similar approach with your customer ambassadors, also known as the engineers. For example, by speaking with your engineers to understand what elements of your FSM system’s mobile app they use the most frequently, you can ensure that access to the relevant parts of the solution need are easily surfaced within the app.

The same of course also goes for your scheduling solution – digitalisation should be an opportunity to put the information your team needs at their fingertips, quickly and seamlessly to improve both service triage and first-time-fix rates. So who better to ask what information should be where than the folks on the front line that need access to such information each and every day? The happiness through efficiency and effectiveness you will weave throughout the services organisation will pay big dividends not only in the traditional operational sense but also in employee retention and the all-important increased customer loyalty.

 

A journey of continuous improvement.

The concept of continuous improvement is one that many field service professionals are fully aware of, yet all too often it doesn’t get factored into discussions around digitalisation.

Facebook is famously always in ‘beta’ when it comes to its development, and whilst I wouldn’t recommend such a fluid approach to something as mission-critical as field service operations, digitalisation certainly allows us the opportunity to tweak things here and there to find those sometimes hidden incremental improvements that can yield seemingly small efficiencies that stack up hugely in the overall picture.

For example, I recall speaking with one service director earlier this year who explained to me that by implementing a simple keystroke study of his dispatch staff across 3 months they were able to identify some simple yet effective changes to the menu structure of their system which brought some frequently used options to the front of the solution when they were previously tucked away behind a couple of sub-menus.

On an individual basis these changes sped up the dispatcher’s role by just a few seconds each time. However, the overall net benefit to the service organisation was millions of dollars per year as those seconds began to add up across the entire workforce just like a snowball accumulating more and more snow as it rolls down the mountain.

Digitalisation allows us to not only make these changes quickly and easily across a large user base but also to understand how, why and where these changes should be made.

 

Build processes today with an eye on tomorrow.

One final piece of advice I would give to companies embarking on their own digitalisation journey is remember you don’t always need to boil the ocean; digitalisation should be an iterative process.

For example, IoT is the hot topic in field service right now and rightly so as it is set to play a huge role in the future of service delivery. Yet, for many companies a full IoT rollout is cost prohibitive and requires a gargantuan feat of logistical planning.

 

"I’d suggest you don’t even need one asset connected before you start building in the processes of identifying key data you wish to collect – what is to stop your engineers noting certain key data points when performing maintenance?"

 

However, do you need to have every asset in your install base connected before you can start pulling data for analysis to dig out some key trends and insights that could be of value to your organisation and perhaps even more importantly to your customers? Of course not!

In fact, I’d suggest you don’t even need one asset connected before you start building in the processes of identifying key data you wish to collect – what is to stop your engineers noting certain key data points when performing maintenance? You can build the processes and collect the data that would form the backbone of a digitalisation strategy before a single asset is connected, and then introduce automation for these new processes across a much more manageable timeframe.

In doing so you will have already begun to think beyond the realms of what is possible today and begun to consider what can we build now that will improve our service delivery tomorrow.

And this at its heart is what good digitalisation strategy should be all about. There are already some masterpiece tapestries with shiny digitalisation threads prominently featured in the field service world today reaping big rewards with their own teams and customers; these will continue to grow and outpace the industry. The best time to have begun your work of art was yesterday. The second best time is today, so gather your thread and your team to design it and start weaving!

---

John Hunt, is Managing Director, EMEA, Astea, 

---

 

Be social and share...

IX Reach, a leading global provider of carrier services and connectivity solutions, and eStruxture Data Centers, a prominent pan-Canadian provider of network and cloud-neutral data centre solutions are further strengthening their partnership and commitment to providing first-class connectivity, cloud and zero-downtime hosting solutions to major blue-chip networks.

This enhanced partnership with IX Reach complements eStruxture’s strategy to give customers more choice, by offering all the benefits of remote peering to the most popular Internet Exchanges in North America and Europe. Customers can access all major IXPs via a single port and enjoy transit that’s optimised for cost and network routes.

The partnership also demonstrates IX Reach’s dedication to supporting the growth of eStruxture as its market share in advanced network and interconnection services continues to expand in both the Canadian and global business marketplace.

 

"Continuing to set IX Reach apart from other network solution providers is its strong partnerships with major Cloud Service Providers..."

 

Continuing to set IX Reach apart from other network solution providers is its strong partnerships with major Cloud Service Providers: Amazon AWS, Google Cloud Platform and Microsoft Azure. The IX Reach platform enhances eStruxture’s Cloud Connect service, a network and cloud-neutral exchange that allows customers to connect securely, easily and directly from the company’s state-of-the-art data centres to an extensive ecosystem of major cloud service providers, network and application providers, bypassing the Internet and taking advantage of a faster and more reliable option for their cloud strategies.

“Our partnership with IX Reach is hugely valuable to us and augments our ever-growing ecosystem of carriers and cloud services. Our customers are able to avoid open networks by connecting directly to hyper-scale cloud providers and benefit from increased speed and security and lower latency,” says Todd Coleman, CEO of eStruxture. “The leading elastic interconnect platform provided by IX Reach enables customers to securely access major peering points and a rich portfolio of products and services such as hyper-scale cloud providers, SaaS providers and partners, via a single connection.”

“We are thrilled to continue working closely with eStruxture Data Centers,” commented Simon Vye, CEO of IX Reach. “IX Reach and eStruxture started their partnership in 2015; since then, both businesses have grown and evolved to provide their customers with world class services and support. We’re looking forward to building on the success of our partnership in the future. “

From eStruxture’s facility in Montreal, IX Reach is well-equipped to support any network with its national and global expansion, regardless of size.

---

 

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...