Maintenance data: from threshold alarm to actionable work order
Connect running hours and process measurements to CMMS or SAP PM while controlling repeated alarms and ownership.
Read the guideSolutions
Maintenance integration
Turn an alarm into a traceable action.
Maintenance teams and asset managers
Connect operating hours and condition events to the maintenance system. Track alerts with a work-order identifier and prevent persistent conditions from repeatedly creating jobs.
SourceRuntime / sensor
OPC RouterConnect · Transform · TransferDestinationCMMS / SAP PM
Typical data points
- Run-hour counter
- Vibration, temperature or pressure threshold
- Alarm state and return to normal
- Equipment code
- Open work-order reference
How the flow works
- Connect
The OPC UA Client reads run-hour, measurement and alarm tags.
- Transform
Thresholds and hysteresis are applied; if an open work order exists for the same equipment a new one is not opened.
- Transfer
A work order is opened or updated through the SAP or REST interface; the returned reference is stored with the source event.
Decisions before connecting
- 01Equipment-code mapping
- 02Threshold and hysteresis
- 03Alarm ownership
- 04Returned work-order reference
Pilot acceptance criterion
Check work-order counts for threshold crossing, recovery and replay on a single asset.
Connectors used in this scenario
Connector availability, version compatibility and licence scope are verified for each project.
Implementation guide
Frequently asked questions
Should every alarm open a work order?
No. Without threshold, hysteresis and repeat-suppression rules a persistent alarm can generate many work orders. A typical approach is not to open a new one while an open work order exists for the equipment, and to update its state on return to normal.
Which maintenance systems does it work with?
Maintenance modules such as SAP PM can be connected through the SAP plug-in and maintenance software with a REST interface through the REST/SOAP plug-in. Scope, version and interface are confirmed in the project.
Your next step
Let’s talk about the systems you need to connect.
Share your source, destination and intended outcome. We’ll help define the project scope.