Security solutions
UVSS & vehicle inspection
Inspect what the chassis can hide, at the point where vehicles are still under your control.
Checking what the chassis can hide
Vehicles can conceal threats, prohibited items or unauthorised modifications beneath the chassis. A guard with a mirror and a torch can only see a fraction of that surface, and only when the light, the weather and the traffic queue allow it. Under Vehicle Surveillance Systems (UVSS) capture the full underside of a vehicle as it passes over a camera line, giving the inspection team an image to work from instead of a guess.
Logitech's vehicle-security portfolio includes UVSS for applications that require inspection of vehicle undercarriages. The value is not the camera alone. It is the checkpoint around it: how vehicles are queued, how the image is reviewed, what the operator does when something looks wrong, and how the record is kept so that a decision can be explained afterwards.
What vehicle inspection covers
-
01
Fixed UVSS installations
Permanent under-vehicle imaging built into a dedicated inspection lane, for sites where every entering vehicle follows the same controlled route.
-
02
Portable and mobile inspection
Deployable under-vehicle imaging for temporary checkpoints, events, construction compounds or sites where the inspection point has to move.
-
03
Under-vehicle image capture
Full-width capture of the chassis as the vehicle passes, presented as a single reviewable image rather than a sequence of partial views.
-
04
Automatic vehicle identification
Plate or tag identification tied to the inspection record, so the underside image belongs to a known vehicle rather than an anonymous lane event.
-
05
Recording and evidence
Images stored with time, lane and vehicle reference, and retrievable later for investigation, audit or dispute resolution.
-
06
Integration with CCTV and access control
Inspection events joined to the wider site picture: the overview camera, the driver's credentials, the barrier decision and the access log.
-
07
Inspection workflow
Review stations, operator prompts and escalation steps defined with the security team, so a flagged vehicle has a route to follow.
How an inspection checkpoint is shaped
Where UVSS is used
Under-vehicle inspection suits sites where vehicle entry is a genuine security boundary rather than a traffic formality: airports and airside gates, border posts, government and diplomatic facilities, critical infrastructure, industrial plants, ports, prisons and other high-security premises. The common factor is that a vehicle which should not be there represents a risk that cannot be managed by looking at the driver alone.
- Airport and aviation landside-to-airside transitions
- Borders and controlled crossings
- Government and critical-infrastructure entrances
- Industrial sites, ports and logistics compounds
- Prisons and other high-security facilities
Designing the lane, not just buying the camera
An under-vehicle system only works at a speed and alignment it was designed for. We assess the approach, the queue length the site can absorb, the road surface and drainage, lighting, power and network at the inspection point, and where the operator will stand while reviewing the image. If the lane cannot be made to work with the traffic the site actually carries, that is worth knowing before equipment is ordered.
- Approach geometry, speed control and lane width
- Review station position relative to the driver and the barrier
- Power, network and civil works required at the checkpoint
- Coverage of the queue so the inspection does not become the bottleneck
Confirming capability for your requirement
Vehicle-inspection technology is a broad category with meaningful differences between products in resolution, vehicle speed, environmental rating and integration options. Before we commit to a design, we confirm that the specific configuration required — fixed or portable, the vehicle types involved, the integration expected and the support arrangement — is available and supported for that site. We would rather establish that at the assessment stage than discover it at commissioning.
Implementation and support
A checkpoint is an operating process. It has to work at shift change, in the rain, and when the queue is long.
- Site assessment covering traffic flow, lane geometry, civil works, power and network before specification.
- Installation sequenced with the security team so the checkpoint remains usable during works.
- Commissioning that tests image quality across the vehicle types the site actually sees, not a single demonstration vehicle.
- Operator training covering review, flagging, escalation and the records that must accompany each decision.
- Maintenance covering camera housings, lighting, image verification and the review software, with a defined fault route.
Questions we are asked
Does every vehicle have to stop?
That depends on the design and the site's risk position. Some checkpoints capture at low speed without a full stop; others require the vehicle to halt at a marked point. The trade-off between throughput and inspection certainty is decided with your security team, and it drives the lane design.
Can it work with our existing barriers and access control?
Where the existing systems expose a usable integration route, yes. The inspection event can be tied to the vehicle record, the credential presented and the barrier decision, so the access log and the underside image refer to the same entry rather than two unrelated records.
What happens when an operator sees something suspicious?
That is a procedure question as much as a technology one. We agree the escalation path with your team during design — who is called, where the vehicle is held, how the image is preserved — and configure the system to support it rather than leaving the operator to improvise.
Is a portable system as good as a fixed one?
They serve different purposes. A fixed installation can be engineered around a known lane and usually gives more consistent results at volume. A portable system buys flexibility for temporary or changing checkpoints. We will tell you where the compromise sits for your use.
How long are inspection images kept?
Storage is sized to the retention period you set, based on the number of vehicles inspected per day and the image volume each record produces. Retention should be agreed with the same consideration you apply to CCTV footage.
Related capabilities
Let’s build the right solution
Tell us what you are trying to achieve. We will help you assess the requirement, shape the architecture and identify the technology needed to deliver it.