Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ASME RAM-2-2016 — RAM Program Development Process for Existing Power Plants
🔋 ASME RAM-2-2016 is the American National Standard for the Reliability, Availability, and Maintainability (RAM) Program Development Process for Existing Power Plants. It was approved by the RAM Standards Committee on September 13, 2016, and approved by ANSI as an American National Standard on December 2, 2016. The Standard amplifies and clarifies the requirements of ASME RAM-1 for implementing a RAM program at a power-generation facility, providing an actionable development process: setting program goals, identifying a master equipment list (MEL) to load into the enterprise asset management system (EAMS), populating scheduling systems with finished content as work orders that are ready to perform work, and finally organizing work as task lists, work orders, routes, and rounds.
💡 The concept of RAM rests on a fundamental principle: power plant availability is a necessary goal. The ideal balance between reliable engineering design, proper equipment operation, and effective, efficient maintenance at the best time yields measurable, real-life availability goals.
1. Scope and Purpose 📌
The purpose of RAM-2 is to provide information that enables plant personnel to develop an effective RAM process in accordance with ASME RAM-1. The Standard describes one concrete way to implement a RAM program in an existing power plant and explicitly addresses seven areas:
- Equipment assessment for risk: risk calculations, expert opinion, and failure experience identify design-inherent risks that drive the scheduled maintenance and monitoring program;
- Asset tagging: hierarchical breakdown of the facility and tagging of equipment (components);
- Template selection and application: common standards for components plus customization for similar context locations in the plant;
- Equipment asset management software (EAMS): loading the MEL into the enterprise asset management system;
- Development and organization of work: operating procedures, rounds, and work orders;
- RAM program plans: documented plans and risk categorization;
- Training required to implement the program: ensuring personnel capability.
⚠️ RAM-2 follows a risk-informed, performance-based approach but does not cover human performance. The Standard assumes plant practices follow manuals, industry standards, and related asset management guidance.
2. Components of the RAM Program 🏗️
The RAM program is a system that organizes the facility, its equipment, and the work: it begins with a hierarchical breakdown of the facility (plant → system → equipment → component), proceeds with tagging each piece of equipment, then performs risk categorization of systems and equipment tags, develops common standards for components, customizes templates for similar context locations, and finally organizes the work into work orders, routes, and rounds. Traditional terms for RAM-related work include preventive maintenance, scheduled maintenance, operations monitoring, and rounds; RAM-2 gives directly actionable guidance to those responsible for equipment-asset-management programs.
| Program Element | Main Content | Outputs |
|---|---|---|
| Facility hierarchical breakdown | Plant → system → equipment → component | Hierarchy tree |
| Asset tagging | Unique identification of each piece of equipment | Tag list, identification procedure |
| Risk categorization | Grade systems/equipment by failure consequence and probability | Risk level table |
| Template development and application | Common component standards + location-specific customization | Template library, customized templates |
| Work organization | Task lists → work orders / routes / rounds | Executable work orders, inspection routes |
💡 The critical closed loop in RAM-2 is from MEL to “ready-to-perform work orders”: equipment is not just catalogued in a register — risk categorization must drive fully populated, execution-ready work orders and inspection content attached to each equipment record.
3. Program Life Cycle: Predevelopment, Development, Implementation, Revision 🔄
The body of RAM-2 (Sections 6–9) divides the program life cycle into four phases, with Mandatory Appendix I providing full-process flowcharts (Figs. I-1 through I-6):
- Predevelopment: define program goals, scope, and resources; identify stakeholders; assess existing asset-management foundations and data quality;
- Development: build the MEL and hierarchy, complete asset tagging, perform risk assessment and categorization, select/customize templates and inject them into the EAMS;
- Implementation: load the developed content into scheduling systems as complete work orders, launch rounds and routes, and deliver personnel training;
- Revision: continuously revise the program based on failure experience, assessment results, and operating data to keep it effective.
⚠️ The four phases are a cycle, not a one-off: the RAM program is not a “build once and lock” document. As failure records, modifications, and operating experience accumulate, risk categorization, template content, and work-order frequencies should be periodically reviewed and revised.
4. Risk Assessment and Work-Order Development 🔬
Risk assessment focuses resources on the equipment that most deserves management. RAM-2 is risk-informed and performance-based: risk calculations, expert opinion, and failure experience identify design-inherent risks, which drive the scheduled maintenance and monitoring program. Typical risk dimensions include failure consequence (impact on availability, safety, and environment) and failure probability (supported by availability and historical failure data). The table below shows a common grading scheme with example responses:
| Risk Level | Typical Criteria (example) | Typical Response |
|---|---|---|
| High (A) | Failure directly trips the unit or derates output, or threatens safety | Enhanced condition monitoring, RCM-based preventive maintenance, spare strategy review |
| Medium (B) | Failure affects efficiency or causes local outage, repairable in a short time | Regular rounds, scheduled maintenance, spare-parts management |
| Low (C) | Minor consequence, easy to repair, or redundant | Basic rounds, corrective maintenance |
Work-order development converts this analysis into executable actions: each work order contains a task list, required resources, safety requirements, and acceptance criteria; similar equipment is generated from templates, then customized for location differences (environment, load, criticality). Work orders loaded into the scheduling system should be ready to perform work as loaded.
🚨 Do not turn the MEL into a “big but unfocused” list: if every piece of equipment is maintained with equal intensity, resources are diluted by low-value assets and the truly critical machines get insufficient attention. Risk categorization must come first, and maintenance intensity must match risk level.
5. Engineering Practice Essentials 🛠️
- 🔍 Goals first: before developing the program, define availability goals (e.g., annual availability, cap on forced outages) and align every activity with them.
- 🔧 Data quality is foundational: inaccurate equipment records, hierarchy relationships, and historical work-order data in the EAMS will corrupt risk categorization and templates — clean the data first.
- 📊 Templates must be customized: the same pump model in different systems (e.g., main feedwater vs. auxiliary cooling water) has different risk levels; template content should be customized by location.
- 📋 Training in parallel: Section 7 lists training as a necessary element; operations and maintenance training should be completed in step with work-order loading during implementation.
✅ Good practice: start with one pilot system (e.g., main feedwater or turbine lube-oil system), walk the full loop “decompose → tag → categorize → build templates → generate work orders → load → perform rounds,” validate it, then roll out plant-wide — this significantly reduces implementation risk.
6. Frequently Asked Questions ❓
❓ Q: How do RAM-1 and RAM-2 relate?
A: RAM-1 describes the higher-level RAM program requirements; RAM-2 amplifies and clarifies them for existing power plants using power-plant terminology and methodology, and provides a concrete development process — it is RAM-1’s “implementation roadmap.”
A: RAM-1 describes the higher-level RAM program requirements; RAM-2 amplifies and clarifies them for existing power plants using power-plant terminology and methodology, and provides a concrete development process — it is RAM-1’s “implementation roadmap.”
❓ Q: What is the master equipment list (MEL), and why load it into the EAMS?
A: The MEL is the list of equipment/components managed under the RAM program — the object set for risk categorization and work-order development. Only after loading the MEL into the enterprise asset management system (EAMS) can tagging, categorization, templates, and work orders be implemented and continuously maintained on one data platform.
A: The MEL is the list of equipment/components managed under the RAM program — the object set for risk categorization and work-order development. Only after loading the MEL into the enterprise asset management system (EAMS) can tagging, categorization, templates, and work orders be implemented and continuously maintained on one data platform.
❓ Q: What does “risk-informed, performance-based” mean?
A: Risk-informed means using risk calculations, expert opinion, and failure experience to identify risks and guide maintenance decisions; performance-based means continuously adjusting the program according to actual equipment performance and availability goals rather than mechanically following fixed intervals.
A: Risk-informed means using risk calculations, expert opinion, and failure experience to identify risks and guide maintenance decisions; performance-based means continuously adjusting the program according to actual equipment performance and availability goals rather than mechanically following fixed intervals.
🔍 Q: What is the difference between rounds and routes in the program?
A: Routes are prearranged inspection paths and sequences; rounds are the recurring inspection actions executed along those routes. Together they institutionalize day-to-day condition monitoring at the execution level and, with preventive-maintenance work orders, make up the program’s work organization.
A: Routes are prearranged inspection paths and sequences; rounds are the recurring inspection actions executed along those routes. Together they institutionalize day-to-day condition monitoring at the execution level and, with preventive-maintenance work orders, make up the program’s work organization.
