utomaticdentificationechnology

Headquarters, U. S. Marine CorpsHQMC (LPV)

IIAA

TT

Agenda

What is AIT?

AIT Organization

AIT Media

Where We Are Today

Policy– Radio Frequency Identification (RFID) Active & Passive– Unique Identification (UID)

Way Ahead

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

--------------------------------------------------------------------------------------------------------------------------------------------------

Linear bar codes Integrated Circuit Card (Smart Card)

2D bar codes Optical Memory Card (OMC)

Contact Memory Button Radio Frequency Identification (RFID)

Satellite Tracking

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

What AIT Does for Us

AIT is not a system

OSD/Joint Staff AIT Organization

OUSD (AT&L)

AIT Senior Steering Group

JSJ4

DoD AIT Office(DLA)

Army(Administers

HW Contract)

Navy(OPNAV/NAVSUP)

Marine Corps Air Force COCOMs, Defense Agencies,

Others

ADUSD L&MR Supply Chain

Integration(RFID)

Dir, Defense Procurement

(UID)Mr. Estevez Ms. Sumpter

Co-chair

Co-chair

OPNAV N4 HQMC DC I&L

Marine Corps AIT Organizational Chart

DC, I&L (LP)Logistics Plans,

Policies, &Strategic Mobility

Division

DC, I&L (LP)Logistics Plans,

Policies, &Strategic Mobility

Division

MARCORSYSCOMAIT Project Officer

MARCORSYSCOMAIT Project Officer

HQMC (DC, I&L) is responsible for oversight of USMC AIT Implementation

DC, I&L LPV

DC, I&L LPV

Other LP Codes

Involved.

LOGCOMLOGCOMMARFORsMARFORs Supporting Establishment

Supporting Establishment

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.

Funding Profile

($M) FY06 FY07 FY08 FY09 FY10 FY11

AIT POM 8.8 10.8 13.8 16.5 10 11.3

Legacy 3.3 3.4 3.5 3.7 3.8 4.1

Active RFID 5.5 7.4 10.3 12.8 6.2 7.2

Passive RFID 0 0 0 0 0 0

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

Technology

Business Process Integration (Retail & Wholesale)

AIT Integration

Policy Media POM Technical Data Syntax & R&D • 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

Policy

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

POM

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

Information Flow HierarchyPresentation Layer

Process Layer

Data Layer

6

GCCS COP Combat Support Enabled

JTAV GTN

JOPES

MDSS IIAMS-TAC

CMOS

Source Data Collection

Mission Applications

Global Information Applications

Battlespace Situational Awareness

GCSS-MCSDE

GCSS-MC

UID/RFID policy, DTR, MILSTDs 129/130, etc.

GCSS-MC satisfies JTAV, DRID 54, GCSS Capstone Document

GCSS-MC SDESatisfies

CoCOM 129, TAV,ITV

AITIntegration

TAV

SDE

Marking

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”

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

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

AIT Media

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/readerContactless – 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

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”

AIT Media

“Automated Operation”

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

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”

AIT Media

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

Policy: DoD 4500.9-R-Part 2/3, DefenseTransportation 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

Issue Release/Receipt Document

What Are We Doing Today With AIT

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

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

Optical Memory Card

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

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

Active RFID

Local ITV Workstation

Local ITV Workstation

Local ITV Workstation

Local ITV Workstation

CONUS

Kuwait

Node NodeNodeNode

LogisticsNode

Depot/Camp/DLA/POEFeed TagPoint ofOrigin

To PACOM

To CONUS

PACOM

JTAVGTN

USAREUR

Asset VisibilityUser Queries WWW for Multiple Data Requirements

Active RFID

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/DescriptionCondition 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).

Tag Content – Asset 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.

Active RFID

Tag Content – Content Level Detail

Active RFID

Jul 03 – Received $4M from HQMC P&R to being to re- engineer our business process to incorporate RFID

HQMC priority of RFID implementation: #1 Sustainment/Distribution #2 Unit Move #3 Prepo

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

Active RFID

Operational Support – Operation Secure Tomorrow:

• RFID Tag requirement for USSOUTHCOM Haiti OPS

• RFID tag write capability installed at Camp LeJeune with S&R 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

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)

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

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 survey’s completed (North Carolina, California, Hawaii, Japan); installation to being Nov 04

• Albany survey being conducted today

Active RFID

MPS:

• Conduct initial business process analysis (30 Nov – 2 Dec 04)

• Provide hardware to test and develop POA&M

• Identify MMC to begin tagging

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.

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)

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

Passive RFID

•Electronic Product Code (EPC)

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

6

A number …………………. in a radio tag …

… which together, uniquely identifies an object

Electronic Product Code (EPC)

The EPC Number (96 bit version)

01 203290 1688648 71912345678

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 it’s impractical to establish Passive RFID to A2P, SASSY, STRATIS

Passive RFID

CLNC ISSA

DDSP

Susquehanna

Edge Services

Edge Services

Information exchange (ASN) & acknowledgement

Edge servers used asEDI transactions cannot take place on legacy systems.

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.

Use of Alien Interrogatorsat Camp Lejeune

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 it’s impractical to change legacy systems to ASC X12 protocol / XML

•GCSS-MC was purchased with ASC X12 protocol included.

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

Unique IDentification (UID) is….

UID is . . .

. . . the set of data for tangible assets that is globally unique and unambiguous, ensures data integrity and data quality throughout life, and supports multi-faceted business applications and users.

UID is represented by a 2D Data Matrix bar code.

UID is a unique serial number never to be repeated……………

UID

UID

DoD Policy:

Mandatory 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 equivalent—e.g. a VIN

• As designated by Program Managers

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.

• Cradle to grave tracking history

• Utilize in AISs in support of business processes

UID

Purpose:

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

UID

Strategic Outcomes:

UIDRegistry

End Item Data (15)• UID (concatenated)• Descriptive data

– UID data elements (5)– Item description– Unit of measure

• Acquisition data– Contractor– Contract number– CLIN/SLIN/ELIN– Price– Acceptance code (identifies acceptor)– Acceptance date– Ship to code

Embedded Items of End Items (10)• UID (concatenated)• Descriptive data

– UID data elements (5)– Item description– Unit of measure

• Parent UID as of delivery date

WAWF

Acquisition

Jan 2004 Jan 2006Gov’t Furnish Prop

Jan 2010Legacy

Compliance Indicator [)>RS

Data Identifier Format Header 06GS

CAGE 17V12345GS

Serial Number S5513HGR1313GS

Part Number 1P6574867635009GS

UID - 2D Data Matrix Bar Code

UID is -123455513HGR13136574867635009

UID

Current Requirement:

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

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

UN194532636786950

EID Serial No. Current Part No.

Other

5678

UID Construct #2

UN1945326361234786950

EID Serial No. Current Part No.

Other

5678

Original Part No.

18S7869501P123412V19453263612V194532636 18S786950

EID Serial No. EID Serial No.Original Part No.

UID Construct #1 UID Construct #2*

IAC IAC

• 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

What Needs to be Marked on the Item?

UID

• 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

Who Decides How and Where to Mark?

UID

UID

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

Reading:

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

UID

Potential Benefits:

• 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

UID

Implementation Challenges:

• In most cases—No

• Initial focus of UID initiative should be on getting items marked and entering the data into the UID Registry.

• When “sufficient” amount of UID data are available it might

make business sense to modify some AISs to accept and formulate UID data in support of business processes.

• Marking items and modifying AISs will be a long-term evolutionary process.

UID

Using UID Today?

UIDDepot/Joint Integration

SDE

FDP&E Planning

OrderManagement

MaintenanceManagement

FulfillmentManagement

Service Fulfillment

Purchasing/Procurement

Personnel Management

Portal

DSS

AL

CombatEngineers

Data Warehouse

Transportation

Warehousing

Distribution

Inventory Control

ResourceManagement

Asset Management

UIDRegistry

GCSS-MC Integration

UID

Which Needs to Deploy First?

67¢

UID

June 26, 1974 First product with a bar code was scanned at a grocery store in Troy, Ohio.

September 1, 1981 DoD adopted bar code for all products sold to DoD.

“Build it and they will come.”

Bar code use essentially universal today.

An Analogy:

UID

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

References:

Shipping Container

Contact Memory Button

Maintain MaintenanceAnd Configuration Data

Military Shipping Label

Mailing Label

UID

Unique Serial Number

SAVI Active Tag

Point-in-time-Tracking

Optical Memory Card

Cargo Manifest

Satellite Tracking

Real-time Tracking

Issue/Release Receipt Document

Materiel ReleaseDocument

Passive RFID Tag

Integrating AIT into our business process

The Challenge

Container/Pallet Identification

SAVI Active Tag

Point-in-time-Tracking

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

Questions