Laserfiche WebLink
<br /> <br /> <br /> Page 18 <br /> the City will ensure that Avocette resources have access to a Dev or Test version of the 3rd party system for interface development. All <br />interfaces will be developed against 1 (one), agreed upon version of the 3rd party system. <br /> the City will provide Avocette with access to test and development environments (where available) for each the City systems that require <br />integration with Clariti Platform. <br />2..7.2 Data Conversion <br />The following information provides detail related to the scope of Avocette’s data conversion services. Due to the inherent complexity of <br />conversion activities, it is critical to address and understand common questions and misconceptions. Any conversion activity or requirement not <br />included in this section is considered out of scope and may be addressed through a Change Request for Avocette services. <br /> <br /> Data Conversion: General Information and Requirements for Conversions <br /> The standard data conversion includes the conversion of active transactional data to the Clariti database when a configured destination <br />exists. In the event there is no destination record type (section 2.2.1) for legacy transactional data then it will be required to be converted <br />as best fits into another area of the configuration or excluded from the conversion effort. The decision on the approach for this data is the <br />responsibility of the City. For all data that requires conversion from SAPIN into the Clariti, a destination record type must be identified in <br />section 2.21 of this document. Data fields within those record types will be identified during the analysis phase. <br /> Avocette and the City will perform unit testing of the conversion program including spot checks of the data within Clariti in order to identify <br />if data corruption issues exist. Extensive quality assurance of the converted data by the City is required in order to ensure accurate <br />transfer of data. Where feasible, control total reports will be built to compare total records from the source system against what has been <br />converted into the system (e.g. Total number of contacts). <br /> A mutually agreed on and signed off build of configuration must be available before Avocette will begin the data conversion mapping effort. <br />Avocette will use existing database information as part of developing the To-Be and build configuration documentation to ensure required <br />data is not missed from data conversion. <br /> Data Conversion Assumptions <br /> “As-Is” Approach: Conversion of transactional tables, Professional License data is executed “As-is” into Clariti. “As-is” means that the <br />data will be transformed as mapped to existing configuration elements in Clariti. The conversion process will not create configuration <br />data or alter the mapped data when processed into Clariti. Additionally, this means if invalid, inaccurate, or incomplete data is provided, it <br />will be loaded into Clariti “As-Is”. All legacy data cleanup and required transformation must occur prior to execution into Clariti. the City <br />will be required to perform the data cleanup and Avocette will provide support and recommendations as required.