Live evidence case / CML-PDRE-001

800V DC Data Center Power Architecture

Question: Has 800V DC power architecture moved from proposal to independently attributable field deployment?

Current answer: One attributable operator record supports one commercial SST-to-800VDC deployment. It does not establish independent validation, replication, industry adoption, or full PDRE validation.
Current state
HUMAN-REVIEWED SINGLE-INSTANCE EVIDENCE
As of
2026-09-20T10:46:47Z
Last material change
2026-09-20

Search context

Questions this record addresses

These are genuine discovery questions. Answers remain bounded by the same public state shown on this page.

State · Evidence · Counter-evidence · Unknowns · Case history · Public change history · Search provenance · Related case

Citable stop point · derived public projection · v0.1

800V DC / SST field deployment

HUMAN-REVIEWED SINGLE-INSTANCE EVIDENCE
Claim

A named operator reported commercial operation of one SST-based 10kV AC to 800VDC system at Sangyuan Cloud Computing Campus.

Scope

One named operator and one named campus near Beijing; this SST-based power architecture only.

Time boundary

Source event 2026-07-02; knowledge time 2026-09-20T10:46:47Z; human review frozen 2026-09-20T11:12:14Z.

Current bounded state

HUMAN-REVIEWED SINGLE-INSTANCE EVIDENCE

Supports

Attributable evidence of commercial operation for this one deployment; the source is the operator's own publication.

Does not support

Independent performance validation, long operating history, multi-entity replication, repeat procurement, industry adoption, or full PDRE validation. Canonical migration readiness was not changed by this review.

Next minimum verification

Obtain an independently attributable operating record for the named site with its observation period and conditions.

A citation is incomplete if “Does not support” is omitted. Derived from the human-reviewed L1 evidence and publication control. No new source was evaluated for this projection.

Have a public source that supports or challenges this boundary? Challenge this gap →

Current evidence state

What the approved records establish now.

States separate architecture, validation, field operation, and adoption. No confidence percentage is inferred.

Architecture possibilitySUPPORTED
System validationSUPPORTED

Source-reported demonstrations; performance claims remain attributed.

Named field deploymentOBSERVED — SINGLE INSTANCE
Long operating historyUNKNOWN
Multi-entity replicationUNKNOWN
Independent third-party validationUNKNOWN
Repeat procurementUNKNOWN
Industry-scale adoptionNOT ESTABLISHED
PDRE full validationNO

Decision transition

What changed our assessment?

Authorization is separate from execution. Evidence acceptance is separate from canonical readiness.

BeforeR5_FIELD_DEPLOYED_NOT_ESTABLISHED
Research gap identifiedDated, attributable field-operation evidence needed
Human authorization1 narrow L1 verification authorized

No general 800V research authorized.

Bounded verification4 queries · 9 sources · 1 deep review
Qualifying evidenceNamed operator · named campus · 10kV AC → SST → 800VDC · commercial operation
Human reviewEvidence accepted
AfterR5_ARCHITECTURE_FIELD_DEPLOYMENT_EVIDENCE_ACCEPTED_SINGLE_INSTANCE

Canonical readiness remains unchanged pending existing governance.

Still unknown5 unresolved dimensions preserved

Source and search provenance

Approved qualifying evidence record.

The source is an attributable operator publication, not an independent third-party audit. The bounded verification used 4 queries, reviewed 9 sources, and performed 1 deep review; no general 800V research was authorized.

L1-EV-CML-PDRE-001-FIELD-DEPLOYMENT-001

Chindata Commences Commercial Operation of an SST-Based DC Power System for Hyperscale Data Centers

Open atomic evidence record →

HUMAN REVIEW ACCEPTED · SINGLE INSTANCE
SOURCE / PUBLISHER
Primary operator publication / Chindata
PUBLICATION DATE
2026-07-02
EVENT DATE
2026-07-02
KNOWLEDGE DATE
2026-09-20T10:46:47Z
OPERATIONAL ENVIRONMENT
Chindata Sangyuan Cloud Computing Campus near Beijing
ARCHITECTURE
10kV utility AC to 800VDC using an SST-based intelligent DC power system
WHAT IT SUPPORTS
One named operator reported commercial operation at one named campus for a materially relevant SST-to-800VDC architecture.
WHAT IT DOES NOT SUPPORT
Independent performance validation, operating history, multi-entity replication, application qualification, repeat procurement, industry adoption, or full PDRE validation.

Counter-evidence

Non-qualifying records remain visible.

Future commercialization or planned deployment bounds the assessment; it is not silently discarded after one qualifying source is found.

PLANNED DEPLOYMENT

Vertiv / practical path to 800 VDC

Commercialization, customer pilots, and deployment ramp were described as future activity. Rejected as field-operation evidence for this question.

UNDER DEVELOPMENT

Siemens + Reinhausen / DC power solutions

The record described technology under development for future deployment. Rejected as field-operation evidence for this question.

BOUNDARY

What these records mean

One observed architecture does not establish that related product paths, supplier systems, or industry adoption are field deployed.

Dependency transfer

The bottleneck moves; it does not disappear.

The alternative path can reduce selected rack-level constraints while creating or elevating new engineering and qualification dependencies.

Old path

MV/LV AC→Transformer→UPS→Rectification→Rack PSU→Low-voltage distribution

Alternative path

MV→SST→800VDC→Rack / sidecar / conversion layer→Compute

Candidate dependency release

  • Lower current
  • Copper pressure
  • Distribution density constraint

Dependency transfer — not all solved

DC protectionFault isolationInsulation / partial dischargeConnectors / busbarsSiC / GaNHF magneticsQualificationThermal integration

Subsystem watch

Readiness is subsystem-specific.

Repository-supported states only. UNKNOWN is an intentional result when the approved packet contains no qualifying evidence.

SUBSYSTEMSTATEEVIDENCE BOUNDARY
SSTFIELD_DEPLOYED · SINGLE INSTANCENamed 10kV-to-800VDC commercial operation record.
SiCUNKNOWNNo approved item-level state.
GaNUNKNOWNNo approved item-level state.
HF transformerUNKNOWNNo approved item-level state.
HF magnetic materialUNKNOWNNo approved item-level state.
Insulation / partial dischargeUNKNOWNTransferred dependency; qualification evidence absent.
Thermal managementUNKNOWNTransferred dependency; qualification evidence absent.
DC protection / SSCBWATCHDC protection is a new critical dependency; no subsystem qualification inferred.
Power rack / sidecarSYSTEM_VALIDATIONSource-reported demonstrations support R3 sample-bench-tested state only.
Busbar / connectorsUNKNOWNTransferred dependency; item-level evidence absent.
Standards / certificationDEVELOPMENTDraft specification and work underway do not establish completed certification.

Open Evidence Gaps

What is still missing?

Two bounded gaps are open for public challenge. Other unknowns remain recorded but are not separate Phase 1 challenge objects.

UNKNOWN

Operating history

Why it matters

Initial operation does not establish duration or reliability.

Minimum resolving evidence

Dated attributable operating-history and reliability record for the named system.

No current Open Evidence Gap
NOT ESTABLISHED

Multi-entity replication

Why it matters

One operator cannot establish repeatability across entities.

Minimum resolving evidence

Attributable field-operation records from additional independent operators.

Challenge this gap
NOT ESTABLISHED

Independent validation

Why it matters

Operator statements are not third-party performance audits.

Minimum resolving evidence

Independent validation against defined performance and safety requirements.

Challenge this gap
UNKNOWN

Repeat procurement

Why it matters

A first project does not establish repeated buying behavior.

Minimum resolving evidence

Dated attributable repeat order or additional commissioned procurement.

No current Open Evidence Gap
NOT ESTABLISHED

Industry-scale adoption

Why it matters

Single deployment and standards activity are not broad adoption.

Minimum resolving evidence

Multi-entity field evidence with repeat deployment across a defined market boundary.

No current Open Evidence Gap

Customer application

Does this evidence apply to your system?

Public evidence can establish a market boundary. Your architecture, qualification requirements, suppliers, and decision deadline determine applicability.