Schedules built your way
Days, weeks, months, or years, with your own catalog of periods. A single plan can have several schedules at once: the monthly check and the annual one for the same equipment coexist.
Feature
You define how often each thing needs checking, and the system generates the work orders on its own, with the right checklist for each asset and respecting the team's calendar.
Preventive maintenance is work done before something fails, following a plan based on elapsed time or accumulated use, instead of reacting to a breakdown. Replacing a filter every three months, checking a fire safety system every year, or greasing a line every 500 hours are all preventive maintenance. Its value isn't in any single task, but in all of them getting done: a plan running at 60% compliance stops protecting anything and just generates work.
It's almost never about lack of will. It's that the plan lives in one place and the work happens in another.
A preventive plan is a rule: which assets, how often, with what checks, and who does it. The system handles the rest.
Days, weeks, months, or years, with your own catalog of periods. A single plan can have several schedules at once: the monthly check and the annual one for the same equipment coexist.
Work orders are created on their own when the date arrives, with the lead time you decide. Every generation run is logged, so you can always see what created what.
The checklist is resolved in a cascade: first the specific asset's, otherwise its model's, then its subfamily's, and finally its family's. Register a new machine and it inherits what needs to be checked.
Holidays and technician availability are checked before generation. You can decide whether work happens on a holiday, happens anyway, or the order shifts to the working day before or after.
A calendar of upcoming work orders with their date, period, assets, and estimated time. Useful for negotiating shutdowns and knowing how many workdays the plan requires.
It inherits address, system, assets, technician, shift, team, estimated time, cost, and revenue from the plan. The technician doesn't get an empty order someone has to fill in.
Annual preventive plan report, hours per month, and per-asset maintenance log, with a count of interventions by type.
Clients can check their upcoming preventive visits on a calendar or timeline from their own access. No more calls asking when the next check is.
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
A monthly plan on paper turns in practice into interventions every five or six weeks, and by year end two are missing. GMAO Cloud can recalculate the next dates from the actual closing of the last work order instead of the theoretical one, so the interval between checks is the one you asked for, not the one that happened. It's a configuration choice, because not every plan wants that: an inspection with a legal due date follows the calendar, no matter what.
The technician receives the preventive work order in the app with the asset's history and the checks they need to do. The technician app works without coverage: it logs what was done, attaches photos, collects the signature, and syncs once the connection comes back. On preventive work orders the app requires every checklist to be closed before finishing, and flags any anomalies found, because a preventive check without the checks actually done proves nothing.
Start with what the manufacturer says and treat it as a starting point, not a final truth. Manual recommendations are written for average use under average conditions, and your installation is rarely average: the same equipment in a dusty environment, running more hours a day, or with frequent start-ups behaves differently. After a year of records you can adjust it with your own judgment.
Review it piece by piece instead of assuming it's all correct. Almost every plant has checklists that have been run for years without anyone remembering where they came from, and some of them no longer add anything. Telling apart what's a regulatory obligation, what's a manufacturer recommendation, and what's just habit is an uncomfortable exercise that usually frees up a fair amount of capacity.
They generate on their own when the date arrives, if the plan is active and set to auto-generate. There's also a button to force generation of maintenance tasks whose date has already arrived, in case you need to run it early.
Yes. A maintenance plan can have several periods at once, which is common when the same equipment needs a frequent check and a more thorough annual one.
It's checked before generation. You can choose not to run the service on a holiday, run it anyway, or reschedule it to the working day before or after. Technician availability is taken into account when the HR module is active.
No. It can be linked to the model, the subfamily, or the asset family, and each piece of equipment inherits the one that applies. Assigning it to a specific machine is only needed when that machine is an exception.
Yes. The estimated time for each plan feeds the forecasted work order calculation and the annual preventive plan report, which is what lets you anticipate workload and negotiate shutdowns.
In the demo we'll register a couple of your real preventive plans and see what work orders come out, and when.
Accessibility
Saved in this browser. Light or dark theme is set from the footer.