LenelS2 Favorability Statistics 2023

Published Jul 21, 2023 13:09 PM

While the Lenel brand was repeatedly deemed one of the worst access control manufacturers in 2020 and 2022's integrator results, its sister S2 consistently received positive feedback. How do integrators view the company 5 years after the two companies merged?

IPVM Image

For context, LenelS2's owner Carrier is now seeking a sale of its fire and security division including LenelS2. This is happening 3 years after Carrier was spun out from UTC.

This report examines statistics and commentary from 170+ security integrators on LenelS2's positioning, pros, and cons.

Net ******** ************ ******

******* ******** +**% *** ******** ************ results ***** *********** **** **** ****** a ******** ***** *** *******. *******, the ******** ** *********** *** ***** "positive" ***** ******* *** ******* **** do *** **** ***** ******* ** areas **** ***** **** ** *** improvements.

IPVM Image

Significant *********** ** *** **** * *****

*******'* *** ************ ******** ** ** percentage ****** ** *** **** *** years.

***** ***** ***, ** **** * net **% ** ****, *********** *** been * *****, ****-**% ** ****(***** ****** ** ****** **** **) **-*% ** ****. ************, ***** *** ***** "***'* Know" ********* ** ** ********** ****** in **** ******** ** ****.

IPVM Image

More ******** *** **** ***** ******* *** **

*******'* *** +**% *** ************ ****** the ** *** +**% ******* *** US. * ****** ********** ** *********** from ******* *** ** (**%) ***** "Don't ****" *** ******* ******** ** their ** ************ (**%).

IPVM Image

******* ** ***** ** *** ****** States **** **** *** ******** ***** and *** ******** ** ***** **-******* companies.

Key ******

********** ********* **** **** ***** *** themes:

  • ******** ** ********
  • ********* ** ********
  • ********* ** *******'* ******** ********* *** Technology ********
  • ****** ***** ******
  • ******
  • ******** ********** **** ******* *** ****** Systems
  • ********* ** *******

Positives ** ********

**** *********** ************ ******* ** *** products ***** **** ******** *** **** weaknesses, **** ** ***** *******, *** further ****** ***** **** *** *******:

  • "***** ******* **** *** **** **** into *** '********** *** *********,' ** at ***** **** *** ** ***** in ********** **** **** **'* *******. And *** *** *** *** **** nice. *** **** **** ** *** standard, ******** ********** (***** *** *** web ***, ******** (** ** ***** it **** ** **) *** ******* queueing). * ***'* ***/*****'* **** *** other ******* ********."
  • "** * *******, **** *** ***** be ********* ** **** ****. ***, when ** ***** ** * ******* product, **** **** ***. *** ******* set ***** *******. **** **** ****** integration **** *********. ** ****** ** possible ** **** ****** *** ****** in ****** ********* - **** ** sending ***** ******** ****** **** ********* to *******, *** **** ** *** possible."
  • "* ***** *********** ******* *** ****** systems. **** **** ***** ***** *** seem ** ** ****. ********* **** the ****** ********* *** *** ****** nature ** *******. ********* **** ****** can ** ******."
  • "**** **** ** ********** **** *********. Variety ** *********** *** */* ******* Complexity ** ********* *********."
  • "* **** *** *** *** ****** wire ** *** *** ***** **** sensors ** ********* ***** ******. *********** can ** * ********* ** ***** but **** *** ********** *** ****** it ***'* ***."
  • "**** **********, *** ****** *** **** system. **** **** * **** ********** team *** *** **** *** **** humble."
  • "**** ** *** * ***** **** is ******** ** *** ** - in *** ** **** *** ******* Fire & ********. *** ***** **** name, **** *** **** **** ********* suppliers."
  • "******** ****** & **** **** ** says - *** ********** ****** ****** in *** **."
  • "******** ******** *** ********. * ****** outdated ********* *** *** ******* ** a **** ** *** ***** *********."
  • "******* ***** ********, ****** **** ****. They **** * **** **** ** go ******, *** * ***** *****."
  • "**** *** ********** ********* ****-** ********* to **** ** *** *****'* ************."
  • "****** ******** ******* *****, **** ********* support. ************ *** *****."
  • "***** **** * ***** *** *** a **** **** ********* *** *** end ****."
  • "** *** ******* **********. * **** it ******* ** ** ****-********."
  • "** **** **** *******, ****** **** previous ******* ****** *******."
  • "*********** **** ****** *** ******* ** offerings."
  • "**** ******** *******-****."
  • "***** ***** ***** ****."
  • "******** *** *****."
  • "***** *******."

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

  • "********** ** ***** ********. ** ******* regular ******* ** ************* *** *********. One ** *** *** ********* * deal **** **** ****** ******** ** us. *** ***** ******** ** ****** along *** **'** ******** ** **** at **** *** **** ********* ***** it ***** ** * **** ***."
  • "**** *********** **** ********* *** * "one **** ** *****" ********* *** the ****. ***** ********, *** *****, but ** **** **** ** *** long ***, *** ***'* *** ***** for ****** *** *********."
  • "* *** **** ******** **** ***** on ***********. *** ***** **** ** like **. **** *********** ************."
  • "******* *** *** ********* ** *********. Open ******** *** ************."
  • "****** *************, ********. **** *********** **** Milestone."
  • "********* *********** *******."
  • "**** ************."

******* *********** **** ******* ** **** to **** ****:

  • "** ***'* **** ** *** *********** side ** *****, *** **'** ****** a *** **** *** ********, *** our ***** *** ****** ** ** pretty ****** *** ***** ** **** to **** ****."
  • "*****, ****** **. *** *******-******* ******** makes ******/************ **** ****."
  • "**** ** *** *** ************* ** S2 ** **** ********."
  • "**** ** ********* *** **********."

*** *********** ************ ** ************ *** not *****:

  • "******** ** *** *********** ** ****** control. *** * **** ******** ******. For *****, ** *** * *** and ******* ** ** *** ***** system. *** ****** *** ******* *** had ****** ** ************ **** ****."
  • "** ** * ***** ****** ****** offering. ***** ***'* ****** **** ************* progress."

**** ********* *******'* ******* *** **** with **********-***** *******:

  • "** **** ****** **** *** ** these ******* *** **'* * ******* enterprise-level ****** ******* ******."
  • "**** ****-******* ********, **** *******, ***** install ****, *** *** ******."
  • "**** ** *** ** *** **** systems *** *****-***** ***********."
  • "*** **-** *** *** ********** ********."
  • "**** ********** ********."

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

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

  • "******* ** **********. *** ********* ** out ** *******. *** ****** ** capable *** *** * ***** **** of ******** *** ***************, *** *** user ********* ** ***** *** *******. This ** **** *********** *** ***** enterprise-level *******, *** ***** *** ****** alternatives **** *** ******** ***** *******."
  • "******* *******. ******** ** **** ********* products, **’* ****** **** ********* ** set ** *** ********. ************ ********** features ******* ******** ********* ********* (>$**** for *** *********?!) *** ***’* ** easy ** **** ****** **."
  • "* ***'* ****** *** ******** **** combined ***** *** ****** ** ****** but *** *** *****. ***** ********* are ********* ****** *** ***** ** not ** ** ********** ******** *** the **** ** ******** **** ***** it **** *** ** ** ******* another ******** ***** ***** **** ****."
  • "***** **** ** *** ****** ***** replacement *** **** * **** **** in *** **** **** *** **** replacing * *******."
  • "********* ******* **** *** ******** *********** who **** **** *********** ** *** over * ******."
  • "*** ** ********* ** ***** ******* like (****/***) ********, ***, ********."
  • "** ******** ***** ********* ***********."
  • "********* *** ****-********."
  • "******** ** **** *******."

Negatives ** *******'* ******** ********* *** ********** ********

******* *********** **** ******** ******** ***** the *******'* ********* *** ********** ********:

  • "*** ***** ************ (**** ********* ********) appears ** **** * **********-**** *** about ***** ******* *** ******* ******** in *** ******. ** *** ***** a ****** *** **** *** ** sell * ****** ******** ******.........*** *** lack ** ******. ** ****** *** for * ****** ******* (**** **** launched *** ** ***** ******* *** the *** ** ******). *** *** their ****** ********?"
  • "******* ******* ******* **** ***** ** there ** * ******* ****** ** patience ******** **** ******* **** ****. We **** *** *** **** **** large *******, ** ** *** *** small/medium ******** ********. *** *** ***** tracking *** ** ***********. ** ********* only **** *** ******* ********* ** I ***'* ***** ***** **."
  • "***** ********** ** *******. *** *** OnGuard *** ****** ******* ** **** cherry-picked ******* ********/** **** **. *** upcoming **** **** ******* ** *** catastrophic, *** **'* ********* ********** ** they **** ****** **** ******** ***** in *** *******. **** **** ** detrimental ** **********/*&*."
  • "*** ******** **** ********* ** *******, although ** ***** **** **** *** never **** ***** *** ***** "*******" platform ******* ***** ******** *** *****."
  • "********* ****** ** ********** *** ****** steps ** **** ******* ** *****, mobile, *** *** ** ** **** scrubbing."
  • "*** ** **** ****** *** *** legacy ******* ****-**-***** ** ******* **** from ****** ********. *** *********."
  • "*** ******* ******** *** **** ******* with **** **** ****."

**** ***** ******** *** ******* *** said **** ******* ** **** **** from ******* ** ******* ****:

  • "** **** **** * ***** ***** for *** ** ***** * **** been **** *** *******. * **** hundreds ** ********* ** *****. **** have **** *** *** ******. ********* is ********* ********** *****, *** **** to ***** **** **** **** *** software *******, ******* ******* **** ** need **, *** **** *********, **** very ****. **** *** **** *** main ******* *** ***** ** *** going ** ** ****** ** ******* in *** ******."
  • "* **** * *** ** ********** with ***** ***** *** ***** ***. It *** ****** **** * ***** access ******* ******, *** ***** *** some ************ **** ***** ******* **** that ***** **** ***."

Supply ***** ******

**** *********** ***** **** ******* *** supply ***** ******:

  • "***** *** ** *** ******* ** access *******. **** **** **** ***** fix ***** ****** ***** ******. **** also **** ** ** ********** **** tech ******* *** ****'* ** ** top ** ****** ** **** ** their ***********."
  • "***** ***** ******* **** **** ************* and **** ** *******. **** **** support *** *** **** **** *** parts *** **** **** * ******** for *** **** ****."
  • "** **** *** ** ******** *** OnGuard. ***** **** ************ ****** ** do *** **** *** ****** **** their ********."
  • "****** ********* **** **** ***** *** a ***** *** ***** ** ** getting ******."
  • "***** **** ***** **** ******* **** down ** ** *** ** **** Galaxy *** **** **** ******."
  • "* **** ***** **. * ***'* like *** ********* **** ***** ** products."
  • "***** ****, *** ****** ***** ****** have ****** **** ******** **** *********."
  • "******** **** ********..."

******

**** *********** ***** ******** *** ******* but **** ** ** *********:

  • "**'* ****** *** * ******* ***-********** user. *** * *** ** *** corporate ********* ** ******* *** *** pricing ** ******* *** **** *** some ********* *** ***'* **** ** have ****-*** ******** ** ***********. **** you *** *** ****** **** ******, it ****** ** *** **** ********* compared ** ***** ******* **** ***. Good ****** **** ** *** **** or *** *********** **** ****** * number ***** ******* ****** **** ***** profitable *** ********* * **** ******* long ****."
  • "** ******* **** ** ***** *******. Overall **'* * **** *******, ********** in ***** **** ********, *.* *** 8.2. ******* ** ********* ***** ** issue *** ********** ******* ** ***** clients *** ********. **** **** *** web ******* ** ** ******** ** needed *** **** ******** *** *** pricing ** ***** **** ******* ****** is *** **** ***** ** *** thick ****** **** * *** ***** features."
  • "*** ***** ** **** ****** **** I *******. * **** ******** **** orders **** **** ** **** **** to ******."
  • "***** ** *** *** **** ******** and ************ ** *** ******. *** only ******** ** ***** **** *****."
  • "**** ******* ** **** ****** ** area. ***** ********* ** ******* ***** to *******."
  • "***** ** * ***** ***, *** pricy **** *********** *****-***** ********."
  • "**** ********, *** **** *******, *** it ** ***** *** ********* *** the ******** ** *******."
  • "***** ********* *** ********* ********, *** can ** ******."
  • "******** *** *** ********* **** *** SSA's."
  • "********** *** ***********."
  • "**** ******, *********."

**** *********** ***** ******** *** ******* because ** *** *****:

  • "********** ******** ** ***** ******* ********* available ** *********."
  • "**** *********** ******** *** ********, *** can ** ****** ** *********."
  • "**********. ******** **** *********. ********** ** work ****."
  • "****** *********** *** *********. **** ******* though."
  • "********** *** ***********."
  • "*********...*** *********."
  • "*** ****-******."
  • "*********."

******** ********** **** ******* *** ****** System

**** *********** **** **** *** ******** experiences **** *******'* **** *** ****** system:

  • "** **** ********* ** *** ***** and ** **** *** ** ***** top *********** *** ***** *** *********** by *****, ***** ******* *** **** horrible. **** **** *** ****** ***** issues (**** ****** **** ***** **** their ***********) *** ***** ******** ** the ********* *** **** *********. *** regional ***** ******* *** **** ********* to *** ** ******** ******** **** (if ** ***) *** ** ** now **** *** *** ******* ******* is **** ** ***. ** ** didn't **** * ***** **** ** installed ******* * ***** ***** *** them *****."
  • "***** ** ****** **** *** ** working ** * ***** *******. *** the ****** *** *** *****, *** have ** **** ** ** ******* to *** ** ** *** **** and **** ******* ** **** ***'* provide *** ****-***** ******. ******* **** on *** ********* ** ****** ***********. They **** ** ******* ***** *********** a *** ** ****** **** ******* the ******** *** ******* *** ***** without ***** ***********. *** ******* ***** of *** ***** **** *** ******** is ** **** ***** ********. ******* with ***** ****** **** ** **** more *********. * ***** **** *** work **** **** *** **** ** email ** ***********. ******** **** **** company ******** * ****+ *** ******* on **********. ** *** ****** *** do **** **** **% ** * need ****. *** *** ***** ***** from *** ****** **** ******* *** involvement *** ****** *** ********** ** on *********, **** ****** *****."
  • "****** **** ***** ** **** **** large **********-***** ********. **** * ***** software ******? ****** **** **** $**,***.**. I *** *** *** ****'** ****** market *****. **** ***** ******* **** their ******, **** ******* ******* ** take ** ****. **** ***'* **** entertain ******** ** ** ****** * dealer."
  • "** ****** ** ******** **** ****. Their **** ******* ** ********. ***'* ever *** * **** ** ****. We ****** **** **** ******* **** and **** ******* ** ** * distributor. * *** ** **** *** system ** **** ** ** ***** get * **** ** ****."
  • "******* *** ***** *** ********* ** the ***** *** *** ** *** 100 ******** ** *******. *** ***** team ***** ***** ** ********** ** provide ******* *** ********* ******* ***** days *** ******* ** ***** ** get **** ** *** ** ****** how ********* *** ***** ** **** the ******** ****. ** **** ******* Lenel/S2 *** ***'* ****."
  • "** *** *** *******; **** **** to **** ** ******** ** ****** new *******, *** *** ******** ** see ** ***** ***** *** ** the ******* ** ********. ********* ***'* right **** ****** *** ******* **** and ***** ***** **** ***** **** Lenel/S2."
  • "** ***'* *** ***** ** ** but ******* **** *** ******** *********, from **** * **** ***** **** their ******* *** ***-***** ** ****** about *** ***** *** ******* ***** being ************ *** ***** **** ********* than *** ***********."
  • "********* ** *** *** ******* ** not * ***** *******. ******* ** partner **** **** *** **** ********* channel ********."
  • " ** ***** ** *** *** new **-******** *** *** ************ ********** the ******* *** ****** *** ***** and ******* *** *** ********** *** market."
  • "***** *** *** ****** *********** *** terrible... ** ********* *** ******** ***** system **** ***** *** ***** ** to ****** *******."
  • "*** * ****** *** **** **** tried ******* ***** *** ******* ** the ****** ** ******* ** ** area **** *** *** ******* ** add *** *** ****."
  • "**** *** *** ***** ***** ***** in *** ******** ******** *** ***** the **** ********* ******."
  • "****** ****** *** *** ***** *** told ** **** **** *** *** looking *** *** ********."
  • "**** (*****) ******* ** ** ***** ago *** *'** *** ** ****** to **** ***** ********* *****."
  • "*** ******** *******, ** *** *** worst. **** ***** ** *** ******** for *** ********* ****** *** *******."
  • "******** ******** *** **, *** ** contacts(customers) **** ***** **** ******** **********. We ** *** ** *****."
  • "*** **** ************ *** ***** *** user * **** ***** **** **** feel **** *** *******."
  • "******* ** *** ********* ******* * real ********* ** ********."
  • "***** ****** *** ********* *** ********* to ***** *******."
  • "******* ************ ** ****** * ******."
  • "***** ** ***** *** ******* ** horrible."
  • "****** *** ***** *** *** *******."
  • "******** *****-***** *******."
  • "******** *******."
  • "** *******."

Positives ** *******

**** ***** *********** **** **** *** good ******* **** *******:

  • "**** * *** *****, **** ** programming ******* *** ********. **** ******* support, ******* *** ****** ** ******* how ** ******* ******** *******. * never ********** **, **** **** ********** helpful."
  • "** **** ********* *** ******* ** LenelS2 *********** ** *** ****. *** customers *** **** ***** **** *******'* products *** *********. *** *********** **** how ** ******* *** ******* ******. Post-installation ******* *** **** ****** ****. We **** ** ******* ************/********** ******* in *** ******."
  • "*** *** *** ** ********** *** tries ** ****** **** ******. *** previous *** *** *** **** *** that *** *** ****** **** *** case **** *****. ****'* *** **** reason * ** *** ********* ******* or ********."
  • "**** ********* ****** *** * **** time. ****** **** **** ***** **** the ******* *** ****** ** ******. Just ******* **** *******, *** **** been *******."
  • "***** *******, **** *****, *** ***** support. **** ******* ** ***** **** some **** *********** ***** *** *** go **** ***** *** ****** ******* a ****** ** ******* ******."
  • "********* ******* **** *** ****** *** long *** ******** *** *** ******; if *** ** *** **** ******** service, **** **** *** ****."
  • "******* ** ******* ****** ********** ******. Responses *** ****** **** **** *******. Almost * ***** ** *********."
  • "**** ***** ** *** ******, **** PRODUCT, ***** ******* ** ******* ******."
  • "**** ******** ******. ****-*****, *** ****** easy ** *** *******."
  • "****** **** ***** **** ******* ********** and ******* ****."
  • "** *** **** **** ***** ************ support. ******* *** *****."
  • "**** ********* ******* ****** *******."
  • "********** ******* *** ****."

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

** ***** ********* **** ** **** **** & Security ********, ** *** *** ******* **** of *******'* *&* ****** (********* *******) has *** ********* ** ************* ******* the ****-**** *********** *** *********** *********** of *** *******.** ******** *******, * ******* ******** can ***** ** * ****** *** innovation ***** ****** **** ********** *****-**** profits.

** *** ****** *******, ******* *** had ***********. ******, *** ********* **** *** ******* ** ******* "more ******* ******** ********** **** **** enable **** ** ******** ***** *** their ********* *** ***********." ***, ******* plans ** **** *** *** ********* $3.6 ******* **** *** ******** ******* business.

*******'* ******** **** *** ***** ***** that *** / ******* ************* ** their ****** *** *** ******* *********** at *** ******* ** ********** *****-**** cash ****. ** ******** ** *******'* executives, *** ********* ** *** ******* organization(UTC/Carrier) **** **** ****** *********** ** LenelS2 *** **** *** ** **** do ** *** ***-****** **** ********, and **** ****** ** ***** *** nuances, ***********, *** *****-****** ** ****** control.

Comments (5)
UE
Undisclosed End User #1
Jul 24, 2023
IPVMU Certified

**** ** *** *** ** *** want ** ********* **** *********? * thought ***** *** ********* **** ***** together.

(1)
JH
John Honovich
Jul 24, 2023
IPVM

***** *** ********* *** *** **** integrated, **** **** * ****** ***** business ***********.

* ***'* **** ****** ***** *****'* VMS ************ ** **** ******** ** which *** ****** ** *****.

(1)
UE
Undisclosed End User #4
Nov 10, 2023

*** *****. **** *** * *****-***** Mercury ***** ******** *** *** **** over *** ***** ** ******. **** also ********* **** ********* *** ****.

UI
Undisclosed Integrator #2
Jul 24, 2023

*** ******* ** ***** **** ***** since **** *** ***** *** **** a **** ** *********.

**** * ******* **** **** ***** the ************ **** ********* * ******** concern *** ****** ***********.

******** * **** ** **** **** could ***** **, * ***** ***** BOSCH ** *** ****** *********** *** much ** *******. ************ *** **** and ******. ****

UI
Undisclosed Integrator #3
Jul 24, 2023

***** **** *** **** *** ******* in *********...