Reporting and metrics for industrial task flows

The task_classification and contact_type fields distinguish industrial task flows on shared tables, enabling independent metrics for breakdowns, deviations, and root cause analyses.

Industrial operations often run multiple task flows on the same underlying tables, which makes clean reporting difficult unless one flow can clearly be distinguished from another. To address this need, a configurable field called task_classification has been introduced across all industrial task types. Even though it doesn't have to be visible in the UI, it provides the essential metadata. This metadata separates tasks that share storage from the tasks that should follow different workflows. It's primarily used to distinguish breakdowns from deviations and to differentiate breakdown analyses from root cause analyses (RCAs). The tables remain common, but the classification value determines the workflow branch, which enables each category to be reported independently without duplicating data structures.

Deviations include a system-only contact_type field with default values that the system sets automatically. These values aren't user-facing and exist only to support metrics and funnel reporting. A deviation is assigned one of the following contact_type values:

• None: Follows the regular deviation life cycle
• New: A deviation is created with classification breakdown
• Converted: A deviation is escalated to a breakdown

With these two markers, teams can produce straightforward counts. For example, how many breakdowns were created, how many deviations remained regular, and how many deviations escalated, without introducing additional UI complexity.

Parent Topic:Exploring Digital Factory Workspace