Access Control Specification Guide

***** **** * **** 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 ******* **:

• ****** ********** **** ****** Guide
• ************ *** ****** *******?
• ******** ****** ************** *****

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:

• **** ***** ******
• ***** ***** *** ****** Control
• ********** *****
• **** ****** *******

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 ** ****.]