In 2024, 4SCM began redesigning an existing integration between a shuttle system and SAP EWM that had been implemented by a previous implementation partner. The shuttle had been running for more than 20 years and had originally been built and implemented for another WMS system. Because of the fundamentals of the architecture chosen at the time, the complexity of integrating the shuttle with SAP EWM was high. There were three main flows identified within the shuttle; inbound, order picking and inventory counting. The main reason why a complete redesign was needed was because the previous partner had integrated the shuttle system as a "black box," causing inventory between EWM and Viadat to be out of sync due to the fact that stock differences, physical stock and pick differences were not communicated.
Role
As implementation partner for SAP EWM, 4SCM was responsible for overseeing the implementation of the integration between Viadat and EWM, ensuring seamless integration and optimization of warehouse processes. In addition, the main requirement was to keep inventory synchronized between EWM and Viadat.
Approach
Our approach began by identifying the business processes needed within the shuttle. From there, it became clear that the biggest problem was inventory discrepancies between EWM and Viadat. Working closely with the business, it was decided to make the EWM system leading and correct any inventory discrepancies between EWM and Viadat directly, communicating through a new inventory counting interface.
Technically, we specified and built the developments, focusing on correct and stable interfacing between EWM and Viadat. Once development was completed, multiple testing phases were performed and, most importantly, the solution was validated in the warehouse itself. After the official "go," master data and inventory migration were implemented. We also led the go-live process as the project's implementation partner so that potential issues could be identified immediately.
Result
Despite the significant changes for the company, both in terms of processes and technology, no significant problems emerged after the go-live and the process became more manageable, fully system-driven and transparent. The system was fully operational again immediately after the go-live.
Overarching interest
It is important to say that the shuttle was not only used for inbound and outbound processes, but also closely integrated with other business processes such as production and returns. Our collaboration with both the business and technical consultant at Viadat ensured a successful implementation that met the client's specific needs.