exhibit i - edr technical environment i - edr... · washington state page 2 of 44 inh ede data...

EXHIBIT I

Washington State of 44 INH EDE Data Integration Administrative Office of the Courts ACQ-2016-0301-RFP

EDR TECHNICAL ENVIRONMENT

TABLE OF CONTENTS

1 INTRODUCTION .............................................................................................................................. 2

2 TECHNICAL REFERENCE ............................................................................................................. 2 2.1 ENTERPRISE DATA REPOSITORY (EDR) DATA MIGRATION AND DATA UPDATE SOURCES

ROADMAP .......................................................................................................................................... 2 2.2 EDR INFRASTRUCTURE ENVIRONMENT ..................................................................................... 5 2.3 JIS DATABASE ......................................................................................................................... 5

JIS Physical Data Model ................................................................................................. 5

JIS Data Dictionary ......................................................................................................... 6

2.4 EDR DATABASE....................................................................................................................... 8 Logical Data Model ......................................................................................................... 8

EDR Physical Table Documentation ............................................................................ 11

2.5 JIS TO EDR DATABASE MAPPING ........................................................................................... 13 2.6 EDR DEPLOYMENT PROCESS ................................................................................................. 29 2.7 EDR SECURITY ..................................................................................................................... 32 2.8 CONNECTING TO EDR ODATA SERVICES ................................................................................ 33

EXHIBIT I


1 INTRODUCTION

This exhibit provides technical support information to assist with responding to this RFP.

2 TECHNICAL REFERENCE

2.1 Enterprise Data Repository (EDR) Data Migration and Data Update Sources Roadmap

1. The EDR shall be initially loaded using the database corresponding to the CMS system

that is sending the data to the EDR. The EDR requires that the source data system

provide all of its 'keys' to data records being created, updated and deleted.

2. Data maintained by existing JIS systems shall be loaded from the JIS database into the

EDR.

3. JIS database updates shall be applied to the EDR after the initial load.

4. The Enterprise Data Warehouse will use the EDR as the source for statewide data when

the EDR goes live.

5. The Data Warehouse will maintain data in addition to the EDR (local data, historical

data, etc.).

6. If the EDR goes live prior to King County then the original data source shall be the JIS.

7. If the EDR goes live at the same time as King County, then King County shall provide

the initial data load for just its court data.

8. King county data shall be purged immediately from the JIS database upon King county

go live (usage of the EDR). The JIS data will remove the corresponding data from the

EDR and Data Warehouse.

9. King county data will be loaded to the EDR, which will trigger data load to the Data

Warehouse.

10. Ongoing audit of Source systems vs the EDR is performed after a court goes live with

providing updates to the EDR. This includes both KC systems (CLJ and Superior), JIS,

and all court systems on boarded as a EDR data provider.

EXHIBIT I


The following provides a graphical depiction of the EDR Roadmap:

EXHIBIT I


EXHIBIT I


2.2 EDR Infrastructure Environment

2.3 JIS Database

JIS Physical Data Model

The diagram below depicts a portion of the JIS physical data model. The entire database is available but is not included here so as to limit the size. Additional diagrams are available if needed.

EXHIBIT I


JIS Data Dictionary

A complete description of the JIS database is available in the JIS Data Dictionary. Here is an example of the table listing:

For each table the following information is available:

EXHIBIT I


For each data element, the following is available:

For each codes table column the following information is available to define the codes table:

And to provide the codes values:

EXHIBIT I


2.4 EDR Database

Logical Data Model

The following depicts the EDR logical model. The following provides definitions for the relationship types:

RequiredIndependent 0 RequiredIndependent The object is a single item that

IS REQUIRED for the relationship to be valid. Deletion of the item(s) at the other end of the relationship WILL NOT delete the item

OptionalIndependent 1 OptionalIndependent The object is a single item that IS NOT REQUIRED for the relationship to be valid. Deletion of the item(s) at the other end of the relationship WILL NOT delete the item

CollectionDependent 2 CollectionDependent The object in the relationship is to be treated as a collection of items that DO RELY on the existence of the item(s) relating to the collection. Therefore, deletion of the item(s) at the other end of the relationship WILL delete the collection

CollectionIndependent 3 CollectionIndependent The object in the relationship is to be treated as a collection of items that DO NOT RELY on the existence of the item(s) relating to the

EXHIBIT I


collection. Therefore, deletion of the item(s) relating to the collection WILL NOT delete the collection.

OptionalDependent 4 OptionalDependent The object is a single item that IS NOT REQUIRED for the relationship to be valid. Deletion of the item(s) at the other end of the relationship WILL delete the item

RequiredDependent 5 RequiredDependent The object is a single item that IS REQUIRED for the relationship to be valid. Deletion of the item(s) at the other end of the relationship WILL delete the item

Actor Domain Model

Case Domain Model

EXHIBIT I


EXHIBIT I


Financial Activity Domain Model

Identity Security Model

EDR Physical Table Documentation

The EDR SQL Server database is documented in the EDR Portal. The following is an example of the information available for each table:

Actor

View Actor in the graphical explorer.

EXHIBIT I


Actor

Columns

Name Type Size Keys

1 Key int PK

2 Name nvarchar 100

3 CreateTimeStamp datetime2

4 CreateCredential nvarchar 60

5 UpdateTimeStamp datetime2

6 UpdateCredential nvarchar 60

7 BeginDate datetime2

8 EndDate datetime2

9 DataSourceKey int FK [DataSource].[Key]

10 SecurityResourceOwnerKey int FK [SecurityResourceOwner].[Key]

Dependents

No tables to display.

ActorAssociationMember

ActorClassification

ActorElectronicContact

ActorEvent

ActorIdentity

ActorKeyMap

ActorLocationAddress

ActorPhoneNumber

ActorStatus

EXHIBIT I


CaseActor

FinancialActivity

Language

Official

Organization

Person

Dependencies

DataSource

SecurityResourceOwner

This information is also available in a graphic explorer view:

2.5 JIS to EDR Database Mapping

The following is a draft version of the JIS to EDR Database mapping. The table shows the mapping of JIS Standard Data element Name (see Exhibit L – JIS Data Standards for Alternative Electronic Court Record Systems for the complete list of JIS Standard Data elements) to EDR data elements and JIS DB2 data elements. This is provided as informational only at this time to give an idea of the mapping. The DB2 Table name and DB2 Data Element

EXHIBIT I


Name columns are intentionally suppressed. Please note that this mapping is partial and does not include all the JIS standard Data elements.

EDR Table EDR Data Element Name

JIS Standard Data ElementName

DB2 Table DB2 Data Element Name

CaseClassification CaseClassificationStatusSourceDefinitionKey

Case Cause of Action Code

CaseClassification CaseClassificationStatusSourceDefinitionKey

CaseClassificationStatusStandardDefinition

CodeValue * reference data *

CaseClassification CaseClassificationSourceDefinitionKey

Case Classification Code



CaseClassificationStandardDefintion


CaseDate Date Case Filing Date

CaseDateSourceCode CodeValue

EXHIBIT I





CaseDate Date

CaseDateSourceReference

CodeValue

CaseDate Date


CodeValue

CaseDate Date


CodeValue

CaseKeyMap SourceKey Case Identifier

CaseKeyMap SourceKey

EXHIBIT I





CaseKeyMap SourceKey

CaseIdentity Value Case Number

CaseIdentity Value

CaseIdentity Value

CaseSecurity CaseSecuritySourceCodeKey

Case Security Status Code

CaseSecurity CaseSecuritySourceCodeKey

CaseSecurityStandardReference


CaseStatus CaseStatusSourceCodeKey

Case Status Code

EXHIBIT I









CaseStatusStandardReference


CaseDate Date Case Status Date


CodeValue

CaseDate Date CaseDateSourceReference

CodeValue

CaseDate Date


CodeValue

CaseDate Date

Go into Status date CodeValue=Status Date

Go into case status Date Go into case status CodeValue=Status

Date

EXHIBIT I





Case Title Case Title Text

Case Title

Case Title

CaseMatterDate Date Charge Plea Date

CaseMatterDateSourceReference

CodeValue

CaseMatterAuthorityReferenceSourceStatus (CasematterAuthority)

CodeValue Charge Plea Type Code

CaseMatterDate Date Charge Arraignment Date


CodeValue

MatterType CodeDescription Charge Definition Law Number

MatterType CodeDescription


CaseMatter DomesticViolenceFlag

Charge Domestic Violence Code


EXHIBIT I






CaseMatterKeyMap SourceKey Charge Identifier

CaseMatterDate Date Charge Information Date


CodeValue

CaseMatterStatusSourceReference EJK look at this

CodeValue Charge Juvenile Disposition Offense Category Code

CaseMatterStatusStandardReference


ReferenceSourceAuthority Source version of this

CodeDescripion Charge Modifier Law Number

CasematterAuthority AuthoritySourceReferenceKey (used with Violation Date and Court Initials to look up foreign key)

Charge Primary Local Law Number

CasematterAuthority AuthoritySourceReferenceKey (used with Violation Date and Court Initials to look up foreign key)

CaseMatterStatus CaseMatterStatusSourceReferenceKey

Charge Primary Result Code

CaseMatterStatus CaseMatterStatusSourceReferenceKey

CaseMatterStatusStandardReference


CaseMatterDate Date Charge Primary Result Date


CodeValue

EXHIBIT I





CaseMatterDate Date


CodeValue

CaseMatterReferenceSourceStatus (CaseMatterStatus)

CodeValue Charge Primary Result Reason Code

MatterType CodeDescription Charge Primary Standard Law Number


CaseMatter ChargeSameCourseConductFlag

Charge Same Course of Conduct Code

CaseMatterDate Date Charge Sentence Date


CodeValue

Actor (CaseActor)

Name Charge Sentence Judicial Official Identifier

These are in Case Matter Authority

You can get these from CHR Law number 2-5) but have to hardcode the values.

Charge Special Allegation Law Number


Charge Special Allegation Result Code


Charge Special Allegation Result Date

CaseMatterDate Date Charge Violation Date


CodeValue

CaseMatterDate Date

EXHIBIT I






CodeValue

CitationFlagSourceReference

CodeValue

CitationFlag Flag Citation Accident Code

CitationAmount Amount Citation Amount

CitationBloodAlcoholContentType

CitationBloodAlcoholContentTypeSourceCodeKey

Citation Blood Alcohol Content Type Code

CitationBloodAlcoholContentTypeStandardReference


CaseDate Date Citation Date


CodeValue

CitationCountSourceReference

CodeValue

CitationCount Count Citation Speed Zone Count

CitationTHCLevel THCLevelCount Citation THC Level Count

CitationTHCLevel CitationTHCLevelSourceCodeKey

Citation THC Type Code

CitationTHCLevelStandardReference


CitationCount Count Citation Vehicle Speed Count

CitationBloodAlcoholContentType

BloodAlcoholContentPercent

Citation Blood Alcohol Content Percent

Condition Amount Condition Amount

Condition Amount

Condition Amount

ConditionKeyMap SourceKey

EXHIBIT I





ConditionKeyMap SourceKey Condition Case

ConditionStatus ConditionStatusSourceCodeKey

Condition Complied Code

ConditionStatus ConditionStatusSourceCodeKey

ConditionStatusStandardReference


ConditionDate Date Condition Complied Date

ConditionDateSourceReference

CodeValue

Condition Status Type

Condition Complied Reason Code

ConditionDate Date Condition Date


CodeValue

ConditionDate Date Condition Date


CodeValue

Key Map Condition Identifier

ConditionDate Date Condition Review Date


CodeValue

ConditionDate Date


CodeValue

ConditionTimeUnit TimeCount Condition Time Count

ConditionTimeUnit ConditionTimeUnitSourceCodeKey

Condition Time Unit Code

ConditionTimeUnitStandardReference


ConditionClassification ConditionClassificationSourceDefinitionKey

Condition Type Code

EXHIBIT I





ConditionClassification ConditionClassificationSourceDefinitionKey

ConditionClassificationStandardReference


CaseDate Date Detention Episode Admission Date


CodeValue

These go into status Detention Episode Admission Reason Code

These go into status These go into status

These go into status Detention Episode Admission Time

ActorIdentity (Organization)

Value Detention Episode Facility Code

Status Detention Episode Intake Code

CaseDate Date Detention Episode Intake Date


CodeValue

CaseDate Time Detention Episode Intake Time

Case Matter Detention Episode Primary Charge Code

Reference data associated with authority on the case matter

Detention Episode Primary Charge Severity Code

CaseStatus Date Detention Episode Release Date

EXHIBIT I





CaseStatusDateSourceReference

CodeValue

Status Detention Episode Release Reason Code

CaseStatus Time Detention Episode Release Time

CaseMatter TimeServedHoursCount (use Minutes/60)

Detention Episode Time Served Hours Count

Case Index something

Document Amount

ActorKeyMap SourceKey Document Authorizing Official Identifier

CaseIndexStatus CaseIndexStatusSourceCodeKey

Document Decision Code

CaseIndexStatusStandardReference


CaseIndexDate Date Status Document Decision Date

CaseIndexDateSourceReference

CodeValue

Case Index Status Document Decision Reason Code

CaseIndexDate Date Document Expiration Date


CodeValue

CaseIndexDate Date Document File Date


CodeValue

CaseIndexDate Date CaseIndexDateSourceReference

CodeValue

CaseIndexKeyMap SourceKey Document Identifier

CaseIndexKeyMap SourceKey

EXHIBIT I





CaseIndexIdentity Document Number look at SDK Microfilm Number

CaseIndexPartyStatus Case Index Status Document

Party Decision Code

ActorKeyMap SourceKey Document Party Person Identifier

CaseActorClassificationSourceReference Needs to go into EJK Research

CodeValue Document Party Role Code

CaseActorClassificationStandardReference


CaseIndexDate Note for EJK. Business Rules that customer needs to send termination notice.

Date Document Termination Date


CodeValue

CaseIndexClassification CaseIndexClassificationSourceReferenceKey

Document Type Code


CaseIndexClassificationStandardReference


CaseIndexDate Date FTA Adjudication Department Of Licensing Date


CodeValue

CaseIndexKeyMap SourceKey FTA Identifier CaseIndexDate Date FTA Issuance

Date

CaseIndexDateSource CodeValue

EXHIBIT I





CaseIndexDate Date FTA Order Date


CodeValue

CaseIndexDate Date FTA Return Adjudication Date


CodeValue

CaseIdentity AuthorizingOrganization

Law Enforcement Agency Code

Originating Agency Code

ActorIdentity Value AuthorizingOrganization

Originating Agency Identifier

CaseIdentity Value Originating Agency Number

CaseIndexDate Date Proceeding Actual Date


CodeValue

ActorKeyMap (Official)

SourceKey Proceeding Actual Official Person Identifier

CaseIndexKeyMap SourceKey Proceeding Identifier

CaseIndexStatus CaseIndexStatusSourceReferenceKey

Proceeding Status Reason Code

CaseIndexDate Date Proceeding Schedule Date


CodeValue

EXHIBIT I





CaseIndexDate Date


CodeValue

CaseIndexDate Time Proceeding Schedule Time

CaseIndexDate Time

ActorKeyMap EJK - Chau make sure CaseIndex has an official. (Official)

SourceKey Proceeding Schedule Official Identifier


Proceeding Status Code

CaseIndexDate Date Proceeding Status Date


CodeValue


Proceeding Type Code


CaseActorIdentity Value Process Control Number

CaseIndexDate Date Process Control Number Arrest Date


CodeValue

CaseIndexDate Date Process Control Number Date


CodeValue

CaseIndexDate Date Return Adjudication Date

EXHIBIT I






CodeValue

CaseIndexAmount Amount Warrant Bail Amount

CaseIndexDate Date Warrant Cancelled Date


CodeValue


Warrant Disposition Code


Warrant Disposition Reason Code

CaseIndexDate Date Warrant Expire Date


CodeValue

CaseIndexAmount Amount Warrant Fee Amount

CaseIndexDate Date Warrant Issuance Date


CodeValue

CaseIndexDate Date Warrant Order Date


CodeValue

CaseIndexDate Date Warrant Quashed Date


CodeValue

CaseIndexDate Date Warrant Recalled Date


CodeValue

CaseIndexDate Date Warrant Service Date


CodeValue

EXHIBIT I






Warrant Type Code

2.6 EDR Deployment Process

The General Deployment Process for AOC EDR is depicted/described below. Individual products may implement their own deployment details, testing strategies, rollback strategies or other conventions and are to be detailed in sub-topics pertaining to the product. Source control branching strategies generally follow the Git Flow Workflow. Additional information about Environments can be found in the Environment topic. The topic is divided into the following sections:

Deployment Process Product Life-Cycles

EXHIBIT I


1. Code is checked into source control. Different code branches are maintained for each Environment Tier.

2. A build is initiated (preferably automated by the integration server). Automated unit tests are executed as part of the build process.

3. upon successful build and test packages/files are staged for deployment 4. a release is initiated with the deployment server (preferably automated by the integration

server) 5. Deployment Server executes the deployment of components from staging to the relevant

environment and initiates any automated integration tests Product Life-Cycles

EXHIBIT I


1. Development Life-Cycle Deployment to environments for individual project teams to develop and test feature changes to EDR Products.

o a. the source from QA branch that is currently deployed to QA-Stage is branched into a Project team's "feature" branch, built and deployed to the Project's Dev environment

o b. Individual project developers pull/merge the Project's Dev branch into their Local environment

o c. Development, Deployment and Rollback is tested locally o d. Local changes are merged into the Project's development branch o e. Development, Deployment and Rollback is tested in the Project's development

environment o Teams repeat steps b-e until the QA Integration Life-Cycle

2. QA Integration Life-Cycle Deployment to server environments for Internal and "privileged" External project teams to Integrate changes to EDR Products or components.

o a. project teams ready for integration pull/merge the latest QA branch into the teams DEV level branch.

o b. products are built with integrated changes from the Team's DEV branch. Product Deployment and Rollback is tested in the integrating team's

EXHIBIT I


Development Environment. The team repeats a-b until their DEV branch includes all changes from the latest QA branch.

o c. The integrating team has their DEV branch merged into QA o d. products are built from QA with Deployment, Testing and Rollback executed in

the QA Integration Environment o e. products are built from QA with Deployment, Testing and Rollback executing in

QA-Volume. This varies from QA Integration in that the environment contains production scale data sizes and should be tested with production scale activity volumes.

3. Release Life-Cycle Deployment to Environments that are External facing

o a. QA source that has been successfully deployed and tested though the QA Integration life-cycle is merged into the Release branch

o b. products are built, Deployed and tested in the QA-Stage environment. Rollback should only occur in the event of Deployment failure or a critical testing failure

o c. products from step b are Deployed and tested in the Production environment o d. Rollback only occurs in the event of critical deployment failure or a critical

testing failure

2.7 EDR Security

Information related to security practice/procedures is contained with the topic and its sub-topics This topic contains the following sections.

Roles and Accounts

Roles and Accounts Information related to the roles/groups and user accounts relevant to the AOC EDR This section contains the following subsections.

Naming Conventions Roles Service Accounts Other Accounts

Naming Conventions All service accounts, groups and roles are base names where the name would be suffixed by an abbreviation of the environments DEV or QA. (e.g. RoleNameDEV, RoleNameQA, UserNameDEV, UserNameQA, etc.). The Production environment would omit the suffix (e.g. RoleName, UserName). Exceptions to this convention are noted in the details of each item.

Roles Please note the Naming Conventions related to Role Names

EDR_Developer

Developers of EDR Components (Excluded from Prod Environment)

EXHIBIT I


Member of Role EDR_Datasource

EDR_Tester

Testers of EDR Components (Excluded from Prod Environment)

EDR_Maintenance

Users or Applications that need Diagnostic permissions for EDR Application Components

EDR_DbMaintenance

Users or Applications that need diagnostic permissions for EDR Database instances

EDR_DeploymentAgent

Users that have permission to Edit build definitions, modify source control and initiate/promote deployments

EDR_Datareader

Applications or Users reading the EDR Database

EDR_Datasource

Applications or Users reading and writing to the EDR Database Service Accounts

Please note the Naming Conventions related to Account Names

SVC_EdrDataSvc

For the app pool(s) which the EDR web service runs Member of Role EDR_DataSource

SVC_EdrDeploy

For applications running in the deployment pipeline (single account that has access to all environments)

Granted dbo on all SQL Server Instances. Needed from execution of deployment scripts that modify schema.

Other Accounts

Please note the Naming Conventions related to Account Names

Support Email

Email Account/Group for documentation feedback/support

Deployment Email

Email Account for deployment applications to send notices with

2.8 Connecting to EDR OData Services

Step-By-Step: Connect to an OData Service

EXHIBIT I


Prerequisites

Visual Studio 2010 or greater.

LINQPad Example

In this example, you will query an OData service using the LINQPad. LINQPad is a popular tool

for constructing LINQ (Language-Integrated Query) queries. More about LINQ can be found

here: https://msdn.microsoft.com/en-us/library/bb397926.aspx

Download & Install

Download and install a free copy of LINQPad.

https://www.linqpad.net/

Install the downloaded copy of LINQPad

Create OData Connection

Open LINQPad and click ‘Add connection’.

Select WCF Data Services’ and click ‘Next >’

EXHIBIT I


In the URI field, enter the following address and click OK.

http://services.odata.org/V3/OData/OData.svc/

Query Service

Add the following LINQ query to a ‘Query Window’.

from p in Persons

EXHIBIT I


// Eagerly Loading of Person Detail

.Expand( "PersonDetail" )

select p

Select the OData source from the connection dropdown, and then click the Execute icon.

Review Results

In the results window you should see all of the records in the Persons table. Passing the

PersonDetail string to the Expand method notifies the service that the related person details

should also be retrieved.

EXHIBIT I


For extra credit, click the ‘Request Log’ and copy the URL to your clipboard.

Open a browser window and and past the URL into the address bar and hit “Enter”.

You’ll should see XML returned

Visual Studio Example

In this example, you will create a console application that performs a query against an OData

service.

Create Project

From the File menu select the ‘New->Project’ menu item.

Select the ‘Console Application’ template and click ‘OK’.

EXHIBIT I


Add Required OData Libraries

Right click the console project (ConsoleApplication1) and select ‘Manage NuGet Packages’.

If you don’t see the ‘Manage NuGet Packages’ icon then you’ll need to download ‘NuGet Package Manager’ from Visual Studio’s ‘Tools -> Extension Manager’ menu.

More Info: https://docs.nuget.org/consume/installing-nuget

* After the install, click the ‘Restart Now’ icon at the bottom right hand corner of the ‘Extension Manager’ dialog.

EXHIBIT I


Click ‘Online’ Tab on the left and select “NuGet.org”. Search ‘NuGet.org’ for the keyword

‘OData’ then install the ‘WCF Data Services Client for OData v1-3’.

Add Service Reference

Right click the console project and select ‘Add Service Reference’.

EXHIBIT I


Enter the service address ( http://services.odata.org/V3/OData/OData.svc/ ), click ‘Go’ then click

‘OK’.

EXHIBIT I


“DataServiceVersion with an unrecognized version ‘3.0’”

If you receive the following error:

You will need to install Microsoft’s ‘WCF Data Services RTM Tools’.

https://www.microsoft.com/en-us/download/details.aspx?id=45308

1) Close Visual Studio

EXHIBIT I


2) Run ‘WCF Data Services RTM Tools’ installer.

3) Start Visual Studio

4) Select your solution (ConsoleApplication.sln) from the ‘File->Recent Projects and Solutions’ menu.

5) Delete the ServiceReference1 service reference that generated the error.

6) Remove Reference to ‘System.Data.Services.Client’.

5) Perform ‘Add Service Reference’ steps again.

EXHIBIT I


Code Sample

Update the Main method with the following code.

static void Main( string [] args)

{

// new service ref

var service = new ServiceReference1

.DemoService( new Uri( "http://services.odata.org/V3/OData/OData.svc/" ));

// create query

var persons = from p in service.Persons

.Expand( "PersonDetail" )

select p;

// execute query

foreach ( var person in persons)

{

// write row results

Console .WriteLine( "{0,-2} {1,-18} {2,-2} {3,-5} {4}" ,

person.ID,

person.Name,

person.PersonDetail.Age,

person.PersonDetail.Gender,

person.PersonDetail.Phone);

}

// prevent console window from closing

Console .Read();

}

EXHIBIT I


Run Sample

Press ‘F5’ or click ‘Debug -> Start Debugging’.

Review Results

You should now see a console window populated with the results of your query.

exhibit i - edr technical environment i - edr... · washington state page 2 of 44 inh ede data...

Documents