Skip to content
MaestroHub
Menu
Partner portalFree trialGet started

Context Engine · semantic layer

One plant. One language.

Every line names and measures things its own way. The semantic layer gives each signal one meaning and one unit, set once, so alarms, charts, dashboards and reports agree.

Illustrative values from the demo plant.

What it solves

Five problems every plant has. Solved once.

Here is what it does.

LiveBeta

The new line speaks °F

TodayLine 4 came from another vendor. Its numbers cannot sit next to the others, and every alarm needs a second set of limits.

With a meaningSay once what the signal is. From then on every chart, alarm and reader gets °C. The device never changes.

Line 2 sends °C and Line 4 sends °F. After one step, both sit on one °C scale.
LiveBeta

Four names for one measurement

Todayproduct_temp, ProductTemp, and a third tag in the blending hall. Nobody can ask for every product temperature.

With a meaningGive them one meaning in one step, whatever each tag is called. New look-alikes are suggested, and a person decides.

One meaning, held by topics with three different naming patterns.
LiveBeta

One alarm for every pump

TodaySix pumps on three lines means six alarms to keep in step.

With a meaningSet the limit once on the meaning. Before you save it, see how often it would have fired.

One limit for six pumps, with a preview before it is turned on.
LiveBeta

The sensor that lies quietly

TodayA transmitter freezes and keeps sending its last value, marked good. The PLC never notices.

With a meaningA meaning knows how a real signal behaves. A value that stops moving is flagged in plain words, with what usually causes it.

A frozen transmitter, flagged on its own topic page.
LiveBeta

Every reader gets clean data

TodayDashboards, scripts and reports each convert Line 4 themselves, each a little differently.

With a meaningMQTT readers and the REST API receive the converted value with its unit attached. Nobody converts it again.

What a reader of Line 4 receives once its signal has a meaning.

Screens from MaestroHub's development build on the built-in demo plant.

Questions

What is MaestroHub's semantic layer?

It gives each signal in the Unified Namespace one meaning: what it measures and the unit it is shown in. Signals from different lines, named differently or sent in other units, then read as one, so alarms, charts, MQTT readers and the REST API agree.

Do I have to change my devices or tag names?

No. The device keeps sending what it sends and every tag keeps its name. The meaning is set in MaestroHub, and the conversion happens there.

Do I have to build a plant model first?

No. Start from your data: MaestroHub reads your signals, recognises what it can, and asks only where two answers are possible. One press applies it, and Undo takes it back.

Status: Live. How MaestroHub works shows how a raw tag gets its name, unit and checks today.

Start from your data, not a model editor

MaestroHub reads your signals, recognises what it can, and asks only where two answers are possible. One press applies it, and Undo takes it back.

Cookie preferences

Choose which categories of cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.