Mipac integration that reaches the systems other tools can't.
Connect Mipac to the historian, LIMS, ERP + AI agents your plant runs on. Read process, metallurgical accounting and alarm data across concentrators, refineries and smelters, without touching control or the safety layer.
+
Live demo · Claude querying Mipac + ops via Rayven MCP
Trusted by 240+ teams across Australia + globally
Mipac is brilliant at what it does. Useless at everything else your data + AI needs to touch.
Mipac runs the plant control and metallurgical accounting well, but recovery and grade data maps to LIMS and ERP by hand, alarms never become work orders, and there is no live path to the enterprise historian, business or AI.
The integration tool you've already tried probably can't fix it.
SaaS-to-SaaS. Useful, until it isn't.
Connectors for Mipac, Slack + a thousand other SaaS apps. Cheap + fast for the easy half of integration. Where they hit a wall:
- Enterprise historians (PI / OSIsoft) that need Mipac plant tags unified across concentrators, refineries and smelters
- LIMS and assay systems that should tie metallurgical accounting and grade results to the process conditions that produced them
- ERP that needs production, recovery and energy data posted against the right plant and cost centre
- CMMS and reliability tools that should turn Mipac alarms and limit breaches into work orders
- Data warehouses and AI models needing live tag, recovery and metallurgical-accounting data beyond Mipac's own reporting
Historians, LIMS, ERP, maintenance + 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.
- Mipac + every historian, LIMS and ERP system
- OPC-UA, historians (PI), Modbus, batch (S88) + 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
Mipac + Rayven: AI, automation + tools that reach every system you run.
5 examples of what Rayven customers run on Mipac + integrated systems. Built in weeks, not months.
Plant tags + accounting, unified
Rayven reads Mipac control tags, production data and historian data via OPC-UA and Modbus and streams them into your historian and a real-time Industrial AI Data Fabric - read-only, full resolution, control untouched.
Grade tied to the process
Mipac metallurgical accounting and grade results flow to LIMS and assay systems so recovery maps to the process conditions behind it. Off-spec grade surfaces live rather than in a shift reconciliation.
Alarms become work orders
Alarms and process-limit breaches flow into CMMS as work orders with full context. Reliability acts on live condition data instead of a control screen.
Recovery + production to the ledger
Production, recovery and energy data post to ERP against the right plant and cost centre. Planning and finance work from live figures, not overnight files.
Minerals process AI, read-only
Every tag, alarm and metallurgical-accounting figure streams into the fabric where AI models flag recovery loss, energy waste and early faults - the same AI reach a large refinery gets, read-only, control untouched.
Integration is the start with Rayven.
Here's what comes with it.
Rayven isn't just a Mipac connector. It's the operational software platform underneath - so once Mipac is connected, four more capabilities come online by default.
AI-ready data layer (AI Data Fabric)
Mipac 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 Mipac and every other connected system. Your AI stops guessing - cites real Mipac records + numbers.
Learn more →
Automation + AI agents
Workflows + AI agents act on Mipac 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 Mipac data. No separate BI tool, no separate dev stack.
Learn more →
All on top of your existing stack. No rip + replace. Mipac stays Mipac. Rayven works on what you've already built. Specifically tuned for read-only Mipac metallurgical accounting and OPC-UA tag reads on minerals plants, with control untouched.
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.
Mipac 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 Mipac's minerals-plant model.
Rayven reads Mipac control tags, alarms, historian data and metallurgical accounting via OPC-UA, Modbus and API. Read-only sync gives concentrators, refineries and smelters the same historian, ERP and AI reach - control and safety are never touched.
We stay after go-live.
No handoff. No disappearing. Rayven is a long-term partner when your Mipac 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 Mipac data needs to live. Your residency, your rules, your local compliance environment.
The questions Mipac admins, RevOps + IT ask first.
If you're evaluating Rayven for Mipac integration, these are the things worth knowing before booking a call.
The 30-minute call covers
- Your Mipac + 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 Mipac integration?
Mipac integration connects Mipac's process-control and metallurgical-accounting systems to the rest of your operation - historian, LIMS, ERP, CMMS and AI - so tags, alarms and metallurgical accounting are visible everywhere they matter. Rayven delivers it as part of an AI data fabric, reading Mipac data only and never touching control or safety.
Does Rayven control Mipac systems or touch our safety functions?
No. Rayven reads Mipac process data, metallurgical accounting and historian through OPC-UA, Modbus and API only. It never writes into the control system, never controls the plant, and never touches the SIS or safety layer. The feed is one-way - out of the control network into your historian, ERP and AI. See how the Rayven Platform separates integration from control.
What systems can Rayven connect Mipac to?
Rayven connects Mipac to 1,228+ systems including your historian, ERP, CMMS, LIMS and AI agents, plus sibling control systems like ABB 800xA and Honeywell Experion PKS. Custom read-only connectors are part of done-for-you delivery.
How long does Mipac integration take with Rayven?
Most Mipac integrations go live in 2-12 weeks. A single Mipac-to-historian or Mipac-to-ERP read flow runs in 2-3 weeks; a full process-data fabric with recovery and energy models runs 6-12 weeks. Choose DIY, done-for-you or hybrid delivery.
Mipac is a specialist minerals control vendor. Is it worth integrating with Rayven?
Yes. Minerals plants gain most from reaching the enterprise: full-resolution reads into a shared historian, metallurgical accounting and grade context to LIMS, alarm-to-work-order routing into CMMS and the same AI and dashboard reach a large refinery gets - all read-only. Rayven complements Mipac, never replaces or controls it.
What are the technical specifics of Mipac integration with Rayven?
Rayven reads Mipac process-control systems through OPC-UA, OPC-HDA, Modbus and vendor APIs, plus Mipac's metallurgical-accounting and historian interfaces, using read-only accounts scoped to the control network. Control tags, production and batch data, grade and recovery figures, alarms and events are read at full resolution and mapped into your historian, ERP, CMMS, LIMS and AI targets. Because Mipac deployments are bespoke per plant, tag and metallurgical-accounting schemas are normalised into one consistent estate view so concentrators, refineries and smelters read into the same fabric. Historian back-fills use batched historical queries with back-pressure so live acquisition is never disturbed. The control and safety layers are never written to and never touched; the integration is a one-way read out of the control network. Validated against Mipac control and metallurgical-accounting deployments across minerals-processing plants, coexisting with existing Mipac reporting.
Mipac + 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.