Defense Logistics Management System

1
Defense Logistics Management System
(DLMS)Introductory Training
Module 6
2
Course Structure

• Module 1 - Introduction to the DLMS
• Module 2 - Electronic Data Interchange (EDI)
  Basics
• Module 3 - DLMS Implementation Strategy
• Module 4 - ASC X12 EDI Definitions and
  Concepts
• Module 5 - DLMS EDI
• Module 5F - DLMS Financial
• Module 6 - XML Emerging Technologies
• Module 7 DODAAD
• Module 8 LOGDRMS

3
Module Structure
Module 6 XML Emerging Technologies

• Extensible Markup Language (XML)
• Item Unique Identification (IUID)
• Radio Frequency Identification (RFID)

4
Module 6 Objectives

• Students will gain basic understanding of
• An introduction to DLMS XML
• IUID Initiative value and its relationship to the
  DLMS
• RFID Initiative value and its relationship to the
  DLMS

5
XML
6
What is XML?

• A set of technical specifications developed by
  the World Wide Web Consortium (W3C). It is a
  pared-down version of Standard Generalized
  Mark-Up Language (SGML), designed especially for
  Web documents. It allows designers to create
  their own customized tags, enabling the
  definition, transmission, validation, and
  interpretation of data between applications and
  between organizations.
• First released in 1998
• Variable length mark-up (tagged) language related
  to SGML and HTML ltPostNamegtFort
  Belvoirlt/PostNamegt
• XML is inherently flexible
• DLMS provides the governance structure for
  managing the myriad of XML variants that have
  evolved over time.

7
What is the benefit of XML?

• Specifically designed for web applications and
  interfaces
• Supports COTS development including Web
  Services, and Business-to-Business (B2B)
  infrastructure software and services
• Supports data modeling and reusable
  constructs
• Is incorporated into a wide variety of COTS
  tools ranging from office automation software
  on user desktops (e.g., MS Office) to
  enterprise applications such as SAP

8
Credit to Rita Knox of the Gartner Group
9
What is DLMS XML?

• EDI-based (currently available for use)
• XML schema automatically generated when changes
  are made to EDI transaction sets
• Spells out tag names (e.g., Transaction Set
  Header in lieu of ST)
• Retains structure and looping of EDI transaction
  set
• CCT-based (under construction)
• XML based on ISO 15000-5 Core Component Types
  (CCT)
• Based on underlying DLMS EDI data model
• Expressed in multiple XML variants (e.g., ebXML,
  CICA, UBL)
• May be extended to add Service unique or
  application unique elements however extensions
  must be approved by DLMSO
• May be a many-to-one relationship with EDI
  Transaction Sets
• May be only a subset of an EDI-based schema

10
Why DLMS XML?

• Provides flexible information exchange designed
  for Web based applications
• DLMSO has developed W3C compliant XML schemas,
  using EDIFECS SpecBuilder tool (EDI-based)
• DLMSO participating/supporting various standards
  bodies (ASC X12, UN/CEFACT, OASIS)
• The capability exists to translate
• MILS-to/from-DLMS X12
• DLMS X12-to/from-DLMS XML
• Using DLMS XML
• Takes advantage of both legacy system and EDI
  capability

11
DLMS XML Strategy

• Maintain existing and develop new DLMS X12 EDI
  transactions
• Maintain current DLMS EDI based XML schemas
• Participate in ASC X12, UN/CEFACT and OASIS
• Adopt International Organization for
  Standardization (ISO) 11179 standards
• Use ISO 15000-5 ebXML Core Components Technical
  Specifications (CCTS) methodology as basis for
  building reusable constructs
• Develop and maintain CCT-based XML message
  schemas
• Support the functionality required by the
  Logistics Community and which DLMSO has been
  delegated responsibility (DOD 4000.25-M).

12
The Advantages of the DLMSO XML Approach are

• Provides standard XML transaction sets and
  constructs to user community
• Standard XML form and tags across DOD logistics
  community, eliminates need for configuration
  management and mediation among multiple XML
  schema formats
• Assured interoperability of DLMS XML to DLMS X12
  EDI
• Allows developers to use either or both DLMS X12
  EDI or DLMS XML dependent on user application
  requirements, DAASC customer profiles/translation
  
• Development and maintenance at no cost to user

13
Sample DLMS EDI-based XML
14
Sample DLMS CCT-based XML
15
Compare of MILS/EDI/XML

• Key references
• AS8 is the Doc ID, same as the 856 is the trans
  ID in EDI and XML
• 6135013336101 is the Product ID (e.g., NSN)

• EA us the unit of issue
• 100 is the quantity
• 2F157363247325483489AD57 is the RFID tag

MILS AS8SMSS6135013336101 EA00100W91R0A80141007
038W91R0A80141007AXXV301
EDI ISA00 00 10W62G2T
10S36121 08020713210040301269
82850PGSSHW62G2TS3612120080207132112698
285X004030ST8560001BSN00ZZ200802071321
AS061HL1VN1Z4M4SMSFRN1ST10WC1JU3
HL2WLINFS6135013336101SN1100EATD5O
REFTNW91R0A80141007REFTGW91R0A80141007AXXDT
M01120080207N1GPM4SGATOLMDFLQ0AS8LQ
BD3LQDFSLQ37301LQ7912HL3PREFJH2F
157363247325483489AD57SE220001GE112698285IE
A1012698285
XML  lt?xml version"1.0" encoding"UTF-8"
standalone"no" ?gt - ltfilegt - ltT_Ship_Notice_Mani
fest_856Sgt - ltS_Transaction_Set_Headergt  
ltE_Transaction_Set_Identifier_Codegt856lt/E_Transact
ion_Set_Identifier_Codegt   lt/S_Transaction_Set_He
adergt ...   ltE_Product_Service_IDgt6135013336101lt/E
_Product_Service_IDgt   lt/S_Item_Identificationgt -
ltS_Item_Detail_Shipment_gt   ltE_Number_of_Units_Sh
ippedgt100lt/E_Number_of_Units_Shippedgt  
ltE_Unit_or_Basis_for_Measurement_CodegtEAlt/E_Unit_o
r_Basis_for_Measurement_Codegt  
ltE_Reference_Identificationgt2F157363247325483489AD
57lt/E_Reference_Identificationgt
16
Compare Summary

• Everything contained in the MILS is also in the
  DLMS EDI and XML
• DLMS includes
• New fields (e.g., RFID, UID)
• Expanded fields (e.g., amount fields increased
  in size)
• Bandwidth
• MILS 80 characters (just like a punch card)
• EDI 650 to 700 characters (with headers
  information)
• XML 4,300 characters (tag name are verbose)

17
DoD Metadata Registry
18
Where To Find The DLMS Transactions

• DLMSO Web Site has .PDF, .SEF
• DLMS X12/XML Schemas
• http//www.dla.mil/j-6/dlmso/elibrary/TransFormats
  /140_997.asp
• DLMSO Web Site has links to
• DoD XML Repository https//metadata.dod.
  mil/mdrPortal/appmanager/mdr/mdr
• DLIS XML Resource Library (XRL)
  https//www.dlis.dla.mil/xrl/

19
Unique Item Identification (IUID), Radio
Frequency Identification (RFID), DLMS
20
IUID, RFID, DLMS Relationship

• The IUID is a data set that identifies an
  instance of an item uniquely from all others
  even if it is identical to others in all other
  physical and functional aspects
• RFID is a technology that allows for hands free
  capture and uploading into a system of the
  occurrence of a business event at a particular
  place and time
• The DLMS X12 EDI and DLMS XML provide the
  capability to broadcast the occurrence of the
  event to other systems in the supply chain

IUID, RFID, and DLMS complement each other in
providing business event intelligence across the
supply chain
21
IUID-RFID Policy Relationship

• Where required Passive RFID tags applied at the
  case and pallet level
• Where required IUID attached or directly marked
  on items using a data matrix to carry the IUID
  data elements

22
Unique Identification (IUID)of Tangible Items
23
DoD Vision for IUID

• To implement a policy establishing a strategic
  imperative for uniquely identifying tangible
  items relying to the maximum extent practical on
  international standards and commercial item
  markings and while not imposing unique government
  data requirements.
• Uniquely identified tangible items will
  facilitate item tracking in DoD business systems
  and provide reliable and accurate data for
  management, financial, accountability and asset
  management purposes.
• Policy continues to evolve! The latest policies
  and information on IUID can be found at
• http//www.acq.osd.mil/dpap/pdi/uid/index.html

24
IUID Policy Overview

• Policy memorandum released on July 29th 2003
  established IUID as a mandatory DoD requirement
  on all solicitations issued on or after January
  1, 2004.
• IUID is required for all property items delivered
  to the Government if
• Items with an acquisition cost below 5,000, when
  identified by the requiring activity as DoD
  serially managed, mission essential, or
  controlled inventory
• Items with an acquisition cost below 5,000 as
  determined by the requiring activity
• Acquisition cost is more than 5,000
• Regardless of value, any DoD serially managed
  subassembly, component or part embedded within an
  item and the parent item in which it is
  embedded
• Wide Area Workflow (WAWF) is the preferred method
  for capturing IUID data

25
IUID Policy Overview (cont)

• The publication of DODI 8320.04, Item Unique
  Identification (IUID) Standards for Tangible
  Personal Property, dated June 16, 2008
  establishes sufficient policy to begin developing
  IUID usage business rules within the DLMS.
• Applicable policy statements having potential
  DLMS impact are as follows
• Paragraph 5.1, identify and track
  Government-furnished property through the use of
  UIIs in transaction-derived data from electronic
  business transactions. . The UII will be used
  globally as a common key in financial, property
  accountability, acquisition, supply, maintenance,
  ad logistics systems. .
• Paragraph 5.2, Use the UII to enhance life-cycle
  management of assets, and more accurate asset
  valuation .
• Paragraph 5.7, acquisition, logistics, and
  property management Automated Information Systems
  with UII requirements including the use of the
  IUID Registry .

26
Unique Item Identifier (UII) 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.
UII is . . .
27
Item Unique Identification (IUID) - How Is It
Done?
The UII Is derived from discrete component data
elements the UII is not required to be marked
on the item as its own data element
Coded in the Data Matrix
28
IUID Role - Business Enterprise Architecture
Enhance the Business Enterprise Architecture
Enhance Total Asset Visibility Improve
Life-Cycle Item Management and Accountability
Improve Data Quality and Interoperability
Clean Audit Opinions on Property, Plant and
Equipment Operating Materials and Supplies
29
IUID Registry Resident at DLIS

• Purpose
• Collect IUID and pedigree information of tangible
  items owned by DoD
• Distribute IUID and pedigree information to DoD
  users
• Provide single point of reference for DoD
  tangible items that have assigned Unique Item
  Identifier
• Additionally, context will be added to that key
  data to
• Identify what the item is
• Identify who owns the item originally
• Identify the initial value of the item
• Identify procuring activity and acceptance timing
• Connect to property management, logistics,
  inventory management
• Manage GFP data both static and fluid
• Data content of IUID registry is evolving,
  additions are likely

30
IUID Registry Statistics(as of 5 August 2009)

• 7,094,132 Items registered
• 5,093,854 New items
• 2,000,278 Legacy
• 1,619 Contractors have delivered new UIIs
• 945 of the contractors (58) are small
  businesses
• 1,430,637 of the new items (28) are from small
  businesses
• Growth rate of over 78,000 new UIIs/week
• 334,643 Items are in GFP status
• Based on current size status in CCR
• Legacy and GFP UIIs often come in large
  batches and weekly rates for those are not
  meaningful

31
Integration of IUID in DLMS

• Concept
• The inclusion of IUID data in the DLMS
  facilitates Unique Item Tracking (UIT) for those
  items that fall under the UID policy criteria of
  serial managed assets.
• Also positions DLMS transactions for wider use of
  IUID as requirements are identified and as
  logistics and financial implementation policies
  evolve.
• DLMS IUID-capable transactions accommodate UII,
  Serial Number, Manufacturer, Batch/Lot
• Expanded IUID data available on specified
  transactions (856 ASN, 856S Shipment Status, 527R
  Receipt)
• UII, UII Type, Serial Number, Original Part
  Number, New Part Number, Enterprise Identifier,
  Manufacturer, Batch/Lot

32
Radio Frequency ID (RFID)
33
Types of RFID Used in DoD

• Active RFID - Longer range
• Continuously powered tag internal power source
• Low-level RF signal received by the tag
• High-level RF signal back to the
  reader/interrogator
• Usually used for longer tag read distances
• Passive RFID Shorter range
• No internal power source collects energy from
  reader
• Needs stronger RF signal from reader stores
  small amount
• Low RF strength signal returned from tag
• Preferred for uses when tag and interrogator are
  close

34
RFID - Optimize the Supply Chain

• DOD is an early adopter of passive RFID
  technology
• Implement passive RFID Business Rules - 1 Jan 05
• Passive tagging of materiel shipped to DOD
• Initial DOD capability to read passive RFID tags
  and use data
• Published DFARS Rule requiring application of
  passive RFID
• Integrated RFID data into the DOD Business
  Enterprise Architecture (e.g., DLMS)
• USTRANSCOM is the DOD functional proponent for
  AIT
• The latest policy and information on DODs RFID
  implementation can be found at
• http//www.acq.osd.mil/log/rfid/index.htm
• http//www.transcom.mil/ait/

• Hands-Off Data Capture
• Improve Data Accuracy
• Improve Logistics Processing Time
• Improve Manpower Utilization
• Enhance Interoperability with Industry

35
DoD RFID Enabled Supply Chain
Items/Cases/Pallets are
Items/Cases/Pallets
Items/Cases/Pallets
Data is timely and
labeled
with passive RFID
are read
as they are
are associated with
accurate via network of
enabled labels. A parent to
received and
new
active RFID tag. When
linked readers
allowing
child relationship exists.
shipments are
reads are transmitted
asset visibility along the
Labeled.
Orders are
to ITV server
entire supply chain
verified for accuracy
Transportation/
Supply/
Manufacturers/
Customers
POEs/PODs
Distribution
Theater
Suppliers
Centers
/Depots
Depots/
TDCs
Timely and Accurate Data

The items/cases/pallets are automatically
received and information is shared with supply
chain AISs via the transmission of DLMS
transactions. Reconfigured shipments receive a
new passive RFID tag
When shipments are
The captured
Customers have constant
visibility of requisitions
reconfigured a new
consolidated shipment
RFID tag
input
and are confident of the status provided by
the system
is created for
information is
into the AIS
the pallet and
and used
associated with cases
to support the
on that pallet
load/stow plan
.
36
IUID, RFID DLMS Operating In Concert Can
Significantly Enhance DOD Supply Chain Processes

• Establish initial acquisition cost and
  subsequent valuations
• Identify a particular item requiring
  maintenance
• Identify particular problem items to be
  singled out for removal or upgrade
• Ensure that exact items are returned to the
  customer
• Locate items for expedited processing
• Maintain a record of items where DOD ownership
  has ended
• Provide an audit trail for lost, stolen, or
  demilitarized items

37
DLMS Supporting IUID

• 140A Small Arms Reporting
• 180M Material Returns Reporting
• 511M Requisition Modification
• 511R Requisition
• 527D Due-in, Advance Receipt, Due Verification
• 527R Receipt, Inquiry, Response Material
  Receipt Acknowledgement
• 810L Logistics Bill
• 842A/W Supply Discrepancy Report Submission
• 842S/Q Storage Quality Control Report
• 842S/R Storage Quality Control Report Reply
• 846A Asset Reclassification
• 846F Ammunition Freeze/Unfreeze
• 846I Asset Status Inquiry/Report
• 846R Location Reconciliation Request
• Advance Ship Notice
• 856R Shipment Status Materiel Return
• 856S Shipment Status
• 861 Acceptance Report
• 867I Issue

DS 527D also contains a UID/RFID indicator(s)
capability to alert the receiving storage
activity that the incoming materiel should have
IUID and/or passive RFID data IAW the contract.
DS 856, 856R, and 856S also include passive
RFID data.
38
DLMS Supporting Passive RFID
856 Advance Shipping Notice (includes
passive RFID data) 856R Shipment Status
Material Returns (will include RFID data) 856S
Shipment Status (includes passive RFID
data) XML Reader Registration XML Visibility
Response XML Visibility
DS 856, 856R, and 856S also include passive
RFID data.
39
Illustrative Examples of IUID and RFID
Transmissions via 856 ASN

• The 856 ASN uses a hierarchical structure to
  convey information and establish relationships
• Between the shipment/contract and the individual
  line items which compose the shipment
• Between the CLIN and the uniquely identified
  items associated with the CLIN
• Between the tagged containers (case or pallet)
  and the number of items or the UII of
  uniquely identified items they contain
• Between tagged containers (cases on a pallet)

40
IUID and RFID in 856 ASN

• The HL loops are defined as Shipment (DD 250
  level) (HL03S) Address (HL03V), Line Item
  (HL03I), IUID (HL03D), and RFID (HL03P)
• The IUID loop includes
• The SLN segment with IUID pedigree information
  acquisition cost, unique item identifier (UII)
  type, enterprise identifier and original part
  number, when applicable
• A separate REF with the UII and serial number for
  each item with the same pedigree in the SLN
• RFID loop includes
• The REF with the RFID tag value and a separate
  REF for each UII, when applicable -- it tells you
  which items are in which container
• The SDQ with the CLIN and the Quantity of that
  line item packed under the RFID to which the SDQ
  is associated -- it tells you how many of which
  CLIN are identified to which RFID tag

41
Single CLIN in a Single Case

• ST8560001
• BSN00DIS00012004072011300001AS
• HL1V1
• HL21S1
• HL32I1
• LIN0001VPABC
• SN14EA
• HL43D0 SLN1O1EAKFUID1MF06481X
  ZD REFU300001(UII 1) REFU300002(UII
  2) REFU300003(UII 3) REFU300004(UII 4)

4 Items with IUID in one tagged container
42
Single CLIN in Multiple Caseswithin an Outer
Container
RFID 1
ST8560001 BSN00DIS00012004072011300001AS
HL1V1 HL21S1 HL32I1 LIN0001VPA
BC SN14EA HL43D0 SLN1O1EAKFU
ID1MF06481XZD REFU300001(UII
1) REFU300002(UII 2) REFU300003(UII
3) REFU300004(UII 4)
HL52P1 REFJH(RFID 1)
RFID 2
HL65P0 REFJH(RFID 2) REFU3(UII
1) REFU3(UII 2) SDQZZ00012
RFID 3
HL75P0 REFJH(RFID 3) REFU3(UII
3) REFU3(UII 4) SDQZZ00012
4 Items with IUID in two tagged cases inside a
tagged container
43
Multiple CLINs in Multiple Cases with Multiple
CLINs per Case and Multiple Cases per CLIN on a
Pallet
ST8560001 BSN00DIS00012004072011300001AS
HL1V1 HL21S1 HL32I1 LIN0001VPA
BC SN14EA HL43D0 SLN1O1 . . .
D REFU3(UII1) REFU3(UII2) REFU3(UII3)
REFU3(UII4) HL52I1 LIN0002VPDEF
SN14EA HL65D0 SLN1O1 . . .
D REFU3(UII5) REFU3(UII6) REFU3(UII7)
REFU3(UII8) HL72I1 LIN0003VPGHI S
N12EA HL87D0 SLN1O1 . . .
D REFU3(UII9) REFU3(UII10) HL92I1
LIN0004VPJKL SN12EA HL109D0 SLN1
O1 . . . D REFU3(UII11) REFU3(UII12)
44
Illustrative Example of RFID Transmission via
856S (Shipment Status)

• The 856S also uses a hierarchical structure to
  convey information and establish relationships
• More simple structure than 856 ASN because 856S
  is created at the requisition document number
  level (same as the MILSTRIP AS_)
• Generally, one tag per transaction (identifying
  case or pallet/tri-wall in which ordered
  material is packed)
• Hierarchy can support multi-level tagging
  relationship between the interior and exterior
  tags
• IUID content planned, but not yet implemented

45
Depot ShipmentDoD Vision Material Release
Order (MRO) Level Tag

• BSN00ZZ20061128225910AS
• HL1V
• N1Z4M4SMSFR
• HL2W
• LINFS5340011514202
• SN14EA
• TD5L
• REFTNW90H9063300907
• REFTGSW312463320377XXX
• DTM01120061128
• N1Z110W26RKTTO
• LMDF
• LQ0AS2
• LQA9W26RKT
• LQBCL
• LQDFU

HL3P REFJH 2F05732354731550000
(Pallet RFID)
RFID
RFID
HL43P REFJH 2F1573235473155000000636
(Case RFID)
RFID
46
Module 6 Quiz

• Question 1 Which of the following is a key
  advantage associated with employing XML as a
  medium of information exchange?
• Low bandwidth requirements
• Supports data modeling and reusable constructs
• Looks pretty
• Incorporated into a wide variety of COTS tools
• Question 2 What benefits does RFID provide to
  DOD?
• Hands-off data capture
• Improve Data Accuracy
• Improve Logistics Processing Time
• All of the above
• Question 3 To improve material visibility
  across the supply chain which of the following
  technologies does DOD need to implement?
• IUID
• RFID
• DLMS
• All the above

47
End of Module 6