Wēlr
Water & wastewater · Water & wastewater equipment OEMs

Permit-linked performance — and the FSE qualified to defend it.

Water and wastewater equipment OEMs — Xylem, Veolia Water Technologies, Suez (now Veolia), Pentair, Evoqua (now Xylem), Grundfos — ship UV reactors, membrane systems, pumps, blowers, and chemical-dosing equipment into investor-owned utilities, municipal utilities, and industrial sites. Your QMS sits under ISO 9001:2015, ISO 14001 / 45001, and increasingly IEC 62443-4-1 (secure product-development lifecycle — the rising supplier requirement as utility OT cybersecurity tightens). Your products certify against NSF/ANSI 60 / 61 / 372 for potable contact and against AWWA C / D / M series standards. Your customer-facing surface includes LTSA performance audits, customer NPDES / SDWA permit renewals, and customer consent decree milestone evidence. Wēlr is the install-base service record that travels with the asset — and the evidence that proves performance against the customer's permit posture.

ISO 9001:2015 · 14001 · 45001 (QMS)IEC 62443-4-1 (secure product dev)NSF/ANSI 60 · 61 · 372 (product cert)AWWA C · D · M seriesEPA LCRR alignment
The service gap

Four pains across the OEM service motion.

  • 01

    Customer permit-renewal evidence reconstructed every cycle.

    When customer NPDES permit (5-yr cycle) or SDWA permit comes up for renewal, the OEM is asked for vendor performance evidence — equipment availability, throughput, treatment efficiency, parts consumption, response-time SLAs. Reconstructed from CMMS records, telemetry archives, warranty databases, and customer reports at every renewal.

  • 02

    FSE credentialing matrix at customer utilities tracked by spreadsheet.

    State-specific operator certifications (where the FSE is doing operator-class work), confined-space, HAZWOPER, NSF/ANSI material handler for product-contact replacement, drug-and-alcohol cycle, geographic work authorization, and LTSA-specific OEM qualifications — tracked per customer in spreadsheets. Dispatch optimizes geography first; credential gaps surface at site arrival.

  • 03

    Fleet monitoring tells you something is wrong; nothing closes the loop.

    UV reactor health, membrane fouling trends, dosing pump performance across the install base — visible in fleet monitoring. None of it dispatches a credentialed FSE against the signal, schedules the on-site execution, and folds the closure evidence back to the fleet view. The work-execution layer between fleet alarm and credentialed FSE doesn't exist as a product.

  • 04

    Customer consent decree milestone evidence pulled from CMMS quarterly.

    Utility customers under EPA consent decrees ask vendors to demonstrate operational performance against decree-specific metrics — throughput sustained, treatment efficiency met, response times honored. OEM-side evidence is reconstructed from CMMS records, telemetry archives, and warranty databases for every quarterly milestone.

What Wēlr brings

Four primitives. One permit-linked install-base record.

01CAPABILITY

Permit-linked performance record per customer

Equipment availability, throughput, treatment efficiency (TSS, BOD, turbidity, log reduction), parts consumption, response-time SLA performance — keyed per customer permit (NPDES, SDWA, LCRR, consent decree), per asset, per reporting period. Renewal-prep is a query against the system.

02CAPABILITY

FSE credentialing matrix on the dispatch path

State operator certifications (where applicable), confined-space, HAZWOPER, NSF/ANSI material handler, geographic work authorization, LTSA-specific OEM qualifications — all live as first-class technician attributes. Dispatch fails closed on incomplete credential set for the customer site and task class.

03CAPABILITY

Fleet signal → credentialed dispatch closure

UV health, membrane fouling, dosing pump performance signals attach to a dispatched FSE with credentials verified at dispatch. Where fleet-monitoring platforms tell the OEM something is wrong, Wēlr completes the work-execution loop — alarm → credentialed dispatch → on-site execution → evidence-back-to-fleet on one record.

04CAPABILITY

Customer consent decree evidence as a query

Decree-specific metrics tracked per customer · vendor performance against each metric · quarterly evidence packet is a query, not a quarterly reconstruction. LCRR LSL replacement progress tracked through the same record at consenting customers.

Vs. the alternatives

Why not build it, or extend the field-service platform you already run?

Most water-equipment OEMs face the same three options. Build in-house (multi-year project; specialized permit-linked performance schema; an FSE org that has to ship while engineering builds). Extend a generic field-service platform (no permit model; no credentialing matrix; no consent decree milestone tracker). Or Wēlr.

CapabilityWēlr Build in-house
24+ mo · 10 engineers · ~$5M
Generic field-service platform
ServiceMax · Salesforce FS · IFS
Permit-linked performance record per customer (NPDES · SDWA · LCRR)First-class data modelMulti-year buildBolt-on
FSE credentialing matrix on dispatchAuth-gated · fails closedSpreadsheet per customerSpreadsheet matrix
Fleet alarm → credentialed dispatch closureSingle workflowCustom integrationTwo systems · manual handoff
Consent decree milestone evidence as a queryQuery, on demandQuarterly reconstructionPer-customer rebuild
IEC 62443-4-1 product-dev-lifecycle evidence per product lineStructural per product lineCustom integrationNot modeled
The artifact your customer's permit cycle asks for

Permit-linked performance — pre-assembled per customer, per cycle.

Your customer's NPDES permit comes up for renewal in 18 months. Their consent decree milestone is due in Q4. Their LCRR LSL replacement audit is in six months. Wēlr maintains vendor-performance evidence pre-assembled per customer permit cycle — availability, throughput, treatment efficiency, parts consumption — keyed against the permit, the decree milestone, and the LCRR posture. When the customer asks, the renewal package is a query, not a quarter-long reconstruction.

  • Performance evidence keyed per customer permit (NPDES · SDWA · LCRR · consent decree) · per asset · per reporting period
  • Renewal packages pre-assembled — customer asks; export builder produces in the customer's required format
  • NSF/ANSI 60 / 61 / 372 product certifications travel with the asset record · proof-of-product-compliance on demand
  • Consent decree milestone evidence tracked against decree-specific metrics · quarterly reporting is a query
Illustrative · example evidence
Permit-linked performance · Filtration system FS-2841
5 customer permits · evidence pre-assembled · 1 renewal in flight
PERM-FS-2841NPDES · SDWA · LCRR · consent decree
CustomerPermit · cycleAvailability · perfEvidence posture
U1 (NYC DEP)NPDES · 2027-0999.4 % · 96.2 % TSSReady
U2 (LADWP)SDWA · 2026-1199.8 % · 99.7 % removalReady
U3 (Boston MWRA)Consent decree Q498.1 % · 97.4 % removalQ4 milestone ready
U4 (DC Water)NPDES · renewal in flight99.6 % · 98.8 %Renewal package ready
U5 (SF PUC)SDWA + LCRR99.2 % · LSL 18 % replaced · on trackLCRR evidence ready
Decision-maker's checklist

If any of these are true, we should talk.

  • Customer NPDES, SDWA, or LCRR permit renewals required you to reconstruct equipment performance evidence from CMMS, telemetry, and warranty databases — every cycle.
  • Your FSE credentialing matrix at customer utilities is tracked on a spreadsheet across state operator certs, confined-space, HAZWOPER, NSF/ANSI material handler, and LTSA qualifications — and gaps surface at site arrival.
  • Your fleet monitoring tells you something is wrong with the install base but doesn't dispatch a credentialed FSE against the signal — the work-execution layer that closes the loop doesn't exist.
  • Your customers under EPA consent decrees ask quarterly for vendor performance evidence against decree-specific metrics — and the assembly is a recurring project across CMMS, telemetry, and warranty databases.
  • A major utility customer issued a supplier finding or LTSA performance dispute in the last cycle, and the root cause was evidence you couldn't reconstruct inside the response window.
Founding partner program — accepting applications

A small founding cohort is shaping Wēlr for water & wastewater equipment oems.

Founding partners get preferential pricing, a direct line to engineering, and meaningful influence over the Water & wastewater roadmap. Limited to a small cohort per vertical.

  • Preferential pricing
  • Direct line to engineering
  • Roadmap influence
  • Limited cohort
Apply to the founding water-equipment-OEM cohort
Next step

Ready to stop stitching service evidence together?

If your team is juggling PDFs, support packages, work orders, customer updates, and QA evidence across five systems, Wēlr is worth a look.

Welr LLC · Delaware