We review historical telemetry for investors, asset managers, and operating teams that need a clear answer quickly. Oxaide surfaces degradation, yield leakage, and failure patterns standard monitoring can miss, then returns a clear report in 5 business days.
Why BESS-first
Weak technical baselines get expensive quickly in storage. The same evidence can shape SPA terms, refinancing, warranty files, insurer review, and operating plans.
Send telemetry exports. We scope the review and return a clear report in 5 business days. Global execution, Singapore-headquartered.
Best self-checkout fit: one bounded telemetry slice, one live decision, one fixed-fee answer. Broader mandates should go through direct review.
Verify takes the raw evidence, rebuilds the asset history, isolates the degradation mode, and turns it into a report people can actually use.
Selected stage
Scope
Defined intake boundary
The full review path stays visible below. Select a stage if you want to inspect the detail more closely.
Stage 01 / 04
What enters review
Forensic kernel
Cell-level exports, BMS history, event context, and the mandate question are fixed before analysis starts.
Asset block
Container 01 · Inv-04
Telemetry window
180 days
Primary finding
Telemetry export received Asset boundary confirmed Review path opened
Illustrative sample report
Findings, evidence basis, risk posture, and next-step recommendation arranged the way a real investment or operating review would need them.
Cover finding
Usable capacity and stress signals no longer support the clean operating narrative.
Evidence insert
Dispatch guardrails excerpt
The preview stays uncropped so you can actually read it. Open the full chart if you want a closer look.
Why this holds up
Review stages
Select any stage to inspect that part of the review path.
Buyer outcomes
This is about making a cleaner acquisition, credit, warranty, insurer, or operating decision while there is still time to act.
Use the report to test usable capacity, degradation, and downside before pricing or lender papers harden.
Use the evidence trail to frame claims, renewals, and underwriting around the physical asset rather than dashboard summaries.
Use the findings to decide whether the next move is protocol change, further test, repair, or escalation.
Use Verify to decide whether the site actually earns a continuous monitoring layer or whether a one-off review is enough.
Method evidence
If you are comparing firms for a BESS forensic audit, the question is simple: who can show you the physics, the evidence trail, and the operating impact, rather than another dashboard screenshot? That is the standard Oxaide should meet.
Independent forensic layer
These are the four public benchmark visuals that best show the Oxaide wedge: chemistry signal, stress sequence, knee-point / RUL framing, and the operating consequence. That is the layer between generic dashboard land and lab-only science theatre.
Oxford / ICA
Start with the derivative fingerprint that shows whether the electrochemical story is as clean as the commercial story implies.
Dataset anchor
Oxford Battery Degradation Dataset
Evidence reference
Oxford ICA Peak Shift
NASA / DCIR
Resistance and abnormal transition logic matter because fragility often appears before the headline KPI story breaks.
Dataset anchor
NASA PCoE Battery Dataset
Evidence reference
NASA Resistance Transition
Predictive maintenance
The independent forensic layer gets commercially useful when it shows whether the asset is still degrading gracefully or entering acceleration risk.
Dataset anchor
Oxford Battery Degradation Dataset
Evidence reference
Oxford Knee Point Rul
Dispatch / guardrails
Diagnostics earn budget when they tighten or relax the operating envelope in a way the asset team can defend.
Dataset anchor
Derived public benchmark context
Evidence reference
Dispatch Guardrails
Verify process
Defined scope. Historical telemetry. Independent review. Clear output.
Step 01
We align on one BESS block, the data window, and the commercial decision before conclusions move.
Step 02
Historical telemetry, BMS / SCADA exports, and context notes are handled inside the defined intake boundary.
Step 03
We test degradation, resistance pressure, derating, imbalance, and anomaly patterns, then explain what they mean for the decision.
Step 04
You get a clear written report within 5 business days, plus next actions and follow-on scope options.
Engagement model
We publish the exact Verify fee because the starting scope is bounded. Horizon shows a starting fee because telemetry path, deployment boundary, and reporting needs materially change the pilot shape.
Fixed-scope review with quantified yield gaps, degradation modes, and practical next steps.
Fixed diagnostic fee
Standard scope · one asset block · written report in 5 business days
Used For
Pilot deployment for teams that need a continuous monitoring layer after the first review.
Scoped pilot starting fee
Typical one-site pilot starts here. Final scope depends on telemetry path, deployment boundary, and reporting needs.
Target Profile
Related review briefs
Verify is the core service. These briefs help buyers, owners, and operators move directly to the review scope that fits the issue in front of them.
Use this when the review is tied to acquisition, refinancing, or investor committee work.
Use this when the battery sits inside a critical-power or data-centre resilience story.
Use this when an owner needs independent evidence before a claim, renewal, or insurer conversation.
Use this when the site is operating, but the field behaviour no longer feels like the commissioning narrative.
Method and evidence
These resources let technical buyers inspect the forensic logic, evidence base, and claim limits before they need to rely on a sales claim.
The lead chemistry-fingerprint method for buyer-side review, especially in LFP-first utility BESS contexts.
The physical stress, heat, and power-fade layer that matters when asset condition needs to be defended commercially.
Why plating risk matters in forensic review long before ordinary dashboard thresholds become persuasive.
Commercial comparison
Many teams are not really shopping for monitoring software. They are trying to answer a diligence, warranty, lender, insurer, or revenue-risk question fast enough to matter. That is why the difference between a one-off forensic review and continuous monitoring should be stated plainly.
A bounded review for teams that need a usable written answer quickly.
Turn telemetry into a technical position fast.
Meetings and spreadsheet churn delay the answer.
Careful intake and handling that respect the site boundary.
Standard cloud flow before the posture is agreed.
Decision-ready output instead of an open-ended advisory loop.
Time and cost grow before the recommendation lands.
FAQ
Typical uses include SPA terms and reserves, lender or refinancing packs, warranty and insurer discussions, and O&M recovery plans when the commissioning narrative no longer matches the field data.
At minimum: telemetry exports, BMS or SCADA histories, asset context, and the operating question you need answered.
No. The same forensic review logic applies to utility, C&I, and infrastructure-adjacent systems when telemetry quality is sufficient.
Yes. Verify can support internal approvals, risk reviews, lender or insurer conversations, and procurement documentation across multiple markets.
A concise principal-led briefing on what the work can support, how the method holds up, and where Verify and Horizon fit.
Covers telemetry limits, main degradation and operating-risk patterns, plus how Verify and Horizon fit the engagement path.
Focus
BESS-First Review
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.
