This page gives you a clear view of what public evidence already supports, and what still needs a live asset review before a decision is made.
Why this page matters
You should not need to decode a full research archive just to understand the claim. This page highlights what public evidence can support today.
It also makes the next step clear: once the mandate is live, the answer comes from a scoped review of your actual asset data.
Oxford chemistry signatures, NASA anomaly and resistance context, and the telemetry-to-review decision bridge.
A coherent lithium-ion method stack, with strongest public support in LFP-first utility BESS use cases.
Not universal chemistry proof, not multi-vendor fleet proof, and not a substitute for live telemetry, site history, and mandate-specific review.
Current public anchors
Use a focused set of references: chemistry signal, anomaly and resistance context, corroboration when ICA is fragile, and operating-context translation.
dQ/dV peak-shift logic.
Peak shift
Oxford / ICA
The strongest public anchor for derivative-based degradation interpretation inside the current Oxaide method set.
Dataset
Oxford Battery Degradation Dataset
Evidence reference
Oxford ICA Peak Shift
Resistance and precursor logic.
Precursor sequence
NASA / anomaly
The benchmark layer that supports anomaly, resistance, and early-warning interpretation before site-specific telemetry enters the room.
Dataset
NASA PCoE Battery Dataset
Evidence reference
NASA Thermal Precursor
Secondary electrochemical cross-check.
DVA
Oxford / DVA
DVA earns its place by supporting or challenging the flagship ICA interpretation when field telemetry is noisy or undersampled.
Dataset
Oxford Battery Degradation Dataset
Evidence reference
Oxford DVA Mechanism
Transition and stress logic.
Resistance logic
Cycle context
Before revenue or underwriting conclusions are drawn, the operating regime has to be read properly. This is the bridge from technical trend to asset-level decision language.
Dataset
NASA PCoE public benchmark context
Evidence reference
NASA Cycle Dispatch Context
Proof hierarchy
Oxford and NASA show that the core diagnostic logic is real, repeatable, and credible.
Public evidence should support a clear, defensible claim, not a broad fleet-wide promise.
Asset condition is confirmed only after operating history, site telemetry, and mandate context are reviewed.
Only then should findings be translated into diligence, warranty, refinancing, insurer, or post-COD decisions.
Representative figures
Use these visuals to understand the argument quickly, then open the atlas only when deeper chart review is required.
Oxford / ICA
The strongest public anchor for derivative-based degradation interpretation inside the current Oxaide method set.
Dataset anchor
Oxford Battery Degradation Dataset
Evidence reference
Oxford ICA Peak Shift
NASA / anomaly
The benchmark layer that supports anomaly, resistance, and early-warning interpretation before site-specific telemetry enters the room.
Dataset anchor
NASA PCoE Battery Dataset
Evidence reference
NASA Thermal Precursor
Weakest-link
The public pack is strongest when it shows not only chemistry and anomaly logic, but the triage path serious operators actually use.
Dataset anchor
NASA PCoE Battery Dataset
Evidence reference
NASA Weakest Link Divergence
Use this as confidence-building context, not as a replacement for your site review. Public datasets show the method logic is credible and grounded.
Final conclusions still come from your telemetry, your site history, and your operating constraints.
Use the method map to understand the review sequence before going into appendix-level detail.
Open the full benchmark-chart appendix when your team needs figure-by-figure evidence.
Move from public proof to a fixed-scope review when the mandate is operational, financial, or underwriting-grade.
Scope first
Defined review scope
Boundary, telemetry window, and mandate question are pinned down before conclusions move.
Encrypted handling
Protected review workflow
Review traffic and operating data are handled with encrypted transfer and controlled access.
Customer boundary
Customer-controlled deployment
Managed, private, and isolated deployment paths are available when the environment requires them.
Direct accountability
Principal sign-off
Technical accountability stays close to the method rather than disappearing into a generic workflow.
