Enterprise Asset Management Eric Cook Solution Architect APAC

The following is intended to outline our general product direction 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 o

Oracle Supports All Asset Types Fixed Plant Buildings & Grounds IT Oracle Supports All Asset Types Let us begin by defining an asset. For this discussion, an ‘asset’ means any physical object that requires maintenance/service and/or tracking. Typically an asset has a capital value and depending on financial ownership it may be financially represented in Fixed Assets of a company’s book. However from a maintenance & service perspective, an asset is an object of value that an organization needs to track, maintain and manage irrespective of financial ownership and value. Given this definition, assets can be broadly classified into fur types as represented in this asset quadrant. On the upper left are assets of type ‘Fixed Plant’ or ‘Static asset’s’. These are assets that may exist in any plant like manufacturing, refinery etc. Examples are machines, equipment, robotic arms. These assets are static because their location rarely changes. The lower left quadrant represents ‘mobile assets’. These are assets that frequently move across locations and an organization usually may have more than one instance of such similar assets. Examples include fleet, vehicles, and spare parts that may be similar in configuration but are dispersed across different locations. Upper right quadrant represents linear assets that are physically continuous in nature and are tracked/maintained in segments. On the lower right are the infrastructure type assets such as buildings, street lights, university campuses etc. Linear/Network Mobile/Fleet

Multiple Maintenance Strategies Condition Based Condition Monitoring System Identification of Limit Violations Workflow-Driven System Action Planned Usage Maintenance Schedules Actual Usage Preventive Maintenance Forecast Estimated Life Maintenance Request Unplanned Maint Scheduling Operator Initiated WO Req / Approval Reactive

Flexible Financial Rollup Track material, labor and contract services costs Enterprise Business Unit Asset Capital or Expense Project Automatically post maintenance charges directly to the General Ledger Dept Parent Work Order Child Work Order Analyze Financial Details at Appropriate Level

Enterprise Asset Management CHALLENGES CAPABILITIES VALUE 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 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

R12 Features

Evolution of Oracle Enterprise Asset Management New in R12… New in R12.1 New in R12.1.2 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) Asset Move Workbench Express Work Order Item Cross Reference Search capability available from EAM Specify source supply sub-inventory for EAM work orders Microsoft Projects Integration for Work Order scheduling Graphical map of asset network relationship Change department on work order operation for crew scheduling Google Maps Integration Construction Workbench Enhance Asset and Work Order Search User Interface Enhancements Primavera Integration New in R12.1.3 Work Permits Encumbrance Accounting ESRI Integration Rapid development has been the norm at Oracle for many years – Here is an example of what was done for our ALM solution in the e-Business Suite for the last 2 releases. All our modules grew in depth and breadth during that time, to challenge the best applications available today. Planned in 12.2 Safety – Clearances Safety – Lock out/ tag out 6

Integration to EBS

126 Integration Points from eAM to EBS

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

Q & Q U E S T I O N S A N S W E R S A

Thank You