Print This Page
spacer
previous section

Condition-Based Maintenance Plus (CBM+)

What is it?
The CBM+ is a Department of Defense proactive equipment maintenance capability that uses system health indications to identify and predict functional failure in advance of the event and provide the ability to take appropriate action. CBM+ is based on a set of rigorously defined maintenance tasks derived from Reliability Centered Maintenance (RCM) analysis. The fundamental building blocks in the development of CBM+ capability are: collecting data on the platform, moving data off the platform, storing data in a data warehouse, analyzing the data, and acting on the data. These processes are described in detail in concept documents, such as the Common Logistics Operating Environment (CLOE) Operational Concept Descriptions (OCD), that were collaboratively developed by materiel and combat developers and the Army G-4. These documents detail the process of collecting essential logistics data from digitized platforms/systems and passing it to key information collection and decision-making nodes within the unit or Brigade Combat Team. At the national level, CLOE-enabled data flows will support fleet trending and analysis, reliability growth, adjustments to maintenance programs, and true prognostic capabilities that will leverage information resources to provide substantially better and more cost-effective sustainment support. The data will also support configuration management and failure analysis, as well as adjustments to stock levels and consumable requirements

What the Army is doing?
The Army has completed its CBM+ Roadmap and Implementation Strategy and expects to publish its CBM+ implementation plan in mid FY09. The Army Integrated Logistics Architecture (AILA) is being collaboratively developed from the platform/tactical level, and is extending to the national level. The AILA is used to design a robust logistics operating environment and to identify the information resources, schedule drivers, and integration needed for Army-wide CBM+ implementation. Program managers are incrementally applying enablers to existing platforms where economically feasible. The aviation community, where aircraft are highly sensored, has been very active in the application of the enablers required for CBM+. The ground community also has a similar ongoing effort that is developing baseline enablers for the exploitation of CBM+ data. The Army Materiel Command's Logistics Support Activity has established an initial Army CBM+ data ontology and is now developing a CBM+ taxonomy. Combined Arms Support Command (CASCOM) is preparing CBM+ documentation, and the U.S. Logistics Innovation Agency (LIA) is developing the CBM+ Implementation Plan. Additionally, the CASCOM has inserted CBM+ language into the US Army Training and Doctrine Common (TRADOC) Writers Guide in accordance with DoD policy to ensure Future Combat Systems (FCS) are CBM+ capable. The immediate challenge is that the Army must resource multiple CBM+ efforts simultaneously to achieve an enterprise-wide capability.

What continued efforts does the Army have planned for the future?
The CBM+ implementation strategy requires the comprehensive synchronization of multiple system and platform programs to reach a threshold objective capability within the current Fiscal Year Defense Plan (FYDP) 2010-2015. Basic implementation planning will be complete within the next two years, to align ongoing investment programs and to support complementary resource requests in the Program Objective Memorandum (POM) 2012-2017 effort. In the near term, the Army must develop a comprehensive resource strategy across program manager lines, lifecycle managers and data storage activities to achieve the desired end-state. The Army must provide for the simultaneous application of CBM+ capabilities to Current Force platforms and enterprise infrastructure and systems. The objective CBM+ capability will be realized with a fully integrated and interoperable force consisting of Current Force and FCS capabilities. The most significant changes will occur in materiel, with hardware and software enablers required on platforms and in command centers to implement the CBM+. The CLOE effort is coordinating and synchronizing future efforts with the program manager Heavy Brigade Combat Team (HBCT), focusing on their emerging vehicle health management system to achieve commonality across the HBCT suite of platforms and systems and integrate future technologies, thus increasing mission readiness and interoperability. Concurrently, it will continue to employ the AILA to support the Army's CBM+ initiative, expanding it beyond the tactical level to address the national level and identify touch points with the other Services; thus enabling an integrated Joint architecture. Planning for an Army-Marine Corps logistics integration demonstration is now underway.

Why is this important to the Army?
The concept of CBM+ supports the evolution of condition-based maintenance from diagnostics to predictive maintenance, with some key systems advancing to prognostic capabilities. The "plus" strategy expands condition-based maintenance to include task enablers and related technologies and processes not necessarily included in current maintenance programs. The ultimate goal of CBM+ is to increase operational availability and readiness throughout the weapon system life cycle. CBM+ supports not only the transition to a RCM strategy, but also provides the automation needed to improve maintenance productivity, reduce the deployed footprint required to provide maintenance services to combat units, and provide visibility of equipment status needed to implement anticipatory logistics concepts to support the Soldier by generating and sustaining combat power. Initial field experience, supported by models and simulations, indicates CBM+ equipped platforms typically experience an increase in readiness in the five percent range. CBM+ capability will enable our Soldiers to be more productive, reduce maintenance services and provide visibility of equipment status needed to implement anticipatory logistics concepts. Maintenance tasks can be preventive, (i.e. scheduled in response to accumulation of specified calendar time intervals or operating hours or mileage). These tasks can be condition-based, meaning they can be dynamically scheduled, based on the detection of a specified deterioration or operating condition.

POC: Mr. Jerry Dolinish (717) 770-7083

 
previous section
   


Back to Top :: Print Version
Questions about Army Posture Statement: ESG@hqda.army.mil