Cybélia IoT : your sensors, watched over
Completed
When a sensor goes quiet
28 Views •Alarms and notifications
23 Views •When something sticks: opening a ticket
23 Views •Readings and curves
22 Views •A sensor's record
22 Views •Dashboards
21 Views •Signing in
21 Views •Rules : when… then…
19 Views •Who it is for
20 Views •Battery life
19 Views •Why measure at all
18 Views •The estate : the list of sensors
18 Views •Settings, set once
17 Views •What Cybelia installs at your premises
17 Views •Who is watching while you work
17 Views •The vocabulary, six words
16 Views •Users and their permissions
16 Views •History and evidence
16 Views •The home screen, and finding your way
16 Views •The mobile app and looking in from anywhere
14 Views •Rules : when… then…
The brain of the tool
A rule is a sentence in two halves. When a reading does this, then that happens. That is all, and you write it with drop-down lists, not with code.
The "when"
You pick a sensor, one of its readings, and a condition: greater than, less than, equal to. You almost always add a duration: "for more than thirty minutes". That duration is the most important setting on the whole screen, and the most often forgotten.
Without it, a one-second spike, somebody opening the kiln door, raises an alarm. With thirty minutes, only a genuine drift raises one. You are not setting the sensitivity of the sensor: you are setting your own patience.
The "then"
Raise an alarm, with a severity. Send an email. Push a notification to phones. Often all three, because they are not read at the same moment.
The three rules at Les Ateliers du Vent d'Ouest
Kiln. When humidity goes above 14% for more than thirty minutes, then a medium alarm, email to Yanis and Camille.
Workshop. When the temperature falls below 8 °C for more than an hour, then a low alarm and an email to Yanis, the heating has failed, and the glue will not set tomorrow morning.
Extraction. When the extraction is stopped while a machine is drawing current, then a high alarm and an immediate push notification. That one is about safety, not quality.
A chatty rule is a useless rule. If you get eight messages a day, you stop reading them within a week, and on the day there is a real problem, nobody sees it. Start loose, tighten later.
Changing rules without fear
A rule can be switched off without being deleted: handy while work is being done on the kiln, so your own maintenance doesn't wake you up. Changing a rule alters neither the history already recorded nor the alarms already open.
In closing
A well-written rule warns the right person at the right time; a badly tuned one warns everybody all the time, and then nobody listens. Start broad, then narrow down to what proved useful.
Commenting is not enabled on this course.