Features
Maintenance planning
This page is about the machinery: how a template becomes a plan, how a plan becomes a task on a real date, what happens to the schedule when the work slips, and why the procedure version travels with the result. If your question is how to get a preventive programme running at all, the Solutions page is the better starting point.
- Biomedical engineering
- Hospital operations
- Field technicians
What is maintenance planning?
Definition
Maintenance planning
Maintenance planning is the definition of what should be done to a class of equipment and how often, its application to specific devices as plans, and the automatic generation of dated tasks from those plans far enough ahead that the work can be scheduled rather than merely noticed.
Three separable pieces, and most tools blur them. A template is the procedure: the steps, the checks, the readings to take. A plan applies that template to a device with a recurrence. A task is the actual dated thing a technician does. Blurring them is why so many systems cannot answer what should have happened last March without also telling you what did.
Every interval in that sentence comes from you. Rydya does not know how often your infusion pumps need servicing, and any software that claims to is telling you about a manufacturer it has never met.
How a plan becomes work on a date
Template, then plan, then generated tasks ahead of time, then completion recorded against the version that was used.
Why maintenance schedules fall apart
Because the schedule is treated as a promise rather than a queue, and the first week it slips it stops describing reality and everybody quietly stops trusting it.
A preventive programme fails in a specific and recognisable way. It works for a quarter. Then a ward will not release a device, a technician is off, a part is late. The task goes overdue. Nothing catches fire, because that is exactly the nature of preventive work: the cost of skipping it is deferred and invisible. The next month a few more slip. Within a year the schedule is a list of red items nobody reads, and the department has learned that overdue means nothing.
The second failure is generation timing. A task that appears on the day it is due is not a plan, it is a notification. Nobody can arrange ward access, a loan device or a technician's day at zero notice, so the work slips on arrival and the schedule was fictional from the start.
The third is the silent template edit. Someone improves the procedure, and now last year's completed tasks appear to have been done against a procedure that did not exist when they were done. The history looks tidy and is quietly wrong, which is worse than looking messy and being right.
How Rydya generates and holds a schedule
Generate early, keep the version with the result, surface slippage as work rather than as a colour, and never let the plan rewrite what happened.
- 1
A template captures the procedure
The steps, checks and readings to capture. It is versioned, so improving it is normal rather than dangerous. What it says today and what it said when a job was done in the past are both retrievable.
- 2
A plan applies it to devices with your recurrence
You configure the interval, because it is a decision about your equipment, your manufacturer guidance and your risk appetite. The software holds the rule you set; it never supplies one.
- 3
Tasks generate ahead of the due date
Far enough ahead to be arranged: ward access negotiated, technician assigned, parts reserved. A schedule you can only react to is not a schedule.
- 4
Completion records the version that was used
The result carries the template version, so a task done last year stays interpretable this year. Improving the procedure never retro-edits the past.
- 5
Slippage becomes visible work
Due, overdue and missed are evaluated by a worker and raised as attention rather than left as a colour on a list. The point is that somebody has to decide, not that the row turns red.
What the planner will not decide for you
The refusals are narrow and deliberate. Each one is a place where invented confidence would be dangerous.
It will not supply an interval
How often a device needs attention depends on the manufacturer, the device, its duty cycle and your risk appetite. Rydya holds the interval you configure and never invents one, because a default here is a clinical claim dressed as a convenience.
It will not decide what the procedure contains
The steps, the checks and the acceptable readings are yours. The template stores them, versions them and carries them to the technician. It does not know what a pass looks like until you tell it.
It will not close a task on a technician's say-so where a gate applies
Where the work touches return to service, the required tests and an authorised clearance still apply. Preventive work is not a way around a safety gate.
It will not quietly rewrite history
Template versions, completed results and the audit trail are append-only. A schedule that can retro-edit what happened is a schedule that cannot be audited.
Who should own the plan, and when to build it
The department accountable for the equipment, starting with the devices where failure hurts most rather than with the whole estate.
The instinct is to plan everything at once, which produces a programme so large it is abandoned in month three. The alternative that works is unglamorous: start with the equipment where an unplanned failure is genuinely expensive or genuinely unsafe, get that running properly, and widen once the rhythm exists. A small programme that runs beats a comprehensive one that does not.
Ownership has to be real. A plan generated by software and owned by nobody produces overdue tasks and nothing else. The value shows up when somebody is accountable for the slippage being a decision, rather than a fact that accumulated while everyone was busy.
Questions
Does Rydya tell us how often to service our equipment?
No, and that is deliberate rather than a gap. Intervals depend on the manufacturer, the device, its duty cycle and your risk appetite, none of which the software knows. Rydya holds the interval you configure, generates the work from it and shows you when it slips. Any tool supplying a default here is making a clinical claim about equipment it has never seen.
How far ahead are tasks generated?
Far enough ahead to be arranged rather than reacted to, and you configure it. A task that appears on the day it is due is a notification, not a plan: nobody can negotiate ward access, assign a technician and reserve parts at zero notice, so the work slips on arrival.
What happens when we improve a procedure?
The template is versioned, so improvement is normal rather than dangerous. New work uses the new version, and every completed task keeps the version it was actually done against. A system that edits the procedure in place makes last year's records appear to follow a procedure that did not exist yet, which looks tidy and is quietly wrong.
What happens to work that goes overdue?
It is evaluated by a worker and raised as attention that needs a decision, rather than left as a red row on a list nobody reads. Preventive work slips for real reasons: ward access, staffing, parts. The aim is that slipping becomes a choice somebody made rather than something that accumulated quietly.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us