Metasys integration that reaches the systems other tools can't.
Connect Johnson Controls Metasys to the energy, work-order, ERP + AI systems your estate runs on. Unify NAE and SNE engines with every other BMS brand across your buildings in real-time, while fire and life-safety stay untouched.
+
Live demo · Claude querying Metasys + ops via Rayven MCP
Trusted by 240+ teams across Australia + globally
Metasys is brilliant at what it does. Useless at everything else your data + AI needs to touch.
Metasys runs each campus from its engines and UI, but energy managers rebuild trends by hand, maintenance hears of faults late, and buildings on other brands stay outside the Metasys picture.
The integration tool you've already tried probably can't fix it.
SaaS-to-SaaS. Useful, until it isn't.
Connectors for Metasys, Slack + a thousand other SaaS apps. Cheap + fast for the easy half of integration. Where they hit a wall:
- Energy + ESG platforms needing live kWh, demand and chiller-plant runtime per building
- CMMS work-order systems that should raise a job when Metasys alarms fire
- ERP and finance systems needing building energy cost by site and asset
- Tenant and workplace apps needing live comfort and booking-driven conditions
- Data warehouses and AI agents needing live Metasys API point, trend and alarm history
Energy, metering, ERP, work orders + 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.
- Metasys + every energy/EMS, work-order (CMMS) and ERP system
- BACnet, Modbus, LonWorks, KNX, MQTT + 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
Metasys + Rayven: AI, automation + tools that reach every system you run.
5 examples of what Rayven customers run on Metasys + integrated systems. Built in weeks, not months.
Alarms become work orders
A Metasys alarm on an AHU, chiller or pump raises a job in your CMMS automatically, with the trend attached. Maintenance acts on the fault before comfort slips.
Engine data to the energy model
Chiller-plant runtime, sub-meter kWh and demand from NAE and SNE engines stream into your energy model in real-time. Energy teams optimise sequencing across the whole campus estate.
Supervised setpoint writeback
Where you scope it, Rayven writes optimised zone and schedule setpoints back to Metasys engines under supervision. Consumption drops while fire and life-safety stay untouched and Johnson Controls stays in control.
Comfort follows occupancy
Occupancy and comfort conditions flow into tenant and workplace apps so people see live temperature and booking status. Facilities close comfort tickets before they become complaints.
Metasys data, AI-ready
Every point, trend and alarm from the Metasys API streams into Rayven's Industrial AI Data Fabric. AI agents flag plant trending to failure and rank sites by energy waste across the portfolio.
Integration is the start with Rayven.
Here's what comes with it.
Rayven isn't just a Metasys connector. It's the operational software platform underneath - so once Metasys is connected, four more capabilities come online by default.
AI-ready data layer (AI Data Fabric)
Metasys 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 Metasys and every other connected system. Your AI stops guessing - cites real Metasys records + numbers.
Learn more →
Automation + AI agents
Workflows + AI agents act on Metasys 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 Metasys data. No separate BI tool, no separate dev stack.
Learn more →
All on top of your existing stack. No rip + replace. Metasys stays Metasys. Rayven works on what you've already built. Specifically tuned for Metasys NAE and SNE engines with the Metasys REST API across a mixed-vendor estate.
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.
Metasys 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 Metasys engines + REST API.
Rayven reads Metasys over native BACnet and the Metasys REST API across NAE and SNE engines. Real-time point, trend and alarm sync feeds energy, work orders and AI, with supervised writeback scoped to comfort - never fire or life-safety.
We stay after go-live.
No handoff. No disappearing. Rayven is a long-term partner when your Metasys 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 Metasys data needs to live. Your residency, your rules, your local compliance environment.
The questions Metasys admins, RevOps + IT ask first.
If you're evaluating Rayven for Metasys integration, these are the things worth knowing before booking a call.
The 30-minute call covers
- Your Metasys + 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 Metasys integration?
Metasys integration is the practice of connecting Johnson Controls' Metasys to the rest of your estate stack - energy, work orders, ERP and AI - so points, trends and alarms are visible everywhere they matter. Rayven delivers it as part of an Industrial AI Data Fabric.
How does Rayven connect Metasys to other systems?
Rayven connects over Metasys native BACnet and the Metasys REST API for real-time bidirectional sync. Points, trends, schedules and alarms from NAE, NCE, SNE and SNC engines all flow as first-class integration events. See the Rayven Platform for how the layers fit together.
What systems can Rayven connect Metasys to?
Rayven connects Metasys to 1,228+ systems including energy platforms, CMMS, ERP, and sibling BMS brands like OpenBlue and Desigo CC. Custom controllers are part of done-for-you delivery.
Does Rayven control or replace Metasys?
No. Metasys keeps running the building. Rayven reads its data and, where you scope it, writes energy and comfort setpoints back under supervision. Rayven never writes to fire or life-safety systems and does not replace your controls - it adds a real-time data and AI layer across the estate. See how the platform works.
What are the most common Metasys integration use cases?
Top use cases are alarm-to-work-order into CMMS, engine data to the energy model, supervised setpoint writeback, comfort to tenant apps and estate-wide AI. See the automations above for specifics.
What are the technical specifics of Metasys integration with Rayven?
Rayven connects to Johnson Controls Metasys over native BACnet and the Metasys REST API for real-time bidirectional sync. Points, trend logs, schedules and alarms from NAE, NCE, SNE and SNC engines are mapped field by field into energy, CMMS, ERP and AI targets. Authentication uses Metasys REST API tokens and BACnet device credentials at the edge. Rayven reads continuously and, where you scope it, writes energy and comfort setpoints back under supervision; it never writes to fire or life-safety systems and Johnson Controls stays in command of the building. REST API scopes and versions vary by release and engine generation, so Rayven maps to a stable point model, and high-volume trend history is batched and back-pressured. MVE validated sites keep change-controlled access. Multi-site Metasys estates reconcile to one point model via edge collectors, running on-prem or sovereign-hosted. Validated against Metasys NAE and SNE engines alongside other BMS brands.
Metasys + 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.