Barriers Of Replacing Access Control Systems Statistics

•Published Dec 29, 2023 13:03 PM

Access control systems are known for the same systems being used for decades, but what do integrators say is the biggest barrier to replacing them, and are newer trends such as cloud or mobile impacting this?

IPVM Image

130+ integrators responded to:

Barriers: What are the biggest barriers to changing / replacing access control systems?

In this report, we examine their responses and highlight the key themes and concerns.

For more, see Replacing / Switching Access Control Systems Guide

*******

****** **** ** *********** ***** "*****" as *** ******* ******* ** ******** / ********* ****** ******* *******. *******, many ******* *** ************** ****** "****," including ***** **** / ****, ******** costs, ********* ********** / ****** *********, and ****, ** **** *********** ****** in ***** ********* ****** ***** ** the ******.

Key ******

*** **** *** ****** / ******** were ** *******, *** ******** ******** are ****** ***** ** *** ******:

**** / ***** / *******
********* ** **** - ***********, *********, etc.
********** ********
****** **** ******* / ******
******* ****** ******* - "** ** Ain't *****, ***'* *** **"
*********** *******
*********** ****** / ******** ******** / Training
******** ************

****: **** ** *** ***** **** we **** **** **** ******, ** we ****** ******* ** *** **** is ******** ** ******** ** **** time, *** ** **** ** ******** to *** **** ****** ** ***** how **** ******* **** ****.

Cost / ***** / *******

*** ******* ******* *** ****. ***** some *********** ************ ********* *** **** factor ** ***** "****" ******** (********, licensing, ***), **** *** *** *********:

"*** *******, **** ***** ** ** the ******* ******."
"**** ** ******* ********* *** ** readers."
"**** ** *** *********."
"********* **** ** *****-*****."
"*** ****, ******* *****."
"****. *** **** *** **** ***** very **** ** * *** ** customers **** *** **** *** ** a **** ****** ******** ** *** wall."
"**** ******* *** ******** ** ****** PACS ******* ** *** ***** ********** with ***-*** ********."
"*** ******** *********** ***** *** ** high."
"*** **** ** ********* *** ****** is *** *******."
"*** **** *** ****** *** *** customer ** ******* ****** *****."
"**** ** ******** *** ******* ******* to ********* ****** ******* *******."
"**** - ****** **** - ********* its *** ****** ******* ******** ****** - *** ** *** **** ** that **** ********* ** *********** **** replacing."
"**** ** ********* ******."
"**** ** *** ******* # * concern."
"**** ** *** *******."
"**** ** *** ********."
"*** ******* ******* ** ****."
"**** ** *** ******* *******."
"***** ***** **** ** *** ******* barrier."
"***** ** ********** **** ** *** biggest ******* ** ********* *** ****** control ******."
"*** ******* ******** *** **** ***** and ********."
"*** **** *** ****** ** ****** the **************."
"**** / ***** **** *** ******** staff / *********."
"****- **** ****** ***** *** * large **********."
"**** ******** ** * *** *** replace ********."
"********** ****."
"****."
"***** ****, ****."
"**** *** *********."
"*****."
"**** *** ******."
"**** *** ****."
"******* ****."
"*** ********* **** ** ********, **** cost. *** ****** **** **** ** the **** **** *** * **** time."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"****."
"**** ***** ** ***."
"*****."
"$$."
"*****."

******* *********** *********** ******** ****** ********, with *** ********* *** **** ******* projects **** ******** ****** ***** ** alleviate **** *********:

"**** - *********** ******* ** ****** require * ****** ******. ** **** with *** ********* ** ****** ******* or ******* *** ******* **** *** course ** ******** ****** ***** ** alleviate **** *****."
"*** ********* ****** ** ****** *******."
"*******."
"********* ******."
"******."
"******."
"****** ********** ** ***** *****."

***** ** ***'* *** *** ***** declining, *** **** ********* ** ** mobile (*.*., ***** / ****** ******) and ***** *******, *** ***** ***** will ** **, *** *********** *** leverage / ******* **** "*****" ** their *********, ****** ** ****** ** switch.

Migration ** **** / *********

*** ****** ******* ** ***** ******* was *** ********** ** *********, ********* of ****, *** ********* **** ******** platforms / *********** ** *** ****, which ** **** ***** ******** **** steps:

"********/********* ** ******** **** **** ** users *** **** ****** ***** ** high ** *** *** ***** ******** as ****. ****** ***** ** **-****** the *****."
"*** **** ** *********** ** *** pre-existing ***** *** ****/***** ******* ** use ** **** *** ****** ** save *****."
"*** *** *** ******* ** ** the **** ** ********* *********** ***/** migrating ***** ******** ******* ***** ******* typically **** * ***** ****** ** credentials ** *********** *** **** ** access ** ***** **** ***** ** 24/7 ** ** ****** ******** ***** operating ***** *** ****** ** **** with."
"********* *********** ** ********. ******** **** such ** ****** ******, ******* ***** numbers."
"*** ******* ******* ** ********* ** access ******* ****** ** *** ********. We ********* ******** ** ******* ** older ********."
"****** ** **** **** **** ** users."
"************ **** * **************** [********* **** and ***************]."
"*** ***********."
"****** ********** **** ** **-***** ***********."
"*** **** ** *********/********** * ****** is * *********."
"********* *** **** ****** ********."
"*** ********* ** *** ******** **** into * *** ******."
" ** *** ******** *** * large ****** ** *********** ***** **** might **** ** ******* ***** **** technology."
"******** **** ******** ***** **** ****** is *** ** *** ****** ****** to ****** *** ****** **** *** systems. **** ****** ********* ** * new **** ********** **** ********* ********* of ***********/** ****** ** ****** ***********."
"*********."
"**** ******** ******* ** ***** * nightmare."
"******* **** *** **** ** **** credential/access ***** **********."
"******** ********* / **********."
"****** ** ******** *********** / *********."
"** ******* *** *** ******** **** re-write *** *********** ***."

Minimizing ********

**** *********** ********* *********** ******* ****** operations ** ********** *** ******** ****** replacing ** ******** ****** ** * main ******* ** ******** / ********* a ******:

"*********** ************* ***** *********."
"** ******* **** **** *** ******** installation."
"**** ** ******** ******** ****** ********** process."
"******* ** ****** **** **** ** possible *** ****."
"** ** ***** *** ******** ** perform * ********* *** ** **** since *** ****** ****** ******** * complete ****** ******. ** ***** ** be **** *********, ** ****, ****, or ******, ******* **** ******* ** parallel **** *** *** ********** ***********. This ******* ******** * *** ** time *** ********."
"*** **** ** *** ************ ** taking * ******** *** ** ******* while *** ****** ** ********."
"**** **** ** *** ******."
"**** **** ** ********."
"********."
"********."
"********** ** ****."

Cabling / ******

**** *********** ********* ******* / ****** as * *** ******* *** *********, and ******* ********* **** ***** **********, ensuring ************** ** ******** *******, *** more ** *** ********:

"****** ** **** ******** ****** *** not **** *** **** ****** ************. If *** ****** ** *** **** really *** **** ******. ** ******* replace ******* ** **** **** **** we **** **** ** *******."
"********* ** *** ****** ** *** existing **** *** ****** ********** *** be *******. ***** ** ** ****** just ** *** *** **** ** the ****** *** **** ** ***** before *** ********* ***** *** ******* available."
"**** ** *** ******** ****** ** usable *** *** *** ******."
"****** ***** ***** ******* ** ** labeling ** ***."
"******* *** ***** *****."
"*******."
"***** ** ****** *** ******* **** legacy *******."
"************* *****."
"******** ******* *******."
"******* ******** ***** ****."
"**** **********."
"******** *******."
"******* ******* *** ** ** *******."
"***** *********** ***** **** *** **** time ** **** *** *******."
"****** ** **** *****."
"****** ** ******* *** ****** ** place ** *** *** ****, ********* the ***** *** *** ***** ** not ******* ***."
"********* ****/******* ********. **** ****** ******* can ** **** ***** ** **-****, the ******** *** ***** ***** *** be ***********."

Current ****** ******* - "** ** ***'* *****, ***'* *** **"

******* *********** ***** *** ************ ** explaining / ********** * *********** ****** if *** ******* ****** ** ***** functioning, **** ******* ******, "** ** ain't *****, ***'* *** **" *** more:

"** ** ***'* *****, ***'* *** it."
"****** ********* ** **** ** *** change."
"**** ** ******* *** ******* ** moving ** *** ******* ****** ** still *******."
"********* ** *** **** ** *** be **** *********** ** **** *** a ******, ********** ** ** ** still "**"."
"***** ****** ** ******** ********** **** function ******** *** ******* ***** ** 'FIX' ********* **** ***'* ****** ******** moving ****** *** ** ****** ***** items **** ********** *** ******* ******* of *** ** ****** ***** **** aren't ******** *** *** *********."
"*** ******** ******* ***** **** ** it ***'* ***** *** *** **."
"*** ********* **** ** *** **** and **** ** ******* ****** ***** are ******** ***** ** *** ******* system."

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

"********* *********** ** ****** ***** *********."
"******** *****'* **** ** ******* ****'* working."
"******* ******* ** ************* * ****** justification *** ******. **** ******'* ** not *** *** ******* ******* ** blue ***** ******* ** * ********** benefit."

Proprietary ******* / ************* ********

**** *********** ****** ******** ***** / comments ** *** ******** **** *********** systems ****** *** ********* *** ************* of ********, ********, ***********, *** ****:

"*********** ******* *** **** ** ********* but *** **********."
"** *** ****** ** ***********, *** capex ***** ** **** ** *******."
"*** ******* ******* ** ********* **** of ****** ** ******* *** **** end ***** ** *** ****** ** the ******* ****** *** ***********."
"*************. **** ******* ***** ******* *** more **** *** ** ** ******** the **** *** ***** ** ****."
"**** ** *** ******** *** ******** compatibilities ****** *** * **** *** and ******* **** ****** ******* ******* funding *** *******."
"****** **** ********** ** **********."
"************* **** ******** ******* (******** *****)."
"************* **** ****** *** ******** ******* (if **** **** ** ***** **** strikes ** *******)."
"*********** *********** ***** **** ** *****."
"********** *************."
"********** *************."
"** **** ***** *** **** *** hardware, ******** *** ******* ******* ********* to ******* * *** ********** ** new ************."
"**** ******** (******) ** *********** ********."
"** *** * ******** ****** **** electric ******* *** ******* **** *** usually ****** ******. *** ****** ****** start **** *** *** ****** ** get ******* * ****** **** *** wireless ** **** ***-******** *****. **** begins ** ** * ******* ** some ** ***** *****."

************, *** *********** ****** ********* ** installing **** ********, ***** ******* **** (but *** ***) ************ ******** ** replacing * ******, ** **** **** still **** ** ****** *** ************* of *** ******** ** *** ********** in *** ****** **** **** ** use:

"*** ***** *** **** ****** ************ less ********* ** ********** **** ******** that *** ******* ******** ******** *********."
"** *** *** ******** * ****** board ******, ** ** ****** *************** (lenel ** ***, ** ** *******. For ***** *******, ** ** *** too ******* **** ***** ** *** just ****** *** **** *** *** reuse *** ******** ********."

Familiarity ****** / ******** ******** / ********

**** *********** ********* *** *********** ****** customers **** **** ***** ******* ******* is * *******. *********** ***** **** customers *** ************ ***** ******* *** that ********* ******* *** ******* ********* and ******* ********** ******** *** *** end-user:

"*** ******* ******* ** **** ** changing ****** ******* ******* ** ****** are ******** **** *** *** **** they ********* **** *** **** **** don't **** ** ***** * *** system."
"******* **** ******* ***** ***** ********** to *** ******** (** ***********) ** their ****, ******** ***** **** ***** disrupt ***** ********."
"******** ********* *** **********."
"******** *** *** ****** *** ****."
"***********/******** ******** *** *** ***** ** credentials, **** ********* *** ***-**** *******."
"********** ** ***** * *** ****** from *** *****."
"* **** ***** ** ***** ** be *** *** **** ******** **** is *** ******* ******* ** ********* access ******* *******. **** **** ** find **** ** ***** *** ** operate *** ******, ** **** ** time ** ***** ***** *****. ** least **** ** *** ****** **** the ******** ******* ****** ** **** to ** ******."
"****** *** *** ***** ** *** want ** ****** **** **** **** been *****."
"******** ** ***** *** *********, ********* changes ** ******* *.*. **** *** replace ***** ** **********."
"****** ******** *** ******."
"********** *** ** *** **."
"******** ******** *** ******."
"*** *****. *** ***** ************** ******* requires * ******** *******, **** ********* levels ** **** ***********. ********** ********* users ** ***** *** *******."
"*********** ****** ******** ***** ** ***/********* software."

Existing ************

******* *********** ***** ******** ************ ** a ******* ** *********, ** ********* systems *** ****** ** ********* ******* - ** *****, ****** ***********. *****, in ****, ***** ******* ********* *** create *** / ********** ********** *** a ***********:

"*** **** ******** ** *** ***** deep *********** **** ****& **********, *** also *** *** **** ***** **** implementing * *** ***."
"******** ************ **** ***** ******* (***, Lifts, *********, *** *****, ***) **** can't ** ********** **** *** *******."
"*** ***** ************ ** ***** ***** that **** ** ** **-*********."
"******** ************."
"*** *** ******** *** ****** ******* systems *** *********** **** ****** *******, taking ********* ** ******** ** *** technologies, *** ********** ******* ********** ***************."

Comments