HID Releases VertX Replacement Aero

By Brian Rhodes, Published Aug 10, 2020, 01:02pm EDT

HID is replacing two established and broadly supported types of access controllers with a new line, Aero, requiring new integrations from partners.

IPVM Image

In this note, based on answers from HID, we examine:

  • Aero replaces two HID controller lines
  • Why it is not compatible with Mercury integrations
  • Which features are limited compared to Mercury hardware
  • The advantages of Aero's similar architecture and size vs. VertX
  • Why Aero can disrupt partners by requiring new integrations
  • The competitive impact of HID Aero in the access market

Aero ******** ***** *** **** ***

*** *** ********* ** will ***** '*** **** controller ***** ***** *******' - ******* ******** *** this *** **** ********.

**** ** ********* *** different *** ********** *****: VertX *** ****. ** terms ** **** ****** applications, ***** ** ******** used *** *****/****** ********** platforms ** *** '*** East, ****, *** *** Middle **** ******** *** platform ** **** ********** with ****** ******* ************ **** ********, *******, and *******.

*** '** ** *** Door' **** ********** ** most ***** **** *** small ** **** ****** door ****** ***********, **** a ***** **** ******/********** model ******** ** ******** single-door ****** ********** ****** called'****' (*** *** ******).

Aero **** ***, ******** *** *** ******** **. ******* ********

*** ***** **** '******** Mercury ********, *****, *** Edge', *** *** *********** does *** *** *** broadly ******* '********* *******' firmware *** ** *** compatible **** ******** ******* integrated ****** ******* ** default.

*** ******* **** **** while **** ******** **** common ******** ** ******* firmware, *** *** ****** is * ******/********* ******** that ** *** ********** with ******** ******* ********. HID ********* ** ****:

******* ********** ********* *** controllers ** *** ********* with **** *** **** versa.

** ***** ** *** separation, *** ******* *********:

*** ********** ****** *** two ******** ********* **** are *********** ** **** other *** ***** ****** core **********. ***** **** is ***** ** ******* Mercury **********, **** ***** utilizes * ****** *** and ******* *** ********* for *** ******** ****** segment *** ****** ******** needs. ***** *** ******** partner ******** ***** **** partners ********* **** **** while ******* ******** ******** to ******* ********* **** the ******* *****.

***** **** ********* **** support **** ******* *** Aero ***********, ***'* ******* strategy ** ** ****** Mercury ******** ******** *** 'high-end', ***** ******* *** promote **** *** *******, more ***** *******.

Uses ***** **** ******* *** ************

**** ******* ******** ******* to *****, ******** *** 'same *** *** **** factors' *** **** ********* locations, *** **** ********* component *** *** *******.

** ***** ** ************, Aero ****** *** **** 4 ***** *******, * door ********** ****** *****, a ****/****** ********* ****** called ****, *** ***** and ****** ********* ************ called **** *** ****:

IPVM Image

*** ******* ****** ** Aero *** ******* ** VertX *** **** **** capacity **** ****, ******** support *** *** *********** of ** '*********' ******. The ********** *** ********* together *** *** ******** cabling ** ****** **-*** connections.

No *** *******

*** **** ***** ** either ** ** ** VDC ** *.** *** and ** *** *** powered.

Aero ******** ******* **. *******

** ***** ** ******* separate **** **** ******* alternatives, *** **** ******* hardware ******** *** *** available ** ****. ***** differences ******* ** ***** support *** '**** ********' (often **********) ********* *** integration ******* ** ******** platforms *** ***** ******* may ** *********** ** relay ******** ****.

** ***** **** ********, higher ******** ******* *** needed, *** ****** ********* toward **** ********* ******* Security *********.

OSDP, ******** ************ **** *****

*******, **** ****** ******* for ********** ******** ******** not ********* ** *****, including **** ****** *******, Encrypted **** (**** **), and ***.** ******* ****** verification.

*** ******** **'****** *******' ******** ******* ** ****** to ** *** **** important *********** *** **** Aero *********.

Pricing *******

*** *** *** ******* specific **** *******, ****** it ** ********* *********** for *** ****** *******, but **** ** ***** be '************* ******':

*** **** ******* ****** is ************* ****** *** the ******** ****** ****** segments *** ********** *******. HID-branded ********** ********* ** to ****** ******* *** partnerships ***** ****** ******* manufacturers ****** ***** ******** with *** ******** *** SDK ** ****** ******* their ********** ***** *** channel. *** *** *** pricing ******* ****** **** from *** **** ******* channel.

*******, ********* ** ** similar ** *****, *** V1000 *** * ****** price ** ~$***, **** 'downstream' ******* ******* **** a ***-**** ********* (****) ~$450 ******* ** *****/****** (V200/V300) ********** ******* ~$***.

Aero ******** *** ************

*** ** *** ******* potential ******** **** **** is **** ******** ***** platforms ****** *** ** unless * *** *********** is *********.

***** ***'* ********** ***** size *** **** ******* in ********** ****** ******* access ****, ** ** not ****** ******* ** not ********* ** ****, but ***** ** *** take ****.

*** ********* **** **** existing ***** ********* **** simply *** ***** ******** Mercury ************ ******* ** Aero, *** ***-******* ******** at *** *******, **** basic *** ** *** access ****** **** ****** need (** **** ********) developed *** *********** **** integrations:

IPVM Image

VertX ********* ******* ********* ** ****

*************, ***** ********* ******* are ********** **** *** Aero ***** ******* *******, and ***/******** ** ***** modules *** **** *********, meaning **** ********* *** retrofit ******* *** *********** still *** ********* *******. HID *********:

*** ***** *** *** I/O ****** **-*** *****. Each *** *** ****** support ***** ** **** I/O *******. *** ***** can ******** *** */* module *** ** ***** and *** ***** ** Aero, **** ** *****, or **** ** ****.

*******, *** ************* ** limited ** ****/***** *** not *******:

** **** ******* ****** communicate **** ******* ** modules *** * ******* partner ****** *********** **** Aero ** *******

VertX ***** **** ****: ******** **, ****

***** *** *** ********* Aero *** **** ***, VertX **** ****** ** distribution ***** ***-**-****, *** support **** ****** ** place ***** *** *** of ****.

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

******** ** ************** • End ** **** – December **, ****• ***** Scheduled **** **** – June **, ****• *** of **** – ******** 31, ****

Competitive ***********

** ** *** ********** Aero ** **** *** segments ** *** ****** market ** ***, *** given *** *** *********** required ** ******** ** use **, **** *** actually ****** ***'* ********* versus ***** ** *** short ****.

*******, *** ** ********** its *** ********* *** reducing ******** ***** *********** with ******* ** ********* Aero.

*** ******* *** ******* set ***** *** ********* large-system, ****-******** ************ ** Mercury ******** ******** *** is ******** **** **** eroding ***** *********. ********, Aero's ************ ***** ** unlikely **** ******* ******** future ******** ***** ** the ***** ****** **** of *** ******.

Comments (19)

**** **** **** **** existing ***** *********** **** not ** ********** **** the *** **** ***********/******, or **** ** **** mean **** ******* **** need ** ******** ************ of *** *** **** platform. * ***** ** mostly ****** ***** ********* compatibility ** *** *** Aero ***********/******.

Agree: 1
Disagree
Informative
Unhelpful
Funny

*** ***** ********* *****/****** VertX ******* *** ********** with *** *** **** X1100.

**** ** **** **** that ******* **** **** to ******** ************ ** the *** **** ********.

**** ** *******. ******** VertX *****/**** ******* ** not ***** *** **** X1100 *** ******** **** need ** ******* *** integrations ** ******* ****.

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

******* ** ** *** S2-ACM ** *** ***** version ** **-***, ** you **** **** *** have ** *** *** new **-*** ****** *** have ** ******* *.* or *******. ** ***** this *** *** **** when *** **** ****** was ********** **-***-**. ********* they **** *********** **** compatibility *** *** ******** systems.

******* *********.

**** *** **** **** report *** **** ** something **** ****** ******.

* ****** **** ***** the ******** ********** ******* footprint **** **** **********. So ******, *****, **, Software *****, ******, **** etc.

******* ******** ***** ** 128/64/32/16/8/4/2/1 ****** ******** ***** along **** * ******** column *** *** ***, Software ******** ** ****** licenses. *** **** ***** be ****.

**** ***** *** *** scale *** ************* ***** on **** ****** ********.

***? **? $$$

Agree
Disagree
Informative
Unhelpful
Funny

**** ** **** ** able ** **** *** spot ** * **** in *** ****** ** a ***** ** ****'* if ** **** *** in * ******* ******** Cloudlink ***, ** ** a **** **** ***, will ***** **** **** to ** ******** **** an ****? 👀🤷‍♂️

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

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

Agree: 1
Disagree
Informative
Unhelpful
Funny

***********. *'** *** *******.

Agree: 2
Disagree
Informative
Unhelpful
Funny

*****,

**** ** ******* **********, Product ********* ******* ** Genetec. ********* *** ***** question, *** **** **** not ******* *** **** in *** *********, ** they **** *** * different ********. *** **** can **** ** ******* by *** *****, ** such, ** ***'* ** able ** ********* ** directly ******* *** ******** Cloud ****.

Agree
Disagree
Informative: 3
Unhelpful
Funny

* ***, * ********** the ***********. ** ***** a **** *** *** Cloudlinks ** *** ***** are ****** *** **** HID?

Agree
Disagree
Informative
Unhelpful
Funny

*** ** **** * plan *** *** ********* to ********** *** ********* with **** ************, *** we *** *** *** ready ** **** ** official ************.

Agree
Disagree
Informative
Unhelpful
Funny

****** ****, ********** ********** your ****!

Agree
Disagree
Informative
Unhelpful
Funny

**********! *** ****.

Agree
Disagree
Informative
Unhelpful
Funny

** *** *** ***** thing **** **** ******* my **** **** * read *** *******, ********* they *** **********.

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

*** *** **** ******** as * ********** ********** like *** **** **** can (************ ******* *** separate ******** ** *** on *** ** **) ?

Agree
Disagree
Informative
Unhelpful
Funny

*'** *** *** ** the *************** ** **** EVO ** *** *** of '****' *** ****** ****. Thanks!

Agree
Disagree
Informative
Unhelpful
Funny

*** *********. ** *******: They ** *** **** yet.

'**** ** * ***** question *** ** *** still ********* *** *******. We **** ******* ******* details ** *** *** streamlined **** *** *********** portfolio ** ** ******** the ****** ** **** product. ***-**-**** *********** ******** to **** *** **** be ******** ** ********* according ** *** ******* lifecycle ************** ******* ** conjunction **** ** **** following *** ****** ************.'

Agree
Disagree
Informative: 1
Unhelpful
Funny

** **** ** * number ** ****** ******* systems. **** ** ***** support **** *** *** VertX *** ******* ******. We **** ***** **** an *** ***** ***** and ** ****** *** Mercury. * ***** *** the ***** ** *** HID ***** **** *** I ***** **** *** same ***. *** *** sell ******* *** **** 20 **** ****** ******* manufacturers ** ****** ****.

Agree
Disagree
Informative
Unhelpful
Funny

*** **** ****** ** logical, ******* *** ******** OEM *****'* ****** **** the ***** ** ******. HID **** ****** ****** partners **** ***** *********** to *** *** ******* platform. **** **** *** others ** *****/****. ******* the ** ***** *** many **** ******** ** Vertx, *** ***** ***** tends ** ** * bit ******** ** *********** options (*** *** *** users) *** ***** *******, which ** ******** ******* what *** *****.

Agree
Disagree
Informative
Unhelpful
Funny

** * ************* **** correctly ? ***** ? maybe *** ? *********** what **** ******* ** achieve ** *** ** be *** ********** ***** of ****** *** *** say ***** ** ****** size ****** ******* ******** partners ? ** ***** actually **** ******* ( thinking ***** ) ? i *** *** ****** control ******* ** **** is *** ******** *** would **** *** ****** integrator ** *** ***** own ( *********** *********** mostly ) , ***** are ***** ********** ***** systems *** ***** ** 32 ***** *** ***** up ** **** *** unlimited *** ****** **** of ******** *** ******** who ****** **** ******* or ** **** **** proprietary ***** ** **** in **** ***** **** VertX ** *** **** aero ********** ** ***** installs **** ***'* **** a *********** *** ******* ? * *** **** Genetec **** ** **** care ** ***** ********* and ******* **** *** making ********* ********** **** AERO ** ********* ****** an ********** ***** ****** compatible **** **** ***'* ? ***'* **** ******** for ******* ******* ? i ***** *** *************** of ***** ******* ** not ********* * ******** manufacturer ** ********** ************ can ****** * ***** if **** ** **** compatible ** ******* **** genetec ** *** ****** access ( ***** *** mentioned **** ) **** isn't **** * ***** where ******* ** ****** be ******* ? *** even **** *** **** two ********** ******. ? Mercury *** **** ? No **** ******** ** negativity ********

Agree
Disagree
Informative
Unhelpful
Funny

*** ************* **** ** publicize *** **** *******, let *** ***** **** where **** ***. ***** of **** ****** ******. Tired ** $** *** month. ***** ** ******** Dinosaurs. ***** ** *** the ******** ** ****** systems **** ** ******** jack. ***** ** ******* and ******* *** **** 1980ish ******* ******* ***** the **** ***** **** is **** ** *** OLD *** ***.

*** ** * ******* time *** ******, **** if ** ***** *** (YES, ******* ***) ** the * *** ** business.

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

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