We build the integrations, so condition data lands where work gets done
An alert nobody acts on is just noise. We connect condition monitoring to your historian, your CMMS or EAM, your OEE data and your APM, so alerts arrive as work orders and avoided losses show up in minutes and dollars.
5 systems
Historians, CMMS/EAM, MES/OEE, APM, ERP
2 weeks
Of shadow mode before any automation is switched on
Read-only
Access to operational technology, no inbound ports
Landscape
Where condition data meets your systems
A data platform in the cloud sits in the middle: connectors, an industrial data lake, ISO and machine learning analytics, alerts and dashboards.
Historians
AVEVA PI System (PI Server, PI AF, PI Web API), Rockwell FactoryTalk Historian, Ignition Tag Historian, Canary, Honeywell Uniformance PHD.
CMMS / EAM
SAP S/4HANA Plant Maintenance, IBM Maximo Application Suite, Octave Attune EAM (formerly HxGN EAM), Oracle EAM, UpKeep, Fiix, MaintainX, Limble, eMaint.
MES / OEE / SCADA
Rockwell FactoryTalk Metrics, Siemens Opcenter, AVEVA MES, Ignition with Sepasoft OEE, MachineMetrics, Vorne XL, Evocon, PLCs over OPC UA.
APM
Octave Attune APM, SAP Asset Performance Management, IBM Maximo Health and Predict, GE Vernova APM, AVEVA APM, Bentley AssetWise, Honeywell Forge.
ERP and finance
SAP S/4HANA, Oracle, Workday: the cost of downtime, spares and labor rolls up to the P&L.
Protocols and APIs
OPC UA, MQTT and Sparkplug B, Modbus TCP, EtherNet/IP, MTConnect, PI Web API and OMF, REST, OData, GraphQL, SQL and ODBC, webhooks, ISA-95 asset models.
Historian
AVEVA PI System: condition data next to the process data your engineers trust
PI context such as load, speed and temperature setpoints explains vibration changes and makes alerts smarter. Monitoring data is written back as PI tags, so asset health shows up in PI Vision next to flow, pressure and speed.
- 1
PI System
PI Server, PI AF and Event Frames: tags, the asset hierarchy, batches, runs and downtime.
- 2
PI Web API
Subscribe over secure WebSockets or poll, with a read-only service account.
- 3
Edge connector
Runs on a site virtual machine, adds asset hierarchy and batch context, filters to good-quality data during valid runs, and backfills after outages.
- 4
Cloud data platform
Industrial data lake in your own cloud account. PI remains the system of record on site.
- 5
Analytics and dashboards
ISO and machine learning models, with dashboards your reliability team can query.
No historian yet? An edge gateway can read OPC UA directly, with Modbus TCP and EtherNet/IP through partner components.
CMMS / EAM closed loop
Alerts that arrive as work orders
Every work order carries the trend snapshot and the failure mode, so the technician arrives knowing what to look for. Closing the order is the feedback that improves the next alert.
- 1
Abnormality detected
Monitoring flags a change on an asset position.
- 2
Severity and criticality checked
Rules decide whether this asset and severity need a work order.
- 3
CMMS API called
The work order request goes to your CMMS through its own API.
- 4
Work order created
With the asset, the failure code and the sensor evidence attached.
- 5
Technician inspects, repairs, closes
The repair and the finding are recorded in the CMMS.
- 6
Outcome tunes the next alert
The closure flows back so thresholds and models improve.
How each CMMS connects
| System | Integration method | What gets created |
|---|---|---|
| SAP S/4HANA Plant Maintenance / SAP APM | OData APIs; SAP Integration Suite; SAP APM rules on streaming IoT data | Maintenance notification, then maintenance order; approvals and technician alerts in SAP |
| IBM Maximo Application Suite | Maximo REST / OSLC APIs; Maximo Monitor and Health consume condition indicators | Work order with asset, location and failure class; health score update |
| Octave Attune EAM (formerly HxGN EAM) | REST web services and partner connectors | Work order and alert to the repair crew, MRO parts reserved |
| Oracle EAM / Fusion Cloud Maintenance | REST APIs | Work request, then work order |
| UpKeep, Fiix, MaintainX, Limble, eMaint | REST APIs and webhooks | Work order with photos, readings and checklist; closure webhook back to the platform |
OEE
Tie asset health to the losses it causes
OEE is Availability × Performance × Quality. We join each downtime event and reason code to the sensor trend of the asset that caused it, so avoided losses are counted in minutes and dollars, not alerts.
Availability
Run time divided by planned time. Unplanned stops are the loss condition monitoring attacks directly.
Performance
Actual rate divided by ideal rate. Slow cycles and minor stops are often a degrading drive or bearing before it fails.
Quality
Good count divided by total count. Scrap after restarts and from misaligned equipment.
Where OEE data lives, and how we connect
| Where OEE data lives | How we connect |
|---|---|
| MES: Rockwell FactoryTalk Metrics, Siemens Opcenter, AVEVA MES | SQL repositories and vendor APIs, with batch and order context |
| SCADA: Ignition with the Sepasoft OEE Downtime module | Ignition SQL tag history and OEE tables; MQTT Sparkplug B |
| Machine monitoring: MachineMetrics, Vorne XL, Evocon | Vendor REST, GraphQL or MQTT interfaces and SQL exports |
| No OEE system yet: PLC signals | Asset models compute availability, performance and quality from OPC UA tags, and keep running offline at the edge |
What you get: assets ranked by OEE impact rather than alert count, an avoided-downtime ledger per line and month, downtime reason codes enriched with the sensor signature that preceded them, and OEE, alerts and work orders on one timeline.
APM
Two ways to get asset performance management
An APM platform decides which assets need attention and why. Your EAM or CMMS plans and does the work. Work history and outcomes feed the next prediction.
Option A: you already run an APM
- Monitoring becomes a condition data source: vibration, temperature, ISO state and anomaly score per asset position
- Indicators and alerts are pushed through the APM's APIs, with the asset ID mapped to its hierarchy
- Your APM keeps strategy, risk scoring and the hand-off to EAM; nothing in your governance changes
Option B: no APM yet, build one with us
- Asset registry and criticality in ISA-95 asset models, synced from your CMMS
- Health scores that blend condition data, historian tags and OEE losses, with a failure-mode library per asset class
- Work-order automation into your CMMS, with approvals and escalation
- Runs in your own cloud account, so the data stays yours; start with one line and add assets
Delivery
How we deliver integrations without disrupting operations
- 1
Discover
Inventory systems, owners, APIs and network zones. Pick the three integrations that move the pilot KPI.
- 2
Model
One ISA-95 asset hierarchy shared by the CMMS, historian and sensors, with tag and ID mapping agreed up front.
- 3
Connect
Connectors for PI Web API, OPC UA, SAP OData, Maximo REST and webhooks, an edge runtime on site and private endpoints in the cloud.
- 4
Secure
Read-only OT access, no inbound ports, least-privilege access, encryption in transit and at rest, and an audit trail on every write to the CMMS.
- 5
Prove
Two weeks of shadow mode: alerts and work orders are reviewed by your team before automation is switched on.
Typical pilot scope: CMMS work-order integration plus one data source (PI historian or OEE) in the first 90 days. An APM feed or custom APM layer comes with the scaled deployment.
Map your integrations in the assessment
We inventory the systems you run during the free assessment and recommend the integrations that move your pilot KPI.