[ The Builder ]

My name's Chris Felle. I have a Maryland Class 5A wastewater license. Before that I did environmental field work and GIS.

During Hurricane Maria I did emergency response mapping. I saw firsthand how an information gap could turn a one-day trip to get supplies to an area into several days, and sometimes that was the difference between kidney dialysis getting there in time and not. I've been acutely aware of information gaps since, and I try to close the ones I can.

I work on the floor: running processes, handling upsets, managing solids, and doing the math to see if something's heading the wrong way. I couldn't find the tools I wanted in one place, so I built them. Everything here is within what the 5A covers: activated sludge, nutrient removal, digestion, dewatering and effluent compliance.

[ Why It Exists ]

A lot of the technical material online is from vendors or behind a paywall, spread across manuals, sales guides and academic papers. This site has no vendors, sponsors or affiliate links. The goal is something that works on a phone, for plants with spotty WiFi.

[ AI & Authorship ]

I used AI tools to help build this. They drafted text, wrote code and organized the structure.

They didn't pick what goes on the site, check that the numbers match real operating conditions, or answer for whether the guidance is right. That's me, and I use the same tools on shift at a real plant.

If something's wrong, open a GitLab issue and it will get an answer.

[ How to Contribute ]

It's open source and the code is on GitLab. Operators, engineers and anyone with field experience can help.

Useful things: corrections to reference data, formulas that are wrong or fail on edge cases, calculators you want added, parameters for the tables, field context for a guide, or sections that should exist and don't.

Open a GitLab issue for suggestions and corrections, or a merge request if you'd rather add the content or code yourself. You don't need to code to file an issue. Just say what's missing or wrong.

I'd especially like guides from other operators, since what nobody writes down goes when people change jobs. Or email hello@wwtp.tools if you'd rather not post it publicly.

Step-by-step guide to contributing on GitLab →