Video Analytics Integration Guide

By IPVM Team, Published Aug 16, 2018, 12:56pm EDT

Video analytics is hot again (at least conceptually) but integrating video analytics with VMSes can be challenging. This is especially significant when using 'smart' IP cameras or 3rd party server-based analytics that need to sent their results / output to a VMS for centralized monitoring.

In this guide, we explain the various issues and steps to take to optimize the integration of video analytics.

In this report, we examine:

  • Single vendor vs. open systems
  • The difficulty in open system analytics integrations
  • Event integration fundamentals
  • Bounding box integration
  • Analytics / VMS integration
  • Tradeoffs between built-in and manual integrations
  • Using Serial / TCP integrations
  • Digital I/O integration
  • Why Confirming VMS support details is so critical
  • 45 combinations of VMS / Camera analytics detailed
  • Problems with integrating configuration of analytics
  • Future developments/ONVIF Profile T
  • Problems with integrating search and facial recognition into VMSes
  • Other analytic integrations

Single ****** **. **** ****** ***********

******* ********* *** ** difficult ** ********* ****** 3rd *******, **** ******* focus ** ******* ***** one '*** ** ***' video ********* / *** solutions. *** **** ****** example ** **** ** Avigilon, ***** ****** *** video ********* *** ********* only ** ***** *** Control ****** ***, **** no *********** ** ***** parties. ***** ******* ******** include *** ******** ****** manufacturers (*.*.,*******'* ******) ***** ********* **** work **** ***** *** VMS.

***** *************, **** ** Dahua, *********, *** *******, also ****** ********* ***** analytics ** ***** *** recorders (********* ******, ******** boxes, *** *************) ***** third-party ******* ** ******* to *** ********* *** events ****.

Event ***********

*** ****** ** ***** analytics ** ********* **** form ** ** ***** (e.g., * ****** ******* a ********, ********* ******** in * ******, ** object *** *******, ***.). Minimally, ************ ***** ********* want * ************ ** that ***** ** ** sent **** *** ********* source (** ****** ** server) ** *** ****** monitoring ******** **** *** using (**** ******** * VMS ** *** ******).

**** ** ************ **** often ** ******* * specific ****** ** *** command ***** ******** * specific ****** ** *** VMS.

*** *******, *** *** client ***** ********** ****** from ****, ******, *** Hikvision *******, **** ** trigger *********, ***** *****, and ******* **** *****:

Bounding ***/****** **** ***********

*********** ******** ****** ** the ***** ****, *** many ***** ****** ******** boxes ** ******** ** any ***********, ** ** makes ******* (*** ***** path) **** ****** ** spot *** ***** ********* and ******* ***** **** triggered ** *****, ************ below.

*******, ******** *** *********** is **** **** **** than ***** ***********, ********* supported ** **** * few **** ******** ** each ********, ** **** as * ************'* *** cameras (** ***). ** our** ****** ********* ********, **** *****, *******, and ********* ********** ******** boxes **** ***** ***** cameras. ********'* ******* *** VMS ********** ******** *****, as ****.

******** *** *********** ** typically ******** *** ** the *** *** ********* the *** ********, ****** some ******* * *** plugin ** ** ********* in ***** ** ******* and ********* ******** **** to **** ***** *****, such ** *********'* ********* integration [**** ** ****** available] (********* ** *********).

Integration ***** ******

******* ** *** ******** VMS/analytic ************ ********, ***** is ** ******** *** up *** *** ****** are ********, **** *** process ******* **** **** analytic ** ******** **** using *** ***.

*** *******, ********* ********* simply ****** ** ****** in **** *****, **** no ********** ************* ********. For *******, ** ******* Security ******, **** ********* (VMD4 ***** *****) *** simply ******** ** *** other ***** ** *** VMS *** ********* ** event ***** *** ****** and *** ** **** to ******* ******.

*******, ** ***** *********, users ******** ****** ***** to ******* ******* ** VMS ******. *** *******, in *****, ********* *** configured ***** ***** ******* to ******* ************, *********, or ****** ***** *******.

*** **** ******** ** this ******** ** **** users **** ******** ********* analytic ***** ** ******* actions ** **** ****** the *** *** ***** exists, ** ***** **** not ******** ** *****-** integrations. *******, ***** ****** configurations *** ***** **** configurable, ** ***** *** customize ***** ***** **** specifically ******* ** ********* pre-defined *******, ****** ************* clearer *** *********.

******* ** ***** *********, users ****** ******* **** their ************(*) ** ********* exactly *** ***** ****** analytic *** *** **********.

Serial/IP ***********

** **** ***** **** event *********** ** *** built **, ***** *** be **** ** *** TCP ****** ******* ** send ***** **** ** the ***. **** ******** manual ************* ** **** the ****** (******** *** TCP ****** *******) *** the *** (*********** ** to ********* ***** ******), which *** **** *********** time *** ******, **-** minutes ** ****, ********* testing *** ***************.

*******, **** ****** ** not *** ********* ** all *******, **** **** not ******** *** ******* to **** ****** ******* on *****. **** ******** this *******, ***** **** others **** ** ********, Dahua, *** ********* ** not. *** ******* ** also *** *********, **** Exacq, *********, *** ********* supporting **** *******, ***** Avigilon **** ***. ******* includes *** ********** *** requires ***** *********** ** C#, ******* ** ******* methods **** ** ******.

*** **** ***** ************ this ******, **** ** integrate ** *** ******** running ** ** **** camera ** *****.

Digital */* ***********

*******, ** ***** ***** event *********** ** *** provided *** ** *** box *** ****** *********** is *** ********, ***** may ** **** ** trigger *** ****** ***** a ******'* ******* */*. Essentially, *** ******'* ****** is ********** ** ******* when *** ******** ********* and **** ********* ** the ******'* *****, ********** itself. *** *** *** then ** ********** ** trigger ********* ***/** ****** upon ********** ** *** camera *****.

**** *** ****** *********** described *****, **** ******** events ** ** ******* in **** ****** *** VMS, ***** *** ** time-consuming. ************, **** ****** assumes *** *** ******** the ******'* ***** ** an ***** *******, *** that */* ** *** required *** *** ***** purpose.

******* ** *** ***** factors, */* *********** ** generally **** ** * "last *****" ****** ** integrating ********* **** *** other ******* *** ***********.

Always ******* *** *******

** ********* ** *** sections *****, *** *********** of ******** ****** *** bounding ***** ****** *********** depending ** **** ********* are ****. ***** **** our********* ********, *** ***** ***** provides ** ******** ** VMS ******* *** **** different *********.

  • ***** ***/**** ********* ******** Deepest ***********:***** *** *** **** Perimeter ******** **** *** most ********** ******** ********* tested, **** ******** ***** supported ** ******** *****.
  • **** ***** *****/**** *** Hanwha ****** *********:****' ***** ********* *** Hanwha's ******* * ********** events ** *** ***** tested ****** *** ******** Control ****** (*** ** bounding *****).

vms support

*** ******* ******** **** reviewing **** ***** *** our ******* ** **** users **** ****** ************* of ***** ********/*** *********** instead ** ******** ** will ****. **** ****** be **********.

Configuration *********** *******

***** **** *****/******** *** integration, *** ****** ********* in *********** ********* ** configuration, ** ****, ****, sensitivity, *** ***** ********** are **** **** ******* to ********* ** * VMS. ******** ************* ** currently **** *** ** three ****:

  • ** *** ******: ** ******* **** built ** ********* **** often ****** *** *** camera *** **** *************. Because ************* ** *********** self *********, **** ****** is ****** **********, **** no ******** ******** ********. However, ** ******** ***** to ***** *** *** interface ** ***** ****** in *** ******, ***** may ** ******* ******** to **** *********** *******.
  • ***** ************* *******:***** ************* *** * configuration ****, **** ***** IVA ** **** ********* Defender, ***** *********** *************, with ************* **** "******" to **** ****** ** the ******. **** ** also *** ****** **** by **** ****** ***** analytics, ***** ******* ***** before ******* ** *** VMS. **** ****** *** be ******* *** **** configuration *** ******** ***** to ******** * ******** application *** ************* ******* the ***.
  • *** *** ***:***** ****** ******* ******** configuration **** ******* ***** VMS (**** **********'* ** *******), **** * *** license ******** ** ********* analytics ** ***. ******* of ****, **** ** other ***** **** **** to ********* ******/******** *****, using **** **** ******* platform ***** *********** ****** license ****, ****** ** unlikely *** ***** ***** do **, ****** ** niche *************, **** ** takeovers.

*************, ******* ** ***** factors, ***** ****** *** expect **** *********** ** analytic ************* **** ***** party ***, ** ** is ****** **** **** in ****. ************, **** centralized ********** ***** * configuration ******* ** ****, only ********* ** * handful ** ****** *********, though **** ****** ** server ***** ********* (****** these *** ************ ****).

Future ***********: ***** ******* *

***** ***** *** ************ had ****** ****** ** analytics *********** ******* ** basic ***** ***********, *** upcoming ******* * *** improve *********** ******* ********** cameras *** ***, **** better-defined ********* *** *** addition ** ********* ******* configuration ****** ** * conditional *******.

**** ***** **** ******************** ******* ********* ***** analytics *** *** ***** the ******** ******* *********. However, ** ********* ******** (*********** ******* ** *********), ******* **** **** analytic ****** ************* *** still ****** ******* ** work **** ******** ***** or **** *****.

******* * ** ** release ********* ***, ********* for ******* ***** **** year, ****** ***** ************ unlikely ***** ** ***** 2019, *** **** ****** even *****.

Search *** ****** *********** *********** ************

***** ********* **** ********** booleans (**/***) *** ******* (e.g., ******* ******, ***** of **** ****), *** more ******* ****** *********** such ** ******, **** ratios, ******** *****, ***. Because ** ****, *********** more ******** ********* ** difficult ***** ******** *** workflows **** ** *********.

*** *******, **** ******* search ********* *** ****** recognition:

  • ******/******** ***** *********:***** ********* ***** ***** to ****** ******* ** recorded ***** ***** ** specific ********, **** ** color, ****** **** (****** vs. ******* **. ****) or ** **** **** advanced *****, ******* **********. Others ***** ***** ** compress **** ***** ********* of ***** **** ******* for ****** ******.
  • ****** ***********:***** ********* ***** ***** of ***** ***** (**** as * ***** **** or * ***** *******) to ******** ********* ** video, ****** ** **** time ** ** ******** video.

***** ***** *** ***** simply ** ** ***, triggered ** ***, ****** must ****** ********* ****** metadata *** ******** *****, while ****** *********** ******** mechanisms ** ****** ***** photos, ****** ***** ** a *********, ***.******* ** this, ***** ************ *** typically ********* **** ** the ******** ***/** *** developers ***** ** ******** demand *** ******** ********/*** combinations, ***** *********** ** too ****** *** ********* which ***** *** ******* use.

*** ********* ** **** is********, ***** ***** ******** analytics **** **** ********** to **** *****, ***** plugins, *** ***********, *** other *****. *******, ******** is * ****** *******, developing ***** ********* *** nearly * ******, *** this ***** ** *********** is *** ******.

License ***** *********** (***)

******* ***** *********** ** is * ********** ******** which ******** ******* ****** plates **** ***** *** translates **** ** ****. This **** *** **** be ******* ******* * list ** ******** ****** (watch ****, ***** ****, stolen ********, ***.).

*** ******** ********* *********** than ******* **** ***** analytics, ***** ******** ***** lists/black *****, ********* *** specific ******, *** ***** tasks **** ** ********** in ****** *****. ******* of ****, **** *** integrations *** ***********, **** full *********** **** ** the *********'* *** ***/*** platform. *******, **** *** output ***** ******, **** as ***** *****, ***** may ** ********** ** third *******.

Other ******** *****

****** *** ****** *********** are *** *** **** additional ******** *****, ******. Users *** *** **** others **** ***** *** unique *********** ************, *********:

  • ******* *********:**** *** ********* ********* also ******* **** ******** analytics **** ** ******* make *** **** (***, car, *****, *****, ***.).
  • ****** ********/********:****** *** **** ***** specialized ************ *** ****** counting *** **** ******* analytics ***** ******* ******** intelligence **** ********* *** many ******** *****/****, *** long **** ***** ** specific *****, ***.

***** ********* *** ****** to ** ***********, ******* to ***** *** ************'* VMS ** ***** ********** platform, ****** ******* *********** is ****** ******** *** likely ** *** **** niche ***.

Comments (11)

Avigilon just announced the new AI Appliance which allows you to use 3rd party cameras with Avigilon analytics in large enterprise deployments.  

Also, Axis analytic events will integrate with ACC if you use Arbitrary Events we have tested this.  You would still manage the setup of the analytics in Axis but the events can be received in ACC.  The others may integrate too but we haven't had time to try. 

Is there a doc somewhere covering Arbitrary Events setup? We're interested to test it, but I couldn't find any info on how to set things up in any admin guide.

We heard back from Avigilon on Arbitrary Events. It requires XML files to be edited. There is no GUI for configuration, nor is there any public documentation of the feature. It's provided on an as-needed basis. 

Since Avigilon devices and Avigilon Control Center (ACC) use the ONVIF protocol as standard to communicate, we can capture arbitrary ONVIF events from 3rd party cameras. To create useful actions based on these events, the integrator or end customer would need XML coding knowledge to perform some configuration by coding an XML file. Since this is a highly technical configuration, we're currently using this capability on a project-by-project basis, as we support specific use cases. We can provide XML configuration and mapping guides as required. We will continue to explore providing the ability to configure this through a user interface accessible to a broader set of users.

I mean I guess a Dell server with preloaded software is an "appliance". That looks like typical server-based analytics, with Avigilon's patented marketing spin.

 

This server is running Linux and managed via a webGUI.  It just processes the video before it is stored on the main servers. 

Oh. So you're saying it's not a Dell server with pre-loaded software? Or that it's not server-based analytics?

Call the new avigilon analytics appliance a, "mid-span avigilon analytics injector" and you have it summarized. Pretty cool if you're avigilon proponent.

Full disclosure, I have avigilon bias.

Regardless, the highest probability of detection and the lowest rate of false positives remains the challenge for wide adoption and success of the overly generalized term, "analytics."

Things can be much easier when the analytics are built-in/native to the VMS and can just pull in the metadata from various cameras 😁

Couldn't agree more.  Although it is pretty brilliant of Avigilon to not integrate any native analytics from cameras, that are free, and say "oh we can use 3rd party cameras with our analytics just buy this appliance!".

 

My 2 cents: With GDPR in place VMS companies are now more motivated to integrate bounding boxes(so objects can be blurred without 3rd party software).

There is now an integration of Avigilon video analytics metadata from the cameras in to the Splunk “big-data” platform. Although Splunk is not a VMS, it is a much more versatile big data storage platform used by a wider range of companies to gain insight about their many systems and data. The integration was completed by one of Avigilon’s distributors in Australia - DNA Connect.

Splunk receives the Avigilon camera metadata, just as it would from any other data source, and Splunk uses it to make decisions, alerts/real-time notifications and reporting. Splunk can use data from several disparate data sources to provide the “glue” in the middle and then make decisions based on historical outcomes or defined responses.

This integration allows Splunk to effectively create solutions not found natively in any one piece of software, for example vehicle counting/time parked in the VMS. Go to www.dna.com.au or contact sales@dna.com.au for more information.

Yes - I work for Avigilon.  

Read this IPVM report for free.

This article is part of IPVM's 6,817 reports, 914 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

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