Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

07 / 10

Case file

02 · ELV Systems

Under Vehicle Surveillance (UVSS).

Full-chassis scan, the moment a vehicle arrives.

Embedded high-resolution UVSS with ANPR and driver-occupant cameras — a critical first line of defence at every vehicle entry point.

Under Vehicle Surveillance (UVSS) — premium installation context

— Vehicle gate sequence

Under-vehicle screening, made legible.

Gate-A-001 · Phase 01 / 07
01020304050607UVSS DECKANPRDRIVERBARRIEREXIT LOOPCHECKPOINT MAP · GATE AQUEUEANPRUVSSDRIVERBARRIERNTG · UVSS GATE SECTIONVIEWBOX 1200 × 700 · SCALE DIAGRAM

Vehicle is before the gate. ANPR is waiting, UVSS deck is armed, barrier remains closed.

/ The discipline, in detail

How we approach under vehicle surveillance (uvss).

A vehicle gate is the single most predictable threat surface on any high-security site, and the one most often defended with a torch and a hand mirror. UVSS replaces that ritual with an evidentiary record: a full-colour underside scan correlated to the registration plate, the driver's face and the time of arrival, comparable in software to the last twenty passes of the same vehicle.

We engineer the install around the actual approach geometry — speed, deck loading, drainage, ANPR camera angles, and the exit interlock that won't lift the boom barrier until the scan has completed and a clean result is logged. Hardware is rated for tropical humidity, monsoon flooding and dust ingress; software is integrated with the visitor-management and access-control layer so the gate becomes one workflow rather than three.

On record

Every under vehicle surveillance (uvss) engagement is documented end-to-end — design, programming, commissioning, calibration — and handed over with the files our successors would need if we were never to return.

/ Three lenses on the same system

Read it the way you actually need it.

Three short readings of under vehicle surveillance (uvss) — for a non-engineer who needs the picture, an engineer who needs the spec, and a buyer who needs to see the system in operation.

/ In simple terms

UVSS replaces the torch-and-mirror under-vehicle check at high-security gates with an embedded scanner that captures the entire underside of every vehicle in a single pass, tied to the number plate and the driver's face. The system can tell you whether anything has changed under that vehicle since its last visit — and gate-release only happens on a clean compare.

/ Technical explanation

Under-Vehicle Surveillance System (UVSS) is an embedded 4096-line line-scan camera array set flush in the road surface, stitching a full chassis image as the vehicle crosses overhead at 5–30 km/h. ANPR pole-camera reads the plate upstream, driver-camera captures occupant frames, compare-server delta-detects against historical passes for the plate-key, and a hardware-interlocked boom barrier releases only on a clean compare or an authorised operator override. Drainage, heat management, deck-loading and evidentiary retention are all explicit engineering line-items.

/ Real project usage

Installed at Koinadhara State Guest House, Guwahati — the system's audit row is tied through to the building's access-control and visitor-management layer, sub-deck sump and ventilation are engineered to Assam's monsoon-climate spec, and a daily lens-clean plus weekly reference-pass test are sat into the AMC pack.

/ System architecture

The layers, named.

Every layer below is engineered as one piece of the integrated stack. Each carries its own commissioning artefact and its own AMC inclusion.

  1. 01

    UVSS scanner deck — embedded line-scan camera array set flush into the road surface in the approach lane, with a 4096-line stitched scanner head capturing the underside as the vehicle passes overhead at 5–30 km/h. Drainage, deck loading (HS-25 / IRC Class A), and heat dissipation are explicit civil line-items.

  2. 02

    ANPR camera — set on a pole approximately 4 m upstream of the UVSS deck, framing the front number-plate at a 15–25° angle for plate-read against the OCR model. IR illumination night and day for consistent capture regardless of ambient light.

  3. 03

    Driver / occupant camera — side-mounted at door-handle height, 1080p with IR-cut filter, recording occupant frames as the vehicle holds on the deck.

  4. 04

    Compare server — software stack that stores the stitched underside image against the plate-key, performs delta-detection against the previous N passes for the same plate, and flags anomalies (added containers, additional welds, tampered chassis pans) for operator confirmation.

  5. 05

    Barrier interlock — the boom barrier's release is gated by the compare result, the operator's release authority, or the explicit override workflow. The interlock is hardware-wired, not software-trusted.

/ Design considerations

The decisions we take early.

  • Approach geometry — the lane must be straight for 8–12 m before the deck so vehicles cross at a controlled speed and angle. Speed bumps placed upstream of the ANPR camera, not between ANPR and UVSS, so the plate is read clean and the underside is captured at consistent speed.
  • Drainage — the UVSS deck sits in a recess that floods within minutes in monsoon-climate sites if not properly graded. Cross-fall away from the deck and a sub-deck sump with redundant submersible pumps is non-negotiable in Guwahati, Assam, Kolkata and similar.
  • Heat management — the line-scan head dissipates heat into the deck enclosure; tropical-summer ambient at 45 °C deck-surface requires forced ventilation or thermo-electric cooling, recorded in the spec.
  • Whitelist / blacklist policy — the plate-key is the single index that ties the system together. The policy for whitelisting (executive cars), blacklisting (banned plates), and provisional-list (visitor vehicles) is operations-level, but the system must enforce it in software.
  • Evidentiary retention — image and video retention is a clearance-level decision, typically 90 days for general commercial, 1 year for VVIP residences and government, 3 years for high-risk perimeters under explicit retention order.

/ Integration logic

How it talks to the rest.

  • Visitor-management — ANPR plate-read feeds the VMS, which auto-issues an appointment-linked credential or refers the visitor to the manned check-in.
  • Access-control — the boom barrier release is a fail-secure relay from the UVSS controller, gated on a clean-compare result.
  • CCTV — the UVSS event triggers a bookmark in the surrounding CCTV cluster (approach camera, plate camera, driver camera) for synchronised replay.
  • Audit log — every pass writes a tamper-evident audit row with plate, underside-image hash, driver-frame hash, operator id, compare-result, release latency.

/ Failure scenarios

What goes wrong, in practice.

  • Deck flooding — sub-deck sump pump fails, monsoon rain ingresses into the line-scan enclosure, system goes dark on the worst-case day. Mitigated by quarterly sump-pump test, redundant submersible pumps, and a UPS-backed alarm to operations on sump-water-high.
  • ANPR misread on dirty plates — winter dust and monsoon mud reduce OCR confidence below release threshold, gate jams the queue. Mitigated by configurable confidence threshold per shift, manual-override workflow, and a daily plate-wash brief to estate maintenance.
  • Compare false-positive — vehicle modification (added rust-shield, replaced silencer) flagged as anomaly, operator over-uses override and starts to ignore compare results. Mitigated by periodic operator-training refresh, supervisor-side analytics on override-rate.
  • Interlock spoofing — soft-release of the barrier by an authorised user without compare-result, used routinely for VIP vehicles. Mitigated by hardware interlock (not software-only), and audit of soft-release rate per operator.
  • Driver-camera coverage gap — high vehicles (vans, SUVs) frame the driver's chest instead of face, defeating occupant capture. Mitigated by per-vehicle-class camera elevation and pre-commissioning sweep on each vehicle type expected.

/ Maintenance expectations

What the AMC actually delivers.

  • Daily deck-wash and lens-clean of UVSS, ANPR and driver-camera lenses.
  • Weekly sample-pass test with a known reference vehicle, comparing the stitched scan against the baseline.
  • Monthly sub-deck sump-pump test under simulated flood condition.
  • Quarterly OCR-confidence calibration with a set of held-out plates.
  • Annual deck-load and drainage inspection during the dry season, before monsoon onset.

/ Where we deploy this

Active across 4 sectors.

Under Vehicle Surveillance (UVSS) is rarely a standalone brief — it sits inside a wider sector practice with its own codes, expectations and operating rhythm.

/ Sister services

The rest of elv.

A serious brief usually crosses two or three of these. Read across the discipline — we deliver them as one contract.

/ Frequently asked

Under Vehicle Surveillance (UVSS) — what buyers ask first.

Why is UVSS preferred over a hand-held mirror?

UVSS captures every pass with date-stamped, plate-correlated, anomaly-flagged evidentiary records — a hand-held mirror produces no record and depends on operator attention. Every pass — date-stamped, plate-correlated, anomaly-flagged. A hand-held mirror produces no record, depends on operator attention, and slows the vehicle queue. UVSS pays back within months at any high-flow gate.

What's an under-vehicle surveillance system actually doing?

A line-scan camera array embedded flush in the road surface captures a high-resolution image of the vehicle's underside as it drives over the deck. The image is stitched into a single composite, indexed against the vehicle's number plate (via paired ANPR), and compared to previous passes of the same vehicle to detect anomalies (added objects, structural changes).

Where is UVSS appropriate?

Government secretariats, defence sites, embassies, premium hospitality at high-threat profile, certain corporate HQs, and residential where the threat assessment justifies it. The deck integrates flush in the driveway and is invisible to the driver. We deploy where the engagement reflects a real threat model.

Surface-mount or in-ground UVSS?

In-ground (flush with the road surface) is the architectural answer for any new build — no visible obstruction, vehicle drives normally over it. Surface-mount is faster to retrofit and useful for temporary deployments, but it creates a visible bump. We almost always specify in-ground for permanent installations.

How is UVSS integrated with ANPR and the boom barrier?

Through the gate-control logic: ANPR reads the plate, UVSS scans the underside, the access database and difference-check return a result, and the boom barrier opens only when both reads return clean and authorised. Integration is programmed in the access-control platform with a written cause-and-effect rule.

What happens during heavy rain or snow?

The deck has heated transparent panels and active drainage that keep the optical surface usable in rain and dust; performance does degrade in heavy monsoon and we document it in the operational protocol. The AMC includes pre-monsoon and post-monsoon optical recalibration.

· Begin

Begin a
under vehicle surveillance (uvss)
brief.

Tell us about the building, the timeline, and what success looks like a year after handover. We will reply within two working days with a written response, not a sales pitch.

Under Vehicle Surveillance (UVSS) | TechnoGuru