Four parts, one server, all on your network.
Acquisition, the operator cockpit, the TV displays and the admin portal are served from one set of Docker containers on a server inside your network: the application, PostgreSQL, Redis, an MQTT broker, a reverse proxy and a nightly backup.
States and counters, read on a cycle or pushed
Browsers on tablets and screens, updated by the server
Docker containers
- Application behind a reverse proxy
- PostgreSQL and Redis
- MQTT broker and nightly backup
Orders in, quantities and times back
Modelling, reports, CSV export
Built to run where the machines are.
The server sits on the same network as the controllers, so a lost internet link does not stop the shop floor, and production data stays on hardware you control. Engagements reuse the same platform, so a bespoke integration does not mean paying for the foundations twice.
Four rules the platform holds to.
They are why the same plant reads the same way on every screen, and why a restore brings back what it should.
- 01
Screens display; the server decides.
Every figure is computed on the server. The cockpit, the TV and the portal render what they are sent, so no screen can publish a number of its own.
- 02
One machine, one line, one workshop, one site.
The plant is modelled as a strict tree. A duplicate machine code is refused, and deactivating a line hides its machines from the cockpits without deleting their history.
- 03
Each role sees its own scope.
Operator, supervisor, technical administrator and TV display, each with its own permissions. Deactivating an account ends its sessions at once.
- 04
A backup is more than the database.
The nightly backup keeps 30 days, and the documents, the retention archives and the scheduled reports go with the database, each in its own file, so a restore brings back the files as well as the rows that name them.
Each part, and where it is described.
Acquisition
Reads OPC UA servers, subscribes to MQTT topics and accepts HTTP push, then works out states and counts from what arrives. Controllers that speak none of these are read through a gateway on the line.
Operator cockpit
The screen at the machine: the current order, the reason a machine stopped, the parts that did not pass. It computes nothing, and it keeps working through a Wi-Fi outage.
TV displays
A browser on a smart TV or a small box, rotating through each line’s state, OEE and cadence against nominal, pushed by the server as it changes.
Admin portal
The browser application where the plant is modelled (structure, articles and their nominal rates, reason trees, shifts, signal mapping, users) and where its history is analysed and reported.
Interfaces
A REST API with service tokens for integrations, a mapped JSON or CSV exchange with the ERP, and a CSV export of the timeline for BI tools.
What the platform commits to.
- Deployment
- Docker Compose, on a server on your network
- Services
- Application · PostgreSQL 16 · Redis · MQTT broker · reverse proxy
- Backups
- Nightly, 30 days kept
- Access
- Accounts, four roles, scoped by site
- Live updates
- Server-sent events to cockpits and TVs
- Interfaces
- REST API · JSON · CSV
- Structure
- Site › workshop › line › machine
Frequently asked questions.
Bring your network and security requirements, and ask the engineers who install it.
Book a callOn a server on your network, as Docker containers: the application behind a reverse proxy, PostgreSQL, Redis and an MQTT broker for the machine signals. The database is backed up nightly, with 30 days kept.
Not to run the shop floor. Machines, cockpits, TV displays and the portal all talk to the server on your network.
Four: operator, for the terminal at the machine; supervisor, for orders, reasons and corrections; technical administrator, for acquisition, structure and accounts; and a read-only role for TV displays.
Yes. A REST API with service tokens serves integrations, and the timeline exports as CSV for BI tools, with its segments, a KPI summary and the counter diagnostics.
The database, and with it the documents and attachments, the retention archives and the scheduled reports, each kept in its own file of the nightly backup.
Plan the change before it reaches the line.
Request a demo and an engineer looks at how your production runs today, shows how the software would fit around it, and where a pilot on one line would start.
01Pick a time
Choose a slot in the calendar, and note what you make and what reads your machines today.
02Screen shared with an engineer
A video call with someone who builds the software, in English or French.
03What would connect
For each machine, its path: native (OPC UA, MQTT or HTTP push), through a gateway, or nothing to build.