PMIS for Water and Wastewater Utilities: A Complete Guide

# PMIS for Water and Wastewater Utilities: A Complete Guide

A Project Management Information System built for general industries will not serve a water or wastewater utility well. The gap is not cosmetic — it is structural. Utilities operate under public accountability standards, multi-decade infrastructure lifecycles, and capital program complexity that commercial project software was never designed to handle. This guide explains what a utility PMIS must do, what generic tools miss, and how to evaluate your options.

What PMIS Means in a Utility Context

PMIS stands for Project Management Information System. In a utility capital program, it is the authoritative system of record for every active construction project — from the moment a Notice to Proceed is issued through the final asset handoff to operations.

For a water or wastewater utility, that scope includes:

• **RFI tracking**: Every request for information, tied to the contract document or drawing that prompted it, with resolution dates and responsible parties logged
• **Submittal management**: Shop drawings, product data, and material certifications moving through a defined review and approval workflow
• **Change order control**: Potential change items, proposed change orders, and executed change orders with budget impact tracked in real time against the original contract value
• **Cost event logging**: Differing site conditions, owner-directed changes, and unforeseen conditions documented before they become disputes
• **Inspection records**: Daily field reports, non-conformance notices, and punch lists tied to contract milestones
• **NTP through closeout**: A complete timeline from project authorization to substantial completion, final completion, and CMMS handoff

That last item — the CMMS handoff — is where most utilities experience their most significant data loss. When construction closes out and institutional knowledge walks out the door with the contractor, utilities are left with paper as-builts, scattered submittals, and asset records that do not reflect what was actually built. A purpose-built PMIS prevents that by structuring closeout documentation from day one.

Why Generic Project Management Tools Fail Utilities

Platforms built for general project management — task boards, timeline tools, collaborative workspaces — solve coordination problems. They do not solve utility capital program problems.

The fundamental mismatch is data structure. A generic tool tracks tasks, milestones, and file attachments. A utility capital project requires tracked relationships between cost events and contract line items, between RFIs and drawing revisions, between submittals and installed equipment that will appear in your CMMS for the next 40 years.

When utilities try to retrofit generic tools to this purpose, they end up with workarounds: spreadsheets for cost tracking, shared drives for submittals, email chains for RFI resolution. The data exists, but it is not connected. When the project manager leaves, the institutional knowledge goes with them.

There is also the accountability problem. Public utilities must defend every capital dollar to their board, their ratepayers, and potentially to state or federal auditors. A PMIS built for utilities produces the documentation trails that make that defense possible. A task management tool produces screenshots.

SharePoint vs. SaaS: Understanding Your Options

Utilities evaluating a PMIS will encounter two broad categories of solutions.

SharePoint-based PMIS platforms are built on Microsoft's SharePoint Online infrastructure, which most utilities already own as part of a Microsoft 365 subscription. A well-implemented SharePoint PMIS uses structured lists for RFIs, submittals, and change orders; Power Automate for workflow routing; and Power BI for cost dashboards. When configured correctly by someone who understands both SharePoint architecture and utility capital programs, these platforms are highly effective. The advantage: your IT environment already owns the infrastructure, and your staff is already working in M365.

Cloud SaaS PMIS platforms are purpose-built applications hosted by the vendor. They may offer more out-of-the-box functionality for specific workflows, but they introduce a separate system that sits outside your existing M365 environment — which creates integration challenges with your finance system, GIS, and CMMS.

A third option — site templates — provides a standardized SharePoint project site structure that can be deployed consistently across every project in your portfolio. This approach ensures that every project starts with the same data structure, the same folder hierarchy, and the same list schemas, which is critical for roll-up reporting and cross-project portfolio management.

The right choice depends on your IT infrastructure, your in-house capacity to configure and maintain a SharePoint environment, and the scale of your capital program.

What a Utility PMIS Must Track

The following categories represent the minimum viable scope for a utility PMIS. If a solution you are evaluating cannot handle all of these natively — without custom development or spreadsheet supplements — it is not a utility PMIS.

Project financial controls:

• Original contract value
• Approved change order total and running revised contract value
• Pending change order value (the number your board actually needs to see)
• Forecast final cost vs. budget
• Contingency draw-down tracking

Document management:

• RFI log with submittal log, open items tracked by aging
• Submittal register with scheduled vs. actual review dates
• Drawing revision control
• Specifications and contract document version control
• Correspondence log

Field and construction management:

• Daily construction reports
• Inspector daily logs
• Non-conformance reports (NCRs) with corrective action tracking
• Photo documentation tied to project location or contract item
• Permit and regulatory compliance tracking

Closeout and CMMS handoff:

• As-built drawing collection and verification
• O&M manual assembly
• Warranty tracking with start dates tied to substantial completion
• Equipment data sheets formatted for CMMS import
• Punch list completion verification

CMMS Handoff: The Most Neglected Phase

Operations staff maintain infrastructure for decades. The quality of the data they inherit at project closeout determines how well they can do that. Yet in most utility capital programs, closeout is the phase with the least process discipline.

A PMIS built for utilities treats closeout as a structured workflow, not an afterthought. Required documents are identified at project kickoff. Equipment data is captured from approved submittals throughout construction, not assembled in a rush after substantial completion. CMMS asset records are pre-populated from project data, reducing manual entry errors.

When the handoff is done right, operations receives an asset that exists in the CMMS with its correct specifications, warranty dates, O&M references, and installation photographs — ready to be maintained.

Evaluating a PMIS: Questions to Ask

Before selecting a PMIS, ask vendors these questions directly:

**How does your system handle change order workflows?** You want a configurable approval chain, not a file attachment process.

**Can we track pending change items before they become executed change orders?** The ability to see unresolved cost exposure in real time is non-negotiable.

**How does RFI management connect to drawing revisions?** An RFI without traceability to the document it affected is a compliance risk.

**What does your closeout process produce?** You want structured data deliverables, not a zip file of PDFs.

**How does your system integrate with our CMMS?** If the answer is "manually," that is a red flag.

**Do your implementation staff have direct utility experience?** Software configured by someone who has never managed a capital project from the owner's side will miss things that matter.

Why Built-for-Utility Experience Matters

Every capital program has its own institutional logic. Water utilities operate under different procurement rules, funding structures, and regulatory requirements than commercial developers. A PMIS that was built by people who managed utility capital programs — not just software developers studying the industry from the outside — will reflect that logic in its data model, its workflows, and its reporting.

The difference shows up in the details: a change order workflow that mirrors your agency's internal approval authority matrix; a cost event form that captures the information your legal team needs if a dispute goes to mediation; a closeout checklist that meets your state's inspection requirements. These are not features that appear in a feature comparison table. They are the result of having built and operated these systems from inside the utility world.

Practical Takeaways

• Do not evaluate a PMIS against a feature checklist alone. Evaluate it against your actual project workflows, your reporting requirements, and your CMMS handoff process.
• Your M365 investment may already give you the infrastructure for a high-performing utility PMIS. The question is whether it has been configured correctly.
• If your current system — whatever it is — does not produce structured closeout data that feeds your CMMS, your capital program has a data problem that will compound over time.
• Involve your operations staff in the PMIS evaluation. The system serves them as much as it serves your project managers.
• A vendor who asks about your CMMS before they show you a demo is worth listening to. One who does not know what a CMMS is should be shown the door.

The right PMIS does not just organize your current projects. It builds an institutional data foundation that makes every future project faster, every audit cleaner, and every asset handoff complete.