The 30-Day Pilot

From first BMS connection to first savings invoice — 30 days.

No hardware orders. No change management tickets. No commitments before you see the data. Here is exactly what happens, day by day.

Start the pilot
Days 1–7 read-only observation, zero commands
Days 8–14 thermal model built, your team reviews
Days 15–30 supervised then autonomous optimization
Phase One

Days 1–7: Read-Only Connection

We establish a read-only BACnet/IP or REST API connection to your BMS. Celaxis passively observes zone temperatures, setpoint history, and occupancy signals — every 5 minutes, around the clock.

No commands are issued. Your BMS operates exactly as it did before. Your operations team receives a daily observation report: here is what we are seeing in your building's thermal behavior.

The BMS connection credentials require only read permissions on zone data objects. Most facilities complete this step in under 2 hours.

Day 1
BMS connection established
Read-only credentials configured. Zone data stream begins.
Days 2–6
Passive observation period
Celaxis records zone temperature, setpoints, occupancy states. No intervention.
Day 7
Observation report delivered
Plain-language summary of what we've learned about your building so far.
Phase Two

Days 8–14: Thermal Model Build

Using the 7-day observation dataset, Celaxis constructs the per-zone thermal inertia model. Your facilities team receives a plain-language summary of each zone's thermal characteristics.

"Zone 3A (Southwest corner office, 8,000 sq ft) needs 2.5 hours to pre-cool from 76°F to 70°F when outdoor temp exceeds 85°F."

Your team approves the model before any control actions are issued. If anything looks wrong, you flag it and we adjust.

Thermal Model Summary — Building 4
Zone 3A — SW corner 2.5h / 6°F
Zone 1B — North open plan 1.8h / 6°F
Zone 2C — Conference 0.9h / 6°F
Zone 4D — Lobby atrium 3.1h / 6°F
Model status: pending your approval
Phase Three

Days 15–21: Supervised Control Start

Celaxis begins issuing setpoint commands — all logged and visible in the dashboard in real time. Your facilities team can override or pause any action with one click. The system defaults to conservative setpoint deltas (max 2°F per action) in the first week.

Comfort complaint reporting is built into the dashboard. If any room temperature complaint is logged, Celaxis automatically adjusts the affected zone model.

"Every command we send, you can see. Every command you can override."
The override button is always available — no cooldown, no approval required.
Day 15
First setpoint command issued
Conservative +/-2°F delta. Full dashboard visibility.
Days 16–20
Supervised optimization continues
Team reviews daily action logs. Comfort feedback loop active.
Day 21
Week-3 check-in
Preliminary savings data shared. Your team approves full optimization mode.
Phase Four

Days 22–30: Full Optimization

After three weeks of approved operation, Celaxis operates autonomously within your approved setpoint bounds. The thermal model is now calibrated with real control data, not just passive observation.

End of Day 30: first savings report generated. kWh baseline vs Celaxis-optimized, peak demand charge avoidance, estimated monthly savings extrapolated from pilot data.

We send this report regardless of whether you continue — no obligation. The data is yours.

Day 30 Report Preview
Baseline energy cost (30-day) $8,420
Celaxis-optimized cost $5,590
Savings — Month 1 $2,830
Annualized projection $33,960
Illustrative pilot data. Methodology: 90-day weather-normalized baseline.

Questions facilities teams ask before the pilot starts

Your BMS reverts to its existing fixed schedule — the same behavior as if Celaxis never existed. Every setpoint Celaxis writes uses BACnet priority level 10 (manual-operator), which expires and releases to lower-priority schedules if Celaxis stops refreshing it. Fail-safe is built into the protocol, not just our software.
Comfort complaints in the pilot program: 0. Celaxis operates within setpoint bounds your team approves. Pre-cooling means the building is at comfortable temperature before occupants arrive — often more comfortable than the post-setback recovery period under the old schedule.
Predictive pre-conditioning typically reduces short-cycling — the rapid on-off cycling that causes the most mechanical wear. Instead of the BMS toggling HVAC on and off at occupancy transitions, Celaxis runs a longer, lower-intensity pre-conditioning cycle. Most HVAC contractors who review Celaxis pilot data note the run-time pattern looks healthier than the reactive cycling it replaces.
Yes. The Portfolio and Enterprise plans support multi-building management from a single dashboard. Each building gets its own thermal model — there is no shared model that could transfer wrong behavior from one building to another.
HVAC setpoint control is the primary optimization — this is where peak demand savings are largest. Lighting zone dimming schedule optimization is available on Portfolio and Enterprise plans, using the same occupancy model and BACnet command channel.
Celaxis retains BMS telemetry for up to 90 days for model training and reporting. After 90 days, raw telemetry is aggregated into monthly summaries and the raw stream is deleted. We do not share operational data with third parties.
Read-only credentials for the observation phase — access to zone temperature, setpoint, and occupancy object types only. Write credentials are added at Day 15 with your explicit approval, scoped to setpoint objects within the min/max bounds your team defines. No admin credentials, no controller-level access.

Start the 30-day pilot on one building.

No hardware purchase, no contracts, no commitment. First month is free — and we walk you through the BMS connection ourselves, usually in under two hours. If the savings data at Day 30 doesn't justify continued use, you cancel and nothing is charged.

Connect a Building