|
62 | 62 | padding-block: clamp(2.5rem, 5vw, 4rem); |
63 | 63 | border-bottom: 1px solid var(--rule); |
64 | 64 | } |
| 65 | +.figure-row { |
| 66 | + display: grid; |
| 67 | + grid-template-columns: 1fr 1fr; |
| 68 | + gap: 1.25rem; |
| 69 | +} |
| 70 | +@media (max-width: 820px) { .figure-row { grid-template-columns: 1fr; } } |
65 | 71 | .figure { |
66 | 72 | background: var(--bg-raised); |
67 | 73 | border: 1px solid var(--rule); |
@@ -185,26 +191,97 @@ <h2>Designed from the panel out.</h2> |
185 | 191 | <p>Everything visible in the diagram above was designed by us. Every wire, every module, every addressable point.</p> |
186 | 192 | </div> |
187 | 193 | </div> |
| 194 | +</div> |
| 195 | + |
| 196 | +<div class="figure-section"> |
| 197 | + <div class="wrap"> |
| 198 | + <div class="figure"> |
| 199 | + <img src="../assets/case-studies/milton-hilton/cameras-exterior.jpg" alt="Exterior camera coverage plan for the Milton Hilton campus, showing placement and coverage cones for existing and newly installed cameras around the building perimeter"> |
| 200 | + <div class="cap"> |
| 201 | + <span class="label">Fig. 03 — Exterior camera coverage plan</span> |
| 202 | + <span>Perimeter · parking · loading docks</span> |
| 203 | + </div> |
| 204 | + </div> |
| 205 | + <div class="figure-row" style="margin-top:1.25rem"> |
| 206 | + <div class="figure"> |
| 207 | + <img src="../assets/case-studies/milton-hilton/cameras-floor-1.png" alt="Floor 1 interior camera coverage plan — camera placements and coverage cones across common corridors, entrances, and shared areas"> |
| 208 | + <div class="cap"> |
| 209 | + <span class="label">Fig. 04 — Floor 1 interior</span> |
| 210 | + <span>Common areas</span> |
| 211 | + </div> |
| 212 | + </div> |
| 213 | + <div class="figure"> |
| 214 | + <img src="../assets/case-studies/milton-hilton/cameras-floor-2.jpg" alt="Floor 2 interior camera coverage plan — camera placements and coverage cones across shared corridors and common spaces on the second floor"> |
| 215 | + <div class="cap"> |
| 216 | + <span class="label">Fig. 05 — Floor 2 interior</span> |
| 217 | + <span>Common areas</span> |
| 218 | + </div> |
| 219 | + </div> |
| 220 | + </div> |
| 221 | + </div> |
| 222 | +</div> |
| 223 | + |
| 224 | +<div class="wrap"> |
| 225 | + <div class="cs-section"> |
| 226 | + <div class="lbl">§ 03 · Security</div> |
| 227 | + <div> |
| 228 | + <h2>Camera and access coverage, engineered.</h2> |
| 229 | + <p>Before a single camera was installed we produced coverage plans at floor-by-floor and exterior scale. Each camera's field of view was laid out over the architectural drawings so every corridor, entrance, loading dock, and shared space had intentional coverage — and so the gaps were visible and deliberate, not accidental.</p> |
| 230 | + <p>The system combines new common-area cameras with the existing cameras already approved for the site. Same recording infrastructure; same review console; one archive. Access control runs on top of the same backbone — card-based entry with tenant-specific profiles, audit logging, and integration with the camera feeds.</p> |
| 231 | + </div> |
| 232 | + </div> |
| 233 | +</div> |
| 234 | + |
| 235 | +<div class="figure-section"> |
| 236 | + <div class="wrap"> |
| 237 | + <div class="figure-row"> |
| 238 | + <div class="figure"> |
| 239 | + <img src="../assets/case-studies/milton-hilton/power-present.jpg" alt="Present power schematic showing generator transfer switch, battery system with inverter, and UPS feeds to the three data rooms while the site is running on generator power"> |
| 240 | + <div class="cap"> |
| 241 | + <span class="label">Fig. 06 — Present schematic · on generator</span> |
| 242 | + <span>Generator · batteries · UPS feeds</span> |
| 243 | + </div> |
| 244 | + </div> |
| 245 | + <div class="figure"> |
| 246 | + <img src="../assets/case-studies/milton-hilton/power-future.jpg" alt="Future power schematic showing the expanded dual-battery configuration with transformer-fed night-light panels and a second battery inverter ready for installation"> |
| 247 | + <div class="cap"> |
| 248 | + <span class="label">Fig. 07 — Future schematic · expansion path</span> |
| 249 | + <span>Dual batteries · transformer-fed loads</span> |
| 250 | + </div> |
| 251 | + </div> |
| 252 | + </div> |
| 253 | + </div> |
| 254 | +</div> |
| 255 | + |
| 256 | +<div class="wrap"> |
| 257 | + <div class="cs-section"> |
| 258 | + <div class="lbl">§ 04 · Power resiliency</div> |
| 259 | + <div> |
| 260 | + <h2>Batteries, generator, and a plan for more.</h2> |
| 261 | + <p>The campus has three data rooms, each with its own UPS. Behind those UPSes is a coordinated battery inverter and a standby generator. The transfer switch and controls were designed so that, from the servers' perspective, the site never loses power — the UPS carries through the cutover, the batteries take over from the UPS, and the generator takes over from the batteries as it comes online.</p> |
| 262 | + <p>The <b>Present schematic</b> above shows the installed system: one battery inverter tied to the generator control panel, a 600V→208V transformer, and discrete 60-amp feeds to the data-room UPSes and night-light panel. The <b>Future schematic</b> shows the planned expansion — a second battery system (Battery02) with its own inverter and transfer switch, repurposed night-light master panels, and a second transformer — all designed in now so the expansion drops in without rewiring the plant.</p> |
| 263 | + </div> |
| 264 | + </div> |
188 | 265 |
|
189 | 266 | <div class="cs-section"> |
190 | | - <div class="lbl">§ 03 · Full scope</div> |
| 267 | + <div class="lbl">§ 05 · Full scope</div> |
191 | 268 | <div> |
192 | 269 | <h2>Everything the campus runs on.</h2> |
193 | | - <p>Agentic HVAC is the differentiator, but it is not the whole delivery. We built the full technology backbone of the building:</p> |
| 270 | + <p>Between the HVAC plant, the control systems, the security coverage, and the power resiliency above, plus the rest:</p> |
194 | 271 | <ul> |
195 | 272 | <li><b>Network & WiFi</b> — Campus-wide managed switching, structured cabling, tenant segmentation, full coverage across the 240,000 sq ft footprint.</li> |
196 | | - <li><b>Servers & compute</b> — Core services, tenant-shared and tenant-isolated compute, monitoring, and backup.</li> |
| 273 | + <li><b>Servers & compute</b> — Three data rooms with core services, tenant-shared and tenant-isolated compute, monitoring, and backup.</li> |
197 | 274 | <li><b>Routers & firewalls</b> — Tenant isolation with shared, metered internet egress.</li> |
198 | | - <li><b>IP camera system</b> — Full interior, exterior, parking, and loading-dock coverage with archival recording.</li> |
| 275 | + <li><b>IP camera system</b> — Full interior, exterior, parking, and loading-dock coverage, planned as shown above.</li> |
199 | 276 | <li><b>Access control</b> — Card-based entry with tenant-specific profiles, audit logging, and integration with the camera system.</li> |
200 | | - <li><b>Power resiliency</b> — UPS capacity for critical loads plus a generator sized to carry the full building through extended outages.</li> |
201 | | - <li><b>HVAC</b> — The 250-ton water-source heat pump system and its agentic controller described above.</li> |
| 277 | + <li><b>Power resiliency</b> — UPS per data room, coordinated battery inverter system, and a generator sized to carry the full building through extended outages.</li> |
| 278 | + <li><b>HVAC</b> — The 250-ton water-source heat pump system with full energy recycling and its agentic controller.</li> |
202 | 279 | </ul> |
203 | 280 | </div> |
204 | 281 | </div> |
205 | 282 |
|
206 | 283 | <div class="cs-section"> |
207 | | - <div class="lbl">§ 04 · Role</div> |
| 284 | + <div class="lbl">§ 06 · Role</div> |
208 | 285 | <div> |
209 | 286 | <h2>Architect, designer, builder.</h2> |
210 | 287 | <p>We handled every layer of the delivery — from the mechanical and electrical design of the HVAC plant to the racks in the IDF closet to the software running on the control supervisor. One accountable practice for the whole building.</p> |
|
0 commit comments