SAP RFID technology

Page 1 / 18

��

SAP Auto-ID Infrastructure 2.0 (AII)

Page 2 / 18

Supported processes

Integration Services

Core Services

Details

Why does SAP get into the RFID world?

“History” of AII at SAP

Sample Process

Integration of SAP EM

Page 3 / 18

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 4 / 18

SAP Auto-ID Cockpit


Core Services

Details



Sample Process

Page 5 / 18

��

71%

24%

3%

0% 10% 20% 30% 40% 50% 60% 70% 80%

Integrated withexisting ERP

Stand aloneapplication with

middlewareconfiguration

Standalone application with

minimal integration

Source: EPC Forum Survey Results, 2003

How do you plan to use Auto-ID data?

Page 6 / 18

!� "� � � ��# ��$�� % �� % �

Physical World represented by Smart Objects

Real world aware Business Processes represented byEnterprise Applications (ERP, SCM, CRM, PLM, SRM ...)

active tag EnvironmentalSensors passive tags

SAP R/3 4.6C/4.7,

ERP 1.0

3rd PartyWMS1

SAPSCEM

SAPBW1 ...

SAP Auto-ID Infrastructure

SAPAPO1

1not supported yet

Page 7 / 18

� �� &��'�� &��

AvailabilityAvailability Goods receiptGoods receiptService requestService request Trigger AssemblyTrigger Assembly

Composite BusinessProcesses

Operational Backbone

Role-basedUser Interfaces

Page 8 / 18

( ��$�&��)* �� '�� % �

AvailabilityAvailability Goods receiptGoods receiptService requestService request Trigger AssemblyTrigger Assembly

Composite BusinessProcesses

Operational Backbone

“IntelligentStuff”

Role-basedUser Interfaces

Page 9 / 18

�&*�� '��&% ��

Read / Write tagsRule processorAutoID supportVisibility

Pallet / Carton levelHU build / PackingShip / ReceiveTrack&Trace (EM)

Q2/2004Today

Auto-ID networksConfigurable transactionsProcess controlVoice supportMaterial Flow Computing

WM: Pick / Putaway / ConsolidateManufacturingItem level taggingSmart shelvesAutoID driven CPFR

Future

Tech

nolo

gyC

onte

nt

Processes and Scenarios

AutoID Infrastructure (��) and beyond

Wal*MartInteroperability

Own EfficiencyImproved Operations / ROI

Page 10 / 18

�% &��*��# ��+,��-��% �

.//0

Wal*Mart expects its US-based 12��3// 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 11 / 18

,�� $��&�� $ 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 12 / 18

SAP Auto-ID Cockpit


Core Services

SAP RFID technology



Sample Process

Page 13 / 18

� The illustration below shows an overview of SAP RFID landscape:

��1��

DeviceController

RFIDTags

Reader

Traffic Generator

Backend

SAP Exchange

Infrastructure (XI)

SAP R/3

SAP Auto-ID Infrastructure (AII)

Auto-ID Cockpit(Web User Interface)

��

6,! ��6,!7�,!!!�

SAP EM(optional)

Page 14 / 18

��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 15 / 18

��% % $$ !� $��&�7��

Reader/Interrogator

Reader/Interrogator

Reader/Interrogator

Reader/Interrogator

Reader/Interrogator

Plant 1 DC 1

Device ControllerGate 1

Device ControllerGate 3

DCGate 2

Reader/Interrogator

Sensor Sensor Sensor Sensor Sensor Sensor

DC Gate 4

AII AII

XI

R/3, ERP EM BW1 SCM1 WM1 ...1

1Not available yet

Page 16 / 18

# �� 5 �� $�8

SmoothingSmoothing

Data abstractionData abstraction

Reader abstractionReader abstraction

Tag abstractionTag abstraction

BufferingBuffering

FilteringFiltering

Expected EventsExpected Events

Labels

"Goods in" scenario

Filtered read / write

Data buffer

Save read "UID"

Read "Address, Len"

Via Ethernet

Read "Tag Pages"

Page 17 / 18

mySAP ERP 2004 or higher

SAP R/3 4.6c or SAP R/3 4.7

Package Requires

SAP Consulting or Partner



ImplementationProject

With SAP ERP 2004 / Business Suite

With SAP R/3 4.6C and SAP R/3 4.7

Without SAP R/3CustomerRFID Landscape

Process based “Out of the Box” Integration

Use Auto ID - R/3 Integrator Toolbox + Project SAP GCDS

Project based via SAP GCDS or Partner

Integration

SAP Auto-IDInfrastructure and Content

SAP Event Management1

SAP Auto-IDInfrastructure and Content

SAP R/3 – Auto-ID Adapter

SAP Event Management

SAP NetWeaver

SAP Auto-ID Infrastructure and Content

SAP NetWeaver

Package Contains

mySAP ERP / Business Suite

RFID enabled SCM Solution Package

SAP NetWeaverSolutionOffering

1 mySAP ERP 2004 standard delivery does not include SAP Event Management (SAP SCM 4.1)

�� &��"��

Page 18 / 18

SAP Auto-ID Cockpit


Core Services

Details

Overview


Sample Process

Page 19 / 18

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 20 / 18

� 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.

��

DeviceController

SAP Exchange

Infrastructure (XI)

Core Services

Auto-ID Cockpit(Web User Interface)



Page 21 / 18

SAP Auto-ID Cockpit


Core Services

Details

Overview


Sample Process

Page 22 / 18

259��,� ��%

ExpectedAction

CurrentState Trace

259��,� ��%

!� �,��,� ��%

Location Product

� �� :��$% � �,� ��%

Device/User Component Backend

�� :��,� ��%

Action Handling

Rule Engine

Event Queue/s

EventMessage

Dispatcher

� 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.

�� '��3�

Core Services

These are the core services’ sub-components:

Page 23 / 18

�� '��.�

� 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.

These are the core services’ sub-components:

259��,� ��%

ExpectedAction

CurrentState Trace

259��,� ��%

!� �,��,� ��%

Location Product

� �� :��$% � �,� ��%

Device/User Component Backend

�� :��,� ��%

Action Handling

Rule Engine

Event Queue/s

EventMessage

Dispatcher

Core Services

Page 24 / 18

SAP Auto-ID Cockpit


Core Services

Details

Overview


Sample Process

Page 25 / 18

�� '��

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 26 / 18

SAP Auto-ID Cockpit


Core Services

Details

Overview


Sample Process

Page 27 / 18

� 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.

MessageReceiver

MessageParser

Conditionand Rule

Processor ActivitiesActivitiesActivities


DeviceController

DB

��% &��$��% &��

XI

Page 28 / 18

# �� $��

ObjectLevel

Auto-ID Support

RFID Activity

Coding

System Activity

Activity Palletizing

HandlingUnit

��

SSCCEPC/GTIN

Pack/VerifyWrite Pal. Tag

PackingInstruct.

Create HU

Loading

Handling UnitDelivery

��

Load

SSCCEPC/GTIN

Goods IssueSend ASN

WarehouseStaging Area GateLocation Gate Staging Area

Unloading

EPC/GTINSSCC

Unload

HandlingUnit

GoodsReceipt

��

Putaway

HandlingUnit

SSCCEPC/GTIN

Register

PutawayConfirm.

��

Case Picking

HandlingUnit

Pick/Verify

EPC/GTIN

PickingConfirm.

��

Staging

HandlingUnit

EPC/GTINSSCC

Register

TOCreation

��

Page 29 / 18

Supported processes


Core Services

Details

Overview


Sample Process


Page 30 / 18

2�5�� $��

Page 31 / 18

��* �; 2�5�� $��'��

SAP XI RFID DeviceSAP AutoIDSAP R/3

Create Outbounddelivery

Confirm DeliveryItem Pick

System TransfersDelivery Data

System StoresDelivery Data

Supervisor UserCreates EPC for HU

and SU

System Checks DataSystem Transfers

EPC Data withDelivery Reference

System UpdatesDelivery with EPC

HU‘s

System TransfersSU Data with EPC

HU Data

Worker Packs andScans Delivery Items

Load Item and ScanEPC Data

System TransfersActual Pallet andSales Unit Data

System TransfersActual Pallet andSales Unit Data

System StoresDelivery Data

System Checks Data

System SetsDelivery Status to

Loaded andUpdates Delivery

System PostsGoods Issue

Page 32 / 18

� 5�� $

Page 33 / 18

< ��$� � ��$ �<

��% �!� $��&�� % &� �

SAP R/3 SAP XI SAP Auto-ID RFID Gate

Create InboundDelivery - (MB1C)

Change DeliveryDetails - (VL32N)

1. Packing in Case2. Packing in Pallet

3. Putaway

IDOC is sent fromR/3 to AIN

(Action Type AUBO)

Unload pallet withtraffic generator

IDOC is sent fromAIN to R/3

(Action Type AUBO)

Status of Deliveryis completed

Check generatedIDOC (WE05)

Check AIN Status ofDelivery

Page 34 / 18

< &��"� � ��$ �<

SAP R/3 SAP XI SAP Auto-ID Mobil Device

IDOC is sent fromR/3 to AIN

(Action Type AUU1)

IDOC is sent fromAIN to R/3

(Action Type AUU1)

Check AIN Status ofDelivery

Status of Deliveryis completed

Unpack Deliverywith Mobile Device

Check Status ofDelivery (VL32N)

Delivery isunpacked

��% �!� $��&�� % &� �

Page 35 / 18

��=��5�� $�� 5�% �1�% ��

SCEM

� Version SCM 4.1 available June 21, mySAP SCM 4.1 Ramp-up,

XI

� Version XI 3.0 available March 31, Netweaver 2004 Ramp-up

AII

� 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 36 / 18

��'� �

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 37 / 18



Core Services

Details

Overview


Sample Process

Page 38 / 18

��,��>�� &��

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

SAP EM is anAward Winning Solution

Winner of the2003 Frost&Sullivan

Market Engineering Awardfor Product Innovation

in the European SCEM Market

Page 39 / 18

Event Manager is …

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 monitorspotential impacts between those relationships

Event Manager is not …

An operational system … although it may take information from operational systems

A planning system … although it constantly monitors against a plan

��,��,��

Page 40 / 18

��, ��&�� % &� �� ?��$�&�� $��&� $

��

�$9��

Learn

Alerts

% � ��

Partner PerformanceCollaborate

% ��

��1�=��1�=�Control

Supply chain object

event 2 event 4

actual events

expected events

event 3

event 1

event 2event 1

Simulate

Plan/Schedule

Page 41 / 18

��% �� ,� 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 42 / 18

2�$��% �=��5�� $��% �<�

Oper. 1 Oper. 2 Oper. n

SO entrySO entry Production

Orderentry

StartProduction

SAP Backend

SAP Event

ManagerSAP Auto-ID Infrastructure

HUtagging

PackagingPackaging WHWH ShippingShipping

Item soldTag deactivted

ShopActivities

ShopActivities

��

VisibilityPortal

Drive businessprocess out of SAP backend

Tag readings processed by SAP

Auto-ID Infrastructure

Track and trace and query done on SAP EMUse as EPCIS

PML Request

Page 43 / 18

��% �!� $��&�� $�� '��

XI

App

licat

ion

/Mes

sage

H

andl

ers

SAPR/3

Devices

AII

ExpectedActions

ExpectedActions

Confirmations

EM

InboundDelivery

OutboundDelivery

HU

.....

Actual Reads

ResultingActivities

Page 44 / 18

��5��, �; �� 2�5�� $�

AII

Expected Action “Pack” created

Expected Action “Load” created

Verify actual RFID read with expected read at packing door reader

XI EM

Event Message„Picking“ for EH

Delivery

E-Msg “Loading” to EH HU

Create Event Handler for Outbound Delivery

R/3

Create Outbound Delivery

Perform the picking

Delivery: Picking Status “Completed”

Create Handling Unit

Book “Goods issue”

Create Event Handlerfor Handling Unit

E-Msg “Packing” send to EH HU + EH Delivery

E-Msg “Goods Issue” to EH Delivery

Verify actual RFID read with expected read at

Load door reader

Verify if Delivery complete

Documents

SAP RFID technology