FactoryTalk Metrics Student Manual 10-10-2020

October 2020
c
Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for use only as
a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The Documentation
should only be used as a learning tool by qualified professionals.
The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this Documentation, mandates
that those responsible for the application and use of those Products must satisfy themselves that all necessary steps have been
taken to ensure that each application and actual use meets all performance and safety requirements, including any applicable
laws, regulations, codes and standards in addition to any applicable technical documents.
In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell Automation”) be
responsible or liable for any indirect or consequential damages resulting from the use or application of the Products described in
this Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on the
alleged use of, or reliance on, this Documentation.
No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software
described in the Documentation.
Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
• properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell Automation
or third-party provided instructions, warnings, recommendations and documentation;
• ensuring that only properly trained personnel use, operate and maintain the Products at all times;
• staying informed of all Product updates and alerts and implementing all updates and fixes; and
• all other factors affecting the Products that are outside of the direct control of Rockwell Automation.
Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is
prohibited.
Throughout this manual we use the following notes to make you aware of safety considerations:
Identifies information about practices or circumstances

that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence
Labels may be located on or inside the drive to alert people that dangerous voltage may be present.
Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.
Rockwell Automation | 2020 2

Table of Contents
Before you begin ........................................................................................................................................... 5
Lesson 1 – FactoryTalk Metrics Overview .................................................................................................... 7
Lesson 2 – FactoryTalk Metrics Guides and Installs on Training Image .................................................... 21
Lesson 3 – Add the Bread Line 3 Data Points to the RAFoods Application ............................................... 23
Lab - Creating a FactoryTalk Transaction Manager Application ............................................................. 26
Part A - Creating a FTTM Application .................................................................................................. 26
Lesson 4 – FactoryTalk Metrics (FTMetrics) Plant Model .......................................................................... 38
Lab – Configuring the FTMetrics Plant Model ......................................................................................... 39
Part A - Adding Bread Line 3 Line to the Plant Model ......................................................................... 39
Part B - Adding the Mixer, Proof-Oven and Packaging Work cells to the Plant Model ....................... 42
Lesson 5 – Configuring FactoryTalk Metrics Machine States ..................................................................... 47
Lab – Configuring Machine States .......................................................................................................... 48
Part A - Creating Machine States ........................................................................................................ 48
Lesson 6 – Configuring the Bread Line 3 Work cell .................................................................................... 50
Lab – Configuring Bread Line 3 Work Cells ............................................................................................ 57
Part A - Configuring the BreadLine3 Work Cell ................................................................................... 57
Part B - Configuring the BL3_Mixer Work Cell .................................................................................... 71
Part C - Configuring the BL3_ProofOven Work Cell ............................................................................ 85
Part D - Configuring the BL3_Packaging Work Cell .......................................................................... 100
Part E - Starting and Verifying the FactoryTalk Transaction Manager Application ........................... 115
Lesson 7 – Creating BL3 Mixer FactoryTalk Metrics User-Defined Events .............................................. 118
Lab – Creating BL3 Mixer FactoryTalk Metrics User-Defined Events ................................................... 119
Part A - BL3 Mixer Line Events .......................................................................................................... 119
Part B - BL3 Mixer Events ................................................................................................................. 128
Part C - BL3 Mixer Over Cycle Events .............................................................................................. 147
3 of 283
Part D - Starting and Verifying the FactoryTalk Transaction Manager Application ........................... 165
Lesson 8 – Creating BL3 ProofOven FactoryTalk Metrics User-Defined Events ..................................... 168
Lab – Creating BL3 ProofOven FactoryTalk Metrics User-Defined Events .......................................... 169
Part A - BL3 ProofOven Line Events ................................................................................................. 169
Part B - BL3 ProofOven Events ......................................................................................................... 177
Part C - BL3 Oven Over Cycle Events............................................................................................... 193
Lesson 9 – Creating BL3 Packaging FactoryTalk Metrics User-Defined Events ...................................... 213
Lab – Creating BL3 Packaging FactoryTalk Metrics User-Defined Events ........................................... 214
Part A - BL3 Packaging Line Events.................................................................................................. 214
Part B - BL3 Packaging Events ......................................................................................................... 222
Part C - BL3 Packaging Over Cycle Events ...................................................................................... 232
Lesson 10 – Exploring the FactoryTalk Metrics Database ....................................................................... 246
Lab – Exploring the FTMetrics Data ...................................................................................................... 248
Part A - Exploring the OEEQWorkcell View....................................................................................... 248
Part B - Exploring the OEEQWorkcellDetail View ............................................................................. 252
Part C - Exploring the OEEQEventHistory View ................................................................................ 255
Part D - Exploring the OEEQEventDetail View .................................................................................. 259
Part E - Exploring the OEEQStateData View .................................................................................... 262
Lesson 11 – Using Report Expert ............................................................................................................. 265
Lab – Using Report Expert to Report on FTMetrics Data ..................................................................... 270
Part A - Viewing FTMetrics with Report Expert Reports .................................................................... 270
Part B - Configuring a User-Defined Parameter Set .......................................................................... 274
Part C - Creating a Report Expert Report .......................................................................................... 280
4 of 283
Before you begin
Before you begin you must check that Studio 5000 Logix Emulate is running. This will ensure that
data is being generated.
1. From the Start menu, open Studio 5000 Logix Emulate.
2. The slots will show “yellow” lights when the Mode is showing “Power Up”.
Note: Hover your mouse over the slot to show the status.
3. When it is finished powering up, check the status of the Mode. If they show “Remote Program”
you will need to change them to “Remote Run” mode.
5 of 283
4. Right-click on the slots that are not in “Remote Run” Mode and click on Run.
5. All slots should be showing “green” lights and in the “Remote Run” Mode.
6 of 283
Lesson 1 – FactoryTalk Metrics Overview
Manufacturing Intelligence
Manufacturing Intelligence Information
Manufacturing Intelligence Information fits into two broad areas. A data-centric view and an
equipment-centric view.
Historian (in general)

• Data-centric view
• Collects values of process variables over time
• Visualization is typically a line chart
• Answers the question: Are my process variables in control?
FactoryTalk Metrics
• Equipment-centric view; monitors machine
• Collect data with specific meaning
• Parts counts
• Event triggers, reason codes
• Extensive interpretation and contextualization of data
• Broad requirements for visualization of KPIs and data
• Answers the question: What is my production equipment doing?
7 of 283
FTMetrics Concepts
Availability
• Measures the difference between when a machine or process SHOULD be making parts or
running a process and when it IS making parts or running a process.
• Availability has two parts - Available Time and Running Time.
• Available time is when a machine or process SHOULD be making parts or running a
process
• Running time is when a machine or process IS be making parts or running a process
• The difference between the two time is the time the machine or process down
• See the following example:
Performance
• Measures the rate at which the machine or process is producing when it is running.
• Example: If a machine ran for 60 minutes and was supposed to produce a part every 60
seconds then it should have produced 60 parts.
• To measure performance requires three parameters
• Total Parts
• Ideal Cycle Time
• Running Time
8 of 283
Quality
• Measures the between the Total Parts produced and the number of Good Parts produced.
Overall Equipment Effectiveness (OEE)

• Measures Availability * Performance * Quality
Overall Equipment Effectiveness (OEE)
9 of 283
FactoryTalk Metrics Data Model
Production Data
• Data to calculate OEE
• Production counts
• Available Time - Running Time – Downtime
• Cycle Times
Custom Events and States
• What are the machines doing?
• State engine
• Time tracking
• Uncover root causes
Context Data
• Used to filter and slice and dice other data
• By date – time – shift
• By Plant Model
• By user defined fields: part – operator – batch – work orders – etc.
FactoryTalk Metrics Data Model
10 of 283
Database Overview
Work cell Table (Conceptual)
Work cell Table Nine Dimensions of Context
Workcell Table Data
Event Table (Conceptual)
Event Table Nine Dimensions of Context
Event Table Data
11 of 283
State Table (Conceptual)
State Table Nine Dimensions of Context
State Table Data
Database Configuration
Work cell Table Data
12 of 283
Event Table Data
State Table Data
13 of 283
Database Reporting
Work cell Table Data
Calculated Values
Calculated Values Continued
14 of 283
Event Table Data
State Table Data
15 of 283
Baking Simulation Demo
Lines
• There are two Lines.
• Bread Line 1
• Bread Line 2
• Example:
16 of 283
Machines
There are three machines on each line:
• Mixer
• The Mixer has 6 steps
• Each step has 1 machine fault associated with it that can stop the process
• Each step has 1 over cycle fault. The over cycle fault does not stop the process
• The Mixer can be either starved or blocked
• Proof-Over
• The Proof-Over has 5 steps
• The Proof-Over can be either starved or blocked
• Packaging
• The Packaging has 5 steps
• Packaging can be either starved or blocked
17 of 283
Using FactoryTalk Metrics (FTMetrics) in the RAFoods Demo
In the RAFoods Demo/Simulation we want to measure the OEE components and events at both the
line and machine levels. The FTMetrics Work cell is used measure both the line and machine
components.
Line Level
• At the line level we wanted to determine the impact of the 3 machines on the overall line
production. This information would allow for real time production results as well as an end of
shift projection report.
Machine Level
• At the line level we wanted to measure the OEE components and events independently for
each machine.
18 of 283
FTMetrics Work cell Configuration Line Level
The line level work cell is not as straight forward as the machine level work cells.
• As an example are the machines running in parallel or series or a combination of both.
• Which machines or machine determines the line level production counts
• How do we measure the line when it is filling up or running out
• Do we want to be proactive as an example if the Mixer is starved but the line still has product
in the Proof-Oven and Packaging do we want that starved condition to impact the line OEE
There is not a right way or a wrong way to configure the line level work cell. You must determine how
each work cell parameter is determined based on your application.
• For the line level OEE we could simply add the machine OEE values and divide by the
number of machines to provide a sample average value for the line
RAFoods Line Level
• There are 4 points that affect the production of the line. When any one of these conditions
exists the overall line production is impacted.
• Mixer Starved
• Proof-Oven Starved
• Packaging Starved
• Packaging Blocked
• As an example a fault in the Proof-Oven does not impact the line production until it causes
the Packaging machine to be starved.
• Production Counts
• Line production counts are the same as the Packaging machine counts.
• The RAFoods Demo does not take into account the line filling or running out
19 of 283
FTMetrics Work cell Configuration Machine Level
• A FTMetrics Work cell has been configured for each machine.
• Each machine is independent of the other machines based on the available and running
parameters for that machine.
• The starved and blocked conditions do not affect the machines available and running parameters.
• The starved and blocked conditions only affect the line level parameters.
• User defined events have been configured for each machine fault, over cycle fault, starved and
blocked conditions
• There are 3 user defined categories for each machine
• Line Events
• Mixer or Proof-Oven or Packaging Events
• Mixer or Proof-Oven or Packaging OverCycle
• Each machine is available when it is in auto mode.
• Each machine is running when it is in auto mode and is not faulted.
• An over cycle condition is not considered a machine fault and will not cause the machine to stop
running.
20 of 283
Lesson 2 – FactoryTalk Metrics Guides and Installs
on Training Image
FactoryTalk Metrics Configuration Guides

FactoryTalk Metrics User Guide
The FactoryTalk Metrics User Guide is designed to help you understand how to access and use the
FactoryTalk Metrics product. This document focuses on the end-user functions of FactoryTalk Metrics
and does not cover installation and operation of underlying system services.
FactoryTalk RSBizWare Administration Guide

The FactoryTalk RSBizWare Administration Guide is designed to help you understand the
RSBizWare architecture, prerequisites and installation.
RA Foods Demo Software

Preconfigured Software
All the software required to complete the rest of the lessons in this courseware have been installed
and configured based on the FactoryTalk Metrics User’s Guide and the FactoryTalk Metrics Detailed
Installation Notes Guide.
Following are some suggestion and comments on the FactoryTalk Metrics Detailed Installation Notes
Guide mentioned above.
Windows Server 2012 R2
• Make sure you have the computer name correct. Changing this later may cause problems
• Make sure that all the windows networking services are configured and functioning correctly
• Verify that you have followed the IIS requirements.
SQL Server 2012
• FactoryTalk Metrics uses the default SQL Server 2012 installation. If you make changes to
the default installation this may result in future problems
• Verify that the IIS setting are configured properly
FactoryTalk Requirements
• Follow the installation guides when installing and configuring all the Rockwell Software
• Verify that all the FactoryTalk application are using the correct FactoryTalk Directory (FTD)
• When configuring a FT Application make use you are using the same names you will use
when you deploy your project to the end user. The names of the Application, Data Servers
and Shortcuts are part of the data point names.
21 of 283
SQL Server Database Requirements
• FactoryTalk Metrics only requires the standard default database.
• The FactoryTalk Metrics does not require any special name. We used FTM
• A SQL Login must be created. That login is used by the FactoryTalk Metrics services to login
to the FactoryTalk Metrics database We use FTM_User
• A System DSN is required. Verify that you have the correct DSN based on your OS
FactoryTalk Transaction Manager
• For collecting FactoryTalk Metrics data the FTM Enterprise connector is the only enterprise
connector required. In the RA Foods Demo we also had an OLEDB connector configured to
collect Time Series data.
• You can use an existing FTTM application or create a new one
RSBizware Services
• The Service Console will be used to configure the FactoryTalk Metrics configuration
• Both Windows Linked Users and FactoryTalk Users can be configured
• Take your time during the configuration as some steps take time to complete as SQL scripts
are running to create all the database tables, views and Stored Procedures required by the
FactoryTalk Metrics configuration
Report Expert
• Report Expert is a separate install
• Report Expert is NOT required to configure or collect FactoryTalk Metrics data
• You must run the Database Wizard to install some additional database objects prior to using
Report Expert. This step is often overlooked
This lesson is complete
22 of 283
Lesson 3 – Add the Bread Line 3 Data Points to the
RAFoods Application
What you will learn:

• Using FactoryTalk Transaction Manager (FTTM)
• Adding data points to a FTTM application
Configuring a FactoryTalk Transaction Manager

Application
Creating a FactoryTalk Transaction Manager Application
FactoryTalk® Transaction Manager software is a Microsoft® Windows®-based application that enables
P P P P P P
the movement of data between process control systems and information management systems. Use
the FactoryTalk Transaction Manager user interface to create transactions that link data points in
devices on your shop floor to columns in your enterprise-wide relational database.
The following FactoryTalk Transaction Manager services work together to move data between data
locations:
Configuration Server
A Configuration Server is a Microsoft Windows 2003/XP/Vista/2008 service that runs continuously to
provide a single interface to the configuration (.dat) files that make up FactoryTalk Transaction
Manager configurations. The Configuration Server simplifies access to configuration files by filtering
changes and interfacing with other FactoryTalk Transaction Manager services, such as the connector
services and Transaction Manager service. The Configuration Server maintains any changes that
affect configuration files and can record them in a log file for future viewing.
The Configuration Server is automatically registered during the FactoryTalk Transaction Manager
installation. When you start the FactoryTalk Transaction Manager user interface for the first time, the
Configuration Server registers on the local host computer. You may then add a Configuration Server
on a remote computer.
Control connectors
The control connector services in the FactoryTalk Transaction Manager facilitate the exchange of
data between the Transaction Manager service and the industrial control systems, such as
programmable logic controllers (PLC) or HMI servers. The Transaction Manager service
communicates with the data server (DDE or OPC) using one of the following control connectors.
23 of 283
Enterprise connectors
FactoryTalk Transaction Manager's enterprise database connector services facilitate the exchange of
data between the Transaction Manager service and the following enterprise database connectors:
• ODBC
• Oracle OCI
• Microsoft OLE DB
The enterprise application connector services facilitate the exchange of data between the Transaction
Manager service and the following enterprise application connectors:
• Microsoft COM+
• Time-series data compression
• FactoryTalk Metrics
Each enterprise database and enterprise application connector service can manage connections with
multiple applications on multiple computers.
Transaction Manager
The Transaction Manager service in the FactoryTalk Transaction Manager manages the flow of data
between:
• control systems and FactoryTalk Transaction Manager via control connector services
U
• enterprise systems and FactoryTalk Transaction Manager via enterprise connector services
U
The Transaction Manager service may also manipulate the data on route to the enterprise system
and return values to the control system. In FactoryTalk Transaction Manager, you must define at least
one enterprise connector, one control connector, and the Transaction Manager service to ensure a
successful configuration.
The Transaction Manager service appears individually in the Service Control Manager.
Transaction Control Manager

The Transaction Control Manager, a service similar to the Transaction Manager, inherits the
functionality of the FactoryTalk Live Data control connector and communicates exclusively with
FactoryTalk servers in configurations that use online edits. The Transaction Control Manager service
appears individually in the Service Control Manager.
FactoryTalk Transaction Manager provides the Configuration Checklist, which is designed to walk you
through the tasks required to configure your FactoryTalk Transaction Manager system.
Data Point Modes

The options in the Data PointCollection Mode group determine the type of event to be used to trigger
the transaction
24 of 283
Scheduled: Maintain the Current Subscribed Value
The RSLinx Classic server sends changes in data point value or quality to the RSLinx control
connector at a specified time interval, which retains the current value in a buffer until the Transaction
Manager service requests it.
Device-Scheduled: Request the Current Value From the Device

The Transaction Manager service requests a data point value from the RSLinx Classic control
connector. The control connector, in turn, requests the value from the RSLinx Classic data server.
The data server retrieves the data point value directly from a device, such as a controller, and sends
the changes in values to the control connector. The control connector then passes the values back to
the Transaction Manager service. The Transaction Manager service waits up to the length of time
specified in the Data Retrieval field for the data point value to be retrieved from the device. If the
value arrives before the specified Data Retrieval time, the value will be used. If it arrives after or not at
all, then the selected substitution option is used. An advantage to using this type of collection mode is
that the data points are not constantly on scan. The disadvantage is that it takes longer to read
individual values, therefore causing data points to time out and be substituted
Unscheduled: Send Subscribed Value Whenever it Changes

When the RSLinx Classic server detects a change in data point value or quality, it sends the value to
the RSLinx control connector, which then passes it to the Transaction Manager service.
25 of 283
Lab - Creating a FactoryTalk Transaction Manager
Application
The following lab will review the minimum steps required to create a FactoryTalk Transaction Manger
application to collect and process FactoryTalk Metrics data.
The FactoryTalk Transaction Manager configuration can be created using the FactoryTalk
Transaction Manager GUI directly or from the FactoryTalk Metrics Service Console.
Part A - Creating a FTTM Application

Note: You will NOT be CREATING or EDITING in any of the following steps in this lab. You
are basically “walking through” configurations that have already been made on this image.
Note: Changing any of the existing FactoryTalk Transaction Manager configuration may
result in future labs not functioning correctly.
1. On the image, from the Start menu (windows icon, lower left) select FactoryTalk Transaction
Manager.
2. If not already, turn on RA Foods by clicking the Start button [ ].
3. Click on Yes to start RA Foods.
4. From the Menu bar select Configuration > Checklist.
26 of 283
5. From the Configuration Name combo box select the RA Foods configuration
Each configuration must have a name.
The RA Foods configuration was created for you.
a. Click the Step 1 button
6. Step 1 defines the configuration. Review the following:

• Name
• Path
• Enable Online Edits
• Control Connector Services
• Enterprise Connector Services
If you check the Enable Online Edits checkbox the only connector available is the FactoryTalk
Live Data connector.
The FactoryTalk Metrics Enterprise Connector Service must be selected if the FTTM is going to
collect FTM data.
Additional Enterprise Connectors can be selected. The Microsoft OLE-DB connector is used for
1T 1T
time series data.

a. Click Close
27 of 283
7. Click Step 2
8. The Connection Definition dialog is used to define each connection service. The
Transaction/Control Manager has the following properties:
• Connector Name
Note: The default name of the Transaction/Control Manager cannot be changed
• Host Name of the computer where the service is running
• Port Number
• User Name: A valid user on the computer where the service is running
• Password: A valid password for the user enter in the User Name text box
9. From the Connector Service combo box select PlantMetrics Connectors.
28 of 283
10. The Connection Definition dialog is used to define each connection service. The PlantMetrics
Connectors has the following properties
• Connector Name
• Host Name of the computer where the service is running
• Port Number
• User Name - A valid user on the computer where the service is running
• Password - A valid password for the user enter in the User Name text box
a. Click Close
11. Click Step 3
29 of 283
12. The FactoryTalk Data Point interface allows you to browse and add the controller tags that your
FactoryTalk Metrics application will require.
All the tags required for Bread Line 3 have already been added
30 of 283
13. The following is a list of tags required to configure the BL_Line_3 work cell and user defined
events.
Line Workcell UDT
FT.RA_Foods._BL3_Line_Workcell.GoodParts
FT.RA_Foods._BL3_Line_Workcell.IdealCT
FT.RA_Foods._BL3_Line_Workcell.Monitored_Availability
FT.RA_Foods._BL3_Line_Workcell.Monitored_Value
FT.RA_Foods._BL3_Line_Workcell.PartId
FT.RA_Foods._BL3_Line_Workcell.Running
FT.RA_Foods._BL3_Line_Workcell.ScrapParts
FT.RA_Foods._BL3_Line_Workcell.Shift
FT.RA_Foods._BL3_Line_Workcell.TotalParts
Line Level Machine Tags
FT.RA_Foods._BL3_Line_1_BreadLine.Mixer_Batch_ID
FT.RA_Foods._BL3_Line_1_BreadLine.Mixer_Current_Product_Code
FT.RA_Foods._BL3_Line_1_BreadLine.Proof_Oven_Batch_ID
FT.RA_Foods._BL3_Line_1_BreadLine.Proof_Oven_Current_Product_Code
FT.RA_Foods._BL3_Line_1_BreadLine.Packaging_Batch_ID
31 of 283
14. The following is a list of tags required to configure the BL3_Mixer work cell and user defined
events
Mixer Workcell UDT
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.IdealCT
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.PartId
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.GoodParts
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.ScrapParts
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.TotalParts
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Shift
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Monitored_Value
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Monitored_Availability
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Running
Mixer Workcell UDT Flex Fields
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Flex_String_2_
Mixer Workcell UDT Events
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Workcell.Events_Digital_9_
32 of 283
Mixer Machine Status
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.MachineActive
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.MachineStep
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.BatchID
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.MachineID
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.MachineStepString
FT.RA_Foods.::_BL3_Program:Mixer.MachineUDT.ProductCode
Mixer Over Cycle
FT.RA_Foods.::_BL3_Program:Mixer.Mixer_Over_Cycle.Mixer_Over_Cycle_Control_Word_5
15. The following is a list of tags required to configure the BL3_ProofOven work cell and user
defined events
ProofOven Workcell UDT
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.IdealCT
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.PartId
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.GoodParts
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.ScrapParts
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.TotalParts
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Shift
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Monitored_Value
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Monitored_Availability
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Running
33 of 283
ProofOven Workcell UDT Flex Fields
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Flex_String_2_
ProofOven Workcell UDT Events
FT.RA_Foods.::_BL3_Program:Proof_Oven.Proof_Oven_Workcell.Events_Digital_9_
ProofOven Machine Status
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.MachineActive
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.MachineStep
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.BatchID
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.MachineID
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.MachineStepString
FT.RA_Foods.::_BL3_Program:Proof_Oven.MachineUDT.ProductCode
34 of 283
ProofOven Over Cycle
FT.RA_Foods.::_BL3_Program:Proof_Oven.ProofOven_Over_Cycle.ProofOvenOverCycleControlWord_5
16. The following is a list of tags required to configure the BL3_Packaging work cell and user
defined events
Packaging Workcell UDT
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.IdealCT
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.PartId
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.GoodParts
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.ScrapParts
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.TotalParts
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Shift
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Monitored_Value
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Monitored_Availability
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Running
Packaging Workcell UDT Flex Fields
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Flex_String_2_
35 of 283
Packaging Workcell UDT Events
FT.RA_Foods.::_BL3_Program:Packaging.Pack_Workcell.Events_Digital_9_
Packaging Machine Status
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.MachineActive
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.MachineStep
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.BatchID
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.MachineID
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.MachineStepString
FT.RA_Foods.::_BL3_Program:Packaging.MachineUDT.ProductCode
Packaging Over Cycle
FT.RA_Foods.::_BL3_Program:Packaging.Packaging_Over_Cycle.PackagingOverCycleControlWord_3
17. Click Close
36 of 283
18. Steps 4 and Step 5 will be configured by the FactoryTalk Metrics Configuration Console when
the Bread Line 3 work cells and user defined events are created.
a. Click Close
19. Close Transaction Manager.
This lab and lesson are complete
37 of 283
Lesson 4 – FactoryTalk Metrics (FTMetrics) Plant
Model

• Adding Lines and Work cells to the FTMetrics Model
FTMetrics Plant Model

The plant model describes your plant to the Configuration Console. A plant model is made up of
activity areas—enterprises, sites, areas, lines, and work cells—and of equipment and labor resources
U U U U U U U U U U U U
(and resource sets). These are based on terms that the Instrument Society of America (ISA) 95
standard defines in order to provide common terminology for improved communication and
integration between control systems and enterprise systems. You can also insert custom activity
U U
areas at any level in the hierarchy.
Enterprise
The highest-level activity area, typically representing the business. An enterprise must be at the root
level or the child of a custom activity area; it cannot be the child of a site, area, line, or work cell.
Site
A group of areas, lines, and work cells representing a geographical location at which products are
manufactured. A site must be at the root level or the child of an enterprise or custom activity area; it
cannot be the child of an area, line, or work cell.
Area
A collection of lines and/or work cells within a site, typically representing a main production capability
(for example, electronic assembly) within a manufacturing location. An area must be at the root level
or the child of an enterprise, site, or custom activity area; it cannot be the child of a line or work cell.
Line
A collection of work cells, which are physically located close to one another or are related to one
another in the production process. A line must be at the root level or the child of an enterprise, site,
area, or custom activity area; it cannot be the child of a work cell.
Work cell
A single location in the plant where work is performed. A work cell can be the child of any other type
of activity area.
38 of 283
Lab – Configuring the FTMetrics Plant Model
Part A - Adding Bread Line 3 Line to the Plant Model

The Plant Model dialog box allows you to add, modify, and delete activity areas (for example, areas,
lines, work cells) that are the components of your factory’s plant model. You also configure the
Capacity property, which allows time patterns and exceptions to be applied to plant model elements.
U U
The plant model hierarchy is displayed as a tree. You will select items from this plant model tree
when you perform such tasks as configuring performance parameters, identifying elements on which
to report (for example, with the OEE Detail ActiveX), and configuring time patterns to define plant
schedules.
1. Go to the Start menu and select Configuration Console.
2. If this is the first time you are opening the Configuration Console you may get the following
dialog box.
a. Click OK
39 of 283
3. In the RSBizware Login dialog enter the following:
a. In the User text box enter Admin.
b. In the Password text box enter Admin.
c. Click Login.
4. From the menu select Configure > Plant Model.
5. Expand the RA_Foods tree.

a. Right-click on the Baking area and select New Activity Area > Line
40 of 283
6. Rename the line to BreadLine3.
a. Click OK
41 of 283
Part B - Adding the Mixer, Proof-Oven and Packaging Work cells to the
Plant Model
2. Expand the RA_Foods tree if required.

a. Right-click on the BreadLine3 line and select New Activity Area > Work Cell.
42 of 283
3. Rename the Work Cell to BL3_Mixer.
4. Expand the RA_Foods tree.

43 of 283
5. Rename the Work Cell to BL3_ProofOven.
6. Expand the RA_Foods tree if required.

44 of 283
7. Rename the Work cell to BL3_Packaging.
a. Click OK
45 of 283
9. Expand all the branches of the RA_Foods tree.
a. Verify that your Plant Model is as indicated below
b. Click OK.
46 of 283
Lesson 5 – Configuring FactoryTalk Metrics Machine
States

• Definition of Machine States
• How to configure Machine States
FactoryTalk Metrics Machine States

Machine States
Machine states must be mutually exclusive from each other; that is, a machine can be in one and only
one state at any time. After you configure a machine state, you must associate the state with user-
U
defined events that define when that state becomes active. A machine state becomes inactive when
U
another state becomes active.

While machine states must be mutually exclusive from each other the relationship with user-defined
events can be a one to one or a one to many relationships.
Machine State names and priority are global in scope but Machine State data is collect for each work
cell
You can configure 99 machine states with a priority from 1 to 99 with 1 being the highest and 99 the
lowest.
If a work cell is not in any of the defined states it is in an undefined state with a priority of 100
47 of 283
Lab – Configuring Machine States
The following lab will review the minimum steps required to create Machine States. Machine State
names and priority are global in scope across all work cells.
Part A - Creating Machine States

Note: You will NOT be CREATING or EDITING any of the following steps.
Note: Changing any of the existing Machine State configuration my result in future labs
not functioning correctly
1. If not already running, go to the Start menu and select Configuration Console.
2. From the menu select Configure > FactoryTalk Metrics > Machine States.
48 of 283
3. Review the Machine States. Each Machine State must have a Name and a Priority.
a. For the RA Foods Demo / Simulator we have created a Machine State for each machine step
or state.
b. The priority starts with Mixer Starved state and ends with the Packaging Blocked state. The
only exceptions are the Mixer Blocked and the ProofOven Blocked states these follow the
Packaging Blocked state.
c. Move the slider down to see all of the machine states
d. Click Close
49 of 283
Lesson 6 – Configuring the Bread Line 3 Work cell

• Basic steps to configure a FTMetrics Work cell
• Basic steps to Configure User Defined Categories
• Basic steps to Configured User Defined Events
FTMetrics Work cell Configuration

Configure a Work cell
The Overall Equipment Effectiveness (OEE) value is a performance rating used to measure the
efficiency of a production asset. Use the Configure OEE Performance Parameters dialog to specify
the parameters that will be used in the calculation of the OEE value for an activity area within your
plant. This step of the OEE Performance Parameter configuration process allows you to select the
FactoryTalk Transaction Manager configuration from which performance parameter data will be
collected.
• The Reporting Tag Alias is the prefix that will be added to the event reporting tag names
when they are made available for reporting. When the Reporting Tag Alias is added to the
event reporting tag name, it will uniquely identify the event reporting tags for your activity
area. Enter a 30 character alpha-numeric value.
• Select the FactoryTalk Transaction Manager configuration from which the performance
parameter data will be collected.
• After you have selected the reporting tags to monitor for this activity area, changing the
selected FactoryTalk Transaction Manager Configuration will invalidate your reporting tag
selections.
• Use the navigation buttons on the left-hand side of the dialog to configure the following
parameters for the activity area:
50 of 283
Configure ideal cycle time and part id
The ideal cycle time is part of the throughput value in the OEE equation. It indicates the length of
time, in seconds, that the activity area should take to produce a single good part. If the activity area is
producing parts faster than the ideal cycle time, the OEE rating will improve. If the activity area is
producing parts slower than the ideal cycle time, the OEE rating will be negatively impacted.
The Part Id value tells FactoryTalk Metrics what type of part is being produced by the activity area.
Changes in the Part Id value allow FactoryTalk Metrics to track operation conditions to the type of
part being produced. If you always know what kind of part the activity area is producing, you can
obtain the OEE ratings for the activity area sorted by part.
Select one of the following options to indicate how the application should determine the ideal cycle
time:
• Use a single Ideal Cycle Time: To specify a constant ideal cycle time; type the ideal cycle
time (in seconds) in the Cycle Time box.
• Use a PartId/Cycle Time List: To specify that the ideal cycle time comes from a list that
defines the ideal cycle time for each part; select the list from the Lookup list or create it by
clicking the Create List... button.
• Monitor an Unscheduled data point for Ideal Cycle Time: To specify an unscheduled data
point from which the ideal cycle time is obtained; click the Select... button to select the data
point. Optionally, you can select a data point as the ideal cycle time event trigger and then
specify the actual ideal cycle time by using a FactoryTalk Transaction Manager expression.
Do this by selecting the "Use a FactoryTalk Transaction Manager Expression to determine
the Ideal Cycle Time value" check box and clicking the Edit... button to create the expression
in the FactoryTalk Transaction Manager Expression editor. If you use a FactoryTalk
Transaction Manager expression, the only data point it can reference is the one selected in
the Data Point box.
Select an option to indicate how FactoryTalk Metrics will determine what type of part the activity area
is making.
• Do not monitor Part Id: To refrain from monitoring the Id of the part being worked on.
• Use a single Part Id: To specify that the activity area produces only the part Id specified in
the Part Id box.
• Monitor an Unscheduled data point for Part Id: To specify an unscheduled data point from
which the part Id is obtained; click the Select... button to select the data point.
51 of 283
Configure user-defined Summarization Criteria parameters
A user-defined summarization criterion is a FactoryTalk Metrics Performance Parameter field—similar
to Shift and Part ID—for which data can be collected. When the value of the field changes, it triggers
the summarization of historical performance data for the activity area in the FactoryTalk Metrics Work
cell History report data source and the FactoryTalk Metrics Event History report data source
(depending on the event data summarization type that you select). The collected values can then be
used to filter OEE performance data for the activity area. For example, if your system is configured to
collect a user-defined summarization criterion called Operator ID for this activity area, you will be able
to calculate the OEE performance for the activity area when a particular operator is running this
equipment.
Select the user-defined summarization criterion that you want to collect from the drop-down list.
Select an option to indicate how FactoryTalk Metrics will determine the value for this user-defined
summarization criterion.
• Select the Do not monitor option if you do not want the application to collect values for this
field. The OEE rating for the activity area will always be based on all user-defined
summarization criterion values of this type.
• Select the Specify a value option if you want to provide a single value for this user-defined
summarization criterion. The OEE rating for the activity area will always be based on this
user-defined summarization criterion value. If the summarization criterion is defined as string
or numeric, enter a value in the edit box; if the summarization criterion is defined as Boolean,
select a Boolean value from the drop-down list.
• Select the Specify an Unscheduled Data Point option if you want to monitor a data point in
the control system to determine the value for this user-defined summarization criterion.
Changes in the user-defined summarization criterion value allow FactoryTalk Metrics to track
operation conditions to a specific user-defined summarization criterion value. In the case of
Operator ID, this would allow FactoryTalk Metrics to track what operator is running the
machinery, and would allow you to obtain the OEE rating for the activity area when a specific
operator was running the machinery.
52 of 283
Configure part count parameter
The Part Count parameter is part of the throughput value in the OEE equation. It indicates how many
parts were produced by the activity area. FactoryTalk Metrics does not care what unit is the measure
of the Part Count value because it is just comparing the rate of items produced to the value given for
the ideal cycle time.
You can configure total part count, good part count, and scrap/bad part count. It is not necessary to
collect all three count values; however, at the minimum, you must collect the good part count or be
able to calculate good part count from the part counts that you collect.
Select the tab that corresponds to the type of part count you want to collect (e.g., Total, Good, or
Scrap/Bad).
Select an option to indicate how FactoryTalk Metrics should determine the number of parts (total,
good, or scrap/bad) that the activity area has produced.
• This Part Count Type is not in use: To refrain from monitoring for this type of part count.
• The Plant Model Activity Area monitors a Scheduled or Unscheduled Data Point to
determine Part Count: To specify a data point from which the part count is obtained; click
the Select... button to select a data point.
• Optionally, you can select a data point as the part count event trigger and then specify the
actual part count by using a FactoryTalk Transaction Manager expression. Do this by
selecting the Use a FactoryTalk Transaction Manager Expression to determine Part
Count value check box and clicking the Edit... button to create the expression in the
Expression Editor. If you use a FactoryTalk Transaction Manager expression with this option,
the only data point it can reference is the one selected in the Data Point box.
• Or, optionally, you can have the Activity Area determine the value of a FactoryTalk
Transaction Manager expression on a scheduled basis by selecting the Evaluate this
FactoryTalk Transaction Manager Expression on a scheduled basis and click the Edit...
button to create the expression in the Expression Editor. If you use a FactoryTalk Transaction
Manager expression with this option, it must not contain any unscheduled data points.
• The Plant Model Activity Area evaluates a Formula to determine Part Count: To specify
an unscheduled data point or a scheduled data point from which the part count is obtained;
click the Select... button to select the data point.
53 of 283
Configure scheduled availability parameters
Scheduled Availability and Monitored Availability are used together to determine the availability
component of the OEE equation and to accumulate available time. Together, these values indicate
when the activity area is supposed to be available to produce parts and define shift information.
Scheduled Availability provides the basic availability information for the activity area, and provides the
shift information. This is most commonly done by way of a fixed and repeating time pattern.
Select one of the three options for Scheduled Availability:
• The Plant Model Activity Area is scheduled to be available at all times. With this option, the
system will expect the activity area to be available and producing 24 hours per day, 365 days per
year. No shift information is collected, so reporting by shift is not allowed. This option should be
used only if the activity area runs 24 hours per day, every day.
• Collect Scheduled Availability information from the control system. If shift schedules
change frequently or are variable, this option is more flexible than using a fixed time pattern.
Using this method, both shift information and an optional Scheduled Availability value are
collected from the control system and used to define availability. The necessary data points must
exist in the control system. Three items can be configured:
• Data Point to monitor for shift information – an unscheduled numeric data point which will
contain the current shift number
• Shift Description Lookup List – this list will translate the shift number to a text description –
both values are stored in the database
• Data Point to Monitor for Scheduled Availability – optional unscheduled numeric or binary
data point, non-zero value indicates activity area is scheduled to be available
• A configured Capacity Time Pattern specifies the Plant Model Activity Area’s Scheduled
Availability and Capacity state. A time pattern defines specific periods of available and
unavailable time that repeat into the future, subject to exceptions like holidays or scheduled
maintenance activities. There are three functions in this section, but you must choose the
Composite button to assign a time pattern to the activity area.
• Pattern – to define repeating time patterns of available time, unavailable time, and shifts.
• Exception – to define availability exceptions and apply them to appropriate activity areas.
• Composite – to assign time patterns and exceptions to activity areas.
The configuration of Scheduled Availability results in the creation of several system events contained
in an event category called Available. These events can be viewed by clicking on the Event button on
the Configure Performance Parameter dialog. Data from these events are logged to the database
and used in the calculation of OEE and other metrics. The events include (depending upon which
options are chosen):
• Schedule Available
• Schedule Exception Unavailable
• Overall Available
• Activity Area Exception Unavailable
• Activity Area Shift Id - Point
• Activity Area Scheduled Availability – Point
54 of 283
Configure monitored availability parameters
Scheduled Availability and Monitored Availability are used together to determine the availability
component of the OEE equation and to accumulate available time. Together, these values indicate
when the activity area is supposed to be available to produce parts and define shift information.
Monitored Availability is the determination of machine availability based on the real-time events that
are occurring on the plant floor (such as blocked/starved). Monitored Availability can override
Scheduled Availability to make a machine unavailable when it otherwise would be available
The benefit to using Monitored Availability to determine available time for an activity area is more
accurate efficiency measurements. Even though an activity area can be scheduled to be available for
an 8-hour shift, for example, there can be times during that shift when the machine is not capable of
producing output through no fault of its own. It might be starved by an upstream process, blocked by
a downstream process, or it may have no work orders. If these times are excluded from available
time, a more accurate picture of the machine’s actual efficiency results. To get this information, you
must use one of the Monitored Availability options. Of course, you will also want to track these non-
productive times as custom events or machine states in order to get an accurate picture of how much
production time is being lost and where the fault for this lost time lies.
By default, an activity area must be both Scheduled Available and Monitored Available to be overall
available and to accumulate Available Time. This setting can be changed in the Advanced properties
of the Configure Performance Parameters screen.
Select one of the four options for Monitored Availability:
• The Plant Model Activity Area is always available. This option essentially disables
Monitored Availability. Overall availability will be determined based on the state of Scheduled
Availability only.
• The Plant Model Activity Area determines Monitored Availability based on the current
Machine State. This option uses machine state to determine Monitored Availability. When
machine states are defined, the (Monitored) Availability of each machine state is set. If
machine states are configured for the current activity area, then at any point in time the
activity area will be in one and only one machine state, and the Monitored Availability of that
machine state (either available or unavailable) will be used.
• The Plant Model Activity Area monitors an Unscheduled Data Point to determine
availability. This option specifies an unscheduled numeric or binary data point to monitor,
and when the data point has a non-zero or true value it indicates the activity area is
Monitored Available. An alternative is to create a FactoryTalk Transaction Manager
expression, which if it resolves to a non-zero or true value, the activity area is Monitored
Available.
• The Plant Model Activity Area evaluates a Formula to determine availability. This option
specifies a formula that is constructed from one or more unscheduled numeric or binary data
points, and when the result of that formula has a non-zero or true value it indicates the
activity area is Monitored Available.
55 of 283
The configuration of Monitored Availability results in the creation of several system events contained
in an event category called Available (in addition to those created by the configuration of Scheduled
Availability). These events can be viewed by clicking on the Event button on the Configure
Performance Parameter screen. Data from these events are logged to the database and used in the
calculation of OEE and other metrics. The events include (depending upon which options are
chosen):
• Activity Area Available – Formula
• Activity Area Available – Point
• Available Formula Point
Configure running state parameter

From the Configure Performance Parameters dialog, click the Running State button. The Running
Performance Parameter dialog is displayed.
Running time is part of the availability value in the OEE equation. The Running parameter allows the
control system to indicate when the activity area is actually producing products.
Select an option to indicate how FactoryTalk Metrics should determine when the activity area is
actually running and producing products.
• The Plant Model Activity Area is always in a running state: The activity area is always
considered to be running.
• The Plant Model Activity Area is always running when it is available and not in a
faulted state: The activity area is always running when it is available and not in a fault state.
• The Plant Model Activity Area determines Running State based on the current Machine
State: The activity area is in a running state if the current machine state indicates a running
state.
• The Plant Model Activity Area monitors an Unscheduled Data Point to determine
running state: To specify an unscheduled data point from which running state is determined;
click the Select... button to select a data point. Optionally, you can select a data point as the
running state event trigger and then specify the actual running state value by using a
FactoryTalk Transaction Manager expression. Do this by selecting the Use a FactoryTalk
Transaction Manager Expression to determine the Running State value check box and
clicking the Edit... button to create the expression in the Expression Editor. If you use a
FactoryTalk Transaction Manager expression, the only data point it can reference is the one
selected in the Data Point box.
• The Plant Model Activity Area evaluates a Formula to determine availability: To specify
a formula to determine availability.
56 of 283
Lab – Configuring Bread Line 3 Work Cells
Part A - Configuring the BreadLine3 Work Cell
1. Start Configuration Console if not already running.
2. From the menu select Configure > FactoryTalk Metrics > Performance Parameters
3. Expand the RA_Foods tree and select BreadLine3.

a. Click Configure.
57 of 283
4. We will use the default Plant Model Activity Area and Reporting Alias names.
a. Check the Enable Data Collection check box.
b. From the FactoryTalk Transaction Manager Configuration combo box select the RA
Foods application.
c. Click the Cycle Time / Part Id button to go to the next step.
5. From the Cycle Time Type combo box select Monitor an Unscheduled data point for Ideal
Cycle Time.
a. Click Select.
Note: Clicking the Select button will open the Select Data Point GUI
58 of 283
6. We will configure the Select Data Point GUI to sort for BL3_Line data points.
a. In the textbox enter BL3_Line.
b. Select the Contains option.
Note: You have 2 ways to move the required data point to the Configure Performance
Parameters - drag and drop or just double-click the required parameter
c. Double-click the work cell IdealCT data point.
Note: Do not close the Select Data Point GUI
7. Verify that the work cell IdealCT was selected.
59 of 283
8. From the Part Id Type combo box select Monitor an Unscheduled data point for Part Id.
a. Click Select.
60 of 283
9. The default data type for Part Id is a string type. From the Data Point Type combo box reselect
the Numeric Data Types.
a. Double-click on the work cell PartId data point.
61 of 283
10. Verify that the work cell Part Id data point was selected.
a. Click Part Count.
We did not have to configure the Summarization Criteria because at the line level there are no
operators, batch or product ids
11. Select the Total Part Count tab.

a. Select The Plant Model Activity Area monitors a Scheduled or Unscheduled Data Point
to determine Part Count option.
b. Click Select.
62 of 283
12. Double-click on the work cell Total Parts data point.
13. Verify that the work cell Total Parts data point was selected.
a. Select the Good Part Count tab.
63 of 283
14. Select The Plant Model Activity Area monitors a Scheduled or Unscheduled Data Point to
determine Part Count option.
a. Click Select.
15. Double-click on the work cell Good Parts data point.
64 of 283
16. Verify that the work cell Good Parts data point was selected.
a. Click Scheduled Availability.
17. Select the Collect Scheduled Availability information from the control system option.
a. Click Select.
65 of 283
18. Double-click on the work cell Shift data point.
19. Verify that the work cell Shift data point was selected.
a. Click Monitored Availability.
66 of 283
20. Select The Plant Model Activity Area monitors an Unscheduled Data Point to determine
availability option.
a. Click Select.
21. Double-click on the work cell Monitored_Availability data point.
67 of 283
22. Verify that the work cell Monitored Availability data point was selected.
a. Click Running State.
running state option.
a. Click Select.
68 of 283
24. Double-click on the work cell Running data point.
69 of 283
25. Verify that the work cell Running data point was selected
a. Click Apply.
b. Click OK.
After clicking OK all the required FTTM transaction will be created.
After clicking OK FactoryTalk Metrics System events will be created based on the selections you
have made.
70 of 283
Part B - Configuring the BL3_Mixer Work Cell
1. Expand the RA_Foods trees and select BL3_Mixer.

a. Click Configure.
Foods application.
c. Click the Cycle Time / Part Id button.
Cycle Time
a. Click Select.
Clicking the Select button will open the Select Data Point GUI.
71 of 283
4. We will configure the Select Data Point GUI to sort for BL3_Mixer data points.
a. In the textbox enter BL3_Program:Mixer.Mixer_Workcell.
b. Check the Show Scheduled Data Point check box.
c. Select the Contains option.
d. Select the Sort Descending option.
e. Double-click the workcell IdealCT data point.
72 of 283
a. Click Select.
73 of 283
7. The default data type for Part Id is a string type.
a. From the Data Point Type combo box reselect the Numeric Data Types.
U U
b. Re-check the Show Scheduled Data Point check box.

c. Double-click on the work cell PartId data point.
8. Verify that the work cell Part Id data point was selected.
a. Click Summarization Criteria.
74 of 283
9. From the Select Summarization Criteria combo box select Operator.
a. Select the Specify an Unscheduled Data Point to Provide Summarization Criteria
information for this Plant Model Activity Area option.
b. Click Select.
10. Double-click on the work cell Flex_String_0_ data point.

a. The Data Point Selection GUI was sorted for String Tags.
75 of 283
11. Verify that the work cell Flex_String_0_ was selected.
12. From the Select Summarization Criteria combo box select BatchID.
b. Click Select.

76 of 283
15. From the Select Summarization Criteria combo box select ProductCode.
b. Click Select.
16. Double-click on the work cell Flex_String_2_ data point

77 of 283
17. Verify that the work cell Flex_String_2 was selected
a. Select Part Count.

to determine Part Count option
b. Click Select
19. Double-click on the work cell TotalParts data point.
78 of 283
20. Verify that the work cell TotalParts data point was selected.
a. Click Select.
22. Double-click on the work cell GoodParts data point.
79 of 283
23. Verify that the work cell GoodParts data point was selected.
a. Click Select.
80 of 283
a. Click Select.
81 of 283
29. Verify that the work cell Monitored_Availability data point was selected.
82 of 283
a. Click Select.
83 of 283
32. Verify that the work cell Running data point was selected.
a. Click Apply.
b. Click OK.
have made.
84 of 283
Part C - Configuring the BL3_ProofOven Work Cell
1. Expand the RA_Foods tree and select BL3_ProofOven.

a. Click Configure.
Foods application.
85 of 283
Cycle Time.
a. Click Select.
4. We will configure the Select Data Point GUI to sort for BL3_ProofOven data points.
a. In the textbox enter BL3_Program:Proof_Oven.Proof_Oven_Workcell.
Parameters - drag and drop or just double click the required parameter
e. Double-click the work cell IdealCT data point.
86 of 283
a. Click Select.
87 of 283
8. Verify that the work cell PartId data point was selected.
88 of 283
b. Click Select.

The Data Point Selection GUI was sorted for String Tags.
89 of 283
b. Click Select.
90 of 283
91 of 283
b. Click Select.

92 of 283

b. Click Select.
93 of 283
a. Click Select.
94 of 283
22. Double-click on the work cell GoodParts data point.
23. Verify that the work cell GoodParts data point was selected.
95 of 283
a. Click Select.
96 of 283
a. Click Select.
97 of 283
a. Click Select.
98 of 283
32. Verify that the work cell Running data point was selected.
b. Click Apply.
a. Click OK.
have made.
99 of 283
Part D - Configuring the BL3_Packaging Work Cell
1. Expand the RA_Foods tree and select BL3_Packaging.

a. Click Configure.
b. From the FactoryTalk Transaction Manager combo box select the RA Foods application.
Cycle Time.
a. Click Select.
100 of 283
4. We will configure the Select Data Point GUI to sort for BL3_Packaging data points.
a. In the textbox enter BL3_Program:Packaging.Pack_Workcell.
Parameters - drag and drop or just double click the required parameter
e. Double-click the work cell IdealCT data point.
101 of 283
a. Click Select.
102 of 283
8. Verify that the work cell PartId data point was selected.
103 of 283
b. Click Select.

104 of 283
b. Click Select.

105 of 283
b. Click Select.
106 of 283

107 of 283
b. Click Select.
a. Select the Good Part Count tab
108 of 283
a. Click Select.
22. Double click on the work cell GoodParts data point.
109 of 283
23. Verify that the work cell Good Parts data point was selected.
a. Click Select.
110 of 283
a. Click Select.
111 of 283
112 of 283
a. Click Select
113 of 283
32. Verify that the work cell Running data point was selected
a. Click Apply.
b. Click OK.
After clicking OK all the required FTTM transactions will be created
have made
33. Click Close.
114 of 283
Part E - Starting and Verifying the FactoryTalk Transaction Manager
Application
To start and verify that the FactoryTalk Transaction Manager (FTTM) is collecting FactoryTalk Metrics
data for all the work cells, we will be using the FTTM GUI.
The FTTM GUI can be open from the Start menu or from the Configuration Console Tools menu.
NOTE: The FTTM configuration maybe running from previous lessons.
1. From the Configuration Console menu select Tools > FactoryTalk Transaction Manager >
Run FactoryTalk Transaction Manager.
2. The FTTM GUI needs to get focus by clicking off and then back on the RA Foods tree.
a. Verify that there a transaction in the right-hand window.
b. Click the Start icon (if already running, click Stop and then after stopped, Start).
3. Click Yes.
4. The following dialog box will appear as the FTTM services started.
115 of 283
5. From the View menu select Transaction Monitor.
6. Watch the data update for a minute or so. Verify the following:
a. That all the FTTM transactions have passed
b. That the Failed number is not increasing
c. That all the Database transactions have passed
d. That the Failed Database transactions are not increasing
7. Back in the Configuration Console, select Configure > FactoryTalk Metrics > Performance
Parameters.
116 of 283
8. Verify that the BreadLine3 icon is a Green arrow.
a. Verify that the BL3_Mixer, BL3_ProofOven and BL3_Packaging icons are Green arrows.
b. Click Close.
9. Close Configuration Console and Transaction Manager.
117 of 283
Lesson 7 – Creating BL3 Mixer FactoryTalk Metrics
User-Defined Events

• How to create user-defined categories
• How to create user-defined events
FactoryTalk Metrics User-defined Events

User-defined Events
User-defined (custom) events allow you to perform control system monitoring that is not required to
calculate an OEE value but is of special interest to your organization. By defining custom events, you
can direct FactoryTalk Metrics to monitor specific bits or registers in the plant control system and
maintain historical records on the behavior of those data points. For example, you can use custom
events to trap and record downtime occurrences, e-stops, upstream/downstream status, machine
state information, and operator input. What is captured by custom events and how it is interpreted is
up to you.
There is no specified limit to the number of custom events that can be associated with a plant model
activity area in FactoryTalk Metrics; however, the addition of each new event will consume more
resources from all the components of the system.
The following are the properties of a user-defined event:
Identifying information – Plant model activity area name (referred to as "Work cell Description" in
FactoryTalk Metrics Event History), event description (user-defined), and event category (a user-
defined grouping or folder of related events).
Summarization rules – How FactoryTalk Metrics handles creating multiple records in the database
for a single occurrence of an event. See also: Event Data Summary.
Trigger - Defines how the event starts and ends (e.g., a bit in the control system goes high to signal
the start of the event and goes low at the end of the event). See also: Event Trigger.
Additional data – Optionally, an additional data point can be collected at the start and/or end of the
event, or a counter can be monitored through the duration of an event. Additional data collected
might be an event reason code, entered by an operator, which explains why the event occurred. See
also: Event Value.
Machine state/faults - How this event will be used when determining machine state and in the
calculation of reliability metrics. See also: Machine State/Faults.
Reporting – Each event can be assigned a severity level from 0 to 100. This is useful for reporting
and sorting events. See also: Reporting.
118 of 283
Lab – Creating BL3 Mixer FactoryTalk Metrics User-
Defined Events
Part A - BL3 Mixer Line Events
1. Use the follow table for the BL3_Mixer Line Events:
dialog box.
a. Click OK.

c. Click Login.
119 of 283
5. From the menu select Configure > FactoryTalk Metrics > Performance Parameters.
6. Expand the RA_Foods tree and select BL3_Mixer.

a. Click Configure.
7. Click Events.
120 of 283
8. Click New.
9. Click New to create a new category.
10. In the Category Name textbox enter LineEvents.

a. Click OK.
121 of 283
11. Do the following steps:
a. In the Description textbox enter MixerBlocked.
b. Check the Enabled check box.
c. From the Data Summarization Type combo box select Any Scheduled Shift Change or
Summarization Criteria Change.
d. Click Event Trigger.

a. From the Event Trigger Type select Monitored Bit Low to High Transition.
b. Click Select.
122 of 283
13. You can filter the Select Data Point GUI to reduce the number of data points and to reduce the
chances for errors.
a. In the textbox enter BL3_Program:Mixer.Mixer.
c. Select the Sort Descending option.
d. Double-click the work cell Events_Digital_0_ data point.
Note: Do Not close the Select Data Point GUI
14. Verify that the work cell Events_Digital_0_ data point was selected.
a. Click Machine State/Faults.
123 of 283
15. Do the following steps
a. Select the When this event is active apply the selected Machine State option.
b. From the Select a Machine State combo box select MixerBlocked.
c. Click OK.
16. Verify that the LineEvents category is selected.

a. Click New.
124 of 283
a. In the Description textbox enter MixerStarved.
c. From the Data Summarization Type combo box select Any Scheduled shift Change or

b. Click Select
125 of 283
chances for errors.
a. Double-click the work cell Events_Digital_1_ data point
126 of 283
b. From the Select a Machine State combo box select MixerStarved.
c. Click OK.
127 of 283
Part B - BL3 Mixer Events
Use the follow table for the BL3_Mixer Mixer Events:
1. Click New.
3. In the Category Name textbox enter MixerEvents.

a. Click OK
128 of 283
a. In the Description textbox enter MixerS1MaterAdd.

b. Click Select.
129 of 283
chances for errors.
a. Double-click the work cell Events_Digital_2_ data point
130 of 283
b. From the Select a Machine State combo box select MixerS1MatterAdd.
c. Click OK.
9. Verify that the MixerEvents category is selected.

a. Click New.
131 of 283
a. In the Description textbox enter MixerS2Mix.

b. Click Select.
132 of 283
chances for errors.
a. Double-click on the work cell Events_Digital_3_ data point.
133 of 283
b. From the Select a Machine State combo box select MixerS2Mix.
a. Click OK.

a. Click New.
134 of 283
a. In the Description textbox enter MixerS3MaterAdd.

b. Click Select.
135 of 283
chances for errors.
136 of 283
b. From the Select a Machine State combo box select MixerS3MaterAdd.
c. Click OK.

a. Click New.
137 of 283
a. In the Description textbox enter MixerS4Knead.

b. Click Select.
138 of 283
chances for errors.
139 of 283
b. From the Select a Machine State combo box select MixerS4Knead.
c. Click OK.

a. Click New.
140 of 283
a. In the Description textbox enter MixerS5Dump.

b. Click Select.
141 of 283
chances for errors.
a. Double-click on the work cell Events_Digital_6_ data point
142 of 283
b. From the Select a Machine State combo box select MixerS5Dump.
c. Click OK.

d. Click New.
143 of 283
a. In the Description textbox enter MixerS6CIP.
f. Click Event Trigger.

b. Click Select.
144 of 283
chances for errors.
145 of 283
b. From the Select a Machine State combo box select MixerStep6CIP.
c. Click OK.
146 of 283
Part C - BL3 Mixer Over Cycle Events
Use the follow table for the BL3_Mixer Mixer Over Cycle Events:
1. Click New.
3. In the Category Name textbox enter MixerOverCycle.

a. Click OK.
147 of 283
a. In the Description textbox enter S1_MaterAdd.
c. From the Summarization Type combo box select Any Scheduled Shift Change or

b. Click Select.
148 of 283
chances for errors.
a. Double-click on the Mixer_Over_Cycle_Control_Word_1 data point
7. Verify that the Mixer_Over_Cycle_Control_Word_1 data point was selected.

149 of 283
b. From the Select a Machine State combo box select MixerOverCycleS1MatterAdd.
c. Click OK.
9. Click New.
150 of 283
a. In the Description textbox enter S2_Mix.

b. Click Select.
151 of 283
chances for errors.
a. Double-click the Mixer_Over_Cycle_Control_Word_2 data point.

152 of 283
b. From the Select a Machine State combo box select MixerOverCycleS2Mix.
c. Click OK.
15. Click New.
153 of 283
a. In the Description textbox enter S3_MaterAdd.

b. Click Select.
154 of 283
chances for errors.
a. Double-click on Mixer_Over_Cycle_Control_Word_3 data point.

155 of 283
b. From the Select a Machine State combo box select MixerOverCycleS3MaterAdd.
c. Click OK.
21. Click New.
156 of 283
a. In the Description textbox enter S4_Knead.

b. Click Select.
157 of 283
chances for errors.
a. Double-click on the Mixer_Over_Cycle_Control_Word_4 data point.

158 of 283
b. From the Select a Machine State combo box select MixerOverCycleS4Knead.
c. Click OK.
159 of 283
27. Click New.

a. In the Description textbox enter S5_Dump.
160 of 283
b. Click Select.
chances for errors.
a. Double-click on the Mixer_Over_Cycle_Control_Word_5 data point
161 of 283

b. From the Select a Machine State combo box select MixerOverCycleS5Dump.
c. Click OK.
162 of 283
33. Verify the following:
a. That the LineEvents have been created
b. That the MixerEvents have been created
c. That the MixerOverCycle events have been created
34. Click Apply.

a. Click OK.
163 of 283
35. Click Close.
164 of 283
Part D - Starting and Verifying the FactoryTalk Transaction Manager
Application
data for the Mixer User-Defined Events, we will be using the FTTM GUI.
NOTE: The FTTM Configuration maybe running from previous lessons.
3. Click Yes.
165 of 283

a. That all the FTTM transactions have passed
b. That the Failed number is not increasing
c. That all the Database transactions have passed
d. That the Failed Database transactions are not increasing
7. From the Configuration Console menu select Configure > FactoryTalk Metrics >
Performance Parameters.
166 of 283
8. Verify that the BL_Line_3 icon is a Green arrow. If not, you may have to close the dialog, wait a
short time and then open it back up again.
a. Verify that the BL3_Mixer icon is a Green arrow
b. Click Close
167 of 283
Lesson 8 – Creating BL3 ProofOven FactoryTalk
Metrics User-Defined Events


User-defined Events
up to you.
Identifying information – Plant model activity area name (referred to as "Workcell Description" in
also: Event Value.
and sorting events. See also: Reporting
168 of 283
Lab – Creating BL3 ProofOven FactoryTalk Metrics
User-Defined Events
Part A - BL3 ProofOven Line Events

Use the follow table for the BL3_ProofOven Line Events.
dialog box.
a. Click OK.

c. Click Login.
169 of 283
4. From the menu select Configure > FactoryTalk Metrics > Performance Parameters.
5. Expand the RA_Foods trees and select BL3_ProofOven.

a. Click Configure.
6. Click Events.
170 of 283
7. Click New.
8. In the Event pane click New to create a new category.

a. Click OK.

a. In the Description textbox enter OvenBlocked.
171 of 283
b. Click Select.
chances for errors.
a. In the textbox enter BL3_Program:Proof_Oven.
d. Double-click on the work cell Events_Digital_0_ data point.
172 of 283

b. From the Select a Machine State combo box select ProofOvenBlocked.
c. Click OK.
173 of 283
a. Click New.

a. In the Description textbox enter OvenStarved.

b. Click Select.
174 of 283
chances for errors.
a. Double-click the work cell Events_Digital_1_ data point.
175 of 283
b. From the Select a Machine State combo box select ProofOvenStarved.
c. Click OK.
176 of 283
Part B - BL3 ProofOven Events
Use the follow table for the BL3_ProofOven Oven Events:
1. Click New.
3. In the Category Name textbox enter OvenEvents.

a. Click OK.
177 of 283
a. In the Description textbox enter OvenS1Proofer.

b. Click Select.
178 of 283
chances for errors.
179 of 283
b. From the Select a Machine State combo box select OvenS1Proofer.
c. Click OK.
9. Verify that the OvenEvents category is selected.

a. Click New.
180 of 283
a. In the Description textbox enter OvenS2Zone1.

b. Click Select.
181 of 283
chances for errors.
182 of 283
b. From the Select a Machine State combo box select OvenS2Zone1.
c. Click OK.

a. Click New.
183 of 283

b. Click Select.
184 of 283
chances for errors.
19. Verify that the Workcell Events_Digital_4_ data point was selected.
185 of 283
c. Click OK.

a. Click New.
186 of 283

b. Click Select.
187 of 283
chances for errors.
188 of 283
c. Click OK.

a. Click New.
189 of 283

b. Click Select.
190 of 283
chances for errors.
191 of 283
b. From the Select a Machine State combo box select Oven5Zone4.
c. Click OK.
192 of 283
Part C - BL3 Oven Over Cycle Events
Use the follow table for the BL3_ProofOven Proof Oven Over Cycle Events:
1. Click New.
3. In the Category Name textbox enter ProofOvenOverCycle.

a. Click OK.
193 of 283
a. In the Description textbox enter S1_Proofer.

b. Click Select.
194 of 283
chances for errors.
a. Double-click on the ProofOvenOverCycleControlWord_1 data point.
7. Verify that the ProofOvenOverCycleControlWord_1 data point was selected.

Note: Highlighting and double clicking on the Data Point will move the cursor to the end.
195 of 283
b. From the Select a Machine State combo box select ProofOvenOverCyclesS1Proofer.
c. Click OK.
9. Click New.
196 of 283
a. In the Description textbox enter S2Zone1.

b. Click Select.
197 of 283
chances for errors.
a. Double-click on the ProofOvenOverCycleControl_Word2 data point.
13. Verify that the ProofOvenOverCycleContro_Word2 data point was selected.

198 of 283
b. From the Select a Machine State combo box select ProofOvenOvercycleS2Zone1.
c. Click OK.
15. Click New.
199 of 283

b. Click Select.
200 of 283
chances for errors.

201 of 283
b. From the Select a Machine State combo box select ProofOvenOverCycleS3Zone2.
c. Click OK.
21. Click New.
202 of 283

b. Click Select.
203 of 283
chances for errors.
25. Verify that the ProofOvenOverCycleControlWord4 data point was selected.

204 of 283
c. Click OK.
27. Click New.
205 of 283

b. Click Select.
206 of 283
chances for errors.

207 of 283
c. Click OK.
33. Verify The following:

a. That the LineEvents have been created.
b. That the OvenEvents have been created.
c. That the ProofOvenOverCycle events have been created.
208 of 283
34. Click Apply.
a. Click OK.
35. Close the Manage Performance Parameters dialog.
209 of 283
Application
data for the ProofOven User-Defined Events, we will be using the FTTM GUI.
NOTE: The FTTM configuration maybe running from a previous lesson.
3. Click Yes.
210 of 283
6. Verify the following

a. That all the FTTM transactions have passed.
b. That the Failed number is not increasing.
c. That all the Database transactions have passed.
d. That the Failed Database transactions are not increasing.
211 of 283
8. Verify that the BreadLine3 icon is a Green arrow (may need to close and re-open dialog).
a. Verify that the BL3_ProofOven icon is a Green arrow.
b. Click Close.
212 of 283
Lesson 9 – Creating BL3 Packaging FactoryTalk
Metrics User-Defined Events


User-defined Events
up to you.
Identifying information – Plant model activity area name (referred to as "Work cell Description" in
also: Event Value.
and sorting events. See also: Reporting
213 of 283
Lab – Creating BL3 Packaging FactoryTalk Metrics
User-Defined Events
Part A - BL3 Packaging Line Events

Use the follow table for the BL3_Packaging Line Events:
1. In Configuration Console, select Configure > FactoryTalk Metrics > Performance

Parameters.
2. Expand the RA_Foods trees and select BL3_Packaging.

a. Click Configure.
214 of 283
3. Click Events.
4. Click New.

a. Click OK.
215 of 283
a. In the Description textbox enter PackagingBlocked.

b. Click Select.
216 of 283
chances for errors.
a. In the textbox enter BL3_Program:Packaging.
d. Double-click on the work cell Events_Digital_0_ data point.
217 of 283
b. From the Select a Machine State combo box select PackagingBlocked.
c. Click OK.

a. Click New.
218 of 283
a. In the Description textbox enter PackagingStarved.

b. Click Select.
219 of 283
chances for errors.
a. Double-click the work cell Events_Digital_1_ data point.
220 of 283
b. From the Select a Machine State combo box select PackagingStarved.
61T 61T
c. Click OK.
221 of 283
Part B - BL3 Packaging Events
Use the follow table for the BL3_Packaging Packaging Events:
1. Click New.
3. In the Category Name textbox enter PackagingEvents.

a. Click OK.
222 of 283
a. In the Description textbox enter PackagingS1Slice.

b. Click Select.
223 of 283
chances for errors.
7. Verify that the Workcell Events_Digital_2_ data point was selected.

224 of 283
b. From the Select a Machine State combo box select PackagingS1Slice.
c. Click OK.
9. Verify that the PackagingEvents category is selected.

a. Click New.
225 of 283
a. In the Description textbox enter PackagingS2ChkWght

b. Click Select.
226 of 283
chances for errors.
227 of 283
b. From the Select a Machine State combo box select PackagingS2ChkWght.
c. Click OK.
15. Verify that the PackagingEvents category is selected.

a. Click New.
228 of 283
a. In the Description textbox enter PackagingS3Bag.

b. Click Select.
229 of 283
chances for errors.
230 of 283
b. From the Select a Machine State combo box select PackagingS3Bag.
c. Click OK.
231 of 283
Part C - BL3 Packaging Over Cycle Events
Use the follow table for the BL3_Packaging Packaging Over Cycle:
1. Click New.
3. In the Category Name textbox enter PackagingOverCycle.

a. Click OK.
232 of 283
a. In the Description textbox enter S1Slice.

b. Click Select.
233 of 283
chances for errors.
a. Double-click on the PackagingOverCycleControlWord_1 data point.
7. Verify that the PackagingOverCycleControlWord_1 data point was selected.

Note: Highlighting and double clicking will move the cursor to the end of the Data Point
234 of 283
b. From the Select a Machine State combo box select PackagingOverCycleS1Slice.
c. Click OK.
9. Click New.
235 of 283
a. In the Description textbox enter S2ChkWght.

b. Click Select.
236 of 283
chances for errors.
a. Double-click on the PackagingOverCycleControl_Word2 data point.
13. Verify that the PackagingOverCycleContro_Word2 data point was selected.

Note: Highlighting and double clicking will move the cursor to the end of the Data Point
1T 1T
b. Click Machine State/Faults.
237 of 283
b. From the Select a Machine State combo box select PackagingOvercycleS2ChkWght.
c. Click OK.
15. Click New.
238 of 283
a. In the Description textbox enter S3Bag.
c. From the Summarization Type combo box select Any Scheduled Shift Change or

b. Click Select.
239 of 283
chances for errors.
a. Double-click on the ProofOvenOverCycleControlWord3 data point.
19. Verify that the ProofOvenOverCycleControlWord3 data point was selected.

Note: Highlighting and double-clicking will move the cursor to the end of the Data Point
b. Click Machine State/Faults.
240 of 283
b. From the Select a Machine State combo box select PackagingOverCycleS3Bag.
c. Click OK.
241 of 283
21. Verify The following:
a. That the LineEvents have been created
b. That the PackagingEvents have been created
c. That the PackingOverCycle events have been created
22. Click Apply.

a. Click OK.
23. Click Close to close the Manage Performance Parameters dialog.
242 of 283
Application
data for the Packaging User-Defined Events, we will be using the FTTM GUI
NOTE: The FTTM application may be running from a previous lesson
3. Click Yes.
243 of 283

a. That all the FTTM transactions have passed.
b. That the Failed number is not increasing.
c. That all the Database transactions have passed.
d. That the Failed Database transactions are not increasing.
244 of 283
8. Verify that the BL_Line_3 icon is a Green arrow (close and reopen if necessary).
a. Verify that the BL3_Packaging icon is a Green arrow.
b. Click Close.
245 of 283
Lesson 10 – Exploring the FactoryTalk Metrics
Database

• The Tables that store FTMetrics data
• The FTMetrics Work cell Views
• The FTMetrics User-Defined Events Views
The FTM Database

The FactoryTalk Metrics database is a standard MSSQL database and is by default open to all DB
Administrators and to the Login that was created during installation. It is the end users responsibility
to apply the security level required to secure their data.
Tables
There are 6 tables that store base FTMetrics data. These tables should not be altered in anyway
• OEEWorkCell
• OEEWorkCellFlexData
• OEEEvent
• OEEEventFlexData
• OEEFaultMetricData
• OEEStateData
The size of these tables must be managed to insure that the database does not slow down the
reporting process or fill up the computer HD
Views
There are several views created that the end user can use as a basis for reporting on the FTMetrics
data. We will explore the following views and run some simple queries to demonstrate that type of
information that the views contain.
• OEEQWorkcell
• OEEQWorkcellDetail
• OEEQEventHistory
• OEEQEventDetail
• OEEQStateData
246 of 283
The recordsets returned by the FTMetrics views do not contain any WHERE clauses or GROUP BY
statements.
FactoryTalk Metrics summaries data in 10 minutes blocks of time by default. If a user-defined event
or machine state is active for greater then the length of the summarization time the user-defined
event or machine state will be present in more than one summarization block. To insure that queries
that are using the MAX, MIN and COUNT function are correct you must group your data by the
occurrence ids for the user-defined event or machine state. A new occurrence id is created each time
the user-defined event or machine state is active and is independent of the summarization time.
It is important to use simple queries that return the raw FTMetrics data. Many reporting programs
either round the millisecond up or down or simply not use them at all.
247 of 283
Lab – Exploring the FTMetrics Data
The FTM Data Queries.sql file used in the following lab contains all the queries for all the parts of
this lab. It is divided into Part A to Part E to follow the sections in the lab. The first query in each
section will return all the rows and all the columns from the view. The following views will return only
selected rows and columns and may have additional functions such as SUM, AVG, CAST and
WHERE and GROUP BY statements.
Note: The SQL Query window allows you to run a selected portion of SQL script. In this
way we can run different query scripts from the same script file.
Part A - Exploring the OEEQWorkcell View

The OEEQWorkcell view has the following columns
248 of 283
1. From the Start menu, open SQL Server Management Console.
2. Select Windows Authentication from the Authentication drop-down window.

a. Click Connect.
3. From the File menu select Open > File.
249 of 283
4. Browse to the C: > Class Files > Database Scripts > FTMetrics folder.
a. Select the FTM Data Queries.sql file.
b. Click Open.
5. From the Part A section of the file select the Script One code and click Execute.
250 of 283
6. Verify the Query executed successfully.
a. The Results window now contains all the rows and columns from the view.
b. Use the vertical and horizontal slider bars to view all the data.
c. The volume of data from this query makes it difficult to gain any useful information.
7. Select Part A Script Two and click Execute.

a. The Results window now contains Data that has been filtered and grouped from the view.
b. This query selects certain columns, sum and converts the AvailableTime, RunTime and
Downtime to hours, minutes and seconds and groups the data by line for the last 30 minutes.
c. The filtering and grouping in this query returns information that help us understand how our
lines are running.
251 of 283
Part B - Exploring the OEEQWorkcellDetail View
The OEEQWorkcellDetail view has the following columns:
1. From the Part B section of the file select the Script One code and click Execute.
252 of 283
3. Select Part B Script Two and click Execute.
253 of 283
b. This query selects certain columns, sum and converts the Available_Percent,
Runtime_Percent, Downtime_Percent, Thoughput_Percent and Quality_Percent and groups
the data by line for the last 30 minutes.
lines are running.
254 of 283
Part C - Exploring the OEEQEventHistory View
The OEEQEventHistory view has the following columns:
255 of 283
1. From the Part C section of the file select the Script One code and click Execute

3. Select Part C Script Two and click Execute.
256 of 283
b. This query selects certain columns, sums the Seconds and MSeconds and groups the data
by line for the last 30 minutes.
lines are running.
Note: That FTMetrics has collected event data to the milliseconds level
Note: Some programs that visualize data will round up or down or discard the millisecond
data. You may have an event on for 300ms several time a shift and those programs would
not show and time for the event. It is always a good idea to look at the raw data using
some basic queries.
5. Select Part C Script Three and click Execute.
257 of 283
Note: This query returns the same data as query Script Two but now combines the
milliseconds with the hours, minutes and seconds into one column that could be used to
visualize the data.
258 of 283
Part D - Exploring the OEEQEventDetail View
The OEEQEventDetail view has the following columns:
1. From the Part D section of the file select the Script One code and click Execute.
259 of 283
Note: The Duration is in Hour:Minutes:Seconds and that some of the events have no time
because they were active for 1 second.
3. Select Part D Script Two and click Execute.
260 of 283
a. The Results window now contains Data that has been filtered from the view.
b. The data has filtered out any duration that had zero time and orders the data by sDecription
and sEventDescription.
lines are running.
261 of 283
Part E - Exploring the OEEQStateData View
The OEEQStateData view has the following columns:
1. From the Part E section of the file select the Script One code and click Execute.
262 of 283
Note: The OEEQStateData view does have a milliseconds column
3. Select Part E Script Two and click Execute.
263 of 283
a. The Results window now contains Data that has been filtered from the view.
b. This query selects certain columns, sum and converts the dDurationSeconds and the tEndMil
into a single column and groups the data by sReportingName and sStateDescription for the
last 30 minutes.
lines are running.
5. Close SQL Server Management Studio.
264 of 283
Lesson 11 – Using Report Expert

• Create a Report Expert Parameter Set
• Create a Report Expert Report
Report Expert Overview

What Is Report Expert?
Report Expert is a new reporting environment available for use with FactoryTalk Metrics. Report
Expert is based on Microsoft Reporting Services and allows you to report on data generated by
FactoryTalk Metrics.
Report Expert is an optional component that is installed separately from RSBizWare and the
FactoryTalk Metrics software.
Report Expert provides a web interface to view and interact with three types of reports that display
FactoryTalk Metrics data:
• QuickWeb reports, which are created with the RSBizWare and FactoryTalk Metrics report
authoring tools.
• Microsoft Reporting Services reports, which are created using the Microsoft Report Services
report designer tools.
• Report Expert reports, which are specially modified Microsoft Reporting Services reports.
A fixed number of Report Expert report templates are installed automatically with Report Expert.
These report templates, when combined with parameter sets you can create, will satisfy a wide range
of reporting requirements. You can create new Report Expert reports using Microsoft Reporting
Services.
265 of 283
Features of Report Expert
The Report Expert product provides the following features:
• Uses standard Microsoft Reporting Services for SQL Server.
• Includes Microsoft Reporting Services for SQL Server, and appropriate client licenses.
• Allows you to view Report Expert reports, standard Microsoft Reporting Services reports, and
QuickWeb reports through a single web interface.
• Allows you to create a custom reporting tree.
• Includes value-added content not available in Microsoft Reporting Services, such as:
o Interactive filtering using the plant model and other FactoryTalk Metrics key fields (for
example, any of the five flex fields).
o Dynamic grouping and sorting.
o Expanded date and time filtering, including shift filtering.
o Pre-defined named filters such as Today, Yesterday, and This Week.
o Drill-down and drill-through.
• Allows you to modify standard Microsoft Reporting Services RDL reports to take advantage of
Report Expert parameter passing (passing values from the Report Expert parameter set into
the report).
• Allows you to create parameter sets that define filtering, grouping, and sorting behaviors and
apply these to report templates to create custom reports.
• Allows you to create and modify your own report parameter sets, as well as save parameter
sets with report templates to create custom reports.
• Allows you to use the parameter settings interactively to perform adhoc reporting.
Benefits of Report Expert

Report Expert uses an industry-standard reporting package from Microsoft, not a proprietary reporting
package from Rockwell Automation. This means it can be much easier and more cost-effective for
you to create and maintain a reporting system.
Expertise on Microsoft Reporting Services can be obtained from Microsoft training classes,
publications, and contractors. Microsoft Reporting Services could be the reporting standard for other
applications in your company, allowing for easier integration of FactoryTalk Metrics data with other
data and applications.
266 of 283
Managing Parameter Sets
The Parameter Sets tab allows you to add, modify, and delete the parameter sets that serve as the
filtering criteria required to execute Report Expert reports.
To display the Parameter Sets tab (this is for information, not a Lab):
U U
1. If the Administration page is not already displayed, in the Report Expert toolbar, click
Administration.
2. Click the Parameter Sets tab:
The name of each parameter set must be unique. When you add, modify or copy a
parameter set, the name you specify must not be identical to the name of any parameter
set that already exists. If it is identical, you will be prompted with an error message
"Parameter set name not unique".
267 of 283
Adding a Parameter Set
To add a new parameter set:
1. Click New.
2. In the Parameter Set Name field, enter a name for the parameter set. The name you enter in the
Parameter Set Name field will appear in the Select Parameter Set field.
3. Complete the parameters on the tab:

• Date/Time/Shift. In the Date / Time / Shift parameter, define how you want to filter the data
based on time.
• Grouping. In the Grouping parameter, define how you want to group and organize the
information in the report.
• Sorting. In the Sorting parameter, define how you want the grouped information sorted.
• Plant Model. In the Plant Model parameter, specify the activity areas for which you want
information to be displayed in the report.
• Filtering. In the Filtering parameter, define how you want to further filter the information in
the report.
• TOP N. In the TOP N parameter, define the data limit of a report to for the top (or bottom)
number (N) of occurrences of a field you specify.
• Terminology. In the Terminology parameter, select different domain terminology sets for
your report parameter set.
The terminology sets you apply in the Report Explorer tab take precedence over
terminology sets you apply via the Parameters Set tab.
4. To save the parameter set, click Save.
Copying a Parameter Set

Copying a parameter set saves time when you create a parameter set that has many of the same
settings as an existing parameter set.
To copy an existing parameter set:
1. In the Select Parameter Set field, select the parameter set to copy.
2. Click Copy. In the Parameter Set Name field, (parameter set name) - copy appears.
3. In the Parameter Set Name field, type a name for the parameter set. The name you enter in the
Parameter Set Name field will appear in the Select Parameter Set list.
4. Modify the desired parameter sets.
5. To save the copied parameter set, click Save. Click Cancel to not save the parameter set.
268 of 283
Modifying a Parameter Set
If you modify a parameter set, your changes may affect the reports that use the parameter
set, including reports already saved in the Report Explorer.
To modify an existing parameter set:
1. In the Select Parameter Set field, select the parameter set you want to modify.
2. Modify the desired parameters.
3. To save the modified parameter set, click Save.
4. To save the modified parameter set under a new name, click Save As. The Save As button
appears in place of the Copy button as soon as you modify any of the parameters.
Deleting a Parameter Set

Deleting a parameter set cannot be undone.
To delete an existing parameter set:
1. In the Select Parameter Set field, select the parameter set to delete.
2. Click Delete.
When prompted to confirm your deletion, click Delete again.
Report Expert Reports

Report Expert reports fall into 5 broad categories
• Dashboards
• Current Shift Reports
• Yesterday Reports
• The Weeks Reports
• Configuration reports
269 of 283
Lab – Using Report Expert to Report on FTMetrics
Data
Part A - Viewing FTMetrics with Report Expert Reports

Note: Report Expert is running as an out of the box application. No additional
configuration has been added.
Note: Report expert will read the FactoryTalk Metrics Model and will return the data in the
FactoryTalk Metrics database based on that model. If the FactoryTalk Metrics Model
changes Report Expert will reflect those changes.
Note: Default Parameter Sets will be applied to each report. In following labs we will
create custom or user-defined parameter sets.
Note: Depending on the length of time the RA Foods Demo has been running some of the
default reports may not return any data like Yesterdays Reports or This Weeks Reports. In
addition the RA Foods Demo has 20 minute shifts which may produce errors in the data as
a shift will appear several time in a given day.
1. On the Start menu select Report Expert.

Note: The first time Report Expert opens it must read the FTMetrics Plant Model and will
take additional time to open.
2. Select the Explorer tab and Expand the Current Shift Reports folder and select Production
Current Shift.
270 of 283
3. Cursor down to the BreadLine2 section of the report.
a. Expand the BL2_Mixer row by clicking on the plus icon the report will refresh.
b. Expand the BL2_Packaging row by clicking on the plus icon the report will refresh.
c. Expand the BL2_ProofOven row by clicking on the plus icon the report will refresh.
4. The expand rows indicate that the Part Id is NULL. The reason for this is that Part Id parameter
for Bread Line 1 and 2 WAS NOT configured. The chart then displays the parts as all having a
NULL Id.
271 of 283
5. Cursor down to the BreadLine3 section of the report.
a. Expand the BL3_Mixer row by clicking on the plus icon the report will refresh.
b. Expand the BL3_Packaging row by clicking on the plus icon the report will refresh.
c. Expand the BL3_ProofOven row by clicking on the plus icon the report will refresh.
6. The expanded rows indicate that the Part Id is present. The reason for this is that Part Id
parameter for Bread Line 3 WAS configured. The chart then displays the parts grouped by Part
Id.
Conclusion: This is a good example of the Report Expert reports displaying what is configure for
each work cell within the same report and making reasonable adjustments when the configuration
does not match the report parameters. There may be cases when an adjustment can’t be made and
the report will not display any data or fail to render.
272 of 283
7. Expand the Configuration Reports folder and select the Event Configuration by Events
Category report.
8. This report is will display how the user-defined events were configured and the data points
1T 1T
used in the configuration.

a. Cursor down to the Breadline3 section and review the event configuration data.
273 of 283
Part B - Configuring a User-Defined Parameter Set
In this section we are going to create a new Parameter Set to display the Production Overview
Current Shift report using Line, Work Cell and Part Id grouping and using the Plant Model filter to filter
for BreadLine3 data.
Note: When first using Report Expert it is easier to modify existing parameters sets than
to create new ones.
1. From the Explorer window select the Production Overview Current Shift report.
2. The Parameter Set, Grouping, Plant Model Filter, Time, Sort, Filter and Top N settings.
a. We will modify these setting in the next few steps to display only the Line and Workcell level
for BreadLine3.
274 of 283
3. Review the report and notice that it displays the Site, Area, Line and Work cells. (You will have
to click the “plus” icon for each BreadLine to view the work cells).
4. With the report still in view click the Parameters tab.
5. Click New.
The selected report is called ProductionOverview. We will need that information in Part C of
this lab to create our own report.
275 of 283
6. In the Edit Parameter Set Name textbox enter BreadLine3.
a. From the Time combo box select Current Shift (MAKE SURE you uncheck All).
b. In the Grouping section select Line, Work Cell and Part Id.
c. In the Sorting section select Work Cell.
276 of 283
7. Cursor down to the Plant Model section and check the BreadLine3 check box and the
subsequent machines below it.
Checking these boxes will filter the report at the BreadLine3 level.
a. Click Save.
b. Click the View Report hyperlink.
8. The Production Overview Report now has a Grouping of Line, Work Cell and Part Id and a Plant
Model filter of Breadline3.
277 of 283
9. Clicking on the BreadLine3 plus icon will display the work cells for line 3.
Only BreadLine3 data is being displayed
10. Select the Explorer tab.

a. Select the Production Overview Current Shift report.
That the original parameter set is selected because this was the parameter set the report was
saved with.
278 of 283
11. Select the Parameters tab.
a. From the Select Parameter Set combo box select the BreadLine3 parameter set.
b. Click the View Report hyperlink.
The report is now using the BreadLine3 parameter set.
In Part C we will create a new report using the ProductionOverview report and the BreadLine3
parameter set.
279 of 283
Part C - Creating a Report Expert Report
1. Select the Administration tab.
2. Click New.
3. In the Tree Item Title enter My Reports.

a. Verify that Tree Item Type selected is a Folder.
b. Click Save.
4. Click New.
280 of 283
5. In the Tree Item Title textbox enter Bread Line 3 Production Current Shift.
a. From the Tree Item Type combo box select Report Expert Report.
b. From the Report Expert Report combo box select ProductionOverview.
c. From the Parameter Set combo box select BreadLine3.
d. Click Save.
6. Select the Explorer tab.
7. Expand the My Reports folder and select the Bread Line 3 Production Current Shift report.
281 of 283
8. Review your new report.
This report is using the default Production Overview report with the user-defined parameter set
BreadLine3.
We will use this parameter set in future labs.
9. Close Report Expert.
This lesson is complete
282 of 283
283 of 283

FactoryTalk Metrics Student Manual 10-10-2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FactoryTalk Metrics Student Manual 10-10-2020

Uploaded by

Copyright:

Available Formats

October 2020

Identifies information about practices or circumstances

Rockwell Automation | 2020 2

Before you begin ........................................................................................................................................... 5

Lesson 1 – FactoryTalk Metrics Overview .................................................................................................... 7

Lesson 2 – FactoryTalk Metrics Guides and Installs on Training Image .................................................... 21

Lab - Creating a FactoryTalk Transaction Manager Application ............................................................. 26

Part A - Creating a FTTM Application .................................................................................................. 26

Lesson 4 – FactoryTalk Metrics (FTMetrics) Plant Model .......................................................................... 38

Lab – Configuring the FTMetrics Plant Model ......................................................................................... 39

Part A - Adding Bread Line 3 Line to the Plant Model ......................................................................... 39

Lesson 5 – Configuring FactoryTalk Metrics Machine States ..................................................................... 47

Lab – Configuring Machine States .......................................................................................................... 48

Part A - Creating Machine States ........................................................................................................ 48

Lesson 6 – Configuring the Bread Line 3 Work cell .................................................................................... 50

Lab – Configuring Bread Line 3 Work Cells ............................................................................................ 57

Part A - Configuring the BreadLine3 Work Cell ................................................................................... 57

Part B - Configuring the BL3_Mixer Work Cell .................................................................................... 71

Part C - Configuring the BL3_ProofOven Work Cell ............................................................................ 85

Part D - Configuring the BL3_Packaging Work Cell .......................................................................... 100

Part A - BL3 Mixer Line Events .......................................................................................................... 119

Part B - BL3 Mixer Events ................................................................................................................. 128

Part C - BL3 Mixer Over Cycle Events .............................................................................................. 147

Part A - BL3 ProofOven Line Events ................................................................................................. 169

Part B - BL3 ProofOven Events ......................................................................................................... 177

Part C - BL3 Oven Over Cycle Events............................................................................................... 193

Part A - BL3 Packaging Line Events.................................................................................................. 214

Part B - BL3 Packaging Events ......................................................................................................... 222

Part C - BL3 Packaging Over Cycle Events ...................................................................................... 232

Lesson 10 – Exploring the FactoryTalk Metrics Database ....................................................................... 246

Lab – Exploring the FTMetrics Data ...................................................................................................... 248

Part A - Exploring the OEEQWorkcell View....................................................................................... 248

Part B - Exploring the OEEQWorkcellDetail View ............................................................................. 252

Part C - Exploring the OEEQEventHistory View ................................................................................ 255

Part D - Exploring the OEEQEventDetail View .................................................................................. 259

Part E - Exploring the OEEQStateData View .................................................................................... 262

Lesson 11 – Using Report Expert ............................................................................................................. 265

Lab – Using Report Expert to Report on FTMetrics Data ..................................................................... 270

Part A - Viewing FTMetrics with Report Expert Reports .................................................................... 270

Part B - Configuring a User-Defined Parameter Set .......................................................................... 274

Part C - Creating a Report Expert Report .......................................................................................... 280

1. From the Start menu, open Studio 5000 Logix Emulate.

Historian (in general)

Overall Equipment Effectiveness (OEE)

Overall Equipment Effectiveness (OEE)

FactoryTalk Metrics Data Model

Workcell Table Data

Event Table (Conceptual)

Event Table Nine Dimensions of Context

Event Table Data

State Table Nine Dimensions of Context

State Table Data

Work cell Table Nine Dimensions of Context

Work cell Table Data

Event Table Nine Dimensions of Context

Event Table Data

State Table (Conceptual)

State Table Nine Dimensions of Context

State Table Data

Work cell Table Data

Calculated Values Continued

Event Table Nine Dimensions of Context

Event Table Data