CMMS, EAM, ERP
Connect your machines to your maintenance & asset software
Turn raw machine signals into the work orders, alarms and asset history your CMMS and EAM need.
- EAM software
- Maintenance software
- Maintenance management software
- Predictive maintenance software
Runtime and alarms
Your workflows
The open bridge to your CMMS or EAM
Melqart does not sell a competing maintenance dashboard. We build the bridge from your machines and gateways into the CMMS, EAM or ERP your teams already use.
Machine events and runtime hours
Condition and alarm data
Work-order-ready payloads
- 01Machines and gatewaysRuntime hours, machine events, condition and alarm data.
- 02Integration bridgeCustomer-owned logic turns events into work-order-ready payloads.
- 03Your CMMS, EAM or ERPThe maintenance system your teams already use, with no duplicate dashboard.
CMMS connector: how machine data and alarms reach your CMMS
A CMMS connector is the layer that receives data from your machines and gateways and passes it to your CMMS in the format it expects. We use the mechanism your software already accepts rather than forcing an interface it does not support.
CMMS REST API: create work orders or service requests and update meter readings from the gateway or the integration bridge.
MQTT: publish machine events and alarms, then forward them to the CMMS through the integration logic.
Webhooks: notify your CMMS or another system as soon as an alarm or threshold is crossed.
File exchange (CSV or JSON) when the CMMS does not expose an API.
Asset mapping: each machine or gateway is linked to the matching asset record in your CMMS.
Synchronizing data with your CMMS: work orders, counters, asset master data
CMMS synchronization is more than a one-off data push. It keeps the CMMS and the machines consistent over time, including when the network drops.
Work orders: created from alarms and thresholds using rules you define.
Counters and runtime hours: reported regularly so preventive maintenance can trigger on actual usage instead of the calendar.
Asset master data: machine and gateway identifiers stay aligned with the asset records in the CMMS.
Offline buffering: during a network outage the gateway keeps events and forwards them when the connection returns.
Predictive, not just reactive
Condition data, runtime hours, alarm events and operating context can trigger better planning, faster intervention and a clearer asset history.
Reliable monitoring
Operating context
Better maintenance priority
You keep ownership of the data
Your integration logic, data contracts and edge configuration remain documented and transferable.
No duplicate dashboard trap
Customer-owned integration code
Clear handover path
Related capabilities
Build the rest of the system
IoT consulting
Validate the business case and architecture before you build.
ExploreCondition monitoring
Related capability for the next technical step.
ExploreIoT development
Related capability for the next technical step.
ExploreRouters & gateways
Related capability for the next technical step.
Explore
Solution datasheet
Maintenance and asset software integration
Run hours, alarms and fault codes delivered into the CMMS or EAM you already use, as meter readings, work-order triggers and asset history.
MS-DS-MAS-2026-47 · PDF · 6 pages · English
FAQ
01What is EAM software?
EAM software manages the lifecycle, work orders and maintenance history of physical assets. Industrial IoT can improve it by feeding reliable runtime, alarms and condition data.
02Do you replace our CMMS?
No. Melqart integrates machine and gateway data into the system you already use or plan to adopt.
03Can this support predictive maintenance?
Yes, when the data quality and operating context are strong enough. We start with condition monitoring and maintenance workflows, then add predictive models where justified.
04Can I connect my machines to my existing CMMS?
Yes. Melqart integrates machine and gateway data into the CMMS you already use, without replacing it. We build on what your software offers: REST API, MQTT, webhooks or file exchange.
05How does a CMMS connector work for machine data?
The connector receives runtime hours, events and alarms from machines and gateways, converts them to the format your CMMS expects, and forwards them by API, MQTT, webhook or file. The integration logic is yours and stays documented.
06Which machine data can be synchronized with a CMMS?
Mainly runtime hours and counters, alarms and condition data, plus the mapping to asset records. This is what lets you create work orders and keep the maintenance history current.
07What is the difference between a CMMS and predictive maintenance?
A CMMS manages assets, work orders and maintenance history. Predictive maintenance uses condition data to anticipate an intervention. Industrial IoT links the two: it feeds the CMMS reliable data, so rules or predictive models can then trigger work orders.
Scope this solution for your estate
We connect the technical architecture to a concrete implementation scope.