Cleared to work with VerifiedAlarms.
The VerifiedAlarms network is the largest network designed for security in Europe.
In order for manufacturer's equipment to work on it it is necessary for the device to comply with some of the published standards and applications.
Note :: Consideration should also be given to the published EN standards.
Designed to connect alarm systems to CCTV cameras/DVR(Digital Video Recorders)/NVR(Network Video Recorders) for alarm verification and allow intelligent CCTV systems to connect to commercial ARC in a common and consistent format for operators to handle (avoiding operator hop).
For example -
IP based CCTV cameras are used to verify that an alarm raised by an intruder alarm is real. Alarm panel zones and CCTV camera is linked in the network.
A CCTV system (DVR/NVR) raises an alarm that requires an operator to view and react to the event.
In both cases alarm transmission must be by SIA, CID or Ademco formats over a protected standard TCP/IP link. Alarms over Telnet are NOT secure and therefore the device will be open to hacking. Telnet is blocked at the network gateway.
SSL/SSH, or other encryption is necessary for high security alarms. The manufacturer can supply a linux based module for polling/alarms received in the network and a Linux or Windows application for alarms received directly at the ARC in Merlin2DotZero.
Merlin2DotZero can also receive alarms from legacy analogue receivers.
In both modes DVR/NVR and Cameras that support the following will be connected in either "GoFetch" or "GoLive" modes or both.
If the only item of equipment in the field is CCTV (DVR/NVR/Camera) it is acceptable that an alarm is raised by another device (for example an alarm panel) as the devices can be linked in the network. Provided it is possible to use CGI or SDK to request images from individual cameras.
The CCTV device ( DVR/NVR/Camera) can also use either FTP or SCP to send alarm images in JPG format to the data center servers. It is not necessary to send any other form of alarm. SCP will be required when images are not sent using our VPN.
The network does handle some SDK, but ONLY where there is no necessity for human interaction. You should contact admin@initsys.co.uk for more information.
To pan/tilt/zoom and commit other actions to cameras the device should ideally support CGI commands. In addition the ability to fetch images from individual cameras or ranges of cameras is essential. UDP should be avoided where possible.
Alternatively the CCTV system should have its own web sever and allow incoming html requests (web page). This is not ideal as the operator at the control room will not be presented with the exact camera in alarm.
The manufacturer may also provide an SDK BUT this may not transmit alarms, these must arrive in one of the industry standard protocols and forms (insurance requirement). The SDK will ONLY be used to view images and possibly control cameras.
Where the CCTV device does not comply with the above then it is possible to connect to the network using an adapter. The VerifiedAlarms adapter takes the alarm spot monitor output and an alarm trigger (digital switched output - relay) from the CCTV system. In the case of an event the device will cause the alarm to be raised at the ARC in the proper format.
The ARC can either view the spot monitor output (recommended as it should follow the alarm triggers). If the DVR has web page or CGI control commands then the ARC can view the images from all cameras in live mode. The adapter also provides a one way audio channel to the site and a switched output.
