Getting startedIndustrial data and context
Industrial data and context
A plant can have several names for the same machine. A historian tag, an equipment drawing and an ERP asset number become useful together only when someone verifies that they refer to the same physical asset.
Customer guide · Updated 14 November 2026
#Core concepts
| Concept | What it means at the plant |
|---|---|
| Asset | A physical item with a stable identity, such as a fan, motor or bearing. Record its parent line, location and corresponding identifiers in each source system. |
| Signal and observation | A signal measures a property at a particular point. An observation is its value at a time, with a unit, source and quality status. “Fan vibration” alone does not identify a bearing position or measurement type. |
| Operating context | Speed, load, running mode and recent interventions help determine which readings are comparable. Start-up and steady production may need different baselines. |
| Ontology | POLYCRON is designed to describe industrial entities and their relationships. The same fan can be linked to its motor, bearings, sensor channels, maintenance history and the line it serves. |
| Finding and evidence | A finding is an interpretation of observations. Keep its supporting time window, baseline, contributing signals and competing explanations available for review. |
| Action and outcome | An inspection request records an intended action. The technician’s measurements, observations and completion record establish what actually happened. |
#How a reading reaches a user
Where an existing plant system exposes suitable data, the deployment can use that connection. Where a measurement is missing, the proposed hardware route uses RAX for acquisition and RGX as the edge gateway. RAVEN handles connectivity and data exchange. POLYCRON supplies asset context. For machine health, ORCAS interprets the evidence and Ultron presents the finding to the user.