1. Draft PDC 1267 DLMS 830D Navy / DLA Gross Demand Planning (GDP)
Pearlis Sturgis J343 Planning
May 17, 2017

2. Discussion
Defense Logistics Management Standards (DLMS) transactions as an enterprise standard, and that Component Automated Information Systems must fully achieve compliancy
DOD Directive E, Defense Logistics Management Standards (DLMS), January 9, 2015
DLM , Defense Logistics Management Standards, Volume 2, Supply Standards and Procedures, June 13, 2012

3. PDC 1267 Focus
Navy Fleet Readiness Centers (FRC) Gross Demand Plan (GDP) to be converted to the DLMS 830D, Demand Data Exchange (DDE) Projected Supply Plan format by calendar year 2019
Required 830D (DDE) projected supply 60 month plan periods with zero filling months with no plan data
Change from current GDP flat file format of required delivery dates and quantities
Allow two (2) decimal positions in all quantity fields to include zeros at the end
Requires Defense Automated Addressing System (DAAS) logic improvement
No impacts to DLA JDA logic

4. PDC 1267 Focus (Cont.)
FRC projections contain other service managed items
Requires DLA creation of 830D new SAP / JDA routing logic
Requires Services SOS approval to accept 830D transactions
Requires direct FRC / DLA forward and other SOS manual collaboration for FRC planned requirement
Impacted Automated Information Systems (AIS)
Navy NDMS, DAAS, DLA EBS (JDA Planning Module)
Army, Air Force, Navy, Marine Corps, US Coast Guard IT solution

5. Proposed Transaction Flow Flow Dependent on Senior Leaders Approval
Navy NDMS IT solution calculates forecasted requirements and creates the DLMS 830D transactions
Transmit to DAAS with RIC set to ‘SMS’ for all items
DAAS receives 830D transactions and transmit to DLA SAP / JDA Planning Module
JDA receives FRC 830D transactions and processes all DLA managed items
JDA identifies Non-DLA managed other SOS items and properly create new 830D and load appropriate Service Routing Identifier Code and process to DAAS
DAAS receives 830D from SAP/ JDA and process to appropriate SOS
Flow Dependent on Senior Leaders Approval

6. Proposed Transaction Flow (Cont.)
DLA Routing to SOS
Navy FRC IT solution codes all 830D transactions with RIC of ‘SMS’ with DAAS acting as a pass through to SAP/JDA.
For YOTH consumables, SAP/JDA) is responsible for identifying the proper RIC/SOS for routing to DAAS. DAAS then routes to appropriate SOS.
830D
(SMS RIC)
830D
(SMS RIC)
830D
SOS
RIC
FRC IT
Solution 1
DAAS 2
SAP
(JDA) 3 4 5
DAAS 6
830D (TBD RIC)
YOTH SoS
830D (TBD RIC)
NAVSUP 6a
830D (TBD RIC) AF 6b
830D (TBD RIC)
830D (TBD RIC)
Army 6c
GSA 6d
Coast Guard 6e
DLA System
Navy System
System TX