![]() Then at the end of the day, we'd have to do the reverse. With Genetec, we'd have to go to each door and individually swap out schedules or modify the existing schedules. ![]() With S2, it took a few seconds to activate the late start profile. We're in the midwest and sometimes it snows bad enough that we delay school by 2 hours in the morning. Instead, you have to go to each individual door and add/ remove the schedule. That alone would solve a ton of problems. My biggest gripe is that you can't simply enable/ disable a schedule. We have very complex schedules with different groups of doors for certain events. Unfortunately for us, the simplicity is the main issue. ![]() Now, it looks like Verkada might have matured to the point where we could consider it, but the cost for Verkada would be the big downside, and the implementation for what limited benefit we would get. We have some more complicated stuff that Verkada (at the time investigated) wouldn't handle really well (elevator control, parking garage, lockdown, lockout, and other wall buttons, strobes, ties into the alarm system, ties into our HR / payroll ERP system to automatically disable badges of termed employees, etc). We have Verkada for cameras, and perhaps eventually will consider Verkada's access control, but for the time being, we continue to roll out DSX, as the cost and reliability is hard to beat, plus we already have a large deployment, so adding a little more here and there makes sense. The system does what it says it will do without fail for as long as you wish seemingly. There are no recurring costs, just buy the hardware, and you're set. If the single DSX VM we have is down, each site/door works perfectly. It's an older system, not the easiest to configure, or the prettiest, but it does have a couple perks: It's extremely reliable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |