Every machine you maintain, with its history attached.
A register of the equipment the maintenance team looks after, organised by site, line and component, with the criticality, the documents, the parts and the full history of every job done on each item.
Maintenance without a register is maintenance from memory.
When nobody can say in one place which machines the team maintains, where they are and what was done to them, every intervention starts by finding out. The history that would explain a recurring failure is scattered across jobs nobody can link back to the machine.
One register, and everything hangs off it.
Work orders, plans, parts and documents all point at an asset, which is what makes the register worth keeping up to date.
Organised by location
Equipment arranged by site, building, line and component, so a work order lands on the exact part that failed and rolls up to everything above it.
One record per asset
Make, model, serial number and date in service, kept on the asset rather than in a filing cabinet or the memory of whoever installed it.
Criticality
Each asset ranked by what its failure costs, so the team knows which breakdown to answer first and which equipment to put on a preventive plan.
Documents on the asset
Manuals, drawings and procedures attached to the equipment they belong to, so a technician finds them from the machine rather than from a shared drive.
The parts that fit it
Spare parts linked to the equipment they fit, so the right one can be found, and its stock checked, from the machine.
The history of every job
Every work order, preventive and corrective, stays on the asset it was carried out on. That history is what failure analysis and indicators such as MTBF and MTTR are built from.
The same machines, inside VZIAM MES.
VZIAM MES models the plant for production first, and its maintenance module breaks each machine down from there. These pages describe how.
- Maintenance in VZIAM MES
Machines broken down into sub-assemblies and components, each with its criticality and status, and MTBF and MTTR from the same stops OEE uses.
- The architecture
Site, workshop, line and machine as the MES structures them, and where the server runs.
- Downtime tracking
Every stop of a machine, timed from the controller and qualified at the line: the raw material of its reliability figures.
- MES vs CMMS
Which of the two a plant needs, set out question by question.
Frequently asked questions.
Send the engineers the equipment list you have today, in whatever form, and ask how it would carry across.
Book a callDetailed enough that a work order lands on the component that failed, and no deeper. Most teams start with lines and machines and add components where failures concentrate.
A ranking of each asset by the consequence of its failure: safety, lost production, quality and repair cost. It decides which breakdown is answered first and which equipment earns a preventive plan.
Yes. Manuals, drawings and procedures are attached to the asset they belong to, so a technician finds them from the machine rather than from a shared drive.
An existing register is usually the starting point, whether it is a spreadsheet or a previous CMMS. Bringing it across is part of scoping the project.
Mean time between failures and mean time to repair per asset, from the corrective jobs recorded on it, and the share of work that was preventive. They are only as good as the history, which is why every job is closed on its asset.
The rest of VZIAM CMMS.
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.