Get everything in one place
Historically the single biggest reason people choose infinitii flowworks: it connects to what you already own, and to what you buy next.
Hardware neutrality is the whole point
Most monitoring software is supplied by whoever made the hardware, which means your data ends up organised by procurement history. Two logger fleets and a SCADA system become three portals and a spreadsheet.
infinitii flowworks is not tied to a manufacturer. Sensors and loggers from any vendor, SCADA systems, and external sources pulled over web API all arrive as raw channels and behave identically once they are in. New sources are added continuously — if something you own is not supported yet, that is usually a conversation rather than a dead end.
Sources
Sensors and loggers
Existing equipment from a mature gauging network, whoever supplied it. Sites reporting over cellular or satellite telemetry are supported the same way as any other — we work with the hardware you buy rather than selling you ours.
SCADA systems
Link a SCADA historian and its points become channels alongside everything else, with the same graphing, alarming and analysis available to them.
Web API sources
External data pulled automatically — public gauge and weather services among them, and third-party gauge-adjusted radar rainfall.
Manual and bulk upload
Historical file import with no size restriction
Data transformation
Transformations run through FACE or FACE Pro and always produce a new calculated channel. The raw data from devices and services is never altered, so there is a record of every transformation applied to it.
Metadata and documents
Date- and time-stamped photos, verification measurements, field observations and attached documents, held against the site.
Public agency services
NOAA, Environment Canada, the USGS, NASA and similar services configured as ordinary sites and channels — observation data, forecast data and the historical intensity-duration-frequency (IDF) curves behind rainfall analysis.
Photo channels
Images from embedded cameras collected as a channel, one per reading interval, so what a site looked like is stored beside what it measured. See visual monitoring.
The infinitii flowworks API, both ways
Integration is not only inbound. An extensive API carries channels — measured and calculated alike — out to other systems and public-facing websites, and accepts data back in. See the API.
Why this matters more than it sounds
Most people working with time-series data already understand the benefit of having all of it in one place.
Consolidation is the reason integration breadth is the first pillar rather than a footnote. Once the data is in one place, the department that consolidated it tends to find the rest of the organisation asking them for things.
In detail
Integrations and new data sources
What connects, and how sources get added.
Data management
Storage, transformation, import and export.
Administration
Accounts, groups and permissions.
Ask about the hardware you already own
The most useful first question is usually a list of what you have. Bring it.