Presentation is loading. Please wait.

Presentation is loading. Please wait.

8/1/071 New Mexico Judiciary Case Management Project Steve Prisoc, Judiciary CIO.

Similar presentations


Presentation on theme: "8/1/071 New Mexico Judiciary Case Management Project Steve Prisoc, Judiciary CIO."— Presentation transcript:

1 8/1/071 New Mexico Judiciary Case Management Project Steve Prisoc, Judiciary CIO

2 8/1/072 Judiciary IT Governance Structure Supreme Court Judicial Information Systems Council Judicial Information Systems Division Administrative Office of the Courts

3 8/1/073 Judicial Information Systems Council Composition Supreme Court Administrative Office of the Courts New Mexico Bar representatives Court and IT Administration (AOC, magistrate, district and metro) Appellate Court Judge Judges (magistrate, district and municipal) Supreme Court Justice

4 8/1/074 Project Management Reporting Hierarchy Supreme Court & AOC Management Team (PMO) Client Project Manager Client Lead Business Advisor Vendor Project Manager Project Team Leaders Conversion Integration Training Business  Project Management  Coordinates activities  Manages project plan and budget  Prioritizes project issues  Evaluates all change requests  Delivers regular progress reports to executive sponsors  Responsible for communication & user relations  Escalates issues  As needed to executive sponsors  Recommends scope changes  Recommends policy/procedural changes

5 8/1/075 High-level Timeline  Phase 0 – Project Startup  Phase 1 – Pilot Implementation  Phase 2 – Additional Pilots / Early Adopters  Phase 3 – Statewide Rollout Phase 0 Phase 1 Phase 2 Year 1Year 2Year 3 Phase 3

6 8/1/076 Pilot Activities Additional (New) Enhancements Dev & Test Client feedback & non-time critical changes Review Train Team Training & Training Preparation Core Requirements Dev & Test Fit Analysis Integrations Dev & Test Configuration Initial Preparation Base Conversion & Verification Go-Live Phase OnePhase Two Configuration Review Site Preparation Site Conversion Cycles & Verification Train Go-Live

7 8/1/077 Project Activities and Responsibilities Data Conversion Modifications Integrations Configuration Training Preparation Client Preparation End User Training Support Activities Fit Analysis / Project Plan Implementation Teams BusinessConversionIntegrationTraining OwnsParticipates Owns Participates Owns ParticipatesOwns Participates Owns Participates OwnsParticipates

8 8/1/078 Data Transformation and Migration IFL Simplified Schema Validation & Verification Tools Reports Protection from application changes Odyssey Determine scope of data to be converted Develop base exports for source systems Reuse for each conversion: Validate data integrity Deal with court- specific data variances Verify Source Systems Supreme Court Court of Appeals District Court (13) Magistrate Court (53) Metropolitan Court Side by Side Business Review –Source System –Odyssey Merging of duplicate party data Business Team approval Push to Production Conversion Database Production Database

9 8/1/079 Server Architecture Design  Primary DB  The primary database server hosts the Odyssey SQL database instances for Production and Training. This server is accessed only by the web and job servers.  When possible no other external access points should be established to the primary database server.  Secondary DB  The replicated database server provides a read-only replica of the primary databases.  Job processing and public access web servers can utilize this server to eliminate load from the primary database, further protecting interactive performance.  The secondary database server can be configured for failover in either an Active-Active or Active-Passive MSCS Cluster.  Additional DB servers can be deployed for warm- standbys or other business purposes. Switches/Routers Domain Controller Firewall WAN / Internet WAN / Internet Front Side Interface HTTP HTTPS Server to Server Inter-connect

10 8/1/0710 Server Architecture Detail

11 8/1/0711 Application Statelessness  No server session affinity  Multiple load-balanced web servers  No single point of failure  Web servers do not need to be symmetrical

12 8/1/0712 Telecommunications Requirements  Clients require TCP/IP access to server via HTTP (Port 80) or HTTPS (Port 443)  T1 (1.544Mbps) = approx. 150 concurrent users  DSL (385kbps) = 38 users; (512kbps) = 50 users  56kbps courts may use MS Terminal Services

13 8/1/0713 Telecommunications Bandwidth  Testing aggregated DSL in 8 court locations  Carrizozo, Chama, Hobbs, Lordsburg, Los Alamos, Roy, Tatum, NM Juvenile Justice Center  If successful, communications speeds will increase by a factor of four to eleven times the current speeds  Statewide implementation could save up to $250,000/yr

14 8/1/0714 Judiciary IT Architecture  Judicial architecture configuration is data center centric. No clients in the data center, only servers.  Judiciary network is divided first into an Outside (public un-trusted Internet zone) and an inside (private zone).  Private zone is subdivided into multiple security zones (perimeter un-trusted zone and trusted zone),  Zones are subsequently subdivided into functional service tiers.  Devices and physical servers providing service capacity are placed in these tiers.  The Tiers imply a security boundary, (Virtual Local Area Network (VLAN), Firewall, etc.)  The design seeks to limit single points of failure.  WEB, application and database components are structured to allow individual system failures without compromising the integrity of the system at large.  The WEB and application servers are clustered and load balanced.  The database servers will be either active-active or active-passive fail-over with shared SAN storage.  Theis design uses a defense-in-depth strategy, which is a comprehensive approach for applying security throughout the infrastructure. This approach is implemented from perimeter network security to data-oriented security on internal networks.  Components include: IDP, Firewall, SSL/VPN, VLANS, and established tiers for services

15 8/1/0715 Judiciary Architecture

16 8/1/0716 JID Application Architecture

17 Proposed Business Continuity and Recovery for New Application 8/1/0717 Albuquerque will serve as a duplicate warm site via database replication for Santa Fe and Metropolitan Court Metropolitan Court will be the main site for their server cluster and SAN Santa Fe will be the primary cluster and SAN site for the Center Repository and the telecommunications hub Records and Archives in Santa Fe will serve as tape repository for Santa Fe

18 8/1/0718 JID Systems Backup Policy Summary  Backup Targets  For Linux systems this policy treats OS and user data the same. OS files include the kernel, UNIX configuration files and system binaries. User data includes files such as home directories, databases, and mail spools. OS and user data will be backed up to removable tape media on a regular basis.  Schedule  Level 0 (i.e., full) backups will occur during the defined backup window of 2:00 a.m. to 4:00 a.m. Tuesdays.  Level 1 (i.e., incremental) backups will occur during the second backup window of 2:00 p.m. to 4:00 a.m. Monday, Wednesday Thursday, Friday.  Retention  All backups will be maintained for 2 weeks, after which time the backup media can be reused.

19 8/1/0719 JID Systems Backup Policy Summary  Backup Targets  For MS Windows applications, state and user data will be backed up to removable tape media on a regular basis, according to the following schedule. User data includes files such as home directories (e.g., /home), databases. OS and user data will be backed up to removable tape media on a regular basis, according to the following schedule.  Schedule  Level 0 (i.e., full) backups will occur during the defined backup window of 2:00 a.m. to 4:00 a.m. Tuesdays.  Level 1 (i.e., incremental) backups will occur during the second backup window of 2:00 p.m. to 4:00 a.m. Monday, Wednesday Thursday, Friday.  Retention  All tape media backups will be maintained for 2 weeks, after which time the backup media can be reused.

20 8/1/0720 JID Systems Backup Policy Summary  Recovery  Users can request recovery of selected files by contacting the helpdesk or client services representative to request file restoration. This request will then be communicated to the Systems Group for file restoration.  Testing  The Backup Management Team must randomly test the recovery of user, application, and OS files and databases at least once every 6 months. A full recovery of a production server to a test system must be performed at least once per year.  Disaster Recovery  Backup media will be moved to an offsite facility the every Tuesday. In addition, the new case management application’s servers (database, web, etc.) will be replicated at the Second Judicial District in Albuquerque, which will serve as a “warm” site.

21 8/1/0721 Independent Validation and Verification  The Judiciary desires to engage in a focused IV&V process that will monitor areas of highest risk  The Judiciary will select an IV&V from statewide price agreements or GSA schedule  IV&V schedule  Identify/interview vendor candidates – 9/30/07  Execute contract on or about 12/31/07

22 8/1/0722 Procurement Strategy for Case Management  The Judicial Branch follows State procurement code policies and practices.  The Judiciary’s intent is to conduct any procurement so as to accomplish two key objectives:  get the best possible product and/or service for the Judiciary  involve the end users in procurement process to satisfy functional needs and obtain buy-in.  Purchase of servers, storage, and other hardware, related software (e.g database, desktop OS, etc.), and services (e.g. E-filing, IV&V, project management, etc.) will be done through statewide price agreements or GSA schedules.

23 8/1/0723 Procurement Strategy (continued)  Additional activities that supported the Judiciary’s due diligence included the following:  Developed a case management application requirements document – AOC business analysts conducted a gap analysis between what was in current FACTS case management application requirements for a new case management application.  Conducted major case management vendors’ client sites – Kansas, Missouri, Minnesota, Massachusetts  Conducted vendor facility site visits – sent teams to onsite assessments of JSI, ACS, Tyler and Maximus  Gathered court functional requirements from all courts – sent requirements documents to every magistrate, district and the appellate courts for review and input  Conducted court functional site visits to verify findings – organized one-day visits to magistrate and district courts in Aztec, Farmington, Carlsbad, Roy, Tucumcari, Roswell, Lovington, Las Cruces, Bernalillo, Santa Fe, Los Lunas, Albuquerque, and Bernalillo County Metropolitan Court to validate functional requirements


Download ppt "8/1/071 New Mexico Judiciary Case Management Project Steve Prisoc, Judiciary CIO."

Similar presentations


Ads by Google