Master Guide

SAP Overall Equipment Effectiveness 1.0

Master Guide

Target Audience
? Technical Consultants
? System Administrators
? Solution Consultants
? Business Process Owners
? Support Specialists

PUBLIC
?vkWo$-"p[C$}Td1Pk.OK)he3 0
Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location: http://service.sap.com/
instguides.

The following table provides an overview of the most important document changes.
Version Date Description
1.0 2013-06-17 Initial Version

2/20 PUBLIC 2013-06-17

Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.1 Planning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.2 Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.3 Related Master Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 SAP OEE Management 1.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Software Units of SAP OEE Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 Overall Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3 Business Scenarios of SAP OEE Management . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 SAP OEE with SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 SAP OEE without SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2013-06-17 PUBLIC 3/20

This page is left blank for documents
that are printed on both sides.
1 Getting Started
1.1 About this Document

1 Getting Started

1.1 About this Document

Purpose

This Master Guide is the central starting point for the technical implementation of SAP Overall
Equipment Effectiveness Management (SAP OEE Management) 1.0. You can find cross-scenario
implementation information as well as scenario-specific information in this guide.

NOTE

The central starting point for the technical upgrade of your SAP application/solution is the
Upgrade Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/
instguides.

Use the Master Guide to get an overview of SAP OEE Management 1.0, its software units, and its scenarios
from a technical perspective. The Master Guide is a planning tool that helps you to design your system
landscape. It refers you to the required detailed documentation, mainly:
mE Installation guides for single software units
mE SAP Notes
mE Configuration documentation
mE SAP Library documentation
For a general overview of the available SAP documentation, see The Main SAP Documentation Types.
The Master Guide consists of the following main sections:
mE SAP OEE Overview: This section provides the high level overview of SAP OEE application.
mE SAP OEE Business Process: This section provides different business processes supported by the SAP
OEE application.
NOTE

You can find the most current information about the technical implementation of SAP OEE
Management 1.0 and the latest installation and configuration guides on SAP Service
Marketplace at http://service.sap.com/instguides. We strongly recommend that you
use the documents available here. The guides are regularly updated.

Constraints

mE The business scenarios that are presented here serve as examples of how you can use SAP software
in your company. The business scenarios are only intended as models and do not necessarily run
the way they are described here in your customer-specific system landscape. Ensure to check your
requirements and systems to determine whether these scenarios can be used productively at your

2013-06-17 PUBLIC 5/20

1 Getting Started
1.2 Related Information

site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems
to ensure they are complete and free of errors before going live.
t This Master Guide primarily discusses the overall technical implementation of SAP OEE
Management 1.0, rather than its subordinate components. This means that additional software
dependencies might exist without being mentioned explicitly in this document. You can find more
information on component-specific software dependencies in the corresponding installation
guides.

1.2 Related Information

1.2.1 Planning Information
For more information about planning topics not covered in this guide, see the following content on
SAP Service Marketplace:
Content Location on SAP Service Marketplace
Latest versions of installation and http://service.sap.com/instguides
upgrade guides
SAP Business Maps - information http://service.sap.com/businessmaps
about applications and business
scenarios
Sizing, calculation of hardware http://service.sap.com/quicksizer
requirements - such as CPU, disk and
memory resource - with the Quick
Sizer tool
Released platforms and technology- http://service.sap.com/platforms
related topics such as maintenance To access the Platform Availablity Matrix directly, enter http://
strategies and language support service.sap.com/pam.

Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about Support Package http://service.sap.com/sp-stacks

Stacks, latest software versions and
patch level requirements
Information about Unicode http://www.sdn.sap.com/irj/sdn/i18n
technology

1.2.2 Further Useful Links

The following table lists further useful links on SAP Service Marketplace:
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/message

SAP Notes search http://service.sap.com/notes

6/20 PUBLIC 2013-06-17

1 Getting Started
1.3 Important SAP Notes

Content Location on SAP Service Marketplace

SAP Software Distribution Center (software download and ordering of http://service.sap.com/swdc
software)
SAP Online Knowledge Products (OKPs) role-specific Learning Maps http://service.sap.com/rkt

1.2.3 Related Master Guides

This Master Guide is based on Master Guides for cross-industry applications. You can find more
information about the relevant applications in the following documents:
Title Location
Guides of SAP http://service.sap.com/instguidesnw
NetWeaver 7.0
Master Guide of SAP https://service.sap.com/instguides SAP Business Suite Application SAP ERP
ERP 6.0
Master Guide of SAP https://service.sap.com/instguides SAP Business Suite Application SAP
MII Manufacturing SAP Manufacturing Integration and Intelligence

1.3 Important SAP Notes

You must read the following SAP Notes before you start the installation. These SAP Notes contain the
most recent information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at http://service.sap.com/notes.
SAP Note Number Title
1468349 SAP Business Suite 7 for SAP NetWeaver 7.3 hubs systems

2013-06-17 PUBLIC 7/20

This page is left blank for documents
that are printed on both sides.
2 SAP OEE Management 1.0 Overview
2.1 Software Units of SAP OEE Management

2 SAP OEE Management 1.0 Overview

SAP OEE Management 1.0 is an SAP MII-based composite application for Overall Equipment
Effectiveness (OEE). OEE is a manufacturing standard term to allow users to analyze plant activity both
in real time and historically to measure, analyze, and adjust manufacturing performance. OEE utilizes
the most common and important sources of manufacturing data and distils them into metrics that
provide a gauge for measuring the availability and performance of equipment and the quality of goods
that the equipment produces.
By assessing equipment performance, plant managers can gain insight into the efficiency and
effectiveness of the manufacturing processes running in their plant. OEE metrics can help them
pinpoint problems and gauge their impact on the overall manufacturing process; it provides a method
for assessing progress as problems are corrected; it can be implemented quickly and easily. However,
OEE is only part of the picture when it comes to achieving overall operational excellence. To be fully
effective, OEE must be evaluated within the larger picture of the entire plant floor, and gaining that
perspective is more involved.
The most efficient way of getting an overall view of plant operations is to integrate your enterprise
software with the plant floor and share the overall manufacturing view to stations throughout the
plant floor in real time. This empowers production personnel to make decisions concerning equipment
based not only on the OEE metrics they can see for the equipment they operate, but on the current
operating status of the entire production.
OEE is comprised of industry and manufacturing standard KPIs and calculations. OEE is in itself an
overall percentage KPI of plant performance made up of three components for Quality, Performance,
and Availability, which are themselves percentage KPIs based on other component KPIs. The Quality
KPI is comprised of component KPIs and calculations for measuring the quality of the parts or product
produced, that is good parts versus bad parts. The Availability KPI is comprised of component KPIs and
calculations for measuring the available time of equipment versus the actual time equipment was
utilized. Finally, the Performance KPI is comprised of component KPIs and calculations for measuring
the amount of product produced given the amount of time equipment was available.

2.1 Software Units of SAP OEE Management

SAP OEE Management has the following software components and the list of dependent components:
Software Component Dependent Software Component
OEE_ERP 1.0 ECC 6.0/6.0X

2013-06-17 PUBLIC 9/20

2 SAP OEE Management 1.0 Overview
2.2 Software Component Matrix

Software Component Dependent Software Component

OEE_MII 1.0 SAP NetWeaver 7.30 SP09 or SAP NetWeaver 7.31 SP06
SAP MII 14.0
HCO_HBA_OEE 1.0 SAP HANA 1.0 SP05 revision 54 or higher
SAP HANA Analytics Foundation 1.0 SP02
HCO_HBA_APPS_OEE 1.0 SAP HANA 1.0 SP05 revision 54 or higher
SAP HANA Analytics Foundation 1.0 SP02
HCO_HBA_OEE 1.0

2.2 Software Component Matrix

This section provides an overview of which business scenario of SAP OEE Management 1.0 uses which
software unit.
For the latest component version and patch level requirements, see Section 1.2.

NOTE

This Master Guide provides just one way to implement each business scenario. For other ways to
implement business scenarios, see the Scenario & Process Component List in SAP Service
Marketplace at http://service.sap.com/scl. The Scenario & Process Component List helps you
to find realization alternatives for SAP solutions, business scenarios and processes. It shows you
which application components are needed to realize a business scenario or process.

Software Units
Business Scenario Key: X = mandatory (X) = optional
OEE_ERP OEE_MII OEE_HANA
SAP OEE with HANA X X X
SAP OEE without HANA X X (X)

2.3 System Landscape

Here is a high level system landscape for SAP OEE Management 1.0 application:

10/20 PUBLIC 2013-06-17

2 SAP OEE Management 1.0 Overview
2.3 System Landscape

 :5
5)8lSAP OEE 1.0 System Landscape

NOTE

The above diagram shows one SAP MII system per plant. It is also possible that you have one SAP
MII system per ERP system. In that case consider appropriate sizing for the SAP MII server. Similarly
it is possible to have one central SAP HANA for multiple ERP systems. In that case consider proper
sizing of the SAP HANA box.

 :5
5)8lSAP OEE Technical System Landscape

2013-06-17 PUBLIC 11/20

2 SAP OEE Management 1.0 Overview
2.4 Overall Implementation Sequence

For high performance, scalability and availability, consider the master guides of respective dependent
components for example, SAP NetWeaver ABAP, SAP NetWeaver Java, SAP HANA, and Plant
Connectivity (PCo).

2.4 Overall Implementation Sequence

Purpose

The following table describes the overall installation sequence for SAP OEE Management 1.0. This table
contains all available software units. However, to implement a specific scenario, you only need a subset
of available software units. Some are only required for special processes. For information about which
software is required to implement a specific scenario, see Section 3.0. For the latest component version
and patch level requirements, see Section 1.2.

Process

Implementation Sequence
Step Action [Required Documentation]
1 Installation of OEE_ERP.
See the Administrators Guide for OEE_ERP at https://service.sap.com/instguides SAP Business
Suite Applications SAP Manufacturing SAP MII-based Manufacturing Products SAP OEE Management
2 Installation of OEE_MII.
See the Administrator's Guide for OEE_MII at https://service.sap.com/instguides SAP Business
Suite Applications SAP Manufacturing SAP MII-based Manufacturing Products SAP OEE Management
3 Installation of OEE_HANA.
See the Administrator's Guide for OEE_HANA at https://service.sap.com/instguides SAP Business
Suite Applications SAP Manufacturing SAP MII-based Manufacturing Products SAP OEE Management

12/20 PUBLIC 2013-06-17

3 Business Scenarios of SAP OEE Management
3.1 SAP OEE with SAP HANA

3 Business Scenarios of SAP OEE

Management

SAP OEE solution can be used in two different scenarios as mentioned below:

3.1 SAP OEE with SAP HANA

SAP OEE Management with SAP HANA has the full capabilities of the software which comprises of the
following:
1. Ability to download SAP ERP and SAP OEE addon configuration data and master data to SAP OEE.
2. Ability to download the production order to SAP OEE and execute the production order.
3. Collect shop floor data manually or automatic through machine interface.
4. Send confirmation to SAP ERP system.
5. Ability to replicate data from SAP ERP and SAP OEE shop floor system to SAP HANA and visualize
some of the KPI values in an analytic report application.

DOhpWtF1CSAP OEE with SAP HANA: High Level Overview

Technical System Landscape

Refer to section 2.3 for System Landscape Requirement.

2013-06-17 PUBLIC 13/20

3 Business Scenarios of SAP OEE Management
3.2 SAP OEE without SAP HANA

Software Units

Refer to section 2.2 for Software Component Matrix.

Implementation Sequence

Refer to section 2.4 for Overall Implementation Sequence.

3.2 SAP OEE without SAP HANA

SAP OEE without SAP HANA has the all capabilities of the software except the SAP HANA reporting
part. This scenario comprises of following capabilities.
1. Ability to download ERP and SAP OEE addon configuration data and master data to SAP OEE.
2. Ability to download the production order to SAP OEE Management and execute the production
order.
3. Collect shop floor data manually or automatic though machine interface.
4. Send confirmation to ERP system.

i<h69SAP OEE without SAP HANA: High Level System Landscape

14/20 PUBLIC 2013-06-17

3 Business Scenarios of SAP OEE Management
3.2 SAP OEE without SAP HANA

System Landscape

M#5c>J%jSAP OEE without SAP HANA: High Level System Landscape

Technical system Landscape

M#5c>J%jSAP OEE without SAP HANA: Technical System Landscape

NOTE

For high performance, scalability, and availability, refer to the master guides of respective
dependent components, for example, SAP Netweaver ABAP, SAP NetWeaver Java, SAP HANA,
and Plant Connectivity (PCo).

2013-06-17 PUBLIC 15/20

3 Business Scenarios of SAP OEE Management
3.2 SAP OEE without SAP HANA

Software Units

Refer to section 2.2 for Software Component Matrix.

Implementation Sequence

Implementation Step 1 and 2 in section 2.4. are required for this scenario.

16/20 PUBLIC 2013-06-17

Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example Gm Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Gm Cross-references to other documentation or published works
Example Gm Output on the screen following a user action, for example, messages
Gm Source code or syntax quoted directly from a program
Gm File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

2013-06-17 PUBLIC 17/20

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.comhttp://service.sap.com/
instguidesinstguides

18/20 PUBLIC 2013-06-17

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.