BESS ASSURANCE · INTERACTIVE DEMO
Know your battery.
Before it costs you.
From live BMS telemetry to health, performance, warranty and cryptographic evidence. One intelligence layer for high-value battery assets.
CAN-nativeDBC decoding
Live + historicalsignal intelligence
Multi-OEMone analytics layer
RECORDED WINDOW05:05 to 13:05 · 5 min resolution
50.0 MWh · 4 containers · 192 racks. Hover a container to load its own telemetry.
Three quantities, three units, three axes. Nothing is normalised onto a shared scale.
RACK HEALTH191/192 reporting · 190/192 available
2 critical1 warning
Fill = ΔT vs fleet median
0 °C+4 °COutline = alert severityCriticalWarning
INTELLIGENCEActive insight
Rack 14 temperature spread is trending upward.
DC BUS 1325.6 V
GRID METER 5.94 MW
RACK CURRENT 23.5 A
SOC 83.0 %
CELL Δ 22 mV
RACK 14 TEMP 32.2 °C
DATA INTEGRITY VERIFIED
WHY THIS MATTERS
Three questions you cannot answer from a SCADA screen.
Not features. The three things that decide whether a battery asset makes money or costs it, with the answer this demo site gives for each one.
Is the thing you bought doing what it was sold to do?
A supply contract promises capacity, efficiency and a degradation curve. Those contractual promises are rarely verified independently and continuously, so a shortfall can surface years later as a dispute instead of as an early warning.
ON THIS SITE
- 46.8 of 50.0 MWh actually dispatchable, so 6.4 % of what was paid for is not available today
- 91.7 % round-trip against a 90.0 % contractual floor: 1.7 points of margin left
- 94.2 % state of health at 4.3 years against 84.6 % guaranteed at that age, so 9.6 points of headroom
The 90 % efficiency floor and the guaranteed capacity curve are the terms of this demo contract. Real contracts differ substantially between suppliers; the platform reads yours rather than assuming an industry default.
Are you inside the warranty, or about to fall out of it?
Battery warranty eligibility depends on operating conditions as well as calendar age. Exceeding contractual temperature, throughput or cycle limits may affect a future warranty claim, often on the grounds that the supporting evidence is operator-supplied.
ON THIS SITE
- 2.8 °C of margin to the 35 °C contractual limit on C-03 · R14, and the gap has been closing for four hours
- 329 of 365 EFC used this year on C-02, the limiting container of the four, so 36 equivalent full cycles of allowance remain
- Two critical rack-level findings currently open, each preserved with the operating record needed to support a future warranty investigation
The 35 °C limit and the 365 EFC annual allowance come from this demo contract. Some suppliers set throughput limits instead of cycle counts, and some newer warranty models drop the cycle limit altogether.
Do you know what it costs you when it does not run?
A battery that cannot dispatch cannot sell. The loss is not the repair bill, it is the revenue that was never earned, and it scales with how long the problem stays invisible.
ILLUSTRATIVE REVENUE EXPOSURE · €95/MWh CAPTURED SPREAD, ONE FULL CYCLE PER DAY
One constrained rack0.26 MWh€173 / week
One container offline12.5 MWh€8,313 / week
The whole site down50.0 MWh€33,250 / week
That ladder is the whole argument. A rack costs hundreds a week and a site costs tens of thousands, and the only thing standing between the two is whether anybody noticed the rack.
The €95 is our assumption, not your price. Real exposure also depends on how many cycles you actually run, your captured spread, round-trip efficiency, market fees, and whether the unavailable energy would have been dispatched at all. In the product the price comes from one of three places, never from us: a figure you enter, your own dispatch and settlement data, or a market feed.
ONE CONTINUOUS BATTERY HISTORY
One record. Six stages. No gap between them.
Manufacturing records describe how the battery was built. OEM specifications define how it should operate. BMS data reveals how it actually operates. Löwentech connects all three, and keeps the chain intact from the first factory test to the recycling handover.
- Identity Serial, BOM, cell data
- Operation Live power, SoC, current
- Health SoH, imbalance, degradation
- Risk Thresholds, margin, severity
- Action Recommendation, alert, work order
- Evidence Sealed archive, signed report
Monitor
Live BMS, EMS, PCS and CAN telemetry across site, container, rack and module level.
Diagnose
SoH, imbalance, thermal behavior, degradation trends and root-cause investigation.
Perform
Dispatchable energy, RTE, constrained capacity, component losses and revenue impact.
Protect
Safety early warning, severity classification, predictive maintenance and alerts.
Warranty
Continuously compare real operation with OEM limits and contractual KPIs.
Prove
Optional cryptographic integrity for telemetry archives, reports and claims evidence.
SOLUTIONS
Six modules. One data layer.
Start with the module that answers your most expensive question. All six share one ingest layer and one set of signal definitions, so adding the next one is configuration rather than a second integration project.
MODULE 01Start here
Live Diagnostics
Is the system actually doing what the SCADA screen says it is?
What it needs from you
- CAN bus access, or an existing Modbus TCP / REST endpoint
- The DBC or a signal list where applicable; we version it and keep it under change control
- If direct bus access is used: an edge gateway, ours or yours, with outbound HTTPS only and no inbound ports
What you get
- Decoded signals at site, container, rack and module level
- 1 s to 5 min resolution, live and historical on one signal dictionary
- Web console, REST API and CSV/Parquet export of the raw and decoded data
- Typical onboarding: 2 to 4 weeks, depending on data access and signal documentation
Best forOperations and asset management
MODULE 02Requires Module 01
Performance Intelligence
How much of what I paid for can I actually dispatch this week?
What it needs from you
- Module 01
- Nameplate capacity, PCS rating and the commissioning baseline test
- Your dispatch schedule or market position, if you want the euro figures
What you get
- Dispatchable energy against nameplate, not against last month
- Round-trip efficiency per cycle with the contractual floor drawn in
- Constrained and restorable capacity separated, then priced per week
- Loss attribution down to the rack or module causing it
Best forAsset owners, traders and performance engineers
MODULE 03Requires Module 01
Safety & Early Warning
Will I know before it becomes an incident, not after?
What it needs from you
- Module 01, including cell temperature and cell voltage at rack level
- Your alarm routing: email, SMS, webhook, or your ticketing system
- An agreed alert and escalation policy, so thresholds and actions are operationally accepted
What you get
- Rate-of-rise detection (dT/dt), not only absolute temperature thresholds
- Deviation against the fleet median, so a slow drift is caught without a fixed limit
- Severity classification with the recommended action attached to each alert
- A signal-level incident timeline for root-cause analysis and incident review
Best forO&M, HSE and the on-call engineer
MODULE 04Requires Module 01
Warranty Intelligence
Am I still inside the contract, and could I prove it in a dispute?
What it needs from you
- Module 01
- The supply and warranty contract: operating limits, EFC allowance, guaranteed capacity curve
- The commissioning acceptance test, as the baseline everything is measured from
What you get
- Continuous comparison against configured, measurable contractual limits, with the remaining margin shown explicitly
- Equivalent full cycles tracked against the contractual allowance
- Measured SoH against the guaranteed curve, per container
- Claim-supporting export of the operating record and the relevant evidence
Best forAsset owners, insurers and lenders
MODULE 05Runs standalone
Living Battery Passport
Are your batteries ready for the 2027 EU passport requirements?
What it needs from you
- Manufacturer documentation: BOM, cell datasheets, factory acceptance tests
- Serial numbers down to the level you want the passport to resolve
- Module 01 if you want the operating data to keep updating itself
What you get
- A structured battery passport record aligned with Regulation (EU) 2023/1542, accessible via QR code
- Composition, carbon footprint and due-diligence fields alongside the technical data
- SoH, cycle count and thermal history written back for the whole operating life
- Second-life and recycling handover record at end of use
Best forWhoever places the battery on the EU market
MODULE 06Add-on
Integrity Layer
Would a third party accept my data as evidence rather than as a claim?
What it needs from you
- Nothing beyond whichever modules you already run
- A retention period, agreed once
- Optionally, your own key if you want to sign exports yourself
What you get
- Five-minute telemetry blocks, hash-chained, with a timestamped daily Merkle root
- Signed or sealed report exports that a third party can verify independently
- An open verification tool, so the OEM or insurer checks it independently
- Tamper-evident by construction rather than by policy
Best forDisputes, insurance, audit and resale
Module 01 is the base: it is what turns a CAN bus into named signals, and Modules 02, 03 and 04 read from it. Module 05 can run on documentation alone if you only need the compliance record, and Module 06 sits beside whatever you run. A typical deployment can start with Modules 01 + 02, with Warranty Intelligence added when contractual monitoring becomes a priority.
CAN-NATIVE DIAGNOSTICS
Raw signals in.
Clarity out.
Löwentech technology originates from real-world remote diagnostics of electric vehicles. The same CAN-native architecture now becomes a direct path from BMS data to battery assurance.
- Version-controlled DBC decoding
- Live and historical telemetry
- Customer-specific signal definitions
- Edge gateway or existing API ingestion
- Multi-OEM data layer
CAN → CLOUD DECODE PIPELINESelected asset · C-03 · Rack 14SAMPLE
RAW CAN · 500 kbit/s
bess-hv-v8.dbc428 signals
rev 8 · verified
DECODED SIGNALS
GETTING THE DATA IN
Two ways in. One way out.
Your data reaches us one of two ways: we ingest it from your existing BMS, EMS, PCS or SCADA through an available interface, or we install our own edge gateway and read the bus directly. From that point on the path is identical. We take it to the cloud, normalise it once, and serve it to everything that asks.
SOURCE
OPTION A
Your existing devices
BMS, EMS, PCS or SCADA over REST, MQTT, Modbus TCP or OPC UA. Existing BMS, EMS, PCS and SCADA interfaces can often be used without additional field hardware.
OPTION B
Our gateway on site
Löwentech edge device with read-only access to the CAN bus, reading the frames directly. Outbound HTTPS only, no inbound ports, no BMS firmware modification.
LÖWENTECH CLOUD
Decode & normaliseVersioned DBC or signal mapping, applied once
StoreRaw and decoded, EU servers, retention you set
AnalyseHealth, performance, warranty, safety rules
SealHash-chained blocks, optional
DELIVERED TO
Web consoleYour own login, your own tenant
Mobile appSame data, same thresholds
REST APIInto your own tools
ReportsScheduled and exportable; signed or sealed with the Integrity Layer
YOU RUN ITYour account, your users, your rules
No ticket required
The platform is yours to operate, not ours to operate on your behalf. You log in to your own tenant on the server and administer it directly. The same principle as the conversion side of the business: we set it up and train your team, and after that you are not waiting on us to get work done.
Users and roles
Invite your own people, set roles per site, revoke access when someone leaves. Single sign-on against your identity provider if you use one.
Assets and signals
Add sites, containers, racks or vehicles yourself. Upload a new DBC, map a signal, rename it. The decoder picks it up without a release from us.
Thresholds and rules
Write your own rules in the rule builder, set severities, decide who each one wakes up. Your limits, not our defaults.
Reports and exports
Schedule your own reports, define what goes in them, pull raw or decoded data over the API whenever you want it. No export request, no waiting.
Your data stays yours
Single-tenant by default, EU hosting, retention you set, deletion on request. We hold no ownership claim over the telemetry and we do not resell it, aggregated or otherwise.
Support when you want it
Onboarding, training and an engineer on call are part of the package. Needing them for routine work is not.
THE WORKFLOW IS THE PRODUCTHow many steps it takes to answer one question
Typical workflow, not a benchmark
Question: "Which container is losing us energy this week, and why?"
Without an analytics layerSCADA plus spreadsheets
- Open the SCADA screen
- Export data per container
- Align timestamps
- Compare container performance
- Retrieve the contractual and OEM limits
- Reconcile the operating data against those limits
6manual steps · multiple tools
With Battery AssuranceOne console
- Ask, or open the ranked view
- Read the answer with its evidence
2steps · one console
Counted as the work an operator actually does, not as a measured benchmark. The point is structural rather than clever: the steps disappear because the decoding, the alignment and the contractual limits were done once at ingest instead of once per question.
PERFORMANCE INTELLIGENCE
Find the energy you are losing.
A battery can remain online while quietly losing capacity, efficiency and revenue. We surface the difference between nameplate performance and what can actually be dispatched.
DISPATCHABLE ENERGY50.0 MWh nameplate
live modelEnergy not dispatched, last 14 daysMWh per day
Value of the capacity you cannot dispatch€2,130 / weekIllustrative: 3.2 MWh unavailable × 7 cycles × €95/MWh assumed captured spread. The price is an assumption for this demo, not a market quote. Change it and the arithmetic follows.
WARRANTY ENVELOPECell temperature vs contractual limit
WARNING
Rack 14Approaching thermal warranty threshold
31.8 °C now · 3.2 °C of margin to the 35 °C contractual limit
WHERE THE ENERGY IS GOINGRacks ranked by unavailable capacity
ConstrainedRestorable5 of 192 racks · 2.91 of 3.20 MWh
| Rack | Contribution | ConstrainedMWh capacity | RestorableMWh capacity | Root cause | Action |
|---|
Constrained capacity is unavailable because of an active technical constraint or fault, and is not expected to return through routine balancing or control intervention. Restorable capacity is unavailable now but is expected to return through a defined reversible intervention such as balancing or thermal correction. These five racks hold 2.91 MWh of the 3.20 MWh currently unavailable, which is the same 3.20 MWh the energy card above splits and the same figure the weekly euro exposure is calculated from. The split matters because only one of the two is worth a site visit this week.
AGING MODEL · FORECASTWhat the dispatch strategy costs you in battery life
Illustrative scenarios · model, not measurement
Same hardware, three ways of running it. The shaded band is the model's uncertainty, and it widens with time because it should. A ten-year projection made today is not a measurement. Stress factors: depth of discharge, cell temperature, SoC window and C-rate.
STATE OF HEALTH SINCE COMMISSIONINGMeasured capacity against the guaranteed curve
Within limits
Solid line: measured, one point per quarter since 21 April 2022. Dashed continuation: projected at the current duty cycle. Yellow: the capacity the supplier guarantees at that age. The number that matters is the vertical gap between them, because that gap is what you would argue about in a claim.
PORTFOLIO VIEW
Twelve containers. One screen.
Site plan across three sites, coloured by the worst open finding inside each container. Container figures are DC power at the battery; the console reads the grid meter, which is lower by the PCS and auxiliary losses. Nothing here is a guess: a container turns amber or red because a rule fired on a decoded signal, and the reason is written on the tile. Site 04 · C-03 is the container this whole page has been following.
Critical · 4
Warning · 1
Normal · 7
Fill = temperature deviation · Outline = alert severity · Grey hatch = no telemetry · each block is two of the 48 racks
TIME-TRAVEL DIAGNOSTICS
Replay any moment.
Trace the fault to its origin.
Scrub through historical telemetry like a video timeline. Switch signal without losing your place, so power, state of charge, temperature and cell spread can all be read at the exact moment a deviation began.
AI SUMMARY
In this window Rack 14 delta-T begins rising 11 minutes before the first BMS warning.
Site 04 · Container 03 · Rack 1412:44:18
05:0507:0509:0511:0513:05
AI-ASSISTED POST-PROCESSING
Ask the fleet a question.
The same assistant that runs inside CloudDiagnostix, pointed at this dataset. It answers from the decoded signals rather than from a summary, and it draws the evidence next to the answer, so you can disagree with it.
BA
Battery Assurance AI
Online · live site context · engine shared with CloudDiagnostix
AI
Demo assistant. Every figure it quotes is computed from the sample dataset on this page, so you can check it against the charts above.
LIVING BATTERY PASSPORT
BATTERY ASSETSite 04 · BESS Container 03
hover to switch
EU 2023/1542Battery passport architecture aligned with the Regulation. This asset was commissioned in 2022, before the passport obligation applies. A later repurposing or remanufacturing event may trigger separate passport requirements. The record is kept to the same structure regardless.
LT-BESS-DE-2022-004-C03
- Manufacturer
- OEM-linked
- Chemistry
- LFP
- Rated Energy
- 12.5 MWh
- Commissioned
- 2022-04-21
- Equivalent full cycles
- 1,482
- SoH
- 94.2%
- Throughput
- 18.5 GWh
- Current warranty status
- Warning · thermal deviation
Last lifecycle updateseconds ago
A passport that keeps living after commissioning.
Identity, chemistry, technical documentation and certificates become the foundation. Operational history, service events, warranty status and health metrics continuously extend the record.
PassportWhat the battery is.
DiagnosticsWhat the battery is doing.
AnalyticsWhat it means.
EvidenceWhat you can prove.
INTELLIGENT ALERTS · CLOUD AND MOBILE
Detect deviation
before it becomes downtime.
Telemetry lands on our cloud server, is decoded or normalised once against version-controlled signal definitions, and is served to everything that asks: the web console, the API, a report, or the phone of the engineer on call. Rule builders, pattern recognition and severity classification mean your team acts on a warning instead of a breakdown, and every alert links back to the signal that raised it.
Critical
Warning
Info
RULE BUILDER
THRESHOLD
CellDelta > 40 mV for 60 s → criticalPATTERN
Rack ΔT vs fleet median > 3 °C for 30 min → warningRATE
Max cell dT/dt > 0.40 K/min → criticalBUDGET
EFC > 90 % of annual allowance → infoRules trigger the alerts delivered on the right
Illustrative rules. Thresholds are configured per OEM, chemistry and site; none of these numbers is a universal battery limit.
Löwentech13:05
SITE 04 · C-0305:05 to 13:05
SOC82.7%
TEMP32.2°
DC BUS1325V
Δ CELL23mV
CAN → CLOUD DECODE
0x18FF50E5
3D 91 F2 08
→.DBC→
SOC 82.7 %
Temp 32.2 °C
BATTERY ASSURANCE AIlive · historical · fleet
Which rack is running hot?
C-03 · R14, 3.8 °C above the fleet median. 2.8 °C of margin left.
ONE REGULATION · TWENTY-SEVEN MARKETS
The passport stops being optional on 18 February 2027.
Regulation (EU) 2023/1542 requires a battery passport for each LMT battery, each industrial battery above 2 kWh, and each electric vehicle battery placed on the EU market or put into service, reachable from a QR code on the battery itself. The 2 kWh threshold applies to industrial batteries only. Responsibility for ensuring the passport is accurate, complete and up to date lies with the economic operator responsible under Article 77, and can transfer on repurposing or remanufacturing.
- Identity that outlives the spreadsheetSerial numbers, BOM, cell data and factory acceptance records held against the battery itself.
- A record that keeps updatingState of health, cycle count, thermal history and service events written back to the same passport for the whole operating life.
- Evidence when it is contestedWarranty, insurance and resale all turn on what the data says, and on whether it can be shown to be unaltered. The Regulation itself asks that passport data be authenticated, reliable and integrity-protected; our hash chain, timestamps and seals are the technical route we chose to that, not a requirement the law spells out.
ManufacturingBOM, cell data, factory acceptance tests
CommissioningBaseline capacity, imbalance, thermal signature
OperationLive telemetry, SoH, degradation, safety
WarrantyOperation against OEM limits, contractual KPIs and warranty conditions
Second lifeResidual condition evidenced, not guessed. What it is worth still depends on the market.
RecyclingComposition and handover record
OPTIONAL EVIDENCE LAYER
Don't just store battery history.
Prove it.
When a warranty claim, an insurance investigation or a technical dispute arrives, historical data has to be more than a row in our database. Otherwise the other side's first question is the one you cannot answer: how do we know this was not edited afterwards?
-
01
Hash · SHA-256 Every five-minute telemetry block is hashed. Change one sample, one timestamp or one signal name and the hash changes completely. Detects any modification made after the block was sealed. A hash on its own proves nothing; it only becomes evidence once it is bound into the chain below.
-
02
Chain · each block carries the previous hash Blocks are linked, then folded pairwise into a daily Merkle root. Any deletion, insertion or reordering becomes detectable when the chain is verified against the trusted daily root.
-
03
Timestamp · RFC 3161 via a qualified trust service The daily root is timestamped by an independent time-stamping authority rather than by our own clock. RFC 3161 is the protocol; it is a qualified timestamp only when the issuer is a qualified trust service meeting eIDAS Article 42. Provides evidence that this exact root existed no later than the trusted timestamp.
-
04
Electronic seal · advanced or qualified A report issued by the company carries an electronic seal. Where a named person has to stand behind it, an authorised representative signs instead: under eIDAS a seal is created by a legal person and a signature by a natural person, and the two are not interchangeable. PAdES and XAdES profiles are supported according to the trust-service configuration you choose. Supports verification of who issued the record and whether it has been altered since sealing. Qualified configurations carry the additional legal presumptions eIDAS defines; advanced ones do not.
-
05
Anchor · public ledger, optional Where a counterparty will not accept a private archive at all, the daily root is published to a public blockchain. Only the 32-byte cryptographic root is published; no raw telemetry or site identifiers leave the customer environment. Reduces the need to trust Löwentech for later integrity verification. Other trust points remain: the gateway, key management, and which records were selected for export. And it does not prove the sensor read correctly in the first place, which no cryptography can.
How the other side checks it
They recompute the hashes from the data you sent, rebuild the Merkle path, compare it to the
timestamped root, and verify the seal. Four steps, standard tools, no account with us required.
If verification succeeds, the recipient can independently confirm that the exported record matches
the sealed dataset and has not been altered after sealing. That materially strengthens your
evidentiary position in a warranty, insurance or technical dispute.
DAILY MERKLE ROOTillustrative subset · a full day is 288 five-minute blocks
87d2…c4af
VERIFIED
ONE ASSET · DIFFERENT QUESTIONS
Turn technical telemetry into stakeholder confidence.
Is my battery working correctly?
Where am I losing performance or revenue?
Was the system operated within specification and contractual limits?
What happened, and does it change the asset risk?
TWO ASSET CLASSES, ONE LAYER
Stationary storage and electric fleets.
Most battery analytics platforms come from one side or the other. This one was built for electric trucks and buses first, then pointed at containers, so the same signal architecture, the same decoding framework and the same warranty-monitoring engine serve both, each configured for its own asset class.
Grid-scale BESS
- Site, container, rack and module resolution
- Dispatchable energy, constrained capacity and revenue impact
- Thermal deviation against the fleet median
- Warranty envelope and equivalent full cycles
Electric trucks, buses and machinery
- The same CAN-native ingest, over the air
- Pack health per vehicle and across the fleet
- Duty-cycle evidence for conversion type approval
- Warranty exposure tracked per vehicle against the applicable contract
Compliance and diagnostics in one record
- Many operations platforms hold telemetry without lifecycle passport context
- Many compliance tools manage passport data without continuous operational telemetry
- A strong warranty case benefits from linked lifecycle documentation and integrity-protected operational evidence
- That gap is the reason this product exists
THE SAME LAYER, ON WHEELSDepot Nord · 8 electric buses · service day
1 bus flagged
Same decoder, same warranty logic, different vehicle. Bus 2041 leaves the depot with the fleet and comes back GAP_PP percentage points lower on the same route, which is consistent with cell imbalance contributing to reduced usable range rather than presenting first as a fault code. On a stationary site the same finding reads as a constrained rack; on a bus it becomes lost range and reduced schedule margin.
PLAIN DEFINITIONS
The six terms this page rests on.
Half the arguments in battery analytics are really arguments about definitions: where a number was measured, and against what. These are the ones we use, stated plainly, so you can check whether we mean the same thing you do.
SoHState of health
Usable capacity now, as a share of the capacity the battery had when new. Not the same as state of charge. BMS-reported SoH is an estimate and should be validated against measured capacity when accuracy matters.
EFCEquivalent full cycle
In this platform, EFC is cumulative discharged energy divided by nominal usable capacity; equivalently, bidirectional throughput divided by twice that capacity. Contracts may define the boundary or the convention differently, in which case we follow the contract. Two half-depth cycles count as one EFC, which is why warranty allowances are written in EFC and not in days.
RTERound-trip efficiency
Energy out divided by energy in over a full charge/discharge cycle, measured at the same boundary each time. Where you measure it, at cell, DC bus or grid meter, changes the number by percentage points.
DoDDepth of discharge
How far a cycle runs down the pack. Shallower cycling can reduce degradation for the same throughput, depending on chemistry, temperature, SoC window and C-rate, which is why dispatch strategy shows up in the ageing curve.
dT/dtRate of temperature rise
The derivative, not the value. A cell at 32 °C climbing steadily is a different problem from a cell sitting at 32 °C. Rate of rise can reveal an emerging thermal problem before an absolute temperature limit is reached.
DPPDigital battery passport
The record required by Regulation (EU) 2023/1542 from 18 February 2027 for each LMT battery, each industrial battery above 2 kWh and each EV battery, reachable from a QR code on the battery.
ABOUT LÖWENTECH
Engineering for electric drive, and the diagnostics that keep it honest.
Löwentech is an engineering company in Berlin with two core competences, and Battery Assurance sits on top of both.
The first is turnkey engineering for diesel-to-electric conversion. We do not run the workshop and we do not own the vehicles. The engineering package is ours: component selection and sizing, integration design, the type-approval route, the test programme and the documentation. The conversion itself is carried out by the customer's own staff, in the customer's own facility, after we have trained them on it. That is deliberate, because a fleet operator who can convert and maintain the vehicle in house is not dependent on us afterwards.
The second is CloudDiagnostix, our cloud diagnostics platform: AI-supported deep analysis on live CAN telemetry. Fault-code interpretation, anomaly detection, degradation trends and root-cause work on vehicles several hundred kilometres away. It exists because the vehicles engineered under those programmes had to be supported without sending an engineer to the depot every time a warning lamp came on.
Battery Assurance extends that cloud-diagnostics competence from electric fleets into stationary energy storage, using the same underlying principles across both asset classes. The platform is CAN-native by heritage and interface-agnostic by design: where raw bus access is available we stay close to the source, and where existing BMS, EMS, PCS or SCADA interfaces are available we integrate with those instead. Its multi-OEM architecture reflects the environment it came from: heterogeneous vehicles, multiple control systems, and real diagnostics across different manufacturers.
Berlin, GermanyEngineering and operations
Turnkey conversion engineering packageEngineering, integration design, approval route, documentation and training. Implemented by the customer's own team.
CloudDiagnostixCloud diagnostics platform, in production
AI-supported deep analysisAnomaly detection and root cause on live CAN
Multi-OEM by designCells, BMS, PCS and EMS from multiple vendors
Type-approval routeUN R100 and conversion approval, documented
Battery passport focusEU 2023/1542, ahead of Feb 2027
Two asset classesStationary storage and electric fleets
TALK TO THE ENGINEERS
Ready to See Inside
Your Battery?
Connect your existing BMS, EMS, PCS, CAN or cloud telemetry. Start with one site, establish its operational baseline and see what the data reveals. Our team typically responds within 2 to 3 business days.