Solutions / Buildings & estates
Turn fragmented BMS alarms into contextual asset conditions, dispatch work with the evidence attached and verify every fix against live building data.
For facility directors, estate owners and operations teams managing critical buildings and portfolios.
MirayaConcept · design-partner stageDegraded cooling capacity
Suspected stuck cooling-coil valve. Valve command is saturated while supply-air temperature drifts.
Beyond the alarm queue
Point-driven tools leave operators to reconstruct the asset, its history and the people affected. That hidden work slows every response.
A single stuck valve can surface as unrelated temperature, valve and zone alarms. Operators must know the asset topology before they can understand the event.
A work order arrives without the evidence that caused it. Technicians attend without ranked causes, asset history or a clear live value to verify after the fix.
The same degradation can affect occupied zones, plant energy and indoor air quality. Without relationships between objects, its full cost stays invisible.
Performance to prove
An asset-centred operating record connects detection, dispatch, arrival and recovery — so service and efficiency can be reviewed together.
Minutes from object condition to owned response
ReduceHours from detection to verified recovery
ReduceWork resolved without a repeat visit
IncreaseUptime for systems serving occupied spaces
IncreaseMeasured against baseline; never blended with projections
EvidenceDirections describe the intended operating outcome. No improvement is claimed without a site baseline and measured result.
Worked example / AHU-TB-12-04
A cooling-coil valve sticks near closed. The object model connects valve command, supply temperature and two occupied zones, then carries that context through dispatch and verification.
Cooling output and valve command indicate degraded capacity, with a suspected stuck coil valve and its evidence chain.
The nearest qualified technician receives the asset history, affected zones, ranked causes and wayfinding to the machine.
Supply-temperature recovery confirms the fix. The condition closes and its measured impact enters the KPI ledger.
Step inside the product
Move from the buyer problem to the relevant product chapter, with its maturity and illustrative-data status kept visible.
Concept chapter / Insight to incident
MirayaConcept · design-partner stageCompare the point-driven queue with an object-led condition, then see dispatch, tenant communication and live-value verification in one continuous story.
Open the incident chapterPilot where the pain is visible
Connect read-only feeds, agree the baseline and prove one workflow end to end before extending the operating model.
Scope a building pilot
