How Industrial DataOps is shaping Industry 4.0
The Problem: Unusable Data
Industry 4.0, Industrial Transformation, and Smart Manufacturing combine disparate information to drive automated decisions from machinery to the Cloud. Multiple technologies play a role in this transformation, including Cloud computing, IIoT platforms, advanced analytics, augmented and virtual visualization, mobile platforms, miniature and inexpensive sensors, and networking. The objective is to put more information in the hands of stakeholders when and where they need it.
Early adopters of Industry 4.0 technologies imagined that simply connecting their industrial data to analytics and visualization applications via APIs would deliver results. Instead, they discovered the data lacked accessibility and context. It was inconsistent across machinery and calibrated to the controls equipment—not to how business users think.
The Solution: Industrial DataOps
→ Data Architecture & Integration
Processing data through layers of systems worked for many years primarily because the amount of data was relatively limited. This is no longer the case. Pushing excess, unused data through systems that don’t need it (to arrive at those that do) complicates and slows processing, reduces security, and increases vulnerability.
→ Data Standardization & Contextualization
Because data in industrial environments is very inconsistent across machinery, lacks context, and is correlated to the controls equipment, an industrial DataOps solution has very different requirements than the DataOps technology used today for business transaction systems.
The Functions
- Standardize, normalize, and contextualize data.
Industrial data is generated by motors, valves, conveyors, machinery, and other such equipment. This data typically comes from PLCs, machine controllers, RTUs, or smart sensors. A factory might have hundreds of PLCs and machine controllers, often purchased at different times from different vendors. The data points available on the controllers vary; they were also designed for use by industrial software solutions.
To derive valuable insights from this data, it must be analyzed across machinery, processes, and products. A set of standard models is required within the DataOps solution to handle the scale of hundreds of machines and controllers, correlate the data, and present it to the consuming applications. - Connect to both industrial and IT systems.
Industrial devices/systems and IT systems natively communicate in different ways. The former use many proprietary protocols, though support for OPC UA and other open protocols is trending upward. IT systems rely on their own protocols to communicate with extensive usage of APIs and bespoke integrations.
IT systems communicating with Edge devices have begun to leverage MQTT, which provides a highly flexible pub/sub methodology, with low overhead, to minimize cybersecurity exposure and secure encrypted communications. A DataOps solution must be able to integrate seamlessly with devices and data sources at the operations layer by leveraging industry standards, while providing value to business applications that conform to current IT best practices. - Manage the flow of information.
It is critical that information flows are contained and managed within a system where they can be identified, enabled, disabled, and modified. In order to ensure that “good” data is being stored, machinery changes must be accurately reflected in the data collected and transformed.
From a security perspective, it is critical to know what data is moving among systems -- and be able to turn it off. Because many vendors want machine data in order to provide enhanced service, the operations team needs to be able to control that data flow and set conditions and frequency. - Provide industrial-level scale and security.
The vast breadth and scale of industrial data distinguish it from the typical transactional data stored in most IT systems. Industrial data is typically used within milliseconds to seconds after it is created and must be contextualized and delivered at a resolution unique to the specific use case.
As such, batch processing ETL solutions built for transactional data do not work well for industrial data. Furthermore, industrial data contains the intellectual property of a manufacturing plant, which must be secured and discretely communicated. - Live at the Edge.
Analytic and visualization applications that consume industrial data may be processed close to the machinery, in an on-premises data center, or in the Cloud. But the industrial DataOps solution itself must run close to the device, feeding applications at the frequency or condition specified. It must also be able to share models across the factory and the company to allow for data standardization and normalization.
The Takeaways
- Addresses data inconsistencies across machinery
- Normalizes and contextualizes data
- Aligns data for business users
- Provides secure management of data flow
- Offers accessibility across network infrastructure, throughout the company, and to external vendors
Want to read more on this topic? Download our white paper DataOps: The Missing Link in Your Industrial Data Architecture.