"** *** **** ****, what ** *** ***** access ******* ********** ********/****** you **** ***** ****? Why?"

* ****** ***** *******: two ********** *** ****** significant ******* **** ******* and ***** ****** ********* may *** ** *** behind.
[********:** *********** *********** ** ******* *** any **** *********, ********* these *******. ****** ****** any ********** *********** ** info@ipvm.com.]
Top ***
*** * ******* **** the **** ***** ****:
*********, *** ***** **** popular ****** *** '****', an ****** **** ********** a *********** ********** ** access ******* ****** ***** security ******** **** ******* and ***. ** ******* those *******, **** ***** commentary *****.
Lenel *******
*** ****** ***** ********* most ********** ** *****: Lenel.
****** ** *** ******* rash ** *****'* ******** issues ******** ** ******** ******** *****, ***** Does *** ********, ** ** ***** from ********* *** ******** are **** **** **** business *************. *** ********'* dated *********, **** *******, and ******** ******* **** cause ******* ** ****.
*******, ********** ******* *****'* VARs *** ********* **** are ***********, *** ***** volume ** ******** ***** is * ********** ** the *******'* **** *********. Indeed, ***** ******** * sizeable ****** ** '******** brand' ***** ** ****. However, **** ** ***** divulged **** ***** ***** VAR ****** ****** ********** with '***** *******', ****** OnGuard **** *** ******* 'favorite', ****** ****, ******.
**** *** ********** **** the *****:
- "*****. * **** * strong ****** *** *****, having ****** **** ** for *** ****. **'* clunky, ******* ******** **** randomly ******* (******* *.*), costs *** **** ** license **** *** *** little **** *** ***, and *** ******* ***'* that *****."
- "***** *** **** *** worst **********. ********** ***** government **** *** **** deciding **** ** **** to ** ** *** federal ***** ***, *** another, ******. ****, ***** had **** *** ****. Hands ****. **** ***** the ****. ***** ** now **** ******* ****** that ***** **** ******* boards. ***** ******* *** has *** *****. ***** innovation ** ****. *** when ** **** * problem, ******* *** ***** resolved ** ****** **********. Example- *** ***'* ******* out ** *** ***."
- "***** *** ** **** through ***** ** ******* and *************** ******* ***** and ***** ** **** time *** ******* *** reputation. **** ******* ** it ***** **** * weeks ** ******* * DOA ****. **** ** find *** **** ******* source **** *** **** they *** * *** batch ** ****** (******* story) *** *** ******* to ******* ******* *** boards. **** ** ********** Lenel *** ** *** was *** ******."
- "*****. *** *********. ********** software. ******* ******* ** difficult ** **** ****."
- "*****. **** *******. *** sales *******. ******** ********."
- "***** ***** *** **** down **** *** *** good ****** ***** **** with ****** ** ******."
- "*****, *** *********** ** us ** * ***."
- "***** ***** *** ****. Services *** ******* ********. Nearly *** ******** ** user ********* *************, **** to ******* ***********."
- "******* **** ****** (*****). Hideous, ********** *********."
- "***** - **** ** get ********** **** *** train ********* **. **** they *** *******, ** seems ** **** **, but ******* ***** ** a ****."
Honeywell ******
******* ******** ******** ****** platforms, ********* ******** ******** and ******* ********** *** all ** ****. ********* access ******** **** '****' distribution (********* ****** *******) *** '******' ******-**** brands (********* ***-***** *******), *** ********** ***** either *** **** **** clearly *****.
** ***** ** *********, Honeywell *** **** * widespread ************ *** ********* channel *** ***** *****, and *** ******** * sizable ********* **** *** either. *******, ** *** negative ****, ********* ***** to **** *** ******* to **** ***** **** product ***********, **** *******, and ******:
- "********* ******/******** ********. ********* amalgam ** ********/********."
- "********* ********. **'* *** too ********* *** ******* for **** ****** ** does ****. **** ********* video, ********."
- "*** ***** ****** ******* system ** **** ***** with ** ********* ******. The **** ********* ***** very *****, *** ** lacks *** ******** ******** and **** ************ **** we ****** (********* ****** limitations ** ****** ****** like ******* ** ********* in ******** ******* **** each **** ** *** clocks ** *** ****** control ***** ******** *** off)."
- "******, ****, ****** *********, system *** ** ****** out **** ** *** to ******* **** ** the ******** ********** ******* disappears."
- "*********. *** **** ********* is ********** *** *** user ********."
- "********* ******."
- "********* - *** **** talk *** ** ******. treat ******* **** **** don't **** **** *** support ** **** ****."
- "********* ****** - *** based ***** ****** ********* compared ** ***** ************* integrated *** ***** ******."
- "********* ***-***. ********** *********. Not **** ********. ******* features ** * **** fledged ********** ********."
No '*****' *****
* ******* ******** ** integrators *** ** ***** access **********. *** **** installers, ****** *********** *** limited ** *** ** two ******, *** *********** ****** ************* *********** *** ************* ********* * ******* ********** may ****** ******** ***** brands ** * ****** job, ****** ******* ** generally ******* ** **** one ** *** ****** vetted *********:
- "*/*. ******* ******** ****** us ** ******** ******. All **** ********."
- "*********** **** *** ***** with ***."
- "****, ******* ** ****** use ***** ****** ******* management ****** ********"
- "** **** *** *********** any **** ** ***** say *** ********."
- "** ***** ******** ******** so ** *** ******** we **** ***."
- "**** *** ********. ***** support ** ** **, but **** *** ****"
- "** **** ******* *** system ******* ** ***'* really ****** ****. (*** Access)"
- "****. * **** **** used **** *** ******* and **** *** ***** good"
- "**** ** **** ** answer. *** ** *** systems ** **** **** decent ********."
Many ************ ********
* ******* ******** ** integrators ********* ***** ****** that ******** ************* ***, but ** **** ******* criticisms. ***** ** ***** brands **** ***** **** than *** ** ***** times, **** ***** *********** better *****, ***********, ** marketed *****. ***** '******' included:
- "******* - *** ***********, only ******** **, ** web ** *** (** - ********* *** ****** but ** ******** *** you ***** **** * PC ******)"
- "****, ***** ************ ******* and ****** ** *** enterprise ***********, *** *** some ******* ******. ******** bugs, ***** ******* *** even ********* ********** **** made ** ********* ** remain ********* ** *** solution."
- "******** *****. ***** *** tech ******* ** ********. We *** * *** fallout **** **** *** to *** ********* ** our ***."
- "********. **** **** ****** improvised *** ****** ******* software ***** ***** *********** of *** *****."
- "**. ** ****** ** up ** * **** because ** *** **** wanted ** ** *** then **** *** **** decided ** **** ***** S2 *********** *** ** bid. ***** ***** *** four ********* ********** *********** that ** ** ** our *****, **** ***** up ***** **** "*********" than **, **** ****** we *** **** ********** them *** ** ******."
- "********. **'* **** ********* interface ** **** ****. Support ** ******* ** they *** * ******* operation."
- "******* *********. ** ** not **** ******** *** it's *** ********* ******** ActiveX ******* ***** **** many **** ***********. ** relies ** .*** ********* and ********* **** ****** when * .*** ***** is *******."
- "**** *******. **** *******. Not * **** ****** system."
- "********* *** *** ******* customer *******."
- "******** *******. ** ******, everything ******* ** *** server. ** *** ******* is ****, ** *** all *** *****. *** very ********."
- "******. ***** ******* *** me **** **** *** customers. **** **** * month *** **** * Net2 ******* ******* *** Paxton-Ievo *********** **********. *** proposed *** ** ****** was '***** **** ******* with * *** ***** databse'"
Access '*********' ****
*******, ** **** ******* our ********* '******** ******' results, ***** ** ***** the **** ****** ****: "What ** **** ******** access ******* ********** ********/******? Why?"
Geographic ********** - ***** *******
** **** ******, ~**% of *********** **** **** North *******, ** *** results *** ******* ****** to *** ***** ******** market. ** *** *** outside **** ******, * different *** ** ****** may **** * ****** regional ********, *** **** that ** ****.
Comments (36)
Vasiles Kiosses
I am amazed to see this type of results, but then again I am an end user so do not see all the struggles between VARs and Vendor. I was privileged to data presented by IHS Technology that shows UTC is on top for Hardware and Software revenue. So are integrators simply just complaining about the way they are treated, the market results seem to show that the products are being sold nonetheless.
Create New Topic
Michael Miller
Help me understand why anyone installs Honeywell access or video. I have never heard any positive comments from current customers. It is the "name recognition" or locking in customers that is most attractive for dealers?
Create New Topic
Undisclosed Integrator #3
We are a Lenel, Avigilon, RS2, DSX, and Honeywell dealer. I want to echo the comments above about RS2 and their support. Awesome guys over there from sales to the tech support to the training level and they are very responsive. They have Lenel and Prowatch migration packages that makes switching pretty easy. Their product is also pretty solid and has been our go to for Mercury migrations for small to larger customers who are coming off of Lenel/Honeywell.
Avigilon would be a good solution end to end if they didn't price gouge dealers on merc boards and like the others said would upgrade their product beyond Red Cloud v1.1.
Create New Topic
Jonathan Lawry
10/20/16 12:26pm
[Disclosure: I was an original Honeywell Pro-Watch developer, and also wrote Mercury firmware for a while]
It is not all that surprising that the large players would have negative rankings. An industry heavyweight once told me:
"Access Control is, at its best, invisible. At its worst, an annoyance. It is very difficult to get above zero in this business."
Hence it is no surprise that any company in this business with some market success is going to be disliked. It's just a function of the numbers.
That said, there are players in the industry that do a remarkable job in a tough environment.
Create New Topic
Michael Miller
From what you have seen which manufacturer offers the best pricing on Mercury boards?
Create New Topic
Undisclosed Manufacturer #4
Poor support seems to be a constant theme, with the complexity of access control I'm not surprised. We struggle with this constantly as I'm sure other manufacturers do, finding good support staff that can range from understanding how to support hardware they may have never seen configured in some unique way, to IIS installation issues all while delivering a good customer experience is not easy.
Cloud offerings will help this because it removes software installation and setup from the equation and puts the manufacturer in a position where they can easily gain access to troubleshoot and fix an issue.
Create New Topic
Richard Lavin
IPVMU Certified | 10/20/16 05:49pm
Correct me if I'm wrong but this one seems like it's not a compliant against S2 but is rather a complaint against the end user that pushed them to pick it up as a line but then went with another company for the maintenance contract. The complaint says nothing about the quality of S2's equipment, software or support. Maybe the complaint is that S2's sales channel is not limited enough?
(I'm a consultant, not an integrator, so my company does not sell any equipment)
Create New Topic
Max Scott
I had a very difficult time working with WINPAK. The tech support was very helpful and thorough, but I must admit that I'd be pretty helpless if it wasn't for six hours on that phone.
It works well, but it's just a pain to upgrade (To add one board, I had to upgrade from 2.0 to 4.0) The communication interface on some of the boards is also very dated...
I'm sure I'm one of very few millenials who's had to work with the technological marvels that are rs-485 and rs-232.
Create New Topic
Josh Bensadon
In my years working with WinPak, I have found two serious bugs. I brought them to Honeywell's attention and they did not take my reports seriously. One bug, I had to fix myself after 40 hours of reverse engineering their firmware. The other bug still exists and I've seen many reports of it through "Loss of History Data". You cannot rely on this product to record card transactions, they can and have gotten lost along the way. Should I say, Something (not so) funny happened on the way to the hard drive.
Josh Bensadon,
Toronto
Create New Topic