Routine work scheduled by the system, not remembered by a person.
Preventive plans by calendar or by usage, each one raising its work order with its checklist when it falls due, so inspections, lubrication and replacements happen on schedule and leave a record when they do.
A plan kept in a spreadsheet is a plan that slips.
When preventive maintenance lives in a spreadsheet or on a wall planner, it depends on someone checking it. Busy weeks are exactly when that stops happening, and the breakdowns that follow are the ones the plan existed to prevent.
Plans that raise their own work.
A plan says what to do, to which equipment, and how often. Everything after that is the software’s job.
Calendar and usage triggers
A plan falls due on a fixed interval or on a usage count such as running hours or cycles, whichever reflects how the equipment actually wears.
Work orders raised when due
When a plan falls due it raises a work order into the same queue as breakdowns, so routine work is planned against everything else the team has to do.
A checklist per plan
The steps of each plan are written once and travel with every work order it raises, so the fifth lubrication is done the same way as the first.
Fixed or floating intervals
The next due date can count from the date the plan was due or from the date the work was actually done, depending on whether the interval is a regulation or a wear pattern.
Usage readings on the asset
Meter readings are recorded against the equipment they belong to, so a usage-based plan knows how far it is from falling due.
Plans you can review
Completed, late and skipped preventive work is visible per plan and per asset, which is how a team sees whether its plans match its breakdowns.
Preventive plans inside VZIAM MES.
In a plant that runs production on VZIAM MES, the maintenance module can schedule preventive work on the running time the MES measures itself. These pages describe how.
- Maintenance in VZIAM MES
Plans by time or by running hours. A plan never raises a second intervention while one is open, and closing it reschedules the plan.
- Machine data acquisition
How running time is read from the PLC over OPC UA, MQTT or a gateway, rather than from a meter someone reads.
- Micro-stop detection
Why short jams are kept out of MTBF in VZIAM MES, so a plan is not shortened by stops that are not failures.
- MES vs CMMS
Which of the two a plant needs, set out question by question.
Frequently asked questions.
Bring the plan you keep today, wherever it lives, and ask the engineers how it would carry across.
Book a callIt depends on how each piece of equipment wears. Calendar intervals suit work driven by time, such as inspections and regulatory checks; usage counts suit wear driven by running, such as lubrication and bearings. A plan can use either.
From meter readings recorded by technicians, or from another system that already counts them. How readings arrive is decided when the project is scoped.
A fixed interval counts from when the work was due, so a late job does not move the next one; it suits regulatory checks. A floating interval counts from when the work was actually done, so the gap between two jobs stays the same; it suits wear.
The equipment whose failure stops production and whose wear is predictable. A plan on equipment that fails at random adds work without preventing anything, and the history in the equipment register is what tells the two apart.
A preventive plan exists to replace failures with scheduled work. Where it does, the time between failures lengthens, which is what MTBF measures; where it does not, the plan is reviewed.
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.