Scribd
Upload
465 views4 pages

Oracle EAM Failure Analysis

The document discusses failure analysis functionality in Oracle eAM R12. It describes how failure codes, cause codes, and resolution codes can be created and linked in failure sets. These sets can then be associated to asset groups to help analyze common failures, causes, and resolutions for maintenance planning and budgeting.

Uploaded by

Dock N Den
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
465 views4 pages

Oracle EAM Failure Analysis

The document discusses failure analysis functionality in Oracle eAM R12. It describes how failure codes, cause codes, and resolution codes can be created and linked in failure sets. These sets can then be associated to asset groups to help analyze common failures, causes, and resolutions for maintenance planning and budgeting.

Uploaded by

Dock N Den
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Oracle eAM-Failure Analysis in R12

1
2
3
4
5
(2 votes, average 5.00 out of 5
!ritten "y Rut# $urly % 2& 'e(te)"er 2010
Oracle eAM-Failure Analysis in R12
Failure Analysis*
+#is is one of t#e ,ey i)(rove)ents as far as t#e 'elf 'ervice (age, Maintenance '- is concerne.. Failure analysis is a great tool
to analy/e t#e kind of failure, t#e root cause of such failure an. t#e resolution take. 0n t#e syste), got to t#e 1Failure +ac,ing
'etu(1 an. (erfor) t#e 2 activities*
Create new failure Codes, cause Codes and Resolution Codes
Create failure sets to link the above three codes together
Associate the failure sets to the Asset Groups
Failure--2ause--Resolution follo3 a one to )any relation. For e4a)(le, One failure co.e can #ave )any causes, an. eac# cause
can #ave )any resolutions.
+#is is very #el(ful for )aintenance )anagers to fin. out 3#at are t#e co))on ty(es of failures, t#e general causes "e#in.
failures, an. t#e resolution usually ta,en. +#is analysis 3ill #el( t#e )anager to .eci.e on*
Necessary precautions
Stock materials required for the most frequent resolutions
Plan more accurately for Preventive Maintenance
Prepare a more Accurate maintenance Budget for the forthcoming year
One fli( si.e of t#is analytical toll is t#at it is very .ata intensive. 'o)eti)es .uring t#e initial .ata u(loa. (rocess, it is e4tre)ely
.ifficult to (in (oint all t#e t#ree ty(es of co.es an. create failure sets. +#erefore t#e i.ea is not to get over"oar. 3it# t#e
functionality.
Data for Failure Analysis is typically uilt over a period of time. 5enerally organi/ations start off 3it# very li)ite. failure
analysis .ata an. as an. 3#en ne3 failures, causes an. resolutions are encountere. in real life, t#e .ata is accor.ingly entere..
+#is, 0 "elieve is t#e correct a((roac# to gain t#e )a4i)u) out of t#is functionality.
Oracle also allo3s you to )a,e t#e failure entry mandatory at t#e ti)e of creating !or, Or.ers. +#is #as to "e .one as t#e Asset
5rou( level. 6lease navigate to t#e Failure !racking Setup, associate t#e Asset grou( to t#e failure co.e an. select Failure
"ode #equired to 1$es1. Refer to t#e screen "elo3*
Once t#is is .one, t#e rest is easy. 7ust create a !or, Or.er to t#at Asset grou( an. 'elect t#e Failure %ntry #equired c#ec,-
"o4. !#en you try to co)(lete t#e !or, Or.er, t#e syste) 3ill (ro)(t you to enter t#e Failure, 2ause an. Resolution co.e as you
#ave set u( in t#e A((lication. Refer to t#e "elo3 screen-s#ot.
8o(e t#is .ocu)ent 3as useful to you.

You might also like