Data Intake

Pre-deployment Data Intake

Before a ClimaMind deployment reaches the site, we build a usable operating picture from BAS trend exports, meter data, equipment schedules, control sequences, and the constraints your facilities team already works within.

The goal is not to ask for every possible file. It is to collect enough verified data to define the optimization boundary, measurement path, BAS touchpoints, and commissioning plan before any on-site work.

01

Scope the operating boundary

We first confirm which plant, air-side, storage, and metering systems are inside the deployment scope.

  • 01List chillers, pumps, towers, AHUs, storage, and major dependent loads.
  • 02Mark which systems stay outside the initial optimization boundary.
  • 03Capture operating schedules, seasonal modes, manual routines, and outage constraints.

02

Collect source data

The intake package combines existing exports with lightweight engineering context so we can assess feasibility before field work.

  • 01BAS trend exports for temperatures, flows, setpoints, status, commands, and alarms.
  • 02Meter data for electricity, thermal energy, steam, chilled water, or fuel where available.
  • 03Equipment schedules, design capacities, sequences of operation, and point lists.
  • 04Historical CSV exports when the site already has them available.

03

Validate quality and gaps

We check whether timestamps, units, naming, sampling intervals, and missing periods support modeling, commissioning, and M&V.

  • 01Normalize units and timestamps before comparing signals.
  • 02Identify missing sensors, stale points, duplicate point names, and flatlined trends.
  • 03Decide whether gaps require a site walk, temporary logging, or a narrower deployment scope.

04

Prepare deployment handoff

The output is a concise readiness package that informs on-site deployment, IPMVP M&V planning, and Trust & Security review.

  • 01Confirm BAS read and write candidates with customer approval.
  • 02Define the measurement boundary and baseline data needed for savings claims.
  • 03Prepare security review context without requesting sensitive access material through intake forms.

Collection checklist

What we ask for before deployment

The exact request is tailored to the building, but most central HVAC projects need these categories before an engineering decision is credible.

BAS trend exports

Time-series points that describe plant state, operator settings, equipment status, and control outputs.

  • Supply and return temperatures
  • Valve, damper, VFD, and setpoint trends
  • Equipment status, alarms, and mode indicators
  • Command histories where BAS exports include them

Meter data

Utility and submeter histories used to understand load, baseline behavior, and measurement options.

  • Electricity interval data
  • Thermal, chilled-water, steam, or fuel meters
  • Demand charges or tariff context when relevant

Equipment schedules

Asset lists and design information that connect point names to physical systems.

  • Chiller, pump, tower, AHU, and storage schedules
  • Design capacities, flows, efficiencies, and staging rules

Control sequences

Operating logic and site rules that define how the current BAS is supposed to run.

  • Sequences of operation
  • Reset schedules and lockout rules
  • Operator overrides and manual procedures

Intake form

Download the intake workbook

The current public intake workbook is available as Excel files in US and metric units. Use these files as a structured starting point; the exact request still depends on the site scope.

Central HVAC Data Intake Template (US Units)

Excel workbook for preliminary study data collection, with US HVAC units for chillers, pumps, boilers, cooling towers, terminal equipment, and historical CSV data requests.

Download file

Central HVAC Data Intake Template (Metric Units)

Excel workbook for preliminary study data collection, with metric HVAC units for chillers, pumps, boilers, cooling towers, terminal equipment, and historical CSV data requests.

Download file