1

DLMSO/DAASC

November 2006

Supply PRC MeetingSupply PRC Meeting

DLMS Bridge Middleware

October, 2007

DLMSO703-767-0600

Defense Logistics Management Standards Office

2

Today: System and Data Flow Complexity – Combined with the Challenge of Connecting New and Legacy Systems

Consolidation/ Consolidation/ DeconsolidationDeconsolidation

TRANSCOMTRANSCOMSystemsSystems

ServiceServiceSystemsSystems

DLADLASystemsSystems

3

Problem: How can new business systems (such as Passive Radio

Frequency Identification) exchange data with legacy systems?

Post 123’s’s PRFID system reads the RFID tag as the shipment passes through the Passive RFID system

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.

How do you exchange business data about the shipment locally with incompatible systems?

Passive RFID

System & software

(EDI)

Legacy

AIS

(MILS)

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

2

3

4

Post 123

4

WAWFGEX

DoD Enterprise Logistics Systems

DAAS Information Databases (AV, LOTS, etc.)

Example: DoD Facility with a legacy system that cannot accept EDI transactions; DLMS migration is not imminent.

Legacy System (e.g., LOG AIS)

Manufacturers/Vendor Suppliers

Tagged Material

DLMS – 856A

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.

Distribution Centers/ Depots Suppliers DLMS-856S

Shipper Material

New system(e.g., RFID)

DLMSBridge

Other Trading Partners

Other Trading Partners

MILS AE_, AS_, DF_

856,etc.

EDI / XML Data

Updates for NICP, Requisition Activities,USTRANSCOM,LOGSA, Services, etc.

Relevant Data

MILSDLMS or MILS determinedby customer system profile

5

• 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.

DLMS Bridge Middleware

6

Business Rules(Library of Business Rules Applicable to Site, Business

Processes, Legacy Systems, or any Service Specific Rules)

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)

Transaction Database(tailored to work with many databases such as SQL Server,

Oracle, SyBase, DB2, MS Access, etc.)

Syst

em In

terf

ace

(Exp

anda

ble

Libr

ary

of S

yste

m S

pecs

& In

terf

aces

)

Com

mun

icat

ions

Inte

rfac

e(E

xpan

dabl

e Li

brar

y of

App

licat

ion

Prog

ram

inte

rfac

e Pl

ug-In

O

r Con

nect

ors

to L

egac

y Sy

stem

s an

d D

AA

S)

Install & Setup(User selects the New and Legacy System interfaces - via

Drop Down Menus - for site installation)

Lega

cy S

yste

ms

and

DA

AS

Flexible Technical Architecture: Modular Construction, Hardware Independent, JAVA-based Code, Multiple O/S (Win XP & Linux so far), Centralized Configuration Management

New System Input

DLMS BRIDGE Architecture

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

WAWFGEX

DoD Enterprise Logistics Systems

DAAS Information Databases (AV, LOTS, etc.)

USMC Facility with a legacy system that cannot accept EDI transactions; a DLMS migration is not imminent.

AMS-TAC System

Manufacturers/Vendor Suppliers

Tagged Material

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).

Distribution Centers/ Depots Suppliers X12 – 858

DLMS-856S

Shipper Material

Passive RFID

System

USMCDLMSBridge

Other Trading Partners

Other Trading Partners

Optical Memory Card (OMC) Files

DLMS 856S,858R, etc.

EDI Data

Updates for NICP, Requisition Activities,USTRANSCOM,LOGSA, Services, etc.

Relevant Data

MILSDLMS or MILS determinedby customer system profile

9

• 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

Summary