SAP Auto-ID Infrastructure 2.

0 (AII)

Page 1 / 18
 “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
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
 “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
 How do you plan to use Auto-ID data?

Standalone
application with
minimal 3%
integration

Stand alone
application with
24%
middleware
configuration

Integrated with
71%
existing ERP

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

Source: EPC Forum Survey Results, 2003

Page 5 / 18
! " # $ % %

Real world aware Business Processes represented by

Enterprise Applications (ERP, SCM, CRM, PLM, SRM ...)
SAP
SAP SAP SAP 3rd Party
R/3 4.6C/4.7, ...
ERP 1.0 SCEM BW1 APO1 WMS1

SAP Auto-ID Infrastructure

Environmental
active tag Sensors passive tags

Physical World represented by Smart Objects

1not supported yet

Page 6 / 18
 & '
&

Role-based
User Interfaces

Composite
Business
Processes Service request Availability Trigger Assembly Goods receipt

Operational
Backbone

Page 7 / 18
 ( $ & ) * ' %

Role-based
User Interfaces

Composite
Business
Processes Service request Availability Trigger Assembly Goods receipt

Operational
Backbone

“Intelligent
Stuff”

Page 8 / 18
 &* ' &%

AutoID Infrastructure ( ) and beyond

Read / Write tags Auto-ID networks

Technology

Rule processor Configurable transactions

AutoID support Process control
Visibility Voice support
Material Flow Computing
Wal*Mart Own Efficiency
Today Interoperability Q2/2004 Improved Operations / ROI
Future

WM: Pick / Putaway / Consolidate

Pallet / Carton level Manufacturing
Content

HU build / Packing Item level tagging

Ship / Receive Smart shelves
Track&Trace (EM) AutoID driven CPFR
Processes and Scenarios

Page 9 / 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 10 / 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 11 / 18
 “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
 1

The illustration below shows an overview of SAP RFID landscape:

Reader Device SAP Auto-ID SAP

Controller Infrastructure (AII) Exchange
SAP EM
RFID Infrastructure
(XI) (optional)
Tags

SAP R/3
!! 6, !7 , ! 6, !

Auto-ID Cockpit Backend

(Web User Interface)

Traffic Generator

Page 13 / 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 14 / 18
 %% $ $! $ & 7

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

XI

Plant 1 DC 1

AII AII

Device Controller DC Device Controller DC

Gate 1 Gate 2 Gate 3 Gate 4

Reader/ Reader/ Reader/ Reader/ Reader/ Reader/

Interrogator Interrogator Interrogator Interrogator Interrogator Interrogator

Sensor Sensor Sensor Sensor Sensor Sensor

Not availablePage
1 yet 15 / 18
# 5 $ 8

Expected
Expected Events
Events

"Goods in" scenario

Filtering
Filtering
Filtered read / write
Buffering
Buffering
Data buffer
Smoothing
Smoothing

Save read "UID"

Data
Data abstraction
abstraction
Read "Address, Len"
Reader
Reader abstraction
abstraction
Via Ethernet
Tag
Tag abstraction
abstraction

Read "Tag Pages"

Labels

Page 16 / 18
 & "

Customer Without SAP R/3 With SAP R/3 4.6C and With SAP ERP 2004 /
RFID Landscape SAP R/3 4.7 Business Suite
Solution SAP NetWeaver RFID enabled SCM mySAP ERP / Business
Offering Solution Package Suite

Package Contains SAP Auto-ID SAP Auto-ID SAP Auto-ID

Infrastructure and Infrastructure and Infrastructure and
Content Content Content
SAP NetWeaver SAP R/3 – Auto-ID SAP Event Management1
Adapter
SAP Event Management
SAP NetWeaver

Package Requires SAP R/3 4.6c or SAP R/3 mySAP ERP 2004 or
4.7 higher

Integration Project based via SAP Use Auto ID - R/3 Process based “Out of
GCDS or Partner Integrator Toolbox + the Box” Integration
Project SAP GCDS
Implementation SAP Consulting or SAP Consulting or SAP Consulting or
Project Partner Partner Partner

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

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

Page 18 / 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 19 / 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.

SAP Auto-ID Infrastructure (AII)

Core Services

Integration Services
SAP
Auto-ID Cockpit Exchange
Device (Web User Interface) Infrastructure
Controller (XI)

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

Page 21 / 18
 ' 3

These are the core services’ sub-components:

Action and Process Management: Core Services

Allows to define specific action handlers : , %
to manage required processes interacting
Action Handling
with the various parties i.e. devices, Event
humans, systems. It includes action Rule Engine Message
handling, rule engine and message Dispatcher
dispatching. Event Queue/s

: $% , %
Configuration & Admin. Management:
Device/User Component Backend
It includes support for the definition of
devices and their operational staff,
259 , %
backend systems and other Auto-ID
Expected Current
Infrastructures. In addition, it controls the Trace
Action State
internal component configuration allowing
for flexible way to enabling and disabling ! , , %
of a component. 259Location , %
Product

Page 22 / 18
 ' .

These are the core services’ sub-components:

Object Data Management: Core Services

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

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

Page 24 / 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 25 / 18
 “History” of AII at SAP
Overview
Details
Core Services
Integration Services
Sample Process
SAP Auto-ID Cockpit

Page 26 / 18
 %& $ %&

SAP Auto-ID Infrastructure (AII)

Condition
Device Message Message
and Rule Activities XI
Controller Receiver Parser Activities
Processor Activities

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
 # $

Location Gate Staging Area Warehouse Staging Area Gate

Activity Unloading Staging Putaway Case Picking Palletizing Loading

Object Handling Handling Handling Handling Handling Handling Unit

Level Unit Unit Unit Unit Unit Delivery

Auto-ID
Support

RFID Pack/Verify
Unload Register Register Pick/Verify Load
Activity Write Pal. Tag
EPC/GTIN EPC/GTIN SSCC SSCC SSCC
Coding EPC/GTIN
SSCC SSCC EPC/GTIN EPC/GTIN EPC/GTIN
System Goods TO Putaway Picking Packing Goods Issue
Activity Receipt Creation Confirm. Confirm. Instruct. Send ASN
Create HU

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

Page 29 / 18
2 5 $

Page 30 / 18
 * ;2 5 $ '
SAP R/3 SAP XI SAP AutoID RFID Device

Create Outbound
delivery

Supervisor User
Confirm Delivery System Transfers System Stores
Creates EPC for HU
Item Pick Delivery Data Delivery Data
and SU

System Updates System Transfers

Worker Packs and
Delivery with EPC EPC Data with System Checks Data
Scans Delivery Items
HU‘s Delivery Reference

System Transfers
System Stores Load Item and Scan
SU Data with EPC
Delivery Data EPC Data
HU Data

System Transfers System Transfers

Actual Pallet and Actual Pallet and System Checks Data
Sales Unit Data Sales Unit Data

System Sets
Delivery Status to
Loaded and
Updates Delivery

System Posts
Goods Issue

Page 31 / 18
 5 $

Page 32 / 18
< $ $ <
% ! $ & %&

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 Check AIN Status of Unload pallet with

IDOC (WE05) Delivery traffic generator

IDOC is sent from

AIN to R/3
(Action Type AUBO)

Status of Delivery
is completed

Page 33 / 18
< & " $ <

% ! $ & %&

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 AIN Status of Unpack Delivery

Check Status of
Delivery with Mobile Device
Delivery (VL32N)

IDOC is sent from

AIN to R/3
(Action Type AUU1)

Delivery is
unpacked

Page 34 / 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 35 / 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 36 / 18
 “History” of AII at SAP
Overview
Details
Core Services
Integration Services
Sample Process
Integration of SAP EM

Page 37 / 18
 , > &
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
 ,

Event Manager is … Event Manager is not …

A supply chain monitoring tool that An operational system … although

enables end-to-end visibility, it may take information from
decision support and performance operational systems
management across the entire
supply chain
A planning system … although it
A bridge between the execution and constantly monitors against a plan
the planning domains that monitors
potential impacts between those
relationships

Page 39 / 18
 , & %& ? $ & $
& $
%

actual events

event 1 event 2 event 3

Supply chain object

event 1 event 2 event 4 Alerts

expected events

1=
Control
Simulate
Plan/Schedule
Learn

Collaborate
Partner Performance

% $9
Page 40 / 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 41 / 18
 2 $ % = 5 $ % <

PML Request

Visibility
Portal SAP
SAP Event SAP Auto-ID
Backend Manager Infrastructure

Drive business
process out of
SAP backend

Track and trace and query

done on SAP EM Tag readings
Use as EPCIS processed by SAP
Auto-ID Infrastructure
Order Start HU Item sold
entry Production tagging Tag deactivted

Oper. 1 Oper. 2 Oper. n

Shop
Shop
SO
SOentry
entry Production Packaging
Packaging WH
WH Shipping
Shipping Activities
Activities

Page 42 / 18
 % ! $ & $ '

EM

AII XI SAPR/3
Inbound
Devices Delivery

Application /Message
Confirmations
Outbound

Handlers
Delivery
Actual Reads
Expected
Expected
Actions
Actions
HU

Resulting .....
Activities

Page 43 / 18
 5 , ; 2 5 $
AII XI R/3 EM

Create Event Handler for

Create Outbound Delivery
Outbound Delivery

Perform the picking

Event Message
Expected Action Delivery: Picking Status
„Picking“ for EH
“Pack” created “Completed”
Delivery

Verify actual RFID read

Create Event Handler
with expected read at
for Handling Unit
packing door reader

Expected Action
Create Handling Unit
“Load” created
E-Msg “Packing” send
to EH HU + EH Delivery

Verify actual RFID read

E-Msg “Loading” to EH
with expected read at
HU
Load door reader

Verify if Delivery E-Msg “Goods Issue”

Book “Goods issue”
complete to EH Delivery

Page 44 / 18