Deployment Concern

Operator Change Management

How the facility team, ClimaMind, and the system integrator keep operating authority clear as optimization moves from review to live use.

Operator change management is part of deployment, not a separate training afterthought. The site should know what ClimaMind can read, recommend, write, log, pause, and escalate before supervised operation begins.

Who Is Involved

Define the operating roles before go-live

The exact staffing model is site-specific, but the deployment review should make the handoff points explicit.

Facility operators

Own day-to-day operation, manual override, alarm response, and local equipment judgement.

  • Know where ClimaMind activity appears in the BAS or agreed operating record.
  • Know who can pause optimization and when a manual override should be treated as the active instruction.

ClimaMind

Explains the approved control boundary, monitors optimization behavior, and supports issue review inside the agreed deployment scope.

  • Clarifies read-only monitoring, advisory mode, and supervised writes.
  • Reviews reported behavior against approved points, limits, fallback rules, and available telemetry.

System integrator

Connects BAS access, point mapping, write permissions, graphics, trend logs, alarms, and local operator workflow.

  • Confirms where operator-facing changes should be made in the BAS.
  • Documents point names, override behavior, alarm interactions, and escalation contacts when available.

Operating Model

Operating modes and authority

Operators should not have to infer whether ClimaMind is observing, recommending, or writing.

  • Read-only monitoring means ClimaMind reads approved data but does not recommend or write actions.
  • Advisory mode means recommendations are reviewed by the facility team or SI before implementation.
  • Supervised writes mean ClimaMind may write only approved points, ranges, schedules, and rates of change.
  • The BAS remains the operator interface and local safety authority unless a different boundary is approved.

Communication

Shift handoff and escalation

A live optimization workflow needs a simple path for routine questions, abnormal behavior, and temporary pauses.

  • Define what the outgoing shift should mention when ClimaMind is active, paused, or in advisory mode.
  • Define who can pause optimization and who should be notified after a pause, override, BAS rejection, or telemetry issue.
  • Separate urgent site operation decisions from later engineering review so operators are not waiting for remote analysis during active operations.

Enablement

Training and reference material

Training should focus on the site-specific control boundary instead of generic AI concepts.

  • Show the approved points, write limits, fallback behavior, and operator override path.
  • Use a short reference packet that explains what should be recorded and where to find the current operating mode.
  • Keep training material aligned with the actual BAS graphics, alarms, and trend names used by the site.

Acceptance

Acceptance and post-go-live review

Change management does not end at cutover. Early operation should be reviewed with the people who run the building.

  • Confirm operators can recognize read-only monitoring, advisory mode, supervised writes, pause state, and fallback state.
  • Review early overrides, rejected writes, alarms, comfort complaints, and excluded periods before expanding authority.
  • Use operator feedback to adjust documentation, escalation paths, or the approved control boundary when needed.

Operating Record

What should be recorded

Records should support site operations, M&V interpretation, and later issue review without turning operators into data clerks.

  • Control actions and recommendation acceptance or rejection when available.
  • Pause, override, BAS rejection, stale telemetry, alarm, fault, and re-enable events.
  • Known operator notes that explain why a manual decision was made, especially during maintenance, abnormal weather, comfort events, or equipment constraints.
Back to deployment overview