Equipment
Join machine readings, work orders and repairs to see which faults repeat and where output slows.
Example tags
What you can learn
- Same fault returned within 7 days of repair
- Ran over the service-hour limit before a job
- Stopped 3 times during one shift
- Output dropped after a temperature alert
- Repair completed, then finished the next run
- Work order open after 2 repeat fault events
Built from recorded events, using the rules we agree with you.
Say what you want to learn. See how it is defined.
DataGlue shows the formula: which events count, in what order, and over what time. Our team builds and checks it with you.
This is an example rule. Your event names, time limits and links are agreed in the build.
Example formulaEvents → tag
Find a machine whose fault came back after repair.
- IoT sensors: fault code recorded
- Maintenance: repair completed
- IoT sensors: same fault code recorded again
In this order, within 7 days of repair, for the same machine.
Tag created
Fault returned after repair
Start with a question that matters.
Find faults that return after repair
Join a machine fault, completed repair and the next matching fault.
See where output drops
Connect machine readings, active shifts and output records for the same run.
Spot service needs before the next run
Join running hours, your service limit and the next planned production job.
Each system adds a piece of the story.
IoT sensors
Machine readings, fault codes and running hours.
Maintenance records
Work orders, inspections and repairs.
Production records
Output, loads and planned runs.
Shift rosters
Shifts and equipment assignments.
We agree how each source connects through your warehouse, API or the connections in your build. Person records need a shared id to join. Vehicle, shipment, machine and site tags stay on those records.
Send the tag where your team works.
Choose the destination. We build the route so the result can reach the tools your team already uses.
- Maintenance tools
- Staff alerts
- BI dashboards
- Warehouse
These are example destinations. The formula stays the same wherever the tag is sent.
Describe the outcome. We’ll join the data.
Bring one machine fault question. We’ll join the readings and repair records.
A dedicated team builds the connections, rules and destinations with you.