My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CourtView Justice Soultions Inc. 5/9/2016
>
Contracts
>
6 Years Then Destroy
>
2017
>
CourtView Justice Soultions Inc. 5/9/2016
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/23/2017 10:16:44 AM
Creation date
6/8/2016 10:28:45 AM
Metadata
Fields
Template:
Contracts
Contractor's Name
CourtView Justice Soultions Inc.
Approval Date
5/9/2016
Council Approval Date
4/27/2016
End Date
12/31/2017
Department
Information Technology
Department Project Manager
Steven Hellyer
Subject / Project Title
Migration to JWorks Case Management Software
Tracking Number
0000109
Total Compensation
$66,277.34
Contract Type
Agreement
Contract Subtype
Technology
Retention Period
6 Years Then Destroy
Document Relationships
CourtView Justice Solutions Inc. 12/31/2017 Amendment 1
(Contract)
Path:
\Records\City Clerk\Contracts\6 Years Then Destroy\2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
65
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Data Migration (WBS 4) <br /> Data Migration enables the City to retain the electronic case histories that have been assembled <br /> over time in legacy systems and/or processes. This legacy data is processed and mapped to fit <br /> within the JWorks data structures. <br /> Data Conversion Overview: <br /> CJS has identified that legacy data currently exists in DAMION <br /> Note: For this effort, CJS has included services to migrate data from Oracle to SQL Server. <br /> The conversion process will require City review of legacy data and will provide the opportunity for <br /> the City to perform data analysis and clean-up, plus mapping of data elements to the JWorks data <br /> structures prior to moving data into the JWorks product. <br /> Conversion Plan: <br /> This Statement of Work includes a high-level overview of the proven strategy that CJS utilizes for <br /> data conversion of legacy data into the JWorks database. CJS will expand on this as well as update <br /> specific plans for the conversion effort. Part of the planning effort will be to make final decisions as <br /> to what legacy data will be converted through an automated data conversion effort. CJS will <br /> facilitate a data conversion planning session(s)with staff and provide a Conversion Plan deliverable <br /> for review and approval. This will occur once for the entire project, representing all implementation <br /> phases. <br /> The CJS conversion methodology includes seven (7) distinct steps: <br /> • Data Mapping Business Rules <br /> • Script Development <br /> • Data Checking <br /> • Sample Data Load <br /> • Mock Implementation / Run <br /> • Final Conversion Implementation / Run <br /> • Stabilization <br /> The activities of each of these conversion steps are described briefly below. <br /> CJS has included '/2 service day for the completion of a data conversion plan. <br /> Data Mapping Business Rules: <br /> CJS and the City will analyze the legacy system data model and determine which data needs to be <br /> transported to JWorks and where it will be viewed within the application. The City is required to <br /> place its existing data into the CJS conversion data model. Detailed worksheets will be provided <br /> outlining the format of these files. <br /> The City is responsible for providing the data extraction files in the required format. Detailed <br /> worksheets will be provided which outline the attributes that are required for each file. <br /> All files must be in ASCII text files having fixed length data attributes, as outlined in the CJS <br /> Standard Format worksheets. CJS will provide Standard Format worksheets as part of the <br /> conversion effort. <br /> CourtVIEW P a g e 1 10 <br /> JUST CF SO:U*IONS <br />
The URL can be used to link to this page
Your browser does not support the video tag.