Horner integration that reaches the systems other tools can't.
Connect Horner APG to your ERP, historian, maintenance + AI in real-time. Read OCS register data and machine-state at the edge over Modbus, EtherNet/IP and CsCAN, no SCADA required, without touching control logic.
+
Live demo · Claude querying Horner + ops via Rayven MCP
Trusted by 240+ teams across Australia + globally
Horner is brilliant at what it does. Useless at everything else your data + AI needs to touch.
OCS registers live in Cscape, remote and telemetry sites report by exception, maintenance reacts after a stoppage, and AI models never see live register data across the estate.
The integration tool you've already tried probably can't fix it.
SaaS-to-SaaS. Useful, until it isn't.
Connectors for Horner, Slack + a thousand other SaaS apps. Cheap + fast for the easy half of integration. Where they hit a wall:
- ERP that needs live machine output and run state from all-in-one OCS controllers
- Historian and data-warehouse targets that should hold every OCS register at full rate
- CMMS that should open a work order when an OCS fault or alarm register fires
- OEE and predictive-maintenance models needing live cycle counts, states and reject data
- Remote and telemetry sites where an OCS runs with no supervisory layer in front
SCADA, historians, ERP, IoT + AI. One platform.
The integration platform built for what other tools can't (or won't) reach - plus an AI data fabric, MCP server + app builder layered on top.
- Horner + every SCADA, historian and ERP system
- OPC-UA, EtherNet/IP, Modbus, PROFINET, S7 + custom-built connectors.
- Files, legacy SQL, FTP + custom-built connectors
- Real-time bidirectional sync, tier-aware + rate-limit-safe
- AI Data Fabric, MCP, automation + custom apps included
Horner + Rayven: AI, automation + tools that reach every system you run.
5 examples of what Rayven customers run on Horner + integrated systems. Built in weeks, not months.
OCS registers stream to the fabric
Rayven reads XL, X series and RCC registers and I/O over Modbus, EtherNet/IP and the CsCAN network, then streams them into a real-time Industrial AI Data Fabric with asset and ERP context. No Cscape export, no SCADA layer required.
Fault register raises the work order
An OCS fault or alarm register opens a work order in CMMS automatically, carrying the site, asset and live state so maintenance mobilises knowing the fault, not just that a site tripped.
Output and run state post upstream
Counts, run state and process values read from OCS registers post to ERP and the asset register in real-time, so operations and finance see true site output rather than an exception report.
Telemetry sites report as one
OCS controllers across remote and telemetry sites read into one central fabric over Modbus and MQTT, so a distributed estate reports live from a single model instead of a dial-in per site.
Supervised setpoint writeback, safely scoped
Where explicitly scoped, Rayven writes a non-safety setpoint back to an OCS register under supervision and full audit. It never reprograms the controller and never writes to safety logic; the control loop stays untouched.
Integration is the start with Rayven.
Here's what comes with it.
Rayven isn't just a Horner connector. It's the operational software platform underneath - so once Horner is connected, four more capabilities come online by default.
AI-ready data layer (AI Data Fabric)
Horner data joined with ERP, IoT + legacy - contextualised, unified and structured so AI models, agents and tools can use it without ETL prep work.
Learn more →
Live AI access (Rayven MCP)
Claude, ChatGPT + Gemini get live, governed access to Horner and every other connected system. Your AI stops guessing - cites real Horner records + numbers.
Learn more →
Automation + AI agents
Workflows + AI agents act on Horner data without human intervention - escalate at-risk accounts, trigger operational work, auto-update forecasts, draft customer comms.
Learn more →
Custom apps + portals
Unified customer portals, ops dashboards, mobile field apps, partner portals - built on top of integrated Horner data. No separate BI tool, no separate dev stack.
Learn more →
All on top of your existing stack. No rip + replace. Horner stays Horner. Rayven works on what you've already built. Specifically tuned for Horner OCS register reads over CsCAN and MQTT for remote telemetry.
Rayven is a five-layer platform ALL your integrations + much more
can run on.
Integration is one layer of Rayven. Data, execution, presentation + governance are the other four - all delivered as one platform on one commercial.
Pick the right tool for your stack.
Horner integration looks different at every scale. Honest comparison of the four common paths - Rayven only wins on some of them.
The integration is the easy bit.
The platform + team behind it is the difference.
Platform + team. One commercial.
Not five vendors stitched together. Rayven is the platform AND the Australia-based expert team that scopes, builds + supports it. One commercial. No licence stacking, no finger-pointing.
Built for the all-in-one OCS model.
Rayven reads Horner XL, X series and RCC registers and I/O over Modbus, EtherNet/IP, the CsCAN network and MQTT for real-time sync, resolving OCS register references to engineering-unit tags. Remote telemetry sites read the same way - reads and contextualises only, never a write to safety logic.
We stay after go-live.
No handoff. No disappearing. Rayven is a long-term partner when your Horner evolves, your stack changes, or you push further. 24/7 support. Same team, same platform, same commercial.
Hosted your way, where you need.
Deploy as cloud, private cloud + on-premise - in Australia, the US, the UK, or anywhere else your Horner data needs to live. Your residency, your rules, your local compliance environment.
The questions Horner admins, RevOps + IT ask first.
If you're evaluating Rayven for Horner integration, these are the things worth knowing before booking a call.
The 30-minute call covers
- Your Horner + connected stack today
- What's reachable + which systems to bring in first
- Live walkthrough of Rayven against your scenario
- Time, scope + delivery estimate
- Honest read on whether Rayven's the right fit
What is Horner APG integration?
Horner APG integration means reading registers off XL, X series and RCC OCS controllers and connecting them to ERP, CMMS and AI. Rayven delivers it as part of an Industrial AI Data Fabric, not a per-site dial-in.
Does Rayven reprogram or control our Horner OCS controllers?
No. Rayven reads OCS registers over Modbus, EtherNet/IP and CsCAN and contextualises them. Supervised writeback is limited to explicitly-scoped non-safety setpoints and never touches safety logic or the control loop. See security, governance + hosting.
Can Rayven read Horner APG data without SCADA?
Yes. Rayven reads XL, X series and RCC controllers directly over Modbus, EtherNet/IP or MQTT at the edge, and the built-in OCS HMI means many run with no separate supervisory layer. Where you do run supervisory software, see SCADA integration. Read more in how Rayven works.
What systems can Rayven connect Horner APG to?
Rayven connects Horner APG to 1,228+ systems including ERP, historians, CMMS and sibling controllers like Unitronics and IDEC. Custom connectors are part of done-for-you delivery.
How long does Horner APG integration take with Rayven?
Most Horner APG integrations go live in 2-12 weeks. A single OCS-to-historian or fault-to-work-order flow runs in 2-3 weeks; a distributed telemetry fabric with predictive maintenance runs 6-12 weeks. Choose DIY, done-for-you or hybrid delivery.
Horner OCS controllers have MQTT and a built-in HMI. Why does Rayven add value on top?
MQTT moves raw registers and the HMI stays on the panel; neither joins data across sites, holds history at rate or runs AI. Rayven reads over Modbus, EtherNet/IP and MQTT together, unifies remote sites and adds the analytics and agent layers on top. Read more in how Rayven works.
What are the technical specifics of Horner APG integration with Rayven?
Rayven reads Horner APG XL, X series and RCC OCS controllers over Modbus TCP and RTU, EtherNet/IP, the CsCAN network and MQTT. OCS register references (%R, %AI, %AQ), bit references, I/O and machine-state values are read at the edge and resolved to named engineering-unit tags, then mapped field by field into an Industrial AI Data Fabric alongside historian, CMMS and ERP data. Bit and word references are addressed separately and normalised on the way in, so a raw reference becomes a usable tag. Remote and telemetry sites read into one central model rather than a dial-in per site. Rayven reads and contextualises only; supervised writeback covers explicitly-scoped non-safety setpoints and never writes to safety logic. Authentication and access are governed at the connector with full audit, deployed at the edge, on-premises or with sovereign hosting. Validated against XL, X series and RCC controllers across remote-monitoring and telemetry sites.
Horner + AI integration.
In weeks, not months.
Book a 30-minute call. Walk away with a tailored plan - what's reachable, what to bring in first, time + scope.