Equipment failure
event documentation
When a machine trips, alarms or fails, a recording starts on a trigger or at the press of a button. The event, its time and the equipment condition are kept together for the root-cause review.
THE PROBLEM
By the time the engineer arrives, the evidence is gone
A compressor trips, a conveyor jams, a DG set fails to pick up load after a power cut. The operator resets it to get production running, and the conditions that caused the failure disappear. The root-cause meeting the next day relies on memory and a log line.
Warranty claims to the equipment maker and insurance claims for breakdowns ask the same question: what exactly happened. Sound and vision at the moment of failure, such as a bearing noise, smoke, a leak or an alarm on the HMI, often say more than any data point.
Recording continuously to catch rare failures creates mountains of footage and privacy concerns. Recording on a trigger, or when the operator decides to, captures the moment without the rest.
HOW WE SET IT UP
Recording that starts when something goes wrong
Triggers and storage are designed for each project, around your equipment and your alarm signals.
Choose the trigger
Recording can start from an equipment alarm, a fault contact, a Modbus status from the controller, or an operator button. We design the trigger to the signals your equipment already gives.
Capture the event
Our connected audio/video event logger records video and audio around the event and attaches time, location and the asset reference. Fixed or handheld placement depends on the equipment.
Tag and link to data
Vision AI tags the event in the recording. Where the equipment is also monitored through our gateways or meters, the clip sits beside the alarm and the readings in RIOD Live.
Hand it to the people who decide
Maintenance, the equipment maker and the insurer can review the same tagged record. Exports to PDF and Excel carry an audit trail.
AT A GLANCE
Failure event documentation in brief
- What is captured
- Video and audio around a failure or alarm event, with time and asset reference
- Hardware
- Our connected audio/video event logger, fixed at the equipment or handheld
- Triggers
- Equipment alarm, fault contact, controller status over Modbus, or operator button
- Power
- 12 V adapter or 2,000 to 5,000 mAh battery, chosen to the placement
- Where data goes
- Our Vision AI portal, or your own server, over MQTT and TLS 1.2
- Integration
- Sits alongside our Modbus, energy and machine monitoring data
- Engineering note
- Trigger logic, recording window and storage are custom design items, set during the project
FAQ
Questions buyers ask us
Can a camera start recording automatically when a machine alarms?
Yes. The recorder can start from an equipment alarm, a fault contact or a controller status read over Modbus. The trigger logic and recording window are designed around your equipment during the project.
Why record failures instead of recording continuously?
Continuous recording produces large volumes of footage that nobody reviews and raises privacy concerns. Triggered or operator-started recording captures the failure itself, which is what root-cause analysis and claims need.
How does failure video help with warranty and insurance claims?
The equipment maker and the insurer both ask what happened at the moment of failure. A tagged recording with time and asset reference, kept with an audit trail, gives them direct evidence instead of a description.
Can failure recordings be linked to machine monitoring data?
Yes. If the equipment is monitored through our Modbus gateways or energy meters, the recording sits beside the alarm and the readings in RIOD Live, so the review sees both together.
Losing the evidence every time a machine fails?
Tell us the equipment and the alarms it gives today. We will propose the trigger, the recorder placement and how the events are stored.