The deliverable problem

Consulting work on a collection system usually ends the same way: data is pulled from loggers, analysis is performed on the extract, and the findings are written up. The report is accurate on the day it is delivered and decays from then on. When the client asks the same question about next season, the work is repeated.

That is a constraint of the delivery mechanism, not of the analysis. The analysis itself — a dry weather flow derivation, an inflow and infiltration (I&I) estimate, a rating, a site-specific correction — is a rule, and rules can run continuously.

An analysis written in Python and deployed into a client's infinitii flowworks system
The alternative

Deliver the capability, not the document

A calculated channel can be built either way: in FACE you assemble it from functions and conditions without writing code, and in FACE Pro you write it in Python or R. Either is deployed once into the client's infinitii flowworks system and then runs against every reading that arrives afterwards. The output is a calculated channel — it graphs, it alarms, it reports, and it feeds other analysis.

The engineering judgement that went into it is preserved and applied continuously rather than captured in a PDF. And the method can stay yours: packaged as a function in FACE Pro, it runs inside the client's system while the client sees the result rather than the script. The client stops asking for the study to be redone, and starts asking what else can be built.

  • Written in Python or R, with NumPy, pandas and scikit-learn
  • Deployed once; runs on all future incoming data
  • Output behaves like any measured channel
  • Survives the end of the engagement — and so does the relationship
What it changes

What this changes commercially

The software requirement in the bid is answered

RFPs commonly ask for engineering and installation services plus a software solution, as one package. infinitii flowworks lets you put a complete response forward without building or subcontracting a platform. See RFP software requirements.

The work outlives the contract

A deployed channel keeps producing after the project closes. The client continues to use something you built, under your name, indefinitely.

The next project starts warmer

You are already inside the system where the next question will be asked, with the data history to answer it.

Your method stays yours

What you deploy is your analysis. infinitii flowworks provides the tools — the data, the execution and the distribution — not the analysis itself.

What your client gets out of it

This matters because it is what makes the arrangement durable. The utility is not acquiring a dependency on a consultant; it is acquiring a capability that happens to have been built by one.

Their data stops being organised by which firm collected it. The analysis is visible, checkable and re-runnable by their own staff. And what you have handed the people who brought you in is worth considerably more to them than the report they asked for.

Where to look next

FACE and FACE Pro

How calculated channels are written, deployed and run.

I&I and collection systems

The analysis most consulting engagements are built around.

RFP software requirements

What infinitii flowworks satisfies when a bid asks for a software solution.

Ready to begin?

Bring an analysis you deliver repeatedly

If there is a calculation your team reproduces for every client, that is the one worth deploying once.