More Related Content
Similar to 1 implementación de_mantenimiento_basado_en_fiabilidad_(rcm)
Similar to 1 implementación de_mantenimiento_basado_en_fiabilidad_(rcm) (20)
1 implementación de_mantenimiento_basado_en_fiabilidad_(rcm)
- 2. Meridium – Partner Estratégico de SAP
Founded 1993
Global presence
Americas
Roanoke, Virginia, USA – Corp HQ
Houston, Texas, USA
Sao Paulo, Brazil
Blacksburg, VA, USA (Virginia Tech)
Europe Integrated Software Implementation &
Walldorf, Germany Applications Integration Service
Middle East/North Africa
Dubai, UAE
Asia-Pacific/South Africa
Perth, Australia
Bangkok, Thailand
Pune, India
Johannesburg, South Africa
Our focus
Help customers achieve predictable RCMO / APM Strategic
production at the lowest sustainable cost Consulting & Partners
Serving asset-intensive industries Education
880+ licensed locations
70+ countries
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 2
- 3. Relación SAP / Meridium
1996 – First joint customers
2000 – Certified integration between SAP PM & Meridium APM
2002 – Synchronization of SAP Master Data in Meridium APM
2003 – BAPI based interface APM <-> SAP
2004 – RCMO product concept and design
2005 – RCMO product co-development
2006 – RCMO™ product release and xApps Certification
2007 – RCMO™ becomes SAP Endorsed Business Solution
2007 – Meridium joined the SAP Industry Value Network for
• Oil and Gas • Utilities
• Forest and Paper • Mining
• Chemicals
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 3
- 4. RCMO forma parte del Roadmap de SAP
Utilities
Oil & Gas
Chemicals
Mining
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 4
- 6. RCMO Live Customers (Excerpt)
Power Generation Canada
Mining Australia
Aluminum Smelter Australia
Paper Netherlands
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 6
- 7. RCMO New Customers in 2007/2008 (Excerpt)
Power Generation USA, Global
Transmission & Distribution
Water Utility USA
Paper Finland, Global
Mining South Africa
Energy, Oil & Gas Canada
Oil & Gas Abu Dhabi
Power Generation Spain
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 7
- 8. Meridium – Customer Successes
Meridium RCMO™ is aanew RCM solution
Meridium RCMO™ is new RCM solution
built with the latest SAP technology and
built with the latest SAP technology and
tightly integrated with SAP Enterprise
tightly integrated with SAP Enterprise "Queensland Alumina has chosen RCMO for our
Asset Management. RCMO...
Asset Management. RCMO... reliability centered maintenance initiative largely
- greatly simplifies the process of due to the integration of the product with our
- greatly simplifies the process of
implementing RCM recommendations in SAP existing SAP system. QAL believes that an effective
implementing RCM recommendations in SAP
- makes it easy to measure performance and RCM program will contribute to optimizing
- makes it easy to measure performance and
adjust strategies over time equipment performance, help control risk, and
adjust strategies over time
- provides the framework for you to define
assist in improving the reliability of our production
- provides the framework for you to define assets.”
maintenance strategies based upon RCM and
maintenance strategies based upon RCM and
Failure Modes and Effects Analysis (FMEA)
Failure Modes and Effects Analysis (FMEA)
principles Colin McDonald,
principles
Maintenance Services Manager
- integrates the recommendations from an
- integrates the recommendations from an
RCM analysis into SAP Maintenance Plans in
RCM analysis into SAP Maintenance Plans in
SAP
SAP
“Ramp-up went much more smoothly than we
- drives automated re-evaluation of
- drives automated re-evaluation of could have hoped for. Our IT Project Manager said
maintenance strategies to ensure
maintenance strategies to ensure this was one of the best enterprise software
effectiveness is constantly measured for
effectiveness is constantly measured for
continuous improvement installations she had seen. Our staff work in SAP
continuous improvement
every day and with RCMO ‘bolted-on’ and widely
available, we can drive the RCM methodology and
culture harder and deeper into our organization.”
Richard Brittin, Manager
Reliability and Performance
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 8
- 9. TransAlta, Canada
KEY CHALLENGES
RCM done at 2 facilities in point solutions
Program localized, no sharing of information
No common methodology for RCM
TransAlta: Canadian Utility
consisting of: PROJECT OBJECTIVES
Common maintenance strategies fleet wide
• 8,444 megawatts (MW) of
capacity and an additional Understanding critical assets and overall risk
540 MW under Optimize O&M costs
development. Increased plant reliability and availability
• 49 facilities in four
regions:
Canada; the U.S.; WHY RCMO WAS SELECTED
Mexico; Australia Integration to existing portal for fleet wide accessibility
Repository for all analyses to leverage across sites
Integration with SAP EAM and BW
Ability to do RCM and FMEA in one system
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 9
- 10. TransAlta RCMO Implementation Plan
Application Installation
Dev ->Test->Production migration over several weeks due to larger SAP
migration plans
Integrated into existing TransAlta Portal for fleet-wide accessibility
Provided tool to allow engineers to build systems of technical objects very
quickly with Excel plug-in
No migration of existing analyses during ramp-up
RCMO User Training
Introduction to RCM (1day)
Product Training (1 day)
Total Implementation Calendar Time
Approximately 8 weeks (4 weeks on-site)
Part of larger migration path and followed TA process
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 10
- 11. TransAlta, Canada
“…Our staff work in SAP every day and with RCMO
“bolted-on” and widely available, we can drive the
RCM methodology and culture harder and deeper into
our organization.”
Richard Brittin -
Manager of Reliability &
“Ramp-up went much more smoothly than we could
Performance
have hoped for. Our IT Project Manager said this was
one of the best enterprise software installations she
had seen, either production or ramp-up.
The Meridium team made commitments to deliver a
scope of work by a certain date and met that
commitment.”
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 11
- 12. Queensland Alumina Limited, Australia
KEY CHALLENGES
Had tried several RCM methodologies in the past
Result was 611 studies and 32,000 recommendations
These were never implemented into SAP EAM
PROJECT OBJECTIVES
QAL – Australian alumina
Ability to streamline analysis implementation
refiner:
Maintain justification for maintenance activity
• Largest alumina refinery Compare existing asset budget to budget from RCM
in the world Implement a “living” RCM program
• Use the Bayer process –
very corrosive for
equipment WHY RCMO WAS SELECTED
SAP integrated approach to creating equipment care plans
Able to reclaim and load existing analyses
Multiple methodologies in one system
Reporting on analysis progress and strategy performance
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 12
- 13. Queensland Alumina Limited, Australia
“Queensland Alumina has chosen RCMO for our reliability
centered maintenance initiative largely due to the integration
of the product with our existing SAP system”
Colin McDonald,
Maintenance Services “QAL believes that an effective RCM program will contribute
Manager to optimizing equipment performance, help control risk, and
assist in improving the reliability of our production assets…
in essence, to stay in control and to modify strategies where
there is a gap in performance.“
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 13
- 15. Motivaciones Habituales para RCM/FMEA
Proteger a las Personas y al Medio
Ambiente
Reducir Costes año tras año
Aumentar los Márgenes
Consumir menos Energía
Eliminación de Pérdidas
Alcanzar las metas de Producción
Mantener la calidad del Producto
¡La Fiabilidad impacta
¡La Fiabilidad impacta
directamente en todo lo
directamente en todo lo
anterior!
anterior!
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 15
- 16. Historia de algunos Conceptos de Mantenimiento
innovative
High
Reliability
Centered
Maintenance
Risk Based
Reliability
tim Maintenance
e
Condition based
Maintenance
Preventive
Maintenance
Reactive
Low
Maintenance
traditional
Low High
Maintenance effort
Direct / indirect cost
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 16
- 17. Equilibrio entre Coste y Fiabilidad
“Low Hanging Fruit”
Total Cost of
Optimum Improved Reliability
Effectiveness
Total Costs
Profit gained Cost to Improve
from improved availability Reliability
Cost of Unreliable
Production
Reliability
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 17
- 18. Del Mantenimiento Reactivo a una Organización
Basada en la Fiabilidad: Beneficios
Typical Overall Impact: Implement and monitor the right maintenance
EFFECTIVE &
1 – 15% Of EFFICIENT strategies
Implement proper monitoring procedures
Maintenance Costs Provide feedback to engineering for increased
reliability
Increase productive life of assets
ASSET LIFE Reduce failure rates and frequencies
Identify which OEM’s provide most the reliable equipment
Increase production by limiting downtime
YIELD & PRODUCTION Increase capacity with limited investment
Focus on critical production assets and equipment
RISK, REGULATORY
Reduce regulatory penalties
& SAFETY Reduce catastrophic failures and save lives
Manage risk of overall asset operations
Reduce maintenance costs (labor & materials)
COST
Reduce scrap and rework
REDUCTION
Reduce maintenance backlog
Increase quality
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 18
- 19. ¿Qué es RCM?
“Reliability Centered
“Reliability Centered “RCM hace énfasis en una
“RCM hace énfasis en una
Maintenance es un método
Maintenance es un método aproximación proactiva al
aproximación proactiva al
formal para determinar los
formal para determinar los mantenimiento. Intenta equilibrar
mantenimiento. Intenta equilibrar
requerimientos en cuanto
requerimientos en cuanto las mejores prácticas de
las mejores prácticas de
a mantenimiento de un
a mantenimiento de un mantenimiento para mitigar un
mantenimiento para mitigar un
activo en su contexto
activo en su contexto fallo potencial con la importancia
fallo potencial con la importancia
operativo.”
operativo.” de prevenir ese fallo.”
de prevenir ese fallo.”
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 19
- 20. Breve Historia del RCM
El Mantenimiento Centrado en la Fiabilidad (RCM) es una metodología
probada para desarrollar estrategias de mantenimiento efectivas
El RCM se aplicó por primera vez comercialmente
en los años sesenta en la industria aeronáutica
Como resultado, los aviones que utilizamos
hoy en día son cien veces más fiables
La tasa de accidentes por millón de despegues
se redujo de 6 a 0,02
Actualmente se utiliza prácticamente en todos los sectores que hacen un uso
intensivo de activos
Durante décadas, los fabricantes han utilizado el RCM para:
Mejorar la fiabilidad operativa
Optimizar el rendimiento del equipo
Tomar mejores decisiones en cuanto a diseño y ciclos de vida
Control de riesgo
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 20
- 21. Contexto Operativo
Accepted Thinking…
Manufacturers recommendations are adequate for
formulating failure management policies
Main Pump
The Reality…
Generic maintenance
policies often force
Standby
Pump over-maintenance and
are not the most
efficient way to manage
Main Pump
equipment failures
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 21
- 22. Estrategia de Mantenimiento: ¿Buscar el
momento adecuado?
Scheduled PM
Activity
Probability
of
Failure
Time
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 22
- 23. La realidad del Fallo (Industria Aeronáutica)
4%
1 2% 11% age-related
5%
2 7%
14%
89% NOT age-related
68%
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 23
- 24. Registro de Seguridad de la Aviación…
¿Qué ocurrió al aplicar los principios del RCM?
30
25
Accidents per million takeoffs
20
15
Non-US Operators
10
5
US Operators
59 61 63 65 67 69 71 73 75 77 79 81 83 85 87 89 91 93 95
Year C.A. Shifrin; Safety in the Civil Aviation Industry, from “Aviation Safety Takes Center
Stage Worldwide”, Aviation Week & Space Technology: Vol. 145 No. 19, pp. 46-48
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 24
- 25. Beneficios de la Implementación de RCM
Failure Finding
• Reduces risk
Tasks • Generally non-intrusive
Condition
Before
• Generally non-intrusive
Monitoring • If it’s working leave it
alone Failure Finding
RCM &
Tasks
Scheduled
Restoration •Intrusive
Condition
Discard Tasks RCM
•Impacts production
•Often introduces defects Monitoring
Scheduled
Defects Restoration &
• Impacts production
Unplanned • May have safety or Discard Tasks
High costs environmental
consequences Defects
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 25
- 26. Las 7+1 Preguntas de RCM
¿Qué activos o sistemas quiero analizar?
1. ¿Cuáles son las funciones y los estándares de
rendimiento deseados para el activo en su
contexto operativo?
2. ¿Cuáles son los fallos que hacen que el
equipo deje de cumplir sus funciones?
3. ¿Qué causa cada fallo funcional?
4. ¿Qué pasa cuando ocurre un fallo?
5. ¿Qué consecuencias tiene el fallo?
6. ¿Qué puede hacerse para predecir o prevenir
el fallo?
7. ¿Qué puede hacerse si el fallo no puede
predecirse o prevenirse?
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 26
- 27. Las 7+1 Preguntas de RCM
¿Qué activos o sistemas quiero analizar?
1. What are the desired functions and performance standards? Functions
To fill a tank at a minimum rate of 100 gal. per min
2. In what ways can it fail to fulfil its functions? Functional Failure
RCM
Tank fills at a rate of less than 100 gal. per min
3. What causes each functional failure? Failure Modes
Filter clogs due to debris
FMEA
4. What happens when each failure occurs? Effects
Flow rate is restricted until pump can no longer meet process demand
5. In what way does each failure matter? Consequences
Production impacted, line must be taken down to repair, 1 hr of downtime
6. What can be done to predict or prevent each failure? Task
Monitor flow with SAP MII, alert when flow is impacted.
7. What can be done if the failure cannot be predicted or prevented? Redesign
Build valve and piping to redirect flow ahead of filter
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 27
- 28. Método de Desarrollo de una Estrategia de
Mantenimiento
Functional
Analysis
Criticality
Assessment
Criticality
High Medium Low
Reliability Failure Modes
Structured
Centered and Effects
Review
Maintenance Analysis
Maintenance Evaluate Strategy
Strategy and Optimize
Implement Strategy in SAP Collect Work
History
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 28
- 29. Resultados Típicos del Proceso RCM
1. Tareas de mantenimiento
preventivo
2. Tareas de supervisión e
inspección
3. Otras recomendaciones como:
Procedimientos operativos
Optimización de recambios y
herramientas
Formación
Rediseños
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 29
- 30. “Buena Gestión pero sin Progresos”
Sin progresos en fiabilidad y coste a pesar de procesos eficientes
Pb.: GMAO permite una Operaciones con SAP EAM/PM/PS
gestión eficiente de la Pb.: ¿Cuál es mi mejor
ejecución de tareas de estrategia de
mantenimiento, pero Hay un continuo ir y venir de mantenimiento?
falta eficacia. No se actividad de mantenimiento, Una pobre fiabilidad de
sabe si se está haciendo pero sin progreso real. los equipos lleva a
el trabajo adecuado en paradas no planificadas
el momento justo y en el y menor disponibilidad.
activo adecuado.
¿Qué reporta el gasto en Resp.
mantenimiento? La Fabricación
producción y la SAP
actividad no mejoran.
Pb.: Los costes de
mantenimiento
aumentan si la
estrategia utilizada no
Órdenes reduce las
indisponibilidades no
Responsable planificadas.
Mantenimiento
Pb.: ¿Qué activos representan
los mayores riesgos en cuanto
a seguridad, conformidad y
medioambiente? ¿Cuáles son
las mejores prácticas?
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 30
- 31. Las operaciones de Mantenimiento deberían seguir
Estrategias para mejorar la Eficacia del gasto
2. Estrategia:
1. Estrategia: Identificar Cómo deberían ser las operaciones Implementar las
y gestionar los sistemas estrategias correctas y
y activos críticos a monitorizar de cerca los
través de un gestión a la activos para minimizar
vez eficiente y eficaz En un mundo perfecto... las paradas no
planificadas,
incrementar la
producción y controlar
los costes de
mantenimiento
Resp.
Fabricación
Si pudiéramos….. SAP
3. Estrategia: Actualización
continua de las estrategias
de mantenimiento para
minimizar las paradas no
Órdenes planificadas, incrementar la
producción, controlar
Responsible costes, mitigar riesgos, … y
Mantenimiento medir los resultados
4. Estrategia: Definir e implementar
estrategias basadas en mejores
prácticas en toda la cartera de activos
empresariales
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 31
- 32. RCMO by Meridium Facilita la Mejora de la Eficacia del
Gasto de Mantenimiento a través de Estrategias
2. Solución: RCMO crea
1. Resultado: RCMO Operaciones con SAP y RCMO las estrategias
Identifica los sistemas y
correctas e identifica
activos críticos y
cómo monitorizar de
gestiona sus riesgos
cerca los activos para
permitiendo a la vez
¡Esto ya me gusta minimizar las paradas
eficiencia y eficacia en
más! no planificadas,
la gestión de activos
incrementar la
producción y controlar
los costes.
¡La producción está Resp.
Fabricación
mejorando de forma SAP
espectacular!
3. Solución: RCMO
analiza de forma
RCMO continua las
estrategias y evalúa
los métodos para
Órdenes reducir las paradas,
mitigar los riesgos
Responsible de producción,
Mantenimiento seguridad y
mediambiente,… y
medir los resultados,
4. Solución: RCMO crea y documenta mejores incluidos los costes.
prácticas para su implementación en toda la
cartera de activos empresariales
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 32
- 33. ¿Por qué utilizar RCM con SAP EAM?
El enfoque de SAP EAM es en la ejecución eficiente de:
Planificación y Programación de Mantenimiento
Trabajo de Mantenimiento
Gestión de Repuestos
Historial de Mantenimiento y Reportes
RCM se enfoca en la eficacia, y contesta la pregunta…
¿Cómo sabe si está
haciendo el mantenimiento correcto?
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 33
- 34. Ejecución Eficiente + Estrategia =
Optimización
SAP EAM + RCMO de Meridium
Instalaciones/
El mejor resultado activos con
el mejor rendimiento
Buen mantenimiento
mal ejecutado
Buen mantenimiento
bien ejecutado
Mejores Estrategias
de Mantenimiento
Mal mantenimiento
Mal mantenimiento bien ejecutado
mal ejecutado
Mejores Planificación y
Planificació
Ejecución del Mantenimiento
Ejecució
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 34
- 35. Cómo RCMO by Meridium con SAP EAM permite
una Gestión de Activos Eficiente y Eficaz
¿Somos eficaces? ¿Somos eficientes?
Evaluar Riesgo Actualizar Tareas
Óptimas de
Mantenimiento Implementación
Existing Identificación Planificación/
y Monitorización de la Estrategia
Strategy de los Trabajos Programación
RCM FMEA
Aplicar
Metodología Apropiada
Identificar Activos Evaluación Reporting/Análisis Finalización/ Ejecución
Críticos y Modos Rendimiento de la Eficiencia Histórico
de Fallo de la Estrategia
del Proceso de Trabajos
SAP EAM
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 35
- 37. Implementing Asset Management Programs
in iterations from core to advanced...*)
s es
es
oc
Operational
Pr
Program sophistication and
s&
Risk Mgt
on
innovation needs accurate
cti
un
STRATEGIC
and meaningful core data!
F
ENTERPRISE MGT
ed
Iterations and
nc
re-evaluations
Advanced Maintenance
va
of programs
Ad
RISK-BASED RCM
MAINTENANCE FMEA RBI
Asset Knowledge Management
s ENTERPRISE LEARNING COLLABORATION
e
ss
ENTERPRISE KNOWLEDGE MGT TASK MANAGEMENT
ce
o
Field Service Management
Pr
&
ns
SCHEDULING & RESOURCE MOBILE
tio
nc
OPTIMIZATION ASSET MGT
Fu
Operations Integration
t
m en
ge
a
GIS SCADA OMS DMS EMS PLANT MGT
an
Sensors
M
et
Enterprise Management & Support
ss
eA
r is
FINANCIALS HUMAN CAPITAL PROJECT & REAL ESTATE INDIRECT
tep
MANAGEMENT PORTFOLIO MGT MGT PROCUREMENT
En
Core Asset Management
re
MAINTENANCE & INVENTORY QUALITY EH&S
Co
*) Source:SAP IBU Utilities
Dr. Walter Kienle OPERATIONS MGT MGT
ANALYTICS
ENGINEERING & PROCUREMENT SPARE WORKFORCE METER & CONNECTIONS
CONSTRUCTION PARTS & SERVICES MGT DEVICE MGT MGT DECOMMISSIONING
Platform
Asset Management Data and Process Platform
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 37
- 38. Tecnología
100% SAP Technology
Developed with Web Dynpro using J2EE and ABAP
Common logon and security model
Runs natively on SAP Web Application Server
Broad platform & DB support
Inherent support for localization
Infrastructure Requirements (RCMO 1.3 and 2.0)
SAP ECC version 5.0 or 6.0
SAP Web Application Server version 7.0
SAP Business Intelligence version 3.5 or 7.0 (optional, recommended)
SAP Portals version 7.0 (optional)
Windows OS
Oracle Database, SQL Server Database, MAXDB
Hardware Requirements
No additional requirements beyond Netweaver ’04 recommendations
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 38
- 39. ¿Por qué integrar RCMO con SAP EAM?
Después de una revisión con clientes de SAP, éstos indicaron que los tres principales
retos en el proceso de RCM son:
1. Las herramientas RCM están desconectadas
El proceso de carga de las recomendaciones en SAP es manual
Una vez cargadas las recomendaciones, el análisis RCM original se pierde
2. Medir el resultado RCM resulta un proceso largo y difícil
3. Mantener los procesos RCM activos es prácticamente imposible
Many RCM assessments fall short today because the
recommendations for making improvements are not translated
into action-oriented tasks within the production system.
Next Generation Enterprise Asset Management
Patrick Connaughton, Forrester Research
April 24, 2006
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 39
- 40. RCMO – Funcionalidad Clave
1. Proceso estructurado para desarrollar estrategias de
mantenimiento
Reliability Centered Maintenance (RCM)
Failure Modes Effects and Criticality Analysis (FMEA/FMECA)
2. Integración con los proceso de trabajo de SAP PM
Utiliza los datos maestros de SAP
Planificación y ejecución de Mantenimiento
Análisis de la efectividad del Mantenimiento
3. Permite la reevaluación automática de las estrategias
de Mantenimiento para la mejora continua.
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 40
- 41. Visión General de la Solución RCMO
Analyze/Identify
1
1 Critical Assets
Define
Continually 6
6 2
Re-evaluate
2 Systems/Assets
to Analyze
Strategies
Closed Loop Reliability
Centered Maintenance
Implement 5
5
Strategies Conduct
(Maintenance, 3
3 RCM/FMEA
Monitoring and Analysis
Inspection) 4
4
Develop
Recommendations
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 41
- 42. Flujo del Proceso RCMO / SAP
SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 46. SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 59. SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 65. Estructura Jerárquica de un Análisis
Analysis
Function
RCM
Function Failure
Failure Mode
Failure Effect
FMEA
FMECA
Recommendation / Task
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 65
- 71. SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 73. Criticality matrix
For each system, each failure mode and each recommendation
a Risk Ranking / Criticality can be defined with risk matrix:
Consequence
Low High
Low
1 2 3 4 5
Probability
2 3 4 5 6 For example:
3 4 5 6 7 Weight: 10
4 5 6 7 8
-> Risk ranking = 10*7 = 70
High
5 6 7 8 9
Your risk matrix can be customized (with n lines / m columns, values) and
you define the areas with different weights:
Consequence Consequence Consequence Consequence
Low High Low High Low High Low High
Low
1 2 3 4 5
Low
Low
Low
1 2 3 4 5 1 2 3 4 5 1 2 3 4 5
Probability
Probability
Probability
Probability
2 3 4 5 6 2 3 4 5 6 2 3 4 5 6 2 3 4 5 6
3 4 5 6 7 3 4 5 6 7 3 4 5 6 7 3 4 5 6 7
4 5 6 7 8 4 5 6 7 8 4 5 6 7 8 4 5 6 7 8
High
High
High
High
5 6 7 8 9 5 6 7 8 9 5 6 7 8 9 5 6 7 8 9
safety environment production image Risk ranking
weight: 10 weight: 5 weight: 10 weight: 1
Risk ranking: 30 + 25 + 40 + 6 = 101
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 73
- 74. Example of a Risk Matrix
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 74
- 82. SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 107. SAP EAM BW
Maintenance
Equipment Maintenance Maintenance
Execution &
Master Data Planning Analysis
Documentation
RCMO FMEA
Optimize
Strategies
System Strategy Strategy
Risk Evaluation
Definition Definition Evaluation
Establish
Evaluation
RCM Criteria
Condition Monitoring Operator
(Future Integration)
Rounds Operational
Performance
Condition Evaluation
Monitoring
- 113. RCMO™ 2.0 Enhancements (01/2009)
Upfront System Definition and System Criticality Analysis
Integration to SAP Document Management System (DMS)
Decision Logic Builder
Revision History
Automatic Node Numbering
Mitigated Risk Ranking for Recommendations
Many Enhancements for Reports,
Search capabilities, Importing analyses and numerous others
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 113
- 114. ¡Muchas Gracias!
César Bonnín
Experto en Soluciones
SAP Iberia
E-mail: cesar.bonnin@sap.com
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 114
- 115. Copyright 2009 SAP AG
All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.
© SAP/Meridium 2009 / SAPIberia, Abril 2009 Page 115