Milton Hilton § 03: add recording-stack details and scale numbers

Camera system is built on a Dell server with redundant power + CPU,
100 TB RAID 5+1, Windows Server on Hyper-V, and Blue Iris as the
recording engine. Scales to 500+ cameras with 90 days of full
retention, currently running 200+ covering every tenant. Per-camera
cost to deploy came in at less than half of traditional-NVR and
industrial-manufacturer alternatives. No fragile NVRs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: rmdevpro

case-studies/milton-hilton.html

@@ -198,6 +198,8 @@ <h2>Designed from the panel out.</h2>
       <h2>Camera and access coverage, engineered.</h2>
       <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>
       <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>
+      <p>The recording stack runs on enterprise server infrastructure — a Dell server with redundant power and CPU, 100 TB of RAID 5+1 storage, Windows Server on Hyper-V, and Blue Iris as the recording engine with open-source integrations where useful. <b>No NVRs</b> — those fail in exactly the moment you need them.</p>
+      <p>The architecture scales to over <b>500 cameras with 90 days of full retention</b>; today it runs over 200, covering every tenant in the building. Per-camera deployment cost came in at less than half of a traditional NVR build and less than half of the industrial-scale systems the major manufacturers sell for this size of site.</p>
     </div>
   </div>