Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Early Intervention System topic
No spam. Unsubscribe anytime.
Police commission hears interim early intervention system, interim database founds 53 officer alerts
Summary
Police Department staff presented an interim early intervention system (EIS) built in-house that has identified 53 officers with alerts over the past 12 months and plans a July 1 rollout of interim reports while the vendor AIM works toward full implementation.
San Francisco Police Department officials told the Police Commission that an interim early intervention system (EIS) is ready to begin producing reports on officers who trigger performance indicators and that a commercial product (AIM) remains scheduled for later implementation.
Lieutenant Brown, who oversees the professional standards unit, said the interim EIS aggregates 10 indicators required under General Order 3.19 to identify members whose performance "may exhibit at-risk behaviors" so supervisors can provide non-disciplinary interventions. Analyst Jim Villanueva described an in-house analytical database he built that has been producing reports since August 2007 and can trace indicators back to 2006.
Villanueva said the interim system identified 53 officers who triggered alerts in the previous 12 months; 12 of those alerts were automatic because they involved officer-involved shootings or discharges, leaving 41 additional officers who met alert criteria absent OIS/OID cases. Brown said the department will roll out the interim EIS to bureau chiefs on July 1 and begin sending alerts and reports going back 12 months.
Officials cautioned that some associated data sources are inconsistent and require cleaning before full automation: activity-report fields in HRMS showed wildly varying counts, and some factors the general order anticipates are not currently tracked reliably. Brown said the interim database will accelerate work with the AIM vendor because it identifies data sources and tables needed for migration.
On timing for the vendor AIM product, Brown said AIM was installed on the department server in December 2007 and the vendor established VPN access in January 2008 for initial testing. The vendor's timeline provided an implementation target of January of the following year "if everything goes as scheduled," though commissioners were told the vendor would provide an updated schedule soon. Brown characterized the interim system as a working analytical tool while AIM completes data migration and design milestones.
The presentation prompted questions from commissioners about installation, data quality, and rollout confidence. Brown said the interim system will be transparent to officers, allowing them to log in and view their own data, and that supervisors will be required to review indicators for the personnel they oversee. The commission did not take a formal vote on the EIS plan during the meeting.
The commission was told the interim EIS will be used to "start looking at what type of interventions are working" and to develop metrics on interventions going forward.
