VR2-0510

① SA Source

Context Before

Source: CoolIT

The shift from liquid + air to 100% liquid systems, combined with higher flow rates and greater cooling capacity, will require changes across the cooling stack. Fans and radiators used in L2A CDUs will become less critical over time. That said, L2A is likely to maintain meaningful share during the current upcycle, where deployment speed matters more than full optimization, though the long-term trajectory clearly favors L2L. High-density L2L systems will also require redesigns across much of the TCS. This includes updated manifolds, larger quick disconnects (Colder Products Company, Danfoss, Staubli, Parker Hannifin), gold-plated cold plates (AVC, Delta, Boyd, CoolIT, Auras) and, very critically, larger pumps capable of delivering the required water volume. Pump sizing is directly linked to power density and the heat that must be removed. Even manufacturers of motor and drive components used in these pumps, such as Allegro MicroSystems, could see their prospects change as either larger motors, more motors, or both are required. In summary, higher heat on the TCS loop likely increases content/MW for white-space cooling vendors. QDs should benefit most, alongside manifolds and cold plates, with CDUs also benefiting, though to a lesser extent.

Evidence

SPX Technologies, alongside BAC and Evapco, could benefit, while Johnson Controls, Carrier, and Trane may be challenged

Context After

Rack Level Infrastructure: Power Delivery

In the GB200 article from 2024 , we discussed the previous evolution on power delivery from node level PSU (power supply unit) to centralized rack level power shelf. As VR NVL72 rack TDP reaches 180kW-220kW per rack from 120kW-140kW for GB200 and GB300, the power delivery infrastructure has evolved yet again. In the section below we will discuss the power delivery infrastructure at the rack level of the reference design and the power delivery at the compute tray level for VR NVL72.

② Atomic Claim

SPX TechnologiesBACEvapco 可能受益;Johnson ControlsCarrierTrane 則可能面臨挑戰。

  • Epistemic Mode: HYPOTHETICAL
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "UNSPECIFIED_ATTRIBUTE",
  "context_nodes": [
    {
      "id": "02_companies/Baltimore Aircoil Company",
      "label": "BAC"
    },
    {
      "id": "02_companies/Evapco",
      "label": "Evapco"
    },
    {
      "id": "02_companies/Johnson Controls",
      "label": "Johnson Controls"
    },
    {
      "id": "02_companies/CARR",
      "label": "Carrier"
    },
    {
      "id": "02_companies/TT",
      "label": "Trane"
    }
  ],
  "entity": {
    "id": "02_companies/SPXC",
    "label": "SPX Technologies"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "SPX Technologies、BAC 與 Evapco 可能受益;Johnson Controls、Carrier 與 Trane 則可能面臨挑戰。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entitySPX TechnologiesSPXC
context_0BAC02_companies/Baltimore Aircoil Company
context_1EvapcoEvapco
context_2Johnson Controls02_companies/Johnson Controls
context_3CarrierCARR
context_4TraneTT

⑤ Human Review

請在 Properties 逐項確認:

  • 原文 → Atomic Claim 是否忠實
  • Atomic Claim → Semantic Frame 是否忠實
  • Canonical Entity mapping 是否正確
  • Epistemic mode 是否保留原文語氣
  • 最後選擇 review_action

Review state

Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。