Access Control Specification Guide

By: Brian Rhodes, Published on May 19, 2016

This 15 page report provides the most in-depth guidance on specifying Access Control systems you will find.

Specifying Access Control correctly can be tricky, because every opening has quirks and are prone to outside factors that impact system performance. Not only this, but what you don't specify can be just as problematic as what you do.

Most access RFPs have serious problems. While they comprehensively spell out contract conditions and business terms, they are typically scant on relevant details about the system. Not only do they tend to be a random smattering of technical points, pulling them together into a cohesive system is often needlessly costly or may even be impossible to build.

The Big Mistakes

Most of the trouble specifying access has a root cause in one of the three areas below:

1. Incomplete details, where things you don't know can ruin your budget and system goals.

2. Difficult to build, where details that sound prudent may actually limit selection and significantly drive complexity to integrate.

3. Proprietary, where even generic boilerplate writes in choices that lock you into one vendor.

In this report, we address the best strategies to avoid these problems.

Doing It Right - 18 Key Specification Areas

The good news is that you do not need to be an expert to specify great systems. In the sections below, we cover the right details to include, how to include them, and how to avoid common traps through addressing these 18 areas:

  • Is This An Expansion or New System?
  • Determining Access Security Goals
  • Establishing Monitored, Managed, or Forensic Use
  • Identifying Other System Integrations
  • Which Credentials To Use
  • Defining Doors/Opening Detail
  • Defining Turnstile Use
  • The Importance of Door Position Switches
  • Defining Existing Locks/Hardware
  • Specifying Readers
  • Deciding to Use IP or Serial based Controllers
  • How To Use PoE For Powering Systems
  • System Edge vs. Centralized Architecture
  • Is System Networking Wired or Wireless?
  • Considerations For Using Existing Databases
  • Evaluating User Management Features
  • Using Special Features Like Time and Attendance & Mustering
  • Establishing System Maintenance Expectations

**** ** **** ****** provides *** **** **-***** guidance ** ********** ****** Control ******* *** **** find.

********** ****** ******* ********* can ** ******, ******* every ******* *** ****** and *** ***** ** outside ******* **** ****** system ***********. *** **** this, *** **** *** don't ******* *** ** just ** *********** ** what *** **.

**** ****** **** **** serious ********. ***** **** comprehensively ***** *** ******** conditions *** ******** *****, they *** ********* ***** on ******** ******* ***** the ******. *** **** do **** **** ** be * ****** ********** of ********* ******, ******* them ******** **** * cohesive ****** ** ***** needlessly ****** ** *** even ** ********** ** build.

The *** ********

**** ** *** ******* specifying ****** *** * root ***** ** *** of *** ***** ***** below:

*. ********** *******, ***** things *** ***'* **** can **** **** ****** and ****** *****.

*. ********* ** *****, where ******* **** ***** prudent *** ******** ***** selection *** ************* ***** complexity ** *********.

*. ***********, ***** **** generic *********** ****** ** choices **** **** *** into *** ******.

** **** ******, ** address *** **** ********** to ***** ***** ********.

Doing ** ***** - ** *** ************* *****

*** **** **** ** that *** ** *** need ** ** ** expert ** ******* ***** systems. ** *** ******** below, ** ***** *** right ******* ** *******, how ** ******* ****, and *** ** ***** common ***** ******* ********** these ** *****:

  • ** **** ** ********* or *** ******?
  • *********** ****** ******** *****
  • ************ *********, *******, ** Forensic ***
  • *********** ***** ****** ************
  • ***** *********** ** ***
  • ******** *****/******* ******
  • ******** ********* ***
  • *** ********** ** **** Position ********
  • ******** ******** *****/********
  • ********** *******
  • ******** ** *** ** or ****** ***** ***********
  • *** ** *** *** For ******** *******
  • ****** **** **. *********** Architecture
  • ** ****** ********** ***** or ********?
  • ************** *** ***** ******** Databases
  • ********** **** ********** ********
  • ***** ******* ******** **** Time *** ********** & Mustering
  • ************ ****** *********** ************

[***************]

***** **** * **** at *** ****** ******** appear:

Common ********

**** *** ****** ******* might ** **** ***********, but **** **** *** mean **** **** *** the *** ****. **** at ***** ******** ** pulled **** ****** ****:

*** ****** ******:**** *** *************, *** risk ** ********* *** many *********** **** *********** drive ****. ******* **** Access *******, *** ******** is **** ********* ****. Take **** ******* **** the ************** ******* ****** ******'* ****** ************:

*** **** ** ******* to ***** * ***** from *** ***** ** the *** *****. ** details ********* ****/******* ****, existing ********, *** **** people **** ** **** access ** **** ********** types **** *****, ** when *** ******** ****** be ******** *** *****. Not ** ******* **** descriptions ** *** *** who *** ****** **** be ****, ** ***** other ******* **** **** to ********* **** *** access ********.

*******, *** ***** ******* may ** ******** ** discovered ***** * *** walk, *** *** *** respondents *** **** * fair ***** ** ***** them ** ***** * bid.

******** *************:******* *********** ***** ** the ********* ** ***** that ***** ***** ** economical, *** ***** ** essentially ***** ******* ** just *** ** *** bids. **** *** ******* from * ****** ********** RFP:

******* *** **** ******** good ****** ********* **** descriptions *** ********* *** is ***-******. *******, *** to *** ********* ** defining '****************' *** *** listing ** * ****** proprietary **** ** **** controller *********** ****** ****** to ********** ** **** existing ******.

******* **** ** ******** or *** ** ********* to *****, ******* ** would ** **** **** efficient *** **** *** solicitor *** *** ******* to ***** **** *********** plainly *******. *** ****** does *** ******* *** proprietary ****** ** ****** systems, **** *** ***** they *** ************ ****** to *** ******** ******** for ******* ******. *******, the **** ** ****** defining '****************' ***** **** option.

Technical *************

**** *** ** ********* aspects ** ******* ** every ****** *************:

Defining ********* ** *** *******

** **** ****** ***, or **** ** ** a ****** ******** ** an ******** ******? ********* this ******* **** ******* for *** ******** **** kind ** **** ** being ******. *** ** the *********** ****** ** most ****** *******, **************** is *********** ***-********, *** if * ****** ** already ** ***** *** satisfactory *** **** **** is ****** ********* **** platform. **** ** ****** the ***** ********* ****** since ********* ********* **** servers *** ******** *** be ******* ** *** needed.

**** ****** **** ***** potentially ****** ********** ****** two ******* **** ****** incorporate **** *****'* *********. Even ** *** **** is ********** ** ******** system, ********** ** ******* some ** *** ******** components ** * **** that ****** ** **** clear **** *** *****. Special ***** ** ******** tools *** ** ****** to ******** ******** ********** information, * ***** *** "********* ****** ******* *******" **** ********** ** more ******.

Security *****

****** ** ******, *** essentially *********, ** ** give * ******* *********** of *** ***** *** the ****** ******. ******* "With **** ******, *** facility ***** ** ******** off-shift ***** **** ******** the ******** *** **** all *** ******* *********** from ******** at *** ****" **** greatly ****** ***** ********* a ****** ** ******* the ********* ******** ** build ******.

************, **** ****** ******* is ********** ** *** issue ** "**********", ******* where *** **** ********* openings *** ******* ** key **** ******************* ** ****** *** risk. *** ****** ********** and ****** ** **** risk, *** *************: ****** ******* ************.

**** **** ********* ****** or ********* ** *** needed, ************ *** ***** groups **** *** ****** and ****/***** **** **** it ** *** ********** of ****** *******. ****** these ***** ***** ***** will **** ******* ****** the ***** ******** **** the ****** ***** ** assignable ******** *** *** stated ****.

********* *** ********* ***** goals **** ********* ** existing ****** ** ***** essential, ** *** ***** of ******* *** *************** can ****** **** ****. Including * ***** ********* describing '******** *****' *** refresh *** ************* ** a ****** **** ******* old.

Monitored, *******, ** ********

**** ** ** ****** how *** '*******' ******* of *** ****** **** be *******. ** *** goal ** *** ********** up *********, *** **** only ****** ** **** absolutely *********? **** ** onsite ***** ***** ******** monitor *** ******* ** events **/*/***? ** ** it ****** ** ****** oversight *** ********** ** active, *** ****** *** to * ******* ******* facility?

******** **** *** *** system ** ***** ** be **** *** ** whom *** ******* ***** by ******** ****** ********, or ** ****** **** the ***** ****** *** manage *** ****** ** the ***** ****.

Other ******* ***********

** *** **** **** access ******* ** ** combined **** ***** ************ or ********* ******? ** you **** * **** alarm ******? ****** * point ** ***** ***** goals, ******** **** *** current ****/******/******** ** *** systems ** ** ********** help ***** ****** *** installation ***** ************.

***********

** *** ****** ** new, ********* ********* ****** not ** ******** ** the ****** *** ********. If ** ********* ** an ******** ******, *** answer ***** ******* ** made. *******, ** ****** case, ********** ******** ***** credential **** ** ******* prevents ** **** ***** a ****** ******** ********.

** ***** ** **********, most ****** ******* *** contactless ***********. ** *** past, *** *** *********** have **** *** ********, but *** ** ******** concerns (**** ** **********) and ******* ******* ********, they **** **** ********** by **.** *** *****. From * **** **********, the **** ******** *********** are *** **** ***** or ******* **** ***** formats.

** ** *********** ******* exist, ******** *** ***** product ** ** **** security ****** ** ** economic ***. *** **** people **** ** ************? Should ***** *** ****** as ******, ** ** a **** ******* ****** needed? **** ***** ******* use ***********, *** ****** they ** ********? **** about **********? **** **** mandate ******** ******* *** used?

************, ** ******** ******** codes *** ** ***, they ****** ** ***** as * ************* ** the ****** ******. *** all ******* *** **** to **** **** ******* codes, *** **** ***** detail *** ***** *********** cost ** *** **** clear.

*** **** *******, **** our ******* **:

Doors/Openings ******

********** *** ******** ** be ********** ** ******* not **** **** * design *********** *** **** from ********* ********** *******. No *** ******** *** alike ** **** *** same ***, *** * short *********** ** ******* of *** ******* *** it ** **** **** far ** ********* **** controls.

*** *******, *** '**** entrance ** ** ****** building' ** ****** ********* as ****:

"*** **** ******** ** a *** ** ***** double ***** **** **** swing ***. ***** ***** are ******** **********, *** the ***** **** ************* opens *** ****** **** a ****** ****** ** pressed. * ****** ******** camera ****** ** ********** into *** ****** ** that *** ********* ***** are ******** ** **** enter. **** ******** ** typically **** ** *** public ****** ******** *****, but ****** ** ****** and **** ********** ** approved ***** **** *** - *** *********. ************* 30 ****** *** **** access ****** * ******* night ****** ***** *****, including ******** ***** *** delivery ******. **** ******* shows *** *******:"

****: ****** **** ** annotation, **** * **** clean **** ** *** opening ** ** ******.

***** *** *********, *** information ******** ***** ***** insight **** ****** ** observed ****** * ***** job **** *** ******** door ****, **** ********, security ****, **** *******, and ********* ****** *********** (video). ***** ****** ********* is *** ******, ******* on ***** ******* ********* guesswork.

*** **** ****** ** how ** ******** ******** openings, ******* **** *** doors, *****, ** **** turnstiles, ***** *** ******** below:

Door ******** ********

*** ** *** **** useful, *** **** ********* aspects ** ****** ******* are *** ******* **** indicate ******* *** **** is **** ** ****. While **** **** *** as ** '*****', ***** remains ** **** ********* or *********** *** ** monitor *** ******* ***** of *** ******* **** these *******.

***** **** *** ****** by **** ** '********', solicitors ****** ********** ***** they **** ***** ******* included. ***** *** "**** ******** ******** (***) For ****** ******* ********" *** **** ******. For ******** ** *** biggest ******* ** ********** use ** *** ********, read "********* **** **** ********" ** ***** *** subtle ******** **** ******* undermines *** ****** ******.

Existing *****/********

**** *****, ******-***** ****** is *** ********, *** basic ************ *** ******. Often ****** ******* ************* with ******** ********** *****, and ***** ********* ** how **** ******* ** appointed ** ********** ** choosing *** **** ****** of *******.

*** **** ****, * picture ** ***** ******* description ** ******: "*** **** **** ** a ***** (*****) **** currently **** ****** **** a ***** ***. *** door ****** *** *** has ** '****' ******* above **. *** **** can ** ****** ** unlocked **** *** ******* of *** **** ** a *** **** ****** to ********. *** ******* for *******:"

*** ******* ******* ** describing ***** ** *** to ****** *** ***** type *** ******** **** access ****, *** ***** posts:

Choosing *******

********* *** ***** ****** is *** ****** ** which *********** *** **** and ***** *** ******* is *******. **** *** written ************ *** ****** of *** *****/*****, **** decisions *** ** **** what **** ** ******* and *****.

******* ********** *** ******** where******** ************** ************* ** **** **** ensure *** ***** ****** is ********* ** ******* all *********** ****** ** that ****.

*** ******* ********** *** more ****** ** ******** readers, ***** *** ****** below:

IP ** ****** ********* *******

*** ******* **** **** a ****** ******** ****** be ********* ** ******** cabling ** *** ****** be ****. **** ********** one **** **** *** other *** ** ****** if ********** ** *** strong, ******** **** ****** systems *** ** ******** as *** ******* ******, a ***** **** **** continue.

** ******** ******** *** to ** ****, ****** the ********* ** ******** switch ***** ***** ****** guesswork ** ********* **********. Marking * *** ** floorplans **** ******* ***** positions **** ** **** specification ** *****:

** *** ** ********* networks *** ******, ****** note ** *** *******, main ***** *****, ** access ****** ******** **** new ***** **** *** concurrent **** ********.

Edge ** *********** ************

** * ****** ******, specifying ***** **** ******* takes ***** ** *********. Most ****** ******* *** a **** ** **** controller ******* **** *** opening, *** ********** *********** location ** ****** ********** could ************* ***** ***** costs ** ****** ** older ******* ***** ***.

**** ** '****' ******* are ****, *** ********* can ** ********* ****** locked ******* ** ******* enclosures. *******, ****** **** enough ***** ** ********* for ***** ******* ** commonly ********** *** *** drive ***** ** *** properly ********** ****** **** writing. ***** ******* ******* more ****** *** *******:

Using ***** **** ********

** **** *****, ******** 802.3 **/** *** *** be **** ** ****** power ** **** *********** and ************ ********* ******* like ******* *** *******. Using *** ** ********* more ********** *** ****** online ********** **** ********, stand ***** ***** ******** typically ** ***.

*******, ***** *** *** limit *** ***** ** connected ******* ***** ** 'total ****-*******' ***** *********, which ** ******* *** mA ** ****, *** the *** ****** ** doors ** * ****** PoE ******* ********** *** limited ** ***. ***** factors ** ******** ******* the ****** ** *** controller ********, *** *********** against ******** ******** ** a ******** ***** **** a *** ********** *** common.

****** ******* ****** ******* Guide******** ** **-***** **** at *** *******.

Wired ** ********

**** ** ***** ** controlling ****, **** ************* of ***** ******* *** cause ****** ** ********* for ****** ** **** to ***** ********. ********** if ***** ***** *** not ******* ****, *** electronic ******* *** ******* is *********, ******** ***** wireless *** '*****-*****' ****** of *****.

***** *** **** **** may ** **** *** a ****** ******** ****, the ******* **** ** connecting ******** ******* ******** via * **** ******* run ***** ** **** expensive. ***** *** ******* price *** *********** ********** with ******** ***** (**: replacing *********) ***** ** prohibitive *** ****** *******, they ***** ***** ** economic *** ** **** of *********** ***** ******* expansion. *** **** ** these ************, *** *** "******** ****** ******".

Using ******** *********

********** *** ******, *****-**** systems, *** ******** *** bring *********** ****. ******** the **** ********** ****** will ** **** ** foolish ****** *** ************* explicitly ****** ***** ******** platform *** ******* ** available. *** "****** **** ** ******: Database" ***** ****** **** point, *** *** ****** options, ** *****.

User **********

******** ****'* ***** *** a ******** ****** ** the *************, *** *** where ********* ******** **** be ********* ** *********. Spelling *** ******** '**** View' *** ********** ******* helps ********* ******* *** configure *** ***** ********. If ********* **** ** lock/unlock ***** ** **** time, ****** ******** ******* are ** ** *******, or ** *** ****** system ****** ********* **** the ***** ************ ******, these ************ ****** ** clear.

**** *** ******* **** are *** ******** *******, if ***** **** '****** access' **** *********** ** inclusion ** '** *****' creation *******, ** ****** not ** ******* ** will ** ******** ****** stated.

****, ** ******** ************ are ** ** **** for ******* *******, *********** of ***** ******** *** build ************** ****** ** listed ** ********* *** system ** ********* ** confirmed. *** **** ******* on *** ******** ********** piece *** ************ ** the ******* ******** *******, see *** ********* *****:

******* ********:****** ******* ** ****** for **** **** **** unlocking *****. **** ******* include ******* *** '**** and **********' ******* **** essentially ******** * **** clock, ** '*********' **** grants *** ******* ********* that **** ******* * roster ** ********* ** a ********** ****.

** ***** ******** *** desired, ** *** ***** integrations ******* ******* *** core ****** ******* *********, effort ****** ** ***** defining *** ******* ****** in ************* *********. ***** posts **** **** ******* what ** *** *** and *** ** **** the ************:

Maintenence *****

*******, ************** ****** ***** out *** ******* ****** software *********** ***** *** any ********** ******* ******** required ** **** *** system ******* *** ***********. Some ********* **** ** ongoing *********** ****, ***** others ******* * ****** plan *** *** *** prioritize ******* ** **** support ** *** *******.

*** **** ** **** maintenance ****** ****** **** system *********, ** * system *** ** ********* less **** ********* *********, but *** ********* ** unrealized ***** ** ********** years.

Access ******* ************* ****

*** ********* ******* ******** a ******* ** **** requirement *** ****** ******* to ********. ** ********* you **** *** ***** this **** **** *** documents *** *** ** as * ******** ***** in ******** *** ************ for **** ****** *******.

Opening/Door ****: Often best depicted in a picture. If not permitted, a short written description describing: Steel, wood single or double door? Right, left, or swing ‘reverse’. Glass opening? Turnstile?

Users *** ****: Average number of users during busy times, so that cycle times of locking hardware can be sized accounting to the busiest period the door permits access.

Opening's ******** *****: The high-level purpose of access control: “Restrict unapproved users from entering during overnight hours” or “Only residents with current rent payments should be allowed to use gym facility.”

Other ********* ** *** ****: Often best expressed in a picture, a snapshot or written description of the other hardware devices hung on the opening. Examples: “Closer on upper hinge side, vertical rod on upper strike side, and an exit device hung on the inside. Outside keyed access.”

Reader ****/******** ********: On the door frame (mullion), or on an adjacent wall? Are mounting surfaces suitable? Are they protected/sheltered from ice and snow? Can someone is a wheelchair or with limited range of movement reach the reader, per ADA (or similar)?

Credentials ** ***/******** ************** ******: Common Choices: 125 mHz, 13.56 MHz contactless. HID format, MiFARE/DESFire? 26,33,34,35 bit cards? Facility code needed? Is more than one credential needed at the door to verify the user?

Intercom ******?: If a user cannot enter the door, or if a visitor request entrance, can they page help or an attendant? Two two-way conversations need to be supported?

Lock **** ******: Choices- typically electric strikes or maglocks, but dictated by building code, AHJ preference, and type of hardware existing on the door.

System ******* ****: TCP/IP, Serial hardwire, wireless, or stand alone locks? If IP, are existing LAN segments available? Are cable pathways and data closets marked? If wireless, the signal strength at doors verified?

Controller *****: Choices- Edge or Centralized? Standalone or host dependent?

Critical **** ********** ********: What real-time features required? What type of reporting is needed? Will users need access from a browser or mobile devices? Are client workstations available?

Server *****/**********?: Do you have available resources in the server stack? Are they physical or virtual? Do you need your servers to host access locally or remotely? Including this ensures no ugly incompatibilities happen at the last minute. If a new server is used, will local IT resources be familiar with configuration and support?

Database ******** ******: Does you enterprise already use a standard database platform like SQL? If so, make note so the access system can plan to make use of existing rather than purchasing new or using a proprietary platform.

Special ********: Do you need Time & Attendance or Mustering? If so, does your hardware design support those features? Make note of the ‘other systems’ you would like access control to feed into or use like video surveillance or intrusion alarm.

[****: **** ***** *** originally ******** ** **** but *** ******* / improved ** ****.]

Comments (1)

Great Article! Really takes into account all the things, large and small, that must be thought when bidding or planning a job. I think this article should be helpful for people trying to grasp AC( and what's involved) for the first time, or a pro getting ready to set up a new system or refurbish an older one. Very insightful!! Thanks for the write up!

Read this IPVM report for free.

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

Related Reports

Use Access Control Logs To Constrain Coronavirus on Apr 09, 2020
Access control users have included capabilities that are not commonly used that can help zero-in and discover potential Coronavirus hotspots in a...
"Severely Impacted" Mercury Security 2020 Leap Year Firmware Issue on Jan 17, 2020
One of the largest access controller manufacturers has a big problem: February 29th. Mercury Security, owned by HID, is alerting partners of the...
Breaking Into A Facility Using Canned Air Tested on Jan 28, 2020
Access control is supposed to make doors more secure, but a $5 can of compressed air may defeat it. With no special training, intruders can...
Multipoint Door Lock Tutorial on Jan 23, 2020
Despite widespread use, locked doors are notoriously weak at stopping entry, and thousands can be misspent on locks that leave doors quite...
The Problem With Fever Detecting Thermal Sunglasses on Apr 15, 2020
While the media has promoted using thermal sunglasses to detect fevers, this approach has fundamental problems and, at best, is health...
Facial Recognition: Weak Sales, Anti Regulation, No Favorite, Says Security Integrators on Jul 07, 2020
While facial recognition has gained greater prominence, a new IPVM study of security systems integrators shows weak sales, opposition to...
Help Security End Users Facing Coronavirus Improve Remote Access on Mar 24, 2020
Many end-users and integrators are struggling with the impact of coronavirus lock downs but remote access can help both sides during this...
Access Credential Form Factor Tutorial on Feb 10, 2020
Deciding which access control credential to use and distribute, including form factor, can be a difficult task. Knowing the limitations and...
Verkada: "IPVM Should Never Be Your Source of News" on Jul 02, 2020
Verkada was unhappy with IPVM's recent coverage declaring that reading IPVM is 'not a good look' and that 'IPVM should never be your source of...
Bottom: Integrators Start To Stand Vs Coronavirus on Apr 20, 2020
Good news - IPVM integrator statistics show that while coronavirus has hit integrators hard, it is now bottoming out and starting to...

Most Recent Industry Reports

Remove Dahua and Hikvision Equipment "Immediately" Or Else Banned From US Government Contracts on Jul 10, 2020
The US government has directed contractors to remove covered equipment, such as Dahua, Hikvision, and Huawei Hisilicon products, "immediately." If...
ZeroEyes Presents Firearm Detection Video Analytics on Jul 09, 2020
ZeroEyes presented its Firearm detection Video Analytics system at the May 2020 IPVM Startups show. A 30-minute video from ZeroEyes...
Directory of 162 "Fever" Camera Suppliers on Jul 09, 2020
This directory provides a list of "Fever" scanning thermal camera providers to help you see and research what options are available. There are...
Clinton Public View Monitor (PVM) Mask Detection Tested on Jul 09, 2020
Face mask detection, or more specifically not wearing one, is expanding amidst the pandemic. Clinton Electronics has added this capability to their...
These Florida Real Estate Agents Are Now Selling "SafeCheck USA" Temperature Detectors on Jul 09, 2020
The "Kakon Brothers", William and Nathan, are self-described "south Florida Power Agents specializing in Luxury Real Estate" who "have closed over...
Avigilon ACC Cloud Tested on Jul 08, 2020
Avigilon merged Blue and ACC, adding VSaaS features to its on-premise VMS, offering remote video and health monitoring that was previously limited...
Hikvision's India Dominance Faces Threat on Jul 08, 2020
While Hikvision has become a dominant video surveillance provider in India, recent tension between the governments of India and the PRC is...
The US Fight Over Facial Recognition Explained on Jul 08, 2020
The controversy around facial recognition has grown significantly in 2020, with Congress members and activists speaking out against it while video...
Sperry West / Alibaba Tablet Temperature Measurement Tested on Jul 07, 2020
In April, we ordered a ~$500 temperature tablet from Alibaba. We set it to the side while doing 18 other temperature screening tests but, after...
Facial Recognition: Weak Sales, Anti Regulation, No Favorite, Says Security Integrators on Jul 07, 2020
While facial recognition has gained greater prominence, a new IPVM study of security systems integrators shows weak sales, opposition to...