EV Charging Asset Management

What an asset record must contain

• Serial number, model and hardware revision, because revisions differ in ways that matter and nobody remembers which
• Current firmware version, which is the field that goes stale fastest
• Install date, installer and commissioning record
• Location, and its history, since units move more than anyone expects
• Warranty status and expiry, per unit rather than per order
• Ownership, which on a host-owned or partner-financed site is not always the operator
• Maintenance and fault history

Hardware revision is the one most often omitted and most often needed. A fault that affects one revision and not another is unresolvable without it.

Units move

Chargers are treated as fixed and are not. A unit is swapped out for a fault, repaired, and installed somewhere else. Without location history, its fault record follows the site rather than the equipment, which is exactly backwards.

The consequence is real: a unit that has failed three times in three different locations looks like three unrelated site problems, and the actual pattern, which is that unit, stays invisible.

Maintenance history as a pattern

1. 1

   Per unit

   Which individual chargers consume disproportionate effort. There are always some, and they are usually a small number.

2. 2

   Per model and revision

   A fault concentrated on one revision is a design or batch issue rather than bad luck, and it changes what you order next.

3. 3

   Per site

   A site where every unit fails more often is telling you about the installation or the environment, not about the units.

4. 4

   Per installer

   Uncomfortable and useful. Installation quality varies and it shows up years later.

5. 5

   Over time

   A failure rate that is rising is the signal worth acting on, and it is invisible without a history to compare against.

Spares, sized against a real number

Spares are usually sized by intuition, which produces either capital sitting in a cupboard or a unit out of service waiting for a part.

• Size against a measured failure rate. Ours runs near 0.5 percent, about one unit in two hundred
• Weight by lead time. A part that takes eight weeks needs more cover than one available locally
• Weight by consequence. A component that takes a whole site down deserves cover a single-bay component does not
• Place them by geography, since a spare in the wrong city is not a spare
• Include consumables that are not failures: connectors and cables wear out on schedule and should not be treated as incidents

The distinction between wear and failure matters here. A connector reaching its rated insertions is a maintenance item, and counting it as a failure inflates the rate you are sizing against.

End of life

• Decide when to stop repairing. A unit repaired four times is telling you something and the fifth repair is a decision, not a default
• Firmware support has an end, and a unit that can no longer be updated is a security position rather than an inconvenience
• Replacement planning, so end of life is budgeted rather than encountered
• Disposal, including whatever local regulation requires of electrical equipment
• Keep the historical data attached to something after the unit goes, or the site's history disappears with it

What an auditor or a buyer will ask

Asset records matter commercially, not only operationally, and this is usually discovered during a transaction.

• What is owned, where it is, and what it is worth
• Its condition and remaining life
• Warranty position across the estate
• Maintenance history, which is what supports a valuation rather than an assertion
• Which units are host owned or financed, and on what terms

An operator who cannot answer these takes a discount. That is usually the moment the value of the register becomes obvious, and it is far too late to build it.