Enterprise Asset Management (eAM) provides an integrated solution for managing, scheduling, and accounting for maintenance of equipment and machinery. It allows organizations to track maintenance costs more efficiently than via spreadsheets. eAM manages assets with a hierarchy and relationships between parent and child assets. It also handles work orders, activities, and interactions between maintenance, procurement, and accounting functions. Successful implementation requires alignment with business needs, testing, training tailored to roles, and ensuring key setup elements like the asset structure and maintenance schedules meet requirements.

1. Enterprise Asset Management
A Quick Tour for Beginners
Donna Christie &
Jeannie Dobney
August 2010

2. • What is Oracle Enterprise Asset Management
(eAM)? / What functionality can it provide us?
• eAM system architecture and interaction with
other Oracle Applications.
• How will the end-users' experience eAM?
• Tips and traps for implementing and using
eAM

3. • eAM provides an integrated solution for
managing, scheduling and accounting for the
maintenance of machinery and equipment.
• Examples of ‘assets’ are: cranes, heating and
ventilation equipment, trucks, buildings etc.
• Without an integrated solution (such as eAM),
organisations may track the cost of
maintenance via spreadsheets and incur
unnecessary inefficiencies and expense.

5. • 2 types of asset:
- Capital e.g. a truck
- Rotable / Rebuildable e.g. a motor that can be swapped out and
rebuilt
• Asset Route - a "virtual asset" that enables multiple assets to
be associated to a single work order
• Maintenance Route - a set of operations necessary to perform
an Activity.
• Asset hierarchy – parent / child relationships between assets
• Asset BOM – a list of the asset’s components
(BOM = Bill of materials)
• Maintenance BOM - lists all items needed to perform an activity

6. • An Operation – The task required to complete the work. Can be
single or multiple
• Asset Activity – A default work template which is then
associated with an asset
• Work Order Status – the status of the work order determines the
actions which can be applied
• Uncomplete – Completed work orders can be uncompleted!
• Meter – measurement device determining m maintenance
requirement e.g. odometer.

9. • eAM Item Open Interface • EAM Meters API
• eAM Asset Number Open Interface • EAM Meter Association API
• eAM Asset Genealogy Open Interface • Meter Reading API
• eAM Meter Reading Open Interface • EAM PM Schedules API
• Asset Number API • Activity Creation API
• Asset Attribute Values API • EAM Activity Association API
• Asset Attribute Groups API • EAM Activity Suppression API
• Asset Routes API • EAM Set Name API
• Asset Areas API • Maintenance Object Instantiation API
• Department Approvers API • Work Order Business Object API
• EAM Parameters API • Work Request API

10. Overview:
 Define Person
 Optionally define competencies
 Define system item (determines interaction
with Payables and Receivables)
 Define Resource, referencing system item and
competencies if required
 Create instances of the resource i.e. person
records linked to the resource
…..See following slides

14. • Oracle assume the use of certain roles and
have designed the interface and their
manuals around this:
• Self Service - work requests, work orders
(non-maintenance and Tradesman)
• Maintenance User (Planner) / Super User
i.e. Maintenance User Workbench
• Scheduler i.e. Scheduler Workbench

15.  Tradesman- Time entry against WO
 Tradesman – Update WO for Materials
 Tradesman – Maintain WOs – Create, Update
 Lead/Supervisor - Maintain WOs – Create,
Update, Complete WOs, Create new Asset
Activities, Report on WOs.
 Scheduler/Planner – Maintain planned
maintenance schedule. Monitor breakin WOs.
 eAM Super User – Maintain Asset hierarchy,
Asset Meters, Asset activities & other setup

27.  Automate work request or work order
generation based on defined criteria.
 Example: a pump has a quality plan where a
WR will automatically be generated based on
a temperature above 50 degrees. An
inspection is carried out at end of shift and
the temp entered in Oracle against the Asset.
If above 50 degrees a WR is raised. The user
who created the plan receives notification.

30.  Do not overtrain.
 Teach them what they need to do their job.
 Create training courses which are ‘building
blocks’. Eg Scheduler needs to attend all.
 Users attend blocks according to their role
needs.
 Training has relevance to their role.

31. • Design and test with all stakeholders e.g.
stores, procurement and accounting
• Align eAm access and tasks to jobs
• eAM has been ‘added’ on using existing Oracle
components e.g. Asset Groups are a type of
Inventory System Item, this may seem a bit
clumsy initially…
• Do you need some co-ordination with
Accounting’s Fixed Asset definitions, if so,
how?

32.  Ensure you get the asset structure correct at
the start
 Make sure Schedulers are able to view the
planned schedule according to business
requirements
 Get the shifts right and set time zones
 Create meaningful work order statuses
 Create Asset BOMs and Activities

33. • Contact us if you have further questions
or comments:
Donna Christie
dtcconsulting@live.com.au
Jeannie Dobney
jdobney@bigpond.com
• Updated slides can be found at jdobney.com