Defense Logistics Management System DLMS Introductory Training

1
Defense Logistics Management System
(DLMS)Introductory Training
Module 3
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 5M DLSS/DLMS Mapping
• Module 6 XML Emerging Technologies

Module 3 / Course Structure
3
Module Structure

• Module 3 DLMS Implementation Strategy

• DLMS Migration Program Management Plan
• DoD Corporate Services
• Operating Concept
• Configuration Management
• Lessons Learned

Module 3 / Course Structure
4
Module 3 Objectives

• Students will gain basic understanding of
• The purpose and contents of the DLMS Migration
  Program Management Plan (PMP)
• What corporate services are available to
  support implementation
• The DLMS operating concept including critical
  translation and conversion processes
• The essential elements of Component planning
  for DLMS implementation
• How DLMS process changes are managed
• Lessons learned during previous DLMS
  implementations

Module 3 / Objectives
5
DLMS Migration Program Management Plan (PMP)
Module 3 / DLMS Program Management Plan
6
DLMS Migration PMP is Largely About
Cutting the Elephant Into Manageable Pieces

• Phased Migration Build your strategy and
  schedule for
• Evolution, not Revolution
• By System
• By Function
• By Transaction Priority Grouping
• By DLSS Transaction Family
• By Individual Transaction
• Include Process Reengineering

Module 3 / DLMS Program Management Plan
7
Table of Contents DLMS Migration Acceleration
Program Management Plan (PMP) Introduction Progra
m Benefits Successful Migrations 10 Steps to
Success Cost Estimates DLSS (MILS) to DLMS
Implementation Program Background Program
Responsibilities Core Team Program Implementation
Strategy Program Requirements Nomination
Information Criteria for Nominated
Projects Business Transformation Agency Review
Process Jump Start Milestones Monthly Status
Reports Metrics Funding Process MIPR
Submission PDC Submission Related Background
Information Risk Assessment DLMS Master Test
Plan Program Correspondence Policy Directives and
Related Documentation PMP Appendices Appendix A
through H
Defense Logistics Management System (DLMS)
Migration Acceleration Program Management Plan
(PMP)
Version 3.0 Revised May 11, 2008
Module 3 / DLMS Program Management Plan
8
Ten Steps to Success

• Jump Start Project Management Plan (PMP) (pg5)
• http//www.dla.mil/j-6/dlmso/Programs/DLMS/jum
  pstart.asp
• Assemble Team of functional and technical experts
  on the system to be migrated
• Initiate early contact with DAASC/other trading
  partners (e.g., DFAS, MOCAS, WAWF) DAASC POC is
  Clarissa Elmore, [phone] DSN 986-3770,
  email Clarissa.Elmore_at_dla.mil
• Develop a Performance Based Agreement (PBA) with
  trading partners and Authority To Operate (ATO)
• Acquire DAASC DLSS to DLMS X12 data maps for the
  transactions to be migrated
• Establish communications mechanisms with DAASC
  and determine what addressing will be used with
  DAAS

Module 3 / DLMS Program Management Plan
9
Ten Steps to Success (cont)

• Schedule DLMS training with DLMSO and acquire
  training
• Training courses can be requested by contacting
  DLMSO
• Ellen Hilert 703-767-0676, DSN 427-0676,
  Ellen.Hilert_at_dla.mil
• Select, acquire or develop an EDI or XML
  translator/parser
• Develop phased migration plan/schedule
• Pick a simple transaction first and do one at a
  time, reusing as much as possible for the next
  transaction
• Use EDI or XML translation software and DAASC
  logical data maps to map/parse data for
  incoming/outgoing DLMS transactions to or from
  legacy database or flat files

Module 3 / DLMS Program Management Plan
10
Ten Steps to Success (cont)

• Establish table driven DLSS or DLMS on/off
  switching mechanism to establish positive
  control, allow for phasing and fail safe fall
  back
• Test, Test, Test
• Establish loop back testing arrangement with
  DAASC. System sends DLMS to DAASC
  DAASC returns same document in DLSS format
  and/or vice versa for validation/verification.
• Conduct unit code testing on each transaction
  (test all conditions)
• Schedule and conduct integration testing with
  DAASC Trading Partners as feasible
• Schedule live cut over in increments,
  implementing few transactions at a time
  coordinating closely with DAASC

Module 3 / DLMS Program Management Plan
11
IMPACT ON TYPICAL SYSTEM - No Change to
Database, applications logic, internal system
messages only the entry exit programs must
be modified.
Legacy System Migration to DLMS Step 5, Phase I
- Modify System to receive and send DLMS
System transaction entry and exit program(s)
System Application n1
System Application n2
DLMS Incoming transaction
Database Or Flat Files
Database
DLMS Outgoing transaction
System Application n3
System Application nn
DLMS Trans
No Change
System transaction entry and exit program(s)
Module 3 / DLMS Program Management Plan
12
IMPACT ON TYPICAL SYSTEM - Changes may be needed
to database, application logic, and
internal system messages
Legacy System Migration to DLMS Step 5, Phase II
Teach System to use new DLMS data
System transaction entry and exit program(s)
System Application n1
System Application n2
Incoming transaction
Database Or Flat Files
Database
Outgoing transaction
DLMS Trans
System Application n3
System Application nn
Potential Change
System transaction entry and exit program(s)
Module 3 / DLMS Program Management Plan
13
Step 6. Pick a simple transaction first and do
one at a time, reusing as much as possible for
the next transaction.

• Transactions within a DLSS family
• Same first two characters of the Document
  Identifier Code (DIC)
• Data content nearly identical -- lots of
  reusability

Module 3 / DLMS Program Management Plan
14
Step 8. Establish table driven DLSS or DLMS
on/off switching mechanism to establish positive
control, allow for phasing and fail-safe fall
back DLSS/DLMS Switching Table (used for DSS)
Module 3 / DLMS Program Management Plan
15
Logistics Data Resource Management System
(LOGDRMS)
Module 3 / Corporate Services
16
Logistics Data Resource Management System
(LOGDRMS) - Before

• Individual localized implementations
• Service Unique Solutions
• Undisciplined, changing requirements
• Manpower Intensive
• Non Standard Processes
• Non Standard Definitions
• Multiple Contexts
• Multiple Syntaxes
• Limited Communication
• Sneaker-Net and Swivel-Chair inputs
• Questionable Content

DOD Services(e.g., USA, USAF, USN, USMC, Federal)
Application Developers(e.g., SAP, Oracle)
Application Interface Builders(e.g., IGC, IDE)
Content Administrators(e.g., DLMSO, DTEB, DDCOI,
Services)
Data Analysts(e.g., DORRA, LOGSA)
System Architects (e.g., DSS, Asset Visibility,
EBS)
17
Logistics Data Resource Management System
(LOGDRMS) - Current

• LOGDRMS Consists Of
• DLMS Data Element Dictionary/Directory
• Directory of DLMS Supplements
• Dictionary/Directory of DLMS Qualifiers
  Reference (Code) Tables
• Summary of Contents
• 67 ANSI X12 Formatted DLMS Supplements
• 213 ANSI X12 Data Elements
• 865 DoD Enterprise Level (Core) Logistics Data
  Elements
• 1900 DLMS Data Elements (Business Data Elements)
• 197 DLMS Qualifiers (Reference (code) Tables)
• Assorted Conversion Guides (Unit of
  Issue/Packing/Transportation)

DOD Services(e.g., USA, USAF, USN, USMC, Federal)
Application Developers(e.g., SAP, Oracle)
Application Interface Builders(e.g., IGC, IDE)
Data Analysts(e.g., DORRA, LOGSA)
System Architects (e.g., DSS, Asset Visibility,
EBS)
Content Administrators(e.g., DLMSO, DTEB, DDCOI,
Services)
18
DoD Corporate Services
Module 3 / Corporate Services
19
DoD Corporate Services

• Fully operational EB infrastructure
• Includes flexible and robust communications
• Supports a transitional DLSS/DLMS environment
• An efficient and effective organizational
  structure
• DoD corporate sponsorship
• Capable of overseeing implementation of
  commercial EDI
• Sustains the DLMS infrastructure

Module 3 / Corporate Services
20

• DLMSO Support to DLMS Implementers
• Functional and technical consultation
• Providing X12 implementation conventions and XML
  schemas
• Arranging trading partner meetings/teleconferences
  
• Testing assistance as required
• Facilitate coordination with DAASC trading
  partners
• Modification configuration management of DLMS
• Business Rules
• Transaction formats
• Metadata
• DLMSO Web site support
• Providing DLMS Training materials and classes

Module 3 / Corporate Services
21
DLMSO Training Support
DLMSO offers a two day DLMS training class. The
class is composed of 9 modules containing 455
training slides used in conjunction with a number
of class exercises and hand outs. Training
covers how to implement DLMS, 10 steps to a
successful implementation, available resources
and lessons learned. Since March 2007, DLMSO has
trained approximately 300 DoD Component
personnel Navy R-Supply Norfolk, VA March
27-28, 2007 Air Force ILS-S/SBSS Maxell-Gunter
AFB, AL April 24-25, 2007 Army LOGSA
LAISO Huntsville, AL June 13-14, 2007
DAASC Dayton, OH July 24-25, 2007 Marine
Corps MAISTER Albany, GA November 14-15, 2007
Navy ERP Annapolis, MD February 26 2008
DFAS Columbus, OH June 11-12, 2008 Air Force
ECSS Dayton, OH July 17-18, 2008 The following
DLMS training is in the planning phase
GSA Washington, DC April 28,
2009 GCSS-Army Petersburg, VA May 12-13,
2009 AF-ECSS (refresh) Dayton, OH TBD
22
DLMSO Support to DLMS Implementations

• DLMSO Management POCs
• Mr. DC Pipp [phone]/DSN 427-0670
  donald.pipp_at_dla.mil
• Major David Walker [phone]/DSN
  427-2611 david.walker_at_dla.mil
• DLMSO Functional Support POCs
• Ms. Ellen Hilert [phone]/DSN 427-0676
  ellen.hilert_at_dla.mil
• Ms. Mary Jane Johnson [phone]/DSN
  427-0677 mary.jane.johnson_at_dla.mil
• Mr. Bob Hammond (703) 767-767-2117/DSN
  427-2117 robert.hammond_at_dla.mil
• Ms. Heidi Daverede [phone]/DSN 427-5111
  heidi.daverede_at_dla.mil
• DLMSO Technical Transaction Support POCs
• Mr. Tommy Lyons [phone]/DSN 427-1481
  thomas.lyons_at_dla.mil
• Mr. Nat Obey [phone]/ DSN 427-2558
  nathaniel.obey.ctr_at_dla.mil
• Mr. Dale Yeakel [phone]/DSN 427-8632
  dale.yeakel.ctr_at_dla.mil
• Mr. Larry Tanner [phone]
  larry.tanner.ctr_at_dla.mil
• DLMSO Technical Metadata Support POCs
• Ms. Marva White [phone]/DSN 427-6296
  marva.white_at_dla.mil
• Mr. Joe Pipan [phone]/DSN 427-0753
  joseph.pipan.ctr_at_dla.mil

Module 3 / Corporate Services
23
DAASC Support to DLMS Implementations

• DAASC technical consultation and support for
• Set-up of new accounts, telecom protocols, and
  data protection schemes.
• Logical data mappings between DLSS, DLMS, and XML
• Coordination of integration testing with System
  PMO and trading partners
• Control and maintenance of customer profiles and
  routing tables.
• Coordination of integration testing with Service
  PM and trading partners.
• Evaluation of test results and assistance with
  problem resolution.
• Help Desk support for establishment of new
  trading partner connectivity, transaction
  tracking, trouble-shooting, and file
  recovery/resubmission.

Module 3 / Corporate Services
24
DAASC Support to DLMS Implementation

• DAASC DLMS eBusiness Program Management POCs
• Clarissa Elmore [phone]/DSN 986-3770
  Clarissa.Elmore_at_dla.mil
• Jennifer Taulbee [phone]/DSN 986-3400
  jennifer.taulbee_at_dla.mil
• Functional Support POCs/DAASC Logistics Division
  
• Army/GSA Pam Meredith [phone]/DSN
  986-3709 pamela.s.meredith_at_dla.mil
• Air Force/DLA Mark Minch [phone]/DSN
  986-3741 mark.minch_at_dla.mil
• Navy/Coast Guard/USMC Joanne Norman (937)
  656-3742/DSN 986-3742 joanne.norman_at_dla.mil
  
• DAASC Mapping Support POCs
• Doug Mummert [phone] doug.mummert.ctr_at_dl
  a.mil
• Bill Strickler [phone]
  william.strickler.ctr_at_dla.mil
• DAASC eBusiness Group (account set-up)
• Jordan Henderson [phone]/DSN 986-3804
  jordan.henderson.ctr_at_dla.mil
• Andy Rohrer [phone]/DSN 986-3805
  andrew.rohrer.ctr_at_dla.mil

Module 3 / Corporate Services
25
DLMS Operating Concept
Module 3 / Operating Concept
26
DLMS Operating Concept

• To avoid the trauma and expense of "turn-key"
  implementations, an incremental migration to
  DLMS is in progress
• DoD will operate in a mixed DLSS / DLMS
  environment for an undetermined period
• During the transition period, logistics systems
  will undergo modernization and process
  reengineering changes

Module 3 / Operating Concept
27
Transition to DLMS

• DLSS/DLMS conversion tables have been developed
  that allow conversion of data from DLSS to DLMS
  (ASC X12/XML) and vice-versa
• These conversion tables enable logistics business
  to be conducted in both environments
• DAAS will also translate between DLMS and
• Multiple versions of ASC X12 standards
• Other emerging standards when adopted as DoD
  standards
• Component User Defined File (UDF) formats (by
  exception)

Module 3 / Operating Concept
28
DLMS Operating Concept

• Conversion Operations

Module 3 / Operating Concept
29
Conversion Operations

• DAASC develops and performs configuration
  management of conversion maps
• DAASC uses a commercial any-to-any
  mapping software package that supports a
  robust conversion
• Components may use at will the format they
  possess DLSS or DLMS to initiate a
  transaction

Module 3 / Operating Concept
30
Conversion Operations

• DAASC incorporates and maintains a profile
  of organizations and specifies whether they are
  operating in DLSS and/or DLMS
• DLSS data elements are retained in the DLMS to
  support conversion
• DLMS enhanced data may not be supported in
  legacy/transitioning systems - coordination with
  DLMSO required

Module 3 / Operating Concept
31
Conversion Policy

• DoD Supply Chain Material Management Regulation
  (DoD 4140.1-R) states DAASC will be used for
  conversion services (see guidance beginning on
  page 162, Paragraphs C8.6.1.1.7, 8, 9, and 10).
• The guidance to the Components to use DAASC is in
  Paragraphs C8.6.1.2.2.1 and C8.6.1.2.2.2. This
  guidance states all transactions are to be sent
  through DAASC and use the DAASC DLSS and DLMS
  standards conversion support capabilities.

Module 3 / Operating Concept
32
DLMS Operating Concept

• Translation Processing

Module 3 / Operating Concept
33
Translation Processing

• In the old DLSS environment, data is exchanged
  in a series of more than 450 fixed-length,
  80-position record transactions
• To generate these transactions, Component
  logistics systems
• Extract data from the appropriate module
• Format the record
• Pass it through DAAS
• The recipient then edits and formats it into
  the receiving application system

Module 3 / Operating Concept
34
Translation Processing continued

• The EDI translator converts data to the DLMS
  format and sends it to DAAS
• The translator also performs a number of other
  functions, including maintaining
• Telecommunications data
• Archiving messages
• Processing errors

Module 3 / Operating Concept
35
The following general rules apply

• Transaction generation programs edit data to
  ensure it adheres to DLMS policy and data
  element standards, as well as ASC X12 syntax
  rules
• Translators group one or more of the same
  transaction sets into a single EDI group and
  envelope
• Initiating systems archive sent messages for no
  less than 90 days to ensure communication
  failures do not lead to loss of transmitted
  data
• Initiators create additional copies for
  recipients not identified in the
  transaction as an addressee or not
  previously specified in DAAS instructions

Module 3 / Operating Concept
36
Transaction Routing

• DAAS is the central hub for routing most DLMS
  transmissions copies transactions and
  routes them to recipients according to DLMS
  procedures. Specialized routing is by
  agreement.
• Components and participating civil agencies can
  establish their primary routing link to the
  BTA GEX sites, which in turn forwards
  transactions to the DAAS GEX for logistics
  processing.
• Conversely, the DAAS GEX will forward acceptance
  report transactions to the BTA GEX which
  supports the mapping into the Wide Area
  Workflow Receipt and Acceptance (WAWF-RA)
  processing system.

Module 3 / Operating Concept
37
Transaction Routing continued
Systems may connect directly or via commercial
VANs
Civil Agencies
DoD Agencies
GEX
LOTS
DAAS
BTA
Commercial VANs
Connection to other DoD corporate databases
DAAS can connect to commercial logistics trading
partners either directly or through the trading
partners Value Added Networks (VANs).
Commercial organizations participating in DoD
logistics
Module 3 / Operating Concept
38
Transaction Routing continued

• Central hub function includes capability to

• Archive transactions
• Open messages and conduct standard or
  recipient-specific edits
• Copy transactions in the DAAS Logistics
  On- Line Tracking System (LOTS) and route
  them to other DoD databases

Module 3 / Operating Concept
39
Transaction Routing continued

• Central hub capabilities continued
• Group transactions that are bound for the same
  destination
• Forward newly grouped envelopes to recipients
  and archive outbound messages
• Forward messages outside the DoD
  telecommunications network to civil agencies,
  commercial Value-Added Networks (VANs), and
  trading partners

Module 3 / Operating Concept
40
Lessons Learned

• Incorporate into your design an On/Off switch
  (table) for all outbound transactions down to the
  3 character DIC DAASC controls your inbound
• Allows control over when and what is migrated
• Allows transactions to be reversed if problems
  occur
• Start work on the Performance Based Agreement
  (PBA) and Authority to Operated (ATO) immediately
  
• Plan to exchange all transactions with all
  trading partners exclusively via DAASC (100)
• Begin discussions with DAASC pertaining to
  intentions, transmission protocol, design, and
  interface testing
• Do NOT try to migrate too many transactions at
  one time!

Module 3 / Lessons Learned
41
Lessons Learned (cont)

• Request DAASCs DLSS to DLMS translation maps
• Scrutinize every piece of data within your DLSS
  transactions to ensure it is accommodated within
  the respective DS and DAASC map (may need to
  request change - PDC)
• Design to incorporate DLMS processing into your
  actual application functionality to enable future
  expansion data capabilities
• Determine which new capabilities you want to
  incorporate into your applications
• Design and develop your system and conduct
  thorough and extensive unit, system and
  interface testing with DAASC

Module 3 / Lessons Learned
42
Lessons Learned (cont)

• Do NOT rely solely upon documentation for data
  formats and validate the data in your MILS
  transactions
• Large samples are best
• They expose more transaction scenarios
• Allow for a fuller view of possible data
  combinations that your system produces

Module 3 / Lessons Learned
43
Module 3 Quiz

• Question 1 Which of the following is not one of
  the 10 steps to a successful DLMS implementation?
• Assemble team e) Establish early relationship
  with DAASC
• Schedule training f) Acquire
  translator/parser
• Develop phased plan g) Cross fingers
• Test, test, test h) DLSS/DLMS on/off
  switching table
• Question 2 PRC processes proposed changes that
  might impact DLMS procedures and DLMS supplements
  to the federal Implementation Conventions.
  However, coordination outside the PRC membership
  is required when changes impact a broader area to
  include
• Federal or DOD policy d) All of the above
• ASC X12 standards e) None of the above
• Federal ICs
• Question 3 Under the DLMS operating concept,
  DAASC can support data translation,
• which of the following is not supported?
• a) Component User Defined File (UDF) formats
• b) English to Spanish
• c) Multiple versions of the ASC X12 standards

Module 3 / Quiz
44
End of Module 3