The battery management system is the component that most determines whether a lithium pack is safe, long-lived, and reliable in the field. Cells store the energy and the format and chemistry set the envelope, but the BMS is what enforces that envelope every second the pack is in service — measuring, protecting, balancing, and reporting. Specifying it poorly undermines an otherwise well-designed pack; specifying it well is what makes the pack a finished, dependable product.
Specifying a BMS means translating two things into a concrete set of parameters: the pack's configuration (how many cells, which chemistry, what voltage and current) and the application's requirements (how it is used, what it must communicate, how it must be protected and certified). This guide walks through what a BMS does and how to specify each dimension, in the order an engineer would actually work through them. (The BMS is engineered around your chemistry and cell-format choices — see our companion guides on choosing a chemistry and a cell format.)
What a BMS Actually Does
A BMS is not a single function but a stack of them working together:
Monitoring — continuously measuring every cell's voltage, the pack current, and temperature at multiple points.
Protection — disconnecting or limiting the pack when any measured value moves outside safe limits.
Balancing — keeping the cells in a series string at matched charge so the whole pack can be used fully and safely.
State estimation — calculating state of charge (SOC) and state of health (SOH) from the measured data.
Communication — reporting status and faults to the host system, charger, or user.
Switching and control — opening and closing the main current path and managing the charge process.
Specifying a BMS is, in effect, specifying each of these layers to match your pack.
Step 1 — Start From the Pack Configuration
Every BMS parameter hangs off the pack's electrical configuration, so define it first:
- Series count (S): how many cells are connected in series. The BMS must monitor and balance exactly this many cell groups — a 13S pack needs a 13S BMS. This is the single most fundamental matching requirement.
- Parallel count (P): how many cells are paralleled per series group, which (with the cell) sets pack capacity and current capability.
- Chemistry: which determines the per-cell voltage window the BMS must enforce.
- Nominal, maximum, and minimum pack voltage: which follow from the series count and chemistry.
Get this anchor right and the rest of the specification follows from it. Get the series count or chemistry wrong, and no other parameter can compensate.
Step 2 — Define the Voltage and Current Limits
With the configuration fixed, set the electrical limits the BMS will enforce.
Per-cell voltage thresholds depend on chemistry. As a representative guide, LFP cells typically charge to around 3.6–3.65 V and cut off on discharge near 2.5 V per cell; NMC and LCO cells typically charge to around 4.2 V and cut off near 2.75–3.0 V per cell. These are starting points only — the authoritative values are the charge and discharge limits on the specific cell's datasheet, and the BMS thresholds should be set from that datasheet.
Continuous and peak current, for both charge and discharge, must be defined from the application's load and charge profile. These figures size the BMS's switching elements and current sensing, and the BMS rating must comfortably exceed the application's worst-case continuous current with margin for peaks. Specify continuous and peak (and the peak's duration) separately — a BMS sized only for the average will fail on inrush or stall currents.
Step 3 — Specify the Protection Functions
Protection is the BMS's primary safety job. A complete specification defines the threshold and the response (limit, disconnect, latch, or auto-recover) for each of:
- Overvoltage (OVP) — per cell, to prevent overcharge.
- Undervoltage (UVP) — per cell, to prevent over-discharge.
- Overcurrent (OCP) — separately for charge and discharge.
- Short-circuit (SCP) — fast disconnect on a hard fault.
- Over- and under-temperature (OTP/UTP) — with separate, tighter limits for charging, since charging a cold or hot cell is a particular hazard.
For each, decide whether the protection latches (requires a reset) or recovers automatically when conditions return to normal, and define the recovery thresholds. The response behavior is as important as the threshold itself.
Step 4 — Choose a Balancing Strategy: Passive vs. Active
Cells in a series string drift apart in charge over time; balancing corrects that drift. There are two approaches.
Passive balancing bleeds charge from the highest cells through resistors, dissipating it as heat. It is simpler, cheaper, and well proven, and it is sufficient for most small and medium packs built from well-matched cells. Its limitations are that it only removes energy (it cannot move it to weaker cells), it is relatively slow, and it generates heat.
Active balancing transfers charge from stronger cells to weaker ones rather than dissipating it. It is more efficient, faster, and better suited to large packs, packs that must extract maximum usable capacity, or packs with greater cell mismatch — at the cost of higher complexity and price.
Specify the approach and the balancing current, which together determine how quickly the pack can correct imbalance. For most cost-sensitive industrial and portable packs, passive balancing is the pragmatic default; active balancing earns its cost in large or performance-critical systems.
Step 5 — Determine State-Estimation Requirements (SOC and SOH)
Decide how accurately the pack must report state of charge, because that drives the estimation method. SOC is usually computed by combining coulomb counting (integrating current) with voltage-based correction against the open-circuit-voltage curve. The catch is chemistry-dependent: LFP's discharge curve is very flat, so voltage gives little information about SOC across much of the range, making accurate estimation harder and placing greater demands on the BMS algorithm. If your application needs a precise fuel gauge on an LFP pack, specify that explicitly.
If the application benefits from tracking ageing, also specify state of health — an estimate of capacity fade and resistance growth over the pack's life — and how it should be reported.
Step 6 — Select the Communication Interface
The BMS reports cell voltages, current, temperature, SOC, SOH, and fault flags to the rest of the system. Specify the protocol the host expects:
- CAN bus — robust and common in electric vehicles and industrial equipment.
- RS485 / Modbus — widely used in energy-storage and industrial systems, good over longer runs.
- SMBus — the smart-battery standard, common in portable and computing devices.
- UART / I2C — simple board-level interfaces for embedded integration.
- Bluetooth — for user-facing monitoring on consumer products.
Specify both the protocol and the data set: which parameters are reported, how often, and which faults are flagged. A BMS that protects the pack but cannot tell the host why it disconnected is incomplete for many applications.
Step 7 — Size the Switching: MOSFET vs. Contactor
The BMS opens and closes the main current path, and the switching technology follows from voltage and current.
MOSFET-based switching is compact, silent, and fast, and suits low- and medium-voltage, low- to moderate-current packs — the majority of portable and light industrial designs.
Contactor- or relay-based switching handles the high currents and voltages of large packs, and is standard in high-voltage EV and large stationary-storage systems, often with a pre-charge circuit to limit inrush.
Specify the switching type, its current and voltage rating, and — for higher-power packs — pre-charge requirements.
Step 8 — Plan Temperature Sensing and BMS Topology
Temperature sensing: specify how many sensors and where they sit. A single sensor is rarely enough for anything but the smallest pack; larger packs need sensors distributed to the locations most likely to run hot so the protection limits reflect real cell temperatures.
Topology: this follows from pack size. A centralized BMS wires every cell to one board and suits small and medium packs. A distributed (modular, master–slave) BMS places slave boards on each module reporting to a master, which reduces wiring, improves scalability, and is standard for large EV and ESS packs. Specify the topology that fits your pack's size and module structure.
Step 9 — Standby Current, Diagnostics, and Certification
Three considerations are easy to omit and costly to retrofit:
Standby (sleep) current matters for any product that sits idle between uses. A BMS that draws too much in standby will flatten the pack during storage or shipping; specify a low-power or sleep mode and its current if idle time is significant.
Diagnostics and fault logging — specify whether the BMS should record fault events and history for field diagnosis and warranty support.
Certification — the BMS is part of the pack's safety case for standards such as IEC 62133 and UN 38.3. Specifying its protection behavior and documentation early avoids rework later in the certification path. (See our guide on battery certification requirements.)
Off-the-Shelf vs. Custom BMS
A standard, off-the-shelf BMS is the right choice when an existing board already matches your series count, chemistry, continuous and peak current, communication protocol, and mechanical envelope. It is faster, cheaper, and proven.
A custom BMS becomes justified when those requirements are not met by available boards — an unusual series count, a specific protocol or data set, a tight or non-standard form factor, particular protection behavior, or integration the application demands. Between the two sits a configurable or semi-custom path, where a standard platform is parameterized to your pack. Decide deliberately: a custom BMS adds cost and lead time and should be chosen because the application needs it, not by default.
A BMS Specification Checklist
When scoping a custom pack, these are the parameters to define and hand to a supplier:
- Configuration: series count (S), parallel count (P), chemistry, nominal / max / min pack voltage
- Voltage limits: per-cell OVP and UVP thresholds (from the cell datasheet)
- Current limits: continuous and peak charge and discharge current (with peak duration)
- Protection: thresholds and response for OVP, UVP, OCP (charge/discharge), SCP, OTP/UTP — and latch vs. auto-recover behavior
- Balancing: passive or active, and balancing current
- State estimation: required SOC accuracy (note LFP flat-curve needs), and whether SOH is required
- Communication: protocol (CAN / RS485 / SMBus / UART / I2C / Bluetooth) and reported data set
- Switching: MOSFET or contactor, rating, and pre-charge for high-power packs
- Temperature: number and placement of sensors
- Topology: centralized or distributed
- Standby: sleep mode and idle current target
- Diagnostics & certification: fault logging, and applicable standards (IEC 62133, UN 38.3, others)
- Mechanical: board size, mounting, connector types
How We Approach BMS Specification
At PackForge Energy, the BMS is specified from the pack and the application together — never bolted on at the end. We work from your configuration, electrical limits, protection and certification requirements, and communication and integration needs to define a BMS specification, and we advise where an off-the-shelf board fits and where a custom or configurable solution is warranted. The result is a BMS matched to the chemistry, format, and use case of your pack rather than a generic board the design has to accommodate.
If you are scoping a custom lithium battery pack, our engineering team can help you turn your application requirements into a complete BMS specification and design the pack around it.