The Uptime blog

A few years ago I met with a customer service executive (Bill) from a well-known office equipment manufacturer. Over the course of several months we had a really good discussion regarding the best ways to improve field service. During this time Bill shared the service statistics for one of his products, which reflected the data I’ve seen in many other industries. What surprised me was the way he interpreted these statistics. Here’s what he found:

1. Over an 8-month period, one product line received 5591 service calls
2. Those calls were the result of 423 different fault codes
3. The top 20 fault codes accounted for 50% of all service calls
4. The other 403 fault codes (95% of total) were responsible for the rest of the service calls
5. Each of those 403 fault codes occurred no more than 51 times. (In fact, 364 fault codes—86%—were tripped 20 times or less.)

Bill told me his company was trying to improve service by focusing on the most common problems—the top 20 fault codes—but he thought this was the wrong approach. He believed the top 20 problems didn’t pose an issue for most technicians because they repaired them so often. It was the other 50% of the calls that made life difficult.

The key to understanding Bill’s perspective can be found in the last two bullets—half of the service calls involved fault codes that occur less than 1% of the time. (In fact, 140 service calls involved fault codes that only occurred once.) Therefore, field technicians got little or no experience repairing these rare problems. Further analysis showed these service calls often took more than two hours to resolve and were at the heart of scheduling delays and blown response times.

Bill felt that the real key to improving customer service was not faster repairs for well-known problems but a more consistent approach to all problems. He said that once he changed his focus from 20 fault codes to 423, he realized the answer was not to streamline call handling, travel, part lookup or closeout but rather it was improving information access in general. If his service teams had an integrated parts and service information system they could address any fault code efficiently and consistently.

Recently, Bill told me his company never did act on his advice and he subsequently left the firm. He realized that a slick new call-center gets more political traction than a system to support field service engineers. After all, a tour of the call center was a great selling tool during customer visits. Unfortunately, at the end of the day it’s those same customers that suffer the results of this decision.

Manufacturing Business Technology recently announced its MBT 2008 Innovation Insight Awards, and among them was an Honorable Mention for Advanced Technology Services (ATS), a company that provides maintenance and repair services for manufacturing plants.

ATS received the kudos because they deployed Knowledgebase—their own proprietary database of processes, procedures and best practices for their field service technicians. What is interesting is that much of the content in this custom application came from the technicians themselves. Knowledgebase helps ATS to fix equipment faster, thereby reducing their customers’ downtime.

Here at Enigma we agree wholeheartedly with capturing and reusing technical expertise, which is why our products such as InService MRO, InService EPC and the Enigma 3C Platform all include a feature called eNotes. (For a mini product demo of this feature, see our August 15 podcast post.) 

While service manuals may contain some previously established best practices or proprietary techniques, eNotes allow mechanics to insert new comments connected to the original content. This lets companies capture feedback on-the-fly and also gives context to the comments because they are linked to the specific task that was being performed. eNotes are also available to other users (based on authorization/distribution rules). This makes it easy for other mechanics to learn from their peers and for OEMs to update documentation so that it reflects real world experience.

But it’s not just eNotes that make Enigma products useful; our products aggregate and deliver all product content in one place, in ways that streamline the entire maintenance execution process. The ability for service technicians to use a single application to pull relevant OEM information, whether parts information or service manuals, from multiple sources, is a tremendous advantage in the field or the service depot. The description of ATS’ Knowledgebase is impressive, but it sounds like an expensive solution. What is more impressive is that, today, any company can provide similar capabilities using Enigma’s out-of-the-box solutions.