Docengoee21sp2 Oee Gettingstarted Eng
Docengoee21sp2 Oee Gettingstarted Eng
Preface
Preparation 1
Defining the Time Model 2
Configuring Reason Trees 3
Configuring State Translation
4
Tables
Displaying Downtime Data 5
Defining Counters and Design
6
SIMATIC IT OEE 2.1 SP2 Speeds
Displaying Counter and Design
Getting Started 7
Speed Data
Configuring Algorithms 8
Configuring Targets and Limits 9
Advanced Runtime Operations 10
Reporting OEE Data 11
SIEMENS AG
Edition 04/2012
Guidelines
This manual contains notices intended to protect the products and connected equipment against
damage. These notices are graded according to severity by the following texts:
CAUTION
Indicates that if the proper precautions are not taken, this can result into property damage.
Important
Highlights key information on handling the product, the product itself or to a particular part of the
documentation.
Note
Draws your attention to additional information.
Trademarks
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and
software described. Since variance cannot be precluded entirely, we cannot guarantee full
consistency. However, the information in this publication is reviewed regularly and any necessary
corrections are included in subsequent editions.
1 Preparation ......................................................................................................................... 10
Guidelines
This manual contains notes of varying importance that should be read with care; i.e.:
Important
Contains essential information regarding handling the product, the product itself or a
specific part of the documentation.
Note
Provides supplementary information regarding handling the product, the product itself or
a specific part of the documentation.
Trademarks
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware
and software described. Since variance cannot be precluded entirely, we cannot guarantee
full consistency. However, the information in this publication is reviewed regularly and any
necessary corrections are included in subsequent editions.
This guide is intended for SIMATIC IT users who are responsible for system configuration,
such as application managers and system integrators (consultants). To be able to
understand the concepts and examples discussed in this guide, the reader should at least
have taken the SIMATIC IT Production Suite Basic Training.
In order to understand this manual, general knowledge of SIMATIC IT is required.
Purpose
This Manual explains How to configure and run a complete OEE project from creating a
PPA Project to viewing algorithms with targets and limits..
Important
This guide does not intend to describe details of OEE installation, migration scenarios,
prerequisites and license requirements. For more information about related concepts,
please see the Related Documentation section.
Related documentation
Document Content
OEE Web Client Online Help Contains information on the using the OEE Web
Client.
These documents are all available online from the SIMATIC IT Documentation Library,
which can be accessed by selecting Start > All Programs > Siemens Automation >
SIMATIC > SIMATIC IT Documentation > English (or German, if available).
Conventions
The table below describes the specific typographic conventions that are used throughout
this manual:
Symbol/
Indicates...
Convention
Text in bold The names of menus, commands, dialog boxes and toolbar buttons and,
in general, all strings (e.g. File menu; Save command).
KEY1+KEY2 Shortcut keys, which permit rapid access to commands (e.g. CTRL+C).
Symbol/
Indicates...
Convention
The SIMATIC IT Documentation Library provides you with a comprehensive and user-
friendly interface to access the overall product documentation where manuals and online
helps can be browsed by functionality or by component.
To access the SIMATIC IT Documentation Library, simply select Start > All Programs >
Siemens Automation > SIMATIC > SIMATIC IT Documentation > English (or German, if
available).
Readme
The installation includes a readme file, which contains information on upgrade procedures
and compatibility with previous releases. This file is supplied both in standard text
(ReadMe.wri) and in Acrobat PDF (ReadMe.pdf) format.
This file is available in folder \ReleaseNotes of the setup DVD. It is also provided in the
SIMATIC IT Documentation Library, which can be accessed by selecting Start > All
Programs > Siemens Automation > SIMATIC > SIMATIC IT Documentation > English
(or German, if available).
Siemens IA AS MES offers a number of training courses to familiarize you with the
SIMATIC IT product suite. To successfully achieve this goal, training consists of lessons in
both theory and practice.
Courses are held year-round, according to a program that is published well in advance of
the first scheduled session.
The material on the basis of which our courses are conducted reflects the result of years of
experience in process, LIMS, quality control and production management.
All courses are held by expert personnel that are aware of the developments and
innovations in the Siemens IA AS MES product suite.
Courses are held in English at the Siemens IA AS MES Training Centers.
Upon request, training courses can also be organized on the customer's premises.
For more information on the training course calendar, please visit our technical web site
(http://www.automation.siemens.com/mcms/mes/en/serviceandsupport/
valueaddedservices/Pages/Default.aspx).
• Software Update Service (SUS): automatic distribution of upgrades and service packs
• Technical Support Service (TSS): support on technical problems with SIMATIC IT
software (standard support and other optional services)
• Online Support: a technical web site, providing information such as Frequently Asked
Questions and technical documentation on SIMATIC IT products
This service provides automatic shipment of new versions and service packs when
released. When a new version / service pack is available for shipping, it is typically shipped
within one month.
One copy of the installation DVD is shipped for each Server covered by Software
Maintenance.
Hot fixes (officially tested and released) are not shipped and must be downloaded from the
Technical Support Service Web site.
To be able to access the TSS, the customer needs to register as a user on the Technical
Support Web site. Connect to http://www.automation.siemens.com/MCMS/MES/EN/Pages/
Default.aspx and in the Restricted areas follow the SIMATIC IT TSS link.
The registration form must be completed with:
• Personal data
• The required company and plant information
• The Contract Number provided by Siemens Back Office when the contract is agreed.
Online Support
A customer who is a registered TSS user, can access the Technical Support Web site
(https://mes-simaticit.siemens.com/tss/RestrictedSupportServices.html), which contains
technical information such as:
• Service conditions (Phone numbers, Working hours, Reaction times,…)
• SIMATIC IT knowledge base: a technical support database that includes practical service
solutions from the Technical Support or the SIMATIC IT community
• SIMATIC IT software (e.g. hot fixes, software examples) and release notes that can be
downloaded
• SIMATIC IT cross-industry libraries that can be downloaded (limited access to SIMATIC
IT certified partners)
• SIMATIC IT product documentation that can be downloaded
• Frequently Asked Questions and useful tips.
Introduction
This Getting Started teaches you how to configure and use SIMATIC® IT OEE product
option to collect and analyze downtime data and key performance indicators to monitor the
efficiency of your plant.
More specifically, you will learn how to:
• create an OEE configuration using the OEE Engineering Client
• use the OEE Web Client to display collected and aggregated data, execute algorithm
calculations and perform other runtime operations.
Prerequisites
This document assumes that you are already familiar with SIMATIC IT Historian, and that
you already installed SIMATIC IT OEE on your computer. Furthermore, it is recommended
that you read at least the OEE Concept Guide before beginning this Getting Started, as it
contains useful information concerning OEE key concepts, and engineering and runtime
workflow.
Scenario
The Getting Started project is based upon an imaginary bottling plant, in which two sections
of the bottling line, deliberately simplified, fill bottles with liquid and cap them.
The restored OEE Plant provides a set of tags and associated tasks in SIMATIC IT RTDS,
which are used to generate simulated online process data. This generated data is used to
represent monitored process data from the bottling plant. Using the simulated data, it is
possible to perform all the monitoring functions required to analyze the availability,
performance and quality in the imaginary plant and, hence, calculate its OEE.
Before setting up your OEE project, you must perform some preliminary steps to set up
information about your plant:
• restore the OEE plant
• create a PPA project the storage, clustering and manipulation of the monitored process
data received from the plant
• create the Equipment Model for the plant, within the PPA project
Introduction
A pre-configured SIMATIC IT example plant is provided for this Getting Started and is found
as a compressed .arq file in the %ICUBEPATH%\Documentation\GettingStarted_Files
directory: it can be opened using SIMATIC IT Backup Manager tool.
Procedure
Result
You have restored the OEE.PLT plant, containing a number of field tags configured in the
Data Dictionary and various simulation tasks created with RTDE. These tasks will be used
to generate dynamic values for the field tags, thereby simulating field data to demonstrate
the OEE capabilities.
Introduction
The configuration on the SIMATIC IT Services level that is required for the Getting Started
project is provided once you have restored OEE.ARQ. However, a Plant Performance
Analyzer project must be configured to collect, store and process the data received from the
plant.
The following procedures explain how to:
• Create a new PPA project
• Create a new PPA configuration
• Create a new OEE configuration
Procedure
Procedure
Procedure
Result
You have created a new Plant Performance Analyzer Project, as well as new configurations
for PPA and OEE.
Introduction
The following plant model, representing a small bottling line, must be configured in PPA
Configuration Editor:
Procedure
Result
You have created a small plant model that will be used for OEE analysis.
Overview
This section explains how to create a simple Time Model for your plant.
Once the Time Model is defined, you will be able to use the following time categories
representing the main reasons of downtime for the plant:
• Planned Shutdown
• Downtime Loss
• Speed Loss
• Quality Loss
Introduction
The first stage in setting up an OEE configuration is to define the time categories into which
the total processing time of BottlingLine1 is divided. These include all the downtime
categories and the remaining Fully Productive Time, which together form the Time Model.
For this example, the Time Model has been kept simple, for clarity. In reality, you can define
whatever categories you like to make the complex process easier to understand and
analyze.
Procedure
1. In the Configuration Editor, delete the default Time Model by right-clicking on Total
Time and selecting Reset Time Model. Everything except the Total Time row is
removed from the Time Model.
2. Right-click inside the main workspace and select Add Row.
3. Type Planned Production Time as Left Item and browse for a color of your choice.
4. Type Planned Shutdown as Right Item and browse for a color of your choice.
5. Repeat the process in steps 2 to 4 to add more rows until you have created the Time
Model shown in the Result section.
Result
Overview
Introduction
Equipment Types help you organize your product structure by equipment type.
Procedure
Result
You have created two Equipment Types: Generic Fan and Generic Machine.
Introduction
Before you can create Reason Trees, you must first specify how many Reason Tree levels
you want to have available for each time category. For our example, you will need to define
all four available levels.
Procedure
Level 1 State
Level 2 Cause
Level 3 Reason
Result
You have defined the names for all four Reason Tree levels.
Introduction
Machine States are used to populate reason trees with all the possible states that can be
assumed by any piece of equipment.
Tip
Creating all the Machine States manually can be a lengthy and tedious task in the case
of complex plants. In alternative, you can create Machine States (and any other
Engineering Object) using Microsoft Excel, as described in the OEE Bulk Operations
manual.
Procedure
Result
You have created all the Machine States for the entire plant.
Introduction
You can create a Reason Tree associated to a particular Equipment Type. A Reason Tree
contains all Machine States that apply to the specified Equipment Type and are organized
hierarchically.
Procedure
Result
You have created the following Reason Tree for your fan equipment:
Introduction
When creating complex Reason Trees, some branches may be repeated in different parts
of the tree. In such cases, it is faster to create reusable Sub Trees.
Procedure
Result
You have created the following Filler Components Sub Tree, which can now be used in
both the Filler and Capper Reason Trees:
Introduction
Complex equipment, such as fillers and cappers, require more complex Reason Trees,
which often contain one or more Sub Trees.
Result Your Filler RT Reason Tree should look like this:
Procedure
Result
Introduction
The Reason Trees of the filler and capper machines are going to be very similar. In this
case, the fastest way to create the capper Reason Tree is to copy the filler Reason Tree,
and then make some changes.
Procedure
5. Create a new Sub Tree called Capper Components, which contains the same states
as the Filler Components Sub Tree, but with Cap instead of Liquid.
6. Add the Capper Components Sub-Tree to the Waiting and Failure states of the
Capper RT Reason Tree.
Result
Overview
This section explains how to create State Translation Tables for existing Reason Trees.
Reason Trees are useful to visualize and classify all the possible reason of downtime for an
equipment unit. They do not, however, provide any mapping between machine status
values collected from the field and machine states. Such mapping is provided by State
Translation Tables, which can be generated automatically from Reason Trees and then
modified manually to specify a value for each Machine State used in by the Reason Tree.
Introduction
After creating Reason Trees, you must create the corresponding State Translation Tables
(STTs), which bind specific Reason Tree state combinations to values received from the
field.
Procedure
Note
5. In the tree list, select Filler RT > Filler STT to display the new STT.
6. Edit the STT so that it looks like the one shown in the Result section.
• To delete a row, right-click it and select Remove.
Tip
You can hold down the SHIFT and CTRL keys to perform multiple row selection.
• To update the Raw Value of a row, double-click a row and enter the new value in the
Modify State Translation Table Item dialog.
7. Repeat this procedure to create the Simple Fan STT (generated from Fan RT), Self
Diagnosing Fan STT (generated from Fan RT) and Capper STT (generated from Capper
RT). In alternative, you can create the STTs using Excel, as explained in the OEE Bulk
Operations Manual.
Result
Introduction
You can now define how each equipment unit retrieves status information from the field, by
configuring equipment attributes.
Procedure
Attribute Value
Microstop Threshold 45
4. In the Downtime Acquisition tab, click the Acquired by Plant Performance Analyzer
radio button.
5. Click the … button next to Status Value.
6. Define a new source point as follows:
Attribute Value
Procedure
Following the steps given in the previous procedure, configure the Capper attributes as
follows:
• General attributes:
Attribute Value
Microstop Threshold 45
• Status value:
Attribute Value
Result
You have configured the Equipment Type, Reason Tree Name and State Translation Table
for the Capper and Filler equipment units, and their status values are now bound to source
points.
Overview
This section explains how to display and modify downtime data at run time, using the OEE
Web Client.
Before being able to do so, you must:
1. Approve the current engineering configuration version.
2. Run the engineering configuration.
3. Configure the OEE Web Client to display data.
Introduction
Before downtime data can be displayed, you must approve both the relevant OEE and PPA
versions, to ensure that they are consistent.
Procedure
Result
Both the PPA and OEE Acquisition Servers are now running and acquiring data.
Introduction
The OEE Web Client is a CAB application containing web pages you can use to view and
modify OEE runtime data.
Prerequisites
You must install the OEE Web Client CAB package as described in OEE Installation
Manual.
Procedure
1. Open Microsoft Internet Explorer and navigate to the following URL: http://localhost/
SITApps/SITPortal/default.aspx.
2. Click the Login tab.
3. Type manager as User Name and click Log In.
4. After logging in, click the Overall Equipment Effectiveness tab.
5. Click User OEE Configuration in the main workspace.
6. In the Equipment section, select BottlingLine\Capper and BottlingLine\Filler.
7. In the Visibility - Refresh section, enable all values and set the refresh to 1 minute.
8. In the Columns Filter section, enable all columns.
9. Click Save Configuration to save the changes.
Result
Introduction
You can view downtime records via the OEE Web Client in two ways:
• in a Gantt chart
• in tabular form
Procedure
Procedure
Result
You are now able to view downtime records. You can also perform other operations on the
DTM Viewer and the Gantt Viewer page, such as exporting data, modifying the display
settings, etc.
Introduction
You can use the DTM Viewer page to modify downtime records manually . This is useful,
for example, when you must enter machine states that cannot be detected automatically.
Procedure
5. Click OK to close the dialog and then click OK again to confirm the operation.
Result
Overview
This section explains how to create counters and design speeds. These two engineering
objects are used, at run time, to collect data related to production measures (for example
number of pieces produced) and speed of equipment units.
Introduction
Before you can create new engineering objects, you must first create a new OEE version of
your engineering configuration.
Procedure
Result
Introduction
You can create Counters to archive the number of items produced or processed by
equipment units. This makes it possible to calculate specific quality-related algorithms.
Procedure
Result
You have defined two Counters that will be used to archive the number of good pieces and
total pieces processed by specific equipment units.
Introduction
Like counters, Design Speeds can be defined in the General Registry. They are used to
archive the speed of equipment units, which is necessary for certain performance-related
algorithms.
Procedure
Result
You have defined a Design Speed that will be used to archive the effective speed of
specific equipment units.
Introduction
After defining Counters in the General Registry, you can associate them to equipment units
and configure how data are acquired at runtime.
Procedure
Attribute Value
Compression Factor 3
Result
You have configured the acquisition of the TotalPieces and GoodPieces counters for both
the Capper and the Filler equipment units.
Introduction
After defining a Design Speed in the General Registry, you can associate it to equipment
units and configure how data are acquired at runtime.
Procedure
Attribute Value
Attribute Value
Result
You have configured the acquisition of the Design Speeds for both the Capper and the
Filler equipment units.
Overview
This section explains how to display counter values and design speed values at run time.
Like downtime records, counter and design speed records can also be modified and
exported.
Introduction
You can view counter records using the OEE Web Client in four ways:
• in tabular form
• in relation to equipment units and contexts
• in trend graphs
• in bar graphs
Prerequisites
Procedure
Procedure
Procedure
Procedure
Result
You can now view counter records. You can also perform other operations with these
pages, like modifying and exporting data, changing the display settings, etc.
Introduction
You can view design speed records using the OEE Web Client in two ways:
• in tabular form
• in trend graphs
Procedure
Procedure
Result
You can now view design speed records. You can also perform other operations using the
Design Speed Viewer, such as modifying and exporting data, changing the display settings,
etc.
Overview
This section explains how to create and configure algorithms which will be used, at run
time, to calculate and display key performance indicators for the plant.
In particular, you will create instances of the following algorithms:
• Mean Time Between Failures
• Mean Time Between Assists
• Availability
• Performance Rate
• Quality Rate
• OEE
Introduction
State Families offer another way to categorize machine states. Unlike Reason Tree levels,
a Machine State can be associated to one or more State Families, and a State Family can
be associated to one or more Machine States.
Prerequisites
You must create a new OEE version to create and update engineering objects.
Procedure
Procedure
Result
Introduction
You can use State Families when configuring the factors of certain algorithms like MTBF
(Mean Time Between Failures) and MTBA (Mean Time Between Assists). These two
algorithms are very similar, depending on the concepts of "failure" and "assist". In this case,
they are defined as follows:
• Failure: an unplanned malfunction lasting more than 30 seconds.
• Assist: an unplanned malfunction lasting 30 seconds or less.
Given these definitions, the Failures State Family can be used for both algorithms and a
distinction can be made between them only as to how Microstops are handled.
Procedure
Procedure
2. Right-click MTBA in the tree list and select New Algorithm. The Add Algorithm wizard
is displayed.
3. Enter MTBA1 as both Algorithm Name and Display Name, and select Microstop
Threshold.
4. In the Numerator Definition step, click Add, select Operating Time, and click OK.
5. In the Denominator Definition step, click Add, select Failures from the State Families
tab, and click OK.
6. Finish the wizard.
Result
Introduction
Procedure
Procedure
Procedure
Procedure
Result
Introduction
You can configure contextual information to be collected together with runtime data, such
as downtime records or counter values. Such contexts are defined through custom fields
created using the Engineering Client. At runtime, you can then filter and group data
according to context values.
Procedure
Procedure
Attribute Value
5. (Optional) Following the steps above, configure custom field acquisition for any counter
or design speed.
6. Repeat this procedure to configure the acquisition of the CustomID custom field for
Filler.
Result
You have created the CustomID custom field and configured how it is acquired both by the
Capper and the Filler equipment units.
Overview
Introduction
Limits are used to configure value ranges for algorithm results. Limits are defined for
specific equipment, in relation to a particular algorithm instance, within a certain time span.
For instance, it is possible to define a limit between 50% and 70% for the Availability of a
piece of equipment, from April 1st to April 15th.
Some OEE web pages are able to display algorithm results in different colors depending on
whether they fall within the range of a limit, thereby providing plant supervisors and
operators with a quick way to evaluate KPIs at-a-glance.
Note that:
• It is not mandatory to specify the end time of a target.
• If two limits are configured on the same piece of equipment and for the same algorithm
instance, they must be defined with the same start and end time but the range of the
limits defined by their minimum and maximum values must not overlap.
Procedure
1. On the side menu bar select the OEE KPI Analysis tab then, the Target and Limit Value
Management page.
2. Select the OEE1 algorithm from the dropdown list.
3. Select limits from the target and limit dropdown list.
4. Insert MyLimit as Name, insert a description of what you want your limit to do as
Description.
5. In the Algorithm Description field insert a description of the algorithm to which you
want to assign the limit.
6. Insert the name of the Product in the product field.
7. In the Start box fill in the day and time fields insert the required timeframe and (optional)
insert the end time and date in the End box.
8. Select Percentage from the Percentage and Absolute dropdown list and insert the
required values.
9. Click Insert and then Click Save.
Note
After step 8 you can configure Triggers which trigger an event whenever the algorithm
value goes above or below them limit, this requires an appropriate Algorithm Event. For
more information see OEE Engineering Client Online Help
Procedure
Result
You have configured the Limits which can be used to add information to algorithm results.
Introduction
Targets are used to configure thresholds for algorithm results. Target are defined for
specific equipment in relation to a particular algorithm instance, within certain time span.
For instance, it is possible to define a target value of 75% for the Performance Rate of a
piece of equipment from March 21st to March 27th.
Some OEE web pages are able to display algorithm results in different colors depending on
whether they are higher or lower than targets, thereby providing plant supervisors and
operators with a quick way to evaluate KPIs at-a-glance.
Note that:
• It is not mandatory to specify the end time of a target.
• It is not possible to configure two targets for the same algorithm, on the same piece of
equipment, with overlapping time spans.
• All targets configured for the same piece of equipment and algorithm instance must have
the same name.
Procedure
1. On the side menu bar select the OEE KPI Analysis tab then, the Target and Limit Value
Management page.
2. Select the OEE1 algorithm from the dropdown list.
3. Select target from the target and limit dropdown list.
4. Insert the MyTarget as Name, insert a description of what you want your target to do as
Description.
5. In the Algorithm Description field insert a description of the algorithm to which you
want to assign the target.
6. Insert the name of the Product in the product field.
7. In the Start box fill in the day and time fields and (optional) insert the end time and date
in the End box.
8. Select Percentage from the Percentage and Absolutedropdown list, and the required
value in the field below.
9. Click Insert and then Click Save.
Note
After step 8 you can assign an alarm to a target. for more information see__OEE
Engineering Client Online Help__.
Procedure
Result
You have configured the Targets which can be used to add information to algorithm results.
Introduction
You can view Targets and Limits in the same way as you can view counters: using the KPI
Viewer page.
Procedure
Result
You can now view algorithm results with their corresponding targets and limits.
Overview
This section explains how to perform some more advanced runtime operations, such as:
• Viewing algorithm results
• Forcing values for contexts
• Configuring and viewing planned downtimes
• Viewing high-level production statistics.
Introduction
You can view algorithm results in the same way you can view counters: using the KPI
Viewer page.
Prerequisites
The OEE version must already have been approved. PPA Acquisition Server and Writing
Service must be stopped and then restarted.
Procedure
Result
You can now view algorithm results grouped according to a custom field.
Introduction
You can use the Context Management page to update context values at runtime.
Procedure
Before you can update context values, you must first modify the OEE Web Client
configuration as follows:
1. In the OEE Web Client, click the Overall Equipment Effectiveness tab and then User
OEE Configuration in the main workspace.
2. In the Context Filter section, select the CustomID context.
3. Click Save Configuration.
Procedure
Result
Introduction
Certain downtime periods, such as scheduled maintenance or plant shutdown, are often
planned ahead of time. In this case, downtime records can be created manually using the
Planned Downtime page.
Procedure
Duration 1 minute
6. Click Add.
Procedure
Result
Introduction
The following web pages can be used to monitor high-level production statistics in real time:
• Runtime Operator Panel
• Equipment Comparison
Procedure
Before you can view high-level production statistics, you must first modify the OEE Web
Client configuration as follows:
1. In the OEE Web Client, click the Overall Equipment Effectiveness tab then click User
OEE Configuration in the main workspace.
2. In the Algorithms section, configure the following settings:
Setting Value
Counter GoodPieces
Procedure
Procedure
3. (Optional) Click Manual Refresh to refresh the page (otherwise, the page will be
refreshed every minute).
Result
You can now view high-level runtime data using the Runtime Operator Panel and the
Equipment Comparison pages.
Introduction
Besides using the standard OEE Web Client pages, SIMATIC IT OEE includes a set of
Operator Pages optimized for touch panel usage.
By using these pages, it is possible to:
• Monitor the current status of one or more production lines and their respective machines.
• Display a production overview for a specific line.
• Update the current and past machine statuses, by justifying, adding or updating stops.
Overview
This section explains how to retrieve specific sets of data from the OEE database using
dedicated OEE standard reports (.rep and .webi reports) provided by SIMATIC IT Report
Manager.
To retrieve data with Report Manager, you must:
1. Create an OEE project and add connections to the OEE database within the Report
Manager Console environment.
2. Install Standard Reports.
3. Run the reports of interest.
4. If necessary, perform additional operations, such as changing the layout of reports,
performing calculations, inserting charts and/or saving the report with different
document formats.
Prerequisite
Check that all Report Manager and Business Objects Services are started (Start > All
Programs > BusinessObjects XI Release 2 > BusinessObjects Enterprise > Central
Configuration Manager).
Procedure
1. Launch Report Manager Console (Start > All Programs > SIMATIC > SIMATIC IT >
Components > Report Manager > Report Manager Console).
2. Select File > New > Project.
3. In the Project Parameters dialog box, type "MyOEEProject" as the name of the project
and click Next.
4. In the Connection Parameters dialog box, configure the following and click OK.
Parameter Description
Component Historian.
5. In the Runtime User Information dialog box, enter the user name and password for a
runtime user (which is usually configured with 'read' rights).
6. If an upgrade is required, a confirmation dialog box is displayed: click Yes.
Introduction
.rep reports are installed by Report Manager in the Administration Tool environment
(Report Manager Console), whereas .webi reports are delivered as BIAR files and must
be installed manually.
WebI reports are located inside the RMAdminToolDataV6.4.zip file under
%ICUBESYS%\SIT\RM\DATA.
In this Getting Started online help, examples are given with both types of standard reports.
Therefore, both procedures below must be followed after creating a project and before
running the reports.
Procedure
Procedure
9. In the Categories step, leave the default settings and click Next.
10. In the Folders and objects step, select the BIAR files you require and click Next.
11. In the Select application folders and objects step, leave the default settings and click
Next.
Result
Standard Reports are imported into the RM repository, under specific folders (for example,
EBR and EBR KPI can be found under the Public Folder > Batch folder; the OEE-DTM
reports can be found under Production > OEE-DTM).
To be used, they must be linked to the correct universe.
Introduction
The Downtime Detail report retrieves data concerning details on a specific selected
downtime from the database.
For a specific downtime record, pertaining to a specific equipment, this report displays the
start and end times, as well as the status duration expressed in terms of time category and
reason tree levels.
This report must be run from the RM InfoView environment.
Procedure
1. Log on to InfoView (Start > All Programs > BusinessObjects XI Release 2 >
BusinessObjects Enterprise).
2. Select the checkbox next to Downtime Detail report and click Modify.
3. Click Edit Query.
4. Click the Properties tab and then click the Browse button next to the Universe box.
5. Select the renamed standard universe created for your project (it should be Univ.
SIMATIC IT Historian PPA for MyOEEProject) and click OK.
6. In the Change Source dialog box, leave the default mappings and click OK.
7. Click Run Queries in the toolbar.
8. In the Prompts dialog box, select or type the required prompt values and click Run
Query.
9. Click Save in the toolbar to apply the settings.
Note
If you do not perform steps 8-9, the changes regarding the universe cannot be saved.
Introduction
This report executes a user-specified algorithm on-the-fly and displays the result in a bar
graph.
Prerequisites
Check that:
• The sql_oee.msi installer has been executed.
• OEE Web Service URL has been set.
Tip
Procedure
Parameter Description
Start Time Type the start time with the format YYYY/MM/DD HH:mm:ss.
End Time Type the end time with the format YYYY/MM/DD HH:mm:ss.
Equipment Select the equipment name from the list of values, or manually type the
list equipment names you require (separated by a comma).
Sub Select a sub cluster from the list of values. The value “none” is acceptable
Cluster if you want to leave the filter empty.
Note
7. Click OK.
Introduction
This report shows the results of any previously-executed algorithms. Choose a Calculation
ID from the list of values.
Procedure
1. Start Report Manager Reporter (Start > All Programs > SIMATIC > SIMATIC IT >
Components > Report Manager > Reporter).
2. Open the OEE-DTM Line Efficiency.rep report (File > Import from Repository> OEE-
DTM).
3. Refresh data.
4. In the Enter or Select Values dialog box, type a value or click Values to select a KPI
calculation value from a list of available values.
5. Click OK.