<Insert Picture Here>

Enterprise Asset Management

Eric Cook
Solution Architect APAC
The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.
 AGENDA

• EAM Overview
• R12 Features
• Integration to EBS
• Critical Requirements for Success
• Q&A
EAM Overview
Oracle’s Asset Maintenance Solution
• Replace Standalone Maintenance Systems
•Single Global Instance
•Out of the Box Integration

• Drive Maintenance Best Practices

•Multiple Maintenance Strategies
•Work Order Planning and Relationships
•Spares Management
•Predictive Analysis

• Manage the Full Asset Lifecycle

•Project Planning and Execution
•Asset Disposal Management

• Support Compliance and Corporate Governance

•Common Data Model
•Flexible Financial Accounting and Control
•Integrated Intelligence
 Fixed Plant

Buildings &
IT
Grounds

Oracle Supports
All Asset Types

Linear/Network Mobile/Fleet

6
 Multiple Maintenance Strategies
Condition
Based

Condition System Identification Workflow-Driven

Monitoring of Limit Violations System Action

Planned
Usage
Maintenance
Preventive

Schedules
Actual
Usage
Maintenance
Forecast
Estimated
Life
Reactive

Maintenance Unplanned Maint Operator Initiated

Request Scheduling WO Req / Approval

7
 Flexible Financial Rollup

Track material, labor and

contract services costs Enterprise

Business
Asset Unit

Capital
or Automatically post
Dept Expense maintenance charges directly
Project to the General Ledger
Parent

Child Work Order

Work Order Analyze Financial Details at Appropriate Level

8
Enterprise Asset Management
CHALLENGES CAPABILITIES
• Assets kept in operation
longer
• Tracking asset
information when repairs
performed by third party
• Increased regulatory
requirements
• Breakdowns reduce
valuable production time
• Reactive maintenance
accounts for majority of
repair work
• Equipment knowledge
lost with employee
turnover
• Maintenance system not
fully integrated with ERP
system
VALUE
• Intuitive, easy to use
system
• Trigger actions from
meter readings
• Contractors can report
activity via web portal
• Mobile device capability
included with eAM
• Attach documents to
assets, work orders, PM’s
• Collect additional
information on assets via
quality control plans
• Failure analysis tools to
help move toward
predictive maintenance
• 126 integration points to
Oracle eBiz Applications
• Reduce training time
needed for users
• Increase equipment
availability and efficiency
• All maintenance activity
available in one place for
analysis
• Manage Regulatory
Compliance
• Decrease search time
and increase wrench time
• Extend life of equipment
• Purchase costs and
inventory items
automatically rolled up to
work order and asset
• Shared visibility of
equipment status
throughout company
 Representative eAM Customers - ANZ

10
R12 Features
 Evolution of Oracle Enterprise Asset Management
New in R12…
• Global consolidated asset
repository
• Enh. fixed asset integration
• Work order cost capitalization
• Maintenance budget forecast
• Multiple activity PM schedules
• Asset check in / check out with
safety and operational data
• Asset operational log
• Work order approval workflow
• User defined work order
status codes
• Warranty support
• Automated material availability
status check
• Mobile maintenance user
workbench
• Single page work order
• Failure Analysis
(projects in bold back-ported to 11i10)
12
New in R12.1 New in R12.1.2
• Asset Move Workbench
• User Interface Enhancements
• Express Work Order • Primavera Integration
• Item Cross Reference Search
capability available from EAM
• Specify source supply sub-
inventory for EAM work orders New in R12.1.3
• Microsoft Projects Integration
for Work Order scheduling • Work Permits
• Graphical map of asset • Encumbrance Accounting
network relationship • ESRI Integration
• Change department on work
order operation for crew
scheduling
• Google Maps Integration Planned in 12.2
• Construction Workbench
• Enhance Asset and Work •Safety – Clearances
Order Search
•Safety – Lock out/ tag out
Integration to EBS
 126 Integration Points from eAM to EBS

14
Critical Requirements for Success
Key EAM Implementation Considerations
• Asset Hierarchy
• Asset Group Definition
• Assets
• Asset Attributes
• Asset BOM
• Asset Categories
• Failure Sets
• PM schedules
• Rotable Definition
• Organization Structure
• Global Considerations
• Data Conversion
Additional Considerations for Success

• Taxonomy Document

• Start data conversion process early

• Data cleansing effort generally underestimated

• End to end system integration testing critical

QUESTIONS
ANSWERS
Thank You