Bespoke plant software, without paying for the foundations twice.
When a plant needs something no product does, we build it on the acquisition, the operator cockpit, the TV displays and the admin portal that VZIAM MES already runs on, so the project pays for what is specific to your plant.
Read directly, or through a gateway on the line.
Maintained with the product.
- Acquisition
- Operator cockpit and TV displays
- Admin portal, roles and rights
Screens, rules and exchanges specific to the plant.
Integrated with, not replaced.
When no product fits, a spreadsheet fills the gap.
Every plant has a process no package describes. What fills the gap is rarely nothing: it is a workbook, a macro, or an application somebody wrote and then left.
The spreadsheet that became a system
A workbook that started as a tally now decides what runs next. Nobody owns it, two copies disagree, and it breaks the week its author is away.
Software nobody can change
An application built once, for one line, by someone no longer at the plant. It works until the line changes, and then it is either rewritten or worked around.
Foundations paid for twice
A bespoke project that starts from nothing pays again for machine connections, operator screens, user rights and an admin interface before it reaches the part that is specific to the plant.
Start from what exists, build what is yours, and keep it running.
Projects start from the parts of VZIAM MES that are already built and maintained, and add what is specific to the plant. Where a plant already runs something that works, we integrate with it rather than replace it.
- 01
Start from VZIAM MES
Acquisition, the operator cockpit, the TV displays and the admin portal already exist and are maintained with the product. A custom project starts from them, served from your own network like the rest of VZIAM MES.
VZIAM MES - 02
Assess and pilot before the build
We walk the floor, agree what done means, and pilot on one line with real signals before the rest is built. You check the result on your own data before committing to more.
How a project runs - 03
Build what is specific to the plant
Delivered in increments against the agreed scope, on your network, with your team in the loop.
- 04
Keep it running
Support, monitoring and changes after go-live. What we built stays ours to answer for.
What a project starts from.
Four parts of VZIAM MES, already built and maintained, each with its own page. A project adds to them rather than rebuilding them.
The machines are already readable.
Controllers that speak OPC UA or MQTT, or post over HTTP, connect directly; Modbus, Siemens S7 and proprietary controllers connect through a gateway on the line. Each machine’s signals are mapped once, and counters are never reset.
Machine data acquisition- Native
- OPC UA, MQTT, HTTP push
- Through a gateway
- Modbus, S7, proprietary
- Counters
- Never reset
A screen at the machine, already in use.
The touch cockpit runs the shift from one screen: orders, stops in three taps, rejects on a numpad, checks and maintenance calls. It keeps working when the Wi-Fi does not, and computes nothing itself.
The operator terminal- Stops
- Qualified in three taps
- Rejects
- On a numpad, with a reason
- Wi-Fi outage
- Queued, not lost
The line’s state, on any screen.
Any browser on a smart TV or a small box shows each line’s state, OEE and cadence against nominal, with alerts raised by type and severity. A new display is a page, not a hardware project.
Andon and TV displays- Hardware
- Any browser
- Per line
- State, OEE, cadence
- Alerts
- Type and severity
Users, rights and the plant’s structure.
Sites, workshops, lines and machines, articles and their nominal rates, users and their roles, all administered in the browser. The server runs as Docker on the plant’s own network.
Where VZIAM MES runs- Structure
- Site, workshop, line, machine
- Access
- Roles and rights
- Runs
- Docker, on your network
What every project inherits.
- Deployment
- Docker, on the plant’s network
- Machine protocols
- OPC UA, MQTT, HTTP push
- Through a gateway
- Modbus, S7, proprietary
- Plant structure
- Site, workshop, line, machine
- ERP exchange
- REST API, JSON, CSV
- Reports
- CSV for Excel, PDF
- Corrections
- Audited, original kept
Frequently asked questions.
Describe the process no product covers, and ask the engineers what already exists for it.
Book a callThat is where it starts, because the acquisition, the terminal, the displays and the admin portal are already built. What the plant already runs and trusts stays, and the project integrates with it rather than replacing it.
With an assessment on the floor and a pilot on one line with real signals, as every VZIAM project does. The scope of the build is agreed after the pilot, against what it showed.
We do. Support, monitoring and changes after go-live are part of the engagement, and the person who wrote an integration is the person who gets called when it stops.
Where VZIAM MES runs: as Docker on the plant’s own network, served to the browsers and terminals on the floor. Nothing a project adds needs to leave the plant to work.
That is one of the most common starting points. The workbook’s logic is written down at the assessment, its data is read from the machines and the orders rather than typed in, and the result runs on the plant’s network with the same users and rights as the rest of VZIAM MES.
The rest of what we do.
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.