Abstract
CBM+ is the application and integration of appropriate processes, technologies, and knowledge-based capabilities to achieve the target availability, reliability, and operation and support costs of DoD systems and components across their life cycle. CBM+ shifts equipment maintenance from an unscheduled, reactive approach at the time of failure to a more proactive and predictive approach that is driven by condition sensing and integrated, analysis-based decisions. With more accurate predictions of impending failures (based on real-time condition data), coupled with more timely and effective repairs, moving toward CBM+ will result in dramatic savings—in time and money—and improved weapon system availability and performance. This forum will look at newly developed CBM+ policy and how it will influence CBM+ implementation. The forum will also include presentations from the Military Services that outline implementation strategy, plans and status as well as information on how they are leveraging CBM+ capabilities and what the keys to their successes have been.
Agenda
1300-1309: Welcome – Greg Kilchenstein (OSD-MR) Presentation
1309-1310: Administrative Notes – Debbie Lilu (NCMS)
1310-1330: New CBM+ Policy Update – Greg Kilchenstein (OSD-MR) Presentation
1330-1345: JAIC and TAMR – COL Kliethermes (JAIC) & Aaron Solomon (TAMR)
1345-1405: Army CBM+ Innovations – Jason Duncan (TACOM) Presentation
1405-1420: USAF CBM+ Innovations – John Hedke (AFLCMC/EZP)
1420-1440: NAVAIR CBM+ on the H-1 – Allen Jones (NAVAIR) Presentation
1440-1455: USMC: Achieving CBM+ – MAJ Mike Whitaker (I&L) Presentation
1455-1500: Wrap-Up Presentation
Minutes
Event: On 26 May 2020, the Joint Technology Exchange Group (JTEG), in coordination with the National Center for Manufacturing Sciences (NCMS), hosted a virtual forum on “Condition Based Maintenance-Plus”.
Purpose: The purpose of this forum was to look at newly developed CBM+ policy and how it will influence CBM+ implementation, and to provide presentations from the Military Services that outline implementation strategy, plans and status as well as information on how they are leveraging CBM+ capabilities and what the keys to their successes have been.
Welcome: Greg Kilchenstein (OSD-MR) welcomed everyone to the forum and thanked the presenters and all the listeners for their attendance. He also stated how important CBM+ capabilities are to maintain readiness and increase the efficiency and effectiveness of DoD equipment.
Administrative: This was an open forum. The presentations, along with questions and answers, were conducted through Adobe Connect and Defense Collaboration Services (DCS), and four of the six presentations were also available online at the JTEG website at https://jteg.ncms.org/. A separate audio line was used. We had 144 participants from across DOD, industry, and academia join in the forum.
New CBM+ Policy Update: Greg Kilchenstein (OSD-MR) discussed newly revised draft DoD Instruction 4151.22; Condition Based Maintenance Plus (CBM+) for Materiel Maintenance, which leverages results from the CBM+ study of top 100 weapon systems and improved the focus on training, commonality, and readily available data. Focus Areas include deeper leadership understanding of CBM+ mechanisms and outcomes, organization constructs necessary to align required lifecycle functions, strong and continuous reliability center maintenance (RCM) efforts, and measures of CBM+ implementation performance and outcome metrics. The DoDI defines CBM+ objectives, describes the seven key characteristics of CBM+ execution, and incudes detailed CBM+ procedural sections for CBM+ during the Acquisition Phase and CBM+ for Legacy Systems. Formal coordination is complete and the DoDI is awaiting Signature. Issuance is projected 2Q-CY2020.
JAIC and TAMR: COL Kliethermes from the DoD Joint Artificial Intelligence Center (JAIC) provided a quick overview of the JAIC and described the Joint Logistics Predictive Maintenance (PMx) Mission Initiative. Aaron Solomon (TAMR) followed with a presentation on the PMx Knowledge Graph Workflow effort which involves the development of a physical knowledge graph to integrate sensor and logbook data with maintenance records which will enable downstream PMx + CBM. In collaboration with NCMS + LMI, TAMR is developing an extensible and repeatable graph building process for the JAIC. Aaron described the structure/goals, three stage process with examples, and future scenarios utilizing the PMx knowledge graph to support CBM+.
Army CBM+ Innovations: Jason Duncan (TACOM) described the Army’s ground vehicle CBM+ plan which utilize an incremental approach to deliver an affordable framework for implementation and scaling of CBM+ for ground vehicle systems. The approach leverages existing technology enablers and tools to provide a baseline capability. The plan focuses on an open architecture and open data model to drive continuous improvement and leverage innovation over time. Jason also discussed CBM+ capability status in the PEO CS & CSS Platforms as well as the PEO GCS Platforms.
USAF CBM+ Innovations: John Hedke (AFMC) provided a CBM+ overview noting that significant progress has been made to scale CBM+ across the USAF enterprise. Including executing to FY20 expansion goal to apply CBM+ to 12 new weapon systems, and scaling both eRCM and sensor based algorithms pathways. Currently, CBM+ is underway on 15 of 16 planned weapon systems. Six weapon systems are fielded and 45 WUCs/components are live. Next Steps include – continue new platform implementation and spiral expansions, continuously evolve CBM+ toolkit, work to improve reliability of components, begin to solidify FY21+ on-boarding plan, and enhance CBM+ product, infrastructure, and enablers.
NAVAIR CBM+ on the H-1: Allen Jones (NAVAIR) described that by using six accelerometers mounted around the UH-1 main rotor gearbox (MRGB), the H-1 diagnostics team has developed a process to isolate fault progression to specific components to recommend component removal. This helped result in a reduction in precautionary emergency landings, cost avoidance from downstream system damage and a reduction on the supply system. Since May 2016, 22 MRGB component removals have been avoided for a savings of $39M and over 7,000 manhours avoided.
USMC – CBM+ Push: Major Whitaker (HQ, USMC I&L) described CBM+ as a shift in maintenance behavior and practices enabled by technology. He described the USMC current maintenance posture of being reactive with a limited ability to conduct just 2 condition monitoring elements. He then described the USMC future proactive maintenance posture including full use of all 5 elements of condition monitoring (fluid analysis, repair history, inspections, electronic data, and site conditions), based on predicting remaining useful life, anticipated events, performed only as needed, diagnostics successfully offboarded, centralized, and analyzed, automated failure analysis, and data-driven insight on future availability. He discussed recent achievements, concept of operations, CBM+ architecture, and critical dependencies to include: a unified approach, access to a technical infrastructure, and data science expertise.
Q&A – A Q&A occurred after each briefer finished their presentation. Questions and answers will be posted on the JTEG website with these minutes.
Closing Comments: Greg Kilchenstein thanked the presenters for their contributions and all the work being done to support CBM+ capabilities efforts across DoD sustainment. He suggested continuing the information exchange beyond the forum and the importance of collaboration within the DoD maintenance community.
Action Items:
- All cleared briefing slides were posted to the JTEG website at https://jteg.ncms.org/ prior to the forum start.
- Obtain Distribution “A” level slides for the two remaining briefs.
Next JTEG Meeting: The next scheduled JTEG virtual forum is 30 June 2020, 1:00 – 3:00 pm EST. The topic is “Digital Maintenance”.
POC this action is Ray Langlais, rlanglais@lmi.org, (571) 633-8019
Q&A
CBM+ Policy – Greg Kilchenstein
Q1. Isn’t CBM+ just an element of RCM?
A1. RCM is part of CBM+. I get asked the question a lot.
Q2. Will the name of DoD Instruction 4152.22-M RCM be changed?
A2. RCM is so foundational that we still believe we need an RCM manual.
Q3. Comment: I like the comment on life-cycle sustainment community early in Acquisition phase. DLA should be brought in earlier than the end as F35 challenges demonstrate.
JAIC and TAMR – COL Kliethermes (JAIC) & Aaron Solomon (TAMR)
Q1. Will a system such as Datalink be used to alert for inspection/maintenance?
A1. We don’t have it now, but it is definitely possible.
Q2. Has the relationship to Reliability Block Diagrams of the maintenance graph been considered?
A2. No, not yet. If you have more information please send it or contact me.
Army CBM+ Innovations – Jason Duncan (TACOM)
Q1. AMC and AFC are two different commands with different money, who pays for this extra CBM+? Is this an extra cost to the PM, or will the money come from other programs?
A1. CBM+ involves hardware, software, personnel and procedures and must be supported by everyone to include the PM who supports acquisition through requirements, as well as the user who performs the proper monitoring and corrective procedures.
Q2. Any plan to include AMPV for future CBM projects within PEO GCS?
A2. We have been in discussions.
USAF CBM+ Innovations – John Hedke (AFLCMC/EZP)
Q1. What Process are you using?
A1. We are using raw data. Our process relies on subject matter experts that understand aircraft maintenance. They convert raw data into a useful format that enable us to understand components and ways to model them. We have created a Predictive Handbook and would like to see it become a USAF instruction.
Q2. How do we get a copy of the Predictive Handbook?
A2. We can distribute within the government.
Q3. How rich is the data set and CBM history from the AF Oil Analysis Program being integrated into these programs ?
A3. I don’t think we have any data from the USAF oil analysis program right now.
NAVAIR CBM+ on the H-1 – Allen Jones (NAVAIR)
Q1. Is NAVAIR still using Design for Maintainers?
A1. It is considered in all the designs.
Q2. You mentioned Hadoop, are you leveraging Spark within the CBM+ implementation? What other COTS tools is NAVAIR leveraging? Python – TensorFlow?
A2. Yes, we use SPARK, Python-TensorFlow. We are also using Anaconda enterprise solution and looking at other possibilities.
USMC: Achieving CBM+ – MAJ Mike Whitaker (I&L)
Q1. How have you integrated SIM and RFID into your ecosystem?
A1. We are using RFID to transfer data and SIM for configuration management. We don’t have a holistic USMC process.