1 / 23

Defense Logistics Management System (DLMS) Supporting the Warfighter Today and the

Defense Logistics Management System (DLMS) Supporting the Warfighter Today and the The Future Logistics Enterprise Tomorrow. http://www.dla.mil/j-6/dlmso/. DLMS Purpose/Mission. Business Process Transformation. Process Reengineering. Business Management Modernization Program.

cady
Télécharger la présentation

Defense Logistics Management System (DLMS) Supporting the Warfighter Today and the

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Defense Logistics Management System (DLMS) Supporting the Warfighter Today and the The Future Logistics Enterprise Tomorrow http://www.dla.mil/j-6/dlmso/

  2. DLMS Purpose/Mission Business Process Transformation Process Reengineering Business Management Modernization Program Agile Combat Support Net-Centric Operations Standard Financial Information Structure SUPPLY CHAIN INTEROPERABILITY Best Business Practices UID/RFID Performance Based Logistics Focused Logistics Enterprise Architecture Information Superiority 2

  3. DLMS Mission • Business Process Transformation & Interoperability • Facilitate enterprise integration and continuous process improvements to logistics management and operations while maintaining interoperability by: • Developing business rules that implement DoD policy • Developing and managing the DoD logistics information exchange infrastructure • Publishing detailed procedures that identify who does what, when, and how along the DoD logistics chain: • Organizational responsibilities • Metrics • Information exchange formats • Standard data elements and codes 3

  4. Enabling Interoperability Data Providers & Data Consumers Demand & Supply Planning Sourcing/Procurement/Contract Admin Core Business Mission Areas Billing & Payment Materiel Supply & Service Management Distribution DLMSO delivers the business rules, transactions & data standards DAASC delivers the routing, translation, archiving, metrics Weapon Systems Management Financial Management Requirements Determination Real Property & Installations Mgnt Human Resources Management 24 x 7 Challenge: To Connect Core Business Mission Areas & DoD Enterprise Data Providers & Data Consumers 4

  5. InteroperabilityFramework • Business Policy: A required outcome – Property stewardship • Business Process: An assemblage of business rules that • collectively form a process -- Physical Inventory Management • Business rule: States what must or must not be done • Storage Activities must report the ending on-hand • inventory balance to the item owner for all items having • any balance effecting business activity that day. • Business Object: A collection of data in a specified format • that launches a business process or reports process results • An order, inventory adjustment, request for payment, etc. • Business Metadata: Data element characteristics • Inventory Balance Date = 8 numeric characters (yyyymmdd) 5

  6. Key DoD Governing Policies • Wynne 22 Dec. 2003, Memo, Migrate to DLMS, Eliminate MILS • DLMSO 5 Jan.2004, Memo, Migrate to DLMS, Eliminate MILS • DoDD 8190.1, DoD Logistics Use of EDI Standards: • Assigns DLMSO as DoD Executive Agent for logistics data interchange • Establishes ANSI ASC X12 as DoD standard for logistics system interchanges: • All new systems • Major modifications to existing systems • DoDD 4140.1 Materiel Management Policy • Authorizes publication of DoD business rules and standards • DoD 4140.1-R Materiel Management Regulation • “Loaded” with DLMSO responsibilities, policy, procedure, and guidance • DoD 4000.25 series of Manuals covering both the DLMS and DLSS/MILS (8K pages) • Prescribes logistics management policy, responsibilities, procedures, rules, and electronic data interchange and data standards Business rule and standard operational development and implementation are well grounded in DoD policy 6

  7. Migration From MILS To DLMS • What are the MILS Transactions? • DoD unique EDI standard developed 40 years ago • Fixed length (80 positions) transactions (over 500 types) • Each transaction contains fixed length data fields • Technically obsolete • Serious constraint to business process improvements • Can not support UID and RFID data exchange requirements • 11 million daily computer-to-computer exchanges via DAASC 7

  8. Migration From MILS To DLMS • What are the DLMS Transactions? • Commercial EDI standard based transactions • ANSI ASC X12 EDI implementation conventions (ICs) • W3C compliant XML schemas • 57 X12 EDI ICs and XML schemas support all MILS functionality • Variable length transactions and data fields • Flexible enough to meet all current & DoD future business • information requirements – supports UID and RFID • 1/2 million daily computer-to-computer exchanges via DAASC 8

  9. New DLMS Functionality • DLMS transactions reflect functionality derived from multiple sources • MILS as currently implemented • Backlog of approved changes with full Component implementation pending (due to lack of resources & competing priorities) • Enhanced capabilities • Enhancement data call to Components – require prior coordination for use • ASC X12 standards-based enhancements • DLSS/DLMS approved changes • Integration of Component unique requirements • New functionality supporting ERP implementation • New functionality supporting DoD initiatives, e.g. UID & RFID 9

  10. ASC X12 Standards-Based Enhancements • 8 digit dates throughout • Multiple transactions • Longer data elements: quantities, reference and identification numbers • Repeating data elements • Transmission date/time • Flexible & clear text addressing • Codified addressing capability expanded: • DoDAAC, RIC, CAGE, DUNS, DUNS+4, MAPAC • Full line of accounting as discrete data • Etc., Etc. 10

  11. DoD Vision for Unique Item Marking • 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 (UID) tangible items will facilitate item tracking in DoD business systems and provide reliable and accurate data for management, financial, accountability and asset management purposes. http://www.acq.osd.mil/dpap/UID/ 11

  12. UID Role In The 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 12

  13. DoD RFID Enabled Supply Chain 13

  14. UID, RFID, & DLMS Relationship • The UID 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 Bottom line: UID, RFID, and DLMS compliment each other in providing business event intelligence across the supply chain 14

  15. DLMS XML DLMS XML Strategy • Provide the DLMS with an immediate XML capability • Standard set of XML schemas equivalent in data content to DLMS X12 EDI • Purchase or develop tool to quickly generate XML schemas from X12 EDI • Assure backward interoperability to legacy MILS systems • Maintain constant synchronization of DLMS X12 EDI and XML schemas • Simplify configuration management of standards and DAASC maps • Work through ANSI to develop long term DLMS XML capability based on CICA • Provide transparent translation between initial DLMS XML & CICA DLMS XML • 57 DLMS XML schemas have been developed and placed in the DLIS repository • All approved schemas/maps have been build into the Mercator translator by DAASC. • It takes approximately 2 weeks per IC to develop and test. 15

  16. DLMS XML • The Advantages of the DLMSO approach are: • Provides immediate XML capability • Standard across logistics community, no mediation among multiple XML schemas required • Assured interoperability to DLMS X12 EDI • Simplified configuration management of the two, since the XML is derived from the EDI via COTS • Allows developers to use either or both dependent on requirements, DAASC customer profiles/translation • Development and maintenance at no cost to user. 16

  17. Migration From MILS To DLMS WHAT’S DIFFERENT? WHAT’S THE SAME? Supply Chain Transaction Flow Same Information Different Transport Standards Provider/ User User/ Provider IDOC ASC X12 MILS XML D A A S C D A A S E G A T E ST*940*0001 W05*N*Z****NA N1*Z4**M4*SMS**FR G62*07*20021001*W*104052 LX*1 W01*1*EA**FS*4820011138224 N9*97*1 N9*TN*FB581922720404 AMT*LI*93558.27 N1*SB**M4*AN5**TO N1*Z1**10*FB5819 N1*BS**10*FB5819 LM*DF LQ*0*A51 LQ*DE*A LQ*DF*S LQ*83*A LQ*AK*01 LQ*AL*999 LQ*A9*Y1G200 LQ*A1*A LQ*78*9BU LQ*79*02 FA1*DY*D340 FA2*B5*6C SE*27*0001 Code Card Column Data Element A51 1-3 Document Identifier AN5 4-6 Routing Identifier S 7 Media and Status 4820011138224 8-22 Stock Number EA 23-24 Unit of Issue 0001 25-29 Quantity FB581922720404 30-43 Document Number 44 Blank Y1G200 45-50 Supplementary Address A 51 Signal 6C 52-53 Fund 01 54-55 Distribution 56 Blank 9BU 57-59 Project 02 60-61 Priority 999 62-64 Required Delivery Date 65-66 Blank SMS 67-69 Date Receipt of Requisition A 70 Ownership A 71 Supply Condition 72-73 Blank 0093558 74-80 Unit Price E1DEDL20 # 1 (HIERARCHY LEVEL # 2) VSTEL = AN5 E1ADRM1 # 6 (HIERARCHY LEVEL # 3) NAME1 = FB589 E1ADRM1 # 7 (HIERARCHY LEVEL # 3) NAME1 = FB5819 E1ADRM1 # 8 (HIERARCHY LEVEL # 3) PARTNER ID = AN5 E1EDL24 # 18 (HIERARCHY LEVEL # 3) MATNR =011138224 E1EDL24 # 18 (HIERARCHY LEVEL # 3) MATWA =011138224 MATKL = 4820 WERKS = AN5 LGORT = AA LFING = 1.000 VRKME = EA LOMNO = 1.000 MEINS = EA Z1SV_Z1ED # 19 (HIERARCHY LEVEL # 4) ZZDOC_ID_ = A51 ZZMEDIA_ST_ = S ZZORIG_DO_ = FB581922720404 ZZSUPP_AD_ = Y16200 ZZSIG_CD- = A ZZFUND_CD_ = 6C ZZDISTR_CD_ = 01 ZZPROJ_CD_ = 9BU ZZPRI_CD_ = 02 ZZNON_STD_ CD = 999 ZZRIC_FROM = SMS E1EDL26 # 21 (HIERARCHY LEVEL # 4) MATKL = 4820 Element-329>0001</Element-329 Element-67>SMS</Element-67 Element-355>EA</Element-355 Element-234>4820011138224</Element-234 Element-127>FB581922720404</Element-127 Element-782>93558</Element-782 Element-67>AN5</Element-67 Element-67>FB5819</Element-67 Element-1271>A51</Element-1271 Element-1271>S</Element-1271 Element-1271>A</Element-1271 Element-1271>01</Element-1271 Element-1271>999</Element-1271 Element-1271>Y1G200</Element-1271 Element-1271>A</Element-1271 Element-1271>9BU</Element-1271 Element-1271>02</Element-1271 Element-1195>C6</Element-1195 Element-329>0001</Element-329 Data transfer media may change, but the data & sender/receiver rules do not. 17

  18. DAASC eBusiness Initiatives/Customers: DAASC tasked in Fall of 1992 by DoD Executive Agent to provide: • A gateway for distribution of EDI documents that would: • Standardize implementation and avoid duplication of effort/expense • Implement DoD standard for interoperability • Connectivity to multiple commercial value-added networks (VANs) • An interface between procurement activities & their vendors/transporters/government contractors • Enhancement of procurement systems 18

  19. Suppliers Defense Logistics Agency Military DAAS Services General Services Admin. DAAS Transactions: Commercial • DLSS (MILS) • DLMS (X12) • DLMS (XML) • UDF Suppliers Business Rules and StandardsReceive, Validate, Edit, Route, & Transmit DAASC delivers the ability to receive and transmit logistics data across various networks, supporting numerous protocols and formats. This communications interoperability minimizes the number of interfaces that the DoD Components must maintain for the exchange of logistics data. DAASC maintains a history of all transactions processed/routed to support supply chain analysis. Customers Transaction Volume (CY 2004): 4,681,959,693 CY 2003 – 4,185,551,967 DLSS/DLMS CY 2002 - 3,360,566,729 DLSS/DLMS • DoD • Departments of: • Army • Navy • Air Force • Marine Corps • USTRANSCOM 97% of workload 193,235 Activities WORLDWIDE • Defense Agencies • Intelligence • DoD Dependent • Schools • NATO • FMS Countries Mapping & Translation Services Routing and Transmission Services Civilian • Departments of: - Commerce - State - Justice - Transportation 3% of workload • FEMA • USPS • GAO • CG • SUPPORT SERVICE / AGENCY CONTINGENCY OPERATIONS • OFFICIAL REPOSITORY & DISTRIBUTION POINT FOR DoD DIRECTORIES • LOGISTICS RESPONSE & CUSTOMER WAIT TIME REPORTING • NASA • GSA • FAA • VA 19

  20. Develop Transaction Maps DAASC Mapping and Customer Bases: • DAASC has developed and maintains 550+ translation maps. • Mercator maps are developed and maintained outside of the DEBX by DAASC. This reduces the dependency on contractor support for revisions to maps supporting critical DoD production systems. DISA relies on Northrop-Grumman IT (NGIT) to develop and issue version updates to their maps. • DAASC maps support DoD Services and Agencies, as well as Federal and State Activities and FMS 20

  21. DAASCeBusiness Services • Standard sorting, routing, and delivery by X12 ISA and GSA • envelope segments • Customized sorting/grouping and delivery of documents, for special • programs and projects, by X12 document type, VAN, TP, prime • vendor, or DoD activity • Delivery by TCP/IP (FTP/SMTP), MQ-Series, and dial-up • (Async/PPP) modem protocols. • Data security by HTTPS, SFTP, SSL,SCP, Compress, PGP, and • VPN • Full auditing and archiving functions with data on-line for 30 days • and archived for at least 2 years. • X12, MILS, UDF, IDOC, and XML transaction mapping/ • translation and consultation services. • Recovery and retransmission of documents • Establishment of new TP agreements and interconnects with VANs. 21

  22. Migration From MILS To DLMS What help is available to assist in migration • DLMSO & DAASC • Functional and technical consultation • DoD Training • DAASC mappings between MILS and DLMS data available to DoD sponsor • Test Transactions • Coordinate system-to-system testing • DLA & USAMMA experience & lessons learned • DLMSO Web Site http://www.dla.mil/j-6/dlmso/ 22

  23. Where To Find The DLMS Transactions • DLMSO Web Site PDF • DLMS X12 http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/x12.asp • DLMS XML Schemas • http://www.dla.mil/j-6/dlmso/eLibrary/TransFormats/xml.asp • DLMSO Web Site Links To: • DoD XML Repository http://xml.dod.mil/xmlreg/user/index.cfm • DLIS XML Resource Library (XRL)https://www.dlis.dla.mil/xrl/ 23

More Related