Duke Medicine's Ted Boyse (left), together with Matt Fahnestock of Columbia Pipeline Group (center) and Deloitte's John Hagel III discussed the importance of data analytics and metrics at this week's Minds + Machines 2015.
The importance of data collection was also discussed by Matt Fahnestock, senior vice president and chief information officer of Columbia Pipeline Group. Access and analysis of data on their 15,000 miles of pipeline is what keeps their business moving, Fahnestock said.
Two years ago, Columbia partnered with GE to develop data analysis and decision support tools to boost reliability, manage risk and prioritize operations of its pipelines.
"With our GE Integrated Pipeline Solution (IPS), the likelihood of failure and consequences of failure, using both static and dynamic factors, can be displayed, as can risk and leak analysis. Operating pressures, historical and active work orders, overall risk rating and how risk has changed over time are all important metrics."
Make the invisible visible
With a step back from specific industry examples, John Hagel III, co-chair of Deloitte Consulting's Center for the Edge strategic research and analysis group, provided a broader context of this need for data, analytics and appropriate metrics. "With intensifying competition, accelerating pace of change and extreme events, it's not a choice. If we don't apply this technology, we will be marginalized," he said.
Much of operations' time and effort are focused on managing exceptions to the routine, such as pipeline leaks or missing inventory, Hagel said. "The analytical ability to predict when an exception is going to happen and to tell people what to do beforehand can lead to performance improvements. Finding these patterns of exceptions in the data will reduce them."
Hagel also noted that to see and understand the frequency of exceptions helps facilitate the redesign of operations to reduce their occurrence. "With the rich diversity of technology, one can target the driving metrics and find the pain points. Then, at an operational level, determine why these exceptions are happening. Regardless of the reason, find the target and make the invisible visible, anticipate and then redesign around the breakdowns focusing on what really matters."