Data is at the core of monitoring any environment. And in an industrial IT environment, this data exists in various devices, systems and sensors in the OT, IIoT and IT areas. And for a sound holistic monitoring concept, there are two aspects you need to consider: what data you need, and how you are going to get the data. Let's take a look at both of these points.
Every industrial infrastructure has its own set of requirements for monitoring, depending on how it is set up, the nature of the production process, and so on. In fact, there are many variables that come into play, so there is certainly not a one-size-fits-all approach to recommend. Rather, it all comes down to defining the goals and actions you need to take in your environment. What goal do you need to achieve, and what do you need to know to achieve it?
Knowing your goals will help you define what kind of data you need to get. For example: some goals might require data from across OT, IT and IIoT, while others might require you to retrofit your older machines.
To illustrate this, here are five examples of common goals in industrial IT.
How much energy are devices or machines using? Many devices and machines have their own built-in energy consumption measurements, but others do not. For the latter, you will need a mechanism – such as a power meter – that can send power consumption data to a monitoring system, where the data can be extracted and analyzed.
Control systems (like SCADA) and execution systems (like MES) play crucial roles in OT, and thus need to be monitored closely. Ensuring that these systems are up and performing as they should be is crucial in a production environment. Thus you will need to understand their current status and condition.
Is the data from sources across the infrastructure making it to the target destination? Is it flowing freely, or are there bottlenecks? Data required for many of the other measurements on this list needs to move from the factory floor to a gateway (for example), and then to an upstream target – perhaps a data center, cloud service, or an ERP system. Components that are unavailable, interfaces that are down, and bandwidth problems can all result in the data not getting to where it is supposed to go.
Once you have defined the data you need for your goals, you can put strategies and solutions in place to obtain it. For this, there are three main aspects you will need to consider: how the data source is connected, what protocols it uses to communicate data, and the security permissions required to access it.
How you access the source – whether it is a machine, control system, or another component - depends on how the devices and systems you need to monitor are connected. This will determine the mechanisms you utilize to get the data. In modern environments, for example, OT could be connected via classic factory LAN systems, industrial WLAN, or even new wireless standards like 5G or LPWAN.
In the OT world, there have historically been several protocols that have served the purpose of communication information on the factory floor – most notably, the FieldBUS protocols. More recently, as industrial infrastructure has become more interconnected, protocols from the IT world have entered the production world. In order to get the data you need, you must be able to communicate using the protocols in your specific environment.
It goes without saying that to be able to access the data source, you need to have the correct security clearance for it. This might mean authentication, having access to the necessary ports, and so on.
Of course, all of the above is strategic, and is only a small part of putting together a monitoring concept. For more information, download our white paper, "Support IT/OT convergence with holistic monitoring", by clicking on the banner below. In it, we cover various considerations for defining a monitoring strategy, including the challenges of monitoring IT and OT, how to visualize your monitoring data, and the importance of notifications and alerts.