From the NVIDIA edition of September 22, 2026
DSX BESS Qualification Overview: AC-terminal tests and core island/black-start controls
NVIDIA · AI factory facilities standards / BESS qualification · Global (DSX reference-design partners)
- Publisher
- NVIDIA DSX Documentation
- Original publication
- undated DSX docs (live Sep 22, 2026 retrieval)
- Source retrieved
- 2026-09-23
- Event date
- 2026-09-22
What happened
NVIDIA’s BESS Qualification Overview details a partner self-qualification packet: PRD line-by-line C/D/E responses with evidence references; materials/safety/compliance disclosures; a Core Requirements checklist; and test procedures. The qualification boundary is at BESS AC terminals; POI ramp needs are verified via approved POI proxy profiles and/or EMT models. Core controls include autonomous island operation, reactive power support within PCS limits, seamless grid/island transition, and black start. Instrumentation requirements apply across tests; all tests run at AC terminals unless marked model-only.
Why it matters
Gives SLED facilities and EPCs the actual control/test vocabulary behind DSX Ready BESS claims—especially islanding and black-start—so reviewers can demand packet evidence rather than logo slides.
Evidence and measured results
PRD Compliant/Non-compliant/Exception responses; Core Requirements checklist; CTRL-CORE-01 island mode; GRID-CORE-02 reactive support; MODE-CORE-01 grid/island transition; MODE-CORE-02 black start; AC-terminal test boundary; POI proxy/EMT for ramp; instrumentation table applies to all tests.
Limitations and uncertainty
Vendor standard, not third-party audited results for a specific SKU; undated page; distinct from the already-archived BESS self-qualification guidelines overview URL.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; 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 cannot tell marketing badges from testable BESS controls.
- Stakeholders
- facilities
- EPC
- procurement
- utility liaison
- Discovery questions
- May we see the Core Requirements checklist?
- Were tests at AC terminals?
- Any POI claims beyond proxy/EMT?
- Value hypothesis
- Packet-based review prevents false site-readiness commitments.
- Potential engagement
- Half-day BESS packet readout against Core Requirements.
- Unsupported claims
- POI compliance via product pass
- Black-start of entire campus proven
- All PRD lines universally compliant
Pre-sales engineering
Role takeaway
- Fit
- Strong for DSX-aligned BESS design reviews.
- Architecture and integration
- PCS controls + instrumentation at AC terminals; POI via proxy/EMT only.
- Prerequisites
- OEM packet
- instrumentation plan
- site EMT/electrical model
- Constraints
- AC-terminal boundary
- Model-only exceptions
- Partner self-test model
- Security
- Include cyber/grid certs in disclosure review.
- Proof of value
- Core IDs evidenced
- Island/black-start tests cited
- POI proxy labeled
Delivery
Role takeaway
- Work
- Checklist audit of partner packet vs Core Requirements.
- Dependencies
- OEM
- EPC
- utility
- Ownership
- Facilities standards engineer.
- Skills and adoption
- Team learns PCS test vocabulary.
- Governance checkpoints
- No unmarked POI claims
- Instrumentation complete
- Exceptions documented
- Acceptance criteria
- Core checklist signed
- Evidence IDs present
- Gap list owned
- Risks
- Incomplete plots
- Boundary creep
- Exception sprawl
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?
Design reviews must align PCS controls and instrumentation to the Core Requirements list and treat POI behavior as out-of-boundary unless modeled via approved proxies.
Governance
Who approves, reviews and stays accountable for outcomes?
Require complete self-qualification packets (plots, time-series, pass/fail) before accepting Ready marketing in campus procurements.
Security and privacy
What data, permissions and controls need testing?
Materials/safety/compliance disclosure step includes regulatory certifications; cybersecurity evidence is expected in partner packets but not reproduced here.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None claimed.
Procurement
What should contracts, pricing and exit terms secure?
Make Core Requirements packet submission a bid deliverable for Ready BESS SKUs.
Operating model
Which teams own the service once it runs?
Stand up a recurring packet QA step before factory acceptance.
Publication history
- 2026-09-22NVIDIA · Issue 178 resources
Stable resource ID: nvidia-bess-qualification-overview-docs-2026