MOC and Oracle Enterprise Asset Management (eAM) Integration
This chapter covers the following topics:
Overview
Oracle Manufacturing Operations Center (MOC) and Oracle Enterprise Asset Management (eAM) integration provides effective coordination between production and maintenance departments to achieve greater utilization of equipment on the shop floor. This is achieved by the rapid exchange of information related to equipment. Examples include down or idle condition of equipment, or equipment exceeding control parameters. MOC initiates actions based on events and alerts captured from shop floor equipment and passes the actions to the specific roles, such as the Maintenance Supervisor. MOC also receives the expected and actual uptime from the maintenance department that assists the planner or scheduler to modify the production schedules according to equipment availability.
MOC and eAM integration:
-
Reduces reaction time between event occurrence and the action/response
-
Improves scheduling based on equipment availability
MOC and eAM integration supports:
-
Configuration and collection of eAM specific objects including meter readings, events, and alarms from actual equipment in MOC
-
Process integration between MOC and eAM to meet the principles of Condition Based Maintenance (CBM)
-
Dashboards and KPI's designed for maintenance specific users and roles
-
Manual or automatic actions based on events using Event Management Framework
MOC and eAM integration is illustrated by the following process flow. It illustrates the integration of data coming from Shop floor devices using Event Management Framework.
Data coming from shop floor is collected using the OPC server provided by device partners (Kepware, Matricon or ILS).
MOC processes the data internally and externally. Processing data internally occurs when the data is collected from the OPC server into MOC, and is then processed. Within MOC, rules are defined using Oracle Warehouse Builder (OWB) pluggable mapping to generate events and allow users to acknowledge and manually trigger actions from the role-based dashboard. External processing of data does not involve MOC, and actions occur outside the boundary of MOC. However, the actions are the same for both internal and external processed events.
Actions include creating work requests, and sending email or mobile alert notifications.