NAVAIR AIR 6.7.1 CBM OSD BRIEF

1
NAVAIR AIR 6.7.1 CBM OSD BRIEF

• XAVIER KOON
• AIR 6.7.1.3
• Xavier.koon_at_navy.mil
• 301 757-2668
• June 3, 2009

2
PURPOSE

• Present NAVAIRs CBM vision/end state
• Brief the current status of NAVAIRs CBM effort
• Brief issues/concerns identified

3
NAVAIRs VISION

• Establish CBM IPT across platforms/competencies
• Establish NAVAIR CBM Charter
• Adopt DoDI CBM definition
• Develop NAVAIR CBM Standard
• Align CBM initiatives into a NAVAIR CBM shared
  vision
• Leverage lessons learned
• Identify strategies that support CBM
• Develop and monitor CBM Technologies
• Establish standardization for Data Management-
  (i.e., data collection, data transmission, data
  storage/retrieval, and usage)
• Improved maintenance/operational decision making
• Integration of all life-cycle management
  processes
• Increase assets life limits

4
CURRENT STATUS

• Briefed
• - NAVAIR ST community on CBM IPT
  initiative
• - Rotary-wings Program Offices on NAVAIR
  CBM initiative by NACRA
• - Fixed-wing Program Offices on NAVAIR
  CBM initiative
• - AIR 6.0 RDML Grosklags on current CBM
  status
• CBM workshop sponsored by AIR 6.7 NACRA (April
  09)
• Participants as follow
• NAVAIRs rotary/fixed-wing Program Offices
• NAVAIRs AIR 4.0/4.0T Engineering competency
• NAVSEA Carderock
• MALSP II Program Office
• FRC-East Cherry Point
• NAVAIR AIR 6.0 Logistics community
• CSI (Coalition Solutions Integrated, Inc.)

5
CURRENT STATUS

• Workshop communication
• Brief by AIR 6.7.1 Dave E. Swanson on need of
  CBM to improve maintenance, decision making and
  reduce cost
• Brief by Greg Kilchenstein on CBM from an OSD
  perspective
• Workshop focus
• Familiarization of the CBM Guidebook
• Life Cycle Sustainment Metrics defined- material
  availability, material reliability, ownership
  cost and mean down time
• Benefit to Warfighter at a strategic level- i.e.,
  common use of data and items among Services to
  reduce logistics footprint and costs
• Identified the elements of CBM and get consensus
• Identified the functionality of the CBM elements
• Follow-up workshop in June 09
• Expand CBM Working Group (WG)
• Identify at least one member per
  program/competency

6
ISSUES/CONCERNS

• Funding to support CBM initiatives
• Management support on policy and guidance
• Program Managers/ Engineering community support
  on CBM initiatives
• CBM data management system inter-ops with NMCI
  IT system

7
QUESTIONS