Professional Documents
Culture Documents
Tony Ciliberti, PE
Principal Engineer, Reliability Dynamics LLC tony.ciliberti@rd-eam.com
Failure
ISO 14224: Collection and exchange of reliability and maintenance data for equipment Reliability-Centered Maintenance (RCM)
Standard
Customers and primary suppliers can use the same process, in essence a common reliability language between them
Failure
reports double as warranty claim forms, if warranty applies Warranty details explicitly given on both equipment records and failure reports Return Material Authorization (RMA) master records
One or more devices assigned to an RMA RMA data visible on equipment master records Complete lifecycle warranty tracking with rigor that eliminates claim duplicity
Each
provision has a counter and duration based on counter units Provisions have a link operator (and/or specification) that can be used to specify when a subset of conditions pertain to the overall warranty validity
result
Warranty master level: all provisions of the warranty are valid based on the link operator (and/or specification) Provision level: the individual provision is valid
Negative
result
Warranty master level: one or more provisions of the warranty are invalid with an and link operator Provision level: the individual provision is invalid
equipment a unique identity in the field (PM) and the warehouse (MM)
EQ# = MM# + Serial# Gives complete lifecycle tracking of equipment Facilitates goods transfers of equipment
status controls/restricts business processes not allowed while the equipment is out of service Once received back from the vendor, the status is reset to the appropriate setting
Failure reporting process based on ISO 14224 and Reliability-Centered Maintenance (RCM) methodologies The notification doubles as a failure reporting mechanism and warranty claim form
Warranty
ISO 14224:2006 Petroleum, petrochemical and natural gas industries -- Collection and exchange of reliability and maintenance data for equipment
10
Usage:
Administer
11
reporting parties can input their findings, including the vendor One or more entries possible per reporting party
12
failure mechanism
party
Codes 100% consistent with vendor reliability coding process (common reliability language)
Customer
Level 2 coding can be maintained in SAP front-end via characteristic maintenance (CT04)
Reliability Dynamics LLC 2010
13
Actions taken by customer and vendor Used to document what was done to address:
The
14
Change
effectivity gives complete lifecycle tracking of all changes and updates to RMA records including equipment assignments and removals Materials serialization allows complete integration with material management processes
Tracking via goods movements Quality management processes Unique specification on SD orders
15
Only
Equipment P101 may be assigned to RMA record 001 from time A to time B, and then to RMA record 002 from time C to time D Complete records for both RMA records and assignments to those RMA records are maintained by the system
Ensures
no duplicate submittals to
vendor
16
17
The PM repair order is the mechanism used to confirm proper vendor credit
All
Failed components (if required by vendor) Replacement parts from vendor returned to inventory with credit to respective orders
Credits
be appoximately zero for warranty repairs (depending on terms) Should reflect core credits when using Caterpillars remanufactured parts Reman Program (or equivalent program by other vendors)
18