Most surprises surface during the first 24 hours after a site goes live. The checks below catch the common ones: missing readings, wrong addresses, and a watchdog that has not been registered. Run them while there is still time to react, before the site has been operating for days with a hidden problem.

1. Confirm live readings are landing

Open Sites → your new site. Within a few minutes of completing the wizard, the Indoor Climate panel should start showing live values, and per-system readings such as supply and extract air temperatures and fan speeds should follow. If the panel stays blank, check the Frozen Sensors panel on the same page. It lists points that have stopped reporting, which usually points to a credential that lost authorisation or an address list CSV row that missed a controller unit.

2. Sanity-check the values

The numbers should look like the building: indoor temperatures in a normal range, supply air temperature responding to outdoor conditions, and fan speeds above zero during occupied hours. Suspiciously round numbers, such as always 0 or always 100, usually mean a stale or defaulted point. Flag it, and we will help track down which data point did not bind correctly.

3. Confirm setpoint writes (if you control setpoints)

For sites where the platform writes setpoints, open the Control Outputs and Control Logs panels on the site page. Control Outputs shows the values currently being written; Control Logs shows the write history with timestamps. Within an hour, you should see new entries arriving at a regular interval. If Control Logs is empty, the control loop never started. Usually this means a deployment step in Step 8 succeeded for the configuration but failed for the secrets, leaving the pod unable to authenticate.

4. Confirm the watchdog (IWMAC sites)

For IWMAC sites where the platform writes setpoints, confirm that IWMAC has registered the watchdog and that the Endpoints CSV from Step 7 was uploaded. The fastest test is to have your IWMAC contact confirm on their side that the watchdog tag is being refreshed at the expected interval. Without this, if our service ever pauses, the building stays on the last value we wrote. That is exactly the failure mode the watchdog exists to prevent.

5. Watch alerts for the first day

First-day issues are usually one of three things: an expired credential, a typo in the address list, or a sensor that never paired. None of these are catastrophic, but they get harder to chase the longer they sit. Frozen Sensors and Control Logs are the two surfaces that catch them earliest. Triage on day one keeps the site clean.

6. Re-run the BMS snapshot in a week

After about a week of live operation, re-run Step 5 (Operational Analysis) on the live site. The platform refreshes its picture of "normal" using a week of real data, and any defaults that were placeholders during onboarding are replaced with measured values. This is also a good moment to revisit any setpoints that felt arbitrary on day one.