IIC Journal of Innovation 7th Edition | Page 40

A Practical Framework To Turn IoT Technology Into Operational Capability business outcomes. This is also the starting point for using the I2OC framework. The top row of chevron arrows first addresses the business requirements before defining the technical infrastructure to achieve them. Three basic questions are used as the basis for establishing common objectives between all the stakeholders: (1) What outcome do we want, (2) what processes or business logic will deliver that and (3) what data do Framework to Agree on Key Business Outcomes The high-level business outcomes in the I2OC framework are the basis for scoring and agreeing on the business impact of a specific IoT-enabled use case. It is often useful to list a number of potential scenarios or use cases and rank them based on their business impact for each desired business outcome. Figure 3 - Business Impact ranking matrix you need for that? This approach focuses on the problem at hand and identifies the key data sources needed, rather than looking at what sensors and data organizations have and then trying to retrofit them to the problem. This approach supports the business viewpoint of the IIRA. To avoid analysis paralysis 17 a simple high, medium and low scoring methodology is used in setting up a ranking matrix. This is best done with the business (operations), IT and OT representatives in a working session. It is also useful to score the technical feasibility (or complexity) for each scenario, again without over-analyzing or getting into to o much technical detail. The I2OC framework is used to address the three challenges of agreeing what success looks like, how to manage complex data integration from heterogeneous sources and how to make it part of the day-to-day operations in industrial organizations. The following section describes how the framework is used to address each of these challenges. 17 In this example, the following technical assessment criteria is used: (1) OT complexity, (2) IT complexity, (3) analytics, (4) system complexity and (5) project readiness. OT and IT complexity, in turn, is described in terms of availability, accuracy, latency and https://en.wikipedia.org/wiki/Analysis_paralysis IIC Journal of Innovation - 39 -