Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Root cause analysis form

The following tables describe the field values for the Root cause analysis form.

FieldDescription
Short descriptionBrief description of the root cause analysis that you’re creating.
DescriptionDetailed description of the root cause analysis that you’re creating.
Functional locationIndustrial facility work area where the root cause analysis is required. This field is defined using the ISA-95 standard. This field is automatically set based on the logged-in user's worker profile.
EquipmentMachine to which the root cause analysis relates.
OriginTask from which the root cause analysis originates.
Found inOrigin or source of the root cause analysis. Options are:- Deviation - Defect - Loss - Other
TypeType of root cause analysis. Options are:- None - Breakdown - Safety - Quality - Performance - Other
Assignment groupTeam or department responsible for completing the task.
Assigned toUser to which the root cause analysis has been assigned. If not selected, this field is populated by the user who opened the root cause analysis.
Additional assignee listList of users to be notified or contributing to the task, but not as the primary assignee. Available options vary depending on the selected functional location or assignment group.
ImpactSegment that the root cause analysis has impact on. Options are:- 1 - Safety - 2 - Quality - 3 - Reliability - 4 - Operations - 5 - Other
UrgencyMeasure of how long the root cause analysis can be delayed until there's a significant impact on an industrial process. Options are:- 1 - Critical - 2 - Important - 3 - Routine
PriorityPriority of the analysis. This field is automatically set based on impact and urgency. Options are:- 1 - Direct - 2 - This shift - 3 - Today - 4 - Within 7 days - 5 - Within 30 days For more details, see Priority matrix for root cause analysis.
Work notesInternal notes about checks, tests, and findings that help identify the cause of the issue.
FieldDescription
WhoIndividuals or teams involved in the issue or affected by it.
WhatDescription of the problem or incident in clear, concise terms.
WhenTimeline of the issue: When it was first detected, when it occurred, and the duration of its impact.
WhereLocation of the issue.
WhyUnderlying causes of the issue.
HowDetails of how the issue occurred and how it was resolved.

Parent Topic:Digital Factory Workspace reference