Top Problems Searching Surveillance Video (Statistics)

By IPVM Team, Published Oct 13, 2017, 08:26am EDT

When crimes, accidents or incidents happen, the video surveillance system is a key component in finding out and proving what actually happened.

Searching that video and finding the relevant footage is key.

But what problems are most common and significant when searching surveillance video? 130+ integrators told IPVM and, in this report, we analyze the top 6 problems they most frequently cited.

Video Search Problems

Integrators reported the following problems, from most to least common:

  • Inexperienced Users
  • Poor Interfaces
  • Time Consuming Process
  • Embedded Devices Poor Performance
  • Lack Of Incident Details
  • Missing Video

Details and analysis of these problematic aspects of video search are outlined below.

Lack ******** ** **********

*** *** ******* ******** was **** ** **** training/experience **** *** ******. Many ***** **** *** associated **** ***** ******** being **** ************, ******* operators ** ****** *** to **** *********** ******** a ***** ******* ** video. 

  • "**** ** ********* **** of **********."
  • "**** ***'* **** *** to *** ***** *******."
  • "********* *****. **** **** video ***** ** *** tube, ***** **** ** step **********, ***, **** places ** ******* **** a **** ******** **** and **** ** ********* staff."
  • "**** *** ***** ***** footage ** * *** seconds ** *** ******** of ******* ****. **** is *** * ******** operation. ********* ***** ** longer **** *** ** do **."
  • "******** ***’* **** *** control *** *******. ** training ** *********."
  • "**** ** *** **** how ** ** ** :)"
  • "********* ***'* **** *** to *** ******. **** don't **** ** *** is ******** ** **** are *** ** ************ users."
  • "** ****** ****** ** site, **** ** ****** know *** ** *** the ********. **** ***'* know *** ************ ** the ****** ********."
  • "********* *****. **** **** video ***** ** *** tube, ***** **** ** step **********, ***, **** places ** ******* **** a **** ******** **** and **** ** ********* staff."
  • "**** ***'* *** ** often ****** ** ** proficient ** ***** **. They *** ** ****** requests ** ** *** we ****** *** *** service ** **** ** economical *** **** ** using ***** **** ******** to ****** *** ***** they ****."

"******" **** ** ******** times, ******** **** ***** were **** ******* *** proficient, *** **** ***** not ****** *** ** use *** ****** **** needed.

  • "**** ****** *** **** on *** ******** ** do *** *** *********. We ***** ******** ******, multiple ******, *** *****'* always **** *** ****** who ***** *** ***** straw... - **** ****** or ***'* **** *** to ****** *** ***** super ***** ***** **** obviously ****'* ******."
  • "********** *********, *** ** search, *** ** ****/**** a ****."
  • "************ ** ********* ** use"
  • "****, ***** * **** users '******' *** ** operate ****** ******** *** effectively."
  • "********** *********, *** ** search, *** ** ****/**** a ****."
  • "****** *** ** ** it ** **** **** difficulty ****** *****"
  • "***** ******* *** ** so ************ **** ****** how."

*********, "***********" *** *** system ****** *** * common ***********.

  • "*********** *** ** ******* the ***/*** ******. ** commonly ** ****** ** help **** **** *******."
  • "**** ***'* ******** *** to ** ** *** exporting."
  • ”***'* ******** *** ** to ****** ******* **** aren't **** *** ** the ****** ** ** it * ******* ** times * ****."
  • "**** ***'* ******** *** to ** **."
  • "*********** *** **'* ****."

Poor ******* **********

***-********* ********** **** "**********" controls ** ************ ******* **** listed ****** ** **** as **** ** ********. In **** ****, **** interfaces ***** ** **** as *** #* ********, as ****** ********** ***** reduce *** **** *** training, *** **** ** easier *** ********* ** find *** ***** **** are ******* ***. 

  • "*** ********* *** ** cumbersome, ********* ** ***** VMS *** ******."
  • "**** ********* *** ** difficult ** ******."
  • "*** *********. **** ******* have *** **** ** and **** *** ** properly."
  • "**** *** *********** *** user **********"
  • "***** ********** (****)."
  • "************ *********, *** *** same ** *******, **** forget ** *** ***** search *** **** ****** by **** *** ****"
  • "********* ** *** ***, searching *** ***** *** be ********** *** **** worse **** *********."
  • "**** ** ***. *********** how ** *** *** system"
  • "********* ** ***... **** clients *** **** **** 3 ** * ************** per ****. ** *** system ** *** **** to ***, **** **** struggle ** *** *** system, ***** ********** ***** to **** ******** *** system **********."
  • "************* *** **** ****** option *** * ********** event. *** *******, ****** vs. ********* ******."
  • "***'* *** *** **** to *** ** **** forget *** ******** ** how ** *** *** GUI ** *** *** results **** **** ******."
  • "*** ************* ******** ******** because ** ******** ********. Not ***** ****** ********** to ****** **** ****** times."
  • "**** ** ***, ******* exactly **** **** *** looking ***."
  • "**** ** *** *** exporting ***** *** *** most ****** ******** ********* have **** ********* *****."
  • "******** *** *** ***."
  • "********** ****** ********* ** some *** *********"

Searching ** *** **** *********

********* ******* ** **** can ** ***** ********* for *****, **** *** be ********** ** **** interfaces, **** ************ ******* the ****** *** *** server, **** *** ***** amount ** ***** ** operator *** ** ****** to **** *** ***** of ********.

  • "** ***** ***** ** go ******* *** ******** and **** **** ********* its ***********"
  • "********* *** **** **** response *** ***** ******** through *******."
  • "**** ******. (******* ******)"
  • "**** *******. **** *** that ******."
  • "**** *** **** ****"
  • "** ******, ********* ***** limits *********, **** ****** search ** **** ********* even **** ******** **** smart ******."
  • "**** **** **** ** spend ** ********* ******."
  • "*** ********* ***** **** time **** **** ****** want."
  • "*** ****** ** **** it ***** ** ******. That ** *** ********** have ****** ** ********."
  • "********* ******* ******* ********."
  • "************* ****** ****/******* ** recorded *****. *** **** consuming"

Low-End ******* ****** ********

*****-*** *******, ********* ******** NVR/DVR ******** *****, **** cited ******** ***** ** a ****** ** ******** when ********* *** *****. Comments ********* ***** ***** tend ** **** **** interfaces *** **** ******** required ** **** ********* more *********.

  • "*** *** *** *************, customers ******* ******** **** poor ****** ******** ******* by *** ****** **** use."
  • "**** ********* (***-** *********, like *********, ***** ***). are ***** **** ** use *** *********."
  • "*** ******* **** ** that ********* ********* (***/***) are *** ********* ** navigate *** ***** **** rather **** * ******* system."
  • "***-********* ****** *********. **** is **** ****** **** Chinese ******. **** ** normal ** ** ** the ********, ** *** normal ** ***** *** use ***** ******* ** an ********** *****. **** is *** ****** ******* usability ******** ** *** Chinese ******."
  • "******** ********* **** ****'* fluid ******. ***, **** have * ********, *** it *****'* ******* ***** and **** ***** ********** fluid *****. ****, *** wrong ***** *** *** could ** ******** *** search *** **** *****."
  • "** ******* *** ******* the ********* *** ** clumsy. ***** ******* *** it ** ************ **** forget ***."
  • "** ** *** * NVR ***** ****** **** it ** **** ****** navigation, **** ** *** VMS **** ****** ******"

Lack ** **** *********** *** ******

******* ******** ********* ********* not ****** **** ******* on **** ** ******** occurred, ****** *** **** of ******* ***** **** challenging *** **** *********.

  • "********* *********** ***** *** events ******** *** ********."
  • "**** ******** ****** ** not **** ** ***** time ** ***** *** event ******** ** ** is * **** ********* process *** *** *** user ** **** *** event."
  • "** **** *** *** sure **** ** ***** happened **** ** ******** theft ***** *** ********* of ***** ** ***** to ******."
  • "******* *** ** ******** that ****'* **** *** time ** **** ** happened."
  • "*********** ***** *****"
  • "** **** ***'* **** an ***** **** *** its **** ****** **** actually **** ** ******** it **** **** *********."
  • "** ***** * **** time ** **** * lot ** ***** ** they ***'* **** ***** the ******** ** **** the ******** ***."
  • "*** ******* *** ***** time ** *** ***** is *** ******* *****."

Missing ***** ********

********* ***** ****** **** not ***** *** *** time ****** *******. **** was ***** ****** ** lack ** *********** ** the ******, ******* ** recording ********. ** ***** cases, ****** ******* ** motion ********* *** ******* as ******** *** *** cause *** ******* *****.

  • "***** ********* ******* ******* notification (**** ** ****). The **** *** ******* in ***** ********* ***** to ** ********* (** something) **** ***** *** notifications **** ******* ****'* recording."
  • "***********. ********'* ****** **** the *** ** * computer/server *** ***** ** be ******* ** *** very ***** ** * weekly *****. * **** later, ** *** * call ****** ***** ** no ***** ******* ***** an ******** **** ** find ******* ************ *** camera, ** ***** * long ***** ******, *** VMS *** *** ****** properly."
  • "*** ****** (******, **** drive ** ******* *********) was *** ******* *** no *** **** ***** it."
  • "********* ***** **** **** a ****** ***'* ******* when **** ** ** search ***** ***** **'* the **** **** **** use ***** ******."
  • "*** **** ********* ***** is **** **** **** not ****** ** ***** system ** **** **** and *** ** *********** done. ** **** ***** system *** *** ** working."
  • "** *** ****** ** recording ** ****** ************ they **** ** ******* events *** ****** ** by *** ***."
  • "************ ******* ** ****** set ** ****** ********* not ******** *** ********."
  • "***** **** *** ** latency ** ****** ******."

 

Comments (3)

While these statements are all true, I would put most of the current devices for archiving light years ahead of when we had to burn CD’s and you had to properly format the CD first, then copy the files.  The CD would be 8x but the drive was 2x so it wasn’t compatible.  Oh, the days.

VCR and Mux’s.....I’ll take the HIKua interface any day.  

What really kills me is seeing the FB, LinkedIn and need reports from a HD system where I recognize the product and someone is jiggling a cell phone to export. 

Heck, many will let you export from the cell phone App and send right to FB and such, IN HD!!!

 

Agree
Disagree
Informative
Unhelpful
Funny

I'll take the HIKua interface any day.

The HIKua interface (mobile)

Agree
Disagree
Informative
Unhelpful
Funny

This is a great article, and is one of two very important report cards on the industry in general.

See if you can find a way to estimate deterrence effectiveness of surveillance.

I'd also be very interested if you could estimate how many events occurred, yet were missed due to coverage (or resolution), in part, or whole.

Bottom line is (IMHO) this is what our customers pay us to provide.

Agree
Disagree
Informative
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 7,211 reports and 960 tests and is only available to subscribers. To get a one-time preview of our work, enter your work email to access the full article.

Already a subscriber? Login here | Join now
Loading Related Reports