Build vs Buy Industrial Pretreatment Program Software for a POTW

For most treatment works the answer is buy, and it is not close

A pretreatment programme is regulated arithmetic wrapped around local judgement, and the arithmetic has been packaged for a long time. Linko has served this market for years, SwiftComply covers pretreatment alongside fats, oils and grease programmes, and Aquatic Informatics holds the broader water data side. Any of them will handle the common shape of a programme: an industrial user register, permits, sampling, results, violations and the annual report.

If you permit a dozen or two industrial users with stable local limits and no satellite communities, buy. The subscription will cost less than the meetings you would hold about building, your coordinator will be productive in weeks, and the money saved buys inspection time, which is what actually protects the plant's own discharge permit. We tell utilities this on discovery calls more often than we quote them, and it is the right answer for a large share of programmes.

Buy also if your real constraint is staffing. One part time inspector and a coordinator with a filing cabinet is not a software problem, it is a capacity problem, and custom software will not sample anything. A packaged product removes data entry. It does not remove the site visit.

One thing to check before signing either way: pretreatment products commonly price by permitted user count. If your utility is likely to annex a satellite community or absorb another system's industrial users, ask how the subscription changes, because your user count can jump without your staffing changing at all. That clause is worth reading before it becomes a budget surprise in a year when you already have a rate case.

The local complications that break a packaged model

The regulatory frame is public and identical everywhere. General pretreatment regulations sit in 40 CFR Part 403, categorical standards live in Parts 405 through 471, and significant noncompliance is defined arithmetic: chronic violation when 66 percent or more of measurements in a six month period exceed a limit, technical review criteria violation when 33 percent or more exceed the limit multiplied by 1.4 for most pollutants and 1.2 for pH and oil and grease.

What is not identical is everything else. Your local limits came from your own headworks analysis. Your enforcement response plan was adopted by your own board. Your surcharge formula sits in your own ordinance. Your billing system is whatever the city bought over a decade ago. Packaged products treat these as configuration, and for a straightforward programme that works.

It stops working in four situations. First, when an industrial user runs two regulated processes under different categorical standards plus local limits, with a combined waste stream formula, so determining the operative limit for a given sample on a given date requires a person who has been there ten years. Second, when satellite communities discharge into your system with their own industrial users, which layers the permitting relationships and effectively doubles the model. Third, when surcharge billing is a meaningful revenue line calculated in a monthly spreadsheet handed to a billing clerk, where errors in the undercharging direction go unnoticed for years. Fourth, when your last programme audit produced findings on recordkeeping or enforcement consistency, because inconsistent enforcement is both a finding and a defence a user's consultant will raise later.

Costing a build inside a municipal budget cycle

The build side prices predictably. A focused first release covering the industrial user register, permits with structured effective dated limits, an automatic sampling schedule with mobile capture and electronic lab deliverable import, automatic violation and significant noncompliance evaluation, and a generated annual report runs $55,000 to $120,000 and ships in ten to sixteen weeks. A full platform adding the enforcement ladder with document generation, an industrial user portal for self monitoring submission, surcharge billing integration, inspection forms and fats, oils and grease or hauled waste handling runs $130,000 to $320,000 phased over six to ten months.

Cost rises with the number of distinct categorical standards your users fall under, since each has its own structure. Combined waste stream formula users are genuinely intricate. Utility billing integration is usually the hardest technical piece because municipal billing systems are old and their interfaces are undocumented. Multiple laboratories with different electronic deliverable formats add mapping work. A satellite programme adds a whole permitting layer.

Then the constraint that is unique to public buyers and that nobody puts in a software comparison: procurement. A build over your utility's threshold requires a formal solicitation, evaluation, and council or board approval, and that process commonly adds three to six months before anyone writes a line of code. Your annual report deadline and your state programme audit do not move to accommodate it. Working backwards from those dates, rather than forwards from a kickoff, is the only realistic way to schedule this. Utilities that ignore it end up approving a contract in the same quarter the audit lands.

Budget fifteen to twenty percent of build cost annually for hosting, support and continued work, and confirm that line survives the next budget cycle before you start.

The costs that show up after approval

Four items. The first is permit modelling. Every complicated permit has to be represented properly as effective dated limit rules attached to outfalls and monitoring points, each knowing its basis, whether local limit, categorical standard or negotiated condition. Coordinators routinely discover ambiguities in their own permit documents during this work. That discovery is valuable and it is also unbudgeted staff time.

The second is historical validation. Run the new violation evaluation in parallel against the last two years of results before trusting it. This does two things: it proves the arithmetic, and it surfaces past determinations that were wrong. Decide in advance, with your attorney, what you will do if it finds a user who should have been published and was not.

The third is the billing interface. Ask your billing vendor, by product name, what integration they actually support. Very often the answer is a scheduled file drop with a fixed layout rather than an interface, and the layout is documented in an email from 2014. That conversation belongs in week one, not month four, because it is the single most common cause of a slipped phase two.

The fourth is the deviation path. Your enforcement response plan sets out escalation, but coordinators exercise judgement, and a system that only permits the rule following path will be worked around until the record becomes fiction. Allowing deviations with a recorded reason is a design requirement, and it is what turns the enforcement record into something defensible rather than merely tidy.

A three permit test

Take your three most complicated permits and ask any vendor or developer to show you how each limit would be stored and evaluated for a sample taken on a specific date at a specific monitoring point.

If they need to simplify your permits to fit their model, the model is wrong for you and that is your answer. If they can explain effective dating, limit basis and sample type without prompting, they understand compliance rather than results storage. Ask the same people to implement the significant noncompliance criteria on a whiteboard, including the chronic test and the technical review criteria multipliers. It is not hard arithmetic, and watching someone reason about rolling six month windows tells you whether they will handle the edge cases.

Then count four things internally. How many significant industrial users do you permit? Above roughly sixty, the case is open. Do satellite communities discharge into your system with their own users? Is your surcharge programme a meaningful revenue line calculated by hand? Did your last programme audit produce findings on recordkeeping or enforcement consistency?

Two or more yes answers is a genuine build case. One is usually solved by buying a packaged product and writing down the rules that currently live in one person's head. None means keep the filing cabinet, keep the spreadsheet, and spend the money on inspections.

How to phase it, and how to interview

Phase one is significant industrial users only: register, permits with structured limits, the sampling schedule, lab deliverable import, and automatic violation and significant noncompliance evaluation, plus the annual report. Non significant users, fats, oils and grease, and hauled waste can wait, and nothing bad happens in the meantime. Surcharge billing belongs in phase two purely because the billing interface is the item most likely to slip.

Our position on this category, stated plainly: the arithmetic is defined in federal regulation and the judgement is entirely local. Software should do all of the arithmetic and none of the judgement, and it should record both. Most programmes today do the reverse, with people doing the arithmetic and nobody recording the judgement, which is exactly backwards from what an audit rewards.

When interviewing, ask how they determine the operative limit for a sample. Ask what they have integrated, by product name, on the laboratory side and the billing side. Ask how deviations from the enforcement response plan get recorded. Ask who owns the code, the cloud accounts and the data, in writing before kickoff, and ask about export format alongside ownership, because this is a compliance record that may be evidence in an enforcement matter years later.

Digital Heroes works from a written product requirements document before any code, which here means your limit structures, significant noncompliance evaluation rules and enforcement escalation are agreed on paper with your coordinator and your attorney. The team is fifty plus people across more than 2,000 delivered projects, holds Fiverr Vetted Pro status, and publishes to 2.5 million subscribers at Digital Marketing Heroes on YouTube. Contracting runs through an India LLP, a US LLC or a UK LTD so assignment happens under your own jurisdiction, and the client owns the repository from the first commit.

When you are ready to turn this into a specification, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You keep the specification either way.