What Should Remote Charger Monitoring Show?

Start with the information needed to answer a simple question: is each charger available and working as expected?

• Charger identity and serial number
• Online or offline status
• Whether a connector is attached to a vehicle
• Whether a charging session is in progress
• Energy delivered during the current session
• Completed and interrupted charging-session records

This visibility helps an operator distinguish between an unused charger, a vehicle that was connected but did not start charging, and a session that stopped before delivering the required energy.

Remote visibility only helps when somebody reviews it. If a platform does not provide proactive alerts, the depot should define routine dashboard checks around important charging windows—for example after vehicles return, during overnight charging and before dispatch.

Use Charging Records to Investigate Repeated Problems

A single failed session does not always identify the source of a problem. Reviewing the charger, connector, RFID card, session time, duration, energy delivered and completion status provides a clearer starting point.

Exportable session records and reports can help teams identify recurring patterns. Several interruptions on one connector may point to an equipment or communication issue. Failures involving one vehicle may require a different investigation. Repeated problems at the same time of day may also justify checking the network connection or operating process.

These records support diagnosis; they do not replace technical inspection. Combine dashboard review with the simple physical checks in our DC EV charger maintenance checklist for fleet depots.

Which Maintenance Tasks Can Be Handled Remotely?

Depending on the equipment and authorised user permissions, a charger management system can reduce the number of occasions on which an engineer must visit merely to collect basic information or perform a supported reset.

Useful remote maintenance functions can include:

• Viewing charger status and diagnostic information
• Restarting the charger after an appropriate fault review
• Updating charger firmware through OTA deployment
• Reviewing or changing supported configuration parameters
• Managing RFID card settings
• Configuring the OCPP platform address

Remote maintenance is not remote repair. Damaged cables, connectors, enclosures, cooling components and internal electrical equipment still require safe on-site inspection by authorised personnel. A fault that returns after a restart should be investigated rather than repeatedly cleared.

Keep Charger Management Separate from Fleet Scheduling

Fleet operators and charge point operators may already use specialist software for route planning, vehicle telematics, energy optimisation, public payments or multi-brand charger networks. A manufacturer CMS can serve a narrower purpose: monitoring, maintaining and configuring the charging equipment supplied for the site.

This distinction matters when specifying a project. Charger status and charging-session data do not automatically provide vehicle state of charge, departure priorities or automatic charging schedules. Those functions depend on the wider software, vehicle data and system integration. Our departure-priority charging guide explains the operational information needed to build a vehicle schedule.

OCPP provides a standard way for chargers and management systems to communicate, but supported functions still depend on the protocol version, implementation and commissioned configuration. Compatibility should therefore be confirmed for the actual charger and platform combination.

When Is Simple RFID Management Enough?

A small private depot may need to identify users and allocate charging costs without deploying a public payment platform. A closed-loop RFID arrangement can meet this limited requirement.

Each RFID card can be assigned its own identifier and balance. The site sets an electricity price for the charger, and charging costs can be recorded against the card as energy is used. Administrators can then review balances and transaction records within the private system.

A three-level account structure—Administrator, Site and Cardholder—keeps overall system management, individual-site access and card use separate. This approach is suitable for controlled internal users; it is not a substitute for public contactless payment, roaming, complex tariffs or full CPO billing.

Match Remote Operations to Serviceable Hardware

Software visibility is most useful when it is paired with equipment that can be maintained efficiently. The Injet Ampax is a modular standalone DC charger available in 60–320kW configurations for fleet depots and commercial charging sites.

When Ampax is connected to Injet CMS, authorised teams can view charger and connector status, examine session records, perform supported restarts and diagnostics, deploy OTA updates and manage relevant configuration without starting every investigation at the charger.

Ampax supports OCPP 1.6J, with an OCA-certified implementation, and also lists support for OCPP 2.0.1. The required protocol version and functions should be specified for each project. Injet CMS itself is intended to manage Injet AC and DC charging equipment rather than operate as a hardware-agnostic CPO platform.