Integrating Oracle EBS R12 and Maximo EAM Using the Maximo ... Oracle EBS R12 … · Integrating Oracle EBS R12 and Maximo EAM using the Maximo Enterprise Adapter 11 Solution Data

1Integrating Oracle EBS R12 and Maximo EAM using the Maximo Enterprise Adapter

Integrating Oracle EBS R12 and Maximo EAM Using the Maximo

Enterprise Adapter

Michigan Oracle Users Summit (MOUS) November 8th, 2017

Integrating Oracle EBS R12 and Maximo EAM using the Maximo Enterprise AdapterCopyright © 2017 Deloitte Development LLC. All rights reserved. 2

Agenda

Presenter 3

Deloitte Overview 5

Solution Overview 7

Detailed Technical Solution 12

Impact of Solution 15

Q&A 16


Presenter


Presenter

Deloitte Consulting LLPMr. Dean is a Senior Manager at Deloitte Consulting LLP. He joined Deloitte in March 2008, and has over 22 years of experience managing Oracle EBS business transformation projects in the Commercial, Higher Education, and Federal sectors. He has Project Management Professional (PMP) and Information Technology Infrastructure Library (ITIL) certifications. He brings a pragmatic approach to Techno-Functional problem solving and delivering enterprise solutions.

Rohit Dean


Deloitte Overview


Federal agencies value Deloitte for our people and the insights and experience we bring to help tackle their challenges.

“Buyers rate Deloitte highly for integrating its project team with the customer's team, meeting the project timeline, and resolving problems/issues related to customer service.”

- IDC MarketScape: Worldwide Oracle Implementation Services 2016 Vendor Assessment

Broad

capabilitiesIndustry

practices

Resources Federal

experience

Offering a broad range of Oracle

capabilities that span diverse disciplines

• Cloud Technologies

• Oracle E-Business Suite

(EBS)

• PeopleSoft

• Customer Relationship

Management (CRM)

• Identity Management

• Engineered Solutions

• Service Oriented Architecture

(SOA)

• Data Warehousing

• Business Reporting and

Analytics

• Master Data Management

• Technical Infrastructure and

Development

• Application Management

Services

• Business Process

Transformation

• Upgrades and

Implementations


Solution Overview


Situational Background

Challenge

The two applications were not integrated, which caused duplicative parts maintenance and transactional data entry, thereby causing data integrity issues across the two disconnected applications.

Solution

Implemented the Maximo Enterprise Adapter (MEA) for Oracle Applications to integrate the two applications.

Developed and deployed additional custom extensions based on client requirements using the MEA for Oracle architecture.

Impact

Eliminated duplicative data entry and parts maintenance, improved data quality, reduced manual processes, and brought back focus of the Electro-mechanical engineers (EM) on machine maintenance rather than data maintenance.

Spare parts are used in manufacturing environments to repair machinery and enable optimum sustainable capacity while producing at the desired level of quality. The client uses Maximo Enterprise Asset Manager (EAM) to document work orders for planned and unplanned maintenance. Oracle E-Business Suite (EBS) is the system of record for inventory and financial transactions.


Business and Technology Landscape

Oracle Identity Manager

The below components describe the Spare Parts Inventory and Work Order management process before the implementation of MEA for Oracle.

Work Orders

• Work Orders are requested for fixing machinery

• Most work orders do not account for Spare Parts

Spare Parts

• Spare Parts used to fix machines (break-fix) and ensure they are running properly (preventive maintenance)

• Spare Parts were tracked in both Maximo and EBS

Maximo

• Maximo tracks work order requests and progress, including tasks that require Spare Parts from Inventory

Oracle EBS

• EBS tracks inventory replenishment, including spare parts consumed through work orders

Lack of integration between Oracle EBS and Maximo caused inaccurate reporting of on-hand quantities, and affected inventory replenishment causing frequent stock-outs


People and Process ChallengePrior to the MEA implementation, there were several breakdowns in the business process for Spare Parts lifecycle management and Work Order management.

Staffing

• Office of Acquisition’s current workforce size could not meet the volume of incoming Min/Max requisitions required

• No dedicated supply chain management team

• EM would add labor to Maximo Work Orders but did not add the associated Spare Parts.

EM Creates Maximo

Work Order

• EM had no real time

visibility into available

inventory in the

storeroom.

• EMs would issue every

part out of the storeroom

and “store” the extra

items that are not

required.

EM Obtains Required

Spare Parts

• Costs of Spare Parts were

not properly allocated to

the correct cost centers.

EM Completes Repair

• Min/Max requisitions were

not being processed

resulting in stock outages.

• Incorrect Min/Max

requirements caused

erroneous requisitions to be

generated.

• Lead times were not

configured for critical Spare

Parts which resulted in

machine downtime.

• Purchases were made with

P-Cards and were not

visible in Oracle EBS and

Maximo.

Spare Parts are

Replenished through

Acquisitions

Issu

es


Solution Data and Process ConfigurationThe below data configuration and process flow was implemented as part of the MEA solution. This enabled seamless integration, consistent and accurate data across both applications, and automated requisitions.

Oracle EBS Maximo

Item definition and inventory replenishment

Send live Inventory quantity updates to Maximo

Source of item consumption via work orders

Send Inventory data from work orders to Oracle EBS

Two-way Integration

Source of

Replenishment

Source of

Consumption

EBS sends live Inventory data

to Maximo

Work Order reserves spare

parts

Maximo sends costing and

decremented inventory data

to EBS

EBS Min/Max replenishment

program automatically

triggers item requisition

Process Solution


Detailed Technical Solution


Technical Solution

Oracle EBS Maximo EAM

• MEA consists of a 2-way interface between Maximo EAM and Oracle EBS

• It exchanges data by using enterprise services and publish channels

• The adapter updates the systems when you change data on either side of the integration, depending on how you configure and customize the integration points

• The adapter uses an extensible framework of interface tables, Cron jobs, triggers, and user exits for implementing the integration

Maximo Enterprise Adapter (MEA) for Oracle

Enterprise Services

Publish Channels


Integration Setups

Maximo

EBS

Object

Structures

End Points

External

System

Publish

Channels

Enterprise

Services

Integration

ControlsCron Job Setup

Table/Column

Sizing

Schema

Tables

Triggers

User Exits

Control Table

Interface

Tables

• Chart of Accounts

• Employee Jobs

• GL Components

• Inventory Balances

• Inventory

• Inventory Issue

• Invoices

• Items

• Employees

• Purchase Contracts

• Purchase Orders

• Projects

• Purchase

Requisitions

• Receiving Rotating

Items

• Receipts

• Vendors

• Chart of Accounts

• Employee Jobs

• GL Components

• Inventory Balances

• Inventory

• Inventory Issue

• Invoices

• Items

• Employees

• Purchase Contracts

• Purchase Orders

• Projects

• Purchase

Requisitions

• Receiving Rotating

Items

• Receipts

• Vendors

• GL Journals

• Inventory

• Invoices

• Inventory

Reservations

• Items

• Purchase

Contracts

• Purchase Orders

• Project Actuals

• Purchase

Requisitions

• Receipts


Impact of Solution


Impact of SolutionAfter implementing MEA and using the framework to deploy extensions to it, the client eliminated duplicative data entry and parts maintenance, improved data quality, reduced manual processes, and brought back focus of the Electro-mechanical engineers on machine maintenance rather than data maintenance.

Provided an extensible framework for integration between EBS and EAM

Eliminated duplicate data entry which would often result in inventory variance reported between the two applications

Provided a window from EAM into EBS whereby EAM can directly check for availability of parts before scheduling maintenance

Reduced manual processes to keep the information in the two applications in synch e.g., work order (actuals) were converted to move order issue transactions

Q&A

18

As used in this document, "Deloitte" means Deloitte Consulting LLP, a subsidiary of Deloitte LLP. Please see www.deloitte.com/us/about for a detailed description of the legal structure of

Deloitte LLP and its subsidiaries. Certain services may not be available to attest clients under the rules and regulations of public accounting.

This communication contains general information only, and none of Deloitte Touche Tohmatsu Limited, its member firms, or their related entities (collectively, the “Deloitte Network”) is, by

means of this communication, rendering professional advice or services. Before making any decision or taking any action that may affect your finances or your business, you should consult

a qualified professional adviser. No entity in the Deloitte Network shall be responsible for any loss whatsoever sustained by any person who relies on this communication.

Documents

Integrating Oracle EBS R12 and Maximo EAM Using the Maximo ... Oracle EBS R12 … · Integrating Oracle EBS R12 and Maximo EAM using the Maximo Enterprise Adapter 11 Solution Data