Product · Superintendent

Last shift, in plain language, before the pre-start.

Winze reads every signal through the night and tells you what happened: the hours equipment ran without producing, why, and what it cost, with each check it made and the readings behind it.

Built for

Shift Superintendent
Mine Superintendent

Book a pilot

Mine Superintendent

Runs the pit and keeps the crusher fed, shift by shift · Winze chat

Illustrative

Why was the primary crusher idle on night shift?

2.4 h

running without producing · $41K lost throughput

2.4 h running without producing: starved of feed.

Motor drew power, belt scale read zero: 3 gaps, 01:00–04:30.
No crusher trip or fault; feed from the ROM pad stopped.
Lost throughput: $41K.

Put this in my start-of-shift report.

Added. Your 06:00 shift report now leads with feed gaps.

Running, not producing
Plain-language shift report
Evidence down to readings

Illustrative conversation. Figures are examples, not customer data.

What it does for Superintendent

Last shift, in plain words.

Running, but not producing

A crusher drawing power with nothing on the belt is running, not producing. Winze finds those hours shift by shift, prices each one and traces it to its cause: the loss that is spread across shifts and circuits, and that a month-end report shows without a cause.

How a lost hour becomes dollars

The start-of-shift report

Ask for a start-of-shift report once and Scheduler runs it at the time you choose, every day, and tells you when it finds something. Tell it in your own words what to lead with: feed gaps, a drifting pump, the stops nothing explains.

Scheduler: two active tasks, one of them “Run a start of shift report”, each running daily at 06:00 and set to tell its owner when it finds something — A start-of-shift report on a daily 06:00 schedule, in the demo tenant.

“What stopped the crusher last shift?”

Ask in your own words. You see each check as Winze makes it: which asset matched, which shift, the stops nothing explains, planned windows, work orders, and what it tried next when a first attempt found nothing.

What it checked, in order: which asset matched, which shift, stops nothing explains, planned maintenance windows, work orders, a walk through the events around a repair, and availability, utilisation, mean time between failures and mean time to repair, each with an evidence link — “Checked 7 things”: each step links to the evidence it read.

Evidence down to the readings

Every figure opens to three things: the figure, the method that produced it, and the raw readings behind that. The model never types a figure; every number is a tool result you can open and re-run.

A dashboard where each tile is marked Verified with the tool that answered it and an "open evidence" link underneath, with the lowest, highest and last figures and the window each one covers — Every tile marked Verified, with the tool that answered it and its evidence one click away.

What it reads

The signals and sources behind every answer.

Read-only by design: nothing writes to your control systems.

Motor power, belt scales and run state
From the OPC-UA server already on site, read-only.
Your shift roster and stop codes
Entered once, so a shift and a known stop read as what they are.
Work orders and planned windows
So a planned stop is never reported as a finding.

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