Setting Up an IP Video Surveillance Camera

As we saw in our two-part series on IP cameras, there are many benefits to moving to IP when the timing is right. Using an IP camera for video surveillance can provide many enhancements that simply aren’t possible with analog cameras. Whether you’re a technician or an organization working with a certified systems integrator, it’s important to understand the options presented by IP. Unlike the days of analog — where NTSC vs. PAL video format was the primary concern — IP cameras introduce a whole new vocabulary, with terms like bit rate, frames per second (fps), compression and image complexity. To maximize the horsepower of your IP camera, you need to determine the optimal setting for each of these variables for your specific application.

The settings you choose determine the amount of information captured by the IP camera. This in turn determines the amount of bandwidth that you’ll need to transfer the information to your backend system and how much storage space you will require. The challenge with IP cameras is to find the best balance between information captured and bandwidth consumed. You want to capture only as much information as is needed to provide excellent surveillance. You don’t want to incur bandwidth costs for detail that isn’t really going to help you resolve a security issue. On the other hand, you don’t want to select the lowest settings everywhere to save bandwidth and end up with less detail than you need.

To get you started, here’s a brief primer on key variables you may encounter.

• Compression: You may have three choices for video compression: H.264, M-PEG4 and M-JPEG. H.264 is more efficient in compressing video, which reduces the storage required; I recommend selecting this option whenever you have a choice. On the opposite end of the spectrum, M-JPEG does not compress the image at all and requires the most storage.

• Complexity: What’s going on in the camera’s field-of-view (FOV) will affect bandwidth. A complex picture that contains lots of elements and motion, such as a busy cafeteria, will demand the highest amounts of bandwidth. A largely static scene with fewer elements, such as an empty hallway, will demand much less. Of course, you need to capture whatever scenes are appropriate to your security needs, but bear in mind that complexity impacts bandwidth.

• Bit rate: There are two types of bit rate: variable bit rate (VBR) and constant bit rate (CBR). With VBR, the number of bits captured will change according to the complexity of the scene. This means that you will always get a predefined level of image quality. But bandwidth can vary widely depending on scene complexity. CRB will set the camera to always deliver a constant bit rate and change quality based on image complexity. By choosing a bit rate that still allows for a good picture during peak times, you will have the image quality you prefer and a very predictable storage requirement. Cameras that have VRB with a cap rate are the best option; they accommodate storage savings when the scene is less complex, but cap the rate when the scene gets very complex (like in complete darkness). By capping your rate, you are guaranteed not to exceed storage capacities.

• Video resolution: If a company invests in a 3MP or 5MP camera and sets it to 1080p, they are just wasting their money. Go ahead and set the camera to its full potential, resolution-wise. And make sure you get the most out every single pixel by streaming to a suitable recorder.

• Frame rate: Use the required frame rate for the application. Many cameras come defaulted at full frame rate, like 30 fps. Other than for casinos, this frame rate is typically not required. For places where you are trying to identify people, such as at a bank teller line, 2-4 fps should be sufficient since the subject is in the scene for long periods of time. In places like retail check-out lanes, where you need to see things moving at faster speeds, 8-10 fps is more common.

• Daily storage: As you can see, camera settings and scene complexity can vary the bandwidth needed. This has a direct impact on storage and the amount of storage required to meet individual retention policies.

The total impact IP cameras have on your network will depend on the settings you choose multiplied by the number of cameras. If you allocate resources wisely, your network should be able to handle the bandwidth load from dozens of cameras easily. However, if you select the highest settings for each variable on each camera, you could bog down your network unnecessarily.

Your best choice, now that you understand what’s at stake, is to rely on the expertise of a certified systems integrator. Integrators are trained professionals who understand the tradeoffs between quality and bandwidth and can tailor your system to best meet your unique security needs. Now that you have a handle on some of the IP terminology, you’ll be better equipped to evaluate the options a systems integrator provides.

You can also take advantage of our System Design Tool or other similar tools available online to estimate the impact IP cameras will have on your system. By varying settings in the tool, you can clearly see how different choices will affect your network and storage. While system design tools can aid in some estimates of storage and bandwidth required, it is best to test different settings to see the trade off in image quality versus storage costs. And remember, an IP camera is still a camera. The best way to observe the benefits first-hand is to test several in a real life, side-by-side shoot out to see which camera is the best for the application. Never purchase a camera based on just its data sheet and price.

IP cameras are well worth the investment, but as with anything else, planning for success means you’ll get exactly what you need without paying more than you have to!