Oracle eAM Implementation Tips

The following tips highlight common questions and issues that arise during eAM implementation:

General Setup: An inventory org may be used for inventory, manufacturing, or maintenance. Spare parts are managed and maintenance work orders are executed in “eAM enabled” inventory orgs.

• Set up an org for eAM separate from any manufacturing orgs.

• Use Average Cost for inventory valuation in eAM orgs.

• When setting up WIP Accounting Classes, use the same maintenance expense account code in both the valuation and variance columns. This will cause maintenance expenses to book to the proper GL account and period.

Asset Definition: Assets are the object that work is performed on. Assets are also defined to represent hierarchical groupings for organizing work and rolling up costs. Asset can be used to represent positions for installation of rebuildable inventory items.

• Define a new Asset Group for each Manufacturer and Model Number combination.

• Define Templates for Asset Groups that will be repetitively used to create new Assets.

• Assign a Parent Asset for each new Asset to place it in the Asset Hierarchy.

• Consider setting up Assets that will move in and out of inventory as Rebuildables. Creating a “position asset” in the asset hierarchy will allow the tracking of rebuildables that have been installed and the cost of maintenance for the position.

• Use the Rebuildable Serial Number form to quickly setup rebuildables.

Preventive Maintenance and Activity Definition: Activities are the method for predefining work. Activities are used as templates to create work orders. Preventive maintenance activities may be scheduled based on meter readings and dates. Condition based maintenance may be triggered by absolute meters or collection plans.

• When launching the Activity Workbench and Maintenance Workbench enter a Parent Asset ID and check the “include children” box. Open Results, All Assets to view and use the hierarchy.

• Standard Operations may be useful for creating Activity Routings.

• When defining meters, be sure to check “used in scheduling.”

• When defining meters, set “past readings” to a number greater than

API To Create And Update An ESTIMATE in Oracle EAM

Following API procedure help us to create and update an ESTIMATE.

Here are the details of the specifications  for the create and update procedures:-
PACKAGE EAM_CONSTRUCTION_EST_PUB
File name: EAMPCESS.pls/EAMPCESB.pls

/*
* These procedures are used to create and update construction estimate records
* p_api_version Version of the API
* p_commit Flag to indicate whether API should commit changes
* p_init_msg_list Flag to indicate initialization of message list
* p_validation_level Validation Level of the API
* px_estimate_rec Record for estimation details of type EAM_EST_DATASTRUCTURES_PUB.EAM_CONSTRUCTION_ESTIMATE_REC
* x_return_status Return status of the procedure call
* x_msg_count Count of the return messages that API returns
* x_msg_data The collection of the messages
*/

PROCEDURE CREATE_ESTIMATE(
p_api_version IN NUMBER,
p_commit IN VARCHAR2,
p_init_msg_list IN VARCHAR2,
p_validation_level IN NUMBER,
px_estimate_rec IN OUT NOCOPY EAM_EST_DATASTRUCTURES_PUB.EAM_CONSTRUCTION_ESTIMATE_REC,
x_return_status OUT NOCOPY VARCHAR2,
x_msg_count OUT NOCOPY NUMBER,
x_msg_data OUT NOCOPY VARCHAR2
);

PROCEDURE UPDATE_ESTIMATE(
p_api_version IN NUMBER,
p_commit IN VARCHAR2,

Aims, Objects and Benefits of Oracle Enterprise Asset Management (EAM)

1.An asset is an entity for which users can report problems. Assets can be cooling towers, cranes, buses, buildings, conveyors, or anything that needs work

2. eAM creates and implements maintenance procedures for both assets and rebuildable Inventory items and takes care of comprehensive and routine maintenance requirements of asset intensive organizations. It effectively maintains assets such as vehicles, cranes and HVAC systems and rotable Inventory items such as motors and engines.

3. eAM enables users to optimally plan and schedule maintenance operations /activities with minimal disruptions to an organization’s operations and productions. It measures performance and optimizes maintenance operations. It tracks the performance of the assets and rebuildable inventory items by using meters, quality plans and conditioning systems.

4. By effectively monitoring operational data such as maintenance history, performance trends, meter readings, and operating conditions, organizations can proactively manage available resources such as inventory, equipment and skilled personnel to match them to asset maintenance demand.

5. Optimization of asset utilizations, scheduling and resources improves resource efficiency and enhances maintenance quality, maximizes resource availability including equipment and labor. Maintenance costs and work history are tracked at asset level.

6. Oracle eAM enables organizations to create and implement optimal and effective asset management strategies that can increase revenue and decrease costs. Both Preventive and Predictive Maintenance strategies are

Oracle's Business Intelligence Foundation Suite (Analytics Applications) are designed for the manufacturing sector and Enterprise asset management (EAM)

Oracle has announced two new analytic applications at Oracle OpenWorld Tokyo.

The new applications, which are both based on Oracle's Business Intelligence Foundation Suite, are designed for the manufacturing sector, and for enterprise asset management (EAM), and are the first in-memory analytic applications for that sector.

Oracle Manufacturing Analytics is intended to help operations managers, manufacturing analysts, manufacturing and supply chain executives and production cost accountants to have a better view into manufacturing processes, inventory and product quality, to enable them to reduce production costs, improve product quality, minimize inventory levels and respond faster to customer demands.

Oracle Enterprise Asset Management Analytics has been designed to give more effective management and analysis of assets, in areas such as projecting expected asset life, planning strategies to reduce maintenance costs and increase uptime

Failure Analysis in Oracle eAM

Failure Analysis enables maintenance users to track an asset failure from the time it is reported until its resolution. Statistics from their collected failure data provide them with information on why an event occurs and causes asset failure. They can then take the necessary steps to eliminate that event. Additionally, they can use the failure statistics, among others, to help them formulate their Reliability-Centered Maintenance (RCM) program. 

Failure hierarchies that support multiple-level failure reporting provide effective root cause and reliability analysis. For specific Asset Groups, each failure (problem) has a defined number of root causes, with each root cause having a defined number of resolutions (remedies). 

1. First step is to define Failure Codes. There are three main Failure Code Types:

1. Failure Code
2. Cause Code and
3. Resolution Code

2. Second step is to define Failure sets. In failure sets user-defined Failure codes, Cause codes and