BESS forensic methods that support diligence, warranty, and post-COD decisions
These method notes show the sequence Oxaide uses when a battery decision needs more than dashboards, vendor posture, or lab-theatre abstractions.
Why this page should exist
This is the method map, not the proof appendix.
Good technical pages do not force buyers to decode the whole evidence archive in the opening frame. They make the operating logic legible first.
That is the job of this page: show the method order, show how the layers connect, and point to the right appendix only when the reader actually wants proof depth.
What this page is
A decision-led method map
This page exists to show how Oxaide thinks, in sequence, before a diligence, warranty, or post-COD mandate is scoped.
What supports it
Benchmark-backed, not benchmark-trapped
Oxford, NASA, and operating-context references support the method logic. The full proof appendix lives elsewhere, not in the opening conversation.
What it is not
Not a substitute for live review
Method notes explain the forensic layer. They do not replace site telemetry review, operating-history analysis, or commercial decision support.
Method sequence
This is the order a disciplined reviewer follows.
The sequence matters because disciplined technical work feels ordered, not ornamental. Each layer earns the next one.
Start with telemetry posture and operating regime
Before chemistry claims, the reviewer needs to know whether the site data is trustworthy, comparable, and being read in the right dispatch context.
Then read chemistry and slow-health signal
ICA, corroborating DVA logic, and knee-point framing matter because serious buyers need more than summary SoH wallpaper.
Pressure-test resistance, heat, and precursor behavior
Resistance rise and plating-risk logic matter because safety, warranty, and downside questions often appear before clean capacity narratives do.
Keep the claim boundary explicit
Method quality rises when proof limits are made visible early and the buyer can inspect where benchmark evidence ends and live-asset review begins.
Core method notes
Open the specific layer that matches the question on the table.
This is where the reader moves from the map into the specific diagnostic lens, without losing sight of the wider decision architecture.
Incremental Capacity Analysis (dQ/dV)
The lead chemistry-fingerprint method for LFP-first BESS diligence, degradation diagnosis, and clear forensic review.
DCIR and Resistance Rise
The physical stress, heat-generation, and power-fade layer that matters in safety review, warranty evidence, and post-COD operating checks.
Lithium Plating Detection
Why plating risk matters long before an operator can defend the issue with dashboard-level summaries alone.
Knee-Point and RUL Framing
How slow-health estimation, acceleration risk, and intervention timing should be read before predictive-maintenance claims get loose.
Usable Capacity vs BMS SoH
The gap that matters in underwriting, SPA negotiations, warranty review, and investor-led battery diligence.
How Oxaide Reads BESS Telemetry
The practical sequence from telemetry triage through spread, resistance, ICA, DVA, and decision synthesis.
Commercial route
Start with the review path that matches the actual mandate.
Acquisition, refinancing, and capital-allocation decisions where the asset condition needs to stand up beyond the data room.
Claims, disputes, renewals, and insurer scrutiny that need more than summary reporting.
Live sites where operating drift, thermal stress, or degradation need to be understood before they get expensive.
For readers who want the claim boundary, benchmark posture, and proof hierarchy before mandating a review.
Chart-by-chart appendix of the benchmark visuals and dataset anchors behind the current method set.
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.