The IoT, or the Industrial version IIoT, means different things to different people. One definition of IoT is that it is a phrase of convenience describing how everything in the world could be connected via the Internet, with a view to each ‘thing’ interacting somehow with the rest. It sounds ideological, but with careful planning, paying attention to security, risk, and data, the IIoT is achievable. Many concepts only require analysis of data, but some include actions such as equipment operation.
Security
Security covers users, assets, and data. 
You should consider not only restrictions/privileges but also physical protection. You need to decide what you want to let the world know versus information accessible to privileged users (and hackers). It is a good idea to assume your system will be compromised at some time and to evaluate the consequences and recovery before it happens.
Assets, including data and people, need protection. Historically, only a local operator using standard operating procedures could operate equipment. However, the IIoT concept says that anyone can start or stop anything. This can be deliberate, accidental, or the far too common remote software malfunction. Systems need to be designed to ensure that equipment is only operated when required and safe; by authorised personnel 100% of the time. Any system that bypasses existing control measures must be avoided for safety and legal requirements.
Risk
There are significant benefits associated with implementing IIoT, several of which only become evident after the system is operational. But there are also risks. For example, many players in the marketplace have the talk but not the skills or understanding. They might promise that they will take the data and report on production consumption and highlight inefficiencies. The simulations and demonstrations look great, but when it comes to implementing and connecting the system to the data source, we have seen too many scenarios where the data is just not available, or if it is, it is different to what the experts require. This typically leads to the project failing. Too many people have been burnt trying to implement unachievable promises and are understandably hesitant to try again.
Data
Planning or specification of the IIoT often starts with thinking about the final product. “What do you want?” “What are your pain points?” “Where are your current inefficiencies?” These are all valid questions and need to be considered. Data is critical to a successful IIoT implementation, but without meaningful, well-understood data, anything based on it will be meaningless. Before the end result, such as the GUI, is considered, the data must be available and usable. For example, is it cost-effective to measure the level of liquid in the tank with sufficient accuracy? The infrastructure and the connectivity to the ‘thing’ need to be in place. Any ghost or phantom data needs to be eliminated. Only when the data is suitably filtered, correctly correlated with other information and well understood can it be presented with meaning and authority.
Mescon have several years of experience in implementing successful, secure and risk-evaluated IIoT systems (they were never called that at the time). Start a discussion today at www.mescon.com.au/contactus.
