Reliability

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.

In practice

The Rotterdam chiller has to be replaced, and somebody has to justify the capital.

  1. Over two years, nine breakdown jobs close on that asset. Each closure is coded from the organisation’s own failure catalogue.
  2. Seven of the nine carry the same problem code: compressor, high-pressure cut-out.
  3. Because everybody codes the same fault the same way, that recurrence is countable rather than remembered.
  4. Mean time between failures on the asset has fallen from 140 days to 47.
  5. Mean time to repair has risen, because the parts are becoming harder to source.
  6. 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.

Other Features

Contractors

Contractors and suppliers sit in one central register with their service agreements, their insurance policies and the expiry dates attached to both. When a contractor’s insurance policy expires, Prova stops…
Read more

Cost Management

Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building and by trade. Labour is valued at the rate in force…
Read more

Evidence

Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned, tagged, and stripped of EXIF metadata on upload. Documents are typed and anchored…
Read more

Permissions

Roles grant permissions resource by resource and action by action, denied by default, with six starter roles for facility management running from local manager to compliance officer. Scopes then decide…
Read more

Maintenance

A maintenance plan defines a cadence, such as quarterly or the first Monday of the month, and Prova materialises it into dated occurrences across a rolling eighteen-month horizon. When an…
Read more

Inspections

Inspections run on a recurring cycle: fire, elevator, boiler, and whatever else your jurisdiction requires. Each inspection produces findings, and each finding is one defect with its own severity, problem…
Read more

Compliance

One grid: every building down the side, every obligation across the top. Obligation categories such as fire safety, electrical testing and lifts are yours to define, each with its own…
Read more

Estate

Prova organises your estate as a tree. Buildings sit under portfolios you group by owner, fund or region, and each building holds its own units: floors, suites and rooms. Segments…
Read more

Next step

See how to optimise your workflow and save money.

Thirty minutes on your own estate: your buildings, your obligations and your numbers. We will show you where the time and the money are going.

Book a demo