Prioritizing machine states – Rockwell Automation FactoryTalk Metrics User Guide User Manual
Page 122

Chapter 3 Collecting Performance Data
After you have defined your machine states, you need to configure
and prioritize them.
The priority of a machine state is used by FactoryTalk Metrics to
select one machine state, if the values collected from one or more
user-defined events would otherwise indicate that two or more
machine states should be active. If there is a situation where the
values of one or more user-defined events can map to more than one
machine state simultaneously, the priority is used to determine
which machine state becomes active. In such a situation, the
machine state with the highest priority (i.e., the lowest priority
number) is selected. If there is no overlap possible between machine
states, their relative priority is unimportant.
In the Sample Enterprise, we would prioritize the machine states in
the following order (from the highest priority to the lowest one):
1. Linefault
This state occurs when data points for Blocked and Starved
are on, so this state must have a higher priority than either of
the other two states. If either Blocked or Starved had a higher
priority than Linefault, the Linefault state would never occur.
2. Blocked
This state must have a higher priority than the Down state,
because when a machine is blocked, it is also down, but when a
machine is down, it is not necessarily blocked (it could be in
the Linefault state, the Starved state, or some down condition
that maps to the Down state).
The relative priority of Blocked and Starved to each other is
unimportant, because when they are both active, the machine
is in the Linefault machine state.
3. Starved
Prioritizing Machine States
122
Rockwell Automation Publication PLTMT-UM001M-EN-P-June 2014