TRITECH SOFTWARE SYSTEMS -2015 - Laserfiche WebLink

Home Browse Search

Project Execution delivery to TriTech. TriTech will assume that all data delivered is legitimate to use in the Data Conversions, and will begin their analysis upon receipt of the legacy data. If the Client chooses to rename storage locations they used in the legacy system they must produce a list of such changes. Similarly, if the Client creates new and different status codes, property description codes, or similar, the Client also needs to provide those to TriTech. The process of analysis and data mapping will require collaboration between TriTech and the Client, and it is necessary for the Client to provide subject matter experts to TriTech to answer any questions that arise during the data mapping and conversion process. It is also required that the Client supply a data dictionary defining all of the data items that are to be included the data conversions. This must be in a machine-readable (i.e. no scanned copies, pdfs, etc.) TriTech and the Client will collaborate to develop the criteria to be used for Master Name resolution of duplicate names. As part of the data mapping exercise, the Client will manually enter a minimum of 3 representative records into each module to be included as part of the Data Conversion. The data used for entry must be included and identified in the initial data extraction supplied to TriTech. A TriTech Business Analyst will assist with this task. Once the Client has completed the sample data entry, they will supply TriTech with a backup of the Inform RMS database plus screen shots of all forms used for this sample data entry. TriTech will further annotate these screen shots and include them in the Operational Scenario Document that TriTech will generate. The results of TriTech's analysis of the data and data mapping will be documented in an OSD, and will be provided to the Client for review and approval prior to creating the conversion scripts. TriTech will map only those fields from the Client's legacy database into the appropriate Inform RMS database module where there is a strong correlation of data type and data use between the two systems. All pertinent legacy data from each module in the Client's legacy database will be captured in a text narrative and attached to the appropriate parent record in the Inform RMS database. This narrative will be available to the user when viewing imported records in the TriTech product. In the event that the Client makes any modification to their original data in order to include it in an Inform RMS record, they must fully document the transformation process used. All transformations so supplied must be able to be implemented via scripts vs. "human -interpretive" processes. These include, but are not limited to names and addresses. Once imported, the Evidence, Evidence_ Items, Evidence_ Location, Evidence_ Cases, and Evidence Names data will be available in Inform RMS. TriTech will convert a sample set of the evidence data into the Inform RMS for the Client to review and test, and upon approval of the accuracy of the converted test data set, the entire data will be imported to the Inform RMS. The delta between the last data submission and the Go Live date will be converted and inserted into the Inform RMS post Go Live. T6.6.1.1 TriTech Responsibilities a) Perform an analysis of the legacy Evidence data, provided by the Client. b) Collaborate with the Client in defining the data mapping, as well the resolution of the duplicate names. e) Provide an Operational Scenario Document (OSD) prior to developing the scripts for the data conversions. d) Create the necessary scripts for the data transfer. e) Perform the initial data conversion and import for review by the Client. f) Perform the final data conversion and import into the Inform RMS. 47