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 BMS, metering, security posture, or M&V requirement.

Parties & Responsibilities

Who participates in deployment

Clear responsibility split is required because optimization touches energy goals, BMS 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, BMS 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.

System Integrator

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

  • Confirm point names, histories, trend configuration, BMS topology, and equipment mapping.
  • Configure approved connectivity, read access, write paths, alarms, overrides, and fallback behavior.
  • Support commissioning and confirm that BMS-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.

Deployment Process

A clear handoff at every step

From initial site review through ongoing optimization, the customer provides defined site inputs and approvals, and ClimaMind returns defined engineering deliverables. The project advances only when both sides agree that the current step is complete.

Customer includes the site owner or operator and an authorized SI/BMS contractor where applicable.

01

Site Qualification

Customer → ClimaMind

  • Provide current plant diagram with major equipment and piping
  • Provide representative BMS screens showing points and controls

ClimaMind → Customer

  • Review plant topology and equipment relationships
  • Check visible points, trends, and control access
  • Identify the most practical integration path

Joint decision

  • Proceed to detailed technical scoping
  • Request specific missing information
  • Pause until site conditions are suitable

02

Technical Scope

Review data requirements

Customer → ClimaMind

  • Define business goals and target operating outcomes
  • Provide current equipment, sequence, and controls documentation
  • Provide available trend exports and meter history
  • Name the customer project lead and SI contact

ClimaMind → Customer

  • Define the systems and outcomes in scope
  • Specify required data, points, and sampling
  • Document gaps, owners, and next actions
  • Propose the access and M&V approach

Joint decision

  • Approve the technical scope and boundaries
  • Confirm inputs are sufficient to begin modeling

03

Model Readiness

Customer → ClimaMind

  • Provide validated historical data for agreed signals
  • Answer outstanding site questions
  • Confirm schedules, limits, and operating constraints

ClimaMind → Customer

  • Build a model calibrated to site behavior
  • Validate model performance against held-out data
  • Evaluate feasible control strategies offline
  • Define writable points, limits, and exclusions

Joint decision

  • Confirm the model is ready for commissioning
  • Approve the proposed control scope and boundaries

04

Site Integration

Review site integration

Customer → ClimaMind

  • Provide approved network and BMS access
  • Coordinate the site window and SI availability
  • Confirm the approved read/write point list
  • Document fallback and manual override paths

ClimaMind → Customer

  • Map approved points to equipment and functions
  • Verify data quality and supervised write paths
  • Test alarms, limits, and safety responses
  • Run in shadow mode before active control

Joint decision

  • Complete the commissioning readiness checklist
  • Require customer authorization for controlled BMS writes

05

Operational Acceptance

Review acceptance criteria

Customer → ClimaMind

  • Provide operator feedback from live operation
  • Log issues, overrides, and unexpected behavior
  • Share agreed BMS and meter evidence

ClimaMind → Customer

  • Summarize availability and issued control actions
  • Review comfort, equipment, and operating constraints
  • Calculate results using the agreed M&V method
  • Track remaining issues, owners, and due dates

Joint decision

  • Sign acceptance against agreed criteria
  • Assign owners and dates for remaining punch-list items

06

Ongoing Optimization

Review ongoing support

Customer → ClimaMind

  • Maintain the approved operating data feed
  • Share operator feedback and emerging priorities
  • Notify ClimaMind of equipment or sequence changes

ClimaMind → Customer

  • Report performance, savings, and operating exceptions
  • Update models and strategies as conditions change
  • Review overrides, drift, and control degradation
  • Provide engineering support for agreed priorities

Joint decision

  • Agree the review and service cadence
  • Require new approval before expanding scope

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.

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

ClimaMind runs locally at the site edge. If internet access is interrupted, local optimization continues and cloud reporting is delayed; if BMS communication is interrupted, ClimaMind uses the approved local fallback and stops issuing new supervised writes for the affected path.

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 BMS 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.

Deployment Packet

Download the deployment technical overview

Use this PDF for customer, facilities, IT/OT, and SI review. It summarizes the deployment path, responsibilities, security boundary, fallback behavior, acceptance, and long-term support.

PDF · Technical overview · Prepared by ClimaMind

Download PDF