Maintenance inside the MES, or a CMMS of its own.
We make both, so this is not an argument for one of them. VZIAM MES includes maintenance on the same record as production; VZIAM CMMS is a dedicated application for maintenance teams. Which one a plant needs depends on whose record maintenance belongs on.
Maintenance in VZIAM MES fits when
- Production and maintenance should share one record, on the lines the MES already runs.
- Requests are raised from the line, with the machine and the running order attached.
- Preventive plans should follow the run hours the machines report.
VZIAM CMMS fits when
- The maintenance team wants a specialised tool built around its own organisation.
- It looks after equipment no MES reads, as well as the production lines.
- There is no MES to build on.
Both are ours, so the choice is made with the plant at the assessment, from who owns maintenance and what its record has to hold.
The same six questions, asked of both.
Every row describes what each one does. Neither column is scored, and both of them are ours.
| Maintenance in VZIAM MES | VZIAM CMMS | |
|---|---|---|
| What it records | Maintenance on the same record as production: the machine, the order that was running, the stop a request came from. | The maintenance organisation’s own record: equipment, work orders, preventive plans, parts and history. |
| Who uses it | Operators raising requests from the line, and the maintenance team handling them. | The maintenance team first (planners, technicians and stores), with requests from anyone. |
| Where a request starts | At the line terminal, carrying the production context the MES already holds. | From anyone who sees a problem, at a workstation or in the mobile app. |
| What drives preventive plans | Run hours measured from the machine. | Calendar intervals or usage counts. |
| What it covers | The machines the MES reads and the lines it runs. | Whatever the maintenance team looks after, whether or not an MES reads it. |
| When a plant needs it | When production and maintenance should share one record, and the MES already runs the lines. | When maintenance wants a specialised tool of its own, or there is no MES to build on. |
Two ways to run maintenance, for two different owners.
The question is not which one is better. It is who owns the maintenance record, and what it has to hold.
An MES with maintenance built in
For a plant that wants production and maintenance on one record. Requests are raised from the line with the machine and the running order attached, and preventive plans can follow the run hours the MES measures.
A dedicated CMMS
For a maintenance organisation that wants a specialised tool of its own: its equipment register, its planning, its stores and its technicians, whether or not production runs on an MES.
What decides it
Who raises and owns the work, what the record has to hold beyond the machines production uses, and whether the maintenance team looks after more than the lines an MES would cover.
Frequently asked questions.
It includes maintenance: requests from the line, interventions, preventive plans, spare parts, and MTBF and MTTR. A maintenance team that wants a specialised tool built around its own organisation is who VZIAM CMMS is for.
No. VZIAM CMMS is a separate application, and it runs on its own.
The choice is made with the plant, at the assessment, from who owns maintenance and what it has to hold. If that changes, what moves across is decided when the new project is scoped.
The other comparisons.
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.