HighByte Blog
|
Read company updates and our technology viewpoints here.
|
|
Time to read: 8 minutes  Posted by Jeffrey Schroeder For quite some time, people have been asking us how the Intelligence Hub relates to a Unified Namespace (UNS). Is it a specific part of a UNS architecture, a platform by which one might build a UNS, or a UNS architecture itself? Over time, our answers have developed alongside the capabilities of the Intelligence Hub. From the beginning, the Intelligence Hub could connect to third-party MQTT brokers as well as model the data going in and out of them. And recently, we added an embedded MQTT broker to the Intelligence Hub to address brokering and provide the ability for MQTT clients to connect to the Intelligence Hub directly. These provided the functionality needed for much of what might facilitate or be considered a UNS, but it was missing a critical part: a way to visualize the contents.
Time to read: 6 minutes  Posted by John Harrington Ever since the first release of HighByte Intelligence Hub in 2020, HighByte has developed the solution to meet the industrial data integration needs of today’s industrial customers and tomorrow’s market requirements. The first version of the Intelligence Hub was a client-based application that collected and published contextualized data to any consuming system. As Industry 4.0 leaders began to integrate more systems and assets into their ecosystems, data consumers needed better data visibility and access. The consumers wanted to be able to see all available information, so they could access exactly what they needed. To deliver this visibility and access, we embedded an MQTT broker into the Intelligence Hub, giving administrators the necessary tools to build a Unified Namespace (UNS) that would allow consumers to easily subscribe to the information they desired.
With changing needs in mind, in May 2023, we took the next step in the evolution of the Intelligence Hub, adding the ability to request data on-demand through the Intelligence Hub with a built-in REST Data Server. This addition allows users to request time series, transactional, or master data from systems through a single, simple API. Time to read: 9 minutes  Posted by Jeffrey Schroeder From our very first release in early 2020, HighByte Intelligence Hub has developed alongside the needs of Industry 4.0 pioneers. We have focused our efforts on addressing the most pressing challenges faced by industrial companies as they integrate systems and modernize their architectures. Today, industrial information networks encompass more sensors, devices, and systems than ever before, indicating an exciting level of connectivity being adopted globally. To facilitate and accelerate this adoption, we are excited to announce Intelligence Hub version 3.1.
Intelligence Hub version 3.1 includes powerful data accessibility, governance, and scaling capabilities from a broad swath of new features, each of which extends the reach of the Intelligence Hub to even more producers and consumers of industrial data. Time to read: 7 minutes  Posted by Torey Penrod-Cambra For the past several months, 55 beta testers in 13 countries have been kicking the tires on HighByte Intelligence Hub version 3.0 and generously providing their feedback. Today, I’m excited to announce this major release is now available.
Version 3.0 is a step change for the Intelligence Hub and for the Industrial DataOps market. It raises the bar for what a DataOps solution can be at Enterprise scale. It introduces a powerful new Pipelines builder to curate complex data pipelines. It makes the often-vague concept of the Unified Namespace (UNS) tangible and achievable with an embedded MQTT broker—reducing additional software, cost, and administration overhead for our customers. I sat down with HighByte Chief Product Officer John Harrington to talk about some of these advancements available in Version 3.0, including Pipelines. His thoughts are below. I also provide insights from our partner Goodtech, a deep dive on the embedded broker, a review of new project management capabilities, and more. |
