Connect a building system to Property Operations

The Operations tab gives an org admin a live, color-coded view of every connected device on every property — fire panels, BMS/HVAC, leak/temperature sensors, access control, power and water meters, cameras. You ack, clear, and escalate alarms inline; life-safety alarms also auto-create a work order so the on-call gets paged through the existing notification stack.

How devices reach Turtini:
1. Pick an adapter — BACnet/IP is the broadest (most fire panels, HVAC controllers, and access systems support it). The mock adapter is on by default for demos and seeds 8–12 sample devices on activation.
2. Stand up an on-prem gateway (Tridium/Niagara, Distech, a Node-Red bridge, or any vendor controller with HTTPS support). The gateway runs on the building LAN — Cloud Functions can't reach BACnet directly because BACnet/IP is UDP broadcast.
3. Configure the gateway to POST event JSON to your propertyIotIngest webhook with adapterId='bacnet'. The adapter normalizes the payload into platform-native events automatically.

What you see:
• Tile board grouped by zone with live status (ok / warn / alarm / offline)
• Event log with severity badges, ack/clear/escalate/silence actions inline
• Wall mode at /property/wall — full-bleed projector or lobby display
• Cross-module: critical fire/leak/gas events auto-create a Field Service work order. Power/water/gas readings flow into Accounting's monthly utility roll-up.

Wally tools:
• "What alarms are active?" → property_listEvents
• "What devices are offline?" → property_listDevices
• "Summarize the alarm storm last night" → property_summarizeIncident
• "Anything weird?" → property_detectPatterns (clusters by category and zone)

The mock adapter gives you a working board on day one. Adding a real building system is one gateway away — there's no per-vendor SDK lock-in here, just normalized JSON.