Converged vs. Dedicated Networks For Surveillance Tutorial

Author: Brian Rhodes, Published on Feb 11, 2015

Use the existing network or deploy a new one?

This is a critical choice in deploying video surveillance systems.

Though 'convergence' was a big theme of the past decade, deciding what to do has been much harder in practice.

In this guide, we break down the key factors in this decision, pro and cons, including:

  • IT vs Security Ownership
  • Existing Networks
  • Bandwidth
  • Network Quality
  • Technical Expertise
  • IT vs Security Ownership
  • Politics: Budget / Control / Avoiding Blame
  • Network Size
  • Expansion Difficulty
  • IP Address Conflict / IP Address Pool / Network Class
  • Security Concerns
  • Ongoing Maintenance Costs

*** *** ******** ******* ** ****** * *** ***?

**** ** * ******** ****** ** ********* ***** ************ *******.

****** '***********' *** * *** ***** ** *** **** ******, deciding **** ** ** *** **** **** ****** ** ********.

** **** *****, ** ***** **** *** *** ******* ** this ********, *** *** ****, *********:

  • ** ** ******** *********
  • ******** ********
  • *********
  • ******* *******
  • ********* *********
  • ** ** ******** *********
  • ********: ****** / ******* / ******** *****
  • ******* ****
  • ********* **********
  • ** ******* ******** / ** ******* **** / ******* *****
  • ******** ********
  • ******* *********** *****

[***************]

Selection ********

** *** *******,*********** **** * ****** ********** *** ********* ********* ************ ********, **** **** * ********* ****** ** ********.

IT ** ******** *********

*** ** *** ******* ******* *** ****** ** ** **** actual ****** ** ********, *** ********.

** ** *** ******** *** *** ******** ***********, ***** ** common, ****** *** *****, ********** ** *** *** ****** ** not ***** **** *****.

*** '***** ****' *** ******** ****** ******* ** ************ **** as ******** *** ***** ******. ********** **** ** **** *** have * *** **** ** ****** ****** *** ********* ** network ******** *********, *** ***** ****** *** ** ******* ** the **** ***** ** **** ********.

**** * ******** *******, *** *********** ** ********* ** ********. Potential *********** ******** *** ******* *** ********** ********, ** *** 'blame ****' ** ***** ****** ** ******* ******** *** ** avoided.

Existing ********

**** ******** **** *** ******** ** ****** *** ******* ** continuous ***** ************ *********. **** ** * ****** ********* ** surveillance ***********.

******* ** ****, ****** ** ************ *** ***** *********** *********** problems, *** **** ******* ***** *********.

*********

****** * *** ******* ** ** ******** ****** *** **** little ****** ** ***** ************ ** *** *******, **** ** email ** ****, ***** ***** ***** ********** ** **** * fraction ** ******* ******* ********. *******, ****** ** ******** ** cameras ****** ********** * ******** ** ****** *** ******** ******* infrastructure ***** ******* ******* ** **** *** ******** ***** ******* run ************.

** *** ***** ****, *** *** ************ ** * ********* separate ******* ** *** **** ** ******** * ********* *******. Not **** *** *** ******** ******* ******, *** ********** *** substantial ****** **** ** ** ***, **** **** ********* ******* maintenance ********.

*** ******* ********* ** * ********* ******* **** *** **** to ***** *********. **** * ****** ***** **** **** **** Ethernet ****** *** ****** ******* ** *****-********* *******, *** *** cost ********** ** ********* ** ******* ****** ** ****** *** continues ** ****. ******** * ********* ******* *** ************ ****** removes *** ****** ** ********* ********* ** ****** **** ********. The ******** *********** ***** **** ** **** ** **********, **********, and *********** * *** *****-**** *******.

Quality ** *******

** ********* ** *******, ******** ***** **** ***** ******* ** services ******** *********** ****** ** *****. ********** ******** *** ****** a ********* *** *** ***** ** *********** ******, **** ****, imagined, ** ******** *******.

*** ***** ************* / ********** ** ******** ******* ** ******* for ********* ******** ***** ** *** ******* ** **** **** hardware *** ************** ***** ** ******* **. ** * ******** lacks ******, *** ****** ** ***** ************ ** ***** ******* may ** ******** *** *********.

**** * ********* *******, **** ***** ** *******, *** ***** is ** ******** **** ***** ******** *** *********. *******, **** again ******** *** ********.

Technical *********

** **********, ******** *** ***** **** ****** ** **** ******* with ** ******* *****. *** **** **** ********** *** ********* plays ** ******** * ************ ******* ** ********* *********.

***** * ****** ******* ** ****** *** **** ******* ***** sense ** **** *** **** ** ******** **** ******** ** managed ******** *** *** ******* ************* ****-***. *********** '******* ** Service *** ***** *** ** * ********* *** ********* ****, but **** **** ********** ** ******* ***********. ******* **** ***** of ************* ** ****** ******** *****, *** ****** ****** ******* the ****** ********** ** ******* **************.

** *** *** *******, * ********** ******* ** ********* ******* to ****** *** ******** ******* ** ******* **** *** *** system ****. *** **** ** *** ***** ** ************* ****, but *** ****** ******** ****** ** ******* *** ******* ****** a ****** ******* ******. '**** *** ****' ******** **** ******* configurations *** *********** ** ********* ***** ********, **** **** ****** IT ***** ** ****** *********** *** ****** **** *** ******** them **** ****** **********.

Expansion ********** & ****** ****

** *******, *** ***** *** **** ** *** ******* ** a *** *************. *** ******** ******** ******** ********* ** ******** sites, *** ************** ********** ***** **** ******** *** ** * huge ******* *** ******** *********** ******* ** ******** ***** ** cable ***********.

**** ************* **** ******* ******** ** ******** ********** ******** ********* and ******** ********, *** ********* ***** ** ******** ***** ******* are ** **********. ********, ***** ***** *** ***** ******* **** some *********** ** ****** ********* ** ****. *** *********** **** of ****** ***** *** ** ********** ***********.

*******, *** ********* ********, **** ***** ******* *** ****** ******* buildings, ***** *** ** ********* ********* ** *********. ** **** cases, ********* ******** **** * ******** *********.

Security ********

*** *** *** ***** ** ********* ***** ********* ******* ******* also ** * ****** *******.

** ********** ********** ************ ******* ** *** *** ******* ***** it ****** ** **** ****** **. ********, ******* ****** ** video ***** ********** ******** ****** ** *** ******* *** ******* that ******* ****** ** ******. ** *******, **** ** * priority ** **** ********* **** ** ****** ** *** ****, even **, *** *** ***** ******* ** ****** ***** ***********.

*** ********* ******** ** **** ******** ******* *** ** ********* or ********* *** ******* ** ****, ****** *** ** *** 'low-risk ******' ******** ***** ** ************** ** ******** *****.

Ongoing *********** *****

*** ******* ** *********** ****** ****** *** **** ** ****, and ****** * *** ******.

*******, *** ******* ******* ** * ********* ******* ** * budgeted ** ********** **** ******* *********** *** ****** ** *** users. ******* *** ******* *********** ** * ******** *** ** departments, *** ****** ***** *** * ********* ******* ********* ********** the ******* ** ******* ***********.

*******, *** ********** *********** ** ******* ******* ** ********** ******** or ******** *******. ***** ***** *********** *** ******** ****** *** be ********* ** ********* * ********** *******, ******* ** *********** or ******* ********** ** ****** *** ** * **** ******* area.

*** ******* **** ** * ********* ******* ** **** ****** maintenance *** ****** *** ** ******* ** **** ** ***** addressed. ********* ** *********** ** **** **** *************** ******** ** fixing ********* ******* ** '***** *******' ** * ****, ** well ** * ********** ** **** *** ******** ****** *** service ** '***** ******' ** **** ***** **** ******** ******** once ** ***** *** ****.

Comments (8)

I think you need to add in the maturity of the customer, their infrastructure and the efficiences they may/may not have with respect to managing thereof.

A few years ago this would be more relevant than it could (or should) be today. So-called "convergence" isn't an event but an evolution. In many environments IT will continue to absorb the responsibility for providing the physical security as infrastructure and the security personnel are another end-user.

Casinos might be a special case in that cameras are a mission critical asset and the risk of getting ripped off is both external and internal.

But in most (modern) environments core switches should be gigabit with high capacity interconnects. VLAN tagging is a convenient way to logically isolate IP video traffic.

POE port density can be a problem towards the edge--in which case it might make sense for new/dedicated equipment. But even at that the proliferation of POE for (say) IP phones is becoming common and so is POE.

My point being, a professionally managed, modern network should be able to support IP video. If it's not, maybe IP video is a good reason to modernize. There exists value in using the same infrastructure for IP video and other networking needs. The dedication of a distinct network for IP video is leaving some of that value on the floor.

You are mixing could with should, with what happens with what you think should happen.

The reality is that this is still a significant issue and the political / territorial / fingerpointing aspect has not gone away for the large portion of users where IT and security remains separate.

I don't doubt that political / territorial is still a big deal and relevant. But, hey, so is analog. What I'm saying is the excuses are falling away. Where the security guy used to be able to say "bandwidth" or "security" he can't necessarily do so any more. I don't doubt that they're still the argument, but they won't be forever in many environments. When the argument becomes clearly political, it's increasingly difficult to justify if the infrastructure--itself designed to service the business as a whole as efficiently as possible--is able to do the job for both and makes sense to be managed singularly.

An example from retail, Yum! Brand's 'future store network' would set minimum bandwidth connections to stores, standardize network hardware in-store designed to (logically) segment wifi to customers, POS, digital signage, and IP video. And, no, the LP guy can't really argue duplicate hardware and infrastructure just because he doesn't get along with Joe over in IT..

As long as IP video is managed like analog but with RJ45 instead of BNC connectors, the customer is leaving a lot of 'internet protocol' opportunity on the floor.

"Where the security guy used to be able to say "bandwidth" or "security" he can't necessarily do so any more."

Actually I am saying the IT guys often say this. Not every IT department wants to have video surveillance dumped on then, the increased risk / troubleshooting.

As for retail:

"An example from retail, Yum! Brand's 'future store network' would set minimum bandwidth connections to stores, standardize network hardware in-store "

Retailers have been using converged networks for 10+ years because they have to. When you have stores / branches / sites scattered around the world, it is not that feasible to have multiple independent WAN connections for each service. And for retailers, they have to see the video remotely so the shared WAN becomes a necessity.

Retailers and anyone who runs credit card transactions have PCI-DSS compliance concerns which generally means that if they are a big box store they already have network infrastructure to support VLANs. Otherwise every device, including the surveillance servers gets added to their PCI audit scope of it's on the same VLAN. Even in some small Restaurant chains have some level of VLANs setup. I feel that restaurants, retail, hospitality, and healthcare facilities (due to HIPAA in the US) are the easiest to push for convergence. I have only done project on one campus but higher education seems to be fairly comfortable with convergence as well. They all already have so much junk riding on their network to begin with - AV control systems, teleconferencing, VOIP, etc. In my opinion big box retailers DEFINE converged IT.

It's places like factories and automotive corporations that I have seen the most push back. Anything that has even the most remote chance of impacting production for even a second starts a fire under IT and the production representatives will back them. Security is just a minor department.

i am willing to bet the vast majority of the time the biggest pushback from IT is sheer laziness or fear of the unknown. Just like every field there are people who are good at their job and some that you have to question who they are related to.

"I feel that restaurants, retail, hospitality, and healthcare facilities (due to HIPAA in the US) are the easiest to push for convergence"

Are you sure about that? We did a hospital that was very glad we to hear we were building a physically seperate network for the cameras. The only part of the system connecting to their network being the NVR, which made it easier for them to control.

As for retailers, it depends on the size of the retailer. Do not assume because the retailer or resturant chain is a big one, that they invest a lot in "compliance". The problem is the smaller, franchise owner who has to squeeze what they can from very small margins, like a sharecropper. So many times I have seen them install free, public wireless systems to attract patrons which are also connected to the same network as their old used, Windows based POS systems that didn't even have antivirus protection on them. When you talk to them about segregating the networks so patrons don't see the POS systems, they're like "Sure, as long as it doesn't cost me a dime. Otherwise... uh, yeah, I'll get to it maybe next month."

"I am willing to bet the vast majority of the time the biggest pushback from IT is sheer laziness or fear of the unknown."

Unfortunately, yes, very true. Not all the time, but more often than non-IT people probably realize. That's why is you don't have staff that are very IT proficient, you'll probably never recognize it.

We don't have a single client using more than 3-5 cameras on their network. I could never put our company's name behind infrastructure that we don't know front to back. If it is impossible to put in our own lines then fine but "convergence" is nice in theory, in practice its a hot mess. Think about it, one day some IT admin screws with the network and blocks port traffic within the network.. Cameras go down and the customer is upset... You consult with IT and they say "we didn't do anything" and you're left with trying to figure out their mess. To the customer it doesn't matter that IT did it, the blame game gets you no where. So I say NEVER piggy back on their network unless absolutely nessesary.
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

ISC East 2018 Mini-Show Final Report on Nov 16, 2018
This is our second (updated) and final show report from ISC East. ISC East, by its own admission, is not a national or international show, billed...
Magos Radar Company Profile on Nov 12, 2018
Magos America General Manager Yaron Zussman admits when he first came across Magos, he asked himself: "What's innovative about radar?" Be that as...
Video Surveillance Hard Drive Size Statistics 2018 on Nov 08, 2018
What is the most common hard drive size for video surveillance? 150+ integrators answered: What size hard drive do you most commonly use? What...
Ubiquiti Protect Video Surveillance Profile on Nov 07, 2018
Ubiquiti has now been in the video surveillance market for 7 years (see our first coverage back in 2011). In that time, the company's revenue has...
Dahua Dual Imager Dome Camera Tested (HDBW4231FN-E2-M) on Nov 07, 2018
Dahua has introduced a dual-imager dome model, the HDBW4231FN-E2-M, with two independently positionable sensors including integrated IR, not found...
Favorite Video Surveillance Hard Drive Manufacturer 2018 on Nov 06, 2018
Who is the favorite hard drive for video surveillance use? 150+ integrators answered: What is your preferred brand/model of hard drive for...
Winter 2019 IP Networking Course on Nov 05, 2018
This is the only networking course designed specifically for video surveillance professionals.  Lots of network training exists but none of it...
Worst Products on Nov 03, 2018
Security integrators periodically report on their favorite and worst products to IPVM. These are known integrators who IPVM pays to answer surveys....
Video Surveillance Hard Drive Failure Statistics 2018 on Nov 02, 2018
Hard drive failures can be significant service problems but how common of an issue are they in video surveillance? How long do drives last when...
Building Occupancy Codes and Access Control Tutorial on Nov 01, 2018
A building or room's classification can greatly impact which building codes must be followed. In terms of access control, these 'occupancy codes'...

Most Recent Industry Reports

Milestone Disrupts Milestone With Arcules on Nov 19, 2018
Milestone is now competing against... Milestone's own spinout Arcules New IPVM testing shows that Arcules has incorporated a substantial amount of...
Pressure Mounts Against Dahua and Hikvision Xinjiang Business on Nov 19, 2018
Pressure is mounting against Hikvision, Dahua, and other companies operating in Xinjiang as an international outcry brews against the Chinese...
Arcules Cloud VMS Tested on Nov 19, 2018
Arcules is a big bet, or as they describe themselves a 'bold company', spun out and backed by Milestone and Canon.  But how good is Arcules cloud...
'Sticker' Surveillance Camera Developed (CSEM Witness) on Nov 16, 2018
The Swiss Center for Electronics and Microtechnology (CSEM) has announced what it calls the: world’s first fully autonomous camera that can be...
ISC East 2018 Mini-Show Final Report on Nov 16, 2018
This is our second (updated) and final show report from ISC East. ISC East, by its own admission, is not a national or international show, billed...
Facial Detection Tested on Nov 16, 2018
Facial detection and recognition are increasingly offered by video surveillance manufacturers. Facial detection detects faces in an image/video...
Throughtek P2P/Cloud Solution Profile on Nov 15, 2018
Many IoT manufacturers either do not have the capabilities or the interest to develop their own cloud management software for their devices....
ASIS Offering Custom Research For Manufacturers on Nov 15, 2018
Manufacturers often want to know what industry people think about trends and, in particular, the segments and product they offer.  ASIS and its...
Hikvision Silent on "Bad Architectural Practices" Cybersecurity Report on Nov 14, 2018
A 'significant vulnerability was found in Hikvision cameras' by VDOO, a startup cybersecurity specialist. Hikvision has fixed the specific...
French Government Threatens School with $1.7M Fine For “Excessive Video Surveillance” on Nov 14, 2018
The French government has notified a high-profile Paris coding academy that it risks a fine of up to 1.5 million euros (about $1.7m) if it...

The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.

About | FAQ | Contact