FAQs

Introduction

This sections contains a list of our clients frequently asked questions. Whilst some are straight forward to answers, other require reference to different sections of the documentation. These answers are, at best, generalised, and any more detailed or site specific questions must instead be directed to the site integrator.

Contents



Questions

The number of radar required, and the radar model, is usually based on a recommendation from Navtech Radar or one of our partners. Although we can make approximate estimates based on maps and drawings, an accurate site design can only be made once a site survey has been completed. We use an online planning tool for the initial estimations and these designs can be shared with customers to visualise how a site would be covered with different radar models.

It is important to note that Navtech Radar will make performance guarantees only if we undertake a site survey and the customer implements the recommended site design.

A Track Engine can support up to ~ 8 radar, so technically the minimum depends on the number of radar. Even for fewer than 8 radar, a second Track Engine can be included in the system as backup for automatic failover.

The system only requires a single Management Server. This handles all the core system functions, such as configuration management, inter-module communication and user management. An additional Management Server can also be included for redundancy with automatic failover.

In theory this is unlimited, but in practice there are limitations based on the total number of connections supported by the Management Server and how easy it is to manage the Track Engines within the Topology manager in the User Interface. Existing production environments are using up to 30x Track Engines.

This is a complex question and is affected by the following factors:

  • Processing Power: the tracker uses sophisticated algorithms that are processor and memory intensive.

  • On-board or Local Processing: the on-board processing module on the CTS350-X and HDR100 series radar can handle the tracking on the radar. This removes a lot of the load from the Track Engine and therefore allows the Track Engine to support more radar.

  • Network Capacity: if lots of radars have to send their raw network data to the same server platform, then it may exceed the default capacity of the hardware.

  • Radar Range: radars with greater range will generate more data and therefore more network traffic and will require more processing power to analyse all of the data.

  • Size of Tracking Area and Total No. of Targets per Minute: busy sites with lots of movement, i.e. a highway, will generate lots of targets for tracking. This will put a heavy load on the tracker, and therefore greater demands on the Track Engine.

As a guideline, when using local trackers (i.e. all trackers running on the Track Engine) we recommend a CPU core and 64MB of RAM per radar. So typically this means a Track Engine can support between 4-8 radar. depending on the model. When using on-board (i.e. the tracker is running on each radar) then the Track Engine can support between 10-20 radar.


 

Safety is everything.