Mais conteúdo relacionado Semelhante a I International Workshop RFID and IoT - Dia 19 - Delivering Value through GS1 EPCglobal Standards - Wilson José da Cruz Silva - GS1 (20) I International Workshop RFID and IoT - Dia 19 - Delivering Value through GS1 EPCglobal Standards - Wilson José da Cruz Silva - GS11. Delivering Value through
GS1 EPCglobal Standards
I International Workshop on RFID
and IoT – CPqD
Campinas – 19/06/2013
Wilson José da Cruz Silva
2. © 2012 GS1 Brasil
GS1 in a nutshell
are not-for-profit organization
are neutral from business partners
are user-driven and governed
serve all companies, from multinationals to
SMEs
are a platform for collaborative agreements
between business partners
We
3. © 2012 GS1 Brasil
111 Member Organizations.
150 Countries served.
Local services, global reach.
Countries
with a GS1
Member
Organisation
Countries served
on a direct basis
from GS1 Global
Office (Brussels)
GS1 Member Organizations
4. © 2012 GS1 Brasil
Awareness
Education
Business
Cases
Partner
Selection
Experiment
Implement
Homepage, Interest Groups, EPC/RFID Events,
Newsletter
EPC/RFID Training, Access to Standards
& Publications
Case Studies, Advisoring, Public Policy Guidelines,
ROI Calculator
EPC/RFID Certified Suppliers Database
EPC/RFID Accredited Test Centers
Electronic Product Code (EPC), EPC Network
GS1 EPCglobal Products
and Services
(global/local)
Learn
Evaluate
& Plan
Adopt
5. © 2012 GS1 Brasil
GS1 EPCglobal Standards
Architecture
7. © 2012 GS1 Brasil
EPCglobal Transponder Classes
Backwardscompatibility
Class 1
• Re-writable, passive transponders
• “KILL” function
• Password protection
• Optional user memory
Class 2
• Enlarged memory
• Authenticated access
Class 3
• Semi-passive transponders with on-board battery
• Integrated sensors
Class 4
• Active transponders
• Tag-to-tag communication (“internet of things”)
• Possibility of ad-hoc networks
9. © 2012 GS1 Brasil
GS1/EPC Numbering System
central allocation by GS1 Member Organisations (MOs)
GS1 Company Prefix (GCP)
encoding on
EPC-Transponder
encoding in
GS1-Barcode
For self-generation of unique identification numbers . . .
10. © 2012 GS1 Brasil
EPCglobal Tag Data Standard (TDS)
EPC Identification based on GS1 Keys
SGTIN Serialized Global Trade Item Number
retail and standard trade units, individual parts
SSCC Serial Shipping Container Code
logistic units
(S)GLN Global Location Number (+ extension)
exact locations (loading docks, production lines, etc.)
GRAI Global Returnable Asset Identifier
Returnable Transport Items (RTIs)
GIAI Global Individual Asset Identifier
fixed assets (machines, tools, equipment, etc)
GSRN Global Service Relation Number
Service relationships (event tickets, patient IDs)
GDTI Global Document Type Identifier
Physical and virtual documents (incl. electronic files)
11. © 2012 GS1 Brasil
Header
GS1 Company
Prefix
Object Class Serial Number
8 bits 20-40 bits 24-4 bits 38 bits
Partition
3 bits
Filter
3 bits
0011 0000 4012345
(decimal)
012345
(decimal)
123456789123
(decimal)
5
(decimal)
001
EPC Composition
Length
Value
identifies the structure of the EPC
(z.B., SGTIN-96, SSCC-96, GRAI-170, usw.)
allows the reader to pre-sort EPC’s at item, case and pallet level
(Retail Consumer Trade Item, Logistical / Shipping Unit, etc.)
indicates length of GS1 Company Prefix
(GCP ist 6, 7, 8, 9, 10, 11 or 12 Ziffern lang)
identifies issuing entity for subsequent parts of the EPC
(eg., Sprockets AG, Friedrichshafener Str. 4711, 50823 Köln)
identifies specific type of item, location, asset or document
(Item Reference / Location Reference / Asset Type / Document Type)
serialisation to distinguish between individuals of same type
Header
Filter
Partition
GS1 Company
Prefix
Object Class
Serial Number
12. © 2012 GS1 Brasil
Indicator DigitGTIN +
Serial
Number
GS1 Company
Prefix
Item
Reference
Check Digit Serial Number
0 4012345 12345 6 123456789123
as EPC (96-bit SGTIN):
Header
GS1 Company
Prefix
Object Class Serial Number
8 bits 20-40 bits 24-4 bits 38 bits
Partition
3 bits
Filter
3 bits
as GS1-128 Barcode:
0011 0000 4012345
(decimal)
012345
(decimal)
123456789123
(decimal)
5
(decimal)
000
Interoperability GS1 EPC
Serialized Global Trade Item Number (SGTIN)
length
value
(01)04012345123456(21)123456789123
checkdigit
14. © 2012 GS1 Brasil
Uniform Resource Identifier (URI) encoding
URI Forms for Pure Identities
URI forms for pure identities
contain only the EPC fields that distinguish one object from another
a different URN namespace is allocated for each pure identity type
urn:epc:id:sgtin:CompanyPrefix.ItemReference.SerialNumber
urn:epc:id:sscc:CompanyPrefix.SerialReference
urn:epc:id:sgln:CompanyPrefix.LocationReference.ExtensionComponent
urn:epc:id:grai:CompanyPrefix.AssetType.SerialNumber
urn:epc:id:giai:CompanyPrefix.IndividualAssetReference
urn:epc:id:gsrn:CompanyPrefix.ServiceReference
urn:epc:id:gdti:CompanyPrefix.DocumentType.SerialNumber
15. © 2012 GS1 Brasil
URI encoding for pure identity
urn:epc:id:sgtin:4022536.042458.123456789123
Serialised Global Trade Item Number (SGTIN)
URI encoding for EPC tags
urn:epc:tag:sgtin-96:1.4022536.042458.123456789123
SGTIN for 96-bit EPC tag filter value for “Retail Consumer Trade Item”
URI encoding for EPC patterns (range of EPCs)
urn:epc:pat:sgtin-96:1.4022536.[042450-042500].*
range of EPC tags with an item reference between 042450 and 042500
URI encodings
17. © 2012 GS1 Brasil
“Kill” password (optional)
Access password (optional)
supplementary information
supports GS1 Application Identifiers (AIs)
as well as ISO Data Identifiers (DIs)
issued by chip manufacturer
not for product identification purposes
extended TID (XTID) offers optional serialization
Cyclic Redundancy Check-16
Protocol Control (PC) Bits inkl. “Hazmats” Bit
Electronic Product Code
Extended Protocol Control Bits (XPC)
EPC Gen 2 Memory Banks
MB 11: User Memory
11 User
10 TID
01 EPC
00 Reserved
Header GCP Object Class Serial NumberPartitionFilter
18. © 2012 GS1 Brasil
data content format*
01 GTIN n2 + n14
400 Customer’s Purchase Order Number n3 + an..30
00 SSCC (Serial Shipping Container Code) n2 + n18
10 Chargennummer n2 + an..20
11 Production Date (YYMMDD) n2 + n6
13 Packaging Date (YYMMDD) n2 + n6
15 Best Before Date (YYMMDD) n2 + n6
17 Verfallsdatum (JJMMTT) n2 + n6
20 Product Variant n2 + n2
21 Serial Number n2 + an..20
30 Count of Items n2 + n..8
310** Net Weight in Kilograms n4 + n6
314** Area in square metres n4 + n6
315** Net Volume in litres n4 + n6
410 “Ship To” GLN of the addressee n3 + n13
AI
421 “Ship To” Postal Code with 3-digit ISO country code n3 + n3 + an..9
Extract from the list of currently
standardised
GS1 Application Identifiers (AIs)
10 Batch or Lot Number n2 + an..20
17 Expiration Date (YYMMDD) n2 + n6
20. © 2012 GS1 Brasil
WHY
•Business Step (e.g., Pick-Up)
•Disposition (e.g., In Transit)
WHAT
Individual object instances
(e.g. SGTIN, SSCC, GRAI...)
WHERE
•Read point (SGLN)
•Business location (SGLN)
WHEN
Time stamp of the event
(date + time + time zone)
...recorded as an EPCIS Event
EPCIS Events at supply chain read points
21. © 2012 GS1 Brasil
Four Core EPCIS Event Types
Object Events
• Observation of EPCs
SGTINs are moved into storage
Aggregation Events
• Physical association of EPCs with parent EPC
SGTINs are picked and assigned to an SSCC
Quantity Events
• Inventory of an object class (item reference)
a total of ___ of GTIN 56789 are currently in storage
Transaction Events
• Link one or more EPCs to a business transaction
SGTINs corresponding to DESADV 4711 are shipped
22. © 2012 GS1 Brasil
storage commssioning shipping
Event
Event
Event Event
EPCIS Repositories
EPCIS Capture of supply chain events
production
TransactionEvent
WHAT: SSCC 4001356.5900000817
GTIN 4026800.010421.101
GTIN 4026800.010421.102
bizTransaction: desadv 471150825
WHERE: SGLN 4012345.00050.0
WHEN: 23.10.2009 14:47:00 UTC+1
ObjectEvent
WHAT: SGTIN 4026800.010421.101
SGTIN 4026800.010421.102
WHERE: SGLN 4012345.01010.0
WHEN: 22.10.2009 09:25:00 UTC+1
WHY: packing
QuantityEvent
WHAT: GTIN 4026800.010421
QTY: 5
WHERE: SGLN 4012345.00031.0
WHEN: 22.10.2009 11:20:00 UTC+1
AggregationEvent
WHAT: SSCC 4001356.5900000817
SGTIN 4026800.010421.101
SGTIN 4026800.010421.102
WHERE: SGLN 4012345.00040.0
WHEN: 23.10.2009 13:40:00 UTC+1
WHY: commissioning
23. © 2012 GS1 Brasil
What?
When?
Where?
Why?
Example: Aggregation Event
<AggregationEvent>
<eventTime>2009-10-23T12:27:11Z</eventTime>
<recordTime>2009-10-23T12:27:11Z</recordTime>
<eventTimeZoneOffset>+01:00</eventTimeZoneOffset>
<parentID>urn:epc:id:sscc:4001356.5900000817</parentID>
<childEPCs>
<epc>urn:epc:id:sgtin:4026800.10421.101</epc>
<epc>urn:epc:id:sgtin:4026800.10421.102</epc>
</childEPCs>
<action>ADD</action>
<bizStep>urn:epcglobal:cbv:bizstep:commissioning</bizStep>
<disposition>urn:epcglobal:cbv:disp:core:active</disposition>
<readPoint>
<id>urn:epc:id:sgln:4012345.01020.0</id>
</readPoint>
<bizLocation>
<id>urn:epc:id:sgln:4012345.00020.0</id>
</bizLocation>
</AggregationEvent>
24. © 2012 GS1 Brasil
EPCIS Read Point and Business
Location
• Read Points are often doorways;
Business Locations are often rooms:
Business Location: Store #23
Business Loc: Store #23 Back Room Business Loc: Store #23 Front Room
Read Point:
Store #23 Dock #1
Read Point:
Store #23 Dock #2
Read Point:
Store #23 Interior Door #1
Product entering sales floor:
Read point = Store #23 Interior Door #1
Business location = Store #23 Front Room
Product returning to storage:
Read point = Store #23 Interior Door #1
Business location = Store #23 Back Room
25. © 2012 GS1 Brasil
EPCIS Business Step
• Business Step - specifies the business context
of an event: What business process step was
taking place when the event was captured?
• A Business Step answers the question: “What
business process was being executed during this
event?”
Example: “Receiving”
26. © 2012 GS1 Brasil
CBV Business Steps
Core Business Vocabulary
accepting
arriving
assembling
collecting
commissioning
decommissioning
departing
destroying
disassembling
encoding
repackaging
repairing
replacing
reserving
retail_selling
shipping
staging_outbound
stocking
storing
transforming
Each CBV-compliant EPCIS event SHALL include a bizStep field
The value of the bizStep field SHALL be a URI as follows:
urn:epcglobal:cbv:bizstep: followed by a string below...
entering_exiting
holding
inspecting
installing
killing
loading
other
packing
picking
receiving
removing
27. © 2012 GS1 Brasil
EPCIS Disposition
• Disposition - specifies the business condition
of the object subsequent to the event. The
disposition is assumed to hold true until another
event indicates a change of disposition.
• Disposition answers the question “What is the
status of the product subsequent to the event?”
Example: “Available for Sale”
28. © 2012 GS1 Brasil
Core Business Vocabulary
active
container_closed
destroyed
encoded
inactive
in_progress
in_transit
non_sellable_expired
non_sellable_damaged
non_sellable_disposed
non_sellable_no_pedigree_match
non_sellable_other
non_sellable_recalled
reserved
returned
sellable_accesible
sellable_not_accessible
retail_sold
unknown
Each CBV-compliant EPCIS event MAY include a disposition field
The value of the disposition field SHALL be a URI as follows:
urn:epcglobal:cbv:bizstep: followed by a string below...
29. © 2012 GS1 Brasil
EPCIS Query of supply chain events
Query
&
Response
Query
&
Response
Query
&
Response
Query
&
Response
EPCIS Repositories
pharmaceutical
plant
logistics
provider
pharmacy customs
regulatory
consumers
“Where are the drugs we ordered?”
“Which serialised blister packs were produced on line 33F in week 37?”
“Who had custody of these articles at any given point?”
“What has been commissioned and is waiting for us to pick up?”
30. © 2012 GS1 Brasil
Object Name Service (ONS)
pointer to source of
information
EPCIS Repository
manufacturer
DS request
authentication of access rights
Discovery Services
authentication of access rights
locates
several
sources of
information
Information pertaining to individual EPCs, and rules governing this access
Discovery Services vs. ONS
ONS request
EPCIS Repository
distributor
EPCIS Repository
retail
32. © 2012 GS1 Brasil
Other EPC Capture standards
Reader Management
•Protocol for monitoring of RFID reader status
•DO / SET / GET commands issued to and confirmed by reader
Low Level Reader Protocol (LLRP)
•Defines interface between client and reader
•Enables execution of air interface commands (e.g., read/write, lock, etc.)
Discovery, Configuration and Initialisation (DCI)
•Protocol for automatic addition of RFID readers to a running system
•Uses IETF Control & Provisioning of Wireless Access Points (CAPWAP)
Application Level Events (ALE)
•Reduces volume of data from readers to applications
•Insulates applications from device details
33. Contact
Wilson José da Cruz Silva
wilson.cruz@gs1br.org
(11) 3068-6249
www.gs1br.org
www.gs1.org/epcglobal
OBRIGADO!!!