Assumes normal distributions
FlowCal validation assumes your data behaves like a normal curve. Many meters don’t — especially with operational changes and seasonal effects.
Why it's needed
FlowCal is powerful — but its validation assumes your meter data is normalized. Real meter data is often skewed, multi-modal, and messy. NDL models the distribution each meter actually has, so you get defensible limits for every meter.
FlowCal validation assumes your data behaves like a normal curve. Many meters don’t — especially with operational changes and seasonal effects.
Assuming a fixed percent of “bad” points floods analysts with fake exceptions and trains teams to ignore alarms.
Tuning high and low limits one meter at a time is slow, hard to repeat, and breaks the moment behavior shifts.
Basic min/max or standard-deviation rules can’t see complex patterns. NDL models the full distribution so you keep the real exceptions.
Every exception an analyst clears that wasn't really an exception is time taken from the one that was. At scale, the noise is the problem.
A few minutes per exception, thousands of times a month, is a full-time role spent on alarms that were never real.
When most exceptions turn out to be nothing, the team stops trusting the queue — and the real problem waits.
When nobody can say why a limit is what it is, every audit and every handoff starts from scratch.
Cut exception noise so analysts spend their time on real issues instead of clearing nuisance alarms.
Automate the heavy lifting of setpoint tuning and recurring reviews — without adding headcount.
Every recommendation is backed by the underlying meter data and model, giving you an audit trail for reviews.
Apply one consistent, explainable methodology to meters across basins, systems, and operating regions.