Skip to content
Ordanis
PT

Guide · Industrial asset monitoring

Monitoring assets starts with knowing what each signal is.

A tag value alone says nothing. Useful industrial asset monitoring links every signal to its component, asset, line and plant — and only then computes state, stops and deviations. This is how Ordanis organizes the data.

The asset model

Every level belongs to an organization and a plant; isolation between plants is enforced on the server.

  1. 01

    Organization

    The company and its access rules.

  2. 02

    Plant

    Each site, with its own time zone and scope.

  3. 03

    Area and line

    Where the asset works and what it produces.

  4. 04

    Asset

    The machine, with a stable identity from project to operation.

  5. 05

    Component

    Motor, bearing, pump: where the failure happens.

  6. 06

    Signal

    Temperature, vibration, current, counter, state.

From raw tag to signal with context

  • 01

    Versioned mapping

    Each tag is linked to an asset signal by a person who accepts, edits or rejects it. Every change is versioned and audited.

  • 02

    Explicit units

    Unit conversions are declared in the mapping — never guessed.

  • 03

    Data quality

    Coverage, gaps, out-of-range values and clock skew feed an explainable score; bad data does not feed calculations.

  • 04

    Machine state

    Per-asset rules derive RUNNING, stopped, setup and unknown from telemetry — the basis for stops, MTBF and OEE.

How the data arrives

  • 01

    Ordanis Edge · OPC UA

    Software on a commercial industrial PC in the plant. Read-only OPC UA client, outbound-only connection (HTTPS), local buffer for network outages and its own identity.

  • 02

    REST and SQL connectors

    Reads systems such as CMMS, MES or historians, read-only, with an allowlist of queries, timeouts and row limits.

  • 03

    CSV/Excel import

    Asset registers, historical work orders and other data with preview, explicit commit and per-row lineage.

Current limits

  • The Edge was tested against simulated OPC UA servers, not yet against a customer's physical PLC.
  • Other protocols (Modbus, MQTT, Profinet…) are not part of the product today.
  • No connector has been validated against a customer's real system; new connectors are only built for a concrete use case.
  • Nothing is written to a PLC or OPC UA node: the machine control policy is read-only.
Ordanis

One Industrial Reality.

Start with one operational problem. Expand into one industrial reality.

Request Pilot