Environmental monitoring data

Every sensor you own, in one place, right now

infinitii flowworks connects the loggers, SCADA systems and data sources you already have — whoever made them — keeps the data current, and gives the people who depend on it the analysis they would otherwise build by hand.

100B+
Sensor readings
90,000
Connected sensors
70+
Cities and districts
infinitii flowworks on desktop and mobile

The analysis is the easy part

Most utilities already collect far more data than they use. It sits in a device manufacturer's portal, a logger file, a SCADA historian or in spreadsheets on local PCs and file servers. Before an engineer can analyze anything, they have to find it, export it, align the timestamps and assemble it together, and on most projects that takes longer than the analysis itself.

Organization gets done periodically, by hand, on extracts. Findings arrive as documents already out of date, and the next question starts the stitching over again. infinitii flowworks takes that work off the desk: every source lands in one place, already aligned, so the time goes into the answer rather than consolidating the inputs.

Devices from many manufacturers feeding one platform
One

Connect Everything

Whatever you already own, and whatever you buy next. Sensors and loggers from any manufacturer, SCADA systems, and external sources pulled automatically over web API. You are never locked to one vendor, and new sources are added continuously.

This is historically the single biggest reason people choose infinitii flowworks: consolidating several systems into one platform requires no instrumentation to be replaced. Existing sensors, loggers and telemetry stay exactly as they are.

  • Any manufacturer's sensors and loggers
  • SCADA integration
  • Automatic web API ingestion, including third-party gauge-adjusted radar rainfall
  • Bulk historical import — no restriction on how far back the record goes
A live dashboard combining map, charts, site details and alarm summaries
Two

See it now

Near real-time data, alarming and notification, and dashboards built for a particular job. Every site on a map with its present value and alarm state. Graphing across sites with saved templates. Dashboards for the person who has to look at them — including people who sign in for their own view and never touch the rest of the application. This is what most customers buy today, and it matters most to operations.

And alarms that reach whoever is actually on duty, by web, email, SMS or voice, with dwell times so a passing spike does not wake anyone. This is what most customers use every day.

  • Live network map with alarm state by colour
  • Multi-site graphing, scatter plots and curve fitting
  • Custom dashboards, shareable with your team or a named group
  • Alarms by web, email, SMS and voice, with schedules and acknowledgment
Configuring a calculated channel that runs continuously against live data
Three

Make it yours

Calculated channels using FACE and FACE Pro, running continuously against live data, for prediction and pattern recognition. FACE builds them without programming: functions and if / and / or / else logic, line by line, and what comes out is always a calculated channel. FACE Pro runs your own Python and R — usually to produce a channel too, but it can also retrieve data, run a model simulation, or test pattern recognition against input channels. A calculated channel behaves like any sensor channel: graph it, alarm on it, report on it.

That includes running Storm Water Management Model (SWMM) and EPANET models against live data rather than a prepared input file. The API is the other half: it carries measured and calculated channels out to other applications and to public-facing websites — which is how a number of cities publish combined sewer overflow (CSO) event warnings to residents.

  • FACE — no-code calculated channels from functions and conditional logic
  • FACE Pro — Python and R, with NumPy, pandas and scikit-learn
  • SWMM and EPANET model integration
  • Predictive channels and pattern recognition
  • Deployed once; runs on all future data
  • An extensive API — carry channels out to other systems and public websites, and bring data back in, when configured to do so

Start from the problem

Select a focus area to see how infinitii flowworks is deployed for that kind of work.

Wastewater & I&I

Collection systems — capacity monitoring, inflow and infiltration (I&I) analysis, improvement planning and day-to-day operations.

Water

Distribution pressure, pressure reducing valve (PRV) performance, reservoir levels and water quality.

Rainfall

intensity-duration-frequency (IDF) curves, return periods, storm statistics and third-party radar rainfall.

Facilities

Pump stations, treatment plants and PRV stations — run hours, duty balance, compliance.

Streamflow

Hydrometric networks, stage–discharge ratings and flood stage alarming.

All solutions

Climate, industrial and visual monitoring as well.

Analysis delivered as a live channel
For partners

Bidding, specifying or supplying?

The subscription can sit wherever it works best. Many utilities hold it themselves; others would rather their engineering partner held it and handled the administration. Either way the utility's data stays the utility's, and the subscription can transfer to them when a project ends and the engineering firm's role is done. infinitii flowworks is often introduced through an RFP or RFQ, and we can help on that side of a bid.

If that is you, what follows is written for you rather than for the utility.

Ready to begin?

Start with your own data

A demo runs on your sites and your history, not a sample dataset. Bring a question you have not been able to answer easily.