Lifespan Of Access Control System Statistics

IT
IPVM Team
•Published Nov 09, 2023 13:12 PM

How long do customers use an access control system before replacing it? Access control is famous for the same system being used for decades, but how are newer trends, such as cloud and mobile, impacting changing systems?

IPVM Image

130+ integrators responded to:

On average, how many years are access control systems in service before they are replaced? Why?

As well as:

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

This report reveals the results, including reasons for replacing systems, and highlights common themes and concerns.

Plus, we contrast these results to past access control lifespan statistics and to lifespan statistics for video surveillance systems.

Executive *******

** ***** ** *** ******* ******** for ****** ******* *******, **** ********** responses, **** * ********* ** ********* shown *****:

IPVM Image

**** ** **% ***** **** *** average ****** ******* ******** **** **** we**** *** **** ** ****. ** *** ***** ***** *****, in ****, *** ******* ******** *** ~16 *****, ******* *** ** ~** years:

IPVM Image

*******, ***** ************ ********* *** *** shorter ** ******* **** *** ****** of ****** *******. ******** ************, ******* **% ** ******* are ************* *-** *****, **** *-* ***** being *** **** ****** ********. *** the ********** ***** *****:

IPVM Image

Upgrade *******

*** ***** *** ******:

  • *** ********
  • ************/***/*** ***********
  • *** ******* ******** **** *******

Barriers *** ******

***** **** *** ******** *****, **** answers ******* ********* ****/*** *** **** costs ***. ************, *** **** ** cabling (*** *** **** ** ********** new), ********* *********** ** *** *** more ****** *******, *** *** ******* and ********** ** ********** ************ *** training ***** ** *** ********* **** mentioned ** ***********:

'High ****" ***** *** ******* *****

********** ******* ****** ** * "****" often ******** *** ***** ** ******* features *** *** ***** **** ***. An ********** ******* ***** ****:

********* ********* ** *** ********** *** helping **** *** *** *****. ** are **** ********* *** ******* ** obtaining *** ********* ** ****** **** to ******* ** *** ******** ******** base.

******* ********* **** ***** ********* *** grow ***** ** ***********, *** ***** systems *** **** '********** ***** **********':

** *** **** ** *** ******* stay **** *** **** **** *** at ***** **-** *****. **** *********** PACS **** ********** *** ******** *** features **** ***** **** *******. *** parent ********* *** ********* ****** *** wave ** * *******'* ******* *** milking ** *** ***** **** ******* reinvestment ** *&*. *** **** ********* catch * ******'* ********* **** *** features ** **** ********** ***** ***** operations.

******** **** ****** *** ***** ******* may ******* *** *********** ***** ** access ******* ** ************ **** *** end ***** **** ***** ***** ** purely ** ****.

10+ ***** ******, ** ****** ****** ******

**** ********* ********* **** ******** ******* that **** **** ** ******* *** a ****** ** ****, *** ****** the ******* ************* ******, ***** ********* are ** ***** ** ******* ****:

  • "**+ **** **** *******. **** ******** when ***** ** ****** ********* ** system ************ ****** ********."
  • "* ***** *** **+ *****. ** the ****** ***** ***** *** *** customer *** ** ***** ********* ** doesn't **** ***** ** **** ** out."
  • "****** **** *******. *** **** **** we **** *******, ** ********, ** access ******* ****** ** **** *** manufacturer ** ****** ********* **."
  • "******* *** **** *** ***** *** customer ** ******* **. *'** **** systems ** ***** *** **+ *****"
  • "**+ *****. ********* ***'* **** ** replace *** ******* ** **** ** the ****** ** ***** ******* *** meeting ***** *****"
  • "**+ ** **** ****, ***** ** no **** ** *******"
  • "** **** ** *** ****** ****, they ***'* ****** ********, **** ** the ****** ** ******** ** **** with."
  • "**** ** * **** *** ** answer. * ***** ******* ** ** answer.. ****** ***** ** * ******** (cyber) ****** ** ******, ** ***'* see ******* ********* *** **** ********. The **** *** ******* ** *** clients ******* ***** ** ***** *** parts ************."
  • "**** ** * ********* ******** ** answer. ** **** ** ***** *** available *** ** ********* ******** **** its ***** *** *******."
  • "* ****** **** **** ******* **** installed *** **** *** ****** ** change ** ******* *** ** *** budget"
  • "******** *****'* **** ** ******* ****'* working."
  • "**+ *****. ******* ***** ** * full *** *** ******* ****** *** system ****."
  • "** ***** +. **** **** ** be ********, *** ** ** *** an **** ** ******* *** ******** to ******* ***** ********* ******* *****."
  • "** ** **********, *** ******* ******** of ****** ******* ** **+ *****. If ***** ******** ** ****, **** customers ***'* *** *** **** ** replace."
  • "** ***** - ********* ***'* **** to ******* ********* ***** ** ******"
  • "*-**+ *** * *** ** ****** so *** ******* ********* **** ** working"

New ********

*******, ****** ************ ********* **** *** functions *** ******** ***** ******* *** that ***-***** *** *** ******** ***** current ******* ****.

************, ***, *****, ******-******** ***********, *** better ************ **** *********:

  • "**-** **** ** **** ***** **** new ******** **** ****'* ********* ** their ******* ******."
  • "** ** ** ** **-**** ****** there ********* ** * **** **** chance **** ******* **** **** **** to ** ******. ** ** ** an "*****" ****** ******, ** *** finding ****** ******** ******* **** *** interested ** * **** ***** ******** that ***** ******* ****** ****** *******. We *** ********* ** *** **** IT *********** **** ******* *** ****** that **-**** ******* ** ******* *** a ***** ***** ********."
  • "*** **** ****** * *** ******* changing ****** ******* ******* *** ** take ********* ** *** ********."
  • "*-** ********** ** * **** ****** platform."
  • "*-** ***** ** *** **********. **** customers **** **** * ****** ***** of ******** ** *** ******** (**** cloud) ** **** ******* **** **** be ********."
  • "* ** * *****, **** *** pace ** ****** **********, **** *** even ** ******* ** *** ****** years."
  • "** **** ******* ******* ** ******* after * ***** *** ** *** technology, **** ***** ** ******** ********, and **** ******** ************."
  • "***** *-** ***** ****** *** *********** expire ** *** **** **** ******"
  • "**-** ********* ** *********/******* ********** ********"
  • "***** ** ** **. *** ********** or ************ *****"
  • "**-** ***** ********** ************ *** ******* the ******. ****** ************ ****** *** newer *************."
  • "****** *** ******** ***** ** ** need * *** ******* **** ** unavailable, ** **** **** ****** *****."
  • "***** ** *****, ...********* ** * new ****** **** ****** ******** ******* sensible"
  • "** * *** **** ********* ******* to ******* *** ******* ******* ****** 10 ***** ** ***** **************. **** see ***** ********** *** **** *** extra ******** *** ******** ** **."
  • "****** *** ****** *** ** *** the **** ** *** ********* *** about ** ****** *********** ** ****** due ** *** **********."
  • "******* ** *****; * ***** **** is ******* *** ******** ************ *** not **** ** **** *** *********** of *** ********."
  • "*** **** ****** *** ****** ** relocation ** ** **** ********* ** newer **********."

Obsolescence/Old/Now ***********

**** ******** ******, *** ****** **** not ******** ******** **** *** *** with *** ******* ** **** * system *********** ** *** **** ** maintaining **:

  • "**+ ***** ******* *** ** *** of **** *** ** *******"
  • "*** ****, ****** ** *** ****** new ***** ** **** ****'* ****** to ** ***** ***** ********."
  • "**+ ***** ****** ** *** **** a ******* ************ *****."
  • "** *****. ********** *** ** ********, but *** ****** **** ****** **** as **** ** *** ***** ** willing ** ******* *** ******* **."
  • "** ** ** ***** - **** reason ** ************ *** ****** ***'* be ******* - ***** ****** ** to **** ********* ** *** ******** - ***** *** * *** ******* - ****** ******* ** ** *** look ** ****** *** ****."
  • "***** ** ***** **** ******* ******* and *** ******** ****** ******** ** when *** ******** *** ** *** market *** *** ******** ****** ***’* incorporate **."
  • "**-** *****. ********* **** *** **** replaced **** ***** ** * ***** enough ******** ************* **** *** ******** system ** **** **** *** ****** is *** ****** ** ********** ** a ***** ****** ************ ****** *** happened **** ** ************ **** *** existing ********."
  • "**** **** ** ****. ******* ******* is ***, **** ** **"
  • "** ************ ** **********"

Older ******* ******* **** *******

******* *********** ********* **** ***** ******* often **** **** ******* *** ********* replacement ** **** ***********, *** *** higher ****-**-********* *** ***** ******* ****** interest ** ***** *******:

  • "* **** **** ** *** **** or *** ***** *** ** ** access ******* ****** ****** ** ***** having ** ** ***** * *** of *******, *** *********** ** ***** components **** ***** *** **** ******* around *** ** **** ****. "
  • "******* ***** *** ** *** **** of ***** *** ******* ******* ** many ***** *****."
  • "**+, **** *******, ***** ***********."
  • "**-** ***** ****, **** ********** ****** unserviceable."
  • "***** ******* **** **** ***** ***** to ******** *** ********* **** ****."

******* ** ** ******* ***** ***** become ********* ** ******* ** **** technical ******* ***** ****** ** **** current *********, *** ***** **** ****** support ** ** ******* ** * barrier.

Expensive/High **** ** ******

*** **** ** ********* ******* *** the **** ******** ***** ******* ** customer *******, ***** **** ****** *********** beyond ****** *** **** *******:

  • "***** ****, ****."
  • "****" **
  • "****. *** **** *** **** ***** very **** ** * *** ** customers **** *** **** *** ** a **** ****** ******** ** *** wall."
  • "**** - *********** ******* ** ****** require * ****** ******. ** **** with *** ********* ** ****** ******* or ******* *** ******* **** *** course ** ******** ****** ***** ** alleviate **** *****."
  • "**** *** ******"
  • "***** ** ********** **** ** *** biggest ******* ** ********* *** ****** control ******."
  • "********** ****. ********* ** *** **** it *** ** **** *********** ** swap *** * ******, ********** ** it ** ***** "**"."
  • "**** ** *** *******. ***** ****** if ******** ********** **** ******** ******** and ******* ***** ** '***' ********* that ***'* ****** ******** ****** ****** the ** ****** ***** ***** **** supporting *** ******* ******* ** *** or ****** ***** **** ****'* ******** can *** *********."
  • "****** ********** ** ***** *****."
  • "*** ******* ******* ** ****. *** cost ** ********* *** ************ *** new ******."
  • "**** *** ********** ** ***** * new ****** **** *** *****"
  • "*** *******, **** ***** ** ** the ******* ******. "
  • "**** ** *** ******* # * concern."
  • "****** ***** *** **** ********* ** what ***** ** ** ********. ** there ** * ***** ****** ************ gap, ***** *** *** ** ****** conductors ** ***** *** *** *** readers *** ********** ***** *** *****. Same ***** **** ***** ********, ***** they ** ******? ***, *** *** long *** **** ****** **** ** service *** **** ** ***** ** issue ** *** **** ******?"
  • "**** ** ******** *** ******* ******* to ********* ****** ******* *******."
  • "***** ***** **** ** *** ******* barrier"
  • "**** ** *** ******* *******."
  • "*** ********* **** ** *** **** and **** ** ******* ****** ***** are ******** ***** ** *** ******* system."
  • "****- **** ****** ***** *** * large **********"
  • "****. ** **** ***** *** **** end ********, ******** *** ******* ******* replacing ** ******* * *** ********** or *** ************."
  • "**** ******** ** * *** *** replace ********."
  • "******"

High **** ** ********* *******/******

******* ************ ********* *** **** ** and ***** ** ****** ****** *** systems ** * *******:

  • "******* *** *******"
  • "********* ** *** ****** ** *** existing **** *** ****** ********** *** be *******. ***** ** ** ****** just ** *** *** **** ** the ****** *** **** ** ***** before *** ********* ***** *** ******* available."
  • "******* ******* *** ** ** ******* Cost ** *** *********"
  • "**** ** *** ******** ****** ** usable *** *** *** ******"
  • "******* *** ***** *****."
  • "************* **** ****** *** ******** ******* (if **** **** ** ***** **** strikes ** *******)"
  • "** *** ****** ** ***, ***** is **** ** ***** ** *** are ******** ** ** *********** - they ***** ** *** **** * network ********** *******."
  • "****** ***** ***** ******* ** ** labeling ** ***."
  • "*****, ******** ******* *******"
  • "*** **** *** ****** ** ****** the **************"
  • "****, ****** ** **** *****, ********** how ** *** **."
  • "************* *****, ******* ***** *** *******."
  • "********* * ****** ** ********* ******* it ***** ******** ******* ** ************, wiring, *** **********. **** ******* ** significant ********** *****. "
  • "******** ******* & ** ****** ** a *** **********, *** ********* ** managers ** ***** *** ****** ******.

Migrating ***********

** ***** ** ******** ************ *** barriers, ******* *** ********* *********** **** the *** ****** *** ***** ********* as * **** ******:

  • "******** **** ******** ***** **** ****** is *** ** *** ****** ****** to ****** *** ****** **** *** systems. **** ****** ********* ** * new **** ********** **** ********* ********* of ***********/** ****** ** ****** ***********."
  • "*** **** ** *********/********** * ****** is * *********."
  • "****** ******* *** **** ***** **** do *** ****** **** *** ******* trend ** ******** ***********."
  • "**** - ****** **** - ********* its *** ****** ******* ******** ****** - *** ** *** **** ** that **** ********* ** *********** **** replacing"
  • "****** ********** **** ** **-***** *********** "
  • "**** & ****** ** ******** *********** / *********"
  • "*****, ** ** ********* ** ****** and ********* ********* *********** ** ***** technology ** ****."
  • "** ******* *** *** ******** **** re-write *** *********** ***."
  • "*** ******* ******** *** **** ***** and ********. *** **** ** *********** in *** ***-******** ***** *** ****/***** already ** *** ** **** *** trying ** **** *****."
  • "********** *************"
  • "**** ** **-*************, *********** ****** ******** rules ** ***/********* ******** *** *** cost ** ******** **** ******* *** readers"
  • "***** ** ****** *** ******* **** legacy *******, *** *** ***********/******** ******** for *** ***** ** ***********, **** Bluetooth *** ***-**** *******."

Redeveloping ************

******* ******** ********* *** ******* *** effort ****** ** ******** ************ ** new *******:

  • "*****, ********** ****, **** ** ***********, existing ************"
  • "*. ******** ************ **** ***** ******* (BMS, *****, *********, *** *****,***) **** can't ** ********** **** *** *******. 2. *********** *********** ***** **** ** scale."
  • "*** ***** ************ ** ***** ***** that **** ** ** **-*********."
  • "****, ********, ***********, ********** **********, ******** concerns."
  • "*** **** ******** ** *** ***** deep *********** **** ****& **********, *** also *** *** **** ***** **** implementing * *** ***"
  • "*** *** ******** *** ****** ******* systems *** *********** **** ****** *******, taking ********* ** ******** ** *** technologies, *** ********** ******* ********** ***************."
  • "******** **** **** ** ****** ******, licence ***** *******. "

Existing ***********/***-********** **********

******* *********** ********** *** **** **** proprietary ******** *** ******** *** ** replaced *******, **** ****** ********* ***/** proprietary *********** ********* ** ******* ** transfer ** *** *******:

  • "******** ************ *** **** ******* ******* hardware *********** *** ** *********** ********. "
  • "*********** ******* *** **** ** ********* but *** **********."
  • "*** ******* ******* ** ********* ** access ******* ****** ** *** ********. We ********* ******** ** ******* ** older ********."
  • "**** ****** ******* *** ** **** cases ** **-****, *** ******** *** labor ***** *** ** ***********."

New ********/ **** *********

** **** *****, *** **** ** driven ** *** ********* *** ***** needed ** ***** ***** ** *** access ********, ********** **** *** **** is ***** *** *** **** ********* to *****:

  • "****, ****** ** **** *****, ********** how ** *** **."
  • "* **** ***** ** ***** ** be *** *** **** ******** **** is *** ******* ******* ** ********* access ******* *******. **** **** ** find **** ** ***** *** ** operate *** ******, ** **** ** time ** ***** ***** *****. "
  • "***** *** *********** **** *** *******"
  • "*** *****. *** ***** ************** ******* requires * ******** *******, **** ********* levels ** **** ***********. "
  • "****, *******, ******** ** ***** *** operators"
  • "******* ****. **** ***** ** ******** and *** ***********"

*******

**** ** * ******** ****** *** development *** ******** ****** ****** *******, as ** ***** **** ***** *** becoming **** ********* ** ******** ******* and ********* ***********.

** *** ***** ****, *********** ******** still ****** **** ****** ****** ************ of *** ********* ***** **** ******* within ****** *******.

Comments