1. Maintenance Plus (CBM+)
Condition Based
Maintenance Plus (CBM+)
Robert Riegert
HAF/A4ID
29 February 2012
Version 2.0

2. Agenda CBM+ USAF Overview
CBM+ Initiative Governance (Not just for CBM+)
Enterprise CBM+ Initiatives (People, Process, and Technology)
Systems Lifecycle Integrity Management (SLIM)
CBM+ Policy in the USAF (Backup)

3. CBM+ Organizational Construct and Initiative Governance
There’s no organization specifically charged with minding the “CBM+ Store”
DoDI compliance left largely up to System Program Management Office
Utilizes Enterprise Logistics Governance (ELG) Processes to energize discussions, address gaps, and transform within the USAF Logistics Enterprise
HAF/A4ID Transformation
CBM+, CBM+RE, HVM, PTC, Policy, RUL…..
CBM+ is policy driven through Policy (Acquisition and Mods)
SLIM: Systems Lifecycle Integrity Management
CBM+: Condition Based Maintenance Plus
CBM+RE: Condition Based Maintenance Plus Research Environment
PTC: Predictive Trending Capability
HVM: High Velocity Maintenance
RUL: Residual Useful Life

4. ELG -Purpose
Permanent governance structure providing logistics community standardized consolidated guidance/decisions across
Goals:
Streamlined decision making and problem resolution
Improved integration:
Among eLog21 and other major logistics improvement efforts
Across SAF, HQ, MAJCOM, ALC, and DRU
Continuous Process Improvement (CPI) mode
Internal - external to logistics
Better use of senior leader time – reduce the number of meetings or boards they must attend
SAF: Secretary of the Air Force
HQ: Head Quarters
MAJCOM: Major Commands
ALC: Air Logistics Center
DRU: Direct Reporting Units
The purpose of the ELG was to establish an in-place governance structure. The aim was to streamline integration with eLog21 initiatives and those outside eLog21. It looks at how do we get together with all CPI under AFSO21, and bring that in from an enterprise point of view. How do we take an enterprise view of projects and elevate issues to an enterprise level? How do we integrate with our Acquisition, A1, and A6 community.
In short, we want to better utilize time of our senior leadership and MAJCOMs; many of whom were tasked to go to separate meetings.

5. Other Functional Boards Logistics Council (LC)
Tiered ELG Structure
Integration
Strategic
Operational
Tactical
LC Members: AF/A4/7; MAJCOM/ANG CVs
Advisors: DLA DD; TRANSCOM/CV; SAF/AQX, SAF/IA
LB Members: AF/A4/7 Deputy, AF/A4I, AF/A4L, AF/A4/7P, AF/A4/7Z; SAF/IEL; MAJCOM/ANG A4s
Advisors:
ALC/CCs (3), AFGLSC/CC, Prod Ctr/CCs (ASC, ESC, AAC, SMC); AFNWC/CC; DLA DSR/CC; DPO (TRANSCOM); SAF/AQX; AFSAC, SAF/USA, SAF/USM, AF/A10
LWG Members: ACC/AFMC/AMC/AETC/AFSPC/AFSOC/USAFE/PACAF/AFRC/ANG/AFGSC A4 Directorates; AF/A4ID; AFMEB; AFLRB; AF/A4LW; AF/A4/7P; AF/A4/7Z; SAF/IEL
Advisors: DLA; DPO (TRANSCOM); SAF/AQXA; AFMC A4D, AFMC A4U; AFGLSC,; AFSAC; AF/A10; SAF/USM
Non A4/7
Governance Groups
Execution
PROJECTS
AFLRB
AFMEB
LIMS-EV UG
Log COI
Other Functional Boards
and Working Groups
Log M&S
LBIWG
Logistics Council (LC)
Chair: SAF/IE
Logistics Board (LB)
Chair: AF A4/7
Logistics Working
Group (LWG)
Co-Chairs:
AF/A4I and AF/A4L
ELG provides leadership to govern and direct enterprise logistics processes to:
Validate alignment of Air Force logistics strategy, including eLog21, with DoD and AF priorities
Maintain the Logistics Enterprise Architecture (LogEA) consistent with Air Force logistics strategy
Oversee the effectiveness of and monitor the compliance with logistics processes and policies to enable optimal enterprise performance. This includes taking a look at metrics to see how well we are performing; how can we target improvement
Provide timely and responsive issue resolution
Advocate a process for ensuring alignment of policy with Air Force logistics strategy
Ensure timely, clear, and consistent communication of logistics enterprise strategies, initiative, and results to logisticians and other stakeholders
Interface with external organizations or structures governing processes that impact enterprise logistics
Approve, prioritize, and oversee enterprise-level projects, efforts or programs, including eLog21 projects

6. Objectives of ELG Validate alignment of logistics strategy
Maintain Logistics
Enterprise Architecture (LogEA)
Oversee effectiveness of logistics enterprise processes and policies
Govern logistic enterprise
projects or efforts
Align policy and logistics strategy
Resolve issues
Interface with external organizations and structures
Communicate with logisticians
ELG provides leadership to govern and direct enterprise logistics processes to:
Validate alignment of Air Force logistics strategy, including eLog21, with DoD and AF priorities
Maintain the Logistics Enterprise Architecture (LogEA) consistent with Air Force logistics strategy
Oversee the effectiveness of and monitor the compliance with logistics processes and policies to enable optimal enterprise performance. This includes taking a look at metrics to see how well we are performing; how can we target improvement
Provide timely and responsive issue resolution
Advocate a process for ensuring alignment of policy with Air Force logistics strategy
Ensure timely, clear, and consistent communication of logistics enterprise strategies, initiative, and results to logisticians and other stakeholders
Interface with external organizations or structures governing processes that impact enterprise logistics
Approve, prioritize, and oversee enterprise-level projects, efforts or programs, including eLog21 projects

7. Logistics Working Group (LWG) Logistics Council (LC)
Examples of
ELG Decisions by Tier
Governance Tier
Logistics Working Group (LWG)
Logistics Board (LB)
Logistics Council (LC)
Strategy
Provide strategy change recommendations and maintain alignment w/ DOD and AF
Validate and change logistics strategy to align w/ DOD and AF
N/A
Enterprise Processes
Review effectiveness and facilitate adoption of enterprise logistics processes
Direct adoption of standard, enterprise logistics process (e.g. AFSO21 improvements)
Logistics
Enterprise
CPI Projects
Approve further analysis and recommend closure for logistics enterprise projects or programs
Approve, prioritize, oversee and direct or approve closure of enterprise projects or programs
Approve new enterprise-level projects or programs (for efforts with strategic impact)
Policy
Recommend policy changes to appropriate functional authorities
Recommend the codification of enterprise wide standard process
Direct updates to policy
Issue
Resolution
Prioritize issues for either resolution or elevation
Resolve issue with strategic impact
External Organizations
Maintain touch points to review and assess changes and deconflict with external communities
Direct the review and assessment of changes to external process for logistics impact
Communication
Communicate benefits of ELG and direct creation of change management plans
Champion ELG decisions and communicate them
Champion ELG decisions
Decisions
The chart shows what ELG decisions are made at the proper level. If things can be done within function, the use of functional boards is acceptable. If integration is required, the LWG will take a look. We have found that very few issues do not involve integration.
The idea is to put items at the right level and only elevate decisions that need to be made. 7 7

8. ELG Project Flow and OversightLC
Governance Groups
Non A4/7 LB
ELG ENTERPRISE
CROSS-FUNCTIONAL
PROJECTS
LWG
* Cross-functional projects go directly to LWG
We would expect an initiative to originate at the working level at the bottom through Functional Boards as the entrance into the LWG. Ideas also arise from above and are pushed down. The right hand shows ideas from outside partners or operational changes entering the structure. We have accommodated for all inputs to enter the process. This provides alignment across the Air Force community.
AFLRB
AFMEB
Log EA
LIMS-EV UG
Log COI
ELG ENTERPRISE
FUNCTIONAL
PROJECTS
LBIWG
Log M&S
Other Functional Boards
and Working Groups
* Functional projects go directly to functional boards and working groups

9. ELG Project Lifecycle
ELG governed projects complete standard work and adhere to a common project management lifecycle
Benefits include:
8-step problem solving process
Interdependency identification and management process
Project status requirements
This shows the cradle through grave path of an ELG project lifecycle. It involves all the tools we have come to know, such as the 8 Step Process. It track interdependencies and standard means for reporting the status of requirements.

10. Enterprise CBM+ Related Initiatives
People
CBM+ Module in LOG 135 educational course (HAF/A4ID-SLIM Initiative)
Process
SLIM Guide and Acquisition Sustainment Toolkit Checklist promotes CBM+ Requirements (HAF/A4ID-SLIM Initiative)
AF Service Representative on OSD CBM+ Advisory Group (HAF/A4ID-SLIM Initiative)
High Velocity Maintenance (HVM) at Warner Robins Air Logistics Center (WR-ALC)
Technology
Logistics and Installations Management System-Enterprise View (LIMS-EV)
Multiple Condition Report Views (LIMS Program Office)
Engineering Technical View (HAF/A4ID-SLIM Initiative)
Condition Based Maintenance Plus Research Environment (CBM+ RE) (HAF/A4ID-SLIM Initiative with AFMC/A4U-Sustainment Engineering)
Discuss Gaps/Issues that each initiative addresses and benefits/objectives of each initiative.

11. USAF CBM+ Framework AFSO21 DSWS Initiative (SCO-1-19) (SLIM)
Multi-source, near real time data vs single source batch aggregation
Multi-source, near real time data vs single source batch aggregation requires SOA and Federation s 11

12. Condition-Based Maintenance Plus Research Environment (CBM+ RE)
Multi-Use Support Capability
Other
CBM+
Data
OEM
Data
Avionics
Data
RESEARCH
Access to pedigreed data
Validate research results
Shorten development/insertion cycle time
Engine Health
Management Data
Metadata Repository
System Integrity Management
Support collaboration of engineering tools
Improve system performance monitoring and assessment
Proactive lifecycle weapon system management
Aircraft Structures Data
Working Storage
CBM+ RE
Global Combat Support System – Data Services
ENTERPRISE INTEGRATION
Integrated architectures define information exchange requirements
Links platforms and logistic enterprise
Attributes:
Federated Architecture
Standard Data Exchange
Single Point Entry and Security Verification
Supports Spiral Development of CBM+ Capabilities

13. USAF CBM+ Framework AFSO21 DSWS Initiative (SCO-1-19)
Use Case A
(C-130 AIRCAT)
Use Case B
(ASIP, F-16)
Use Case C
(F110/F100, ETOW)
Use Case D
(F110/F100, UBL/ESP)
Use Case E
(F110/F100, F-16)
Multi-source, near real time data vs single source batch aggregation
Select Use Cases will be used to validate the framework and establish a data strategy s 13

14. CBM+RE Major Functionalities
Resource Discovery Application
Engineering Model Mashup

15. Resource Discovery Application
A web application providing a rich and intuitive user experience to subject matter experts for searching and displaying both static and dynamic enterprise resource links
Built on top of the MDE Information Asset Discovery, it will leverage the vocabulary repository to drive ad hoc data discovery

16. What is an Engineering Model Mashup?
Web application that provides aggregation, transformation, and computational services over top of the data exposed by one or more sources.
It focuses on run time development, drag-and-drop, and Subject Matter Expert empowerment.

17. What an Engineering Mashup Provides
Aggregation and Transformation of engineering data to provide new reusable data sources
Uploading and Execution of 3rd party algorithms
3rd party intellectual property assurance
Testing on live data
WSDL Interrogator (Support dynamic service call)
Credential proxy for data assurance
Parallel processing
Results of analysis that can be reused across the AF enterprise

18. CBM+RE Capabilities and Topics
Server Architecture
Federated Security
CBM+RE Major Functionalities
SOA Framework Maturation

19. CBM+ Policy in the USAF USAF is compliant with DoD policy
USAF Policy hierarchy: AFI – AFM – AFMCI (MAJCOM) – Organizational Instructions (e.g. Air Logistics Center)
AFPAM = guidance
USAF Policy Updates
Air Force Instructions in revision / updates pending
AFI Aircraft and Equipment Maintenance Management
AFI becoming AFI Systems Engineering (updates Life Cycle Systems Engineering)
Acquisition and Sustainment Life Cycle Management
Update Released 12 Jan 2012 – New AFI Propulsion Management for Aerial Vehicles (Replaced AFI )
NEW – AFI on Product Support in work, CBM+/RCM unknown

20. Back Up Slides

21. CBM+ in Current USAF Policy
Sec/Para
Topic
Office/OPR/Topic
CBM+
Notes
AFI
2.16.6
Roles
A4/7 X
Ensure Condition Based Maintenance Plus (CBM+) concepts and functions are developed and implemented as applicable.
AFMC/CC
Ensure Serialized Item Management (SIM), Reliability Centered Maintenance (RCM) and Condition Based Maintenance Plus (CBM+) concepts and functions are developed and implemented as applicable.
AFSC/CC
Ensure SIM, RCM and CBM+ concepts and functions are developed and implemented as applicable
2.29.9
Program Mgr/SPM
Develop and implement, as applicable, Condition Based Maintenance Plus (CBM+) functions.
3.88.6
Sustainment Planning Requirements
Product Support/Sustainment Planning Overview
Condition Based Maintenance Plus (CBM+), as an extension of the maintenance design program executed during development, shall be used to improve maintenance agility and responsiveness, increase operational availability, and reduce life cycle total ownership costs. The goal is to perform maintenance only upon evidence of need by employment of technologies, processes, and procedures to improve maintenance/logistics. Enabling technologies and concepts include prognostics, diagnostics, portable maintenance aids, interactive electronic technical manuals, interactive training, data analysis, integrated information systems, automatic identification, reliability-centered maintenance, and joint total asset visibility. See DODI , Condition Based Maintenance Plus (CBM+) for Materiel Maintenance, for more details
3.96
Support Equipment/Automatic Test Equip
Application of standardized Support Equipment/Automatic Test Systems (SE/ATS) is preferred to provide efficiency and reduce cost. The PM shall minimize the proliferation of system-unique equipment at all levels while ensuring the maintenance and deployment requirements of existing and developing systems are met

22. CBM+ in Current USAF Policy (continued)
Sec/Para
Topic
Office/OPR/Topic
CBM+
Notes
AFI
Product Support Strategy Requirements X
Condition-based maintenance plus (CBM+), reference: DoD Maintenance Policy, Programs and Resources, is an initiative to improve maintenance agility and responsiveness, increase operational availability and reduce life-cycle total ownership costs. The goal of CBM+ is to perform maintenance only upon evidence of need. Condition-based maintenance (CBM) is a set of maintenance processes that rely on a real time assessment of weapon system condition generated by embedded sensors and/or external tests and measurements using portable equipment, CBM+ expands on these basic concepts by employing other technologies, processes and procedures to improve maintenance/logistics. These existing and future technologies, processes and procedures are to be addressed during all phases of a weapon system's life cycle planning, acquisition, sustainment and reclamation.
The enabling technologies and concepts that constitute an acceptable initial AF baseline for achieving CBM+ implementation are: prognostics, diagnostics, portable maintenance aids, interactive electronic technical manuals, interactive training, data analysis, integrated information systems, automatic identification, reliability-centered maintenance (RCM) and joint total asset visibility (JTAV)
AFI
Propulsion Management for Aerial Vehicles
Condition Based Maintenance Plus (CBM+). CBM+ concepts shall be used to optimize key performance measures of engine readiness, availability, reliability, mean downtime, and ownership costs. Reference DODI , Condition Based Maintenance Plus (CBM+) for Materiel Maintenance and AFI , Acquisition and Sustainment Life Cycle Management. Engine Health Management (EHM). EHM shall be implemented on propulsion assets. EHM is the application of CBM+ concepts to aircraft engines and implementation may vary depending on the TMS support concept, MAJCOM requirements, and data availability. The goal of EHM is to tie together ET&D and RCM to enable a predictive maintenance end state capability. Refer to or reference TO CD-1, Technical Manual - Engine Health Management Plus (EHM+) General Information User Manual for additional direction and/or guidance.
AFMCI
A2.8.2
The overarching support concept should be considered from the start of any development or modification effort. Support concepts like condition based maintenance will drive requirements and design decisions. Early ALC representation in development of the support concept and related requirements is necessary to reduce total ownership costs.

23. CBM+ in Current USAF Policy (continued)
Sec/Para
Topic
Office/OPR/Topic
CBM+
Notes
AFPAM
Life Cycle Management Plan:Program Performance/System Indicators and Requirements X
Describe your maintenance and inspection program; include the methodology basis (Conditioned Based Maintenance Plus (CBM+), Reliability Centered Maintenance (RCM), and/or Maintenance Steering Group III (MSG-3). Describe the relationship of the RAM approach with other related program efforts such as Weapon System Integrity Programs (WSIP), Aircraft Information Program (AIP), and Military Flight Operations Quality Assurance (MFOQA) Program
3.7.13
LCS: Maintenance Planning and Management
Define requirement for maintenance data collection. Technical Order provides a broad understanding of the objectives, scope, concept, and policy of Maintenance Data Documentation (MDD) and some intended uses of the data collected. Define what is to be collected (failure, availability, maintenance) and when it should be reported (IOC, turnover, etc.). Define how and where to report data. Integrated Maintenance Data System (IMDS) is the approved Air Force Base Level MDD system and Reliability and Maintainability Information System (REMIS) is the approved Depot Level MDD system.