CCMS banner

Justice Partner Outreach

Adopting Data Exchanges

Adopting the data exchanges is essential for justice partners who want to exchange data electronically with the courts. As CCMS is deployed and adopted by the courts, justice partners will need to modify and test their systems to provide and consume data to ensure that integrations with the courts still exist.

Successful replacement of existing integrations is critical to the success of the deployment and the entire project. In addition to being either NIEM- or CCMS XML-compliant, the data exchanges and the ISB offer:

  • Standard, predefined rules and content requirements for exchanging information between justice partners and the courts;
  • Reliable, efficient submission of and access to information with the courts;
  • Use of standard proven technologies to exchange information;
  • A way to manage technological incompatibilities; and
  • Support of system-to-system exchanges and the portal for direct query.

Preparing to Adopt the Data Exchanges

One of the challenges justice partners will face during the deployment of CCMS will be replacing the current local integrations to the legacy court case management systems.

For this deployment to be successful, your agency will need to perform many tasks associated with discovery, design, development, implementation, and testing. The tasks from design through testing need to be performed on your own systems, adapters, and integrations/Enterprise Service Bus (ESB) and by working with the AOC and its deployment vendor. These tasks are identified below in two phases.

A discovery phase, during which you will:

  • Understand the AOC's deployment schedule (once the deployment vendor is selected and the schedule is published);
  • Understand the integration strategy of data exchanges;
  • Identify the technical capabilities of your agency or county to implement the exchanges using the technology being deployed by the AOC (e.g., messaging and Web services);
  • Identify the following resources to implement data exchanges:
    • Staff resources with subject matter expertise about your agency's business;
    • Technical staff to support the technology;
    • Funds to make the necessary changes to existing information management systems such as records management system (RMS), probation system, or jail and inmate management system (JMS/IMS) software applications; and
    • Funds for adapter and data transformation design, development, and deployment, and possible middleware/ESB deployment requirements.
  • Obtain approval for the fiscal and staff resources from agency heads, county boards of supervisors, or city councils; and
  • Develop project plans to deploy the exchanges.

The design, development, implementation, and testing phase tasks include:

  • Forming internal project teams;
  • Working with the AOC and its deployment vendor to identify modifications and additions to the existing data exchanges;
  • Designing, developing, implementing, or modifying in-house systems;
  • Testing systems after modifications are made; and
  • Testing data exchanges and conducting end-to-end testing with CCMS.

A challenge for courts leading the deployment for their justice partner agencies is to execute the discovery phase and complete a high-level scope of the system, adapter, and middleware/ESB changes. The outcome of this phase will be helpful to secure a budget to implement the changes in coordination with the CCMS deployment. Information from the discovery phase will provide you with the data that is necessary to make changes to your system.

To help you prepare, we have developed a Local Integration Assessment Methodology (LIAM) with the AOC's deployment vendor. A scaled-down version, LIAM "Light," has been created to allow for a quick assessment of your local integrations.

To get a copy of the LIAM Light and its templates, click the following links:

LIAM Light
Appendix D. Sample Data Collection Tool
Appendix E. Phase II Local Integration Assessment Template
Appendix F. Phase II Key Integration Attributes Template
Appendix G. Phase III Desired Integration Capabilities