RAPID PM

Development
Presented by:

Jason Ballentine
ARMS Reliability
Objectives of Strategy Development
• Complete Baseline Maintenance Program before Startup

• Leverage Maintenance Knowledge Where Possible

• Engage Workers in Development, Build Ownership of PMs

• Develop Flexible PM Generation Capability

• Establish Feedback Loop for Task Improvement

• Provide Foundation for Later RCM and Strategy

Optimization Where Applicable
 Challenges

• Project Timeline Very Constrained

• Limited Vendor Access

• Over 10 to 1 Ratio of Inexperienced to

Experienced Craft

• Need to:
– Develop and translate clear, concise task
descriptions into Spanish
PM Development Options

PMO
RCM
RAPID
PM

?
FMEA MTA

Manf.
Rec’s
Rapid PM Development is the Solution

• Capture Vendor Recommendations for Preventive Tasks

• Align Tasks to Dominant Failure Modes

• Validate Tasks & Frequencies with Maintainers/Operators

• Develop Task Lists/Groups for Upload to CMMS

High Level Rapid PM Flowchart

Develop/Validate Develop First

Collect / Capture
Equipment Pass Library
Data
Hierarchy Model

Identify
Validate Library Validate Task
Exceptions for
Model with SMEs Groups/Routing
Larger Hierarchy

Analyze Results &

Generate Import to CMMS
Feedback /
TaskGroup PMs & Implement
Refine PMs
 Determining Level / Detail

• System, Sub-System or Maintainable Item Level?

• At What Level Do We Manage Failures for This System

• In-House/On-Site Repair or Vendor Repair /

Replacement?

• Swap Failed Unit for Factory Refurbished Spare?

Hierarchy Structure
Vendor Data Collection and Capture

• What Failure Modes are Vendor Recommended

Tasks trying to manage/prevent?
• What Other Significant Ways Can Equipment Fail?
• Is There a Best Practice Task Relevant for this
Maintainable Item?

• Leave a “Trail of Assumptions”

– Record Sources and Details for future Review
Trail of Assumptions
 Developing an Equipment Library

• Develop a RCMCost Library Model for each Covered

Equipment Type or Model.

• Complete Functional Structure with Failure Mode, Task

Description, Duration and Labor Required.

• Validate with SME’s

• Update Failure Modes and Tasks where appropriate

when Equipment or Operating Context varies
Significantly

• Populate Area Hierarchy Model with Library Model Data

Library Creation
Inspection Task Detail
Apply Library Model to Hierarchy Model

Library
Models
Like
Pumps
Populating PM Template
Note Fields
PM Template, Page 1A
PM Template, Page 2A
Successes of Rapid PM Development

• Baseline PM program in place prior to plant start-up.

• Vendor recommendations captured and validated.

• Best Practice Tasks added where appropriate.

• Sense of Ownership of PM Program High –based on level

of feedback for refinements in routing/ordering, task
language etc.

• Provides means of Educating New Operators and

Maintainers in What Critical Areas Required to Ensure High
Plant Availability.

• Provides Systematic Process of Knowledge Capture that

can be Challenged and Updated over Life of Plant.
Questions?

JASON BALLENTINE
Engineering Manager

jballentine@armsreliability.com