Comparing one proposal to another can be a nightmare — even for our team, who does this for a living every day. Look for items missing from the proposal. That is the only way to ensure that your proposals and corresponding expectations will ultimately meet the business needs that you and your team have set forth early in the process.
This discipline and focus is something that should start when reviewing proposals and continue all the way through implementation. For example, sales teams will often demo one version of a product, but the proposal team will assume a different version of the software — all without necessarily knowing or telling you the difference.
Each proposal looks different, has different assumptions, different scopes of functionality and other variables that vary from vendor to vendor, so it is vital to decipher and normalize accordingly so you are comparing apples to apples in your evaluation efforts.
Understanding these assumptions will ensure that you are fully aware of what is driving the details of the proposal. When reviewing ERP proposals, look for these missing critical success factors, which you know you will need to address in some fashion in order to be successful.
For example, how much work are they planning to shift to your team versus taking on themselves? For example, one vendor might include their advanced demand planning and budgeting modules, while others may have excluded these modules, but included others. Murky Terminology You are here: It may or may not also include potential services, integration efforts, customization services, hosting services and other items suggested to implement software.
This is why it is important to understand exactly what is in proposals that you may receive. Most ERP vendors are good at one thing: Keep in mind that software vendors are trying to sell you on their solution, which includes outlining the ways that costs, timelines and risks will be minimized if you select their solution.
Evaluating a series of ERP vendor proposals is never going to be easy. Define and understand key proposal assumptions, such as your roles and responsibilities in the project. Constant updates to software versions, multiple variations of available modules and disconnects between the demo and proposal cycle can all create ambiguities that are difficult to manage.
Trace the proposal back to you business requirements. This typically outlines anticipated scopes, costs, timelines, resources and other critical components of procuring the software.
Ensure that you are comparing apples to apples. It is not necessarily in their best short-term interest to be overly realistic in the sales cycle, so it is your job to make sure you understand what is driving their implementation cost and time assumptions. However, understanding the nuances and complexities will enable you and your team to ensure that you not only find the right software for your organization, but that you also implement it in a way that will meet your needs and expectations.
Few of these challenges are intentionally caused by ERP vendors and their sales reps, but a number of oversights and lack of attention to detail early in the software evaluation cycle often come back to haunt organizations — especially as they get into the ERP implementation process.
Getting to the bottom of what exact software is being proposed can be more challenging than it sounds.ASEE Zone I Conference, April, University of Bridgeport, Bridgeport, CT, USA.
ERP Systems and their Effects on Organizations: A Proposed Scheme for ERP Success. ERP Blog; Unpacking the ERP Software Proposal: Murky Terminology One of the first major milestones in any ERP implementation is the receipt of the ERP software proposal. This typically outlines anticipated scopes, costs, timelines, resources and other critical components of procuring the software.
which is ultimately what will make. REQUEST FOR PROPOSALS FOR. SAP ERP SYSTEM AND INFORMATION SECURITY PROGRAM ASSESSMENTS.
ISSUING OFFICE. Pennsylvania Turnpike Commission. PROGRAM AND BUDGET COMMITTEE Twelfth Session Geneva, September 11 to 13, PROPOSAL FOR THE IMPLEMENTATION OF AN ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM Document prepared by the Secretariat [Project Proposal for the Implementation of an ERP.
To assist ERP staff in managing potential conflicts of interest as part of the review and selection process, we are requesting applicants to provide information on who will directly benefit if your proposal is funded. Methodological proposal to implement enterprise resource planning systems.
Methodological proposal to implement enterprise. PROPOSAL OF ERP IMPLEMENTATION METHODOLOGY.Download