County Justice Information Exchange Project ~ CJIEP

Transcription

1 Architectural Solution and Technical Requirements Document County Justice Information Exchange Project ~ CJIEP Detailed System Design Version 1.54

2 Table of Contents 1 Introduction Purpose Scope Organization System Overview Web Service Consumer Web Service Provider UDDI Design Considerations Assumptions and Dependencies Guidelines System Design Strategies WS-I Basic Profile Messaging ( SOAP / HTTP ) WSDL UDDI XML and XML schema Detailed System Design State Diagram Activity Diagram Collaboration Diagram Web Service Consumer Identifying the web service(s) required for the exchange Deployment Web Service Provider UDDI UDDI Implementation WSDL Hardware and Software Specification Detailed Exchange Specification Bindover Conversation, Exchange Number Bind case over Affidavit of Probable Cause Message Bail / Bond Message Criminal Complaint Docket Transcript Sentencing Conversation, Exchange Number Provide Parole Decision Parole Order Sentencing Conversation, Exchange Number Report Probation Sentence Court Order Sentencing Conversation, Exchange Number Inform that subject s non-compliance resulted in sentence modification Court Order Sentencing Conversation, Exchange Number Page i

3 Inform that subject s sentence is modified Court Order Glossary Table of Figures Figure 1 System Overview... 4 Figure 2 Information Exchange State Diagram Figure 3 Information Exchange Activity Diagram Figure 4 Information Exchange Collaboration Diagram Figure 5 System Hardware Specification Figure 6 Bind Case Over Use Case Figure 7 Bind Case Over Sequence Diagram Figure 8 Bind Case Over Process Figure 9 Provide Parole Decision Use Case Figure 10 Provide Parole Decision Sequence Diagram Figure 11 Provide Parole Decision Process Figure 12 Report Probation Sentence Use Case Figure 13 Report Probation Sentence Sequence Diagram Figure 14 Report Probation Sentence Process Figure 15 Sentence Modification Use Case Figure 16 Sentence Modification Sequence Diagram Figure 17 Sentence Modification Process Figure 18 Sentence Modification Use Case Figure 19 Sentence Modification Sequence Diagram Figure 20 Sentence Modification Process Page ii

4 1 Introduction 1.1 Purpose This document will provide the detailed design specifications for the County Justice Information Exchange Project (CJIEP) pilot deliverable. This document includes the detailed system architecture and design, state, activity and collaboration diagrams, and the specific data elements for each document involved in the defined exchanges. Accompanying this document will be the individual WSDL specifications for each exchange. These WSDL specifications will be used by the Web Service Providers to define and develop the interface to the web service for each exchange. 1.2 Scope The detailed design addresses elements specific to the CJIEP implementation. It details the technical specifications for each aspect identified in the CCAP Information Exchange Milestone Acceptance Form. 1.3 Organization This document details the system design, components and exchange specifications that comprise the CJIEP. For each component, the specification shall provide features, data elements and implementation details. The detailed system design consists of the following key sections. Section Description Introduction Purpose Scope Organization System Overview Web Service Provider Web Service Consumer UDDI Service Design Considerations Assumptions and Dependencies Goals and Guidelines System Design Strategies WS-I Basic Profile 1.0 Detailed System Design State Diagram Activity Diagram Collaboration Diagram Web Service Consumer Component Web Service Provider Component Page 3

5 UDDI Hardware Specification Detailed Exchange Specification Bindover Conversation Exchanges Sentencing Conversation Exchanges Glossary Glossary of Terms 2 System Overview The design of the information exchange system is based on a Service-Oriented Architecture (SOA) framework. A CJIEP exchange web service will be created by the web service provider for each exchange. The web service consumer will be charged with passing the exchange message to the provider s service and, if needed, also with creating the appropriate GJXDM exchange message before passing the exchange message to the provider s service. The following diagram gives an overall picture of the elements involved in the CJIEP infrastructure, the UDDI Service, the Web Service Consumer and Web Service Provider(s). AOPC CPCMS AOPC Court Case Event Message AOPC Court Case Event Message Web Service Consumer AOPC Court Case Event Message (SOAP) Web Service Provider MI Node Service Agent JNET JNET MI/CJIEP Bridge Receive Function Web Service Proxy HTTP Adult Probation and Parole, District Attorney and County Jail WSDL UDDI Service Figure 1 System Overview 2.1 Web Service Consumer The web service consumer s responsibilities begin with identifying the event that triggered the publishing of the AOPC Court Case Event Message. The event will determine which of the identified exchanges needs to be processed (consumed). Once the exchange is identified, the consumer must determine the proper provider web service(s) to exchange the AOPC Court Case Event Message with. An XML configuration file will be used to map events to exchanges and exchanges to standard UDDI web service identifiers. These identifiers will allow the consumer to Page 4

6 query the UDDI Service for the WSDL description of the interface, protocol bindings and deployment details for each web service provider involved in the exchange. The consumer must now pass the SOAP message via HTTP to the web service(s) for processing. Should the call to a specified web service fail, the consumer will be responsible for persisting the SOAP message in a temporary repository until a successful call to the web service is executed. Once the SOAP message has been successfully transmitted to all web service provider involved in the exchange, the message will be removed from the temporary repository. The pilot project specifics for the web service consumer can be found in the Detailed System Design section of this document. 2.2 Web Service Provider It is the provider s responsibility, through the web service, to accept the designated GJXDM compliant exchange message from the web service consumer as a SOAP attachment. The provider will then validate the document against the document s GJXDM schema. Based on the web service invoked and event type of the message, the appropriate document information will be extracted from the body of the message. This information will then be transferred to the appropriate provider system. For the pilot project, the three provider systems have been identified as Adult Probation and Parole, District Attorney System and the County Jail. The pilot project specifics for the web service provider can be found in the Detailed System Design section of this document. 2.3 UDDI The Universal Description, Discovery, and Integration (UDDI) protocol will be used to define the standard method for publishing and discovering the network-based software components of the information exchange SOA. An implementation of the UDDI specification for Web Services will be deployed to the information exchange system. As mentioned above, the consumer will query the UDDI Service for the WSDL description of the required interface, protocol bindings and deployment details for each web service involved in the exchange. The web service provider will be responsible for registering their web service(s) in the UDDI registry. The pilot project specifics for the UDDI service can be found in the Detailed System Design section of this document. Page 5

7 3 Design Considerations This section describes any assumptions, dependencies and guidelines followed in the detailed design and implementation of CJIEP pilot. 3.1 Assumptions and Dependencies All references and examples of xml and xsd in this document and attached to this document are considered works in progress and it should be assumed that these will be modified as needed during the development phase of the project. This document and all accompanying documents will be modified to reflect any changes made to the xml and xsd. In order to utilize existing hardware, the system will be deployed on servers currently available on each pilot county s network. 3.2 Guidelines UML diagrams are provided for UML State, Activity and Collaboration. Schema documents have been created using appropriate GJXDM based Information Exchange Packages ( IEP) and supporting Information Exchange Package Documentation. 4 System Design Strategies The following standards will provide the guidelines and direction for the detailed system design of this project. For the CJIEP project, the WS-I Basic Profile 1.0 will be the SOA standards specification starting point for non-proprietary Web services specification conformance. This profile includes: SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0, XML Schema and HTTP 1.1 As business driven needs of the pilot require additional Web services capabilities, and the PCCD County Architect provides approval, the WS-I Basic Profile 1.1, which consists of a set of additional (specifically in the area of security) non-proprietary Page 6

8 Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability, will be followed for conformance. If necessary, again, based on business need and the lack of capability support by WS- I Basic Profile 1.0, 100% conformance to this specification will be a goal of the pilot project. Pilot usage of Itinerary-Based Routing, if needed - Itinerary based routing is when a message contains a list of addresses it would need to visit. This list is in the metadata and is carried with the message. The County Information Exchange Pilot Project intra-county service bus will have several end points and a message could need to visit multiple service location end points, as it does so, it is then forwarded on by each service location s invocation mechanism based on it s Itinerary based routing list contained in it s metadata. The example message, shown below, carries a list of locations that the message would pass through in its progress to the final destination. <S:Envelope xmlns:s=" <S:Header> <m:path xmlns:m=" <m:action> <m:to>soap://sale.com/endpoint</m:to> <m:fwd> <m:via>soap://order.com</m:via> <m:via>soap://pricing.com</m:via> </m:fwd> <m:rev> <m:via/> </m:rev> <m:id>uuid:a034c795-3de7-49f0-ad03-505bd09437c1</m:id> </m:path> </S:Header> <S:Body>... </S:Body> </S:Envelope> The service consumer would determine the need to invoke Itinerary-Based Routing, each service provider on the County Information Exchange Pilot Project intra-county service bus will be designed to handle Itinerary-Based Routing if requested by the service consumer. Page 7

9 If absolutely necessary, based on business need and PCCD County Architect approval, the following non-ws-i Basic Profile 1.1 specification may be considered during the pilot: WSIL SAML WS-Security 1.0 (as a foundation to WS-Trust, WS-Secure Conversation, WS-Policy, WS-Authorization and WS-Privacy) WS-Addressing (as a foundation to WS- Resource Framework and WS-Notification) WS-Reliability WS-Reliable Messaging BPML BPEL4WS WS-Choreography BPSS ebxml Registry 4.1 WS-I Basic Profile 1.0 The profile identifies how Web services specifications should be used together to create interoperable Web services. The Basic Profile deals with the following components Messaging ( SOAP / HTTP ) SOAP 1.1 defines an XML-based message exchange model for the transmitting and processing of messages. SOAP over HTTP messaging will allow our Web Service interfaces to communicate with each other WSDL Web Service Description Language (WSDL), an XML format for describing Web services, will be employed to describe standardized communications between our Web Services. WSDL service definitions provide documentation for distributed systems and serve as a basis for automating the details involved in applications communication. In addition, the SOA implementation of WSDL to describe the available services will allow our services to support dynamic binding and services reuse. Page 8

10 4.1.3 UDDI The Universal Description Discovery and Integration specification (UDDI) will provide a platform-independent means of describing, discovering and integrating our services over the network. The UDDI data structures provide a framework for the description of basic business and service information and create a mechanism to provide detailed service access information using WSDL XML and XML schema The system will use Global Justice XML (GJXML), an XML standard designed specifically for criminal justice information exchanges. The GJXDM is an objectoriented data model for organizing the content of a data dictionary (the Global JXDD) in a database. From this database an XML schema specification can be generated that consistently represents the semantics and structure of common data elements and types required to exchange information within the justice and public safety communities. GJXDM provides a consistent, extensible, maintainable XML schema reference specification for data elements and types that represent the data requirements of all the documents contained in the pilot and in potential future exchanges. 5 Detailed System Design 5.1 State Diagram Below is the state diagram which outlines the behavior of the information exchange system. It describes all of the possible states of our exchange information (message) as it passes through the exchange process. Page 9

11 Figure 2 Information Exchange State Diagram Page 10

12 5.2 Activity Diagram Below is the activity diagram which describes the workflow behavior of the information exchange system. The diagram describes the state of activities by showing the sequence of activities performed. Figure 3 Information Exchange Activity Diagram Page 11

13 5.3 Collaboration Diagram Below is the collaboration diagram which shows the relationship between objects in the information exchange system and the order of messages passed between them. The sequence numbers next to each message show the sequence of the messages as they are passed between the objects. Figure 4 Information Exchange Collaboration Diagram 5.4 Web Service Consumer Identifying the web service(s) required for the exchange An XML configuration file will be used to map the AOPC Court Case Event Message based on the event that triggered the publishing of message. It will be mapped to one of the identified exchanges in the pilot. This mapping will produce an exchange identifier. The identifier will be used to find the associated Service identifiers used to query the UDDI Service for the WSDL interface description of the exchange. The following is an example of this XML configuration file. Page 12

14 <?xml version="1.0" encoding="utf-8"?> <ServiceAgent> <OrganizationName>Adams County Courthouse</OrganizationName> <SourceDirectory>InMessages</SourceDirectory> <RejectedEventsDirectory>RejectedMessages</RejectedEventsDirectory> <Exchanges> <Exchange id="cjiep_4_66_07_bindcaseover"> <Documents> <Document id="courtcaseevent" xsl="" xsd=""></document> </Documents> <Services> <Service id="cjiep_4_66_07_bindcaseoverservice" uddi_id="cjiep_4_66_07_bindcaseover.jws" directory="cjiep_4_66_07_bindcaseover"> </Service> </Services> </Exchange> <Exchange id="cjiep_6_76_17_reportprobationsentence"> <Documents> <Document id="courtcaseevent" xsl="" xsd=""></document> </Documents> <Services> <Service id="cjiep_6_76_17_reportprobationsentenceservice" uddi_id="cjiep_6_76_17_reportprobationsentence.jws" directory="cjiep_6_76_17_reportprobationsentence"> </Service> </Services> </Exchange> <Exchange id="cjiep_6_78_38_noncompliancesentencemodification"> <Documents> <Document id="courtcaseevent" xsl="" xsd=""></document> </Documents> <Services> <Service id="cjiep_6_78_38_noncompliancesentencemodificationservice" uddi_id="cjiep_6_78_38_noncompliancesentencemodification.jws" directory="cjiep_6_78_38_noncompliancesentencemodification"> </Service> </Services> </Exchange> <Exchange id="cjiep_6_78_40_sentencemodified"> <Documents> <Document id="courtcaseevent" xsl="" xsd=""></document> </Documents> <Services> <Service id="cjiep_6_78_40_sentencemodifiedservice" uddi_id="cjiep_6_78_40_sentencemodified.jws" directory="cjiep_6_78_40_sentencemodified"> </Service> </Services> </Exchange> <Exchange id="cjiep_6_47_01_provideparoledecision"> <Documents> <Document id="courtcaseevent" xsl="" xsd=""></document> </Documents> <Services> <Service id="cjiep_6_47_01_provideparoledecisionservice" uddi_id="cjiep_6_47_01_provideparoledecision.jws" directory="cjiep_6_47_01_provideparoledecision"> </Service> </Services> </Exchange> </Exchanges> <Events> <Event id="case BIND OVER PUBLISH"> <Exchanges> <Exchange id="cjiep_4_66_07_bindcaseover"></exchange> </Exchanges> </Event> <Event id="sentence PUBLISH"> <Exchanges> Page 13

15 <Exchange id="cjiep_6_76_17_reportprobationsentence"></exchange> <Exchange id="cjiep_6_78_38_noncompliancesentencemodification"></exchange> <Exchange id="cjiep_6_78_40_sentencemodified"></exchange> <Exchange id="cjiep_6_47_01_provideparoledecision"></exchange> </Exchanges> </Event> </Events> </ServiceAgent> While JIEM documents will not be used for the pilot, the documents involved in the exchange and the xsl file required to transform the message into that document will be identified in each <Document> element of the <Exchange> element for future reference and development. The following is the list of exchange names which will be used when referring to a specific exchange via the uddi_id attribute. CJIEP_4_66_07_BindCaseOver CJIEP_6_47_01_ProvideParoleDecision CJIEP_6_76_17_ReportProbationSentence CJIEP_6_78_38_NonComplianceSentenceModification CJIEP_6_78_40_SentenceModified Deployment The AOPC Court Case Event Message will be produced by the AOPC Court Case event in the CPCMS system. CPCMS creates the appropriate AOPC Court Case Event Message and publishes it on the JNET network. A JNET MI/CJIEP Bridge module will be deployed in the pilot counties. Similar to a standard JNET JIBLet, it subscribes to a specific topic and pulls any AOPC Court Case Event Messages published to that topic. The JNET MI/CJIEP Bridge module will pull the appropriate AOPC Court Case Event Messages from the JNET queue and place it in a configuration specific directory on the Service Agent server. For the pilot project, the CJIEP Service Agent deployed in each county will act as the web service consumer. In order to utilize existing hardware, it will reside on an existing Biztalk server. The Service Agent will pick up the message, filtering any AOPC Court Case Event messages not meant for that specific county. It will map the message to the appropriate exchange web service and then access the UDDI directory for the url of the specified web service. It will then call the web service, passing the AOPC Court Case Event message. If the web service is unavailable, the Service Agent will temporarily store the message until the web service becomes available, at Page 14

16 which point it will execute the web service call and remove the message from the temporary store. 5.5 Web Service Provider Detailed design for each web service will be provided by the Web Service Provider as a separate document. 5.6 UDDI UDDI Implementation juddi (pronounced Judy ) will be used to implement the UDDI registry for the pilot project. juddi is an open source Java implementation of the UDDI specification for the Apache Web Services Project. It is a Web Services Registry and Repository for building Service-Oriented Architectures. The Service Registry provides the means for registering and discovering web services. The Service Registry is available through the Apache Web Services Project. The steps required to register the WSDL in the UDDI Registry are outlined in the next section WSDL The process of creation, utilization and deployment of the WSDL for the pilot project can be summarized in three major steps. 1. The first step is to create the WSDL service interface definition. The service interface definition will include service interfaces and protocol bindings, and will be made publicly available. The WSDL service interface definitions are then registered as UDDI tmodels; the overview Doc field in each new tmodel will point to the corresponding WSDL document. 2. Next, the service provider will build services that conform to the industry standard service definitions and documented CJIEP System Design Strategies. Either manually or using appropriate UDDI-aware tooling, the provider will retrieve the tmodel description of the industry standard definition, and obtain the corresponding WSDL definition document. WSDL-aware tooling, in turn, can help generate an implementation that supports the standard interfaces and bindings. 3. Finally, the new service must be deployed and registered in the UDDI repository. Either manually or using WSDL and UDDI-aware tooling, a UDDI business Service data structure is created, and then registered. Typically when using WSDL and UDDI-aware tools, service deployment information (some type of deployment descriptor document) will be generated at that same time. Page 15

17 5.7 Hardware and Software Specification All hardware required for the Information Exchange project currently exists in each pilot county. The following diagram outlines the existing networks and servers and their specific use. Figure 5 System Hardware Specification Hardware Specifications The following are the hardware specifications for all servers and workstations required for the CJIEP pilot. Server: Pentium III, 933Mhz or Faster, PCI bus, 512K L2 cache, 512 MB RAM Work Station: Pentium III 350Mhz or faster with L2 Cache, 64K or larger County MI Node The County MI Node is required to link the County Justice Information Project to the JNET Messaging Infrastructure (MI). It requires the installation of IBM MQ Series and a Java Virtual Machine (JVM). A server operating system is not required. The minimum operating system necessary is Windows NT, Windows 2000 or Windows XP. For the pilot project, the existing MI nodes in each pilot county will be utilized. Information Exchange Server The Information Exchange Server will host the Service Agent windows service and message repository, the UDDI Interface and Repository and the JNET MI / CJIEP Bridge component. A server operating system is not required. The minimum operating system necessary is Windows NT, Windows 2000 or Windows XP. Required is the installation of the Service Agent, the juddi Service Registry and the JNET MI / CJIEP Bridge component. The Bridge Page 16

18 component will need to be configured to interface to the MI Node MQSeries queues. Additionally, to support the Service Registry, the following software will need to be installed: JDK or later and Apache Tomcat 5. For the pilot project, the existing Biztalk server running Windows 2000 Server in each pilot county will be utilized. Web Server A Web Server will be required in each county to host the Provider Web Service. It requires connectivity to the databases used for each of the agency systems. The minimum operating system necessary is Windows NT, Windows 2000 or Windows XP. It requires the installation of an application server. For the application server, the service provider recommends the JBoss Application Server. Adult Probation The Adult Probation System must reside on the county network and be accessible by the CJIEP web service. For the pilot, the existing Adult Probation System in each county will be utilized. No modifications to the system will be necessary. District Attorney The District Attorney System must reside on the county network and be accessible by the CJIEP web service. For the pilot, the existing District Attorney System in each county will be utilized. No modifications to the system will be necessary. County Jail The County Jail System must reside on the county network and be accessible by the CJIEP web service. For the pilot, the existing County Jail System in each county will be utilized. No modifications to the system will be necessary. 6 Detailed Exchange Specification The following sections contain the description, specification and design of the five exchanges chosen for the Pilot project. The narratives are from the JIEM to be Modeling tool as provided by PCCD s SEARCH consultant, MTG. 6.1 Bindover Conversation, Exchange Number Bind case over During the Pre-disposition Court process, at the Preliminary Hearing event, if district judge finds probable cause to proceed, the Magisterial District Judges sends the Affidavit of Probable Cause, Bail/Bond, Criminal Complaint, and Docket Transcript Page 17

19 to the Court of Common Pleas for the Open Case event in the Pre-disposition Court process. This service returns a SOAP exception. The use case for this exchange is shown in the following diagram: Figure 6 Bind Case Over Use Case The sequence for this exchange is shown in the following diagram: Figure 7 Bind Case Over Sequence Diagram The process executed for this service is shown in the following diagram: Page 18

20 Figure 8 Bind Case Over Process The messages utilized in this exchange will include the following information: Affidavit of Probable Cause Message Type: asynchronous AOPC court service agent sends: Affidavit of Probable Cause Document Contents: Affidavit of Probable Cause XML Criminal Complaint Information Complaint/Incident Number Case Identifiers Common Pleas Docket # / Court Case # Police Incident # Comments / Notes / Other Information Probable Cause Belief County Pa. County Id Signatures Filing Officer s / Affiant Signature Filing Officer s / Affiant Signature Date Issuing Authority Signature Issuing Authority Signature Date Warrant Information Warrant Control # Security: Protocol: none http AOPC court service agent receives: SOAP Exception Bail / Bond Message Page 19

21 Type: AOPC court service agent sends: Contents: asynchronous Bail / Bond Document Bail / Bond XML Offense / Charge Information Bail / Bond Information Case Identifiers Defendant Information Offense / Charge Offense / Charge # Offense / Charge Description Offense Date Nominal Bail Nominal Bail Amount Bail Bond Order Date Conditions of Release Bail Bond Security or Surety Cash in full amount of bail Percentage cash bail Money furnished by Certification of Sufficient Bail By the Defendant On behalf of the Defendant By Name of Surety Address of Surety License Number of Surety Next Court Action Date and Time of Next Court Action Location of Next Court Action Defendant Sent To Detention Center Defendant Sent to Other Police Case # OTN (Offense Tracking Number) Court Case Number(s) (CC) C.P. Term and Number Defendant Name Defendant Telephone Number Defendant Address Defendant Address Street Defendant Address City Defendant Address State Defendant Address Zip Code Defendant Occupation Defendant Present Employer Detention Status Discharge Date Magisterial District Justice Information Magisterial District Justice Number Page 20

22 Officials Security: Protocol: Judge Names Issuing Authority Court Clerk Signatures Clerk of Court Signature Clerk of Court Signature Date none http AOPC court service agent receives: SOAP Exception Criminal Complaint Type: AOPC court service agent sends: Contents: asynchronous Criminal Complaint Criminal Complaint XML Criminal Complaint Information Complaint Filed Date Complaint/Incident Number Complaint/Incident Number if other Participants Date Criminal Complaint Completed and Verified District Attorney s Office Approval District Attorney s Office Disapproval District Attorney s Office Disapproved Reason Violation Information Location of Violation Participant(s) Name(s) to the violation List of Acts Committed by the Accused Violation Section Violation Subsection Violation Pennsylvania Statute Counts of Violation Other Information LiveScan Tracking Number UCR/NIBRS Code Case Identifiers OTN (Offense Tracking Number) County Pa. County Id Defendant Information Defendant Name Defendant Alternate Name / A.K.A Defendant Race/Ethnicity Defendant Sex Page 21

23 Defendant Date of Birth Defendant Social Security Number Defendant Address Defendant Address Street Defendant Address City Defendant Address State Defendant Address Zip Code Defendant Occupation Defendant Present Employer Defendant SID Defendant Vehicle License Plate # Defendant Vehicle State Licensed to Defendant Vehicle Registration Sticker Date Defendant Driver s License # Defendant Driver s License State District Attorney Information District Attorney Name District Attorney Signature District Attorney Signature Date Magisterial District Justice Information Magisterial District Number (final issuing) Magisterial District Justice Name (final issuing) Magisterial District Justice Address Street Magisterial District Justice Address City Magisterial District Justice Address State Magisterial District Justice Address Zip Code Magisterial District Justice Telephone Number Magisterial District Justice Docket Number Officials Filing Officer s / Affiant s Name Filing Officer s / Affiant s Badge Number Department or Agency Represented Political Subdivision Police Agency ORI Number Originating Agency Case Number (OCA) Signatures Filing Officer s / Affiant Signature Magisterial District Justice Signature Magisterial District Justice Signature Date Security: Protocol: none http AOPC court service agent receives: SOAP Exception Docket Transcript Type: asynchronous Page 22

24 AOPC court service agent sends: Contents: Docket Transcript Docket Transcript XML Offense / Charge Information Offense Offense Description Offense Grading Offense Date Offense Section and Subsection Offense Disposition Citation Information Date Citation Issued Date Citation Filed Criminal Complaint Information Complaint Filed Date Arrest Information Arrest Date Case Identifiers Final Issuing Authority Docket # Common Pleas Docket # State Identification # OTN Codefendant Codefendant 1 Name Codefendant 1 OTN Codefendant 2 Name Codefendant 2 OTN Codefendant 3 Name Codefendant 3 OTN Codefendant 4 Name Codefendant 4 OTN Affiant Who Signed Complaint Complainant Name Complainant Address ORI OCA Badge # / Officer ID Defendant Information Defendant Name Defendant Race/Ethnicity Defendant Sex Defendant Date of Birth Defendant Address Defendant Address Street Defendant Address City Defendant Address State Defendant Address Zip Code Defendant Driver s License # Defendant Driver s License State Page 23

25 Distribution List Clerk of Courts Trial Court Administration Magisterial District Justice Information Magisterial District Number Magisterial District Justice Name Magisterial District Justice Address Zip Code Magisterial District Justice Telephone Number Magisterial District Justice Docket Number Initial MDJ Name Transferred From Initial MDJ Number Transferred From Initial MDJ Docket Number Date of Transfer from Initial MDJ Attorneys Commonwealth Attorney Name Commonwealth Attorney Address Commonwealth Attorney ID Number Complainant Attorney Name Complainant Attorney Address Complainant Attorney ID Number Defense Council Name Defense Council Address Defense Council Private Defense Council Other Defense Council ID Number Preliminary Arraignment Preliminary Arraignment Date Preliminary Arraignment Time Preliminary Arraignment Bail Type Amount Date Set Date Posted Preliminary Arraignment Surety Name Individual Individual Address Name Corporate Corporate Address Date Waived to Court Preliminary Hearing / Summary Trial Trial Date Trial Address Preliminary Hearing Information Date for Preliminary Hearing Continuation of Hearing Decision Date Fines Amount Costs Amount Judgment of Sentence Judgment of Sentence Balance Amount Page 24

26 Magisterial District Justice Summons Information Warrant Information Witness Information Security: Protocol: Current Bail / Bail at Preliminary Hearing Type Amount Posted Date Bail Date Set Surety Name Individual Individual Address Name Corporate Corporate Address If Committed Date Code Place of Commitment Defendant Advised of Assignment of Council Right Public Defender Requested by Defendant Application Provided- Appointment of Public Def. Reasonable Effort to Settle Difference Date Date Transcript Sent to Court Certification of MDJ Docket Transcript Date Date Printed Signature Commission Expiration Date Summons Issued Date Summons Returned Date Warrant Issued Date Witness for Complainant or Defendant Name Address Witness Sworn Witness Testified Defense Persons to be Notified none http AOPC court service agent receives: SOAP Exception 6.2 Sentencing Conversation, Exchange Number Provide Parole Decision During the Post-disposition Court process, at the Sentence Hearing event, if subject is in custody, and if court sentences subject to probation or parole, the Court of Page 25

27 Common Pleas sends the Parole Order to the County Jail for the Release event in the Post-disposition Supervision process. This service returns a SOAP exception. The use case for this exchange is shown in the following diagram: Figure 9 Provide Parole Decision Use Case The sequence for this exchange is shown in the following diagram: Figure 10 Provide Parole Decision Sequence Diagram The process executed for this service is shown in the following diagram: Page 26

28 Figure 11 Provide Parole Decision Process The messages utilized in this exchange will include the following information: Parole Order Type: AOPC court service agent sends: Contents: asynchronous Parole Order Parole Order XML Offense / Charge Information Case Identifiers Offense Offense Description Offense Grading Offense Date Offense Section and Subsection OTN Common Pleas Docket # Court Case # Costs / Fines Defendant Responsible for Prosecution Costs County Responsible for Prosecution Costs Fines Costs Total Fines Crime Lab User Fee Restitution Restitution Amount Court Order / Case Disposition Court Ordered Parole Date of Court Order Date of Court Ordered Sentencing Parole Order Other Information Defendant Information Defendant Name Defendant Date of Birth Page 27

29 Defendant Social Security Number Defendant Telephone Number Defendant Address Street City State Zip Code Defendant SID District Attorney Information District Attorney Name Intermediate Punishment Information Defendant Sentenced Defendant Sentenced to a period of Defendant Electronic Monitoring effective date Defendant Non-electronic Monitoring Defendant Non-electronic Monitoring Approved After Date Officials Judge Name Defense Counsel Name Court Reporter Court Clerk Probation Information Probation Probation without Verdict Probation for a period of Probation Starts Effective Date Special Condition List Agency Name Address Sentence Date of Sentencing Mandatory Sentence Plea Plea Agreement Non-Jury Jury Nolo Probation Violation Parole Violation IP Violation Disposition as to Count Mandatory Sentence Split Sentence Offense Nol Pros Merges with Committed Years Months Page 28

30 Signatures Security: Protocol: Days Hours Committed To Years Months Days Probation / ARD Years Months Days Serve At County Prison Name SCI (State Correctional Institution) Name Intermediate Punishment Program Concurrent Sentence to Consecutive Sentence to Disposition as to Other Counts Clerk of Court Signature Judge Signature Judge Signature Date Minute Clerk Signature none http AOPC court service agent receives: SOAP Exception 6.3 Sentencing Conversation, Exchange Number Report Probation Sentence During the Post-disposition Court process, at the Sentence Hearing event, if court sentences subject to probation or parole, the Court of Common Pleas sends the Court Order to the Adult Probation and Parole for the Release event in the Post-disposition Supervision process. This service returns a SOAP exception. The use case for this exchange is shown in the following diagram: Page 29

31 Figure 12 Report Probation Sentence Use Case The sequence for this exchange is shown in the following diagram: Figure 13 Report Probation Sentence Sequence Diagram The process executed for this service is shown in the following diagram: Figure 14 Report Probation Sentence Process Page 30

32 The messages utilized in this exchange will include the following information: Court Order Type: AOPC court service agent sends: Contents: asynchronous Court Order Court Order XML Offense / Charge Information Case Identifiers Offense / Charge Offense / Charge Number Offense Description OTN Common Pleas Docket # / Court Case # Court Case Number(s) (CC) Costs / Fines Defendant Responsible for Prosecution Costs County Responsible for Prosecution Costs Fines Costs Total Fines Crime Lab User Fee Restitution Restitution Amount Court Order / Case Disposition Court Ordered Sentencing Date of Court Order Court Order as to Count / Violation Date of Court Ordered Sentencing Court Order Parole Order Other Information Defendant Information Defendant Name Defendant Date of Birth Defendant Social Security Number Defendant Telephone Number Defendant Address Street City State Zip Code Defendant SID Detention Status Defendant in Custody Defendant Custody Location Page 31

33 District Attorney Information District Attorney Name Intermediate Punishment Information Defendant Sentenced Defendant Sentenced to a period of Defendant Electronic Monitoring effective date Defendant Non-electronic Monitoring Defendant Non-electronic Monitoring Approved After Date Jail Information County Jail Name County Jail Period of Incarceration State Correctional Institution Name State Correctional Incarceration Period State Correctional Incarceration Effective Date State Correctional Incarceration Additional Credit Concurrent Sentence(s) Consecutive Sentence(s) Defendant Permitted Alternative Housing Defendant s Location of Alternative Housing Defendant Granted Work Release Defendant to be Paroled Defendant s Effective Date of Parole Officials Judge Name Defense Counsel Name Court Reporter Court Clerk Probation Information Probation Probation without Verdict Probation for a period of Probation Starts Effective Date Probation Special Conditions Megan s Law Registration DUI Fine Amount Interlock Complete Regional Alcohol Program DNA Registration No Contact w/victim Drug and Alcohol Evaluation Domestic Abuse Classes MH/MR Evaluation Probation Supervising Agency County State Sentence Mandatory Sentence Plea Modified Sentence Re-Sentencing Page 32

34 Signatures Security: Protocol: Sentencing ARD Summary Appeal Other Plea Agreement Non-Jury Jury Nolo Probation Violation Parole Violation IP Violation Disposition as to Count Mandatory Sentence Split Sentence Offense Nol Pros Merges with Committed (Years,Months,Days) Committed To (Years,Months,Days) Probation / ARD (Years,Months,Days) Serve At County Prison Name SCI (State Correctional Institution) Name Intermediate Punishment Program Disposition as to Other Counts Clerk of Court Signature Judge Signature Judge Signature Date Minute Clerk Signature none http AOPC court service agent receives: SOAP Exception 6.4 Sentencing Conversation, Exchange Number Inform that subject s non-compliance resulted in sentence modification During the Post-disposition Court process, at the Review Hearing event, if subject fails to comply with sentencing terms, and if court determines that subject action requires sentence modification, the Court of Common Pleas sends the Court Order to the District Attorney for the Update Case File event in the Post-disposition Court process. This service returns a SOAP exception. The use case for this exchange is shown in the following diagram: Page 33

35 Figure 15 Sentence Modification Use Case The sequence for this exchange is shown in the following diagram: Figure 16 Sentence Modification Sequence Diagram The process executed for this service is shown in the following diagram: Figure 17 Sentence Modification Process Page 34

36 The messages included in this exchange are defined as follows: Court Order Type: AOPC court service agent sends: Contents: AOPC court service agent receives: asynchronous Court Order Court Order XML SOAP Exception ( See Court Order contents section ) 6.5 Sentencing Conversation, Exchange Number Inform that subject s sentence is modified During the Post-disposition Court process, at the Review Hearing event, if court orders a modification to probation or parole sentence, the Court of Common Pleas sends the Court Order to the Adult Probation and Parole for the Update Case File event in the Post-disposition Court process. This service returns a SOAP exception. The use case for this exchange is shown in the following diagram: Figure 18 Sentence Modification Use Case The sequence for this exchange is shown in the following diagram: Page 35

37 Figure 19 Sentence Modification Sequence Diagram The process executed for this service is shown in the following diagram: Figure 20 Sentence Modification Process The messages included in this exchange are defined as follows: Court Order Type: AOPC court service agent sends: Contents: AOPC court service agent receives: asynchronous Court Order Court Order XML SOAP Exception ( See Court Order contents section ) Page 36

38 Term Choreography CJIEP CPCMS ebxml 7 Glossary Exchange message GJXDM HTTP Itinerary-Based Routing Jail OMS JIEM JNet Network AOPC Court Case Event Message PCCD SEARCH Service Agent Service Consumer Service Consumer SOA SOAP Description Term used to refer to the sequence and conditions that describe exchange of messages. County Justice Information Exchange Project The project to which this document refers. AOPC s Court of Common Pleas Criminal Court Case Management System that will supply the information to be used for the exchanges identified for this pilot. Electronic Business XML Initiative. Specification that enables XML to be utilized in a consistent manner for the exchange of electronic business data. Message that is involved in an exchange between Service Agent and Service Provider. Global Justice XML Data Model Data reference model used for the exchange of justice and public safety information. Hypertext Transmission Protocol the standard data transmission format used between web browsers and web servers Itinerary based routing is when a message contains a list of addresses it would need to visit. This list is in the metadata and is carried with the message. Jail s Offender Management System. Justice Information Exchange Model Model describing the flow of justice information between criminal justice agencies. Secure virtual system for the sharing of justice information by authorized users. - Message generated by AOPC s CPCMS system containing justice information. The AOPC Court Case Event Message will be transformed into exchange messages identified for this pilot. Pennsylvania Commission on Crime and Delinquency Organization promoting a collaborative approach to enhance the quality of justice through guidance, leadership and resources by empowering citizens and communities and influencing state policy (PCCD mission statement). The National Consortium for Justice Information and Statistics. Organization focused on improving information management and exchange between criminal justice and public safety agencies. Mechanism responsible for packaging the exchange message, identifying the specified service provider for the exchange, and accessing the provider s web service to exchange the message. Agency that utilizes web services provided by other agencies. Consumer s service agent passes the exchange message to the service provider. Agency that utilizes web services provided by other agencies. Consumer s service agent passes the exchange message to the service provider. Service Oriented Architecture Software architecture methodology that provides interaction of independent, reusable components that perform business process. Simple Object Access Protocol XML based message protocol for exchanging messages between web services. Page 37

39 UDDI Web Service Providers Web Services WSDL WS I XML Universal Description, Discovery and Integration Registry for listings and discovery of web-services and their descriptions. Agency that provides web services to consumer agencies. Provider s web service receives the selected exchange message from a consumer. Web Services encompasses a collection of protocols and technologies allowing a standardized exchange of data. Web Service Description Language XML language used for describing web services. Web Services Interoperability Organization an open industry organization chartered to promote web services interoperability across platforms, operating systems and programming languages. Extensible Markup Language Markup language used for creating custom messages for data exchange. Page 38