Solutions
Downtime management
Downtime is the argument biomedical engineering always loses, because it is universally felt and almost never measured. The fix is not rhetoric; it is a duration and a defensible rate.
- Executive and finance
- Biomedical engineering
- Hospital operations
What is equipment downtime management?
Definition
Downtime management
Downtime management is the practice of recording when equipment stopped being available for its intended use, when it became available again, why, and what the interval cost.
Three questions surface at implementation. When did the device stop being available, rather than when somebody reported it? Does waiting for a part count like waiting for a decision? What is an hour of this device being unavailable worth?
Rydya answers the first two by measuring rather than asking, and refuses to answer the third on your behalf. The rate comes from you.
Why downtime is invisible
Because it requires a record spanning fault, work and return to service, and most organisations keep those in three systems, or none.
Downtime is an interval with two ends owned by different people: the start is known to a nurse at 3am, the end to an engineer signing off a safety test. If those facts live in different systems, the interval does not exist as data and cannot be summed, compared or costed.
What organisations have instead is a memory of the worst incidents, a sample selected for drama rather than cost. The scanner everyone remembers may not be the asset costing most; the pump quietly out for two days every six weeks very often is.
Without measured downtime you cannot build a replacement case, prioritise by impact, or answer the finance director who asks what the department prevents. You are arguing from anecdote against a spreadsheet.
How Rydya measures and prices downtime
The duration is measured from the record you already produce; the rate is configured by you. Where the rate is missing, Rydya says so rather than guessing.
- 1
The interval comes from the work, not a survey
Downtime events are anchored to the fault at one end and the return-to-service gate at the other: real timestamps, not recollections. A background sweep watches for open, stale and unclosed downtime.
- 2
You say what the asset earns
Tick that an asset is revenue generating and enter what it makes per day, week or month; every change is audited. If an asset does not earn revenue directly, leave it unset.
- 3
One setting converts it
A single organisation-level setting, the hours a day equipment is normally in use, turns a per-month figure into an hourly rate applied consistently.
- 4
The cost appears while it still matters
A fault on a valued asset shows an estimated cost immediately. A number that arrives while the equipment is still down can change what happens next.
- 5
The estimate never becomes the actual by accident
Estimated and confirmed impact are separate records, never merged. Original amounts and currency are immutable; conversions carry their rate, source and timestamp rather than overwriting the source.
What the number is for
Not for a dashboard. For four arguments biomedical engineering currently cannot win.
The replacement case
Four failures with a measured cost attached to each interval is a business case. Four remembered failures is a complaint.
The planned-maintenance negotiation
When a refused planned window becomes an unplanned failure with a measured cost, the next conversation starts differently. Rydya does not win that argument; it makes it available.
Prioritising by impact rather than by volume
The loudest asset and the most expensive asset are rarely the same one. Measured downtime lets a department spend its finite attention on the second.
Answering the finance director
A cost centre that prevents costs is the hardest thing in an organisation to fund. A measured downtime figure is the only honest way to make prevention visible.
Estimated and confirmed impact are different things
Conflating them is the fastest way to lose a finance team's trust, so Rydya keeps them structurally separate.
| Aspect | Estimated impact | Confirmed impact |
|---|---|---|
| Exists | While the equipment is down | After the facts are known |
| Built from | Your configured rate and the measured duration | Actual recorded costs and finance-approved figures |
| Used for | Deciding what to do next, prioritising, escalating | Accounts, reporting, the replacement case |
| Can it change? | Yes, as the duration grows | It is a record; corrections are audited amendments |
| If unconfigured | Reported as "not configured", never guessed | Simply does not exist yet |
How the two financial records differ in purpose, timing and authority
Money is never invented
If you have not set what an asset earns, and no finance-approved rate applies, Rydya says the downtime cost is not configured. It will not print a number it cannot defend: an invented figure is worse than no figure, because somebody will make a decision with it. A finance-approved valuation always takes precedence over the per-asset figure.
Who should set the rate, and when
Whoever can edit the asset, at the moment they add it. Valuation deferred to a committee never happens.
Gating valuation behind a finance approval creates a queue, the queue creates waiting, and the exercise stays permanently just about to start. It is why most organisations have no valuations at all.
Rydya takes the other position deliberately: anyone who can add an asset may enter what it earns, audited. A figure entered by a department head and visible to finance beats a perfect figure that does not exist. A finance-approved valuation, once configured, takes precedence automatically.
The right moment is registration: one field then; a project later, and the project will lose to something urgent.
Questions
How does Rydya calculate the cost of downtime?
From figures you configure and a duration it measures. You set what a revenue-generating asset earns per day, week or month, plus one setting for the hours a day equipment is normally in use; that produces an hourly rate applied to the measured interval. If neither that nor a finance-approved valuation exists, the cost is reported as not configured, never estimated.
What if an asset does not generate revenue directly?
Leave it unset. Much critical equipment earns no money directly, and a notional figure would poison every number downstream. Rydya still measures the interval; it just attaches no currency figure it cannot defend.
Who is allowed to set what an asset earns?
Anyone who can edit the asset, and every change is audited. A single-department valuation queue is why most organisations have no valuations at all. A finance-approved valuation always takes precedence over the simple per-asset figure.
Can we trust the downtime duration?
It is as good as both ends of the interval: a QR-scan fault report at the start, close to the real moment, and the return-to-service gate at the end. A background sweep watches for open, stale and unclosed downtime.
Does the estimate turn into the actual cost automatically?
No. Estimated and confirmed impact are separate records and never merged. Original amounts and currency are immutable; conversions carry their rate, source and timestamp. That separation is what lets the number survive a finance review.
Keep reading
Hospital equipment maintenance
The loop that produces both ends of the downtime interval.
Preventive maintenance
The planned work whose value downtime cost is what finally proves.
Fault reporting
Where the interval starts, and why a QR scan beats a phone call.
Diagnostic and imaging centres
The segment where an hour of downtime has the clearest price.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us