The Biggest Problem in Corporations - Data Proliferation, 3 tips to tackle this issue

on Friday, 14 June 2013. Posted in Solution & Business Architecture

The Biggest Problem in Corporations - Data Proliferation, 3 tips to tackle this issue
 
 
Data is impacted by numerous processes, most of which affect its quality to a certain degree. As data proliferation in the enterprise continues its exponential expansion and the size, complexity, and heterogeneous nature of IT systems environments scales to keep up, data quality and trust become increasingly important. Trusted data initiatives will remain strategic.

The business drivers that are pushing (Master Data Management) MDM:

•   Runaway costs that include bad data

•   Missed opportunities mostly from lack of transparency from the business pipeline

•   With the potential jail time to corporate officer’s regulatory compliance, security and sensitive data will continue the push towards a standardized view of critical data.

•   Integrating new businesses as M&A continues, consolidating corporate data from multiple acquisitions.

2014-16 will be great years for MDM, I think standards and the trustworthy view of critical data will be propagated and included in the processes of most businesses. I think we will soon reach a meeting point between MDM and Big Data, as we know big data comes in many forms: some is structured, some unstructured; some is generated internally, some externally. The current MDM solutions are know being built with internal and some external integration points.

When selecting an MDM technology I would recommend use the Gartner or Forrester reports, and in my opinion I would only spend time looking the top right quadrant.

Some companies are naïve when it comes to choosing MDM technologies, wrongly assuming that the market is mature and that everything works fine these days. In my view, this is wrong it will take another 3-5 years for this area to mature.

Below is the year over year Gartner Magic quadrant on MDM

MDM 2012-2013 Gartner Comparison

Three tips

  1. Shortlist your suppliers and make sure they have a track record with your type of data
  2. MDM projects are always tricky, follow a think big start small approach. The approach should consider all data domains, but take a gradual, step-wise approach to implementation, delivering incremental business value
  3. In 2014,I think companies will be moving toward an Enterprise App Store similar to Google and Apple store and this will oblige companies to accelerate their efforts on MDM.(look into creating an enterprise app store)

One of the big accomplishments of these technologies, analysis of data has become a key differentiator within many industries.

Like usual please share your thoughts on MDM, Big data and the Enterprise App Stores trends

Comments (9)

  • Marc Wilson

    Marc Wilson

    14 June 2013 at 19:56 |
    Alex, good article, I enjoy your content, my view MDM succeeds when failure is not an option, my company avoided MDM until we made headlines, data governance became strategic.
    An enterprise app store like the Google store would make sense where I work like a self service application store.
  • Marianne

    Marianne

    14 June 2013 at 20:26 |
    The trend should be that the majority of global 500 enterprises will have no choice to deploy like you say data integration architectures, loosely coupled between structured and unstructured, your writing is compelling and engaging, bookmarked your site!
  • Nicole M.

    Nicole M.

    15 June 2013 at 00:04 |
    We have been trying to establish data governce in our company but quite hard the politics seem to be more important than taking decisionswith good data, my advice make sure you follow a top down approach . Our company is also currently analyzing some of the technology leaders in the mdm market. Good points
  • Terry Edwards

    Terry Edwards

    15 June 2013 at 06:27 |
    The big issue with MDM in the corporate world is the CXO, they all look for the quick wins and no one takes alonger term approach on data. My tip MDM projects should use graphical modeling, text and documents are often interpreted incorrectly.
  • Arthur Brown

    Arthur Brown

    15 June 2013 at 09:21 |
    First time visitor, my experience with MDM, we were sold the easy button from the provider sales team(If i had to give one advice never take any advice from a sales person), it was nothing like(easy button), the project costs were tripled, functionality integration was not as seamless as it was sold, the big plus we are starting to see the fruits of the initiative, overall i am happy with the implementation of the project, I also know get more job opportunities MDM is hot in the US.just bookmarked this site!
  • Steven Singh

    Steven Singh

    16 June 2013 at 10:05 |
    Great article, we stopped an MDM project in march at my company, the reason we had spend large amounts of money for the last 18 months with no real progress! Our main issue we could not figure out how to breakdown the data ownership as it relates to the organization and are lesson learned we did not follow 'start small strategy'. Would you be available for a 12 month contract in Seattle, can you share your experiences/approach on data ownership. Thanks
    • Alex Antonatos

      Alex Antonatos

      16 June 2013 at 14:52 |
      Hi Steven,
      Unfortunately, i am unavailable until the end of September.
      Data ownership is always a sensitive subject in any company, make sure in your next phase , have a CXO level sponsor, to help in the areas that are grey.
      Here is what i propose as your next data ownership plan/activities for the project:

      1) Start with requirements workshop bring together role owners, data administrators, senior management and known issues to elicit requirements, issues, conflicts, benefits, and outline data ownership policy
      2) Document the data ownership policy to provide authority and basic tenements of data ownership in your case in PeopleSoft, Siebel and Oracle EBS
      and have a steering committee to ratify and then distribute policy to project teams
      3) Identify and inventory the data, data sources, role owners, responsibilities, dependencies. This produces evidence and information on the data available.
      (FYI Largest single task in the project).
      4) Understanding the commercial nature, sensitivity or other dimensions of data classification. Draw conclusions as to any necessary stratification and data association to those strata.
      5) Confirm roles to ensure ownership, maintenance, delegated authority and related responsibilities, policies, procedures and yo must make they are applied applied.
      6) Document procedures to reflect business rules, access authorities and administration of data to ensure accuracy, completeness and timeliness of data.
      7) As your company realized the first time around, it does not mean if you hire a large or small consulting firm the project will be a success, put your A team internally and try to hire the best experienced consultants. MDM projects are never easy and will always be filled with challenges.
      Kind regards,
      Alex
  • John Rodriguez

    John Rodriguez

    16 June 2013 at 15:10 |
    Hi Alex, I enjoy your blog on MDM, I find your site quite original, perhaps the best lesson that I ever learned as a person that spends lots of time on the internet is that I am drawn to others who speak their mind, who have something unique to say and who say it in a creative and fresh way.Keep it up.
  • Cynthia

    Cynthia

    20 June 2013 at 21:18 |
    good points!

Copyright 2014 Appsconsultant.com. All rights reserved.