A flow defines the mapping and execution of data coming in and data going out of HighByte Intelligence Hub. A flow’s sources can be primitive or complex inputs, aggregated calculations of inputs, or modeled instances, while its targets are specific outputs on a connection. When sending data to a system, it is critical to configure the flow based on the type of publish that is needed.
Some systems want the complete set of data published to them at a consistent frequency. This is typically used when publishing to a SQL database where time-based trends and analysis are used to visualize the data. HighByte Intelligence Hub can be configured to publish at any interval from tens of milliseconds to multiple days. The publishes can also be configured to only occur when the machine is operating by monitoring a specific input for a value.
Other systems want data to be published to them when an event occurs. This could be when a work cell has completed a part or when the temperature or pressure exceeds an allowable limit. With event publishing, a complete set of information is assembled when the event happens to notify a system or log the event. The flow can be configured to be published when a specific condition evaluates to true. Flows set to Event, result in the Intelligence Hub immediately executing flows when data is received, and guarantee data is not lost. Event based flows are available for MQTT, Sparkplug, Webhook, OPC UA Subscriptions, Azure IoT Hub, and Azure Event Hubs Inputs.
Many Operational Technology (OT) systems and some IT systems are able to consume and reconstruct time series data. Time series data publishing only publishes changes and is the lightest load on the network and storage, but the heaviest when it comes to reconstructing information for visualization. HighByte Intelligence Hub may be set to only publish when changes occur and to only publish the data items that change. The Intelligence Hub can also publish into or pull data from time series systems, including PI System and InfluxDB.
Identify source inputs, or instances and target outputs
Define flow triggering cycle, data change, or event
Send fully defined objects or only values that have changed
Track execution and performance more precisely with flow statistics
Mass enable and disable flows
Monitor flow status within the user interface or at scale using third-party system-monitoring applications
Trigger flows immediately when messages are received over MQTT, Webhook, OPC UA, and other event-based connectors to guarantee no messages are dropped
Join the free trial program to get hands-on access to all the features and functionality within HighByte Intelligence Hub and start testing the software in your unique environment.