Integration with a document library system and the ability to keep an all-digital court process is essential to court operations. We are neither prepared nor able to surrender our all-digital courtroom. Furthermore, it is not simply a matter losing technology enhancements and functionality. Each of our jurisdictions has made a significant investment in time and money in creating an all-digital process. Our local governments have not anticipated the loss of these programs and are not prepared to cover the costs associated to returning to a traditional, paper driven courtroom once we convert to the new CLJ CMS program.

This request is to enable the data exchange between the OCourts platform and the new managed CLJ-CMS.

The CLJ-CMS Project Steering Committee raised a concern regarding possible unmet capabilities by the Tyler suite of applications and the loss of specific business capabilities and efficiencies currently provided by locally implemented applications such as virtual/remote courts, real-time forms management and signatures, scheduling hearings by clients, financial collections, and access by various devices (smart phones, tablets, etc.). If these local capabilities are unmet by the Tyler applications, the courts will lose efficiencies that may result in manual workarounds and the need for additional staff resources.

Currently, 40 jurisdictions operate using one or more modules of the OCourts suite. OCourts has 67 electronic forms, most of which mirror the state's Pattern Forms. In order to avoid losing current functionality and the technology enhancements developed to eliminate stopgaps in the current JIS program, the courts using the OCourts program are requesting to integrate with the new Enterprise Integration Platform and External AOC API.

This change will address the functional gaps between the local applications and Enterprise Justice (Odyssey).

OCourts will connect to the External AOC API to exchange information with the managed CMS solution.

The Administrative Office of the Courts (AOC) would provide technical and business support to help local jurisdictions and their vendors to onboard locally implemented court applications to the new External AOC API system that taps into the Enterprise Justice-based CLJ-CMS system.

Note: This proposed solution analysis only covers the work at AOC and does not encompass the work or costs required by the third-party software vendor or the court staff. It will be up to the local courts to fund the third-party vendor's work to connect to the External AOC API and Enterprise Integration Platform.

This request is to enable the data exchange between the OCourts platform and the new managed CLJ-CMS.

The CLJ-CMS Project Steering Committee raised a concern regarding possible unmet capabilities by the Tyler suite of applications and the loss of specific business capabilities and efficiencies currently provided by locally implemented applications such as virtual/remote courts, real-time forms management and signatures, scheduling hearings by clients, financial collections, and access by various devices (smart phones, tablets, etc.). If these local capabilities are unmet by the Tyler applications, the courts will lose efficiencies that may result in manual workarounds and the need for additional staff resources.

Currently, 40 jurisdictions operate using one or more modules of the OCourts suite. OCourts has 67 electronic forms, most of which mirror the state's Pattern Forms. In order to avoid losing current functionality and the technology enhancements developed to eliminate stopgaps in the current JIS program, the courts using the OCourts program are requesting to integrate with the new Enterprise Integration Platform and External AOC API.

This change will address the functional gaps between the local applications and Enterprise Justice (Odyssey).

The Administrative Office of the Courts (AOC) would provide technical and business support to help local jurisdictions and their vendors to onboard locally implemented court applications to the new External AOC API system that taps into the Enterprise Justice-based CLJ-CMS system.

Note: This proposed solution analysis only covers the work at AOC and does not encompass the work or costs required by the third-party software vendor or the court staff. It will be up to the local courts to fund the third-party vendor's work to connect to the External AOC API and Enterprise Integration Platform.

OCourts will connect to the External AOC API to exchange information with the managed CMS solution.

This request was authorized by Vonnie Diseth on September 8, 2022.