1. LEGAL PAPERLESS SYSTEM
Overview of State Implementation of San Diego’s Legal Paperless System (LPS)
Jeff Grissom, San Diego DCSS Director
Erik Welton, San Diego Supervising Child Support Attorney
Darius Fattahipour, San Diego Applications Manager

2. GENERAL INFORMATION AND LATEST DEVELOPMENTS
Terminology
CAT (Child support Application Tools)
LPS (Legal Paperless System)
Dashboard (queue management module)
Calendar (court calendar module)
Production environment went live on State servers on March 23rd for San Diego and Napa
Napa training in late April and scheduled for court use in May

3. GUIDING PRINCIPLES OF DESIGN AND IMPLEMENTATION
Leveraging existing systems to make each step more efficient
Maximize input from staff and flexibility for users – business practice considerations
Ability to litigate as quickly as with paper files
Minimize paper file conversion effort – San Diego is 97.7% paperless as of 2/2015

4. SYSTEM WORKFLOW

5. LPS DEMO – 3 MAIN SCREENS Legal Paperless Calendar Facesheet
List of cases on calendar that day – replaces the paper calendar attorneys would notate
Facesheet
Details of a specific case – parties’ names, issues before the court, CSE data, history of court hearings
Issue Screen
Detailed preparation notes by the attorney and meet and confer notes

6. TECHNICAL HIGHLIGHTS
Integrated with CA Central login (Active Directory)
Single sign-on, but local control of user access levels
Courtroom IT Infrastructure
Connectivity in the courtroom (hard wired or WiFi)
Dual-Screen Monitors
Tablets for mobility and additional screen
Systems Integration
Data exchange between Superior Court Calendaring System
CSE data from the Data Repository
Queue Management System Integration – Real-time updates
Management Reports

7. TRAINING CONSIDERATIONS
User interface designed to be easily understood and learned
User Guides are largely descriptions of the screens and the functionality
Video Tutorials module – short videos on navigation and functionality
Access to a Test Environment
Each test environment specific to each LCSA
State DCSS Training steps
Train the trainers, followed by observation of Napa training

8. SYSTEM REQUIREMENTS AND MAINTENANCE
CAT architected in Software as a Service (SAAS) model – no local LCSA infrastructure (servers, etc.) required
Single-sign On (SSO) using existing LCSA Secure site credentials
“CAT Configuration Checklist” will be provided to each LCSA for onboarding
State DCSS Help Desk
Account Administration (i.e. password resets)
Report System Issues