State of Energy (SoE) is a metric, expressed in watt-hours (Wh), that indicates the absolute amount of usable energy remaining in a battery, accounting for its current State of Health (SoH) and operating conditions. Unlike State of Charge (SoC), which is a simple percentage of capacity, SoE provides a direct, physics-based measure of how much work an agent can still perform before depletion.
Glossary
State of Energy (SoE)

What is State of Energy (SoE)?
State of Energy (SoE) is a critical metric for predicting the remaining operational runtime of a mobile agent, expressed in absolute energy units rather than a simple percentage.
SoE is derived by multiplying the battery's nominal capacity by its current SoC and then scaling by its SoH factor, which accounts for permanent capacity fade. This value is further adjusted by the real-time Battery Thermal Model and discharge rate, as higher temperatures or a high C-Rate can temporarily reduce the available energy, making SoE a dynamic input for Energy-Aware Routing and Battery-Aware Task Sequencing.
Key Characteristics of State of Energy
State of Energy (SoE) provides a direct measurement of remaining usable energy in watt-hours, offering a more actionable metric than percentage-based State of Charge for operational planning.
Absolute Energy Quantification
SoE is expressed in watt-hours (Wh) or kilowatt-hours (kWh), representing the total usable energy reservoir. Unlike SoC, which is a relative percentage, SoE accounts for State of Health (SoH) degradation and current operating conditions.
- A battery at 80% SoH with a nominal 1000Wh capacity has a maximum SoE of 800Wh
- SoE decreases non-linearly with temperature and discharge rate
- Provides fleet operators with a direct range-remaining calculation
SoE vs. State of Charge (SoC)
While SoC indicates the percentage of nominal capacity remaining, SoE reveals the actual usable energy. Two batteries with identical 50% SoC can have vastly different SoE values due to age, temperature, and load.
- SoC: 50% of 1000Wh nominal = 500Wh theoretical
- SoE: 50% of 800Wh actual (degraded) = 400Wh usable
- Critical for heterogeneous fleets where battery age varies across agents
- Prevents premature task termination by basing decisions on real energy reserves
Temperature-Dependent Dynamics
SoE is highly sensitive to ambient and internal battery temperature. Low temperatures increase internal resistance, reducing the extractable energy from the same electrochemical state.
- At -10°C, available SoE can drop by 20-30% compared to 25°C
- Battery thermal models feed temperature data into SoE calculations
- Orchestration systems use SoE to pre-warm batteries before high-demand periods
- Ensures agents are not dispatched to cold zones with insufficient energy buffer
Integration with Energy-Aware Scheduling
SoE is the foundational input for battery-aware task sequencing and charge scheduling algorithms. Task allocation engines query each agent's SoE to determine feasible work assignments.
- Tasks are matched to agents based on predicted energy consumption vs. available SoE
- Energy cost functions use SoE to optimize for time-of-use electricity rates
- Prevents dispatching an agent to a task that exceeds its remaining usable energy
- Enables opportunity charging decisions when SoE drops below minimum thresholds
Estimation via Coulomb Counting
SoE is commonly estimated using Coulomb counting—integrating current flow over time from a known starting point. This method tracks energy entering and leaving the battery.
- SoE(t) = SoE(initial) - ∫ I(t) × V(t) dt
- Requires periodic recalibration against open-circuit voltage (OCV) measurements
- Drift errors accumulate over time without correction from a Battery Management System (BMS)
- Modern BMS units combine Coulomb counting with Kalman filtering for high accuracy
Operational Safety Buffers
SoE directly informs the minimum charge threshold and energy buffer settings in fleet orchestration. These buffers reserve a portion of SoE for contingencies rather than productive work.
- A 1000Wh agent with a 10% energy buffer reserves 100Wh of SoE
- Buffers cover emergency maneuvers, unexpected diversions, and BMS estimation errors
- Charge depletion strategies trigger recharge when SoE reaches the buffer boundary
- Prevents deep discharges that accelerate battery degradation
Frequently Asked Questions
Clear, technical answers to the most common questions about State of Energy (SoE) and its role in battery-aware fleet orchestration.
State of Energy (SoE) is the absolute amount of usable energy remaining in a battery, expressed in watt-hours (Wh). It accounts for the battery's current State of Health (SoH) and real-time operating conditions like temperature and discharge rate. In contrast, State of Charge (SoC) is a simple percentage (0-100%) indicating the relative charge level compared to the battery's nominal capacity. SoC is a fuel gauge; SoE is the actual distance you can travel. For example, a degraded battery at 100% SoC might only hold 80% of its original SoE, meaning a robot relying on SoC alone could fail mid-mission. SoE provides the ground truth for energy-aware scheduling by converting a percentage into a physically meaningful, actionable quantity.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding State of Energy (SoE) requires context from related battery metrics, operational strategies, and scheduling algorithms that together form the foundation of battery-aware fleet orchestration.
State of Charge (SoC)
State of Charge (SoC) is the most common battery metric, expressed as a percentage (0-100%) indicating remaining capacity relative to a full charge. Unlike SoE, SoC does not account for State of Health (SoH) degradation or temperature effects.
- Analogy: SoC is like a fuel gauge showing how full the tank is
- Limitation: A battery at 100% SoC but 70% SoH actually holds far less usable energy than a new battery
- Relationship to SoE: SoE = SoC × SoH × Temperature Derating Factor
- Use case: Quick operator reference; insufficient for precision scheduling
State of Health (SoH)
State of Health (SoH) quantifies a battery's current condition as a percentage of original factory capacity. It captures irreversible degradation from charge cycles, calendar aging, and thermal stress.
- Key indicators: Capacity fade, internal resistance increase
- Degradation factors: High C-rates, deep discharges, elevated temperatures
- SoE dependency: SoH directly scales the usable energy calculation; a battery at 80% SoH can only deliver 80% of its nameplate watt-hours
- Tracking methods: Coulomb counting, voltage curve analysis, electrochemical impedance spectroscopy
Battery Telemetry
Battery telemetry is the real-time data stream from the Battery Management System (BMS) that feeds SoE calculations. It provides the raw sensor inputs required for accurate energy estimation.
- Core metrics streamed: Voltage (V), current (A), temperature (°C), SoC, SoH
- Sampling rates: Typically 1-10 Hz for fleet orchestration; higher rates for safety monitoring
- Integration: Accessed via BMS API (CAN bus, Modbus, or MQTT) by the orchestration platform
- Critical for SoE: Temperature telemetry enables dynamic derating of available energy based on real-time thermal conditions
Energy Consumption Model
An energy consumption model predicts the watt-hours an agent will expend on a given route, enabling the orchestrator to compare required energy against available SoE.
- Inputs: Route distance, speed profile, payload mass, terrain grade, acceleration events
- Outputs: Predicted energy draw in watt-hours (Wh) per segment
- SoE integration: The model determines if an agent's current SoE is sufficient to complete a task without mid-route charging
- Regenerative braking: Advanced models subtract recovered energy during deceleration phases from total consumption
Minimum Charge Threshold
The minimum charge threshold is a configurable SoC or SoE lower limit below which an agent is removed from task assignment and directed to charge. It preserves battery health and maintains an operational safety buffer.
- Typical settings: 20-30% SoC for lithium-ion batteries to avoid deep discharge stress
- SoE-based thresholds: More precise than SoC thresholds because they account for degraded capacity
- Safety buffer: Reserved energy for unexpected diversions, emergency stops, or communication loss recovery
- Dynamic adjustment: Thresholds can be raised during peak demand periods to ensure availability
Charge Scheduling Algorithm
A charge scheduling algorithm determines when, where, and for how long each agent should charge, using SoE as a primary decision variable to maximize fleet uptime.
- Inputs: Current SoE of all agents, task queue, energy costs, station availability
- Optimization goals: Minimize downtime, reduce peak power demand, extend battery lifespan
- Constraint types: Station capacity, charging windows, minimum SoE thresholds, time-of-use tariffs
- SoE advantage: Algorithms using SoE rather than SoC make better decisions for degraded batteries, avoiding premature charge triggers

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us