HighByte Blog
Read company updates and our technology viewpoints here.
|
Read company updates and our technology viewpoints here.
|
Time to read: 7 minutes ![]() The efforts of standards organizations like OPC Foundation, Eclipse Foundation (Sparkplug), ISA, CESMII, and MTConnect represent a significant step forward for the advancement of Industry 4.0 in manufacturing. But industry standards only go so far. Businesses need data to tell the story of what is happening, why it is happening, and how to fix it. Multiple pieces of information must be assembled with other pieces of information from other sources to tell the use case story—just like words must be combined into sentences and sentences combined to form stories. Data standards can’t tell the use case story—they can only provide a dictionary. Standardizing the device-level data into structures is key, but only the beginning. Data standards alone will not solve your interoperability problems because they don’t provide the use case related context you need to make strategic decisions. Here are four key reasons why you still need an Industrial DataOps solution like the Intelligence Hub—even with the introduction or evolution of new standards. Time to read: 6 minutes ![]() Data modeling is all about standardization. It enables interoperability, shows intent, determines trust, and ensures proper data governance. Given the criticality of usable data at scale for Industry 4.0, many manufacturers have turned to ISA-95—probably the most commonly recognized data-modeling standard around the world—for guidance. Created by a standards committee at the International Society of Automation, the ISA-95 specification defines in detail the electronic information exchange between manufacturing control functions and other enterprise functions, including data models and exchange definitions. The purpose of ISA-95 is “to create a standard that will define the interface between control functions and other enterprise functions based upon the Purdue Reference Model”. Per the committee, the goal is to reduce the risk, cost, and errors associated with system integration. Historically, ISA-95 has been the guide for many off-the-shelf and bespoke manufacturing execution systems (MES). Today, ISA-95 also helps industrial organizations implement data integrations that link MES, enterprise resource planning (ERP) systems, IIoT platforms, data lakes, and analytics solutions. It also eases the implementation of a unified namespace (UNS) for enterprise data integration. The specification defines a hierarchal model for systems, detailed information models, and a data flow model for manufacturing operations management (MOM). Let’s take a look at these 3 key attributes in more detail and uncover how the ISA-95 specification can be applied within HighByte Intelligence Hub. Time to read: 6 minutes ![]() In my last post, “An intro to industrial data modeling”, I shared my definition of a data model and why data modeling is important for Industry 4.0. I’d like to take that a step further in this post by explaining why you need a dedicated abstraction layer for data modeling to achieve a data infrastructure that can really scale.
Time to read: 7 minutes
![]()
The data model forms the basis for standardizing data across a wide range of raw input data. An industrial DataOps solution like HighByte Intelligence Hub enables users to develop models that standardize and contextualize industrial data. In short, HighByte Intelligence Hub is a data hub with a modeling and transformation engine at its core.
But what exactly is a data model, and why is data modeling important for Industry 4.0? This post aims to address these questions and provide an introduction to modeling data at scale. |
|