CMMS software for the team that keeps the machines running.
Requests from anyone who sees a problem, work orders with an owner and a due date, preventive plans that raise their own work, the register of every asset with its history, and the parts on the shelf. One application, built for the maintenance team, that runs without an MES.
A maintenance management system, and only that.
VZIAM CMMS is a computerised maintenance management system: a dedicated application in which a maintenance team receives requests, turns them into work orders, schedules preventive maintenance, keeps the register of the equipment it looks after and manages its spare parts, with an app for technicians at the machine. It is a separate product from VZIAM MES and runs on its own.
- 01
Request
Anyone who sees a problem reports it against the equipment.
- 02
Work order
Maintenance triages it, sets a priority and gives it an owner.
- 03
At the machine
The technician works the checklist and records time and parts.
- 04
History
The closed job stays on the asset it was done on.
- 05
Plan
Preventive plans and their intervals are set from that history.
Five parts of one maintenance record.
Each one writes to the same assets, so a part used on a job, a plan that fell due and a request from the line all end up on the history of the machine they concern.
Requests and work orders
Requests raised by anyone who sees a problem, triaged by the maintenance team into work orders with a priority, an owner and a due date, and closed with the work done, the time spent and the parts used.
Request › work order › closed job
Preventive maintenance
Plans by calendar or by usage that raise their work orders when they fall due, so routine work enters the same queue as breakdowns.
Due by calendar or by usage reading
Equipment register
Every asset by site, line and component, with its criticality, its documents and every job done on it.
Site › line › machine › component
Spare parts
The parts held, where each one is stored, what each job used, and a minimum level that says when to reorder.
Booked to the job that used it
Technician app
Assigned work, the asset’s history and documents on a phone or tablet, and the job recorded and closed at the machine.
Phone or tablet, at the machine
Five people, one record of the same work.
The manager plans it, the technician does it, the stores supply it, the methods engineer learns from it, and production reports it. None of them has to ask another what happened.
The backlog, by priority and by age.
Triage the requests that came in, turn the ones that need work into work orders, give each an owner and a due date, and see what is open, what is late and what was closed this week.
Requests and work orders- Open work
- By priority, age and asset
- Preventive due
- This week and next
- Late
- Named, with its owner
The job, at the machine.
The work orders assigned to you on a phone or tablet, with the asset’s documents and its previous jobs, the checklist to work through, and the time, parts and notes recorded before you walk away.
The technician app- Assigned work
- In priority order
- At the machine
- History and documents
- Closing
- Work done, time, parts
The shelf, and what is about to empty it.
Every part with its reference, its location and the equipment it fits. Parts used are booked to the job that used them, and the parts below their minimum are listed so someone decides what to reorder.
Spare parts- Each part
- Reference, location, equipment
- Consumption
- Booked to the work order
- Below minimum
- Listed for reorder
Which machines fail, and how often.
The register ranks assets by criticality, and each one carries every job done on it. That history is what MTBF, MTTR and the choice of preventive interval are worked out from.
The equipment register- Criticality
- Set per asset
- History
- Every job, on its asset
- Indicators
- MTBF · MTTR
Report it once, and see it answered.
Anyone on the line raises a request against the machine with what they saw, without knowing who will take it. Maintenance accepts it as a job or refuses it, so a report does not sit unanswered in someone’s inbox.
How a request becomes a work order- Against
- The machine or component
- With
- What was seen, how urgent
- Then
- Accepted or refused
Plants that run VZIAM MES already have maintenance built in.
VZIAM MES includes a maintenance module on the production record, with requests raised at the machine. It suits a plant that wants maintenance and production in one place. VZIAM CMMS is for a maintenance team that wants an application of its own.
VZIAM MES, the product- Maintenance in VZIAM MES
Requests from the operator’s cockpit with the component, the severity and the running order attached, and procedures with mandatory steps.
- Downtime tracking
How the MES detects a stop from the controller and has it qualified at the machine, before anyone raises a request.
- Machine data acquisition
The running time the MES reads from the PLC, which its preventive plans can fall due on instead of a meter reading.
- MES vs CMMS
Which of the two a plant needs, set out question by question.
Start from the equipment list you already have.
Most teams have a register somewhere, in a spreadsheet or a previous tool. The project starts from it.
- 01
Scoping
We go through how maintenance runs today: the equipment and how deep the register needs to go, how requests arrive, the preventive plans and the stores.
- 02
Set-up and migration
Assets, parts and plans are configured, and what is worth keeping from a spreadsheet or a previous tool is brought across.
- 03
Go-live
The team starts working in VZIAM CMMS, with support from the engineers who set it up.
Frequently asked questions.
Describe how maintenance runs today, and ask the engineers what would change.
Book a callNo. VZIAM CMMS is a separate application for maintenance teams, and it runs on its own. If you also run production on VZIAM MES, its built-in maintenance module may already be enough; the comparison between the two sets out when it is and when it is not.
Maintenance teams that want a specialised tool of their own: the manager planning the work, the technicians carrying it out, the stores holding the parts, and the people on the line who report problems.
The MES module keeps maintenance on the same record as production, with requests raised at the machine’s cockpit and preventive plans that can follow the running time the MES measures. VZIAM CMMS is built around the maintenance organisation itself: its equipment register, its planning, its stores and its technicians, including equipment no MES reads.
Yes. Raising a request does not require knowing who will handle it, so anyone who sees a problem can report it against the machine. The maintenance team then accepts it as a work order or refuses it.
Equipment, parts, plans and history are brought across where they are worth keeping. How much of it, and from what, is decided at scoping.
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.