Location Hub™ Use Cases for Emergency Response Information

KEY NEEDS

• Require address data formats which meet 911 dispatch regulatory and Local Service Request (LSR) Requirements
• Address validation which can establish the reliability of an address record
• Attribute enrichment of address data to provide increased intelligence about each address record and fuel further decision-making processes
• Matching new customer point address databases with range Master Street Address Guide (MSAG) address databases

LOCATION HUB™ SOLUTION

• Ability to provide sophisticated parsing and standardization of addresses to meet LSR and 911 requirements
• Ability to provide a unique and sophisticated validation process which evaluates the reality of address records and provides the user with an educated score of confidence in that reality
• Multiple source address data attribute enrichment allows address data to be populated with coordinate information and additional attribution, based on the user requirements
• Ability for the user to match point customer addresses with Master Street Address Guide (MSAG) range addresses using the Database Operations option available in the Location Hub^™ portal
• Ability to increase matching rates between new customer databases and MSAG databases using DMTI unique address ID, fuzzy logic and other business rules, which have been developed through many years of MSAG experience at DMTI

A Location Hub™ portal user can input two databases, a current MSAG and a point address file, such as a database of new customers. Both address databases are batch-processed through Location Hub^™ Address Recognition Engine (ARE) and all address records are parsed, standardized and recognized in the Master Address Space (MAS). Matching is performed by the user in the Location Hub^™ portal using Dataset Operations. The resulting database is composed of the original new customer addresses with the addition of the MSAG standard addresses.