Annual simulation
Every run against a weather year happens in the Simulate tab. Hand the Design canvas off with one click — it arrives as a machine serving a default room and runs as it stands, nothing saved first.
WeatherFetch a real typical meteorological year for 50 major cities (PVGIS © EU/JRC), generate a labeled synthetic design year, or import hourly CSV mapped by column names (an optional ghi irradiance column feeds solar gains).
ControlA machine serving rooms runs under full load-following control — automatic staging (ventilation → evaporative → mechanical; heating with a heater present), compressor modulation, the room's own closed-loop demand. The machine's strategy — SZVAV, custom stages, stage policy — is declared in the Design tab and saved with the system.
SweepOr run the handed-off system flat out every hour with no control: an equipment characterization across the year, with the same dashboards.
Run8,760 hourly solves in a few seconds. Dashboards: monthly energy/water, operating-mode hours, supply-temperature distribution, unmet hours.
RevisitCompleted runs are saved per account — reopen any dashboard from "Previous runs".
Compute tokens meter everything the engine does, and both rails price by size. A point solve costs 1 token per ten components, so an ordinary machine is one. A simulated year is 8 760 of those solves, so it costs 10 times what one solve of the same system costs — ten tokens for an ordinary machine, more for a large plant. There is no cap on how large a system may be: a bigger one costs more tokens rather than being refused. Every tier has a monthly allowance; top-ups (200 for $10) never expire.