Automated Operator10 Permit Exceedance Alerts
Every morning, WebRun opens Operator10, compares yesterday's logged results against your NPDES permit limits, flags any daily maximum or monthly average heading over the line, alerts your compliance lead in Microsoft Teams, and drafts a heads-up email to management for review when a true exceedance is confirmed.
How do I catch NPDES permit exceedances from Operator10 automatically?
WebRun opens Operator10 every morning and compares yesterday's logged results against your NPDES permit limits for each outfall. It flags any parameter over its daily maximum or rolling average, alerts your compliance lead in Microsoft Teams, and drafts a management heads-up email for review, so exceedances surface early and nothing is reported without human approval.
- Exceedances are flagged the morning after they log, not at month end
- Parameters trending close to a limit get a warning before they breach
- No regulatory notice goes out without human review and approval
Built for compliance leads · wastewater operators · utility managers · environmental compliance staff
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
allmaxsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
AllMax Operator10 - check readings against permit limits
WebRun opens Operator10 to check readings against permit limits. - Open Operator10 and load the DataViews that hold permitted parameters
- Read yesterday's logged results for each permitted outfall
- Compare each value against its daily maximum and rolling average limit
- Flag any parameter at or over its limit, and any trending close to it
Done when Every permitted parameter is checked and any exceedance or near miss is flagged.
-
2
Microsoft Teams - alert the compliance lead
WebRun opens Microsoft Teams to alert the compliance lead. - Post a compliance alert to the operations Teams channel
- List each flagged parameter with its value, its limit, and the outfall
- Separate confirmed exceedances from parameters merely trending close
Done when The compliance lead has a Teams alert naming every flagged parameter and limit.
-
3
Gmail - draft a management heads-up
WebRun opens Gmail to draft a management heads-up. - When a true exceedance is confirmed, draft a plain heads-up email to management
- Summarize the parameter, the result, the limit, and the date
- Leave the email unsent as a draft for a human to review and send
Done when A management heads-up email is drafted and waiting for human review, never sent on its own.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it report an exceedance to the regulator on its own?
No. WebRun only posts an internal Teams alert and drafts a management email for review. Any notification to a regulator or state agency is left entirely to a human to approve and send.
How does it know each parameter's limit?
It reads the permit limits you have set up against each parameter in Operator10, checking daily maximums and rolling averages, so the comparison always matches the limits already in your system of record.
Can it warn me before a limit is actually breached?
Yes. Alongside confirmed exceedances, WebRun flags parameters trending close to their limit, so your compliance lead can act on a rising trend before it crosses the line.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.