EVANTEON Battery SystemsRequest a Quote

Qualify · Reference TL-012 · Technical review:

What Information Is Required to Engineer a Custom Battery?

A usable brief connects the equipment mission to electrical, mechanical, charging, validation and production decisions. Unknowns need an owner and a resolution method.

Start with the decision ↓

The engineering decision

Build a requirement with measurable acceptance criteria and explicit open decisions. Use it to agree the next engineering review and its required evidence.

Have these inputs ready

  • Application and mission
  • Voltage/current/time profile
  • Mechanical and environmental constraints
  • Markets, validation, volume and lifecycle

Each requirement must reach a verification method

Scroll horizontally to view the full diagram →

Each requirement must reach a verification methodProposed requirement chain. Open inputs stay visible until the responsible review closes them. Mission; Interfaces; Limits; Verification; Production; LifecycleMission01Interfaces02Limits03Verification04Production05Lifecycle06Define the evidence required before the next step
Proposed requirement chain. Open inputs stay visible until the responsible review closes them.

Specify the equipment boundary first

Start with the application, intended use and operating states. Name the equipment interface where voltage and current limits apply. A nominal 24 V or 48 V label leaves maximum charge voltage, minimum loaded voltage and transient tolerance unresolved.

Describe available volume, mass, mounting, connector orientation, service access and environmental conditions. Include charging, communications and safe-state behavior so electrical choices can be assessed within the physical product.

For an existing design, attach controlled drawings, BOM, firmware/configuration and validation reports with a change list. For a new design, state the known constraints and which architecture decisions remain open.

Requirement setScroll horizontally to compare all columns →
AreaRequired inputsVerification output
MissionStates, durations, payload and routeRepresentative duty-cycle test
ElectricalFull voltage window, peaks, duration and repetitionLoaded voltage and thermal acceptance
MechanicalEnvelope, mass, mounting and interfacesDrawing review and integration fit
EnvironmentTemperature, ingress, vibration and storageApplication-specific validation matrix
Charging / controlsSource, recharge window, protocol and fault responseCharge/transition and communication tests
MarketsDestination, transport mode and intended useApplicability matrix
Production / lifecycleQuantities, records, service and change policyRelease and repeat-supply plan

Resolve an incomplete “48 V, 20 Ah” request

Consider a hypothetical robot brief containing only 48 V nominal and 20 Ah. Suppose the later mission review requires 900 Wh at the battery terminals, with only 80% of validated usable energy allocated to the mission. The usable-energy target becomes 1,125 Wh. The nominal 960 Wh arithmetic from the original label cannot demonstrate that requirement.

If the equipment also needs 2.4 kW at a 40 V minimum input, the pack must support a 60 A event with defined duration and repetition. The series/parallel architecture, protection settings and enclosure cannot be finalized until those conditions and the charge-voltage ceiling are known.

900 Wh / 0.8 = 1,125 Wh usable 2,400 W / 40 V = 60 A

Turn missing information into an engineering task

Open-decision registerScroll horizontally to compare all columns →
Missing inputUnresolved decisionNext action
Peak durationSwitch and cell pulse/thermal requirementCapture the operating event
Equipment minimum voltageSag margin and usable energyObtain controller limits; verify at interface
Charger behaviorPower path and recharge timeReview source/charger data and transitions
Destination marketsCompliance scopeComplete application/market matrix
Environmental limitsEnclosure and validation conditionsDefine service and storage envelope
Production recordsAcceptance and containment coverageAgree the batch data schema

Define the review output before requesting it

A first review should return a requirement baseline, unresolved questions, architecture options and the evidence needed to compare them. A feasibility estimate can use explicit assumptions; those assumptions need owners and closure criteria before design release.

Link every critical requirement to a verification method and responsible party. A requirement such as “high current” is not testable. “Maintain at least the agreed terminal voltage during the recorded peak sequence at the specified service conditions” can be translated into a test.

Agree how changes are handled after approval. A different cell, charger, connector, BMS configuration or enclosure can affect validation and production evidence. Keep lifecycle replacements and record retention inside the same controlled process.

Measurement & validation procedure

Application acceptance checklistScroll horizontally to compare all columns →
Test / reviewRecordAcceptance condition
Review completenessKnown values and open-decision registerEvery critical unknown has an owner and resolution method
Link requirements to validationRequirement ID, method, condition and acceptanceCritical functions have measurable criteria
Prepare the engineering handoffBrief, supporting files and requested review outputNext decision and evidence package are explicit

Continue this engineering task

Related engineering guidance

Prepare the evidence for review

  • Mission and current-time profile
  • Equipment/charger data and drawings
  • Markets, environment and validation targets
  • Quantity, timing and production-record expectations
Continue to engineering review

Technical sources & claim support

References support the stated engineering principles. Worked examples use their explicitly stated assumptions.

  1. Molicel INR-21700-P45B product data sheet, revision 1.2 ↗

    Cell specifications; discharge-rate and temperature characteristics

    Cell-specific capacity, impedance and rate/temperature data; worked examples state their own input values.

  2. Texas Instruments BQ76952 data sheet, SLUSE13B ↗

    Sections 7 and 10–12: electrical characteristics, measurement, protection and FET control

    Example of a monitor/protector architecture; capabilities depend on the selected IC and complete circuit.

  3. Texas Instruments BQ25798 data sheet ↗

    Power-path management; battery supplement mode; charge termination

    Low-voltage power-path example covering load sharing, charge termination and battery supplement mode; apply the device voltage and current limits.

  4. IEC 62619:2022 ↗

    Official scope: industrial secondary lithium cells and batteries

    Industrial-cell and battery safety scope; develop the conformity test plan from the full standard and applicable edition.

  5. ISO 9001:2026 — Quality management systems: requirements and official publication status ↗

    Quality management systems; consistency of products and services

    Quality-system context for documented information, process control and traceable production records.

Key claims and evidence
Evidence mappingScroll horizontally to compare all columns →
ClaimBasisReference
Nominal Ah alone leaves system limits unresolvedinferenceMolicel INR-21700-P45B product data sheet, revision 1.2; Texas Instruments BQ76952 data sheet, SLUSE13B
Illustrative energy allocation requires 1125 Wh usablecalculationcalculation
Requirement-to-verification mapping is a proposed workflowworkflowengineering workflow
PROJECT ENQUIRY

Prepare your battery brief.

Start with the information you have. Your selected battery, application and service are already included.

Open as a full page ↗