Automated Operator10 Daily Log Compilation
Every morning, WebRun opens Operator10, reads yesterday's process and shift readings from your DataViews, compiles them into a clean daily operator log in Google Sheets, and posts a shift summary to Microsoft Teams so operators start the day with one clear picture of the plant.
How do I compile a daily operator log from Operator10 automatically?
WebRun opens Operator10 every morning, reads yesterday's process and shift readings from your DataViews, and compiles them into a dated daily operator log in Google Sheets. It flags any missing readings, then posts a short shift summary to Microsoft Teams, so operators start each day with one clear, complete picture of the plant.
- Operators open one compiled daily log instead of chasing scattered readings
- Missing readings surface every morning before reports come due
- The Operator10 system of record is never edited, only read
Built for wastewater operators · water treatment plants · utility operations staff · chief plant operators
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 - read yesterday's DataView readings
allmaxsoftware.com
WebRun opens Operator10 to read yesterday's DataView readings. - Open Operator10 and load the daily process and shift DataViews
- Read yesterday's logged readings across each process area and shift
- Capture the parameter, value, units, and logging operator for each entry
- Note any blank or missing readings that an operator still needs to enter
Done when Yesterday's full set of shift readings is captured with any gaps flagged.
-
2
Google Sheets - compile the daily log
google.com
WebRun opens Google Sheets to compile the daily log. - Open the Daily Operator Log workbook
- Add a dated tab or row block for yesterday's shifts
- Write each reading in order by process area with its value, units, and operator
- List any missing readings in a Gaps section at the top
Done when The daily log workbook holds yesterday's compiled readings with a gaps list.
-
3
Microsoft Teams - post the shift summary
microsoft.com
WebRun opens Microsoft Teams to post the shift summary. - Post a short shift summary to the operations Teams channel
- Lead with any missing readings so they get entered early
- Include a link to the full compiled log in Google Sheets
Done when Operators have a shift summary in Teams with a link to the full log.
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
Does it change any readings in Operator10?
No. WebRun only reads your Operator10 DataViews and compiles the values elsewhere. It never edits, overwrites, or deletes logged readings in Operator10, so your system of record stays untouched.
What happens when an operator forgot to log a reading?
Missing readings are surfaced first, both in the Google Sheet gaps list and at the top of the Teams summary, so the on-shift operator can enter them in Operator10 before reports are due.
Is the Teams summary posted on its own?
Yes, the Teams summary is an internal digest to your own operations channel, so WebRun posts it automatically each morning. Nothing leaves the plant and no external or regulatory message is sent.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.