October 8, 2019
By Ben Dolmar, Director of Software Development, Nerdery
Industrial Internet of Things (IIoT) adoption continues to accelerate. Eighty-six percent of companies had IIoT solutions in place in 2018, many of them for the first time. Roughly half had been using the solutions for less than 12 months. Companies breaking new ground in IIoT have a unique opportunity to prevent data siloing from the start to avoid backtracking to patch past bad behavior.
IIoT allows manufacturers to better track data originating from machines making it more valuable for all internal stakeholders. However, value only exists if data is translated into complete, accurate and actionable information.
When piloting IIoT, manufacturers frequently start planning around a single piece of machinery. The temptation at that point is to ignore the processes and other machines that also will be impacted. That’s where new data silos form.
Common technical pitfalls that result in data isolation include:
When data is left in silos rather than an integrated system, businesses miss out on improvements in the opportunity to drive efficiency across production lines.
Starting with a small test across a non-essential process is a good idea; however, in order to ensure that the smaller case lays the groundwork for future expansion, it is critical that the planning and design look past the initial build. To do so, ensure that you take the following steps:
While all these technical steps are important to ensure data silos are avoided when implementing IIoT solutions, they’re only half the equation.
Frequently, data silos develop when companies deploy solutions that take a narrow, technical and task-oriented view of the problem. For example, a problem statement like, “I want to get data off this machine into the cloud,” is a limiting view to the problem. It leads to a solution that puts the data into a database in the cloud but does not result in operational changes.
If instead the problem is framed in terms of business impact and human decision-making, companies can look for ways to pull together all of the relevant data. For example, a problem statement like, “I need to understand which of my machines have capacity so that I can appropriately limit my work-in-progress,” encourages pulling in metrics from multiple machines and systems. It might lead to analysis of transit time and operator efficiency.
Recently, Nerdery was working with a client on a system for integrating IoT data into a factory management solution. Prioritizing users and their needs drove the shape of our solution and its technical implementation. When we approached the problem we started by:
Using those tools we were able to design a solution that focused on the data that helped people make better decisions both at the line- and operational-level.
The biggest opportunities for IIoT lie in marrying a broad spectrum of data types. Avoiding data silos from the onset is the crucial difference between companies who find success in IIoT and those who flounder.
Ben Dolmar is the Director of Software Development at Nerdery, a Minneapolis-based digital consultancy of strategists, designers and engineers. In his 11 years with Nerdery, Ben has contributed to more than 500 projects and worked on mobile and IoT apps for entrepreneurs and Fortune 500 companies. A graduate from the University of Wisconsin–Madison with a dual major in journalism and political science, Ben joined Nerdery in 2007 as a Senior Developer and served as Principal Software Engineer before becoming Director of Software Development.
Contact Info: info@nerdery.com
Patti Jo Rosenthal chats about her role as Manager of K-12 STEM Education Programs at ASME where she drives nationally scaled STEM education initiatives, building pathways that foster equitable access to engineering education assets and fosters curiosity vital to “thinking like an engineer.”