Product · Environment & Compliance
It finds the exceedance. A person decides.
Winze holds the conditions your site is held to, measures every monitor against the limits you configure, and raises an exceedance the moment an average passes one. Whether that is a breach is for a named person to say. Software never notifies a regulator on its own.
Ask it
Questions it answers, in your words.
Is the dust monitor over its PM10 limit right now?
Check the night noise obligation against the last two days of readings.
Build the evidence pack for the overnight dust exceedance.
Examples from the product’s own tools. Each answer carries its figures, its window, its method and the readings behind it.
What it does for Environment & Compliance
Exceedances found, people decide.
01
Monitors against the limits you configure
An obligation is the sentence in your licence, word for word, beside the numbers you confirmed from it: the limit, the unit, how it is averaged and over how long, and when it applies. Every monitor is measured against it from the instrument’s own readings, never a cleaned or filled-in series.
- 01The conditionWord for word, as your licence states it
- 02The limitIts value and unit, confirmed by you
- 03The averagingA rolling 24-hour mean, a 15-minute mean
- 04When it appliesAnd how much of each window must hold good data
02
24-hour averages, and the share of valid readings
Each monitor is averaged the way its condition says. A reading that is missing or marked bad by the instrument is left out and counted. A window with too little good data is reported as not enough data: never as compliant, and never as zero.
- The figures
- The average and the limit it passed
- The window
- When, and over how long
- The method
- How the average was taken
- The valid share
- How many readings counted, and how many did not
03
An obligations register
Every condition for every site in one register, with the monitors that report against it and its exceedances in the owner’s queue. The same readings always give the same figures: plain arithmetic you can check, with no model in any figure or decision.
- Obligations
- Each site’s conditions, as written
- Monitors
- The streams that report against them
- Exceedances
- In the owner’s queue to assess
04
A named person decides, and records how the regulator was told
Whether an exceedance is a breach, a monitor fault, a time the condition did not apply or planned work is for a person to say, with a reason, and their name is recorded. When you tell the regulator, you record that you did: when, by what channel and under what reference.
- 01RaisedAn average past the limit, with its evidence
- 02AssessedA named person decides, with a reason
- 03NotifiedYou record when, how and under what reference
- 04ClosedThe record is yours; software told no one
What it reads
The signals and sources behind every answer.
Read-only by design: nothing writes to your control systems.
Environmental monitor readings
Dust, noise, water quality: whatever your monitors report, as the instrument recorded it.
Your obligations
The conditions, limits and averaging rules you configure.
Who may decide
Environmental Officers at each site, named on every decision.
One plant, every area
Next step: a pilot on one site.
See it on your own plant. Book a pilot and we’ll run it with you on one site: the unexplained loss on your plant, priced, with its evidence.
- 01
Connect one site
OPC-UA, read-only, one command on site
- 02
Run it for 90 days
Chat, shift reports and Scheduler tasks
- 03
Review the findings together
The unexplained loss, priced, with its evidence
