Annual simulation

Every run against a weather year happens in a building tab. Simulate this system, under Solve on a system tab, hands the machine to one — on its own, or serving the rooms you give it — and it runs as it stands, nothing saved first.

WeatherWeather year, over the scene: fetch a real typical meteorological year for 51 major cities (PVGIS © EU/JRC), generate a labelled synthetic design year, or import an hourly CSV mapped by column names.

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 on the system tab and saved with the system.

SweepA machine with no room to serve runs 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 kept per account, as many as the plan holds — reopen any dashboard from Runs, over the scene.

Whose a weather year is. A fetched city year is shared by every account. A year you generate or import is your account's own — listed for nobody else, 25 at most, yours to delete — and adding one takes a plan that can simulate. A fetched year runs in the city's standard time — PVGIS labels it in UTC and the app rotates it — so an occupancy written 07–19 lands on the local day and the sun peaks at noon; an imported CSV's hours are taken as local, and an optional ghi irradiance column feeds solar gains (what a file must be).

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. A report is a solve too: it costs one solve for its design point and one for each extra design point it tabulates, 12 at most. No plan caps how large a system may be — a bigger one costs more tokens rather than being refused — and the engine itself refuses a graph of more than 500 components. Nothing is charged for a request refused before it is solved. Every tier has a monthly allowance; top-ups (500 for $10) never expire.

← Solving & resultsBuilding simulation →