The importance of establishing a use case for asset data

In this edition of the Field Service News Think Tank Sessions, our focus was on digging deeper into a finding within a recent FSN Research study that revealed that 57% of field service companies surveyed stated that while they were able to access asset data, they felt they were not leveraging that data effectively.

 

As always in our Think Tank sessions, this initial starting point for the discussion led down many interesting avenues of debate, all of which are summarised in the executive briefing report currently available for a limited time on our forever-free FSN FREE subscription tier.

 

In this feature, based on a section of that report, we focus on the importance of establishing a clear use case for the application of data within the service operation.

 

Indeed, when discussions around the use of data within the field service sector first raised their head, everybody in the industry rushed towards embracing a holy grail of data-driven predictive maintenance fueled by the emerging potential of the IoT. However, as we’ve worked towards becoming more data-driven, we see the importance of establishing a clear use case for data applications and keeping things somewhat simpler than we perhaps first imagined…

 

As Sumair Dutta, Senior Director, Product Marketing – Customer and Market Insight, ServiceMax, explained:

 

“I think when we started as an industry looking at data, many companies talked about wanting to build predictive models. There was a common thread of discussion across the sector around generating predictive insights, utilising predictive analytics and IoT.

 

“However, for many companies who did some great work in this area, still they often found that while the model did its job, the scalability or the impact of that perhaps wasn’t as powerful as was hoped in that they, for instance, able to sell predictive solutions as well as they may have anticipated at the outset,” Dutta added.

 

“We typically have found that use cases that might be slightly simpler, whether it’s a commercial use case, such as a sales model or even a specific customer use case, where customer facing data and customer insights are generated – from a customer experience perspective these might be more impactful.”

Want to know more?

This content is available exclusively for FSN PRO/PRO+ members. If you already have a valid membership but cannot see the watch now button below, please ensure you are logged in to access this content. 

Not yet subscribed? Instantly unlock this content and over 600+ hours of industry-leading education with FSN PRO now! 

 

SIGN UP TODAY! Use the code TRIAL9 to claim an incredible introductory offer for your first month for just £9 (regular price £45) 

"Our approach instead was to recruit internally and have somebody we could train to become a data scientist who knew the machines and the data from scratch" - Daniel Kingham, Elekta

What is often overlooked in the quest for clever applications of data is the pragmatic approaches that underpin so much best practice within field service operations.

 

“The trouble is that in our world a lot of what we need is transactional data at the point of need. For example, we all send people to addresses,” commented Mark Homer, Managing Partner, Field Service Associates

 

“What’s interesting is when you look at an asset record, it will state where an asset is located. When you sometimes look at the work instructions provided on the work order, the actual journey travelled and where the engineer parked compared to where the actual asset is located are often entirely different.

 

“I think that’s another important challenge in that there is a granularity of the data needed by the persona at the point of need and this is sometimes very different to what the corporate view or the transactional view is at the ERP level. From a scheduling optimisation perspective, the most valuable aspect is that granularity, which can really be crucial in improving marginal responsiveness.”

 

Homer’s point is astute; however, sometimes, operating towards a use-case scenario doesn’t always mean working towards a more straightforward path. As Daniel Kingham, Vice President and Head of Service Innovation and Design, Elekta outlined, it can also be a more complex process of evolution and learning.

 

“In our scenario, we didn’t go towards the simpler use cases, perhaps we should have, but we took a different approach of realising that there was gold in our data, but our machines are incredibly complex – they’ve got many, many moving parts,” Kingham explained.

 

“Because of this complexity, we were training third parties on how machines work, to understand the data. So our approach instead was to recruit internally and have somebody we could train to become a data scientist who knew the machines and the data from scratch. And that’s what led us down the path we followed.

 

“We took this route as a proof of concept. We hired somebody with the view that they try this for one year, and if it’s ultimately unsuccessful, then we’ve learned something else, but they won’t be let go. Six years later, that team is now five strong, and we have automated everything they have developed over time. Today, they continue to do new creations, and we automate and use AI to evolve what they start,” he added.

 

“However, it was all about getting the right skill set and people that understood the data that enabled us to move forward rather than starting with mostly anomalous cases.

"Data for the sake of data is no good to anybody. But the data that gives you insights and insights that are valuable to your customer is where the rubber meets the road..." Dave Hart, Field Service Associates

“Interestingly, with some of the relatively complex but manual activities, we tried to automate them with AI initially, and that was successful to a certain extent, but that also forced us to reflect that some of this can be done a lot more simply than we had initially approached it. For example, we’ve been able to automate using people with Python skills rather than having full-on AI specialists. That’s been quite a steep learning curve in that over the last year, we were expecting a very skilled part of the organisation to help us, we didn’t get the help we needed, and we realised we could do a considerable amount ourselves.

 

“We’ve become good at fail, fail fast, and then try something different,” Kingham continued.

 

“Also, we’ve done exactly as a business what Mark [Wilding, ServiceMax] described earlier. We’ve now put in somebody who’s accountable for data governance, and their primary remit isn’t really the day-to-day go-to person for data governance; instead, they are the person that you take the continuous problems to, and they help find the root cause.

 

“However, that’s been missing across the organisation on the broad level, whereas my team have been the people that determine what data they want from something and how they will use it. So they’re both the consumer and the designer, and that’s unique, really unique in our organisation.

 

“We are allegedly a pleasure to work with, with our BI teams, for example, because we know the constructs of everything that we’re touching. We know the foibles, and we know all of the ways the data is formed. Whereas in other parts of our organisation, we’ve got people that want the answers and when they find the data is inconsistent, they give up and walk away.

 

“That’s the challenge that we’ve had in my team, we’ve had to actually establish ourselves as part of the data strategy and help drive it rather than being somebody that just wants the outsider view.”

 

Reflecting on Kingham’s description of the journey Elekta had undertaken, Dave Hart, Managing Partner, Field Service Associates, commented:

 

“Data for the sake of data is no good to anybody. But the data that gives you insights and insights that are valuable to your customer is where the rubber meets the road for me.

 

“That, for me is what makes you [Elekta] really sticky as a solution, because I know you’re in a very highly regulated but highly competitive marketplace and anything that adds additional value like that is really gold.”

 

It certainly seems that the approach of understanding what it is you are trying to achieve through the application of digital transformation and the use of asset data, whether that be improving a specific aspect of service operations or even a customer-specific solution, is likely to yield better results than broader all-encompassing projects, where we often find ourselves collecting data for the sake of it.

 

If you wish to read more from the group on how the challenges, benefits and barriers to effective use of asset data then download the full executive briefing now (available for a limited period on our forever free subscription tier FSN FREE)

Want to know more?

This content is available exclusively for FSN PRO/PRO+ members. If you already have a valid membership but cannot see the watch now button below, please ensure you are logged in to access this content. 

Not yet subscribed? Instantly unlock this content and over 600+ hours of industry-leading education with FSN PRO now! 

 

SIGN UP TODAY! Use the code TRIAL9 to claim an incredible introductory offer for your first month for just £9 (regular price £45) 

 


 

Many thanks to our Think Tank members present during this session. 

 

  • Sumair Dutta, Senior Director, Product Marketing – Customer and Market Insight, ServiceMax
  • Mark Homer, Managing Partner, Field Service Associates
  • Rajat Kakar, Managing Director, QuickWork EMEA
  • Chris Hird, Editor, Field Service News
  • Dave Hart, Managing Partner, Field Service Associates
  • Daniel Kingham, Vice President and Head of Service Innovation and Design, Elekta
  • Mark Homer, Managing Partner, Field Service Associates
  • Mark Wilding, VP Global Customer Transformation, ServiceMax
  • Terence Horsman, COO, Orca Service Technologies/MCFT
  • Clinten van der Merwe, EMEA Service Director, Smiths Detection

 


 

All members of the Field Service Think Tanks are speaking from their own personal opinions which are not necessarily reflective of the organisations they work for. 

Close