MSDW: MDM vs. IDM
Recently, over at MSDynamicsWorld.com, an article was posted about 'MDM vs. IDM'. This article talked about SOA, and the importance of understanding what Master Data Management means.
I assume this was prompted by the soon to be released IDM, or Intelligent Data Management tool that will be coming out for Dynamics AX. This was actually talked about during convergence, and there is not a lot out there right now talking about this.
I agree with the article, the points about needing to understand MDM, or Master Data Management, specifically in regard to SOA. And why would that be important? Well the reason is, as in previous posts I have pointed out.:
-Microsoft's strategy and vision for Dynamics AX and SOA
-WCF: The Enterprise Service Bus for Dynamics AX and the rest of the Microsoft Stack
SOA, and the cloud, are becoming more and more important and very much a part of Dynamics AX. SOA or WCF Services are being developed for the next versions of Dynmaics AX so even the internal modules that make up Dynamics AX will communicate with each other in such a way. And what does this mean? This means that then parts of a Dynamics AX instance could truly be in the cloud, with other parts being on premise at the customer still. (Not all modules or types of processes make sense for the cloud, like MRP, etc.)
So to Jeff's point in the article, that it's very important to understand and develop processes and polocies for Managing your Master Data, he is right. What will lead you though, to that understanding and give you the ability to develop such processes and polocies is understanding what technologies will make this up, so that the solution can be properly deployed, and therefore proper and correct processes and polocies can be setup for managing your Master Data.
For example, take my post about the future of Microsoft BI: Project Gemini, that was demoed in full this week at TechEd.
In that post I go over the future, and part of that is Excel Services. Note the part, that IT orgs will be able to use this to control access to your data. The point should be well understood, in that, if there is not control, several versions of "the truth" start to exists, and without proper control this can get out of hand, and get a company in trouble.
So it's very important that your partner understands these technologies, the future of them, and can work with you to develop a plan. I happen to know one of the best, Sunrise Technologies, Inc.. If your needing a partner that understands this, and understands the technologies, and deep vertical knowledge you need, then feel free to contact us from the link provided.
As for IDM, more will be coming out soon about that. I am lining up some Microsoft technical interviews about this release. The point of IDM is well covered in Jeff's article, linked from the top. It is a tool that will help manage an instance of Dynamics AX, to cut down on unneeded data, to archive old data and help with even indexes.
Well check back soon, as more great post to come! See you then!
"Visit the Dynamics AX Community Page today!"
I assume this was prompted by the soon to be released IDM, or Intelligent Data Management tool that will be coming out for Dynamics AX. This was actually talked about during convergence, and there is not a lot out there right now talking about this.
I agree with the article, the points about needing to understand MDM, or Master Data Management, specifically in regard to SOA. And why would that be important? Well the reason is, as in previous posts I have pointed out.:
-Microsoft's strategy and vision for Dynamics AX and SOA
-WCF: The Enterprise Service Bus for Dynamics AX and the rest of the Microsoft Stack
SOA, and the cloud, are becoming more and more important and very much a part of Dynamics AX. SOA or WCF Services are being developed for the next versions of Dynmaics AX so even the internal modules that make up Dynamics AX will communicate with each other in such a way. And what does this mean? This means that then parts of a Dynamics AX instance could truly be in the cloud, with other parts being on premise at the customer still. (Not all modules or types of processes make sense for the cloud, like MRP, etc.)
So to Jeff's point in the article, that it's very important to understand and develop processes and polocies for Managing your Master Data, he is right. What will lead you though, to that understanding and give you the ability to develop such processes and polocies is understanding what technologies will make this up, so that the solution can be properly deployed, and therefore proper and correct processes and polocies can be setup for managing your Master Data.
For example, take my post about the future of Microsoft BI: Project Gemini, that was demoed in full this week at TechEd.
In that post I go over the future, and part of that is Excel Services. Note the part, that IT orgs will be able to use this to control access to your data. The point should be well understood, in that, if there is not control, several versions of "the truth" start to exists, and without proper control this can get out of hand, and get a company in trouble.
So it's very important that your partner understands these technologies, the future of them, and can work with you to develop a plan. I happen to know one of the best, Sunrise Technologies, Inc.. If your needing a partner that understands this, and understands the technologies, and deep vertical knowledge you need, then feel free to contact us from the link provided.
As for IDM, more will be coming out soon about that. I am lining up some Microsoft technical interviews about this release. The point of IDM is well covered in Jeff's article, linked from the top. It is a tool that will help manage an instance of Dynamics AX, to cut down on unneeded data, to archive old data and help with even indexes.
Well check back soon, as more great post to come! See you then!
"Visit the Dynamics AX Community Page today!"
Labels: Dynamics AX, Dynamics AX 2009, IDM, Master Data Management, MDM, MSDW, MSDynamicsWorld.com
0 Comments:
Post a Comment
<< Home