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

Collecting Performance Data Chapter 3
To report on running versus downtime data, use the Running
Percent and Downtime Percent columns in the PlantMetrics
Workcell Detail report data source.
For more information, see "Report Data Sources (page 261)".
The advantage of using the method of downtime tracking is that
very little configuration or control system data is required. The
disadvantage of this method is that all the non-running time is
lumped together, making it impossible to determine the downtime
causes.
The ability to configure user-defined events in FactoryTalk Metrics
allows you to collect and report on virtually any event that happens
on the factory floor, provided that the event can be detected by the
control system. This is the most powerful capability of the product,
and through it FactoryTalk Metrics can illuminate all sorts of
conditions (e.g., machine component behavior, setups and
changeovers, quality checks).
With user-defined events, downtime can be tracked to the lowest
level of detail that is implemented in the control system. To
effectively track downtime, control system indicators of a downtime
condition, as well as reason indicators, should be implemented as
separate user-defined events, and be collected in a category called
“Downtime”. Create as many different events as should be useful.
The more distinct events are logged, the better picture of downtime
causes can be created.
You should also identify any conditions that may impact the
machine output that are not caused by machine failure (if that is
your definition of downtime) and configure user-defined events for
them. Examples might be setups, changeovers, or material delays.
Again, the more granular you can make the events, the better.
User-defined Downtime
Events
Rockwell Automation Publication PLTMT-UM001M-EN-P-June 2014 129