Andrew White

A member of the Gartner Blog Network

Andrew White header image 2

MDM and the Semantic Enterprise

December 12th, 2008 · 5 Comments

About two years ago Kathy Harris (see her blog here), a colleague of mine, and I spent some time with an idea that went nowhere.  The idea we explored the issue that arises when firms segment their customers, yet customers don’t always follow predictable patterns of behavior that are implied by the suppliers segmentation of the customer.  Still with me? 

 

Many firms segment their customers in order to focus energies and services more effectively.  We all know the truism that some customers are more important than others (just think about the period end to prove the point) but most firms are not able to treat customers equally even if they wanted too, since resources are finite.  So customer segmentation makes very good sense; it should support notions of leverage of supplier resources in order to better relationships and revenue exchange.  But, the way firms segment their customers do not, as a rule, follow the methods by which customers segment themselves!  So the question arose: would it be better (i.e. more revenue) for the supplier if they could a) understand how customers segment themselves, and b) can a supplier actually relate this segmentation to how they do business?  Can an inside-out viewer understand an outside-in view, and map to it?

 

Little did I know but this question had some roots in semantics, and MDM. But before I can make that link, we need to first look at segmentation.  Just look at your son or daughter and evaluate how they define their social networks – both online and offline.  These networks, the aggregation of them, represent a near-unique structure that would large numbers of preferences, likes, and intentions.  But these segments are self-described (with respect to the firm, even if they are offered by 3rd parties who want you to join their network), and most likely not even related to the suppliers of products and services.  Kathy and I came to the conclusion, 2 years ago, that there were two maps that needed to be bridged: one map represents how the firm looks at its customers and market; and the other is how the individual customer relates to all other market stake-holders.  In fact, the problem is how to map ontology’s.

 

Now before you go all bleary eyed on me, don’t panic!  This is not that hard to talk about, really.  As Wikipedia states, “An ontology in computer science and information science is a formal representation of a set of concepts within a domain and the relationships between those concepts. It is used to reason about the properties of that domain, and may be used to define the domain.”  So a very large and complex ontology could be used to describe how my son connects and relates to all manner of networks; and a much simpler one could be used to describe how a firm perceives its markets and customers, and how they relate to each other and how they are segmented.  

 

MDM comes in as part of the semantic dialog in that to bridge the ontology’s, some semantic mapping needs to take place and where would you start, but with the master data that is re-used across the ontology’s: the common keys, if you will.  So why this post today?  It so happened that I spent yesterday with a large technology vendors who is researching (they have a large technology research body) how to get commercial value from, and I paraphrase, the semantic enterprise to the semantic web.  I coined the term semantic enterprise 5 years ago when I presented, with another colleague of mine, Simon Hayward, on the topic of the Connected Enterprise.  The premise was: how does a firm change its behavior of semantics were pure and consistently clean across the enterprise.  Today of course we spend a lot of our IT budget coping with the fact that much of our data is messed up, duplicated, of poor quality, and so on.  Semantic are rarely top of mind of executives, but it seems that semantics, or the miss management of them, are the root of many of our mutual ills.

 

At least I found a peer in industry that is looking at the same problem- and a peer that has some emerging technology that may, in time, prove valuable.  And whoever thought that talking about semantic and ontology’s was boring?

Share:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • LinkedIn
  • Live
  • MySpace
  • NewsVine
  • Reddit
  • Slashdot
  • StumbleUpon
  • Technorati

Tags: Ontology · Semantics

5 responses so far ↓

  • 1 Kingsley Idehen // Dec 13, 2008 at 2:30 pm

    Andrew,

    MDM (which is grounded on an Entity-Attribute-Value data model) is one of the fundamental areas of enterprise data & information integration that benefits from technologies emerging from the “Semantic Web” vision realm.

    For example, Let’s take the emergent “Linked Data” meme which is centered on the ability to construct Entity IDs (or Object IDs) using HTTP. In the MDM scenario this means giving HTTP based IDs to each “Customer”, “Order”, “Order Item”, “Employee”, “Product”, “Product Category” etc.. And due to the inherent power and ubiquity of HTTP in networked environments (e.g. World Wide Web or Intranets) you are able to access Entitiy descriptions (i.e., de-reference the attributes and relationships graphs in different representations e.g. HTML). This also means simply integration of data across MDM solutions.

    I’ve been writing about some of these matters for a while and my blog contains a plethora of links to live examples such as:

    1. http://dbpedia.org/resource/Linked_Data – showing the same principles using Wikipedia data via DBpedia project
    2. http://demo.openlinksw.com/Northwind/Customer/ALFKI
    3. http://data.openlinksw.com/oplweb/product_family/virtuoso – Product Information Integration (another realm associated with MDM)
    4. http://data.openlinksw.com/oplweb/product_family/virtuoso – more detailed product release data .

    Kingsley Idehen

  • 2 Kingsley Idehen // Dec 13, 2008 at 2:33 pm

    Andrew,

    Two additional links in relation to MDM and RDF based Linked Data:

    1. http://tinyurl.com/6a24ts – correction for last link in my earlier comment

    2. http://tinyurl.com/6xerjd – a presentation of Linked Data that I gave at Linked Data Planet earlier this year.

    Kingsley

  • 3 Brian Schulte // Dec 14, 2008 at 10:34 am

    Customer segmentation is certainly a good place to try to engage business management on the topic. But, as you said in your blog, our big problem is still the money spent on “coping with the fact that much of our data is messed up…”. Tuning and polishing customer segmentation can only happen when master data is rock solid. Shouldn’t we be thinking about how we can introduce ontology-based solutions into the fundamentals of the MDM practice as it is still a very difficult, labor-intensive and expensive undertaking?

  • 4 Andrew White // Dec 15, 2008 at 9:56 am

    Can MDM ever be “rock solid”? I talk with a lot of customers and I don’t think that there are many examples of, “rock solid” MDM. Most practical implementations make some great progress, but I think that the real world is limited to, “get something going, as best as you can, and build from there”. Seems to me that MDM is a long, long journey; one we have been on for a long time even before we used the term, MDM. However, your point overall makes a lot of sense to me overall: clean up the data before you start to take critical decisions based on it.

  • 5 Brian Schulte // Mar 1, 2009 at 12:41 pm

    Good point. The term “rock solid” is over-the-top. I’ll modify by point to say that until you’ve got ’something going’ with MDM you should be careful setting expectations about using new technology to get you better information. (managing expectations is easier said than done) So when I think of ontologies and the semantic web I would like to see if they can make MDM easier – - before building on a house of cards.

    Kingsley – I had trouble getting to your last 2 links.

Leave a Comment