Your people need information they can trust, but combining data from multiple sources requires too much code and scripting. It just doesn’t scale.
Flow solves this problem by reshaping how we address analytics.
With Flow, you can collect, combine, and normalize data from multiple disparate OT and IT sources, create calculations and event frames, and contextualize the results using time and model information.
Think of Flow as a hub
Flow is a centralized hub that allows you to collect data from multiple disparate sources, combine it, normalize it, perform calculations on it, and then store the resultant information within time and model context. We call this the data transformation process, and Flow is the hub that allows you to manage that transformation pipeline. This Analytics Hub represents what we call the “single source of truth”, the one place your users need to know about to access the information they need to make decisions in real time.
As data streams into the Flow Analytics Hub and is transformed by the pipeline, it immediately becomes available for presentation via charts and dashboards, and for publishing out to other systems that require its consolidation and calculation capability.
Flow is the hub that allows you to manage your data transformation pipeline.
Industrial Data Management is hard. Which ways have you tried?
Let's move everything to the cloud, to our data lake
Ever heard this one? Is the data in the lake structured and modeled? Is it accessible to all your people? Are your analysts spending half their time searching for and massaging the data? What about bandwidth costs? Is the lake actually being used, or has it turned into an unusable swamp?
We'll get our historian vendor to build the extra functionality we need
This one happens a lot! You get your historian vendor to build a new chart type, one you've always wanted, great! Now you want to use this shiny new chart to show some data from a different database. Can you get that data into your historian? Does it make sense to duplicate your transactional data into a time-series format?
Let's keep using our spreadsheet system
How about this one? How often is the spreadsheet incomplete in your morning meeting? How often do the spreadsheet files become corrupted? How do you know a key value being reported hasn't been changed without you knowing? In the end, how many versions of the ``truth`` do you have?
Let's custom build it; it won't take long
This is a common one. But, do you know how long it will take? Six months, a year, maybe two? Will you need a dedicated development team? Will they keep up with new requests? What if they resign?
Here's how FLOW works
Collecting data is simple; turning it into actionable information is not! Data management, collation, and contextualization is the biggest problem facing industry today.
But imagine what you could do if you had a scalable platform built specifically for IT teams to transform OT and IoT data streams into analytics-ready information. Flow includes the tools you need to:
MODEL
Consolidated modeling to abstract and unify multiple underlying namespaces.
CONNECT
Connection into multiple data sources, including OT, IoT, IT, and manually entered.
TRANSFORM
Calculation services to clean, transform, contextualize, and combine time-series and transactional data.
VISUALIZE
Decision support via browser- based visualization, reporting, dashboarding, and notification.
BRIDGE
Data collection and bridging via industry standard-protocols, including MQTT and REST.
For scalability, Flow provides a modeling and configuration environment with an open architecture and templating. Leverage the work you have done in your existing systems while using Flow’s self-service no code/low code approach.
