One ERP Software for a company is a complex project. In this series, we try to shed light on the various aspects of this task. After the basics in the first in the second part to understand the different motivations around a ERP project. After the third partwhich names the responsible persons, it is about the specifications for the ERP selection.
The specifications for ERP selection
Paper is patient, and so are Excel lists. Because that's where the content developed during the search phase ends up, line by line, worksheet by worksheet. Each worksheet is a department or functional area and each row has the columns at the end where applying providers should enter whether their software fulfils the required function in the default can be implemented, whether adjustments are necessary, whether additional software needs to be used or whether the function is impossible to realise. It is not uncommon for the individual sheets in the Excel-Some functions in sheet 1 contradict those in sheet 2, or one and the same requirement appears in different places.
TIP
Take a look at various software solutions before you start formulating the specifications. Get an impression of what is currently state of the art.
Less is more! Concentrate on the most important things in the specifications. But this should be detailed and comprehensive.
With attention to detail and the courage to leave gaps
A strange discrepancy in the specifications for ERP selection often arises in the level of detail in the description of the desired functions. There are some who describe the order form down to the last detail, including all fields as they appear in the form and (differently) in the Database should be named. Other functions are handled with a simple one-liner, such as: "Suppliers are to be connected via IDE". The suspicion arises when reading such a specification sheet that the authors included people with very different levels of desire, expertise and/or time, without there being a coordinating body.
TIP
It may sound like a truism:
The specifications are about the "WHAT" not the "HOW". However, the "WHAT" should be sufficiently well described.
Everything standard - even the specifications
Others fall back on the quite understandable thought: "For such a Specifications there must be templates. You would think so, after all we are talking about standard software. Ergo, there must be standards that can be queried. There are templates for ERP specifications - lots of them! If in doubt, there is also a consultant who will fill out the template with you. However, if the template is supposed to be suitable for many companies, the questions may be too general or completely off the mark. For example, a company that has no stock items is asked how it deals with batch management.
ERP selection - if it were that easy / Part 1
ERP selection - if it were that easy / Part 2
ERP selection - if it were that easy / Part 3
ERP selection - if it were that easy / Part 4
ERP selection - if it were that easy / Part 5
