Reliability Detection #3: Low Power

Low Power Detections: What’s Really Limiting the Charge?

Effective low power detection starts with historical context

Every charger has a number on the sticker.

150 kW. 350 kW. 50 kW.

That number sets an expectation. For drivers, it’s simple: this is how fast my car should charge.

Operators know it’s more complicated.

When a session comes in lower than expected, the immediate instinct is often to explain it away:

• The battery is at a high state of charge

• The vehicle is tapering

• The car can’t accept that much power

And to be fair - those explanations are often correct.

Low Power Isn’t Always a Problem

EV charging is dynamic by nature.

Vehicles taper as they fill. Acceptance rates vary by model. Environmental conditions matter. A 150 kW charger does not mean 150 kW at every moment of every session.

But this nuance creates a challenge.

Because low power can be normal, it becomes easy to assume it always is.

Without clear visibility into what should have happened, operators can unintentionally default to blaming the vehicle, the battery, or the driver’s state of charge — even when the charger itself is the limiting factor.

Low power delivery is a problem.

Strong operators own that.

The responsibility is to determine whether the limitation is expected or avoidable - and to rule out charger configuration, site constraints, or performance issues before defaulting to the vehicle or state of charge as the explanation. 

The Visibility Problem

A charger may be intentionally configured to limit output.

Smart charging profiles may cap power. Load management systems may redistribute capacity across dispensers. In some implementations, power can gradually step down over time as allocations shift.

The driver doesn’t see any of this.

And often, the person answering the support call doesn’t either.

From the outside, it simply looks like underperformance.

Meanwhile, if drivers consistently experience lower-than-expected speeds at a location, they may compare networks - and notice when charging feels faster somewhere else.

Without clear data, it’s impossible to know whether:

• The charger is operating exactly as configured

• A smart charging policy is actively limiting power

• The vehicle is the true constraint

• Or a performance issue is emerging

 

Best Practice: Look for Patterns, Not Anecdotes

One slow session is not enough to diagnose a problem.

Effective low power detection starts with historical context.

Operators should be asking:

• What is the normal delivery profile for this charger?

• What does power typically look like across vehicle types and states of charge?

• Is this session outside the expected range?

Pattern-based analysis - especially using statistical thresholds rather than fixed assumptions - reduces noise while still surfacing meaningful deviations.

This avoids overreacting to normal tapering, while preventing persistent underperformance from being dismissed as “just the car.”

Best Practice: Identify the True Limiting Factor

Detection alone isn’t enough.

The critical step is determining where the limit originates.

Is the charger delivering the maximum power it is configured to allow?

Is a smart charging or load management system intentionally capping output?

Or is the vehicle itself limiting acceptance?

This distinction is operationally important.

If the charger is the constraint - even intentionally - operators need to understand how often that limit is being hit and how it affects driver perception.

If the vehicle is the constraint, support teams should be able to explain that clearly and confidently.

Either way, transparency is key.

In the Moment: Clarity Over Assumption

When a driver asks, “Why am I only getting 72 kW on a 150 kW charger?”

The worst answer isn’t slow charging.

It’s uncertainty.

Best-in-class operations prioritize real-time visibility into power limits and session context, so support teams can quickly determine whether a session is:

• Behaving as expected

• Being intentionally limited

• Or showing signs of abnormal performance

That clarity protects driver trust and improves decision-making.

But explanation is only step one.

Mature operators use low power detection to surface systemic constraints - the patterns that repeat across days, weeks, and sites. If a charger frequently hits a configured ceiling, if smart charging consistently steps power down at peak hours, or if a specific dispenser underperforms relative to its peers, those are not one-off events. They are network signals.

Tracking these patterns over time allows operators to:

• Quantify how often chargers are the limiting factor

• Identify sites where configuration changes could unlock more delivered power

• Detect emerging hardware degradation before it becomes a failure

• Prioritize investments based on real performance data

The objective isn’t just to understand low power in the moment - it’s to systematically remove avoidable power constraints across the network.

When operators can see where power is consistently being left on the table, they can fix it.

Our Approach

At Clockwork, this philosophy drives how we handle low power detection.

We analyze charge history to establish what “normal” looks like for each charger and identify statistically unusual behavior rather than reacting to single sessions. Our Root Cause Analysis engine then evaluates whether the limiting factor originates from charger configuration, smart charging policy, or vehicle behavior.

The goal isn’t just to flag low power.

It’s to make sure operators can clearly see - and confidently explain - what’s really happening, right when it matters.