Location Hub™ Business Use Cases For the Utilities Industry

KEY ISSUES

• As utility companies are driven by safety, one maintained address data repository is vital for all services
• Integration within different sides of their enterprise in order to quickly respond to the serviceability of their customers, particularly to better prioritize preventative maintenance
• Address standardization in order to have a consistent business standard which will improve unit integration and communication
• Address accuracy and address validation is essential to establish the precise location and reliability of an address record, particularly in cases when utility companies need to communicate address information to 9-1-1
• Accurate coordinate information, particularly at high precision, is critical for emergency preparedness exercises and for routing
• Gas companies require the ability to recognize and identify potential clients so as not to overlook revenue-increasing opportunities
• Gas companies require the ability to recognize and identify multiple-dwelling units (MDU) so as not to overlook areas suitable for increasing service penetration
• Attribute enrichment of address data, from the integration of third party data, to provide increased intelligence about each address record and fuel further decision-making industry processes
• Ability to more efficiently record data in the field and to rapidly absorb field audit information into the appropriate database

LOCATION HUB™ SOLUTION

• A single standardized Master Address Management repository consisting of multiple source address data attribute enrichment
• Sophisticated exact and fuzzy matching rules which can allow for a substantial increase in recognizing and matching address records which are missing key address elements or those which are incorrectly represented
• Rich aliasing of address data, based on fourteen years of address data experience at DMTI, in order to further increase address record matching rates
• A unique address identifier that can allow utility companies to persistently link address records through once disparate databases
• Advanced address parsing and standardization and is able to convert multiple address data formats
• A unique and sophisticated address validation process which evaluates the reality of address records and provides the user with an educated score of confidence in that reality
• Ability to provide coordinate information at accurate high precision quality
• Ability to identify common customers among various lines of business and to identify potential customer opportunities using superior address recognition and address record matching
• Advanced MDU (multiple-dwelling unit) address collection within the Master Address Management repository enabling businesses to increase their market and service penetration in these areas
• Mobile applications which will allow field auditors to remotely view pre-populated address and attribute related data to be verified or updated in the field. Photographs can be captured on the device and uploaded to the appropriate database

The Utilities user of the Location Hub™ portal can import three customer databases, such as services and billing. The address records are batch-processed through Location Hub™ Address Recognition Engine (ARE), where the records are parsed, standardized and recognized against Location Hub™ Master Address System (MAS). Address records that are not recognized during this process are considered Fall-Out (F/O) and these records are sent for Manual Resolution within DMTI. The Fall-Out address records fall into three categories: insufficient due to missing or erroneous components, not found in MAS for various reasons or fixed and sent through ARE a second time. Those address records which are recognized a second time, are added back to the databases as recognized addresses for further processing. In this example, address records that were not found were also added back to the database for further processing.

The resulting database consists of all recognized addresses from the three customer databases, all address records were assigned UAID and UUAID, and common and uncommon customer records between the three databases are identified through matching.