Achieving IoT Interoperability
enterprisenetworkingmag

Achieving IoT Interoperability

By Scott Johnson, CEO & Founder, Devicify

Scott Johnson, CEO & Founder, Devicify

As the effects of the Internet of Things (IoT) permeate our lives, companies will be forced to figure out how to effectively control an often huge pool of connected products in addition to properly leveraging the subsequent potential flood of information. Most IoT initiatives that have begun to tackle this challenge have understandably focused on the “Things” or the products. The unfortunate results include data structures, infrastructures and development priorities that incorrectly favor the product over the business. The collisions between digital-physical, IT-OT and product-service, being fueled by the IoT make it increasingly important that product generated or sensed data be relevant and accessible to the business systems. Companies that succeed in reconciling these normally contrasting areas to achieve interoperability across stakeholders and systems, both internal and external, will gain tremendous advantage.

This article outlines several steps, based on a methodology developed by Devicify, which will help maintain focus on the most important aspects of an IoT initiative to ensure interoperability that overcomes many of the largest challenges.

“Collisions between digital-physical, IT-OT and product-service, being fueled by the IoT make it increasingly important that product generated or sensed data be relevant and accessible to the business systems”  

Step 1, Plan (for Control): Proper control will be able to expose information as broadly as is appropriate and valuable. Defining a reference architecture that supports this is always challenging, and more so considering the new situations introduced by the IoT means most of us will not yet have deep experience. Begin by considering what information should be collected from or through the products or sensors you wish to build, sell or deploy. Challenge why that information can be made valuable (i.e. actionable). Determine the desirable control over product functionality and again challenge why. Having these answers up front is often less-than-realistic, so use method of representing and implementing important elements that can be easily expanded.

With confidence in your method, you need not, and should not, plan the entire solution up front. Get moving but make certain you’ve addressed these three elements to preserve scalability.

1) Control. Ensure visibility over the product and its functions and establish control over the enablement of those functions and data you’ve determined to be valuable.

2) Access. Implement a security model that leverages relevant business relationships and context in determining access to products and data.

3) Flexibility. Use a data model that accommodates a wide range of product types, microprocessor powers or even vendor sources so that the use case drives your innovation, not the limitations of your technologies.

Step 2, Design (around Interoperability): Having planned around such criteria, the effort can return to a more typical product development path that is predominantly a developer-led initiative. This is the right time to engage the necessary building, trying and testing. The appropriate architecture will allow the innovative work done by technical teams during this step to be more easily put into practice since the resulting solutions are inherently accessible to and controllable by the business.

Embedding such interoperability yields benefits in the near term but is instrumental in positioning for a more successful follow through. The bigger opportunity and greater challenge arises from how we adapt our processes in order to operate and compete differently by employing the information collected through the products we make and use. Processes and workflows must be designed to respond to events detected by those products, and responses must include automation, not just notification.

tag

IoT

Weekly Brief

Read Also

Data to Marshal on Field Troops

Data to Marshal on Field Troops

Eric Rivas, Director of Service, Cattron Global
Is Your Architecture Team Stopping Business Innovation?

Is Your Architecture Team Stopping Business Innovation?

Paul Ayers, Cloud Enterprise Architect Director, Oracle
Making Meaningful Change on the Cloud Native Journey

Making Meaningful Change on the Cloud Native Journey

Mark Ardito, Divisional Vice President, Digital Delivery, Health Care Service Corporation
Demystifying The Sd-Wan Ecosystem

Demystifying The Sd-Wan Ecosystem

Marc Ashworth CISSP, CISM, CRISC, Senior VP—Chief Information Security Officer, First Bank [NASDAQ: FRBA]
Build your own layer cake

Build your own layer cake

John Walshaw, Director of Telecommunications, Kaman [NYSE: KAMN]
Sd-wan one way  or another

Sd-wan one way or another

Blaine Crawford, Director of Information Technology, C.W. Driver, LLC