Marcus Haberichter DMSMS Program Manager Marcus'Haberichtertinker'af'mil

1
Centralized DMSMSManagement Office(CDMO)25 Jan
2006

• Marcus HaberichterDMSMS Program
  ManagerMarcus.Haberichter_at_tinker.af.mil

I n t e g r i t y - S e r v i c e - E x c e l
l e n c e
2
Introduction

• What is DMSMS and why do we care?
• What is the CDMO and what do we do?
• Why a CDMO?
• Who do we support?
• Benefits
• Summary

3
DMSMS Definition

• Diminishing Manufacturing Sources and Material
  Shortages
• Obsolescence occurs when a source of supply is no
  longer available
• Especially prevalent in the electronics arena
• Impact to the warfighter
• Becoming more common for DoD weapon systems
• Small market
• Increasing technological dependence
• Long weapon system life cycles

4
DMSMS Program Requirements

• AFMCI 23-103
• Analysis to determine most cost effective
  resolution
• Actions shall be most cost effective over life of
  the system
• ALC Responsibilities
• Designate a DMSMS Focal Point
• Resolve DMSMS issues for all items under its
  responsibility
• Screen new system parts for obsolescence

5
OC-ALC CDMO

• Centralized DMSMS Management Office
• Spawned in 2004 at joint ALC lean event at Robins
  ALC
• Brought together the common efforts of multiple
  weapons systems
• Oversees all DMSMS efforts for OC-ALC
• Share proposed solutions across platforms
• Weapons system engineer maintains OSSE
• Data sharing between programs other ALCs
• Agreement in place to share information
  potential solutions
• Several common items between the depots

6
CDMO Efforts

• Consolidated efforts under a single contract
• Manage the tool of choice for DMSMS
• AVCOM 5.0 on-line web-based tool
• Loading of data is first step
• T.O.s, Drawings, Commercial Manuals
• Parts Status provided
• Search alternative solutions/proposals
• AVCOM able to provide file to update API

7
CDMO Efforts

• Increased capability within the CDMO
• 2 Engineers assigned full time
• Contractor support for analysis
• Research common problems
• Provide proposed solutions
• Research requests from Weapon Systems or other
  customers
• Program Offices
• Parts Buyers
• Share information with other ALC DMSMS offices
• Eliminate redundant efforts between ALCs

8
CDMO Scope

• Over 1349 Tech Orders loaded into AVCOM
• Over 150 of the T.O.s identified as having
  multiple platform usage, i.e. B-52, -135, E-3,
  etc
• Expanded content on 349 additional T.O.s
• Originally had only loaded electronics data
• All parts now included in AVCOM analysis
• Over 300 T.O.s shared from WR-ALC
• Over 261K unique parts entered
• Identified 2K items with errors for correction or
  verification
• Provided to Equipment Specialist for resolution
• Status provided for over 170K parts

9
CDMO Benefits

• Reduced redundant efforts
• Lower cost for data loading
• Common parts chased one time
• Expertise at finding alternative solutions
• Not just limited to AVCOM identified parts
• CDMO savings based on avoidance
• DMEA Cost Avoidance Model
• Actual cost avoidance based on next most
  expensive solution

10
DMEA Standard
11
Next Steps for the CDMO

• 16500 items shown as Red
• 7500 items have solutions or no other actions
  required
• 9000 items still to be looked at
• Contract analysis
• Perform analysis in CDMO for programs
• Assess impact and analysis of need
• Develop feedback loop from program offices

12
CDMO POCs

• CDMO willing to assist our customer base
• Proactive Assessment
• Most cost effective
• Reactive Assistance
• Response to an existing problem
• POCs
• Marcus Haberichter marcus.haberichter_at_tinker.af.mi
  l
• Duncan Moore duncan.moore_at_tinker.af.mil
• 558 CBSS/GBHBA

13
Summary

• DMSMS is a problem that will not go away
• CDMO works to provide proactive solutions
• CDMO supports multiple weapons system across the
  ALCs
• Cost effective
• Sharing of information is key to success
• If it works its obsolete!

14
Questions/Comments
15
TEAM TINKER