Advisory mode
ClimaMind can begin by recommending setpoint changes without writing to the BAS.
01
Add an AI control layer above your existing BAS to optimize chillers, pumps, cooling towers, and selected setpoints as one coordinated system.
Retained
Existing BAS
Maintained
Operator authority
What we optimize
The solution is designed around the operating system you already have in the field, then extended with supervisory logic that can coordinate the assets that matter most.
A supervisory layer evaluates live conditions and recommends plant-level setpoints without replacing existing controls.

The BAS remains the operating interface and native control layer. Operators keep visibility, overrides, and local authority.
ClimaMind focuses on the assets that drive plant energy: chillers, pumps, towers, storage, and selected system setpoints.
Adjacent systems stay outside the optimization boundary unless they are explicitly mapped into the deployment scope.
Secure intervention
Before AI writes to the BAS, ClimaMind can start in advisory mode, define hard limits, apply bounded tuning steps, and preserve a clear path back to native BAS control.
ClimaMind can begin by recommending setpoint changes without writing to the BAS.
01
Commands outside authorized equipment limits are rejected automatically.
02
Gradual, rate-limited adjustments avoid aggressive transients.
03
Operators can return control to BAS while fail-hold preserves safe operation.
04
Deployment path
Optimize inside guardrails; keep BAS control.
Step 1
Capture schematics, equipment inventory, point lists, and control boundaries before any write path is enabled.
Step 2
Deploy a site-resident edge appliance that reads the live system and integrates with the existing BAS architecture.
Step 3
Define authorized points, approval steps, rate limits, and fallback behavior with site operators in the loop.
Step 4
Move from observation to controlled optimization at the pace the site can support, with rollback visibility preserved.

Operational guardrails
The operating model keeps native BAS authority and human takeover inside the same frame as the AI layer.
How value is measured
Measurement fits the site's operating constraints, metering, and commercial boundary so results can be reviewed by operators and sponsors.
Used where site operations allow a controlled comparison between baseline and optimized operation.
Used when direct A/B cycling is not practical and the site needs a baseline-based reporting path.
Ties plant performance back to the metering and utility context the customer actually manages.
Keeps the setpoint and operating record available so measured outcomes can be tied back to runtime decisions.
Meter-aligned
Energy reporting
Utility-aware
Cost reporting
The measurement package depends on site conditions, available data, and the agreed commercial boundary.
Commercial model
Shared savings is the default. Cooling-tonnage pricing is reserved for long-term customers or sites with special procurement requirements.
Default
Payment aligns to measured savings when the site boundary and reporting data support it.
Long-term / special requirements
Available when a fixed cooling-tonnage basis fits a long-term customer relationship or procurement requirement better.
Where it fits
The control layer stays conceptually consistent even when the facilities and operating constraints change.

Central cooling systems serving multi-tenant or comfort-sensitive operations.

Multi-asset environments with varying loads across buildings or thermal loops.

Reliability-sensitive environments that need explicit oversight and fallback paths.

Cooling infrastructure where operator control boundaries and measurable outcomes both matter.
Deployment-readiness briefing
Review control scope, guardrails, and measurement approach with our team before any closed-loop rollout.