Battery degradation is often hidden until a portable instrument loses runtime or stops operating when needed. A full-charge indication does not necessarily mean that the pack still has its original usable capacity. Capacity fade, imbalance, inaccurate digital estimates, and application-specific load demands can all reduce practical reliability.
A constructive diagnostic approach treats the battery as a serviceable system rather than an invisible or disposable component. The Battery Ecosystem concept connects charging, condition assessment, operating targets, service decisions, inventory control, and replacement planning. The objective is to identify declining performance early enough to calibrate, reassign, or replace a pack before it causes an operational failure.
How a Battery Ecosystem Turns Hidden Degradation into Action
A battery ecosystem creates a feedback path between the pack, the charger, the host instrument, and the people responsible for service. Instead of relying only on the instrument’s remaining-charge display, the system can compare available capacity and battery history with the requirements of the application.
This distinction matters because state of charge (SoC) describes the energy believed to remain at a particular time, while state of health (SoH) describes the condition of the battery relative to its expected or original capability. A battery can show a high SoC while having substantially less total capacity than when new. State of function (SoF) is more application-oriented: it indicates whether the battery can perform the required function under the relevant conditions.
The ecosystem therefore supports four connected activities:
- charging the pack under controlled conditions;
- making degradation and operating readiness visible;
- deciding whether calibration, continued use, reassignment, or replacement is appropriate; and
- maintaining records across a group of batteries.
The resulting decisions should remain tied to measured performance, pack safety, manufacturer limits, and the demands of the equipment. A software indication is useful, but it is not by itself proof that a physically degraded or damaged battery is safe to use.
Setting a Minimum Usable Reserve with MORE
Minimum Operational Reserve Energy (MORE) is a target for the minimum usable energy that should remain available for the intended operation. It is different from simply asking whether the battery has reached a nominal full-charge indication. MORE defines how much reserve the user or service organization wants before the pack is considered marginal for a particular application.
A higher operating target provides a larger margin against unexpected runtime demands, aging, temperature effects, and variation between packs. A lower or more relaxed target may allow a battery to remain in service longer, especially in an application where a shorter duty cycle is acceptable and charging opportunities are frequent. The setting is therefore a reliability-versus-battery-economy decision, not a universal battery-health limit.
For example, a user may choose a reserve appropriate for an ordinary operating day, while a medical, safety-critical, or remote application may require a larger margin. Any percentage used for such a target should be treated as an application-specific example rather than a general recommendation for every chemistry, pack design, or instrument.
The selected target should consider:
- expected operating duration and load profile;
- access to a charger or spare pack;
- temperature and other environmental conditions;
- consequences of an unexpected shutdown;
- manufacturer limits and service guidance; and
- whether the battery’s reported capacity has been independently validated.
A host device can continue to display 100% after charging even when the pack’s full-charge capacity has declined. MORE is intended to make that hidden reduction relevant to the operating decision by comparing the available reserve with a defined requirement. It should not be confused with SoC, rated capacity, or a guarantee of runtime.
Visualizing Battery Condition with Fishbowl
Fishbowl is described in the Battery Ecosystem material as a host-connected user interface for making battery condition easier to interpret. Rather than presenting only a charge percentage, it combines information about current charge, capacity fade, and the selected operating target so that the remaining operating margin is more apparent.
The visual model uses an outer charge indication and an inner or central condition display. In practical terms, the charge indication represents how much energy the battery is currently believed to hold, while the capacity-fade or function indication shows how much capability the pack can provide compared with its expected condition. The target threshold provides a reference for deciding whether the remaining capability is adequate for the intended duty.
As a battery ages or accumulates use, its full-charge capacity may decline. The same displayed charge level can then represent less absolute energy than it did when the pack was new. The distance between current capability and the selected target becomes smaller, reducing the margin available to the user. A visual redline or service indication, where configured, should be interpreted according to the relevant charger and host implementation rather than assumed to be universal.
The values shown may combine direct measurements with estimates maintained by the battery-management system or charger. SoC is commonly estimated from current, voltage, accumulated charge, and operating history. SoH and SoF may also be calculated from capacity tests, usage history, pack data, and application settings. Users should therefore distinguish between a useful diagnostic estimate and an independently measured capacity test.
Using Smart-Battery Data for Life Prediction and Service
Remaining-useful-life estimation should not rely on calendar age alone. A battery’s service condition is influenced by charge and discharge history, depth of use, operating temperature, storage, load, and the amount of capacity that has been lost. Smart-battery data can provide the history needed to make that assessment more consistent.
Relevant fields may include:
- Full-charge capacity (FCC): the capacity the battery-management system currently believes is available after a full charge;
- cycle count: an indication of accumulated use, although the definition of a cycle can vary by system;
- operating target: the reserve or capacity threshold selected for the application;
- cell-balance information: where supported, including differences between cell voltages;
- manufacturer settings and pack configuration; and
- serial number and related identification data.
Not every battery exposes every field, and the information may be stored in the battery, obtained by the charger, or transferred to a host or fleet platform. Cell-voltage differences can provide useful evidence of imbalance in supported battery systems, but they must be interpreted with temperature, load, measurement accuracy, and manufacturer limits in mind.
A digital FCC value or life estimate is not the same as an independently measured capacity. The battery-management system may need suitable charge and discharge conditions to update its estimate, and different algorithms may produce different results. A service decision should compare the reported data with actual runtime, load performance, fault records, temperature behavior, and application requirements.
When reported capacity falls below the selected operating target, calibration or diagnostic service may be appropriate. Calibration can correct the relationship between the battery’s internal estimate and its actual state of charge or capacity. It cannot restore active material, repair damaged cells, remove permanent impedance growth, or return physically degraded cells to new condition.
If calibration does not return the pack to an acceptable and validated condition, the battery may need replacement or reassignment to a less demanding duty. Reassignment is appropriate only when the pack remains safe and its reduced capability is compatible with the new application. Imbalance, abnormal temperature, swelling, damage, fault codes, excessive impedance, or other safety findings can require removal from service regardless of the displayed capacity.
Plug-and-Play Battery Diagnostics from Charger to Fleet
A plug-and-play workflow makes battery information available at progressively broader levels. The charger can provide an immediate indication, a connected host can show more detailed battery condition, and a fleet system can retain information for supervisors and service personnel.
This progression also preserves the distinction between SoH and SoF. SoH concerns the degree of aging or remaining capacity. SoF concerns whether the battery can perform the required function under current conditions. A pack may have acceptable SoH for one low-demand task but inadequate SoF for a high-load or long-duration task.
Three Levels of Battery Visibility
Level 1 is charger-based visibility. Simple status lights or equivalent indications can provide an immediate go, caution, or service message while the battery is connected. In the supplied Battery Ecosystem description, green indicates a go condition and amber calls for calibration. Exact colors, thresholds, and additional service states depend on the charger implementation and should be confirmed in its documentation.
Level 2 adds host-connected visibility. A battery connected to a compatible host through an interface such as USB can expose more detailed information through a user-facing display. Fishbowl is described as the interface used to show battery state of function and related condition information. This level helps the instrument user see that a full charge is not necessarily equivalent to full original capacity.
Level 3 stores and shares the information. Battery records can be made available to fleet supervisors, service managers, or other authorized personnel. This supports comparisons among packs, identification of units approaching a configured threshold, and planning for service or spares. Connectivity, data retention, permissions, and platform availability depend on the implementation.
The three levels are complementary. A charger indication supports an immediate decision, a host interface provides context at the point of use, and fleet visibility supports decisions across many packs. None removes the need for safety inspection or application-specific validation.
Inventory Alerts and Replacement Planning
An inventory view can identify batteries approaching a configured retirement or fringe-capacity threshold. The purpose is not to declare that every pack below a software threshold must be discarded. It is to bring potentially marginal packs to the attention of the people who can verify their condition and plan accordingly.
Advance identification can help a fleet manager:
- reserve working spares before a pack becomes unavailable;
- schedule calibration or diagnostic testing;
- separate batteries by application and expected duty;
- forecast likely replacement needs; and
- avoid discovering several marginal packs during an operational shortage.
Charger-side identification is particularly useful because the pack is already being presented for charging or inspection. Fleet-level records add history and allow service personnel to see whether the same pack has repeatedly approached its limit.
Threshold alerts remain decision aids. Before ordering or retiring a pack, confirm actual runtime, load requirements, safety condition, cell balance where available, temperature behavior, and manufacturer restrictions. A cloud or fleet platform may also require defined connectivity, user permissions, data retention, and privacy controls. Those operational details should be verified for the current platform rather than assumed from the general ecosystem model.
The Battery Endurance Loop
The Battery Endurance Loop describes a lifecycle process rather than a single test: charge the pack, assess its condition, calibrate when appropriate, continue service while it remains suitable, retire it when it no longer meets the requirement, and replace it at the appropriate time.
A practical loop can follow these steps:
- Charge the battery using a compatible charger and record the available diagnostic information.
- Compare its condition with the selected operating target and the demands of the equipment.
- Investigate marginal readings through calibration or additional testing when permitted by the battery and manufacturer.
- Continue using the pack when its measured performance and safety condition remain acceptable.
- Reassign, retire, or replace the pack when calibration cannot restore an acceptable validated condition.
- Update the fleet record so the next service or purchasing decision uses the latest information.
Just-in-time replacement reduces the chance of an unexpected operational failure while avoiding replacement based only on age or an unverified software estimate. It can also reduce unnecessary disruption and premature disposal, but those benefits depend on accurate diagnostics and suitable service controls.
Not every battery can be safely extended. Chemistry, cell design, pack construction, protection circuitry, environmental exposure, physical damage, imbalance, temperature history, and manufacturer limits all affect the decision. A capacity threshold alone is not sufficient when safety or functional faults are present. The correct endpoint is a documented decision based on measured performance, battery data, application demands, and safe operating practice.
References
- BU-924: Battery Ecosystem. (n.d.). http://www.batteryuniversity.com/article/bu-924-battery-ecosystem
- INSTALLATION AND OPERATION MANUAL. (n.d.). https://discoverbattery.com/s4x_files/resources/db-lithium-blue-manual.pdf
- What does SOC & SOH & SOP & SOF Mean for Batttery? Understanding the Battery “Inner World”. (n.d.). https://www.neware.net/news/battery-soc-soh-sop-sof-understanding-the-battery-inner-world/230/196.html
- January 2025 - Article - Cadex Ecomm Platform. (n.d.). https://www.cadex.com/blog/post/january-newsletter
- Staco 924. (n.d.). https://www.stacoenergy.com/products-solutions/products/emergency-lighting-inverters/staco-924.html
- What are SOC and SOH of a battery, how to measure them?. (n.d.). https://www.biologic.net/topics/battery-states-state-of-charge-soc-state-of-health-soh
- Electric Battery SOH: Definition and Calculation | Qovoltis. (n.d.). https://www.qovoltis.com/en/actualites/soh-de-la-batterie-du-vehicule-electrique
- SOC vs SOH: Understanding the Critical Difference in Battery Health Monitoring | Learn | Xbattery. (n.d.). https://xbattery.energy/learn/soc-vs-soh
- Battery in the cloud. (n.d.). https://www.bosch-mobility.com/en/solutions/software/battery-in-the-cloud/battery-in-the-cloud
- SoC and SoH Explained: State of Charge & Battery Health. (n.d.). https://jolt.energy/en/news/soc-and-soh-explained-understanding-state-of-charge