General Reference

Compliance Queries Folder

Compliance Folder Items

The Catalog folder \\Public\Meridium\Modules\Inspection\Compliance\Queries contains the following items.

Query

Behavior and Usage

Assets with Templates

Displays assets that have a Compliance Strategy Template linked. The entity key of the asset must be used in the query and have the alias ASSET_ENTY_KEY.

Assets without Templates

Displays assets that do not have a Compliance Strategy Template linked.

The following columns in the query must be used, and the aliases must be the following values:


Column	Alias
MI_ENTITY.ENTY_KEY	ASSET_ENTY_KEY
[MI_SUGG_COMP_TEMP].[MI_SUGG_COMP_TEMP_TMP_KEY_N]	TEMP_KEY

Compliance Recommendations by Plan

Displays Compliance Recommendations based on the Inspection Plan.

The following columns in the query must be used, and the aliases must be the following values:


Column	Alias
[MI_INSP_PLAN].ENTY_KEY	ENTY_KEY
[MI_COMP_RECOMM].ENTY_ID	REC_ENTY_ID
[MI_COMP_RECOMM].[MI_RBIRECOM_TASK_TYPE_C]	TASK_TYPE
[MI_COMP_RECOMM].ENTY_KEY	REC_ENTY_KEY
[MI_TASKINSP].[MI_TASK_ID]	TASK_ID
a."SUCC_ENTY_KEY"	Linked Actions

Important: Public\Meridium\Modules\Inspection\Compliance\Queries\Compliance Superseded Recommendation Counts is a subquery and should not be removed from the parent query. In this subquery, the SUCC_ENTY_KEY column is required, and the alias should not be modified.

Compliance Recommendations to Supersede

Displays Compliance Recommendations for the given entity keys. This query is used for selecting the master Recommended Action while superseding Compliance Recommendations.

Important: The [MI_COMP_RECOMM].ENTY_KEY column should not be removed, and the alias, REC_ENTY_KEY, should not be modified.

Compliance Superseded Recommendations

Displays Compliance Recommendations that are in the Superseded state and are linked to the given entity.

Important: The [MI_COMP_RECOMM].ENTY_KEY column should not be removed, and the alias, REC_ENTY_KEY, should not be modified.

Compliance Template Assets

Displays the Compliance Strategy Templates for the given compliance category. This query populates the Assets section in a Compliance Strategy Template.

Important:

The ASSET_ENTY_KEY should not be modified or deleted.
If you are using assets that from families other than Equipment or Functional Location, you must add the family to the query using a union.

Compliance Templates by Category

Displays the assets associated with the given Compliance Strategy Template.

Important: The [MI_COMP_STRAT_TEMP].ENTY_KEY column should not be removed, and the alias, ENTY_KEY, should not be modified. In the WHERE criteria, the ID of the parameter must be category.

Inspection Tasks for Asset

Displays Inspection Tasks for an asset. In the WHERE criteria, the ID of the parameter must be ASSET_ENTY_KEY.

Compliance Permissions

The following security privileges have been assigned to the \\Public\Meridium\Modules\Inspection\Compliance\ folder.

Role	Permissions
MI Inspection	View Edit Create Delete
MI Inspection Viewer	View
MI RBI Administrator	View
MI RBI Analyst	View
MI Thickness Monitoring Administrator	View
MI Thickness Monitoring Inspector	View
MI Thickness Monitoring User	View

Compliance Management URLs

There is one URL route associated with Compliance Management: cm. The following table describes the various paths that build on the route and the elements that you can specify for each.


Element	Description	Accepted Value(s)	Notes
cm/overview: Accesses the Compliance Management Overview page.
cm/asset/<assetKey>: Accesses the Inspection Plan for the specified asset.
<assetKey>	Specifies the entity key of the asset record which you want to view.	Any asset key that is associated with an asset in the Asset Hierarchy	You should use the asset key of an asset that has an Inspection Plan created. If you select an asset that does not have an Inspection Plan, a warning message appears.

URLs


Example URL	Destination
cm/overview	The Compliance Management Overview page.
cm/asset/3290820029	The Inspection Plan for the selected asset.

Compliance Strategies URLs

The following URLs in Inspection Management allow you to access Compliance Strategies administrative options.


Element	Description	Accepted Value(s)	Notes
im-admin-preferences/compliance-configuration: Accesses the Compliance Strategies workspace.
im-admin-preferences/compliance-configuration/<templateKey>: Accesses a Compliance Strategy Template.
<templateKey>	Specifies the entity key of the Compliance Strategy Template that you want to view.	The entity key of any Compliance Strategy Template.	None.

Compliance Management System Code Tables

The following table lists the System Code Tables that are used by Compliance Management.


Table ID	Table Description	Function
INSM	Inspection Interval Types	Used to populate the Desired Interval Basis list in Inspection Task records.
MI DEGRADATION MECHANISM TYPES	Degradation Mechanism Types	Used to populate the Degradation Mechanism list in Inspection Plan records.

Compliance Management State Management

The following state changes can be applied to Compliance Recommendations and Inspection Plans based on user Security Roles.

The diagram below shows the workflow of the baseline State Management process as it applies to Compliance Recommendations.

The diagram below shows the workflow of the baseline State Management process as it applies to Inspection Plans.

Details

The Proposed state is the initial state of all Compliance Recommendations.
The Proposed state is the initial state of all Inspection Plans.
When you change the state of an Inspection Plan from Approved to Modified, an Inspection Plan Revision History record is created.
Operations in Compliance Management change the state of Compliance Recommendations or Inspection Plans. Users must have the appropriate security roles to execute these operations.

Reserved States and Operations for Compliance Recommendations

The following tables indicate whether the baseline states and operations are reserved. You cannot remove or modify reserved states or operations.


State Caption	Reserved State	Security Role
Implemented	Yes	MI Compliance Analyst MI Compliance Approver
Not Required	Yes	MI Compliance Analyst MI Compliance Approver
Proposed	No	MI Compliance Analyst MI Compliance Approver
Superseded	Yes	MI Compliance Analyst MI Compliance Approver


Operations	Reserved Operation	Predecessor States	Successor State
Implement	Yes	Proposed	Implemented
Make Proposed	No	Not Required	Proposed
Mark Not Required	Yes	Proposed	Not Required
Supersede	Yes	Proposed	Supersede
Unimplement	Yes	Implemented	Proposed

Reserved States and Operations for Inspection Plans

The following tables indicate whether the baseline states and operations are reserved. You cannot remove or modify reserved states or operations.


State Caption	Reserved State	Security Roles
Approved	No	MI Compliance Approver
Modified	Yes	MI Compliance Analyst MI Compliance Approver
Proposed	No	MI Compliance Analyst MI Compliance Approver


Operation ID	Reserved Operation	Predecessor	Successor
MI_APPROVE	No	Proposed	Approved
MI_APPV_MODIFIED	No	Modified	Approved
MI_MODIFY	Yes	Approved	Modified

Compliance Recommendation and Inspection Task Mappings

When you implement a Compliance Recommendation, you can create new Inspection Tasks or link existing Inspection Tasks to the Compliance Recommendation. Values from the Compliance Recommendation fields populate fields in the Inspection Task.

The following tables list the Inspection Task fields that are populated automatically from these sources.

Table 1. Link Existing Inspection Tasks to Compliance Recommendations
This Inspection Task field:	...is populated with:	...from the following record:
Desired Interval	The value in the Recommended Interval Scope field. Note: This field is only populated with the value of the Recommended Interval Scope field if the value in the Override Interval field is False.	Compliance Recommendation
Desired Interval Basis	Compliance Recommendation Note: This field is only populated with the value of the Recommended Interval Scope field if the value in the Override Interval field is False.	Compliance Recommendation
Task Details	The value in the Recommended Inspection Scope field.	Compliance Recommendation
Task Type	The value in the Task Type field.	Compliance Recommendation

Table 2. Link New Tasks to Compliance Recommendations
This Inspection Task field:	...is populated with:	...from the following record:
Desired Interval	The value in the Recommended Interval Scope.	Compliance Recommendation
Desired Interval Basis	Compliance Recommendation	Compliance Recommendation
Override Interval	False	Compliance Recommendation
Task Details	The value in the Recommended Inspection Scope field.	Compliance Recommendation
Task ID	The values in the Damage Mechanism and Task Type fields in the following format: <Damage Mechanism><Task Type>.	Compliance Recommendation
Task Type	The value from the Task Type field.	Compliance Recommendation