Standard · Industrial batteries

IEC 62619 battery testing

Functional and system safety for industrial lithium batteries. OEM specs often mix it with UN 38.3 and the EU Battery Regulation, without clear mapping Spec → test → evidence.

  • In-use safety
  • Spec → standard
  • Audit-ready
IEC 62619 · clause trace3 of 4 covered
  1. SYS-REQ-0211Cell overcharge§7.2.1OverchargeOK
  2. SYS-REQ-0224Thermal abuse§7.2.4Thermal abuseOK
  3. SYS-REQ-0230External short circuit§7.2.2External shortOK
  4. SYS-REQ-0241Cell propagation§8.2Gap
Excerpt · demo data

Context

What IEC 62619 means in the test plan

IEC 62619 is the safety standard for industrial lithium batteries: stationary storage, traction packs outside passenger-car UN 38.3 transport, and many machine and commercial-vehicle programmes.

Unlike UN 38.3 this is not dangerous-goods transport. It is safe behaviour in use and abuse: overcharge, short circuit, thermal abuse, propagation. OEM specs often cite “per IEC 62619” without a clause or acceptance. That is where traceability breaks.

What the plan has to lock

  • Clause, not only the standard number. §7.2 is a different set from §8.2. Without a section number the requirement is not auditable.
  • DUT level. Cell, module or system. Propagation evidence rarely sits on the same level as the cell overcharge test.
  • Protective devices. BMS, fuse, enclosure: what may stay active in the test, what must be bypassed.
  • Boundary vs UN 38.3 and OEM. The same physical quantity (temperature, shock) has three profiles in three documents.

Cevelar maps spec sentences to clauses and test cases. Gaps stay orange, not in a footnote. See battery validation before the lab.

Impact

Gaps show up before homologation.

Spec → Norm Traceability instead of keyword search
IEC ≠ UN In-use safety vs transport tests
  1. Protection / BMS Prove cut-off, limits, fail-safe behaviour and retest criteria.
  2. Thermal safety Plan events, propagation, isolation, sensors and lab time.
  3. Mechanical load Base norm vs OEM stress profile: duplicate campaign risk.
  4. Documentation Define early which evidence audit and homologation expect.

Distinction

IEC 62619 vs UN 38.3

UN 38.3

  • RoleTransport rules T.1–T.8
  • FocusShipping and transport loads
  • RiskDuplicate transport campaigns

IEC 62619

  • RoleIn-use industrial safety
  • FocusFunction, system, protection concept
  • RiskOpen system-safety evidence
  1. Protection / BMS Which tests prove cut-off and limits? Risk: unclear fail/retest criteria.
  2. Thermal events Propagation, isolation, sensors specified? Risk: underestimated lab time.
  3. Mechanical OEM profile vs base norm clarified? Risk: duplicate campaigns.
  4. Documentation Which evidence for audit/homologation? Risk: rework after the lab.

For heads of validation

Matrix Spec → standard → procedure.

Early gap and conflict detection (IEC vs UN 38.3 vs OEM), cost/sequence estimates and export for Polarion, Jira or audit. Cevelar delivers that from the spec, EU-hosted.

FAQ

IEC 62619 questions

Clause, DUT and boundaries before homologation.

What does IEC 62619 test?

IEC 62619 sets safety tests for industrial lithium batteries, including overcharge, short circuit, thermal abuse and aspects of cell propagation. It is a safety standard, not a transport standard.

How does IEC 62619 differ from UN 38.3?

UN 38.3 is transport (T.1–T.8). IEC 62619 is in-use safety and abuse. Many programmes need both. Without mapping you get duplicate tests or blind spots.

Why do spec-to-clause traces fail?

Because the spec writes “IEC 62619” but not the section, the sample or the pass criterion. The auditor asks first for the clause behind the test case.

How does Cevelar put IEC 62619 into the test plan?

Requirements from the spec are mapped to clauses and test cases. Missing sections stay visible as gaps. Export to Polarion, Jira or Excel, EU-hosted.

Contact

Map IEC 62619 on a real spec.

Book a briefing or start the demo. We reply personally.