Battery State of Charge (SoC)

Battery State of Charge (SoC) is a percentage metric representing the current amount of usable electrical energy stored in a battery relative to its total capacity at full charge. It is the primary variable for energy-aware scheduling.

• Key Measurement Methods: SoC is estimated, not directly measured. Common techniques include Coulomb Counting (integrating current over time) and Open Circuit Voltage (OCV) measurement, often combined with Kalman Filters for greater accuracy.
• Operational Significance: In fleet orchestration, SoC dictates an agent's remaining operational time and is the central input for charge scheduling algorithms and energy-aware routing.

SoC must be interpreted in the context of State of Health (SoH), which represents the battery's degradation. SoH is the ratio of current maximum capacity to original factory capacity.

• Critical Interaction: A reported 50% SoC on a battery with 80% SoH means the available energy is only 40% of the original specification. Scheduling systems must use SoC = (Current Capacity / Original Capacity) * 100%, where Current Capacity is diminished by SoH.
• Impact on Planning: Degradation models that predict SoH fade are essential for long-term charge discharge cycle optimization and accurate Remaining Useful Life (RUL) forecasts.

SoC is not a standalone metric; it is a dynamic constraint within the orchestration middleware. The platform continuously ingests SoC telemetry via the Battery Management System (BMS) API.

• Scheduling Input: SoC levels, combined with energy consumption models, determine an agent's feasible work window before requiring recharge.
• Constraint in Solvers: The battery constraint solver treats SoC thresholds as hard constraints, preventing tasks from being assigned that would deplete an agent below its minimum charge threshold.
• Trigger for Actions: Low SoC triggers real-time replanning engines to route the agent to a charging station, invoking charge queue management protocols.

Effective fleet management defines strategic SoC limits to ensure safety, battery longevity, and operational resilience.

• Minimum Charge Threshold: A safety buffer (e.g., 15-20% SoC) below which an agent is forced to recharge. This prevents deep discharge cycles that accelerate degradation.
• Energy Buffer: A reserved portion of capacity (e.g., 10% SoC) held in reserve for unexpected task allocation changes, route diversions, or emergency maneuvers.
• Recharge Trigger Point: The SoC level (e.g., 30%) at which the scheduler proactively assigns a charging task, considering travel time to the nearest available station.

SoC depletion is non-linear and influenced by multiple real-time variables, making simple time-based estimates inaccurate.

• C-Rate: High discharge currents (high C-Rate) can reduce usable capacity due to voltage sag and internal resistance, causing the reported SoC to drop faster.
• Environmental Temperature: Low temperatures increase internal resistance, reducing effective capacity and distorting the SoC-to-energy relationship.
• Agent Load & Kinematics: Energy consumption models must factor in payload weight, acceleration profiles, terrain, and regenerative braking recovery to accurately predict SoC drop along a route.

SoC data enables advanced energy management strategies that reduce operational expenses and support grid stability.

• Load Shifting: Charging is scheduled to periods of low energy cost or high renewable availability. Agents may operate down to a lower SoC during peak cost periods.
• Peak Shaving: The orchestration platform aggregates fleet SoC to avoid simultaneous high-power charging during utility peak demand windows.
• Energy Cost Function: The scheduler's optimizer uses SoC projections to evaluate the monetary cost of performing a task now (depleting battery for later expensive recharge) versus later, integrating time-of-use electricity rates.

State of Health (SoH) is a metric, expressed as a percentage, that indicates a battery's current condition and ability to store charge relative to its original factory specifications. While SoC measures the current 'fuel level,' SoH measures the overall degradation of the battery's capacity.

• Key Relationship: A battery with 80% SoH can only be charged to 80% of its original capacity. Therefore, a 100% SoC reading on a degraded battery represents less absolute energy (State of Energy).
• Calculation Factors: SoH is estimated from metrics like capacity fade, increased internal resistance, and charge acceptance rate.
• Scheduling Impact: Fleet orchestration systems use SoH to predict realistic operational range and to implement charge discharge cycle optimization strategies that slow further degradation.

Depth of Discharge (DoD) is a metric, expressed as a percentage, that indicates the amount of energy that has been withdrawn from a battery relative to its total capacity. It is intrinsically linked to SoC (DoD = 100% - SoC).

• Battery Lifespan: Deep discharges (high DoD) accelerate chemical wear. Battery degradation models use DoD history to predict capacity loss.
• Operational Strategy: Effective battery-aware scheduling often involves setting a minimum charge threshold (e.g., 20% SoC, or 80% DoD) to avoid deep cycles, preserving Remaining Useful Life (RUL).
• Energy Buffer: Maintaining a deliberate energy buffer by limiting maximum DoD ensures agents have reserve power for replanning or emergencies.

C-Rate is a standardized measure of the charge or discharge current of a battery relative to its total capacity. A 1C rate is the current required to fully charge or discharge the battery in one hour.

• Charge Scheduling: Fast charging protocols often operate at high C-rates (>1C) but generate heat, which a battery thermal model must manage to prevent damage.
• Discharge Impact: High discharge C-rates (e.g., from rapid acceleration or heavy lifting) can cause voltage sag, making the State of Charge (SoC) estimation less accurate and reducing effective capacity.
• Algorithmic Input: Energy consumption models convert an agent's planned movements and actions into an estimated C-rate profile, which is used by charge scheduling algorithms to plan feasible work intervals.

Energy-aware routing is a path planning algorithm that selects a route for a mobile agent by optimizing for minimal energy consumption, rather than just the shortest distance.

• Beyond SoC: It uses an energy consumption model that factors in terrain incline, surface friction, required acceleration/deceleration (and potential regenerative braking), payload, and ambient temperature.
• Integration with Scheduling: This routing is a core component of battery-aware task sequencing and spatial-temporal scheduling. The chosen route directly determines the SoC depletion profile, informing when and where opportunity charging is feasible.
• Objective Function: The route cost is often defined by an energy cost function that combines electricity cost and battery wear.

A charge scheduling algorithm is an optimization routine that determines when, where, and for how long each agent in a fleet should charge to meet operational demands while respecting constraints.

• Core Inputs: It processes agent battery telemetry (SoC, SoH), energy consumption model forecasts, task lists, charging station locations/capacities, and energy cost functions.
• Strategies: It can implement scheduled charging for cost control, opportunity charging for uptime, and load shifting or peak shaving for grid efficiency.
• Output: The algorithm produces a schedule that may involve charge queue management for station contention and defines charging windows for each agent. It is often implemented as a battery constraint solver.

A Battery Management System (BMS) API is the critical software interface that allows the fleet orchestration middleware to communicate with an agent's onboard battery controller.

• Data Ingress: The API provides real-time battery telemetry, including voltage, current, temperature, State of Charge (SoC), and State of Health (SoH) estimates. This data feeds fleet health monitoring and state estimation.
• Command Egress: The orchestration platform can send commands through the API, such as setting charge current limits (informed by C-Rate and battery thermal models) or initiating/stopping a charge cycle.
• Abstraction Layer: It abstracts the heterogeneity of different battery chemistries and hardware, providing a unified data model for the orchestration middleware to make scheduling decisions.