According to Gartner, the #1 reason for MDM failure is the lack of a business case to qualify and quantify data management value creation. In this third session, learn more about how to evaluate the complexity of an MDM platform and the questions to ask to calculate the true cost of ownership in another informative & lively discussion with Bill O’Kane – Profisee VP & MDM Strategist, Harbert Bernard – Profisee Director of Value Management and Christopher Dwight – Profisee VP of Customer Success.
Listen to the Podcast!
In this session, we will discuss more on understanding the components of TCO (total cost of ownership) that you need to take into account for the investment portion of your MDM project. Harbert starts off the discussion sharing this vision:
Protip: There may be some additional costs that should play into your model. Here are some questions to consider:
There are many options to consider with what deployment option works best for you, and you will want to include the downstream associated costs that may need to be considered into your TCO calculation.
Next, the guys discuss some of the surrounding costs including:
There are some definite pitfalls to watch out for when calculating TCO:
How do we handle those costs that you may have been previously doing in another project – like perhaps some type of address verification service as an example? What happens to those costs now that those services will be used or potentially used in the MDM project?
Bill: That’s a great question. The trick is figuring out is there a top-level bucket for the ‘good of the nation’ type expenses around governance, etc. where you have 7 or 8 departments benefiting from this solution and spreading out those costs. The alternative is that if the MDM project takes those costs on, then the business that is now relieved of those costs knows they are relieved of that cost burden because they are being managed through the master data management program and not simply that they just went away. Ideally, this is handled by a business led data governance council.
Harbert and Christopher point out – ironically, sometimes a data management initiative uncovers data services, like D&B, that exist in multiple instances throughout a company (think companies that grow by acquisition), and an MDM project comes in and can help reduce that cost by only using one instance albeit now used effectively in the MDM project, and this reduction actually comes as a benefit in your TCO cost.
In the last session, we talked about think big, start small. A great question from one of the attendees is “well, how do you account for these opportunities for additional projects with multiple use cases and/or multiple domains that could immensely benefit the organization after the initial project is completed?”
Bill: Well you need to understand how the vendors charge for adding domains especially (some can be up to 2x of initial investment) as it is not uncommon that once you have mastered customer data, you will next want to consider the intersection of customer and product. Since in some platforms this could be additional costs, you will want to understand the potential costs of adding new areas to master within your MDM program with whatever platform you are considering.
Final question: How often do you have to do this detailed TCO calculation? We were planning on making MDM a part of a bigger project because it won’t be successful without clean data, so we got approval to just put the MDM project piece into this larger initiative we are doing.
Christopher and Bill state there is a significant risk of not taking the time to calculate the benefits of the MDM project piece. You can do it, but if there are problems down the line in the bigger initiative, you will want to protect the work that has been done and you will more easily be able to show the benefits of MDM even in the bigger initiative. And if the bigger project gets cut, you don’t want to put at risk the MDM component as well. Having that value line protects you!
There are many components to calculating a fully loaded and comprehensive total cost of ownership for your MDM project.
In the next session, we will get into program scope, figuring how to get some quick wins, where to focus, and the options you have when it comes to implementation styles. Until then!
"The Profisee MDM platform provides exactly what we are looking for."
―Slobodan R.Read the full review
"Very capable MDM platform with solid development toolkit and favorable TCO"
―Data & Analytics Architecture Manager in the ManufRead the full review
"Profisee really stood out with their attractive pricing model and implementation time compared to the competition."
―Project Manager in the Finance IndustryRead the full review
"Very affordable and user friendly. Great for modeling big data domains."
―User in Higher EducationRead the full review
"Great end-to-end product to make MDM easier for organizations."
―Internal ConsultantRead the full review
"Excellent vision and roadmap for the product."
―Senior Manager Business Intelligence in the ServicRead the full review
"The Profisee product is intuitive enough for us to implement our first domain in under six months."
―Manager of Data Architecture in the ManufacturingRead the full review
"The technology is well built and is a flexible/robust tool - powerful engine and has solid UI and exceptional workflows - and ability to customize."
―Vice President in the Manufacturing IndustryRead the full review
"The best thing about the software is the UI, it is very nice and clear. It is very easy to understand"
―Administrator in Computer SoftwareRead the full review