Application | Application Type | Description | How many |
---|---|---|---|
Piccadilly | Windows Service | Primary system server. Manages system configuration and coordinates all other services. | 1 per site |
Sentinel | Windows Application | Radar management client (UI). It provides admin functions for installation and commissioning as well as a full operator interface for managing a site. | 1 or more (additional license costs may apply) |
Canary | Windows Service | External interface service. This provides the functions required to integrate with 3rd party systems. | 1 per site |
Cyclops | Windows Service | Camera control service. This provides the logic to administer and control all the cameras on site. | 1 per site |
Bloodhound | Windows Service | Radar tracker. Provides the core tracking capability for each radar. | 1 per radar |
Vault | Windows Service | Database management service. This provides the interface between the database storage engine and the rest of the application. | 1 per site |
Hydra | Windows Service | Data splitter service. This service can be used on legacy radars to allow more than 1 client to connect to the same radar. | 1 per radar |
When considering the system design for Witness, the following points should be taken into account:
The following system diagram illustrates a simple 3 radar system. The setup includes a dedicated server for tracking with 3x Bloodhounds (1 per radar) and a primary server with the remainder of the software. The client software, Sentinel, is run from a standard PC. The two servers can be installed in a data centre or server room whilst the client PC will need to be located with the operators / users.
Witness Cyclops must have network access to any installed IP cameras or video encoders which are being used with Witness. Likewise, Witness Canary must have suitable network access to any third party system.
Note that in this scenario we have used an additional tracking server to cope with the additional Bloodhounds. We have also separated the database function onto a dedicated server. As a system uses more radar it will process many more tracks / targets. If you wish to record these tracks for later analysis or display, then the demand on the database is much greater - hence the requirement for a dedicated server. In addition all the tracks have to pass through Piccadilly for alarm analysis. This means the main server will also be more heavily utilised which is another reason to separate this function from the database.
We strongly recommend that a network diagram is created for every project, This will help identify the equipment needed, any issues in the design but more importantly provide a basis on which the project can be discussed with all those contributing to delivery.
In order to help our own engineers we created a simple set of Vision shapes that can be used to quickly develop network diagrams. Partners, system integrators and customers are welcome to use them. They can be on the download resources page.