From a request at the machine to a closed intervention.
The operator raises a request from the cockpit with the machine, the component and the severity attached. Maintenance accepts or refuses it, plans the intervention, follows its procedure, books the parts used and closes it with a report, on the record production already runs on.
The context travels with the request.
A breakdown reported by phone arrives as a machine name and an impression. In VZIAM MES the request already carries the machine, the component, the order that was running and who raised it, and preventive plans can fall due on the running time the MES measures from the controller. Maintenance teams that want an application of their own have VZIAM CMMS.
Five rules from request to closure.
They keep a request, the work done and the stock used tied to each other, which is what makes the history worth reading later.
- 01
A refusal needs a reason.
A request is new, accepted or refused. Refusing it requires a written reason; accepting it creates the intervention that carries the work.
- 02
The severity felt is not the diagnosis.
The operator says how serious it seems: low, normal, high or blocking. That is kept as reported, and the diagnosis belongs to the intervention.
- 03
Mandatory steps are checked at closure.
An intervention that follows a procedure cannot be closed until its mandatory steps are done.
- 04
A part used is a part out of stock.
Booking a part to an intervention decrements the stock in the same transaction, at the unit price of the movement. Stock is never allowed to go negative.
- 05
A preventive plan never doubles up.
A plan does not generate a second intervention while one is still open, and closing the intervention reschedules the plan from the work actually done.
The maintenance module, part by part.
Requests from the cockpit
Raised at the machine with the component and the severity, alongside the order that was running. The request outlives the order, so closing production does not close the problem.
Interventions, planned to closed
Preventive, corrective or improvement; assigned to a person, a team or both; planned, in progress, done or cancelled, with start, end and report kept.
Preventive plans by time or usage
A plan falls due on the calendar or on running time, which the MES measures from the controller rather than from a meter someone reads.
Components and procedures
Machines broken down into sub-assemblies and components, each with its criticality and status; procedures with mandatory steps; manuals attached through the document library.
Spare parts and stock thresholds
A catalogue with stock, minimum and location; consumption booked to the intervention; and a list of parts below their minimum, so someone can decide what to reorder.
MTBF and MTTR from the OEE engine
Reliability figures per machine come from the same stops OEE does, so maintenance and production argue about causes rather than about whose numbers are right. Micro-stops are left out.
What the module commits to.
- Request states
- New · accepted · refused
- Severity
- Low · normal · high · blocking
- Intervention types
- Preventive · corrective · improvement
- Plan triggers
- Time · usage
- Stock
- Decremented with the consumption, never negative
- Indicators
- MTBF · MTTR, from the OEE engine
Frequently asked questions.
Describe how a breakdown reaches your technicians today, and ask the engineers what would change.
Book a callIt includes it: requests from the line, interventions, preventive plans by time or usage, procedures, spare parts, MTBF and MTTR. A maintenance team that wants a dedicated application of its own can use VZIAM CMMS; the comparison page sets out which fits.
Yes. A plan can fall due on usage, measured from the running time the MES records from the controller, as well as on the calendar.
No. Closing it records the work done and reschedules any preventive plan. Returning the machine to production follows your site’s own procedure, and the cockpit does not switch over on its own.
No. Parts below their minimum stock are listed so someone can decide what to reorder; purchasing stays in your ERP.
From the OEE engine’s own stops for that machine, so the maintenance view and the production view use the same figures. Micro-stops are left out, so short jams do not read as failures.
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.