Every steel plant control room runs on SCADA — Siemens WinCC watching the hot strip mill, GE iFIX tracking the caster, AVEVA Wonderware logging blast furnace pressure. These systems know the exact moment a bearing overheats or a hydraulic line drifts out of range. The problem is that this knowledge stays locked inside the control room. Maintenance teams find out about the same failure hours later, from a phone call or a walk-past, long after the SCADA screen already flagged it in red. Closing that gap means connecting SCADA tag data directly to the work order system maintenance actually uses, which is exactly what OxMaint's CMMS is built to do for WinCC, iFIX, and Wonderware environments.
Why SCADA Data and Maintenance Work Orders Live in Two Different Worlds
A SCADA screen and a maintenance work order describe the same failure in two different languages. WinCC, iFIX, and Wonderware are built to visualise process state for operators — pressures, temperatures, vibration, flow — in real time, on screens designed for control decisions, not repair decisions. A CMMS is built to schedule, dispatch, and document repair work. Historically, the only bridge between the two has been a person: an operator who notices an alarm, picks up a radio, and describes it to a supervisor who then writes a paper or Excel work order. Every one of those handoffs adds delay, and on steel assets with narrow failure windows, delay is expensive.
A hot strip mill or continuous caster can generate hundreds of SCADA alarms a shift. Operators acknowledge them to clear the screen, but acknowledging is not the same as raising a repair task — most alarms never become a tracked work order.
WinCC and Wonderware historians hold years of trend data on a bearing or hydraulic circuit, but a technician dispatched verbally arrives with none of it — no prior alarm frequency, no last repair date, no known failure pattern.
The typical path from an alarm firing on a Level 2 screen to a technician being dispatched runs four to eight hours in a manual environment — long enough for a warning condition to become an unplanned shutdown.
Process data sits in the historian, work orders sit in a spreadsheet or a separate maintenance system, and reconstructing a full failure timeline for a reliability review means merging files by hand.
Four Ways to Move Data From SCADA Into a CMMS
There is no single universal connector between control systems and maintenance software — the right integration method depends on what your WinCC, iFIX, or Wonderware environment already exposes. Most steel plants end up using a combination of the four approaches below rather than just one.
| Protocol | Best Fit | Typical Source | Steel Plant Use |
|---|---|---|---|
| OPC-UA | New integration projects, cross-vendor plants | WinCC Unified OPC UA server, iFIX OPC gateway, AVEVA System Platform | Real-time tag values plus structured alarm objects with timestamp and severity |
| REST API | Cloud CMMS platforms, modern architectures | Level 2 MES layers, historian web services | JSON-based exchange between plant systems and cloud dashboards |
| MQTT | High-volume sensor and IoT data | Edge gateways on rolling mills, conveyors, drives | Lightweight publish-subscribe for condition monitoring sensors |
| Historian Direct | Long-range trend and pattern analysis | AVEVA Historian, GE Proficy Historian, OSIsoft PI | Attaches years of trend context to a single alarm-triggered work order |
Older iFIX installations running OPC-DA rather than OPC-UA are not left out — a protocol wrapper sits between the classic OPC-DA server and the CMMS, translating the connection without any change to the existing SCADA configuration. The integration always runs as a read-only client, so PLC logic, HMI graphics, and control-loop configuration are never touched.
The Four-Layer Architecture Behind a Reliable SCADA-CMMS Connection
Integration is never a single wire between two systems. A dependable connection between WinCC, iFIX, or Wonderware and a CMMS moves data through distinct layers, and skipping one of them is usually why an integration project stalls or floods technicians with noise.
Siemens S7, Allen-Bradley, and ABB controllers expose live tag data through native OPC-UA servers, typically on port 4840. This layer is never modified by the integration.
WinCC, iFIX, and AVEVA System Platform act as OPC-UA servers or expose SQL and REST interfaces, publishing alarm events and threshold tags at a configurable polling interval.
AVEVA Historian, GE Proficy Historian, and OSIsoft PI store years of compressed time-series data, giving every alarm-triggered work order full trend context at the moment of failure.
OxMaint applies alarm-persistence filtering, prioritises the event, and dispatches a structured work order to a technician's mobile device — with asset history and procedure attached, in under 60 seconds.
WinCC, iFIX, and Wonderware — Feature Support Compared
Each SCADA platform exposes its data slightly differently, which changes how quickly an integration can be deployed and how much historical context it can carry.
| Capability | Siemens WinCC | GE iFIX | AVEVA Wonderware |
|---|---|---|---|
| Native OPC-UA server | Yes, on WinCC Unified | Via OPC gateway module | Yes, via System Platform |
| MQTT support | Native on Unified PC | Requires add-on driver | Supported via edge gateway |
| Historian for trend context | SIMATIC / third party | Proficy Historian | AVEVA Historian |
| Alarm and event extraction | OPC A&C standard | Best via Historian A&E collector | Native alarm/event store |
| Read-only integration path | Supported | Supported | Supported |
Your SCADA Already Has the Answer — It Just Never Reaches Maintenance
OxMaint connects to your existing WinCC, iFIX, or Wonderware environment as a read-only client, turning alarm tags into prioritised work orders without a single change to your control system configuration.
What Changes After the Connection Goes Live
The clearest way to see the value of a SCADA-CMMS connection is through what happens to alarms that used to go nowhere. One integrated steel plant tracked a hot strip mill and continuous caster where operators were seeing roughly four hundred SCADA alarms a shift, acknowledging them each time, and turning only a small fraction into an actual maintenance record. After the OPC-UA connection to OxMaint was configured with alarm-to-work-order rules, the same four hundred alarms produced far more tracked, resolved work orders — because alarms that repeated across shifts were finally visible as an asset problem instead of noise that got cleared and forgotten.
The recurring alarms that used to disappear at shift change are the ones that were quietly wearing down bearings and hydraulic seals for months. Once those alarms became visible as tracked assets problems instead of noise an operator cleared, the maintenance team could finally see the pattern and act before the failure, not after it.
Frequently Asked Questions
Stop Losing SCADA Alarms Between the Control Room and the Work Order
WinCC, iFIX, and Wonderware already know when something is wrong. OxMaint makes sure maintenance knows it too — in under sixty seconds, with full asset history attached, and without touching a single line of PLC logic.
.png)
