Vehicle Safety Sensors & Proximity Detection

---

A proximity sensor that fires every time the tipper body cycles is not a safety system — it is noise that drivers learn to tune out, and then to disable. The challenge of sensor specification on UK fleet vehicles is not identifying which zones need coverage; it is specifying sensors that cover those zones accurately without triggering false alerts from the vehicle’s own complex bodywork. A BSIS sensor calibrated for the wrong vehicle profile is operationally identical to no sensor at all.

Backwatch supplies sensors with programmable detection zones, exclusion zones for the vehicle’s own body profile, and the UNECE compliance standards that DVS PSS, FORS, and CLOCS require. Each sensor is calibrated for the specific vehicle it is installed on — not a generic factory configuration applied across the fleet.

Why sensor specification matters

Three failure patterns are common with poorly specified sensor installations:

• False alerts from vehicle bodywork. A rear sensor that “sees” the tipper body during tipping operations generates continuous alerts that drivers learn to ignore. Programmable exclusion zones that mask the vehicle’s own profile are the difference between a usable sensor and one that gets disabled within weeks.
• Indicator-activation logic missing or wrong. DVS PSS requires the BSIS sensor to be active during left turns and below 30 km/h. A sensor that runs continuously generates alert fatigue; one that doesn’t activate on indicator misses the specific risk window the regulation targets.
• Wrong sensor technology for the environment. Ultrasonic sensors are affected by airborne dust at high concentrations and can be attenuated in quarry environments. Radar performs reliably regardless of dust or moisture but requires programmable zones for false-alert management. Specifying the right technology for the operating environment is as important as the position.

Featured products in our sensor range

Sensor specification matrix

Sensor	Technology	Position	Detection range	Activation	Compliance
BWBSIS Sensor	Radar	Nearside blind zone	0–5m programmable, two-zone	Left indicator, <30 km/h	DVS PSS, FORS Silver+, UNECE R151
BWMOIS	Camera-AI	Front, immediate forward	AI pedestrian detection	Vehicle stationary, before move-off	DVS PSS, UNECE R159
BWBSISMOISCOM	Combined radar + camera-AI	Nearside + front	BSIS + MOIS in single unit	Both standards apply	DVS PSS, UNECE R151+R159
BWFR77GHZ	77GHz radar	Front	Extended-range radar	Stationary alert	DVS PSS (MOIS)
BWAI	AI camera + radar	Various positions	Multi-zone AI detection	Configurable	DVS PSS, AI fleet programmes
BWB07 Ultra Sonic Sensor	Ultrasonic	Close-range (rear, blind spots)	0–2m	Reverse gear or continuous	Supplementary detection

Sensor types by function

BSIS — Blind Spot Information System (nearside)

The BSIS sensor — the BWBSIS — is the UNECE Regulation 151-compliant nearside detection system required by DVS PSS and FORS Silver+. Two-zone programmable: warning zone (0–5m) and alert zone (0–2m). Indicator-activated to prevent continuous false alerts during motorway running. Mounting position and exclusion zone configuration is per-vehicle — particularly on tippers and articulated configurations where the body profile creates false-alert risk.

MOIS — Moving Off Information System (front)

MOIS addresses the specific risk of moving-off pedestrian fatalities. UNECE Regulation 159 requires AI-based pedestrian detection covering the area directly ahead of the vehicle at ground level — the zone the driver cannot see from the cab in a high-driving-position HGV. Three options:

• BWMOIS — dedicated camera-AI MOIS unit
• BWFR77GHZ — 77GHz radar variant for vehicles with extended bonnet profiles
• BWBSISMOISCOM — combined BSIS+MOIS in a single mounting position (useful for retrofitting older vehicles with limited mounting space)

AI camera-sensor fusion

The BWAI is Backwatch’s AI variant — combining camera and radar with AI processing for pedestrian, cyclist, and vehicle detection across configurable zones. Used by fleets standardising on AI across PSS and FORS programmes, and in driver monitoring applications where the AI processor handles fatigue, phone use, and seatbelt detection alongside pedestrian zones.

Ultrasonic close-range

The BWB07 ultrasonic sensor provides supplementary close-range detection — typically the immediate rear bumper zone (0–2m) on reversing operations. Ultrasonic is lower cost than radar and adequate for confined-zone detection where the vehicle’s body profile is straightforward. For complex profiles (tippers, refuse vehicles), radar with programmable zones is the more reliable technology.

By vehicle type

• Construction tippers: BWBSIS nearside (DVS PSS), BWMOIS or BWFR77GHZ front (DVS PSS), BWB07 rear ultrasonic. Exclusion zones configured for the tipper body profile to prevent false alerts during tipping.
• Refuse collection vehicles: BWBSIS nearside, BWMOIS front (PSS), bin lift zone proximity sensors (LOLER). The bin lift mechanism creates a continuous false-alert source unless the sensor is properly configured to exclude the lift arm’s expected motion path.
• Articulated logistics: BWBSIS nearside with FORS Version 7 (January 2025) positioning to prevent false alerts from trailer articulation. Pre-V7 sensor configurations should be reviewed during next audit cycle.
• Coaches and PSV: BWBSIS nearside (DVS PSS for over-12T coaches), MOIS front for tourist-stop and hotel drop-off pedestrian risk zones.
• Quarry and off-road industrial: Programmable radar with extended outer zone (8–10m on large dump trucks). Higher G-sensor thresholds; radar performs better than ultrasonic in dusty conditions.
• Council fleets: Standard BWBSIS + BWMOIS for refuse and large maintenance vehicles. Light vehicles (street maintenance vans) use BWB07 ultrasonic where appropriate to the risk assessment.

Calibration and configuration

Sensors are not a plug-and-play installation. Each unit requires per-vehicle calibration:

• Mounting position — set to provide coverage of the actual hazard zone at the vehicle’s operating height
• Detection zone configuration — programmable zones set to cover the road-level pedestrian/cyclist zone alongside the vehicle
• Exclusion zones — bodywork (tipper bodies, side outriggers, collection chutes, articulated trailer arc) excluded from detection to prevent false alerts
• Activation logic — indicator-activated for BSIS (DVS PSS requirement), continuous for safety-critical zones, vehicle-stationary for MOIS
• Alert behaviour — in-cab audible/visual alert volume and pattern set for the cab environment

Backwatch installation includes commissioning tests — walking through each detection zone to confirm alerts trigger correctly, and walking through exclusion zones to confirm no false alerts. The commissioning record is provided per vehicle for FORS audit and DVSA inspection purposes.

Installation and support

• On-site fitting across England and Wales — typically 2–3 hours per sensor including calibration
• Weekend fitting available — at no extra cost
• 2-year product warranty on all sensors supplied and installed
• IP69K rated across the range
• UNECE compliance — BWBSIS (R151), BWMOIS (R159) — installation certificates provided per vehicle
• UK-based technical support for sensor configuration, recalibration after vehicle modifications, and audit responses

Frequently asked questions

What’s the difference between a BSIS sensor and a standard proximity sensor?

A Blind Spot Information System (BSIS) sensor meets UNECE Regulation 151, which defines specific performance requirements for HGV nearside blind-spot detection: detection zone coverage area, response time, false-alert rate, indicator-activation logic, and below-30km/h activation. A standard proximity sensor doesn’t necessarily meet these requirements — it may detect objects but at different ranges, with different alert logic, and without the indicator activation that DVS PSS requires. For DVS PSS or FORS Silver+ compliance, the nearside sensor must be UNECE R151 compliant. Backwatch’s BWBSIS is R151-compliant; ultrasonic close-range sensors are not (and aren’t intended to be — they serve a different purpose).

How is MOIS different from a front parking sensor?

MOIS (UNECE Regulation 159) requires AI-based detection that can specifically identify pedestrians ahead of the vehicle and alert before the vehicle moves off from a stationary position. A front parking sensor detects any object at close range using ultrasonic or short-range radar — it doesn’t distinguish pedestrians from other obstacles, and it doesn’t activate before move-off. For DVS PSS compliance, MOIS-specific equipment is required. Backwatch’s BWMOIS, BWFR77GHZ, and BWAI all meet R159; standard parking sensors don’t.

Do my existing sensors need to be replaced for FORS Version 7?

FORS V7 (January 2025) updated sensor positioning rules specifically for articulated vehicles — sensors must not falsely activate from trailer articulation movements during turns. If your fleet uses sensors on articulated configurations installed before January 2025, those installations should be reviewed against the updated standard during your next audit. Rigid HGVs and non-articulated configurations are not directly affected. Backwatch can audit existing installations and provide a compliance report identifying any vehicles requiring sensor reposition.

Why do sensors generate false alerts and how do you prevent it?

False alerts come from two main sources: the vehicle’s own bodywork being detected by the sensor (tipper bodies, collection chutes, trailer arcs), and environmental triggers (other vehicles in tight spaces, kerbs, fixed structures). Programmable radar sensors prevent body-triggered false alerts by configuring exclusion zones that mask the vehicle’s profile from the detection field. Environmental triggers are managed by tuning the alert threshold and activation logic — for example, BSIS sensors only activating below 30 km/h means urban driving alerts are useful while motorway driving doesn’t generate constant noise. Calibration is per-vehicle and requires technician expertise; it’s not a generic factory setting.

Can BSIS sensors be used on the offside (right side) for cyclist protection?

UNECE R151 specifies BSIS for the nearside (kerb side) where the primary cyclist collision risk is — cyclists alongside a left-turning HGV in the UK. Offside (right-side) coverage isn’t required by DVS PSS or FORS, but is best practice on vehicles that frequently overtake cyclists or operate in continental Europe (where the kerb side switches). Backwatch can supply offside BSIS-equivalent sensors with the same technology and detection performance as the nearside; the configuration is independent of the indicator-activation logic the nearside uses.

What’s the failure mode for sensors over time, and how do you detect it?

Sensor failure modes include: connector corrosion (most common in pressure-washed environments), mounting bracket damage from impact or vibration, lens or sensor surface contamination from dust or salt, and electronic failure of the radar or AI processor. Silent failure — where the sensor appears operational but doesn’t actually detect — is the most dangerous mode. Backwatch sensors integrate with the Live View Platform’s system health monitoring, which flags offline or unresponsive sensors in the portal so fleet managers know about faults before the next walkaround check. Daily walkaround checks should include a physical sensor function test (walking in the detection zone to confirm alert fires) — required under FORS Silver+.

Are there sensors that can detect vulnerable road users specifically (cyclists vs cars)?

AI-based sensors (BWAI) can distinguish between pedestrians, cyclists, and vehicles by training the detection model on each class. Standard radar sensors detect any object in the zone but don’t classify it. For most DVS PSS / FORS applications, classification isn’t required — any object in the detection zone should generate an alert. Where classification matters is for advanced fleet programmes (FORS Gold with cyclist-specific routing, or AI-driven coaching programmes that score driver responses to specific VRU events). Most operators start with object-detection sensors and add AI classification for advanced programmes.