CMMS Integration
ThingConnect, connecting to MachDatum CMMS
MachDatum, ThingConnect's parent company, runs a full CMMS product: asset records, work orders, preventive maintenance scheduling, all of it. The two connect directly, so machine downtime and condition data flow from ThingConnect into MachDatum CMMS as work orders and maintenance sees a stop the moment it's classified rather than hearing about it secondhand.
The problem
Why this matters
- Maintenance finds out a machine went down when someone walks over and tells them, so the clock on a repair starts well after the stop did.
- Downtime hours on a work order get estimated at the end of the week, while ThingConnect measured them from the control as they happened. Two numbers for one stop, and neither side trusts the other's.
- The same machine exists twice, once as an asset record in maintenance and once as a monitored machine on the floor, and somebody reconciles them by hand.
A real, live product
What is MachDatum CMMS?
MachDatum CMMS is a separate maintenance management product built by ThingConnect’s parent company. You can use it on its own, or connected to ThingConnect as described below.
Asset management
Every machine has one record holding location, criticality, documents, and full history in one place, with custom attribute schemas per equipment class.
Work order management
A full audit trail on every job: asset, assignee, priority, root cause, failure mode, and downtime hours captured live as the work happens.
Preventive maintenance scheduling
Set the cadence once. When the date arrives, MachDatum creates and assigns the work order automatically, with no manual trigger.
Mobile app
iOS and Android apps let technicians open, update, and close jobs from the floor, with QR-code scanning for instant asset lookup.
Opens machdatum.com in a new tab, a separate site from thingconnect.io.
How it works
How the integration works
ThingConnect and MachDatum CMMS share data directly, so a machine event on one side shows up on the other without anyone re-entering it by hand.
Downtime as work orders
A machine stop detected and classified in ThingConnect flows straight into MachDatum CMMS as a work order, instead of maintenance hearing about it secondhand.
Machine condition into triggers
Condition and alarm signals ThingConnect reads from the controller feed MachDatum's condition-based maintenance triggers, not just a separate report.
One asset, not two records
A machine's ThingConnect identity and its MachDatum maintenance record resolve to the same asset, so nobody is reconciling two systems by hand.
The handoff
Maintenance knows in the same minute the stop is named
One stop on VMC-01, followed end to end. Nobody walks over to report it, nobody retypes it, and both systems finish holding the same hours.
The clock stops at the handoff on purpose. How long the repair itself takes is your shop’s number, not something an integration can promise. What changes is that the job started at 13:40 instead of whenever someone got round to mentioning it.
It’s the same stop predictive maintenance catches as cutting-load drift, and the same one downtime tracking ranks in the loss Pareto.
- 13:39ThingConnect
VMC-01 stops mid-cycle
Detected from the control the moment it happens, not written on a board and typed up at the end of the shift. It sits as Unclassified until someone names it.
- 13:40ThingConnect
The operator taps Tool break
Category, then reason, from the tree your admin configured. A few taps on the screen already in front of them.
- 13:40MachDatum CMMS
The work order is already open
Same minute. Asset VMC-01, failure mode Tool break, downtime hours counting from the stop itself. A planner still sets priority and assignee, but nobody retypes what the machine already knew.
- MachDatum CMMS
A technician closes it on the floor
However long the job takes, and that part is your shop's rather than ours. Closed from the mobile app against the versioned checklist for that work order type, so an auditor sees the exact procedure followed.
- ThingConnect
Both systems hold the same hours
Measured from the control, stop to restart. The loss Pareto and the work order agree, because neither of them was estimated at the end of the week.
Triggers
What raises what
Not everything that happens on a machine deserves a work order. These are the events that do, and the kind of record each one opens.
| In ThingConnect | In MachDatum CMMS |
|---|---|
| An unplanned stop, reason-coded by the operator | A corrective work order against that machine, with the failure mode already set from the reason |
| The same alarm returning on one axis | A work request to inspect it, before it becomes a breakdown |
| A tool reaching the end of its life | A scheduled task against that machine, rather than a surprise mid-cut |
| Cutting load drifting out of its normal range | A condition-based trigger, MachDatum's own, fed by the machine instead of a calendar |
Field by field
What the work order already knows
A MachDatum work order captures six things. Three of them arrive from the machine; the rest are judgement calls only your team can make.
| Work-order field | Where it comes from | Filled by |
|---|---|---|
| Asset | The machine ThingConnect detected the stop on | The machine |
| Downtime hours | Measured from the control, stop to restart | The machine |
| Failure mode | The reason the operator tapped | The machine |
| Root cause | What the technician finds once they are at the machine | Your team |
| Priority | A planning decision, not a measurement | Your team |
| Assignee | Who is on shift and free | Your team |
Questions
Before you book a demo
No. They're separate products from the same parent company. ThingConnect works fully on its own; MachDatum CMMS only matters to you if your shop also wants a maintenance and work-order system alongside it.
MachDatum CMMS is ThingConnect's parent company's maintenance management product: asset records, work order management with a full audit trail, automatic preventive maintenance scheduling, and an iOS/Android mobile app for technicians on the floor. It also has a configurable location hierarchy, versioned checklists, a REST API and its own ERP sync. See machdatum.com for the full product.
Yes. It's a full product independent of ThingConnect; visit machdatum.com to see it directly.
Machine downtime events and condition data that ThingConnect collects flow into MachDatum CMMS as work orders, and both systems share one asset record instead of two. It doesn't make a repair faster. What it removes is the gap between a machine stopping and maintenance holding a work order that already knows the asset, the reason, and the measured downtime. See "The handoff" above for one stop followed end to end.
Asset, downtime hours, and failure mode come from the machine and the operator's reason code. Root cause, priority, and assignee stay with your team, because they're judgement calls rather than measurements. See "What the work order already knows" above for the field-by-field breakdown.
No. That would bury maintenance in tickets. Unplanned stops that an operator reason-codes raise a corrective work order; a repeating alarm raises a request to inspect; tool life and condition signals raise scheduled or condition-based tasks. See "What raises what" above.
Talk to us
See the CMMS connection fit into your maintenance workflow
A 30-minute call to walk through your maintenance workflow today and how ThingConnect and MachDatum CMMS work together on it.