Inspection Management Upgrade

Upgrade or Update Inspection Management to V5.1.4.0.0

The following table provides you the reference to procedures to upgrade from an earlier APM version to the latest version.

Upgrade from Upgrade to Procedure
V5.1.0 - V5.1.2.xV5.1.4.0.0
V5.0.xV5.1.4.0.0
V4.6.2 or a later V4.6.x releaseV5.1.4.0.0
  1. Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0
  2. Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0
V4.6.1.x or earlierV5.1.4.0.0
  1. Upgrade from any version V4.6.1.x or earlier to V4.6.2.0.0 or a later V4.6.x release
  2. Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0
  3. Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0
Note: For more information on upgrading to APM V4.6.2.0.0 or a later V4.6.x release, refer to the Upgrade documentation for the corresponding version.

Upgrade from any version V5.1.0.0.0 through V5.1.2.1.0

This module will be upgraded to V5.1.4.0.0 automatically when you upgrade the components in the basic APM system architecture. No additional steps are required.

Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0

The following tables outline the steps that you must complete to upgrade this module to V5.1.4.0.0. These instructions assume that you have completed the steps for upgrading the basic APM system architecture.

These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.

StepTaskNotes
1Clear the Offline check box for Related Families of the Checklist Inspection Template family. This step is required only if you have previously modified the Related Family settings for the Checklist Inspection Template family.

This step will be completed automatically when you upgrade the components in the basic APM architecture.

2Revert PRD Pop Test Checklist Datasheet to Baseline.This step is required only if you have modified the PRD Pop Test Checklist datasheet.
3Revert the following query to baseline to include the Inspection family in the All Tasks view of Integrity Mobile:
  • Public/Meridium/Modules/Inspection/Overview/Queries folder.
    • All Tasks for Date Range
This step is required only if you have previously modified the query.
4Revert the following query to baseline to coalesce Functional Location ID into the Asset ID field within the My Inspections view of Integrity Mobile:
  • Public/Meridium/Modules/Inspection/Overview/Queries folder.
    • Users Open Inspections (Including Team Members)
This step is required only if you have previously modified the query.

Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0

The following tables outline the steps that you must complete to upgrade this module to V5.1.4.0.0. These instructions assume that you have completed the steps for upgrading the basic APM system architecture.

These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.

Note: If you are using Inspection Field Data Collection for Offline Inspections, please follow the upgrade steps to install the latest app on mobile devices used for Inspection Field Data Collection.

After you upgrade:

A new Human Resource role, Contract Inspector (ID: CONTRACT INSPECTOR) is now available in MI_RESOURCE_ROLE system code table. This is to facilitate the enhancement where a Contract Inspector can now update the Status field in Inspection records to Pending Approval without being the user defined in the Inspection Report Owner field if they are also a Team Member in the associated Inspection record.

StepTaskNotes
1Update entity key parameters from :n to :k for the following catalog queries:
  • Public/Meridium/Modules/Inspection/Overview Queries folder.
    • All Inspections for Unit
    • All Tasks for Asset
    • Returns all Inspection Tasks between the provided date range
    • All Health Evaluations for Asset
  • Public/Meridium/Modules/Inspection/Compliance/Queries folder.
    • Recommendations to Supersede on Inspection Plan
    • Inspection Tasks Available to Implement
    • Inspection Tasks for Asset
    • Recommended Actions by Selected Plans
    • Compliance Template Assets
  • Public/Meridium/Modules/Inspection/Report Queries folder.
    • MI_INSPHIST_ASSETDTL
    • Inspection History - General Findings
    • Inspection History Details
    • Inspection Recommendation History
    • Inspection History – Thickness Monitoring Summary
    • All Inspection Tasks in a Work Pack
    • MI Reference Document
    • MI_FIND_GEN
    • MI_FIND_CHECK
    • MI_INSPPSUB
    • MI_RECINSP
    • MI_TEAMINSP
    • MI Asset Corrosion Analysis

This step is required only if you have previously modified the queries.

This step will be completed automatically when you upgrade the components in the basic APM system architecture.

2Revert the following queries to baseline to remove the references to the MI_ENTITIES family that has been deprecated:
  • Public/Meridium/Modules/Inspection/Overview Queries folder.
    • All Inspections for Unit
    • All Inspections for Unit and Below
    • All Inspections for Asset
    • All Inspections for Asset with Inspection Grouping
    • All Tasks for Asset
    • All Tasks for this Unit
    • All Tasks for Unit
    • My Open Inspections
    • Open Inspection Recommendations for Unit (State Management)
    • Open Inspection Recommendations for Unit (Status)
    • Open Inspections for Unit
    • Open Recommendations for Asset (State Management)
    • Open Recommendations for Asset (Status)
    • Overdue Inspection Recommendations for Unit (State Management)
    • Overdue Inspection Recommendations for Unit (Status)
    • Recommendations Due for Implementation for Unit (Status)
    • Recommendations Due for Implementation for Unit (State Management)
    • Overdue Tasks for Unit
  • Public/Meridium/Modules/Inspection/Report Queries folder.
    • Inspection History – Thickness Monitoring Summary
    • Inspection History Details
    • Inspection Recommendation History
    • MI Asset Corrosion Analysis
    • MI_INSPBSUB
    • MI_INSPPSUB
  • Public/Meridium/Modules/Inspection/Resource Queries folder.
    • All Human Resources
  • Public/Meridium/Modules/Inspection/Review Queries folder.
    • All Inspections for Reviewer

This step is required only if you have previously modified the queries.

This step will be completed automatically when you upgrade the components in the basic APM system architecture.

3Revert the following queries to baseline to support notifications generation functionality in SAP from APM:
  • Public/Meridium/Modules/SAP Integration Interfaces/Queries folder.
    • Get Tasks for Work Order Generation

This step is required only if you have previously modified the queries.

This step will be completed automatically when you upgrade the components in the basic APM system architecture.

4Configure Inspection Management ActiveMQ settings for MIExecution Service.This step is optional. You can perform this step if you want to modify the default retries or concurrency settings.
5Ensure that the Meridium MIExecution Service is installed and running.If the basic APM system architecture is already installed, the Meridium MIExecution Service is automatically installed, and the service runs automatically.
6If you have previously used the following queries and want to continue to use them, you must export the queries from the previous version and import them into the current version. They are no longer used in the application and have been removed.
Folder: Public/Meridium/Modules/Inspection/Document Queries
  • All Equipment That Can Have API 510 External Checklist Inspections
  • All Equipment That Can Have API 510 Internal Checklist Inspections
  • All Equipment That Can Have API 510 Internal Exchanger Checklist Inspections
  • All Equipment That Can Have API 570 External Checklist Inspections
  • All Equipment That Can Have API 653 External Checklist Inspections
  • All Equipment That Can Have API 653 Internal Checklist Inspections
  • All Equipment That Can Have Bundle Inspections
  • All Equipment That Can Have External PRD Checklist Inspections
  • All Equipment That Can Have Full Inspections
  • All Equipment That Can Have General Inspections
  • All Equipment That Can Have Inspections
  • All Equipment That Can Have Pressure Test Inspections
  • All Inspection Records
  • All Inspection Records for selected equipment
  • Get Inspections by Asset Key
  • Get Inspections by Function Location Key
Folder: Public/Meridium/Modules/Inspection/Work Pack Queries
  • All Work Packs
  • Number of Inspections in a Work Pack
  • Status of All Bundle Inspections
  • Status of All Full Inspections
  • Status of All General Inspection
  • Status of All Inspections
  • Status of All Pressure Test Inspections
  • Task Status Chart Query
  • Union of all Inspection Status
Folder: Public/Meridium/Modules/Inspection/Task Queries
  • All Equipment That Can Have Tasks
Folder: Public/Meridium/Modules/Inspection/Resources Queries
  • Human Resources with certification
  • Human Resources with roles
Folder: Public/Meridium/Modules/Inspection/Manage Report Queries
  • Bundle Inspection - formatted reports for all equipment
  • Bundle Inspection - formatted reports with prompt for equipment
  • Checklist Inspections - formatted reports for all equipment
  • Checklist Inspections - formatted reports with prompt for equipment
  • Full Inspection - formatted reports for all equipment
  • Full Inspection - formatted reports with prompt for equipment
  • General Inspection - formatted reports for all equipment
  • General Inspection - formatted reports with prompt for equipment
  • Pressure Test Inspection - formatted reports for all equipment
  • Pressure Test Inspection - formatted reports with prompt for equipment
Folder: Public/Meridium/Modules/Inspection/Conditional Alert Queries
  • All Inspection Alerts
Folder: Public/Meridium/Modules/Inspection/Profile Queries
  • All Equipment than can have an Inspection Profiles
Folder: Public/Meridium/Modules/Inspection/Config Queries
  • Base Summary Query
  • Inspection History Summary Query
  • Published Documents
  • Published Documents by Asset
This step is optional.
7Revert the following queries to baseline to fix the query compilation error:
Folder: Public/Meridium/Modules/Inspection/Compliance/Queries
  • All Inspection Plans for Unit
  • Assets with Templates without Inspection Plans
  • Assets without Templates
  • Compliance Superseded Recommendations
Folder: Public/Meridium/Modules/Inspection/Overview Queries
  • Top-Level Work Packs
Folder: Public/Meridium/Modules/Inspection/Review Queries
  • Bundle Inspections for Review for Current User - Choose State
  • Bundle Inspections for Review - Choose State and Reviewer
  • Bundle Inspections Pending Approval for Current User
  • Full Inspections for Review for Current User - Choose State
  • Full Inspections for Review - Choose State and Reviewer
  • Full Inspections Pending Approval for Current User
  • General Inspections for Review for Current User - Choose State
  • General Inspections for Review - Choose State and Reviewer
  • General Inspections Pending Approval for Current User
  • Pressure Inspections Pending Approval for Current User
  • Pressure Test Inspections for Review for Current User - Choose State
  • Pressure Test Inspections for Review - Choose State and Reviewer

This step is required only if you have previously modified the queries.

8Revert the following Inspection Management queries to baseline:
  • Public\Meridium\Modules\Inspection\Work Pack Queries\All Inspections in a Work Pack
  • Public\Meridium\Modules\Inspection\Review Queries\Open Inspections for Bulk Review
This step is required only if you have previously modified the queries.
9Revert the following Inspection Management queries to baseline as the MI_SM_STATES.SMST_STAT_IND field is deprecated :
  • Public\Meridium\Modules\Inspection\Overview Queries\Open Recommendations for Unit
This step is required only if you have previously modified the queries.
10Map the following Baseline Inspection Document Status to the respective State:
StatusState
DRAFTMI_DRAFT
APPROVEDMI_APPROVED
RE-REFERREDMI_REWORK
PENDING APPROVALMI_PENDING_APPROVAL
AUDITEDMI_AUDITED
This step will be completed automatically, when you upgrade the components in the basic APM system architecture.
Note: Select the Revert to Baseline utility if you have a custom state machine at Inspection parent family and want to use the baseline state. You may want to skip this upgrade if you have custom statuses that you want to convert to a custom state machine. In this scenario, skip the database upgrade, configure your custom state machine, and then use the Map Inspection Status to State upgrade utility available in the Inspection Admin Preferences page. For more details on the steps to follow if you want to skip the baseline upgrade, refer to the KBA 000039706.

If State Management is customized for families under the Inspection parent family (MI_INSP_001), refer to the KBA 000040189 to use the baseline state.

11Revert the following queries to baseline to remove the references to the Status field in Inspection family that has been replaced by State Management fields.
  • Public/Meridium/Modules/Inspection/Overview Queries folder.
    • Open Inspections for Unit
    • My Open Inspections
    • Users Open Inspections (Including Team Members)
    • User's Open Inspections
  • Public/Meridium/Modules/Inspection/Report Queries folder.
    • MI_INSPFULL
    • MI_INSP_GEN
    • MI_INSPPTST
    • MI_INSPBUND
    • Inspection History Details
  • Public/Meridium/Modules/Inspection/ Work Pack Queries folder.
    • All Inspections in a Work Pack
  • Public/Meridium/Modules/Inspection/ Review Queries folder.
    • All Inspections for Reviewer
This step is required only if you have previously modified the queries.

This step will be completed automatically when you upgrade the components in the basic APM system architecture.

12

Execute the Revert to Baseline utility to update the following Datasheets:

Family NameDatasheet Name
Full Inspection
  • Full Visual Inspection
  • Visual Inspection
  • Visual Inspection SAP Integration
  • EU Inspection Report
General Inspection
  • General Inspection - Default
  • General Inspection
  • General Inspection SAP Integration
API 510 External ChecklistAPI 510 External Checklist - Default
API 510 Internal ChecklistAPI 510 Internal Checklist - Default
API 510 Internal Exchanger ChecklistAPI 510 Internal Exchanger Checklist - Default
API 570 External ChecklistAPI 570 External Checklist - Default
API 653 External ChecklistAPI 653 External Checklist - Default
API 653 Internal ChecklistAPI 653 Internal Checklist - Default
Checklist Inspection TemplateChecklist Inspection Template
External PRD ChecklistExternal PRD Checklist
PRD Pop Test ChecklistPRD Pop Test Checklist
ILI ChecklistILI Checklist - Default
Third Party Damage ChecklistThird Party Damage Checklist - Default
Bundle Inspection
  • Bundle Inspection - Default
  • Bundle Inspection
  • Bundle Inspection SAP Integration
Pressure Test Inspection
  • Pressure Test Inspection - Default
  • Pressure Test Inspection
  • Pressure Test Inspection SAP Integration
Bundle Sub-InspectionBundle Sub-Inspection
General FindingFindings

This step is required only if you have modified the following datasheets:

  • Full Visual Inspection
  • Visual Inspection
  • Visual Inspection SAP Integration
  • EU Inspection Report
  • General Inspection - Default
  • General Inspection
  • General Inspection SAP Integration
  • API 510 External Checklist - Default
  • API 510 Internal Checklist - Default
  • API 510 Internal Exchanger Checklist - Default
  • API 570 External Checklist - Default
  • API 653 External Checklist - Default
  • API 653 Internal Checklist - Default
  • Checklist Inspection Template
  • External PRD Checklist
  • PRD Pop Test Checklist
  • ILI Checklist - Default
  • Third Party Damage Checklist - Default
  • Bundle Inspection - Default
  • Bundle Inspection
  • Bundle Inspection SAP Integration
  • Pressure Test Inspection - Default
  • Pressure Test Inspection
  • Pressure Test Inspection SAP Integration
  • Bundle Sub-Inspection
  • Findings
13The users with Baseline Human Resource Roles will be assigned the security Roles based on the following table:
Human Resource RoleSecurity Role
INSPECTORMI Inspector
INSPECTION SUPERVISORMI Inspection Supervisor
CONTRACT INSPECTORMI Contract Inspector
This step will be completed automatically when you upgrade the components in the basic APM system architecture
14Change the following system code tables display format to Description only:
  • MI_FINDING_TYPE
  • MI_ACTION
  • MI_INSPECTION_METHOD_CATEGORY
  • MI_DAMAGE_MECHANISM
  • MI_DAMAGE_MODE
  • MI_INSPECTION_PROFILE_CATEGORY
This step is required only if you have modified the values in the system code tables.
15Revert the following Inspection Management dashboard to baseline as the ALL INSPECTIONS PENDING APPROVAL FOR REVIEWER widget has been removed:
  • Public\Meridium\Modules\Mechanical Integrity\Dashboards\Inspection Overview
This step is required only if you have previously modified the dashboard.
16Clear the Offline check box for Related Families of the Checklist Inspection Template family.This step is required only if you have previously modified the Related Family settings for the Checklist Inspection Template family.

This step will be completed automatically when you upgrade the components in the basic APM architecture.

Remove Offline Option for Related Families of Checklist Inspection Template

About This Task

To load Inspections taken in the Checklist Inspection Template family into the Integrity Mobile app, the Offline option for the configured related families must be disabled.

Procedure

  1. Log in to APM as an Inspection Administrator.
  2. In the module navigation menu, select Admin > Application Settings > Inspection Management.
  3. Select .
  4. Select Event Configurations.
  5. In the Checklist Inspection Template row, select the link in the Related Families column.
  6. For the General Findings, Bundle Sub-Inspection, and Pressure Test Sub-Inspection families, clear the check box in the Offline column.
  7. Select Done.
  8. Select .

Revert Inspection Management Queries to Baseline

This action is required only if you have modified the Inspection Management queries.

About This Task

If you have modified the Inspection Management query, perform the steps to revert the query to baseline.

Procedure

  1. Access the Catalog page.
  2. Navigate to the Public folder for the query that you want to revert.
    The queries are stored in specific sub-folders within the Public/Meridium/Modules/Inspection/ folder.
  3. Select the check box next to the query that you want to revert, and then select .
    The Confirm Delete window appears, asking you to confirm if you want to delete the selected query.
  4. Select OK.
    The selected query is deleted.
  5. Navigate to the Baseline folder for queries.
    The baseline queries are stored in specific sub-folders within the Baseline/Meridium/Modules/Inspection/ folder.
  6. Select the check box next to the query that you want to revert, and then select .
    The Catalog Folder Browser window appears.
  7. Navigate to the folder containing the public query that you deleted in step 3.
  8. Select OK.
    A success message appears indicating that the selected Item has been copied successfully.
  9. Repeat Steps 2-8 for each query that you want to revert to baseline.

Inspection Datasheets - Revert to Baseline

About This Task

The default datasheets on Inspection families supported for Inspection Field Data Collection have been updated to include fields to track download information:
FamilyFamily IDDatasheet Updated (Default)
Full InspectionMI_INSPFULLFull Visual Inspection
General InspectionMI_INSP_GENGeneral Inspection - Default
API 510 External ChecklistMI_API510EXT_CHECKAPI 510 External Checklist - Default
API 510 Internal ChecklistMI_API510INT_CHECKAPI 510 Internal Checklist - Default
API 510 Internal Exchanger ChecklistMI_API510IEX_CHECKAPI 510 Internal Exchanger Checklist - Default
API 570 External ChecklistMI_API570EXT_CHECKAPI 570 External Checklist - Default
API 653 External ChecklistMI_API653EXT_CHECKAPI 653 External Checklist – Default
API 653 Internal ChecklistMI_API653INT_CHECKAPI 653 Internal Checklist - Default
External PRD ChecklistMI_EXTNL_PRD_CHECKExternal PRD Checklist
PRD Pop Test ChecklistMI_PRD_PT_CHECKPRD Pop Test Checklist
Checklist Inspection TemplateMI_GEN_INSP_TMPChecklist Inspection Template
If you have customized the default datasheet for any of these families and want to see the download data for Inspection Field Data Collection must do one of the following:
  • Using Family Management, edit the default datasheet of each family. Add a new section, Download Information with the following fields:
    • Downloaded
    • Last Downloaded By
    • Last Downloaded Date
    • Last Synced Back By
    • Last Synced Date
  • Run Revert to Baseline for each family.
Important: Running this utility overwrites your current datasheet and replaces it with the baseline version. You must be a super user in APM to run the Revert to Baseline utility.

Procedure

  1. Log in to the server where APM is installed.
  2. Navigate to <Installation Directory>\Meridium\Upgrade\DBUpgrade.
  3. Run the RevertToBaselineApp.exe file as administrator.
    The Revert To Baseline Login window appears.

  4. In the Meridium Data Source box, enter the data source name that you want to access.
  5. Enter your login credentials, and then select Next.
    The available families that can be reverted to baseline appear.
  6. Select the Inspection family that you want to update, and then select Revert to Baseline.
    The Various Options For Revert window appears.

  7. Select Datasheets.
    Select the Default Datasheet from the drop-down, and then select Ok.
  8. Repeat steps 6-7 for each Inspection Family.

Update the Query Parameter Type

After the database upgrade for APM, if the entity key fields are of the type string, you must modify the catalog query parameters to use the correct type by performing the following steps.

Procedure

  1. Access the Query page.
  2. Select Browse.
    The Select a query from the catalog window appears.
  3. Navigate to the folder containing the query that you want to update, and select the link for the query.
    The Results workspace appears.
  4. Select the SQL tab.
    The SQL workspace appears, where you can modify the SQL code.
  5. Modify all the entity key numeric parameters to key.
    For example, (? :n) must be updated to (? :k).
  6. Select Save.
    The modified query is saved.

Inspection Recommendation State Management - Revert to Baseline

About This Task

The Inspection Recommendation state management is now available with a new state configuration for the approval workflow. This state configuration allows Inspection Recommendation approval workflow to use the State field, instead of the Status field. For more information about the new state configuration, refer to the Inspection Management State Management topic. If you are using a customized state configuration for the approval workflow and want to use the functionality of the new state management without impacting the current approval workflow, you must map the existing states to the new states using the Revert to Baseline utility. You can run this utility in any of the following conditions:
  • You are using customized state configuration for the approval workflow and want to use the new state configuration.
  • You have a customized state configuration for the approval workflow, but using the recommendation status for the approval workflow, and want to use the new state configuration.
Important: Running this utility overwrites your current state configuration. After you transition to the new state configuration, you cannot revert to the old state configuration.

Before You Begin

  • You must be a super user in APM.
  • The State Configuration for Inspection Recommendation must be enabled.

Procedure

  1. Log in to the server where APM is installed.
  2. Navigate to <Installation Directory>\Meridium\Upgrade\DBUpgrade.
  3. Run the RevertToBaselineApp.exe file as administrator.
    The Revert To Baseline Login window appears.

  4. In the Meridium Data Source box, enter the data source name that you want to access.
  5. Enter your login credentials, and then select Next.
    The available families that can be reverted to baseline appear.

  6. Select the Inspection Recommendation family, and then select Revert to Baseline.
    The Various Options For Revert window appears.

  7. Select State Management, and then select Ok.
    The State Management Mapper window appears.

  8. In the Entity Families pane, select Inspection Recommendation.
    The State Management Baseline Mapping table appears and contains the following columns:
    • Custom Source: Contains all the existing states that are available for mapping to the new states.
    • Select Target: Allows you to select the new states that you want to map to the existing states.
    • Baseline Target: Displays the newly mapped states corresponding to the existing states.
  9. Using the Select Target column, select the state that you want to map to the existing state.
    Note: You can use the Auto Map button to automatically map the existing states to the new states based on the state name.
  10. Repeat step 9 for all the existing states.
  11. Select Save Mapping.
  12. Browse for the path where you want to save the mapping file, and then select Save.
    A .xml file containing the state mappings is saved.
  13. Select Revert Single Family.
  14. Select the state mapping file that you saved in step 12, and then select OK.
    The mapping operation starts. After the operation is successfully completed, a success message appears.
  15. Select Exit.
    The Revert to Baseline utility is closed.

Configure APM to Create Task Revisions

About This Task

You can configure APM to create records that track changes to Task record values, so that you can keep a historical record of Task data on a given date and time. Throughout this documentation, we refer to these revision-tracking records as Task Revision records. The family caption, however, is not necessarily Task Revision.

APM provides the following Task Revision families, but you can create your own:

  • Task Revision
  • Inspection Task Revision

We assume that you do not want a Task Revision record to be created when you create a new Task record or update an existing Task record. If, however, you want these Task Revision records to be created, you will need to perform the following step.

Procedure

Configure the Has Task Revision relationship to include the Task family as the predecessor and its Task Revision subfamily as the successor.

Results

When you create or modify a task, a Task Revision is created and linked to the task.

About Configuring the Has Task Revision Relationship

The Has Task Revision relationship family is used to link Task Revisions to Tasks. If a relationship definition exists between a Task family and its Task Revision subfamily, when you create a Task record in that family, the APM system will automatically create a Task Revision and link it to the Task. The Task Revision serves as a historical record of the Task data on a given date and time. If you later update the Task, a new Task Revision will be created.

We assume that you do not want a Task Revision to be created when you create a new Task or update an existing Task. If, however, you do want these Task Revisions to be created, you will need to configure the Has Task Revision relationship to include the required families. No relationship definitions are configured for this family in the baseline APM database.

The following table provides an example of a relationship definition that you might configure for the Has Task Revision relationship if you are using the root Task family.

PredecessorSuccessorCardinality
TaskTask RevisionOne to Many

Inspection Task Revision

We assume that you do not want an Inspection Task Revision to be created when you create a new Inspection Task or update an existing Inspection Task. If, however, you do want these Inspection Task Revisions to be created, you will need to configure the Has Task Revision relationship to include the required families. No relationship definitions are configured for this family in the baseline Inspection Management product.

The following table provides an example of a relationship definition that you might configure for the Has Task Revision relationship if you are using the Inspection Task family.

PredecessorSuccessorCardinality
Inspection TaskInspection Task RevisionOne to Many

Configure Inspection Management ActiveMQ settings for MIExecution Service

The MIExecution Service,on each APM Server serves RBI, Inspection and Thickness Monitoring module queues. This service is configured to use a single shared ActiveMQ queue service across APM. Available queue configuration options include retries and concurrency limit.

Procedure

  1. On the APM Server, access the folder that contains the MIExecution Service files.
    Note: If you have installed APM in the default location, you can locate the folder in C:\Program Files\Meridium\ApplicationServer\mi-execution
  2. Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
  3. In the file, locate the following text:
    "Queue_Config": {
    	    "Queues": [
    	      {
    	        "Name": "MI_IM_Queue", 
    	        "ConcurrencyLimit": 100,
    	        "Retries": 5,
                   "LimitPerTenantRequired": true
    	      }
    	    ]
              }
    Note: ConcurrencyLimit indicates the maximum number of messages that will be consumed concurrently. Retries indicates the number of times it retries to send the messages to ActiveMQ if it fails. LimitPerTenantRequired indicates whether Maximum Concurrency limit per Tenant is specified in scheduler service for the queue.
  4. Update the key values as desired.
  5. Save and close the file.
    The updated settings will be applied when the MIExecution Service is stopped and restarted.

Inspection Management Security Groups and Roles

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 GroupRoles
MI Inspection

MI Mechanical Integrity Administrator

MI Mechanical Integrity Power

MI Mechanical Integrity User

MI Inspection Viewer

MI APM Viewer

MI Mechanical Integrity Viewer

The following roles can be assigned to a group or user:
  • Inspector
  • Inspection Supervisor
  • SC Recommendations Implementer
  • SC Recommendations Reviewer

These roles are used in State Management.

FamilyMI Inspection MI Inspection Viewer
Entity Families
AlertView, Insert, Update, DeleteView
CertificationView, Insert, Update, DeleteView
Checklist FindingView, Insert, Update, DeleteView
Conditional AlertsView, Insert, Update, DeleteView
CorrosionView, Insert, Update, DeleteView
EquipmentView, Insert, Update, DeleteView
EventView, Insert, Update, DeleteView
FindingView, Insert, Update, DeleteView
Human ResourceViewView
Inspection MethodView, Insert, Update, DeleteView
Inspection ProfileView, Insert, Update, DeleteView
Inspection Team MemberView, Insert, Update, DeleteView
Inventory Group ConfigurationViewView
Potential Degradation MechanismsViewView
RBI Degradation MechanismsViewView
RBI Inspection Auto-Selection CriteriaViewView
RecommendationView, Insert, Update, DeleteView
Reference DocumentView, Insert, Update, DeleteView
Resource RoleView, Insert, Update, DeleteView
SAP SystemViewView
Security UserViewView
StrategyView, UpdateView
TaskView, Insert, Update, DeleteView
Taxonomy ReferencesViewView
Time Based Inspection IntervalView, Insert, Update, DeleteView
Time Based Inspection SettingView, Insert, Update, DeleteView
Work PackView, Insert, Update, DeleteView
Relationship Families
Belongs to a UnitView, Update, Insert, DeleteView
Checklist Has FindingView, Insert, Update, DeleteView
Has CertificationsView, Insert, Update, DeleteView
Has Degradation MechanismsViewView
Has FindingsView, Insert, Update, DeleteView
Has Inspection MethodView, Insert, Update, DeleteView
Has Inspection ProfileView, Insert, Update, DeleteView
Has Inspection ScopeView, Insert, Update, DeleteView
Has InspectionsView, Insert, Update, DeleteView
Has Potential Degradation MechanismsViewView
Has RecommendationsView, Insert, Update, DeleteView
Has Reference DocumentsView, Insert, Update, DeleteView
Has RolesView, Insert, Update, DeleteView
Has Sub-InspectionsView, Insert, Update, DeleteView
Has TasksView, Insert, Update, DeleteView
Has Task HistoryView, InsertView
Has Task RevisionView, InsertView
Has Team MemberView, Insert, Update, DeleteView
Has Taxonomy Hierarchy ElementViewView
Has Taxonomy MappingViewView
Has Time Based Inspection IntervalView, Insert, Update, DeleteView
Has Work PackView, Update, Insert, DeleteView
Is a UserViewView
Is Planned ByView, Insert, Update, DeleteView
Is Executed ByView, Insert, Update, DeleteView
Note: Security privileges for all modules and catalog folders can be found in the APM documentation.

Note that:

  • The family-level privileges granted to the following families are also spread to all of their subfamilies:
    • Event
    • Taxonomy References
  • The Has Task History relationship family is inactive in the baseline APM database.
  • In addition to the families listed in the preceding table, members of the MI Inspection Security Group have View privileges to additional families to facilitate integration with the Risk Based Inspection module. Since these families are not used elsewhere in Inspection Management, they are not listed in this table.
Note: As part of implementing Inspection Management, you will decide whether you want to link Inspection records to Equipment records, Functional Location records, or both. If you want to link Inspection records to Functional Location records, you will need to grant members of the MI Inspection Security Group at least View privileges to the Functional Location family and the Functional Location Has Equipment relationship family. All new users are automatically assigned to the Everyone user group.

Revert Inspection Management Dashboard to Baseline

Before You Begin

This action is required only if you have modified the Inspection Management dashboard.

About This Task

If you have modified the Inspection Management dashboard, perform the following steps to revert the dashboard to baseline.

Procedure

  1. Access the Catalog page.
  2. Navigate to the Public folder for the dashboard that you want to revert.
    The dashboards are stored within the Public/Meridium/Modules/Mechanical Integrity/Dashboards/ folder.
  3. Select the check box next to the dashboard that you want to revert, and then select .
    The Confirm Delete window appears, asking you to confirm if you want to delete the selected dashboard.
  4. Select OK.
    The selected dashboard is deleted.
  5. Navigate to the Baseline folder for dashboards.
    The baseline dashboards are stored within the Public/Meridium/Modules/Mechanical Integrity/Dashboards/ folder.
  6. Select the check box next to the dashboard that you want to revert, and then select .
    The Catalog Folder Browser window appears.
  7. Navigate to the folder containing the public dashboard that you deleted in step 3.
  8. Select OK.
    A success message appears indicating that the selected item has been copied successfully.
  9. Repeat Steps 2-8 for each dashboard that you want to revert to baseline.