One place to look.
Ask where a pallet was when the cold room went out of range, and see the order and the operator beside it.
DigiWarehouse · Plant data
One model of your building, with every reading tied to the work.
Sites, zones, conveyors and equipment sit in one model, following ISA-95. Each reading carries the order, the lot, the operator and the place it belongs to, and DigiOS publishes it to a unified namespace, so the other systems that need it can listen.
Three views of the same data
Site, zone, line, equipment.
The building as your people describe it, with each piece of equipment in its place and carrying its type.
- Your warehouse
- Dock
- Line 2
- Infeed
- Scale S2
- Sorter SD-201
- Lane 3
- Cold room 1
3.12 kgat 10:42:07
- Order
- SO-48213
- Carton
- C-77120
- Packed by
- Mei at 10:31
- Place
- Line 2, scale S2
| Topic | Value | Time |
|---|---|---|
| yourwarehouse/line2/scale-s2/weight | 3.12 kg | 10:42:07 |
| yourwarehouse/line2/sorter-sd201/speed | 0.82 m/s | 10:42:07 |
| yourwarehouse/line2/lane3/full | true | 10:38:22 |
| yourwarehouse/coldroom1/temperature | 7.2 °C | 10:42:00 |
| yourwarehouse/dock/door5/open | true | 10:30:04 |
A number with its context.
A temperature is not just a tag: it belongs to a cold room, a pallet's lot, the order that put it there and the person on shift.
- Your warehouse
- Dock
- Line 2
- Infeed
- Scale S2
- Sorter SD-201
- Lane 3
- Cold room 1
3.12 kgat 10:42:07
- Order
- SO-48213
- Carton
- C-77120
- Packed by
- Mei at 10:31
- Place
- Line 2, scale S2
| Topic | Value | Time |
|---|---|---|
| yourwarehouse/line2/scale-s2/weight | 3.12 kg | 10:42:07 |
| yourwarehouse/line2/sorter-sd201/speed | 0.82 m/s | 10:42:07 |
| yourwarehouse/line2/lane3/full | true | 10:38:22 |
| yourwarehouse/coldroom1/temperature | 7.2 °C | 10:42:00 |
| yourwarehouse/dock/door5/open | true | 10:30:04 |
The names other systems listen to.
Each reading goes out under its place in the model, ready for your ERP, your historian or your analytics.
- Your warehouse
- Dock
- Line 2
- Infeed
- Scale S2
- Sorter SD-201
- Lane 3
- Cold room 1
3.12 kgat 10:42:07
- Order
- SO-48213
- Carton
- C-77120
- Packed by
- Mei at 10:31
- Place
- Line 2, scale S2
| Topic | Value | Time |
|---|---|---|
| yourwarehouse/line2/scale-s2/weight | 3.12 kg | 10:42:07 |
| yourwarehouse/line2/sorter-sd201/speed | 0.82 m/s | 10:42:07 |
| yourwarehouse/line2/lane3/full | true | 10:38:22 |
| yourwarehouse/coldroom1/temperature | 7.2 °C | 10:42:00 |
| yourwarehouse/dock/door5/open | true | 10:30:04 |
A tag name, and a reading with its context
Where it is
A tag in a PLCA register address or a tag name.
A reading in the modelCold room 2, zone C, the building it belongs to.
What it is for
A tag in a PLCNothing the reading says.
A reading in the modelThe order, the lot and the client it belongs to.
Who it involves
A tag in a PLCNobody.
A reading in the modelThe operator on shift and the person holding control.
Who can use it
A tag in a PLCThe system that owns the PLC.
A reading in the modelAny system that listens to the namespace.
Publish once, listen anywhere.
DigiOS publishes the model and its readings to a unified namespace over MQTT, on the ISA-95 path, with Sparkplug B at the device edge. Your ERP, your historian and your analytics tools listen to the names they need, and none of them has to know which PLC a reading came from.
- One name for each reading, by its place in the model.
- The same readings feed the operator screens and the alarms.
A reading is worth what you can tie it to.
Order, lot, operator and place travel with every number, from the sensor to the report.
What it speaks
| Category | Names | What it does |
|---|---|---|
| Model | ISA-95 | Sites, areas, lines and equipment in the layers the standard describes. |
| Publishing | Unified namespace, MQTT, Sparkplug B at the device edge | Readings and the model go out under one name each. |
| Identifiers | GTIN, SSCC, GS1-128, LPN | The pallet, the product and the lot a reading belongs to. |
| Systems | ERP, MES, REST, webhooks | Your other systems read and write the model through the same names. |
What a site gets
Fewer integrations.
A system listens to the namespace once, instead of being wired to each PLC.
Screens and alarms on the same data.
What an operator sees, what raises an alarm and what your reports use are the same readings.
Questions
Do we need to model everything first?
No. Start with one zone. Equipment joins the model as you connect it.
Can we keep our own historian?
Yes. It listens to the namespace like any other system.
Tell us what you'd want to ask.
We'll show you one reading from your floor with its order, lot and operator.