utomatic

1
A
utomatic
I
dentification
T
echnology
Headquarters, U. S. Marine Corps HQMC (LPV)
2
Agenda

• What is AIT?
• AIT Organization
• AIT Media
• Where We Are Today
• Policy
• Radio Frequency Identification (RFID) Active
  Passive
• Unique Identification (UID)
• Way Ahead

3
Automatic Identification Technology Definition

• AIT is a suite of technologies that enable the
  automatic capture of source data, thereby
  enhancing the ability to identify, track,
  document and control deploying and redeploying
  forces, equipment, personnel and sustainment
  cargo.
• --------------------------------------------------
  --------------------------------------------------
  ----------------------------------------------

4
What AIT Does for Us

• Benefits
• AIT improves Naval logistics and enhances war
  fighting capability by
• Improving source data capture
• Speeding data processing and transmission
• Improving data accuracy
• Facilitating decision making
• Supporting material accountability
• Contributing to total asset visibility
• Providing portable data file capability

AIT is not a system
5
OSD/Joint Staff AIT Organization
OUSD (ATL)
ADUSD LMR Supply Chain Integration (RFID)
Dir, Defense Procurement (UID)
Mr. Estevez
Ms. Sumpter
Co-chair
AIT Senior Steering Group ? ? ?
Co-chair
JSJ4
OPNAV N4
HQMC DC IL
DoD AIT Office (DLA)
Army (Administers HW Contract)
Navy (OPNAV/NAVSUP)
Marine Corps
COCOMs, Defense Agencies, Others
Air Force
6
Marine Corps AIT Organizational Chart
DC, IL (LP) Logistics Plans, Policies,
Strategic Mobility Division
Other LP Codes Involved.
DC, IL LPV
MARCORSYSCOM AIT Project Officer
LOGCOM
MARFORs
Supporting Establishment
HQMC (DC, IL) is responsible for oversight of
USMC AIT Implementation
7
Responsibilities as Service AIT POC

• Primary POC for Service-wide AIT policy,
  procedures, instrumentation, and
  implementation in support of the MARFORs and
  Supporting Establishment.
• Lead and support for Service POM issues to
  include external agencies such as OSD and the
  Joint Staff.
• Coordination of AIT pilots, testing, and
  evaluation with all functional advocates to
  ensure full AIT integration across the business
  enterprise.
• Coordination of those AIT business processes
  outside the functional lines (i.e.,
  installation of RFID at a base/station) to
  include long-term maintenance.
• Development and review of architectural
  requirements for future AIS under GCSS-MC,
  which includes Log C2
• Coordination with TECOM for AIT insertion into
  MOS training packages.

8
Funding Profile
9
AIT Integration
Business Process Integration (Retail Wholesale)

• Acquisition/
• Contracting Supply Distribution
  Transportation Maintenance Others
• UID IRRD IRRD
  MSL UID
  Ammo
• RFID RFID RFID
  RFID
  Aviation
• MSL OMC
  OMC
  PEIs/SecReps
• 
  
  Garrison Prop
• 
  
  Wholesale

• AIT Integrator
• POM
• HW Acq
• Sys Integration
• Data Standards
• HW Maint
• Technical SME

• Coordination
• NLI
• OSD/JSJ4/COCOMs
• DoD AIT Office
• Services
• MARFORs/SEs

Policy
POM
Policy Media
POM Technical Data
Syntax RD Linear Bar
Codes
Specifications Data Identifiers
2D Bar Codes - PDF417
(MSL/IRRD) - Datamatrix
(UID) Optical Memory Card
(AMS) Contact Memory Button
Integrated Circuit Card (CAC)
RFID - Active
(SAVI) - Passive
(Alien/Matrix)

• Working Groups
• DoD AIT IPT
• AIT Technical Working Group
• DoD RFID IPT
• - RFID Technical Working Group
• - RFID Business Process Working Group
• - RFID Implementation Working Group
• UID Working Group
• Tradeshows
• Frontline Expo
• Air Force Symposiums
• Navy AIT Steering Group

Technology
10
Information Flow Hierarchy
Presentation Layer
AIT Integration TAV SDE Marking
Battlespace Situational Awareness
Process Layer
GCSS-MC satisfies JTAV, DRID 54, GCSS Capstone
Document
Global Information Applications
GCSS-MC SDE Satisfies CoCOM 129, TAV, ITV
AMS-TAC
CMOS
MDSS II
GCSS-MC
Mission Applications
Data Layer
UID/RFID policy, DTR, MILSTDs 129/130, etc.
Source Data Collection
11
AIT Media

• Barcodes Linear
• Code 3 of 9
• DoD adoption of commercial standard
• capacity 40 ASCII character set
• durability susceptible to sunlight, moisture
• widely used, common
• license plate information linked to database
  record
• read with linear/2D/Charged Coupled Device (CCD)
  scanner
• reproduced on specialty/laser printers

Easy, reliable, cost effective
12
AIT Media

• Barcodes 2D
• PDF417 - EDI and manifesting
• Can carry large amounts of data within a symbol
  on shipping cartons and documents, where there is
  typically more room to carry information
• MaxiCode - sortation and parcel tracking
• Can be quickly located by high speed sortation
  equipment due to its built-in bulls-eye
  pattern
• DataMatrix - direct item marking
• Can carry data in a small area, a silicon wafer
  for example
• DoD has specified for UID

13
AIT Media

• Optical Memory Card (OMC)
• CD-ROM in a card format
• Capacity Up to 4.1 MB
• Durability Acrylic overcoat provides 1,000
  times more durability than a PVC credit card
• Characteristics Credit card size flexible
  capable of multiple technologies (magnetic
  stripe, IC chip) supports embedded holograms and
  other security options
• Read/write Write once, read many (WORM)
  technology allows data to be added until capacity
  is reached requires dedicated, fixed reader
  

14
AIT Media

• Integrated Circuit Card (ICC)
• PC on a card
• Types Memory cards just store data
  (up to 8k bits)
• Microprocessor cards mini- computers
  w/OS and hard disk (up to 64k bytes)
• Interfaces Contact require physical contact
  w/reader
• Contactless embedded antenna eliminates
  need for physical contact w/reader
• Characteristics Credit card size flexible
  capable of multiple technologies (magnetic
  stripe, IC chip) microprocessor cards very
  secure w/data encryption, PKI biometrics
  
• Read/write Capable of up to 75,000 reads

15
AIT Media

• Active RFID
• Standard evolving manufacturers proprietary
  systems/protocols
• Range up to 300 feet
• Characteristics small tag with internal power
  cell mounted to item interrogator queries tag,
  uploads/downloads data data capacities vary

Increased range and data
16
AIT Media

• Passive RFID
• Standard evolving uses back scatter technology
• Range typically measured in inches, industry
  working toward feet
• Characteristics requires choke point, data
  capacity limited (license plate data)

Tag
Automated Operation
17
AIT Media

• Contact Memory Button (CMB)
• Highly versatile, EEPROM-based storage device
• capacity up to 8 MB
• durability hermetically sealed, various casing
  options survive almost all forms of environmental
  exposure including xray/Electromagnetic
  Interference (EMI)
• characteristics 16mm x 5mm, or 5mm x 3mm
  footprints, numerous mounting techniques,
  battery-less, limitless data retention
• read/write via portable or RS232 devices data
  transfer rates in milliseconds

Compact, durable, abundant storage
18
What Are We Doing Today With AIT
Policy DoD 4000.25-1-M Military Standard
Requisitioning and Issue Procedures
(MILSTRIP) Requirement Requires a 2D IRRD to be
printed for all requisitions Legacy systems
capability STRATIS, ROLMS, Optimized-NALCOMIS
Issue Release/Receipt Document
Policy DoD 4500.9-R-Part 2/3,
Defense Transportation Regulation
Requirement Requires a 2D MSL for sustainment
shipments and unit move equipment entering the
organic distribution system Legacy systems
capability CMOS, MDSS II, AMS-TAC
Military Shipping Label
19
What Are We Doing Today With AIT
Policy None Requirement Equipment label used
to account and track unit move and Maritime
Preposition Ship (MPS) equipment Legacy systems
capability MDSS II
LOGMARS Label
Policy None Requirement Provide requisition
and transportation data for multipack and
container shipments from DLA to facilitate
in-check process of materiel Legacy systems
capability AMS-TAC
Optical Memory Card
20
Active RFID
The Beginning USCENTCOM 311340ZJUL02 required
all air pallets, containers, and commercial
sustainment moving to/from the theater and
intra-theater movements to be tagged with RFID at
origin for asset and in-transit visibility
tracking in the AOR. Organizations that cannot
implement RFID tagging must establish procedures
that enable content level detail to be entered
into GTN and JTAV manually within the timeliness
standards.
RFID offers the best potential for immediate
In-Transit Visibility
21
Active RFID
DoD Mandate DoD Components will immediately
resource and implement the use of high data
capacity active RFID in the DoD operational
environment. DoD Components must ensure that all
consolidated shipments (sustainment/ retrograde,
unit move, ammunition, and preposition) moving
to, from, or between overseas locations are
tagged, including retrograde, and must expand the
active RFID infrastructure to provide global
intransit visibility (30 Jul 2004).
22
Active RFID
JTAV GTN
User Queries WWW for Multiple Data Requirements
Asset Visibility
PACOM
USAREUR
To CONUS
To PACOM
CONUS
Kuwait
Depot/ Camp/ DLA/ POE Feed Tag Point of Origin
Local ITV Workstation
Local ITV Workstation
Local ITV Workstation
Local ITV Workstation
Logistics Node
Node
Node
Node
Node
23
Active RFID
Tag Content Asset Level Detail

• Asset level detail is the most fundamental of
  information necessary to describe an item and a
  mandatory requirement in obtaining visibility.
  The following data elements are the minimum
  required, as applicable, to describe the physical
  and identification characteristics of a single
  asset
• National Stock Number (NSN)Nomenclature/Descript
  ionCondition CodeItem WeightItem CubeLine
  Item Number (LIN)/Package Identification
  (PKGID)Ammunition Lot NumberDepartment of
  Defense Identification Code (DODIC)Hazardous
  Cargo Descriptor Codes (to include ammo/
  hazardous materiel).

24
Active RFID
Tag Content Content Level Detail

• Content Level Detail includes those data elements
  that describe the asset plus the following
  additional required data elements necessary to
  minimally identify each level of a complete
  shipment entity (a single shipment unit or a
  consolidated shipment). The following required
  data elements represent the minimum necessary to
  provide Content Level Detail visibility for each
  shipment unit and are contained in the
  requisition documents, the Transportation Control
  and Movement Document (TCMD), the commercial
  carrier transactions, and the Consolidated
  Shipment Information transactions that describe
  the shipment and shipment movement
  characteristics
• Requisition Document Number, Required
  Delivery Date (RDD) or expedited shipment and
  handling codes, Project Code, Asset (item)
  Quantity, Unit of Issue (U/I), From Routing
  Indicator Code (RIC) (for DOD shipments),
  Inventory Control Point (ICP) RIC (for
  contractor/vendor shipments), Shipment
  Transportation Control Number (TCN) for single
  shipment unit, Intermediate TCN for a
  multi-level consolidated shipment, Conveyance
  (lead) TCN for a consolidated shipment,
  Commercial Carrier Shipment Tracking Identifier,
  Transportation Priority, Sender (Consignor)
  DODAAC/CAGE Code, Ship Date, Point of Embarkation
  (POE) Code, Point of Debarkation (POD) Code,
  Shipment Total Pieces, Shipment Total Weight,
  Shipment Total Cube, Oversize Length/Width/Height,
  Receiver (Consignee) DODAAC, Commodity Class,
  Commodity Code (air/water), Special Handling Code
  (air/water), Water Type Cargo Code, Net Explosive
  Weight (NEW), Unit Identification Code (UIC),
  Unit Line Number (ULN), Operation/Exercise Name,
  Hazardous Material (HAZMAT) Shipping
  Characteristics, United Nations Identification
  Number (UN ID), Class or Division Number, Package
  Group, Compatibility Group.

25
(No Transcript)
26
(No Transcript)
27
(No Transcript)
28
Active RFID
Jul 03 Received 4M from HQMC PR to being to
re- engineer our business process to incorporate
RFID HQMC priority of RFID implementation
1 Sustainment/Distribution 2 Unit Move 3
Prepo
29
Active RFID

• Operational Support (OIF II)
• HQMC designated I MEF SMU as focus of effort
• Use of RFID tags applied to SMU Class IX
  accompanying supplies (sustainment cargo) only
• AMS-TAC (TMO in-check system) provided RFID tags
  write capability
• SAVI Active Tags used with existing RFID
  infrastructure to gain nodal visibility of
  shipments down to unit level

30
Active RFID

• Operational Support Operation Secure Tomorrow
• RFID Tag requirement for USSOUTHCOM Haiti OPS
• RFID tag write capability installed at Camp
  LeJeune with SR Platoon using AMS-TAC
• RFID Interrogators placed at Triangle Gate and
  Lot 201 (Container Lot) at Camp LeJeune, APOE
  at Cherry Point, CSSD20 in Haiti
• Satellite tracking (IRIDIUM and VISTAR) placed
  on sustainment channel ship OLYMPOS and Haiti
  patrol boats

31
Active RFID

• Operational Support OIF IIB and III
• Focus turns to II MEF Deployment will
  include Unit Move and accompanying
  supplies (sustainment) RFID tagging
• II MEF RFID requirements being developed
  
• (CONUS and Deployed)
• Interrogator already installed at Lot 201
  Container Lot
• Preparing to install interrogators at
  various locations at Camp LeJeune
  (several gates, railhead, LMCC lot) Cherry
  Point (main gate, APOE) New River (main gate)

32
Active RFID

• Systems Modifications
• MDSS II ver. 7.1 will write unit move RFID tags
  with Jan 05 fielding (Government Acceptance
  Testing being conducted)
• AMS-TAC will write sustainment formatted RFID
  tags
• CMOS available Nov 04 with RFID tag write
  capability for TMO outbound shipments

33
Active RFID

• RFID Road To III MEF
• Limited RFID equipment procured 2000 RFID tags
  with some interrogators and scanners shipped
  in Sep 04
• Fixed Infrastructure
• Over 40 site surveys completed (North Carolina,
  California, Hawaii, Japan) installation to
  being Nov 04
• Albany survey being conducted today

34
Active RFID

• MPS
• Conduct initial business process analysis (30
  Nov 2 Dec 04)
• Provide hardware to test and develop POAM
• Identify MMC to begin tagging

35
Passive RFID

• DoD Mandate
• RFID will be mandatory on solicitations issued
  on or after 1 Oct 04 for delivery of materiel
  after 1 Jan 05
• Passive Tags will be applied to the Case,
  Pallet and item packaging for UID items.

36
Passive RFID

• Basics
• Interrogator/Reader
• Tag
• Server linked to appropriate database
• Tag range and memory capacity is primary
  difference between Passive and Active RFID
• Range for Passive Approx three meters
• Memory for Passive is a 96-bit binary code
• Consistent with Electronic Product Code (EPC)

37
Passive RFID

• Scanning Limitations
• Cannot scan Passive RFID tags and build an active
  RFID tag
• Cannot scan from a distance greater than a few
  meters
• Scan only provides license plate data must link
  to data- base

38
Passive RFID

• Electronic Product Code (EPC)
• Will be applied to all products unique number
  for each
• 96-Bit binary associated with Passive RFID
  (below)

39
Passive RFID

• Labeling
• A scanned tag yields what?
• Binary
• To get beyond the binary you must link to a
  database
• Currently there is no database tied to legacy
  systems
• At this point its impractical to establish
  Passive RFID to A2P, SASSY, STRATIS

40
Passive RFID
DDSP Susquehanna
Information exchange (ASN) acknowledgement
Edge Services
Edge servers used as EDI transactions cannot take
place on legacy systems.
CLNC ISSA
Edge Services
41
Passive RFID

• Current efforts associated with II MEF experiment
• DDSP tags all case/pallets
• Information fed to Edge Server at DDSP
• Shares info w/ Edge Server at CLNC
• When RFID tags interrogated at CLNC receipt
  signal sent
• Greatest value to DoD in metrics this will
  link to all Services eventually.

42
Use of Alien Interrogators at Camp Lejeune
43
Passive RFID

• EDI Transactions
• Marine Corps legacy systems are designed to
  accept 80 card-column (MILS) transactions
• RFID falls into an (American Standards Committee)
  ASC X12 protocol
• With GCSS-MC inbound its impractical to change
  legacy systems to ASC X12 protocol / XML
• GCSS-MC was purchased with ASC X12 protocol
  included.

44
Passive RFID

• How can the Marine Corps take advantage of
  Passive RFID now?
• Requires database for tag information to be held
• Edge or other servers
• No funding identified to support additional
  implementation unitl 2007

45
UID
46
UID

• DoD PolicyMandatory for contracts issued on or
  after January 1, 2004 for the following items
• Acquisition cost of 5,000 or more
• Serial managed
• Mission essential
• Controlled
• Reparable
• If item has a UID equivalente.g. a VIN
• As designated by Program Managers

47
UID

• Additional UID Marking Policy
• Government Furnished Property
• January 1, 2006 and after (Dates changed
  recently from Jan 05 to Jan 06)
• Government furnished property provided to
  contractors must be marked.
• Government furnished property that is in the
  possession of a contractor must be marked if
  the item is moved or delivered to a different
  location with a different enterprise
  identifier.
• Legacy Item Marking (Depot Maintenance,
  Inventory and Operational Use)
• FY 2007 All existing serialized assets should
  be entered into the UID registry and UID
  marking capabilities are established for all
  existing items and embedded assets such that
  marking can commence as applicable equipment
  are returned for maintenance.
• December 31, 2010 Complete UID marking of items
  and all embedded assets within existing items.
• Additional guidance on Virtual UID alternative
  forthcoming.

48
UID
Purpose

• Cradle to grave tracking history
• Utilize in AISs in support of business
  processes

49
UID
Strategic Outcomes

• DoD considers the implementation of unique
  identification to be a strategic imperative,
  necessary to efficiently move supplies to
  warfighters. UID will
• Enhance logistics, contracting, and financial
  business transactions supporting U.S. and
  coalition troops
• Enable DoD to consistently capture the value of
  items it buys, control these items during
  their use, reduce operating costs and combat
  counterfeiting of parts
• Enable DoD to make appropriate entries into its
  property accountability, inventory, and
  financial management information systems toward
  achieving compliance with the Chief
  Financial Officers Act.

• Lower costs of managing and ownership of assets
• Increase business intelligence
• Achieve clean audit opinion
• Lower asset management infrastructure costs
• Increase systems/equipment operational
  availability

UID Payoffs
50
UID
Current Requirement
UID - 2D Data Matrix Bar Code
Compliance Indicator )gtRS Data Identifier
Format Header 06GS CAGE 17V12345GS Serial
Number S5513HGR1313GS Part Number 1P6574867635
009GS
UID is -123455513HGR13136574867635009
51
UID

• Composition
• When constructing the UID
• Spaces will be deleted
• Special characters will be deleted from the
  Enterprise Identifier
• Special characters will not be deleted from the
  part number or serial number

UID Construct 1
UID Construct 2
12V194532636
12V194532636
18S786950
EID
Serial No.
EID
Original Part No.
Serial No.
UID Construct 1 UN194532636786950
Other 5678
Other 5678
UID Construct 2 UN1945326361234786950
IAC
EID
Serial No.
EID
Serial No.
Original Part No.
IAC
Current Part No.
Current Part No.
UID Construct 2 will be modified (Construct 2A)
to include lot or batch number in the UID. This
will enable unique marking of an ammunition item
that requires a UID without negatively impacting
current business practices.
52
UID
What Needs to be Marked on the Item?

• Required Data Matrix Bar Code
• If Real Estate Permits
• Preferred Data matrix Human Readable Linear
• Next Best Data matrix Human Readable
• Next Best Data matrix

53
UID
Who Decides How and Where to Mark?

• Program Manager
• The design activity shall specify the actual
  method(s) to be used in applying markings
• Basic Marking Methods
• Ink Jet
• Laser Marking
• Dot Peening/Pin Stamping
• Electro-Chemical Etching
• Other Methods
• MIL-STD-130L governs the marking of items

54
UID
Reading

• Primary requirement dictates need for a 2
  Dimensional Data Matrix Reader
• Where possible
• Linear Bar Code Backup
• Nomenclature and data written out in human
  readable format
• Contact Memory Buttons if desired

55
UID
Potential Benefits

• Accurate product information
• Enhanced maintenance management
• Enhanced material management
• Historical maintenance information
• Frequency of repair
• Failure and problem item identification
• Mechanics proficiency
• Contractor performance
• Identification of poor performing or problem
  items
• Warranty enforcement
• Tracking OM costs
• Decrease in premature disposal of items
• Capture of data that drives reliability
  improvement
• Management of specific warranty requirements
• Primary key to relational databases

56
UID
Implementation Challenges

• Specify where on a part to apply UID symbol
• Specify how big to make the UID symbol
• Specify the UID construct for an enterprise doing
  marking
• Specify the marking technology to use for each
  part
• Revise drawings for all affected items
• Specify which parts need UID
• Specify when and how UID data is to be used
• Specify what data is to be collected along with
  UID
• Determine if existing databases or information
  systems need to be modified or new ones need to
  be developed to accommodate UID data
• Select and procure marking and reading equipment
• Train personnel
• Develop marking, reading, and data entry
  procedures or modify existing procedures to
  accommodate UID data collection
• Prior to marking, generate the specific UID
  character string for a part
• Apply UID marks to outgoing items
• Read UID marks on incoming items
• Enter UID data into information systems

57
UID
Using UID Today?
58
UID
GCSS-MC Integration
59
UID
Which Needs to Deploy First?
60
UID
An Analogy

67
61
UID
References
Basic overall reference www.acq.osd.mil/uid/
Commercial site www.uidsupport.com Defense
Acquisition University www.dau.mil DoD Logistics
AIT Office www.dodait.com Wide Area Workflow
https//wawf.eb.mil

62
The Challenge
Passive RFID Tag
Container/Pallet Identification
Integrating AIT into our business process
63
Way Ahead

• Providing Educational Briefs
• Developing Implementation Plans and MCOs on
  AIT
• Energizing Functional Advocates to develop
  requirements for AIT and incorporate into
  existing and/or planned policy documents
• Supporting GCSS-MC functional requirements
  for AIT

64
Questions
Questions..