Deployment Process
Cloud Deployment
ClimaMind qualifies most projects for cloud deployment first and keeps approved BMS writes under explicit review with the required safeguards, approvals, and operating evidence in place.
Parties & Responsibilities
Who participates in deployment
Clear responsibility split is required because cloud services, approved BMS integration, site operations, and M&V evidence move at different speeds.
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 qualification 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
Initial 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, telemetry quality, and deployment-readiness constraints
- Check visible points, trends, control access, and security dependencies
- Identify whether the approved deployment path is ready to proceed
Joint decision
- Proceed to connection and technical scoping
- Request specific missing information
- Pause until site conditions are suitable
02
Connection & Scope
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, data path, and outcomes in scope
- Specify required data, points, sampling, and approval checkpoints
- Document gaps, owners, next actions, and approved write boundaries
- Propose the access, fallback, 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
Commissioning & Advisory
Customer → ClimaMind
- Provide approved connectivity, operator contacts, and BMS stakeholders
- Coordinate the review window and SI availability
- Confirm the approved read/write point list
- Document fallback and manual override paths
ClimaMind → Customer
- Run commissioning and advisory review against the approved boundary
- Map approved points to equipment and functions before authority expands
- Verify data quality, alarms, limits, and supervised write prerequisites
- Run in shadow mode before any active control path is approved
Joint decision
- Complete the commissioning readiness checklist
- Confirm whether the approved deployment path is sufficient for the scope
- Proceed directly to acceptance and ongoing optimization when the approved path is sufficient
05
Site deployment
Customer → ClimaMind
- Provide approved network and BMS access
- Coordinate the site window and SI availability
- Confirm the approved write list
- Confirm customer authorization for supervised BMS writes
ClimaMind → Customer
- Verify the approved BMS boundary for supervised writes
- Verify supervised write paths, fallback behavior, and operator-visible status
- Test alarms, limits, safety responses, and manual-override handling
- Document field evidence for acceptance and ongoing optimization
Joint decision
- Complete the commissioning readiness checklist
- Require customer authorization for controlled BMS writes
06
Acceptance & ongoing optimization
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, due dates, and optimization follow-ups
Joint decision
- Sign acceptance against agreed criteria
- Agree the review and service cadence for ongoing optimization
- 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, acceptance, or the decision to proceed.
Security & Access Control
Data transfer, user access, network connectivity, approved site communications, write permissions, and support access 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
If cloud connectivity or BMS communication is interrupted, ClimaMind falls back to the approved BMS/manual path, pauses new supervised writes for the affected scope, and resumes only after telemetry, approvals, and safeguards are revalidated.
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 cloud 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