One contract, one standard
One service standard for all locations
A network of facilities requires comparable data, clear accountability, and history assigned to each location. A pilot allows us to test the process before covering the entire portfolio.
Not all facilities need to have the same priority or travel time – what is common is the method of description, reporting, and cost.
What we organise
Portfolio in one language.
- List of facilities and contact persons
- Function criticality and priorities
- Travel zones and access hours
- Existing documentation and inspection deadlines
- Cost limits and approval path
- Report and photo standard
- Invoicing and cost centres
- KPIs and management meeting cycle
Pilot before scaling
Proof first, then the entire portfolio.
- Selection of 5–10 facilitiesDifferent types of locations – a representative sample.
- Data importBasic data and documents.
- Categories and prioritiesCommon dictionary of requests.
- Request handlingReal interventions and one planned work.
- ReportTime, cost, data quality, and deviations.
- CorrectionFine-tuning SLA, forms, and roles.
- Decision on waveScaling to subsequent locations.
Portfolio report
Comparable data from the entire network.
- Requests by location, category, and priority
- Median service times
- Costs broken down by facility and type of work
- Recurring faults
- Inspection deadlines and overdue works
- Open risks and prevention & CAPEX plan
Integrations
Fair data and API.
Before we connect to your system
- export, API or integration — priced after data model confirmation,
- permissions, security and maintenance are agreed upfront,
- you can retain local contractors — we then separate responsibilities and reports.
The word "API" itself, without a working solution, is not proof — which is why we only communicate it after implementation.
FAQ
Portfolio questions.
Do all locations need to have the same SLA?
No. Priorities, zones and hours may vary according to the object's role. The method of description and reporting is common — SLA service rules are defined per object.
Can local contractors be retained?
Yes — the model can include coordination or a regional component. Responsibilities, data and reports must then be clearly separated.
How is a single invoice settled?
The agreement may provide for a collective invoice with analytics per location or a breakdown by cost centres. The format is agreed before the pilot.
How is object data protected?
We define roles, access scope, retention, method of attachment transfer and client requirements — before importing documentation.
B2B Contact
Plan a portfolio pilot.
Select 5–10 representative locations — on these, we will check the process, timings and data quality before scaling.
Our principle: first a pilot and report, then a decision to cover the entire portfolio.