...
As you can tell from the above example, the simple and a more complicated examples are very similar yet different and the Solution Architect will need to work with the customer to determine what is the best course of action based upon many different factors (regulations, safety, internet connectivity, maintenance schedules, physical access to the device, cost, among many others). The IIoT at the Smart Device Edge family of blueprints is designed to help the solution architect and end user determine what their needs are and how to create solution that works for them. It is very possible that there is no perfect fit of the blueprints here, but there is most likely a combination of the blueprints will provide a complete solution. With this in mind the blueprints are designed to be componentized so that they can be separated and combined in many different ways.
...
The basic infrastructure for this family is Smart Edge Device that is connected to some type sensor (Southbound) and the device is able to communicate both Northbound to a Cloud or an on-Prem System. Most Use Cases will extend this basic diagram to run some type of application in a
...
- computer vision, eg stream video
- high bandwidth is needed
- the killer app is to process this at the edge
- machine intelligence, eg structured telemetry
- many different protocols,
- varying amounts of data volume (eg vibration data vs temperature data)
...
a container or VM.
The killer apps for this family will applications that can take advantage of the compute power at the device edge. Two examples would be Computer Vision and AI/MI. For computer vision applications, a large pipe is needed to stream the video to the edge device, then it can process the video and send responses back to the edge components and/or send a filtered set back to the cloud. Having the ability to do compute at the edge allows for AI/MI at the edge, thus predictions can be created without leaving the device
Family- IIoT at the Smart Device Edge
...