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

Bristlecone Webinar on Supplier Risk Management

Purchasing Magazine, Bristlecone and SAP getting together to bring you very good discussion on supplier risk management. Webinar will be held on June 24, 2 to 3 PM eastern Time, USA. Contributors are - Paul Teague from Purchasing magazine , Jason Buch from spendmatters , Naresh Hingorani from Bristlecone - Supply chain leader company and Padmini Ranganathan from SAP. As we always talk about spend visibility, data issues, strategic sourcing - these distinguised speakers will bring out more strategic views to the table on how all this can be achieved to analyze your business risks better, upfront. You can register for event by accessing this link and register See you there.

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 - Elephant & Seven Blind Men

I am sure most of you read a story of Elephant and Seven Blind Men. For starters - this is how the story goes - "A number of blind men came to an elephant. Somebody told them that it was an elephant. The blind men asked, ‘What is the elephant like?’ and they began to touch its body. One of them said: 'It is like a pillar.' This blind man had only touched its leg. Another man said, ‘The elephant is like a husking basket.’ This person had only touched its ears. Similarly, he who touched its trunk or its belly talked of it differently." As Wikipedia mentions - This story has been used to illustrate a range of truths and fallacies. At various times it has provided insight into the relativism, opaqueness or inexpressible nature of truth, the behavior of experts in fields where there is a deficit or inaccessibility of information, the need for communication, and respect for different perspectives. The moral of the story is - While one's subjective experience...