HighByte Blog
|
Read company updates and our technology viewpoints here.
|
|
Time to read: 7 minutes  Posted by John Harrington The unified namespace (sometimes referred to as the UNS or universal namespace) can be an allusive concept for many of us as we move to an Industry 4.0. world. At HighByte, we define the UNS as a consolidated, abstracted structure by which all business applications are able to consume real-time industrial data in a consistent manner. The benefits of a UNS include reduced time to implement new integrations, reduced efforts to maintain data integrations, improved agility of integrations, access to new data, and improved data quality and security.
We are often asked if HighByte Intelligence Hub is a UNS. The answer depends on your priorities and project scope. We typically see three architectural patterns for implementing the UNS. HighByte Intelligence Hub can play a key role in each approach by both providing access and structure to the UNS or acting as the UNS. Time to read: 6 minutes Posted by John Harrington 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  Posted by Aron Semle Our latest release is packed with new features and capabilities that make common Industry 4.0 use cases not just easy, but fun!
Do you need to get SQL data into your Unified Namespace (UNS)? How about data from your test equipment that’s sitting around in CSV files? Maybe you’re moving away from SQL and experimenting with NoSQL alternatives because your data models are in a state of change? Even better, maybe you have your Edge-to-Cloud strategy figured out, and now you’re looking at “Cloud-to-Edge”, trying to get alerts generated by machine learning back to the factory floor. These are just a handful of use cases we hear from customers and new use cases we’ve enabled in HighByte Intelligence Hub version 1.4. Time to read: 6 minutes  Posted by Tony Paine 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.
|
