Maintenance
Nico · Product specialist · 33 s
Interactive practical example · simulation
One report. One complete story.
A maintenance report is linked to the system, action and history. You are exploring how it works; no real data is processed and no actions are carried out.
01Report
The problem belongs to a system.
A report about a heat pump is linked to the correct system. The room and previous maintenance records form part of the same context.
Fictitious example · Heat pump WP-03.
02Context
Find what you need before the intervention.
The person responsible reviews the relevant manual, previous notes and the location of the system.
No searching through separate emails or a second file.
03Work order
Make the next step clear.
A work order brings together the problem, the location and the relevant supplier. In this example, we only review the intended follow-up.
No supplier is contacted and no order is sent.
04Evidence & costs
The result is recorded in context.
An intervention report and the relevant costs are linked to the existing file.
Example information, not a real invoice or completed intervention.
05Building passport
The next manager can find it again.
The maintenance history remains linked to the same system and the same building passport.
One building. The same information, in the right workspace.
The same property, a different perspective.
These examples illustrate the intended connections. They are not proof of production functionality.
Meet Nico
Maintenance
From a reported issue to follow-up, starting with the building.
Explore a practical example
Nico
Maintenance
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usWatch the practical example
Pilot direction: start with one workspace and expand later.
ObraPad is designed to keep Obra Core as the shared foundation while you add capabilities over time.
Building-specific activation and restricted installer access are being prepared for the pilot and verified end to end. Ask which scopes can currently be tested.
Intended starting point
The pilot direction is to begin with one workspace and add more later.
Planned per-building expansion
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
Planned access model
The access model is being developed so an installer or partner can use only the selected building, installation or task.
Intended example: heat pump maintenance
In the intended scenario, the installer only accesses the heat pump, its documents and assigned maintenance tasks in one building. Other buildings, financial information and private documents remain outside the scope. View, change, duration and revocation controls must be proven server-side before availability.
The design keeps an additional workspace and partner access as separate choices, with the building passport as the shared foundation.
