|Sign-Up for Free Exclusive Services:||Portals|||||eNewsletters|||||Web Seminars|||||dataWarehouse.com|||||DM Review Magazine|
|Covering Business Intelligence, Integration & Analytics||Advanced Search|
Beyond the Data Warehouse:
Moving beyond rows and columns requires advanced meta data. There is a rich menu of beneficial applications that can only be efficient and sustainable if they are based on extreme information maturity, i.e., a formal enterprise data management process.
Normally, the content of these articles is planned months in advance. Editorial calendars, travel, billable work (now there's a concept!) all influence when material is published. This month we are revising the sequence. This is due to the breath-taking amount of mail after the previous column, "Practical Knowledge Management (or What Comes After the Rows and Columns)". posted to DMReview.com in October, 2002. Many of the e-mails asked us to delve into the extreme information maturity aspect, as many shops are apparently trying to get a handle on information management as a more formal component of business strategy. So we will do that one first and then tie back unstructured information and collaborative intelligence in upcoming articles and wrap up by revisiting all the topics and supplying some real-life examples.
As we stated in the last article, the knowledge management (KM) discipline is providing a host of neat approaches for new information and knowledge challenges. But unlike IT, KM has turned into a group of philosophies rather than a corporate discipline. The KM concepts are shepherding many folks through the evolution from historical and operational rows and columns and predictable latency to predictive, proactive uses of structured and unstructured information. The upshot of all of this is the need to create a layer of meta data that will literally take an active part in managing the business. The KM concepts that are supported are:
The extended BI/DW processes supported (and hinting heavily at KM as well) are:
Obviously, these new meta data requirements reflect a more rigid philosophy for the management of information (and knowledge) as an asset. Not an asset in a figurative sense, but a real, accountable component of an organization's value. This functionality and discipline needs to be incorporated into existing DW/BI programs as well as used for the extended DW. New information management processes are required to support moving through enterprise data management (EDM) to an extreme maturity level of knowledge and information asset management.
Note: The term that seems to be arising to cover this area is enterprise data management (EDM). While I am not sure if this term will "stick," we can use it in this article.
From an evolutionary view, EDM starts by deemphasizing business events in terms of collection and processing. The emphasis becomes twofold: 1) process data so the organization keeps useful, high quality information, and 2) view data from a process standpoint (if it isn't used, it has no value). Therefore, EDM places an emphasis on workflow.
The meta data in this scenario is obviously active. There will be multiple layers of meta data. (Yes Virginia, there will be meta meta data - sigh.) EDM will manage various layers of abstraction of meta data, processes and a wide range of other information and knowledge content. The Object Management Group (OMG) calls this a Model Driven Architecture. That is a good phrase. The figure below is a recap of the OMG layers of abstraction, called the Meta Object Facility (MOF) - go to www.omg.org to download some excellent information on this topic.
Figure 1: Object Management Group's Meta Object Facility
Notice abstraction, notice that the meta layers accommodate all types of content and honors other meta models that may previously existed.
Besides layers of abstraction, the technology for EDM will feature XML. While XML offers little value from an operational performance viewpoint (so far), it is quite excellent at collecting and managing the necessary meta data aspects for EDM.
Well beyond technology for collection, documentation and navigation, the meta data aspect of these concepts offers some new and interesting content. The requirements for extreme information maturity carry a few particular wrinkles, namely some new meta data requirements and new aspects of managing the information asset.
The new meta data requirements for these types of information and knowledge functions range from advanced to extreme. It is important to note that meta data is not an option, as it has been with pure data warehouses. There must be a meta data layer that contains all of the traditional functionality as well as new components.
Remember the preceding meta data content is in addition to "traditional" meta data information - definitions, ranges, synonyms, security etc. The Figure 2 demonstrates how the various meta data types interact with advanced information and knowledge functions.
What type of benefits and projects will this future meta data support? After all, the meta data layer isn't going to be done first; rather, an EDM philosophy will evolve the meta layer. Here is a brief example of where the meta layer we have discussed comes in handy.
A specialty manufacturer can design and produce thousands of different items but produces orders in relatively small quantities. Therefore, drawing upon the various setups for a job and product is knowledge-intensive. A portal is implemented that accesses a knowledge base of prior setups. In addition, operators can access best practices and customer specifications to alter setups.
The Figure 3 demonstrates a sample evolution that is enabled by maturing meta data content. Note that, excluding the top two rectangles; these steps are obtainable by most shops familiar with managing a data warehouse or sophisticated content management. We will explore how to develop your own evolution path in the fourth article in this series.
Moving beyond rows and columns requires advanced meta data. Plain and simple. Without a sound EDM evolution strategy, organization may be able to answer "How did we do that?" questions but only on a siloed basis. The benefits, like those of older data marts, will soon disappear in the morass of non-integration. There is a rich menu of beneficial applications that can only be efficient and sustainable if they are based on extreme information maturity, i.e., a formal enterprise data management process.
When John is not writing poetry as a hobby, he is a director for Navigant Consulting, which recently acquired KI Solutions, a management consulting firm specializing in knowledge and information asset management and strategic business intelligence planning and delivery. Ladley is an internationally recognized speaker and, more importantly, hands-on practitioner, of information and knowledge management solutions. He can be reached at email@example.com. Comments, ideas, questions and corroborating or contradictory examples are welcomed.
|E-Mail This Column|