68,465 docs · 699,649 pages · 88,897 facts · as of 2026-07-30

Record D-4114 · nsa_report

21st-quarterly-report.pdf

oaklandca · 1.1 MB · 89 pages extracted · 65 facts cite this document · retrieved 2026-07-15 · original location · open the PDF

Figures extracted from this document

NSA Task 1 compliance status0compliance_status2015-05-04p.86
NSA Task 13 compliance status1compliance_status2015-05-04p.88
NSA Task 16 compliance status1compliance_status2015-05-04p.29
NSA Task 18 compliance status1compliance_status2015-05-04p.31
NSA Task 2 compliance status1compliance_status2015-05-04p.11
NSA Task 2.1 compliance status1compliance_status2015-05-04p.10
NSA Task 2.2 compliance status1compliance_status2015-05-04p.10
NSA Task 2.3 compliance status1compliance_status2015-05-04p.11
NSA Task 20 compliance status1compliance_status2015-05-04p.34
NSA Task 20.1 compliance status1compliance_status2015-05-04p.32
NSA Task 20.2 compliance status1compliance_status2015-05-04p.33
NSA Task 20.3 compliance status1compliance_status2015-05-04p.33
NSA Task 20.5 compliance status1compliance_status2015-05-04p.34
NSA Task 20.6 compliance status1compliance_status2015-05-04p.34
NSA Task 24 compliance status1compliance_status2015-05-04p.38
NSA Task 24.1 compliance status1compliance_status2015-05-04p.36
NSA Task 24.2 compliance status1compliance_status2015-05-04p.37
NSA Task 24.3 compliance status1compliance_status2015-05-04p.37
NSA Task 24.4 compliance status1compliance_status2015-05-04p.37
NSA Task 24.9 compliance status1compliance_status2015-05-04p.37
NSA Task 25 compliance status1compliance_status2015-05-04p.42
NSA Task 25.1 compliance status1compliance_status2015-05-04p.40
NSA Task 25.2 compliance status1compliance_status2015-05-04p.41
NSA Task 25.3 compliance status1compliance_status2015-05-04p.41
NSA Task 25.4 compliance status1compliance_status2015-05-04p.41
NSA Task 25.5 compliance status1compliance_status2015-05-04p.42
NSA Task 25.6 compliance status1compliance_status2015-05-04p.42
NSA Task 26 compliance status1compliance_status2015-05-04p.45
NSA Task 26.2 compliance status1compliance_status2015-05-04p.44
NSA Task 3 compliance status1compliance_status2015-05-04p.13
NSA Task 30 compliance status1compliance_status2015-05-04p.46
NSA Task 33 compliance status1compliance_status2015-05-04p.49
NSA Task 34 compliance status0.5compliance_status2015-05-04p.56
NSA Task 34.1 compliance status1compliance_status2015-05-04p.50
NSA Task 34.2 compliance status1compliance_status2015-05-04p.51
NSA Task 34.3 compliance status0.5compliance_status2015-05-04p.55
NSA Task 35 compliance status1compliance_status2015-05-04p.57
NSA Task 35.3 compliance status1compliance_status2015-05-04p.57
NSA Task 35.4 compliance status1compliance_status2015-05-04p.57
NSA Task 37 compliance status1compliance_status2015-05-04p.59

…and 25 more in the API.

Extracted text

· page 67 of 89 · · see this page in the PDF

Twenty-First Quarterly Report of the Independent Monitor for the Oakland Police Department May 4, 2015 Page 66 The Department is also in the process of developing IPAS2, which is a new data system for use in the risk management process. Work has proceeded over this reporting period and, although there were organization problems associated with one vendor, those have been resolved. During our most recent site visit, the Department held a project overview meeting of IPAS2 stakeholders. The major vendor Microsoft Corporation provided the overview. Although the agenda was quite limited, it did seem clear that the technological aspects of the project are on target. Microsoft presented a plan highlighting four expected stages in the process, although no content for these stages was on the presentation slide or in its description. The vendor expects an 11-month time period to completion. When compared with the work on the technology, the Monitoring Team is less sanguine about developments around the expected use and value of the new system for Department management. That is to say, the attention to technological concerns is not matched by the corresponding attention to the potential value of the system for risk reduction in the Department. Repeating here what we noted in the last report: An important step in this process will be to formulate key questions so that they may be captured in reports through the new system. Such reports might include a Department analysis of officers repeatedly meeting thresholds, and identification of high productive officers who do not regularly exceed risk thresholds, as well as analyses of low performing officers. There should be a process for systematically considering the questions the risk management process should be answering and for designing the appropriate reports for the new system. That will allow the Department to take advantage of the capabilities of the new system for accomplishing things the last generation database could not. The examples above are suggested only as illustrations. A broad set of question should be formulated at this time. In fact, during the discussion at the IPAS2 stakeholders meeting, several attendees offered additional examples in this area. It would be desirable to have a systematic process in place to address these matters of use. That process would run parallel to the technology developments on the project. During the stakeholders’ meeting, the Department noted its plans to form a separate committee to address the critical issues regarding use of the system. The makeup of this committee, its process, and its products will be of interest to the Monitor. The Department’s commitment in this area, as well as the City’s, reflects recognition of the importance of the risk management process as outlined in the NSA. As development and implementation moves forward, it would be useful to look beyond the processes associated with the earlier system and toward broader questions as to how IPAS2 can more effectively support the management of the Department. As in previous reports, we have continued our examination of the stages of the PAS process consistent with this Task. We examined the threshold analyses that were performed for the period of October 1, through December 31, 2014. This included a review of peer-based threshold analyses completed by the PAS Administration Unit and the identification of officers meeting the single-event threshold.