SAP Auto-ID Infrastructure 2.0 (AII) Page 1 / 18

Transcription

1 SAP Auto-ID Infrastructure 2.0 (AII) Page 1 / 18

2 History of AII at SAP Why does SAP get into the RFID world? Details Core Services Integration Services Sample Process Supported processes Integration of SAP EM Page 2 / 18

3 1999 Initial development of RFID integration Point of Sale Demo at various Sapphires 2000 Specification and design for RFID Engine Warehouse Management Demo at various Sapphires 2001 Concept for Auto-ID Infrastructure Started Cooperation with Auto-ID Center & M-Lab 2002 Started Auto-ID Infrastructure Prototypical Development Adaptive Supply Chain Demo at various Sapphires (Smart Shelf) 2003 Go-Live of Future Store Initiative Go-Live of Procter & Gamble Pilot 2004 Ramp-Up for SAP RFID solution package Page 3 / 18

4 History of AII at SAP Why does SAP get into the RFID world? Details Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 4 / 18

5 How do you plan to use Auto-ID data? Standalone application with minimal integration 3% Stand alone application with middleware configuration 24% Integrated with existing ERP 71% 0% 10% 20% 30% 40% 50% 60% 70% 80% Source: EPC Forum Survey Results, 2003 Page 5 / 18

6 !" # $ % % SAP R/3 4.6C/4.7, ERP 1.0 Real world aware Business Processes represented by Enterprise Applications (ERP, SCM, CRM, PLM, SRM...) SAP SCEM SAP SAP 3 rd Party BW 1 WMS 1... APO 1 SAP Auto-ID Infrastructure active tag Environmental Sensors passive tags Physical World represented by Smart Objects Page 6 / 18 1 not supported yet

7 &' & Role-based User Interfaces Composite Business Processes Service request Availability Trigger Assembly Goods receipt Operational Backbone Page 7 / 18

8 ( $& )*'% Role-based User Interfaces Composite Business Processes Service request Availability Trigger Assembly Goods receipt Operational Backbone Intelligent Stuff Page 8 / 18

9 &* '&% AutoID Infrastructure () and beyond Technology Read / Write tags Rule processor AutoID support Visibility Auto-ID networks Configurable transactions Process control Voice support Material Flow Computing Today Wal*Mart Interoperability Q2/2004 Own Efficiency Improved Operations / ROI Future Content Pallet / Carton level HU build / Packing Ship / Receive Track&Trace (EM) Processes and Scenarios WM: Pick / Putaway / Consolidate Manufacturing Item level tagging Smart shelves AutoID driven CPFR Page 9 / 18

10 %&* #+, -%.//0 Wal*Mart expects its US-based 123// suppliers to provide RFID tags on case and pallet level Wal*Mart wants its suppliers to benefit from RFID investments Wal*Mart wants one global standard Wal*Mart wants to collaborate tightly with its suppliers Wal*Mart wants the solutions to start easy.//4 Wal-Mart expects!! its US-based suppliers to use Auto-ID on case and pallet level Page 10 / 18

11 ,$ & $5#+, 3 Rollout Jan 2005 Distribution Centers: Regional: Sanger TX Grocery: Cleburn TX Sam s cross docks: Desoto TX 100 Suppliers + 32 volunteers Dedicated product lines per supplier Stores / Clubs in that region 150 Stores & Clubs Discount Super Centers (incl DSD) SAM s club (incl DSD) Neighborhood market (incl DSD) Through 2005 rollout nationally Through 2006 Rollout internationally Jan 2006 all suppliers Page 11 / 18

12 History of AII at SAP Why does SAP get into the RFID world? SAP RFID technology Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 12 / 18

13 1 The illustration below shows an overview of SAP RFID landscape: RFID Tags Reader Device Controller SAP Auto-ID Infrastructure (AII) SAP Exchange Infrastructure (XI) SAP EM (optional)!! 6,!7,! Auto-ID Cockpit (Web User Interface) 6,! SAP R/3 Backend Traffic Generator Page 13 / 18

14 2''* SAP Auto-ID Infrastructure 2.0 (AII) is a middleware solution receiving RFID data from data capture sources, e.g. RFID devices, and integrates the data directly into enterprise applications. It converts raw RFID data into business process information by making associations of key business rules, master data and transactions to raw RFID data. Key AII capabilities include: integration of high-volume RFID data into enterprise applications that drive business processes encoding and re-writing of RFID tags local business intelligence and decision support at point of data capture multi-layered RFID data aggregation and filtering RFID data capture device management central business rule, device and inventory information management role-based access to RFID data synchronous and asynchronous communication with Auto-ID data capture devices exception alerting and reporting pre-configured back-end process enablement adaptors and generic API for SAP R/3 4.6c or greater. Page 14 / 18

15 %% $$!$&7 R/3, ERP EM BW 1 SCM 1 WM XI Plant 1 DC 1 AII AII Device Controller Gate 1 DC Gate 2 Device Controller Gate 3 DC Gate 4 Reader/ Interrogator Reader/ Interrogator Reader/ Interrogator Reader/ Interrogator Reader/ Interrogator Reader/ Interrogator Sensor Sensor Sensor Sensor Sensor Sensor 1 Not available yet Page 15 / 18

16 # 5 $8 Expected Events Filtering Buffering Smoothing Data abstraction Reader abstraction Tag abstraction "Goods in" scenario Filtered read / write Data buffer Save read "UID" Read "Address, Len" Via Ethernet Labels Read "Tag Pages" Page 16 / 18

17 &" Customer RFID Landscape Without SAP R/3 With SAP R/3 4.6C and SAP R/3 4.7 With SAP ERP 2004 / Business Suite Solution Offering SAP NetWeaver RFID enabled SCM Solution Package mysap ERP / Business Suite Package Contains SAP Auto-ID Infrastructure and Content SAP Auto-ID Infrastructure and Content SAP Auto-ID Infrastructure and Content SAP NetWeaver SAP R/3 Auto-ID Adapter SAP Event Management 1 SAP Event Management SAP NetWeaver Package Requires SAP R/3 4.6c or SAP R/3 4.7 mysap ERP 2004 or higher Integration Project based via SAP GCDS or Partner Use Auto ID - R/3 Integrator Toolbox + Project SAP GCDS Process based Out of the Box Integration Implementation Project SAP Consulting or Partner SAP Consulting or Partner SAP Consulting or Partner 1 mysap ERP 2004 standard delivery does not include SAP Event Management (SAP SCM 4.1) Page 17 / 18

18 History of AII at SAP Overview Details Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 18 / 18

19 "& SAP Auto-ID Cockpit is a Java Web Dynpro-based tool that enables you to configure and administer SAP Auto-ID Infrastructure systems. Using the SAP Auto-ID Cockpit, you can perform the following: Activity management, including maintaining activities, rules and conditions Data management, including displaying transaction data and master data, as well as performing various manual processing functions Auto-ID infrastructure customizing, including maintaining RFID devices, message dispatcher for messaging, action types, archiving settings and GTIN number ranges for EPC generation Page 19 / 18

20 The SAP Auto-ID Infrastructure 2.0 is realized as a Java based web application and it is running on SAP J2EE Web Application Server 6.40 SAP Auto-ID Infrastructure 2.0 is composed of two main components: Core services The core part includes flexible definitions and a rule-sets environment accompanied by a powerful execution engine to address the various processes required by each SAP Auto-ID Infrastructure. Integration services SAP Auto-ID Infrastructure needs to interact with three types of environments including backend systems (via SAP XI), devices (via Device Controller) and operational staff, and also to support human interaction for definition, control and maintenance. SAP Auto-ID Infrastructure (AII) Core Services Device Controller Integration Services Auto-ID Cockpit (Web User Interface) SAP Exchange Infrastructure (XI) Page 20 / 18

21 History of AII at SAP Overview Details Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 21 / 18

22 '3 These are the core services sub-components: Action and Process Management: Allows to define specific action handlers to manage required processes interacting with the various parties i.e. devices, humans, systems. It includes action handling, rule engine and message dispatching. Configuration & Admin. Management: It includes support for the definition of devices and their operational staff, backend systems and other Auto-ID Infrastructures. In addition, it controls the internal component configuration allowing for flexible way to enabling and disabling of a component. Core Services :,% Action Handling Rule Engine Event Queue/s :$%,% Device/User Component Backend 259,% Expected Current Trace Action State!,,% 259,% Location Event Message Dispatcher Product Page 22 / 18

23 '. These are the core services sub-components: Object Data Management: The target of Object Data Management is thus to control the current state of an object (e.g. pallet of goods, case or consuming unit) in terms of location and structure, and also to record past actions. Supporting this need requires also having an object expected action, which improves the accuracy and minimizing user-required action. Expected action is a representation of backend order documents. Lean Master Data Management: SAP Auto-ID Infrastructure requires a limited sub-set of master data to mainly support user interaction (e.g. product description) as well as to supporting local executed rules (e.g. read threshold by vendor) and translation of tag information. Core Services :,% Action Handling Rule Engine Event Queue/s :$%,% Device/User Component Backend 259,% Expected Current Trace Action State!,,% 259,% Location Event Message Dispatcher Product Page 23 / 18

24 History of AII at SAP Overview Details Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 24 / 18

25 ' Integration services are aimed to enable integration with the 3 different environments that interact with a SAP Auto-ID Infrastructure. The purpose of these services is to also isolate the internal core service of a node from the external world and to make it independent. Human Integration Supports the access of users (via Auto-ID Cockpit) for the following purposes: definition, controlling and maintenance ensuring also security and authorization management. Backend System Integration The purpose of this component is to handle all the communication with the various backend systems (normally via XI). The component offers an environment for two types of adapters, communication adapters supporting the various communication protocols and technologies as well as application adapters that can also perform data conversion. In addition it exposes a generic set of API that serves as the interface to the core part. Device Integration The SAP Auto-ID Infrastructure is expected to interact with Device controllers. The Device Controller is directly connected to the sensor level i.e. read/write unit (also known as interrogator or reader ). The device integration is analogous to the backend system integration. Page 25 / 18

26 History of AII at SAP Overview Details Core Services Integration Services Sample Process SAP Auto-ID Cockpit Page 26 / 18

27 %&$%& SAP Auto-ID Infrastructure (AII) Device Controller Message Receiver Message Parser Condition and Rule Processor Activities Activities Activities XI DB The above illustration shows a possible (simplified) process in SAP Auto-ID Infrastructure: An XML message containing raw EPC data is submitted from Device Controller to AII. There the message is finished by the Message Receiver class and forwarded to Message Parser. The Parser class extracts all important information from the message and converts it into a message object. This new object handled by Condition and Rule Processor. Depending on the object s type and data the Rule Processor initiates one ore more activities. These activities can influence information stored in a database or generate a new message which is forwarded to SAP Exchange Infrastructure (XI). XI itself will do some conversion and send it up to R/3 backend where it initiates some other action. Page 27 / 18

28 # $ Location Gate Staging Area Warehouse Staging Area Gate Activity Unloading Staging Putaway Case Picking Palletizing Loading Object Level Handling Unit Handling Unit Handling Unit Handling Unit Handling Unit Handling Unit Delivery Auto-ID Support RFID Activity Unload Register Register Pick/Verify Pack/Verify Write Pal. Tag Load Coding EPC/GTIN SSCC EPC/GTIN SSCC SSCC EPC/GTIN EPC/GTIN SSCC EPC/GTIN SSCC EPC/GTIN System Activity Goods Receipt TO Creation Putaway Confirm. Picking Confirm. Packing Instruct. Create HU Goods Issue Send ASN Page 28 / 18

29 History of AII at SAP Overview Details Core Services Integration Services Sample Process Supported processes Integration of SAP EM Page 29 / 18

30 2 5$ Page 30 / 18

31 * ; 2 5$' SAP R/3 SAP XI SAP AutoID RFID Device Create Outbound delivery Confirm Delivery Item Pick System Transfers Delivery Data System Stores Delivery Data Supervisor User Creates EPC for HU and SU System Updates Delivery with EPC HU s System Transfers EPC Data with Delivery Reference System Checks Data Worker Packs and Scans Delivery Items System Transfers SU Data with EPC HU Data System Stores Delivery Data Load Item and Scan EPC Data System Transfers Actual Pallet and Sales Unit Data System Transfers Actual Pallet and Sales Unit Data System Checks Data System Sets Delivery Status to Loaded and Updates Delivery System Posts Goods Issue Page 31 / 18

32 5$ Page 32 / 18

33 <$ $ < %!$& %& SAP R/3 SAP XI SAP Auto-ID RFID Gate Create Inbound Delivery - (MB1C) Change Delivery Details - (VL32N) 1. Packing in Case 2. Packing in Pallet 3. Putaway IDOC is sent from R/3 to AIN (Action Type AUBO) Check generated IDOC (WE05) Status of Delivery is completed IDOC is sent from AIN to R/3 (Action Type AUBO) Check AIN Status of Delivery Unload pallet with traffic generator Page 33 / 18

34 <&" $ < %!$& %& SAP R/3 SAP XI SAP Auto-ID Mobil Device Status of Delivery is completed IDOC is sent from R/3 to AIN (Action Type AUU1) Check Status of Delivery (VL32N) Check AIN Status of Delivery Unpack Delivery with Mobile Device IDOC is sent from AIN to R/3 (Action Type AUU1) Delivery is unpacked Page 34 / 18

35 =5 $ 5% 1% SCEM XI AII Version SCM 4.1 available June 21, mysap SCM 4.1 Ramp-up, Version XI 3.0 available March 31, Netweaver 2004 Ramp-up SAP Lab in Philly, on March 18 Pilot availability on May 4 Version AII 2.0 (available June 21, mysap ERP Ramp-up SP01, available about July 15 Add-ons for SAP R/3 46C and R/3 47, June 21 SAP Portal and SAP BW are not in the scope of the AII 2.0 Page 35 / 18

36 ' In AII 2.0 SP 0: when using an R/3 backend, you have the possibility of archiving completed documents (status = 07). In the Archiving section of the UI, you define which action types are to be archived and also after how much time (i.e.: Residence period) should they be archived. This archiving procedure is triggered via a scheduled activity (which already exists) that you configure in the Activity section of the UI. You define when the activity is to start archiving, at what frequency and for how many times. Then, these archived documents get the status 08 for archived. You then have another scheduled activity (which already exists) that is responsible for deleting all archived documents from the AII database. In AII SP01: If the customer does not have a R/3 backend system, then there is an archiving mechanism in the J2EE engine, but this will be available in AII 2.0 SP1. Page 36 / 18

37 History of AII at SAP Overview Details Core Services Integration Services Sample Process Integration of SAP EM Page 37 / 18

38 , >& SAP EM is an Award Winning Solution Winner of the 2003 Frost&Sullivan Market Engineering Award for Product Innovation in the European SCEM Market Supply Chain Event Management (SAP EM) monitors the execution of supply chain processes the communication compliance of partners Supply Chain Event Management (SAP EM) can control the visibility process by using rule based reactions the business process by directly interfacing with planning and scheduling systems In case of delays or deviations from plans, SAP EM can alert staff members or initiate other activities determine how the delay will impact schedules Page 38 / 18

39 , Event Manager is Event Manager is not A supply chain monitoring tool that enables end-to-end visibility, decision support and performance management across the entire supply chain A bridge between the execution and the planning domains that monitors potential impacts between those relationships An operational system although it may take information from operational systems A planning system although it constantly monitors against a plan Page 39 / 18

40 , & %&?$& $ &$ % actual events event 1 event 2 event 3 event 1 Supply chain object event 2 event 4 Alerts expected events Learn Control 1= Simulate Plan/Schedule Partner Performance Collaborate % $9 Page 40 / 18

41 , $ %&% % %, Inter-company collection of visibility data Monitoring of complete, distributed processes Enabling of exception-based Process Monitoring Central instance for whole company % Lean, stand-alone solution Local implementation for local handling of RFID data Pre-filtering and consolidation of high-volume RFID data Direct feedback to equipment and workforce ' $ %&% Both components integrate with any back-end system Auto-ID Infrastructure is closer to the physical process SAP EM is closer to the IT-Implementation of the process Both components can be tightly connected in business processes Page 41 / 18

42 2$% =5 $ % < PML Request Visibility Portal SAP Backend SAP Event Manager SAP Auto-ID Infrastructure Drive business process out of SAP backend Order entry Start Production Track and trace and query done on SAP EM Use as EPCIS HU tagging Tag readings processed by SAP Auto-ID Infrastructure Item sold Tag deactivted SO SO entry entry Oper. 1 Oper. 2 Oper. n Production Packaging Packaging WH WH Shipping Shipping Shop Shop Activities Activities Page 42 / 18

43 %!$&$ ' EM AII XI SAPR/3 Devices Confirmations Actual Reads Expected Expected Actions Actions Resulting Activities Application /Message Handlers Inbound Delivery Outbound Delivery HU... Page 43 / 18

44 5, ; 2 5$ AII XI R/3 EM Create Outbound Delivery Create Event Handler for Outbound Delivery Perform the picking Expected Action Pack created Delivery: Picking Status Completed Event Message Picking for EH Delivery Verify actual RFID read with expected read at packing door reader Create Event Handler for Handling Unit Expected Action Load created Create Handling Unit E-Msg Packing send to EH HU + EH Delivery Verify actual RFID read with expected read at Load door reader E-Msg Loading to EH HU Verify if Delivery complete Book Goods issue E-Msg Goods Issue to EH Delivery Page 44 / 18