HVAC Data Intake Template
A standardized data collection form for chillers, pumps, and terminal units to accelerate project scoping.
Resources
Resources
Share your project details and site photos through our simple online forms. We will take it from there.
Site Walkthrough Checklist
On-site checklist to capture control strategies, point counts, and comfort observations during commissioning prep.
ClimaMind One-Pager
Company overview and pilot path summary for commercial HVAC owners, operators, and local partners.
Need anything else? Email info@climamind.com and we will help right away.
FAQ
Practical answers for operators, engineers, and buyers.
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 include a perpetual license for the edge platform with optional service agreements. Shared savings engagements are 5-8 year partnerships where ClimaMind funds the deployment and is paid from verified energy reductions.
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
Which BAS or BMS protocols can ClimaMind connect to?
Projects usually start from the protocols and point maps already available at the site. Common integrations include BACnet, Modbus TCP/RTU, MQTT, and vendor gateways exposed by the existing automation layer. During scoping, we confirm readable telemetry, writable setpoints, network segmentation, and fallback permissions before any control mode is enabled.
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.