ONVIF Favorability Results 2019

By IPVM Team, Published Mar 15, 2019, 11:01am EDT

In the past decade, ONVIF has grown from a reaction to the outside Cisco-lead PSIA challenge, to being the de facto video surveillance standard officially supported by 11,000 products and thousands of more illicitly.

Integrators have responded positively, in IPVM's latest study of 200+ integrators, with a clear majority positive, as the chart below shows:

fav onvif 2019

However, that does not mean that integrators are completely happy with ONVIF, with numerous complaints about limited functionality and failure to ensure compliance leading the way.

In this note, we examine the key themes for integrators about ONVIF.

Key ******

*** *** ****** *******:

  • "********" - **** **** ever, **** *********** *** ONVIF ** * ********.
  • ******** *********** ***** *****
  • ********** ***** *** **** to *** ****** ******* over *****
  • ******** **** *** *********** of *****, **** ** working **** *.***, ********* and **** (************* * ******* ** improve*****).
  • **** ** *********** / compliance ***** *****

Standards ****

**** *********** ********** ******* ONVIF ** ***** * standard, **** ****** *** question **** ** ********* to ****:

  • "** ******* ** ** an ******** ********."
  • "******** ******** - **** to *** **** ****** over ******* ******* ******* VMS."
  • "***** ***, ***** *** more ** * "**********" than * "********." *****, it ******* *****-********** ****** means *** ******* **** play **** **** *** recorders."
  • "* ***** *** ********* to **** * ******** compatibility ******** ** *** industry."
  • "*** * ******** ** need ** *******"
  • "******** *** ****** **** to ****."
  • "**'* *** ******* **** protocol *** ** ******."
  • "*************** ***** **** ****** for *** **********."
  • "* ***** *************** ** any **** ** * good *****."
  • "**** ** *** **** there ** * "********" to ***** *** ********!"
  • "******* *** ********* ******** is ******* **'* ***** in *** ******."
  • "**** **** ** *** standards **** *** ***** of ******* *** ***'* play ********."
  • "* **** ***** ****** because ** *** ******** to ******* **********."
  • "* ***** ***** *** done * ***** *** of ************* ******** *******."
  • "****'* *** ** ****? An **** ******** ** keep *** ****** **** is **** ****"
  • "********* *** ****** **** for *** ********. ******** camera-wise ** *** ** started ****** **** * couple ***** *** **** met ** ** *********."

Positive ******

*** ***** ******** ******** were ***** *****'* ******* good ****** ** *** industry:

  • "*** ******* * ***** forced *** ******** ** move *******. **** ** has *** *********, *** overall, ****** ********."
  • "************* ******* ** ** integrators * *** ** options ** ***** *** right ******** *** *** customers."
  • "***** - ** * great **** *** **'* come ** ***** ** a *** ********* **** adding ******* ** ******** systems."
  • "****** *** **** ******* mixing *** ******** ****** due ** *****."
  • "** ****** ******** **** before *****? ** ****'* pretty. *** *** *****."

Not ******

*******, **** ** ***********, including **** *** ***** positive *** *****, *** cite ******** ***** ***** not ***** *** ****** and ****** ******** ***** beyond ***** ***** ********* and *************:

  • "** ** **** ** for ***** *********."
  • "**** * ***** *********, does *** **** **** advantage ** *** *** features ** *** ******."
  • "******* ** **** *** integration ** ****** *** and ****, ********** **** it ***** ** *********."
  • "*** ******* ***** ** sometimes *** ********* ***’* want ** **** *********."
  • "** *** **** **** you're ****** ** **, and *** ******* ** accept **** ***********, ** works ****.
  • "** *** "*****" **** caution. **** ******* ********** to, "*** *** *** and ******" *** *** lose **** ******* **** as *** *** ********* record ** ******."
  • "***** ***** ******* *** supported, **** *** ******* (absolute, **********, ********) ******* is ****** ** **** and * ******* ** worst."
  • "** ***** **** ****** functions *** **** ***'* actually ********. ***** ******."
  • "***** ** ****** ******* I *** *** *** ONVIF * ***'* *** a ****** ** ** what * **** **** though *** ****** *** VMS **** ******* *** same *******. ***** ***** a *** ** **** I *****."
  • "***** ***** *** *** issues **** ****** ** use *** **** ********* of *** ******. ** constantly **** ********, *********** etc. **** ** *** onvif ** * ******** of *******."
  • "****** **** ** *** proprietary ******** ** **** systems."
  • "******* ** **** *********, but *****'* ***** *** the ********** ***** *********."
  • "*** ********* *** *** work, *** * ** not **** *** ********* that **** ***** *********."
  • "***** ** * *** of **** *** *********** to ****** ******* **** features."
  • "*** ** ********** ** terms ** **** ******** are ******** ********* ******* ONVIF ***********."
  • "***** ** ******, *****'* always ****. ** *.*** support."
  • "** *****´* ****** *.*** nor ***** ****** ** fully ********** **** **** protocol. ** ******* **, as *********** ** ***** that * ****** **** that ** ******* ***** like *****, *** *******, have ** **** *** other ****** ***** *** compatibility **** ***** ***'*."

Profile * **** ** ******* ********** ********

** ****,***** ******** ******* * which **** ** *********** ** *** *********** that *********** ************** ********** about. *******, ** ** March ****, *** **** of **** ***********, ***** Profile * *** **** 1 *** ********** **********, making *** ***** *******. It ** ******** **** this **** *******, ******* quite *************, ** *** next ****.

Compliance ******

*** ***** *** ******* that *********** ****** *** was *** **** ** actual **********. ***** ***** has ** ******** *********** process, *** ******* *** claim ** ** ***** 'certified' ** '***** **** ONVIF' *** *** ********** that ***** **** ********* is **** *** (** have ******* **** **** the *****). **** *** sample ********** **********:

  • "** ****** ******** ** a ********."
  • "* **** ***** *** a *** *** ***** was *** ** *** more ******** ** ************ to ******."
  • "*** **** **** *** doing ** **** **** the ********** ** ******* their *********...***** ****** *****."
  • "******* *** ***** ***** is ******** ******* ***** accurate, *** *** ******** rendered ** **** *********. If ***** *** * crack-down ** ***-********* ********, it ***** **** ** more *********."
  • "***** ******** ********* *** set, * ***'* *** much ********* ** *****. It's **** **** *** effort *** **** ** create * ********, *** it ***** ** **** teeth. ** ********* *** camera ***** ** ***** standard, ****'* *** *****?"
  • "** **** *********, *** needs ** ** ******** better ** ************* ******* self ******** *************."
  • "***** ** ** ***** in *** "********". **** too ***** *** ******** in *** ******. *** gotten ****** *** ***** needs ** ********."
  • "* ***’* **** *** inconsistency ** *** ************ using ***** ***** ** why *** *** *** cameras ******** ****."
  • "*** **** ********* ***** onvif ********* *** ***** vms ***** **** ********."
  • "** * ********, ******** but ***** ** **** better ** ******** ******** and *********. ***** ******** is '***** **********'"
  • "***** ** * ******** is * **** **** but ***** ****** ** more ********* *********** *** conformity ** *****."
  • "***** **** ***** ******* is ***** - *** what **** **** ****."
  • "*** **** **** ****** not “******” **** **** manufacturers *** *** ***** seal ** ************* ** their ******** ******* ****** being ********** **** *** standardized ***** ********"
  • "* **** *** ********** was ******** ** ****** conformance."

**** *********** **** ***** over *** *****, *** impression ** *** ** that **** ** *** care *** **** ****** active ***********. ** ** strange. ***** ** *** a ***** ************, **** 495 ******* *** ****** membership **** ** ~$*.* million (***** ** ***** pricing ************* *********). *********, ***** **** not *** *********** ** a ******** ** ***** spending.

*******

*** ******* ** ***** certainly ******** *** *****, depending ** *** **** Profile * ***** *** is *******, ** **** could ***** *** ******* pain ***** *** ***** usage.

Comments (17)

***** ** * *****, but **** ********* ******* for *** ********.  ************* you ***'* **** *** into * **** *** declare ******** *** ********, it ***** ***** *** years ** ***** *** groundwork ********* ** ** accepted.  ***** *****'* **** the ***** **** **** or **** ***, ** it's * **** ***-**-**** situation.  ****, **** ******* with **** ** *** manufacturers ** ***-**** ******** that ** *** ***** day, **** **** ** do **** ****** ** get ** *** ***** list *** *** **** in ***** ** ****** customers ******** *** ** their **** ******** **** them *** *** ****** and ******** *******.

**** **** ** ***** ONVIF ** **'* *** to ****.  *** ****** ever ****** ** *** who ******* ***** *********?  Designee's (*******) **** ************* with ****, ****, *****, etc.  *** **** **********, all ******* *** *********,  just *** *** * client ******** ** / interacts **** ** * MAC ******* (** ******* and ********).

****, ** ***** *** warm *** ***** ******* that **** ******** ******* something **** *** **** with * ******* "*" profile, *** "*" ********** is ******* *****.  *** would *** ***** ******* to *** **** *** compliant **** *** ****** feature *****'* **** ** be ***, **** ***** exceptions.

 

*** ****** **** ****** to *** *** ******* these *********? ********'* (*******) with ************* **** ****, Sony, *****, ***

**** *********** ****:

*** ******** ***** * Wise ******** *** ****?

*** **** ** ****** Out ** *****?

***** ******** ********** *** Cost ******* (****, ** Works ** ****)

****** **#*.  ***** * could **** ***** ****** some **** ** ******* at *** ******** ******* of ******* ****** *** ONVIF ****.  ***** *** to ****, *** ******** my *** ******.

**** ** ******* **** were *** ******** ****** in *** *** ***.

**** ** ******* **** were *** ******** ****** in *** *** ***.

*** ***** **** ***** be *********** ** ****, via *********** **** *****, would ** **** ********** cameras ******** ******* (** the *****) *** *****.

** ** *% ** 50%? ********* ** **** info *** ******* **** reported *********...

********* ** *** ********** (see: ***** ***** ********** ****), *** ********** ** around **%.

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

*******.

** ***** **** **** is *** ***** **** of *****, *** * assume ** *** ****** been ** *** ****.

***** ** ******** *** insecure ****** ** ***** ancient *****.

** *** ******* **** adopt *****. ***** *** already **** ********** ******** because **** ****'* **** trap ** ***** *** their *** ****** *** efficient ********.

**** ** **** **** of "********** ********"?

***** ***'* * ************ yet *** ****** ** in **** **** *** of **** ************ ************ summary. ** **** ***** does *******, ** ****, or ** ****** *****, or **** ***** * survey?

** **** ************ ** that *** ***** ** mildly **********. * ********** your ******** ** *****.

****’* ** *********** ****. We *** ******* **** technologies ** *** **** version. ******.

*******: ***** *** ******** *. *** *** ** thinking ** *****, ***** has ********** *(****** ***** ***** ** going ** ** ******* anyway).

****, *** *'* ******* my *** **** ***...

*. **'* * *** excruciating ** *** **** to * **** ***** a ******** *******. *. there's ** **** ******.

***** ***'* * ************, but **** **** ********* (access ** ***** *****, test *****, *********** *******, etc.) **** *** * spec-able **** **** **** products ** *** ******** strive ***.

****** **** **** ** a **** ***** **** a ********* ************, **** as ****, *** **** don't **** *** ******* database ** **** ** use ***** *********. **** don't **** * **** tool **** ** **** for *********** *******. ***** has *** ** *****.

******* ** *** **** is ******* *** ** be...

****? *** **** ******* for *******? ** ** have **?

Read this IPVM report for free.

This article is part of IPVM's 6,803 reports, 913 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