Overview
During the summer release cycle, Virtual Facility continued to mature alarm triage, work-creation context, reporting visibility, and backend reliability. These updates helped teams understand alarms faster, apply more consistent triage decisions, and give technicians better context before closing work.
Standardized Triage Reason
Standardized Triage Reason was delivered across the product, including admin settings, snooze and decline workflows, tables, lenses, filters, and reporting. This gives teams a more consistent way to categorize alarm decisions and analyze triage outcomes over time.
Admin settings — Snooze and Decline reason sets, with details-required toggle
Triage reason required when snoozing an alarm
Triage Reporting
A Triage Actions Report was added to provide clearer visibility into alarm-handling activity. Triage reporting was also expanded across alarms, assets, users, and teams, making it easier to understand how alarms are being reviewed, acted on, and resolved.
Triage Actions Report — filters include Last Triaged By and Triage Reason
Work-Creation Context
Related alarms can now be offered during work creation, helping users reduce fragmented work handling and provide technicians with better context. Rosie automated work creation also preserves related-alarm grouping more effectively, keeping connected alarm activity together when work is created automatically.
Related alarms carried into work creation (Associated Alarms)
Alarm Status in WebTMA
Alarm Status in WebTMA was introduced so technicians can see the Virtual Facility alarm status before closing work orders. This improves coordination between alarm triage and downstream maintenance workflows.
Alarm Notes and History
Expandable Alarm Notes were added to improve usability when reviewing long-form alarm context. Alarm History was also enriched with a Last Triaged By column, giving teams better traceability into who last acted on an alarm.
Alarm History — Last Triage Status and Last Triaged By columns
Alarm and Asset Intelligence
Controller alarm parsing was added so controller-related alarms can be identified and assigned to controller-type assets automatically. Building parsing, a building parser, and a matching engine were also introduced to support future modeling and reporting workflows. Asset Criticality can now be set manually, giving teams more flexibility in asset management and prioritization.
Filters, Groups, and Reporting Foundations
Alarm Source became available in work filters and reporting, while CMMS-related display names were made clearer. Teams also gained an Asset Group filter, and building and asset grouping enhancements strengthened organization across the product. New Cloud SQL reporting views were introduced as foundational work for future reporting.
Integration and Data Reliability
Summer introduced Hexmodal integration v2 and Schneider EBO PostgreSQL export normalization v2 as part of broader integration modernization. Data Pump behavior was improved for acknowledged-alarm retention and exporter timing, while Pub/Sub retry policies, dead-letter queues, and database-aware ingest flood control improved delivery reliability at scale. Late-summer releases added customer-facing reliability improvements across Otto AI, AI-Insights, CMMS integrations, building rename propagation, and alarm reporting, including more efficient field-value responses, safer proxy handling, better dark-theme chart readability, more reliable Otto AI reconnect behavior, deep links into alarm and asset slideouts, stronger triage-reason persistence, improved regular-user filtering, Nuisance Alarm Report exports with open work order numbers, and more complete building rename updates across reports, filters, aliases, and CMMS mappings.