Appendix_J_16_-_Interface_Descriptions.pdf

ID System Current / Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

Go-Live

Outbound from CMS

A near real time electronic interface between the Courts’ existing case management system and the Abila MIP Financial System. This Outbound leg of the interface transmits Accounts Payable transactions receipted in the CMS to the Abila MIP Financial System where an AP record is generated, a check number is assigned and a return transaction is triggered back to the CMS.

Must Have

Inbound to

CMS

A near real time electronic interface between the Courts’ existing case management system and the Abila MIP Financial System. The Inbound leg of the interface receives data such as the Check Number from the Abila MIP Financial System that is populated on the case record in the CMS.

Must Have

Outbound from CMS

A near real time electronic interface between the Adult Criminal and Domestic Violence operational units and the D.C. Criminal Justice Coordinating Council (CJCC). This leg of the interface facilitates the exchange of Court case data comprised of party, docket, charge, sentencing, alerts, etc. with approximately 12 participating agency partners through a robust outbound data schema. All Court Inbound as well as Outbound interface transactions transverse the CJCC’s JUSTIS platform, which functions as a “hub” between the Court and participating agency partners.

Must Have

Inbound to

CMS

A near real time electronic interface between the Adult Criminal and Domestic Violence operational units and the D.C. Criminal Justice Coordinating Council (CJCC). This leg of the interface supports the exchange of arrest and charging data along with associated documents from the Metropolitan Police Department (MPD), U.S. Attorneys Office, the Office of the Attorney General of D.C. to the Court. Highly sensitive reports from the Pre-trial Services Agency are also exchanged with the Court thru this interface. All Court Inbound as well as Outbound interface transactions transverse the CJCC’s JUSTIS platform, which functions as a “hub” between the Court and participating agency partners.

Must Have

Outbound from CMS

Similar to the Adult Criminal interface that flows through the CJCC JUSTIS platform, this near real time bi-directional interface facilitates the exchange of arrest and charging data and documents between the Court, MPD, and the OAG. In addition to supporting the exchange of required data to initiate juvenile delinquency matters with the Court, this interface serves to update existing juvenile social file information maintained by the Court Social Services Division of the Court.

Must Have

Inbound to

CMS

Interface between the Family Court and Child & Family Services (CFSA).

Interface includes data as well as images. The scope of this interface covers case initiation of juvenile Abuse & Neglect cases as well as subsequent (post case initiation) submittals. This transaction facilitates the transfer of social worker reports from the CFSA FACES system to the CMS. These subsequent filings are processed through the interface platform generating docket entries on existing cases in the CMS. This interface is facilitated using Secure File Transfer Protocol.

Must Have

Appendix J.16 - Interface Descriptions

Near real-time Offeror

Near real-time Offeror

Near real-time Offeror1

SQL ServerCJCC Internally developed by

CJCC

CurrentCJCC's JUSTIS System - Adult2

Abila's MIP Financial System

SQL ServerCJCC Internally developed by

CJCC

Current3 CJCC's JUSTIS System - Juvenile

Current COTS On-premises SQL Server

Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

Go-Live

Appendix J.16 - Interface Descriptions

Outbound from CMS

A near real bi-directional interface between the Court and MPD for exchange of data relative to the issuance of bench warrants, Domestic Violence stay away orders associated with adult criminal and domestic violence matters. Following the creation of warrants alerts in the case management system a notification is sent thru the CJCC JUSTIS platform to MPD’s eAgent application, which in turn updates the FBI NIC system with the appropriate data. The MPD system sends back a confirmation transaction following successful service of the warrant. An additional component of this interface is a separate set of transactions that support the exchange of juvenile custody order information with the eAgent system. These transactions are not updated to the NIC system.

Must Have

Inbound to

CMS

A near real bi-directional interface between the Court and MPD for exchange of data relative to the issuance of bench warrants, Domestic Violence stay away orders associated with adult criminal and domestic violence matters. Following the creation of warrants alerts in the case management system a notification is sent thru the CJCC JUSTIS platform to MPD’s eAgent application, which in turn updates the FBI NIC system with the appropriate data. The MPD system sends back a confirmation transaction following successful service of the warrant, which in turn updates the status of the warrant record in the CMS. An additional component of this interface is a separate set of transactions that support the exchange of juvenile custody order information with the eAgent system. These transactions are not updated to the NIC system.

Must Have

Outbound from CMS

An internal interface between the Court’s case management system and the Court Social Services Division (CSSD) that facilitates the exchange of information relative to the management and monitoring of juveniles under the supervision of the CSSD. Select updates in the JPCM system trigger updates back to the court case management system to update related juvenile delinquency and truancy cases in the form of identity creation, demographic changes scheduled events, tickers and associated docket entries. The data transfer from CourtView to JPCMS is facilitated through courts enterprise data warehouse to ensure performance and for securely transferring data between Case Management System and the JPCMS cloud database using Oracle Data Integrator and oracle ewallet for encrypting the data.

Must Have

Inbound to

CMS

An internal interface between the Court’s case management system and the Court Social Services Division's (CSSD) Juvenile Probation case management system (JPCMS) that facilitates the exchange of information relative to the management and monitoring of juveniles under the supervision of the CSSD.

The Inbound exchange between the JPCMS and the Court CMS ensures the two systems remain synchronized when parties are created or updated in the JPCMS. This leg of the interface also includes the capability to call CMS web services for the creation of docket entries on existing cases including document images.

Must Have

Near real-time Offeror

OfferorNear real-time4 CJCC's JUSTIS

System - Warrant Current Internally developed by

CJCC

CJCC SQL Server

Juvenile Probation Case

Management

(JPCMS)

5 SQL Server SaaS hosted in MS Azure

COTSCurrent

Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

Outbound from CMS

At minimum, notices of appeal, the appellate package (which should include all filings, exhibits (lodged or admitted), transcripts, jury notes, case-related communications between the Court and counsel (generally emails)), and any of materials later added to the Superior Court CMS. The appellate package will be a large electronic package including all case documents, docket, transcripts, exhibits, recordings, and any information relating to the appealed case.

Exchange shall include the ability to send notifications to judge panels and defined DCCA staff regarding Superior Court filings and any case activity applicable to an appealed case.

Must Have

Inbound to

CMS

At minimum, orders (dismissing appeal, granting/denying a stay, granting/denying writs of mandamus & resolving the case on the merits), MOJs, opinions, and mandates. C-Track should transmit case information, including case numbers, attorney names, etc. to the Superior Court upon cases being originated in the Court of Appeals (e.g. small claims, select criminal cases).

Unique appeals case numbers should be transmitted on all exchanged appellate cases

Must Have

Outbound from CMS

An electronic interface acknowledgement of the receipt of Bar information transmitted in the Outbound leg of the interface process. Nice-to-Have

Inbound to

CMS

An electronic interface that provides the CMS with new and updated information on practicing attorneys in the District of Columbia. The Court would expect to receive notification of attorneys not in good standing with the Bar.

Nice-to-Have

Outbound from CMS

Once per day

At the conclusion of each business day the Court compiles an electronic listing of future hearing dates for Abuse and Neglect cases and transmits it to the Child and Family Services Agency’s FACES case management system.

Must Have

Inbound to

CMS

Batch process twice per day

Interface between the Family Court and Child & Family Services (CFSA).

Interface includes data as well as images. The scope of this interface covers case initiation of juvenile Abuse & Neglect cases as well as subsequent (post case initiation) submittals. This transaction addresses initiation of Abuse & Neglect cases including the automated generation of the Complaint based on the data contained in the transaction. This interface is facilitated using Secure File Transfer Protocol.

Must Have

Outbound from CMS

Interface between the Family Court and Child & Family Services (CFSA).

Interface includes data as well as images. The scope of this interface covers case initiation of juvenile Abuse & Neglect cases as well as subsequent (post case initiation) submittals. This transaction facilitates the selection of judicial order documents and associated meta data from the CMS to the CFSA FACES system. This interface is facilitated using Secure File Transfer Protocol.

Must Have

Inbound to

CMS

Interface between the Family Court and Child & Family Services (CFSA).

Interface includes data as well as images. Must Have

Offeror

Batch process twice per day

Offeror

Near real-time Offeror

Near real-time Offeror

CFSA's FACES System

COTS On-premises

DCCA's C-Track Case Management

System

DC BarTBDFuture District of

Columbia Bar Association

CFSA's FACES System9 TBDCFSA

Internally developed by

CFSA

Current

TBD

Future

CFSA

Internally developed by

CFSA

Current

SQL Server

TBD

Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

10 CFSA's FACES System Current

Internally developed by

CFSA

CFSA TBD Outbound from CMS

Batch process twice per day

Offeror

Interface between the Family Court and Child & Family Services (CFSA).

Interface includes data as well as images. The scope of this interface covers case initiation of juvenile Abuse & Neglect cases as well as subsequent (post case initiation) submittals of status reports from case and social workers. In addition to incoming information from CFSA, this interface includes an outbound capability for the Court to transmit participating judicial orders to CFSA’s FACES case management system.

Must Have

11 CourtSmart Audio Recording System Current COTS On-premises SQL Server Inbound to

CMS

Near real-time Offeror

Interface that will allow CourtSmart digital recordings to be associated to cases in the CMS. Users shall be able to access and listen to a recording on-demand from the CMS docket, eliminating the need for users to exit the system. In addition to access and playback, the recordings will have the capability to annotate ("tag") the case and trigger docket entries based on events such as case was called, witness appeared, etc. While not required, a real-time interface allowing users to listen to the hearings live from the CMS is desired.

Must Have

ProBonoNet's

Document Assembly System

Future COTS SaaS hosted in MS Azure

TBD Inbound to CMS TBD Offeror

A uni-directional interface between the interactive interview/document assembly hosted platform solution and the CMS that facilitates the exchange of meta data and documents relative to new case initiations as well as post-case initiation activities.

Nice-to-Have

District of

Columbia Sex Offender Registry

Future TBD TBD TBD Inbound to CMS TBD Offeror

Interface between District of Columbia Metropolitan Police Department Sex Offender Registry and the Court. Exchanged information must include party name and sex offender classifications. The Court uses this information to assemble a complete profile of case participants for use in judicial decision making and offering of Court services.

Nice-to-Have

District of

Columbia Vital Records

Future TBD TBD TBD Inbound to CMS TBD Offeror

Interface between District of Columbia Department of Health Vital Records and the Courts. Exchanged information must include birth and death certificates. The Court uses this information in Probate, Family and Adoption proceedings, as well as to update participants records.

Nice-to-Have

District of

Columbia Division of Motor Vehicles

Future TBD TBD TBD TBD TBD Offeror Interface between the Court and DMV that provides information relative to case dispositions associated with traffic and drug charges. DMV uses this information to suspend licenses.

Must Have

16 Xerox's AgileJury System Current COTS On-premises Oracle Outbound from CMS Near real-time Offeror

Interface exchanging case information from the CMS to AgileJury. The cases to be exchanged shall only be eligible cases ready for trial and contain the case number, case type, case description, hearing time, judge and courtroom. For future expansion, the Courts may consider making this a bi-directional exchange to enable, for example, juror data from AgileJury to populate the CMS in order to facilitate juror payments and utilization analysis.

Must Have

Business Intelligence/Data

Warehouse Platform

Current Internally developed by

DCC

On-premises Oracle Outbound from CMS

Near real-time DCC

A real time internal interface between the Court’s CMS and the Enterprise Data warehouse / Oracle OBIE platform. Case Management Data is replicated to the data warehouse staging environment using SherPlex replication technology.

Data is then populated to the Courts' data warehouse near-real-time using ODI ETL tool. Subject Areas are created for all case management functional areas for end user Operational reports, Dashboards, Trend analysis and AD-hoc self service analytics.

Must Have

Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

DCSC's Docketron

Today's Court Schedule

Current N/A On-premises SQL Server Outbound from CMS

Near real-time DCC

Interface that facilitates the real-time exchange of the Court schedule from the CMS to the Courts' Docketron. Data to be exchanged includes party name, case number, hearing time, judge, building, and courtroom.

Must Have

DCSC's Digital Signage for C-10

& Other High Volume

Courtrooms

Current N/A On-premises SQL Server Outbound from CMS

Near real-time DCC

Interface exchanging the party name, hearing time, judge, and courtroom in real-time from the CMS to Digital Signage. Digital Signage utilizes several VBScript/Windows Scripting Host (WSH) scripts which will query the CMS database for data. These scripts are executed at a regular interval to generate text files to display information digitally.

Must Have www.dccourts.go v (Today's

Superior Court Cases)

Current Internally developed by

DCC

On-premises MySQL Outbound from CMS

Near real-time DCC

Interface exchanging the Court schedule in real-time from the CMS to the Courts' homepage. Data to be exchanged includes party name, case number, hearing time, judge, courtroom, and building. Data must be exchanged in a format to enable it to be searchable and filterable on the Courts' home page by party, case number, judge, and courtroom. The Courts may explore expanding this data exchange to populate future schedules and/or to enable mobile accessibility.

Must Have

21 APEX E-Lobby System Future

Internally developed by

DCC

On-premises Oracle Outbound from CMS Near real-time DCC

Interface that populate the CMS with party check-in information captured in e- Lobby. The Courts desire check-in information be used to notify the Courts' CMS users of arrivals, location of arrivals, and any missing parties for hearings.

Improved tracking and notification will help the Courts optimize scheduling, promote on-time hearings, control traffic in the court, and better assign/prepare resources for parties upon arrival (e.g. mediators and translators).

Nice-to-Have

22 Web Transcript Tracking System Current

Internally developed by

DCC

On-premises Oracle Outbound from CMS Daily DCC

A uni-directional interface between the CMS and Web Tracking System (APEX application) exchanging case hearing information. Information exchanged includes case number, hearing date, judge, court room information, and hearing categories. Data exchanges are scheduled and conducted at 6:00AM daily.

Manual transfers can be performed on-demand.

Must Have

23 Web Interpreter System Current

Internally developed by

DCC

On-premises Oracle Outbound from CMS Near real-time DCC

A uni-directional interface that facilitates the assignment of interpreter resources to court matters. This interface relies on Shareplex data replication to transfer interpreter requests, hearing date, case number, case description, language, judge, courtroom and hearing information to the Courts' internally developed Oracle APEX application where resource availability and qualifications are maintained. The interface runs daily. The Courts desire that the future exchange also include participant disabilities, special requirements, mad a timestamp. This will enable the Courts to identify time-sensitive requests and effectively distribute resources.

Must Have

24 Web Voucher System Current

Internally developed by

DCC

On-premises Oracle Outbound from CMS Near real-time DCC

A near real time interface process that automatically generates payment vouchers for attorneys as well as other individuals providing services to the Court. Triggered by the application of certain docket entries in the CMS, the interface runs nightly for Multidoor, SC-CCAN, and SC-CJA. The data fields pulled vary by interface and customer needs, but generally include case number Attorney/Mediator, appointment date or mediation date, and charge or mediation outcome.

Future

In-House / External

Hosting Location Database Direction of

Data Frequency Tentative Lead Description of Data Exchanged Priority for

25 Web Mediation System Current

Internally developed by

DCC

On-premises Oracle Outbound from CMS Near real-time DCC An uni-directional interface that uses CMS data to populate the Web Mediation System with, at minimum, case number, party names and contact information, case descriptions, and case files. The Courts use this information to assign and schedule mediators effectively.

Must Have

26 Wills System Current Internally developed by

DCC

On-premises Oracle Outbound from CMS Daily DCC

A uni-directional interface between the Wills System and the CMS. The Wills system houses all wills that have ever been filed in the District of Columbia.

Probate uses this information, and requires access to it from within the CMS.

Interface Descriptions