From alert to approved fix: monitoring your team will trust
Most monitoring fails quietly: too many alarms, too few reasons, and nobody sure whether the fix worked. Here is how to set up alerts, likely causes and approve-to-act controls, so the routine watching runs itself and your engineers make the calls.
In short
- Three alerts cover most needs: gone quiet, too high and too low.
- Trends find problems before limits do, and a likely cause with its reasons tells people where to look first.
- A fix can be a button a person presses, confirmed by the readings, while your control system stays in charge.
- Every answer your team gives is kept, so the rules can be tested and improved.
Start with three alerts
Gone quiet. A sensor that stops reporting is often the first sign of trouble, and the easiest to miss. Say how long silence is acceptable for each measurement: 15 minutes for a vibration sensor that usually reports every five.
Too high and too low. Set limits where someone needs to act, not where a value is merely unusual. 7.1 mm/s of vibration on a drive is a limit; a reading slightly above yesterday’s is not.
In Evalu8 Pro, alerts open by themselves, clear by themselves when the reading recovers, and can be acknowledged. They show on the record, the dashboard and the Monitoring page, and in the API. Devices report when they report: charts and totals go by how often each sensor actually sends readings, not how often it was meant to, so they stay honest when a gateway falls behind.
Limits catch failures. Trends catch them early.
A drive’s vibration rarely jumps from fine to failed. It climbs a few tenths of a millimetre a second each day, well inside its limit, for days, and the alarm only sounds at the end.
Drive motor CV3-M2Vibration, last 7 days
Vibration at the drive-end bearing, mm/s
Likely causeBearing wear
- Vibration rising 1.2 mm/s a day
- Temperature rising 3 °C a day
- 2,140 running hours since the last service
ConfirmCorrect it
A diagnosis rule watches for the pattern instead. In plain English: when a drive’s vibration has been climbing for a day, weigh its temperature, its current draw and the hours since its last service, and suggest a cause. Each possible cause has its own evidence. Rising temperature and long hours since a service point to bearing wear. A recent service and a steady temperature point to misalignment or looseness. A jump in current draw points to the drive working too hard.
The suggestion arrives with its reasons and advice on what to check first. An engineer confirms it, corrects it or dismisses it, and the answer is kept with the readings behind it.
Write down what a mistake costs
Every alert and diagnosis trades catching problems against crying wolf. Most teams leave that trade-off unspoken, and it gets made differently on every shift.
Write it down instead, as part of what you are aiming for: “A missed fault costs us a morning; a false alarm costs an engineer an hour.” Evalu8 Pro’s assistant reads your aims whenever it works for you and weighs its answers against them, and one button on Monitoring has it review how everything is doing against them.
Make the fix a button, not a phone call
When a fix is a change the equipment can take, such as reducing a line’s speed, it can be a control on the record: described once, pressed by someone allowed to, and sent to the controller as a request it can refuse.
Line 2Line controller
- Asked for: line speed 80%[email protected] via Ask · 14:02 · after “ok, do it”
- Sent to the line controller14:02 · the controller replied “accepted”
- Confirmed by the readings14:05 · speed 80%, as asked
A press only counts as confirmed when the readings show the change. Every press is logged with who pressed it, what was sent and what came back. Nothing is retried by itself, and a double press is refused. A diagnosis can offer the control that fixes its cause, so the reason and the remedy sit side by side, and Ask can propose the same control in answer to a question, running it only when told to go ahead.
This is deliberately not closed-loop control. Your PLCs and SCADA keep real-time control, interlocks and safety limits, and the plant runs on if Evalu8 Pro is offline. It reads, advises and sends only what a person approves.
Check the fix worked, without remembering to
The usual gap in maintenance is not the fix but the follow-up. A watch is a check kept on a record’s readings until a deadline: is vibration back below 3 mm/s within 48 hours? It is met as soon as the readings pass, and missed if time runs out. A missed watch stays on Monitoring until someone acknowledges it.
- Drive motor CV3-M2Vibration below 3 mm/s within 48 hoursWatching
- Drive motor CV2-M1Temperature down 5 °C within 24 hoursMet
- Sorter induct SI-4Current below 12 A within 8 hoursMissed
Anyone can set a watch from a record’s page, Ask sets one when you ask it to check on something later, and a fix pressed from a diagnosis can set its own. Watches only read.
Let the answers sharpen the rules
Every confirmed or corrected diagnosis is kept with the readings behind it. After a few months, that is the best record you have of how your equipment actually fails.
Evalu8 Pro can study that history against your aims, weekly if you choose or whenever you ask, and propose at most three changes to its rules, alert limits and numbers. Each one is tested against the answers your team has already given, and shown with how many of them it agrees with before and after, and the cases it would have called differently. A person applies each one, any of them can be undone, and dismissed ones are not proposed again.
The answers are yours to use elsewhere too: every answered diagnosis is available through the API with the measurements behind it, ready to train your own models on.
A checklist for your first line
- Describe the assets and sensors on one line, with how long each measurement may go quiet and where its limits are.
- Connect the readings and the maintenance history.
- Agree one diagnosis rule with your engineers, for the failure that costs you most.
- Write down your aims, and what a missed fault and a false alarm each cost.
- Answer every suggestion for a month.
- Add a control only where pressing a button beats walking to the panel.
- Study the answers, then widen to the next line.