The goal is not to optimize individual departments but to coordinate the entire organization.
After defining strategic goals and department-specific goals, you can then build specific functional requirements. You are ready to start creating the hierarchical library worksheet. While this is not a trivial task, the trick is to choose the right depth of information.
Requirements documentation that is too superficial can lead to many problems and misunderstandings. At the other extreme - a most detailed requirements document containing all possible scenarios - ERP providers are difficult to address and result in a disproportionate amount of effort and revenue. To strike a balance between these two characteristics, the following rules of thumb are helpful:
Describe processes and ERP requirements for external understanding.
Don't get bogged down in unnecessary details.
Avoid unrealistic "value for money" features.
Don't focus on the standard features provided in all ERP systems (for example, purchase order-based invoice verification).
Do not specify the solution in the requirements
Another important rule of ERP requirements documentation is to describe your requirements, not their implementation. In other words: Requirements should always be solution-neutral.
This is best illustrated by an example. Suppose you need a feature to start production. It is unwise to write something as specific as: "The top left corner should be a red button through which production orders can be issued", so you strictly exclude all ERP vendors who cannot implement the required button. You can even sort out solutions that automatically start production orders, for example, if the order falls below a defined minimum inventory level. For example, a solution-neutral requirement statement would be: "A function is required to start production."
Conclusion: ERP requirements documentation is a key part of ERP selection
The enterprise Resource Planning Requirements document supports the selection of appropriate enterprise resource planning providers and forms the basis for a successful enterprise resource planning process. When creating your requirements document, it is important to consider higher-level company goals and strategies. In addition, there is a need to work closely with specialized departments that are most adept at using ERP systems. Ideally, you should create the requirements document in a process-oriented, structured, solution-neutral manner with the appropriate level of detail.