From the NVIDIA edition of September 21, 2026
NVIDIA launches DSX Ready to qualify BESS and CDU products for AI factories
NVIDIA · AI factory facilities / power and cooling ecosystem · Global (vendor program announcement)
- Publisher
- NVIDIA Blog
- Original publication
- September 21, 2026
- Source retrieved
- 2026-09-22
- Event date
- 2026-09-21
What happened
On Sep 21, 2026 NVIDIA launched DSX Ready, a qualification program for partner products that meet applicable DSX AI factory reference-design requirements, starting with battery energy storage systems (BESS) and cooling distribution units (CDUs). Initial qualified BESS names Hitachi Energy, LG Energy Solution and Tesla; initial CDUs name LG Electronics, LiquidStack and Vertiv. NVIDIA states category-specific requirements and review are meant to reduce integration risk, while explicitly warning that passing qualification does not replace site-level engineering or imply site-level stability. Additional infrastructure and software categories are planned over time.
Why it matters
Gives SLED facilities and procurement teams a vendor-curated shortlist language for power and liquid-cooling BOM alignment to DSX—but qualification is category-bounded and does not certify a campus/agency site, utility interconnection, or water budget.
Evidence and measured results
Program launch date Sep 21, 2026; two launch categories BESS and CDU; named BESS: Hitachi Energy, LG Energy Solution, Tesla; named CDUs: LG Electronics, LiquidStack, Vertiv; BESS partners run tests and submit data for NVIDIA review within a defined qualification boundary; site-level engineering/stability explicitly not implied.
Limitations and uncertainty
Vendor program announcement; named partners are examples at launch, not an exhaustive marketplace audit; no measured token or facility MW outcomes in this post.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Buyers struggle to select power/cooling products that fit DSX AI factory designs without costly rework.
- Stakeholders
- facilities
- procurement
- AI platform
- utility liaison
- Discovery questions
- Is the site targeting DSX reference design?
- Do you need BESS for buffering/DR or only CDUs?
- Who owns site-level electrical/thermal acceptance?
- Value hypothesis
- DSX Ready shortlists can reduce integration risk if paired with site engineering gates.
- Potential engagement
- BOM screening workshop mapping DSX Ready BESS/CDU options to one hall’s envelope.
- Unsupported claims
- Site is DSX Ready certified
- Utility interconnect approved via product qualification
- Token throughput guaranteed by CDU/BESS badge
Pre-sales engineering
Role takeaway
- Fit
- Strong for DSX-aligned greenfield/retrofit halls needing qualified BESS/CDU; weak as sole architecture proof.
- Architecture and integration
- Select category-qualified products; keep site transformers/switchgear/campus controls outside product boundary.
- Prerequisites
- DSX design intent
- site power/thermal model
- partner qualification packet
- OT network plan
- Constraints
- Launch categories limited to BESS and CDU
- Qualification ≠ site stability
- Vendor-curated initial list
- Security
- Harden BESS/CDU controllers and telemetry paths; source silent on CC.
- Proof of value
- Site envelope holds under load swings
- Partner test evidence reviewed
- Rollback of setpoints demonstrated
Delivery
Role takeaway
- Work
- Map BOM to DSX Ready categories; integrate and SAT one power domain.
- Dependencies
- facilities electrical/mechanical
- OEM application engineers
- platform SRE
- Ownership
- Facilities program lead with platform co-owner.
- Skills and adoption
- Train ops on BESS/CDU control modes and qualification boundary language.
- Governance checkpoints
- No capacity claim from logo alone
- AHJ/utility approvals tracked separately
- OT security review before production
- Acceptance criteria
- Site SAT signed
- Qualification packet filed
- Stability envelope documented
- Risks
- Scope confusion with site ATO/interconnect
- Partner list churn
- Water/power constraints still bind
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Treat DSX Ready SKUs as reference-design-aligned building blocks inside a full power/cooling topology; still require site electrical, thermal, and controls integration models beyond the product boundary.
Governance
Who approves, reviews and stays accountable for outcomes?
Procurement can prefer DSX Ready listings for BOM screening, but must retain independent site engineering acceptance and not equate NVIDIA product approval with utility or AHJ approvals.
Security and privacy
What data, permissions and controls need testing?
BESS/CDU control planes expand OT attack surface; source is silent on cyber controls beyond product qualification scope.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None stated; facilities staffing for OT/power systems may increase.
Procurement
What should contracts, pricing and exit terms secure?
Allow DSX Ready as an evaluation preference, not a sole-source mandate; retain competitive BOM and site engineering SOW clauses.
Operating model
Which teams own the service once it runs?
Shifts vendor management toward continuous category qualification tracking alongside GPU software pins.
Publication history
- 2026-09-21NVIDIA · Issue 168 resources
Stable resource ID: nvidia-dsx-ready-bess-cdu-20260921