Location Hub™ Business Use Cases For the Telecommunications Industry

KEY ISSUES

• Address standardization in order to have a consistent business standard which will improve business unit data integration and communication
• Address validation which can establish the reliability of address records
• Attribute enrichment of address data to provide increased intelligence about each address record and fuel further decision-making business processes
• Integration within different sides of their enterprise in order to quickly respond to the serviceability of customers, such as integration between engineering, invoicing and customer service
• Increase address record match rates between business units, such as marketing and operational units, in order to identify additional revenue opportunities
• Ability to recognize and identify potential clients within serviceable boundaries so as not to overlook revenue-increasing opportunities
• Ability to recognize and identify multiple-dwelling units (MDU) so as not to overlook areas suitable for increasing service penetration and areas where revenue can be increased through product-layering
• Tools to make more informed and cost-effective decisions regarding marketing strategies and engineering plans

LOCATION HUB™ SOLUTION

• A single standardized Master Address Management repository consisting of multiple source address data attribute enrichment
• 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
• 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 universal address identifier that can allow businesses to persistently link address records through once disparate databases
• 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
• Ability to perform dataset operations (add, subtract and join functions) on address record databases in order to identify infill and common customers

The Telecommunications user of the Location Hub™ portal can import two customer databases, such as service and billing. The address records are batch-processed through Location Hub^TM 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 Process 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. The resulting database consists of all recognized addresses from the two customer databases, all address records were assigned UAID and UUAID, and common and uncommon customer records between the two databases are identified through matching.

The customer address records, created from the previous process, are matched to Location Hub™ Master Validated Record and can also be matched to a territory boundary. In this way, prospective customer data can be extracted from the Master Validated Record, within boundaries serviceable by the Telecommunications user. The resulting database consists of validated new customer addresses and any attributes, which are required by the user, to be attached to these addresses for various purposes.