Comments on: Microsoft MDM? Don’t hold your breath http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/ Andy Hayler, founder of Kalido and The Information Difference, gives his views on the enterprise software market. Issues covered include data warehousing, master data management, business intelligence and data quality. Sun, 12 Oct 2008 22:20:03 +0000 http://wordpress.org/?v=2.0.3 by: Jim http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-23561 Mon, 12 Feb 2007 08:58:57 +0000 http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-23561 Look for news around this in the next few weeks. Look for news around this in the next few weeks.

]]> by: Andy Hayler http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-65 Thu, 30 Mar 2006 07:48:00 +0000 http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-65 Indeed. I imagine there are a few red faces at Microsoft over this shambles. Indeed. I imagine there are a few red faces at Microsoft over this shambles.

]]> by: Mikael J http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-64 Thu, 30 Mar 2006 06:29:00 +0000 http://andyonenterprisesoftware.com/2006/03/microsoft-mdm-dont-hold-your-breath/#comment-64 I think your analysis is pretty much spot on. Microsoft took water over their heads when trying to merge many different business applications. One problem is the impossible mission of merging the products into one code base. Microsoft obviously thought they could do like they have done before, look at the code, rewrite it, enhance it, package it and put it to the market backed with heavy marketing. They failed to realise that you may be able to do that with one application, the re-writing that is, maybe, but not with several. On top of that one them, Navision Financials, used its own database, at least for a large number of applications. The other problem Microsoft did not realise was the problems they would run into dealing with the resellers. Resellers of ERP-systems do not work like or can be managed like resellers of Office products or even some of the more complex applications Microsoft have in their portfolio. Reading the article you linked to it now feels as if there will not really be a new product. Quite amazing since they have been developing this since they bought Great Plains, which they did in 2000. Soon it is 6 years By 2010 it will be 10 years. Maybe it would have been better had they started with a white piece of paper and no customers in 2000. I think your analysis is pretty much spot on. Microsoft took water over their heads when trying to merge many different business applications. One problem is the impossible mission of merging the products into one code base. Microsoft obviously thought they could do like they have done before, look at the code, rewrite it, enhance it, package it and put it to the market backed with heavy marketing. They failed to realise that you may be able to do that with one application, the re-writing that is, maybe, but not with several. On top of that one them, Navision Financials, used its own database, at least for a large number of applications. The other problem Microsoft did not realise was the problems they would run into dealing with the resellers. Resellers of ERP-systems do not work like or can be managed like resellers of Office products or even some of the more complex applications Microsoft have in their portfolio.

Reading the article you linked to it now feels as if there will not really be a new product. Quite amazing since they have been developing this since they bought Great Plains, which they did in 2000. Soon it is 6 years By 2010 it will be 10 years. Maybe it would have been better had they started with a white piece of paper and no customers in 2000.

]]>