Orange County NC Website
Browse       Search
DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 <br /> SOW Attachments G and H. Providing data in this format will ensure that data is properly imported into the system. Data <br /> not provided in this structure will not be considered for import. <br /> ❑ Data scrubbing/cleansing <br /> Any data scrubbing should be done by the customer prior to populating the DCT-DB. Data scrubbing and cleansing is not <br /> included in the EnerGov proposal. <br /> ❑ Required Fields <br /> Problems in data conversions typically result from customer data that has not been scrubbed prior to the data conversion <br /> process. There are certain fields in the EnerGov software which are required fields,and we cannot write records to the <br /> EnerGov master DB without populating these columns. Sometimes,these required fields will not be available in the legacy <br /> source data,so a simple default value can be written to the DCT-DB to fulfill the NOT NULL constraint. Tyler would <br /> write the default value as part of the conversion process. <br /> ❑ Custom Fields <br /> Most legacy systems will have some attribute fields that are not specified in the corresponding master table within DCT- <br /> DB. In the EnerGov software,we will refer to these as custom fields. Within each module,there will be a child table for <br /> such custom fields. Since these are specific to the legacy system(s),the customer may add columns to these tables in DCT- <br /> DB to accommodate any needed custom fields in the migration. <br /> ❑ Parsing data <br /> The data format is defined based on the fields that exist in the EnerGov module(street number and street name,for <br /> example). If the customer would like that data to be converted,the customer will have to break out its legacy data so that it <br /> matches the EnerGov data fields. <br /> Address Data: Tyler does not parse out address information for optimization purposes.Rather the customer is responsible <br /> to deliver the address information in the requested(preferred format).Tyler will import the address data delivered(format) <br /> and map the fields to the best possible location in the EnerGov system. Tyler is not responsible for cleanup of inconsistent <br /> addressing. <br /> Phone Numbers:Phone numbers are imported in the format in which the data is delivered to Tyler. Tyler is not <br /> responsible for cleanup of inconsistent numbering or sequencing. <br /> Individuals/Names: Individual names are imported in the format in which the data is delivered to Tyler. Tyler is not <br /> responsible for parsing out single name fields into First,Last,Middle,Company,etc. <br /> Contacts Data: Tyler creates a unique Contact ID for each contact in the EnerGov system,along with duplicate detection <br /> measures,to ensure that a contact is entered once,and only once. If contact data is not keyed in such a way that each <br /> instance of a person has one,and only one,contact record(the record with all of their attributes such as name,address, <br /> company,phone,etc.)in the data source,then the contacts associated with a record will typically be imported into a general <br /> information tab rather than into the EnerGov Enterprise Contacts Manager. <br /> ❑ Business-Specific Rules <br /> Business specific rules are handled in the software configuration process and cannot typically be mapped within the data <br /> conversion process.This includes but is not limited to EnerGov Intelligent Objects and EnerGov Case Workflows. <br /> ❑ Calendars&Scheduling <br /> EnerGov software can import scheduled hearings and meeting details;however any data residing on an actual calendar <br /> control is excluded from the scope of the data conversion. <br /> . tyler <br /> 41 <br />