IT environments in large institutional processes are often characterized by duplicated data. The reduction in cost of data warehouse creation and management has led to their proliferation, and it is often cheaper to err on the side of comprehensiveness when designing operating databases.
IT infrastructures of major financial institutions can feature dozens of operating data warehouses, resulting from either acquisitions or segmented business operations. Even as the MDM movement kicks into higher gear, the same data will be used in a variety of locations for different purposes. This will be fiercely defended by both DBA and GM’s alike, because access to data can often determine business success.
Location intelligence is the emerging term for information that allows an analytical conclusion about a geospatial location, e.g., distance to DSL switch, P&C insurance risk, demographic inclusion, traffic dynamics. This involves placing a point within one or more boundaries, and seeing where that point is relative to other points or boundaries.
How does a data architect make sure that this point-boundary integrity is maintained in an environment of data redundancy described above?
Consider Enterprise Address Management.
What if you could provide these capabilities to each DWH or operational data management system on demand:
- Provide geographic location information for an address (Geocode, lat/lon, place code), intersection address matching, parcel information, etc.
- Standardize or normalize Postal formats for world-wide addresses
- Merge multiple data lists/data bases based on address or location identities
- Merge NCOAlink, ACS COA, and other country COA address updates to multiple, heterogeneous databases with arbitrary frequency
- Complete postal addresses based on basic input (e.g., zip+4), transactional and batch, with all requisite pre- and post print image processing, e.g., RDI, DPV, EWS, and third party data
- Advanced data entry support for the capture and correction of postal addresses
Under the EAM principle, each Enterprise Application can use a common service to perform location intelligence processing suitable to its business processes. Postal processes are not necessarily interesting to marketing BI analysts; billing processes are primarily interested in postal fulfillment for customer locations.
Enterprise Address Management provides a central competence in managing, updating and processing location-based data for distributed enterprise applications
Most of the time when data comes from a Customer or data is entered by a CSO, there is a chance of getting wrong Postal code and typo in City name. Address management tool or data cleansing tool play very important role in resolving this.
My question is, how powerfull is these tools to handle address data worldwide?
Like in Countries like India and China is it possible to do geocoding by City name or address, i guess it is still challenging task to the industry.
Any comments!!
Thanks
Raghavendra Ganiga