Selecting an ERP system is a daunting task. However, there is a recipe to ensure success when choosing a new ERP, or enterprise resource planning, software system. One of the critical ingredients in that recipe is system requirements.
When done correctly, documenting system requirements can provide many benefits. For example, it can maintain structure and objectivity within the project, as well as the visibility you need to maintain momentum and gain the sponsorship you need for project completion. It also can help you identify the scope of the
So, what do system requirements look like? I tend to think of them as an outline, or a
Once you’ve started the outline, the next thing you want to do is define the
Once you do that for each line item, it’s time to prioritize them. Assign a value, like "must have," "nice to have," or "of interest." Another way is to assign a numerical value from one to five.
When system requirements are done correctly, it's going to set the stage for evaluating vendors, software demonstrations, testing the new system, training your staff as well as onboarding new staff. It will also provide an audit trail that your auditors may be interested in seeing, especially when they learn that you've implemented a new ERP system.
Learn more about ERP system requirements by contacting a partner like
by Gary Volland, The Resource Group