FAQ
Technical
Does the AI layer compromise the stability of the existing BMS or plant control?
ClimaMind runs in parallel with your BMS. Every command is constrained by multi-level safety limits and rate-of-change policies. If telemetry is out of bounds, the system reverts to the native sequence, and operators retain manual override at all times.
Technical
What part of the HVAC system do you optimize?
ClimaMind mainly focuses on central plant optimization, especially chiller-side systems. In some cases, we may interact with limited AHU-related control logic, but we are not focused on VAV-level or zone-level control. We work with the data and control points already available in the existing BAS/BMS environment whenever possible, and we generally do not require additional sensor deployment as a starting condition.
Technical
Do we need new sensors or significant hardware retrofits?
Most deployments reuse existing plant instrumentation—supply/return temperatures, flow, and power meters. We add a hardened edge server with UPS backup and networking gear but avoid intrusive sensor retrofits whenever possible.
Technical
How long before energy savings are measurable?
Once telemetry quality, safety limits, and operator approvals are validated, we enable reinforcement learning in a staged rollout. A 30-day alternating-day test or historical baseline comparison then produces auditable savings results.
Commercial
How do the CapEx and shared savings models differ?
CapEx projects are structured as a direct purchase of the edge platform and related services. Shared savings engagements let ClimaMind participate in the verified energy reduction, with commercial terms tied to the measurement plan, data access, and operating responsibilities agreed before deployment.
Commercial
How are savings calculated and validated?
We prioritize alternating-day comparisons—AI control one day, native control the next—using utility metering or plant power data. Where historical data is reliable, we also offer multi-year baseline models to satisfy ESG reporting requirements.
Technical
Can the platform run in the cloud?
Yes. ClimaMind can operate fully on-premises via the edge appliance or integrate with a secure cloud environment. Commissioning typically uses an isolated network segment with firewall rules that align to your cybersecurity policies.
Technical
Why does the web dashboard differ slightly from live BMS values?
The web UI is near real-time, not raw direct readout. Data passes through ingestion, quality checks, and aggregation, so short delays are expected. When discrepancies appear, compare the same point, unit, and timestamp window first.
Technical
Can operators issue control commands from the web portal?
Yes, based on role and site policy. Projects can run in read-only, advisory, or closed-loop mode. Any command-capable setup should enforce RBAC, approval workflow, and full audit logging before enabling production write access.
Technical
How are web alerts triggered and managed?
Alerts use threshold plus duration logic with anti-chatter filtering, rather than one-time spikes. Teams can acknowledge, assign, and close alerts with traceable logs, making incident handling auditable for operations and compliance reviews.
Technical
Can we export energy performance reports from the web portal?
Yes. The portal supports daily, weekly, and monthly summaries with exportable charts/tables. For external reporting, include the baseline method and weather normalization assumptions so savings claims remain consistent and review-ready.
Technical
Does the AI control system require a detailed first-principles model before go-live?
The rollout is staged. We start with model-driven optimization to provide stable, verifiable early performance, then introduce model-free reinforcement learning after sufficient site data is accumulated. This balances commissioning reliability with long-term adaptive savings.
Technical
What BAS or OT integration methods does ClimaMind support?
ClimaMind can support common BAS and OT integration methods including BACnet/IP, Modbus TCP, Modbus RTU, OPC UA, Snap7, HTTP API, and MQTT. The actual integration method depends on the site's BAS architecture, gateway capability, available point list, network segmentation, and write-permission policy.
Technical
What data leaves the site during a deployment?
Deployment can be configured for local-first operation. Remote access, cloud analytics, and report export are scoped with the owner, and only the approved telemetry, metadata, and performance summaries are transmitted. Credentials and customer network details are handled outside the public website workflow and should follow the site's security policy.
Technical
What happens if the edge device, network, or AI service goes offline?
The native BMS sequence remains the fallback control layer. If the edge appliance, network, or optimization service is unavailable, ClimaMind stops issuing new recommendations or commands and the plant continues under the approved local sequence. Recovery procedures are agreed during commissioning and recorded in the project runbook.
Technical
How do you protect comfort and operating constraints?
Optimization is bounded by site-specific comfort, equipment, and operations limits. We model hard limits, rate limits, deadbands, and operator-defined override rules, then review early recommendations before progressing toward automation. Comfort complaints, equipment alarms, and manual overrides are treated as control signals, not afterthoughts.
Commercial
What information do you need to start an assessment?
A useful first packet includes a point list, equipment schedule, recent trend logs, utility or plant power data, control narratives, floor or plant diagrams, and any known comfort or maintenance constraints. If those files are incomplete, the online intake form and walkthrough checklist help identify what is missing.
Commercial
Which sites are a good fit for ClimaMind?
The strongest fit is a site with meaningful HVAC energy spend, a central plant or coordinated air-side system, reliable metering, and a team willing to review measured results. Sites with no usable controls, no trend data, or unresolved equipment faults may need a controls or maintenance step before AI optimization is appropriate.
Commercial
Can ClimaMind work with our ESCO, controls contractor, or BAS vendor?
Yes. We can work alongside an ESCO, commissioning agent, controls contractor, or BAS vendor as the optimization layer above the existing automation stack. Clear ownership matters: the project should define who approves point access, who updates control logic, who reviews savings, and who responds to site issues.
Commercial
Do we need to replace our current controls vendor or BMS?
No. ClimaMind is designed as a supervisory layer over the existing control environment. If the current BMS can expose the required data and accept approved setpoint changes, the project usually focuses on integration, safety limits, measurement, and operator workflow rather than replacing the base controls system.
Technical
Which BAS/BMS platforms is ClimaMind compatible with?
ClimaMind does not require a specific BMS brand. We integrate through the site's existing BAS/BMS interface, typically BACnet/IP, BACnet MS/TP, BACnet/SC, Modbus TCP/RTU, OPC UA, MQTT, Haystack, vendor APIs, or a gateway provided by the controls contractor. Strong-fit platforms usually include Niagara, EcoStruxure, Metasys, Desigo CC, Honeywell WEBs, Distech EC-Net, JENEsys, WebCTRL, i-Vu, Delta enteliWEB, Trane Tracer, ABB Cylon ASPECT, and FIN. Final compatibility depends on point mapping, trend availability, write permissions, operator override, and IT/OT approval.
Commercial
How does ClimaMind pricing work?
ClimaMind can structure pricing around verified energy savings, so the customer pays from the value created rather than treating optimization as a traditional software-only purchase. Customers who agree to share approved operating data for product improvement may qualify for a discounted commercial arrangement. If detailed plant-level data sharing is not acceptable, the savings calculation can be based on the whole-building utility meter or other agreed main-meter evidence, with the baseline method documented before deployment.
Technical
How does ClimaMind avoid unsafe exploration?
ClimaMind does not perform unrestricted online exploration in real buildings. During deployment, control policies operate only within predefined safety boundaries. The system limits control actions such as equipment frequency, temperature setpoints, and equipment staging, while monitoring key operating variables such as water temperature, pressure, and indoor temperature and humidity. If the system approaches a safety boundary, sees abnormal input data, or detects unstable control behavior, it reduces optimization strength and can fall back to the existing BAS control logic or manual control. In high-reliability environments, comfort, equipment safety, and operational stability take priority.
Commercial
How does a first pilot usually start?
A first pilot should feel like a focused operating question, not a major building redesign. We start with the building's existing BAS data, point list, trend logs, equipment context, and metering evidence to establish a baseline and understand normal plant behavior. The project then moves through advisory validation before any limited closed-loop control is enabled on approved systems and points.
Commercial
Which HVAC systems are the best fit, and which are lower priority?
The strongest fit is usually a water-cooled central plant with multiple chillers, pumps, towers, usable BAS/BMS access, trend data, and reliable metering. These systems have enough coupling and energy value for supervisory optimization to matter. Sites dominated by RTUs, VRF/VRV, standalone equipment, no trend history, or no write permissions may still be evaluated, but they are usually lower priority for a first deployment.
Technical
Is ClimaMind just another dashboard, FDD tool, or commissioning service?
No. Dashboards and FDD tools help teams see issues, and commissioning can reset a building to a better operating state. ClimaMind is designed to go further: it connects BAS data, operating constraints, advisory validation, approved control actions, fallback behavior, and savings measurement into a supervisory optimization workflow. The goal is not only to observe the plant, but to help it keep finding efficient operating points safely.
Technical
How does ClimaMind address IT/OT security requirements?
ClimaMind provides an IT/OT security guideline covering network isolation, least-privilege writes, access control, audit logging, remote access, fail-safe behavior, and fallback mechanisms. The guideline is available from the ClimaMind website.
Technical
How does ClimaMind handle sensor faults or abnormal data?
ClimaMind includes abnormal data detection and degraded operation mechanisms. When sensor data is abnormal, drifting, missing, or failed, the system flags and filters the data rather than treating it as a reliable control input. When redundant or related points are available, they can be used for cross-checking or substitution. If no reliable substitute is available, the system reduces optimization strength, limits the relevant control authority, and can fall back to the existing BAS control logic or manual control.
Technical
Can ClimaMind's savings persist over long-term operation?
Based on ClimaMind testing and re-testing, we have not observed savings naturally decay simply because the system has been running longer. The system continues to adapt to changing site conditions while operating within approved safety boundaries.