A phosphate complex finds $11.3M a year in the plant it already runs

Thousands of readings, and no way to ask the right question

Your site makes sulfuric acid in three identical trains, and phosphoric acid on two filter lines. It also runs two cooling towers, a raw water supply, a demineralised water plant, a wastewater plant and a few smaller areas. Most of what the records show is paired equipment, so a unit that drifts can be compared with its twin beside it.

The sulfuric and phosphoric lines feed each other. Acid trains make steam and need cooling water. The filter lines need wash water and vacuum, and the cooling towers and water treatment plant supply the water. When one unit slips, its neighbours often show it too.

This is not a wastewater-led plant, so the audit judges each unit against its twin and its own past, not against a permit. The records give no permit limit, and the findings name none. Where the data cannot separate two causes, the notes say so.

Most large process sites are in this position. The control system keeps every reading inside its limits, and every unit is individually reasonable. What it cannot do is notice that two units built to behave alike have quietly stopped doing so. That is where these losses sit, and it is why none of them announced itself.

Find the loss, find the cause, price it, confirm it

AquaMesh does not assume that software saves a fixed percentage. It starts from the plant's existing control-system and historian data and works through five steps.

5 causes, each against its own twin

Each card shows the unit with the problem (red) against its identical twin (green) over the whole record, what the operator does about it, and how the saving is confirmed afterwards.

One lead is not counted. It is shown because it is worth a day of checking, and kept out of the total until a field check confirms it.

$11.3M a year, and where each dollar comes from

The same $11.3M two ways: by cause, and by the kind of cost it removes. Every priced line belongs to exactly one category, so no dollar is counted twice.

By cause

By kind of cost

"Of what the plant uses" compares each saving with the quantity measured in this record, scaled to a year of 8,059 operating hours. Electrical energy is set against the metered load in the data, not the whole site.

The water balance still closes

A saving that does not respect conservation of water is not a saving. For the largest water cause, evaporation is fixed by the heat the tower has to reject, so only the drained water, and the fresh water that replaces it, can change.

How confident to be

78% of the total rests on quantities read directly from the plant's instruments, such as concentrations, flows and power. The rest uses a physical assumption, such as the tower's drift loss. Prices are the plant's own unit costs; the table shows how far the total moves if each is wrong by the range tested.

What is not counted

The headline excludes the unconfirmed lead (up to $344,821/yr), any benefit from the instrumentation below, avoided failures, operator time and the effect of cleaner operation on downstream production. All are real; none is claimed.

Where the plant is blind, one probe pays for itself in months

Everything above came from instruments the plant already owns. A few costly conditions cannot be seen with them at all, and that is where AquaSpectra goes. It sits in the pipe and reads the water's full spectral fingerprint continuously, so a change shows up as it happens, not in tomorrow's lab result.

Capital$25,000per measuring point, to be firmed with a quote

Value counted$81,455/yrone sensor, one event a year, half the avoided loss

Simple payback4 monthson that one sensor

Savings it protects$2.5M/yrthe cooling-water saving, protected and not counted twice

What the plant can see today, and what the sensor adds

How early would it have seen the membrane slide?

The demineralised plant's recovery fell for 71 days before the end of the record, and the loss grew the whole time. Spectral change analysis is built to flag the first sign. The dashed line marks the point where about 15% of the slide had happened, instead of all of it.

How the value is counted

It is an estimate on stated assumptions: one fouling event a year, caught early, and only half the avoided loss counted. The cooling-water probes are shown with no value because they are early warning. They are what makes running the towers at higher reuse safe.

From finding to money on the bill

Five of the causes are settings or planned maintenance that the plant already schedules. The value arrives as each is done, and is confirmed against a baseline built from this same record, normalised for production and weather.

The full instrumentation package

Everything above came from data the plant already collects. Instrumentation comes after, and only where a costly condition cannot already be seen. Items that are early warning rather than savings are shown with no value, so the payback is not flattered by them.

The full report

The audit is the working behind every figure above: each finding, the evidence for it, how it was priced, and the check that confirms it.

What this assumes

Quantities are read from 125 measuring points over 120 days. The record covers one season, and cooling load and water use change through the year, so a full year of records would tighten every figure. Savings are ceilings that assume each fix is made and kept; they are not netted against the cost of the fixes, which is mostly labour and downtime the plant already plans for. Findings indicate; they do not prove, and each names the check that settles it. This is an example case study: the plant and its figures illustrate the method, and no named company is an AquaMesh customer.