Vendor presents cloud‑managed cameras, intercoms and vape sensors to Douglas County School District

A vendor team presented a multi‑product security proposal to the Douglas County School District board during its regular meeting on April 1, outlining a system that would add cloud‑managed cameras across campuses, license‑plate cameras at entrances, two‑way intercoms, environmental and vape sensors for restrooms, and live bus camera tracking.

The vendor said the system’s command dashboard would let the district view floor plans with camera icons, create SRO grids for rapid coverage, and run visual analytics—filters for clothing color, vehicle type and license‑plate matches—plus a face‑match workflow for locating a person by photo. "All of the access is completely in your hands," Christina, a lead product presenter, told the board, describing granular permission settings that can limit who sees live and archived footage.

Why it matters: District staff framed the project as a safety and interoperability upgrade that could integrate cameras, SRO access and the county 911 center. Administration described the presentation as information only; no action was requested that night. Superintendent Marcus Alvarado and staff said the likely funding source for a future contract would be the IT capital budget, which staff noted includes $585,000 annually for IT capital projects.

What the presentation said: The vendor—identified in presentation slides and spoken remarks with varying spellings in the transcript—described a hybrid storage model: camera‑level storage (SD) with cloud backup for redundancy. Retention is configurable; presenters used a 30‑day local retention example and said that clips can be archived indefinitely to the cloud. The vendor also described encryption and enterprise key management that it said prevents vendor staff from accessing customer archives without a temporary support token.

Board questions focused on data custody, retention, cost and access. Trustee Dave Brady asked who controls storage and how long footage is kept; vendor staff responded that retention is set by the district, that archived clips can be kept indefinitely at no additional platform charge, and that support access is temporary and revocable. The vendor said it aligned a seven‑year warranty with the proposed licensing term and agreed to extend the written quote’s expiration when requested by district staff.

Privacy and safeguards: Presenters emphasized configurable analytic features and said people‑analytics and facial recognition are off by default and require explicit enablement. They demonstrated a face‑blurring option for archived clips and described tamper mounts and vibration‑sensors for vape detectors in restrooms. Board members and staff raised signage and policy questions for public events and outdoor fields; presenters recommended configurable perimeter sharing and signage decisions be set by the district.

Costs and next steps: Staff said the board was not being asked to approve a contract at this meeting; if the board wishes, staff will return with a contract and funding clarification. A vendor representative told the board they would update and extend the quote that appeared in the meeting packet. The board took no formal vote on the vendor recommendation at the meeting.

What to watch for next: Staff said a contract would return to the board for approval at a later meeting if the board directs it forward. The district will need to decide retention policies, permissioning, signage, and how and which external agencies (SROs or dispatch) receive access in an emergency.