1 / 14

UID/DLMS Migration Workshop, Washington DC, 9-10 March 04

DSS DLMS Migration. UID/DLMS Migration Workshop, Washington DC, 9-10 March 04. Presented by Mr. Jeff Charlesworth jcharlesworth@dsdc.dla.milIT Chief DLA Systems Integration Office, DSIO-U. Agenda.

fritzi
Download Presentation

UID/DLMS Migration Workshop, Washington DC, 9-10 March 04

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. DSS DLMS Migration UID/DLMS Migration Workshop, Washington DC, 9-10 March 04 Presented by Mr. Jeff Charlesworth jcharlesworth@dsdc.dla.milIT Chief DLA Systems Integration Office, DSIO-U

  2. Agenda • Background on DSS and DLMS • The DSS Approach to DLMS • Challenges and Lessons Learned

  3. Background • Distribution Standard System (DSS) • Standard system performing wholesale logistics for the Defense Logistics Agency • Supports the mission of the Defense Distribution Center • Interacts with many DoD logistics systems including BSM, SAMMS, UICP, UADPS-2, LMP CCSS, AMCISS, D035K, LOGSA, FLIS, etc

  4. Background Cont. • Distribution Standard System (DSS) • Sends out approximately 1.5 million transaction per day • Receives approximately 500,000 transaction per day

  5. DSS’s Need For DLMS • Navy requested that DLA be able to receive, store and issue material by a Unique Item Identifier (UII/serial number) • The size of this number is thirty positions, and needed to be recorded in transactions such as the Due In, Shipment Status, etc • DLMS was the most viable solution

  6. Preliminary Steps to DLMS • Identified all MILs transactions • Identified the DLMS equivalent • Worked with DLMSO and the DLMSO Implementation Convention for data placement • Worked with DAASC for Logical Data Maps

  7. Former MILS Processing DAASC DAASC MADS and MQ Series DSS Processing DSS Entry Outbound MILS transactions MILs Transactions Files for DSS

  8. DLMS Inbound Processing DAASC MQ Series Single X12 DLMS Transaction DSS Inbound DLMS queue Build PMRs Parse Data DFT and RDT 527D Route Transactions Feed to MRO Processing 940R Parse Data DFT and RDT 856N Build Receipt Info DFT and RDT Parse Data

  9. DLMS Outbound Processing 856S Build 856S DSS Processes XML Outbound queue 945A Build 945A 140B Build 140B Process Transactions X12 or XML? DLMS Store data on DFT/RDT DLMS or MADS? DAASC Build 527R 527R 867I Build 867I MADS DAASC Process as today X12 Outbound queue 947I Build 947I

  10. DAASC Processing DAASC Convert to XML or X12. Yes Routing to DLMS Customers? DLMS Customer No Convert to MILS MILS Customer

  11. Challenges • Planning • Amount of Detail is Time Consuming • Testing Presents Challenges • Standardization of XML Implementation Convention

  12. Lessons Learned • Create a table driven DLMS/MILs On/Off Switch • Detailed Requirements Analysis Upfront • DLMSO and DAASC are key • Trading Partner Coordination

  13. DLSS Formats Converted

  14. DLSS Formats Converted

More Related