Home / Case Studies / AiTBMS · HQ Tower Case Study · AiTBMS · Building Intelligence

Intelligent Group HQ Tower: 45,000 sq ft on AiTBMS Stage 3.

A Class A office tower needed live BMS visibility, sub-meter telemetry, and an audit trail that didn’t depend on a vendor portal. We deployed AiTBMS against ourselves first.

Book a 30-Min Walkthrough
← All case studies
Product AiTBMS — Stage 3 multi-tenant cloud + edge collector
Customer Intelligent Group HQ Tower (self-pilot)
Site 45,000 sq ft Class A office, NY metro
BMS Vendor Automated Logic WebCTRL

About Intelligent Group HQ Tower

Intelligent Group HQ Tower is a 45,000 sq ft Class A office building in the New York metro (timezone America/New_York) operated as the headquarters of Intelligent Group, the parent MSP behind Intelligent IT. The building runs Automated Logic WebCTRL across HVAC, lighting, and tenant sub-metering, and previously had no cloud-side telemetry, no historian beyond WebCTRL’s local trends, and no asset-level alerting that reached the operations team off-site.

It was selected as the AiTBMS Stage 3 pilot site for two reasons: (a) the engineering team controls both the BMS and the IT estate, so install windows are internal decisions rather than client gates, and (b) a self-pilot lets Intelligent IT prove the architecture against real loads before onboarding paying customers.

The Challenge

Before AiTBMS, every site condition that mattered — chiller faults, hot-aisle drift on the 14th-floor server closet, after-hours light schedules running through unoccupied space — was visible only to whoever was logged into the WebCTRL console on the controls server. Off-site staff had no way to see the building. Energy-efficiency conversations with the property manager stalled at “we think it’s running OK” because there was no normalized kWh-per-sqft trend, and no comparison against benchmark.

Three operational gaps drove the pilot: no cloud historian (so 30+ day trends required FTP-pulling raw .csv from the controller), no role-based dashboard for tenants vs. ownership, and no integrated alert path from BMS into the IT incident channel where the on-call rotation actually lives. Adding those one product at a time would have meant three vendor contracts, three identity stores, and three places for an alert to go missing. AiTBMS was scoped to consolidate all three into one tenant-aware platform.

The pilot also had to clear an internal bar: the new Windows service running on the WebCTRL server could not destabilize the existing controls workload, and the rollback path had to be a single uninstall script. A new Windows service on a controls server is treated as a BMS change — it lands in a low-occupancy install window with rollback ready.

The Solution

Intelligent IT deployed AiTBMS Stage 3 against HQ Tower over a single change window, plus a 24-hour soak. The architecture has three planes: (1) an edge collector — a Node-based Windows service installed via NSSM on the WebCTRL server, reusing the existing mssql driver the dashboard already shipped with; (2) a Supabase Pro project (us-east-1) holding tenant-aware time-series, alert state, and the trust portal schema; and (3) a Next.js 16 + React 19 dashboard hosted on Vercel, with the frontend’s lib/data.ts swapping between local fixtures and Supabase via a single DATA_SOURCE env var.

Identity is Clerk, organized one Clerk org per site, so when site #2 onboards no schema or auth refactor is needed — only a Clerk Pro upgrade for multi-org. The first heartbeat is verified within 60–90 seconds of installer run via the operator’s /internal/sites view (color flips green); if anything is anomalous in the first 24 hours, service/uninstall.ps1 cleanly removes the agent and archives logs. None of that was used — the pilot soak passed clean.

Results

Quantitative outcomes after the first full quarter on AiTBMS. Numbers below are templated against the pilot runbook; live metrics are confirmed with each release of the case study.

[X]%Energy reduction vs. pre-pilot baseline
[X] minMean alert acknowledgement time
[X]Faults caught before tenant complaint
0.5 hrInstall + 24h soak per site (operational benchmark)
1Sites onboarded under same architecture (capacity proof)
$[X]Avoided cost vs. 3-vendor stack

Templated metrics will be replaced with HQ Tower’s live numbers at end of Q2 2026.

What’s next

Stage 3.1 wires Clerk into a per-site org model and lights up tenant logins. Stage 3.2 adds the alert state machine — opened → acknowledged → resolved — plumbed into PagerDuty for Sev-1, Slack for everything else. Stage 3.3 introduces the three-tier oncall rotation (NOC, AiTBMS eng, Manuel as last-line). Stage 3.4 onboards site #2 against a per-site subdomain scheme (app.aitbms.intelligentit.io remains the org-level entry).

  • Multi-site rollout to additional buildings under the same Supabase tenant model
  • Sub-meter expansion: per-floor or per-tenant electrical metering with chargeback reports
  • CMMS integration: auto-create work orders from acknowledged BMS alerts
  • Trust portal lift-out to a dedicated Supabase project once data-sovereignty is requested

In their words

“We finally see the building. Before AiTBMS, the BMS lived inside one console; now the ops team sees a chiller fault before the tenant does.”

— Manuel Ruiz, Founder & CEO, Intelligent Group — pilot site sponsor

About Intelligent IT

Intelligent IT (a brand of Intelligent Group) is an MSP that ships AiT-branded SaaS products for building management (AiTBMS), customer ops (AiTCRM), customer success (AiTCSG), building compliance (AiTLEED), and SOC operations (AiT SOC Sentinel). We deploy them ourselves first, then to design partners, then to the market.

Want AiTBMS against your portfolio?

Pilots are scoped against one site, one BMS vendor, and one specific outcome you want to prove out.

Case study as of 2026-05-07. Templated metrics pending live-pilot confirmation. Manuel Ruiz, Founder. © Intelligent Group · intelligentit.io