DLMSO/DAASC November 2006 - PowerPoint PPT Presentation

slide1 l.
Skip this Video
Loading SlideShow in 5 Seconds..
DLMSO/DAASC November 2006 PowerPoint Presentation
DLMSO/DAASC November 2006

play fullscreen
1 / 9
Download Presentation
sharis
Views
Download Presentation

DLMSO/DAASC November 2006

Presentation Transcript

  1. Defense Logistics Management Standards Office Supply PRC Meeting DLMSO/DAASC November 2006 DLMS Bridge Middleware October, 2007 DLMSO 703-767-0600

  2. Today: System and Data Flow Complexity – Combined with the Challenge of Connecting New and Legacy Systems TRANSCOM Systems DLA Systems Service Systems Consolidation/ Deconsolidation

  3. Problem: How can new business systems (such as Passive Radio Frequency Identification) exchange data with legacy systems? The depot sends a shipment to Post 123. The 856S (DLMS) for the shipment is created and sent to DAASC. The legacy AIS at the receiving installation cannot use this data-rich DLMS transaction. 1 Post 123 Passive RFID System & software (EDI) Legacy AIS (MILS) How do you exchange business data about the shipment locally with incompatible systems? Post 123’s’s PRFID system reads the RFID tag as the shipment passes through the Passive RFID system 4 2 The tag data is collected and processed through the PRFID software; this data cannot be exchanged or processed by the local Legacy AIS in its current form. 3

  4. DLMS Bridge Concept: Transaction data cannot flow between certain incompatible DOD systems. The DLMS Bridge can “translate” the data for immediate use between these systems w/o significant effort or cost. Manufacturers/Vendor Suppliers DoD Enterprise Logistics Systems WAWF DLMS – 856A GEX Shipper Material Relevant Data Information Databases (AV, LOTS, etc.) DAAS Distribution Centers/ Depots Suppliers DLMS-856S 856, etc. DLMS or MILS determined by customer system profile Tagged Material MILS Other Trading Partners New system (e.g., RFID) DLMS Bridge Legacy System (e.g., LOG AIS) Updates for NICP, Requisition Activities, USTRANSCOM, LOGSA, Services, etc. EDI / XML Data MILS AE_, AS_, DF_ Example: DoD Facility with a legacy system that cannot accept EDI transactions; DLMS migration is not imminent.

  5. DLMS Bridge Middleware • Converts DOD transactions of one type or source into another type or source (e. g., MILS to DLMS, DLMS to MILS, EDI to DLMS, etc.). • Handles Passive RFID registration and visibility transactions. • Supports enterprise reporting needs (IUID, LOTS, Asset Visibility, etc.). • Connects Passive RFID and legacy systems such as the Automated Manifesting System-Tactical (AMS-TAC), Cargo Movement Operation System (CMOS), Standard Army Retail Supply System (SARSS), etc. • Accommodates user output requirements other than DLMS or MILS (e.g., flat files, “data sets”, user defined files (UDF), XML, Optical Memory Card (OMC) files, etc.). • Simple, flexible architecture with central configuration management.

  6. DLMS BRIDGE Architecture Install & Setup (User selects the New and Legacy System interfaces - via Drop Down Menus - for site installation) Business Rules (Library of Business Rules Applicable to Site, Business Processes, Legacy Systems, or any Service Specific Rules) Communications Interface (Expandable Library of Application Program interface Plug-In Or Connectors to Legacy Systems and DAAS) Translation Maps An Expandable Library of Maps: DLMS to MILS, DLMS to UDF, MILS to DLMS, UDF to DLMS etc. (e.g., 856S, 856A, 858, 527, UDF, OMC file or others as needed) System Interface (Expandable Library of System Specs & Interfaces) Legacy Systems and DAAS New System Input Transaction Database (tailored to work with many databases such as SQL Server, Oracle, SyBase, DB2, MS Access, etc.) Flexible Technical Architecture: Modular Construction, Hardware Independent, JAVA-based Code, Multiple O/S (Win XP & Linux so far), Centralized Configuration Management

  7. USMC Passive RFID Pilot- with DLMS Bridge • The USMC DLMS Bridge has been integrated into the USMC Passive RFID software solution (named “EasyRFID”) for use at Camp Lejeune. • The USMC DLMS Bridge processes tag reads, reader registration data, and visibility data (ADC 219); sends the transaction data to DAASC (USMC Pilot Phase 1). • The USMC DLMS Bridge also processes OMC files, 856S and 858R transactions; interfaces with AMS-TAC (Pilot Phase 2). • USMC Passive RFID pilot supports both the Supply Management Unit (SMU) and Traffic Management Office (TMO).

  8. USMC DLMS Bridge: Provides shipment data (856S) and selected transportation data (858R) for use with certain legacy DOD systems. The DLMS Bridge “translates” the DLMS and EDI data for immediate use in the AMS-TAC system (in a legacy system OMC file format). Manufacturers/Vendor Suppliers DoD Enterprise Logistics Systems WAWF GEX Shipper Material Relevant Data Information Databases (AV, LOTS, etc.) DAAS Distribution Centers/ Depots Suppliers X12 – 858 DLMS-856S DLMS 856S, 858R, etc. DLMS or MILS determined by customer system profile Tagged Material MILS Other Trading Partners Passive RFID System USMC DLMS Bridge AMS-TAC System Updates for NICP, Requisition Activities, USTRANSCOM, LOGSA, Services, etc. EDI Data Optical Memory Card (OMC) Files USMC Facility with a legacy system that cannot accept EDI transactions; a DLMS migration is not imminent.

  9. Summary • The DLMS Bridge captures and then “repackages” data for use by systems with different functions, standards, formats and interfaces. • The DLMS Bridge supports IUID data and RFID implementations. • Scalable architecture; accommodates User Defined Files, flat files, OMC files, DLMS, XML, data sets, etc.). • The DLMS Bridge supports a variety of functional areas including supply, finance (SFIS), transportation, acquisition, etc. • It comes with support at no additional expense (no DLMS Bridge programming costs, transaction mapping costs or help desk costs). • It is available for tailoring to your specific system integration challenge. • DLMSO Contact for further information: john.schwarz.ctr@dla.mil