EV Charging Station Management / Site security

EV Charger Tamper Monitoring

A charger that has been forced, struck or opened reports nothing about any of it. It reports a fault, days later, and the operator repairs the same unit again. Sensors mounted on the unit and wired into the charging management platform close that gap: the event is recorded when it happens, with the time and the unit on it.

The sensors we mount on the charger, how they report into the charging management platform, what an operator gets from it, and what happens at the unit when something fires.

Talk about repeat damage

For An operator of public or semi-public sites, repairing the same units repeatedly without knowing why.

01

The sensors we mount on the charger

Hardware fitted to the unit, supplied as part of the charging station management solution. Three things, chosen because they are the three that precede almost every repeat repair.

  1. 1

    Tilt

    Orientation against a baseline taken at commissioning. A pedestal being worked loose, leaned on hard or pulled at shows as a change in angle well before it shows as a broken mounting.

  2. 2

    Impact

    Force applied to the unit, with the magnitude recorded rather than a bare alarm. A vehicle reversing into a bollard and a person attacking a display are both impacts, and the difference is in the trace.

  3. 3

    Panel opening

    The enclosure being opened, which is unambiguous. There is no innocent reading of a service panel open at eleven at night with no job raised against that unit.

The sensors are mounted with the unit rather than built into it, which is what allows them to be fitted to chargers already in the field, including chargers that are not ours.

02

How it reaches your CMS

  1. 1

    The hardware reports to the platform

    The sensors communicate into the charging management system over the site link the chargers already use. No separate alarm panel, no second system to check.

  2. 2

    The event lands with its context

    Time, unit, site, what fired and at what magnitude, whether a session was running, and whether a job was open against that unit. A panel opening with a technician dispatched is maintenance; the same event with nothing raised is not.

  3. 3

    A ticket opens on its own

    Through the same automated ticketing that handles charger faults, routed by what was detected, before anyone is told.

  4. 4

    The response is per site

    Alert, trigger a camera at that moment rather than searching footage later, stop charging where continuing could be unsafe. Returning to service takes a person.

03

What an operator gets from it

  1. 1

    The repeat repair gets a cause

    A unit that fails three times faster than the rest of the estate is either taking heavy legitimate use or taking something else. The event log answers that. The repair record never will.

  2. 2

    Evidence that holds up

    A timestamped event with the unit, what fired and the site state around it is what an insurer or a landlord will accept. An alert saying tamper detected supports nothing.

  3. 3

    Camera footage you can find

    Triggered at the moment of the event, so it is retrieved by timestamp rather than searched for across days.

  4. 4

    Fewer alerts the team ignores

    Because the platform can read a sensor against live session and job data, most of what would otherwise be a false alarm resolves itself before it reaches anyone. An alert the team does not trust is worse than none, since it also creates the impression of coverage.

Want this applied to your own site?

Talk about repeat damage

Technically reviewed by Deepu Joy, Director of Products and Delivery. Last reviewed 2026-09-10.

Frequently asked questions

What does the hardware actually detect?

Tilt, impact and panel opening. Tilt is measured against a baseline taken at commissioning, impact records magnitude rather than raising a bare alarm, and panel opening is unambiguous.

Can it be fitted to chargers we already have?

Yes. The sensors mount with the unit rather than being built into it, so they go onto chargers already in the field, including chargers that are not ours, taken with the station management solution.

How does the alert reach us?

The hardware reports into the charging management platform over the link the chargers already use, and automated ticketing opens a ticket with the time, the unit, the site and whether a session or a job was running against it.

Should the charger stop when something is detected?

Only where continuing could be unsafe. Recording the event with a timestamp always happens first, before any other response, because a response with no record leaves nothing to investigate.

What makes tamper monitoring fail?

False alarms. Reading a sensor against live session and job data is what keeps the rate down: a panel opened with a technician dispatched to that unit is maintenance, and the platform is the only thing that knows.

Repairing the same units repeatedly?

Send the repair history by site and by part. Where the same unit keeps coming back, sensors on it usually answer why within a month.

Talk about repeat damage