Every site, grouped by region or country, with the equipment inside it.
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 group buildings by rule rather than by hand, so you define the rule once, such as all offices above 5,000 square metres in Denmark, and membership keeps itself current as the estate changes. Every address carries its jurisdiction, its timezone and its coordinates, so a site in another country calculates its own dates correctly.
Most facility teams keep the estate in a spreadsheet that describes the buildings but connects to nothing else. In Prova the building is the centre of gravity: its equipment, its jobs, its certificates, its contractors and its costs all hang off the same record. That is what makes a portfolio-level question answerable in seconds instead of by emailing five site managers and waiting.
The buildings register: every site with its country, portfolio, segments and tags.
How it works
Portfolios
Hand-picked groups of buildings, by owner, fund or region. The top of the property hierarchy.
Segments
Rule-driven groupings. Define the rule once and membership keeps itself current.
Buildings
The operational centre. Everything else references it.
Units
Floors, suites and rooms: leasable, inspectable, addressable.
Addresses
Typed, with jurisdiction, timezone and coordinates. Geography-driven segments recompute the moment one changes.
Tags
Org-owned informal labels that live beside the formal groupings.
In practice
A new depot opens at Antwerp Dock 4, and one person creates it.
The building is created with its address: Belgium, timezone Europe/Brussels, coordinates on the map.
It is added by hand to the Benelux portfolio, because that is an ownership grouping somebody decides.
The segment sites over 5,000 square metres picks it up on its own, because the rule matched. Nobody added it.
The scope tree gains a building leaf under the Belgium node, so the Benelux manager can see it immediately. No grant was issued.
The compliance matrix gains a row. Every Belgian obligation reads nothing on file until certificates are filed against it.
The Belgian business calendar applies, so Belgian public holidays stop machine-hours accruing on the equipment inside it.
One person created one record. Five other parts of the system are now correct without anybody maintaining them. That is the argument for the building being the centre of gravity rather than a row in a list.
Illustrative walkthrough. Not a customer record.
What we will show you in a demo
A building added to a region, with the segment, the access grants and the compliance matrix all picking it up without further input.
The move from a portfolio-level view down to a single unit, without changing system.
A building's country changed, with the timezone and jurisdiction following it.
We have buildings in six countries. Does it handle that?
Each address carries its own jurisdiction and timezone, and business calendars are holiday-aware per jurisdiction. Dates are stored in UTC with the site's own timezone beside them.
Do we have to restructure our estate to fit your model?
Portfolios are hand-picked and segments are rules you write yourself. Neither imposes a hierarchy on you.
How long before our estate is actually in there?
Our team completes initial system setup and data onboarding with your staff before launch. Nobody starts with an empty screen.
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)
