IBM MDM Hybrid Style implementation

IBM MDM V11 release marked a significant change in the way MDM was being implemented in the market. It provide a solution that could support various styles of MDM by performing one single installation and that was HYBRID MDM. This support in V11 provided capability where customer could easily transition from registry to transactional style or co-exist their datasources in each of these styles and at the same time have a centralized MDM solution across the enterprise.

The concept is very simple. The customer has a set of datasources and some or most of these sources want to manage their own data. Well, they can keep on doing that in Virtual MDM (old Initiate Engine) in V11 .There are some other datasources which are transactional and all thier data and attributes are stored in the centralized MDM system. Well that is what Physical MDM (aka old DWL) is all about. But using V11, it is easily possible to move some of the data from Virtual MDM to Physical and persist is as a single unique entity by enabling a single switch during installation of IBM MDM V11.

This is a very unique capability, because there is a lot of MDM requirement in the market around this case. Look at some of the State Resident Hub requirements at State level in India for MDM. There are around 30-40 different departments supported in State Governments like Pension, Scholarship, Ration Cards and each of them want to identify the uniqueness of the resident across these datasources and at the same time keep the ownership of this data because of the propriety attributes. They could easily start with Virtual MDM and move to Physical. As and when they add new departments all of them could do these transitions.

Acquisitions are other scenario where this capability can be a huge advantage to bring in the acquired data into a centralized repository using this capability.

There will be enhancements on the hybrid MDM support in releases to come.

Some interesting links for more info

More details on IBM Hybrid Implementation 

It would be interesting to know opinion and feedback on the Hybrid MDM capability in V11.

IBM InfoSphere MDM V11 is out!

Back to my blogs after a long time. And the break was for no other reason than the fact that was very busy in the Next release of MDM and here it is out after all the hardwork. :-)

IBM InfoSphere Master Data Management Server V11 release brings in IBM InfoSphere MDM Advanced Edition aka DWLCustomer and IBM InfoSphere MDM Standard Edition aka Initiate lot more closer to each other. Both the engines go behind the same Enterprise Container and taking a step closer to a vision where Customer's can build plethora of MDM solutions raging from registry to transactional to hybrid styles of MDM Solutions.

The V11 release of MDM brings in a lot of new capabilities in the MDM product like :-

1. Unified Advanced and Standard Edition Installer
2. Unified Advanced and Standard Edition Workbench
3. New BPM Based UIs with Embedded Workflow Engines
4. OSGI’ied Engine/ backend making the customizations on the product much more easier
5. Common security framework for the Combined engine
6. Hybrid MDM style of implementation

In order to get more information on the latest version of the product, help yourself to the following links and get the latest information and insight.

• IBM InfoSphere MDM Advanced Edition and Standard Edition Developerworks Community
• IBM InfoSphere MDM Workbench
• IBM InfoSphere Master Data Management Server for Product Information Management Developerworks Community

Post topics for MDM V11 on which you would want more information. we can plan some of them as blogs and articles on the same.

Government Department - Use Case for Registry Style MDM

In a Government Organization, there are lot of departments like Ration Card, Pension Scheme, and Student Scholarship etc. Each of this department has their own data which has been collected while providing cards, schemes etc for the people. Each of this department owns their data and do not want to share the same. To get to a single view without passing the ownership of the data forms a very good use case for a registry style implementation of MDM.

This is the reason why Initiate akka IBM InfoSphere MDM Standard Edition fits very well in such use cases. The UID implementation is again another department and other departments can use that for reference but UID does not own the data for other department. So UID will also not be able to provide a solution of owing the data of various departments. The complete journey of MDM to reach to a physical and transactional style of MDM may be long time away as far as the government organization go.

One another good use case for government organization is the data collected is in various Indian Languages. Initiate has good capability of being able to match when the data is in various native languages and can give very good results. However when the various department have language in various different language, transliteration capability have to be used to convert them into one language for the search to happen.

Fingers crossed to see some of the Government sector realizes and jumps at this option.



20-20 Cricket match or Test Cricket

Any day if a cricket fan is asked what would he or she love to watch given a choice between 20-20 and Test match and 90%(I think) would probably say 20-20 . In fact a Test match has started taking the form of 20-20 and finish off in 3 days rather than the whole 5 days. Shehwag has to be blamed for that probably because of irrespective of what form of cricket he is playing he males century at the same speed. Poor guy he is just doing what he is naturally good at. :-)

Given the age and time that we are in why do we think that a customer would wait for 9 months to see a solution implemented. Talk about an MDM Solution and we say that any implementation will take nothing less than 9 months. The customer has every right to say then “Thank You” and move on. The MDM solution ROI has to be shown in lesser time and the complexity has to be hidden. That will be the point where we will be make exceptional growth in markets like India. The Customers in growth market do not have a huge IT department to implement complex solution and neither do they have a window big enough as 9 months to see the ROI.

IBM has taken a step in the right direction by acquiring Initiate into the MDM portfolio and enables customers to implement the simple MDM solution at the same time and realize the ROI earlier. The conceptualization of a virtual MDM to a physical MDM would allow the customer to see the MDM path and end goal much more clearly.

The IBM InfoSphere Master Data Management V10 is the latest release from IBM MDM portfolio. Find all the details about it on the following URL
http://www-01.ibm.com/software/data/infosphere/mdm/features.html

Hope it it a step in the righ direction to convert some of the MDM Test matches to a 20-20 and customers come flocking towards it. :-)

MDM proposition is for Business leaders not IT Department

In market like India, the biggest challenge for selling a product like MDM is the fact that the software is sold to IT department of a company rather than business leaders. The discussion to buy a piece of software or not has still not gone to the Board of Directors or Business leader chambers. The MDM story is approached from typically by fixing the Data Quality issues and ends up becoming a Data Warehousing project along with Analytics losing its advocacy midway somewhere. This is because the customer and their IT department can see the value immediately. However the long term vision of creating a operational hub where the single version of truth can exist is something that can be envisaged as a business need rather than a technology requirement.

Companies need to have business leaders who can vision the roadmap of MDM. Currently the Growth markets customers are trying to solve their day to day problem and the IT Department of various companies are working towards that. When an MDM value proposition is given to the IT department it always gets into make vs buy discussion which becomes an ugly one. The problem needs to be approached as a roadmap where the long term vision needs to be clear. Hopefully these changes soon in countries like India where IT becomes more business driven along with the technology driven as they need to be hand in hand for success. This would lead to more successful stories of MDM in growth market countries like India.

UID has woken up India to MDM

Couple of years back MDM solutions was not even heard in India. Even though MDM had arrived in various other parts of the world including countries like China and Philippines, India had still not woken to that. Any customer that you would go in India like banks and government sectors, it was difficult to make them understand the concept of MDM. Even if they understood there were questions and concerns around basic infrastructure to support that and a big dilemma on the quality of their data. Data Quality is a big throttle to the MDM.

But the story is a little different now. MDM solution was started being conceptualized in various sectors in India with UID. It had become simple to explain MDM to customers if you would just say UID. The statement 'It would give the Unique Identification to each and every customer that you have" rang a bell. It was even easier to explain to my father as to what is the product that I work on. :-)

There is a very interesting video on You Tube also on MDM which is my personal favorite. Do have a look at that.

http://www.youtube.com/watch?v=IC17e0HAQg8&feature=related

The IOD event in Las Vegas will showcase some of the interesting use cases of MDM with respect to Retail, Telco and Government sector. All what you wanted to know about IBM MDM will be there at IOD.


http://www-01.ibm.com/software/data/2011-conference/im-forum.html

Make verses Buy

Think of a situation where there is a desperate need and desire to eat a chocolate cake. Now in order to make it you would need flour, egg, coco powder, some essence, baking powder, eggs and in case the person is vegetarian then lots of cream. So you would either go to the market buy all these items and then make it at home. The other option is order the same and you might get it in half the time and effort. Definitely if you are not an experienced baker you would choose the second option.

The same debate happened in my last customer visit. The customer thinks that they have a solution which is some what similar to MDM and if they enhance it further they can make it a complete MDM solution. However what they fail to understand is MDM is not a software installation but a journey. It is not only to give to that single customer view but taking that view to the next step which helps them making further decisions on long term future and goals. However one can still go ahead and build an MDM solution if the company understands its own requirement around MDM. If it has experts who have knowledge on this domain and can build this solution. If they do not then it is better to ask the ‘experts’ and their solution rather than start building it else that would lead to failure.

The other reason could be when the company is caught in such dilemmas is when they do not have the long term goal set. Unfortunately a lot of companies especially in growth market still do not understand this because probably they look at short term benefits and probably miss the bigger picture.

Moral of the story, build if you know what you want else get the experts.