We write software that has to agree with a machine.
Most business software can be wrong quietly for a month. Ours cannot: a controller changed state at a particular instant, and either the record says so or it does not. That constraint shapes everything below.
Two products, and the engineering around them.
VZIAM MES is manufacturing execution in the narrow sense: reading what the equipment did, asking a person only what the equipment cannot know, and turning the two into a figure somebody is willing to act on. VZIAM CMMS is a dedicated maintenance application, for teams that want a tool of their own. The services connect both to what a plant already runs.
VZIAM MES
Machine data from the controllers, the terminal at the line, stops and rejects with their reasons, OEE computed on the server to AFNOR NF E60-182, and one record per work order and lot.
VZIAM CMMS
Work orders and requests, preventive plans, the equipment register, spare parts and a mobile app for technicians, in an application of its own.
Services
Machine connections, ERP integration and software for what no product covers, from an assessment and a pilot on one line to support after go-live.
Three commitments, in the order they matter.
None of these are aspirations. Each one has cost us something on a project, which is the only evidence that a principle is real.
- 01
The machine is the source, and the operator is the authority
Durations come from the controller because a person cannot time a stop they are busy resolving. Causes come from the operator because no controller knows why. Systems that invert this (asking people for durations and inferring causes) produce data that nobody on the floor recognises.
How a stop is timed and qualified - 02
Old equipment is the normal case
A plant is a thirty-year accumulation of decisions, and the press that matters most is rarely the one with the newest interface. A machine with no fieldbus is a normal integration problem rather than an exclusion, because a model that skips the difficult third of the shop is not a model of the shop.
How older machines are read - 03
We are the people who have to live with it
The person who writes an integration is the person who gets called when it stops. That arrangement is slower to staff, and it removes the incentive to ship something that demonstrates well and maintains badly.
How a project runs
How we work with a plant.
Four steps, the same on every project. The pilot runs on one line with real signals before any commitment to a rollout, and what we build stays ours to support.
Our services- 01
Assess
We walk the floor, map the machines and the data that already exists, and agree what “done” means before anything is built.
- 02
Pilot
One line, one machine, real signals, in weeks. You check your own data before you commit to a rollout.
- 03
Build
Delivered in increments against the agreed scope, on your network, with your team in the loop.
- 04
Run
Support, monitoring and changes after go-live. What we built stays ours to answer for.
What this site shows, and what it leaves out.
No logo wall, no client names and no percentage without a plant behind it. What is here instead is meant to be checked, and you will notice the absences.
Engagements without names
The services page describes three engagements by sector and by what changed in kind. The clients’ names are withheld under NDA, and no logo implies one on their behalf.
Three engagementsNo figure without a plant
A result needs a plant, a period and a method behind it. Where we cannot give all three, the sentence is written without a number rather than with a plausible one.
Things you can test
Specifications you can check against your own equipment, an OEE definition stated in full including what it excludes, and comparisons that concede where the alternative is better.
The OEE definition, in full
Checkable things.
- Discipline
- Industrial software & systems integration
- Products
- VZIAM MES, VZIAM CMMS
- Based in
- France
- Working languages
- English, French
- Runs
- Docker, on the plant’s network
- OEE standard implemented
- AFNOR NF E60-182
- Native protocols
- OPC UA, MQTT, HTTP push
- Through a gateway
- Modbus, Siemens S7, proprietary
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.