# Configuring Root Cause Analysis (QMS)

QMS supports the ability for a user to [perform and document a 5 Whys root cause analysis](/en/lr/54469205/) of a _Quality Event_ or _Complaint_.

A 5 Whys Analysis is a common cause-effect technique used to perform root cause analysis. The general approach is to start with your problem statement and ask "why" after each answer, forming the basis of the new "why" until you clearly identify the root cause.

In addition to starting a root cause analysis from a _Quality Event_, QMS users also can start a root cause analysis from an _Investigation_. When the root cause analysis is complete, Vault creates one (1) or more _Root Cause_ records and links them with the _Investigation_ record and the associated _Quality Event_ record.

## Configuration Overview

To use root cause analysis, such as a 5 Whys Analysis, you must perform the following setup steps:

  * Add the _Related Root Cause Analysis Item_ object field to the _Root Cause_ [object page layout](/en/lr/26387/).
  * Add the [_Root Cause Analysis Tool_][1] section to the _Root Cause Analysis_ [object page layout](/en/lr/26387/).
  * Optional: Add the _Investigation_ object field to the _Root Cause_ and _Root Cause Analysis_ object page layouts.
  * Optional: Activate the [_Standalone CAPA_](/en/lr/981251/) field, [add](/en/lr/26387/#how-to-add-object-fields) it to the object layout for the _Root Cause_, _Root Cause Analysis_, and _Investigation_ objects, and configure a [layout rule](/en/lr/51632/) to hide the _Standalone CAPA_ field if it is blank.
  * Add a _Root Cause Analysis_ and a _Root Cause_ related object section to the page layout of any object for which you want to perform root cause analyses, for example, _Quality Event_ [object type page layouts](/en/lr/26387/).
  * Optional: Add the _Root Cause Analysis_ and _Root Cause_ related object sections to the _Investigation Details_ page layout.
  * Configure the [_Root Cause Analysis Lifecycle_][2] according to your organization processes. Optionally, you can create one or more workflows to progress the analysis through the lifecycle.

## Root Cause Analysis Tool {#rca-tool}

Add this section to the _Root Cause Analysis_ object page layout to make it visible to users. The special Root Cause Analysis Tool section allows users to perform 5 Whys analyses in a friendly interface, directly from a _Root Cause Analysis_ object record details page.

## Root Cause Analysis Lifecycle {#rca-lc}

Configure your _Root Cause Analysis Lifecycle_ to fit your business processes. When a _Root Cause Analysis_ record enters the _Completed_ lifecycle state type, Vault automatically creates _Root Cause_ records for each root cause identified in the Root Cause Analysis Tool. If object types are enabled on the _Root Cause_ object, users can select the object type of the created _Root Cause_ records during their analysis. 

Root cause analysis respects _Atomic Security: Relationships_ settings. To make these settings available, enable [secure relationships](/en/lr/47850/#how-to-enable-atomic-security-on-object-to-object-relationships) for the _Root Cause Analysis_ field on the _Root Cause Analysis Item_ object. To enable users to perform a root cause analysis, [set](/en/lr/47850/#secure_inbound_relationships) _Edit_ access for the _Root Cause Analysis Items_ relationship on the relevant states of the _Root Cause Analysis Lifecycle_. In order to prevent users from making changes after the _Root Cause Analysis_ is closed, we recommend [removing](/en/lr/47850/#secure_inbound_relationships) _Edit_ access for any secure relationships in the terminal and post-approval lifecycle states defined by your organization.


### Field Data Transfer

During automated _Root Cause_ creation, Vault transfers _Root Cause Analysis Item_ field data to resulting _Root Cause_ records. Any required standard or custom fields which share the same _Name_ will have their data carried over to the resulting _Root Causes_. This data transfer does not support Formula or Lookup fields, and fields of these types will not appear in the tool, however they may be configured on the _Root Cause Analysis Item_ object, as needed.

## Limitations

The following limitations apply to the Root Cause Analysis feature:

* Root cause analysis supports [static VQL constraints](/en/lr/1037069/#static-reference-constraints) on object reference fields on the _Root Cause_ or _Root Cause Analysis Item_ objects. If VQL constraints apply to a field on the _Root Cause_ object, they do not need to be added to the _Root Cause Analysis Item_ object reference field, and adding a constraint to the _Root Cause Analysis Item_ field that is different than the constraint on the _Root Cause_ reference field may result in an error.
* Vault does not support non-required fields with default values. You must make fields with default values required.

## Related Permissions

To allow users to fully create and perform a 5 Whys Analysis, update or create the appropriate permission sets to provide:

  * _Read_, and _Edit_ permissions for the _Root Cause Analysis_ object and _5 Whys Analysis_ object type
  * _Read_, _Create_, _Edit_, and _Delete_ permissions to the _Root Cause Analysis Item_ object and _Why_ object type
  * _Read_, _Create_, and _Delete_ permissions to the _Root Cause_ object
  * _View_ permissions on the _Root Cause Analysis Tool_ object control within the _Root Cause Analysis_ object permission settings

  [1]: #rca-tool
  [2]: #rca-lc