Buildings
Sofia · Product specialist · 31 s
A working day with Buildings · illustrative scenario
You do your work.
The context stays with you.
Look up a manual, then the supplier and then previous interventions. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Open the itemAccording to configured rules
YOUR ACTION
You open the system or its QR reference.
THE SOFTWARE HELPS
The correct file is retrieved within your permissions.
WHAT THIS DELIVERS
The space and system are known.
02View the contextAccording to configured rules
YOUR ACTION
You select the manual or history.
THE SOFTWARE HELPS
Existing documents and previous interventions are linked to the same system.
WHAT THIS DELIVERS
No searching in separate folders.
03Continue the workAccording to configured rules
YOUR ACTION
You continue to maintenance or an inspection.
THE SOFTWARE HELPS
The system remains the shared reference.
WHAT THIS DELIVERS
Your next action has immediate context.
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 time spent searching on site and less knowledge lost during handover.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Meet Sofia
Buildings & building passport
All the information about a building in one familiar place.
Explore a practical example
Sofia
Buildings & building passport
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.
