Maintenance
Nico · Product specialist · 33 s
A working day with Maintenance · illustrative scenario
You do your work.
The context stays with you.
Send the technician the location, manual and previous intervention separately. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Receive the notificationAccording to configured rules
YOUR ACTION
A fault is recorded for heat pump WP-03.
THE SOFTWARE HELPS
Location, manual and history form the same context.
WHAT THIS DELIVERS
The basic information is together.
02Plan the workAccording to configured rules
YOUR ACTION
You select the person responsible and the date.
THE SOFTWARE HELPS
The work order can be monitored through the configured follow-up.
WHAT THIS DELIVERS
Fewer separate reminders.
03Complete the fileAccording to configured rules
YOUR ACTION
The contractor adds the report and photo; the authorised role reviews them.
THE SOFTWARE HELPS
The intervention and costs remain linked to WP-03.
WHAT THIS DELIVERS
For a subsequent fault, you can retrieve the history.
04Finish with a clear resultYour review
YOUR ACTION
You review the recorded data and decide what is complete and what still requires follow-up.
THE SOFTWARE HELPS
The decision refers to the same source, task or file context; there is no silent copy to another workspace.
WHAT THIS DELIVERS
A clear status and a traceable next step.
Less chasing and searching; better visibility into recurring problems and costs.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
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.
