Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Covering Business Intelligence, Integration & Analytics
   Covering Business Intelligence, Integration & Analytics Advanced Search

View all Portals

Scheduled Events

White Paper Library
Research Papers

View Job Listings
Post a job


DM Review Home
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

Buyer's Guide
Industry Events Calendar
Monthly Product Guides
Software Demo Lab
Vendor Listings

About Us
Press Releases
Advertising/Media Kit
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Meta Data & Knowledge Management:
MME Best Practices Case Study Allstate Insurance, Part 4

  Column published in DM Review Magazine
May 2005 Issue
  By David Marco

This column is adapted from the book Universal Meta Data Models by David Marco & Michael Jennings, John Wiley & Sons, 2004.

In part three of this five-part series on Allstate's managed meta data environment (MME), I walked through the meta data sourcing layer component of their MME. In this fourth installment, I will present the details of the meta data delivery layer of their MME.

Allstate's MME has a sophisticated meta data delivery layer, which has several different meta data delivery mechanisms. These mechanisms include meta data for the data warehouse, static data management,  DTDs and schemas, and viewers.

Meta Data for the Data Warehouse. Allstate's data warehouse is the most popular application of their meta data and is certainly their MME's driving force. The data warehouse's end-user query tool is directly linked to the meta data in the MME. This allows Allstate's data warehouse users to view English names (from the logical data model in the MME) rather than the cryptic physical names that would normally appear. The end users can view the descriptions created during the logical data modeling. In addition, all of the business values discovered through the analysis of the codes analysts are passed in the meta data to the end-user query tool so that instead of a data warehouse user needing to view "03" as a code, he or she can see the value of "automobile."

Static Data Management. As Allstate collected domain information and documented the valid codes and values, the application areas within the company started to ask if they could leverage this meta data directly in their applications. This led Allstate to create the ability to request the generation of static data tables. A static data table is simply the valid codes and values for one or more domains deployed to a table so that an application may use the data.

Over the years, when speaking and writing about meta data management, we discussed the idea that a future MME architectural trend is the desire of corporations to implement "closed loop" functionality. A closed-loop MME architecture feeds meta data from the MME directly into a corporation's IT applications. At the time, I stated that this approach is a natural progression of MME architecture; however, I was not aware of any corporation that had implemented this advanced technique - that is, until now. Allstate's MME has implemented closed-loop functionality in their MME architecture. Allstate extended their MME's capabilities by implementing a universal code translation (UCT) table. This table is populated with multiple enumerated domains and all their associated collections. This allows an application to utilize this table to translate from its "language," or representation of the code, to any other "language." Typically, they'd translate into another application's specific representation of that code if they were doing a point to point, or the common Web front-end. This table is maintained by the enterprise data management group and replicated to all nine regional operating centers throughout Allstate. Once an application implements the UCT, it no longer needs to make any program changes when new codes are deployed. Allstate's team leader of codes analysts and meta data services, Pam Gardell, commented, "Centralizing our ability to manage code data through linking our MME directly into Allstate applications has reduced the tremendous costs of managing these codes and greatly increased our flexibility to changing those codes over time."

DTD and Schemas. As the meta data for common messages is captured in the MME, the meta data is also generated from the repository and imported by the message broker product used by Allstate. This common event description is the basis for Allstate's "common namespace." This is the format that a sending application needs to translate "to," and "from" which a receiving application must translate.

Viewers. The MME has a great deal of value as a reference tool for both application developers and business users alike. As a result, Allstate custom developed a generic Web browser-based tool, the "Metadata Viewer," which allows anyone in the enterprise to view the meta data in the MME. For example, if someone needs to know the "Accident Type" codes used in the claims system or vehicle classifications in property and casualty, the information is now readily available.

Because the scope of the meta data can be a bit overwhelming for a user browsing the information, application-specific "views" have been constructed and made available through the creation of custom viewers. Currently, Allstate has deployed a "CMS Viewer" that presents the same information as the Metadata Viewer but orients its display toward a user who is only interested in the code information from the MME.

In my final installment of this series on Allstate's world-class MME, I will discuss their MME's return on investment and future directions.


For more information on related topics visit the following related portals...
Meta Data.

David Marco is an internationally recognized expert in the fields of enterprise architecture, data warehousing and business intelligence and is the world's foremost authority on meta data. He is the author of Universal Meta Data Models (Wiley, 2004) and Building and Managing the Meta Data Repository: A Full Life-Cycle Guide (Wiley, 2000). Marco has taught at the University of Chicago and DePaul University, and in 2004 he was selected to the prestigious Crain's Chicago Business "Top 40 Under 40."  He is the founder and president of Enterprise Warehousing Solutions, Inc., a GSA schedule and Chicago-headquartered strategic partner and systems integrator dedicated to providing companies and large government agencies with best-in-class business intelligence solutions using data warehousing and meta data repository technologies. He may be reached at (866) EWS-1100 or via e-mail at DMarco@EWSolutions.com.

Solutions Marketplace
Provided by IndustryBrains

Verify Data at the Point of Collection: Free Trial
Protect against fraud, waste and excess marketing costs by cleaning your customer database of inaccurate, incomplete or undeliverable addresses. Add on phone check, name parsing and geo-coding as needed. FREE trial of Data Quality dev tools here.

Design Databases with ER/Studio: Free Trial
ER/Studio delivers next-generation data modeling. Multiple, distinct physical models based on a single logical model give you the tools you need to manage complex database environments and critical metadata in an intuitive user interface.

Free EII Buyer's Guide
Understand EII - Trends. Tech. Apps. Calculate ROI. Download Now.

Data Mining: Levels I, II & III
Learn how experts build and deploy predictive models by attending The Modeling Agency's vendor-neutral courses. Leverage valuable information hidden within your data through predictive analytics. Click through to view upcoming events.

Click here to advertise in this space

View Full Issue View Full Magazine Issue
E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2006 DM Review and SourceMedia, Inc. All rights reserved.
SourceMedia is an Investcorp company.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.