Blog: Dan E. Linstedt« IT from Cost Center to Profit Center - Next Steps | Main | Appliances and EDW Integration, a second look » The Answer? MDM - MMDM - SOA and RegistriesThe question? What does the new business initiative really need to focus on? Today's business initiatives seem to be headed in many different directions, from SOA to MDM to registries, and business processes. The issue is that when different initiatives take on different directions (rather than a consolidated view and set of drivers) they all end up at different destinations. The cost is heart-ache, silo'd solutions, and a maintenance nightmare. The bottom line is that there is convergence afoot. I've written about this over the past 5 years in my convergence articles on TDAN, B-Eye Network, and Teradata Magazine. In this entry we'll explore what business should do, and how they should approach these very different initiatives (all with a common goal). MDM - Master Data Management And of course the tools of the trade: Ok now that we got that out of the way... Businesses have been divesting their interests for years (at least when it comes to I.T. projects). It's time to get a little convergence back into the mix. Businesses who start separate initiatives for each of the categories above will quickly find that they end up with one or more of the following: * Silo'd answer sets And so on... Executive staff should realize that the good things in life don't come cheap, or easy. After all, they've worked extremely hard to get where they are. IT is no different, and should be treated as a single operational business unit. IT's initiatives should be aligned, but in a way that allows IT to work together rather than against each other. So you've heard this all before have you? What does this have to do with lining up: MDM, MMDM, SOA, and Registries? Underneath the SOA are Master Data, Master Metadata, Web Services, Registries, Auditability, EDW, OLTP, data marts, and Information Integration. All of these are the components necessary to make SOA a success. But remember, SOA is a journey not a destination - just like alignment of IT is a continuous process (it never ends). So what do all of these have in common? From a project standpoint: There is also a certain dependency (order) in which these items must be executed. If one is left out of the process chain, then the business stands to suffer at the end of the day. Convergence is upon us, and real-time (active), metadata (descriptive), data sets (asset base), registries (organization of all data and metadata underneath), security and services (access layers) are all a part of the enterprise initiative to bring IT in to focus. More to come on this topic - if you have questions, I'd like to try to answer them. Feel free to ask publicly or privately. Cheers, |
Comments
Interesting stuff, Dan. We all know that much of the focus of SOA is in "wrapping legacy applications." Everyone talks about that. But two things people are not talking about are quite germane to this entry.
First, much of the purpose of wrapping legacy is to make existing _data_ available in a new/better way. So it's really the data people are after, not an invocation of the lagacy application. Hence the term "Data Web Services" people are starting to use in order to distinguish.
Second, and here comes the metadata (or lack thereof) issue, where is the metadata that tells me what I'm looking at? The SOA registry/repository may have WSDL and some metadata about the service, but does it extend back to the data? So the same old metadata issues arise - What does 'customer' mean in the WSDL's XML schema? How did they compute that value? What are the data sources for this Web Service? So it does seem that the SOA and metadata crowds are going to have to start getting together. A joint TDWI/W3C conference?...
Posted by: Tim Matthews | May 15, 2006 11:15 AM
Good Answer Dan...
I may get cooked for this, but Enterprise Information Management to me includes both structured and unstructured data. The need for what I bundle as Enterprise Metadata, Enterprise Master Data, Enterprise Taxonomy and Enterprise Controlled Vocabulary management is there for many of the same reasons...
In Content, Document and Records Management... the controlled list of values describing these resources need the same type of management as the customer master table does...
Its about quality, timely, synchronized results.
I have read definitions that try to define metadata as the column name and datatype.... Does the definition of metadata change from one content repository architecture to another....
Why is it so important to distinguish Master Data as something to do with a transactional system?
Its all about managing controlled values so they can be shared across the enterprise..
Posted by: Ray White | May 30, 2006 12:18 PM