General Reference | On-Premises APM

FMEA Data Model

The following diagram shows how the families used in FMEA are related to one another.

Note: In the diagram, boxes represent entity families and arrows represent relationship families that are configured in the baseline database. You can determine the direction of each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

In the preceding diagram:

The RCM FMEA Asset box represents a single RCM FMEA Asset record within an analysis. The RCM FMEA Analysis record can be linked to multiple RCM FMEA Asset records, each of which can optionally be linked to an Equipment or Functional Location record.
The Equipment or Functional Location box represents the Equipment or Functional Location family for which the Is RCM FMEA Asset, Has Recommendations, and Has Tasks have been defined between that family and the specified predecessor or successor.
When an RCM FMEA Recommendation record is created for the analysis, the Recommendation record is linked to the Equipment or Functional Location record to which the RCM FMEA Asset record is linked.
When an RCM FMEA Recommendation record is promoted to an Action record, the Action record will be linked to a Proposed Strategy record and associated with the Equipment or Functional Location record. For details, see the ASM help.

In addition to the families included in the preceding image, the following families are used by the Decision Logic Builder in FMEA:

Decision Tree Consequence
Decision Tree Response
Decision Tree Structure

Within the baseline APM family hierarchy, these families are subfamilies of the APM Reference Tables family. Baseline records are provided in each of these families to support the Decision Logic Builder functionality.

Entity and Relationship Families used in FMEA

The following table provides a summary of the entity families and relationship families that are used to develop an FMEA Analysis.


Records in this entity family:	...Can be linked to records in this entity family:	...Through a relationship definition on this relationship family:
RCM FMEA Analysis	RCM FMEA Asset	Has RCM FMEA Asset
RCM FMEA Asset	RCM FMEA Failure Mode	Has RCM FMEA Failure Mode
RCM FMEA Failure Effect	RCM FMEA Recommendation	Has RCM FMEA Recommendation
RCM FMEA Failure Mode	RCM FMEA Failure Effect	Has RCM FMEA Failure Effect

The following families and relationships are also used by FMEA but not within the analysis itself.


Records in this entity family:	...Can be linked to records in this entity family:	...Through this relationship:	Purpose
RCM FMEA Analysis	Human Resource	Has RCM FMEA Team Member	Facilitates the construction of the RCM Analysis Team Members list. Through this relationship, Human Resource records are linked directly to the RCM FMEA Analysis record.
RCM FMEA Analysis	RCM FMEA Task	Has Tasks	Allows Task records generated from Recommendation records to be linked to the RCM FMEA Analysis record for which the recommendation was created. Note that in the current version of APM, RCM FMEA Task records cannot be created from RCM FMEA Recommendation records. Instead, RCM FMEA Recommendation records can be used to create Action records in ASM. This relationship still exists, however, to support legacy RCM FMEA Task records.
RCM FMEA Analysis	RCM FMEA Template	Has Templates	Facilitates the creation of FMEA Templates.
RCM FMEA Asset	Asset Strategy	Has Strategy	Facilitates the promotion of RCM FMEA Asset records to Asset Strategy records via Recommendation Management. This link is established when an RCM FMEA Analysis is linked to a physical or "virtual" piece of equipment or location for which you have defined Recommendation records.
RCM FMEA Asset	Asset Strategy Template	Has Strategy	Facilitates the promotion of RCM FMEA Asset records to Asset Strategy Template records via Recommendation Management. This link is established when an RCM FMEA Analysis is linked to a "virtual" piece of equipment or location for which you have defined Recommendation records.
RCM FMEA Asset	RCM FMEA Task	Has Tasks	Allows RCM FMEA Asset records to be linked to RCM FMEA Task records. This link is established only when a Task record is generated from a recommendation where the related RCM FMEA Asset record (i.e., the RCM FMEA Asset record that is linked to the RCM FMEA Analysis record) is not linked to an Equipment or Functional Location record. Note that in the current version APM, RCM FMEA Task records cannot be created from RCM FMEA Recommendation records. Instead, RCM FMEA Recommendation records can be used to create Action records in ASM. This relationship still exists, however, to support legacy RCM FMEA Task records.
RCM FMEA Asset	RCM FMEA Template	Has Templates	Facilitates the creation of FMEA Templates.
RCM FMEA Asset	Task History	Has Task History	Facilitates the rejection of RCM FMEA Task records that are linked to RCM FMEA Asset records. When you reject an RCM FMEA Task record, a Task History record is created and linked to the RCM FMEA Asset record through the Has Task History relationship.
RCM FMEA Failure Effect	RCM FMEA Template	Has Templates	Facilitates the creation of FMEA Templates.
RCM FMEA Failure Mode	RCM FMEA Template	Has Templates	Facilitates the creation of FMEA Templates.
RCM FMEA Recommendation	Mitigates Risk	Risk Assessment	Allows you to determine how a recommendation mitigates a risk.
RCM FMEA Recommendation	RCM FMEA Task	Has Tasks	Allows RCM FMEA Recommendation records to be linked to RCM FMEA Task records that are generated from those recommendations. Note that in the current version of APM, RCM FMEA Task records cannot be created from RCM FMEA Recommendation records. Instead, RCM FMEA Recommendation records can be used to create Action records in ASM. This relationship still exists, however, to support legacy RCM FMEA Task records.
RCM FMEA Recommendation	RCM FMEA Template	Has Templates	Facilitates the creation of FMEA Templates.

FMEA Security Groups

The following table lists the baseline Security Groups available for users within this module, as well as the baseline Roles to which those Security Groups are assigned.

Important: Assigning a Security User to a Role grants that user the privileges associated with all of the Security Groups that are assigned to that Role. To avoid granting a Security User unintended privileges, before assigning a Security User to a Role, be sure to review all of the privileges associated with the Security Groups assigned to that Role. Also, be aware that additional Roles, as well as Security Groups assigned to existing Roles, can be added via Security Manager.


Security Group	Roles
MI ASI Administrator	MI Strategy Admin
MI RCM User	MI Strategy Admin MI Strategy Power MI Strategy User
MI RCM Viewer	MI APM Viewer MI Strategy Admin MI Strategy Power MI Strategy User

The baseline family-level privileges that exist for these Security Groups are summarized in the following table.


Family Caption	MI RCM User	MI RCM Viewer
Entity families
Action	View	View
Asset Criticality Analysis System	View	None
Consequence Definition	View	View
Decision Tree Consequence	View	View
Decision Tree Response	View	View
Decision Tree Structure	View	View
Human Resource	View, Update, Insert, Delete	View
Mitigates Risk	View, Update, Insert, Delete	View
Probability Definition	View	View
Protection Level	View	View
RCM FMEA Analysis	View, Update, Insert, Delete	View
RCM FMEA Asset	View, Update, Insert, Delete	View
RCM Function	View, Update, Insert, Delete	View
RCM Functional Failure	View, Update, Insert, Delete	View
RCM FMEA Failure Mode	View, Update, Insert, Delete	View
RCM FMEA Failure Effect	View, Update, Insert, Delete	View
RCM FMEA Recommendation	View, Update, Insert, Delete	View
RCM FMEA Template	View, Update, Insert, Delete	View
RCM FMEA Task	View, Update, Insert, Delete	View
Reference Documents	View, Update, Insert, Delete	View
Risk Assessment	View, Update, Insert, Delete	View
Risk Category	View	View
Risk Matrix	View	View
Risk Rank	View, Update, Insert, Delete	View
Risk Threshold	View	View
Site Reference	View	View
Task History Note: The Task History relationship family is inactive in the baseline APM database.	View, Update, Insert, Delete	View
Relationship Families
Has Associated Recommendation	View	View
Has Consolidated Recommendations	View	View
Has Driving Recommendation	View	View
Has RCM FMEA Team Member	View, Update, Insert, Delete	View
Has RCM FMEA Analysis	View, Insert, Delete	None
Has RCM FMEA Asset	View, Update, Insert, Delete	View
Has RCM Function	View, Update, Insert, Delete	View
Has RCM Functional Failure	View, Update, Insert, Delete	View
Has RCM FMEA Failure Mode	View, Update, Insert, Delete	View
Has RCM FMEA Failure Effect	View, Update, Insert, Delete	View
Has RCM FMEA Recommendation	View, Update, Insert, Delete	View
Has Reference Values	View	View
Has Recommendations	View, Update, Insert, Delete	View
Has Reference Documents	View, Update, Insert, Delete	View
Has Risk	View	None
Has Risk Category	View, Update, Insert, Delete	View
Has Site Reference	View	View
Has Superseded Recommendations	View	View
Has Task History Note: The Has Task History relationship family is inactive in the baseline APM database.	View, Update, Insert, Delete	View
Has Tasks	View, Update, Insert, Delete	View
Has Templates	View, Update, Insert, Delete	View
Is Based on RCM FMEA Failure Effect	View	View
Is RCM FMEA Asset	View, Update, Insert, Delete	View

With these privileges, any user who is a member of the MI RCM User Security Group will have access to ALL records involved in FMEA Analyses. In addition to these baseline privileges, which you can grant by assigning users to the MI RCM User Security Group, you will need to grant FMEA users permission to the Equipment or Functional Location family if it is related to the RCM FMEA Asset family through the Is RCM FMEA Asset relationship.

Note: You may also want to grant some users permission to modify the items in the following Catalog folders: \\Public\Meridium\Modules\RCM.

The current page on your desktop (create shortcut), in an email message, or on a Home Page.
Help: Displays the context-sensitive Help topic for the FMEA Team Members page for FMEA Templates.

FMEA System Code Tables

The following System Code Table is used by FMEA.


Table ID	Table Description	Function
SC_RECOM_RESOURCE	Recommended Resource	Use to populate the Recommended Resource list in RCM FMEA Recommendation records.

FMEA URLs

There are two URL routes associated with FMEA: fmea/overview and strategy/fmea. The following table describes the various paths that build on the routes, and the elements that you can specify for each.


Element	Description	Accepted Value(s)	Notes
fmea/overview: Displays the FMEA Overview page. strategy/fmea/analysis/<EntityKey>: Displays a specific analysis based on the entity key.
<EntityKey>	Specifies the analysis that you want to access.	Any numeric Entity Key that corresponds to an existing analysis.	Displays the specified analysis in a new tab.
strategy/fmea/template/<EntityKey>: Displays a specific template based on the entity key.
<EntityKey>	Specifies the template that you want to access.	Any numeric Entity Key that corresponds to an existing template.	Displays the specified template in a new tab.

Example URLs


Example URL	Destination
fmea/overview	The FMEA Overview page.
strategy/fmea/analysis/64251758233	The FMEA analysis record with Entity Key 64251758233.
strategy/fmea/template/64251549394	The FMEA template record with Entity Key 64251549394.

About the FMEA Data Structure

Within the FMEA module, families are used to represent the various components of an FMEA Analysis. APM leverages its fundamental entity and relationship family infrastructure to store data related to an FMEA Analysis.

Each FMEA Analysis is represented at the root level by an RCM FMEA Analysis family record. FMEA Analyses use the same root analysis family, and they are distinguished from RCM Analyses via the Analysis Type field in the RCM FMEA Analysis record. The Analysis Type can be either RCM or FMEA. For an RCM FMEA Analysis that will be used for an FMEA Analysis, the Analysis Type is FMEA.

Note: Because both RCM and FMEA Analysis records belong to the same family, a query on the RCM FMEA Analysis family will return results that include all analyses of any type. To limit your results to include only one analysis type, you must include the Analysis Type field in your query and define criteria to filter on either RCM or FMEA.

For an FMEA Analysis (a record in which the Analysis Type is FMEA), the RCM FMEA Analysis record can be linked to RCM FMEA Asset records through the Has RCM FMEA Asset relationship. RCM FMEA Asset records can, in turn, be linked to RCM FMEA Failure Mode records through the Has RCM FMEA Failure Mode relationship, and so on, for all components of the analysis. Together, the root RCM FMEA Analysis record and all the records that are linked to it, either directly or indirectly, make up the FMEA Analysis.

Failure Finding Activity in FMEA Recommended Actions

When you define an FMEA recommendation and specify the Action Type as Failure Finding, you can use the Failure Finding Activity cells to calculate the failure finding task interval (FFI).

The following equation is used to calculate FFI:

FFI = MTIVE x [(n + 1)(MTED)/MMF]1/n

Note that the information used for the FFI calculation is based upon the concepts in SAE Standard JA1012, "A Guide to the Reliability-Centered Maintenance (RCM) Standard." The process and terminology used in the FFI calculation are described in more detail in this standards document. To use the Failure Finding Activity cells effectively, you will need to be familiar with this standard.

In addition, the FFI calculation is based upon information in the book "Reliability-Centered Maintenance" by John Moubray.

The following table describes the Failure Finding Activity cells in the APM Framework.


Cell	Description
MMF	Stores the mean time between multiple failures. For example, a 1 in 1,000,000 probability of a multiple failure in one year implies a mean time between failures of 1,000,000 years. The probability of multiple failures occurring in any one year is 1/MMF.
MTIVE	Stores the mean time between failures of the protective device.
MTED	Stores the mean time between failures of the protected function. For example, if the demand rate of the protected function is once in 200 years, this equals a probability of failure for the protected function of 1 in 200 in any one year, or a mean time between failures of the protected function of 200 years. The probability of failure of the protected function in any one year is 1/MTED.
n	The number of protective devices.

FMEA State Configuration

This topic describes the different analysis states in a Failure Modes and Effects Analysis analysis configuration.

By default, the following baseline State Configuration exists for the FMEA Analysis family.

Initial State

The Draft state is the initial state of all new FMEA Analysis records.

Datasheet Configuration

By default, no states and operations will appear on the datasheet when you are viewing an RCM FMEA Analysis record in RCM, FMEA, the Record Manager, or the Bulk Data Form.

Reserved States and Operations

By default, no states or operations displayed in the preceding diagram are reserved. This means that you can remove or modify any of these states or operations. You can also add your own states and operations to the State Configuration.

FMEA Site Filtering

FMEA Analyses

Site filtering is applied to FMEA analysis records by setting the site on the datasheet or by linking an asset with an existing site assignment to a global analysis. If you assign a site to an FMEA analysis by linking an existing asset, then all of the records associated with the analysis inherit the same site. After the site is set for an analysis, you can only link assets with that same site assignment.

FMEA Analysis Templates

When you create a new analysis template, you can use the Site control to set the site for the template, which then gets populated through all of the records associated with an analysis. You can apply any viewable template to any viewable analysis, regardless of the site assignment, as long as the risk matrices match.

Examples

Consider an organization that has two sites, Site X and Site Y, and then consider the following scenarios:

Scenario 1: User assigned to Site X and Site Y applies a template to an analysis

Template A is assigned to Site X. Analysis 1 is assigned to Site Y. The user applies Template A to Analysis 1, even though they have separate site assignments, as long as there are no conflicts between the risk matrices.

Scenario 2: User assigned to Site X and Site Y links an asset to an analysis

Equipment 1 is assigned to Site X and Equipment 2 is assigned to Site Y. Analysis 1 is assigned to Site Y. The user links Equipment 2 to Analysis 1, because they share the same site (Site Y).

The user is unable to link Equipment 1 to Analysis 1, because Equipment 1 would not appear in the list of available assets to link there due to site incompatibility. So, even though this multi-site user can view both Equipment 1 and Equipment 2, they cannot link an equipment to an analysis with an incompatible site assignment.

About Values Mapped from FMEA Analysis to Asset Strategy

When you promote FMEA analysis to an ASM analysis, several fields in the Asset Strategy family are populated with the fields that are mapped from RCM FMEA Analysis family.

The following table lists the field mapped for Risk family:


This field in RCM FMEA Failure Effect and RCM FMEA Failure Mode family:	...populates this field in Risk family
Basis for Assessment	Basis for Assessment
Failure Mode Name,Effect Name	Name
Failure Mode Long Description, Effect Long Description	Description
Failure Mode Name	Failure Mode
Maintainable Item	Maintainable Item
Damage Code	Condition
PF Interval	PF Interval
PF Interval Units	PF Interval Units

The following table lists the field mapped for Action family:


This field in RCM FMEA Recommendation family:	...populates this field in Action family
Recommendation Headline	Name
Recommendation Description	Description
Action Type	Action Type
Interval	Interval
Interval Units	Interval Units
Estimated Cost	Cost
Asset Shutdown Required?	Shutdown Required
Estimated Cost Basis	Cost Basis
Nonrecurring	Nonrecurring
Performance Interval	Performance Interval
Performance Interval Units	Performance Interval Units
Recommended Resource	Recommended Resource
Target Completion Date	Target Completion Date