Equipment maintenance software that reads the machines itself.

Backoffice plans the week from live meter readings, and Field Office runs it on site.

Flowplan Backoffice, showing consumption and service tasks across a fleet of machines

One integrated platform.

From consumption data to invoicing, the Flowplan software brings insight, service, and billing together in one place.

Your whole operation on one screen.

Your overview, your layout

Smart dashboard

The first thing you see when you log in: a fully customisable dashboard where widgets cover every part of the operation, from installations and tasks to usage and service.

  • Widgets for everythingLive map, task calendar, usage and service stats: every corner of the app has a widget.
  • Drag and dropArrange the layout so the overview fits your workflow.

Where it fits

It does not replace your field service system.

Most service teams already run equipment maintenance software of some kind, to schedule work and raise invoices. Flowplan does not ask you to move off it. The platform sits underneath: it reads the machines, works out what needs doing and when, and puts that into the system your team already opens every morning.

Service tasks go to Dynamics 365 Field Service or Dobby. Filter, leak and connection events are pushed automatically. The API runs both ways, so you can create and update customers, locations and installations from your own systems, and read consumption back out per customer and per location.

What changes is where the work comes from. A task appears because a filter is close to its real capacity, or because a line is running while the venue is shut. Nobody set that interval by hand.

Service tasks grouped into windows per location in Flowplan Backoffice
Is this a CMMS?

No. A CMMS holds your asset register and the jobs against it, and it relies on someone entering what happened. Flowplan measures the equipment directly, works out what needs doing from that, and hands the job to the system you already use. Teams run both.

How is it different from the equipment maintenance software we already run?

Most equipment maintenance software schedules from a date and a service interval. This schedules from the machine: litres through the filter, temperature at the outlet, hours of use. The interval stops being a guess, so visits land where they are needed.

Does it replace Dynamics 365 Field Service or Dobby?

No, it feeds them. Service tasks are sent across, and filter, leak and connection events are pushed automatically. If you run something else, the API goes both ways.

What does the technician actually use?

Field Office on a phone. A QR scan pulls up the machine, its filter and its history, the technician logs the swap in a couple of taps, and the day's stops and packing list work offline.

Where does the data come from?

A Beam on the machine, reading its own temperature sensor and whatever meter sits on the line. Beam reads third-party meters too, so a mixed fleet does not need standardising on our hardware first.

Can our customers see their own numbers?

Yes. You choose which consumption and performance figures each customer gets access to.

Can we invoice from it?

Water use and service events are logged per customer and per location, and come out through reports or the API into your invoicing flow. Nobody re-reads a meter to raise the invoice.