CASE STUDY

The Challenge

From a technical standpoint, many challenges existed. The team needed to provide prototypes of the data, based on existing and developing requirements. Major requirements changes were put in place. Initial web hearing questions were going to be a simple “data dump.” However, as the project moved forward, new, and important dynamic features were identified and became important to the final requirements. All these changes presented major technical challenges for the teams. Before the settlement agreement was finally locked down, requirements were always changing. How that data was eventually to be presented, was also changing.

Therefore, quick, creative, and technically challenging solutions were needed. The Enqbator team not only had to work creatively, but also collaboratively, as different groups were involved in the process, from IT and technical teams to attorneys and administrators. All the way up to the final project being put into place, Enqbator needed to be open to innovative ideas and ready to devise and quickly implement effective new methods and solutions. All aspects of this project were very new. No other court system in the country had developed such a unique solution, so the pressure was on to produce a complete and effective process.

The Solution

Working closely with the team at the 36th District Court, Enqbator put into place a solution that satisfied all initial requirements and discovered new and creative ways to solve some unforeseen needs. The partnership between Enqbator and the court was a long and trusted one. This enabled all parties to take the time to look beyond only what was first needed and ultimately provide a more complete and better final product. Since this was a solution never used in the industry, it allowed both teams to explore the best ways to get the job done. Enqbator listened to the court’s needs and got to work. The main part of the solution was the integration and creation of five important reports.

Data for these reports was pulled from the court’s existing case management system. Creative integrations were created to also pull data from the Power BI application, JIS (Judicial Information System), and the newly created web hearing questionnaire. These “web hearing questions” are now a pivotal part of the arraignment process and must be answered for each case by the Judicial Officer. That input from the Judicial Officer was then integrated into the Power BI reports, which were also pulling in information from the JIS. Integrating all of this was extremely necessary to help determine what report a certain case would fall under.

The Result

In the end, the solution implemented, and the data provided solved a major challenge facing the court system. The work done by Enqbator and the technical Docket Management team at the 36th District Court proved both effective and transformational. The final data made available through the reports assured all involved that the time spent was necessary. All reports are doing exactly what was intended, helping to improve the ACLU’s concerns with existing processes. The current process is stable and working extremely well. As a result of all the challenging work and the partnerships created, the system put into place will help make the courts of Detroit a more equitable and more effective system for all.