by Andrew White | August 17, 2009 | Comments Off on Mastering Asset Information
Sometimes even I am flabbergasted at the rate at which research get’s published Gartner. It can be a veritable fire-hose of stuff – I am sure hard for some users to keep up with. A few notes snuck out in the last couple days. Here are three of my favorite notes (and they are not all mine J ):
Kristian Steenstrup published a note, The Value of Asset Intelligence for Utilities, where Kristian explores “single view” of asset data. IT systems can provide the support utilities needed to improve the approach to asset management from inception, construction or acquisition, through to performance and investment decisions. This research provides a full explanation of the emerging components of a complete asset management view. This “360 degree” view of asset aligns nicely with our idea of a master data lifecycle. Master data (of all kinds) experiences a life cycle that is unique; this is not the same as Information Lifecycle Management, which looks at the physical storage requirements for all data as it moves through a usage pattern. Asset master lifecycle is unique in that is spans design, construction (two MDM use cases), as well as operations, and analytics (the other two MDM use cases). Utilities are well versed in this lifecycle concept so are in a position to lever MDM quickly.
Jeff Woods published a note, How to Evaluate Your Vendor’s ERP Strategy, where Jeff provides a comprehensive framework to help you evaluate your vendor’s ERP strategy. Most enterprises will be tied to their ERP vendors for more than 10 years. Therefore, it pays to make a fully informed decision about those vendors, beyond just functional fit, before you implement or engage in an expansion of your ERP project. This is particularly complex since what is meant by “ERP” has changed over the years. The original concept was a specific application sported a “single data model/single process model”. Over time as those vendors grew in size, and acquired applications and application suites, “ERP vendors” now offer more of a heterogeneous landscape. SAP and Oracle, the two largest “ERP vendors”, still offer an ERP option from old, but that is far less useful to the majority of users, that now focus on an “ERP strategy” which is “source as much stuff from one vendor”. Whatever your ERP strategy, this research is great for scoping out the ERP footprint.
Lastly, Mark Beyer and I wrote a note, The Emerging Vision for Data Services: Master Data and Content Management for SOA. This is a very important note, because we have not written that much on the relationship between MDM (and Content Management, for that matter) and SOA and this is changing. This note represents a core piece of research that explains why MDM needs SOA. There is more to come on why SOA needs MDM. This note explores the increasing first hand experience users are reporting when they try to create integration between MDM hubs and application oriented data that also stores master data. Mark and I will be exploring this in more detail at our upcoming MDM summit (see below).
I hope you find the research helpful. Let us know if you don’t, and why.
Submit a customer case study to win the Gartner MDM Excellence Award 2009! Go here: http://www.gartner.com/it/page.jsp?id=851612&tab=special¶ms=pg,zzz.html
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.