SMRP Annual Conference

September 28 - October 1, 2026 Raleigh, NC  #SMRP2026

Join Us in Raleigh, NC

We’re proud to call Raleigh home and look forward to welcoming maintenance and reliability professionals from around the world during SMRP. Beyond the conference, downtown Raleigh offers exceptional dining, local breweries, rooftop bars, live entertainment, and countless opportunities to connect with industry peers. Whether you’re looking to discuss reliability strategies over coffee, continue a conference conversation at dinner, or simply experience the city’s unique blend of innovation and Southern hospitality, we hope you’ll take advantage of your time in Raleigh. If you’re attending SMRP, stop by our booth 914/916—we’d love the opportunity to meet, network, and share why we’re proud to call this city home.

Here's the SMRP workshop you don't want to miss

Many organizations invest heavily in Reliability Centered Maintenance (RCM) yet still face repeat failures and inconsistent performance. The issue is rarely the analysis—it’s the gap between insight and execution. This 4-hour workshop introduces a practical, field-tested approach to closing that gap by integrating RCM with Root Cause Problem Elimination (RCPE). Designed for intermediate practitioners, the session focuses on when to apply RCM versus RCPE—and how they work together to prevent failures, detect issues earlier, and eliminate recurring problems. Participants will learn to identify breakdowns between strategy and execution, align maintenance and operations, and implement cost-effective, sustainable solutions. Using a common-sense “how-can” methodology, attendees will gain tools applicable across industries and asset types. The result: a shift from reactive maintenance to proactive reliability, driving improved uptime, capacity, and operational consistency.

8-step-checklist-preventive-maintenance-program-download
Free Download & Video

8 Steps to Successfully Implement Preventive Maintenance

Reduce your costs with an effective PM program

This field is for validation purposes and should be left unchanged.