[38182] in Resnet-Forum
Re: Electronic Door Locks
daemon@ATHENA.MIT.EDU (Kevin Davis)
Tue Apr 9 08:59:32 2013
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_A8252A3FDFAE444A91261B07F86B15FD08060EE0exmbg05windukee_"
MIME-Version: 1.0
Message-ID: <A8252A3FDFAE444A91261B07F86B15FD08060EE0@ex-mbg-05.win.duke.edu>
Date: Tue, 9 Apr 2013 12:58:01 +0000
Reply-To: Resnet Forum <RESNET-L@LISTSERV.ND.EDU>
From: Kevin Davis <ksdavis@duke.edu>
To: RESNET-L@LISTSERV.ND.EDU
--_000_A8252A3FDFAE444A91261B07F86B15FD08060EE0exmbg05windukee_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
I don't support ResNet anymore but still lurk on the list (and it's nice to=
see old colleagues pop up from time to time!) Among my duties now at Duke=
is oversight of our campus one-card system.
Currently Duke has almost 1,200 access-controlled doors with magstripe read=
ers. We have another 600+ "point doors" that are time-controlled lock/unlo=
ck or alarmed. We use the Blackboard legacy platform (Unix =97 formerly Op=
tim), which is EOL in summer 2014.
We have recently issued an RFP and are reviewing responses from vendors to =
replace our current system. We are looking at Blackboard as well as non-Bl=
ackboard products, and are looking both at retaining a "one-card" system (a=
ccess and financial) or transitioning to separate access and financial syst=
ems.
Among Duke's Ivy Plus peers, Blackboard and CBORD have the predominant shar=
e for financials. Some use them for access control; others use Lenel or So=
ftware House/CCURE. If I were looking at access control vendors, I would p=
robably include AMAG and Honeywell in a list to evaluate. If you're a stat=
e institution, there may already be state procurement contracts to make a s=
ystem more affordable.
We have not previously installed wireless readers at Duke although we may i=
n the future. Stanford hosted a Lenel higher ed users' group meeting last =
spring and there are useful presentations on their website, including one o=
n Cornell's experience testing multiple wireless access control systems: ht=
tps://www.stanford.edu/dept/its/events/2012/lenel/
I think your instinct to wire external doors is right on target. Would nev=
er recommend wireless for those. And if you do wire doors, make sure you h=
ome-run the wiring back to a telecom closet and host your controllers there=
. It will make network interconnects and future upgrades/replacements much=
easier than if they are mounted above the door. Wireless for interior doo=
rs has clearly worked well at many schools. You do have to replace batteri=
es in the doors every 1-2 years; the Cornell PDF has good info on that.
As we evaluate systems at Duke, we developed several hundred requirements i=
n meetings with a couple dozen stakeholder groups. We then held a charrett=
e with about 40 key stakeholders to get the top prioritized "thematic" requ=
irements to help in making a system selection. Our users' top priorities i=
ncluded:
* User friendly for end-users (students/staff) including web interfaces=
for self service
* Robust distributed administrative controls (e.g., for departments to =
control their own door access within reason)
* Open architecture where Duke has full API-level access to the system =
and data and can provision/deprovision access ourselves
* Connection with campus identity management systems =97 either as a di=
rect feed from Oracle Identity Manager, or via the LDAP/AD directories it p=
opulates
* Mobile-savvy, ideally with smartphone apps or SMS connections since s=
tudents carry phones everywhere and seemingly always lose their cards
* Connection with enterprise systems, like PeopleSoft and SAP, for fina=
ncial transactions and reconciliations
* Cost-effective, such that we can make services more affordable for de=
partments (we do monthly charge-backs per door for access control)
* Contactless support for proximity/RFID
* Robust support for privacy, role-based access, audit logs and system =
security
Whether we stay with our current vendor or switch, we expect to roll out co=
ntactless to replace magstripe readers at doors. In general, I have found =
the dedicated access control vendors to be less-attuned to higher-ed specif=
ic needs and features than the one-card vendors like Blackboard and CBORD. =
On the other hand, a dedicated access control system may use more "generic=
" hardware like Mercury door controller boards and readers, so the implemen=
tation cost may be lower.
I'd be happy to share the RFP document off-list if it's helpful to compare =
requirements, etc. as others go through product searches. Good luck!
Kevin
---
Kevin Davis
Director, Service Management & Operational Integration
Duke University Office of Information Technology
919-668-5367 (desk) or 919-599-8194 (cell)
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--_000_A8252A3FDFAE444A91261B07F86B15FD08060EE0exmbg05windukee_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <152686B558732A4BA09302217025EF6B@win.duke.edu>
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-fami=
ly: Helvetica, sans-serif; ">
<div>I don't support ResNet anymore but still lurk on the list (and it's ni=
ce to see old colleagues pop up from time to time!) Among my duties n=
ow at Duke is oversight of our campus one-card system.</div>
<div><br>
</div>
<div>Currently Duke has almost 1,200 access-controlled doors with magstripe=
readers. We have another 600+ "point doors" that are t=
ime-controlled lock/unlock or alarmed. We use the Blackboard legacy p=
latform (Unix =97 formerly Optim), which is EOL in summer
2014. </div>
<div><br>
</div>
<div>We have recently issued an RFP and are reviewing responses from vendor=
s to replace our current system. We are looking at Blackboard as well=
as non-Blackboard products, and are looking both at retaining a "one-=
card" system (access and financial) or transitioning
to separate access and financial systems.</div>
<div><br>
</div>
<div>Among Duke's Ivy Plus peers, Blackboard and CBORD have the predominant=
share for financials. Some use them for access control; others use L=
enel or Software House/CCURE. If I were looking at access control ven=
dors, I would probably include AMAG and Honeywell
in a list to evaluate. If you're a state institution, there may alre=
ady be state procurement contracts to make a system more affordable.</div>
<div><br>
</div>
<div>We have not previously installed wireless readers at Duke although we =
may in the future. Stanford hosted a Lenel higher ed users' group mee=
ting last spring and there are useful presentations on their website, inclu=
ding one on Cornell's experience testing
multiple wireless access control systems: <a href=3D"https://www.stan=
ford.edu/dept/its/events/2012/lenel/">https://www.stanford.edu/dept/its/eve=
nts/2012/lenel/</a></div>
<div><br>
</div>
<div>I think your instinct to wire external doors is right on target.  =
;Would never recommend wireless for those. And if you do wire doors, =
make sure you home-run the wiring back to a telecom closet and host your co=
ntrollers there. It will make network interconnects
and future upgrades/replacements much easier than if they are mounted abov=
e the door. Wireless for interior doors has clearly worked well at ma=
ny schools. You do have to replace batteries in the doors every 1-2 y=
ears; the Cornell PDF has good info on that.</div>
<div><br>
</div>
<div>As we evaluate systems at Duke, we developed several hundred requireme=
nts in meetings with a couple dozen stakeholder groups. We then held =
a charrette with about 40 key stakeholders to get the top prioritized "=
;thematic" requirements to help in making
a system selection. Our users' top priorities included:</div>
<ul>
<li>User friendly for end-users (students/staff) including web interfaces f=
or self service</li><li>Robust distributed administrative controls (e.g., f=
or departments to control their own door access within reason)</li><li>Open=
architecture where Duke has full API-level access to the system and data a=
nd can provision/deprovision access ourselves</li><li>Connection with campu=
s identity management systems =97 either as a direct feed from Oracle Ident=
ity Manager, or via the LDAP/AD directories it populates</li><li>Mobile-sav=
vy, ideally with smartphone apps or SMS connections since students carry ph=
ones everywhere and seemingly always lose their cards</li><li>Connection wi=
th enterprise systems, like PeopleSoft and SAP, for financial transactions =
and reconciliations</li><li>Cost-effective, such that we can make services =
more affordable for departments (we do monthly charge-backs per door for ac=
cess control)</li><li>Contactless support for proximity/RFID</li><li>Robust=
support for privacy, role-based access, audit logs and system security</li=
></ul>
<div>Whether we stay with our current vendor or switch, we expect to roll o=
ut contactless to replace magstripe readers at doors. In general, I h=
ave found the dedicated access control vendors to be less-attuned to higher=
-ed specific needs and features than
the one-card vendors like Blackboard and CBORD. On the other hand, a=
dedicated access control system may use more "generic" hardware =
like Mercury door controller boards and readers, so the implementation cost=
may be lower.</div>
<div><br>
</div>
<div>I'd be happy to share the RFP document off-list if it's helpful to com=
pare requirements, etc. as others go through product searches. Good l=
uck!</div>
<div><br>
</div>
<div>Kevin</div>
<div><br>
</div>
<div>
<div>
<div>
<div><br>
</div>
<div>---</div>
<div>Kevin Davis</div>
<div>Director, Service Management & Operational Integration</div>
<div>Duke University Office of Information Technology</div>
<div>919-668-5367 (desk) or 919-599-8194 (cell)</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
</div>
</body>
</html>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to <a href=3D"http://LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a>
___________________________________________________
--_000_A8252A3FDFAE444A91261B07F86B15FD08060EE0exmbg05windukee_--
