Deployment Process

From data intake to acceptance

A ClimaMind deployment is a staged engineering process. Each stage has a defined owner, input, output, and exit condition before the project moves from data review to model training, site work, and acceptance.

This overview is intentionally operational. It does not assume that every site has the same BAS, metering, security posture, or M&V requirement.

Parties & Responsibilities

Who participates in deployment

Clear responsibility split is required because optimization touches energy goals, BAS integration, site operations, and M&V evidence.

Customer

The building owner, facility operator, energy team, or asset manager responsible for the site and business approval.

  • Define business goals, operating constraints, and acceptance criteria.
  • Authorize access to approved data, BAS stakeholders, and site context.
  • Approve deployment boundaries, write permissions, fallback expectations, and final acceptance.

ClimaMind

The AI HVAC optimization provider responsible for data review, modeling, control strategy design, deployment support, and performance analysis.

  • Assess data quality, train and validate models, and identify feasible control strategies.
  • Prepare point mapping, control recommendations, risk registers, and operating evidence.
  • Support deployment, monitor performance, and produce customer-readable M&V and operating reports.

SI / System Integrator

The BAS/BMS or controls contractor responsible for site-side integration and controls implementation support.

  • Confirm point names, histories, trend configuration, BAS topology, and equipment mapping.
  • Configure approved connectivity, read access, write paths, alarms, overrides, and fallback behavior.
  • Support commissioning and confirm that BAS-side logic matches the approved control boundary.

Optional M&V Partner

An independent measurement and verification partner used when the customer wants third-party review or contractual savings evidence.

  • Review baseline method, measurement boundary, adjustments, and evidence requirements.
  • Check savings calculations against the agreed M&V plan and available data.
  • Provide independent review input for acceptance when the commercial arrangement requires it.

Process

The four deployment stages

The stages are sequential, but review work can overlap when the project team already has reliable data and a known BAS integration path.

01

Data Intake

Collect and validate the operating data needed to understand the site before field deployment decisions are made.

Open data intake details
  • 01Gather BAS trend exports, meter data, equipment schedules, control sequences, point lists, and operating constraints.
  • 02Map raw signals to equipment, sensors, setpoints, commands, and energy measurements.
  • 03Confirm which signals are required for deployment and which are only useful context.
  • 04Identify gaps that could block baseline modeling, control review, or on-site commissioning.

02

Model Training

Use validated historical data and site constraints to build baseline models and evaluate control strategies before site activation.

  • 01Train models on aligned BAS, meter, weather, schedule, and operating-context data where available.
  • 02Build baseline behavior for the systems inside the agreed measurement boundary.
  • 03Test candidate strategies offline against comfort, equipment, safety, and customer approval constraints.
  • 04Produce a model readiness summary that separates feasible control opportunities from unsupported assumptions.
  • 05Hold back strategies that require missing signals, unclear permissions, or unverified operating modes.

03

On-site Deployment

Connect the approved deployment boundary to the customer site, usually progressing from read-only monitoring to advisory or supervised control.

Open on-site deployment details
  • 01Confirm network path, user permissions, edge device placement, point access, and BAS-side fallback behavior.
  • 02Commission point mapping, telemetry quality, alarms, overrides, and operator review workflows.
  • 03Start with monitoring or advisory operation when the site needs staged confidence building.
  • 04Only enable BAS writes after the customer-approved write list, limits, and manual override path are reviewed.

04

Acceptance

Close the deployment with evidence that the system is operating within the agreed boundary and that results can be reviewed.

Open acceptance details
  • 01Review comfort, equipment constraints, uptime, control actions, operator overrides, and issue logs.
  • 02Evaluate savings against the agreed M&V method when savings claims are part of acceptance.
  • 03Document sign-off criteria, open items, and the cadence for ongoing optimization.

05

Long-term Support

After sign-off, ClimaMind can stay engaged at your site—keeping approved operating data when useful, refining models as conditions change, and adding dashboard visibility or deeper engineering support where the project needs it.

Open long-term support details
  • 01Hold approved BAS, meter, and operating data when the site wants continuous review without restarting intake.
  • 02Retrain models and adjust control strategies as weather, occupancy, tariffs, and equipment conditions shift.
  • 03Give authorized operators dashboard access to status, savings trends, and agreed reports when visibility is part of the service.
  • 04Support deeper tuning for priority systems and adjacent integration or reporting work as the partnership matures.

Additional Concerns

Topics handled alongside the main stages

These topics are not a separate deployment phase. They are checked at the stage where they affect risk, approval, or acceptance.

Security & Access Control

Data transfer, user access, network connectivity, edge device communication, write permissions, and remote support are reviewed through the approved security process, not through informal file exchange.

BAS/BMS Compatibility

Protocol, vendor, point naming, trend history, alarm behavior, override semantics, and write limitations affect both integration effort and control scope.

Fallback & Manual Override

Deployment must define what happens if connectivity is lost, a point is stale, an operator overrides a command, or the BAS rejects an action.

Measurement & Verification

M&V requirements should be agreed before acceptance. Not every project needs a third-party partner, but every savings claim needs a defined measurement boundary and evidence path.

Operator Change Management

Facility operators need to know what ClimaMind reads, what it recommends, what it may write, how to override it, and how issues are escalated.

Readiness Blockers

Common blockers include missing trend history, unclear meter boundaries, inaccessible BAS points, unresolved network approvals, or no agreed M&V plan for contractual savings.

Long-term Support

After sign-off, ClimaMind can keep holding approved data, improving models over time, and supporting operators with dashboard access or deeper site-specific engineering when needed.