Plans on a date cadence or a runtime counter. When one falls due, the work order appears.
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 occurrence falls due, the work order is raised against the right asset with the relevant service agreement already attached. Plans can also run on usage instead of dates: an asset’s runtime meter is fed either by manual readings or by an operating schedule that accrues hours per weekday in the site’s timezone and stops on that jurisdiction’s holidays, and the service order is raised when the counter passes its threshold. Editing a plan regenerates only future dates, and readings are append-only, so a correction supersedes an earlier reading rather than erasing it.
Planned maintenance rarely fails because a team forgets the concept. It fails because the calendar lives in somebody’s head, and leaves when they do. Putting the cadence into the system turns it into forecastable workload, so you can see next quarter’s servicing before you commit the budget. Usage-based plans then fix the other half of the problem: servicing a standby generator every six months regardless of use either wastes money or misses real wear.
Maintenance plans run by calendar date or by runtime hours, per building and asset.
How it works
Recurrence rules
A standard calendar cadence (RFC 5545) over a subject, with a rolling 18-month horizon. Edits regenerate only the future.
Occurrences
Each date on the calendar. A due date raises its work order automatically, or on demand.
Planned by date
Weekly, monthly or annual routines planned in advance, so upcoming workload can be forecast.
Planned by usage
Service orders triggered on equipment runtime readings rather than calendar dates.
Business calendars
Holiday-aware date arithmetic per jurisdiction. Operating schedules accrue zero machine-hours on holidays.
Reminders
Task alerts and weekly status summaries for upcoming or overdue maintenance.
In practice
Two pieces of equipment need servicing on completely different logic, and neither depends on anybody remembering.
A plan is written once for AHU-03 at Berlin Nord: quarterly, first Monday. Prova turns that cadence into dated occurrences across the next eighteen months.
On each due date the work order appears against the asset, with the HVAC service agreement already attached, so whoever picks it up can see the contracted response time.
In March the contract moves to six-monthly. Editing the plan regenerates only future dates. The two services already performed stay exactly as they were recorded.
The standby generator at Lyon Sud runs on hours instead. Its operating schedule accrues ten hours per weekday in French local time, and accrues nothing on French public holidays.
A technician enters a real meter reading in April. It supersedes the accrued estimate; the estimate is not deleted, and the lineage stays visible.
The 500-hour service fires when the counter passes 500, whether that lands in month four or month seven.
One estate, two maintenance philosophies, no calendar in anybody’s head. The quarterly plan forecasts workload before the budget is committed; the usage plan stops you servicing a generator that has barely run.
Illustrative walkthrough. Not a customer record.
What we will show you in a demo
Next quarter's servicing workload, visible before the budget is committed.
A plan edited, with past occurrences untouched while future ones regenerate.
A usage-based plan firing off a meter reading rather than a date.
A plan raising a job with the service agreement already attached to it.
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)
