For starters, I would stop comparing tools, and start looking at my business and what I want to achieve. So identify objectives and what's blocking achievement, define quality outcomes for the obejctives you want to achieve and build your businesscase on efficiency improvement. What earnings, savings, benefits are achieved when meeting your obectives. Based on the blocking issues you identified, build use cases and challenge vendors to prove their outcome by building a PoV (Proof of Value). Basically start looking for what improvement your business and processes need, rather than start looking for a tool. After all a tool is just a tool.
As a followup, I would not 'assume world class ERP has these features covered'.
We've seen several actual cases of RFP's (which is why we no longer rely on this outdated capital procurement process to evaluate strategic deployments) - but we've seen where several vendors will check YES to the RFP question concerning a certain feature. Company A does the certain feature well, with a single click. A couple other vendors do it OK, and a couple of the YES answerers require everyone to log out of the system, balance the outlying modules, jump through 6 undecipherable processes, and then YES - it does that.
If that particular feature is something you need 15 or 20 times a day, well, you're probably starting an expensive and long running development effort if you picked the wrong ERP.
The main point is, ERP evaluations need to be a defined process by which you don't make assumptions, skip steps, and your methodology should be repeatedly proven across multiple instances, industries, and shown to deliver with different internal teams (who's mileage may vary).
ERP has the potential to be wildly successful and given a solid business case, provide the tools for your staff to create substantial returns. It also has the potential for abject failure, and that potential for failure is north of 80%, industrywide. So your choices are whether you are comfortable with a big pile of money or a large vat of risk.
SAP ERP = Company has to organize my directions. Microsoft ERP = I have to organize the company's directions.
2.Which industry do you stay in? In the SAP is more suitable for "Manufacturing", ERP is more suitable for "Retail and Distribution". The rest of the industries are the same difference.
3. Your business logics are too complicated? Microsoft Dynamics can be adapted easily.
4. On-Premise vs Cloud? On-Premise = SAP, Cloud = Microsoft
5. Reporting? It's too hard to access Microsoft Data today. Because no one can be accessed the operational data directly.
6. Commerce? Microsoft Commerce platform is well defined for omnichannel commerce.
Do you want to do it for a specific purpose or to tick a box?
Lets assume you are looking for system deployment. I would focus on the key areas of your business rather than what Gene has listed below, which is looking at point for point comparisons. (The Panorama report is SUPERB for getting up to speed....)
Then look at weighting for specific key business differentiation opportunities - such as single global instance for multiple companies, integrated CRM into Finance and Operations, off-line capabilities for customer facing processes, seamless transfer of customer conversations from one channel to another.
Then ask for client references to answer 5 key questions:
- Are they live?
- how was the deployment support from the OEM/partner and what was the % work split required to go live (as in your input vs partner vs OEM)
- how many customisations were requried to achieve xxx (your key areas)
- would they use the OEM again and what would they change going forward
Then look at demonstration from the OEM and costing for the solution
I would not go on a tender for each and every feature and function because we assume world class solutions have these typical areas covered.
I think Panorama Consulting Group publishes some of their ERP shootouts comparing SAP/Oracle/Microsoft with Infor thrown in as a bonus.
Our firm is more of a boutique operation that compares internal company requirements then picks software known for its propensity to work well in those industries/environments. But if you get to the stage where you need some guidance on who some of the top partners and resources are for those software packages, hit us up.
ERP systems streamline business operations by integrating processes and data into a unified platform, enhancing efficiency and decision-making capabilities. They support a range of functions such as finance, HR, supply chain, and production.ERP helps organizations manage core business activities, providing real-time visibility across departments. This integration leads to improved productivity while reducing costs. They are vital in aligning everyday operations with strategic objectives,...
For starters, I would stop comparing tools, and start looking at my business and what I want to achieve. So identify objectives and what's blocking achievement, define quality outcomes for the obejctives you want to achieve and build your businesscase on efficiency improvement. What earnings, savings, benefits are achieved when meeting your obectives.
Based on the blocking issues you identified, build use cases and challenge vendors to prove their outcome by building a PoV (Proof of Value).
Basically start looking for what improvement your business and processes need, rather than start looking for a tool. After all a tool is just a tool.
As a followup, I would not 'assume world class ERP has these features covered'.
We've seen several actual cases of RFP's (which is why we no longer rely on this outdated capital procurement process to evaluate strategic deployments) - but we've seen where several vendors will check YES to the RFP question concerning a certain feature. Company A does the certain feature well, with a single click. A couple other vendors do it OK, and a couple of the YES answerers require everyone to log out of the system, balance the outlying modules, jump through 6 undecipherable processes, and then YES - it does that.
If that particular feature is something you need 15 or 20 times a day, well, you're probably starting an expensive and long running development effort if you picked the wrong ERP.
The main point is, ERP evaluations need to be a defined process by which you don't make assumptions, skip steps, and your methodology should be repeatedly proven across multiple instances, industries, and shown to deliver with different internal teams (who's mileage may vary).
ERP has the potential to be wildly successful and given a solid business case, provide the tools for your staff to create substantial returns. It also has the potential for abject failure, and that potential for failure is north of 80%, industrywide. So your choices are whether you are comfortable with a big pile of money or a large vat of risk.
Only you can determine your comfort zone.
1. Your business is well defined?
SAP ERP = Company has to organize my directions. Microsoft ERP = I have to organize the company's directions.
2.Which industry do you stay in? In the SAP is more suitable for "Manufacturing", ERP is more suitable for "Retail and Distribution". The rest of the industries are the same difference.
3. Your business logics are too complicated? Microsoft Dynamics can be adapted easily.
4. On-Premise vs Cloud? On-Premise = SAP, Cloud = Microsoft
5. Reporting? It's too hard to access Microsoft Data today. Because no one can be accessed the operational data directly.
6. Commerce? Microsoft Commerce platform is well defined for omnichannel commerce.
I think.
Do you want to do it for a specific purpose or to tick a box?
Lets assume you are looking for system deployment. I would focus on the key areas of your business rather than what Gene has listed below, which is looking at point for point comparisons. (The Panorama report is SUPERB for getting up to speed....)
Then look at weighting for specific key business differentiation opportunities - such as single global instance for multiple companies, integrated CRM into Finance and Operations, off-line capabilities for customer facing processes, seamless transfer of customer conversations from one channel to another.
Then ask for client references to answer 5 key questions:
- Are they live?
- how was the deployment support from the OEM/partner and what was the % work split required to go live (as in your input vs partner vs OEM)
- how many customisations were requried to achieve xxx (your key areas)
- would they use the OEM again and what would they change going forward
Then look at demonstration from the OEM and costing for the solution
I would not go on a tender for each and every feature and function because we assume world class solutions have these typical areas covered.
Happy to discuss how to do this practically if required. Daniel@liferocksconsulting.co.za
I think Panorama Consulting Group publishes some of their ERP shootouts comparing SAP/Oracle/Microsoft with Infor thrown in as a bonus.
Our firm is more of a boutique operation that compares internal company requirements then picks software known for its propensity to work well in those industries/environments. But if you get to the stage where you need some guidance on who some of the top partners and resources are for those software packages, hit us up.