Army Logistics Strategy

1
Army Logistics Strategy For Migration to Joint
Interoperability
1 of 7
2
Background

• Military Standard (MILS) Business Rules govern
  the vast majority of legacy Logistics systems
• 1990s DMLS Business Rules have been slowly
  adopted in legacy systems Process Review
  Committee (PRC)
• NOV 00 OSD Approval of Army Strategy
• AUG 01 OSD Approval of Army Plan
• Prior to Army decision on Enterprise
  solution

2 of 7
3
Current Interoperability
TRANSCOM / SDDC
Air Force
MUFFIN
DRMS
EMALL
Internal Army MILS
DAASC
TOOLBOX
Projected into FY07
3 of 7
4
Army Logistics Transformation

• Developing an end-to-end Enterprise solution
  (SAP)
• Uses Commercial Business Rules/Practices
• Scalable to meet current and emerging
  requirements
• Integrating state-of-the-art, Satellite based,
  global communications
• Reducing EDI bandwidth requirements by sending
  only the data required by each trading partner

4 of 7
5
Enterprise Interoperability (FY07-09)
JTA 6.0
BEA
GCSS-Navy
GCSS-Army
GCSS-Air Force
SAP IDOCS
GCSS-Marines
PLM / Netweaver
GCSS-Joint
MILS
XML
ANSI ASC X12
DLA/BSM
Legacy Army Uniques
Commercial Vendors
Legacy Army STAMIS
GIG ES
BMMP
5 of 7
6
PLM / Netweaver

• Robust, Universal Translator
• Based on Commercial Best Business Practices
• Each Trading Partner Agreement specifies exact
• transmission data, and EDI format
  requirements
• Backward compatibility with older systems
• Scalable for Future Technology / EDI protocols

6 of 7
7
Bottom Line

• Army Logistics will continue to use DAASC for
• translation services until PLM is online
• Projected migration date FY07
• Based on current schedule, resources,
  and prioritization of efforts

7 of 7