ERP Requirements Refinement



When you start a system selection, you first need to determine which business process are the “value - add” processes. In other words, which processes in the business add to the value of the service or product you are providing to the market. The customer is only willing to pay for those activities that help you produce, ensure quality, or account for your product or service. All other activities are waste.

When defining your ERP requirements, you need to be cognizant of these “value - add” activities. These are the activities that should be captured in your requirements. Non-value-add activities should not be included in your ERP requirements. These do not produce results that create additional value to the product/service and these are only distractions when it comes down to the actual implementation.

ERP Requirements and Lean

All of this comes from Lean Manufacturing or the Toyota Production method. Essentially, as stated above, you want to eliminate “Muda” or waste in the process. Many firms have successfully implemented this in their operational processes, but a smaller group has implemented this Lean system in their business office processes.

Consider this example. When defining your ERP Requirements you determine that there is an accounting process that has people spending 2 man days per month reconciling the cost of keeping track of the materials used at the construction site. Does this process add any value to the actual completion of the Project? Possibly, but it sounds like this process can be reworked and possibly using the new ERP system you can eliminate this process and drive the data down to the actual transactions at the site. You don’t need accountants researching the transactions. What you might need is a system that tracks the materials and their usage as part of the construction process and can give a report on what these transactions cost. These transaction costs can then be factored into the pricing of the project, without the overhead of 2 man days of reconciliation.

The time when you are defining your new ERP Requirements is the perfect time to start looking critically at your processes and keying in on what brings value to the process. Then you can design your new system (both process and software) around those items that bring value to not only the customer but also the bottom line.

Mapping your ERP requirements

When you are cataloging all of your ERP Requirements, you should write down all of your requirements (perhaps on a spreadsheet) and then give them an identifying number (such as R1, R2, R3, etc.) You can then evaluate each of these requirements with the business team to determine if the requirement is one that you want to carry forward into your deliverable of requirements that will be provided to the ERP software vendors.

Starting with the desired business results ensures that we drive to only those requirements that directly support true business value. First, it is an exercise that really puts into perspective the purpose of a business model (results). This exercise is not only useful to the project team but also the business stakeholders. Second, it is an approach that can help you justify why certain existing business activities are not being carried forward in the new business solution. Third, taking a business results oriented approach enables your project team to be more successful at focusing on the right business requirements and not wasting time on capturing requirements for non-value-add activities. 

Keep in mind that some ERP Requirements that you identify may not seem valuable at first, but you need to review these requirements with the functional user team to ensure that key processes are not eliminated by mistake. There may be requirements that are a requirement because of a legal concern or perhaps a health and safety issue.

In the end, if you have successfully mapped out your business processes and defined these in your ERP Requirement list, then you will be a lot closer to selecting a system that actually functions in a way that brings value to everyone.

Hope that this will aid you in better defining your ERP Requirements.

Comments

Post a Comment

Popular posts from this blog

Determine the Business Value of ERP

Image
Return on Investment (ROI) is one of the most important considerations for the company management. After all, any investment must yield some value to be worthwhile. But what about the ROI of an Enterprise Resource Planning (ERP) system? Understandably, management may be hesitant to invest in a costly software solution like ERP. Like any new technology, ERP systems  take time to implement  and require all workers  to be adequately trained . Is the value of ERP really worth the cost? Answering this question comes down to understanding two things: what kinds of value ERP brings to your company and how to attach a dollar amount to them. In this post, we’ll cover both. Adding Value to Organization Before understanding the value of an ERP solution that brings to the organization, first there is a need to understand where the existing challenges and pain points persist. When weighing the potential areas where ERP will bring value to the business,  one ...
Read more

Customization in ERP Software Implementation

Image
Customization is one of the most controversial topics surrounding ERP software.  A majority of companies have every intention of leveraging vanilla, off-the-shelf software during their software selection process.  However, as project teams get into the details of the software during the implementation cycle, requests to make one or more customizations to the software are inevitable. The reason for the controversy around customization is threefold. First, it increases the complexity and risk of an implementation, while at the same time making it potentially more difficult to upgrade software in the future.  Second, it in some ways undermines the best practices built into the software, which software vendors often spend significant R&D developing.  Thirdly and finally, customization is often a symptom of bigger problems, including a solution’s mismatch with a company’s requirements or a lack of project controls during implementation. So what to do?  ...
Read more

Best Practices to Manage End-to-End Business Processes in Your ERP System

Image
It’s no secret that most ERP systems fail to deliver the business benefits anticipated by the organizations implementing the software. 50-percent of organizations fail to receive at least 50-percent of the expected business benefits from their investments in enterprise software. Adding insult to injury, and as outlined in our blog last week, is the fact that most organizations experience a misalignment between their business operations and ERP systems, which typically worsens over time as the companies go through acquisitions, international expansion, supply chain reorganizations, and other changes. The reasons for the failures to achieve business benefits as well as operational misalignments with ERP software often point to business processes. As opposed to incorporating process best practices in their ERP systems, most ERP vendors and system integrators use the flawed practice of designing and configuring the software to handle a hodgepodge of transact...
Read more