Available
Integrate. Don’t rip and replace
Ozari connects to the field devices and enterprise systems you already run, through a fault-isolated gateway and one open data layer. Every value carries its quality and its time, so people and AI can trust it.
- IEC 61850
- IEC 60870-5-104
- DNP3
- Modbus TCP
- MQTT Sparkplug B
- OPC UA
- CIM / CGMES
- ICCP / TASE.2
- Syslog and CEF
- InfluxDB line protocol
- Prometheus
- OIDC
Protocols
Honest status, protocol by protocol
We label each one by how far it has been proven. Lab-grade means tested against reference servers, not yet in the field.
| Protocol | Used for | Status |
|---|---|---|
| IEC 61850 (MMS) | Substation automation | Via certified stack Lab-proven against a reference server. GOOSE and sampled values are out of scope. |
| IEC 60870-5-104 | Telecontrol | Native, lab-grade Passes 18 of 18 conformance tests. A certified stack is also verified. |
| DNP3 | Telecontrol | Via certified stack Control proven in the lab. Production needs a commercial stack licence. |
| Modbus TCP | Inverters, meters, battery gateways | Native, lab-grade Monitor and control. |
| MQTT Sparkplug B | Edge gateways | Native, lab-grade Monitor only. |
| OPC UA | Plant and industrial systems | In development Through the gateway and a certified stack. |
| ICCP / TASE.2 | Peer control centres | Lab-grade model Transport through a certified stack, in development. |
| CIM / CGMES | Network models | Built Core-class import and export, round-trip tested. |
| IEEE 2030.5 (CSIP-AUS) | Customer solar and batteries in Australia | Not supported Ozari does not connect to CSIP-AUS utility servers today. DER control runs through Modbus gateways. |
Architecture
Why a separate gateway
Fault isolation
Certified vendor stacks run in their own process. If one crashes, the control plane keeps running.
Certification stays intact
Vendor stacks keep their certification, and the control plane stays small and pure Go.
Clean zoning
Gateways sit in their own zone, near the field. Links to the control plane use TLS or mutual TLS.
Data out
Your data, in the systems you already use
Historian
InfluxDB line protocol and file export. PI, AVEVA or Timescale connect through the same interface as a project integration.
Security analytics
Audit and security events as RFC 5424 syslog or CEF, over UDP or TCP, for the security platform you use.
Network models
CIM/CGMES export for planning and GIS tools, plus JSON.
Monitoring
Prometheus metrics, alert rules and a ready-made Grafana dashboard.
Peer control centres
ICCP/TASE.2 object model for data exchange with other control centres (lab-grade).
Operator console
A REST API for control and a live event stream for the console.
Commissioning
One point list, not two
The gateway can supply the tag-to-I/O map, so your engineers do not keep two copies in step. Each point carries its address, scale, offset and quality.
- A/B field-link redundancy for gateways that support it.
- Quality on every value: good, stale, bad or substituted.
- Network models imported from CIM/CGMES or JSON.
- A field simulator for testing the full path before site work.
Start safely
Begin with a read-only shadow pilot
Ozari runs beside your current systems, sees the same data and issues no commands. You measure the value with your own data before anything changes.