NDL · Meter Setpoints

Setpoints that fit
your meters.

Meter Setpoints reads your own FlowCal history and calculates High/Low validation limits meter by meter — then shows the exception counts before and after, on the same period, so the value is proven before anything gets loaded.

Pay as you use — starting at $0.40 per meter.

No hardware changes. No IT project. Built for FlowCal-based measurement teams.

Why it's needed

Manual setpoints don't match real-world meter behavior.

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.

01

Assumes normal distributions

FlowCal validation assumes your data behaves like a normal curve. Many meters don’t — especially with operational changes and seasonal effects.

02

Percent-bad rules drive noise

Assuming a fixed percent of “bad” points floods analysts with fake exceptions and trains teams to ignore alarms.

03

Manual limits are slow and brittle

Tuning high and low limits one meter at a time is slow, hard to repeat, and breaks the moment behavior shifts.

04

Standard stats miss real issues

Basic min/max or standard-deviation rules can’t see complex patterns. NDL models the full distribution so you keep the real exceptions.

How it works

From FlowCal data to loadable limits in three steps.

Step 01

Upload your FlowCal data

Start with a simple export. NDL ingests hourly or daily values per meter along with your existing validation limits.

No database changes required.
Works with typical FlowCal exports.

Step 02

NDL learns each meter

Our models capture skew, multiple modes, and operational nuance instead of forcing everything into a normal curve.

Per-meter models, not blanket rules.
Finds limits too tight and too loose.

Step 03

Export optimized limits

NDL generates recommended high and low validation limits you load back into FlowCal, with a clear rationale.

Fewer nuisance exceptions.
Traceable, defendable change history.

−85%

exception volume on the same period, sample account

13 mo

of history is all we need to build a per-meter model

$0.40

per meter, usage-based — no platform fee

500

free meters in your Proof of Value

The product

Upload, review, load. That's the whole loop.

Walk through a Proof of Value →
Calculated Limits report in Meter Setpoints

Benefits

What measurement teams get with Meter Setpoints.

Built for the analysts who live in FlowCal and are tired of noisy validation rules.

Fewer false positives

Cut exception noise so analysts spend their time on real issues instead of clearing nuisance alarms.

Analyst time back

Automate the heavy lifting of setpoint tuning and recurring reviews — without adding headcount.

Defensible limits

Every recommendation is backed by the underlying meter data and model, giving you an audit trail for reviews.

Scales across assets

Apply one consistent, explainable methodology to meters across basins, systems, and operating regions.

Pricing

Pay only for the meters you use.

Usage-based pricing, designed to return measurable value in analyst time and reduced noise.

$0.40per meter
No hardware to install or maintain.Scale up or down as your meter count changes.Designed for 3–4× return in analyst time.

Review and accept the agreement, add billing details, and receive your login — all online.

FAQ

Questions measurement teams ask.

Does this change how FlowCal is configured?

No. Meter Setpoints works alongside FlowCal. You export data, we recommend limits, and you decide which to load back. Your existing setup stays intact.

What data do you need?

At minimum, 13 months of hourly data per meter (every third hour is enough) for the meters in scope — meter number, timestamp, volume, differential pressure, pressure, and temperature.

What if I am not the person who pulls the data?

Send the query pack to whoever is. It covers on-premise FlowCal and QCloud, Oracle and SQL Server, and needs no integration work.

How is data security handled?

Data is encrypted in transit and at rest. Access is restricted to your organization, and you control what is uploaded or retained.

What happens to meters without enough history?

They are set aside rather than guessed at. Every one shows up in the No Validations report with the reason, so you can review them separately.

Can I start with a subset of meters?

Yes — and you should. Most teams start with 25 to 100 meters, then scale once they have seen the before/after on their own data.