IPfocus IT Integration - The Challenge
In this two part article, the guys from Codestuff explain what is involved in real-life integration projects and how to deal with the unexpected.
Deploying, integrating and configuring an IP based VMS (Video Management System) is seldom a turnkey event. Even a relatively small installation can require careful preparation. There are many pitfalls that can trap the unwary, not least of which is managing user expectations. The site could involve an existing network and equipment, including DVRs, analogue CCTV cameras, monitors and a matrix. A customer may be reluctant to give up on their earlier investment and there may even be an existing VMS in place with which the customer and key staff are familiar.
So when deploying a new system it is important to identify and manage some key stages on the way to achieving a successful installation. These include:
Planning Training Preparation Deployment Maintenance
Though many of these steps are ultimately independent of the actual VMS – the choice of VMS can prove a help or could be a hindrance through the process.
Planning
A careful assessment of the existing infrastructure is required – both in terms of network and existing video equipment. On the network side you need to look at the existing usage, and topology. Video over a corporate network where it is competing for a limited common resource can lead to a very difficult discussion with the customer. Video is a great consumer of network bandwidth but due to the nature of the streaming protocols typically used will tend to give way to other services that move data around the network. For example, a nightly backup could severely impact the quality of video delivery as large quantities of data are moved around at a specific time.
A general corporate network may also be installed with features that would seem very sensible in a normal corporate scenario – but not for a 24/7 video recording system. There have been some examples of network equipment powering down at weekends or overnight as an energy saving measure.
Some parts of a network may be particularly remote, or allow for limited connectivity. Whether for legacy or for logistical reasons the choice of VMS can help out in these cases. If multicast is supported on the network then this can be a sensible choice for streaming from video devices on these poorly served nodes. Another feature of some VMSs is to allow a proxy to take the single stream and make this available to other parts of
6_issue 30
(Graphica/Graphica 2) fall into this category. In some cases this can lead to a simpler, more cost effective solution. However, there can be performance limitations associated with even the newer DVRs, and they do not address the emerging megapixel market.
Megapixel is often sold on the basis of fewer cameras to cover the same area. While the merits of this can be debated, VMSs can offer some helpful features for dealing with megapixel data streams e.g .virtual cameras and digital PTZ.
the LAN or across a wider network. Products from Omniscient, Milestone and Codestuff support this capability. Another existing resource may be computer equipment. Some suppliers will supply hardware to run the VMS server and NVR components as part of a package. This can simplify the configuration and maintenance – but does put restrictions on customer choice, and can add significantly to the up front costs. Software only suppliers have a more difficult job putting constraints on the system, and in addition to providing adequate training, often provide tools to help manage the variables in software only systems.
One of the components that can be difficult to manage and plan for successfully is the NVR. The variables that must be considered include average bit rate from the cameras, the available storage (and type e.g. RAID, NAS, SAN) and the total data throughput on the provided hardware. In a software only solution the provision of accurate end system specifications is important – but in all cases the question “how many streams will it record?” is painfully difficult to answer. Video sources come in all shapes and sizes, with different codecs, different resolutions and varying data rates that depend on what is happening. VMS suppliers can help by providing guidelines. There is certainly scope to automate and simplify the process, taking some of the magic out. Part of this could include providing appropriate system alarms, for example on storage space running low or data throughput approaching the maximum possible on the available hardware (and disallowing one too many playback sessions).
A common means of interfacing with legacy CCTV equipment is to add encoders and decoders. If a site already contains some DVRs, these may offer some level of network connectivity and avoid the need for additional encoders. However, the network interface of some DVRs can be of secondary importance and poorly designed – and the frame rate and quality of older DVRs may not meet the specifications for the newer system. There are VMSs that do specialise in interfacing with DVRs, and give the option of installing newer more capable DVRs in place of encoders and NVRs. Offerings from CBC (VSoIP) and Norbain
A further consideration to make when planning for a new system is the availability of an automation interface or API (Application Programming Interface). If there is existing software, or if the integrator is wanting to put together a package that includes interaction with other components e.g. access control, an easy to use and flexible API can simplify the effort in integrating the final system. As an example the Quorum Server and NVR include Web Services APIs to simplify integration with other systems.
Training
On all but the most basic installation some form of training is invaluable. It is an opportunity to get buy-in to the new system. Most VMSs allow for multiple levels of users e.g. administrator, managers/supervisors and the operator. These users all require very different levels of training.
The most critical training is of the administrator. The complexities involved in this role can approach the requirements of a general IT administrator. Much as we would expect IT administrators to take on appropriate training to properly use the tools available and manage the corporate network – it pays for VMS providers to make available training and documentation in the administration aspects of their system.
A VMS that clearly separates and provides interfaces that are tailored for the roles can help. For example, for the administrator the system overview and configuration is key, whereas the end user will require a very different kind of interface. As an example, in the Quorum VMS the Quorum Site application is provided to manage the complexities related to setting up the system, while the Quorum Pro viewing application is dedicated to the requirements of the end user.
Training can also help in a very real way to reduce the costs of on-going support for the newly installed systems. With adequate training the end user may be more capable at dealing with post installation issues before picking up the phone to call in support.
The more successful VMS vendors, including Milestone and Mobotix, make significant investment in the area of training, and certification and put significant requirements on their resellers to ensure that they can provide sufficient front-line support. Continued IPfocus August 2011
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48