O-ARC
AnalyseA tag is not an asset. O-ARC makes it one.
Telemetry arrives as thousands of tags with names somebody chose in 2019. O-ARC connects to the systems that hold them, maps each tag onto the asset it actually belongs to, and keeps the history, so a reading can be read alongside the imagery of the same equipment.
O-ARC resolves every tag in your historian and control system to the component it actually belongs to, so telemetry and imagery finally describe the same piece of equipment.
The data is already there. Nothing can read it together.
The historian has ten years of inverter current. The SCADA system alarms on thresholds set at commissioning. The inspection platform has a thermal anomaly on string B-07-14. None of the three knows that these are the same piece of equipment, so the correlation that would tell you whether the hotspot matters has to be made by a person, from memory, if anyone thinks to make it at all.
From a name somebody chose in 2019
The same six weeks of inverter data, four times over: as it arrives, as it is understood, as it is compared, and as it becomes something worth acting on.
- 01
The tags arrive exactly as they are
A historian hands over strings like INV04_DC_A_I at whatever rate it was configured for. No hierarchy, no units you can trust, no idea which physical thing any of it describes.
o-arcThe tags arrive exactly as they are1/4 - 02
Each one is bound to a real asset
The tag becomes inverter 04, string A, current, on a named site. That mapping is the whole job: it is what lets a question about an asset reach the data underneath it.
o-arcEach one is bound to a real asset2/4 - 03
The series is read against its peers
A single current curve tells you almost nothing. The same curve next to the other strings on the same combiner, under the same irradiance, tells you which one is behaving differently.
o-arcThe series is read against its peers3/4 - 04
Drift is called before it is a fault
No threshold has tripped and no alarm has fired. The string has simply been falling away from its neighbours for six weeks, which is the point at which it is still cheap to fix.
o-arcDrift is called before it is a fault4/4
From tag to signal
Six things happen between a reading arriving and it meaning something about a specific asset.
Connectors
SCADA, OPC-UA, Modbus TCP and RTU, MQTT and Sparkplug B, IEC 61850, DNP3, BACnet, historians, and REST or webhook for anything else. Read from what you run, no migration.
Edge gateway
Connectors run at the site. When the link drops, readings buffer locally and reconcile on reconnect, so a remote site does not simply have a hole in its history.
Contextualisation
The step that matters: every tag is mapped to a component in the asset register, so telemetry, imagery and work history describe the same thing and can be queried together.
Time series
History kept at source resolution, with the aggregates that make it usable. Compare a reading against the same asset last year, not against whatever the dashboard has cached.
Drift and anomaly detection
Detection against an asset's own history and against its peers, so a slow decline that never crosses a fixed threshold is still visible before it becomes an outage.
Failure prediction
Remaining useful life and failure mode estimates built from telemetry and work history together, since neither on its own tells you why something is degrading.
What it connects to
Everything here reads from the system that already owns the data. Nothing requires that data to move first.
- OPC-UAPlant and process control, modern SCADARead, subscribe
- Modbus TCP / RTUInverters, meters, trackers, BOS devicesPoll
- MQTT / Sparkplug BEdge devices, IIoT gatewaysSubscribe
- IEC 61850Substation automation, protection relaysRead, report
- DNP3Utility SCADA, RTUsPoll, unsolicited
- BACnetBuilding and facility plantPoll
- Historian APIsPI, and other time-series archivesBackfill, stream
- REST / webhookAnything with an API and no standard protocolPush, pull
The systems already running your site
O-ARC reads what is there rather than asking you to replace it. Control systems, historians and the business systems the work eventually has to land in.
Control and field
- Siemens
- Schneider Electric
- ABB
- Rockwell
- GE
- MQTT
Historians and stores
- InfluxDB
- PostgreSQL
- Apache Kafka
- Snowflake
- Grafana
- APAVEVA PI
Business systems
- SAP
- IMIBM Maximo
- Autodesk
- Esri ArcGIS
- DJI
- SSalesforce
Tags read
14,208
Assets resolved
3,114
Live
Streaming from four systems, normalised into one asset model.
Where it earns its place
A thermal hotspot on its own is a maybe. A thermal hotspot on a string whose current has been drifting for six weeks is a decision.
The imagery finds something
O-EYE classifies a hotspot on string B-07-14 and gives it a severity.
The telemetry is checked
O-ARC pulls that string's current and voltage history and compares it against its neighbours on the same combiner.
The record is consulted
O-OPS shows the string was reterminated eleven months ago, and by whom.
One decision comes out
O-AGENT raises the work order with all three attached, or holds it if the confidence sits below your bar.
- 01O-EYEDetectInspection & digital twin
- 02O-ARCAnalyseSensors, IoT & telemetry
- 03O-OPSOperationsThe system of record
- 04actsO-AGENTDecide & actThe agentic layer
Every action writes back to the record, so the model sharpens with every job.
Questions
Does this touch our control system?
It reads. O-ARC does not write setpoints and does not sit in a control loop. Where a connector supports writing at all, it is off unless you turn it on.
What about OT network segmentation?
The gateway runs on the site network and pushes outward. It does not require inbound access to your OT segment, which is usually the condition a security team cares most about.
How much history do you need?
It works from the first reading, but drift detection needs a baseline. Backfilling from the historian gives you that on day one instead of in six months.
Our tag names are a mess. Is that a problem?
It is the normal starting condition. Mapping tags to assets is a setup step we expect to do with you, and it is the step that makes everything after it work.