From a technical point of view, there are no differences between an SAP® EWM implementation project in a greenfield or an existing warehouse. What’s different, however, is the way these two project types are prepared and implemented.
In brownfield projects, old systems that have been in use for 20 years or more are replaced. This means there is a wealth of documentation available, which is vital for an SAP® EWM implementation project. That’s why we recommend reviewing these documents prior to project start to verify if interface adaptations, specifications on resolving error situations and subsequent changes to the implementation and operation phases – among other things – have been clearly and completely documented. Along with extensive documentation, old systems are usually highly optimized because of their long-time usage. Although it’s tempting to map these systems in SAP® EWM as they are, doing so is not very useful for understanding the requirements for the new system that are independent of the solution. An analysis with respect to future market and customer requirements should be conducted to identify which processes are already covered by the SAP® EWM standard solution and which might need to be adapted. The fit-gap analysis mentioned above helps to determine which processes fall under each category.
When implementing SAP® EWM for a greenfield project, there are no historic legacies to deal with. This is a great opportunity to tailor the new system from scratch to meet current requirements without having to compromise. But let’s not get carried away. Even for a greenfield project, you should focus on what matters most and plan the ramp-up phase properly and in detail so it can be completed in a timely fashion.