Skip to main content

Daily Operations Triage

Use daily triage when facility teams need a repeatable operating review across assets, alarms, inspections, work orders, energy signals, and field feedback. The review should produce a short, evidence-backed handover rather than a long dashboard tour.

Daily triage is usually run by an operator, facility manager, maintenance lead, or shift owner. AI Agent can help summarize records, but the accountable owner reviews the final decisions.

Triage Flow

Prerequisites

RequirementWhy it matters
Active operating boundaryDefines which site, systems, assets, and records the shift review covers.
Current source statusShows whether BMS, meter, Inspector, CMMS, DFS, and ECM records are fresh enough.
Owner rosterMaps alarms, inspections, work orders, and blockers to accountable people or teams.
Review templateKeeps each handover short, consistent, and traceable.

Inputs

InputWhat to confirm
Source freshnessLatest BMS, meter, CMMS, Inspector, and DFS sync timestamps.
Active alarmsSeverity, asset, location, first seen time, latest value, related work, and repeated pattern.
InspectionsToday's scheduled tasks, overdue tasks, issues found, attachments, and QR or check-in status.
Work ordersOpen, assigned, in progress, blocked, returned, completed, and waiting-for-review work.
Energy and subsystem signalsMeter anomalies, consumption changes, chiller or HVAC notes, and operating constraints.
DocumentsSOPs, drawings, manuals, or service records needed for the next action.

Step 1: Check Source Freshness

Start by checking whether the data is current enough for a daily decision.

SourceFreshness question
BMS and metersAre readings current for the review window?
InspectorAre alerts, inspections, and field uploads synced?
CMMS or work-order sourceAre status changes and completion notes visible?
ECMAre required manuals, SOPs, or service reports indexed and accessible?
DFSAre connector sync, quality, and rejected-record states acceptable?

If a source is stale, record the freshness issue in the handover and avoid treating missing activity as a confirmed normal state.

Step 2: Review Active Alarms and Findings

Group events by operating impact.

Review dimensionGuidance
SeverityStart with safety, production, tenant impact, service availability, and repeated high-severity alarms.
Asset criticalityPrioritize equipment that affects multiple spaces, critical services, or dependent systems.
RecurrenceLook for repeated alarms, reopen patterns, and recently closed work on the same asset.
Source evidenceCompare alarm time, latest value, inspection notes, and recent work-order history.
Missing evidenceRecord missing values, unclear units, stale signals, or unmapped asset identity.

Use Alert to Inspection and Work Order Loop when an event needs field action.

Step 3: Review Open Work

Daily triage should make work ownership visible.

Work stateTriage action
NewConfirm owner, asset, location, priority, and evidence.
AssignedConfirm the responsible team has accepted the work.
In progressCheck progress, blockers, attachments, and expected completion.
Returned or blockedIdentify missing access, parts, contractor, permit, or source data.
CompletedConfirm closure notes, evidence, and follow-up recommendations.
RepeatedReview root cause, asset condition, and whether a wider system check is needed.

When multiple CMMS providers are connected, use Multi-CMMS Consolidation to keep downstream execution systems in place while FactVerse provides a common operating layer.

Step 4: Check Energy and Subsystem Signals

Facility triage may include energy or subsystem review when those records are connected.

SignalReview focus
ConsumptionUnexpected demand, abnormal consumption, or shift from baseline.
Meter qualityMissing intervals, stale readings, unit mismatch, or meter-to-space mapping issue.
Chiller or HVACEfficiency indicators, setpoint changes, VAV diagnostic notes, and affected zones.
IAQ or environmentalOut-of-range values, repeated complaints, or sensor placement concerns.
Green Mark evidenceMissing records, expiring documents, or clause evidence gaps requiring owner follow-up.

Energy review should capture assumptions such as time window, operating schedule, weather context, and meter mapping.

Step 5: Prepare the Handover

A useful handover is short and traceable.

SectionInclude
Operating summarySite, shift, systems reviewed, source freshness, and key risks.
Active issuesAsset, location, severity, owner, evidence, and next action.
Open workWork-order status, blocked items, field owner, and expected next update.
Data gapsStale sources, missing mappings, rejected rows, or documents not found.
Follow-upAssigned owners, deadlines, and records to review in the next shift.

AI Agent Use

AI Agent can help gather source records, summarize unresolved events, compare recent work history, and draft the handover. The reviewed handover should keep source references visible and separate suggested checks from approved actions.

Validation Checklist

  • The review includes source freshness before conclusions.
  • High-impact alarms and findings have owner, asset, location, and evidence.
  • Open work states match the execution system.
  • Blockers and missing data are explicit.
  • Energy or subsystem findings include assumptions and meter or sensor context.
  • The handover names next owners and follow-up records.

Expected Output

The daily triage should produce a reviewed handover with source freshness, active issues, open work, blockers, owner assignments, and the records that should be checked in the next shift or maintenance review.