1 / 22

Know More. Do More. Spend Less.

The Future of Oracle WMS. AgendaWMS 11.5.10WMS Release 12WMS RFID SupportQ

sema
Download Presentation

Know More. Do More. Spend Less.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    1. Welcome today we are going to talk about new capabilities from Oracle to address the needs of the Warehouse.Welcome today we are going to talk about new capabilities from Oracle to address the needs of the Warehouse.

    2. The Future of Oracle WMS Agenda WMS 11.5.10 WMS Release 12 WMS RFID Support Q & A

    3. So how is it going So how is it going

    4. Oracle WMS 11.5.10 Available since November 2004 Part of Integrated Logistics solution Strengthened Transportation Execution New Transportation Planning Improved Operational Efficiency Advanced, Configurable Picking UI Enhanced Inbound Processes Bulk Picking & Overpicking Packing & Kitting Workbench DBI Analytics for Logistics (DBI 7.1) Labeling Industry / Compliance Support Built-in RFID/EPC Support (Wal-Mart, DoD) UCC14/UCC128 (CPG, Retail) Catchweight (Grocery, Metals, ) PAR Replenishment Counts (Healthcare)

    5. Advanced Pick Load Highly Configurable Mobile Picking UI Picking

    6. Packing & Kitting Workbench High Volume, Efficient Packing of Material

    7. Graphical Mobile User Interface Improved look and feel, equivalent performance

    8. Material Handling Integration A Warehouse Control System (WCS) Framework WMS setup for device definitions and business event mapping remains the same in CU#1. However, the setups required for the WCS directive definitions and sequence of execution are new. The primary function of the configuration table is to define the directive or message structure as a dynamic SQL query for association by business event to the device. Once a business event enable a WCS API call, the configuration defined for that device are applied during the creation of the directive or message. With the processing complete, an entry is written into the Queue table for a request-response dialog. All communications and event actions are logged into a database table for analysis or inquiry.WMS setup for device definitions and business event mapping remains the same in CU#1. However, the setups required for the WCS directive definitions and sequence of execution are new. The primary function of the configuration table is to define the directive or message structure as a dynamic SQL query for association by business event to the device. Once a business event enable a WCS API call, the configuration defined for that device are applied during the creation of the directive or message. With the processing complete, an entry is written into the Queue table for a request-response dialog. All communications and event actions are logged into a database table for analysis or inquiry.

    9. DBI for the Warehouse Manager

    10. So how is it going So how is it going

    11. Oracle WMS Release 12.0 Scheduled Availability mid-2006 Part of Integrated Logistics solution Converged Logistics Container Model Convergence with Oracle Process Manufacturing Integrated Warehouse Control System for Material Handling Devices Improved Operational Efficiency Labor Management Mobile UI Personalization Planned Cross-Docking Control Board, Material Workbench Enhancements Industry / Compliance Support Enhanced EPC Generation capabilities Process Features (DUOM, rules based reservations) Additional industry enablers

    12. Labor Management ELS, Data collection, Analytics, Labor Planning

    13. Planned Cross-Docking Automate Cross-Dock Pegging and Execution

    14. MWA Personalization Configure and Extend Mobile pages without code change

    15. Process Features Enhancing Inventory for Process Convergence Item Tracking Enhancements Dual Unit of Measure Availability by Material Status Operational Efficiencies Rules-based Reservations Manual selection of rules-validated material Enhanced Lot Control Additional standard attributes Indivisibility Detailed genealogy

    16. So how is it going So how is it going

    17. Oracle Sensor-Based Services HTTP Post ? Knee Jerk Reaction Want to determine event based on not just last 5 seconds, but over past month. Based on same set of data, want multiple consumers (different criteria for events). Hence, throw it in the queue and archive in Sensor Data Hub AS has interface layer on top of SDH ? EPCIS HTTP Post ? Knee Jerk Reaction Want to determine event based on not just last 5 seconds, but over past month. Based on same set of data, want multiple consumers (different criteria for events). Hence, throw it in the queue and archive in Sensor Data Hub AS has interface layer on top of SDH ? EPCIS

    18. Sensor-Based Services Start small and grow - leverage existing investments

    19. Standalone RFID Compliance RFID Capabilities with no Applications Prerequisites Functionality Import ASN Assign EPCs and generate Labels Verify RFID tags against ASN Return updated ASN Prerequisites No requirement for any Oracle Application footprint Oracle Application Server 10g for verification process XML for labels may require labeling software (or XML printers) Target Market Customers unable to upgrade prior to mandate Additional pilot project opportunities Delivered as consulting accelerator rather then full product

    20. RFID-Initiated Shipping & Receiving Built-in support for this emerging technology This diagram outlines the planned flow of an RFID Receipt. The huge potential of RFID is that data capture does not require user interaction or line of sight. So transaction can be processed without any manual user interaction with the system. Here the action of a receiving dock worker driving through a doorway which is covered by an RFID reader, will automatically trigger an ASN Receipt. Similar processes are possible for intra-warehouse moves, shipping, etc. To make this work several components are required: First, middleware is required to interface with the RFID Reader hardware and to provide the appropriate filtering so that duplicate or erroneous reads are eliminated. Next, the information from the read must be interpreted as a specific business event. This means that the ID of the tag must be resolved into some data on the system and based on the state of that data, the transaction to be processed can be deduced. For example, if you read an ID at a reader in Receiving, and that ID is associated with an LPN on an ASN that you have received from your supplier, then the transaction to be processed is an ASN Receipt of that LPN. Next, the application must process that transaction using a API which does not require user input. Finally any results or exceptions must be processed and these made available via the middleware. to the light trees, buzzers, etc to single results to the user. The above framework is currently being prototyped for possible inclusion in a future release.This diagram outlines the planned flow of an RFID Receipt. The huge potential of RFID is that data capture does not require user interaction or line of sight. So transaction can be processed without any manual user interaction with the system. Here the action of a receiving dock worker driving through a doorway which is covered by an RFID reader, will automatically trigger an ASN Receipt. Similar processes are possible for intra-warehouse moves, shipping, etc. To make this work several components are required: First, middleware is required to interface with the RFID Reader hardware and to provide the appropriate filtering so that duplicate or erroneous reads are eliminated. Next, the information from the read must be interpreted as a specific business event. This means that the ID of the tag must be resolved into some data on the system and based on the state of that data, the transaction to be processed can be deduced. For example, if you read an ID at a reader in Receiving, and that ID is associated with an LPN on an ASN that you have received from your supplier, then the transaction to be processed is an ASN Receipt of that LPN. Next, the application must process that transaction using a API which does not require user input. Finally any results or exceptions must be processed and these made available via the middleware. to the light trees, buzzers, etc to single results to the user. The above framework is currently being prototyped for possible inclusion in a future release.

    21. Oracle Differentiators Maximize the return on your RFID investment Architect to reduce risk Automatic data capture and filtering from various sensors Integrate with existing applications, business processes and Immediate access to accurate global information Common view of information that is available to all applications and business processes Start small and grow Breadth of technology provides customers with RFID-compliant solutions today and the infrastructure for RFID-centric businesses of the future Leverage existing investments Low integration, implementation, maintenance costs Technology leverages Oracles existing, proven, scalable architecture Optimized and flexible use of resources Automate and optimize business processes for competitive advantage Real-time supply chain visibility Continually optimize your business processes and IT infrastructure Processes (BPM), Events (BAM), Optimize (BPO), System

More Related