Architectural framework IIoT systems comprise connected systems of machines, or industrial systems, exchanging data, analysis, and actions to improve production and performance, and reduce defects or failures. Vast quantities of data are collected, analyzed, and transmitted at a rapid rate to consuming systems or components, where further analysis and actions may occur. An architectural framework therefore becomes necessary to guide the design of the system and ensure all stakeholders' expectations are considered. Specific concerns of each stakeholder are described and organized into appropriate types of models (model kind). The various model kinds of each viewpoint are consolidated and organized, while resolving concerns, into an architectural view for the respective viewpoints. The architectural views of the various viewpoints in turn form the architecture...

Many disciplines and viewpoints need to be considered in architecting an IIoT solution, and the various stakeholders from each viewpoint can have intertwining concerns spanning the lifetime of the system.

Let's discuss the following typical viewpoints and how they interact with each other:

• Business viewpoint
• Usage viewpoint
• Functional viewpoint
• Implementation viewpoint

The business viewpoint maps business strategy to capabilities and identifies opportunities to achieve additional value thru IIoT. The business viewpoint identifies the capabilities that become the driver for the usage viewpoint, which deals with how the system is used. The usage viewpoint guides the life cycle of the project, including design, development, implementation, deployment, and the sustaining engineering. The functional viewpoint defines what the system does, and breaks...

IIoT solutions rely heavily on the use of advanced analytics on the data collected from the operational systems. This data is often merged with the data from the enterprise systems. Typically, the volume of data from the operation systems may far exceed the data from the latter source. Let's take an example of data from aircraft. According to Aviation Week, a modern generation aircraft can generate over one terabyte of data in a cross-country flight. Modern generation aircraft can have more than 1,000 sensors, including about 300 in the jet engine alone (http://aviationweek.com/connected-aerospace/internet-aircraft-things-industry-set-be-transformed).

This poses several kinds of challenges for the data and analytics design in the case of IIoT systems. Here are a few considerations:

• Storage of data: The sheer volume of data that can be generated by recording...

The PoC enables the demonstration of technical feasibility to deliver business value for an IIoT solution. A PoC is carried out on a smaller scale than a production system, giving the project team this opportunity to work out technical issues at a reduced cost and risk. It also provides an ecosystem for the various viewpoints to discuss and form an agreement about the business values and technical solutions.

The scope for the POC must be clearly defined and agreed upon. The success and eventual acceptance of the IIoT solution is not only dependent on the technology, but on how well the solution fulfills the business goals. Therefore, the business viewpoint is the predominant factor...

This chapter set the foundation of the architectural approaches for designing a successful IIoT project. You learned about the different architectural viewpoints that are needed, from business considerations to the implementation stage. You then learned about the data and analytics considerations of an IIoT project. Finally, we looked at how to get started using PoCs.

The next chapter will focus on business requirements gathering. The traits that an architect must focus on for IIoT project requirements gathering differs from those for traditional IT projects. The chapter will cover how to align with the right business leaders. Furthermore, you will learn how to estimate the cost of the IIoT projects to help justify the ROI.