Three separate safety systems installed on the same vehicle by three different suppliers are not an integrated system. They are three systems that may or may not interact correctly, maintained by three separate support relationships, with failure modes that occur at the integration points nobody owns. When the BSIS sensor is supposed to activate via the left indicator but the indicator circuit wiring was done by the camera supplier who didn’t specify that connection, the system fails silently in exactly the situation it was supposed to work.
This guide explains how Backwatch integrates cameras, sensors, and MDVR into a single working system — what the integration actually involves at a technical level, and why it matters for both compliance and day-to-day operation.
Camera and sensor systems for commercial vehicles involve four categories of integration that each create potential failure points if not addressed systematically:
Power integration: Cameras, sensors, and the MDVR all draw power from the vehicle’s electrical system. The power supply must be stable — not subject to the voltage spikes that occur on commercial vehicle electrical systems during engine start, alternator switching, and accessory load changes. A supercapacitor or buffer circuit between the vehicle’s power supply and the MDVR ensures that the recorder completes a clean write cycle before power is interrupted, preserving footage that would otherwise be lost when the ignition is turned off.
Video integration: Camera signals must arrive at the MDVR in the correct format for the recorder’s input specification. The video signal path from camera to MDVR — cable type, cable length, connector specification — must be matched to the camera’s output and the MDVR’s input. Signal degradation over long cable runs (rear cameras on articulated vehicles, or cameras at the extremities of long-wheelbase vehicles) requires attention to cable specification or signal amplification.
Trigger integration: The BSIS sensor and CMS camera are supposed to activate when the left indicator is operated. This requires a clean connection to the indicator circuit that reads the activation signal without interfering with the indicator’s function. On some commercial vehicle types, the indicator circuit runs at a different voltage or uses a multiplexed signal that requires an adapter. The MOIS system triggers before moving off — typically connected to the handbrake release or a separate activation switch. Each trigger connection must be verified in operation, not just wired in.
Alert integration: When the BSIS sensor detects an object, it needs to trigger an in-cab alert. The alert signal must reach the driver clearly — audible and visual — without being confused with other vehicle warning signals. On vehicles with existing alarm systems, the Backwatch sensor alert must be distinguishable from existing alarms. The MDVR should also log the sensor event with a timestamp, so that sensor activations are recorded alongside the camera footage for evidential purposes.
The MDVR is not just a recording device — it is the integration hub for the complete safety system. In a properly configured Backwatch installation:
The Backwatch portal receives data from the MDVR via the vehicle’s cellular connection. The portal provides fleet managers with:
The system health monitoring is the practical integration benefit that most fleet managers identify as operationally important. A camera that has lost connectivity — due to a connector failure, lens damage, or cable break — appears in the portal as an offline unit within minutes. The fleet manager knows about the fault before the daily walkaround check, before the vehicle enters a situation where the missing camera coverage creates a risk, and before a FORS audit identifies a non-functional camera that wasn’t in the check records.
Integration is not complete at the point of wiring. Each component requires configuration for the specific vehicle it is installed on:
Yes, where the vehicle’s MDVR supports CAN bus input. CAN bus integration allows the MDVR to receive data directly from the vehicle’s electronic control system — speed data, door status, PTO activation, and other vehicle-generated signals that supplement camera and GPS data. For council refuse vehicles where the compaction cycle and bin lift operation are CAN-bus-controlled, this integration means the MDVR can timestamp lift operations and compaction cycles against the camera footage automatically. CAN bus compatibility should be confirmed for each vehicle make and model at the specification stage.
The BSIS sensor and CMS camera are configured to activate when the vehicle’s left indicator is operated. In practice, this means that on normal motorway or rural driving with no indicator use, the driver is not distracted by continuous nearside camera and sensor operation. When the left indicator is applied — for a left turn, a lane change to the left, or pulling to the nearside — the camera feed appears on the in-cab monitor and the sensor’s detection zone becomes active. If an object is detected, the driver receives the in-cab alert at the same moment they are indicating to move in that direction. The trigger integration ensures the alert reaches the driver at the moment it is most relevant, rather than continuously throughout the journey.
Footage is recorded locally on the MDVR’s SSD storage regardless of cellular connectivity. The portal receives data when connectivity is available — event clips are uploaded when the vehicle re-enters coverage, GPS position updates when the signal is restored. For vehicles operating in areas with intermittent coverage, the store-and-forward capability means that all footage from covered periods is ultimately uploaded to the portal, and all footage from non-covered periods remains accessible on the vehicle’s MDVR until the rolling retention cycle overwrites it. Critical event clips triggered by G-sensor events are prioritised for upload as soon as connectivity is available.
Each Backwatch installation is tested through a documented commissioning procedure before handover. The commissioning test covers: all camera feeds displaying correctly on the in-cab monitor; all cameras recording correctly to the MDVR; GPS signal confirmed and embedded in footage; indicator-activation test for CMS and BSIS; MOIS detection test (walking in front of the vehicle and confirming alert before simulated move-off); G-sensor calibration test; sensor detection zone verification (walking around the vehicle in each sensor’s zone and confirming alerts); portal connectivity confirmed and footage accessible remotely. The commissioning record is provided to the fleet manager as part of the installation documentation set.
Backwatch provides UK-based technical support for all installations — accessible by phone and email during business hours. For components that fail within the two-year warranty period, Backwatch arranges replacement and reinstallation at no charge to the operator. For out-of-warranty failures, replacement components are available and installation can be scheduled with a Backwatch engineer. The portal’s system health monitoring typically identifies component failures before the operator notices them in operation — the support response is initiated based on the health alert, not on a driver report or daily walkaround finding.
Download this free checklist to apply the guidance in this article to your fleet.
Related guides: The Backwatch Approach to Fleet Safety · The Benefits of Working With Backwatch for Fleet Compliance
4 August 2026
Monday to Friday:
8.30am-5.30pm
