Synapse Thermal Portal
Synapse Thermal
/Garrison Data Partners·Halls A–Cillustrative data
Ingestionread-only · day 90/90
/dashboard

Facility headroom, verified

Signed capacity for Garrison Halls A–C, the capital it lets wait, and the live feed behind both. Nothing below was changed on site: the study was read-only for 90 days.

Zone headroom at design condition

Signed Oct 18, 2026
Current IT loadSafe additionalAgreed margin M(z)Track = verified limit of the binding path

Live ingestion stream

simulated feed · 2 s cadence
    Production pulls these records from the demo.synapsethermal.com ingestion engine (BMS, PDU, CRAH and CDU points). The engine requires sign-in, so this prototype generates records with the same shape. Click a point id to open it in the engine.

    Capital waiting on verified headroom

    Open simulator

    Method status

    4 / 4 steps complete
    /telemetry

    Telemetry engine

    The ingestion engine at demo.synapsethermal.com holds every raw point behind the signed table. It opens in its own tab with its own sign-in; the portal links into it by zone, point and time window.

    API reference Open telemetry engine ↗

    Connection

    reachable

    Access

    operators

    Link scheme

    Edit in setup

    Open by zone

    links carry zone, point and window; the engine applies its own sign-in

    Study, API and health

    How to sign in

    first open only
    1

    Open the engine from any link on this page

    It opens in a new tab. The browser shows the engine's own sign-in prompt (HTTP Basic, realm "Synapse").

    browser
    2

    Enter the operator credentials issued with the study

    Credentials come from Synapse Thermal with the facility's onboarding pack; the portal never asks for or stores them.

    operator
    3

    Later links open directly

    The browser keeps the session, so zone and point links from the dashboard, certificates and the DRL module land on the right view without a second prompt.

    done
    /capacity/signed-table

    Signed safe-kW table

    One row per zone. Each names the element that binds first, so the fix can be priced against the upgrade it delays. Capacity counts as released only when both the electrical path and the cooling zone verify.

    Release rule
    kWsafe(z) = min( Helec(z), Hcool(z) ) − M(z)

    H is the verified headroom of each path at the design condition; M is the safety margin agreed with the operator. Whichever term is smaller names the limiting factor. Edit M(z) in the table to see the rule recompute; any edit voids the signature until the verifier re-signs.

    Verification bounds

    Zone matrix

    Signed · digest verified
    Table digest (SHA-256 of canonical JSON): computing…
    /capex/deferral-calculator

    CapEx deferral simulator

    A verified table is worth most when it lets a purchase wait. The value of waiting is the present-value saving from paying later, set against the low-cost remediation that keeps the zone releasing kW in the meantime.

    Inputs
    V = C × ( 1 − 1 / (1 + r)t )
    Upgrade cost C$500K
    $50K$2.0M
    Cost of capital r10.0%
    2%20%
    Deferral period t1.0 yr
    3 mo5 yr
    Presets from the brief
    Deferral value
    Present-value saving from waiting
    $45.5K
    on a $500K purchase deferred 1.0 yr at 10%
    Deferral value by period
    V at current rV at r + 5 ptsHover for values

    Savings tracker · deferral vs. tactical remediation

    Values from the brief's illustrative case; r applies portfolio-wide
    /future-readiness/800v

    800 V DC transition planner

    The same release rule, evaluated per zone under three architectures. Projections come from the calibrated models; they narrow the range of outcomes but are not measurements.

    Where heat is rejected

    415 VAC · verified

    Thermal / electrical flip analyzer

    Limiting element per zone

    Headroom under scenario

    Verified · 415 VACProjected · selected scenario

    Remediation roadmap · build in now

    avoids post-lease retrofit
    /drl/orchestration

    DRL cooling forecasting & orchestration

    Thermal coupling works the same way in air and in liquid: more IT load raises return-air or return-water temperature, which raises fan or pump demand on the same electrical path. The forecast shows that overhead before it lands. On direct-liquid zones the controller also works the ΔT–flow trade at the CDU, which is where the verified limit sits. The pilot is offered only on zones the study proved cooling-limited.

    Tenant-side telemetry

    What the controller minimizes

    Cooling loop

    Capacity effect

    projection · re-verify before re-signing

    Control pilot

    Shadow mode
    Closed-loop control · off
    Recommendations are logged, nothing is actuated.

    Pilot results · since activation

    not active
    BMS baselineDRL-controlledkWh avoided
    Energy is the smaller pool. Pilot pricing at 10 racks put cooling-energy savings at roughly $2–16K a year; production work is priced against deferred capital and released kW. Direct-liquid loops are modeled from measured heat rejection (ΔT × flow) on the testbed, not vendor curves.
    /setup/facility

    Facility setup

    Everything a study needs before day 0: the zones in scope, the telemetry that feeds them, the terms the table is signed under, and who may see or control what. The open items from the scoping call live here, with their answers.