How to build an IIOT system as an enterprise solution
#digitaltransformation #goingdigital #iiot #enterprisesolutions #industry4.0 #smartfactory#automotive

How to build an IIOT system as an enterprise solution

First, we need to understand that IIOT system isn’t just that System with many devices connected to each other point to point and thus the systems and data are hardwired to each other, and exchange data via different protocols.

No alt text provided for this image

IIOT system is based on a creating a unified place to be a central place for data exchanging, every single data is pushed to and pulled from this specific place when ever it needed, to whom needs it, and that is called a “Unified Namespace”, and then the whole system is connected to a cloud, after all, Artificial Intelligence and machine learning could be implemented to maintain, develop, and enhance the system over the time, we can recognize it in manufacturing sectors, energy industry, and automotive industry, and this point we can say in other words that we are trying to implement a 4.0 industry solution.

No alt text provided for this image
No alt text provided for this image

  • The question is how to build a Namespace?

1- We need a device to unify all the different communication protocol from OT (Operational Technology), and IT (Information Technology) levels.

2- We need a broker which is more likely a server but subscribed by multiple clients and also publish to multiple clients, all at the same time.

3- We need to structure the broker in a way that is easy to interact with, but it’s not that tough to build, since data is structured according to a model provided in ISA-95 standard.

4- We need to connect to a cloud via server more likely from amazon, Azure, or any other different server provider.

No alt text provided for this image

First, The Namespace uses MQTT/sparkplug which is a communication protocol based on the application layer publisher/subscriber, this communication protocol provides interoperability when using devices from different vendors, different APIs, and databases like SQL databases, So a smart Gateway or MQTT gateway is used if the device doesn’t support MQTT protocol.

In addition, a MQTT broker is provided by companies like HIVEMQ and highbyte.

Thirdly, the data is structured according to ISA-95 std, and every level, process, or unit in the unified namespace is connected through a tag, python code, or any other method, and provided with dashboards real time.

the OEE (Overall Equipment Effectiveness) is calculated and monitored and it’s a mandatory concept in manufacturing, it reflects the Availability, Quality, and efficiency of the manufacturing process.?

No alt text provided for this image

  • Examples of IIOT Enterprise solutions and unified namespace concept:

No alt text provided for this image
No alt text provided for this image

References:

https://www.hivemq.com/blog/sparkplug-essentials-part-2-architecture/

https://www.hivemq.com/blog/azure-iot-edge-and-hivemq/

https://www.hivemq.com/iiot-protocols-opc-ua-mqtt-sparkplug-comparison/

https://www.youtube.com/watch?v=vkTGRfwcFyM&ab_channel=4.0Solutions

https://docs.inmation.com/datastudio/1.82/model-panels/isa95-equipment-model.html

https://documents.opto22.com/2357_Industrial_Strength_MQTT_Sparkplug_B.pdf



By: Ahmed Khaled

要查看或添加评论,请登录

Ahmed Khaled的更多文章

社区洞察

其他会员也浏览了