Implementing a Video Management System (VMS) at Stanford. NACCU 2016 April

Transcription

1 Implementing a Video Management System (VMS) at Stanford NACCU 2016 April

2 OUR PARTNERSHIP We are both part of the central IT Services Organization Jay Kohn is responsible for the card services vision, business model, and card issuance. Anne Pinkowski is responsible for the technical operations and staff responsible for the support of the systems.

3 ABOUT STANFORD 6994 Undergraduate Students 9128 Graduate Students 4:1 student to faculty ratio 8180 acres 700 buildings 97% of undergrads live on campus 22.2 billion dollars in endowment

4 ABOUT OUR DEPLOYMENT 300+ buildings on Lenel 250 cameras deployed 423 total access panels: 343 LNL-3300 panels 12 LNL-2220 panels 117 ILS panels 2777 total doors: 2397 wired locks 254 wireless locks 126 electrified locks 61,000+ Active cardholders 52 Segments

5 AN INVITATION Join us as we share our journey, our lessons learned, and our vision for the future of video management on The Farm: from the pilot, through the RFP, including challenges regarding the entire process, privacy, user interface, funding, etc. Page 5

6 THE BEGINNINGS Asked to provide video for new construction Originally used incumbent access control provider Issued RFP when original solution didn t align with needs Developed Video Surveillance Guidelines with Public Safety and Risk Management Page 6

7 THE RFP Vendors considered for formal RFP Page 7

8 THE PROCESS PILOT PREP PILOT OVERVIEW Common platform (BCD Video) Each provider given 2 indoor cameras + 2 outdoor cameras (Axis, Sony, Arecont) Each provider (Exacq, Milestone, Genetec) had 1 interior + 1 exterior location Signage posted (Stanford requirement) that video was in progress Two separate components: video retrieval and viewing interface and an admin interface Series of use cases and scenarios: - Saved 1 minute, 5 minutes, and 1 day of video to see the quality, speed of retrieval, evidence locker, etc. - Tested ease of use: setting up users, templates, granularity of permissions, etc. - Tested management of devices All vendor solutions delivered through both a thick client and web/mobile interface Page 8

9 THE PROCESS PILOT PREP Common platform (BCD Video) Each provider given 2 indoor cameras + 2 outdoor cameras (Axis, Sony, Arecont) Each provider (Exacq, Milestone, Genetec) had 1 interior + 1 exterior location PILOT DECIDING FACTORS Signage posted (Stanford requirement) that video was in progress PILOT OVERVIEW PRIVACY REQUIREMENTS Ability to create templates to manage campus access Ability to provide finely detailed access control to the various system components (for distributed management) Two separate components: video retrieval and Includes both day-to-day access and retrieval of stored video viewing interface and an admin interface Audit log detail for changes Series of use cases and scenarios: - Saved 1 minute, 5 minutes, and 1 day of video to see the quality, speed of retrieval, evidence locker, etc. - Tested ease of use: setting up users, templates, granularity of permissions, etc. - Tested management of devices Exacq $ All vendor solutions delivered Pricing through Milestone both $ a thick client and web interface Genetec $$ Lenel $$ Auditing (audit log details) User Interface Firewall requirements Page 9

10 THE CHALLENGES 1 Already had 7 active locations with over 200 cameras on Lenel by the time our pilot completed 4 Vendors provided training, but tests occurred after they left, which led to information overload 2 Since buildings needed VMS during our pilot, we sank costs in the existing video solution 5 We had to migrate all existing camera locations to the new solution after selection 3 Time consuming to compare each solution (loading clients, walking through tests, etc.) 6 To test, we had to install test hardware in the field, which was expensive and challenging Page 10

11 THE RESULTS Hands down easier to use; had fewer options but more than enough for our needs Good interface; a lot of moving parts Not as clean for a comparable level of information; a lot of moving parts Page 11

12 THE LESSONS LEARNED Prepare for a time-consuming process Compare carefully Timing/coordination for each vendor install and training Checklists for each vendor for each item There are so many configuration options! Make sure you are comparing apples to apples Take the notes as you go, you won t remember later Take time for presentations upfront Pilot the solutions Talk to others who have been through or are going through this We learned about other applications after the RFP but weren t prepared to start over It helped to narrow down the choices Use consistent platform configurations Use consistent camera configurations We purchased some items as we couldn t get enough demo equipment to meet our needs Page 12

13 IN CONCLUSION QUESTIONS? Jay Kohn Director of Card Services Anne Pinkowski Director of Integration and Client Solutions Page 13

14 APPENDIX Page 14

15 APPENDIX 1 TECHNICAL REQUIREMENTS Page 15

16 APPENDIX 2 SECURITY, OPS, LICENSING REQUIREMENTS Page 16