Defining the Evidence Needed Before a DC Charger Firmware Update

Before updating a direct-current (DC) charger, establish what will change, which equipment is eligible and how the operator will recognise a successful result. An installation message saying “complete” confirms only part of the job. The charging services that matter to the site also need to work after the change.
Treat firmware maintenance as an operating decision with a technical owner. The supplier needs to explain the update; the site needs to explain the service it must preserve. Those responsibilities meet in a small, documented test and rollout plan.
Start with the reason for the update
Obtain the manufacturer’s release information for the proposed version. Record the problem being addressed, supported hardware and any prerequisites. A security correction, a compatibility change and a new optional function can justify different priorities and test scopes.
Do not leave a necessary update unaddressed merely because testing takes effort. Instead, ask the responsible parties to weigh the reason for the update against the effect of installing it. The US National Institute of Standards and Technology (NIST) treats acquiring, installing and verifying updates as part of preventive maintenance in its enterprise patch-management guidance.
Preserve the currently installed version and configuration record. If a fault appears later, the operator needs to know which devices changed and when. A mixed estate described only as “latest firmware” loses that reference.
Select representative equipment deliberately
Group chargers by the actual hardware, software and service arrangement. Include the management platform, authorisation method and any site-control dependency relevant to each group. Similar cabinets do not necessarily represent the same configuration.
EVB’s DC charger portfolio separates wall-mounted, floor-mounted and split equipment. Use the installed family as one inventory field, alongside its hardware revision, current firmware and management platform. This makes it easier to select pilot units that represent the rollout group.
A pilot should represent the configurations the update will reach. One lightly used charger on a different backend may be convenient to test, but it may not answer the questions that matter to the busy production group.
Define the service checks before installation
List the functions the site actually uses. These might include a card-authorised session, remote status reporting, an agreed charging limit or a payment route. Keep the list tied to the installation rather than treating every advertised protocol feature as a required test.
The Open Charge Point Protocol (OCPP) provides station-to-management communication, but a version label does not prove that a changed firmware build works with the chosen platform. Check the actual combination and the functions the operator depends on.
For an illustrative pilot, a site could select one representative charger, two vehicle types and its normal access method. The plan should state what is observed before and after the update, which differences are expected and who judges an unexpected result. This is an example of test scope, not a certification procedure.
Agree how an unsuccessful pilot is handled
Ask whether the manufacturer supports restoring the earlier version and configuration. Do not assume downgrade is possible or permitted. If restoration is unavailable, agree another documented route for recovering service before the update begins.
Identify who can pause the rollout, how support is reached and which information should be preserved. An operator should not have to decide during an incident whether to reset equipment repeatedly or continue installing the same version elsewhere.
The decision to proceed needs explicit conditions. A successful charging session with missing records may still be an unacceptable outcome for the site. Conversely, a changed display that the release notes explain is not automatically a service failure.
Expand the rollout with a record of what happened
Retain the pilot’s equipment identity, versions, test conditions, results and unresolved items. When the responsible parties authorise a wider rollout, record its scope and timing. Keep a way to identify equipment that has not yet been updated.
Afterwards, examine relevant service observations without claiming every new incident was caused by the update. Compare evidence and configuration before assigning a cause. This preserves a useful distinction between a change that preceded a problem and a change shown to have produced it.
Good firmware maintenance leaves the site with supported software and an understandable operating history. The objective is a verified change to a working service, not simply a collection of devices displaying a newer version number.