Cloud-dependent
Streaming audio and video off the car burns power, raises privacy questions, and stops working the moment connectivity does.
VMS — by GPI International
A low-power embedded system that detects and classifies physical events on and around a vehicle in real time — impacts, someone leaning or sitting on the car, sustained contact, scratches, breaking glass — and reports them through a companion app.
Why it exists
Vehicles are exposed, and detection has been stuck between three bad options.
Streaming audio and video off the car burns power, raises privacy questions, and stops working the moment connectivity does.
Continuous AI inference drains the battery, which is incompatible with monitoring a car that is parked — the situation that matters most.
Naïve sensors fire on passing music, slamming doors and road vibration. Alerts that cry wolf stop being read.
Signal and noise
The second column is the harder engineering problem. A detector that catches everything is easy; one that stays quiet through ordinary life is not.
How it works
Microphones and an accelerometer capture the raw signal from the body of the car.
A small set of discriminative features is computed continuously from that signal.
A low-power gate flags anomalies and rejects the obvious, without waking anything expensive.
A neural stage names the event and returns a confidence, locally, with no round trip.
An ultra low-power stage watches the sensors continuously and decides the exact moment to wake the full AI pipeline. The expensive part sleeps until there is a reason not to — which is what makes always-on monitoring possible on a battery.
All processing happens on the microcontroller. No audio leaves the vehicle, and nothing depends on a connection being available. Models can be improved over the air without changing any hardware.
The data behind it
An automated 360° test rig runs reproducible interactions across a whole vehicle and labels every session into training-ready data — configurable by zone, material, duration and intensity.
The same event, in the same place, at the same intensity, as many times as it takes. That is what separates a dataset from a collection of recordings.
Long stretches of ordinary vehicle life — parked, driving, day, night, every season. It is what makes the suppression figures credible rather than optimistic.
Performance
Demo figures are measured. Production figures are targets, and are labelled as such — a number without its conditions is not a number.
| Event | Demo, measured | Production target |
|---|---|---|
| Kick or punch to a surface | >80% | >95% |
| Person sits on the hood | >80% | >95% |
| Contact near the bumper | >80% | >95% |
| Window smash | >80% | >95% |
| Scratch | >80% | >95% |
Design goals for the production system: disturber suppression above 90%, an always-on sensing budget under 1 mA, and classification within 500 ms of an event beginning.
Where it applies
Design-win driven, with functional-safety expectations and factory integration. The deepest and highest-value path.
Retrofit-friendly and fast to market. Lower integration depth, price-sensitive channels, the quickest route to a fielded product.
Verified event data for claims validation and risk pricing — as much a data service as a sensor.
The same core in adjacent applications, with different environmental and certification constraints.
We can walk through the architecture, the data engine and where it stands today.