IT OPS

Daily Building Anomaly Digest to MS Teams

Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMorning scheduled digest run
  • ActionQuery prior-day anomalies from BigQueryGoogle BigQueryBigQuery
  • LogicGroup and rank by site, system, severity
  • ActionDraft prioritized briefing with OpenAIOpenAI
  • OutputPost digest to MS Teams channelMicrosoft Teams

What it does

This workflow gives facilities managers a single morning briefing instead of a stream of overnight alerts. It pulls the last 24 hours of flagged anomalies from your BigQuery telemetry store, groups them by site and system (HVAC, power, water, air quality), counts and ranks them by severity, and writes a readable summary that an LLM formats into a tidy briefing. The digest lands in MS Teams before the team's first standup.

When to use it

Use it when real-time pages cover emergencies but you also want a calm daily rollup for planning, trend-spotting, and catching low-grade recurring issues that never breach paging thresholds. Pairs naturally with the telemetry archive workflow.

How it works

  1. 1A morning schedule triggers the digest.
  2. 2A BigQuery query returns the prior day's flagged anomalies.
  3. 3A logic step groups and ranks them by site, system, and severity.
  4. 4An OpenAI step turns the grouped data into a clear, prioritized briefing.
  5. 5The briefing is posted to the MS Teams facilities channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.