Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction 1
Pre-requisites 1
Setup Flowchart 1
Setup Details 3
Create resources 6
Create Equipment 7
Setup Contextualization 10
Setup Tags 10
Load Assets 16
Setup Events 16
Dashboard Details 17
Production Assets 17
OEE by Asset 17
Asset Events 18
Conclusion 22
The Asset Performance Dashboard provides reporting capabilities for production and maintenance
assets within an organization. The dashboard displays reports for the shop floor events such as
breakdown, excessive scrap, unstable equipment, and also details of asset status, production
performance, output, scrap, and operating parameters.
The scope of this whitepaper is restricted to production assets only. Users can additionally prepare
data for non-production assets.
Pre-requisites
Before commencing the data preparation for the asset performance dashboard, complete the following tasks:
Apply MOC patches and configure ODI and OBIEE according to the Oracle Manufacturing Operations Center
Installation Note for release 12.2.4 (Document ID: 1669093.1).
Generate a Gregorian calendar by running the concurrent program MTH: Populate MOC Gregorian Calendar.
Generate seed data by running the ODI scenario MTH_PKG_ SEED_DATA from the ODI studio.
Setup Flowchart
This section provides information on preparing the Asset Performance Dashboard in MOC. Some of the steps
outlined in this flowchart are required and some are optional. You need to perform optional steps only if you intend
to use the related feature or complete certain business functions. MOC allows three modes of data entry application
page, flat files, and tags. Each of the steps describes the applicable data entry modes. For the whitepaper, flat files
are used to the maximum extent possible. However, users can explore other modes as well depending upon their
business requirements.
Create System Create or collect Setup Tags, Setup Equipment Setup Message
Record in MOC Equipment Map to Equipment Standard Rates Domain for Alerts
Load Equipment
Setup or collect Setup Equipment Setup or collect Production Load Assets
Organizations Hierarchy Items Schedules
Legend:
Tag CSV file MOC Page Source EBS
Mandatory Setup
Optional Setup
Create Site
A site represents a production or non-production facility. Define a MOC site using the Site Home page under the
Manufacturing Operations Center Administrator responsibility as shown in Figure 2.
Navigate to ODI Studio with the credentials provided by your administrator. Select the Operator tab and then select
the Load Plans and Scenarios folder. Expand the folder as shown in Figure 3
Select the MTH Setup folder. Expand the folder and then select the MTH Systems subfolder. Select the ODI
Scenario MTH_PKG_SYSTEMS_SETUP_EXT version 001. Right click on the scenario name and select Run. In the
Run prompt, select a Context from the list of values. Logical Agent and Log Level are optional fields. Click OK.
Go to the Site Setup page and then Data Source Regions. Update the Source Organization from -99999 to M1 for
the first record. Next, add a new record with system code as DM and Source Organization as M1 as shown in Figure
4. The second record represents the flat file mode of data entry.
Create Resources
A machine resource is created in each of the departments of the Seattle Manufacturing plant. These resources
include a Paint Shop resource, Testing resource, Assembly resource, and Molding resource. You can complete the
resource setup using the application page, csv file, or collected from the source EBS system.
Navigation: Manufacturing Operations Center Administrator (responsibility) Setup Entity Hierarchy Home
Resource Setup. After setup is completed, it must look as shown in Figure 6.
Alternatively, you can use the MTH_RESOURCES.csv provided as part of this whitepaper that contains demo
data and then run ODI Scenario MTH_PKG_RESOURCES_EXT from ODI Studio. To load resources from EBS, run
the ODI Scenario MTH_PKG_RESOURCES_SRC.
Create Equipment
For this demo, we will use MIXER1201, BRUSH02, CNC2008, BOILER, CONVEYOR, MOLDING MACHINE, and
TESTING MACHINE.
Navigation: Manufacturing Operations Center Administrator (responsibility Setup Entity Hierarchy Home
Equipment Setup. Upon completion, it must look as shown in Figure 7.
Alternatively, you can use the MTH_EQUIP_MASTER.csv provided as part of this whitepaper that contains demo
data. Next, run ODI Scenario MTH_PKG_EQUIPMENT_EXT from the ODI Studio. To load equipment entities from
EBS, run the ODI Scenario MTH_PKG_EQUIPMENT_ENTITIES_SRC. The equipment collected from EBS will have
the following naming convention: <Resource Name + Equipment Item Name + Serial Number>.
SETUP
Navigate to the Equipment Reason Code Setup page to associate reason codes with equipment. Select the
Equipment Hierarchy = Department Hierarchy, Level Name = Equipment, Level Instance = MIXER1201. Click the
Go button. Once the record is displayed in the Equipment Region, select the equipment by clicking the check box
and click the Update Sequentially button. This opens the Update Equipment Reason Code Sequentially:
&EQUIPMENT (1 of 1) page. Select the Downtime tab. In the Reason Code region, add the reason codes for
downtime. Complete the set up for idle time and Scrap. The setup, upon completion, must appear as shown in
Figure 9.
Alternatively, you can use the MTH_EQUIP_REASON_SETUP.csv provided as part of this whitepaper that
contains demo data. Load the csv file to the file location and then run the ODI Scenario
MTH_PKG_EQUIPMENT_REASONS_EXT from the ODI Studio.
Set Up Contextualization
For this whitepaper we will use Tag Based contextualization as shown in figure 10.
Set Up Tags
Set up the tags using the Tag Setup page. Alternatively, use the MTH_TAG_MASTER_UI.csv with the sample data
as per table 6 to update the tag details and then run the ODI scenario MTH_PKG_TAGS_EXT.
Review or update the csv file MTH_ITEMS_MASTER.csv and run the ODI Scenario MTH_PKG_ITEMS_EXT.
TABLE 7: ITEMS
ITEM PRIMARY KEY PRIMARY UOM SOURCE ORG SYSTEM KEY ITEM NAME DESCRIPTION
You can set up item hierarchy by loading MTH_ITEM_HIERARCHY.csv and then running the ODI scenario
MTH_PKG_ITEM_HIERARCHY_EXT.
Alternatively, production schedules can be collected from the source EBS system.
M1-CNC2008 10 ITEM3-M1 EA 6
VALUE
PROFILE
Load Assets
MOC Asset is linked to EAM Asset using the Asset Serial Number. Assets can be created in MOC using
MTH_ASSET_MASTER.CSV and then running the ODI scenario MTH_PKG_ASSETS_EXT. Query the asset from
the Define Asset Number form in EAM (as shown in screenshot). Note the Asset Number, Asset Group, and Asset
Group ID. These must be the same in the MTH Asset Master Table.
Set Up Events
Navigate to Setup > Events Setup and create a new event. Enter Equipment Hierarchy as Department Hierarchy,
Level Name as Equipment, and Level Instance as MIXER1201. Press the Go Button. In the Equipments region,
Equipment MIXER1201 displays. Click Update Sequentially. Select Event Type as Equipment Down. There are
other event types which should be explained as part of the demo, but the scope of this script is limited to equipment
down, and optionally to equipment down over a period. Select Event Action as Create Work Request in EAM, select
Notification Preferences, and enter your Full Name. Tab out of the field. The E-Mail address is defaulted. Save the
record.
Production Assets
The first region displays the time prompts and the asset prompt that contain only the list of production assets. The
default value for the time prompt is the previous month.
The second region displays three charts: OEE By Asset, OEE Breakup by Asset, and Asset Events. The OEE by
Asset chart displays a gauge indicating the OEE value for the selected production asset. The OEE Breakup chart
displays Machine Availability, Machine Performance, and First Pass Yield values. You can navigate to the Machine
Availability Details page, Machine Performance Details page, and First Pass Yield Details page by clicking on the
links in the respective tables in Machine Availability, Machine Performance, and First Pass Yield columns,
respectively. The third chart is Asset Events
OEE by Asset
The OEE by Asset chart displays a gauge indicating the OEE value for the selected production asset.
The Asset Downtime Analysis pie chart displays percentage of down time by downtime reasons
Asset Operation Parameters display the trend of a selected operation parameter from the operation parameter
prompt and consists of a list of operation parameters seeded for Extensible Attribute in MOC. These parameters
include pressure, temperature, RPM, length, width, thickness, and weight.
Asset Events
The Asset Events chart displays details of events triggered for the assets including time, description of events,
reasons for the events, and event actions. Manufacturing Operations Center (MOC) provides two seeded event
actions that include creation of work requests in Oracle Enterprise Asset Management Application and Mail
Notifications.
The Asset Detail Status Trend chart displays trend of run time, idle time, down time, and off time in hours.
The Asset Operation Parameters chart displays the trend of a selected operation parameter from the operation
parameter prompt and consists of a list of operation parameters seeded for Extensible Attribute in MOC. These
parameters include pressure, temperature, RPM, length, width, thickness, and weight.
Conclusion
The Asset Performance Dashboard is a role-based dashboard for plant managers, providing insight into equipment
performance of production and non-production assets. The dashboard provides reports on events, asset detail
status trend, asset downtime analysis, asset production performance, asset output and scrap, and asset operational
parameters for production assets. The dashboard also provides reports about events, asset detail status trend,
asset downtime analysis, and asset operational parameters for non-production assets. This whitepaper illustrates
the steps to implement the Asset Performance Dashboard in Release 12.2.
CONNECT W ITH US
blogs.oracle.com/oracle
Copyright 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
twitter.com/oracle formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0615