RCA Template Data Loader

About the Root Cause Analysis (RCA) Template Data Loader

The Root Cause Analysis (RCA) Data Loader allows both primary and third-party content to be imported to APM in accordance with the RCA Data Model. You can then use the imported data to maintain relationships between the RCA data and the Failure Modes and Hypotheses. You can use the data loader to import:
  • Legacy analysis templates
  • Update existing RCA Analyses that have been exported from APM

The data loader transfers data from a fixed-format Excel workbook into either the RCA Data Model or the RCA Logic Tree. The imported data can be any of the following records:

  • An RCA Analysis Template
  • An RCA Event
  • A Failure Mode
  • A Logic Gate
  • An RCA Hypothesis
  • An RCA Diagram Relationship
    Note: The Root Cause Analysis (RCA) Data Loader is not backward compatible with earlier versions of APM.

The RCA Data Loader Template Requirements

To use the Root Cause Analysis (RCA) Template Data Loader, your organization must have completed the deployment of the Root Cause Analysis module.

Security Settings

The Security User performing the data load operation must be associated with either the MI Data Loader User or MI Data Loader Admin Security Role, and must also be associated with the MI PROACT Administrator Security Group or a Security Role that is associated with this Security Group.

The RCA Data Loader Data Models

RCA Data Model



RCA Logic Tree Data Model



The RCA Template Data Loader General Loading Strategy

Best Practices

When importing data using the data loader, you must use the following best practices:
  • ID fields (row 2 of each worksheet) must not include special characters or spaces.
  • Columns in the worksheets must be formatted as either text or dates.
  • The first two rows of each worksheet must not be modified.
  • Only import a maximum of 500 analyses in each data load.
  • You must use the Root Cause Analysis (RCA) Data Loader workbook (Root Cause Analysis (RCA).xlsx). Do not change the values in column headings in any of the worksheets.

Limitations

  • Any column values in a customized format will not be imported by the data loader.
  • If you import the same data multiple times, the most recently imported data is included in the database. If a record is already available in the database and is then reimported, the newly imported file will replace the existing file in the database. The Root Cause Analysis (RCA) Data Loader does not append to the existing record.

Load Sequence

  1. An RCA Analysis is created.
  2. RCA Events are created and linked to the RCA Analysis through the RCA Analysis Relationship.
  3. Failure Modes are created and linked to the RCA Event through the RCA Analysis Relationship.
  4. Logic Gates are created and linked to a Failure Mode through the Has Analysis Relationship, where the Failure Mode is the predecessor of the Logic Gate.
  5. Hypotheses are created and linked to a Logic Gate through the Has Analysis Relationship, where the Hypothesis is the successor of the Logic Gate.

The RCA Template Data Loader Workbook Layout and Use

To import data using the data loader, we provide an Excel workbook (Root Cause Analysis (RCA).xlsx) that supports baseline Root Cause Analysis in APM. This template must be used to perform the data load. Using custom changes in code and in design, you can modify the Excel template to include custom fields used by your organization.

The following table lists the worksheets that are included in the Root Cause Analysis (RCA).xlsx workbook:
WorksheetDescription
RCA_Analysis_TemplateThis worksheet is used to define Analysis records.
RCA_EventThis worksheet is used to define Event records.
RCA_Failure_ModeThis worksheet is used to specify Failure Mode details.
RCA_Logic_GateThis worksheet is used to specify Logic Gate details.
RCA_HypothesisThis worksheet is used to specify Hypothesis details.
RCA_Diagram_RelationshipThis worksheet is used to specify Diagram Relationship details.
RCA_SecondaryEventThis worksheet is used to specify Secondary Event details.

RCA Diagram Relationship

The following Logic Tree diagram shows an RCA Diagram Relationship for a Pump Failure. The Logic Tree displays two distinct parent nodes and their subsequent child nodes:

Using the Logic Tree diagram, you can parse the parent/child relationships into the RCA_Diagram_Relationship worksheet provided by the Root Cause Analysis (RCA) Data Loader workbook. Once the workbook is complete, the Root Cause Analysis (RCA) Data Loader can be employed.
RCA Template KeyParent Node KeyChild Node KeyParent Node TypeChild Node Type
RCA_TEMPLATE_KEYPARENT_NODE_KEYCHILD_NODE_KEYPARENT_NODE_TYPECHILD_NODE_TYPE
1234None101RCA_Analysis_TemplateRCA_Event
1234101201RCA_EventRCA_Failure_Mode
1234101202RCA_EventRCA_Failure_Mode
1234201301RCA_Failure_ModeRCA_Logic_Gate
1234202302RCA_Failure_ModeRCA_Logic_Gate
1234301401RCA_Logic_GateRCA_Hypothesis
1234301402RCA_Logic_GateRCA_Hypothesis
1234302403RCA_Logic_GateRCA_Hypothesis

System Code Tables

The following table lists the fields from the RCA System Codes table that must be configured:
Field NameField ID
Analysis TypeMI_AN_ANALY_TYPE_CHR
Hypothesis Confidence FactorsMI_RCA_HYPOTHESIS_CONFIDENCE_FACTORS
Hypothesis StateRCA_Hypothesis_State

RCA_Analysis_Template Worksheet

RCA Analysis records store basic information about a Root Cause Analysis created to track and analyze causes of Asset failures.
Field CaptionField IDData Type (Length)Comments
Analysis DescriptionMI_AN_SHORT_DESCR_CHRCharacter (255)None
Analysis IDMI_AN_ANALY_ID_CHRCharacter (255)A value is required and must be unique.
Analysis TypeMI_AN_ANALY_TYPE_CHRCharacter (50)Enter one of the following values:
  • Mechanical
  • Operational
  • Quality
  • Safety
  • Environmental
CommentsMI_RCA_ANALY_COMME_TXTextNone
Cost NumberMI_RCA_ANALY_COST_NBRNumericThe estimated cost of the failure events you are analyzing. By default, the currency is set to $.
End DateMI_RCA_ANALY_END_DATE_DTDateEnter a value in the following format based on your local time zone: YYYY-MM-DD HH:mm:ss (for example, 2015-01-31 17:30:00).

The date specified in the End Date field must be greater than the date specified in the Start Date field.

Event NarrationMI_RCA_ANALY_EVENT_NARRA_TXTextInformation about the equipment failure
Frequency NumberMI_RCA_ANALY_FREQU_NBRNumericNone
RCA Analysis KeyRCA_ANALYSIS_KEYNumericA value is required and must be unique.
Start dateMI_RCA_ANALY_START_DATE_DTDateEnter a value in the following format dependent on your local time zone: YYYY-MM-DD HH:mm:ss (for example, 2015-01-31 17:30:00).

RCA Event Worksheet

RCA Event records store basic information about a failure event.
Field CaptionField IDData Type (Length)Comments
Event End DateMI_EVENT_END_DTDateIf the Root Cause Analysis was created from a Production Event, this field will be populated automatically with the value in the End Date field of that Production Event. Otherwise, you can define this value manually when you create the RCA Event. The date specified in the End Date field must be greater than the date specified in the Start Date field.
Event LabelMI_RCA_EVENT_LABEL_CHRCharacter (255)If the RCA was created from a Production Event, this field will be populated automatically with the value in the Headline field of that Production Event. Otherwise, you can define this value manually when you create the RCA Event.

This field is required.

Event Long DescriptionMI_EVENT_LNG_DSC_TXTextIf the RCA was created from a Production Event, this field will be populated automatically with the value in the Description field of that Production Event. Otherwise, you can define this value manually when you create the RCA Event.
Event Start DateMI_EVENT_STRT_DTDateIf the RCA was created from a Production Event, this field will be populated automatically with the value in the Start Date field of that Production Event. Otherwise, you can define this value manually when you create the RCA Event.
Event X Position NumberMI_RCA_EVENT_XPOSI_NBRNumericThe RCA Event Node is placed in the diagram at a predefined position, where the X Position Number is 350. A different value can be entered, but 350 is recommended.
Event Y Position NumberMI_RCA_EVENT_YPOSI_NBRNumericThe RCA Event Node is placed in the diagram at a predefined position, where the Y Position Number is 30. A different value can be entered, but 30 is recommended.
RCA Event KeyRCA_EVENT_KEYNumericThis field is required and must be unique.
RCA Template KeyRCA_TEMPLATE_KEYNumericThis field is required and must match the template key provided in the RCA_Analysis_Template worksheet.

RCA Failure Mode Worksheet

RCA Failure Mode records are possible causes associated with failure events.
Field CaptionField IDData Type (Length)Comments
Failure Mode DescriptionMI_RCA_FAILU_MODE_DESCR_TXTextThe value of this field is a detailed description of the failure mode.
Failure Mode LabelMI_RCA_FAILU_MODE_LABEL_CHRCharacter (255)The name of the failure mode that you want to appear on the Logic Tree.
RCA Failure Mode KeyRCA_FAILU_MODE_KEYNumericThis field must contain a unique value that identifies a RCA Failure Mode.

This field is required.

RCA Template KeyRCA_TEMPLATE_KEYNumericThis field is required and must match the template key provided in the RCA_Analysis_Template worksheet.

RCA Logic Gate Worksheet

RCA Logic Gate records define connections between logic nodes.
Field CaptionField IDData Type (Length)Comments
Logic Gate TypeMI_RCA_LOGIC_GATE_GATE_TYPE_CHCharacter (50)Enter one of the following values:
  • and
  • or
This field is required.
Long DescriptionMI_RCA_LOGIC_GATE_LONG_DESCR_TTextThe value of this field is a detailed description of the logic gate.
RCA Logic Gate KeyRCA_LOGICGATE_KEYNumericThis field is required and must be unique.
RCA Template KeyRCA_TEMPLATE_KEYNumericThis field is required and must match the template key provided in the RCA_Analysis_Template worksheet.
Short DescriptionMI_RCA_LOGIC_GATE_SHORT_DESCR_CHRCharacter (255)None

RCA Hypothesis Worksheet

RCA Hypothesis records store basic information about the root cause of a failure event.
Field CaptionField IDData Type (Length)Comments
Confidence Factor NumberMI_RCA_HYPOT_CONFI_FACTO_NBRNumericEnter one of the following values:
  • Not True (0)
  • Somewhat true (1)
  • Possibly
  • True (2)
  • Likely (3)
  • Highly Likely (4)
  • True (5)
If you select a value in this field, the value that you select will appear in brackets to the right of the hypothesis name in the Logic Tree.
DescriptionMI_RCA_HYPOT_DESCR_TXTextThe value of this field is a detailed description of the hypothesis.
Hypothesis StateMI_RCA_HYPOT_STATE_CHRCharacter (255)You can choose from the following states:
  • Hypothesis
  • Hypothesis True
  • Hypothesis Not True
  • Cause Human
  • Cause Latent
  • Cause Physical
This field is set to Hypothesis by default.
LabelMI_RCA_HYPOT_LABEL_CHRCharacter (255)The value of this field is a description of the hypothesis as you want it to appear on the Logic Tree.
RCA Hypothesis KeyRCA_HYPOTHESIS_KEYNumericThis field is required and must be unique.
RCA Template KeyRCA_TEMPLATE_KEYNumericThis field is required and must match the template key provided in the RCA_Analysis_Template worksheet.

RCA Diagram Relationship Worksheet

RCA Diagram Relationship records display the parent-child relationship of the RCA families in Logic Tree diagrams.
Field CaptionField IDData Type (Length)Comments
RCA Template KeyRCA_TEMPLATE_KEYNumericThis field is required and must match the template key provided in the RCA_Analysis_Template worksheet.
Parent Node KeyPARENT_NODE_KEYNumericThe value of this field is the node key of the parent node. The parent node key is blank only when the parent-child relationship is created by an RCA Event.
Child Node KeyCHILD_NODE_KEYNumericThis field is required and must be unique.
Parent Node TypePARENT_NODE_TYPECharacter (50)This field is required.
Child Node TypeCHILD_NODE_TYPECharacter (50)This field is required.

About the RCA Data Loader Load Verification

After a successful data load, you can navigate to the RCA Overview page and view any of the imported workbooks to view the details and logic tree associated with the workbook and to import workbook content into an analysis.

A successful import can also be defined as an event where partial data on a worksheet is loaded into APM, and where you provide appropriate messaging that enables you to identify and correct issues resulting from the import.