Defense Logistics Management System - PowerPoint PPT Presentation

1 / 46
About This Presentation
Title:

Defense Logistics Management System

Description:

Hierarchy of Relationship. ASC X12 Transaction Set. Federally Approved IC. business ... the supplemental address, or the fund code (also identifies a free issue) ... – PowerPoint PPT presentation

Number of Views:28
Avg rating:3.0/5.0
Slides: 47
Provided by: dla
Category:

less

Transcript and Presenter's Notes

Title: Defense Logistics Management System


1
Defense Logistics Management System
(DLMS)Electronic Data Interchange (EDI)
2
Topics Discussed
  • Federal Implementation Conventions (ICs)
  • DLMS Supplements to the Federal ICs
  • DLMS Supplement to the Federal 511R IC
  • DLMSO Web Site Navigation

3
Objectives
  • Students will gain basic understanding of
  • The purpose and content of the Federal ICs used
    in the DLMS
  • How DLMS Supplements are used to support DLMS
    implementation
  • How to read a DLMS Supplement
  • How to navigate the DLMSO Web Site

4
Federal Implementation Conventions
5
Hierarchy of Relationship
  • ASC X12 Transaction Set
  • Federally Approved IC

business specific interpretation
6
Approved ICs
  • All ICs supporting DLMS implementation are
    Federally or DoD Approved
  • Define the structure and content of an ASC X12
    EDI standard transaction as it pertains to a
    particular usage
  • Map application data requirements into specific
    data fields within the transaction set
  • Establish the parameters for the corresponding
    DLMS Supplement

7
DLMS Supplements Supporting Use of Federal ICs
8
Hierarchy of Relationship
  • ASC X12 Transaction Set
  • Federally Approved IC

9
DLMS Supplements to Federal ICs
  • DLMS supplements to Federal ICs (along with
    the DLMS manual) constitute DoD's trading
    partner agreement for use of the Federal ICs
    within the DoD logistics process
  • DLMS supplements incorporate detailed
    information which would fall outside the
    scope of Federal ICs - - but which is
    necessary for a successful, coordinated
    implementation

10
Content of DLMS Supplements
  • The DLMS Supplements mirror the approved Federal
    ICs and include
  • Federal IC notes (as applicable)
  • DLMS notes Detailed DLMS business rules - the
    Supplements accept or prohibit options and often
    add conditions to the use of optional data
    within DoD logistics
  • Key transition guidance governing operation in a
    mixed DLSS/DLMS environment

11
Transition Guidance
12
Streamlining Goals
13
Codes Targeted for Streamlining (Example)
  • Signal Code
  • Acts as a pointer indicating ship-to and bill-to
    activity as conveyed by the document number,
    the supplemental address, or the fund code
    (also identifies a free issue)
  • Under DLMS Replaced by specific identification
    of each organization within address segment
    using flexible addressing as appropriate (free
    issue is identified independently)

14
DLMS Supplement Notes
  • DLMS Business Rules
  • DLMS Enhancements
  • Field Size Constraints
  • Streamlined Data
  • Approved DLMS Changes

15
Example 1 DLMS Business Rules
Notes delineate appropriate functional
application for a particular transaction
DLMS Supplement
Federal IC
16
Example 2 - DLMS Enhancement
  • Data associated with a DLMS enhancement may
    not be received or understood by the
    recipient's automated processing system
  • DLMS procedures may not have been developed
  • Components must coordinate requirements and
    business rules with DLMSO prior to use

DLMS Supplement
17
Example 3 - Field Size Constraints
  • Data elements which have an expanded field
    size above existing DLSS capability may not
    be supported by the recipient's automated
    processing system
  • Components must coordinate implementation with
    DLMSO prior to use.

DLMS Supplement
18
Example 4 - Streamlined Data
  • DLSS data is retained in the DLMS for a
    transition period to support transaction
    conversion in a mixed DLSS/ DLMS
    environment
  • This data will be streamlined out once full
    DLMS implementation is reached
  • Components may coordinate with DLMSO for early
    termination (or retention) of specific data
    requirements for users operating in a
    full DLMS environment

DLMS Supplement
19
Example 5 - Approved Change
  • Data associated with an Approved Change
    may not have an established
    implementation date.
  • This data may not be received or
    understood by the recipients
    automated processing system.
  • Components must coordinate
    implementation with DLMSO prior to use.

DLMS Supplement
20
Example 6 Repetition of Data
  • Repetition of data is not compatible
    with existing DLSS/DLMS capability.
  • This data may not be supported by the
    recipients automated processing system.
  • Components must coordinate implementation
    with DLMSO prior to use.

DLMS Supplement
21
Example 7 Authorized Enhancement
  • Data associated with an Authorized
    Enhancement should be included as part
    of the modernization when applicable.
  • Inclusion of this data should not cause
    an inappropriate rejection of the
    transaction.
  • Prior coordination with DLMSO is not
    required prior to use.

DLMS Supplement
22
DLMS 511R, Requisition
  • Basic Functionality
  • Standard and non-standard material
  • Government-furnished material (GFM)
  • Security Assistance
  • Passing orders
  • Referral orders

23
DLMS Enhancements
  • Transaction set preparation date/time
  • Supply condition code
  • Unit Price/Total Dollar Value
  • Utilization code
  • Special requirements code
  • Shipment Status
  • Points of contact
  • Remarks
  • Detailed line of accounting components
  • Associated special program requirement
    transaction number

24
DLMS Enhancements (cont)
  • Expanded item identification
  • Weapon system designator code
  • Quantity stratified by weapon system and
    demand code
  • Reason for requisitioning code
  • Party(ies) to receive status DoDAAC
  • Mark-for-Party
  • Unique item identification information
  • Clear text exception ship-to location

25
DLMS Enhancements Applicable to Non-Standard
Material
  • Supporting Document No.
  • Color
  • Drawing Revision No.
  • Catalog Number
  • Series Identifier
  • Model Number
  • Figure Number
  • General Specification No.
  • Manufacturers Name
  • Process Number
  • Publication Number
  • Dimension/Measurement
  • Material Description
  • Potential Source of Supply
  • End Item Manufacturer

26
Overview of DLMS Supplement to the Federal 511R IC
27
DLMS 511R, Requisition
Transaction Set Segments
ST Transaction Set Header BR Beginning Segment
for Material Management Identifies type of
transaction N1 Name Identifies organization
originating the transaction G61 Contact
Identifies a person to whom communication
should be directed LX Assigned Number Marks
start of detail loop each loop represents a
new requisition
28
DLMS 511R, Requisition
Transaction Set Segments - continued
N9 Reference Identification Identifies
document number and various supporting
information P01 Baseline Item Data Identifies
quantity ordered and provides enhanced
material identification DD Demand Detail
Stratifies quantity ordered by demand type and
weapon system GF Furnished Goods and
Services Identifies authority for contractor
requisitioning of GFM
29
DLMS 511R, Requisition
Transaction Set Segments - continued
G62 Date/Time Specifies pertinent dates and
times LIN Item Identification MEA
Measurements G69 Line Item Detail- Descrip
tion NTE Note/Special Instruction
Narrative exception data when manual
intervention needed
Provides detailed descriptive data for
nonstandard material
30
DLMS 511R, Requisition
Transaction Set Segments - continued
LM Code Source Information LQ Industry
Code
Identifies DoD code source and the specific
applicable code, e.g. project code, advice code,
or priority designator code -- capacity almost
limitless
31
DLMS 511R, Requisition
Transaction Set Segments - continued
N1 Name N2 Additional Name Information N3
Address Information N4 Geographic Location
Identifies specific parties by type of
organization, e.g. ship-to, bill-to, status
recipients. Allows various identifying codes or
clear text address.
32
DLMS 511R, Requisition
Transaction Set Segments - continued
REF Reference
Identification N9 Reference
Identification N1 Name FA1 Type of
Financial Accounting Data FA2 Accounting
Data SE Transaction Set Trailer
Supports unique item identification Specifies
line of accounting data
33
DLMS 511R, Requisition
ST51100000001 BR00A020000729131708 N1O
B10FB2300FR LX1 N9TNFB230093070001 PO11
EAFS5910001234567 DDR74 LMDF LQ802A LQ
0A0A LQAL777 LQDF2 LQDEA LQ78XZZ
LQ7902 LQA9YBLDG1 LQAKF N1Z4M4S9ETO N1
Z110FB2060 N1Z110FD2040 N1BS10FB2300 F
A1DYD340 FA2B5KZ SE2400000001
34
DLMS 511R, Requisition Supplement
Refer to hard-copy DLMS Supplement for a closer
look.
35
Want more information about the DLMS?
Check out the DLMSO web site
www.dla.mil/j-6/dlmso
36
Easy Access To
  • Latest published DLSS DLMS manuals
  • DLMS Supplements to Federal ICs
  • DLMS XML Schemas
  • Process change documentation
  • Committee information
  • DLMS Dictionary
  • Link to Logistics Functional Data Administration
    web site
  • Link to DLMS training
  • Access changes (.gov/.mil)
  • And more worth exploring!!!

37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
End of Module 5
43
(No Transcript)
44
(No Transcript)
45
(No Transcript)
46
Questions
Write a Comment
User Comments (0)
About PowerShow.com