Proof of Value

Prove it on 500 meters. Free.

A Proof of Value is a guided six-step run on your own meters, at no cost, ending in a readout you can take to your team. Start one, pause it, come back — your progress is saved with the POV.

1

Pull data

Run our queries against your FlowCal, on-premise or QCloud.

2

Upload

Drop in the four files — we check them before you continue.

3

Generate

Setpoints and an FCLoader file, built automatically.

4

Review

See how your exception counts would change, meter by meter.

5

Validate

Resolve every flagged meter to a decision.

6

Readout

A before/after summary to share with your team.

Step 1 · Pull data

Four queries against your own FlowCal

On-premise or QCloud, Oracle or SQL Server — the queries are the same, only the connection differs. Not the person who pulls the data? Email the whole query pack to whoever is.

Start with 25 to 100 meters.Every meter needs 13 months of history.Your first 500 meters are free.
Proof of Value step one — pull data from FlowCal
Choosing evaluation meters

Step 2 · Upload

Drop in four files, we check them first

Exception history, your current setpoints, 13 months of measured hourly data, and the 3-month exception period. The tool checks column names, meter count, and date range before you continue.

Column templates shown per file.Nothing runs until the files check out.
Uploading the four Proof of Value files

Step 3 · Generate

Nothing for you to do here

The tool creates the import, attaches your baseline, builds the before-and-after comparison, and produces an FCLoader file automatically.

Meters without enough history are set aside, not guessed at.They show up in Reports to review separately.
Generating smart setpoints

Step 4 · Review

See exactly how your exceptions would change

Current counts come from your uploaded history. Projected counts are what NDL setpoints would have produced against the same measured data — per meter, sortable, with charts behind every row.

Filter to biggest decrease, biggest increase, or little change.Charts show the NDL band against your current limit, hour by hour.
How your exception counts would change
Per-meter charts overview

Step 5 · Validate

Work every flag down to a decision

Meters an analyst flagged during review come here. Setpoints fine, or exclude — with a note. When every flag is resolved, the POV is complete.

Open flags block the readout on purpose.Decisions and notes stay on the record.
Validating flagged meters

Step 6 · Readout

The page you take into a funding discussion

Meters tested, exceptions before and after, what analysts decided, and the estimated impact in hours and dollars — using your own minutes-per-exception and analyst rate, extrapolated across your full meter count.

Download the readout, or print it.FCLoader file is right there when you are ready.
Proof of Value readout summary
Estimated impact and biggest movers