LOW KAH YIENGINEER & SYSTEMS THINKER
Appearance
Contact
← Critical Systems Lab

EXPERIMENT 01 / COOLING & RESILIENCE

Heat rises.
What happens next?

Three cooling units. A changing heat load. One decision at a time. See why spare capacity and a good response both matter.

CHOOSE YOUR EXPERIENCE

PREDICT → OBSERVE → INTERVENE

One unit down.
What would you change?

At 60 seconds, heat load rises to 440 kW. At 120 seconds, one of three 200 kW cooling units fails. Will the zone cross 27°C within ten minutes?

1 / Make a prediction

Choose a prediction to begin.

Start with a scenario
SYNTHETIC FACILITY / THERMAL MODEL 02600 s
UNIT 1AVAILABLEUNIT 2AVAILABLEUNIT 3OFFLINESHARED THERMAL ZONE24.0°CTARGET 24°C / LIMIT 27°C3 × 200 kW UNITS · ILLUSTRATIVE CAPACITY
Heat arriving
360kW
Heat removed
363kW
Available capacity
400kW

Temperature through the event

28.0°25.5°23.0°27°03 min6 min10 min
━ Selected scenario┄ All 3 units available┄ 27°C limit

60 s: heat load changes. 120 s: selected units remain available.

Peak temperature
24.75°C
Time above 27°C
0 s
Capacity minus load
40 kW
Recovery after 120 s
61 s

Results cover the full 600 s run. Recovery means within ±0.5°C of 24°C for the rest of the run, with at least 30 s remaining. Capacity reserve is not a redundancy certification.

Inspect the numeric results
Samples at 60-second intervals. Export CSV for the complete 0.5-second trace.
Time (s)Temperature (°C)Heat load (kW)Cooling (kW)Capacity (kW)
024.00240240.0600
6024.00360240.0600
12024.75360346.5400
18024.50360399.2400
24024.11360396.2400
30023.87360370.3400
36023.88360350.4400
42023.99360350.2400
48024.05360358.6400
54024.03360363.4400
60024.00360362.5400

OPEN THE ENGINEERING NOTEBOOK

A heat balance you can inspect.

This independent experiment uses a single, well-mixed thermal zone with an effective heat capacity of 6,000 kJ/K. It begins at 24°C with a 240 kW heat load and matching cooling. Each of three idealized units can remove up to 200 kW.

C · dT/dt = Qload − Qcooling

A PI controller requests cooling from temperature error. Equipment responds with a first-order lag. Output is limited to the available units, with conditional integration to avoid windup. The 27°C limit is an illustrative scenario threshold, not an operating recommendation.

Sequence of operations & model assumptions
  1. Start at thermal equilibrium, with all three units available.
  2. At 60 s, change heat generation to the selected load.
  3. At 120 s, restrict available cooling to the selected unit count. Removed units contribute no further cooling.
  4. Continue to 600 s. Compare with the same controller and load while retaining all three units.

Responsive tuning: Kp = 100 kW/K, Ki = 2 kW/(K·s). Gradual tuning: Kp = 45, Ki = 0.4. Equipment lag is selected independently: 12 s or 45 s. Changing tuning leaves the equipment unchanged. Version 1 links retain their original paired settings. Controller updates every 0.5 s; cooling lag and its heat removal integral are evaluated analytically within each step.

Points list & acceptance checks

Points: zone temperature (°C), heat load (kW), requested cooling (kW), delivered cooling (kW), available capacity (kW), and elapsed time (s).

Automated model checks cover equilibrium, saturated heat balance, event boundaries, capacity constraints, numerical convergence and exact reproduction from a versioned link. Browser checks exercise scenario changes, numeric inspection, sharing and keyboard access.

What this model leaves out

No spatial hotspots, humidity, airflow, hydraulic network, heat-exchanger curves, ambient conditions, electrical failures or equipment-specific protection logic are modeled. There is no calibrated facility or operating dataset behind it. Cooling capacity is held constant within each equipment state. Use the experiment to explore a trade-off, not to size equipment or establish a redundancy rating.

Why this runs in your browser

A dedicated Web Worker computes the simulation while the page remains available for interaction. The initial result is rendered as HTML and SVG. Scenario links contain only versioned settings; running or sharing an experiment requires no account or cloud save.