Maintenance planning
Maintenance planning for your vending fleet
“Descale every coffee machine every three months.” Stored once as a rule, Vecodesk creates the ticket when the maintenance falls due and resets the clock as soon as the visit is closed.
- Intervals from days to years
- The ticket appears automatically
- Records without re-entry
Preventive maintenance
Maintenance that puts itself on the list
The maintenance status sits on the machine
The maintenance record is the clock. It comes from closed tickets, manual entries or imported history, and it sits on the machine's page.
Due maintenance becomes a ticket
When maintenance falls due, Vecodesk creates the ticket — in the same queue as a fault, with your priority and your category.
Every ticket explains itself
Every automatically created ticket carries an immutable explanation: which rule fired, for which machine, due since when.
How it works
From the rule to the record
A maintenance plan is three pieces of information: what, how often, for whom.
- 1
The rule: type, interval, scope
You name the maintenance types — filter change, descaling, safety check — plus an interval and what the clock runs on. Every plan carries a ticket template.
- Intervals in days, weeks, months or years
- Clock per machine, per address or per customer
- Scope narrowed by customers, machines, machine types and tags
- 2
The run: every morning, before the day starts
Once a day Vecodesk checks what is due and creates the tickets the ordinary way, recognizable by the source “automation”.
- 3
The record: written on closing
When a ticket carrying a maintenance type is closed, Vecodesk writes the record itself and restarts the interval.
In detail
Maintenance planning that fits the fleet
Rules per machine type
Coffee machines differently from water dispensers: scope narrows to machine types and tags.
Whole sites at once
The clock runs per machine, per address or per customer — for rounds where one visit serves many machines.
One list for everything
Maintenance and fault tickets sit side by side: same views, same dispatch, same deadlines.
FAQ
Questions about maintenance planning
Do maintenance tickets land in the same list as faults?
Yes. They run the ordinary path: dispatch, accept, on site, report, close. They are recognizable by the source “automation” and by the explanation attached.
Can we record past maintenance?
Yes. Records come from closed tickets, but can also be entered by hand or imported from your previous system. That is the usual path when switching.
How finely can the scope be cut?
By customers, individual machines, machine types and tags, in combination. “Every coffee machine at customers tagged full-service, every three months” is one rule.
Related
Put your maintenance intervals into one system.
In the demo we build one of your rules, with your machine types and your interval.