Download presentation
Presentation is loading. Please wait.
Published byArline Shaw Modified over 8 years ago
1
DLSS Undefined Data Impact on Component ERPs/Modernizations & Legacy Systems Mr. Dale Yeakel 703.767.6983 Mr. Dale Yeakel 703.767.6983 Right Item, Right Time, Right Place, Right Price, Every Time... Best Value Solutions For America's Warfighter
2
DRAFThttp://www.dla.mil/j-6/dlmso/2 OutlineOutline Definition Issue Undefined data types Impact Component-unique data studies Alternatives Recommendations Summary Discussion
3
DRAFThttp://www.dla.mil/j-6/dlmso/3 DefinitionDefinition Undefined data, in this context, are data transmitted within the DLSS & DLSS-like transaction sets, for which business rules, validation criteria, and meta data have not been vetted through the PRCs and are therefore undocumented in DoD 4000.25 series manuals.
4
DRAFThttp://www.dla.mil/j-6/dlmso/4 IssueIssue Impact of undefined data contained within standard DLSS & DLSS-like transactions on Component ERP and other modernization efforts migrating to DLMS.
5
DRAFThttp://www.dla.mil/j-6/dlmso/5 Undefined Data Types Intra-Service transactions such as “B”, “C”, & “X” series Undefined multi- or dual-use record positions in existing DLSS transactions Service use of DLSS “Blank” record positions
6
DRAFThttp://www.dla.mil/j-6/dlmso/6 ImpactImpact Undefined data are passing intra- and inter- Component Meanings and rules not centrally documented DAASC does not convert most undefined data Volume/criticality of undefined data unknown Concern - Component undefined data could negatively impact ERP/modernizations & legacy systems Could Break System
7
DRAFThttp://www.dla.mil/j-6/dlmso/7 Component Undefined Data Studies LMI review of Army, Navy, Air Force, & DLA data studies Most S/A undefined data can easily be accommodated in DLMS LMI prepared draft change proposals DLMSO & Components team effort to fix
8
DRAFThttp://www.dla.mil/j-6/dlmso/8 Alternative 1 Legacy Sys DAASCERPs/modernization DLSS/MILS w/unique data DLSS/MILS w/out unique data DLMS/X12 w/out unique data DLMS/X12 w/out unique data DAASC purges undefined Component data during DLSS to DLMS conversion process: Pros Simplified processing ERP/modernization operates in pure environment Cons Component data lost Component impact unknown Components would be “put on notice” and offered assistance in identification of undefined data requirements Burden on DAASC
9
DRAFThttp://www.dla.mil/j-6/dlmso/9 Alternative 2 DAASC purges undefined Component data going to ERP/ modernization – reinstates data going back to Component during DLMS to DLSS conversion process: Pros No data lost ERPs/modernizations operate in pure environment Cons Complicates conversion process DAASC impact unknown Undefined data never reaches transaction recipient - - any anticipated response not possible Legacy SysDAASCERPs/modernization DLSS/MILS w/unique data DLMS/X12 w/out unique data DLMS/X12 w/out unique data DLSS/MILS w/unique data Burden on DAASC
10
DRAFThttp://www.dla.mil/j-6/dlmso/10 Alternative 3 DAASC - ERP/modernization perpetuates undefined Component data retained during DLSS to DLMS conversion process: Pros No data lost ERPs/modernization must store extra data Cons Complicates conversion process - data not mapped to DLMS DAASC impact unknown ERPs/, modernization impact unknown Legacy SysDAASCERPs/modernization DLSS/MILS w/unique data DLMS/X12 w/unique data DLMS/X12 w/unique data DLSS/MILS w/unique data DAASC-Component shared burden
11
DRAFThttp://www.dla.mil/j-6/dlmso/11 Components and DLMSO define and map to DLMS multi- and dual-use data contained in DLSS transactions Cons Change proposals must be validated, finalized & staffed DLSS/DLMS maps must be completed Pros No data lost Draft change proposals prepared Data required for logistics business processes defined DLMSO/DAASC/ Component shared burden Alternative 4
12
DRAFThttp://www.dla.mil/j-6/dlmso/12 Components and DLMSO define and map applicable data contained in “B”, “C”, & “X” series transactions Cons Change proposals must be validated, finalized & staffed DLSS/DLMS maps must be completed Pros No data lost Draft change proposals prepared Data required for logistics business processes defined DLMSO/DAASC/ Component shared burden Alternative 5
13
DRAFThttp://www.dla.mil/j-6/dlmso/13 RecommendationsRecommendations Intra-Service transactions such as “B”, “C”, & “X” series -- Option 5 Undefined multi- or dual-use record positions in existing DLSS transactions -- Option 4 Service use of DLSS “Blank” record positions – Alternative 1
14
DRAFThttp://www.dla.mil/j-6/dlmso/14 SummarySummary Undocumented arrangements embedded in DLSS Alternatives 1, 2 and 3 avoid issue and burden DAASC, DLMSO, & Components without resolving the issue Alternatives 4 & 5 address issues and provide viable solutions Many years (decades) have passed without enforcement Risk – inadvertently dropping critical logistics business data
15
DRAFThttp://www.dla.mil/j-6/dlmso/15 DiscussionDiscussion
16
DRAFThttp://www.dla.mil/j-6/dlmso/16 BackupBackup
17
DRAFThttp://www.dla.mil/j-6/dlmso/17 Policy Guidance Compliance with DoD Directive 8190.1, May 5, 2000, subject: Defense Logistics Use of Electronic Data Interchange (EDI) Standards Use only FIPS 161-2 approved data exchange standards for Commercial partner interface Internal EDI Implement with ongoing and planned system modernization Assign responsibilities for the direction, management coordination, and control of the implementation process DLMSO DAASC
18
DRAFThttp://www.dla.mil/j-6/dlmso/18 Policy Guidance continued continued Compliance with DUSD(L&MR) memorandum, November 30, 2000, subject: Community Data Exchange Services for Logistics Business Processes DLMSO provide configuration management for all changes to logistics business processes regardless of EB/EC technology used DLMSO provide business rules for total logistics support for all EC community data exchange services for logistics business processes DAASC provide telecommunication support, archiving and storage, translation services, ASC X12/DLSS conversion processes, and other services to support Component implementation
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.