Dedicated Behind-The-Meter Power For Data Centers

Standard air-cooled deployments are sized 100–300 MW per site, matching the typical density envelope of conventional data centers and most local permitting baselines. Liquid-cooled high-density deployments can scale up to 400 MW per site. Liquid cooling concentrates more compute, and therefore more power demand, into a smaller physical footprint, which raises per-site MW load and unlocks the economics for a larger generation set. Both architectures (modular 10 MW RICE units or combined-cycle gas turbines) scale to the upper end; the choice is driven by ramp behavior, redundancy preference, and operating profile rather than by capacity ceiling.

Outages, voltage instability, curtailments, and restoration timelines create SLA exposure and reputational damage. BTM turns power into dedicated infrastructure so availability is engineered and measurable.

BTM reduces dependence on multi-year transmission and substation upgrades. The schedule is driven by permitting, interconnect scope, and equipment lead times surfaced early.

We propose architecture against your actual load shape rather than forcing one technology onto every site. Modular 10 MW RICE units are well-suited to volatile ramp profiles, phased capacity, faster mean-time-to-repair, and rolling maintenance. Combined-cycle gas turbines are well-suited to steady, high-efficiency baseload at scale. Both can integrate CHP where beneficial.

With modular RICE topology, N+2 means the project is designed so the site can sustain its contracted delivery even with two engines out of service, subject to defined operating conditions and agreed outage classifications. With CCGT, N+2 is achieved through redundant trains and balance-of-plant design. In both cases, N+2 is a topology, not a slogan.

We align operating protocols and capacity blocks to ramp behavior so power delivery keeps pace with compute commissioning and tenant onboarding.

Availability is driven by balance-of-plant and electrical topology as much as engines. Modular generation, segmented MV architecture, protection coordination, essential UPS-backed controls power, and a critical spares strategy reduce single point failures.

We define A and B demarcation expectations at the POD, including protection responsibilities, routing assumptions, and metering so your internal distribution can remain concurrently maintainable.

Planned maintenance windows and notice requirements are defined in advance and coordinated around your operating calendar. Modular RICE topology supports rolling maintenance - individual engines can be serviced without taking the site offline.

We engineer the POD interface with appropriate MV design, protection coordination, and operating protocols aligned to your sensitivity to voltage and frequency events.

Operational playbooks define triage, escalation, restoration targets, communications, and reporting aligned to SLA terms so your team knows what happens at 2 a.m.

Restoration procedures are defined, and black start capability supports controlled restart after major events and predictable commissioning and re-commissioning behavior.

Availability suffers when critical components have long replacement timelines. A critical spares and replenishment strategy is planned, aligned to vendor service response. Modular RICE engines are smaller, more interchangeable, and faster to replace than large frame turbines, which materially reduces mean time to recovery.

Curtailment rights, settlement rules, and availability accounting are defined contractually. This is critical in constrained regions where curtailments can be frequent.

Sites are engineered so combined heat and power can be added without retrofit risk. For data center campuses with adjacent thermal loads, this is a real path to higher total energy utilization later without committing capital today.

Operating model, staffing expectations, maintenance planning, and reporting cadence are aligned to the SLA so reliability is backed by execution, not just design.

Optional cyber-isolated control architectures with segmentation and hardened interfaces can be tailored to hyperscaler and enterprise security standards.

Tier certification applies to the facility topology. We support Tier III-style architectures by delivering a defined POD boundary and a contractable SLA, while your UPS and standby generation strategy governs ride-through and facility-level redundancy.

We define an SLA at the POD with availability math, outage hour definitions, planned maintenance windows, exclusions, and remedies suitable for procurement and finance diligence.

We provide a clear POD boundary definition, metering approach, SLA framework, permitting plan, and milestone schedule suitable for internal approvals and lender diligence.

Revenue-grade metering at the POD and transparent settlement definitions reduce invoice friction and enable audit-ready reconciliations and tenant pass-through structures.

Pricing can be fixed, indexed, capped, collared, or hedged depending on how you want to allocate fuel and basis risk.

The POD demarcation defines equipment responsibility, protection responsibility, outage classification, and communications requirements so there is no ambiguity in performance accounting.

Capacity is delivered in modular 10 MW increments so you can match commitments to real tenant and compute growth timing and avoid overbuying early. Modular RICE topology makes this especially clean - additional 10 MW units are added as the load grows.

In many markets, data centers are increasingly framed as a driver of local rate pressure. That can become mandatory grid upgrade funding, take-or-pay obligations for new generation built on your behalf, and stricter scrutiny of incentives and local impacts. BTM reduces dependence on contested grid buildouts.

We plan for higher scrutiny on incentives and local impacts. Project disclosures and stakeholder engagement are structured early to avoid late-stage schedule disruption.

Water, noise, and community impacts are common permitting leverage points. Site design and mitigation planning address these early.

We provide the technical boundary, commercial structure, and milestone plan needed to move from exploratory discussions to a term sheet and defined execution path.