The great thing about the internet is that anyone can share their thoughts, the problem with the internet is that anyone can share there thoughts. A classic dichotomy if you will.
We see this all the time, people talking utter, utter rubbish about things they don’t understand. As “organisations” have started to blog more and more this issue has increased. The way I see it is like this… If you run “Mega Corps” would you want me bloging for you? I probably wouldn’t. You see I’m not a talented writer, my spelling and grammar are poor and I’m not adept at making my point – as I will now prove. So “Mega Crops” ask the people who can do these things well to blog for them. What actually makes for a good bloger is someone who can think well! See, a bad idea expressed well is still a bad idea. What makes a great bloger is someone who can think and write well – and these types are rare. But still, what would you rather have, an ill-conceived observation expressed elegantly or a quality observation just expressed?
Now I need to be careful here, I don’t what to offend anyone.
Equally I’d like to address the lack of understanding and insight, or at least offer a counter view. I have some grounds to make these observations, being somewhat familiar with Excel and having worked in supply chain for the last decade or so.
Basically both articles point out the limitations of Excel, principally by comparing the differences between Excel and a Generic ERP system. For example:
“Excel has features that can calculate safety stock by using prebuilt basic formulas such as moving average, standard deviations forecasts etc. Keep in mind that by doing this, an organization will not have the ability to see the entire supply and demand relationship. On the other hand, when the same safety stock is calculated within an application, it will provide visibility to outstanding supplies that need to be replenished; orders can be planned for production; and it can calculate how quickly organizations can turn a forecast into a deliverable product.”
“I completely agree with the author that there is a big risk to SCM Professionals who rely too heavily on Excel. There are all the reasons listed in the article such as lack of collaboration, visibility, control and no ability to perform “what-if” scenarios. I would like to add some additional thoughts to this discussion.”
So, Excel has limitations creating what if scenarios, and pre built basic functions!! Clearly not Excel experts! Another common theme is that Excel is not very good for collaboration, information sharing and data security…
It is almost impossible to control the integrity of spreadsheet data and access to the spreadsheet. With multiple people accessing the spreadsheet and no security, how can anyone have any confidence in the data?
Well true. Sharepoint (etc.) might help here, but that’s another issue. So basically don’t use Excel as a database. Fair enough but…
Comparing Excel to an ERP system is like comparing a Motor Bike to a Train Network. It’s just stupid. Telling people not to use Excel because it does not have the same capabilities as an ERP system is likewise really bad advice. Excel is different to an ERP system, we could easily re frame the argument the other way around and draw the conclusion that ERP system are the work of the Devil!
In fact, lets do just that.
Beware Supply Chain ERP Users—YOU are DOOMED!!!!
ERP systems are slow expensive complex beasts, with poorly documented calculation methods, inflexible font ends, and limited reporting capabilities. I recently talked to a number of supply chain professional and was shocked by how many of them are using their ERP systems in blind faith that the system are optimised for their needs. In the fast passed global supply chains of today, how can these default settings and calculation models possibly be right for your business?
Consider yourself doomed if you ever find yourself using an ERP system for any of these:
Reporting and Analysis: ERP system can out put reports in a number of formats, but typically they cant build well constructed dashboards, which are tailored to your companies specific needs, and/or ones that can be quickly adapted and changed over time as the needs of the business change. And forget it if you want to do some sort of analysis that the System Architect didn’t think you’d need to do in the 2 month he was specifying the system for your company 3 years ago. (Not that that would ever happen of course…).
Changing the model: ERP systems provide various forecasting tools, is getting the best results from them a skill or a science? Do you even know what equations are being used, it’s unlikely because this is the IP of the vendor, and what about data sources, is that data from the Spanish plant accurate, if it’s not can you do anything about it? Not all that flexible are we!
Your team just grew: Better get your wallet out…
You want someone form out side the organising to use the system: No.
You have a new data source that you’d like to add to the model: Humm, can you see where we’re going…
And so on…
In conclusion neither ERP systems or Excel can doom your supply chain and comparing one against the other as a way to high light a weakness is a logical flaw. Neither ERP systems or Excel are inherently good or bad, badly designed and/or used spreadsheets are a business risk, just like a poor quality ERP system or ones that are used poorly are a risk. Each “system” has strengths and areas where their use makes sense, and this are extremely well document. Likewise the “miss use” of Excel and the motivations for this are also well document, and note – not all of them are unreasonable.
I take exception to the two blog posts because as well as misrepresent the capabilities of Excel, they also give poor or misleading reasons as to why it’s use is dangerous, also they both take one or two valid, but already extremely well understood points, and extrapolate them to reach irrational end points.
So were doe this leave us?
Well, here are some of my thoughts on what you should do to help you avoid risks if your using spread sheets (for anything really)
- Design you spread sheets well from the ground up (here, and here for help)
- Understand connected or discounted data sources
- Learn how to connect to enterprise data bases.
- Learn about versions, and version control and try to apply it
- Think about risk, and except it explicitly if you have to
And there ended the rant ;-).