ASME RAM-2:2016 pdf free download

ASME RAM-2:2016 pdf free download.Reliability, Availability, and Maintainability Program Development Process for Existing Power Plants.
A reliability, availability, and maintainability (RAM) program Is a structured way to identify and deliver the RAM requirements of a power plant in the most cost-effective manner. This Standard provides guidance for the program implementation portion of the RAM process described in ASME RAM-i. It is intended to implement a comprehensive availability assurance program. This Standard Is intended for existing facilities.
2 SCOPE
This Standard amplifies and clarilies the requirements of ASME RAM-i for implementing a RAM program for a power-generation facility. This Standard assists in developing program goals, identifying a master equipment list (MEL) to load into the enterprise asset management system (EAMS), and populating scheduling systems with finished content as complete work orders that are ready to perform work. A RAM program includes hierarchical breakdown of the facility, tagging of equipment (i.e., components), risk categorization of systems and equipment tags. development of common standards for components, and customization for similar context locations in the plant. This Standard finalizes work organization as task lists in work orders, routes, and rounds. It provides a process to implement ASME RAM-i based on terminology and methodology used in power plants.
This Standard addresses the following:
(a) equipment assessment for risk
(b) asset tagging
(c) template selection and application
(d) equipment asset management software
(e) development and organization of work (e.g., development of operating procedures, rounds, and work orders)
(I) RAM program plans
(g) training required to implement the program
3 PURPOSE
The purpose ot this Standard is to provide information to enable plant personnel to develop an effective RAM process in accordance with ASME RAM-i. An effective RAM program ensures that critical plant equipment performs cost-effectively as intended by design.
7.6.1 Contexts. A context is a function of the attributes of a component that make the component unique, such as location in the plant. service, risk, criticality, environment, and age. Contexts should be grouped by relevant application. Use of context permits a standard template to be customized.
7.6.2 Sources. Standard templates are used as the basis, or source, for most custom templates; this minimizes rework and maintains consistency across all templates. Development of a custom template without the use of a standard template should be considered only where the equipment is unique. In such cases, it is the responsibility of the RAM engineer to consult the VTM and subject matter experts regarding the specific context and the risk associated with using a non-standard- based template.
7.6.3 Common Context AppLication. Multiple equipment items in a plant often share a common context. Using a common context standardizes work task content across all common instances of a group and is another way to simplify and standardize work. Grouping minimizes customization and variation that would increase program complexity, lower effectiveness. and raise costs. Context may Include
(a) duty cycle based on installation usage
(b) installation -dependent environmental stress
(c) functions, provided directly, indirectly, or redundantly
(d) diversity of equipment functions
(e) design margin
(17 other risk functions
RAM programs shall identify the common contexts by component type, and then group similar tags that share the same program based on similar context. A common equipment tag may identify a context group. The group may be identified by a common application, common tag, or similar unique name.
7.6.4 Custom TempLate Attributes. A custom template should be based on a similar component-type standard template and its attributes. RAM personnel customize standard templates Into custom templates by modifying the existing or providing additional application attributes, based on context. Custom templates share common attributes with standard templates. Considerations for custom template application include the following.