Features
Financial impact
Every claim a maintenance department makes about money is eventually checked by someone whose job is checking money. This page is about the rules that decide whether that goes well, and they are unglamorous, restrictive, and the reason the figures hold up.
- Executive and finance
- Biomedical engineering
- Hospital operations
What is financial impact tracking?
Definition
Financial impact
Financial impact tracking is the accumulation of what equipment actually costs: the parts, the labour, the vendor invoices and the priced downtime, each recorded against the device with its original amount and currency preserved, so that a figure can be traced to the records that produced it.
The test any of this has to pass is not whether a dashboard looks convincing. It is whether the number survives a finance director asking where it came from, in a meeting, without notice. That is a harder test than producing a figure, and it is the test these rules exist to pass.
Rydya is deliberately conservative here. It will show fewer numbers than some tools and it will refuse to produce some you might want. Both behaviours are deliberate, and both follow from the rules described below.
Why maintenance cost figures get dismissed
Because one indefensible number in a pack discredits the defensible ones, and finance teams are professionally trained to find it.
The pattern is worth recognising because it happens to good departments with true arguments. A business case goes up. It contains a downtime cost derived from an industry benchmark, because nobody had configured a real one. The finance director asks which hospital that benchmark is from. Nobody knows. Every other figure in the pack, including the ones built from real invoices, is now suspect, and the case fails on the strength of its weakest number rather than its strongest.
The second pattern is the silent revaluation. A figure was quoted in one currency last year and the system now displays it converted at today's rate, or worse, overwrote the original at some point. The number has changed and nothing recorded why. In a regulated environment this is not an inconvenience, it is the end of the conversation.
The third is the merged total. Estimated impact and confirmed cost added together into one impressive figure. It is defensible as neither: too soft to be an accounting number, too precise to be an estimate. It reads as authoritative, which is exactly what makes it dangerous.
The rules the money follows
Five, and they are enforced at the data model rather than left to a report author's discretion.
The original amount and currency are immutable
What was recorded is what stays recorded. A figure quoted six months ago reproduces exactly today, because nothing has been helpfully updated underneath it.
Conversions live separately
With their rate id, source and timestamp. A converted figure is always traceable to the rate that produced it, so "why is this different from last quarter" has an answer rather than a theory.
Estimated and confirmed never merge
An estimate built from a configured revenue figure and a confirmed cost from a real invoice are different records with different weight. They are shown as what they are, because a merged total is defensible in neither direction.
Money is never a floating point number
Stored as exact numeric values. Floating point arithmetic in currency is how totals disagree with the sum of their parts, and how somebody loses an afternoon proving a system wrong about a penny.
Corrections are amendments, never edits
A closed financial record is not edited in place. A correction is an audited amendment that sits alongside the original, so the trail shows what was believed then and what is believed now.
How an unpriced hour stays unpriced
It reads "downtime cost not configured", which is the honest answer and the most commercially useful one.
When no revenue figure or rate has been configured against a device, Rydya does not price its downtime. It does not fall back to zero, which would quietly drag every average downwards and make the estate look better than it is. It does not reach for an industry benchmark, which would be a fact about somebody else's hospital presented as a fact about yours.
Departments sometimes find this frustrating in week one, and the same restraint is what a business case later stands on. The figures that exist are all defensible, and the gaps are visible as gaps rather than disguised as measurements. A pack where every number holds beats a fuller pack with one number that does not, because the pack is only ever as strong as the figure somebody chooses to question.
Setting a revenue figure is self-serve, and that is a deliberate choice
Anyone who can edit an asset can set what it earns and over what period, and the change is audited. There is no finance approval workflow in front of it, because a valuation that requires a committee is a valuation that never gets set, and an unpriced estate is the actual problem. Where a governed figure has been configured, it wins. Money is still never invented; it is simply not gatekept into non-existence.
Questions
Why does Rydya not estimate our downtime cost for us?
Because any estimate it could produce would be a fact about a different hospital. Where no rate is configured, the impact reads "downtime cost not configured" rather than zero or a benchmark. Departments find this frustrating in week one and are grateful in month six, when the business case survives a finance director asking where a number came from.
What happens to a figure when exchange rates move?
Nothing. The original amount and currency are immutable, and conversions live separately carrying their rate id, source and timestamp. A figure quoted six months ago reproduces exactly today. A system that silently revalues history is not an inconvenience in a regulated environment, it is the end of the conversation.
Can we see one total combining estimated and confirmed costs?
No, and this is deliberate rather than missing. An estimate derived from a revenue figure and a confirmed cost from a real invoice carry different weight, and adding them produces a number that is too soft to be an accounting figure and too precise to be an estimate. It reads as authoritative, which is precisely what makes it dangerous.
Who can set what a device is worth per hour?
Anyone who can edit the asset, and the change is audited. There is no approval workflow in front of it, because a valuation requiring a committee is a valuation that never gets set, and an unpriced estate is the real problem. Where a governed figure has been configured, it takes precedence.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us