Intelligence

The Intelligence module helps you understand what actually happened across your charging network and why, without reviewing raw OCPP logs or individual charger diagnostics.

It automatically analyzes charging sessions and fault events and converts them into clear, actionable insights for:

  • Operations teams
  • Support teams
  • Technicians
  • Management

No configuration is required. Intelligence works automatically on available session and fault data.


What Intelligence Is (and Is Not)

📌

Important

Intelligence does not control chargers, change settings, or resolve issues automatically.

Its role is to explain behavior, surface patterns, and guide decisions.

Think of Intelligence as a continuously running analyst that reviews everything that happened and highlights what matters.


Time Range Selection

At the top of the Intelligence view, you can switch between:

  • Day
  • Week
  • Month

This controls the time window used for analysis.

When to use each view

ViewBest used for
DayIncident review, support cases, recent failures
WeekIdentifying recurring issues and early warning patterns
MonthManagement overview, stability trends, long-term performance

All insights, charts, and metrics update automatically when the time range changes.


Top Insights (AI Summary)

The Top Insights section provides an AI-generated summary of the most important findings for the selected period.

It is designed to answer three key questions:

  1. How healthy is the network overall?
  2. Which chargers require attention?
  3. Are there signs of serious technical breakdowns?

Performance & Impact Snapshot

What this shows A high-level view of how charging failures affected overall network reliability.

This insight evaluates the overall health of the charging network by correlating session failures with their real operational impact, not just fault counts.

Impact levels

LevelMeaning
Low ImpactFailures are isolated and do not meaningfully affect availability or user experience
Moderate ImpactFailures are recurring or clustered and have a noticeable impact
High ImpactFailures are frequent or widespread and significantly reduce charging success
📌

Start here

Use this insight as your first checkpoint when opening Intelligence.


High Attention Chargers

What this shows Chargers (EVSEs) that require technical attention due to recurring or abnormal failure patterns.

This insight focuses on the concentration of problematic chargers, identified through AI analysis of session behavior and fault recurrence.

Risk levels

LevelMeaning
All ClearNo chargers show concerning patterns
Low RiskEarly warning signs on a small number of chargers
Moderate RiskMultiple chargers show recurring issues
High RiskPersistent or escalating faults requiring immediate attention
⚠️

Operational tip Use this list to prioritize inspections, firmware checks, or on-site visits.


Critical Fault Signals

What this shows Indicators of severe technical breakdowns that may affect safety or reliability.

This insight is based on:

  • Critical Fault Rate (share of failures caused by severe technical faults)
  • Overall Session Failure Rate

It answers the question: Are failures pointing to serious technical problems?

Risk levels

LevelMeaning
All ClearNo critical fault patterns detected
Low RiskRare and isolated critical faults
Moderate RiskRepeated critical faults on specific chargers
High RiskFrequent or widespread critical faults indicating serious reliability or safety risk
🔴

High Risk requires action

Chargers flagged here should be reviewed before issues escalate further.


Health and Session Metrics

Below the Top Insights, you will find key metrics for the selected period:

  • Health index – Overall success score for analyzed sessions
  • Analyzed sessions – Total sessions included in the analysis
  • Successful sessions – Sessions completed without faults
  • Fault rate – Percentage of sessions that failed
  • Faults – Total detected failures

These metrics provide context and help validate the insights above.


Failure Distribution

The failure distribution section explains what failed and where the issue most likely originated.

📌

Best practice

Always read Failures by Type and Failures by Origin together.


Failures by Type

What this shows How charging sessions ended.

This chart explains what happened during failed sessions.

Failure typeDescription
Vehicle disconnectedThe cable or vehicle connection was interrupted during the session
Vehicle stopped chargingThe vehicle stopped requesting power while the charger was available
Stopped by userThe charging session was manually stopped by the user
Grid power supplyInsufficient power could be delivered from the local grid or installation
Safety protection activatedCharging stopped automatically to protect people or equipment
Charger hardware or firmware faultInternal charger fault prevented continued charging
Communication errorLoss of communication between charger and backend

Failures by Origin

What this shows Where the issue most likely originated.

This chart explains who or what caused the failure.

OriginMeaning
VehicleCaused by the vehicle or its interaction with the charger
UserResult of a direct user action
On-site powerOriginated from the local electrical installation or grid
ChargerCaused by charger hardware, firmware, or safety logic

Detected Faults Table

The Detected Faults table lists individual failed sessions within the selected time range.

For each session, you can see:

  • Session ID and timestamp
  • Charger and connector
  • Location and operator
  • Fault reason
  • Recommended action
  • Fault origin

This table is usually the starting point for investigating specific issues.


Session Details (Read More)

Click Read more on a failed session to open a detailed chronological explanation.

What the session view shows

  • Charger and connector details

  • Protocol information

  • A step-by-step timeline of OCPP events

  • Key actions such as:

    • MeterValues
    • StatusNotification
    • RemoteStopTransaction
    • StopTransaction

Events are displayed in the exact order they occurred.


How to use the session timeline

Use the timeline to:

  • Confirm whether energy transfer actually started
  • See who initiated a stop (user, backend, or charger)
  • Understand why the session ended
  • Identify unexpected backend logic or automation
🧠

Insight

This replaces manual log inspection and makes complex charging behavior understandable for both technical and non-technical users.


Best Practices

  • Review Intelligence daily or weekly

  • Use Day view for incident and support follow-up

  • Use Week and Month views for trend analysis

  • Prioritize chargers listed under High Attention Chargers

  • Use session timelines when working with:

    • Support cases
    • Hardware vendors
    • On-site technicians