Aquatic Informatics Alternatives for Water Data, Pretreatment and Compliance Teams

Why water teams start looking for an alternative

The usual trigger is a mismatch between what your programme actually does and what the software assumes it does. Industrial pretreatment is the clearest example. Your ordinance has local limits, your permits carry conditions that were negotiated with specific industries, your inspectors follow up in a sequence your programme decided on, and your significant noncompliance determinations have to be defensible to a state reviewer. Configurable software gets you most of the way there and then hits a wall on the part that is genuinely local, which is the part that matters when a permittee disputes a violation.

The second trigger is budget shape. A mid sized utility with one pretreatment coordinator, a couple of inspectors and a lab is paying for a platform designed to serve programmes of every size. When renewal arrives and the coordinator counts how many of the available modules the team actually opens in a year, the maths starts to look unfavourable. That is not a criticism of the product. It is the normal tension of buying general purpose software for a specific programme.

The third trigger is data ambition. You have years of monitoring data, and somebody on council asks a question that spans sampling results, inspection outcomes, enforcement actions and billing. Answering it means pulling three exports into a spreadsheet, and now your evidence for a public claim lives on somebody's desktop.

What Aquatic Informatics genuinely does well

Time series water data management is much harder than it appears from outside. Sensor drift, gaps, corrections, provisional versus approved states, rating curve shifts, and the requirement that every edit be reversible and attributable are all real engineering problems. Building a hydrological data engine that hydrologists trust takes years, and a general purpose database with a dashboard on top will not do it. If continuous monitoring data is the core of your work, that capability is the strongest argument for staying exactly where you are.

The compliance products carry a similar advantage in a different direction. Pretreatment and permit management involves regulatory content that changes, reporting formats that agencies expect, and a paper trail that has to hold up under review. A vendor that maintains that content across many jurisdictions is absorbing work you would otherwise carry. Their reporting formats being familiar to state reviewers is quiet value that only shows up when you lose it.

Where it actually strains

Configuration ceilings show up first. Local ordinance language, unusual permit conditions and enforcement sequences that your programme designed tend to be approximated rather than modelled. Approximations are fine until the day you need the system to be the record of why you acted, and it can only tell you what was recorded, not why the rule applied.

Reporting rigidity is second. Standard reports cover standard obligations well. The council briefing, the rate study input, the environmental justice analysis by service area, the trend across a decade of a single industrial user: those tend to be built by hand. Once the manual version exists, it becomes the version people cite, and it is neither versioned nor auditable.

Third is integration burden. Your programme touches billing, GIS, laboratory systems, work orders and sometimes a permit portal. Each connection is a file transfer or an interface project, and utilities rarely have integration staff sitting idle. The common outcome is that the same industrial user exists under three slightly different names in three systems, and nobody wants to be the person who reconciles them.

Fourth is per site and per module economics. Buying by module means every capability you add is permanent recurring cost, and small agencies feel that most sharply, because the fixed cost of a platform is spread across a small programme. Larger agencies get better value from the same product, which is exactly why the answer to this question differs by size rather than by preference.

Your real options

Staying is genuinely correct for a lot of teams. If you manage continuous monitoring data at scale, if your compliance reporting is standard, or if your programme is small enough that any custom system would be unmaintained within two years, keep what you have and spend the effort on data hygiene and staff training instead. A cleaned up industrial user register and consistent sampling scheduling will do more for your programme than new software.

Switching vendors is the second option. Hach WIMS is long established for utility operational data, Kisters is a serious name in hydrological time series, and laboratory information management vendors cover the sampling and results side from another angle. Some utilities also consolidate into their existing enterprise asset management or work order platform, accepting weaker specialist depth in exchange for one system and one login. That trade is reasonable when compliance reporting is your smaller obligation and operations is your larger one.

The third option is a custom build, and the boundary matters. Do not rebuild a hydrological time series engine with correction and rating curve handling unless that is your organisation's core scientific work and you have the specialists to own it. Do build the programme layer: an industrial user and permit register that reflects your ordinance, sampling schedules with automatic non compliance flags, an inspector mobile workflow that works without signal in a plant basement, enforcement escalation that follows your response guide, letter and notice generation with your legal language, and a self monitoring report portal so permittees submit data instead of emailing PDFs to your coordinator.

When a custom build pays back

Build when your programme has meaningful local specificity that the platform cannot hold, because that gap is permanent and it grows. Build when the same data is being rekeyed between systems, since rekeying is both the cost and the source of the discrepancies you will spend later years resolving. Build when permittee self service would remove a large share of your coordinator's inbox. Build when you run several related programmes, such as pretreatment, fats and oils, stormwater and groundwater monitoring, and each currently has its own tool or spreadsheet, because one shared model across programmes is where the real efficiency sits.

Do not build if you are a single small programme with no internal technical support, if your requirements are actually standard and the frustration is about training rather than fit, or if the driver is a one off report you could produce another way.

Migration reality

Environmental data migrations are dominated by defensibility. You need sampling results with method, detection limits, chain of custody references and any qualifiers intact, because a result stripped of its qualifiers is not evidence. You need permit history with effective dates, violation and enforcement history exactly as issued, and inspection records with their attachments. Anything you might have to produce in a public records request or an enforcement dispute has to survive the move without alteration.

Run parallel for at least one full reporting cycle, and pick a cycle that includes a compliance determination so you can compare outcomes, not just data. Retrain in the field, not in a conference room, because inspectors abandon a workflow that fights them at a site. Keep the old system readable through your records retention schedule rather than trusting an export you have never queried.

Cost bands

Aquatic Informatics quotes by product and deployment rather than publishing list pricing, so the number that matters is your own renewal including modules, sites and support. On the custom side, from what Digital Heroes typically delivers: a focused programme build covering permit and user registers, sampling schedules, inspections, enforcement workflow and notice generation runs $45k to $110k over 10 to 16 weeks. A multi programme platform with a permittee portal, laboratory and billing integrations and public reporting runs $140k to $320k. Add hosting of a few hundred dollars a month and a maintenance allowance, because environmental rules change and the system has to change with them.

The honest recommendation

Split the decision by data type. Continuous monitoring and hydrological time series belong in a specialist system, and replacing that with something bespoke is a bad trade for almost every utility. Programme administration, inspections, enforcement and permittee self service are workflow problems shaped by your ordinance, and workflow shaped by local rules is exactly what custom software is good at. The strongest position for a mid sized agency is usually both: keep the specialist engine for the science, and own the programme layer that your inspectors, your permittees and your council actually interact with.