Today I would like to have an open discussion on integrating Robots with SAP EWM using SAP Warehouse Robotics or 3rd party softwares. I listed some of the considerations to choose the better solution for the project. I give my point of view and feel free to share your views and experiences. Hope this healthy and unbiased discussion will help many to make the right decision. Also remember that the discussion is based on the offerings as of today.
- System Architecture
- Software Cost
- Implementation effort
- Monitoring/Troubleshooting the work
- Value additions
- Dependencies
- Supported Processes
- Lessons learnt
System Architecture
SAP: At high-level it is a new SAP’s cloud (released in 2205) product helps you to integrate your SAP EWM (9.5 or S4H EWM) with the Robots. Visit the help page to get yourself familiar with the SAP Warehouse Robotics. It is a kind of add-on, and easy to plug-in. It works as a middleman between SAP EWM and Robots. It mostly uses the same EWM terminology. It can talk to Robots from different vendors. These Robots can connect to it directly or via the vendor software.
Non-SAP: You may need to develop interfaces based on IDocs or ODATA or SOAP XML to connect SAP EWM with the vendor software. SAP provided some IDocs to integrate with the sub-systems. In the latest version of S4HANA APIs are also available.
My view: I am inclined towards SAP Warehouse Robotics since it is easy and hassle free.
Software Cost
SAP: I am not aware how much it costs and how the licensing works. At least I understood from the online resources (check the comments on this URL) that it is not for free even if you have BTP. Please comment if you have any details on this.
Non-SAP: The cost varies vendor to vendor and size of the project etc. At least from my past experience, the client starts seeing the returns from the 2nd year.
My view: Not having enough details to compare.
Implementation Effort
SAP: It requires minimal configuration effort. Since it is a SAP product, the integration between EWM and SAP Warehouse Robotics can be established easily. However, you may have some effort to integrate the Robots with the SAP Warehouse Robotics. SAP already provided APIs to consume readily.
Non-SAP: Some vendors are flexible, they can work with whatever SAP EWM can offer by standard. In other cases, you may need to develop interfaces. The complexity of interfaces may vary depends on your project scenarios.
My view: I prefer SAP Warehouse Robotics.
Monitoring/Troubleshooting the work
SAP: It provides Fiori apps to monitors the progress, exception handling (basic) and troubleshooting (to certain extent).
Non-SAP: Your vendor may provide some tools to monitor and troubleshoot. Otherwise you can still use the warehouse monitor to track the progress. You may have to build the exception handling in your interfaces and test them thoroughly. Or you should have clearly defined the exception handling manually. Some vendors can provide alerts for any failures otherwise you have to setup them in SAP. Some vendors can provide better graphical layout view of the warehouse.
My view: Can’t decide.
Value Additions
SAP: In this architecture SAP EWM is still the brain and other components are hands.
Non-SAP: You can setup a basic warehouse in SAP EWM and dump all the computational work to the vendors software. Most of these vendors are very competitive in the market and coming up with the new technologies such as AI for the optimization (e.g. pick path, task consolidation etc.) and automations.
My view: Non-SAP. I do not hear about using AI in SAP EWM at least.
Dependencies
SAP: The more systems you add to the landscape the more dependencies you have. Compared to Non-SAP architecture this is an extra component to handle by the basis team. In this architecture, the client still needs to rely on the Robots vendor for some support (e.g. software/hardware issues).
Non-SAP: Your vendor is your single point of contact for hardware/software issues. These vendors can work with directly SAP EWM, no middleware tool is needed.
My view: Non-SAP.
Supported Processes
SAP: There are some limitations and all the scenario may not support. Since it is a cloud product it may not be easy to develop a custom solution.
Non-SAP: You can develop and customize the interfaces to meet your needs.
My view: Can’t decide. It depends on your project needs.
Lessons Learnt
SAP:
Non-SAP:
My view: I worked on integrating AGVs with Robots using non-SAP softwares. We did thorough testing to resolve most of the issues. The very few remaining issues were out in the initial phase of the hypercare. Within 3 months we had smooth exit of the project.