Coding failures the same way every time is what makes recurrence countable.
When a job closes on a breakdown, Prova captures the closure in a standard shape: problem, cause, remedy, severity and downtime. The vocabulary comes from a failure code catalogue your organisation owns and edits, so the same fault is coded the same way every time and by everyone.
Coding failures consistently is what makes recurrence countable. It turns a stack of individual repairs into mean time between failures and mean time to repair, per asset, per category and per site. That is the evidence you need to argue for replacing a machine rather than repairing it a fourth time, and to identify the contractor whose fixes do not hold.
How it works
Failure record
Problem, cause, remedy, severity and downtime, captured at closure rather than reconstructed later.
Failure codes
A catalogue you own and edit, not a fixed vendor taxonomy.
Derived measures
Mean time between failures and mean time to repair, per asset, per category and per site.
In practice
The Rotterdam chiller has to be replaced, and somebody has to justify the capital.
Over two years, nine breakdown jobs close on that asset. Each closure is coded from the organisation’s own failure catalogue.
Seven of the nine carry the same problem code: compressor, high-pressure cut-out.
Because everybody codes the same fault the same way, that recurrence is countable rather than remembered.
Mean time between failures on the asset has fallen from 140 days to 47.
Mean time to repair has risen, because the parts are becoming harder to source.
The same coding across the estate shows the pattern is specific to this unit, not to the model.
The capital request stops being “it keeps breaking” and becomes an interval, a trend, a downtime figure and a cost. It also identifies the opposite case: a contractor whose repairs do not hold shows up as the same code returning on the same asset, which is evidence rather than suspicion.
Illustrative walkthrough. Not a customer record.
What we will show you in a demo
Repeat failures on one asset counted rather than remembered.
Mean time between failures across sites for one equipment category.
A contractor whose fixes do not hold, evidenced rather than suspected.
You do. It is an organisation-owned catalogue that you edit, which is what keeps the coding consistent with how your team actually talks.
Is this not just reporting?
The coding happens at closure, as part of finishing the job. The reporting is a consequence of that, not a separate exercise somebody has to remember to do.
Insurance, contracts and spending limits as live records with dates on them, not folders somebody forgot to open. Contractors and suppliers sit in one central register with their service agreements,…
Every euro attributed, and a changed number that leaves a trace. Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building…
Proof attached to the thing it proves, not merely filed somewhere near it. Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned,…
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
English (UK)
