Use case · Manufacturing
Machine alerts on the device your operators already wear
A stopped line, a jammed feeder, a temperature alarm. Cuebly sends the fault straight to the safety device or app of the right operator, the same device that protects them when they work alone.
- Line 3 stopped
- Teltonika I/O
- TWIG
- Cuebly app
- Per shift
How it works
From a machine fault to the operator, in one flow
Step 1 · Fault
A machine stops
Line 3 jams. The control panel switches a fault contact, as it already does for the warning light.
Step 2 · Gateway
The I/O gateway notices
A Teltonika I/O gateway on that contact sends an event to Cuebly. Other systems, such as SCADA, can call the API or a webhook instead.
Step 3 · Scenario
The scenario picks the people
The scenario for this input knows which operators and which technician belong to line 3, and what the message should say.
Step 4 · Message
The message lands on their device
“Line 3 stopped, feeder jammed” appears on the operator’s TWIG and in the Cuebly app of the shift leader.
Step 5 · Log
On record
The operator clears the jam and the line runs again. The message and who received it are in the log.
Why it works
One device for safety and for the machines
Operators walk around
A warning light only helps when someone sees it. A message on the device they wear reaches them anywhere in the hall.
Too loud for a beep
In a noisy hall a horn gets missed. A vibrating device with the text of the fault does not.
Nothing extra to carry
The device that detects a fall or sends an SOS also shows the machine alert. No pager next to it.
Built on what is there
A fault contact exists on almost every machine. A small I/O gateway is enough to connect it.
Getting started
Connecting the first machine
Pick the contacts
Choose the machine faults that matter, such as a stop, a jam or a temperature alarm, and find their contacts.
An afternoon on site
Place the gateway
Wire a Teltonika I/O gateway to those contacts. It is added in Cuebly like any other device.
Minutes per gateway
Write the scenario
Link each input to the right people and the text of the message, per line or per shift.
Under an hour
Test and go
Trigger each contact once, check that the message arrives on the right devices, and hand it over.
Same day
Explore
Related
Teltonika gateways and safety devices in one place.
Scenarios, alarms and the log behind this use case.
Lone worker app or dedicated device?
How the app and devices like TWIG work together.
Questions
Frequently asked questions
The simplest way is a Teltonika I/O gateway on a potential-free contact or relay of the machine or its control panel. When the contact switches, the gateway sends an event to Cuebly. Systems with software of their own can also call Cuebly through the API or a webhook.
Devices with a display, such as TWIG devices, show the text. The Cuebly app shows it as a critical message. Devices without a display can still get a call or an SMS on a phone.
Yes. Operators keep one device for their own safety and for the machine messages. The man down and SOS alarms keep working as before.
You decide in the scenario: the operator of that line, everyone on the shift, a team or a technician. Every input of the gateway can have its own text and its own people.
Yes. Every message and who received it is kept in the log for that customer.
Demo
See a machine alert reach an operator
In the demo we trigger an input and show the message arriving on a TWIG and in the app.