HARDWARE PARTITIONING Module 3 UNIT II RCM PROCESS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."

Slides:



Advertisements
Similar presentations
DATA CONSIDERATIONS Module 3 UNIT IV ADDITIONAL TOPICS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
Advertisements

Trane Voyager™ rooftop units
Unit III Module 6 - Developing Age Exploration Tasks
Unit I Module 1 - Introduction to RCM
Root Cause Analysis for Effective Incident Investigation Christy Wolter, CIH Principal Consultant Environmental and Occupational Risk Management (EORM.
NERC Lessons Learned Summary December NERC lessons learned published in December 2014 Three NERC lessons learned (LL) were published in December.
Using Data Flow Diagrams
PLANT DESIGN (I) Prof. Dr. Hasan farag.
STEP 1 Develop/update RCM Program Plan STEP 2 New Equipment Design Recommended STEP 2B Complete Level 2 Breakdown STEP 4 Complete Levels 3 and 4 Breakdowns.
Module 3 UNIT I " Copyright 2002, Information Spectrum, Inc. All Rights Reserved." INTRODUCTION TO RCM RCM TERMINOLOGY AND CONCEPTS.
Group Meeting #1 January 29 th, 2013 Michael Bentel Jeremy David Erik Peterson Arpit Shah 1.
Failure Modes and Effects Analysis A Failure Modes and Effects Analysis (FMEA) tabulates failure modes of equipment and their effects on a system or plant.
" Copyright 2002, Information Spectrum, Inc. All Rights Reserved." RCM DECISION LOGIC Module 5 UNIT II RCM PROCESS.
Elisati Hulu. Definition  “a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project.
Elisati Hulu. Definition  “a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project.
W Reliability Centered Maintenance w Day II w Salih O. Duffuaa.
Using Dataflow Diagrams
PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
Unit III Module 4 - Hard Time Task
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Combined_Cycle_Power_Plant Prepared by: Nimesh Gajjar.
Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 4 Product/Process Innovation McGraw-Hill/Irwin.
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
Energy Management Proposed At KTPS. Objectives for Energy Management Generate energy at lowest possible price Manage energy use at highest energy efficiency.
CPS ® and CAP ® Examination Review OFFICE SYTEMS AND TECHNOLOGY, Fifth Edition By Schroeder and Graf ©2005 Pearson Education, Inc. Pearson Prentice Hall.
 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Quality and Innovation in Product and Process Design.
Unit I Module 2 - NAVAIR RCM Policy and Organization
FAILURE MODE, EFFECTS, AND CRITICALITY ANALYSIS (FMECA) Module 4 UNIT II RCM PROCESS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
FRANKLIN engineering group, inc. Start-up Shutdown Malfunction Plan Development and Implementation Duncan F. Kimbro
An Introduction to Software Architecture
TASK PACKAGING Module 1 UNIT IV ADDITIONAL TOPICS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1 Module 8 UNIT III " Copyright 2002, Information Spectrum, Inc. All Rights Reserved." HOW TO PERFORM RCM ANALYTICAL METHODS.
Copyright 2008 Introduction to Project Management, Second Edition 2  Many people have heard the following sayings: ◦ If you fail to plan, you plan to.
UNIT II RCM PROCESS Module 2 PLANNING AND PREPARATION " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
SUSTAINING THE ANALYSIS Module 2 UNIT IV ADDITIONAL TOPICS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a logical hierarchy of work packages involved in a project.
Work Breakdown Structure Use and Demo
Fuel Cell Systems Engineering, F06 Fuel Cell Systems Engineering Systems Engineering Process.
UNIT III HOW TO PERFORM RCM Module 1 RCM SOFTWARE REVIEW " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNP 1 v3.0 Module 1 Overview of Scalable Internetworks.
SERVICING AND LUBRICATION TASKS Module 2 UNIT III HOW TO PERFORM RCM " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
SELECTING TASK OR OTHER OPTIONS Module 7 UNIT III HOW TO PERFORM RCM " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
Unit II Module 1 - RCM Process Overview
ON CONDITION TASK Module 3 UNIT III HOW TO PERFORM RCM " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
8-1 Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
1 Fundamentals of RCM Analysis R ELIABILITY C ENTERED M AINTENANCE.
FAILURE FINDING TASK Module 5 UNIT III HOW TO PERFORM RCM " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
DBS201: Data Modeling. Agenda Data Modeling Types of Models Entity Relationship Model.
Continuously Pushing the Limits of Innovation, Technology & Conventional Thinking For Official Use Only RCM Theory and Concepts Workshop RCM Theory and.
Materials Management (MM) Organizational Structure EGN 5620 Enterprise Systems Configuration (Professional MSEM) Fall, 2013.
Failure Modes, Effects and Criticality Analysis
Stracener_EMIS 7305/5305_Spr08_ Reliability Centered Maintenance Analysis (RCMA) Dr. Jerrell T. Stracener, SAE Fellow Leadership in Engineering.
FAILURE MODE EFFECTIVE ANALYSIS. Introduction Failure Mode Effect Analysis is an analytical technique that goes in for combining Technology and Experience.
Process Safety Management Soft Skills Programme Nexus Alliance Ltd.
Breakdown Work Structure Applying Management Tools to a Project.
Version 1.0, May 2015 BASIC PROFESSIONAL TRAINING COURSE Module XX Regulatory control Case Study This material was prepared by the IAEA and co-funded by.
Accounting Information Systems: An Overview
Architecture Concept Documents
Defining the Activities
Model of block distribution system (Fukuoka City Waterworks Bureau)
Root Cause Analysis for Effective Incident Investigation
COT 5611 Operating Systems Design Principles Spring 2012
An Introduction to Software Architecture
Unit I Module 3 - RCM Terminology and Concepts
Piping and Instrumentation for Process Industries
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
BASIC PROFESSIONAL TRAINING COURSE Module XX Regulatory control Case Study Version 1.0, May 2015 This material was prepared by the IAEA and.
Presentation transcript:

HARDWARE PARTITIONING Module 3 UNIT II RCM PROCESS " Copyright 2002, Information Spectrum, Inc. All Rights Reserved."

Introduction Module Preview: Hardware Partition IntroductionIntroduction Exercise Exercise Review and Summary HARDWARE PARTITIONING

Module Objective: This module will: Provide an introduction to the concept of Hardware Partitioning Provide an introduction to the concept of Hardware Partitioning Demonstrate how to develop a Hardware Partition Demonstrate how to develop a Hardware Partition Show how performing RCM at different levels affects the analysis. Show how performing RCM at different levels affects the analysis. IntroductionIntroduction HARDWARE PARTITIONING

1. Identify Team and responsibilities 4. Identify and document Review Process 2. Identify analysis items 5. Orientation/Training 3. Prioritize Items 6. Ground Rules and Assumptions PLANNING AND PREPARATION ANALYSIS RCM Process Analysis Approac h/ RCM Plan Analysis MaintenanceRequirementsMaintenanceRequirements MaintenanceProgramMaintenanceProgram DataData 1.Equipment Kick-off Meeting 2.Initial Data Gathering 3.Hardware Partition 4.Function 5.Functional Failure 6.Failure Mode 7.Failure Effects 8.Failure Consequences 9.Task Evaluation 10.Task Selection 1.Package Maintenance Task 2.Implement Other Actions Results IMPLEMENT RESULTS 1.Emergent Issues 2.Age Exploration 3.Hardware Changes 4.Trend/degrader analysis 5.Document Reviews SUSTAIN PartitioningPartitioning

Definition:Definition: For the purposes of this course: The terms “Asset”, “Hardware”, and Item” are used interchangeably to describe the equipment under analysis PartitioningPartitioning HARDWARE PARTITIONING

Definition:Definition: HARDWARE PARTITION A logical hierarchical division of an asset into progressively lower levels to show relationships among systems, subsystems, components, etc. Also called EQUIPMENT HIERARCHY or HARDWARE BREAKDOWN PartitioningPartitioning HARDWARE PARTITIONING

Aircraft Example: FLT CONTROL SYS AIRCRAFT1 LANDING GEAR FUEL SYSTEM CONTROLRODS14220RUDDER14230 TRIM TAB SUBSYSTEM 1B2 RUDDER SUB SYS SUBSYSTEM 1B4 SUBSYSTEM 1B1 ACTUATOR14210TRIMMOTOR14250 PartitioningPartitioning HARDWARE PARTITIONING

Power Plant Example: UNIT 2 N02 POWER PLANT UNIT 1 N01 UNIT 3 N03 FLY ASH N02NA BED ASH N02NB BOILER N02B WASTE SYSTEM N02N FUEL N02F PartitioningPartitioning HARDWARE PARTITIONING

Air Compressor Example: PRESSURIZATION SYSTEM 1B INGERSOLL RAND COMPRESSOR SYSTEM1ASYSTEM1C COMPR1B3B CHK VALVE 1B3C AIR FILTER 1B3D SUBSYSTEM 1B2 1B2 AIR PUMP ASSY 1B3 SUBSYSTEM1B4 SUBSYSTEM1B1 MOTOR1B3APRESSURE REG 1B3E PartitioningPartitioning HARDWARE PARTITIONING

Partition may use any logical system: CMMS CMMS Work Unit Code Work Unit Code Maintenance/Operators manuals Maintenance/Operators manuals OEM Parts breakdown OEM Parts breakdown Physical boundaries Physical boundaries Considerations:Considerations:PartitioningPartitioning HARDWARE PARTITIONING

Hardware Partitioning Considerations/Suggestions: Must be a physical partition: Must be a physical partition: Each item should only be in one branch of the hierarchy Each item should only be in one branch of the hierarchy Consider how failure data is recorded Consider how failure data is recorded Manuals may provide logical divisions of equipment Manuals may provide logical divisions of equipment Boundaries should be clearly identified: Boundaries should be clearly identified: List specific valves, terminal blocks, etc. that end one system and begin another List specific valves, terminal blocks, etc. that end one system and begin another Boundaries should take into consideration functions of equipment Boundaries should take into consideration functions of equipment General boundary statements can be used General boundary statements can be used Be prepared to adjust boundaries: Be prepared to adjust boundaries: During an analysis, better partitioning may become evident, especially when defining functions During an analysis, better partitioning may become evident, especially when defining functions Partition one level below where the analysis will be performed: Partition one level below where the analysis will be performed: Provides helpful information during the analysis Provides helpful information during the analysis Considerations:Considerations:PartitioningPartitioning HARDWARE PARTITIONING

Identification:Identification: Hardware Partition should include a Numbering or Identification System Uniquely identifies each system, sub-system, etc. Uniquely identifies each system, sub-system, etc. Should identify relationships between parent and child items Should identify relationships between parent and child items Can use existing system or create a new one: Can use existing system or create a new one: CMMS scheme CMMS scheme Equipment Identification Numbers Equipment Identification Numbers Military: WUC, Logistics Control Number, etc. Military: WUC, Logistics Control Number, etc. PartitioningPartitioning HARDWARE PARTITIONING

What level to perform RCM analysis? System or Subsystem level is usually the best starting point System or Subsystem level is usually the best starting point Complexity or other factors may warrant a lower or higher level Complexity or other factors may warrant a lower or higher level Different levels can be used within same analysis Different levels can be used within same analysis Consider on-equipment maintenance level Consider on-equipment maintenance level Level of Analysis: PartitioningPartitioning HARDWARE PARTITIONING

System/Subsystem Analysis: System/Subsystem Analysis: Most efficient for a large scale analysis effort Most efficient for a large scale analysis effort Reduces number of functions to identify Reduces number of functions to identify Secondary functions are easier to identify Secondary functions are easier to identify Aids in proper effects determination Aids in proper effects determination Aids in identification of “significant” failure modes Aids in identification of “significant” failure modes Allows combination of failure modes where it makes sense Allows combination of failure modes where it makes sense Helps focus maintenance tasks on preservation of system/end item operation Helps focus maintenance tasks on preservation of system/end item operation Level of Analysis: PartitioningPartitioning HARDWARE PARTITIONING

Component level analysis: Most effective for limited analysis of a few specific hardware items or failure modes Most effective for limited analysis of a few specific hardware items or failure modes Also useful for analysis of components used on multiple systems Also useful for analysis of components used on multiple systems Level of Analysis: PartitioningPartitioning HARDWARE PARTITIONING

Hardware partition should provide boundary definitions that eliminate confusion over what is/is not included in analysis Examples: Piping or tubing Piping or tubing Controls Controls Air or water supply sources Air or water supply sources Brackets, fixtures, or attach points Brackets, fixtures, or attach points Boundaries/Interfaces:Boundaries/Interfaces:PartitioningPartitioning HARDWARE PARTITIONING

Class Exercise Objective: Perform a End Item Hardware Partion for a Coffee Maker PartitioningPartitioningExerciseExercise HARDWARE PARTITIONING

HOT PLATE SUBSYSTEM 1B4 PWR SWITCH SUBSYSTEM 1B1 CLOCK PROGRAMMER SUBSYSTEM 1B2 WATER HEATING SUBSYSTEM 1B3 FILTRATION SUBSYSTEM 1A2 CARAFE SUBSYSTEM 1A3 WATER RESERVOIR SUBSYSTEM 1A1 3 Fly Ins COFFEE MAKER 1 ELECTRICAL SYSTEM 1B BREWING SYSTEM 1A ExerciseExercise

IntroductionIntroduction Learning Objectives Hardware Partitioning Definition Definition Identification Identification Considerations Considerations Level of Analysis Level of Analysis Boundaries & Interfaces Boundaries & Interfaces ExerciseExercise Review and summary Provided an understanding of the Hardware Partitioning Process. Module Objective HARDWARE PARTITIONING

End of Module up next…….. FMECA End of Module up next…….. FMECA