Original Date: 11/06/2007
Revision Date: / /
Best Practice : Electronic Reliability-Centered Maintenance Development
CACI International’s development of the Web-based Electronic Reliability-Centered Maintenance process significantly reduces Reliability Centered Maintenance development time by eliminating redundant work through automation while significantly decreasing submission errors through automated process validation.
CACI International is an industry leader in the training and application of Reliability-Centered Maintenance (RCM). Responding to a need to further streamline workflow and improve RCM processes, CACI developed Electronic Reliability-Centered Maintenance (eRCM), a uniquely suited Web-based application that delivers the RCM process through an electronic tool. Now in its third release, this easy-to-use tool captures and stores all RCM process data in an electronic form. eRCM also provides a means for deploying and enforcing the Naval Sea Systems Command’s (NAVSEA’s) RCM process rules throughout government and industry.
CACI began the eRCM development process by instructing the software development program manager in RCM theory. Like all CACI RCM staff members, software developers are RCM Level I- and II-certified. The development team had to be familiar with all aspects of RCM methodology before writing code for this system. This is CACI’s way of institutionalizing RCM processes for the Navy in an electronic expert system. After the software development team was conversant in RCM theory and practice, they began the process of creating a rules-based, easily administered, expandable and portable world-class tool.
When starting an eRCM program, all users must first agree to roles (e.g., branch head, reviewer, approver, etc.). eRCM then divides the overall RCM process into two major process areas: development of maintenance requirements and construction of maintenance procedures. The eRCM tool captures the 12 core phases and analyzes RCM developments. All aspects of MIL-P-24534A are included. The eRCM tool consists of a breakdown of the RCM process elements logically grouped and placed in sequence or workflow. The individual phases that compose the RCM process are broken out as documents and captured separately in unique interfaces. Phases are then grouped into packages (Figure 2-1). Packages are part of the overall development track that reflect the workflow for a given development for all phases – from phase 1 through phase 12. The overall eRCM structure, as implemented by NAVSEA 04RM, is in accordance with MIL-P-24534A (Figure 2-2). Figure 2-3 illustrates the structural flow for Navy implementation of eRCM.
Use of the eRCM Web-based tool significantly reduces RCM development time, which is possible because eRCM eliminates redundant work through automation. CACI’s eRCM Web-based tool significantly decreases submission errors through an automated process validation. RCM developers also have easy access and centralized historical data as well as a built-in review/approval system with integrated ability for capturing and displaying multiple comments. An e-mail notification system alerts eRCM users of impending work. eRCM uses dashboards to convey general/detailed status, indicates work required, and provides a means for organizing and searching developments as well as for conducting overall development of RCM. Access is free, with an unlimited number of users allowed to accommodate additional review.
When a program or development cycle is complete, a data-locking system can be used to avoid previously approved packages being altered. Work packages can conversely be unlocked. The eRCM has a flexible reporting system for presenting data and deliverables in various formats as needed. All phases for the Navy, for example, are provided in original MIL-P format as contractually directed. Key bits of information are all captured as individual data elements that include system and equipment breakdowns and identification, functions, failures, failure modes, maintenance tasks, and periodicities. This allows for mapping a specific data element beyond eRCM and into other maintenance, scheduling, financial, and or related systems.
Figure 2-1. eRCM Phases Grouped Into Packages
Figure 2-2. eRCM Structural Implementation of Navy RCM Process
Figure 2-3. Structural Flow Diagram for Navy Implementation of eRCM
For more information see the
Point of Contact for this survey.