Data management
All historical data can be loaded. Site-specific metadata is a separate thing from the time-series data the analysis works on.
What it does
No transformation happens as data is loaded. Everything arrives raw, and transformation runs afterwards in calculated channels, so every change is tracked.
Data can be loaded through the API, or through the import feature in infinitii flowworks, which offers a choice of import formats.
Metadata is files and user-created custom fields — the information you do not see in the graph. It is added in the site detail view.
Custom fields cover the attributes infinitii flowworks does not collect for you. Alongside the built-in site type, collection method and data point count, you can define your own — installation date, catchment area, pipe diameter, pipe material, or anything else your asset register cares about. Fields are grouped into sets, a set is assigned to a site or a group of sites, and each field is typed as text, date and time, or a selection list so the values stay consistent across the network.
Sets are created by a Group Admin. Values are set by a Site Config Admin and readable by everyone in the client from Site Details on the network map — so the pipe diameter is where somebody looking at the site is already standing, rather than in a spreadsheet somewhere else.
- Transformation of units, offsets and corrections on ingest
- Direct live links or bulk historical upload
- High-speed download of a day, a year or a decade
- Metadata, photographs, observations and attached documents
- Custom fields for your own site attributes, typed and grouped into sets
Where this sits
Collection & integration
This capability is part of the collection & integration group.
All features
The other five groups.
Solutions
Or start from the problem instead.
See it on your own data
Feature lists are hard to judge. A demo runs on your sites and your history.