in development

Smart factory is being built on the platform the six live kinds of asset run on. Everything here exists in the product today unless it is marked next; none of it has been through an acceptance run yet.

Smart factory

It reads your machines. It never writes.

Every machine on the floor read in its own protocol, into the same twin, alarms and work orders as everything else you run.

Read-only statement · generated each release
Modbusfunction codes 01–04 only
OPC UAread, browse, subscribe — write and call refused
ADSread by name or address; no Write, Write Control or Read Write
FINSmemory area read, unit data, unit status
Not a setting. A property of the program. A test on every release sends a write on every protocol and fails unless each is refused.

Who it is for now

A pilot plant whose machines speak a listed protocol.

The agent’s own code holds no write for any protocol; where a library carries one, the agent refuses it — and the statement that proves it ships with every release.

Live on day one
  • The twin, rules, alarms and work orders — the same as every other kind of asset
  • The technician’s and manager’s phones, offline-safe
  • Machines read over the protocols below, read-only
Not yet
  • The Floor: every machine's state now, its shift's OEE and the stops still asking for a reason — not yet verified by an acceptance run
  • Machines as places in the twin — factory, area, line and cell — each with its devices and its state over time; shifts and orders read from the systems that own them — not yet verified by an acceptance run
  • OEE per shift (availability × performance × quality) from each machine's own readings, energy by machine state, a line by its named bottleneck — not yet verified by an acceptance run
  • Stop reasons and scrap counts entered by operators, from the phone or the web, offline — not yet verified by an acceptance run
  • The acceptance run that marks the vertical live

What it reads today

  • MTConnect in development
  • OPC UA companion specifications: machinery, machine tool, packaging (PackML), robotics, plastics in development
  • Sparkplug B live
  • ADS in development
  • FINS in development
  • SLMP in development
  • Modbus TCP live

Each protocol is HOLOIN's own code from the published specification, cited by edition, or an open library listed in the software bill of materials that ships with every release. “Based on” a specification, never “compliant” — and no standard's number appears here until the standard has been bought and verified.

Next

Machines as places. Orders consumed. OEE on its own history.

Machines will become places in the twin, as a room or a vehicle is. Shifts and orders will be read from the systems that own them and never kept here. Availability, performance and quality will be computed from each machine’s own readings, against its own past. Each line moves to the ledger, with its status, when it is in the product.

Tell us what your machines speak

The pilot form asks for the protocols on your floor and the controllers behind them — that is all we need to say whether a pilot is possible today.

a few sentences on what you run and what you want to know

What happens next: we reply to the address you gave. Your details go nowhere else — see Privacy.