Brivo Opens Up, Adds Mercury Support

•Published Mar 16, 2017 13:56 PM

Brivo's cloud-based access control was built around the companies proprietary hardware controllers, and was often seen as a limitation by customers. Now, the company has shifted strategy, by embracing hardware from perhaps the most well-known open platform access control company, Mercury Security.

IPVM spoke with Brivo CEO Steven Van Till [link no longer available] about their decision to embrace open hardware and what this means for Brivo's own hardware line.

In this report we share details of the conversation and analysis of this move.

*****/******* ************

***** ********* ******** ******* *** ******* ********** ***** *****-****** ********, **** ************ anticipated ** ********* ****. ********* ** the *******, *** ******* ******** **** provide *** **** **** ************* ** Brivo's *** *********** ********, *** **** allow ********* **** ****** *********** ** the ****** ** ******* ******** *******-***** ****** control ******* ** *****'* ********.

Consultants ******* ****** *******

***** **** **** *** ******** *********** becoming **** ********** ** *****-***** ****** control *******, *** ** *** **** time, **** ********** ** ****** ******* in *******. ******* ********* **** * project ** * ********** ** *********** a ********** **** *** * ************, and **** *********** ***** **** ********, such ** ******* **** ********, ******** ** ***** ***** *** ***** to **** **** **** ** *********** consultants, ****** ***** ****** ********.

Integrators **** ***** ******** ** *******

*********** **** ***** **** ***** **** saw ** *********** *** *****'* ***** system, **** ********* ** ****** *** number ** *********** **** *********** ****** to ******** ******** **. ***** **** **** the ****** ** *** ******* ******** was *** ** *** *** ********* feedback ***** **** ***********, *** *** difficult ** ******* **** ******* ******** that *** **** *******-*******.

Proprietary *** ****

*****'* *** **** **** *** ******* plans ** ******** *** ******* **** of *********** ******** ******, *** *** no plans ** *********** ****. *** ******* is ********** ** ****** *********** ******* in ***** ******** *** ********* ****** expect ******* ** *****'* *** ********.

No ***** *** *** ** ***** ********

***** ***** *** ** ******** ***** to ******* ***** ******** ******* ****** Mercury, ***** **** **** **** **** *** ruled *** *** ***********. *** ******* of *** ******* ***********, *** ******** from *********, **** ********* ***** ******, if ***, ***** **** ******* *** ****.

Utilizes ******* "**** ****" ********

********* *** **** ** *** ******* hardware, ** ******* ******** *******-***** ******* to *****'* ********, ****** ** **** to ** ** ******* *** **** for ********** ******** ** *********** ********, according ** *****. *******-******* ******* *********** have ********* * "**** ****" ******* for ******* *****, ***** ***** **** can ** ******** ** ******* *** controller ** *****'* ***** ****** ******* the **** *** *** *****-******** ****** hardware.

New ******** **** ** ****** ******

**** **** ** **** ***** ****** integrators *** *********** ******* ******* ** install ***** ** *** ********* **. take **** ******** *******, ********* *** CEO. ***** ****** ********* *** ********, the ******* **** **** *** *** their ******* ********** *** ****** ******* hardware *******.

Price **********

********* ** *****, ******* *** * system ***** ***** ******** ** ******* hardware ****** "**** ** ***** **%" for * ********** ****** *****, *******, etc. *** ******** ************ ***** ** same *** ****** ********.

Good **** *** *****

***** ***** ******* ******** ************* ***** customers *** ******* ** ****** **** Brivo ** ***** ****** ******* *********, this **** ******* *****'* ********** ** their ********, *** ********** *** ****** for *********** ** ***** **** ** a ****** ** *********** *******. ************, Brivo *** **** ********* ** *********** Mercury cards, **** ** ***** ***** [**** ** longer *********] *** ****** [**** ** ****** *********] *****, **** systems ******* ******** ************** (**: ******** *******) that ** **** *********, ** ***********, when **** **** *****'* *** ********.