From a single protocol to portfolio risk management
Districts and cities need comparable data, predictable response times, and documentation assigned to facilities. We are building a common standard for schools, social care homes, offices, cultural institutions, sports facilities, and critical services.
A city with district rights performs both municipal and district tasks in parallel — which is why we divide facilities into portfolios, criticality levels, and procurement parts.
District — most common scope
- District Office and service centres
- Secondary schools and special facilities
- Social care homes and social units
- Hospitals and clinics belonging to the district
- Roads, signalling, and ancillary facilities
- Warehouses, PSP, and OLiOC resource coordination
- Mobile power sources for several municipalities
City — most common scope
- Office and organisational units
- Residential and municipal buildings
- Lighting, crossings, public spaces and signalling
- Schools, kindergartens, culture and sports
- Server rooms, control centres and security systems
- Waterworks, sewage treatment plants, transport and municipal companies
- Framework agreements for breakdowns and minor works
Model for a large portfolio
Seven stages — from pilot to readiness test.
- Pilot of 10 facilitiesdata standard and protocol test
- Segmentationcritical · social · administrative · technical · other
- Batches and schedulescale adjusted to the actual number of teams
- Coordinator and deputyclear responsibility
- Dashboarddeadlines, faults, SLA and costs
- Quarterly reportdecisions, risks and CAPEX plan
- Readiness testselected critical facilities and backup sources
Measurable SLA
We break down times instead of promising a single "24/7".
- Confirmation of notification receipt
- Criticality qualification
- Arrival time or remote diagnosis
- Breakdown securing
- Temporary and permanent repair
- Protocol deadline
- Escalation and report
Fair SLA principle
We do not publish a universal "24/7" without on-call duty, resources, and contractual conditions that allow it to be met. The times for your portfolio are recorded in the contract — and we report on their fulfilment every quarter.
Questions and Answers
How do you divide a large portfolio into order parts?
According to criticality segments and geography, with batches adjusted to the actual number of teams. The data and protocol standard is common to all parts — this makes the collective report meaningful.
Does the dashboard require the implementation of a system on the city's side?
No — order status, deadlines, and faults are available in our panel, and reports are provided in a format agreed with the unit. Data export remains on the part of the ordering party.
How does cooperation begin?
With a pilot of 10 representative facilities: standard test, portfolio valuation, and a report, based on which the decision on scale is made.
Unit registration form
Ref.: SP/2026/MIASTA · response: office hoursOne submission is enough — the coordinator will come back with technical questions or a proposal for scope and deadline.
Information security: do not send classified information, facility diagrams, evacuation routes, or security details via the public form. We exchange OPZ documentation through an agreed, secure channel after contact is established.