Seventeen YMCA branches, two weeks, one login
The YMCA of Greater Richmond rolled cameras across its branches faster than most organisations finish a pilot. The reason it stuck was Active Directory.
The figure Spot AI leads with for the YMCA of Greater Richmond is 17 locations in two weeks, in 2021. That is a fast rollout for any organisation, and unusually fast for a non-profit whose IT function is small enough that one person carries the title Technology Project Lead and Systems Specialist. That person is Louie Klenke, and his account of why it worked has little to do with cameras.
The lockout problem
Before the switch, according to Spot AI's published account, the YMCA's previous camera system made ordinary administration painful. "If a user got locked out, the team had to completely delete and re-add them," the case study says.
The fix was single sign-on through the YMCA's existing Active Directory, so staff log in with their Outlook credentials. Users, locations, cameras and appliance health, the account says, are now visible on a single dashboard.
No longer does Spot or any other product feel like an outside product, it now feels like it's part of our ecosystem.
That is Klenke's line. A camera system that lives outside the identity directory is a system IT has to babysit; one that lives inside it inherits every new hire and every password reset without anyone touching the camera software.
Footage in Dropbox
The second problem was investigation. The YMCA had inconsistent NVR setups and different storage limits at different sites, which meant nobody could be sure the footage they needed still existed. When it did, sharing it meant pushing large files through Dropbox and OneDrive.
Spot AI's account describes the replacement: 30 days of retention across all sites, plus a feature called Cases that keeps footage in the cloud indefinitely and lets the team annotate it and share it with internal and external parties. Cases is described as a favourite of the YMCA's team.
It has saved our risk management officer a tremendous amount of time and increased our efficiency of incident reporting.
The pool alerts
The detail most specific to a YMCA is where the AI alerts ended up pointing. The team uses them at entry and exit points and as secondary security at night, which is the standard pattern. It also uses them, the account says, "to monitor various processes like drain and fill operations for their pools."
A pool that is draining or filling is an unattended process with a long duration and an expensive failure mode, and watching it means standing beside the pool for hours. An aquatics operation reached for a security camera to do that job. If you run a facility, what is the long, boring, costly-to-get-wrong process that nobody wants to stand next to?
What was actually bought
Read the whole case study and the video hardly features. The YMCA bought a directory integration, a retention policy that is the same everywhere, a way to share a clip without a file-transfer service, and an alert that fires when a pool does something it should not. Seventeen sites in two weeks was possible because none of those required anyone to visit a branch.