Honeywell NetAXS Access Control Profile

By Brian Rhodes, Published Jan 06, 2016, 12:00am EST

Honeywell is one of the biggest names in security, and one of their most popular offerings is web based access. Inside we examine Honeywell's NetAXS platform's target market, pricing, key strengths and biggest gaps for access control.

Profile

Honeywell's access offerings include several separate platforms, each positioned to a different market and installer segment. NetAXS [link no longer available] is a panel based, webpage client small system platform, available to ADI customers servicing small to medium businesses.  NetAXS is a serverless, edge controller system without the bells and whistles of more advanced platforms.

For larger, heavily integrated, enterprise scale systems, Honeywell offers Prowatch, a platform we will cover in a different profile. Of note, that particular line requires dealer training before reselling or services is allowed, while NetAXS essentially is open to any ADI customer.

In part due to ADI's substantial distribution availability and brand awareness among end users, NetAXS is typically represented by dealers already familiar with the relative design and nomenclature of Honeywell's alarm systems, especially the Vista line of intrusion panels.  NetAXS is an easier transition for alarm installers to sell, service, and install than other more complex access systems. 

Comparison Chart

The table below contrasts Honeywell NetAXS versus relative competition based on common differentiation factors like system size, platform 'openness', ease of video integration, and how the product is sold or available:

 

Hardware *******

****** *********** *** ********* in *** **** *******, an ********* ***** ***** can ***** ***** (****** [link ** ****** *********]) , ** * ******* wall ******* ********* (**** [**** no ****** *********]) ******* ** the **** *****. *** ***** ********** between *** *** ******* is *** ******* ********* model ** *** *****-**** while *** ***** *** model ******** ** ******** 4 ***, *** ******* power ****** *** ***** for ****** ********* *** door ********* *****:

* ***** **** ** controller, *** ******-* (***** [link ** ****** *********]), is * ****-**** ******* board ********* **** ** a ***** *** *********. Multiple ******, ******* **** are ****** **** ** four **** ****, ** if **** *** ******** with *** ** *** door ********* ******, *** be ********* ********.  *********** can ** **** ****** via **-*** ***** ** each ***** ** ** way ** *** ******* an '******** ******* ****' where *** ********* ***** is ******** ** '******'.

*** ****** ****-**** ***** ** connected *******, *****, ** switches. *** ******* ******* allow * *** ** 450 ** @ *****, while ***** *** ********* models ****** ** ** 3.5 * ****.

Management ********

********* ****** ** * serverless ****** ******, ***** a ********* ********** ** module/card ***** ***** ** host ********. *** ******* based ****** ** *** same, **** ***** ********, regardless ** ***** ****** hardware ****** *** ****:

*** ********* *** ********** functions *** *****, **** live **** ********, ********** management, *** *********** ********* each ********* ** ******* options **** *** **** webpage *********.

****** ****** ********, ********* alarms *** ************* ******* are ***** ** *** main ******* **** *** automatically *******. *** ****** software ** **** ********* onboard ***** ********, ********* user ********* *** ********* and ******** ************ ** SQL ** ***** ********* are *** *********.

** *******, ****** **** proprietary ******** *** *** system ****** ******** ******** access *******. *******, ******** adapters *** ********* *** taking **** ******** **** Rusco ********, ***** ********* new ************* ** ***** and *********. *** ***** Mercury ******** *********** ** HID ***** ****** *** not *********, ****** ***** small ****** ******* **** ******** ****** ******* ** **********'* ****** ****.

****

*** *****, ******-*******-**** ******* requiring ** ***** ***********, NetAXS ** ****** ***** or ******** **** **** other ******* *******. ****** **** ** generally ******* $*** - $450 per **** *** **** including * ******* ***** and * *** *** reader. ** *******, *** 'per ****' ******* ***** with ****** ******* ***** four-door *********** ******** ** the ****** **** ********.

******** ** ***** ***** level *******, ****** ** less ********* **** **** other *** ****** *******, due ** *** ********** system ****** **** ***** an ******* ******* ~$**** in ***** *******, **** the ********* ************* *** ******. ****** ***** ****** or ********* ***** *** platforms, ****** **** *** integrate **** ***** ******* and ***** ************ ******* is ****** *** *********-****.

*******, ***** ********** ******* like**** ***** *********************'* *** *************** **** ******* '******-****' features **** ***** **** roughly equal ******** *** **** with ******.   

************, ****** *** ** recurring ********* ** *********** fees ** ***, ** contrast ** **** ********* systems.

 

********

********* ****** **** *** ********* ** 3rd ***** **** *********** and ******** *** **** works **** *** *** hardware ****. 

** ********, ****** ******* is *********** **** ** any ***** ********** ******* and *********** **** ** bits ** ****, ********* most *** *** *** 125 *** *** ******/******* 13.56 *** *******.

Video ***********

***** ***** *********** *** NetAXS [**** ** ****** available] ** ********* *** an ******** ***** **** includes * **** *** drive, ******* ** ** very *******. *** ** the ******* ** **** ****** ***** can **** ** **** with ********* ** ******* and ** ***** ***** cameras, *******, ** ******* can ** ****. ****** video **** ******** *******, and ******** ******** ******** is *** **** ********** supported *******.

************, * *** ** three ** ******* *** be ********* *** *****, with ********** *** **** resolutions ******* ** * 1 ***.  ***** ** not *********, *** * maximum ** *** **** can ** **** **** CIF **********.

******* ** ******* ** a ******* *:** *** event **** ********* ***/**** alarms *** ***** ********.  Clip ******** ** ********** within *** ******* ****** web *********. ****** *********** of ****** *** ***** events ********** ** ****** events, *** ******* *** not ********.  ***** ***** can ** ********, *** access ******* ****** ********.

WIN-PAK *** ******** ********

** ****** *****, ********* integration, ** ** ***** advanced ******** **** ***** or ******* ****** *** needed, * ******** ****** based *********** ****** ********* WIN-PAK [**** ** ****** available] **** ** ****.  This ******** **** *********** cost, **** ******* *** software ******* ~$***+. ** addition, ******* *** ******* ********* approval ****** ***** **** to ******** *** *******.

***-*** *** ************ **** Honeywell's **** ******** ***** platforms **** ***** *** or ****** ***, *** no *** ***** ***** or ****** *******.

**********

****** ******* ******** ** ******* *** party integration **** ***** ******* like *********/**** ****** ** 3rd ***** *****. ******* are ******** ******** **** elevator *******, ****** */* integration, *** *** ******** integration.

******* ***** * ***** number ** **** **** **** ** a *******. ***** ***** can *** ****** ** to *** **** *******, system *********** **** ** sluggish ******** ** ****** based ******** *** ** dependence ** *****-**** *********, and ****** ***** **** badge ******** *** ****** reporting *** *** ** supported.  

** ***** ****** ** upgrade ** ***-********* ****** platforms, **** **** *** be **** ** ***** existing ********** ******** *** an ********* '********' ******* will ** ********.

No ****** ***

******* ******** ** **** NetAXS *** ** *** for ****** *******, ******* instead ** ****** ******* for **** ****** ******.  In ***** ******* ** NetAXS, ** ******** ********* app *** *********, *** ** *** ***** been ********* *** ** ** ****** *********. 

Other ********

**** **** ** **** of ** ******* ****** ** profile ***** ** ****** companies. **** *** **** others:

 

Comments (6)

Steve Nauman

01/07/16 04:38pm

You know what they say: once you go Honeywell, you never go back.

Because you can't without ripping most everything out and starting over.

Avatar

Chuck Janzer

IPVMU Certified | 01/09/16 01:42am

"When users choose to upgrade platforms, they will not be able to reuse existing controller hardware and an expensive 'forklift' upgrade will be required."

I will take issue with this comment. While it is true that the NetAXS hardware is not compatible with other manufacturers - as with almost all Honeywell hardware - the NetAXS panels are fully and directly supported in WinPak. They are also supported in ProWatch, when you know how to do it. And I'm told it will be directly supported in ProWatch in a future release.

ProWatch also supports a number Mercury controllers, not just the Honeywell version of the Mercury, PW6 series.

Steve Nauman

In reply to Chuck Janzer | 01/09/16 02:00am

"Honeywell hardware is compatible with some Honeywell software! Kind of. Sometimes"

Not impressed.

Avatar

Brian Rhodes

IPVMU Certified | In reply to Chuck Janzer | 01/09/16 02:13am

Thanks. I clarified the statement in the post to read:

"If users choose to upgrade to non-Honeywell access platforms, they will not be able to reuse existing controller hardware and an expensive 'forklift' upgrade will be required."

Also, WIN-PAK is like a Honeywell-proprietary PSIM. It is purely optional to buy and use, and is not a required element of NetAXS.

ProWatch is a separate system and is not compatible within NetAXS, unless software like WIN-PAK is used.

Avatar

Chuck Janzer

IPVMU Certified | In reply to Brian Rhodes | 01/09/16 03:37pm

Better, but still not quite right. ProWatch is software. An "upgrade" to WinPak. Almost all hardware used in a WinPak system can be upgraded to work in a ProWatch system. Hence my comment about making NetAXS work on ProWatch - already possible, but not officially supported by Honeywell. A future release of ProWatch is suppose to directly support NetAXS hardware.

Avatar

Brian Rhodes

IPVMU Certified | In reply to Chuck Janzer | 01/09/16 09:52pm

ProWatch is altogether a different platform, just like WIN-PAK. Neither are needed for NetAXS.

You cannot use ProWatch controllers, or any PW marked hardware, in NetAXS.

Keeping this point clear is important for this profile addressing (only) NetAXS.

Read this IPVM report for free.

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