Print Version - Arizona Judicial Department

More documents

Recommendations

Info

ELECTRONIC FILING PROJECT GOALS AND ACCOMPLISHMENTS Electronic Filing or “e-filing” is a composite project that makes use of portions of other individual projects necessary to enable filing of documents and data into courts. E- Filing in courts stems from adoption of the Uniform Electronic Transactions Act (UETA) by Arizona (A.R.S. 44-7001) to facilitate and promote commerce and governmental transactions by validating and authorizing the use of electronic contracts, records, and signatures. AZTurboCourt is the Court’s designated statewide e-filing system. AZTurboCourt’s main components include the Electronic Filing Service Provider (EFSP), Electronic Filing Manager (EFM), and an optional Clerk and Judge Review application for use with case management systems (CMS). The EFSP (described in detail in the Internet Public Interactive Service section of this document) enables users to interact with the e-filing system described in this section. The EFM stores and transmits case file information to and awaits, records, and communicates responses from the destination or “target” case management system. The Clerk and Judge Review application enables clerks of the court to accept or reject case file submissions. Back-end facilities keep track of registered users, filed documents, reviews within the court, and cases available to be viewed by the public. Related projects described in prior plans include court-to-court records transfer (C2C) and justice partner filings on criminal cases into the Arizona Supreme Court and Court of Appeals Division One (ACE). ACE was retired in 2010 after AZTurboCourt was configured to accept Arizona Supreme Court and Court of Division I initial and subsequent case submissions. The AZTurboCourt technical design diagram (below) highlights the various components that are either dedicated to the e-filing system or play a role in the e-filing system’s operation. Some of the components highlighted also support non-e-filing applications and are part of the shared services infrastructure. The EFSP, EFM, and Clerk/Judge ARIZONA JUDICIAL BRANCH | INFORMATION TECHNOLOGY STRATEGIC PLAN: 2013-2015 146
Review functions (and their corresponding databases) are dedicated to supporting efiling services. The EFSP represents the AZTurboCourt “store front” or customer frontend. The EFM and Clerk/Judge Review components represent the back-end components that support court processes. Individual users of the AZTurboCourt e-filing system (e.g., case parties, attorneys, document preparers, law enforcement agencies) only have direct access to the EFSP portion of the e-filing system. The EFSP then facilitates the requisite communications to and from the EFM. Also facilitating communications to the EFM are the target CMSs. The target CMSs receive information from and return information to the EFM via various “middleware” components, namely IBM MQ and the AOC’s Central Case Index (CCI) and Central Document Repository (CDR). IBM MQ transports/routes messages between the EFM and target CMSs. The CCI and CDR maintain either the location of successfully filed case documents or copies of actual case documents. The CCI-CDR environment serves two essential purposes. First, they provide a central location through which users of AZTurboCourt can quickly locate and retrieve secondary copies of the official court record. Second, the combined systems mitigate the need for direct access to the target CMSs. This design approach significantly reduces AJIN network traffic and system overhead on each of the target CMSs. AZTurboCourt Logical Design Diagram Revised 6/24/2010 8:24:17 AM Filers Clerks Internet HTTP/HTTPS EFSP Components Self-Help Portal EDP – Services Infrastructure Document Integrity Manager Court Profile – Configuration Manager EDR – Stats & Financial Reports EDCS – Customer Support Clerk Review EFM Components e-Filing Component XML Generation Core Transport Component Transport Core EFSP Confirmation Caller Core EFSP E-Filing Confirmation Generator EFM Confirmation Caller Core Zone 1 DMZ – Web Servers Zone 2 DMZ– Application Gateway Firewall Zone 3 – AOC/AJIN Network AZTurboCourt Primary DBMSs Primary DBMSs Filing Assembling Filing Review Astaro Security Gateway 525 Accepts Port 80 Connections; Translates to Port 8080 to Web Server Secured Replication Stores Statewide ESB – Virtual Court Record MDE ROAM/CCI Secondary DBMSs Filing Assembling Filing Review App Server Interface Points to Internet (AZTurboCourt.Gov Web Server) OnBase App/Web Server Unity & DTM B2 C2 CCI-App C6 C4 CDR DBMS AJIN Intranet AZTurboCourt Filing Assembly MDE EFSP App Server With Host IDS, Clerk Review, Merchant Interface Local Court System Environment – Court Record MDE ARIZONA JUDICIAL BRANCH | INFORMATION TECHNOLOGY STRATEGIC PLAN: 2013-2015 147 C3 B1 or C1 B3 or C5/C7 IBM MQ Opt: Non-CDR Court Opt: DTM A1. RecordFiling A2. NotifyDocketingComplete (MQ to/from CMS) B. GetCase (MQ to/from CCI API) C. GetDocument (MQ to/from CCI API) OTC Scanner Clerk Review Court CMS A1. RecordFiling / A2. NotifyDocketingComplete Local EDMS Firewall AZTurboCourt Filing Review MDE ActiveMQ EFM App Server IBM MQ Client
Page 1 and 2:
FISCAL YEARS 2013—2015 ARIZONA JU
Page 3 and 4:
ARIZONA JUDICIAL BRANCH INFORMATION
Page 5 and 6:
are now focusing, in cooperation wi
Page 7 and 8:
Creation of standardized processing
Page 9 and 10:
information requires coordination o
Page 11 and 12:
I. INTRODUCTION BACKGROUND The Ariz
Page 13 and 14:
justice history files. Being centra
Page 15 and 16:
CHAIR HON. ANDREW HURWITZ Vice Chie
Page 17 and 18:
COURT AUTOMATION COORDINATING COMMI
Page 19 and 20:
CHAIR ANDREW HURWITZ Vice Chief Jus
Page 21 and 22:
Justice 20/20: A Vision of the Futu
Page 23 and 24:
III. JUDICIAL BRANCH VISION We must
Page 25 and 26:
objective data with the risk level
Page 27 and 28:
1-B SIMPLIFYING AND ENHANCING SYSTE
Page 29 and 30:
GOAL 2 MAINTAINING A PROFESSIONAL W
Page 31 and 32:
GOAL 3 IMPROVING COMMUNICATIONS Pub
Page 33 and 34:
Review the current processing of do
Page 35 and 36:
5-B MODERNIZING THE ATTORNEY ADMISS
Page 37 and 38:
Determine the allocation of availab
Page 39 and 40:
Improved effectiveness in jury mana
Page 41 and 42:
STRATEGIC TECHNOLOGY PROJECT ALIGNM
Page 43 and 44:
VI. FISCAL YEAR 2012 ACCOMPLISHMENT
Page 45 and 46:
PROGRAM DESCRIPTION FY 2012 AJIN EN
Page 47 and 48:
PROGRAM DESCRIPTION FY 2012 ARIZONA
Page 49 and 50:
PROGRAM DESCRIPTION FY 2012 ENTERPR
Page 51 and 52:
PROGRAM DESCRIPTION FY 2012 STATEWI
Page 53 and 54:
PROGRAM DESCRIPTION FY 2012 ACCOMPL
Page 55 and 56:
PROGRAM DESCRIPTION FY 2012 EDMS El
Page 57 and 58:
PROGRAM DESCRIPTION FY 2012 automat
Page 59 and 60:
Pima Courts Pinal Courts Clerk’s
Page 61 and 62:
VII. CURRENT ENVIRONMENT ANALYSIS H
Page 63 and 64:
ARIZONA JUDICIAL BRANCH INFORMATION
Page 65 and 66:
need to balance the immediate need
Page 67 and 68:
BACKGROUND The Judicial Branch is d
Page 69 and 70:
IMPACTS The impact is widespread. E
Page 71 and 72:
First-level support assists court p
Page 73 and 74:
CENTRALIZED HELP DESK Improved ove
Page 75 and 76:
BACKGROUND The digital world is bec
Page 77 and 78:
STRATEGIC ALIGNMENT BUSINESS VALUE
Page 79 and 80:
BACKGROUND As courts enter the real
Page 81 and 82:
STRATEGIC ALIGNMENT BUSINESS VALUE
Page 83 and 84:
BACKGROUND The courts embarked on t
Page 85 and 86:
to proceed with development using t
Page 87 and 88:
DEPENDENCIES The maintenance and c
Page 89 and 90:
een expanded to accept an XML data
Page 91 and 92:
Improved quality of service to the
Page 93 and 94:
BACKGROUND Courts are following ind
Page 95 and 96:
output a stream of digital data. An
Page 97 and 98:
ELECTRONIC CASE FILING Extend fili
Page 99 and 100: Background In addition to supportin
Page 101 and 102: Provided project milestone reports,
Page 103 and 104: IX. INFORMATION TECHNOLOGY STRATEGI
Page 105 and 106: STRATEGIC PROJECTS BY OBJECTIVE Tra
Page 107 and 108: A Description section describes the
Page 109 and 110: TECHNOLOGY STRATEGIC PROJECTS Elect
Page 111 and 112: created basic infrastructure and bu
Page 113 and 114: STRATEGIC PROJECTS UTILITY ENHANCEM
Page 115 and 116: SUPPORT SERVICES PROVIDED: An aver
Page 117 and 118: design sessions. Training staff spe
Page 119 and 120: PROJECT GOALS Provide specific tra
Page 121 and 122: impact. TAC created a survey tool t
Page 123 and 124: PROJECT GOALS COMPUTER/TABLET REFRE
Page 125 and 126: PROJECT GOALS CORE SOFTWARE & SUPPO
Page 127 and 128: 1. Automated validation tables (AVT
Page 129 and 130: o Migrated current APETS software t
Page 139 and 140: The data collection mechanism for t
Page 141 and 142: PROJECT DESCRIPTION This project re
Page 143 and 144: SNAPSHOT CLASS STATUS RISK Utility
Page 145 and 146: PROJECT GOALS ELECTRONIC DOCUMENT M
Page 147 and 148: Enhancement On-going Medium Frontie
Page 149: during the workday by storing image
Page 153 and 154: Enable court users and/or the CMS i
Page 155 and 156: CENTRAL CASE INDEX (CCI) Began uti
Page 157 and 158: electronic filing submissions. The
Page 159 and 160: filing “front door,” a single e
Page 161 and 162: solution. Discussions were held abo
Page 163 and 164: Inside the court system, the issue
Page 165 and 166: SNAPSHOT CLASS STATUS RISK Utility
Page 167 and 168: PROJECT GOALS INFRASTRUCTURE MAINTE
Page 169 and 170: Continued to expand hardware and ap
Page 171 and 172: Firewalls and security monitoring e
Page 173 and 174: Create a single governance structur
Page 175 and 176: then printed and delivered, or soon
Page 177 and 178: PROJECT GOALS JOLTSAZ NEXT GENERATI
Page 179 and 180: PROJECT GOALS JUDGE’S AUTOMATION
Page 181 and 182: ARIZONA JUDICIAL BRANCH | INFORMATI
Page 183 and 184: Produced a couple of ADRS training
Page 185 and 186: PROJECT GOALS JUSTICE WEB INTERFACE
Page 187 and 188: PROJECT GOALS LIMITED JURISDICTION
Page 189 and 190: The existing case management system
Page 191 and 192: Increase backlog collections by re-
Page 193 and 194: Courtesy notices Delinquency notic
Page 195 and 196: The Limited Jurisdiction Standardiz
Page 197 and 198: These projects are planned to dovet
Page 199 and 200: Began work on the core architectura
Page 201 and 202:
PROJECT GOALS STATEWIDE E-WARRANT S
Page 203 and 204:
PROJECT GOALS TECHNICAL TRAINING PR
Page 205 and 206:
Various other products that are use
Page 207 and 208:
APPENDIX - A. HARDWARE ENVIRONMENT
Page 209 and 210:
APPENDIX - B. SOFTWARE ENVIRONMENT
Page 211 and 212:
SOFTWARE APPLICATION Child Support
Page 213 and 214:
Software Application Vendor/Interna
Page 215 and 216:
APPENDIX - C
Page 217 and 218:
ARS Arizona Revised Statutes AS/400
Page 219 and 220:
E-COURT An ad hoc subcommittee of t
Page 221 and 222:
JPIJ Judicial Project Investment Ju
Page 223 and 224:
SSIA SQL Server Integration Service
show all

Print Version - Arizona Judicial Department

Create successful ePaper yourself

Delete template?

Save as template?