Favorite Access Control Manufacturers 2016

By Brian Rhodes, Published Oct 25, 2016, 09:31am EDT

Integrators told us "What is your favorite access control management software/system? Why?", and the responses are interesting indeed.

IPVM Image

***** ** ***** ****** favorite *** *****, *** group ** ****** ** the *** ******** **** familiar ***** *** ******** some ****** ******* ***** for ***** *******.

****** ** **** ** the *******, ******* *** key ****** ** ****, and ******* **********'* ***** comments ********** ***** *****.

[********:** *********** *********** ** ******* *** any **** *********, ********* these *******. ****** ****** any ********** *********** ** info@ipvm.com.]

Top *********

** ****** ******** *** voted ** *** ***** favorite. **** **** ** different ********* **** *********, with **** ******* * percentage ** ***** ** warrant '**** ********' ** all.

*******, *** ***** ** 'top ****' ****** ***** most ***** *************** ********,******** ***** *****,** ******,******, *********** ***. ***** ********** **** responding *********** *******:

  • "********* ** **** *** reliability ** *** ******** and *** ***** ** the ********. ** **** that ** ** **** to *** *** *** a *** ** ***** in ********."
  • "** *** *** *********** and ***** ** *******."
  • "******* ********. ** ****** it ******* ** ** a ******* ******* ********* video, ***, *** ******* other ****** **********."
  • "********** ** ********'* ******. It's * ***** **** interface, *** *** * lot ***** ********* ****** of ******* **** ***** systems **'** ****. ****** systems ******* ****** ******* over ***** ****, *** they **** **** **** everything."
  • "******. **** **** ** install *** *** ****** Blu ******* ** ******* for * *** ** our ******* *********."
  • "******* ****** *** * very **** ******* *** tightly ********** **** ****** control."
  • "******** ***** ********. **'* very ********* *** **** give *** * *** flexibility."
  • "****** **** ** *** easy ** ****** (**** colour ***** ******) *** great *******."

** *******, ***** *** strengths ** ***** ******, themes ** ****** ********* support, ****** ******** *** hardware, *** ***********/**** ********* 3rd ***** ************ *** important *** *********.

Avigilon *** ******

***** ******* ****** ** **** question, *** ** *** biggest ********* ** '********' votes:******** ***. ******** ********:

  • "******** ***. ***** **** as ********. "*'* * Linux ***" ***** ****** it. ***** **, ******** backend, **** *********** **** other ** *******, *** just ********* ***** **** it *** **** ** IT ****** ****** **** an ********* ******** *******."
  • "*** - *** ***** like *** *********."
  • "******** *** ** **** for **** ** *** customers, **** *** ****** ones."
  • "********. **** ** ***, open ********. ** **** into ***** ***** ******."
  • "******** - ** ***, annual ****, ***"

*********** ****** ******* ********** *** *** **** drawbacks ******** ** *** other '*********' ********* *** even ***** ******* ****** offerings. ***** ***'* ******* core ****** ************* ** solid, *** ******** ***** many *********** ******* **** third ***** *******, *** does *** **** ********* tightly **** ********'* *** video ********** ******** **** only ***** ******** *** searching ****** ** ***, but ** ****** ******** inside *** **** **** ACC.

*******, ******* *********** ***** ACM ******** ** ********** clients ** ******* ******** maintenance **** *** * plus, ******** ** **** other ********* **** ******* hundreds ** **** ********* in ********* **********.

*****'******

***** *** ******* * fair ****** ** ******** votes, *******, ***** ***** selections **** *** ******* than *********, *** **** than *** ***** *******. Lenel *** ******* ** the***** ****** ******* **********.

Mercury ***** ******* *******

******* ***** ***** ***** top ****** ** **************** with ******* ******** ********. Indeed, ~**%+ ** *** top ***** ****** ****** are ****** ***** **, or *** ********** ****, panels *** *********** **** by *******.

** ***** ** ********, not *** *******-***** ********* offer *** **** ***** of *********, *** **** advanced ****** ******** **** event *****-******* *** ***-*** access ***** *** ********* in ****-*** *********. ****** the *****, ******** ***** support ** ******** *** devices, **** ******** ********, and ******** */* ******** are * ******* *********** over **** **************** ****** *************** *********, ********* *** many ******* ****** ****** choose ******* **** **** cheaper ******** ** *********:

  • "**** *******... **** ***** Mercury ********, ***** **** interface, *** *** ****** apps *** **** ***** integrations."
  • "** - **** ******** - ***** **** ******* boards *** **** ********* and *** **** *********** with *****."
  • "********* ***-***** **** ******* with ******* ******."
  • "***, ** **** *** reliability ** *** [*******] hardware *** *** ***** of *** ********."
  • "**** **** ******* ********* and ***** **** **** support"

Regional ********* ******

************** ***************** ********** ****** ****** ********, access ** **** **** regionally **********. ** **** cases, *********** ******** ***** small *** ***** ********* for *** ****** ****** that **** ******* *** better *** ******* *** more *********** ** ***** specific ****.

***** '******' ********:

  • "** *** ******* ******** access ******* *********. *** most *********** ** ** is ****** (****.**) ******* of *********** ******* *** strong **** *******."
  • "***** ***** *********: **** to ***, ********* *** user ***, ******* **********. Does ****** *** ******** very ****."
  • "** *** ***** ******* Access ******* ******... **********, good ************ **** *** manufacturer ** ******* ******* customization ******* *** ********** service."
  • "** *** ******* ** ICT."
  • "**********. ** ** ****** in ************ *** ***."

Government ********* & ********* ************ *********

*** ** **** *****, the ****** ** ******** is ***** ** ***** regulations ** ******** ******** requirements, **** ** ****-******** government ** ********** *********. Depending ** *** ****** vertical ** ********** *******, advanced ******** **********, ******* protocols, ** *********** ******* may ** ******** **** more ********** ****** *** not ****:

  • "****** ********. ** ** a ******, ********** ***** software ******* **** ** essentially **** ** ****** and *** ** ****** SSA ************. ** *** get **** .*** ****, there *** ******* *** FICAM ********** *** **** checks, *** **** ** you ******* ***** **********."
  • "******** ***** *** * good *** ****** ******* and *** **** *** most *** ********** **** FIPS ***. ****** *** validation ******** ** *** panel **** ******** ********* readers (**** ***** ****) is *********."
  • "*******/***** ********** ******** ******* it ********** **** *** HVAC ******** ********** ******* and ** **** ******** BACnet ****** *** *********** to ***** *** *******."
  • "** ** ******* ****** to **** ****** **** integrates **** **** ** the ******** ******* ** our ****, ** *** 'favorites' *** ****** **** job ** *** ***** on **** ** ***** used."

Access '*****' ******

********** ** ************* ****** ******* **********' *******, ***** ** asked *** **** ****** pool: "** *** **** ****, what ** *** ***** access ******* ********** ********/****** you **** ***** ****? Why?"

Geographic ********** - ***** *******

** **** ******, ~**% of *********** **** **** North *******, ** *** results *** ******* ****** to *** ***** ******** market. ** *** *** outside **** ******, * different *** ** ****** may **** * ****** regional ********, *** **** that ** ****.

Comments (18)

With the number of vendors using Mercury hardware, has anyone asked the whatif question, what if Mecury just cant supply hardware anymore.

Avigilon is supplying mercury hw.

I believe his 'what-if' is what happens if Mercury is unable/unwilling to supply hardware to their business partners.

I would think another manufacturer would pick up on the opportunity to provide a similar product and there would be enough leftover Mercury hardware in storage places and distribution to last in the meantime.

So your question is really, "What if Mercury decided to put itself out of business?" As in they decided not to provide parts anymore?

If they had a manufacturing issue it would maybe cause a delay in parts, but not for long. They are first class in terms of production and finding/fixing issues.

Why would Mercury stop when clearly their business model is successful?

This could be applied to any successful open product. What if HID stopped producing readers? What if Corning stopped producing fiber?

Why would Mercury stop when clearly their business model is successful?

They could be purchased by a much bigger corporation, for strategic reasons, and whose endgame isn't necessarily as open as Mercury's was before. A slow pivot.

Maybe like where Milestone ends up in 5 years.

Silly question. Take a company like Mercury. They have a small number of products you could count on 2 hands so they don't have a huge product lineup like a lot of manufacturers. Dozens of access control systems utilize their hardware since it would be silly of them to try to make something on their own when they can get something ready for prime time and open to anybody. They are probably doing quite well. I'm small time and I installed probably 100 or so doors of Mercury hardware in the last year or so. I don't think they are going anywhere.

Avigilon and Paxton for me. Small project Paxton is great, Larger its ACM :)

What's the definition of large in this context?

I cannot agree with Genetec unless something has changed recently. It is extremely difficult to deploy on a site with more than a couple of doors. Try a 100+ door project where every input, alarm type and function has to be individually programmed. No ability to create device templates, alarm templates etc. Also found SV controllers like to lock up often and randomly. Maybe it's better now?

Hi Undisclosed Integrator #5,

I am the access control product manager at Genetec. I would like to invite you to contact me to discuss further. We do appreciate constructive feedback and I could take the opportunity to talk about how the product changed since your last experience.

Nice to see our Inner Range Integriti access & intruder system in the regional section (we do mainly ANZ and Europe). The product is spelled with an "i" at the end, though. We Aussies are a bunch of bad spellers.

Thanks. Fixed.

A graph of voting results would have been nice, like in the past .

We generally do not do graphs anymore. Reason #1 it becomes too tempting for people to misuse in marketing / promotions. Reason #2 we want people to focus on the reasons integrators gave more than the 'rank'.

As Mercury is so common, another issue is security.......

1. the installer is investing a lot of efforts in the deal, discounting, installing, thinking this customer is for the long haul. few months later, another sales guy from a competitor that use Mercury walks in and, take over for lower cost........

2. Mercury SDK is easy to get, what will prevent hostile hacking?

Having generic / open source technology provide flexibility, but, at the same time, it is not secured as much as proprietary equipment. Readers, Locks, Sensors can be generic, but, the main Control Devices and PCs must be secured and protected.

 

something to think about.....

Many systems have the ability to use Mercury Hardware. Those same systems use SQL as a database while other use Postgres. 

Vulnerabilities grow on the trees around us. Ever try and Konboot an S2 panel? What about the new Istar GCM can you Konboot that?

Synergis cloud link on embedded 7, there just has to be a SSH connection somewhere.

This hardware is not available to everyone, use your abilities and access to learn. So you can prevent world hunger.

 

 

Read this IPVM report for free.

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