Optimising warehouse operations using SAP and integrated complementary technologies <br />Presenter: Stephen Hackett<br />...
Seminar Overview<br />The seminar will focus on:<br /><ul><li>The opportunities for warehouse process optimisation provide...
How substantial business benefit can be achieved with the integration of complementary technologies such as Voice, Mobile ...
An overview of how to integrate complementary technologies directly into an SAP based solution and the advantages of this ...
We work across the entire project with your business experts delivering practical and optimal solutions that add value acr...
Rocket provides professional solutions using SAP software, complementary technology such as mobile (RF) data and voice dev...
With a strong track record of delivering successful projects across a diverse range of industries, Rocket offers a valuabl...
Extended Warehouse Management (EWM)
Supply Chain Management (SCM)
Extended Warehouse Management (EWM)</li></ul>Not all customers realise the full business potential of functionality alread...
ERP Extended Warehouse Management<br /><ul><li>The standard SAP ERP warehousing solution can be enhanced/extended greatly ...
Task and Resource Management (TRM)
Extends the basic SAP warehousing solution, which focused purely on the activity that should be performed, allowing you to...
Yard Management (YM)
Provides greater  “real time” control  of all yard movements from the arrival to departure from the site.
Integrates directly into SAP Shipping and Transportation components providing more accurate planning and controlling data....
Most importantly SCM-EWM provides true seamless integration between physical layout and business process.
Can be run as an integrated solution with ERP 6.0, or a decentralised solution connected to SAP ERP 6.0 back to 4.6C.</li>...
Graphical Warehouse Layout</li></ul>Release 7.0 includes a graphical warehouse layout tool, however Rocket Consulting have...
Warehouse Process Optimisation with Complementary Technologies<br />Technologies allowing you to streamline your existing ...
Replaced the traditional paper based approach to executing tasks within a warehouse.
Reduced double entry
Upcoming SlideShare
Loading in...5
×

Warehouse process optimisation using SAP and integrated complementary technology

5,954

Published on

Exploring the opportunities for warehouse process optimisation provided by the SAP Warehouse Management, Logistics Execution and Supply Chain Management software.

Published in: Technology, Business
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,954
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Probably won’t bother speaking this page. Instead will simply have this displayed as people enter the seminar room (automatically scrolling between Page 1 and 2).The real presentation will start from slide 3 (Introduction).- Bullet this slide, so it’s easier to read.
  • I have been involved with the SAP software product for over 10 yearsImplemented SAP Warehouse Management and Logistics Execution modules in businesses across Europe and AfricaPrimary role in Rocket Consulting is the implementation of SAP Warehouse Management and complementary technologies.
  • This slide introduces the SAP software products that are available for Warehouse Management and Logistics Execution. The subsequent few slide will look at the major benefits of these solutions. The idea is not to discourage clients from one product or another, but rather play on the fact that if they’re not ready to make a full upgrade to SCM-EWM, there is still opportunity to use other process with an older ERP-EWM version.- Explain commonly used SAP acronyms.
  • This slide is a basic overview of some of the more advanced features in the well established ERP Extended Warehouse Management solution (focusing on TRM and Yard Management). Main points to make about TRM: Ensures that the right user get the right work at the right time. Can provide much more accurate information back to management report on picker performance.Main points to make about YM:Provides appropriate functionality allowing you to control and monitor all aspects of the Yard including Gatehouse, weigh bridges, door allocation and parking. Provide a graphical planning tool for inbound and outbound deliveries, allowing drag &amp; drop functionality for adjusting schedules.
  • SCM-EWM started out in the Service Parts Industry when the Standard WM functionality inside SAP couldn’t cater for the complexity that the businesses in this sector where faced with. SAP was approached by a joint venture between Ford &amp; Caterpillar with their complex requirements and this resulted in eWMThe Service Parts supply chain is very complex and because of this complexity, eWM functionality also meets the requirements stemming from several other industries too. Most important point to make is that the integration between the physical movement of stock and the processes that can occur are now seemless (receipt, deconsolidate, possibly some QM, putaway). This wasn‘t impossible with ERP WM, but did require more effort.SAP has strategically placed all development focus and priority on the development of their eWM offering
  • A brief discussion of the latest benefits, but really using this as an opportunity to introduce VWM via the discussion on the Graphical Warehouse Layout tool.7.0:Graphical Warehouse Layout: this is a management tool that provides a 2D representation of your warehouse, and can be used for ensuring that relevant configuration is correct (bin/conveyor layout), but also for monitoring the flow of goods throughout the warehouse. You can also view conveyor PLC’s in this display allowing you to see any potential problems that may have occurred (this is covered further when we discuss MFS as part of warehouse automation).VWM: Virtually wander around the warehouse, we thought this was missing in our experience.Resource Management Improvements: Resource Management has been available since 5.1, however 7.0 now includes more advance resource constraint logic similar to TRM.Other improvements include Cross Docking, Production Supply and general improvements on the warehouse monitor.
  • This slide will introduce the complementary technologies that I am going to discuss. Initially we will just provide a brief overview of each technology (for those that may not be so familiar with what they are), but then dive into the implementation of each and discuss the relative merits of integrated and interfaced approached.
  • The purpose of this slide is to identify the difference between an integrated and interfaced solution, this is used as a basis for the remainder of the discussion today with regards to the various technologies.- The advantages/disadvantages will be discussed on subsequent slides, the only point to make here is that integrated solutions (for the purpose of today’s discussion) are built within the SAP-ERP/SCM system framework, whereas the alternative is to link disparate systems via interfaces to the SAP-ERP system framework in order to achieve a business process.
  • The purpose of this slide is to explain at a high level what we mean between Integrated vs. Interfaced when discussing the introduction of new functionality into your business processes.Points to make:Not a debate about which is better. Both solutions have advantages over the other and can deliver comparable performance to the user. The decision is based on the business requirements, the ease of implementation, how the system can be supported, and the ongoing-maintenance and continuous improvement cycle. Rocket experience over the last number of years has made us believe that an integrated approach is better. Why? The entire business process solution can be structured in a single system allowing for the control logic to be driven directly from the business process. Type of request to user may be governed based on one or more business rules (e.g. Special customer, vendor may require additional steps of processing). Continued evolution of the product after go-live is far simpler. Specialist firms will not hang around after go-live completion. Bringing them back to do additional work can be time consuming (and costly). Reporting can be far more effective and less complex as all the required data is available in a single system. Other options (such as business content) are possible for middleware based solutions, however this all adds additional complexity. And not all clients are running the appropriate SAP software to read this data. Processes are far simpler to test “end to end” and do not requiring jumping between multiple systems. Interfaced: Some middleware solutions are delivered with a preset list of interfaces (certified with SAP). Day to day warehouse processes may not fit so neatly into these categories. Some middleware solutions are themselves also capable of WMS functions, these solutions can sometimes dependant on each other (e.g. A pick request may therefore require a product master) meaning that they are delivered “all or nothing”. So additional data may be required from SAP simply to “workaround” these requirements. Cost of middleware with resilience. Not financial cost, but rather additional time spent during project implementation, plus potential restrictions on business processes that a required to support offline events. Must ensure that business processes can provide adequate supply of data to system so that in the event of downtime, there is actually something there to work on (e.g. Wave picking would be advantageous). The point to make here is that even with the best backup/offline process in the world, if there was not enough work in the middleware before the system went down, then productivity is not really going to be improved.
  • The purpose of this slide is to explain at a high level what we mean between Integrated vs. Interfaced when discussing the introduction of new functionality into your business processes.Points to make:Not a debate about which is better. Both solutions have advantages over the other and can deliver comparable performance to the user. The decision is based on the business requirements, the ease of implementation, how the system can be supported, and the ongoing-maintenance and continuous improvement cycle. Rocket experience over the last number of years has made us believe that an integrated approach is better. Why? The entire business process solution can be structured in a single system allowing for the control logic to be driven directly from the business process. Type of request to user may be governed based on one or more business rules (e.g. Special customer, vendor may require additional steps of processing). Continued evolution of the product after go-live is far simpler. Specialist firms will not hang around after go-live completion. Bringing them back to do additional work can be time consuming (and costly). Reporting can be far more effective and less complex as all the required data is available in a single system. Other options (such as business content) are possible for middleware based solutions, however this all adds additional complexity. And not all clients are running the appropriate SAP software to read this data. Processes are far simpler to test “end to end” and do not requiring jumping between multiple systems. Interfaced: Some middleware solutions are delivered with a preset list of interfaces (certified with SAP). Day to day warehouse processes may not fit so neatly into these categories. Some middleware solutions are themselves also capable of WMS functions, these solutions can sometimes dependant on each other (e.g. A pick request may therefore require a product master) meaning that they are delivered “all or nothing”. So additional data may be required from SAP simply to “workaround” these requirements. Cost of middleware with resilience. Not financial cost, but rather additional time spent during project implementation, plus potential restrictions on business processes that a required to support offline events. Must ensure that business processes can provide adequate supply of data to system so that in the event of downtime, there is actually something there to work on (e.g. Wave picking would be advantageous). The point to make here is that even with the best backup/offline process in the world, if there was not enough work in the middleware before the system went down, then productivity is not really going to be improved.
  • The purpose of this slide is to explain at a high level what we mean between Integrated vs. Interfaced when discussing the introduction of new functionality into your business processes.Points to make:Not a debate about which is better. Both solutions have advantages over the other and can deliver comparable performance to the user. The decision is based on the business requirements, the ease of implementation, how the system can be supported, and the ongoing-maintenance and continuous improvement cycle. Rocket experience over the last number of years has made us believe that an integrated approach is better. Why? The entire business process solution can be structured in a single system allowing for the control logic to be driven directly from the business process. Type of request to user may be governed based on one or more business rules (e.g. Special customer, vendor may require additional steps of processing). Continued evolution of the product after go-live is far simpler. Specialist firms will not hang around after go-live completion. Bringing them back to do additional work can be time consuming (and costly). Reporting can be far more effective and less complex as all the required data is available in a single system. Other options (such as business content) are possible for middleware based solutions, however this all adds additional complexity. And not all clients are running the appropriate SAP software to read this data. Processes are far simpler to test “end to end” and do not requiring jumping between multiple systems. Interfaced: Some middleware solutions are delivered with a preset list of interfaces (certified with SAP). Day to day warehouse processes may not fit so neatly into these categories. Some middleware solutions are themselves also capable of WMS functions, these solutions can sometimes dependant on each other (e.g. A pick request may therefore require a product master) meaning that they are delivered “all or nothing”. So additional data may be required from SAP simply to “workaround” these requirements. Cost of middleware with resilience. Not financial cost, but rather additional time spent during project implementation, plus potential restrictions on business processes that a required to support offline events. Must ensure that business processes can provide adequate supply of data to system so that in the event of downtime, there is actually something there to work on (e.g. Wave picking would be advantageous). The point to make here is that even with the best backup/offline process in the world, if there was not enough work in the middleware before the system went down, then productivity is not really going to be improved.
  • Points to make regarding advantages and benefits of an integrated RF approach: SAP RF transactions that come as standard (loading/unloading, putaway, picking, packing, physical inventory) Option to be up-and-running out of the box with RF. Transactions can be used as templates for more complicated business processes. Implementation simplicity due to single system. Enhancements can be made quickly and easily (no reliance on a specific external company). Developed as any other normal dialog transaction in SAP.A brief explanation of the development tool.
  • Points to make regarding advantages and benefits of an integrated RF approach: SAP RF transactions that come as standard (loading/unloading, putaway, picking, packing, physical inventory) Option to be up-and-running out of the box with RF. Transactions can be used as templates for more complicated business processes. Implementation simplicity due to single system. Enhancements can be made quickly and easily (no reliance on a specific external company). Developed as any other normal dialog transaction in SAP.A brief explanation of the development tool.
  • This slide illustrates the various RF integration approaches that are available are available with SAP.Points to make: Execution logic is contained within SAP-ERP Evolution from using SAP Console, through WebSAPConsole, to ITS. Explain advantages of each evolution. SAP Console, first solution available, text based.WebSAPConsole, same as first, although presented better.ITSMobile, full flexibility with modifiying screen presentation without actually changing the standard SAP solution (e.g. Introducing graphics, etc).Make sure it is pointed out that the processing execution logic is held within the WMS and the above technologies simply enable the communication between RF and SAP. There are alternatives to SAP software above (e.g. TekConsole, claiming better session management, etc).
  • Points to discuss:- Very quick overview of Voice.
  • Just brief overview of the advantages of voice over other picking technologies.
  • This slide presents the Rocket recommended approach to Voice integration.Points to make: All voice operations and business logic is held within the WMS. Two different solutions available based on your current version of SAP, WebSAPConsole enabled backwards compatibility of integrated voice with pre ECC 6.0 SAP systems (e.g. 4.6C). Existing SAP RF transactions (that you may already have in use today) can be enabled for Voice. Voice Enabled Web Browser (TopSPEECH Lydia) Speech recognition supports over 25 languagesSpeaker independent alleviating need for voice training Speaker dependent support if requiredReduced training times from three levels of spoken detailEase of use with true spoken voice (not synthesised) Supports Text-to-Speech conversion e.g. material descriptions No proprietary hardware or middleware requiredVoice only or Multi-modal (Voice + scanning + screen in/output) Recommended solution (assuming ECC 6.0) is integrated ITS process. Most flexible (in terms of development and extension of existing SAP RF transactions). Most resilient and more powerful with integrated ITS (e.g. Better session management and performance monitoring).
  • I’d like to mention SAP MFS which is a component of SCM-EWM.Until recently nearly all warehouse automation implementations have involved SAP comm
  • I’d like to mention SAP MFS which is a component of SCM-EWM.Until recently nearly all warehouse automation implementations have involved SAP comm
  • Illustration of the integration of MFS with other advanced components of SCM-EWM 7.0Points to make: Conveyor layout is mapped in SAP and can be visually displayed with the Graphical Warehouse Layout tool. Allows for the monitor of stock currently on the conveyor and also trouble points. Removing the need to view two separate systems for daily monitoring.
  • Final page, identifying where our stand is for follow up discussions, etc.
  • This slide illustrates the various RF integration approaches that are available are available with SAP.Points to make: Execution logic is contained within SAP-ERP Evolution from using SAP Console, through WebSAPConsole, to ITS. Explain advantages of each evolution. SAP Console, first solution available, text based.WebSAPConsole, same as first, although presented better.ITSMobile, full flexibility with modifiying screen presentation without actually changing the standard SAP solution (e.g. Introducing graphics, etc).Make sure it is pointed out that the processing execution logic is held within the WMS and the above technologies simply enable the communication between RF and SAP. There are alternatives to SAP software above (e.g. TekConsole, claiming better session management, etc).
  • This slide illustrates the standard interfaced approach with SAP for RF processing.Points to make: Application logic for the user resides a lot more on the Middleware side. Although this depends on the particular vendor, and decisions that are made during the implementation process (e.g. Bin verifications, generally require communication back to SAP bin master unless data held locally). Execution logic is held in middleware. No rule governing when/how the middleware communicates with SAP. Synchronisation is important for resilience (e.g. Creation/deletion of work). Problem solving can be more difficult.
  • The purpose of this slide will be to show that we have performed Voice implementations using both interfaced and integrated solutions. The key point to make is that although we have performed both types of implementation, the Integrated approach at Brady is our preferred.
  • Warehouse process optimisation using SAP and integrated complementary technology

    1. 1. Optimising warehouse operations using SAP and integrated complementary technologies <br />Presenter: Stephen Hackett<br />Created on: 27/01/09<br />Version 1.5<br />Copyright © Rocket Consulting Limited 2009.<br />All Trademarks are hereby acknowledged.<br /> <br />This document contains information that is proprietary to Rocket Consulting<br />and must not be disclosed in whole or in part to any third party.<br />
    2. 2. Seminar Overview<br />The seminar will focus on:<br /><ul><li>The opportunities for warehouse process optimisation provided by the SAP Warehouse Management, Logistics Execution and Supply Chain Management software
    3. 3. How substantial business benefit can be achieved with the integration of complementary technologies such as Voice, Mobile (RF) Data Entry, and warehouse automation.
    4. 4. An overview of how to integrate complementary technologies directly into an SAP based solution and the advantages of this approach compared to interfacing other external solutions. </li></li></ul><li>Introduction<br /><ul><li>Rocket Consulting is a specialist SAP consultancy dedicated to helping businesses meet the demands of today’s supply chain and warehouse management operations.
    5. 5. We work across the entire project with your business experts delivering practical and optimal solutions that add value across the industry.
    6. 6. Rocket provides professional solutions using SAP software, complementary technology such as mobile (RF) data and voice devices, RFID and warehouse automation, and specially designed SAP add-ons.
    7. 7. With a strong track record of delivering successful projects across a diverse range of industries, Rocket offers a valuable combination of knowledge, fresh thinking and best practices.</li></li></ul><li>Warehouse Process Optimisation using SAP<br />Two main SAP Warehouse Management solutions available:<br /><ul><li>Enterprise Resource Planning (ERP)
    8. 8. Extended Warehouse Management (EWM)
    9. 9. Supply Chain Management (SCM)
    10. 10. Extended Warehouse Management (EWM)</li></ul>Not all customers realise the full business potential of functionality already available in their existing SAP WM systems.<br />
    11. 11. ERP Extended Warehouse Management<br /><ul><li>The standard SAP ERP warehousing solution can be enhanced/extended greatly using Task & Resource Management, and Yard Management. Both have been available for a number of years and can significantly improve your business process.
    12. 12. Task and Resource Management (TRM)
    13. 13. Extends the basic SAP warehousing solution, which focused purely on the activity that should be performed, allowing you to control/monitor when and how each activity is performed.
    14. 14. Yard Management (YM)
    15. 15. Provides greater “real time” control of all yard movements from the arrival to departure from the site.
    16. 16. Integrates directly into SAP Shipping and Transportation components providing more accurate planning and controlling data.</li></li></ul><li>SCM Extended Warehouse Management<br /><ul><li>SCM-EWM was developed as a replacement to ERP-EWM taking many of the advanced components (TRM, YM) and integrating these into a single seamless package.
    17. 17. Most importantly SCM-EWM provides true seamless integration between physical layout and business process.
    18. 18. Can be run as an integrated solution with ERP 6.0, or a decentralised solution connected to SAP ERP 6.0 back to 4.6C.</li></li></ul><li>SCM Extended Warehouse Management<br />Release 7.0 in ramp-up Q3/4 2008, improvements:<br /><ul><li>Resource Management, Cross Docking, Production Supply
    19. 19. Graphical Warehouse Layout</li></ul>Release 7.0 includes a graphical warehouse layout tool, however Rocket Consulting have also developed a 3D graphical warehouse tool (call Virtual Warehouse Monitor) that is backward compatible with all SAP Warehouse Management Implementations (with some restrictions and requirements for non-TRM based solutions).<br />Graphical Warehouse Layout<br />Virtual Warehouse Monitor<br />
    20. 20. Warehouse Process Optimisation with Complementary Technologies<br />Technologies allowing you to streamline your existing supply chain operations giving your existing systems and processes a major efficiency boost.<br /><ul><li>Radio Frequency
    21. 21. Replaced the traditional paper based approach to executing tasks within a warehouse.
    22. 22. Reduced double entry
    23. 23. Increased accuracy and efficiency
    24. 24. Voice
    25. 25. Frees hands and eyes of the worker
    26. 26. Improves productivity (approx 25% on RF)
    27. 27. Automation
    28. 28. Reduction in labour
    29. 29. Better space utilisation
    30. 30. Improved throughput</li></li></ul><li>Implementing Complementary TechnologiesIntegrated or Interfaced?<br />Integrated<br /><ul><li>A single application supports all the business requirements in the entire warehouse.</li></ul>Interfaced<br /><ul><li>Two or more separate applications are utilised in order to support a business process and build a system.
    31. 31. Communication structures (interfaces) are setup in order to transfer the necessary information between the applications (e.g. master data, pick request, pick confirmation).</li></li></ul><li>Integrated or Interfaced?<br /><ul><li>Business and Control logic
    32. 32. Keeping the business and control logic in a single system simplifies the definition and implementation of warehouse processes.
    33. 33. As soon as the business and/or control logic is distributed to other applications, the responsibilities of each application becomes much more complex to manage.
    34. 34. Management Tools
    35. 35. The ability to provide up-to-date real time reporting is made far simpler if the dataset can be accessed locally and completely.
    36. 36. The dissemination of information on other systems requires the implementation of a central Business Content repository and appropriate data maintenance tools.</li></li></ul><li>Integrated or Interfaced?<br /><ul><li>Users and Master Data
    37. 37. Both solutions offer single sign-on benefit, however some interfaced solutions will only use a generic logon with ERP reducing traceability and increasing the complexity of user authorisations and restrictions.
    38. 38. Master Data distribution can become a hot topic during business process design, especially if the desired functionality is over and above the middleware’s Out of the Box capabilities.
    39. 39. Support
    40. 40. With an integrated solution, existing support contracts can remain with little or no alterations required, compared with having to setup a second support contract with a new vendor requiring a clear demarcation of system boundaries.</li></li></ul><li>Integrated or Interfaced?<br /><ul><li>Continuous Improvement
    41. 41. System enhancements for evolving business requirements can be handled by existing systems support on a integrated platform, whereas middleware based solutions can be more complex/difficult requiring specialist “niche” vendors.</li></ul>The Rocket methodology places high emphasis on implementing integrated solutions with SAP.<br />
    42. 42. Radio Frequency (RF) <br /><ul><li>Paper based operations require initial recording of data by a user and then re-entry into the system by a clerk, whereas an RF solution will only require entry of information once.
    43. 43. The users actions can be verified in real-time enabling greater accuracy of warehouse processes.
    44. 44. Execution and extraction of transactional data can be simplified with the integration of optical and RFID scanning technologies.
    45. 45. Information on task execution by a user can be tracked in real-time providing the necessary data for performance reporting and traceability.</li></li></ul><li>Benefits of an Integrated SAP RF Solution<br /><ul><li>Implementation is kept simple as all relevant business logic is in the same system as the RF transaction.
    46. 46. Faster implementation times
    47. 47. Enhancements can be made easily and quickly
    48. 48. SAP already supplies a large amount of RF transaction as standard covering most warehouse operations (loading/unloading, picking, packing, physical inventory, VAS)
    49. 49. Development tools for these RF “dialog” transactions have evolved from SAP Mobile Data Entry, TRM Presentation Management and now RF Framework, which has taken the best elements of flexibility and functionality.</li></li></ul><li>RF Integration Options with SAP<br />Connects with Telnet Client<br />Telnet Server<br />SAP<br />WMS<br />SAP Console<br />Web Server<br />SAP<br />WMS<br />WebSAP Console<br />Connects via Internet Browser<br />SAP<br />WMS<br />Integrated<br />ITS<br />
    50. 50. Voice<br />Voice control liberates the workforce’s Eyes and Hands to do their jobs effectively<br /> Provides natural person to system communication<br /><ul><li> Better concentration on the job helps eliminate mistakes
    51. 51. Removes need to focus on or hold a device or paper</li></ul> Increased accuracy<br /><ul><li> Substantial miss-pick (product inversion, quantity) reduction</li></ul> Increased efficiency<br /> Very quick and easy to train new operators<br /> Improved workplace safety<br /> Operators like it!<br />
    52. 52. How does Voice compare?<br />
    53. 53. Voice Integrated with SAP<br /><ul><li>Voice controlled operations achieved with SAP through Rocket and TopSystems partnership</li></ul>Web Server<br />SAP<br />WMS<br />Voice Enabled Web Browser<br /><ul><li>Carries out voice presentation
    54. 54. Interprets spoken responses</li></ul>WebSAP Console<br />Voice <br />Control<br />SAP<br />WMS<br />Integrated<br />ITS<br />Voice Control<br />
    55. 55. Warehouse Automation<br /><ul><li>Warehouse Automation covers a large scope:
    56. 56. Automatic transportation of boxes/totes between locations.
    57. 57. Automated storage and retrieval of pallets.
    58. 58. Automatic sorting, labeling, and staging of goods for customer deliveries.
    59. 59. Benefits of Warehouse Automation
    60. 60. Decreased inventory handling and therefore reduced chance of damage to articles.
    61. 61. Decreased personnel and labour costs.
    62. 62. Improved efficiency and accuracy.
    63. 63. Increased throughput.</li></ul>Traditional implementations involved the development of interfaces between SAP and Warehouse Control Systems.<br />
    64. 64. Warehouse Automation Integrated with SAP<br />SAP Material Flow System (MFS) has been introduced with EWM 5.0 (part of the SCM platform) to provide an integrated solution to warehouse automation.<br /><ul><li>Communicates directly with PLC’s and other automation equipment removing the need for Warehouse Control Systems.
    65. 65. A single system can monitor the entire operation. This is especially important for deliveries that may contain pick requests that are divided between conveyor and non-conveyor operations (historically requiring creative reporting).
    66. 66. Delivers all the required tools to monitor communication and reacting accordingly in the event of failure.
    67. 67. Added flexibility for process improvement.</li></li></ul><li>Warehouse Automation Integrated with SAP<br /><ul><li> Integrated with Graphical Warehouse Layout tool in version SCM 7.0</li></li></ul><li>Thankyou for you time.<br />Please visit us at stand 95 if you have any further queries.<br />www.rocket-consulting.com <br />
    68. 68. Appendix Slides<br />
    69. 69. Radio Frequency Interfaced with SAP<br />Middleware<br />SAP<br />WMS<br /><ul><li>Single sign-on to Middleware
    70. 70. Transactional elements (menu’s, fields, buttons, etc) are stored and handled in the Middleware
    71. 71. Transaction logic and verifications can be executed in Middleware
    72. 72. Middleware executes all requests to SAP on the users behalf (sometimes via a single user ID).
    73. 73. Communication between SAP and Middleware usually via IDoc interface, although tRFC/qRFC also possible</li></li></ul><li>Examples of Recent Voice Experience <br /><ul><li> Brady Corporation (Integrated)
    74. 74. High variety of SKUs (health & safety and office consumables)
    75. 75. Trolley put-away
    76. 76. Trolley picking by transfer order item
    77. 77. Trolley picking by material with accumulated quantity
    78. 78. Integration into SAP warehouse management
    79. 79. Laithwaites / Direct Wines (Interfaced)
    80. 80. High volume wine distribution centre
    81. 81. Picking and packing of wines cases onto conveyor
    82. 82. Interfaced into SAP warehouse management with </li></ul> task and resource management<br />

    ×