Frequently Asked Questions

No need to return to the unit to download information; it automatically arrives in your dashboard ready for verification by your team. Then there are several ways to see the information:

Using your sign-in account
Team coordinators can see the results on their dashboard, including which vehicles are persistent offenders and where and when those incidents tend to occur. Verified information is aggregated over all your Roadside Units giving a really useful insight into which vehicles are deliberately breaking the law, and the relative severity.

Automated Reports
Each coordinator can also send the local police electronic reports for each location they look after. These reports are typically an automatically produced email containing prioritised vehicle offenders, with links to allow the police to see the offences directly themselves. Alternatively a CSV of the raw data can be downloaded for combination with other sources before submission to the police. Both AutoSpeedWatch and AutoNoiseWatch 'connect' community teams together so that the police can identify poor and anti-social driving behaviours across locations.

Police/authority direct access
The police can also have direct access to the system. This allows them to see real-time collected intelligence across their entire region, or any subset of it, rather than sifting through individual data logs. They see prioritised specific vehicles offences across multiple locations, and where and when offences tend to occur. The intelligence the police see includes :
  • which vehicles across their region are persistently causing the greatest problem
  • where those specific vehicles tend to offend and when
  • which recorded vehicles do not have Vehicle Duty (Road Tax) or valid MoT
  • where and when to deploy Traffic Enforcement Units for best effect
  • when speeding/noise occurs at each of the AutoSpeedWatch/AutoNoiseWatch locations

API access
The police can also get a real-time data feed into their systems via our API. This allows them to dice-and-slice the data in anyway they need and automatically generate letters, resource schedules, prioritise enforcement, etc.

In all cases the system shows the police where best to prioritise their limited resources to get the largest safety improvements.
Not easily, but then it misses much of the point of the system to move them. Sometimes (for example changes to road layout or parking) it makes good sense and can be done with a little previous coordination and some work from us. The units have been designed to be simple, affordable, and fit-and-forget; as a consequence are designed to be permanently fixed at a single position, and not moved between locations. Currently, the captured data from a unit is synonymous with a physical location, and moving the unit will invalidate all previous data recorded by the unit, requiring administrative data-reconfiguration. The networked nature of the unit means that moving the unit also impacts data for neighbouring units. Moving a unit about tends to reduce the intelligence of the system down towards the data-logging level of existing solutions, removing much of the benefit for the police. So, it is possible, but is not simple and involves service charges we need to make each time a move is made. We find that many people ask about moving units before they purchase, but once installed they tend to want to leave it where it is. It's low cost and it works.
Your coordinator can change multiple parameters used by the Roadside Unit of when and how the unit camera gets triggered. These changes take effect within 5 minutes of making the adjustment.

For AutoSpeedWatch, parameters include zone speed, trigger speeds, exposure, time schedule, etc.

For AutoNoiseWatch, parameters include sound levels, calibration data, exposure, time schedule, etc.
For AutoSpeedWatch:
  • It shows where and when vehicles that persistently speed will be, allowing targeted SEU enforcement.
  • It highlights vehicles without Tax or MoT.
  • Heatmaps show police when each community suffers its most speeding, allowing better SEU scheduling.
  • It collates data from all communities into meta-information, removing the mass of low-level data the police are asked to process.
  • The worst-first approach builds better police-community relationships, keeping the driving public onside.
  • CSW teams remain engaged and productive.
  • Its very presence deters speeding and reduces the scale of the problem.

For AutoNoiseWatch:
  • It shows where and when noisy vehicles tend to be used, allowing targeted Traffic Policing.
  • It highlights noisy vehicles without Tax or MoT.
  • It allows efficient enforcement testing of specific vehicles in controlled conditions, allowing robust conviction evidence.
  • It builds community relationships and leverages on their goodwill in helping address the problem.
  • Its very presence deters excessive noise.
If the Roadside Unit is to be installed on private land then seek the landowners permission, otherwise obtain approval from your local parish council and/or the highways authority in your area. Depending on the installation position, you may need to have Chapter 8 competencies to ensure the safety of you and others during the installation. The installation of traffic and speed cameras is not development as defined in the Town and Country Planning Act 1990, so neither planning permission nor permitted development rights are required for their installation.
The easiest way to do this is to select exactly what you want from the store, selecting payment by BACS/Cheque/Money Order, and complete the checkout process. This will generate a PDF invoice with the correct payment/shipping details and we will email it to you. We don't process the order until payment is received, so if you decide not to proceed to payment then the order will be cancelled..
The unit has been designed to make the installation as simple as possible. One security band and no wiring makes the installation a ten minute job. All the required tools and fittings are included in the box. However, it is important that you first select a good location of the unit as this is crucial in its performance. You should have permission to install the unit (either from the landowner if private land, or the council if not). You must also ensure that your relevant Highway Authority are involved beforehand to ensure the unit causes no risk of distraction, obscuring views, strikes, etc. If the installation is located where pedestrian access is not separated from road traffic (by kerbs, barriers, etc), then you will probably need to use someone who is 'Chapter 8' competent to perform the installation . If in doubt, ask Highways or look it up until you are sure of what to do. We can help you find someone, if needed. The Roadside Unit should be ideally mounted at a height of between 2.4m and 4m, with an ideal height around 2.4-3.2m. See our page on Site Location for details.

AutoSpeedWatch:
We've designed the system to be as reliable and accurate as possible within the physical limitations of the underlying technology. Although it is not Home Office approved for the purposes of evidence to issue a penalty under the Road Traffic Act (it doesn't need to be), it is important that we do not falsely accuse law-abiding drivers. As with any similar radar-based system it works in a very complex radar environment - it therefore has multiple filters and processing constraints to check that it is measuring what it intends to measure and not some interaction caused by other combinations of vehicle movements. If there's doubt we'd rather ignore a speeder than photograph every one. It typically takes between 15 and 60 speed measurements of a vehicle, checks for consistency, and averages the past 5 (always rounds down to the nearest integer speed). It then goes through 9 layers of filtering before taking a image. This works well - whilst individual records can't be used as definitive proof of speeding, multiple records are very compelling..... typically within a few days it becomes very obvious which vehicles are habitually speeding. The networked nature of the system means that bad driving attitude is identified even if a vehicle passes several different units. The system is tested as accurate against other radar based systems and is accurate.....its error margin is < 1mph.

It does not require 'calibration' as (unlike earlier systems) as there is nothing to adjust. Instead a differential frequency comparator means the speed recorded immutably linked to the law of Doppler physics.

AutoNoiseWatch:
The system uses aggregated data to determine which vehicles seem to be breaking the law regarding noise emissions. Rather than incorrectly penalise vehicles due to the uncontrolled real-world environmental conditions, instead it aggregates multiple offences to provide compelling information sufficient to warrant targeted vehicle enforcement using Home Office approved devices under calibrated test conditions. This allows very efficient enforcement costs. Expected accuracy is <0.6dBm,; this should be validated shortly in our system-test phase.

We offer an annual calibration service that tests the accuracy of the AutoNoiseWatch Roadside Unit using specialist test equipment.
Showing 16 to 23 of 23 (2 Pages)