Rockwell Automation FactoryTalk Metrics User Guide - Manual (Page 119)

Collecting Performance Data Chapter 3
an activity area can be in one and only one machine state at a time,
and each activity area that has machine states configured is always in
the machine state at all times.
The advantage of using machine states is that it is possible to
account for all the time in the activity area by means of the defined
machine states, without gaps and without double counting the time.
If you do not use machine states, you need to implement a similar
machine-state logic in the control system, if you want to collect the
machine state information.
Machine states are defined for the FactoryTalk Metrics application
as a whole (not for individual activity areas). Up to 99 unique
machine states can be defined for a FactoryTalk Metrics application.
When you configure the performance parameters for an activity
area, you can also configure the appropriate machine states for the
activity area. Each activity area can be in only one machine state at a
time, so all machine states should be mutually exclusive. All, some, or
none of the defined machine states can be configured in a particular
activity area.
Each machine state has a priority, so if multiple machine states could
be active simultaneously, only the machine state with the highest
priority would actually be active. If at any time the activity area is
not in a defined machine state, the machine state will be logged as
Undefined.
The following examples illustrate a possible approach to defining
machine states, and how they can be configured for one sample
activity area. The data used in the examples is not available in the
sample databases.
Rockwell Automation Publication PLTMT-UM001M-EN-P-June 2014 119