PIMS Software: A Complete Guide for Mid-Sized Organizations

If you run a pretreatment program, you already know where the week goes. A permit is up for renewal and the file lives in three places. An inspector comes back from a site visit with a paper form that someone has to retype. Sampling results arrive by email from the lab. And every year the annual report has to be assembled by hand from all of it, under a deadline, for a regulator who is entitled to ask how you got each number.

None of that is a staffing problem. It is a systems problem, and it is the reason pretreatment information management system software exists.

This guide covers what a PIMS actually does, when a program has outgrown spreadsheets, what to look for when you evaluate options, and why a growing number of POTWs are building theirs on the Microsoft 365 they already pay for instead of signing another subscription.

What a pretreatment information management system actually is

A PIMS is the system of record for an industrial pretreatment program. It holds your industrial users, their permits, their sampling and monitoring data, your inspections, your enforcement actions, and the reporting you owe the state and EPA.

The regulatory frame is the National Pretreatment Program under 40 CFR Part 403. If you are a POTW with an approved program, you are responsible for permitting your significant industrial users, inspecting and monitoring them at least annually, enforcing your local limits, and reporting on all of it. A PIMS is what turns those obligations into a workflow instead of a scramble.

The word “system” matters more than the word “software”. Plenty of programs technically have software and still run on a spreadsheet, because the software does not cover inspections, or does not talk to the lab, or produces a report nobody trusts without checking it by hand.

Signs your program has outgrown spreadsheets

Most pretreatment programs start on spreadsheets for a good reason. They work, they are free, and one person can hold the whole thing in their head. The trouble starts when the program grows or that person moves on.

• Permit deadlines are tracked by memory or a calendar reminder. A missed renewal is a compliance finding, not an inconvenience.
• Inspections come back on paper. Field notes get retyped, photos live on a phone, and the record of what was observed is separated from the record of what was permitted.
• Lab results are re-keyed. Every manual transfer is a chance to introduce an error into a number you may have to defend.
• Nobody can answer a question quickly. “When did we last inspect this user and what did we find?” should take seconds.
• The annual report takes weeks. If assembling it means reopening a year of files, the data was never really in a system.
• One person is the system. If your program’s institutional knowledge would walk out the door with a retirement, that is the risk to fix first.

Encina Wastewater Authority reached this point with a legacy system they had outgrown, and moved their source control program onto a platform their own team controls.

What to look for in PIMS software

Permit and industrial user management

Every industrial user in one place, with the permit, its limits, its expiration, its history, and its correspondence attached to the record. Renewals should surface before they are urgent, not after.

Inspections your field staff will actually use

Inspections belong on a phone or tablet, with the permit conditions visible while the inspector is standing on site, photos attached in the moment, and the report filed before they get back to the truck. If the field tool is harder than paper, your staff will keep using paper.

Sampling, monitoring, and LIMS integration

Sampling schedules, chain of custody, and results tied to the user and the permit limit they are being measured against. If your lab runs a LIMS, the results should flow in rather than being typed twice. LIMS integration is usually the single biggest reduction in manual work available to a pretreatment program.

Violations and enforcement

Automatic comparison of results against local limits, so a violation is flagged when it happens. Then the enforcement response tracked from notice through resolution, because significant noncompliance determinations depend on that record being complete.

Reporting that does not need rebuilding

The annual report, SNC determinations, and state submissions should be produced from the data you have already captured. If your reporting is a separate exercise from your record keeping, you have two systems and one of them is wrong.

Audit trails and retention

Who changed what, when, and why. Records retained for the period your program requires, with the history intact. This is the part nobody thinks about until an audit, and the part that is very hard to add later.

Mapping and asset context

Knowing where a user sits in your collection system changes how you investigate a problem. GIS context is not a luxury for a program dealing with FOG or an industrial discharge investigation.

The option most programs overlook: build it on what you already own

The default assumption is that a PIMS means buying a purpose-built product from a vendor who serves pretreatment programs. That is one route, and for some agencies it is the right one.

The route that gets overlooked is that most public agencies are already paying for Microsoft 365, and most are using a fraction of it. SharePoint holds the records and the permits. Power Apps gives inspectors a mobile form. Power Automate handles the renewal reminders, the routing, and the escalations. Power BI produces the dashboards and the reporting. It is all under the licensing your agency already has.

Three things tend to matter most to the agencies that choose this route:

• You own your data. It sits in your tenant, under your security and your retention policy. You are not asking a vendor for an export.
• No forever licensing. You are not adding a per-seat subscription on top of the one you already fund every year.
• It fits your program, not the average program. Local limits, permit types, and enforcement procedures vary between agencies. A configured system can match how you actually work.

The honest trade-off: this is a build, not a purchase, and it needs a partner who has done it before in a regulated environment. A product you buy off the shelf is faster to stand up. A system built on your own stack fits better and costs less to keep.

What changes when it works

Programs that make this move usually report the same handful of results. Inspections are filed the same day instead of the same week. Permit renewals stop being a source of anxiety. The annual report is assembled from data that was already correct. New staff can answer a question about an industrial user without asking the person who has been there fifteen years.

The measurable version: hours returned to your source control staff, a shorter reporting cycle, and a complete record when a regulator asks for one. Our work with Encina Wastewater Authority is the clearest example of what that looks like in practice.

How to evaluate without a year of procurement

1. Write down where the time actually goes. One week of honest tracking across permitting, inspections, sampling, and reporting will tell you which part to fix first.
2. Pick the worst one and scope only that. Getting inspections off paper is a common starting point because the benefit is immediate and visible to the people doing the work.
3. Check what your agency already licenses. Ask IT what your Microsoft 365 plan includes. The answer often changes the budget conversation.
4. Ask about ownership and exit up front. Where does the data live, who can export it, and what happens if you change direction in five years.
5. Talk to a peer agency. Pretreatment is a small world. Someone near you has solved the problem you are looking at.

You do not have to replace everything at once. Small steps to giant leaps is a reasonable way to run this, and it keeps the risk where a public budget can carry it.

One acronym, three meanings

PIMS is used for several different systems, which makes searching for it confusing. Worth being clear about which one you need.

• Pretreatment Information Management System. Industrial pretreatment compliance for POTWs, which is what this guide covers and what we build.
• Permit and Inspection Management System. Overlapping and often the same need described differently, covering industrial user permits and inspections.
• Project Information Management System. A different discipline entirely, covering documents and controls on a capital project. We cover that one in our guide to PIMS for project management.

Common questions

Do we need a PIMS if our program only has a handful of industrial users?

Not necessarily. A small program with stable users can run well on a simple system. The question is not how many users you have, it is whether your records would survive an audit and a staffing change. If the answer is no, size is not the issue.

Can this really run on Microsoft 365, or is that a stretch?

It runs on Microsoft 365. SharePoint, Power Apps, Power Automate, and Power BI cover records, mobile inspections, workflow, and reporting respectively. The work is in configuring it to your program, not in whether the platform can do it.

How does a PIMS help with the annual report?

By making the report a query rather than a project. If permits, inspections, sampling results, violations, and enforcement actions are captured as they happen and tied to the right user, the report is assembled from data you already have. See our guide to EPA pretreatment compliance for what the report has to contain.

What about NPDES permit tracking?

Related but distinct. Your pretreatment program sits under your own NPDES permit, and many agencies want both tracked in one place. Our guide to NPDES permit tracking software covers the difference between tracking permits you hold and permits you issue.

How long does an implementation take?

It depends on scope, and any honest answer starts there. A single workflow such as mobile inspections is a matter of weeks. A full program migration off a legacy system is a project measured in months, and it is usually phased so your team gets value before the whole thing is finished.

Related reading: pretreatment program management software, pretreatment inspection software, and wastewater pretreatment software.