EV Charger Management Software: OCPP, Load Balancing, and Diagnostics

# EV Charger Management Software: OCPP, Load Balancing, and Diagnostics

There are two layers of software in EV charging, and they are often confused. One manages energy: when to charge, at what power, to minimize cost and grid impact. The other manages chargers: whether they are online, what firmware they run, whether they are delivering power correctly. This article is about the second layer.

EV charger management software answers one question: are your chargers working right now, and if not, why. Without it, you are driving to sites to check if chargers are working, manually updating firmware, and guessing at uptime. With it, you see problems before drivers do. This guide explains what charger management software does, how OCPP makes it possible, and how to choose between building, buying, or going open-source.

Charger management vs energy management: the confusion

These two terms are used interchangeably, and that causes real problems in procurement. Here is the distinction.

An EMS (energy management system) tells the charger when and how fast to charge. A charger management system tells you whether the charger is healthy enough to execute those commands.

Some platforms do both. Some do one well and the other poorly. If you buy an EMS expecting charger management features, you will be disappointed. If you buy a charger management platform expecting TOU optimization, same result.

For the energy management side, see our EMS buyer's guide. This article covers the charger management layer.

What charger management software actually does

Charger management software connects to chargers via OCPP and provides four core functions.

1. Monitoring and uptime tracking

Real-time status for every charger: online, offline, charging, faulted, reserved. Historical uptime reports by charger, by site, by network. Alerting when a charger goes offline or reports a fault code.

This is the baseline. If your software cannot tell you that charger #7 went offline at 02:14 and came back at 06:30, you do not have charger management. You have a spreadsheet.

2. Remote diagnostics

When a charger faults, the software should pull diagnostic data: error codes, voltage and current logs, temperature readings, communication status. The goal is to diagnose without a site visit.

Good diagnostics answer:

• Is the fault in the charger, the vehicle, or the grid?
• Is it a hardware failure or a firmware bug?
• Can it be cleared remotely, or does it need a technician?

3. Firmware management

Chargers are computers. They need updates for security patches, bug fixes, and new features. Charger management software should support:

• Remote firmware updates over OCPP
• Scheduled updates during low-utilization windows
• Rollback capability if an update fails
• Version tracking per charger

If your vendor requires a site visit for every firmware update, you will spend more on truck rolls than on software.

4. Configuration management

Charger settings: maximum power, connector type, payment options, display language, network settings. These should be configurable remotely, per charger or in bulk.

Bulk configuration matters at scale. Changing the idle screen message on 100 chargers should not require 100 individual logins.

OCPP as the protocol foundation

OCPP (Open Charge Point Protocol) is the language between chargers and management software. Without it, each charger manufacturer invents their own protocol, and you are locked into their backend forever.

OCPP 1.6J vs 2.0.1 for charger management

OCPP 1.6J is the practical standard today. It supports:

• Remote start/stop
• Status notifications
• Firmware management
• Smart charging profiles
• Diagnostics upload

OCPP 2.0.1 adds:

• Improved security (PKI, certificate management)
• Device management model (more granular component monitoring)
• ISO 15118 integration (Plug & Charge)
• Better display and tariff management

For a detailed comparison, see our OCPP 1.6 vs 2.0.1 article. The short version: 1.6J is proven and sufficient for most fleet operations today. 2.0.1 is the future, but backend support is still maturing.

Why open protocol matters

We ship OCPP 1.6J as standard on all FBK POWER chargers. We do not force a subscription to our own backend. This is a deliberate choice.

When the protocol is open:

• You can switch backend providers without replacing hardware.
• You can integrate with third-party platforms (Monta, Driivz, SteVe, and others).
• You can build your own backend if you have the engineering capacity.
• You are not hostage to a single vendor's pricing or roadmap.

When the protocol is proprietary, the vendor owns your operations. One fleet customer came to us paying a per-charger monthly fee in that range for a monitoring dashboard their incumbent bundled with the hardware. For 100 chargers that is a five-figure annual bill for software that reads OCPP status messages. That is $60,000 per year for 100 chargers, for software that should cost a fraction of that.

Build vs buy vs open-source

There are three paths to charger management software. Each has tradeoffs.

Option 1: Build your own

Best for: fleets with in-house software teams and unique requirements.

Pros:

• Complete control over features and roadmap.
• No per-charger licensing fees.
• Deep integration with existing dispatch and telematics.

Cons:

• 6-12 months of development before you have basic monitoring.
• Ongoing maintenance burden.
• OCPP implementation is harder than it looks; edge cases abound.

Option 2: Buy commercial

Best for: fleets that want proven reliability and support.

Pros:

• Faster deployment (weeks, not months).
• Vendor support and SLA.
• Regular updates and security patches.

Cons:

• Per-charger or per-site licensing fees.
• Feature roadmap controlled by vendor.
• Integration with custom systems may require professional services.

Common commercial platforms include Monta, Driivz, and others. We do not endorse specific vendors; evaluate them against your requirements.

Option 3: Open-source

Best for: technical teams with budget constraints and tolerance for DIY.

Pros:

• No licensing fees.
• Full source code access.
• Community support for common issues.

Cons:

• You are the support team.
• Security patches depend on community activity.
• Integration and customization require development work.

SteVe is a widely used open-source OCPP backend. It handles basic charger management well but lacks advanced features like automated demand response or sophisticated analytics.

Evaluation criteria for charger management software

Use this checklist when comparing platforms.

The OCPP compatibility test

Before you commit to any platform, run this test with your actual charger model:

1. Connect the charger to the platform via OCPP.
2. Start a charging session remotely.
3. Stop the session remotely.
4. Push a firmware update.
5. Pull diagnostic logs.
6. Change a configuration parameter (e.g., max power).
7. Simulate a fault and verify the alert.

If any step fails, ask why. Some platforms claim OCPP compliance but implement only the subset they need. Others have bugs with specific charger firmware versions. Test before you buy.

Common integration pitfalls

1. Assuming OCPP compliance means full compatibility

OCPP is a protocol, not a guarantee. Implementation details vary. Some chargers send meter values every 15 seconds; others every 60 seconds. Some support all smart charging profile types; others support only a subset. Test the specific charger-backend pair.

2. Ignoring network reliability

Charger management software assumes a stable internet connection. If your depot has flaky cellular coverage, chargers will appear offline when they are actually fine. Plan for local caching and store-and-forward behavior.

3. Overlooking user permissions

A fleet operator needs different access than a maintenance technician. A driver needs different access than a facility manager. If the software has only one user role, you will either over-permission or under-permission your team.

4. Forgetting about data ownership

Some platforms claim ownership of your charging data. Others restrict API access to prevent you from exporting data to competitors. Read the terms of service. Your operational data belongs to you.

5. Skipping the pilot

Connect 2-3 chargers to the platform and run for one month before you commit to 100. The pilot reveals integration issues that demos hide.

The uptime benchmark

Managed operations make a measurable difference. The Sinopec deployment we support runs 100+ sites and 400+ ports with 99.2% uptime. That uptime is not from the chargers alone; it is from a management layer that catches faults before they strand drivers, schedules firmware updates during low-utilization windows, and alerts technicians with diagnostic data already attached.

Without charger management software, 99.2% uptime is not achievable at scale. You might hit it with 5 chargers and a diligent technician. You will not hit it with 50 chargers across 10 sites.

Bottom line

Charger management software is the operational layer that keeps chargers running. It is distinct from energy management, which optimizes cost and grid impact. OCPP 1.6J is the protocol foundation that makes charger management possible without vendor lock-in.

When you evaluate platforms, test OCPP compatibility with your actual charger model. Run the 7-step compatibility test. Choose build, buy, or open-source based on your team's capacity and your fleet's scale. And insist on data ownership: your operational data is yours.

If you are evaluating charger hardware, ask for OCPP documentation. Our chargers ship with OCPP 1.6J support and no forced subscription. We can provide compatibility documentation for common backends on request. For a deeper look at OCPP versions, see our OCPP 1.6 vs 2.0.1 comparison.

We can provide compatibility documentation for common backends on request.