Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes

Platform · Unified Namespace

Every signal gets an address that means something.

Raw registers become modelled signals in one hierarchy (enterprise, site, area, process cell, equipment module, device, tag) with units, scaling and context attached. The same model on every site, so the second plant does not need a second vocabulary.

Structure
Enterprise / site / area / process cell / equipment module / device / tag
Carries
Value, unit, data type, quality and timestamp
Reused through
Device profiles shared by identical machines, on every site
Consumed by
Dashboards, integrations, reports and AI access: one definition, many readers

One address per signal

The plant, as one tree.

Every signal sits under the machine that produces it, the same way at every site.

  1. Enterprise Meridian
  2. Site Lyon Foods Plant
  3. Area Processing
  4. Process cell Dough
  5. Device MFB_LYS_MIXER_2
  6. Tag MotorCurrent · 182 A Live value, unit and history

In the product

Find it, subscribe to it, see what depends on it.

Find a signal by where it is

Open the tree from the enterprise down to a machine; every node shows its devices and tags, every signal its live value.

  • Live value and last update on every signal
  • Search across the whole plant
MQTT · one value
# topic
v1/Meridian/Lyon_Foods_Plant/Processing/Dough/MFB_LYS_MIXER_2/telemetry/MotorCurrent

# payload
{
  "ts": "2026-11-07T08:15:30.123Z",
  "value": 182.4,
  "dataType": "Double",
  "unit": "A",
  "quality": "Good",
  "source": "Proxus"
}

Subscribe to the plant, not to a PLC

Each gateway’s built-in MQTT broker publishes every value under its place in the tree.

  • JSON by default, Sparkplug B as a gateway setting
  • One site at a time: v1/Meridian/Lyon_Foods_Plant/#

See what depends on a signal

Trace any device to see what it relies on and everything it feeds, before you change or retire it.

  • Its gateway, profile and tags
  • The historian, rules and targets it feeds

Real Proxus screens; the machine data shown is simulated.

Want to see your plant as one tree? Plan your namespace

Technical details Problems it solves, every capability and the full protocol table

What it solves

What teams run into without it.

  • DB1.DBD0 is not a cycle time

    Meaning lives in a spreadsheet or in one engineer’s head, so every new report starts with the same archaeology.

  • Every site names things differently

    Two plants, two naming schemes, and any group-level comparison becomes a mapping exercise.

  • No agreed source of truth

    When three systems each hold their own version of a value, the meeting is about whose number is right.

What you get

Built in, not bolted on.

  • Modelled hierarchy

    An ISA-95-compatible structure that reflects the plant, not the wiring cabinet.

  • Browsable and searchable

    Explore the namespace with the live value and last update on every node, and quality and targets in the detail panel.

  • Device profiles

    Describe a machine type once (protocol, connection settings, tags); every device that uses the profile inherits it, so new lines start from the model instead of reinventing it.

  • Register to signal mapping

    Scaling, units and data types applied at the point of collection, so consumers never have to guess.

  • Path-based permissions

    Allow or deny access by namespace path, so a supplier or a team sees exactly the branch it should.

  • One definition, many consumers

    Dashboards, integrations and AI access all read the same modelled signal instead of separate copies.

What this enables

What the capabilities add up to, in practice.

  • Give every signal one address that means the same thing on every site
  • Cut the archaeology out of every new report or integration
  • Roll out a new site with a model instead of a naming argument
  • Grant access by namespace branch rather than by database credential

Detail

Topic structure

Each gateway’s built-in MQTT broker publishes the namespace, one topic per value, so any authorised subscriber reads it in plant order.

MQTT and the UNS topics
Topic
v1/<enterprise>/<site>/<area>/<process cell>/<equipment module>/<device>/telemetry/<tag>
One site
v1/Meridian/Lyon_Foods_Plant/#
Payload
JSON by default; Sparkplug B 3.0 is a setting on the gateway

Questions

What teams ask before the first call.

Ask something else
What is a Unified Namespace, in practical terms?

One address space where every signal in the business has a single, meaningful name (enterprise, site, area, process cell, equipment module, device, tag) instead of each system holding its own naming scheme. Consumers subscribe to that structure rather than to individual machines.

Does this follow ISA-95?

The hierarchy is ISA-95-compatible in shape. You are not forced into it: the model is yours to define, and most plants find the ISA-95 levels map cleanly onto how they already talk about the site.

How much modelling work is it to start?

Start with one line. Model the machine types on it, and the second identical machine inherits the model through a template. The work is front-loaded per machine type, not per machine.

What happens when we add a second site?

It reuses the same model and templates. That is the main reason to model at all: the second plant should not need a second vocabulary, and group-level comparison should not need a mapping exercise.

Can we restrict who sees which part of the namespace?

Yes. Permissions are applied by namespace path, so a contractor, a supplier or a specific team can be given exactly one branch and nothing else.

Plan your namespace

How is your plant named today?

Tell us how many sites and lines you have. An engineer sketches the tree with you and replies within one working day.

Your naming today

We use your email to answer this check. Marketing emails only if you tick the box; no resale. Privacy notice

Plan namespace Live demo