Open Access Controller Guide (Axis, HID, Isonas, Mercury)

By Brian Rhodes, Published Sep 19, 2019, 11:28am EDT

In the access control market, there are many software platforms, but only a few companies that make non-proprietary door controllers.

********,**** ******** * *** party-only ******************* ****** '********' *****, ******** ********* ******* ********.

** **** ****, ** contrast ****** ****** ******** providers *** ***** ****** of ******** **** ****** management ******* ***.

  • *** *** ***** ********* of ****, ***, ******, and *******
  • *** ***** ******* ********
  • *** ***** *** ****** Control ** *** * Big ******
  • * ***** ********** ***** controllers ** ******* ****** platforms *******
  • *** ***** ******* **** may ********** *********

'Open' ********** *******

** *** ****** ******, the ****** ** ************* producing **** ********** ******** is ************* ***** ** the ***** ****** ** vendors ******* ********** ********.

***** **** ********* ****** to ******* ***** *** proprietary ********** *******, * significant ******* ** *** market ******* ** ********* with '****' *** ***** devices ************ ** ******.

*** *** ****** ******* market, *** **** ****** recognized ***-*********** **** *********** are ******** ** ***** companies:

  • ****: *** ******* ****** two ********* ***********, ****************. **** ****** *** two-door ***********, *** *** A1601 ** ***** **** higher ****** ********, ****** processors, **** * ******. Both ***** *** ****'***** ***, ******** *** **** embedded**** ***** ******* ********** **** ** ****** for *** *****.
  • *** ******: ***** ** **** Abloy, *** **** ************ two ****** ** ***********, Edge *** *****, **** with * ******** ****** can ** ***** ** over **+ ********* ****** systems.
  • ******:*********** *********** ******** ****************** **'* **** ** controllers** ***** ********** **** other ********* ** ****. The *******'* **** ** combo *******/*********** *** ** based *** *** *******.
  • ******* ********:********* ** *** ** 2017, *** ******** ************ sells **** ** ***** businesses. ******* ******** ******* lines ** *********** *** expansion *******, ********* *** IP-based ** *** ** series ********* * ************** **** * ****** firmware *********.**** ** ************ ******* ******** ********, or ***** ******** ***** Mercury's ******** ********.

***** ********* ******* **** of *** '****' ********** options ** *** ******, but ** *** *** familiar **** ****** **** free ******* **** ** *** *** to *** ****.

Defining '****' *** ******

** *** **** ** access ******* *** *** broader ******** ******, '****' has * ********* ******* meaning **** ** *** software *********** ***. '****' for ****** *********** ***** 'non-proprietary' **** ** *********** compatible **** ******* *******.

**** ******* **** '********' in ***** **** ***** where '****-******' ********* ***** use ** ****, ************* is ******, *** ********* (if ***********) ** ***** and ***********.

Cost **********

***** ******* ****** *** each **********, *** ******** cost ***** *** **** be ******* ** ********** software *********. *******, ** a ******** **** *****, pricing ***** ****:

  • **** ***** & *****:*** ***** ** ****** available ****** *** ~$***, while *** ***** **** ~$700.
  • *** **** ***:*** ****** **** ********** is ********* **** ************ with * ****** ***** of ~$***, **** ******* for ***** **** ********** readers *** ~$***.
  • *** *****:*** **** ********** *** two-door ********* ****** ** available ******* ********* *** ~$650, *** ***** **** varies ********* ** ***** base ********** *** *** many ********* ******* *** used.
  • ******: *** *******'* **** of **-**, ********, *** IP ****** *********** ***** from $*** (****** ****) - $*,*** (***** **** bridge) ********* ** ************* of *** ******** ******.
  • ******* ********:**** ** ***** ******** are ********* ** ****** purchases **** ******* ** through ************. ****** **** controllers ******* ***** ** price **** $*** - $400, *** *** ***** cost ** ***** ******* negotiated *** ***** *** projects **** ***** **** counts.

Compatibility *****

*** ***** ***** ******** a **** ** ******* access ******, *** ***** door *********** **** **** with:

Proprietary ******* ***** ******** ******

****** *** *** ********* use ** *** ********** with ***** ***** ******.

*** *******, ***** ********* like ****'* ******** ***** use *********** ***********, ***** differ *** *** *** compatible **** ***** **** access ******** **** *** distribution ****** **** ******* that **** *** *** proprietary ******.

******** ***************************-***** ********** ****** *******, *** **** *** available ** ******** **** use ***** *** *********** controller ******/****** ** * standalone ********** ********.

Access ***** *** * ******

**** ** ***** ** interoperability *********, ****** ******* is ************* **** ********* of ********* **** ***** and ** *** ***** standard ** ****** *******.

** ***** ******** ******* **** *** Want *****, ******* ***** ** readily ******* ** ***** platforms, **** ***** **************** standards, ******* * *** Profile * **** **** adoption **** ******* **** only *** *******:

Three ****** ******** **********

***** ********* ********, '*********', where *********** ********** **** one ******** *** ******** to *******, **** **********.

*** ***** ****** ******* that ********** ****** ********* and ********** **************** ***:

  • *********** ********/************
  • *** *********/*** **** *****
  • ****** ******** ** *******

Unsupported ********/************

*****, ** ***** ** existing ****** ************ *** features, **** ******* ******* system ******** *** **** controller ********, ***** ** no ********* * *** platform ******** *** **** range ** ******** *** integrations. ********** ********, **** OSDP ** ***** *****-******* may ** ********* ** the ***** ** *** system, *** *** *** other.

New *********/*** **** *****

******* *******, ** ***** in**** ***** ******* ********* Mercury ******** ********?** **** ********* *** observe * '******* *** Mask' **** ***** ******** to * ******** *****.

*** ***** *** *** always ******** *** *** all *** ***** ******* have **** ** *****, but ****** ******** ******** to * *** ****** can ** ******* *** potentially ******* ********** ********* fees ** **** ***** refused ** *** *** vendor.

** ***** *****, **** Honeywell ********, ********** ******** chips ** *** ********** board *** ** ********.

Voided ******** ** *******

*******, ******* *** ***** to *** '**** *******' taken-over *******, *** ** they ********* ******** **** when ********* **** *****.

Comments (22)

The chart above is confusing to me. What does "PRIVATE BRANDED" mean?

Avigilon doesn't have any private branded hardware for access control, nor does Genetec.

Agree
Disagree
Informative
Unhelpful
Funny

in terms of the chart, 'Private Branded' means it may be 3rd party, but the company directly offers it as their own part number or private labels.

Your points about Avigilon and Genetec are interesting though, because while they have their own part numbers, neither companies hide the original manufacturer brands. I'll edit that chart based on this. Thanks for raising it!

Agree
Disagree
Informative
Unhelpful
Funny

Thanks, Brian. I thought that might be what you meant.

They definitely don't hide them at all -- Genetec literally only adds "SY" (for Synergis) in front of the standard Mercury part numbers. Avigilon's are much more convoluted, but even they have more recently started using "LP1502" for controllers, and the MR-52s have always been designated as such --- thus my confusion.

Agree
Disagree
Informative
Unhelpful
Funny

Same with BluB0X... we use Mercury's board naming convention.

Agree
Disagree
Informative
Unhelpful
Funny

Thanks!

Agree
Disagree
Informative
Unhelpful
Funny

Avigion private labels Vertx (embedded version) and Genetec private labels ICT (Synergis IX).

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

If slapping your name on someone else's product is ""Private Branded", then there needs to be a completely different category for "Proprietary" like Software House, S2, AMAG, etc. I suppose maybe there is a case there for the Synergis IX line if it couldn't be used as a standalone ICT system separate from Genetec (I have no idea), but as far as I know there is nothing about the VertX units from Avigilon that is any different than the Mercury boards -- their product under a different name.

Agree
Disagree
Informative
Unhelpful
Funny

Not sure how it should be defined. However the Synergis IX was specially/braded made for Genetec, not sure if it will work with standard ICT software or not. Prowatch hardware is another one that is custom made by Mercury but could be used by other systems by updating chips. Avigilon has their own software embedded on Vertx (small systems only) so it's not merely a sticker.

Agree
Disagree
Informative
Unhelpful
Funny

This may be for another report - but it would be interesting to have a breakdown of what features of the Mercury boards are supported by each software manufacturer.

Agree: 3
Disagree
Informative
Unhelpful
Funny

I'll ask around about this and see how complex the list might be. As the saying goes 'There's more than one way to peel the banana' (yikes) so this pragmatically means that different combinations of hardware and software functions produce similar platform abilities.

'Elevator Access' is one example. Lots of platforms claim this, but some use I/O hardware contacts, while others integrate with elevator control systems. Same claims, but (very) different control types.

Agree
Disagree: 1
Informative
Unhelpful
Funny

Another software platform which could be included is AccessNsite by American Direct, which supports both Mercury and HID hardware.

Control Panels - AccessNsite

Agree
Disagree
Informative
Unhelpful
Funny

Nice article and charts, might add Gallagher, have done some work with them in past, particularly around their PIV offering, they have their own controllers. Might you consider OSDP and other standards mappings?

Agree
Disagree
Informative
Unhelpful
Funny

This chart is a keeper - thanks.

Agree: 1
Disagree
Informative
Unhelpful
Funny

We have to upgrade to the group plan to download the PDF?

Agree
Disagree
Informative
Unhelpful
Funny: 1
Agree
Disagree
Informative
Unhelpful
Funny

This is a helpful chart, but where is Hirsch?

Agree: 2
Disagree
Informative: 1
Unhelpful
Funny

I'm reading the article in question but, I mean you put AXIS as a main manufacturer of Access Control systems?? Axis is Big on cameras and VMS systems, no doubt about that but AXIS is not relevant when it comes to controllers for Access controls!

I get HID and Mercury but why Axis ??

You could've included names such Software House, Lenel/S2, UTC. which are big in the Industry !!! I know they're not Open platforms but for Big Jobs only HID and Mercury are fitted..

Agree
Disagree
Informative
Unhelpful
Funny

Regardless of their market share, Axis is an Open ACS platform that is supported by various 3rd party software packages.

SWHouse and Lenel are both on the chart, but this article is about Open systems, not proprietary.

Agree
Disagree
Informative
Unhelpful: 1
Funny

Thanks for the comment!

The subject of this post is clearly: 3rd party, interoperable controllers. This is not a list ordered by overall market share. Whatever the market share, Axis controllers are supported by a number of other systems.

To your point about including 'Software House, Lenel/S2', both of those platforms are listed.

Agree
Disagree
Informative
Unhelpful
Funny

Looking for OEM list for Access Control product globally.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Very informative article. I didn't know there are so many brand.

Agree
Disagree
Informative
Unhelpful
Funny

Very informative article. I didn't know there are so many brand.

Agree
Disagree
Informative
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 7,203 reports and 959 tests and is only available to subscribers. To get a one-time preview of our work, enter your work email to access the full article.

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