8,760-hour cooling & power analytics
Your power envelope has one weak point: your mechanical cooling (AKA chiller plant). It drives your peak PUE, and on the hottest afternoon of the year it decides how much IT your site can carry. IceBrick changes how that cooling operates — in a way no other system can. Give us a few details about your data center and we'll run all 8,760 hours of your year to show you exactly how much headroom you can reclaim: typically 5–15% more IT capacity behind the grid connection you already own.
Aside from compute, weather is the single biggest driver of cooling cost. Click the hub closest to your site — we will synthesize 50 years of hourly dry-bulb and wet-bulb from that location's climate normals.
Every project starts from one of two numbers — the substation connection you were offered, or the IT nameplate you want to install. Type yours into its box and continue from that box: the other quantity is derived for you at the design day. The two sliders below the boxes apply to both paths.
Pick the cooling cascade that matches your plant. This decides how much of the year is free, how much runs on water, and how much lands on a compressor.
This decides what the next question even means. A liquid hall has a CDU between your facility loop and the chips, and the temperature that matters is the one the cold plates are promised. An air hall has chilled water going straight to coils, and the temperature that matters is what leaves the plant. Pick one and we will draw your loop.
Your IT does not see facility water — it sees whatever comes out of the CDU, one heat exchanger later. So we ask for the number your racks are promised and the step the CDU adds — the SLA ceiling comes on the next page, where IceBrick makes it usable. Facility water is then whatever the plant has to make to deliver it, and that is the loop the entire before analysis runs on.
This simulator runs two distinct advanced thermal-management methodologies, for two separate use cases. The IceBrick system can be deployed as a means of acquiring power flexibility — a firm curtailment you commit to the grid for a demand-response event — or to optimize your power envelope — more IT behind the connection you already own, every hour of the year. Pick the use case; the questions that follow describe your plant, and the same weather, the same chiller and the same 8,760-hour baseline serve either one.
Utility calls are usually 13:00–19:00 and run four hours. The store is sized to what the night before can freeze under your own operational limit; the grid picks which ten hours of the year we show you first.
The same loop with IceBrick tied in at the CDU. Watch the same spike again: the DCIM sees it the moment it starts, IceBrick is dispatched, and the cold wave reaches the CDU HX ahead of the heat — the hall never feels the hour. That interception, guaranteed under SLA, is what lets you commit to the warmest supply your rack architecture allows.
This is the baseline operating matrix we will simulate. Change anything you like — you can also come back and re-run with different answers at any time.