Presentation on theme: "Maintenance Plus (CBM+)"— Presentation transcript:
1 Maintenance Plus (CBM+) Condition BasedMaintenance Plus (CBM+)Robert RiegertHAF/A4ID29 February 2012Version 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 OfficeUtilizes Enterprise Logistics Governance (ELG) Processes to energize discussions, address gaps, and transform within the USAF Logistics EnterpriseHAF/A4ID TransformationCBM+, CBM+RE, HVM, PTC, Policy, RUL…..CBM+ is policy driven through Policy (Acquisition and Mods)SLIM: Systems Lifecycle Integrity ManagementCBM+: Condition Based Maintenance PlusCBM+RE: Condition Based Maintenance Plus Research EnvironmentPTC: Predictive Trending CapabilityHVM: High Velocity MaintenanceRUL: Residual Useful Life
4 ELG -PurposePermanent governance structure providing logistics community standardized consolidated guidance/decisions acrossGoals:Streamlined decision making and problem resolutionImproved integration:Among eLog21 and other major logistics improvement effortsAcross SAF, HQ, MAJCOM, ALC, and DRUContinuous Process Improvement (CPI) modeInternal - external to logisticsBetter use of senior leader time – reduce the number of meetings or boards they must attendSAF: Secretary of the Air ForceHQ: Head QuartersMAJCOM: Major CommandsALC: Air Logistics CenterDRU: Direct Reporting UnitsThe 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 StructureIntegrationStrategicOperationalTacticalLC Members: AF/A4/7; MAJCOM/ANG CVsAdvisors: DLA DD; TRANSCOM/CV; SAF/AQX, SAF/IALB Members: AF/A4/7 Deputy, AF/A4I, AF/A4L, AF/A4/7P, AF/A4/7Z; SAF/IEL; MAJCOM/ANG A4sAdvisors: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/A10LWG 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/IELAdvisors: DLA; DPO (TRANSCOM); SAF/AQXA; AFMC A4D, AFMC A4U; AFGLSC,; AFSAC; AF/A10; SAF/USMNon A4/7Governance GroupsExecutionPROJECTSAFLRBAFMEBLIMS-EVUGLog COIOther Functional Boardsand Working GroupsLog M&SLBIWGLogistics Council (LC)Chair: SAF/IELogistics Board (LB)Chair: AF A4/7Logistics WorkingGroup (LWG)Co-Chairs:AF/A4I and AF/A4LELG provides leadership to govern and direct enterprise logistics processes to:Validate alignment of Air Force logistics strategy, including eLog21, with DoD and AF prioritiesMaintain the Logistics Enterprise Architecture (LogEA) consistent with Air Force logistics strategyOversee 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 improvementProvide timely and responsive issue resolutionAdvocate a process for ensuring alignment of policy with Air Force logistics strategyEnsure timely, clear, and consistent communication of logistics enterprise strategies, initiative, and results to logisticians and other stakeholdersInterface with external organizations or structures governing processes that impact enterprise logisticsApprove, prioritize, and oversee enterprise-level projects, efforts or programs, including eLog21 projects
6 Objectives of ELG Validate alignment of logistics strategy Maintain LogisticsEnterprise Architecture (LogEA)Oversee effectiveness of logistics enterprise processes and policiesGovern logistic enterpriseprojects or effortsAlign policy and logistics strategyResolve issuesInterface with external organizations and structuresCommunicate with logisticiansELG provides leadership to govern and direct enterprise logistics processes to:Validate alignment of Air Force logistics strategy, including eLog21, with DoD and AF prioritiesMaintain the Logistics Enterprise Architecture (LogEA) consistent with Air Force logistics strategyOversee 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 improvementProvide timely and responsive issue resolutionAdvocate a process for ensuring alignment of policy with Air Force logistics strategyEnsure timely, clear, and consistent communication of logistics enterprise strategies, initiative, and results to logisticians and other stakeholdersInterface with external organizations or structures governing processes that impact enterprise logisticsApprove, prioritize, and oversee enterprise-level projects, efforts or programs, including eLog21 projects
7 Logistics Working Group (LWG) Logistics Council (LC) Examples ofELG Decisions by TierGovernance TierLogistics Working Group (LWG)Logistics Board (LB)Logistics Council (LC)StrategyProvide strategy change recommendations and maintain alignment w/ DOD and AFValidate and change logistics strategy to align w/ DOD and AFN/AEnterprise ProcessesReview effectiveness and facilitate adoption of enterprise logistics processesDirect adoption of standard, enterprise logistics process (e.g. AFSO21 improvements)LogisticsEnterpriseCPI ProjectsApprove further analysis and recommend closure for logistics enterprise projects or programsApprove, prioritize, oversee and direct or approve closure of enterprise projects or programsApprove new enterprise-level projects or programs (for efforts with strategic impact)PolicyRecommend policy changes to appropriate functional authoritiesRecommend the codification of enterprise wide standard processDirect updates to policyIssueResolutionPrioritize issues for either resolution or elevationResolve issue with strategic impactExternal OrganizationsMaintain touch points to review and assess changes and deconflict with external communitiesDirect the review and assessment of changes to external process for logistics impactCommunicationCommunicate benefits of ELG and direct creation of change management plansChampion ELG decisions and communicate themChampion ELG decisionsDecisionsThe 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.77
8 ELG Project Flow and Oversight LCGovernance GroupsNon A4/7LBELG ENTERPRISECROSS-FUNCTIONALPROJECTSLWG* Cross-functional projects go directly to LWGWe 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.AFLRBAFMEBLog EALIMS-EVUGLog COIELG ENTERPRISEFUNCTIONALPROJECTSLBIWGLog M&SOther Functional Boardsand Working Groups* Functional projects go directly to functional boards and working groups
9 ELG Project LifecycleELG governed projects complete standard work and adhere to a common project management lifecycleBenefits include:8-step problem solving processInterdependency identification and management processProject status requirementsThis 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 PeopleCBM+ Module in LOG 135 educational course (HAF/A4ID-SLIM Initiative)ProcessSLIM 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)TechnologyLogistics 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 aggregationMulti-source, near real time data vs single source batch aggregation requires SOA and Federations11
12 Condition-Based Maintenance Plus Research Environment (CBM+ RE) Multi-Use Support CapabilityOtherCBM+DataOEMDataAvionicsDataRESEARCHAccess to pedigreed dataValidate research resultsShorten development/insertion cycle timeEngine HealthManagement DataMetadata RepositorySystem Integrity ManagementSupport collaboration of engineering toolsImprove system performance monitoring and assessmentProactive lifecycle weapon system managementAircraft Structures DataWorking StorageCBM+ REGlobal Combat Support System – Data ServicesENTERPRISE INTEGRATIONIntegrated architectures define information exchange requirementsLinks platforms and logistic enterpriseAttributes:Federated ArchitectureStandard Data ExchangeSingle Point Entry and Security VerificationSupports 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 aggregationSelect Use Cases will be used to validate the framework and establish a data strategys13
14 CBM+RE Major Functionalities Resource Discovery ApplicationEngineering 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 linksBuilt 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 sourcesUploading and Execution of 3rd party algorithms3rd party intellectual property assuranceTesting on live dataWSDL Interrogator (Support dynamic service call)Credential proxy for data assuranceParallel processingResults of analysis that can be reused across the AF enterprise
18 CBM+RE Capabilities and Topics Server ArchitectureFederated SecurityCBM+RE Major FunctionalitiesSOA 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 = guidanceUSAF Policy UpdatesAir Force Instructions in revision / updates pendingAFI Aircraft and Equipment Maintenance ManagementAFI becoming AFI Systems Engineering (updates Life Cycle Systems Engineering)Acquisition and Sustainment Life Cycle ManagementUpdate Released 12 Jan 2012 – New AFI Propulsion Management for Aerial Vehicles (Replaced AFI )NEW – AFI on Product Support in work, CBM+/RCM unknown
21 CBM+ in Current USAF Policy Sec/ParaTopicOffice/OPR/TopicCBM+NotesAFI2.16.6RolesA4/7XEnsure Condition Based Maintenance Plus (CBM+) concepts and functions are developed and implemented as applicable.AFMC/CCEnsure Serialized Item Management (SIM), Reliability Centered Maintenance (RCM) and Condition Based Maintenance Plus (CBM+) concepts and functions are developed and implemented as applicable.AFSC/CCEnsure SIM, RCM and CBM+ concepts and functions are developed and implemented as applicable2.29.9Program Mgr/SPMDevelop and implement, as applicable, Condition Based Maintenance Plus (CBM+) functions.3.88.6Sustainment Planning RequirementsProduct Support/Sustainment Planning OverviewCondition 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 details3.96Support Equipment/Automatic Test EquipApplication 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/ParaTopicOffice/OPR/TopicCBM+NotesAFIProduct Support Strategy RequirementsXCondition-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)AFIPropulsion Management for Aerial VehiclesCondition 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.AFMCIA2.8.2The 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/ParaTopicOffice/OPR/TopicCBM+NotesAFPAMLife Cycle Management Plan:Program Performance/System Indicators and RequirementsXDescribe 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) Program3.7.13LCS: Maintenance Planning and ManagementDefine 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.