Skip to content
DigiOS.
Log inBook a working session
DigiFactory · Plant data

One model of plant, line and machine, with every reading tied to its work order.

DigiFactory holds your plant as one ISA-95 model: sites, areas, lines and machines. Each reading carries its work order, its lot, its operator and its location, and goes out to a unified namespace for your MES, ERP and historian.

Describe one line

The plant as your engineers draw it.

Plant, area, line, machine: the model follows ISA-95, so the names your MES and ERP use are the names DigiFactory uses. A machine is added once, with its type, and its faceplate, alarms and trends follow.

  • Line and machine types reused across plants.
  • A change to the model is a controlled change.
Every reading is tied to its order, lot, operator and location where it is taken, and published under its place in the site, area, line and equipment, for other systems to use.

A reading on its own, and a reading in context

Which batch
A tag on a machineMatched later, by timestamp.
A reading in the modelCarried with the reading: the work order and the lot.
Which shift
A tag on a machineLooked up in a roster.
A reading in the modelThe operator on the machine when it was taken.
Which machine
A tag on a machineA tag path.
A reading in the modelLine 2, filler, in the plant model.

Three views of the same data

Plant, area, line, machine.

The plant as your engineers draw it, with each machine in its place and carrying its type.

Plant dataEvery reading belongs to a job: a work order, a lot, an operator, a machine. Find a machine in the tree, see what its latest reading is tied to, and see which topics carry it.

A number with its work order.

A fill weight belongs to a machine, a work order, a lot and the operator who was there.

Plant dataEvery reading belongs to a job: a work order, a lot, an operator, a machine. Find a machine in the tree, see what its latest reading is tied to, and see which topics carry it.

The names your systems listen to.

Each reading goes out under its place in the plant, ready for your MES, your ERP and your historian.

Plant dataEvery reading belongs to a job: a work order, a lot, an operator, a machine. Find a machine in the tree, see what its latest reading is tied to, and see which topics carry it.

Every number knows its batch.

Work order, lot, operator and location are stored with the reading, not matched up afterwards.

What it speaks

Standards and protocols
CategoryNamesWhat it does
ModelISA-95Plant, area, line and machine, in the layers the standard describes.
PublishingUnified namespace, MQTT, Sparkplug B at the device edgeOne name for each reading, by its place in the plant.
MachinesPLC, Modbus TCP, EtherNet/IP, PROFINET, edge gatewayWhere the readings come from.
Plant systemsMES, ERP, BOM, routings, work ordersWhat the readings are tied to.

Where each part stands

Parts of plant data and where each stands
PartWhere it stands
One model of plant, area, line and machine
Every reading tied to its work order, lot, operator and location
Published to a unified namespace

Around plant data

Operator screensA screen for each line, from the model.Equipment and controlTake work to the machines.ProductionKitting and assembly with every lot traced.

Questions

Do we have to model the whole plant first?

No. Start with one line. Each machine joins the model as you connect it.

Which systems can listen?

Any that speak MQTT, REST or webhooks: your MES, your ERP, your historian and your reports.

Describe one line.

Tell us which machines are on it. We'll show you the model and one reading with its work order.

Describe one line