Automation Rules
About Automation Rules
Reliability Distribution and Reliability Growth Analyses can be generated interactively or through Reliability Automation Rules. These rules can generate multiple Reliability Analyses for an entire hierarchy of equipment and locations that have related events or for a list of equipment that are returned by a query.
Using Reliability Automation Rules, you can analyze an entire family or elements of several families in a single step. Based on the parameters that you define for the automation rule query, the system will automatically generate the analysis calculations and generate the appropriate reliability analyses. The calculations can be based on an entire selected family, or on the results of a query, which could contain members of multiple families.
About Creating Queries for Use with the Automation Rule Builder
In the Reliability Automation Rule Builder window, you can select an existing query to provide the data on which auto-generated Reliability Analyses will be built for a query-based Automation Rule. Before you can use the Reliability Automation Rule Builder window, one or more appropriate queries must be defined.
Details
Automation Rule queries must contain:
-
All of the fields needed for mapping to the selected analysis type (Reliability Distribution, Reliability Growth). For all analysis types, the following fields should be selected:
- Asset ID (required).
- Asset Installation Date (optional).
- Failure Date (required).
- Downtime (optional).
- The fields that will be used for grouping populations of events (including system fields such as Family ID and Family Key and the entity family caption)
- Filtering criteria.
We recommend that you use a query that contains the metadata information in the Asset ID and Failure Date fields (which are required fields) and that these two fields are defined in two separate entity families. This precludes the use of Group By queries, complex (non metadata-based) queries in the SQL Editor, and system fields or calculated fields for Asset ID and Failure Date information.
The master query cannot contain parameters. The master query should be stored in a public directory in the Catalog and must not be deleted. We recommend that you store this query in the APM Catalog in the following folder: \\Public\Meridium\Modules\ReliabilityManager.
If you require additional fields for mapping or population grouping in the Reliability Automation Rule, you must change the master query. The master query should be accessible to members of the MI Reliability Administrators Security Group who will be working with Reliability Automation Rules. When the Reliability Automation Rule is executed to generate the analyses, sub-queries will be created using the master query as the source. If the master query is deleted, the sub-queries will cease to operate.
Access an Automation Rule
Procedure
Create an Automation Rule Based on a Query
Before You Begin
- To create a Reliability Automation Rule based on a query, the query must exist in the Catalog.
Procedure
Create an Automation Rule Based on Asset-Event Data Structure
About This Task
This topic describes how to create an Automation Rule based on Asset-Event Data structure. You can also create an Automation Rule Based on a Query.
Procedure
Modify an Automation Rule
Procedure
Merge Analyses
About This Task
If two or more analyses share similar characteristics, you may find it useful to merge them and produce one analysis instead of separate analyses. Also, if an analysis does not have the minimum number of failure events required to create an analysis, you can merge it with another analysis.
Procedure
Unmerge Analyses
Procedure
Execute an Automation Rule
About This Task
When a rule is executed, only the potential analyses that contain the minimum number of failure points for an analysis will be created or updated. The following number of failure points is required for each analysis that can be created from a Reliability Automation Rule.
- Reliability Growth Analysis: 3 failure points
- Reliability Distribution Analysis: 2 failure points
If the potential analysis does not contain the corresponding number of failures or more, when the rule is executed, the analysis will not be created.