804_USNB_RptTo_SC31.ppt

1
(No Transcript)
2
NATIONAL BODY REPORTto JTC 1/SC 31United States
of America

• Craig K. Harmon
• 18 May 2004

3
ASC MH10/SC 8

• Standards and Projects
• MH10.8.100 Shipping label standard needs to be
  revised Began 1 January 2004
• MH10.8.204 Data Application identifier
  standard Continual maintenance
• MH10.8.302 Syntax for High Capacity ADC Media
  Discussion needed for possible additional
  format indicators
• MH10.8.402 RFID Tags for Returnable
  Containers needs to be revised Alignment with
  ISO/IEC documents Start 3rd Quarter 2004
• MH10.8.5 Number retired Not to be used No
  action required
• MH10.8.602 Product Packaging standard 1st
  Edition 2003-08-28
• MH10.8.7 Product Marking standard Target
  issue date is 2nd quarter 2004
• MH10.8.8 RFID for Parcels, Packages and Flat
  Mail Target date is 3rd Quarter 2004
• MH10.8.9 Product ID using other than optically
  readable media Start after MH10.8.7 is done,
  3rd Quarter 2004
• MH10.8.10 RFID for Product Packaging PINS
  Submitted 2003-12-08

4
ASC MH10/SC 8

• Schedule
• 1-2 Apr 2004 Napa, CA
• 10-11 Jun 2004 Bar Harbor, ME
• 3-4 Aug 2004 Vancouver, BC
• 6-7 Oct 6 2004 Niagara Falls, ON
• 9-10 Jan 12005 Boca Raton, FL
• 5-6 Apr 2005 San Antonio, TX (Tentative)

5
EIA/CEA
EIA - Electronic Industries Alliance CEA -
Consumer Electronics Association
6
EIA/CEA

• Recent events
• All the EIA-xxx standards are being renamed to
  CEA-xxx.
• CEA 556-C (f.k.a. EIA-556-B) Re-write has
  begun. Key decision is whether MH10.8.1 should
  be used?
• CEA 706-A Rewritten, but pending release until
  ISO/IEC 15415 is approved. This will affect
  MH10.8.7.
• CEA R9 at present is not establishing efforts on
  RFID, preferring to let MH10 SC8 and others to
  take the lead.

EIA - Electronic Industries Alliance CEA -
Consumer Electronics Association
7
TCIF/ATIS BCSC
TCIF - Telecommunications Industry Forum
8
TCIF/ATIS BCSC

• TCIF has been moved to a different parts of the
  Alliance for Telecommunications Industry
  Solutions (ATIS). The Bar code/Standard Coding
  Committee (BCSC) assigned to Network Integration,
  Operations, and Administration Forum (NIOAF).
• There is new interest in investigating the use of
  RFID in the industry. BCSC expects to start
  discussions on he issues and requirements this
  year.
• TCIF Guideline Review completed for Guideline for
  Identifying Downloadable Software for Plug-in
  Cards. Approved as TCIF-03-005.

TCIF - Telecommunications Industry Forum
9
ASC HIBCC

• Standards and Projects
• ANS HIBC-196 - HIBC Provider Application
  Standard (PAS)
• ANS HIBC-297 - HIBC Supplier Labeling Standard
  (SLS)
• Schedule
• 5-6 Aug 2004 - Boulder, CO
• 8-10 Dec 2004 - Phoenix, AZ

10
ASC INCITS T6

• Standards and Projects
• ANS INCITS 25699 Radio-frequency
  Identification (RFID) (API, Intermec 2450, SCS
  2450, Micron 2450, Savi 433)
• ANS INCITS 25601 Add PinPoint 2450, Intermec
  915, SCS 915, TI 13.56, SCS 13.56, SCS 27.1
• ANS INCITS 2560? Drop Micron 2450, PinPoint
  2450, SCS 13.56, SCS 27.1, Additional API,
  Multi-standard, multi-frequency, multi-protocol
  reader, Interrogator Communications)
• Four T6 air interfaces and API advanced by SC 31
  18000 (TI 13.56, Savi 433, Intermec 915, Intermec
  2450)
• Schedule
• 7 May 2004 - Conference Call
• 31 Aug - 1 Sep 2004 - Tobyhanna, PA
• 7-8 Dec 2004 - Knoxville, TN

11
ASC INCITS T20

• Standards and Projects
• Approved 25 July 2003
• ANS INCITS 371.1 Real Time Locating Systems
  (RTLS) 2450 MHz
• ANS INCITS 371.2 Real Time Locating Systems
  (RTLS) 433 MHz
• ANS INCITS 371.3 Real Time Locating Systems
  (RTLS) Application Programmer Interface (API)
• ISO/IEC WI24730 - Information Technology,
  Automatic Identification and Data Capture
  Techniques Real Time Locating Systems (RTLS)
  Part 1 Application Programming Interface (API),
  Part 2 2.4 GHz, and Part 3 433 MHz
• Schedule
• In maintenance

12
AIAG

• Standards and Projects
• B-2 - Vehicle Identification Number (VIN) Label
  Application Standard (in revision to include 2D)
• B-4 - Parts Identification and Tracking
  Application Standard
• B-7 - Vehicle Emission Configuration Label
  Standard (in revision to include 2D)
• B-8 - Quality Assurance Guide for Shipping Labels
  Other Bar Code Applications (Linear 2D)
• B-9 - Gas Cylinder Identification Label Standard
• B-10 - Trading Partner Labels Guideline (in
  revision adding B-10 and B-14)
• B-11 - Tire and Wheel Identification Label
  Standard (reopened for EPC)
• B-12 - Quick Receive Guideline (in revision to be
  included in B-10)
• B-13 - 2D Symbology White Paper
• B-14 - Guidelines for use of Two-Dimensional
  Symbols with the B-10 Trading Partner Labels (in
  revision to be included in B-10)
• B-15 - Standard Carrier Alpha Code Trailer
  Identification Label (SCACTIL)
• B-16 - Global Transport Label (GTL) Standard For
  the Automotive Industry
• B-17 - 2D Direct Parts Marking Guideline
• Schedule - Meets every month - 1st Tuesday, after
  3rd Monday

AIAG - Automotive Industry Action Group
13
EPCglobal

• Standards and Projects
• EPCglobal 1 EPC Tag Data Specification SAG
  Version 1.24 Later slide
• EPCglobal 2 900 MHz Radio Frequency (RF)
  Identification Tag Specification (Class 0)
  Candidate recommendation
• EPCglobal 3 13.56 MHz ISM Band Class 1 Radio
  Frequency (RF) Identification Tag Interface
  Specification (Class 1) Candidate
  recommendation
• EPCglobal 4 860 MHz - 930 MHz Class I Radio
  Frequency (RF) Identification Tag Radio Frequency
  Logical Communication Interface Specification
  (Class 1 Version 1) HAG Candidate
  recommendation
• EPCglobal 5 OID Radio Frequency Identity
  Protocols Generation 2 Identity Tag (Class 1)
  Protocol for Communications at 860 MHz 960 MHz
  (Generation 2) HAG
• EPCglobal 6 Reader Protocol SAG
• EPCglobal 7 Savant Specification SAG
• EPCglobal 8 Physical Markup Language (PML) Core
  Specification, XML Schema and Instance Files
  SAG
• EPCglobal 9 Object Name Service (ONS)
  Specification SAG
• Schedule
• Interim conference calls and webinars
• 27-28 May 2004 - HAG - Anaheim, CA
• 28 September - 1 October 2004 - Baltimore, MD

EPC - Electronic Product Code
14
EPCEPCglobalan agency of UCC and EAN
15
MIT AutoID Center

• Officially began 1 October 1999
• Initially funded by Uniform Code Council, The
  Gillette Company and Procter and Gamble
• Split into AutoID Lab at MIT and EPCglobal under
  UCC and EAN (http//www.epcglobalinc.org/ and
  http//www.epcglobalus.org/) in Q3 2003
• Software components
• Object Naming Service (ONS)
• Savant
• Product Markup Language (PML)
• Air interface protocols
• 860 - 930 MHz
• 13.56 MHz
• Supply chain impact studies
• Field trials
• Intellectual Property

16
EPC - Network vs. Code
The globally unique identifier that serves as a
pointer for making enquiries about the item it
identifies
17
EPC Class I - V
18
EPC - How it works
19
EPCglobal
Architecture Review Committee
20
EPC-96 Structure

• Class 0 - 64 bits
• Class 1 - 96 bits
• Class 1 G2 - 128/256 bits
• Class 2 - Class 1 with larger memory and
  read/write
• Class 3 - Class 2 with sensors (semi-passive)
• Class 4 - Active tags

21
EPCglobal or ISO

• ISO 18000, Part 6 (860 - 960 MHz) published
  5/31/4
• ISO 18000, Part 7 (433 MHz) published 5/31/4
• EPCglobal has four competing camps

22
Wal-Mart DoD
23
Application Requirements

• Wal-Mart - Suppliers will mark inbound cases and
  pallets with RFID - 1 January 2005 - May, 2003
  specification calls for 256 bit read/write tag
• U.S. Department of Defense - 2nd Draft RFID
  policy presented on 20 February 2003 - To issue
  final policy in July of 2004 that will require
  suppliers to put passive RFID tags on selected
  case/pallet packaging by January of 2005. -
  Policy will call for passive tag (est. 256 byte)
  and active tag

24
U.S. Department of Defense

• Projects
• Unique Identification (UID)
• RFID
• RFID Experts Group

25
DOD Unique Identification (UID)

• A world-wide unique identification of items
• Typically consists
• Enterprise ID (Company code)
• Product code (may not be required where the
  serial number is unique within the enterprise)
• Serial number
• May be discrete or concatenated fields
• Under ISO definition, this code may be up to 50
  characters in length

http//www.acq.osd.mil/uid/
26
DOD Unique Identification (UID)

• DoD unique item identification, or a DoD
  recognized unique identification equivalent, is
  required for
• All new solicitations for materiel issued after
  January 1, 2004.
• Items existing under contract or in inventory,
  i.e. legacy items
• Items considered tangible personal property owned
  by the Government in possession of a contractor
  after January 1, 2005, i.e. property management
  items
• All items for which the Governments unit
  acquisition cost is 5,000 or more
• Items for which the Governments unit acquisition
  cost is less than 5,000, when determined
  necessary by the requiring activity for serially
  managed, mission essential, or controlled
  inventory equipment, repairable items, or
  consumable items or material and
• Subassemblies, components, and parts embedded
  within an item identified on a Contract Data
  Requirements List or other exhibit
• If unique item identification is not required,
  the contractor shall provide commonly accepted
  commercial marks

http//www.acq.osd.mil/uid/
27
DOD Radio-Frequency Identification (RFID)

• DoD RFID, is required for-
• All new solicitations for materiel issued after
  October 1, 2004 for delivery on or after January
  1, 2005 will contain the following requirement
  for EPC compliant passive RFID tagging at the
  case, pallet (2nd level packaging) and UID item
  packaging level.

http//www.acq.osd.mil/uid/
28
DoD RFID Policy (as of 1 March 2004)

• Latest draft 20 February 2004
• Active
• Freight containers, air pallets
• 433.92 MHz/18000-7/Savi
• Passive
• Returnable Transport Item
• Product Packaging
• EPC 860 - 960 MHz
• Will accept for UHFGen 2 when available
• 64-bit Class 0 v1 (ReadOnly) / Matrics
• 96-bit Class 1 v1 (WORM) / Alien

29
DOD Information Systems

• The Department of Defense has numerous logistics
  systems
• These systems are fed by legacy data structures,
  notably, NATO/National Stock Numbers, CAGE/NCAGE
  codes, DoDAACs, and TCNs
• Such legacy data structures serve as the primary
  keys to DOD systems

30
DOD is not Wal-Mart

• While DOD can take advantage of the Wal-Mart
  initiatives, their business processes differ
• Where Wal-Mart will require little modification
  to their information systems, DODs modifications
  would be substantial
• Wal-Marts data structures can easily be
  converted from EPC (EPC-ready) DODs cannot

31
EPC-256 Data Structure (Legacy License Plate)
w with (1) or without (0) part number x for
future use (other demographics)
88432 52 bits (leaving 204 bits for Part
Number Serial Number) (ab 204)
32
Legacy Data DOD Supply Transportation
33
RFID Experts Group (REG)

• Standards and Projects
• Guidance to users on implementation of RFID (DoD
  Commercial)
• Schedule
• Meets every two weeks until 16 Jun 04
• Proposed to become an agency of AIM
• Meets periodically after 16 Jun 04

34
RFID Experts GroupTerms of Reference . . .

• 1. Technology selection guidelines based on usage
  parameters
• How far
• How fast
• How many
• How much
• Applied to what and the contents of the container
• 2. With multiple readers in a network, guidance
  to
• minimize overlapping reader signals of adjacent
  systems,
• ensure that the aggregated data from each reader
  system is correct
• handle / communicate with the variety of tags
  being placed before the reader, multi-protocol,
  multi-frequency readers
• define the interface to peripheral control
  mechanisms

35
RFID Experts Group . . . Terms of Reference . . .

• 3. Tag and label issues
• Placement guidance
• Tags and inserts active and passive
• Application to plastic, cardboard, plywood, free
  space, metal
• Orientation guidance
• Based on tag antenna type
• Determined by reader / antenna guidance
• Label design
• Label material and adhesive guidance for specific
  surface onto which tag mounted
• Determined by reader / antenna guidance
• 4. Data aggregation / singulation / deaggregation
  
• provide guidance on how to provide the greatest
  assurance that all tags presented to the reader
  are read

36
RFID Experts Group . . . Terms of Reference . .
.

• 5. Safety and regulatory
• With respect to frequency, power, duty cycle,
  and radiation levels, guidance on human exposure
  limitations, to include
• HERO
• HERF
• HERP
• ICNIRP
• Intrinsically safe
• 6. Security and privacy
• With respect to tag to reader, reader to host,
  and host to computing system, guidance on
  security and privacy and how to achieve the same
• FIPS 140
• Privacy guidelines

37
RFID Experts Group . . . Terms of Reference

• 7. Backup. With respect to RF tags, guidance on
  procedures to be undertaken if one or more tags
  are unable to be read
• Secure business process / implementation group
  representative
• 8. Sensors/Transducers
• SAL-C . . . IEEE 1451
• Sensor interface. With respect to higher
  functionality tags guidance on the implementation
  of sensor technology input.
• How do I know with which tag I am communicating

38
RFID Experts Group Phase II Issues

• 9. Rogue tags
• With respect to transmitted bits and ubiquitous
  implementation, guidance on how one ensures that
  the tag being read is for the application
  intended.
• 10. Tag to tag communications and networking

39
U.S. FDA

• Standards and Projects
• HHS Announces New Requirements for Bar Codes on
  Drugs and Blood to Reduce Risks of Medication
  Errors
• Combating counterfeit drugs (using RFID)
• Schedule
• 25 February 2004, New medications covered by the
  rule will have to include bar codes within 60
  days of their approval most previously approved
  medicines and all blood and blood products will
  have to comply with the new requirements within
  two years.
• February 2004, The adoption and common use of
  reliable track and trace technology (RFID) is
  feasible by 2007

FDA - Food and Drug Administration
40
Bar Code Requirementto reduce Medication Errors
41
Item Identificationversus Anti-Counterfeiting
42
U.S. FCC

• Standards and Projects
• FCC adopts rule changes for improved radio
  frequency identification systems (at 433 MHz) to
  facilitate Homeland Security efforts at ports,
  rail yards and warehouses in commercial and
  industrial settings enabling the contents of
  containers to be rapidly inventoried.
• Schedule
• Approved 15 April 2004

FCC - Federal Communications Commission
43
Recent Developments

• 433 MHz
• ISM band permitted by ITU (implemented in Region
  1 but for different parameters in Regions 2 and
  3)
• ITU receptive to Regions 2 and 3 supporting
  Region 1 for a 433 MHz allocation for freight
  containers
• Chairman of ISO TC 104 (Freight containers) has
  made request to ITU and WCO to embrace both
  passive (860 - 960) and active (433.92 MHz)
  calling out 18000-6 and 18000-7
• Under serious consideration in both Japan and
  Korea
• Both Japan and Korea have requested U.S.
  governmental letters of support, i.e., FCC, NTIA,
  DoD, NATO
• Received support through new (April 2004) FCC
  rules, specific to RFID, that increases both
  power and duty cycle.

44
U.S. FTC / Privacy

• Project
• JTC 1 Privacy Technology Study Group
• Public Workshop Radio Frequency Identification
  Applications and Implications for Consumers
• Schedule
• 17-18 Jun 2004 - JTC 1 Privacy Technology Study
  Group, Montreal, QC
• The workshop will be held on Monday, June 21,
  2004, from 830 a.m. to 530 p.m. at the Federal
  Trade Commissions Satellite Building, which is
  located at 601 New Jersey Avenue, N.W.,
  Washington, DC. The event is open to the public
  and there is no fee for attendance.
  Pre-registration is not required.

45
???
46
Thank you!!!
47
(No Transcript)