Book Image

Industrial IoT for Architects and Engineers

By : Joey Bernal, Bharath Sridhar
Book Image

Industrial IoT for Architects and Engineers

By: Joey Bernal, Bharath Sridhar

Overview of this book

When it comes to using the core and managed services available on AWS for making decisions about architectural environments for an enterprise, there are as many challenges as there are advantages. This Industrial IoT book follows the journey of data from the shop floor to the boardroom, identifying goals and aiding in strong architectural decision-making. You’ll begin from the ground up, analyzing environment needs and understanding what is required from the captured data, applying industry standards and conventions throughout the process. This will help you realize why digital integration is crucial and how to approach an Industrial IoT project from a holistic perspective. As you advance, you’ll delve into the operational technology realm and consider integration patterns with common industrial protocols for data gathering and analysis with direct connectivity to data through sensors or systems. The book will equip you with the essentials for designing industrial IoT architectures while also covering intelligence at the edge and creating a greater awareness of the role of machine learning and artificial intelligence in overcoming architectural challenges. By the end of this book, you’ll be ready to apply IoT directly to the industry while adapting the concepts covered to implement AWS IoT technologies.
Table of Contents (19 chapters)
1
Part 1:An Introduction to Industrial IoT and Moving Toward Industry 4.0
6
Part 2: IoT Integration for Industrial Protocols and Systems
11
Part 3:Building Scalable, Robust, and Secure Solutions

Putting the layers together

Putting all the pieces of the architecture together, you can see that the complete flow from the sensor to the screen is relatively simple. That is our initial goal – getting some data flowing and obtaining a better understanding of what type of environment we are working with. This is just one path for one set of use cases, but it allows us to start formalizing the layers we have defined, to understand or test what services and components we may use, and to vet some of the data needs from our initial environment. Figure 4.13 provides a view of the complete architecture as we have implemented it so far:

Figure 4.13 – Overall architecture

Figure 4.13 – Overall architecture

You can see that some of the layers have been skipped for this example. Our focus is to crawl and walk first and then run later, especially when we are just getting the initial phases of the architecture designed and built. It has been said that architecture is as much of an art...