ONVIF Usage Statistics 2018

By: Sean Patton, Published on Mar 05, 2018

ONVIF has long 'won' the standards battle for video surveillance.

But has the now 10-year-old ONVIF 'won' vs direct integrations? Undoubtedly, ONVIF has very wide support, with 9,496 (and counting) conformant products. However, most VMS and recorders still offer direct integration to many devices that typically offer deeper and more reliable support than ONVIF. Indeed, Hikvision recently disabled ONVIF by default in favor of its own direct integration, a blow to ease of using ONVIF with their cameras.

Has ONVIF become good enough and broad enough to displace direct integration? 150+ integrators told IPVM what percentage of camera integrations they used ONVIF for in the past year and why.

Overall Usage

3 out of every 10 cameras were integrated using ONVIF in the past year, according to statistics IPVM gathered from integrators:

This would also mean the percentage of all cameras integrated with ONVIF is significantly less than those using direct integration, as the number of cameras using ONVIF would certainly be lower in past years as well, as the number of ONVIF conformant devices is growing.

Breakdown by Integrator

***** ******* '***' *** ********* battle*** ***** ************.

*** *** *** *** 10-year-old ***** '***' ** direct ************? ***********, ***** has **** **** *******,**** *,*** (*** ********) conformant ********. *******, **** *** and ********* ***** ***** direct *********** ** **** devices **** ********* ***** deeper *** **** ******** support **** *****. ******,********* ******** ******** ***** by ********* ***** ** *** own ****** ***********, * blow ** **** ** using ***** **** ***** cameras.

*** ***** ****** **** enough *** ***** ****** to ******** ****** ***********? 150+ *********** **** **** what ********** ** ****** integrations **** **** ***** for ** *** **** year *** ***.

Overall *****

* *** ** ***** 10 ******* **** ********** using ***** ** *** past ****, ********* ** statistics **** ******** **** integrators:

**** ***** **** **** the ********** ** *** cameras ********** **** ***** is ************* **** **** those ***** ****** ***********, as *** ****** ** cameras ***** ***** ***** certainly ** ***** ** past ***** ** ****, as *** ****** ** ONVIF ********** ******* ** growing.

Breakdown ** **********

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

******** **** *** ********* by ********** **********, *********** are ******* ********* ** using ***** **** * majority ***** ** ****** never ***** ** *** a *********** ******** ***** it *** *** ****:

Limited *** *****

* ******* ******** ** integrators ***** ******* **%-**% use ** ***** *** camera ************. ** **** cases ***** **** ******** situations *** *** **********, because ** ******** ********* or ******** ************ ******* of ***** *******:

  • "*** ********** ** ******* i **** **** ***** for *** *********** *** 12%, ******* *** ****** had ******* **** ***** that **** ******* *****"
  • "**% ***** **** **** installations ******* *** *********** either *** *** **** the ******* ******* ** stock ** **** *** not **** *** ******* camera *** *** *** at ***, *** ********* we *** ** **** on *** ***** ******* to *** *** *** up *** ******* ***********. "
  • "**% **** ** ********** where ***** *** ******** cameras, **** **** *** work ******** **** ***/*** brand"
  • "****** **%. ******** ********* 3rd ***** ******* *** individually ********** **** ****** VMS."
  • **%. *** *** ******** we ******* **** *** have * **** ********* of ********** ******* *** relies ******* ** *** use ** *****.
  • "**% ******* ******* *** directly ********** **** *** VMS"
  • "**% ** *** ****** needed ** *** ***** due ** ********* *** take **** ** ***** that *** ******** ************* cameras ** *** ******"
  • "**% - ********* *** value / ***** ******** only ********* ******** ********."
  • "**% - ** **** pretty ***** ** *** main ************* ***** ** Axis *** *********. **** we *** **** ***** integration ** **** ** needed ** *** ********'* existing *******"

Direct ******* *********

**** *** ************* **** developed ****** ****** ************ to ****** ******** ** the ***** ****** ***** protocols *******. ***** ****** drivers **** ********* ** be *********, *** **** proven ** *********** ** be **** ******** *** provide **** ********** ******* integration **** *** ***** VMS *********:

  • "**** ** *** **** I ** ********** *** IP ******* **** **** direct *** **** *** VMS. * ****** ***** the ** ****** *********** page"
  • "** ******** ****** *** and ******* **** *** same ************/********"
  • "...** ******* ****** **** the *** ** *** same *****. **** ***** cam **** ***** *** or **** *** *** companion ***."
  • "...**** *** **** *********** with ***** **** *******, Milestone."
  • "...******** ** ******* ******** was ** *** ********* list ** *** ** the **** ************ *** both ****** *** ***. Reason ** ******* *** will *** **** *** concern ** *** ** the *************."
  • "**** ****** **** **** brand ****** ******* ** cameras **** ********* ******** recognises."
  • "** ****** *** ******* that **** ****** *********** to *** ***"
  • "** *** **** ***** products. ** ***** ** no **** *** ** for *****"
  • "*** *** ******* * have **** **** ****** been **** **** ********* and **** * ****** or **** **** **** manufacturers ***"
  • "** **** ******* *** manage ******* **** **** a ******* ********* *********** with *** *** ********"
  • "** *** * *** Axis ***** *** ***** uses *** **** ***** for *** *******. "
  • "** *** *** **** cameras **** *******, ** it **** *** **** driver **** ** *******. "
  • "* **** *** ***** matched ******* **** ****."
  • "*** ******* ** **** integrate ******** **** *** VMS"
  • "**** **** *% *****. Most ** *** ******* have ** *********** ****** with *** *** ** use"

Some ******** ** *****

**** *********** ********* **** they ** *** ***** that *** "********" ******* actually ******:

  • "**** *** ********* ***** we **** *** ** problems **** ***** **** ONVIF ********* *** ** have *** ******** **** camera '******' "
  • "**% ** ******* *** integrated ***** ****** ********* due ** **** ************* requirements. *** ******* **** Onvif **, **** ** the ************* ** *** present."
  • "**** ****** ***** ** finger *** **** ** will ****. ***** ****** much ** ********** **** onvif. "
  • "...*** *****, ***** ***** still ** **** *********** of ************* ***** ********* during *********** ***** ******* are ********."
  • "********* ****'* *** ******** and ** **** ** use *****. ** ***** cases **'* ******** ** success, *** ***** **** be ****** ****** ******** can ** ****."
  • "* ****** ****** ******* against ***** ***** ******* wherever ********"
  • "*****, ** ***** ** my *******, ** *** a ********. ** ** just *** ******* ***** we ****"
  • "***** *****'* ****** **** as ********** ******."
  • "*% * ***’* ***** ONVIF."
  • "** **** ******* ** ONVIF ****** ****** **** in *** ***********."

***** ** ********* ** Some

***** **** **** ********* that ********* *** ******** aspects ** *****:

  • "***% *****, * ** not **** ** ** “vendor ******”"
  • "***%, ** **** ******* 3 ***** ** ******* and **** *** *** ONVIF *********. ** **** install * ****** ** we **** *** ********** each ****** ****."
  • "***%, ***** ** ********* when ***** ******** *** and ****** ******* **** necessary."
  • "***% *** ************ ********"
  • "**% - **** ******* would **** ****** ** our *** ** ** ONVIF ******"
  • "** *** ** % ONVIF **** *** *********** as ** ** **** for *** ***** *******"

******** **** ***** *** their *** *******

*** ***** ********** ******* in *** ********* *** some ******** *********** **** not ***** **** ******** actually **** *** ***** protocol ** *** ******** cameras ** ***. **** Avigilon's *** ***** *** [link ** ****** *********]:

*** ******** ** ******, Bullet, ****, ***** ****, and *** ****** ****** all **** ** ***** communication *********, ********* ******* S, ** *********** **** the ******** ******* ****** system.

******** ** ****, **** responses ******* ** ********* to ***** ***** ** using ******** ******* **** ACC:

  • "***** **** ** ******** left ** ** *** Technician ***** *** *****, most ***** ** **** cameras ******** **** *** VMS, **** ** ******** VMS **** ******** ******. This *** ** *** full ******* *** ******** enhancements."
  • "*** **** ****** ***** be ** *** ********** camera ** *** ********* directly ** *** ***. 90% ** *** *** sales **** ********."
  • "* ****** ***** *** onvif ******. ****** *** cameras ******** **** *** VMS (********) *** ********."
  • "**, ** **** *** Avigilon."
  • "** *** ** ****** supply * ******* ******** via ********, ** ** integrated ******** **** ******** support"
  • "*** **** ****** ***** be ** *** ********** camera ** *** ********* directly ** *** ***. 90% ** *** *** sales **** ********."

***** ****** *** **** person:

  • "*%, ****** *** ******* Avigilon ***** ***** ** connect ** ***, **** it's **%."

******* *** *****

***** ***** ************ *** clearly ***** * ******** minority, ***** ******* *** become ** *********** *** important ***** ** *********** video ************ *******. **** noted, ** ****** ****** integrations ** ******** ** be ********* ** **** allows ****** ********* ** ensure ******* *********** *** depth ** *********** ** systems.

**** /****

Comments (10)

As a follow up, I would be very interested in finding out what the top five or six functionalities not offered by ONVIF that makes integrators prefer deeper, camera 'driver' integration?

From our experience it's a question how well camera support ONVIF spec. For example common issues with ONVIF implementations from different camera manufacturers: enable VBR on stream channel, enable/disable motion detection (or any other camera analytics).

1. Motion detection with onvif requires a extra level of setting, due to most cameras own motion being of a different design, that's to say blocks on screen, and settings, like you know the normal (low low high higher names!). So motion detection on Onvif is an issue, most of time people opt to use the VMS / NVRs motion detection. VMS suffer as they need to process then internally so CPU takes a hit.

2. H.265 Support. which indeed supported on VMS, a lot of Onvif devices fail to send the correct describe element as part of the RTSP stream, which would allow a H.265 to be sent, hopefully Onvif will set this straight when everyone catches up in 2025.  ( a top previously covered by IPVM)

3. Events, be it motion as in 1, or login events, camera errors, backup problems. Event logging security or otherwise seems to not get much in way of support, making potentially device attacks harder to track. That's to say a good VMS could offer an alert notification centrally. 

4. Local memory card recording. Many devices have the  "we support 128gb SD" or if your a Chinese vendor they like to call it TF card (odd when some are clearly some are microSD which there is no such TF device!). So recording to this card has little use, unless a proper Onvif is done so for instance a network outage could allow device to still record, and once back online the recording on the VMS / NVR could be retrieved. As far as I know Genetec do support this, but have never seen it 100% functionally. Axis offer their own take on this but as native only protocol.

5.Certificate management, SSL certificate or indeed any certificate for a device could be read by Onvif, wouldn't be a bad thing a VMS could then produce a set of true secure points of data security to prevent unauthorised access.

6.Configuration backup, there is almost no Onvif support for a device configuration backup, so many device have a so different set of data that makes this a tuff task, however Onvif could in fact make this simple with a extended set of parameters in a simple XML format which can then make a simper way, for a replacement of a device and also allow a VMS platform to backup all cameras, like a snapshot. with the occasional problem, a replacement could be installed and backup and running with minimal effort time and cost.

$0.02

You like the drill, give a thumbs up if you like, or a down if you don't! (opps that's YouTube :-) 

Manf#1, you bring up a very good point. If a VMS has a direct driver for a camera, why couldn't backup of the camera's settings me a function of that? Something to aim for, including making it a function of ONVIF, too.

This is a very good question!

In my perspective Onvif standard is very rich in functionality, sometimes even more then camera direct driver, and the upcoming profile T should really cover most of the needed areas that Profile S did not.

My opinion of ONVIF mirrors Gandalf's opinion on the mines of Moria... I would only choose that path if I had no other choice.

In my opinion, ONVIF is a disaster.  It's heavy, bloated, misleading and open to interpretation.  This is leading to it being implemented at the camera in 'slightly' different flavors.  We support it in our VMS platform, but I'd take a direct implementation to each camera any day.  That direct implementation is cleaner, more robust and generally works better for the customer in almost every scenario.

 

Whatever happened to PSIA :)

In my opinion, ONVIF is a disaster. 

ONVIF is the worst of all possible IP camera standards, except for the other one, PSIA, which failed completely.

Just because it 'failed' doesn't mean it's worse.  That spec was lighter, better defined and way easier to implement than the ONVIF kitchen sink.

Just because it 'failed' doesn't mean it's worse.

Yes, it does. It is worse because no one supports it. Both of us are speaking philosophically at this point because PSIA is not making a comeback. What would you like ONVIF to do to improve?

Read this IPVM report for free.

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

Related Reports

Verkada Coronavirus Response: Free Temp Systems For Government and Health Care on Apr 07, 2020
Verkada has built a reputation on giving away things for free - free Yeti...
Cisco Acquiring Fluidmesh on Apr 09, 2020
Cisco announced it is acquiring niche wireless manufacturer...
PSIM CNL Acquired By Everbridge on Mar 09, 2020
The end has finally come for CNL. Despite for years saying they would...
LSP Presents 2nd Generation FP Power Supplies on Apr 29, 2020
Life Safety Power (LSP) presented its FP2 power supply in the April 2020 IPVM...
Remote Network Access for Video Surveillance Guide on Jul 27, 2020
Remotely accessing surveillance systems is key in 2020, with more and more...
Axis Discontinues Companion Hardware, Fully NDAA Compliant on Feb 03, 2020
Axis will be fully NDAA compliant, as the company has confirmed to IPVM it is...
TVT / InVid White Light Camera Tested Vs Hikvision ColorVu on Mar 18, 2020
With mega China manufacturers Dahua and Hikvision facing both bans and human...
Sunell Panda Cam Body Temperature Measurement Camera Tested on May 14, 2020
Sunell is far less well known than its gargantuan domestic competitors Dahua...
Hikvision Global News Reports Directory on Jun 18, 2020
Hikvision has received the most global news reporting of any video...
Cast Presents PoE Perimeter Lighting on Apr 28, 2020
Cast Lighting presented its PoE powered Perimeter fence system during the...
JCI "Fever Camera" Partners With China TVT on May 19, 2020
Johnson Controls (JCI) is the next big player to get into the 'fever camera'...
Genetec Security Center 5.9 Release Examined on Feb 06, 2020
Genetec released the next major version of Security Center, less than a year...
Milestone Presents XProtect On AWS on May 04, 2020
Milestone presented its XProtect on AWS offering at the April 2020 IPVM New...
Converged vs Dedicated Networks For Surveillance Tutorial on Feb 12, 2020
Use the existing network or deploy a new one? This is a critical choice in...
HID Presents Signo on Apr 23, 2020
HID Global presented their new Signo readers they claim read farther and...

Recent Reports

SIA Coaches Sellers on NDAA 889B Blacklist Workarounds on Aug 05, 2020
Last month SIA demanded that NDAA 899B "must be delayed". Now that they have...
ADI Returns To Growth, Back To 'Pre-COVID Levels' on Aug 05, 2020
While ADI was hit hard in April, with revenue declining 21%, the company's...
Exposing Fever Tablet Suppliers and 40+ Relabelers on Aug 05, 2020
IPVM has found 40+ USA and EU companies relabeling fever tablets designed,...
Indian Government Restricts PRC Manufacturers From Public Projects on Aug 04, 2020
In a move that mirrors the U.S. government’s ban on Dahua and Hikvision...
Directory of 200 "Fever" Camera Suppliers on Aug 04, 2020
This directory provides a list of "Fever" scanning thermal camera providers...
Face Masks Increase Face Recognition Errors Says NIST on Aug 04, 2020
COVID-19 has led to widespread facemask use, which as IPVM testing has shown...
Dahua Loses Australian Medical Device Approval on Aug 04, 2020
Dahua has cancelled its medical device registration after "discussions" with...
Google Invests in ADT, ADT Stock Soars on Aug 03, 2020
Google has announced a $450 million investment in the Florida-based security...
US Startup Fever Inspect Examined on Aug 03, 2020
Undoubtedly late to fever cameras, this US company, Fever Inspect, led by a...
Motorola Solutions Acquires Pelco on Aug 03, 2020
Motorola Solutions has acquired Pelco, pledging to bring blue back and make...
False: Verkada: "If You Want To Remote View Your Cameras You Need To Punch Holes In Your Firewall" on Jul 31, 2020
Verkada falsely declared to “3,000+ customers”, “300 school districts”, and...
US GSA Explains NDAA 889 Part B Blacklisting on Jul 31, 2020
With the 'Blacklist Clause' going into effect August 13 that bans the US...
Access Control Online Show July 2020 - On-Demand Recording of 45+ Manufacturers Presentations on Jul 30, 2020
The show featured 48 Access Control presentations, all now recorded and...
Face Detection Shootout - Dahua, Hanwha, Hikvision, Uniview, Vivotek on Jul 30, 2020
Face detection analytics are available from a number of manufactures...
Sunell is The First China Manufacturer to Market NDAA Compliance on Jul 30, 2020
Most China manufacturers are going to be impacted by the NDAA 'Blacklist...