Skip to main content

Your Data is Bad - Does it matter if you know in 3 hours or 3 Minutes ?

These days every discussions in analytic and business intelligence areas eventually end up with "speed of analysis". Since SAP introduced HANA - the buzzword is about speed, real time, near real time dashboards. Everybody wants to talk about a cloud application - so they can get up & running with applications tomorrow, and if its deployed on HANA - more than happy since they get it faster. So CIO can start getting his dashboard from next week, every time he looks at it - its just near real time. Isn't it faster ROI ? Gone are the days when it used to take few months to get systems up and running, 3 hours everyday to get those BI reports and tune those dashboards where "Go Live" was a big event.

The only question remains - When CIO looks at that new dashboard created in 3 minutes rather than 3 hours - how much time does it take to tell you that your data in the system is bad.  No surprise here.

Last week I was talking to a procurement executive from a reputed media company. They are going through this peculiar problem of "defining taxonomy" to address their dynamic business transactions - a photographer takes a photo of Brad Pitt taking coffee on the NY street and comes to them - gets paid $2000 and goes away. No PO, No Supplier, probably just a invoice with a gibberish - "Brad Pitt Photo" and a money paid. Now if that happens everyday with a fast social media, digitized world where you need to be the first one to get hold and publish it - you don't care about the "Process". Result - Bad Data. When a CIO - CFO looks at the "spend analysis" dashboard - which tells them there are "Other" category transactions which accounts for 28% of spend - guess a reaction.

Not to say - speed of analysis is less important, but as the title of this blog suggests - priority is important. If your data is bad - doesn't matter if you get analysis in 3 hours or 3 minutes time. If your data is good - anyway it doesn't matter 3 hrs or 3 minutes, since you know where to fix the problem already. Important part is - DATA Quality

Comments

Popular posts from this blog

Master Data Management – Product or Process ?

I have 2 SAP systems and I want to fix my material master, Services Master. I want all that data to be clean, standardized, classified, enriched and load it back to my SAP in next 6 months. What do you suggest ? Chris - one of my key client was explaining during a “solution understanding” call. My sales manager Tom, enthusiastically started talking about new version of the MDM platform by ERP company, tools, technologies, product landscape, licenses etc. After 30 minutes of sales pitch, I could see confusion on Chris’s face clearly. He said - but I don’t want to add any new product in my infrastructure for all this. Can you just implement MDM for me without I adding any new software ?   Both are using MDM implementation as a keyword, but in a completely different context. Chris wants to implement MDM as a process while Tom was trying to sell MDM as a new software. Whats the difference ? Lot I will say. MDM as a product – when you sell a   software license to a...

Data Management - Terminologies & Definitions

As a third step in my Data Management article series – lets look at commonly used terminology in the domain. Now these are very standard definitions I am quoting from a standard available glossary. The next step – next article would be to explain the relevance and usage of these terminology in business world. E.g. How to look at data standardization in supplier data context or material data context – when it comes to optimizing your procurement processes. That’s next. In my first article in this data management series –I compared data management with the story of elephant and seven blind men. http://manageyourdata.blogspot.in/2012/09/data-management-elephant-seven-blind-men.html The second post is more about – why its important to speak same language when you are running any data management initiative.   http://manageyourdata.blogspot.in/2012/09/data-management-are-we-all-speaking.html Data analysis : Analysis of data is a process of inspecting, cleaning, transfo...

Journey of procurement transformation begins with..….. Part II

 Original Blog post - https://www.linkedin.com/pulse/journey-procurement-transformation-begins-part-ii-prashant-mendki Procurement transformation journey is complex, cross functional, time consuming and even frustrating at times. The very basic but a strategic step to start this journey is “Spend Analysis”. Again – this has to be done in a right way to get the potential benefits. We talked about that in first part of this article https://www.linkedin.com/pulse/journey-procurement-transformation-begins-part-i-prashant-mendki By definition – Spend Analysis is an analysis of your spend (invoice paid), what items you are spending on (product), who you are paying to (supplier). It looks really simple – no? When I worked with one of the large Media Entertainment company few years back, they had thousands of suppliers, millions of transactions, good amount of Maverick spend. It’s a global business with more than $2Bn in Spend, 12 different global systems. Thousands of trans...