Laserfiche WebLink
DocuSign Envelope ID: A69C2874-A23C-4EBA-AE3F-17C057920A28 <br />I� <br />2.2.10 Records I CaIDOJ I CIBRS Interface: Axon will deliver an <br />interface between Axon Records and Cal DOJ for <br />submission of CIBRS reports from Axon Records. <br />2.2.11 Records I Llnx I Data Export: Axon will build an interface <br />with LInX where Axon will export incident data to the LInX <br />system. The specific datapoints and method of transfer <br />will be determined during the Requirements phase of the <br />project. <br />2.2.12 Records I LexisNexis Virtual Crime Center I Data Export: <br />Axon will build an interface with LexisNexis' Virtual Crime <br />Center where Axon will export incident data to the Virtual <br />Crime Center system. The specific datapoints and method <br />of transfer will be determined during the Requirements <br />phase of the project. <br />2.2.13 Records I Auto -Return I Vehicle Impound Interface: Axon <br />will build an interface with Auto -Return that will import <br />vehicle data from the Auto -Return system, to prepopulate <br />the impound form in Axon Records. <br />GO -LIVE CONTINGENCY <br />Before interfaces are complete, the agency may Go -Live. This does not <br />relieve Axon from completing the interfaces, but the agency will be <br />charged upon using the software. <br />2.3 DATA CONVERSION <br />Axon implements a structured methodology for converting data from the <br />agency's legacy system to the product. The agency is responsible for <br />providing Axon with extracted data in a format that can be used by Axon <br />for import. The preferred method for delivering legacy data to Axon is <br />by using the Microsoft Data Migration Assistant. The next best method <br />is for the agency to send a .bacpac file to Axon. If neither method is <br />available, a direct query through the Microsoft Self Hosted Integration <br />Runtime (SHIRt) can be used. <br />Axon queries the data to identify completeness, missing values, and <br />other measures of data integrity across records and provides the <br />agency with detailed findings. The agency may or may not elect to <br />process the data further to address completeness or may have Axon <br />move forward with the conversion process. <br />Subject to the data conversion plan, Axon can perform an initial <br />conversion to inject the data into the product training and/or <br />production instance(s) prior to Go -Live. A second conversion is <br />PAGE <br />