Meridium Enterprise APM Modules and Features · View,Update,Insert, Delete View OPCReading View View OPCSystem View View OPCTag View View RelationshipFamilies HasCheckpoint View View

Meridium Enterprise APM Modules and Features

Confidential and Proprietary Information of Meridium, Inc. • Page 1 of 276


V4.1.0.0

Copyright and Legal



V4.1.0.0

Copyright © Meridium, Inc. 2015

All rights reserved. Printed in the U.S.A.

This software/documentation contains proprietary information of Meridium, Inc.;it is provided under a license agreement containing restrictions on use and dis-closure. All rights including reproduction by photographic or electronic processand translation into other languages of this material are fully reserved undercopyright laws. Reproduction or use of this material in whole or in part in anymanner without written permission fromMeridium, Inc. is strictly prohibited.

Meridium is a registered trademark of Meridium, Inc.

All trade names referenced are the service mark, trademark or registered trade-mark of the respective manufacturer.

Table of Contents


Table of Contents

ŗImportant: This document is utilizing a prototype PDF template. Links to externaldocuments do not function correctly and should not be used. You will be promptedwhen you attempt to use a link to an external document. This template will continueto be updated.

Meridium Enterprise APM Modules and Features 1

Copyright and Legal 2

Table of Contents 3

Deploying Modules and Features 8

Deploying Asset Health Manager (AHM) 9

Deploying Asset Health Manager (AHM) for the First Time 10

Upgrading Asset Health Manager (AHM) to V4.1.0.0 12

About the Asset Health Services 21

Configure the Meridium Notification Service for AHM 24

Asset Health Manager Security Groups and Roles 25

Deploying Asset Criticality Analysis (ACA) 28

Deploying Asset Criticality Analysis (ACA) for the First Time 29

Upgrading Asset Criticality Analysis (ACA) to V4.1.0.0 30

ACA Security Groups and Roles 33

About Associating an ACA with a Specific Site 36

Specify an Alternate Unmitigated Risk Label 37

Deploying Asset Strategy Implementation (ASI) 38

Deploying Asset Strategy Implementation (ASI) for the First Time 39

Upgrading Asset Strategy Implementation (ASI) to V4.1.0.0 41

ASI Security Groups and Roles 42

Deploying Asset Strategy Management (ASM) 48

Deploying Asset Strategy Management (ASM) for the First Time 49

Upgrading Asset Strategy Management (ASM) to V4.1.0.0 50

ASM Security Groups and Roles 52

Deploying Calibration Management 62

Table of Contents


Deploying Calibration Management for the First Time 63

Upgrading Calibration Management to V4.1.0.0 64

Calibration Management Security Groups and Roles 65

Deploying Failure Modes and Effects Analysis (FMEA) 69

Deploying Failure Modes and Effects Analysis (FMEA) for the First Time 70

Upgrading Failure Modes and Effects Analysis (FMEA) to V4.1.0.0 71

Failure Modes and Effects Analysis (FMEA) Security Groups and Roles 72

Deploying Hazards Analysis 76

Deploying Hazards Analysis for the First Time 77

Upgrading Hazards Analysis to V4.1.0.0 79

Hazards Analysis Security Groups and Roles 81

Deploying Inspection Management 87

Deploying Inspection Management for the First Time 88

Upgrading Inspection Management to V4.1.0.0 90

Inspection Management Security Groups and Roles 91

Deploying Metrics and Scorecards 95

Deploying Metrics and Scorecards for the First Time 96

Upgrading Metrics and Scorecards to V4.1.0.0 100

About Configuring a Cube for Usage Metrics Tracking 102

About Scheduling Cubes for Processing 103

Install SQL Server Analysis Services on the Server 104

Migrate SQL Server Cubes 105

Deploy the Work History Cube 107

Metrics and Scorecard Security Groups and Roles 108

Deploying Policy Designer 110

Deploying Policy Designer for the First Time 111

Upgrading Policy Designer to V4.1.0.0 112


About Configuring Policy Execution 119

Configure the Policy Trigger Service 120

Table of Contents


Configure Multiple Meridium Enterprise APM Servers for Policy Execution 121

Policy Designer Security Groups and Roles 123

Deploying Process Data Integration (PDI) 124

Deploying Process Data Integration (PDI) for the First Time 125

Upgrading Process Data Integration (PDI) to V4.1.0.0 127

Process Data Integration Server Roles 132


Install the Process Data Integration Service 136

Upgrade the Process Data Integration Service 138

Configure the Meridium Notification Service for PDI 140

Configure the Process Data Integration Service 142

Configure Multiple Data Sources 146

Configure Multiple Process Data Integration and OPC Servers 147

Process Data Integration Security Groups and Roles 149

Deploying Production Loss Analysis (PLA) 150

Deploying Production Loss Analysis (PLA) for the First Time 151

Upgrading Production Loss Analysis (PLA) to V4.1.0.0 155

Production Loss Analysis Security Groups and Roles 160

Deploying Recommendation Management 164

Deploying Recommendation Management for the First Time 165

Upgrading Recommendation Management to V4.1.0.0 166

Recommendation Management Security Groups and Roles 167

About Asset Queries 169

Deploying Reliability Analytics 171

Deploying Reliability Analytics for the First Time 172

Upgrading Reliability Analytics to V4.1.0.0 173

Reliability Analytics Security Groups and Roles 174

Deploying Reliability Centered Maintenance (RCM) 179

Deploying Reliability Centered Maintenance (RCM) for the First Time 180

Upgrading Reliability Centered Maintenance (RCM) to V4.1.0.0 181

Table of Contents


Reliability Centered Maintenance (RCM) Security Groups and Roles 182

Reports 187

Deploying Reports for the First Time 188

Install the APM Reports Designer 189

Set Up the APM Report Designer 195

Deploying Risk Based Inspection (RBI) 197

Deploying Risk Based Inspection (RBI) for the First Time 198

Upgrading Risk Based Inspection (RBI) to V4.1.0.0 201

Risk Based Inspection Security Groups and Roles 209

Deploying Root Cause Analysis (RCA) 215

Deploying Root Cause Analysis (RCA) for the First Time 216

Upgrading Root Cause Analysis (RCA) to V4.1.0.0 217

RCA Security 218

Root Cause Analysis Security Groups and Roles 219

Deploying Rounds 222

Deploying Rounds for the First Time 223

Upgrading Rounds to V4.1.0.0 228

Security Groups and Privileges In Rounds 233

Manage the Measurement Location Template Mappings 237

Deploying Rules 238

Install the Meridium Rules Editor 239

Deploying SIS Management 245

Deploying SIS Management for the First Time 246

Upgrade Workflow 248

SIS Management Security Groups and Roles 251

Deploying Thickness Monitoring (TM) 258

Deploying Thickness Monitoring (TM) for the First Time 259

Upgrading Thickness Monitoring (TM) to V4.1.0.0 262

Use Custom TML Analysis Types 268

Install the Meridium Device Service 270

Table of Contents


Configure the Meridium Device Service 271

Thickness Monitoring Functional Security Privileges 272

Thickness Monitoring Security Groups and Roles 274

Deploying Modules and Features


Deploying Modules and FeaturesThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring the Meridium Enterprise APM modules and features, whetheryou are deploying the module for the first time or upgrading from a previous module.



Deploying Asset Health Manager (AHM)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Asset Health Manager (AHM) for theFirst TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.

These tasks may be completed by multiple people in your organization. We recom-mend, however, that the tasks be completed in the order in which they are listed. Allsteps are required unless otherwise noted.

Step Task Required? Notes

1 Assign Security Users to the Asset HealthManager Security Groups. Y None

2On the Meridium Enterprise APM Server,configure the Meridium Notification Ser-vice for AHM.

Y None

3On the Meridium Enterprise APMServer, start or restart the MeridiumNotification Service.

Y None

4

On the Meridium Enterprise APM Server,start the Meridium AHM Service.

Note: The Meridium AHM Service isreferred to as the "Asset Health Indic-ator Service" throughout the MeridiumEnterprise APM documentation.

Y

When you start theservice, Health Indic-ator records are cre-ated or updatedautomatically basedon health indicatorand reading sourcerecords.

5

Review the AHM data model to determ-ine which relationship definitions youwill need to modify to include your cus-tom asset families.

N

Required if you storeasset information infamilies other thanthe baseline Equip-ment and FunctionalLocation families.

6

Determine the equipment or locationwhose overall health you want to eval-uate, and make sure that an assetrecord exists in the database for thisequipment or location and is included inthe Asset Hierarchy configuration.

Y

If you are using cus-tom asset familiesand relationships (seeStep 5), make surethat the equivalentrecords and linksexist in the database.




7

Configure Health Indicator Mappingrecords for each family that you want touse as a health indicator source, forwhich a baseline Health Indicator Map-ping record does not already exist.

Y

Baseline Health Indic-ator Mapping recordsexist for the followinghealth indicatorsource families:

l MeasurementLocation

l KPIl OPC Tagl Health Indicator

8Link each asset record to the record(s)that you want to use as a health indic-ator source records.

Y None

9

For any specific records in a health indic-ator source family for which you do notwant health indicators to be created,exclude these records from the auto-matic health indicator creation.

N None

10

Review the baseline event mappings andmodify or create new mappings asnecessary to customize the informationthat is displayed in the Events section inAsset Health Manager.

N

Refer to the AssetHealth Manager enduser help for moreinformation aboutevents.



Upgrading Asset Health Manager (AHM) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


V3.6.0.0.0Step Task Required? Notes

1On the Meridium Enterprise APMServer, configure the MeridiumNotification Service for AHM.

Y None

2On the Meridium Enterprise APMServer, start or restart theMeridium Notification Service.

Y None

3

Start or restart the MeridiumAHM Service.

Note: The MeridiumAHM Service is referred to asthe "Asset Health Indicator Ser-vice" throughout the MeridiumEnterprise APM documentation.

Y None




4

Review the potential health indic-ator source records in your data-base and specify whether or nothealth indicators should be auto-matically created for each.

Y

During the databaseupgrade process, any validhealth indicator sourcerecords that are linked to anasset and not linked to aHealth Indicator record willbe excluded from the auto-matic health indicator cre-ation by default.

Note: Alternatively,prior to upgrading toV4.1.0.0, you can use theHealth Indicator Builder inV3 to create Health Indic-ator records for the neces-sary source records.

5

If you previously used the Hier-archy Item Definition family tocreate a custom hierarchy forAsset Health Manager, ensurethat the relevant asset familiesare included in the application-wide Asset Hierarchy con-figuration.

Y None

6

If you are using custom HealthIndicator Mapping records, spe-cify values in the Type Field andType Value fields to ensure thatthe mappings are used for theappropriate reading type.

Y None

V3.5.1





Y None


Y None

3



Y None

4


Y






5

If you previously used the Hier-archy Item Definition family tocreate a custom hierarchy forAsset Health Manager, ensurethat the relevant asset familiesare included in the application-wide Asset Hierarchy con-figuration..

Y None

6


Y None

V3.5.0 SP1 LPStep Task Required? Notes

1On the Meridium Enterprise APM Server, con-figure the Meridium Notification Service for AHM.

Y None

2On the Meridium Enterprise APM Server, start orrestart the Meridium Notification Service.

Y None

3

Start or restart the Meridium AHM Service.

Note: The Meridium AHM Service is referredto as the "Asset Health Indicator Service"throughout the Meridium Enterprise APM doc-umentation.

Y None




4

Review the potential health indicator sourcerecords in your database and specify whether ornot health indicators should be automatically cre-ated for each.

Y

During thedatabaseupgrade pro-cess, anyvalid healthindicatorsourcerecords thatare linked toan asset andnot linked toa HealthIndicatorrecord willbe excludedfrom theautomatichealth indic-ator creationby default.

Note:Altern-atively,prior toupgradingto V4.1.0.0,you canuse theHealthIndicatorBuilder inV3 to cre-ate HealthIndicatorrecords forthe neces-sary




sourcerecords.

5

If you previously used the Hierarchy Item Defin-ition family to create a custom hierarchy for AssetHealth Manager, ensure that the relevant assetfamilies are included in the application-wideAsset Hierarchy configuration.

Y None

6

If you are using custom Health Indicator Mappingrecords, specify values in the Type Field and TypeValue fields to ensure that the mappings are usedfor the appropriate reading type.

Y None

V3.5.0Step Task Required? Notes


Y None


Y None

3



Y None




4


Y



5


Y None

6


Y None

V3.4.5





Y None


Y None

3



Y None

4


Y






5


Y None

6


Y None



About the Asset Health ServicesWhen you deploy the Asset Health Manager, Process Data Integration, and PolicyDesigner modules together, the services used by each module interact with each otherin various ways. This topic summarizes those services and describes a standard systemarchitecture containing the components used by all three modules.

For a list of tasks that you must complete to deploy each module, refer to the followingtopics:

l Deploying Asset Health Manager (AHM) for the First Timel Deploying Policy Designer for the First Timel Deploying Process Data Integration (PDI) for the First Time

Services Summary

The following services are used by the Asset Health Manager, Process Data Integration,and Policy Designer modules:

l Asset Health Indicator Service: Automatically updates the following field valuesin a Health Indicator record when reading values related to the health indicatorsource record (e.g., an OPC Tag or Measurement Location record) change:

l Alert Levell Last Reading Datel Last Char Reading Value (for records that accept character values)l Last Numeric Reading Value (for records that accept numeric values)

This service also facilitates the automatic creation of Health Indicator records forconfigured sources.

l Policy Trigger Service: When an input to a policy (i.e., an associated record in theMeridium Enterprise APM database or reading value in the process historian)changes or when a policy schedule is due, a message is added to the policy triggerqueue. The Policy Trigger Service monitors this queue and sends these messagesto an appropriate policy execution queue.

l Policy Execution Service: The Meridium Enterprise APM Policy Execution Servicehandles the execution of policies. Specifically, the Policy Execution Service mon-itors a corresponding policy execution queue and executes the policies that areadded to it.

l Process Data Integration (PDI) Service: Monitors the subscribed tags (i.e., tagsthat are used in policies and health indicators or tags for which readings are beingstored in the Meridium database) and, when data changes occur on these tags,adds messages to the appropriate queues. This service also facilitates the auto-matic import and synchronization of tags from a configured process historian.

Example: Standard System Architecture Configuration



The following diagram illustrates the machines in the Meridium Enterprise APM systemarchitecture when the Policy Designer, Process Data Integration (PDI), and Asset HealthManager (AHM) modules are used together. This image depicts the standard con-figuration, where the OPC Server software and the Process Data Integration Service areon the same machine.

Note: In this example configuration, only one machine of each type is illustrated.Your specific architecture may include multiple Meridium Enterprise APM Servers, mul-tiple OPC Servers, or multiple Meridium Enterprise APM Servers used for policy exe-cutions.

The following table summarizes the machines illustrated in this diagram and the soft-ware and services that you will install when you complete the first-time deploymentsteps for Asset Health Manager, Policy Designer, and Process Data Integration.

Machine SoftwareInstalled

Asset Health Service InstalledAutomatically with ServiceSoftware

Meridium Enterprise APMServer

Meridium Enter-prise APM Serversoftware

Asset Health Indicator Service

Policy Trigger Service

Policy Execution Service





Process Data IntegrationServer, which also acts as theOPC Server

Process Data Integ-ration Service soft-ware

Process Data Integration Service

OPC Server soft-ware NA

Process Historian Process historiansoftware NA



Configure the Meridium Notification Service forAHMIn order for the Asset Health Indicator service to work correctly, you must configure theMeridium Notification Service by modifying the file Meridi-um.Service.Notification.exe.config on all Meridium Enterprise APM Servers.

Steps

1. On the Meridium Enterprise APM Server, navigate to the folder where theMeridium Notification Service files are installed. If you installed the software in thedefault location, you can locate these files in the folder C:\Program Files\Meridi-um\Services.

2. Open the file Meridium.Service.Notification.exe.config in an application thatyou can use to modify XML script (e.g., Notepad).

3. If you have not done so already, complete any necessary basic configuration forthe Meridium Notification Service.

4. Within the <notification> tags, within the <notificationSettings>tags, uncom-ment the following text string (i.e., delete the ):



5. Within the <system.serviceModel> tags, within the <client> tags, uncomment thefollowing text string (i.e., delete the ):



6. Save and close the file.

7. Start or restart the Meridium Notification Service.



Asset Health Manager Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, 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 asso-ciated with all of the Security Groups that are assigned to that Role. To avoid grantinga Security User unintended privileges, before assigning a Security User to a Role, besure to review all of the privileges associated with the Security Groups assigned to thatRole. Also be aware that additional Roles, as well as Security Groups assigned to exist-ing Roles, can be added via Security Manager.

Security Group Roles

MI AHI Administrator MI Health Admin

MI AHI UserMI Health User

MI Health Power

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

Family MI AHI Administrator MI AHI User

Entity Families

Checkpoint Task View, Update, Insert View, Update, Insert

Event Mapping View, Update, Insert,Delete View

Health Indicator View, Update, Insert,Delete View, Update

Health Indicator Mapping View, Update, Insert,Delete View

Health Indicator Value View, Update, Insert,Delete View

Hierarchy Item Child Definition View, Update, Insert,Delete View

Hierarchy Item Definition View, Update, Insert,Delete View

Measurement Location View View

KPI View View




KPI Measurement View View

Measurement Location Tem-plate View View

Operator Rounds Allowable Val-ues View View

Policy View View

Policy Instance View View

Reading View View

Recommendation View, Update, Insert,Delete

View, Update, Insert,Delete

Timestamped Value View, Update, Insert,Delete View

OPC Reading View View

OPC System View View

OPC Tag View View

Relationship Families

Has Checkpoint View View

Has Child Hierarchy Item View, Update, Insert,Delete View

Has Health Indicators View, Update, Insert,Delete View

Has Readings View View

Has Recommendations View, Update, Insert,Delete


Has Timestamped Value View, Update, Insert,Delete View

Has OPC Reading View View

Has OPC Tag View View

Health Indicator Has Mapping View, Update, Insert,Delete View




Health Indicator Has Source View, Update, Insert,Delete View



Deploying Asset Criticality Analysis (ACA)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Asset Criticality Analysis (ACA) for theFirst TimeThe following table outlines the steps that you must complete to deploy and configureACA for the first time. These instructions assume that you have completed the steps fordeploying the basic Meridium Enterprise APM system architecture.


Step Task Notes

1 Assign Security Users to one or more ofthe ACA Security Groups. This step is required.

2

Review the ACA data model to determinewhich relationship definitions you willneed to modify to include your customequipment and location families.

Required if you will use equip-ment and location families otherthan the baseline Equipment andFunctional Location families.

3 Define sites to associate with ACA Ana-lyses. None

4

Specify the alternate label that you wantto use for the Unmitigated Risk columnin the grid on the Asset Criticality Ana-lysis Systems page.

Required if you do not want touse the default label, UnmitigatedRisk.

5 Lock the Risk Matrix.Required if you do not want riskvalues to be specified manuallyvia the Risk Matrix.



Upgrading Asset Criticality Analysis (ACA) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


V3.6.0.0.0Step Task Notes

1

Specify the alternate label that you want touse for the Unmitigated Risk column in thegrid on the Asset Criticality Analysis Sys-tems page.

Required if you do not want touse the default label, Unmit-igated Risk.


3Create Criticality Mapping records and linkthem to corresponding Risk Thresholdrecords.

Required if you want to updateyour SAP system to reflect thecriticality value that is determ-ined in ACA.

V3.5.1Step Task Notes

1








V3.5.0 SP1 LPStep Task Notes

1







1







1





Step Task Notes






ACA Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI ACA Administrator MI Foundation Admin

MI ACA Member

MI Foundation Admin

MI Foundation Power

MI Foundation User

MI ACA OwnerMI Foundation Admin

MI Foundation Power

The baseline privileges for these Security Groups are summarized in the following table.

Family MI ACA Admin-istrator

MI ACAMember MI ACA Owner

Analysis Has Human Resource View, Update,Insert, Delete View View, Update,

Insert, Delete

Asset Criticality Analysis View, Update,Insert, Delete View View, Update,

Insert, Delete

Asset Criticality Analysis HasSystem

View, Update,Insert, Delete View View, Update,

Insert, Delete

Asset Criticality Analysis Sys-tem


Insert, Delete

Consequence View, Update,Insert, Delete View View

Consequence Modifier View, Update,Insert, Delete View View

Criticality Mapping View View View





Equipment View View View

Equipment Has Equipment View View View

Functional Location View View View

Functional Location Has Equip-ment View View View

Functional Location Has Func-tional Location View View View

Has Criticality Mapping View View View

Has Functional Location View, Update,Insert, Delete View View, Update,

Insert, Delete

Has RCM FMEA Analysis View None None

Has Recommendations View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Reference Documents View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Reference Values View, Update,Insert, Delete View View

Has Risk View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Risk Category View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Risk Matrix View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Site Reference View, Update,Insert, Delete View View, Update,

Insert, Delete

Has Strategy View None None

Human Resource View, Update,Insert, Delete None View, Update,

Insert, Delete

Meridium General Recom-mendation


Insert, Delete

Mitigates Risk View, Update,Insert, Delete View View, Update,

Insert, Delete





Notification View, Update,Insert, Delete View View, Update,

Insert, Delete

Probability View, Update,Insert, Delete View View

Protection Level View View View

RCM FMEA Analysis View None None

Reference Document View, Update,Insert, Delete View View, Update,

Insert, Delete

Risk View, Update,Insert, Delete View View, Update,

Insert, Delete

Risk Assessment View, Update,Insert, Delete View View, Update,

Insert, Delete

Risk Category View, Update,Insert, Delete View View, Update,

Insert, Delete

Risk Matrix View, Update,Insert, Delete View View, Update,

Insert, Delete

Risk Threshold View, Update,Insert, Delete View View

Safety Analysis Has Equipment View, Update,Insert, Delete View View, Update,

Insert, Delete

Site Reference View View View

System Strategy View None None



About Associating an ACA with a Specific SiteSome companies that use the Meridium Enterprise APM software have facilities at mul-tiple sites, or locations, around the world. Each site contains unique units, systems, andassets.

If desired, you can define these sites and associate equipment and locations with thesite to which they belong. You can also associate risk matrices with specific sites. If a riskmatrix is associated with a site, you can specify which site you want to associate with anACA. You can associate a site with an ACA by selecting the ID of the desired Site Refer-ence record in the Site ID field on the Analysis Definition datasheet for that ACA.

After an ACA is associated with a site, when you create a Risk Assessment record for anAsset Criticality Analysis System, Equipment, or Functional Location record associatedwith the ACA, rather than seeing the default risk matrix, you will see the risk matrix thatis associated with the specified site.

You can add to an ACA an Equipment or Functional Location record that is already asso-ciated with a site even if the site is different than the one specified in the Asset CriticalityAnalysis record. If an Equipment or Functional Location record is already associatedwith a site and a risk rank value already exists for that record:

l The risk rank value that was determined using the risk matrix associated with theEquipment or Functional Location record will appear in the Analysis Summarypane beneath its parent system.

l When you try to view or modify the risk rank for the Equipment or Functional Loca-tion record, a message will appear, indicating that the risk rank was determinedusing a risk matrix other than the one that is currently associated with the ana-lysis. When this message appears, you can choose to:

l Accept the current risk rank value that was determined using a risk matrixother than the one that is associated with the current analysis. If you choosethis option, you will not be able to modify the risk rank for the record.

l Determine the risk rank for the Equipment or Functional Location recordusing the risk matrix that is associated with the current analysis.

Note: This information is also true if you specify a site for the ACA, and then laterspecify a different site.

If an Equipment or Functional Location record is associated with a site but a risk rankvalue has not been determined for that record, when you select the Risk Matrix link todefine the risk rank for that record, the risk matrix that is currently associated with theACA appears.



Specify an Alternate Unmitigated Risk LabelIn ACA, the Unmitigated Risk section displays the unmitigated risk for each Asset Crit-icality Analysis System, Equipment, and Functional Location record. If your companyprefers a label other than Unmitigated Risk, you can use the following instructions to spe-cify an alternate label.

Note that an alternate label is specified using the Risk Matrix record. This means thatafter you specify an alternate label in a Risk Matrix record, it will be used by all ACA Ana-lyses that use that Risk Matrix.

Steps

1. On the Meridium navigation menu, on the left toolbar, select Admin, and thenselect Operations Manager.

The Operations Manager page appears.

2. Select Risk Matrix.

The Risk Matrix Admin page appears.

3. In the Name column, select the risk matrix record that you want to access.

The datasheet for the selected risk matrix appears.

4. To enable editing of the datasheet, select {pencil icon}.

5. In the Appearance section, in the Unmitigated Risk Label field, modify the fieldvalue as needed.

6. Select {disk icon}.

The Unmitigated Risk Label for that risk matrix is changed.



Deploying Asset Strategy Implementation (ASI)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Asset Strategy Implementation (ASI) forthe First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.

Steps are marked as Required in the Required/Optional column if you must performthe steps to take advantage of ASI functionality. This documentation assumes that, inaddition to implementing the basic ASI functionality, that you also want to implementintegration with SAP. Steps necessary for SAP integration are also designated as Requiredin the following table.


Step Task Required/Optional Notes

1 Install the ASI for SAP ABAPadd-on on your SAP System. Required None

2

Review the ASI data model todetermine which rela-tionship definitions you willneed to modify to includeyour custom equipment andlocation families. Modify anyrelationship definitions asneeded via the ConfigurationManager application.

Optional

This task is neces-sary only if youstore equipmentand location inform-ation in familiesother than thebaseline Equipmentand Functional Loca-tion families.

3

Assign users to one or moreof the Strategy Security Rolesvia the Security Managerapplication.

Required

Users will need per-missions to the ASIfamilies in order touse ASI.

4 Configure SAP permissions. Required None

5Configure secured Main-tenance Plants in yourSAP System.

Optional None




6

Configure Work Man-agement Item Definitionrecords via theASI Application Settings.

Optional

This task is neces-sary only if you wantto use Work Man-agement Item Defin-ition recordsbeyond thoseprovided with thebaseline database.

7Define Implementation Rolesvia the ASI Application Set-

tings.Optional None

8

Define the SAP connectionthat will be used when SAPitems are created fromrecords that represent workitems. You can do so via theASI Application Settings.

Required None



Upgrading Asset Strategy Implementation (ASI) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


1Upgrade the ASI for SAP ABAP add-on in your SAP Sys-tem.

Y None



Y None



Y None



Y None



Y None



ASI Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI ASI User MI Strategy User

MI ASI User MI Strategy Power

MI ASI User

MI ASI AdministratorMI Strategy Admin


Family MI ASI Admin-istrator MI ASI user

Entity Families

Action None View, Update

Action Mapping View, Update, Insert,Delete View

Active Strategy None View

Asset Strategy None View

Calibration Task None View, Update, Insert,Delete

Consequence None View

Equipment View, Update, Insert,Delete View, Update, Insert

Execution Mapping View, Update, Insert,Delete View



Functional Location View, Update, Insert,Delete View, Update, Insert

Health Indicator None View

Health Indicator Mapping None View

Hierarchy Item Child Definition None View

Hierarchy Item Definition None View

Implementation Authorization View, Update, Insert,Delete View

Implementation Package None View, Update, Insert,Delete

Implementation Role View, Update, Insert,Delete View

Inspection Task None View, Update, Insert,Delete

KPI None View

KPI Measurement None View

Maintenance Item None View, Update, Insert,Delete

Maintenance Package None View, Update, Insert,Delete

Maintenance Plan None View, Update, Insert,Delete

Material None View, Update, Insert,Delete

Measurement Location None View, Update, Insert,Delete

Measurement Location Group None View, Update, Insert,Delete

Measurement Location Template View, Update, Insert,Delete View, Update, Insert

Notification None View, Update, Insert,Delete

Object List Item None View, Update, Insert,Delete



Operation None View, Update, Insert,Delete

Operator Rounds Allowable Values None View

Probability None View

Proposed Strategy None View

Protection Level None View

PRT None View, Update, Insert,Delete

PRT Template View, Update, Insert,Delete View

RCM FMEA Asset None View

RCM FMEA Recommendation None View

Risk None View

Risk Assessment None View

Risk Category None View

Risk Matrix None View

Risk Rank None View

Risk Threshold None View

SAP System View, Update, Insert,Delete View

Site Reference View View

System Strategy None View

Task List None View, Update, Insert,Delete

Task Types None View

Thickness Monitoring Task None View, Update, Insert,Delete

Unit Strategy None View

Work Management Item Child Definition View, Update, Insert,Delete View



Work Management Item Definition View, Update, Insert,Delete View

Work Management Item Definition Con-figuration

View, Update, Insert,Delete View


Authorized to Implement View, Update, Insert,Delete View

Documents Action View, Update, Insert,Delete


Has Actions None View

Has Action Mapping View, Update, Insert,Delete View

Has Action Revisions None View

Has Active Strategy None View

Has Asset Strategy None View

Has Associated Recommendation None View

Has Checkpoint None View, Insert

Has Child Hierarchy Item None View

Has Child Work Management Item View, Update, Insert,Delete View

Has Driving Recommendation None View

Has Execution Mapping View, Update, Insert,Delete View

Has Health Indicators View, Update, Insert,Delete


Has KPI Measurement None View

Has Maintenance Item None View, Update, Insert,Delete

Has Maintenance Package None View, Update, Insert,Delete

Has Material None View, Update, Insert,Delete



Has Measurement Location Group None View, Update, Insert,Delete

Has Mitigation Revisions None View

Has Object List Item None View, Update, Insert,Delete

Has Operation None View, Update, Insert,Delete

Has Proposed Strategy None View

Has PRT None View, Update, Insert,Delete

Has Reference Values None View

Has Risk None View

Has Risk Category None View

Has Risk Revisions None View

Has SAP System None View, Update, Insert,Delete

Has Strategy None View

Has Strategy Revision None View

Has System Strategy None View

Has Tasks None View, Update, Insert,Delete

Has Task List None View, Update, Insert,Delete

Has Task Revision None View, Update, Insert,Delete

Has Work Management Item None View, Update, Insert,Delete

Has Work Management Item DefinitionConfiguration


Health Indicator Has Mapping None View, Update, Insert

Health Indicator Has Source None View, Update, Insert,Delete



Implements Action None View, Update, Insert,Delete

Implements Strategy None View, Update, Insert,Delete

Implements Secondary Strategy None View, Update, Insert,Delete

Is Mitigated None View

Master Template Has Asset Strategy None View

Mitigates Risk None View

Was Applied to Asset Strategy View, Update, Insert,Delete


Was Applied to PRT View, Update, Insert,Delete




Deploying Asset Strategy Management (ASM)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Asset Strategy Management (ASM) forthe First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

If you are using families outside of thebaseline Equipment and FunctionalLocation families, review the ASM datamodule to determine which relationshipdefinitions you will need to modify toinclude your custom equipment and loc-ation families. Modify any relationshipdefinitions as needed via the Con-figuration Manager application.

Optional

This step isnecessaryonly if youare usingfamilies out-side thebaselineEquipmentand Func-tional Loca-tionfamilies tostore equip-ment andlocationdata.

2Assign users to one or more of theStrategy Security Roles via the SecurityManager application.

Required None



Upgrading Asset Strategy Management (ASM) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0ASM will be upgraded from V3.6.0.0.0 to V4.1.0.0 automatically when you upgrade thecomponents in the basic Meridium Enterprise APM system architecture. No additionalsteps are required.

V3.5.1ASM will be upgraded from V3.5.1 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.


1

Move to the Asset Strategy family any custom rules thatare defined for the following families and configuredto be executed during the Asset Strategy activation pro-cess: Action; Risk; Risk Assessment; Risk Rank; ActionRevision; Risk Revision; Risk Assessment Revision;Strategy Revision.

Y None

2

Move to the Asset Strategy Template family any customrules that are defined for the following families andconfigured to be executed when a new Asset StrategyTemplate is saved after being created from an existingAsset Strategy Template or Asset Strategy: Action; Risk;Risk Assessment; Risk Rank; Has Risk Category.

Y None

3

Move to the Asset Strategy or Asset Strategy Templatefamily (as appropriate) any custom rules that aredefined for any other family and are configured to beexecuted when an Asset Strategy or Asset Strategy Tem-plate is deleted.

Y None

V3.5.0




1

Move to the Asset Strategy family any custom rules thatare defined for the following families and configuredto be executed during the activation process: Action;Risk; Risk Assessment; Risk Rank; Action Revision; RiskRevision; Risk Assessment Revision; Strategy Revision.

Y None


1

Move to the Asset Strategy family any custom rules thatare defined for the following families and configuredto be executed during the activation process: Action;Risk; Risk Assessment; Risk Rank; Action Revision; RiskRevision; Risk Assessment Revision; Strategy Revision.

Y None



ASM Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI ASM Analyst

MI ASM ViewerMI Strategy User

MI ASM Analyst

MI ASM Reviewer

MI ASM Viewer

MI Strategy Power

MI ASM Management Administrator

MI ASM Analyst

MI ASM Reviewer

MI ASM Viewer

MI Strategy Admin


Family MI ASMAnalyst

MI ASMAdministrator

MI ASMReviewer

MI ASMViewer

ActionInsert, View,Update, andDelete

ViewInsert, View,Update, andDelete

View

Action Mapping View None None None

Active StrategyInsert, View,Update, andDelete


View

Analysis Link View View View View

Asset Criticality Analysis View View View View



Asset Criticality AnalysisHas System View View View View

Asset Criticality AnalysisSystem View View View View

Asset StrategyInsert, View,Update, andDelete

View View andUpdate View

Calibration Task View None View None

Checkpoint Task Insert, Viewand Update

Insert, View andUpdate

Insert, Viewand Update

Insert,View andUpdate

Consequence ViewInsert, View,Update, andDelete

View View

DistributionInsert, View,Update, andDelete

View View View

Execution Mapping View None None None

Growth Model View View View View

Has Action DriverInsert, View,Update, andDelete

None None None

Has Action Mapping View None None None

Has Action RevisionsInsert, View,Update, andDelete


View

Has ActionsInsert, View,Update, andDelete


View

Has Active StrategyInsert, View,Update, andDelete


View

Has Asset StrategyInsert, View,Update, andDelete

View View View



Has Associated Recom-mendation

Insert, View,Update, andDelete

View View View

Has Associated StrategyInsert, View,Update, andDelete

View View View

Has Checkpoint View None None None

Has Child HierarchyItem View


View View

Has Child Work Man-agement Item View None None None

Has Driving Recom-mendation


View View andDelete View

Has Execution Mapping View None None None

Has Functional Location View n/a View n/a

Has Global EventsInsert, View,Update, andDelete

View View View

Has Health IndicatorsInsert, View,Update, andDelete

View View View

Has Measurement Loca-tion Group


None None None

Has Mitigated TTF Dis-tribution


View View View

Has Mitigation Revi-sions



View

Has Planned ResourceUsages


View View View

Has Proposed StrategyInsert, View,Update, andDelete


View



Has Readings View View View View

Has RecommendationsInsert, View,Update, andDelete

None None n/a

Has Reference Values ViewInsert, View,Update, andDelete

View View

Has Resource UsagesInsert, View,Update, andDelete

View View View

Has RiskInsert, View,Update, andDelete


View

Has Risk AssessmentsInsert, View,Update, andDelete

View View View

Has Risk CategoryInsert, View,Update, andDelete



View

Has Risk Matrix View None None None

Has Risk RevisionsInsert, View,Update, andDelete


View

Has Root SystemInsert, View,Update, andDelete

View View View

Has ScenariosInsert, View,Update, andDelete

View View View

Has Site Reference View None None n/a

Has StrategyInsert, View,Update, andDelete

View View View

Has Strategy RevisionInsert, View,Update, andDelete


View



Has System ActionsInsert, View,Update, andDelete

View View View

Has System ElementsInsert, View,Update, andDelete

View View View

Has System Optim-ization


View View View

Has System ResourcesInsert, View,Update, andDelete

View View View

Has System ResultsInsert, View,Update, andDelete

View View View

Has System RisksInsert, View,Update, andDelete

View View View

Has System StrategyInsert, View,Update, andDelete

View View View

Has TTF DistributionInsert, View,Update, andDelete

View View View

Has TTR DistributionInsert, View,Update, andDelete

View View View

Has UnplannedResource Usages


View View View

Has Work ManagementItem

Insert, Viewand Update None None None

Has Work ManagementItem Definition Con-figuration

View None None None

Health IndicatorInsert, View,Update, andDelete

None View andUpdate

View andUpdate



Health Indicator HasMapping


View View View

Health Indicator HasSource


View View View

Health Indicator Map-ping View


View View

Hierarchy Item ChildDefinition View


View View

Hierarchy Item Defin-ition View


View View

Implementation Pack-age

View andInsert None None None

Implementation Role View View View View

Implements Action Insert, Viewand Update None None None

Implements Strategy View andInsert None None None

Implements SecondaryStrategy View None None None

Inspection Task View None View View

Is Based on RBI Degrad-ation Mechanism None None View and

Delete None

Is Based on RCM FMEAFailure Effect


None None None

Is Basis for AssetStrategy Template



Is MitigatedInsert, View,Update, andDelete


View

KPI View View View View



KPI Measurement View View View View

Master Template HasAsset Strategy



Measurement Location View View View View

Measurement LocationGroup

Insert, Viewand Update None None None

Measurement LocationTemplate View View View View

Mitigates RiskInsert, View,Update, andDelete


View

Operator Rounds Allow-able Values View View View View

Probability ViewInsert, View,Update, andDelete

View View

Proposed StrategyInsert, View,Update, andDelete


Protection Level View View View View

RBI Degradation Mech-anisms

View andUpdate None None None

RBI Recommendation View andUpdate None None None

RCM FMEA AssetInsert, View,Update, andDelete

View View View

Reading View View View View

Reliability Distribution View View View View

Reliability Growth View View View View

Risk AssessmentInsert, View,Update, andDelete


View



Risk Category ViewInsert, View,Update, andDelete

View View

Risk Matrix ViewInsert, View,Update, andDelete

View View

Risk RankInsert, View,Update, andDelete


View

Risk Threshold ViewInsert, View,Update, andDelete

View View

Safety Analysis HasEquipment View n/a View n/a

Site Reference View View View View

System ActionInsert, View,Update, andDelete

View View View

System Action Mapping ViewInsert, View,Update, andDelete

View View

System Action Optim-ization


View View View

System Action ResultInsert, View,Update, andDelete

View View View

System AnalysisInsert, View,Update, andDelete

View View View

System ElementInsert, View,Update, andDelete

View View View

System Element ResultInsert, View,Update, andDelete

View View View



System Global EventInsert, View,Update, andDelete

View View View

System ResourceInsert, View,Update, andDelete

View View View

System Resource ResultInsert, View,Update, andDelete

View View View

System Resource UsageInsert, View,Update, andDelete

View View View

System Risk AssessmentInsert, View,Update, andDelete

View View View

System ScenarioInsert, View,Update, andDelete

View View View

System SensorInsert, View,Update, andDelete

View View View

System StrategyInsert, View,Update, andDelete


Unit StrategyInsert, View,Update, andDelete


Was Applied to AssetStrategy



Was Promoted to ASMElement View None View View

Work Management ItemChild Definition View None None None

Work Management ItemDefinition View None None None

Work Management ItemDefinition Configuration View None None None



Associating a Strategy with a Specific Site

Some companies that use the Meridium Enterprise APM software have facilities at mul-tiple sites, or locations, around the world. Each site contains unique locations and equip-ment.

If desired, you can define these sites and associate equipment and locations with thesite to which they belong. When you create an Asset Strategy record and link it to anEquipment or Functional Location record, the Site Reference field will be populated auto-matically with the Record ID of the Site Reference record to which the Equipment orFunctional Location record is linked. To help streamline the strategy-building process,the Meridium Enterprise APM system will allow you to add multiple Asset Strategies toSystem Strategies only if all the underlying equipment and locations belong to the samesite. Likewise, you can add multiple System Strategies to a Unit Strategy only if all under-lying equipment and locations belong to the same site.



Deploying Calibration ManagementThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Calibration Management for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the Calibration Man-agement data model to determinewhich relationship definitions youwill need to modify to includeyour custom families.

Optional

Required if you willstore equipmentor location data infamilies other thanthe baseline Equip-ment and Func-tional Locationfamilies.

2Assign the desired Security Usersto the Calibration ManagementSecurity Groups .

Required None

3

Configure the Has Standard Gasrelationship family to include thedesired Instrument families as pre-decessors to the Standard GasCylinder family in ConfigurationManager.

Required None

4 Define alternate search queries . Optional

Required if you donot want to usethe baselinesearch queries.

5

Configure default values for Cal-ibration Template and CalibrationEvent Records by accessing the Cal-ibration Setup Defaults family inConfiguration Manager.

Required None



Upgrading Calibration Management to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0Calibration Management will be upgraded from V3.6.0.0 to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.

V3.5.1Calibration Management will be upgraded from V3.5.1 to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.

V3.5.0 SP1 LPCalibration Management will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automaticallywhen you upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.





Calibration Management Security Groups andRolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Calibration Administrator MI Safety Admin

MI Calibration User

MI Safety Admin

MI Safety Power

MI Safety User

Note: Any Security User who is a member of the MI Calibration Administrator Secur-ity Group should also be added to MI Devices Administrators Security Group. Mem-bers of the MI Calibration User Security Group should also be added to MI DevicesPower Users Security Group. This will allow Calibration users to perform automatedcalibration.


Family MI Calibration Admin-istrator

MI CalibrationUser

Entity Families

Alert View, Update, Insert,Delete


Calibration Recommendation View, Update, Insert,Delete View, Update, Insert

Calibration Setup Defaults View, Update, Insert,Delete View

Calibration Task View, Update, Insert,Delete





MI CalibrationUser

Calibration Template View, Update, Insert,Delete View

Calibration Template Defaults View, Update, Insert,Delete View

Calibration Template Detail View, Update, Insert,Delete View

Calibration Template Detail, Ana-lyzer


Calibration (Event) View, Update, Insert,Delete


Calibration Result View, Update, Insert,Delete


Equipment View View

Functional Location View View

Reference Document View, Update, Insert,Delete View

SAP System View None

Task View, Update, Insert,Delete None

Task Types View, Update, Insert,Delete View

Test Equipment View, Update, Insert,Delete


Test Equipment History View, Update, Insert,Delete


Work History View View

Work History Detail View View


Equipment Has Equipment View View

Functional Location Has Equipment View View




MI CalibrationUser

Functional Location Has FunctionalLocation(s) View View

Has Associated Recommendation View, Update, Insert,Delete View

Has Calibration View, Update, Insert,Delete


Has Calibration Results View, Update, Insert,Delete


Has Consolidated Recom-mendations


Has Driving Recommendations View, Update, Insert,Delete View

Has Event Detail View View



Has Reference Documents View, Update, Insert,Delete


Has Standard Gas View, Update, Insert,Delete


Has Standard Gas Details View, Update, Insert,Delete


Has Superseded Recommendations View, Update, Insert,Delete View

Has Task Revision View, Update, Insert,Delete None

Has Tasks View, Update, Insert,Delete


Has Templates View, Update, Insert,Delete


Has Template Detail View, Update, Insert,Delete View

Has Test Equipment View, Update, Insert,Delete





MI CalibrationUser

Has Work History View View

Test Equipment Has Equipment View, Update, Insert,Delete


Test Equipment Has History View, Update, Insert,Delete




Deploying Failure Modes and Effects Analysis(FMEA)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Failure Modes and Effects Analysis(FMEA) for the First TimeDeploying and configuring FMEA for the first time includes completing multiple steps,which are outlined in the table in this topic. The steps in this section of the doc-umentation provide all the information that you need to deploy and configure FMEA ontop of the basic Meridium Enterprise APM system architecture.

Whether a step is required or optional is indicated in the Required/Optional cell. Stepsare marked as Required if you must perform the step to take advantage of FMEA func-tionality.

The person responsible for completing each task may vary within your organization. Werecommend, however, that the steps be performed in relatively the same order in whichthey are listed in the table.


1

Review the FMEA data modelto determine which rela-tionship definitions you willneed to modify to includeyour custom equipment andlocation families.

Optional

This task is necessaryonly if you store equip-ment and locationinformation in familiesother than the baselineEquipment and Func-tional Location fam-ilies.

2


Required None



Upgrading Failure Modes and Effects Analysis(FMEA) to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0FMEA will be upgraded from V3.6.0.0.0 to V4.1.0.0 automatically when you upgrade thecomponents in the basic Meridium Enterprise APM system architecture. No additionalsteps are required.

V3.5.1FMEA will be upgraded from V3.5.1 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.

V3.5.0 SP1 LPFMEA will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automatically when you upgradethe components in the basic Meridium Enterprise APM system architecture. No addi-tional steps are required.

V3.5.0FMEA will be upgraded from V3.5.0 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.


1Assign Security Usersto the MI RCM ViewerSecurity Group.

Y None

2

Add values to theRecommendedResource System CodeTable.

Y

This System Code Table is used to pop-ulate the Recommended Resource fieldin RCM FMEA Recommendationrecords.



Failure Modes and Effects Analysis (FMEA) Secur-ity Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI RCM User

MI RCM ViewerMI Strategy User

MI RCM User

MI RCM ViewerMI Strategy Power

MI RCM User

MI RCM Viewer

MI ASI Administrator

MI Strategy Admin


Family Caption MI RCMUser

MIRCMViewer

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




Task History

Note: The Task History relationship family is inactive in thebaseline Meridium Enterprise APM database.

View, Update,Insert, Delete View


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 inactivein the baseline Meridium Enterprise APM database.


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 willhave access to ALL records involved in FMEA Analyses. In addition to these baseline priv-ileges, which you can grant by assigning users to the MI RCM User Security Group, youwill need to grant FMEA users permission to the Equipment or Functional Location fam-ily if it is related to the RCM FMEA Asset family through the Is RCM FMEA Asset rela-tionship.

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

l The current page on your desktop (create shortcut), in an email message, or on aHome Page.

l Help: Displays the context-sensitive Help topic for the FMEA Team Members pagefor FMEA Templates.



Deploying Hazards AnalysisThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Hazards Analysis for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the Hazards Analysisdata model to determine whichrelationship definitions you willneed to modify to include yourcustom equipment or locationfamilies. Modify any rela-tionship definitions as neededvia the Configuration Managerapplication.

Optional

Required if you storeequipment and loc-ation information infamilies other thanthe baseline Equip-ment and FunctionalLocation families.

2

Assign the desired SecurityUsers to one or more HazardsAnalysis Security Groups in Con-figuration Manager.

Required

Users will not beable to access Haz-ards Analysis unlessthey have per-missions to the Haz-ards Analysisfamilies.

3 Define alternate search queries. Optional

Required if you donot want to use thebaseline search quer-ies.

4

Manage the types of Deviationsin a HAZOP Analysis. To do so,add a code to the MI_HAZOP_DEVIATIONS system code table.

Optional

Required if you wantto add another valueto the list of defaultvalues in the Devi-ation/Guideword listin the HAZOP Devi-ation datasheet.




5 Activate the SIS Managementlicense. Optional

Required if you wantto take advantage ofthe integrationbetween the SIS Man-agement moduleand HazardsAnalysis.

6Assign Security Users to the MISIS Administrator or MI SISEngineer Security Group.

Optional

Required if you wantto take advantage ofthe integrationbetween the SIS Man-agement moduleand HazardsAnalysis.



Upgrading Hazards Analysis to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.



1Activate theSIS Management license .

No

Required if you want to takeadvantage of the integrationbetween the SIS Management mod-ule and Hazards Analysis.

2

Assign Security Users to theMI SIS Administrator or MISIS Engineer Security Group.

No




No


2


No




No





2


No




No


2

Assign Security Users to theMI SIS Administrator or MISIS Engineer SecurityGroup.

No




No


2


No




Hazards Analysis Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI HA Administrator MI Safety Admin

MI HA OwnerMI Safety Admin

MI Safety Power

MI HA Facilitator

MI Safety Admin

MI Safety Power

MI Safety User

MI HA Member

MI Safety Admin

MI Safety Power

MI Safety User


Family MI HA Admin-istrator

MI HAOwner MI HA Facilitator MI HA

Member

Entity Families

Alert View, Update,Insert, Delete

View,Update,Insert,Delete

View, Update, Insert,Delete None

Consequence View, Update,Insert, Delete View View View

Equipment View View View View





Member

Functional Loca-tion View View View View

Hazards Analysis View, Update,Insert, Delete



Hazards AnalysisCause

View, Update,Insert, Delete



Hazards AnalysisConsequence




Hazards AnalysisSafeguard




Hazards AnalysisSystem/Node




HAZOP Deviation View, Update,Insert, Delete



Human Resource View, Update,Insert, Delete



Independent Pro-tection Layer




InstrumentedFunction View View View View

Probability View, Update,Insert, Delete View View View





Member

Protection Level View, Update,Insert, Delete

View,Insert View, Insert View,

Insert

Reference Docu-ment




Risk Assessment View, Update,Insert, Delete



Risk AssessmentRecommendation




Risk Category View, Update,Insert, Delete



Risk Matrix View, Update,Insert, Delete



Risk Rank View, Update,Insert, Delete



Risk Threshold View, Update,Insert, Delete View View View

Site Reference View View View View

What If View, Update,Insert, Delete








Member

Analysis HasHuman Resource




Cause Has Con-sequence




Cause RevisionHas ConsequenceRevision




Consequence HasSafeguard




Consequence Revi-sion Has Safe-guard Revision




Deviation\What IfHas Cause




Deviation\What IfRevision HasCause Revision




Equipment HasEquipment View View View View

Functional Loca-tion Has Equip-ment

View View View View

Functional Loca-tion Has Func-tional Location

View View View View





Member

Has Hazards Ana-lysis Revision




Has HAZOP Refer-ence




Has IF View, Update,Insert, Delete



Has FunctionalLocation




Has Recom-mendations




Has ReferenceDocuments




Has Reference Val-ues

View, Update,Insert, Delete View View View

Has Risk View, Update,Insert, Delete



Has Risk Category View, Update,Insert, Delete



Has Risk Matrix View, Update,Insert, Delete







Member

Has Site Reference View, Update,Insert, Delete



Hazards AnalysisHas Assets




Hazards AnalysisRevision Has Sys-tems/Nodes Revi-sion




Is IndependentProtection Layer




Mitigates Risk View, Update,Insert, Delete



Safety AnalysisHas Equipment




Safeguard Revi-sion Has IPL Revi-sion




System/Node HasDeviations/WhatIfs




System/Node HasDeviations/WhatIfs Revision






Deploying Inspection ManagementThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.

l Meridium Enterprise APM Installation and Upgrade



Deploying Inspection Management for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the Inspection Man-agement data model todetermine which rela-tionship definitions you willneed to modify to includeyour custom equipment andlocation families. Modifyany relationship definitionsas needed via ConfigurationManager.

N

Required if you store equipmentand location information in fam-ilies other than the baseline Equip-ment and Functional Locationfamilies.

2

Assign Security Users to oneor more of the InspectionManagement SecurityGroups.

Y

Security Users will need per-missions to the Inspection Man-agement families before they canuse the Inspection Managementfeatures.

3Set the Asset Query Path set-ting to the baseline AssetQuery.

Y

In the baseline database, this set-ting is not defined. The doc-umentation assumes that you areusing the product according tothe Meridium Enterprise APMBest Practice. Therefore, weassume that you will set the AssetQuery Path setting to the baselineAsset Query.



4 Modify baseline ApplicationConfiguration settings. N

The following Application Con-figurations are defined in thebaseline database: Asset QueryPath; Associated RelationshipFamily; Published Query Path;Summary Query Path; AlertsQuery Path; Asset Is Successor;Profile Configuration; MethodConfiguration; Strategy Rule Con-figuration. You can modify theseApplication Configurations if youwant.

5

Assign roles to users whoshould be able to completetasks in Inspection Man-agement.

Y None

6Define the Inspection Profilefor each piece of equipmentthat you will inspect.

N

Required if you plan to createInspection records in baselinefamilies other than the Checklistssubfamilies.

7 Modify the baseline Assetquery. N

Required if you want Inspectionrecords to be linked to records ina family other than the Equipmentfamily.

8Define Event Configurationsfor any new Inspection fam-ilies that you have created.

N

Required if you have created cus-tom Inspection families that youwant to use within InspectionManagement.

9 Assign certifications tousers. N None

10 Group inspection work intoWork Packs. N None

11 Define Time-Based Inspec-tion settings. N None



Upgrading Inspection Management to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0Inspection Management will be upgraded from V3.6.0.0.0 to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.

V3.5.1Inspection Management will be upgraded from V3.5.1 to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.


1 Define Time-Based Inspection settings . N None




1

If you have added System Codes to the MI_INSPECTION_TYPE System Code Table, createTask Types records representing those task

types, and set the value in the Referencefield to Inspection.

N

Required if youhave added Sys-tem Codes to theMI_INSPECTION_TYPE SystemCode table.




Inspection Management Security Groups andRolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Inspection

MI Mechanical Integrity Administrator

MI Mechanical Integrity Power

MI Mechanical Integrity User

The baseline family-level privileges that exist for this Security Group is summarized inthe following table.

Family Privileges

Entity Families

Alert View, Insert, Update, Delete

Certification View, Insert, Update, Delete

Checklist Finding View, Insert, Update, Delete

Conditional Alerts View, Insert, Update, Delete

Corrosion View, Insert, Update, Delete

Equipment View, Insert, Update, Delete

Event View, Insert, Update, Delete

Finding View, Insert, Update, Delete

Human Resource View

Inspection Method View, Insert, Update, Delete

Inspection Profile View, Insert, Update, Delete



Family Privileges

Inspection Team Member View, Insert, Update, Delete

Potential Degradation Mechanisms View

RBI Degradation Mechanisms View

Recommendation View, Insert, Update, Delete

Reference Document View, Insert, Update, Delete

Resource Role View, Insert, Update, Delete

SAP System View

Security User View

Strategy View, Update

Task View, Insert, Update, Delete

Taxonomy References View

Time Based Inspection Interval View, Insert, Update, Delete

Time Based Inspection Setting View, Insert, Update, Delete

Work Pack View, Insert, Update, Delete


Belongs to a Unit View, Update, Insert, Delete

Checklist Has Finding View, Insert, Update, Delete

Has Certifications View, Insert, Update, Delete

Has Degradation Mechanisms View

Has Findings View, Insert, Update, Delete

Has Inspection Method View, Insert, Update, Delete

Has Inspection Profile View, Insert, Update, Delete

Has Inspection Scope View, Insert, Update, Delete

Has Inspections View, Insert, Update, Delete

Has Potential Degradation Mechanisms View

Has Recommendations View, Insert, Update, Delete

Has Reference Documents View, Insert, Update, Delete



Family Privileges

Has Roles View, Insert, Update, Delete

Has Sub-Inspections View, Insert, Update, Delete

Has Tasks View, Insert, Update, Delete

Has Task History View, Insert

Has Task Revision View, Insert

Has Team Member View, Insert, Update, Delete

Has Taxonomy Hierarchy Element View

Has Taxonomy Mapping View

Has Time Based Inspection Interval View, Insert, Update, Delete

Has Work Pack View, Update, Insert, Delete

Is a User View

Is Planned By View, Insert, Update, Delete

Is Executed By View, Insert, Update, Delete

Note: Security privileges for all modules and catalog folders can be found in theAPM documentation.

Note that:

l The family-level privileges granted to the following families are also spread to allof their subfamilies:

l Eventl Taxonomy References

l The Has Task History relationship family is inactive in the baseline Meridium Enter-prise APM database.

l In addition to the families listed in the preceding table, members of the MI Inspec-tion Security Group have View privileges to additional families to facilitate integ-ration with the Risk Based Inspection module. Since these families are not usedelsewhere in Inspection Management, they are not listed in this table.

Note: As part of implementing Inspection Management, you will decide whetheryou want to link Inspection records to Equipment records, Functional Locationrecords, 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 priv-ileges to the Functional Location family and the Functional Location Has Equipmentrelationship family.





Deploying Metrics and ScorecardsThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Metrics and Scorecards for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.





1

Deploy SQL Server Analysis Services onthe SQL Server Analysis Server (Version12 or Version 14) machine.

Deploying SQL Server Analysis Serviceson the SQL Server Analysis Servermachine includes the following steps:

1. Install SQL Server Analysis Ser-vices.

2. Deploy Work History Analysis Ser-vices database.

This is a replacement ofMeridium_Event_Analysis database,and Equipment and Functional Loca-tion Work History cubes deliveredas packaged solution.

3. Create a Windows User on theAnalysis Server or in your organ-ization’s Active Directory.

The user name requires min-imum privileges and will only beused by the Meridium EnterpriseApplication Server to connect tothe cubes. It is recommendedthat:

l The password for this usershould never expire

l The user should be restric-ted to change password

l The user should be restric-ted to log in to others serv-ers. Ex: meridium_ssas_user

4. Add the user created in Step 3 toa role on all SQL Analysis Servicesdatabases you want to access inMeridium Enterprise APM soft-ware.

The role should have read anddrill through permissions. Work

Y

This step assumes thatyou have read the Met-rics and Scorecardshardware and soft-ware requirementsand that you haveobtained the SQLServer Analysis Ser-vices softwareinstaller.




History database already has aView role defined, you should addthe user to this role. For moreinformation, consult the MSDNdocumentation regarding Rolesand Permissions for Analysis Ser-vices.

5. Configure SQL Server AnalysisServer for HTTP or HTTPS accessusing basic authentication.

HTTPS is recommended withbasic authentication. For moreinformation, consult the MSDNdocumentation regarding con-figuring the HTTP access to Ana-lysis Services on InternetInformation Service (IIS).

2Configure a cube for usage metricstracking on the SQL Server AnalysisServer.

N

Required if you willuse Metrics and Score-cards to view theusage metrics in acube.

3 Schedule cubes for processing on theSQL Server Analysis Server. Y None

4If needed, migrate SQL Server cubesfrom one version of SQL Server Ana-lysis Services to another.

Y None

5 Assign Security Users to the Metricsand Scorecards Security Groups. Y None

6

Create Analysis Services Cube recordsfor each cube that has been defined inSQL Server Analysis Services.

Since Meridium Enterprise APM usesHTTP connection to connect to thecube, with server address you need toprovide credentials of the user createdin Step 1 Task 3.

Y None




7Grant Security Users and Groupsaccess rights to Analysis Services Cuberecords.

Y None

8 Configure privileges for KPI. Y None

9 Configure privileges for Scorecards. Y None



Upgrading Metrics and Scorecards to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0The DBUMS utility will upgrade existing Scorecards and KPIs seamlessly. However, toupgrade metric views, ensure that the user running the upgrade utility has read per-missions on the cubes associated to metric views and the cubes are active.

V3.5.1Metrics and Scorecards will be upgraded from V3.5.1 to V4.1.0.0 automatically when youupgrade the components in the basic Meridium Enterprise APM system architecture. Noadditional steps are required.


1

Migrate your SQL Server Ana-lysis Services database andcubes to SQL Server AnalysisServices 2012.

N

Required if you were previouslyusing SQL Server Analysis Services2008 R2 and want to useSQL Server Analysis Services 2012instead.


1

Migrate your SQL Server Ana-lysis Services database andcubes to SQL Server AnalysisServices 2012.

N

Required if you were previouslyusing SQL Server Analysis Services2008 R2 and want to useSQL Server Analysis Services 2012instead.

V3.4.5




1

Migrate your SQL Server AnalysisServices database and cubes toeither of the following sup-ported SQL Server Analysis Ser-vices versions:

l 2008 R2

l 2012

N

Required if you were pre-viously using SQL Server Ana-lysis Services 2005.

This step is optional if youwere previously using SQLServer Analysis Services 2008R2 and want to use SQLServer Analysis Services 2012instead.

2Create a master scheduled itemfor managing automatic KPIupdates.

YThis step is necessary for sup-porting automatic KPIupdates.



About Configuring a Cube for Usage Metrics Track-ingYou can track the usage of users in your system. Usage metrics are stored in the MI_USAGE_METRICS system table. When a user logs in to Meridium Enterprise APM, actionsfor which usage metrics tracking has been enabled will be stored for that session andsaved in batch to the MI_USAGE_METRICS table when the user logs out of MeridiumEnterprise APM.

The following actions can be recorded in the MI_USAGE_METRICS table:

l Login.l Logout.l Session time.l URL visit.

The following columns of data are stored in the MI_USAGE_METRICS table:

l USME_KEY: The key value assigned to the action to identify it in the usage metricstable.

l USME_EVENT_TYPE_DVD: The type of event (login, logout, session time, or URLvisit).

l SEUS_KEY: The key value associated with the Security User who performed theaction.

l USME_EVENT_DT: The date and time the action was performed.l USME_EVENT_DESC_TX: A description of the action. For URL visits, this column

stores the URL.l USME_MEASR_NBR: For session time entries, a numeric value that represents the

session time.

Note: Usage metrics are recorded only for activities performed via the MeridiumEnterprise APM. Usage metrics are not recorded for activities performed in theMeridium Enterprise APM Administrative Applications.

To view the usage metrics that have been tracked for your system, you must create acube based upon the MI_USAGE_METRICS table. After you create the cube, you must cre-ate a join between the MI_USAGE_METRICS table and the MIV_MI_IS_A_USER table. Youmust also join the MIV_MI_IS_A_USER table to the MIV_MI_HUMAN_RESOURCE table.

Note: Before you can use the cube in the Metrics and Scorecards module, youmust enable usage metrics tracking via the Monitoring page in Configuration Man-ager.



About Scheduling Cubes for ProcessingAn Analysis Services cube is a combination of measures and dimensions that togetherdetermine how a set of data can be viewed and analyzed. A cube is a static object and ini-tially represents the data that existed in Analysis Services for the selected measures anddimensions when the cube was created. To keep a cube current, it must be processedregularly, whereby the cube is updated with the most current data in Analysis Services.

To make sure that a cube always provides users with the most current data, you shouldschedule it for processing regularly, usually on a daily basis. One way to process cubesand shared dimensions successfully is to do so manually on the Analysis Server. Usingthis method, you can process shared dimensions first, and then process the relatedcubes. Processing cubes manually, however, is not a viable option if you have manycubes that you want to process on a daily basis.

Instead, a preferable option would be to schedule cubes for processing using DataTransformation Services (DTS). This functionality is available in the SQL Server BusinessIntelligence Development Studio, which is included in SQL Server Standard Edition. Fordetails on creating a DTS package that can be used to process objects according to a cus-tom schedule, see your SQL Server documentation.



Install SQL Server Analysis Services on the ServerSQL Server Analysis Services is the foundation for the Meridium Enterprise APM Metricsand Scorecards module because it serves as a storage and management mechanism forcubes, which can then be accessed and viewed via the Meridium Enterprise APM. To sup-port Metrics and Scorecards features, SQL Server Analysis Services must be installed onthe machine that will serve as the Analysis Server. The Analysis Server must be set up asa machine that is separate from the Meridium Enterprise APM Application Server.

Where Does This Software Need to Be Installed?

SQL Server Analysis Services must be installed on the machine that will function as theAnalysis Server. You do not need to install any SQL Server components on the Applic-ation Server to support the Metrics and Scorecards functionality.

Performing the Installation

SQL Server Analysis Services can be installed using the SQL Server Standard Editioninstallation package, which you may have received from Meridium, Inc. or from a third-party vendor, depending upon the licensing options you selected when you purchasedthe Meridium Enterprise APM product. Instructions for performing the installation canbe found in the documentation included in the SQL Server Standard Edition installationpackage.

Creating the Analysis Services Database, Data Source, andCubes

In addition to creating the Analysis Services database, data source, and cubes, the cubesmust be processed before they will be available for use in the Meridium Enterprise APMsystem. For details on completing these tasks, consult your SQL Server documentation.



Migrate SQL Server CubesIf you are upgrading from a previous version of Meridium Enterprise APM and you haveexisting Metrics and Scorecards objects (e.g., Metric Views and KPIs) that are based uponSQL Server 2005 or SQL Server 2008 R2 Analysis Services cubes, you may be able tomigrate your cubes while maintaining the proper functioning of your existing MeridiumEnterprise APM objects.

l If you have SQL Server Server 2008 cubes, you must migrate them to SQL Server2012.

l If you have SQL Server 2012 cubes, you can migrate them to SQL Server 2014.

The following workflow provides a general overview of the process for migrating cubesfrom an older version of SQL Server Analysis Services to a newer version of SQL ServerAnalysis Services. For more details, you should see your SQL Server documentation.

ŗIMPORTANT: Depending upon the complexity of your cubes, you may or may notbe able to migrate them successfully. We recommend that you attempt to migratethem using the following procedure. If you review the cubes after the migration anddetermine that the migration was not successful, the cubes will need to be rebuilt. Inthat case, any KPIs and Metric Views that were based upon those cubes must also berebuilt.

Steps

1. On the SQL Server Analysis Services Server where the older version of SQL ServerAnalysis Services is installed, open the SQL Server Management Studio window.

2. Connect to the SQL Sever Analysis Services database that you want to upgrade.

3. In the Object Explorer pane, right-click Databases, and select Backup.

The Backup Database - <Database Name> window appears, where <DatabaseName> is the name of the database that you want to upgrade.

4. To the right of the Backup file text box, select the Browse button, and specify thelocation where the database will be backed up.

5. Specify any additional settings, and then select OK.

The selected database is saved to an .ABF file in the specified location.

6. Open the SQL Server Management Studio window for the new version of SQLServer Analysis Services.

7. In the Object Explorer pane, right-click Databases, and select New Database.

The New Database window appears.

8. In the Database name cell, enter a name for the database that you are migrating



to the new version of SQL Server Analysis Services.

9. Specify any additional settings, and then select OK.

The specified database is created, and a corresponding node appears in theObject Explorer pane.

10. Right-click the node representing the new database, and then select Restore.

The Restore Database window appears.

11. In the Backup file cell, enter the file path or select the Browse button and nav-igate to the database file that you backed up in step 5.

12. Specify an additional settings, and then select OK.

Your SQL Server Analysis Services database is migrated to the new SQL Server Ana-lysis Services version.

13. In the Meridium Enterprise APM, in the Metrics and Scorecards module, modifythe remaining properties of each Analysis Services Cube record, including select-ing the appropriate new SQL Server Analysis Server. You can do by using the Man-age Cubes page in the Metrics and Scorecard module.

14. View existing objects (e.g. Metric Views and KPIs) that are based upon themigrated cubes to ensure that the correct data is being displayed. If the correctdata is not displayed, rebuild the cubes and the objects that are based upon them.For details on rebuilding cubes, see your SQL Server documentation.



Deploy the Work History Cube

Steps

1. Create a copy of the Cubes folder from the Release CD to a folder in SQL ServerAnalysis Services Server.

2. In the copied Cubes folder, select the Work History folder.

The folder contains following files:

l Work History.asdatabasel Work History.configsettingsl Work History.deploymentoptionsl Work History.deploymenttargets

3. Run the Analysis Services Deployment Wizard program.

The Welcome page appears.

4. Select Next.

5. When the wizard prompts you to choose the database file, navigate to the WorkHistory folder, and then select the file Work History.asdatabase.

6. Run through all steps of the wizard to deploy the Work History database to SQLServer Analysis Services Server.

For more information, consult the MSDN documentation regarding Analysis Ser-vices Deployment Wizard.



Metrics and Scorecard Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Metrics Administrator MI Foundation Admin

MI Metrics User MI Foundation User

Everyone

MI Foundation Admin

MI Foundation Power

MI Foundation User


Family MI MetricsAdministrator

MI Met-rics User Everyone

Entity Families

Analysis ServicesCube

View, Update,Insert, Delete View View

KPI View, Update,Insert, Delete


View, Update, Insert, Delete

KPI Measurement View, Update,Insert, Delete



Scorecard View, Update,Insert, Delete





Family MI MetricsAdministrator

MI Met-rics User Everyone


Has KPI Meas-urement




Has Privileges View, Update,Insert, Delete



Has Sub Indicators View, Update,Insert, Delete



Is Used By Score-card




In addition to performing functions associated with the family-level privileges describedin this table, members of the MI Metrics Administrator Security Group:

l Can manage cube privileges by granting view access to the users.l Has full access to all KPIs, Scorecards, and Cubes without needing to be granted

additional privileges via the Meridium Enterprise APM.



Deploying Policy DesignerThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Policy Designer for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Assign the neededSecurity Users toone or more PolicyDesigner SecurityGroups.

Y None

2

On the MeridiumEnterpriseAPM Server, startthe Policy Exe-cution Service.

Y

If your system architecture contains morethan one Meridium Enterprise APM Server,you must complete this step for everyserver in the load-balanced cluster thatyou want to use for policy execution.

3

On the MeridiumEnterpriseAPM Server, startthe Policy TriggerService.

Y

If your system architecture contains morethan one Meridium Enterprise APM Server,you must first configure the Policy TriggerService on each server to specify the nameof the load-balanced server cluster thatyou want to use for policy execution.

4On the MeridiumEnterprise APMServer, reset IIS.

Y None

5

On the MeridiumProcess Data Integ-ration Server, startor restart the Pro-cess Data Integ-ration Service.

N Required only if you want to use OPC Tagrecords in your policies.



Upgrading Policy Designer to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

If your system architecture contains multiple servers to process policy executions, thesesteps assume that you have configured them according to your company's preferencefor server load-balancing.


1On the Meridium Enterprise APM Server, start orrestart the Policy Execution Service.

Y None

2

If your system architecture contains more than oneMeridium Enterprise APM Server, you must first con-figure the Policy Trigger Service on each server tospecify the name of the load-balanced servercluster that you want to use for policy execution.

Y None

3 Start or restart the Policy Trigger Service. Y None

4 On the Meridium Enterprise APM Server, reset IIS. Y None

5On the Meridium Process Data Integration Server,start (or restart if it is already started) the ProcessData Integration Service.

Y

Requiredonly if youwant touse OPCTagrecords inyourpolicies.



Y None




2


Y None




Y




Y None

2


Y None







Y




Y None

2


Y None




Y




Y None




2


Y None




Y







Services Summary
































About Configuring Policy ExecutionPolicy designers can configure a policy to be executed on a schedule or automaticallywhen records or reading values associated with the policy are updated. This topicdescribes the ways that the items configured in the first-time deployment workflow facil-itate each type of policy execution.

Note: Only the active instances of active policies are executed.

Automatic Execution

When records or reading values associated with the policy are updated, the MeridiumEnterprise APM Server adds messages to the policy trigger queue. The Policy Trigger Ser-vice monitors the trigger queue and sends any messages to the appropriate policy exe-cution queue. Finally, the corresponding Policy Execution Service executes the policiesassociated with the records or reading values that were updated.

Scheduled Execution

When a policy is due, the scheduled job adds a message to the policy trigger queue. ThePolicy Trigger Service monitors the trigger queue and sends messages to the appro-priate policy execution queue. Finally, the corresponding Policy Execution Serviceexecutes the policies that are due.



Configure the Policy Trigger Service

Steps

1. On the Meridium Enterprise APM Server, navigate to the folder where the PolicyTrigger Service files are installed. If you installed the software in the default loc-ation, you can locate this file in the folder C:\Program Files\Meridium\Services.

2. Open the file Meridium.Policies.Service.exe.config in an application that you canuse to modify XML script (e.g., Notepad).

3. Within the <executionServers> tags, locate the following text:

<add url="http://localhost/Meridium" />

4. Within the add url attribute:l If you have only one Meridium Enterprise APM Server in your system archi-

tecture, accept the default value (i.e., localhost).-or-

l If you have more than one Meridium Enterprise APM Server in your systemarchitecture, replace localhost with the name of the server cluster that youwant to use for policy executions.


Your settings will be applied when the Policy Trigger Service is started or restarted.



Configure Multiple Meridium EnterpriseAPM Servers for Policy ExecutionDepending on the number of policies that you need to manage in your system, you mayhave multiple Meridium Enterprise APM Servers to process policy executions. Based onyour company’s preference for server load balancing, you can configure your MeridiumEnterprise APM System Architecture using global load balancing or isolated load bal-ancing.

Regardless of the approach you use, you must fully configure each Meridium EnterpriseAPM Server according to the steps for deploying the basic Meridium Enterprise APM sys-tem architecture. In addition, each Meridium Enterprise APM Server must be configuredto use the same instance of Redis.

Global Load Balancing

In global load balancing, you configure all Meridium Enterprise APM Server(s) to processpolicy executions in a single load-balanced cluster. In this scenario, an increase in activ-ity from any server can be absorbed across all servers in your system architecture.Because there is only one cluster to manage in this scenario, this is the simpler con-figuration to set up and manage.

In this scenario, you must:

l Configure the Policy Trigger service on all Meridium Enterprise APM Servers to spe-cify the name of the cluster.

l Start the Policy Execution Service on all Meridium Enterprise APM Servers.



Isolated Load Balancing

In isolated load balancing, you configure designated Meridium Enterprise APM Server(s)to process policy executions in a separate load-balanced cluster from other MeridiumEnterprise APM Server(s). In this scenario, the policy execution processes are isolatedfrom the Meridium Enterprise APM Server processes, therefore preventing an increasein activity in one cluster from negatively impacting the processes of the other.

In this scenario, you must:

l Configure the Policy Trigger service on all Meridium Enterprise APM Servers to spe-cify the name of the cluster used for policy executions.

l Start the Policy Execution Service on only the Meridium Enterprise APM Servers inthe cluster designated to process policy executions.



Policy Designer Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Policy DesignerMI Health Power

MI Health Admin

MI Policy User MI Health User

MI Policy Viewer None


Family MI Policy Designer MI Policy User MI PolicyViewer

Entity Families

Health IndicatorValue

View, Update, Insert,Delete None View

Policy View, Update, Insert,Delete View View

Policy Event View, Update, Insert,Delete View, Update View

Policy Instance View, Update, Insert,Delete


Policy Recom-mendation

View, Update, Insert,Delete View, Update View


Has Event View, Update, Insert,Delete View, Update View



Deploying Process Data Integration (PDI)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Process Data Integration (PDI) for theFirst TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have already con-figured the Meridium Enterprise APM Server on a separate machine.


Note: These steps assume that your system architecture contains only one ProcessData Integration Server and one OPC Server. If your system architecture contains morethan one Process Data Integration Server and OPC Server, you must install and con-figure the Process Data Integration Service on each Process Data Integration Servermachine.


1

Ensure that your OPC Server andprocess historian are configuredaccording to the PDI systemrequirements.

Y None

2

Review the server roles that areconfigured for the Process DataIntegration Server in theMeridium Enterprise APM testingenvironment, and configure roleson your Process Data IntegrationServer accordingly.

Y None

3Assign Security Users to one ormore of the Process Data Integ-ration Security Groups.

Y None

4

In Meridium Enterprise APM, cre-ate an OPC System record to rep-resent the OPC-compliant systemfrom which you want to retrievedata.

Y None




5On the Process Data IntegrationServer, install the Process DataIntegration Service.

Y

We recommend that the OPCServer is the same machineas the Process Data Integ-ration server. However, if it isa separate machine, refer tothe PDI system requirementsfor information on addi-tional configuration that isrequired.

6

On the Process Data IntegrationServer, modify the Process DataIntegration Service configurationfile to specify your OPC Server,the Meridium Enterprise APMServer, Meridium Enterprise APMdatabase, and login credentials.

Y None

7On the Process Data IntegrationServer, start the Process DataIntegration Service.

Y

When you start the service,tags from the configured pro-cess historian are importedautomatically into theMeridium Enterprise APMdatabase as OPC Tagrecords.

8On the Meridium Enterprise APMServer, configure the MeridiumNotification Service for PDI.

Y None


Y None

10

Review the Process Data Integ-ration data model to determinewhich relationship definitionsyou will need to modify toinclude your custom equipmentand location families.

N

Required if you store equip-ment and location inform-ation in families other thanthe baseline Equipment andFunctional Location families.

11 In Meridium APM, link OPC Tagrecords to related asset records. Y None



Upgrading Process Data Integration (PDI) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


1On the Process Data IntegrationServer, upgrade the Process Data Integ-ration Service.

Y None

2

On the Process Data IntegrationServer, modify the Process DataIntegration Service configuration file tospecify your OPC Server, the MeridiumEnterprise APM Server, Meridium Enter-prise APM database, and login cre-dentials.

Y None

3On the Process Data IntegrationServer, start or restart the ProcessData Integration Service.

Y

When you start the ser-vice, tags from the con-figured processhistorian are importedautomatically into theMeridium EnterpriseAPM database as OPCTag records.

4On the Meridium Enterprise APMServer, configure the Meridium Noti-fication Service for PDI.

Y None

5On the Meridium Enterprise APMServer, restart the Meridium Noti-fication Service.

Y None

6In Meridium Enterprise APM, link anynew OPC Tag records to related assetrecords.

Y None

V3.5.1





Y None

2


Y None


Y



Y None


Y None

6In Meridium Enterprise APM, link anynew OPC Tag records to related assetrecords.

Y None



Y None




2


Y None


Y



Y None


Y None

6In Meridium APM, link any newOPC Tag records to related assetrecords.

Y None



Y None




2


Y None


Y



Y None


Y None


Y None



Y None




2


Y None


Y



Y None


Y None


Y None



Process Data Integration Server RolesThe following server roles are configured on the Process Data Integration Server in theMeridium Enterprise APM test environment.

Note: Roles and features can be added via the Add Roles and Features Wizard on aWindows Server machine. To add roles and features, in Server Manager, on the Man-age menu, select Add Roles and Features to open the wizard. Select role-based orfeature based installation and then continue through the wizard.

In the Server Roles section:

l Application Server

In the Role Services section for the Application Server:

l .NET Framework 4.5l TCP Port Sharingl Windows Process Activation Service Support

l Message Queuing Activation, and all featuresl Named Pipes Activation, and all featuresl TCP Activation, and all features






Services Summary
































Install the Process Data Integration ServiceThe following instructions provide details on installing the Process Data Integration Ser-vice using the Meridium Enterprise APM Server and Add-ons installer.

Steps

1. On the machine that will serve as the Meridium Process Data Integration Server,access the Meridium Enterprise APM distribution package, and then navigate tothe folder \\Setup\Meridium Enterprise APM Server and Add-ons.

2. Double-click the file Setup.exe.

The Welcome screen appears.

3. Select Next.

The License Agreement screen appears.

4. Read the License Agreement and, if you agree, select the I accept the terms ofthe license agreement check box. Then, select Next.

The Select Installation Location screen appears.

5. Select Next to accept the default location.

The Select the features you want to install screen appears.

6. Select the Meridium Process Data Integration Service option.

Note: While additional options are available for selection, these options arenot meant to be installed on the Process Data Integration Server. These instruc-tions assume that you want to install only the Meridium Process Data Integ-ration Service software. When this software is installed, the Meridium EnterpriseAPM System Administration Tool will also be installed automatically.

7. Select Next.

Meridium Enterprise APM performs a check to make sure that your machine con-tains the required prerequisites for the features that you want to install.

l If one or more prerequisites are missing on the machine, a dialog box willappear, explaining which prerequisites are missing. If this occurs, close theinstaller, install the missing prerequisite, and then run the installer again.

l If all the prerequisites for the selected components are installed on themachine, or you have selected components that do not require any pre-requisites, the Complete the Installation screen appears.

8. Select Install.



The Setup Status screen appears, which displays a progress bar that shows theprogress of the installation process. After the progress bar reaches the end, a mes-sage appears, indicating that your server is being configured. After your server isconfigured, the Installation is Complete screen appears.

You can also select to optionally launch the APM System Administration tool whenthe installer window closes.

9. Select Finish.

You should now refer back to the checklist.



Upgrade the Process Data Integration ServiceThe following instructions provide details on upgrading the Process Data Integration Ser-vice on the Process Data Integration Server. These instructions assume that you are anAdministrator with full access to the Meridium Process Data Integration server machine.

Steps

1. On the machine that will serve as the Meridium Process Data Integration Server,access the Meridium Enterprise APM distribution package, and then navigate tothe folder \\Setup\Meridium Enterprise APM Server and Add-ons.

2. Select the file setup.exe.

A message appears, asking if you want to allow setup.exe to make changes to yourmachine.

3. Select Yes.

The Meridium Enterprise APM Server and Add-ons installer appears, displayingthe Preparing Setup screen. The Preparing Setup screen contains a progress barthat indicates when the installer is ready to upgrade the components on yourmachine.

When the progress bar reaches the end, a message appears, asking if you want toupgrade your server.

4. Select Yes.



The Setup Status screen appears, displaying a progress bar that indicates thestatus of the upgrade process. After the progress bar reaches the end, the Main-tenance Complete screen appears.

You can also select to optionally launch the APM System Administration tool whenthe installer window closes.

5. Select Finish.

You should now refer back to the upgrade checklist.



Configure the Meridium Notification Service forPDIIn order for the Process Data Integration service to work correctly, you must configurethe Meridium Notification Service by modifying the file Meridi-um.Service.Notification.exe.config on the Meridium Enterprise APM Server.

Steps

1. On the Meridium Enterprise APM Server, navigate to the folder where theMeridium Notification Service files are installed. If you installed the software in thedefault location, you can locate these files in the folder C:\Program Files\Meridi-um\Services.

2. Open the file Meridium.Service.Notification.exe.config in an application thatyou can use to modify XML script (e.g., Notepad).

3. If you have not done so already, complete any necessary basic configuration forthe Meridium Notification Service.

4. Within the <notification> tags, within the <notificationSettings>tags, uncom-ment the following text string (i.e., delete the ):



5. Within the <system.serviceModel> tags, within the <client> tags, uncomment thefollowing text string (i.e., delete the ):



6. Within the address attribute, replace PDISERVERNAME with the name or IPAddress of the Process Data Integration Server.

7. If you have only one Process Data Integration Server in your system architecture,save and close the file.

-or

If you have multiple Process Data Integration Servers, complete the followingsteps for each additional server:

a. Copy the string within the <notificationSettings> tags that you uncom-mented in Step 4.

b. Directly after the text that you copied (after the />), paste the copied text.



c. Within the key attribute, specify a unique name for the connection.

d. Within the endPointName attribute, specify a unique name for the endpoint.

e. Copy the string within the <client> tags that you uncommented in Step 5.

f. Within the name attribute, enter the name for the endpoint that you spe-cified in Step d.

g. Modify the address attribute to specify the name or IP Address of the addi-tional Process Data Integration Server.

h. Save and close the file.

8. Start or restart the Meridium Notification Service.

ExampleIf your system architecture has two Process Data Integration Servers, the strings in the<notificationSettings> tags might look like this:

<add key="PDIserver1" serverType="external" endPointName-e="pdiService"/>

<add key="PDIserver2" serverType="external" endPointName-e="pdiService2"/>

...and the corresponding strings in the <client> tags might look like this:

<endpoint name="pdiService" address-s="net.tcp://Matrikon/Meridium/PDI/NotifyHandler" bind-ing="netTcpBinding"contract="Meridium.Core.Common.Contracts.INotificationService"/>

<endpoint name="pdiService2" address-s="net.tcp://OsiPi/Meridium/PDI/NotifyHandler" bind-ing="netTcpBinding"contract="Meridium.Core.Common.Contracts.INotificationService"/>



Configure the Process Data Integration ServiceIn order to use Process Data Integration, you must configure the Process Data Integ-ration Service by modifying the file Meridium.PDI.Service.exe.config on the Meridium Pro-cess Data Integration Server. If you installed the Process Data Integration Service in thedefault location, you can locate this file in the folder C:\Program Files\Meridi-um\Services.

Some modifications can be made using the APM System Administration tool and othermodifications must be made by opening the file in an application that you can use tomodify XML script (e.g., Notepad). The following instructions provide details on makingall required modifications at one time, using both the APM System Administration tooland a text editor.

Note: This configuration file defines several endpoints on the Process DataIntegration Server with URLs and ports that must be accessible from the MeridiumEnterprise APM Server. You should ensure that your firewalls are configured to allowthis access.

Steps

1. On the Meridium Process Data Integration Server, access the APM System Admin-istration tool.

2. In the APM System Administration window, in the Configuration section, clickthe PDI Service link.

Some contents of the Meridium.PDI.Service.exe.config file appear to the right ofthe Configuration section.

3. In the OPCDA and OPCHDA boxes, enter the values that identify your OPC Server.

The following table contains the default values that identify the OPC Servers forthe process historians that have been tested by Meridium, Inc. We recommend,however, that you contact the third-party distributor of your process historian soft-ware to confirm the values that you should use for your system configuration.

Process Historian OPCDA OPCHDA

OSIsoft® PI Server OSI.DA.1 OSI.HDA.1

Matrikon Simulationtool Matrikon.OPC.Simulation.1 Matrikon.OPC.Simulation.1

IP21 Aspen.Infoplus21_DA.1 N/A



Process Historian OPCDA OPCHDA

MatrikonOPC HDAServer for IP21* Matrikon.OPC.IP21.1 Matrikon.OPC.IP21.1

Honeywell Uni-formance® ProcessHistory Database(PHD)

OPC.PHDServerDA.1 OPC.PHDServerHDA.1

*In the Meridium Enterprise APM testing environment, IP21 and MatrikonOPC forIP21 are installed on separate machines.

4. In the OPCDAHOST and OPCHDAHOST boxes:

l If the Process Data Integration Service and OPC software are installed on thesame machine, leave these text boxes empty.-or-

l If the Process Data Integration Service and OPC software are installed on dif-ferent machines, enter the name or IP address of your OPC Server. Note thatwe do not recommend this configuration. For additional information, referto the PDI system requirements.

5. In the Tag Sync Interval box, replace the example value with the frequency (inhours) at which you want the tag synchronization to occur.

6. In the Initial Tag Sync Time box, replace the example value with the date andtime (in UTC) that you want the first scheduled tag synchronization to occur.

Note: This value must be specified using the ISO 8601 standard for UTC dateformats (i.e., the letters T and Z must be included), for example, 2014-01-01T04:00:00Z.

7. In the Max Sync Time box, replace the example value with the maximum lengthof time (in hours) that you want to allow the tag synchronization to run.

Note: The purpose of this setting is to stop a synchronization that is runningsignificantly longer than expected (e.g., because it encountered an error) so thatthe synchronization will start over at the next scheduled time. Therefore, themaximum synchronization time that you allow should be longer than the lengthof time that it takes for tags to synchronize under normal circumstances andshould account for known factors that may extend the synchronization time(e.g., network connection speed).

8. At the bottom of the APM System Administration window, click the Save button.



Your changes are saved to the file Meridium.PDI.Service.exe.config. You must nowopen the actual file to complete the service configuration.

9. Click the Open File link.

10. Within the <meridiumConnections> tags, uncomment the example connectiontag by deleting  from the beginning andend of the string.

11. Within the <meridiumConnections> tags, modify the attributes as described inthe following table.

Within thisattribute... Make this change Notes

connection name

Replace CONNECTION 1with a name to identifythe connection to the data-base.

This value is used only by theconfiguration file. If you areconfiguring connections to mul-tiple data sources, each con-nection name must be unique.

applicationServer

Replace APPSERVER_NAME with the name orIP Address of theMeridium Enterprise APMServer on which the datasource specified in thedatasource attribute isconfigured.

None

datasource

Replace DATASOURCE_NAME with the name ofthe Meridium EnterpriseAPM database to whichyou want to connect.

The data source value is casesensitive and should be typedexactly as it is defined for theMeridium EnterpriseAPM Server in the DataSources section of OperationsManager.

userId

Replace SERVICE_USER_NAME with the User ID ofthe Security User whosecredentials should beused to log in to the spe-cified Meridium Enter-prise APM database.

The user you specify should bea member of the MI ProcessData Integration Service Secur-ity Group.



Within thisattribute... Make this change Notes

passwordReplace PaSsWoRd withthe password for the spe-cified user.

You should not delete the ! infront of the password. Thissymbol is not part of the pass-word itself. Instead, this sym-bol will cause the password tobe encrypted automaticallywhen the service is restarted.

xiServers

Replace OPC System1with the value that existsin the OPC System ID fieldin an OPC System recordin the Meridium Enter-prise APM database.

If multiple OPC System recordsexist to identify multiple OPCServers, you can specify mul-tiple values and separate themwith a semicolon (e.g., "OPCSystem1;OPC System2").


When the Process Data Integration Service is started or restarted, your settingswill be applied and the initial tag synchronization will occur.



Configure Multiple Data SourcesFor each unique Meridium Enterprise APM Server and data source combination thatexists in your architecture, you must specify a separate connection string in thePDI Service configuration file. For example, if your system architecture contains twoMeridium Enterprise APM Servers writing to the same database, regardless of whetherthe same or different data source names are specified on each, you need to configuretwo connection strings.

Steps

1. Configure the first connection by modifying the attributes within <meridi-umConnections> tags, as described in the instructions for configuring the Pro-cess Data Integration Service.

2. Copy the text within the <meridiumConnections> tags (e.g., <connection name-e="CONNECTION 1" applicationServer="" datasource="DATASOURCE_NAME" userId="SERVICE_USER_NAME" password="!PaSsWoRd" />)

3. Directly after the text that you copied (after the />), paste the copied text.

4. Modify the attributes as needed.

Note: The connection name that you specify in each connection string mustbe unique.

5. Repeat these steps for each required connection.



Configure Multiple Process Data Integration andOPC ServersDepending on your specific system architecture, you may have multiple Process DataIntegration and OPC Server machines.

The following diagram illustrates multiple OPC Servers in the standard configurationwhere the OPC Server is the same machine as the Process Data Integration (PDI) Server(i.e., the OPC Server software is installed on the PDI Server).

The following diagram illustrates multiple OPC Servers in an alternative configurationwhere the OPC Servers are separate machines from the PDI Servers.



In either of these scenarios, when you complete the first-time deployment steps for PDI,you must install and configure the Process Data Integration Service on each ProcessData Integration Server machine.

Whether the OPC Servers are the same machine as the Process Data Integration Serversor not, in the Meridium Enterprise APM application, you will create an OPC Systemrecord for each OPC Server (e.g., OPCServer1 and OPCServer2). Then, when you con-figure the Process Data Integration Service, you must specify the appropriate OPC Serverrecord in the xiServers attribute within the meridumConnections tags. For example,the connection string on each machine might look like this:

l On the first Process Data Integration Server: <connection name="EXAMPLE_CONNECTION" applicationServer="APPSERVER_NAME" data-source="DATASOURCE_NAME" userId=" SERVICE_USER_NAME" pass-word="!PaSsWoRd" xiServers="OPCSystem1" />

l On the second Process Data Integration Server: <connection name="EXAMPLE_CONNECTION" applicationServer="APPSERVER_NAME" data-source="DATASOURCE_NAME" userId="SERVICE_USER_NAME" pass-word="!PaSsWoRd" xiServers="OPCSystem2" />



Process Data Integration Security Groups andRolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Process Data Integration Administrator MI Health Admin

MI Process Data Integration Service None

MI Process Data Integration UserMI Health User

MI Health Power


Family MI Process Data Integ-ration Administrator

MI Process DataIntegration Service

MI Process DataIntegration User

Entity Families

OPC Read-ing



OPC Sys-tem

View, Update, Insert,Delete View View

OPC Tag View, Update, Insert,Delete View View


Has OPCReading



Has OPCTag




Deploying Production Loss Analysis (PLA)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Production Loss Analysis (PLA) for theFirst TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.


Step Task Notes

1

Review the PLA data model todetermine which relationshipdefinitions you will need tomodify to include your customequipment and location fam-ilies. Modify any relationshipdefinitions as needed via Con-figuration Manager.

This task is required if you store equipmentand location information in families otherthan the baseline Equipment and Func-tional Location families.

2 Assign Security Users to one ormore PLA Security Groups.

This task is required. Users must have per-missions to the PLA families to use the PLAfunctionality.

3 Change the default currencysymbol .

The currency symbol is set by default to $ and displayed in the following places:

l Default Margin field on the Pro-duction Profile datasheet.

l Production Summary tab of the Pro-duction Loss Analysis Details page.

4 Define all products .

This task is required. You must define allproducts whose production you plan totrack using PLA. Each product is stored in aProduct record.



Step Task Notes

5 Define production units .

This task is required. You must identify theproduction units that produce the productsyou defined in the previous task. A singleproduct can be produced by more than oneproduction unit. A single production unit

can also produce more than one product.

Each production unit is stored in a Pro-duction Unit record, which can be linked toan existing Functional Location record thatcontains more detailed information aboutthe production unit.

6 Define production profiles .

This task is required. For each productionunit that you defined in the previous task,you must identify all the products they pro-duce and information about thoseproducts, such as the maximum demon-strated rate of production and the amountof profit one of those products yields. Thecombination of data about a product andthe corresponding production unit is theproduction profile for that production unit.A production unit will have one productionprofile for each product it produces.

Each production profile is stored in a Pro-duction Profile record, which is linked to thecorresponding Product record and Pro-duction Unit record.



Step Task Notes

7 Define production event codes .

The baseline Meridium Enterprise APMdatabase contains Production Event Coderecords that define a set of basic pro-duction event codes. Therefore, this step isrequired only if you do not want to use thebaseline production event codes or if youwant to use codes in addition to those thatare provided.

You must use production event codes tocategorize the types of events that cancause you to produce less than the max-imum sustained capacity amount. Pro-duction event codes define the cause of lostproduction and answer the question: Whyare we losing production? You can also groupthe types of events by structuring them in ahierarchy. For example, you might groupevent types into planned and unplanned,where planned events are events such asmaintenance down days or employee hol-idays, and unplanned events are eventssuch as equipment failures or natural dis-asters (e.g., floods or hurricanes).

Each event type will be stored in a separateProduction Event Code record.

8 Define impact codes .

The baseline Meridium Enterprise APMdatabase contains Impact Code records thatdefine a set of basic impact codes. There-fore, this step is required only if you do notwant to use the baseline impact codes or ifyou want to use codes in addition to thosethat are provided.

9 Define OEE codes .

The baseline Meridium Enterprise APMdatabase contains OEE Code records thatdefine a set of basic OEE codes. Therefore,this step is required only if you do not wantto use the baseline OEE codes or if youwant to use codes in addition to those thatare provided. For non-baseline codes to beincluded in the OEE Metric View, however,they must be children of the baseline par-ent codes.



Step Task Notes

10Define values that will bemapped to a Production Ana-lysis .

By default, certain PLA values are mappedto the production data in a Production Ana-lysis. If you want to map different or addi-tional PLA values, you can do so bymodifying the All Production Data query.

11

Configure PLA for PDI Integ-ration:

l Define production eventtemplates .

l Link Production Profilerecords to OPC Tagrecords.

This task is required if you want to use theintegration between PLA and the ProcessData Integration feature where ProductionEvent records are created automatically.

12Replace the Top 10 Bad Actorsquery for the PLA Overviewpage.

This task is optional. The Top 10 Bad Actorsquery is used by MeridiumEnterprise APM to populate the Top 10 BadActors graph on the Production Loss Ana-lysis Overview page. In some databases,when viewing this graph, you may receivean error that prevents the graph from pop-ulating correctly. If this error occurs,replace the Top 10 Bad Actors query.



Upgrading Production Loss Analysis (PLA) toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V4.0.0.0Step Task Notes

1

Replacethe Top 10Bad Act-ors queryfor thePLA Over-viewpage.

This task is optional. The Top 10 Bad Actors query is used byMeridium Enterprise APM to populate the Top 10 Bad Actorsgraph on the Production Loss Analysis Overview page. In somedatabases, when viewing this graph, you may receive an errorthat prevents the graph from populating correctly. If this erroroccurs, replace the Top 10 Bad Actors query.

V3.6.0.0.0Step Task Notes

1

On theMeridiumEnterpriseAPM Server,import therequiredbaseline rules.

ŗImportant: This procedure must be completed beforeupgrading the Meridium Enterprise APM Server and AddOns software on the Meridium Enterprise APM Server(s).After completing this procedure, you should return to theupgrade Meridium Enterprise APM workflow. After com-pleting this procedure and the remainder of the upgradeMeridium Enterprise APM workflow, when you are ready toupgrade PLA, proceed to step 2 in this workflow.

2

Confirm thedeployment ofthe ProductionData cube andEquipmentCosts Datacube on theSQL Server Ana-lysis Server.

If you deployed the Production Data cube and EquipmentCosts Data cube on the SQL Server Analysis Server inV3.6.0.0.0, you do not need to configure these again.



Step Task Notes

3

Set thetimezones forthe ProductionUnits.

If the timezones for the Production Units are set, all the Pro-duction Plan records, Plan Data records, and Production Tar-get records will be updated based on the timezone for therespective Production Unit.

Note: You must set the timezones for all the ProductionUnits.

l If you do not set the timezones for the ProductionUnits, and if the Production Plan records exist in thedatabase, the Production Plan records, Plan Datarecords, and Production Target records will beupdated based on the timezone of the user who lastmodified the Production Plan record.

l If you do not set the timezones for the ProductionUnits, and if the Production Plan records do not existin the database, the timezone for the Production Unitwill be updated based on the timezone of the userwho last modified the Production Unit record.


1





Step Task Notes

2


If you deployed the Production Data cube and EquipmentCosts Data cube on the SQL Server Analysis Server in V3.5.1,you do not need to configure these again.

V3.5.0 SP1 LPStep Task Notes

1



2


If you deployed the Production Data cube and EquipmentCosts Data cube on the SQL Server Analysis Server in V3.5.0.SP1 LP, you do not need to configure these again.

V3.5.0



Step Task Notes

1



2




1



2Define OEEcodes .

You can use the baseline OEE Code records that are providedin the Meridium Enterprise APM database. If you do not wantto use the OEE Code records that are provided, you will needto create custom OEE codes to identify the types of lossesyou can incur. Each OEE code will be stored in an OEE Coderecord.



Step Task Notes

3

Define valuesthat will bemapped to aProductionAnalysis .

By default, certain PLA values are mapped to the productiondata in a Production Analysis. If you want to map different oradditional PLA values, you can do so by modifying the All Pro-duction Data query.

4





Production Loss Analysis Security Groups andRolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Production Loss Accounting Administrator MI FE Admin

MI Production Loss Accounting ManagerMI FE Admin

MI FE PowerUser

MI Production Loss Accounting Service MI FE Admin

MI Production Loss Accounting User

MI FE Admin

MI FE PowerUser

MI FE User

The following table lists the default privileges that members of each group have to thePLA entity and relationship families.

FamilyMI ProductionLoss AccountingAdministrator

MI ProductionLoss Account-ing Manager

MI Pro-duction LossAccountingService

MI Pro-ductionLossAccountingUser

Entity Families

Equipment View, Update,Insert, Delete View View View

FunctionalLocation View View View View

Impact Code View, Update,Insert, Delete View View View







Interface Log View, Update,Insert, Delete View View View

OEE Code View, Update,Insert, Delete View View View

Product View, Update,Insert, Delete View View View

ProductionAnalysis

View, Update,Insert, Delete View View View, Update,

Insert, Delete

ProductionData


Insert, DeleteView, Update,Insert

ProductionEvent


Insert, DeleteView, Update,Insert, Delete

ProductionEvent Code

View, Update,Insert, Delete View View View

ProductionEvent Tem-plate


Insert, Delete

ProductionLong RangePlan



ProductionLoss



ProductionLosses

View, Update,Insert, Delete None View, Update,


ProductionPlan


Insert, Delete

ProductionTarget


Insert, Delete

Xi Reading None None View None

Xi Tag View None View None








Analysis Link View, Update,Insert, Delete View View View, Update,

Insert, Delete

Caused by Pro-duction Event



Has Base Pro-duction EventCode



Has Child Pro-duction EventCode


Insert, Delete View

Has ImpactCode



Has Losses View, Update,Insert, Delete View View, Update,


Has OEE Code View, Update,Insert, Delete View View, Update,


Has Product View, Update,Insert, Delete View View, Update,

Insert, Delete View

Has Pro-duction Data



Has Pro-duction Event



Has Pro-duction EventCode



Has Pro-duction EventTemplate



Has Pro-duction LongRange Plan









Has Pro-duction Plan



Has Pro-duction Pro-file



Has Pro-duction Tar-get


Insert, Delete

Has Pro-duction Unit



Has ReferenceDocuments


Insert, Delete

Has Reliability View, Update,Insert, Delete View View View, Update,

Insert, Delete

Has Unit Pro-file


Insert, Delete View

Has Work His-tory



ProductionEvent Has RCAAnalysis



Is ProductionUnit


Insert, Delete View

Xi Tag Has Pro-duction EventTemplate





Deploying Recommendation ManagementThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Recommendation Management for theFirst TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the Recommendation Man-agement data model to determinewhich relationship definitions you willneed to modify to include your cus-tom equipment and location families.

N

Required if you storeequipment and locationinformation in familiesother than the baselineEquipment and Func-tional Location families.

2Assign Security Users to the Recom-mendation Management SecurityGroup via the Configuration Manager.

Y None

3 Modify the asset queries used byRecommendation Management. N




Upgrading Recommendation Management toV4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0Recommendation Management will be upgraded from V3.6.0.0.0 to V4.1.0.0 auto-matically when you upgrade the components in the basic Meridium Enterprise APM sys-tem architecture. No additional steps are required.

V3.5.1Recommendation Management will be upgraded from V3.5.1 to V4.1.0.0 automaticallywhen you upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.

V3.5.0 SP1 LPRecommendation Management will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 auto-matically when you upgrade the components in the basic Meridium Enterprise APM sys-tem architecture. No additional steps are required.





Recommendation Management Security Groupsand RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.


One baseline Security Group is provided for Recommendation Management: MI Recom-mendation Management User.


Entity Families

Family Privileges

Action View

Equipment View

Hazards Analysis Consequence View

Instrumented Function View

Protective Instrument Loop View

RCA Analysis View

RCA Team Member View

RCM FMEA Analysis View

Recommendation View, Update, Insert, Delete

SIS Proof Test View

SIS Proof Test Template View




Family Privileges

Has Asset Strategy View, Update, Insert, Delete

Has Associated Recommendation View, Update, Insert, Delete

Has Consolidated Recommendations View, Update, Insert, Delete

Has Driving Recommendation View, Update, Insert, Delete

Has Recommendations View, Update, Insert, Delete

Has RMC FMEA Recommendation View, Update, Insert, Delete

Has Strategy View, Update, Insert, Delete

Has Superseded Recommendations View, Update, Insert, Delete

Is RCM FMEA Asset View, Update, Insert, Delete

Production Event Has RCA Analysis View

RCA Analysis Relationships View



About Asset QueriesTo identify the Equipment or Functional Location record that will be used to completean operation, the Meridium Enterprise APM system runs the following queries, whichare stored in the Catalog folder \\Public\Meridium\Modules\Core\Queries:

l Equipment Asset Query: After providing a prompt for an Entity Key, the Equip-ment Asset Query returns the record with the provided Entity Key. In the baselineMeridium Enterprise APM database, the query returns records in the Equipmentfamily.

l Location Asset Query: After providing a prompt for an Entity Key, the LocationAsset Query returns the record with the provided Entity Key. In the baselineMeridium Enterprise APM database, the query returns records in the FunctionalLocation family.

The Equipment Asset Query is always run first. If it returns a record, that record isassumed to be the correct predecessor record, and the Location Asset Query is not run.This means that if a Recommendation record is linked to an Equipment record and aFunctional Location record, the Equipment record will always be assumed to be the cor-rect predecessor record.

You will need to modify the baseline queries only if your Recommendation records arelinked to records in a family other than the Equipment family or the Functional Locationfamily. When you modify the queries, keep in mind that they must contain the Entity Keyfield from the source family whose records you want to return. A prompt must exist onthe Entity Key field, but the prompt can be a simple prompt with no valid values.

Both of these queries should query at the highest level necessary to include all equip-ment or location subfamilies. This means that if all of your customer-defined equip-ment and location families are structured in a hierarchy under a single parent family,such as Asset, you should modify only the Equipment Asset Query to include this parentfamily. In this case, the Location Asset Query will never be run because all customer-defined equipment and location records will be returned by the Equipment Asset Query.

When These Queries are RunThe Equipment Asset Query and Location Asset Query are not meant to be run on theirown. Instead, the Meridium Enterprise APM system runs these queries when you pro-mote a Recommendation record to an Action record.

When these queries are run, the Meridium Enterprise APM system supplies the promptwith the Entity Keys of the predecessor records that are linked to the selected Recom-mendation record using the following workflow.

l The Meridium Enterprise APM system first runs the Equipment Asset Query. If anyof the predecessor Entity Keys identify a record that belongs to the EquipmentAsset Query's source family, the Asset Strategy record will be linked to the recordthat is returned by the query.



l If none of the predecessor Entity Keys identify a record that belongs to the Equip-ment Asset Query's source family, the Meridium Enterprise APM system runs theLocation Asset Query. If any of the Entity Keys identify a record that belongs to thisquery source's family, the Asset Strategy record will be linked to the record that isreturned by this query.

l If none of the predecessor Entity Keys identify a record that belongs to the Loca-tion Asset Query's source family, the Recommendation record will be promoted toan Action record, but the Asset Strategy will not be linked to an Equipment or Func-tional Location record.

Example: Asset QuerySuppose a Recommendation record is linked to the Equipment record HX-112 and theRBI Criticality Analysis record Analysis 101. If you promote that Recommendation recordto an Action record, the Meridium Enterprise APM system will:

l Identify the Entity Key of the Equipment record HX-112 and the RBI Criticality Ana-lysis record Analysis 101.

l Supply these Entity Keys to the prompt in the Equipment Asset Query.

l Identify the record that is returned by the query. Because the source family is theEquipment family, the Equipment record HX-112 will be returned by the query.

l Link the new Asset Strategy record to the Equipment record HX-112.



Deploying Reliability AnalyticsThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Reliability Analytics for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the Reliability Analytics data mod-els to determine which relationshipdefinitions you will need to modify toinclude your custom equipment and loc-ation families. Modify any relationshipdefinitions as required.

N

Required if you storeequipment and loc-ation information infamilies other thanthe baseline Equip-ment and FunctionalLocation families.

2 Assign Security Users to one or moreReliability Analytics Security Groups. Y

Users will not be ableto access ReliabilityAnalytics unless theyhave permissions tothe Reliability Ana-lytics families.



Upgrading Reliability Analytics to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0Reliability Analytics will be upgraded from V3.6.0.0 to V4.1.0.0 automatically when youupgrade the components in the basic Meridium Enterprise APM system architecture. Noadditional steps are required.

V3.5.1Reliability Analytics will be upgraded from V3.5.1 to V4.1.0.0 automatically when youupgrade the components in the basic Meridium Enterprise APM system architecture. Noadditional steps are required.

V3.5.0 SP1 LPReliability Analytics will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridi4um Enterprise APM system archi-tecture. No additional steps are required.

V3.5.0Reliability Analytics will be upgraded from V3.5.0 to V4.1.0.0 automatically when youupgrade the components in the basic Meridium Enterprise APM system architecture. Noadditional steps are required.


1

Configure the ability forusers to create Reli-ability Distribution andReliability Growth Ana-lyses from AssociatedPages.

N

This feature is new in V3.5.0, so even ifyou have deployed Reliability Analyticsin V3.4.5, you will not have completed

this step. You need to complete thistask, however, only if you want toimplement this functionality.



Reliability Analytics Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Reliability Administrator MI FE Admin

MI Reliability User

MI FE Admin

MI FE PowerUser

MI FE User

MI Reliability Viewer

MI FE Admin

MI FE PowerUser

MI FE User

The following table lists the default privileges that members of each group have to theReliability Analytics entity and relationship families.

Family MI ReliabilityAdministrator

MI ReliabilityUser

MI ReliabilityViewer

Analysis View View View

Distribution View, Update, Insert,Delete


Exponential View, Update, Insert,Delete


Growth Model View, Update, Insert,Delete


Lognormal View, Update, Insert,Delete


Normal View, Update, Insert,Delete





MI ReliabilityUser


Production Analysis View, Update, Insert,Delete


Production Losses View, Update, Insert,Delete


Reliability AutomationRule


Reliability Distribution View, Update, Insert,Delete


Reliability Growth View, Update, Insert,Delete


Reliability Recom-mendation



Spare View, Update, Insert,Delete


Spares Analysis View, Update, Insert,Delete


Spare Analysis Chart View, Update, Insert,Delete


Spare Application View, Update, Insert,Delete


Spare Application Pop-ulation



System Action View, Update, Insert,Delete


System Action Mapping View, Update, Insert,Delete


System Action Optim-ization



System Action Result View, Update, Insert,Delete


System Analysis View, Update, Insert,Delete





MI ReliabilityUser


System Asset View, Update, Insert,Delete


System Buffer View, Update, Insert,Delete


System Condition Mon-itor



System Element View, Update, Insert,Delete


System Element Result View, Update, Insert,Delete


System Global Event View, Update, Insert,Delete


System Inspection View, Update, Insert,Delete


System Link View, Update, Insert,Delete


System PreventativeMaintenance



System Resource View, Update, Insert,Delete


System Resource Result View, Update, Insert,Delete


System Resource Usage View, Update, Insert,Delete


System Risk View, Update, Insert,Delete


System Risk Assessment View, Update, Insert,Delete


System Scenario View, Update, Insert,Delete


System Sensor View, Update, Insert,Delete





MI ReliabilityUser


System Special Action View, Update, Insert,Delete


System Subsystem View, Update, Insert,Delete


System Switch View, Update, Insert,Delete


Weibull View, Update, Insert,Delete


Analysis Link View, Update, Insert,Delete


Has Global Events View, Update, Insert,Delete


Has Mitigated TTF Dis-tribution



Has Planned ResourceUsages



Has Consolidated Recom-mendations View View View



Has Reliability View, Update, Insert,Delete


Has Resource Usage View, Update, Insert,Delete


Has Risk Assessments View, Update, Insert,Delete


Has Root System View, Update, Insert,Delete


Has Scenarios View, Update, Insert,Delete


Has System Actions View, Update, Insert,Delete





MI ReliabilityUser


Has System Elements View, Update, Insert,Delete


Has System Optimization View, Update, Insert,Delete


Has System Resources View, Update, Insert,Delete


Has System Results View, Update, Insert,Delete


Has System Risks View, Update, Insert,Delete


Has TTF Distribution View, Update, Insert,Delete


Has Unplanned ResourceUsages





Deploying Reliability Centered Maintenance (RCM)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Reliability Centered Maintenance (RCM)for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the RCM data model todetermine which relationshipdefinitions you will need tomodify to include your cus-tom equipment and locationfamilies.

Optional

This task is necessaryonly if you store equip-ment and locationinformation in familiesother than the baselineEquipment and Func-tional Location fam-ilies.

2


Required None



Upgrading Reliability Centered Maintenance(RCM) to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0RCM will be upgraded from V3.6.0.0.0 to V4.1.0.0 automatically when you upgrade thecomponents in the basic Meridium Enterprise APM system architecture. No additionalsteps are required.

V3.5.1RCM will be upgraded from V3.5.1 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.

V3.5.0 SP1 LPRCM will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automatically when you upgradethe components in the basic Meridium Enterprise APM system architecture. No addi-tional steps are required.

V3.5.0RCM will be upgraded from V3.5.0 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.


1Assign Security Usersto the MI RCM ViewerSecurity Group.

Y None

2

Add values to theRecommendedResource System CodeTable.

Y

This System Code Table is used to pop-ulate the Recommended Resource fieldin RCM FMEA Recommendationrecords.



Reliability Centered Maintenance (RCM) SecurityGroups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI RCM User

MI RCM ViewerMI Strategy User

MI RCM User

MI RCM ViewerMI Strategy Power

MI RCM User

MI RCM Viewer

MI ASI Administrator

MI Strategy Admin

Associating RCM Analyses with a Specific Site

Some companies that use the Meridium Enterprise APM software have facilities at mul-tiple sites, or locations, where each site contains unique equipment and locations. Ifdesired, you can define the sites in your organization and associate equipment and loc-ations with the site to which they belong. When you create RCM Analyses for thosepieces of equipment and locations, you will need to select the appropriate site on theAnalysis datasheet of the RCM Analysis.

To help streamline the analysis-creation process, after you select a site on the Analysisdatasheet, the Meridium Enterprise APM system will allow you to add Equipment andFunctional Location records to the RCM Analysis only if those pieces of equipment andlocations belong to that site.

You can also associate Risk Matrices with specific sites. If a Risk Matrix is associated witha site and an RCM Analysis is associated with the same site, when you define the unmit-igated risk for a failure effect, rather than seeing the default Risk Matrix, you will see theRisk Matrix that is associated with that site.





MIRCMViewer

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




MIRCMViewer

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


Task History

Note: The Task History relationship family is inactive inthe baseline Meridium Enterprise APM database.



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




MIRCMViewer

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 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 inact-ive in the baseline Meridium Enterprise APM database.


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 willhave access to ALL records involved in RCM Analyses. In addition to these baseline priv-ileges, which you can grant by assigning users to the MI RCM User Security Group, you



will need to grant RCM users permission to the Equipment or Functional Location familyif 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 inthe following Catalog folders: \\Public\Meridium\Modules\RCM.



ReportsThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Reports for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1 Install the Reports Designer. Required None

2 Set Up the Reports Designer. Required None



Install the APM Reports DesignerBefore You Begin

l Install Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio2013 (available at the official Microsoft website).

Steps

1. On the machine that will serve as the APM Reports Designer, access the MeridiumAPM Enterprise APM Distribution package, and navigate to the Admin folder.


The Meridium Admin - InstallShield Wizard appears.

3. Select Next.




4. Read the License Agreement and, if you agree, select the I accept the terms ofthe license agreement check box. Then, select Next.






6. Select SSRS Data Processing Extension for Visual Studio, and then select Next.

The Complete the Installation screen appears.



7. Select Install.

The Setup Status screen appears, which displays a progress bar that shows theprogress of the installation process. After the progress bar reaches the end, a mes-sage appears, indicating that Meridium Admin is installed successfully. Optionally,you can select to launch the APM System Administration tool when the installerwindow closes.

8. Clear the Launch APM System Administration now box, and then select Finish.



Note:You may be asked to restart your system for the changes to take effect.

The APM System Administration window appears.



9. Select Sql Server Report Designer.

The Add Meridium URL to SSRS Designer box appears.

10. Enter the server URL in the Add Meridium URL to SSRS Designer box.

11. Select Save.

The Meridium Server URL is added.

12. Select Exit.

Results

APM Report Designer is now installed.



Set Up the APM Report DesignerAfter installing the APM Report Designer plugin, you must set up APM Report Designerto interact with Meridium Enterprise APM Server.

Before You Beginl Install the APM Report Designer.

Steps

1. On the Meridium Enterprise APM Server, open Microsoft Visual Studio.

2. On the Tools menu, select Options.

The Options window appears.

3. On the Options window, in the left section, select APM Report Designer, andthen select General.

The MeridiumServerURL box appears in the right section.



4. In the MeridiumServerURL box, enter the Meridium Web Services URL in the fol-lowing format:

http://<server_name>//meridium/api/

The APM Report Designer setup is now complete.



Deploying Risk Based Inspection (RBI)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Risk Based Inspection (RBI) for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the RBI data model todetermine which relationshipdefinitions you will need tomodify to include your customequipment and location fam-ilies. Modify any relationshipdefinitions as needed via Con-figuration Manager.

N

Required if you store equip-ment and location inform-ation in families other thanthe baseline Equipment andFunctional Location families.

2Assign Security Users to one ormore of the RBI SecurityGroups.

YUsers will need permissions tothe RBI families in order touse the RBI functionality.

3

Add the following types of RBIusers to at least one TM Secur-ity Group:

l Users who are respons-ible for completing thesteps necessary to use TMAnalysis values to cal-culate RBI corrosionrates.

l Users who should be ableto navigate to TM via RBI.

NRequired if you are using theintegration between the RBIand TM modules.

4

If you plan to create your ownPotential Degradation Mech-anisms records, modify the MI_DEGRADATION_MECHANISM_TYPES System Code Table byadding the desired SystemCode values.

N




5

Modify the RecommendationCreation Enabled setting in theRBI Global Preferences work-space.

N

This setting is enabled bydefault. This task is necessaryonly if you want to disable thissetting because you use theAsset Strategy Management(ASM) module to recommendactions and manage mitigatedrisk.

6

Modify the Enable Recom-mendations to be Generated atCreated State setting in the RBIGlobal Preferences work-space.

N

This setting is disabled bydefault. This task is necessaryonly if you want to create RBIRecommendation recordswhile RBI Criticality Analysisrecords are in the Createdstate.

7

Modify the Allow Override of Cal-culated Unmitigated Risk Valuessetting in the RBIGlobal Preferences work-space.

N

This setting is disabled bydefault. This task is necessaryonly if you want to want toenable this setting becauseyou use a custom calculator.

8

Modify the Consider Half-Lifewhen Determining Inspection TaskInterval setting in the RBIGlobal Preferences work-space.

None

This setting is disabled bydefault. If you are followingthe Meridium Enterprise APMRBI Best Practice, you shouldenable this setting so that addi-tional values will be con-sidered when determining theDesired Interval value in cer-tain Inspection Task records.

9

Select the Is a Unit? check boxin Functional Location recordsthat represent units in yourfacility.

Y

This field is used throughoutRBI to distinguish these Func-tional Location records fromthose that represent otherlevels in the location hier-archy.

10

Using the Belongs to a Unitrelationship, link Equipmentrecords to Functional Locationrecords representing units towhich that equipment belongs(i.e., the field Is a Unit? con-tains the value True).

Y




11

Configure the Meridium Enter-prise APM system to generateRBI Recommendation recordsautomatically.

N You can complete this taskonly if certain conditions exist.

12 Create Potential DegradationMechanisms records . N

Required if you want to useadditional Potential Degrad-ation Mechanism records thatare not provided in thebaseline Meridium EnterpriseAPM database.

13Assign a ranking to all PotentialDegradation Mechanismsrecords .

N

Required if you want the Prob-ability Category field in certainCriticality Degradation Mech

Evaluation records to be pop-ulated automatically basedupon this ranking.



Upgrading Risk Based Inspection (RBI) to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


1

Import Policy records that Meridium,Inc. modified in order to fix issues inthe associated policy diagrams. Thisincludes the following Policy records:Appendix_G; Appendix_H; Appendix_I.

N

Required if you usePolicy records to gen-erateRBI Recommendationrecords.

2

Copy your customized SQL code fromthe Review Analyses by Asset queryto the Review Analyses by Asset 580query, and then replace the ReviewAnalyses by Asset query with itsbaseline version.

N

This step is requiredonly if you have pre-viously customized thequery that is used topopulate the list of ana-lyses on the RBI -Review Analyses page.


1

Import Policy records that Meridium,Inc. modified in order to fix issues inthe associated policy diagrams. Thisincludes the following Policy records:Appendix_B; Appendix D; Appendix E;Appendix F; Appendix G; Appendix H;Appendix I; PRD Strategies.

N





2

Import the Inspection Strategy recordsthat Meridium, Inc. modified in order tofix issues in existing Inspection Strategyrecords. To do so:

1. Using the Import/ExportMetadata window, navigate tothe following location on theMeridium Enterprise APM Servermachine: C:\Meridi-um\DbUpg\MI_DB_Master_3600000\3600000\20_IEU\50_Other\2_RecordsLinks.

2. Import the file MI_INSP_STRAT.xmlfrom this location.

The file is imported, and the associatedInspection Strategy records are created,replacing the previous ones.

Y

3

Copy your customized SQL code fromthe Review Analyses by Asset query tothe Review Analyses by Asset 580query, and then replace the ReviewAnalyses by Asset query with itsbaseline version.

N

This step is requiredonly if you have pre-viously customized thequery that is used topopulate the list ofanalyses on the RBI -Review Analysespage.

V3.5.0 SP1 LP




1

Import Policy records that Meridium,Inc. modified in order to fix issues inthe associated policy diagrams. Thisincludes the following Policyrecords:Appendix_B; Appendix D;Appendix E; Appendix F; Appendix G;Appendix H; Appendix I; PRD Strategies.

N


2





Y

3

Import Policy records that are new toV3.5.1. The XML files that you will needto import are: Int Corrosion Insp Group-ing Policy.xml; CUI Insp GroupingPolicy.xml.

N

Required if you wantto use InspectionGrouping func-tionality.

4In Functional Location records that rep-resent units in your facility, select the Isa Unit? check box.

Y

This step will ensurethat queries used byRBI modules functioncorrectly when return-ing results.




5

Using the Belongs to a Unit relationship,link Equipment records to FunctionalLocation records representing units towhich that equipment belongs (i.e., thefield Is a Unit? contains the value True).

Y

6Modify the Enable Recommendations tobe Generated at Created State setting onthe Global Preferences workspace.

N

This setting is disabledby default. This task isnecessary only if youwant to create RBIRecommendationrecords while RBI Crit-icality Analysis recordsare in the Createdstate.

7

Copy your customized SQL code fromthe Review Analyses by Asset query tothe Review Analyses by Asset 580query, and then replace the ReviewAnalyses by Asset query with itsbaseline version.

N

This step is requiredonly if you have pre-viously customizedthe query that is usedto populate the list ofanalyses on the RBI -Review Analysespage.


1


N





2





Y

3


N



Y


5


Y





N



1


N





2





Y

3


N



Y


5


Y





N




Risk Based Inspection Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI RBI Administrator MI Mechanical Integrity Administrator

MI RBI AnalystMI Mechanical Integrity Administrator



Family MI RBI Admin-istrator MI RBI Analyst

Entity Families

Asset Group View, Update, Insert,Delete


Consequence Evaluation Factors View, Update, Insert,Delete


Corrosion View View

Corrosion Analysis Settings View View

Criticality Consequence Evaluation View, Update, Insert,Delete


Criticality Other Damage Mech. Eval. View, Update, Insert,Delete


Criticality Env. Crack. Deg. Mech. Eval. View, Update, Insert,Delete


Criticality Ext. Corr. Deg. Mech. Eval. View, Update, Insert,Delete





Criticality Int. Corr. Deg. Mech. Eval. View, Update, Insert,Delete


Criticality RBI Component -Cylindrical Shell



Criticality RBI Component -Exchanger Bundle



Criticality RBI Component -Exchanger Header



Criticality RBI Component -Exchanger Tube



Criticality RBI Component - Piping View, Update, Insert,Delete


Criticality RBI Component - Tank Bot-tom



Data Mapping Column-Field Pair View, Update, Insert,Delete View

Data Mapping Group View, Update, Insert,Delete View

Data Mapping Query View, Update, Insert,Delete View

Degradation Mechanisms EvaluationFactors



Equipment View, Update, Insert,Delete


Functional Location View, Update, Insert,Delete


Grouping Element View, Update, Insert,Delete


Inspection Task View, Update, Insert,Delete


Meridium General Recommendation View View, Update, Insert,Delete




Meridium Reference Tables View, Update, Insert,Delete View

Policy View View

Potential Degradation Mechanisms View, Update, Insert,Delete View

RBI Criticality Analysis View, Update, Insert,Delete


RBI Degradation Mechanisms View, Update, Insert,Delete


RBI Recommendation View, Update, Insert,Delete


RBI Strategy Mapping Configuration View, Update, Insert,Delete


RBI Strategy Mapping Details View, Update, Insert,Delete


RBI System View, Update, Insert,Delete


Reference Document View, Update, Insert,Delete


Risk Assessment View, Update, Insert,Delete


Risk Rank View, Update, Insert,Delete


Risk Translation View, Update, Insert,Delete


SAP System View View

Strategy Logic Case View, Update, Insert,Delete View

Strategy Reference Table View, Update, Insert,Delete


Task Type View, Update, Insert,Delete





Time Based Inspection Interval View, Update, Insert,Delete


Time Based Inspection Setting View, Update, Insert,Delete



Belongs to a Unit View, Update, Insert,Delete


Data Mapping has Column-Field Pair View, Update, Insert,Delete View

Data Mapping has Query View, Update, Insert,Delete View

Data Mapping has Subgroup View, Update, Insert,Delete View

Has Asset Group View, Update, Insert,Delete


Has Child RBI Criticality Analysis View, Update, Insert,Delete


Has Consequence Evaluation View, Update, Insert,Delete


Has Consolidated Recommendations View View, Update, Insert,Delete

Has corrosion Analyses View View

Has Corrosion Analysis Settings View View

Has Datapoints View View

Has Degradation Mechanisms View, Update, Insert,Delete


Has Inspections View View, Update, Insert,Delete

Has Inspection Scope View View

HasPotential Degradation Mechanisms






Has RBI Components View, Update, Insert,Delete


Has RBI Criticality Analysis View, Update, Insert,Delete


Has RBI Degradation MechanismsEvaluation



Has RBI Strategy Mapping Con-figuration



Has RBI Systems View, Update, Insert,Delete




Has Reference Documents View, Update, Insert,Delete



Has SAP System View View

Has Superseded Recommendations View View, Update, Insert,Delete

Has Task Revision View View, Update, Insert,Delete

Has Tasks View, Update, Insert,Delete


Has Time Based Inspection Interval View, Update, Insert,Delete


Has Unmitigated Risk View, Update, Insert,Delete


Is Based on RBI Degradation Mech-anisms



Is Mitigated View, Update, Insert,Delete


Is Part of Group View, Update, Insert,Delete





Mapped to RBI Component View, Update, Insert,Delete


Represents Inspections View, Update, Insert,Delete


Note: Security privileges for all modules and catalog folders can be found in theAPM documentation.

These families are not used elsewhere in the RBI module.

l Privileges to the following entity and relationship families support integration withthe Inspection Management module:

l Has Inspection Scopel Has Time Based Inspection Intervall Time Based Inspection Intervall Time Based Inspection Setting

Specifically, certain features of the Time-Based Inspection Settings functionality, whichyou can use if the Inspection Management license is active, are facilitated by these priv-ileges.



Deploying Root Cause Analysis (RCA)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Root Cause Analysis (RCA) for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the RCA data model todetermine which relationship defin-itions you will need to modify toinclude your custom equipment andlocation families. Modify any rela-tionship definitions as required.

N


2 Assign Security Users to one ormore RCA Security Groups. Y

Users will not be able toaccess Root Cause Ana-lysis unless they belongto an RCA Security Group.

3Specify the Team Charter after youcreate a new Root Cause Analysisrecord.

N

A default Team Charterexists in the baselineMeridium Enterprise APMdatabase. You can selectthe default Team Charteror define your own.

4Specify the Critical Success Factorsafter you create a new Root CauseAnalysis record.

N

Default Critical SuccessFactors exist in thebaseline Meridium Enter-prise APM database. Youcan select one or moredefault Critical SuccessFactors or define yourown.

5 Define the Tracking EvaluationQuery. N

Required only if you donot want to use thebaseline query, which isdefined by default.



Upgrading Root Cause Analysis (RCA) to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0RCA will be upgraded from V3.6.0.0 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.

V3.5.1RCA will be upgraded from V3.5.1 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.

V3.5.0 SP1 LPRCA will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automatically when you upgradethe components in the basic Meridium Enterprise APM system architecture. No addi-tional steps are required.





RCA Security



Root Cause Analysis Security Groups and Roles

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



MI PROACT Administrator MI FE Admin

MI PROACT Team Member

MI FE Admin

MI FE PowerUser

MI FE User

MI PROACT Viewer

MI FE Admin

MI FE PowerUser

MI FE User

The following table lists the default privileges that members of each group have to theRCA entity and relationship families.

Note: Access to RCA is not granted through these privileges but through mem-bership in these Security Groups and the privileges associated with them.

Family MI PROACTAdministrator

MI PROACTTeam Member

MIPROACTViewer


Functional Location View View View

Human Resource View, Update,Insert

View, Update,Insert View

Notification View, Update,Insert, Delete






MIPROACTViewer

RCA Analysis View, Update,Insert, Delete


RCA Build List Item View, Update,Insert, Delete


RCA Critical Success Factor View, Update,Insert, Delete


RCA Event View, Update,Insert, Delete


RCA Failure Mode View, Update,Insert, Delete


RCA Hypothesis View, Update,Insert, Delete


RCA Logic Gate View, Update,Insert, Delete


RCA Preserve Item View, Update,Insert, Delete


RCA Recommendation View, Update,Insert, Delete


RCA Sequence Node View, Update,Insert, Delete


RCA Team Member View, Update,Insert, Delete


RCA Tracking Item View, Update,Insert, Delete


RCA Verification View, Update,Insert, Delete


Reference Document View, Update,Insert, Delete


RCA Image View, Update,Insert, Delete


Security User View View View





MIPROACTViewer

Has Consolidated Recom-mendations View View View

Has Recommendations View, Update,Insert, Delete


Has Reference Documents View, Update,Insert, Delete


Is a User View, Update,Insert


Group Assignment View, Update,Insert


Production Event Has RCAAnalysis



RCA Analysis Has Asset View, Update,Insert, Delete


RCA Analysis Relationships View, Update,Insert, Delete


RCA System Relationships View, Update,Insert, Delete


RCA Tracking Item Rela-tionships



User Assignment View, Update,Insert


Equipment Has Equipment View View View

Functional Location HasEquipment View View View

Functional Location Has Func-tional Location(s) View View View



Deploying RoundsThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Rounds for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.


Meridium APM Sync Server

Note: Meridium APM Sync Server is only required if you want to use OperatorRounds on Windows Mobile handheld devices


1

Configure the Meridium APM SyncServer. Configuring the MeridiumAPM Sync Server includes com-pleting the following steps:

l Install Meridium APM Sync Ser-vices.

l Install the Microsoft SyncFramework.

l Modify the file web.configdepending on Oracle databaseprovider or SQL database pro-vider.

l Modify the file Meridi-umSync.config.

Optional None

2 Configure security for the Meridi-umSyncService Service. Optional None

Module level Configuration Tasks




1

Review the Rounds data model todetermine which relationship defin-itions you will need to modify toinclude your custom asset families.Modify any relationship definitions asneeded.

Optional

Required ifyou haveasset data infamilies out-side of thebaselineEquipmentand Func-tional Loca-tion families.

2

Assign the desired Security Users to thefollowing Security Groups:

l MI Operator RoundsAdministrator

l MI Operator Rounds Mobile User

Note: The MAPM Security Groupthat has been provided withMeridium Enterprise APM v3.6 is alsoavailable. The user privileges are thesame for the MAPM Security User andthe MI Operator Rounds SecurityUser. However, we recommend thatyou use the MI Operator Rounds UserSecurity Group instead of theMAPM Security Group.

Required None

3 Manage Measurement Location Tem-plate mappings. Optional

Required ifyou addedfields to theMeasurementLocation Tem-plate familyvia Con-figurationManager.




6

If you have created a new asset family,create a relationship definition as fol-lows:

l Relationship family: Has Check-point

l Predecessor: The asset familyl Successor: The Measurement

Location family or LubricationRequirement family

l Cardinality: ONE to MANY

Optional

Required ifyou createdan asset fam-ily that youwant to linkto a Meas-urement Loca-tion or aLubricationRequirementusing the HasCheckpointrelationshipfamily.

7Install the Meridium Enterprise APMapplication on the mobile device thatyou plan to use for data collection.

Optional

Required onlyif you want touse a mobiledevice fordata col-lection.

8Set the local time zone on the mobiledevice that you will use for data col-lection, typically the user time zone.

Optional

Required ifyou will use amobile devicefor data col-lection.

9 Set up the Scheduled Compliance task . Required

The sched-uled com-pliance taskstarts as soonas theRounds mod-ule isdeployed,and is set torun con-tinuously aslong asRounds inuse.

Note:It is important that in addition to the above tasks, you compile the databaseand reset IIS on the Meridium APM Application Server.

Windows Mobile Hand Held Device



The following tasks need to be performed on each Windows Mobile handheld devicethat you want to use with Operator Rounds.


1

Ensure that all the Windows Mobile hand-held devices that you want to use with Oper-ator Rounds meet the softwarerequirements.

Required None

2 Install the .NET Compact Framework. Required None

3 Install Microsoft SQL CE. Install MicrosoftSQL CE. Required None

4 Install Microsoft Sync Services for ADO.NET. Required None

5 Install the Meridium APM MobileFramework. Required None

6 Access Device Settings Screen. Required None

7 Identify the Sync Server within the MeridiumEnterprise APM Mobile Framework. Required None

8 Specify the security query to be used withthe Meridium APM Mobile Framework. Required None

9 Modify the user time-out value. Optional None

10 Install Operator Rounds. Required None

11

Configure barcode scanning. Configuringbarcode scanning includes the followingssteps:

l Install the Barcode add-on.l Enable barcode scanning.

Optional

Requiredif youwill usean Bar-codescannerwithOperatorRounds.

12

Configure RFID tag scanning. ConfiguringRFID scanning includes the following steps:

l Install the RFID add-on.l Enable RFID tag scanning.

Optional

Requiredif youwill usean RFIDscannerwithOperatorRounds.

13 Install translations for Operator Rounds. Optional None





Upgrading Rounds to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.


Before You BeginIn Meridium Enterprise APM V4.1.0.0, a Checkpoint can be linked to one asset. Duringupgrade from earlier versions to V4.1.0.0, the related asset entity key is added to a fieldon the Checkpoint family. Hence, if you have Checkpoints that are linked to more thanone asset, then you must remove the linkage to the additional assets prior to theupgrade.

To do so, perform the following steps:

1. Using an appropriate database management tool, run the following query in thedatabase configured with the current version of Meridium Enterprise APM thatyou will configure to work with Meridium Enterprise APM V4.1.0.0. For example,run the following query for ML in the database:

SELECTMI_MEAS_LOC.ENTY_KEY as "ML_KEY",MI_ENTITIES.ENTY_ID as "ML ID",MIV_MIR_HS_MEASLOC.PRED_ENTY_KEY as "Asset Key"FROM MI_MEAS_LOCJOIN MIV_MIR_HS_MEASLOC ON MI_MEAS_LOC.ENTY_KEY = MIV_MIR_HS_MEASLOC.SUCC_ENTY_KEYJOIN MI_ENTITIES on MIV_MIR_HS_MEASLOC.SUCC_ENTY_KEY = MI_ENTITIES.ENTY_KEYAND SUCC_ENTY_KEY IN(SELECTSUCC_ENTY_KEYFROM MIV_MIR_HS_MEASLOCGROUP BY SUCC_ENTY_KEYHAVING COUNT( * ) > 1)ORDER BY 1,2;GO



A list of Checkpoints that are linked to multiple assets appears, providing theCheckpoint key, Checkpoint ID, and the Asset Key of the assets linked to the Check-point.

2. Access each Checkpoint in Record Manager in the current version of MeridiumAPM.

The left pane displays the records that are related to the Checkpoint.

3. Unlink the additional assets from the Checkpoint such that it is linked only to oneasset (e.g., either a Functional Location or an Equipment if you are using thedefault asset families).


1

Install Meridium Enterprise APMv4.1.0.0, or Meridium APM MobileFramework v4.1.0.0 on the mobiledevice that you will use for datacollection.

NoRequired if you will use amobile device for data col-lection.

2Set the local time zone on themobile device that you will use fordata collection.

NoRequired if you will use amobile device for data col-lection.

3

Confirm the assignment of Usersfor the existing route sub-scriptions and make additionalassignments if needed.

Yes

Routes that were subcribedto by a user in MeridiumMobileAPM will be assignedto the user automaticallythrough the DB upgradeprocess.


1

Install Meridium Enterprise APM v4.1.0.0, orMeridium APM Mobile Framework v4.1.0.0 onthe mobile device that you will use for data col-lection.

No

Required if youwill use amobile devicefor data col-lection.




2Set the local time zone on the mobile devicethat you will use for data collection.

No


3 Assign mobile device users to Routes. No



1

Install Meridium Enterprise APM v4.1.0.0, orMeridium APM Mobile Framework v4.1.0.0 onthe mobile device that you will use for data col-lection.

No



No




V3.5.0




1

Install Meridium Enterprise APM Install MeridiumEnterprise APM v4.1.0.0, or Meridium APMMobile Framework v4.1.0.0 on the mobile devicethat you will use for data collection.

No

Required ifyou will usea mobiledevice fordata col-lection.

2Set the local time zone on the mobile device thatyou will use for data collection.

No





1

Install Meridium Enterprise APM v4.1.0.0, orMeridium APM Mobile Framework v4.1.0.0onthe mobile device that you will use for data col-lection.

No



No








Security Groups and Privileges In RoundsThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Operator Rounds Administrator MI HealthAdmin

MI Operator Rounds Mobile User

MI HealthAdmin

MI HealthPower

MI HealthUser

Users who should be able to run Rounds queries to view the Rounds data after it hasbeen uploaded from a tablet or a mobile device will need a combination of the priv-ileges listed in the following table, depending on the families included in the queriesthey want to run.

Note: The privileges assigned to the members of the MAPM Security Group, whichwas provided in the baseline Rounds module in Meridium Enterprise APM V3.6.0, arealso assigned to the members of the MI Operator Rounds Mobile User Security Group.However, we recommend that you use the MI Operator Rounds User Security Groupinstead of the MAPM Security Group.

The following table lists the default privileges that members of each group have to theRounds entity and relationship families.

Family MI Operator Rounds Admin-istrator

MI Oper-atorRoundsMobileUser

MAPMSecurityGroup

Entity Families





MAPMSecurityGroup

Checkpoint Condition View, Update, Insert, Delete View View

Checkpoint Task View, Update, Insert, Delete View,Update

View,Update

Health Indicator View View View

Health Indicator Map-ping View, Update, Insert, Delete View View

Hierarchy Item ChildDefinition View, Update, Insert, Delete View View

Hierarchy Item Defin-ition View, Update, Insert, Delete View View

Measurement Location View, Update, Insert, Delete View View

Measurement LocationTemplate View, Update, Insert, Delete View View

Operator Rounds Allow-able Values View, Update, Insert, Delete View View

Operator RoundsRecommendation View, Update, Insert, Delete



Reading View, Update, Insert, Delete



Reference Document View, Update, Insert, Delete View View

Route View, Update, Insert, Delete View,Update

View,Update

Route History View, Update, Insert, Delete

View,Insert,Update,Delete

View,Insert

Task None View,Update

View,Update





MAPMSecurityGroup

Template Group View, Update, Insert, Delete View View


Condition Has ML View, Update, Insert, Delete View View

Has Checkpoint View, Update, Insert, Delete View View

Has Checkpoint Tem-plate View, Update, Insert, Delete View View

Has Health Indicator View View View

Has History View, Update, Insert, DeleteView,Insert,Delete

View,Insert

Has Readings View, Update, Insert, Delete



Has Recommendations View, Update, Insert, Delete



Has Reference Docu-ments View, Update, Insert, Delete View View

Has Route View, Update, Insert, Delete



Has Tasks View, Update, Insert, Delete View View

Health Indicator HasMapping View, Update, Insert, Delete View View

Health Indicator HasSource View View View

ML Has Condition View, Update, Insert, Delete View View





MAPMSecurityGroup

ML HasOPR Recommendation View, Update, Insert, Delete



Route Has Checkpoint View, Update, Insert, Delete View View

Route Has HumanResource View, Update, Insert, Delete Insert Insert

Template Has Check-point View, Update, Insert, Delete View View



Manage the Measurement Location TemplateMappingsThe Measurement Location Template family and the Measurement Location family areprovided as part of the baseline Rounds data model. If you create a Measurement Loca-tion Template in the Meridium Enterprise APM application, you can then create a Meas-urement Location based on that template. If you do so, all values in MeasurementLocation Template fields that also exist on the Measurement Location will be mappedautomatically to the new Measurement Location.

You might find that the Measurement Location Template and Measurement Locationdatasheets do not contain all the fields that you need. If so, you can add fields to theMeasurement Location Template family so that the values from the new fields will bemapped to Measurement Locations based on that template. To do so, you will need to:

1. Create a new Measurement Location Template field.

2. Add the new Measurement Location Template field to the Measurement LocationTemplate datasheet.

3. Create a new Measurement Location field. We recommend that the field captionof this field be the same as the field caption you defined for the MeasurementLocation Template field. This will ensure that the text in the field IDs that identifythe fields are the same. If they are not the same, the values will not be mappedfrom the Measurement Location Template to the Measurement Location.

4. Add the new Measurement Location field to the Measurement Location datasheet.



Deploying RulesThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Install the Meridium Rules EditorBefore You Begin

l Microsoft Visual Studio 2012 or 2013 Professional must be installed on every work-station where you want to work with Meridium rules in the Meridium EnterpriseAPM system.

l MSXML must also be installed on these workstations.

l You must be logged in as the administrator for the system.

Steps

1. On the machine that will serve as the Meridium rules editor, insert the MeridiumEnterprise APM Framework and Server Setup DVD, and navigate to the Adminfolder.


The Meridium Admin - InstallShield Wizard screen appears.

3. Select Next.




4. Read the License Agreement and, if you agree, select the I accept the terms ofthe license agreement option. Then, select Next button.






6. Select the APM Rules Editor Extension for Visual Studio option.

Note: There are additional options available for selection. You may selectthese options depending on the requirement.

Meridium Enterprise APM performs a check to make sure that your machine con-tains the required prerequisites for the features that you want to install.

l If one or more prerequisites are missing or there is not enough space on themachine, a dialog box will appear, explaining which prerequisites are miss-ing or asking to free up space. If this occurs, close the installer, install themissing prerequisite or free up some space, and then run the installer again.



7. Select Next.

The Complete the Installation screen appears.

8. Select Install.



The Setup Status screen appears, which displays a progress bar that shows theprogress of the installation process. After the progress bar reaches the end, a mes-sage appears, indicating that Meridium Admin is installed successfully. Optionally,you can select to launch the APM System Administration tool when the installerwindow closes.

9. Clear the Launch APM System Administration now box, and then select Finish.



Results

l The Meridium Rules Editor is installed.

What's Next?

l Open the Meridium Rules Editor



Deploying SIS ManagementThe checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying SIS Management for the First TimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the SIS Management datamodel to determine which rela-tionship definitions you will need tomodify to include your custom equip-ment or location families. Modifyany relationship definitions asneeded using the Configuration Man-ager.

Optional

This task isnecessary only ifyou store equip-ment or locationinformation infamilies otherthan thebaseline Equip-ment and Func-tional Locationfamilies.

2

Assign the desired Security Users toone or more SIS Management Secur-ity Groups using the ConfigurationManager.

Required

Users will not beable to accesssSIS Managementunless they havepermissions totheSIS Managementfamilies.

3 Define alternate search queries . Optional

Required if youdo not want touse the baselinesearch queries.

4 Import data from an Exida projectfile . Optional

This is necessaryonly if you wantto create SIL Ana-lyses using anExida projectfile.

5 Export data from an Exida projectfile . Optional None




6

Manage the types of independent lay-ers of protection that will be used topopulate the Type list in an Independ-ent Layer of Protection record. To doso, add a code to the MI_IPL_TYPEsystem code table.

Optional

Required if youwant to addanother value tothe list ofdefault values inthe Type list inthe IndependentLayer of Pro-tection data-sheet.

7 Activate the Hazards Analysis license. Optional

This is necessaryonly if you wantto take advant-age of the integ-ration betweenthe SIS Man-agement mod-ule and HazardsAnalysis.

8

Assign at least view permissions tothe Hazards Analysis family to SISManagement Security Groups in Con-figuration Manager.

Optional

This is necessaryonly for SecurityGroups that willbe used in theintegrationbetween the SISManagementmodule and Haz-ards Analysis.



Upgrade WorkflowThe following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.



1Activate the Hazards Analysislicense .

No

Required if you want to takeadvantage of the integ-ration between the SIS Man-agement module andHazards Analysis.

2

Assign at least View permissionsto the Hazards Analysis family toSIS Management Security Groupsin Configuration Manager .

No




No


2


No


V3.5.0 SP1 LP





No


2


No




No


2


No




No





2


No




SIS Management Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI SIS Administrator MI Safety Admin

MI SIS Engineer

MI Safety Admin

MI Safety Power

MI Safety User

MI SIS User

MI Safety Admin

MI Safety Power

MI Safety User


Family MISIS Administrator

MISIS Engineer MI SIS User

Entity Families

Asset_Criticality_Analysis View None None

Asset_Criticality_Analysis_System View None None

Consequence View, Update,Insert, Delete View View

Consequence_Modifier View, Update,Insert, Delete



External_Assessment View, Update,Insert, Delete

View, Update,Insert, Delete None





Functional_Location View View View

Functional_Systems View, Update,Insert, Delete


Functional_Test_Detail View, Update,Insert, Delete



Human_Resource View, Update,Insert, Delete


Independent_Layer_of_Pro-tection



Instrumented_Function View, Update,Insert, Delete


IPL_Type View, Update,Insert, Delete


LOPA View, Update,Insert, Delete


Notification View, Update,Insert, Delete


PHA_Internal_Assessment View, Update,Insert, Delete


Probability View, Update,Insert, Delete View View

Protection_Level View, Update,Insert, Delete View, Insert View

Protective_Instrument_Loop View, Update,Insert, Delete View, Insert View

Protective_Instrument_Loop_Element



Proven_In_Use_Justification View, Update,Insert, Delete


RBI_Components View, Update,Insert, Delete


Reference_Document View, Update,Insert, Delete






Risk View, Update,Insert, Delete


Risk_Assessment View, Update,Insert, Delete


Risk_Assessment_Recom-mendation



Risk_Category View, Update,Insert, Delete


Risk_Matrix View, Update,Insert, Delete View View

Risk_Matrix_Internal_Assess-ment



Risk_Threshold View, Update,Insert, Delete View View

Safety_Instrumented_Sys-tem



Safety_Integrity_Level View, Update,Insert, Delete View View

SIF_Common_Cause_Failure View, Update,Insert, Delete


SIL_Analysis View, Update,Insert, Delete


SIL_Threshold View, Update,Insert, Delete View View

SIS_Proof_Test View, Update,Insert, Delete



SIS_Proof_Test_Template View, Update,Insert, Delete


SIS_Proof_Test_Template_Detail



SIS_Trip_Report View, Update,Insert, Delete






SIS_Trip_Report_Detail View, Update,Insert, Delete


Site_Reference View View View

Task View, Update,Insert, Delete


Time_Based_Inspection_Interval View View View

Time_Based_Inspection_Set-ting View View View

Relationship_Families

Analysis_Has_Human_Resource



Asset_Criticality_Analysis_Has_System View None View

Equipment_Has_Equipment View View View

Functional_Location_Has_Equipment View View View

Functional_Location_Has_Functional_Location View View View

Has_Consequence_Modifier View, Update,Insert, Delete


Has_Equipment View, Update,Insert, Delete


Has_Functional_Location View, Update,Insert, Delete


Has_Functional_Location_Detail



Has_Functional_Test View, Update,Insert, Delete



Has_Functional_Test_Detail View, Update,Insert, Delete



Has_Hazard_Event View, Update,Insert, Delete






Has_HAZOP_Reference View, Update,Insert, Delete



Has_IF View, Update,Insert, Delete


Has_Independent_Pro-tection_Layer



Has_Instrumented_Func-tion_Revision



Has_Instrument_Loop View, Update,Insert, Delete


Has_Instrument_Loop_Revi-sion



Has_LOPA View, Update,Insert, Delete


Has_LOPA_Revision View, Update,Insert, Delete


Has_PIL_Device View, Update,Insert, Delete


Has_PIL_Device_Revision View, Update,Insert, Delete


Has_PIL_Group View, Update,Insert, Delete


Has_PIL_Group_Revision View, Update,Insert, Delete


Has_PIL_Subsystem View, Update,Insert, Delete


Has_PIL_Subsystem_Revi-sion



Has_Proven_In_Use_Jus-tification



Has_RBI_Components View, Update,Insert, Delete






Has_Recommendations View, Update,Insert, Delete


Has_Reference_Documents View, Update,Insert, Delete

View, Update,Insert, Delete View, Insert

Has_Reference_Values View, Update,Insert, Delete


Has_Risk View, Update,Insert, Delete


Has_Risk_Category View, Update,Insert, Delete


Has_Risk_Matrix View, Update,Insert, Delete


Has_SIF_Common_Cause_Failures



Has_SIL_Assessment View, Update,Insert, Delete


Has_SIS_Analysis_Revision View, Update,Insert, Delete


Has_SIS_Revision View, Update,Insert, Delete


Has_SIS_Trip_Report_Detail View, Update,Insert, Delete


Has_Site_Reference View, Update,Insert, Delete


Has_Task_History View, Update,Insert, Delete

View, Update,Insert, Delete View, Insert

Has_Tasks View, Update,Insert, Delete


Has_Task_Revision View View View

Has_Template_Detail View, Update,Insert, Delete


Has_Templates View, Update,Insert, Delete






Has_Time_Based_Inspec-tion_Interval View View View

Migrates_Risk View, Update,Insert, Delete


Was_Promoted_to_ASM View, Update,Insert, Delete




Deploying Thickness Monitoring (TM)The checklists in this section of the documentation contain all the steps necessary fordeploying and configuring this module whether you are deploying the module for thefirst time or upgrading from a previous module.



Deploying Thickness Monitoring (TM) for the FirstTimeThe following table outlines the steps that you must complete to deploy and configurethis module for the first time. These instructions assume that you have completed thesteps for deploying the basic Meridium Enterprise APM system architecture.



1

Review the TM data model todetermine which relationshipdefinitions you will need tomodify to include your cus-tom equipment families.Modify any relationship defin-itions as needed. Modify anyrelationship definitions asneeded.

N

Required if you store equipmentinformation in families otherthan the baseline Equipmentand TML Group families.

2Assign the desired SecurityUsers to one or more TMSecurity Groups.

YUser must have permissions tothe TM families in order to usethe TM functionality.




3Configure settings for theEquipment and TML Groupfamilies.

Y

Required regardless of whetheror not you follow the TM BestPractice. If you do not follow theTM Best Practice, you must con-figure settings for the familiesthat will be used to store equip-ment data in Thickness Mon-itoring.

The following relationships mustbe defined regardless ofwhether you follow TM BestPractice:

l For the Equipment family,the Asset to Sub-component Relationshipbox must be set to HasTML Group, and the Com-ponent ID field must beset to Equipment ID. TheSubcomponent to AssetRelationship box shouldbe left blank.

l For the TML Group family,the Subcomponent toAsset Relationship boxmust be set to Has TMLGroup, and the Com-ponent ID field must beset to TML Group ID. TheAsset to SubcomponentRelationship box shouldbe left blank.

4 Configure global settings. N

Default reading preferences andNominal T-Min preferences existin the baseline Meridium Enter-prise APM database. These willbe used if you do not defineyour own. You can also defineadditional, optional global pref-erences that are not defined inthe baseline Meridium Enter-prise APM database.




5 Configure the system to usecustom TML Types. N

Default TML Types exist in thebaseline Meridium EnterpriseAPM database. You can defineadditional TML Types to use inyour Corrosion Analyses.

6 Manage Thickness Mon-itoring Rules Lookup records. N

You can complete this task if youwant to view or modify Thick-ness Monitoring Rules Lookuprecords whose values are usedto perform certain TM cal-culations.

7

Define additional fields thatwill be displayed in theheader section of the TMMeasurement Data Entry.

N

Default Thickness Measurementfields are displayed in theheader section of these pages inthe baseline Meridium Enter-prise APM database. You canspecify that additional fields bedisplayed in the header sectionof these pages.

8 Disable the Auto ManageTasks setting. N Required if are using both the

RBI and the TM modules.

9

Install the Meridium DeviceService on all of the machinesthat will connect to devicesthat will be used with Thick-ness Monitoring.

N

Required if you will use anydevice to collect data that youtransfer toThickness Monitoring.

10

Install the drivers and sup-porting files for any deviceson all of the machines thatwill connect to devices thatwill be used with ThicknessMonitoring.

N

Required if you will use thesedevices to collect data that youtransfer toThickness Monitoring.



Upgrading Thickness Monitoring (TM) to V4.1.0.0The following table outlines the steps that you must complete to upgrade this moduleto V4.1.0.0. These instructions assume that you have completed the steps for upgradingthe basic Meridium Enterprise APM system architecture.

V3.6.0.0.0Thickness Monitoring will be upgraded from V3.6.0.0.0 to V4.1.0.0 automatically whenyou upgrade the components in the basic Meridium Enterprise APM system archi-tecture. No additional steps are required.

V3.5.1TM will be upgraded from V3.5.1 to V4.1.0.0 automatically when you upgrade the com-ponents in the basic Meridium Enterprise APM system architecture. No additional stepsare required.

V3.5.0 SP1 LPTM will be upgraded from V3.5.0 SP1 LP to V4.1.0.0 automatically when you upgrade thecomponents in the basic Meridium Enterprise APM system architecture. No additionalsteps are required.

V3.5.0




1

Manually update TM Analyses for whichyou used custom corrosion rates. To doso:

1. Locate the records that you willneed to update by running the fol-lowing query:

SELECT [MI_EQUIP000].[MI_EQUIP000_EQUIP_ID_C] "Equip-ment ID", [MI_TMLGROUP].[MI_TMLGROUP_ID_C] "TML GroupID", [MI Thickness MeasurementLocation].[MI_DP_ASSET_ID_CHR]"TML Asset ID", [MI ThicknessMeasurement Location].[MI_DP_ID_CHR] "TML ID", [MI TML Cor-rosion Analysis].[MI_TML_CA_A_CR_N] "Custom Calculation A Cor-ros", [MI TML Corrosion Analysis].[MI_TML_CA_B_CR_N] "Custom Cal-culation B Corros" FROM [MI_EQUIP000] JOIN_SUCC [MI_TMLGROUP] JOIN_SUCC [MI Thick-ness Measurement Location]JOIN_SUCC [MI TML Corrosion Ana-lysis] ON {MI Has Corrosion Ana-lyses} ON {MI Has Datapoints} ON{MIR_HSTMLGP} WHERE ([MI TMLCorrosion Analysis].[MI_TML_CA_A_CR_N] > 0 AND [MI TML Cor-rosion Analysis].[MI_TML_CA_B_CR_N] > 0)

2. Use the Bulk Analyze tool toupdate TM Analyses associatedwith the Equipment and TMLGroup records returned by thisquery.

N

In previous versionsof Meridium APM, ifyou used custom cor-rosion rates in yourTM Analyses, certainfields in the asso-ciated TML CorrosionAnalysis records werepopulated with val-

ues using the unit ofmeasure (UOM)inches per dayinstead of IN/YR (TM)(i.e., inches per year),which is the UOM thatis specified in theproperties of thefields. In order to cor-rect this issue in exist-ing records, you mustperform this step tomanually update TMAnalyses. For moreinformation aboutthis issue, see theV3.5.1 Release Notes.




Note that these instructions assume thatyou are using the baseline Equipmentand TML Group families. If you use cus-tom equipment families, you mustreplace the following values before run-ning the query in order to identify therecords requiring update:

l MI_EQUIP000 and MI_TMLGROUPwith your custom family IDs.

l MI_EQUIP000_EQUIP_ID_C and MI_TMLGROUP_ID_C with the field IDsused to identify these customequipment records.

Then, run the Bulk Analyze tool usingyour custom records.

V3.4.5




1

Update certain TM Analyses to correctTML Corrosion Analyses for which youperformed measurement variance eval-uation prior to V4.1.0.0. To do so:

1. Locate the records that you willneed to update by creating a querythat returns TML Corrosion Ana-lyses whose:

l Short Term Corrosion Ratefield contains the value 0(zero).

l Allowable Measurement Vari-ance Applied field is set toTrue.

2. Use the Bulk Analyze tool toupdate TM Analyses that are asso-ciated with TML Corrosion Ana-lyses returned by the query youcreated in step 1.

N

In previous versionsof Meridium APM, incertain cir-cumstances, TML Cor-rosion Analyses forwhich you performedmeasurement vari-ance evaluation con-tained incorrectvalues in the ShortTerm Corrosion Rateand Allowable Meas-urement VarianceApplied fields. Inorder to correct thisissue in existingrecords, you mustperform this step tomanually update TMAnalyses.




2

Manually update TM Analyses for whichyou used custom corrosion rates. To doso:

1. Locate the records that you willneed to update by running the fol-lowing query:

SELECT [MI_EQUIP000].[MI_EQUIP000_EQUIP_ID_C] "Equip-ment ID", [MI_TMLGROUP].[MI_TMLGROUP_ID_C] "TML Group ID",[MI Thickness Measurement Loca-tion].[MI_DP_ASSET_ID_CHR] "TMLAsset ID", [MI Thickness Meas-urement Location].[MI_DP_ID_CHR] "TML ID", [MI TML CorrosionAnalysis].[MI_TML_CA_A_CR_N]"Custom Calculation A Corros", [MITML Corrosion Analysis].[MI_TML_CA_B_CR_N] "Custom Calculation BCorros" FROM [MI_EQUIP000]JOIN_SUCC [MI_TMLGROUP] JOIN_SUCC [MI Thickness MeasurementLocation] JOIN_SUCC [MI TML Cor-rosion Analysis] ON {MI Has Cor-rosion Analyses} ON {MI HasDatapoints} ON {MIR_HSTMLGP}WHERE ([MI TML Corrosion Ana-lysis].[MI_TML_CA_A_CR_N] > 0AND [MI TML Corrosion Analysis].[MI_TML_CA_B_CR_N] > 0)

2. Use the Bulk Analyze tool toupdate TM Analyses associatedwith the Equipment and TMLGroup records returned by thisquery.

Note that these instructions assume that

N

In previous versionsof Meridium APM, ifyou used custom cor-rosion rates in yourTM Analyses, certainfields in the asso-ciated TML CorrosionAnalyses were pop-ulated with valuesusing the unit ofmeasure (UOM)inches per day insteadof IN/YR (TM) (i.e.,inches per year),which is the UOMthat is specified inthe properties of thefields. In order to cor-rect this issue in exist-ing records, you mustperform this step tomanually update TMAnalyses. For moreinformation aboutthis issue, see theV3.5.1 Release Notes.




you are using the baseline Equipmentand TML Group families. If you use cus-tom equipment families, you mustreplace the following values before run-ning the query in order to identify therecords requiring update:

l MI_EQUIP000 and MI_TMLGROUPwith your custom family IDs.

l MI_EQUIP000_EQUIP_ID_C and MI_TMLGROUP_ID_C with the field IDsused to identify these customequipment records.

Then, run the Bulk Analyze tool usingyour custom records.



Use Custom TML Analysis TypesThe baseline Meridium Enterprise APM database includes the Thickness MeasurementLocation family, which contains the TML Analysis Type field. This field is used to classifyTMLs based upon the collection method that will be used for recording Thickness Meas-urements at that location.

The TML Analysis Type field contains a list of values that is populated with the CorrosionInspection Type values from all Corrosion Analysis Settings records that are associatedwith the asset or TML Group to which the Thickness Measurement Location record islinked.

The values that are used to populate the Corrosion Inspection Type field in the Cor-rosion Analysis Settings family are stored in the System Code Table CITP (CorrosionInspection Type). In the baseline Meridium Enterprise APM database, this table containsthree System Codes: UT, RT, and TML. You can only create Thickness Measurement Loca-tion records with a given TML Analysis Type value if an associated Corrosion Analysis Set-tings record contains the same value in the Corrosion Inspection Type field.

Using the baseline functionality, you can separate Corrosion Analysis calculations intogroups based upon TML Analysis Type. If you want to use this functionality, you willwant to classify your TMLs as UT (measurements collected using ultrasonic thickness) orRT (measurements collected using radiographic thickness). This separation will be desir-able for some implementations. Other implementations will prefer not to separateTMLs according to collection method and instead perform calculations on the entiregroup of TMLs that exists for an asset. For these implementations, you will want to clas-sify all TMLs using the TML Analysis Type TML.

Depending upon your preferred implementation, you may choose to make one or moreof the following changes to the System Code Table CITP (Corrosion Inspection Type):

l Add System Codes if you want to classify TMLs using methods in addition to UTand RT.

l Delete System Codes that you do not want to use.l Modify the IDs and descriptions of the System Codes so that the classification

options are more intuitive to your users.

If you make changes to this System Code Table, keep in mind that the analysis types thatare stored in the System Code Table CITP (Corrosion Inspection Type) will be used whenyou create Corrosion Analysis Settings records, and therefore, will determine the ana-lysis types for which you can create Thickness Measurement Location records.

Additionally, in Thickness Measurement Location records, the TML Analysis Type fieldhas a baseline Default Value rule that is coded to present UT as the default value whenyou have defined the UT TML Analysis Type in your Corrosion Analysis (i.e., you have cre-ated a Corrosion Analysis Settings record with a Corrosion Inspection Type of UT). Youcould modify this rule if, for example, you wanted RT to be presented as the defaultvalue when you have defined the RT TML Analysis Type in your Corrosion Analysis (i.e.,



you have created a Corrosion Analysis Settings record with a Corrosion Inspection Typeof RT). To do this, you would modify the MI_TML_TYPE_CHR class as follows:

<MetadataField("MI_TML_TYPE_CHR")> _

Public Class MI_TML_TYPE_CHR

Inherits Baseline.MI_Thickness_Measurement_Location.MI_TML_TYPE_CHR

Public Sub New(ByVal record As Meridium.Core.DataManager.DataRecord, ByVal field AsMeridium.Core.DataManager.DataField)

MyBase.New(record, field)

End Sub

Public Overrides Function GetDefaultInitialValue() As Object

Return CStr("RT")

End Function

End Class

More information on customizing baseline rules is available here.



Install the Meridium Device Service

ŗIMPORTANT: This procedure needs to be repeated on every machine to which adatalogger will be connected.

The Meridium Device Service can be installed in the normal workflow when using data-loggers with Thickness Monitoring.

Steps

1. Access Dataloggers for the any asset or TML Group.

2. Select Send.

Note: A datalogger does not need to be connected.

The Meridium Device Service Not Found window appears.

3. Select the Download link.

MeridiumDevices.exe is downloaded.

4. Run MeridiumDevices.exe and follow the instructions in the installer.

The Meridium Device Service is installed.

5. In the Meridium Device Service Not Found window, select Continue.

Dataloggers can now be used with Thickness Monitoring.



Configure the Meridium Device ServiceAfter installing the Meridium Device Service, you can make changes to certain con-figuration settings. The Meridium Device Service is designed to function out of the box.Generally, you will only make changes to the configuration if you need to increase the cli-ent timeout period, or change the port the service uses (by default, port 2014).

Steps

1. In Windows Explorer, navigate to C:\Program Files\Meridium\Services.

2. Using a text editor, open the Meridium.Service.Devices.exe.config file.

3. In the text editor, navigate to the appSettings section (lines 24 to 28).

l On line 25, edit the port number used by the service.

Note: The datalogger settings in Thickness Monitoring must be mod-ified so that the port number matches the one defined in this step.

l On line 26, edit the timeout value in milliseconds. By default, the value forthis setting is 60000, or 1 minute.

l On line 27, if your organization utilizes a different URL protocol forMeridium Enterprise APM, edit the protocol the service should use. Forexample, http://* can be changed to https://*.

4. Save the file, and then close the text editor.

5. Restart the Meridium Device Service.

The Meridium Device Service configuration settings are updated.



Thickness Monitoring Functional Security Priv-ilegesMeridium Enterprise APM provides the following baseline Security Groups for use withThickness Monitoring and provides baseline family-level privileges for these groups:

l MI Thickness Monitoring Administratorl MI Thickness Monitoring Inspectorl MI Thickness Monitoring User

Access to certain functions in Meridium Enterprise APM is determined by membershipin these Security Groups. Note that in addition to the baseline family-level privileges thatexist for these Security Groups, users will also need at least View privileges for all cus-tomer-defined predecessor or successor families that participate in the Thickness Mon-itoring relationships. Keep in mind that:

l Users who will need to create new records in TM will need Insert privileges to thesefamilies.

l Users who will need to modify records will need Update privileges to these fam-ilies.

l Any user who should be allowed to delete TM records will need Delete privileges tothese families.

The following table summarizes the functional privileges associated with each group.

Function

Can be done by mem-bers of the MI Thick-ness MonitoringAdministrator Group?

Can be done bymembers of the MIThickness Mon-itoring InspectorGroup?

Can be done bymembers of the MIThickness Mon-itoring UserGroup?

ConfigureGlobalPreferences

Yes No No

ConfigureFamilyPreferences

Yes No No

Use the T-Min Caluc-lator

No Yes No

Archive Cor-rosion Rates No Yes No



Function

Can be done by mem-bers of the MI Thick-ness MonitoringAdministrator Group?

Can be done bymembers of the MIThickness Mon-itoring InspectorGroup?

Can be done bymembers of the MIThickness Mon-itoring UserGroup?

Reset theMaximumHistoricalCorrosionRate

Yes No No

ExcludeTMLs No Yes No

Renew TMLs No Yes No

Reset UserPreferences Yes No No

Set ColorCodingPreferences

Yes No No



Thickness Monitoring Security Groups and RolesThe following table lists the baseline Security Groups available for users within this mod-ule, as well as the baseline Roles to which those Security Groups are assigned.



MI Thickness Monitoring Administrator MI Mechanical Integrity Administrator

MI Thickness Monitoring Inspector




MI Thickness Monitoring User




The following table lists the baseline family-level privileges that exist for these SecurityGroups.

FamilyMI Thickness Mon-itoring Admin-istrator

MI Thickness Mon-itoring Inspector

MI ThicknessMonitoringUser

Entity Family

Corrosion View, Update, Insert View, Update, Insert View, Update,Insert

Datapoint View, Update, Insert View, Update, Insert View, Update,Insert

Datapoint Meas-urement



View, Update,Insert


Human Resource View, Update, Insert,Delete View View






Inspection Task View View, Update View

Materials of Con-struction View View View

Meridium ReferenceTables


Resource Role View, Update, Insert,Delete View View

Security Group View View View

Security User View View View

Settings View, Update, Insert View, Update, Insert View

Task Execution View, Insert View, Insert View

Thickness Mon-itoring Task

View, Update, Insert,Delete View, Update, Insert View, Update,

Insert

TML Group View, Update, Insert,Delete


Relationship Family

Belongs to a Unit View, Update, Insert,Delete View, Update, Insert View, Update,

Insert

Equipment HasEquipment View View View

Group Assignment View View View

Has Archived Cor-rosion Analyses




Has Archived Cor-rosion Analysis Set-tings




Has Archived Sub-component AnalysisSettings




Has Archived Sub-component Cor-rosion Analyses









Has Corrosion Ana-lyses




Has Corrosion Ana-lysis Settings




Has Datapoints View, Update, Insert,Delete



Has Measurements View, Update, Insert,Delete



Has Roles View, Update, Insert,Delete View View

Has Task Execution View, Insert View, Insert View

Has Task Revision View, Insert View, Insert View

Has Tasks View, Insert View, Insert View, Insert

Has TML Group View, Update, Insert,Delete


Is a User View View View

User Assignment View View View