Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the School Security Technology topic

No spam. Unsubscribe anytime.

Advisory committee urges dedicated IT and budget lines to maintain cameras, access systems and vendor‑supplied security tech

Student Safety and Well-being Advisory Committee · December 17, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

A school safety work group recommended a full‑time IT technician dedicated to facilities and security systems, plus distinct operating and capital budget lines to maintain cameras, firmware and vendor services; members also heard that a two‑phase weapons‑detection study is underway.

The Student Safety and Well‑being Advisory Committee reviewed a report from the Modern Facilities and Resources work group recommending a dedicated IT position and clearer budgeting to maintain school security systems.

The committee heard that current camera and access systems (referred to in discussion as GenTech and the Raptor system) require ongoing firmware and licensing management. A committee member said a full‑time IT technician focused on facilities and safety would “plan and budget” for replacements and updates so the district is not repeatedly reallocating funds across programs. Vendors have been invited to demonstrate hardware and software; the work group described a two‑phase weapons‑detection study whose first phase is complete and whose second phase will begin after the new year.

Why this matters: committee members stressed that buying equipment is only the first step. “Technology alone will not fix this problem,” the chair said, noting that screening lines and detection systems require staffing, training and recurring funds. Members pressed for a dedicated security budget that would cover repairs, monitoring, data storage and unanticipated vendor costs rather than relying on one‑time or ad‑hoc transfers.

Details and debate: presenters described common concerns: whether LEA or county funds should be used during construction projects; the need to track renewal dates for firmware and licenses; and how a district‑level IT staffer could advise budget forecasts. Committee members also raised operational questions about which systems to prioritize for sites that host large after‑hours events—football games, concerts and other gatherings—and whether Calvert was being prioritized in the vendor rollout or treated as a proactive pilot site.

Next steps: presenters said vendor briefings and additional cost estimates are expected in coming weeks; the subgroup will deliver a fuller facilities recommendation for the committee to review in January. The chair closed the item by asking staff to return with budget‑level figures and clearer staffing proposals.