ASWP

About the Asset Strategy Work Process
The Asset Strategy Work Process is focused on proactive asset management plans that are
designed for the purpose of mitigating risks. The Asset Strategy Work Process consists of
the steps that are outlined in the following table.
Step Description
1
Evaluate asset risk

and performance.
Details
Allows you to:
Identify and qualify unmitigated risks.

Define how your current maintenance plans mitigate
risks.
Identify gaps in mitigation.
Define regulatory actions.
Mitigate risks with Allows you to assess and document what is currently being
an action plan.
done to mitigate risk as well as identify additional actions to
mitigate risk.
Allows you to review your current mitigation plan to:
Optimize
mitigations.
Identify actions that have no current value to see if they
can be removed or replaced.
Identify less intrusive actions that supersede other, more
intrusive actions.
Document areas that need improving.
Document your decision process.
Review the impact of the new strategy on risk and cost,

compared to the original strategy.
Allows you to communicate the following information that was
documented in previous steps of the work process:
Communicate an
improved plan.
The updated strategy profile.

What changed from the original strategy.
Why the updated strategy was selected.
The return on investment value.
The risk reduction numbers.

Allows you to implement the new strategy into your work
management system. Specifically, during this step, you will
want to implement:
Implement the
Strategy.
Recommendations that were identified.

Processes to measure the effectiveness of the strategy.
Document the decision-making process behind the new

strategy.
A process for obtaining and communicating feedback

from the workforce in the field.
Allows you to execute the work via your organization's work
management system and current processes. Specifically, during
this step, you will want to:
Execute the
Strategy.
Ensure the work is being documented.

Ensure the workforce understands the value in executing
the plan.
Review work history to maintain and ensure regulation

compliance.
The following image shows an illustration of how the steps in the Asset Strategy Work
Process relate to one another. Each step in the work process is represented by a green
circle. In addition, you can see that the entire work process is built upon the APM
Foundation Work Process, whose components are represented by the blue boxes.
Within the Meridium APM product, each of the steps listed above can be accomplished
using one or more of the following modules:
Asset Strategy Management (ASM)

Asset Strategy Implementation (ASI)
Asset Strategy Optimization (ASO)
Reliability Centered Maintenance (RCM) and Failure Modes and Effects Analysis
(FMEA)
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.
Asset Strategy System Requirements

Multiple licenses are required to take advantage of Asset Strategy functionality. In
addition to the following licenses, your system must contain the basic Meridium APM
system architecture:
Asset Strategy Management (ASM)

Asset Strategy Implementation (ASI)
Asset Strategy Optimization (ASO)
Reliability Centered Maintenance (RCM) and Failure Modes and Effects Analysis
(FMEA)
After you have configured the basic system architecture and licensed Asset Strategy
modules, you will need to perform some configuration steps.
First-Time Deployment Workflow

Deploying the Asset Strategy Work Process for the first time includes completed multiple
steps, which are outlined in the table in this topic. All of the steps are required to fully
implement the Asset Strategy Work Process. These steps provide all of the information
that you need to deploy Asset Strategy with the basic Meridium APM system
architecture.
Step Task
1
Configure the Asset Strategy Management module.
Configure the Asset Strategy Implementation

module.
Configure the Asset Strategy Optimization module.
Configure one of the following modules:

4
Reliability Centered Maintenance
Failure Modes and Effects Analysis
Upgrade Workflow
You can upgrade to V3.6.0.0.0 using the instructions that are provided in the Installation,
Upgrade, and Configuration documentation for each Asset Strategy module:
Asset Strategy Management

Asset Strategy Implementation
Asset Strategy Optimization
Reliability Centered Maintenance
Failure Modes and Effects Analysis
Asset Strategy User Instructions

The user instructions for the Asset Strategy modules are provided in the documentation
for the related modules. Documentation for the Asset Strategy dashboard is provided in
the Asset Strategy Reference Information documentation.
Accessing the Asset Strategy Dashboard

To access the Asset Strategy dashboard:
On the Meridium APM Framework main menu, click Go To, point to Asset
Strategy, and then click Dashboard.
The Dashboard page appears, displaying the Asset Strategy dashboard.
Aspects of the Asset Strategy Dashboard

The Asset Strategy dashboard contains sections that display information about the pieces
of equipment and locations that you analyze using Asset Strategy modules.
The Asset Strategy dashboard contains the following sections:
Content Filter section

Total Unplanned Maintenance Costs section
Evaluate Risk and Performance section
Mitigate Risk & Optimize Action Plan section
Communicate, Implement, and Execute Plan section
Criticality Distribution section
Asset Strategy Workflows section
In addition, the dashboard contains several hidden sections, which you can add to the
dashboard or use as a starting point for defining your own sections.
Note: The baseline Asset Strategy dashboard contains the maximum amount of content
that can be displayed without introducing a time-out error when opening the page. If you
want to add content, including any of the hidden content, we recommend that you also
remove or modify some of the baseline content to ensure that the dashboard performance
is not degraded.
Content Filter
The Content Filter section is a configured Content Filter section that contains lists that are
used to filter the data that is displayed in other sections on the dashboard.
The Content Filter section contains the following lists:
Site: Contains a list of all the values that are stored in the Functional Location
Description field in Functional Location records whose Catalog Profile
Description field contains the value Site. For example, in the following image,
consider the query results, which indicate that four Functional Location records
contain the value Site in the Catalog Profile Description field.
As a result, on the dashboard, the values appear in the Site list, as shown in the following
image.
Area: Contains a list of all the values that are stored in the Functional Location
Description field in Functional Location records that meet the following criteria:
Their Catalog Profile Description field contains the value Area.
Their Superior Function Location field contains the value that is stored in
the Functional Location field in the record whose Functional Location
Description field contains the value that you selected in the Site list.
For example, suppose that you select Meridium Roanoke Production in the Site list, and
the associated Functional Location record (record A) contains the value MRD-ROA in
the Functional Location field. If another Functional Location record (record B) contains
the value Area in the Catalog Profile Description field and MRD-ROA in the Superior
Functional Location field, the value in the Functional Location Description field in that
record (record B) will appear in the Area list.
Unit: Contains a list of all the values that are stored in the Functional Location
Description field in Functional Location records that meet the following criteria:
Their Catalog Profile Description field contains the value Unit.
Their Superior Function Location field contains the value that is stored in
the Functional Location field in the record whose Functional Location
Description field contains the value that you selected in the Area list.
For example, suppose that you select Meridium Roanoke Chemicals in the Area list, and
the associated Functional Location record (record A) contains the value MRD-ROACHEM in the Functional Location field. If another Functional Location record (record B)
contains the value Unit in the Catalog Profile Description field and MRD-ROA-CHEM in
the Superior Functional Location field, the value in the Functional Location Description
field in that record (record B) will appear in the Unit list.
Although the lists allow you to select values only in Functional Location records, the
Meridium APM system also finds the Equipment records that are linked to those
Functional Location records. Whenever other content on the dashboard is being filtered
based upon your selections in the Content Filter section, that content is being filtered
based upon the selected Functional Location records and the Equipment records to which
they are linked. For this reason, this documentation refers to Functional Location records
and Equipment records that are returned by the filters.
Note: If you store equipment and location data in families other than the baseline
Equipment and Functional Location families, you will need to modify the underlying
queries accordingly. Also, even if you do use the baseline Functional Location family, if
you identify sites, areas, and units using a value other than Site, Area, and Unit or a field
other than Catalog Profile Description, you will need to modify the underlying queries
accordingly.
The values that you select in these lists will be used to filter the content that is displayed
in the following sections:
Total Unplanned Maintenance Costs

Criticality Distribution
Evaluate Risk and Performance
Mitigate Risk and Optimize Action Plan (only the % of Extreme Criticality Assets
with Strategy and % of Very High Criticality Asses with Strategy measures)
Total Unplanned Maintenance Costs

The Total Unplanned Maintenance Costs section is a configured Chart - Series section
that displays a bar graph that plots on a monthly basis, for the past 12 months (including
the current month), the sum of the values in the Maintenance Cost field in all Work
History records that meet the following criteria:
They are linked to the Functional Location and Equipment records that are
returned by the Filter Content section.
They contain the value Repair in the Event Type field.
For example, suppose that:
You select the value Roanoke in the Site list.

The Functional Location record Roanoke is linked to the Equipment record Pump.
The Functional Location record Roanoke is linked to a Work History record

containing the following values in the following fields:
Event Start Date: 7/17/2013
Event Type: Repair
Maintenance Cost: 100
The Equipment record Pump is linked to a Work History record containing the
following values in the following fields:
o
Event Start Date: 7/15/2013
Event Type: Repair
Maintenance Cost: 50
In this case, the graph for the month of July will account for the maintenance cost in both
Work History records (i.e., the one linked to the Functional Location record and the one
linked to the Equipment record). Assuming that no other Work History records meet the
requirements, the graph for July would look like the one in the following image, where
the total unplanned maintenance cost is $150 (100 + 50).
Evaluate Risk and Performance

The Evaluate Risk and Performance section is a configured Measures - General section
that displays the measure % of Assets with Criticality Assigned, which displays the
percentage of Functional Location and Equipment records that are returned by the
Content Filter section and are linked to a Risk Assessment record through the Has Risk
relationship. The target for this measure is 95%, meaning that ideally, at least 95% of the
Functional Location and Equipment that are returned by the filters should be linked to a
Risk Assessment record.
Note: Equipment and Functional Location records are linked to Risk Assessment records
when you follow the ACA workflow.
In the previous image, you can see that only 5% of Functional Location and Equipment
records that are returned by the filters are linked to a Risk Assessment record.
Mitigate Risk & Optimize Action Plan

The Mitigate Risk & Optimize Action Plan section is a configured Measures - General
section that displays information about locations, equipment, and their associated Asset
Strategies.
The following measures are displayed in the Mitigate Risk & Optimize Action Plan
section:
% of Extreme Criticality Assets with Strategy: Displays the percentage of

Functional Location and Equipment records that are returned by the Content Filter
section and meet the following criteria:
They are linked to an Asset Strategy record.
They are linked to a Risk Assessment record, and their risk rank falls
within the Extreme threshold.
The target for this measure is 90%, meaning that ideally, at least 90% of the Functional
Location and Equipment records that are returned by the filters and have an Extreme risk
rank should be linked to an Asset Strategy record.
% of Very High Criticality Assets with Strategy: Displays the percentage of

They are linked to an Asset Strategy record.
within the Very High threshold.
The target for this measure is 80%, meaning that ideally, at least 80% of the Functional
Location and Equipment records that are returned by the filters and have a Very High risk
rank should be linked to an Asset Strategy record.
% of Strategies Approved: Displays the percentage of all Asset Strategies that are
set to the Active state. The target for this measure is 90%, meaning that ideally, at
least 90% of your Asset Strategies should be set to the Active state.
% of Strategies Draft: Displays the percentage of all Asset Strategies that are set
to the Draft state. The target for this measure is 20%, meaning that ideally, no
more than 20% of your Asset Strategies should be set to the Draft state.
Communicate, Implement, and Execute

Plan
The Communicate, Implement, and Execute Plan section is a configured Measures General section that displays information about locations, equipment, and their associated
Asset Strategies.
The following measures are displayed in the Communicate, Implement, and Execute Plan
section:
% of Actions Implemented: Displays the percentage of Actions that have been

used to create work item records in an ASI Implementation Package. Specifically,
the underlying query looks for Action Revision records that are linked to work
item records through the Implements Action relationship. The target for this
measure is 90%, meaning that ideally, at least 90% of your Actions should have
been used to create work item records in ASI.
% of Extreme Criticality Strategies Implemented: Displays the percentage of
They are linked to an Asset Strategy record that is linked to an

Implementation Package record.
within the Extreme threshold.
The target for this measure is 95%, meaning that ideally, for the Functional Location and
Equipment records that are returned by the filters and have an Extreme risk rank and an
associated Asset Strategy, 95% of those Asset Strategies should be linked to an
% of Very High Criticality Strategies Implemented: Displays the percentage of

They are linked to an Asset Strategy record that is linked to an
within the Very High threshold.
The target for this measure is 95%, meaning that ideally, for the Functional Location and
Equipment records that are returned by the filters and have a Very High risk rank and an
associated Asset Strategy, 95% of those Asset Strategies should be linked to an
The Criticality Distribution section is a configured Chart - Category section that displays
a doughnut chart representing the risk ranks of all Functional Location and Equipment
records that are returned by the Content Filter section. The chart is divided into sections
based upon the values in the Risk Rank field in the Risk Assessment records that are
linked to the Functional Location and Equipment records.
Below the chart, a legend displays the color that is associated with each value. In the
preceding image, you can see that there are 28 Equipment or Functional Location records
whose risk rank is Very High.
Asset Strategy Workflows

The Asset Strategy Workflows section is a configured Hyperlinks section that displays
links to the start pages for the modules that are included in the Asset Strategy workflow
and to the Policy Manager module.
The Asset Strategy Workflows section contains the following links:
Criticality Analysis: Displays the Asset Criticality Analysis Start Page.

Failure Modes and Effects Analysis: Displays the FMEA Start Page.
Reliability Centered Maintenance Analysis: Displays the RCM Start Page.
Strategy Management: Displays the ASM - Start Page.
Strategy Implementation: Displays the Asset Strategy Implementation Start Page.
Policy Manager: Displays the Policy Manager Start Page.
Hidden Sections
The Asset Strategy dashboard includes the following sections that are hidden by default:
Hidden Measures: A configured Measures - General section that displays

additional information about your locations, equipment, and strategies. The
Hidden Measures section contains the following measures:
% of RCM FMEA Risks Without Recommendations
# of Risks Without Actions
# of Asset Strategies with Actions Implemented in EAM
% of Non-Critical Assets with Strategy
% of Extreme Criticality Assets with an Analysis
% of Strategies in Review
Cost of Events per Month by Asset: A configured Chart - Series section that
displays a bar graph that plots on a monthly basis, for the past 12 months
(including the current month), the sum of the values in the Total Cost field in all
Work History records that are linked to the Equipment records that are returned by
the Filter Content section. The chart displays Equipment IDs on the x-axis.
Total Cost of Unreliability: A configured Chart - Series section that displays a bar
graph that plots on a monthly basis, for the past 12 months (including the current
month), the sum of the values in the Total Cost field in all Work History records
that meet the following criteria:
They are linked to the Functional Location and Equipment records that are
returned by the Filter Content section.
They contain the value Repair in the Event Type field.
The chart displays months on the x-axis.
About the Asset Strategy Catalog Folder

Structure
The main Asset Strategy Catalog folder is \\Public\Meridium\Modules\Asset Strategy.
This folder contains subfolders that store a dashboard and queries that are used to display
content on the dashboard.
You can store additional items in the main Asset Strategy Catalog folder or in its
subfolders. You can also create new subfolders to store additional items.
Note: All of the Public folders exist by default. Any item in a Public folder is also
available in the corresponding Baseline folder. Throughout this documentation, we refer
to the items in the Public folder.
Dashboards Folder
The dashboard listed in the following table is stored in the Catalog location
\\Public\Meridium\Modules\Asset Strategy\Dashboards. The dashboard is listed by name
in the table. The dashboard name and caption are the same.
Dashboard
Behavior and Usage
Asset Strategy Dashboard Displays the Asset Strategy dashboard on the Dashboard
page.
Dashboard Queries Folder

The following table lists the queries that are stored in the Catalog location
\\Public\Meridium\Modules\Asset Strategy\Queries\Dashboard Queries. The queries are
listed by name in the table. The query name and caption are the same.
Query
Behavior and Usage
Cost of Events per Month Used by the Cost of Events per Month by Asset section.
by Asset
Used by the Criticality Distribution section.
Filter Widget
Used by the Content Filter section.
Filtered Assets
Used by various measures to determine equipment and

location criticality.
Filtered Assets With

Criticality

Non Critical Filtered

Assets

Number of Risks Without Used to display the # of Risks Without Actions measure in the
Actions
Hidden Measures section.
Number Strategies
Implemented in EAM
Used to display the # of Asset Strategies Implemented in

EAM measure in the Hidden Measures section.
Percentage of Actions
Implemented
Used to display the % of Actions Implemented measure in the

Communicate, Implement, and Execute Plan section.
Percentage of Assets with Used to display the % of Assets with Criticality Assigned
Criticality Assigned
measure in the Evaluate Risk and Performance section.
Percentage of Critical
Assets with an Analysis
Used to display the % of Extreme Criticality Assets with an

Analysis measure in the Hidden Measures section.
In addition to the All Criticality Definitions query (in the
Percentage of Criticality Criticality Definitions Catalog folder), this query is used to
Value Assets with Strategy display the following measures in the Mitigate Risk and
Optimize Action Plan section:
Percentage of Criticality
Value Strategies
Implemented
% of Extreme Criticality Assets with Strategy
% of Very High Criticality Assets with Strategy
In addition to the All Criticality Definitions query (in the

Criticality Definitions Catalog folder), this query is used to
display the % of Extreme Criticality Strategies Implemented
measure in the Communicate, Implement, and Execute Plan

section.
Percentage of Non Critical Used to display the % of Non-Critical Assets with Strategy
Assets with Strategy
measure in the Hidden Measures section.
Percentage of RCM
FMEA Risks Without
Recommendations
Used to display the % of RCM FMEA Risks Without

Recommendations measure in the Hidden Measures section.
Used to display the following measures:
Percentage of Strategies In
State Value
% of Strategies Approved (in the Mitigate Risk and

Optimize Action Plan section)
% of Strategies Draft (in the Mitigate Risk and
Optimize Action Plan section)
% of Strategies in Review (in the Hidden Measures
section)
Total Cost of Unreliability Used by the Total Cost of Unreliability section.

Total Unplanned
Maintenance Costs
Used by the Total Unplanned Maintenance Costs section.
Criticality Definitions Folder

The queries that are stored in the Catalog location \\Public\Meridium\Modules\Asset
Strategy\Queries\Dashboard Queries\Criticality Definitions are used to determine the risk
thresholds into which each piece of equipment's or location's risk rank falls. The queries
are configured in the baseline database to correspond to the risk thresholds that are
defined in the baseline Risk Matrix (i.e., the Standard Practice Risk Matrix). For
example, the baseline query Extreme Criticality Definition indicates that a risk rank is
considered Extreme if it is greater than or equal to 1,000 and less than or equal to
1,000,000,000.
Together, all the queries in this folder are used to determine which equipment, locations,
and strategies to return in the Asset Strategy dashboard measures that look at equipment
and location risk rank.
Note: If you are using a Risk Matrix that uses risk thresholds that differ from those in the
baseline Risk Matrix, you will need to modify these queries accordingly. If you do
modify the queries, remember to review the names of the corresponding dashboard
sections and modify them if needed (e.g., % of Extreme Criticality Assets with Strategy).
Overview of Asset Strategy

Management
The Meridium APM Asset Strategy Management (ASM) module lets you create a
strategy, which is a set of actions that represent a plan to optimize equipment and
location performance to achieve business benefits.
Using ASM, you can create the following types of strategies:
Asset Strategy: The combination of Actions and Risks that are associated with a
piece of equipment or location.
System Strategy: A collection of Asset Strategies.
Unit Strategy: A collection of System Strategies.
In other words, ASM allows you to create Asset Strategies to define ways in which
equipment and locations can fail and the actions that you want to perform to prevent
those failures and reduce their consequences. After your database contains multiple Asset
Strategies, you can bundle those Asset Strategies into a System Strategy. Likewise, after
your database contains multiple System Strategies, you can bundle those System
Strategies into a Unit Strategy. A Unit Strategy, therefore, represents a global plan for
multiple pieces of equipment and locations.
Because strategies are built as a hierarchy, where Asset Strategies roll up to System
Strategies and System Strategies roll up to Unit Strategies, before you can build a System
Strategy or a Unit Strategy, you will need to build an Asset Strategy. D
ASM System Requirements

The ASM and ASI license is required to take advantage of ASM. In addition, your system
must contain the basic Meridium APM system architecture.
After you have installed and configured the basic system architecture, you will need to
perform some configuration tasks specifically for the ASM module.
When the ASM module is active, the Asset Strategy Implementation (ASI) module is also
activate. To use the ASM and ASI integration to its full advantage, you will need to
perform some configuration tasks specifically for the ASI module. This module may
require additional hardware or software.
Overview of the ASM Data Structure

ASM helps you create a strategy through a cycle of proposing changes that result in a
plan that maintains a piece of equipment or location while posing the least possible risk
and incurring the least possible cost. Because it might take months of research and
discussion for a team to decide upon the proposed changes to an existing strategy,
companies need a way to track proposed strategy changes separately from the current
strategy. This tracking method allows management to review the cost difference and risk
difference between the proposed changes and the current implementation.
ASM facilitates the creation of multiple records to help you store information about a
suggested strategy separately from information about the current strategy. The first step to
creating any strategy is to create an Asset Strategy record. When you first save an Asset
Strategy record, Meridium APM creates the following records, which are linked
automatically to the Asset Strategy record:
Proposed Strategy
Active Strategy
These records serve as containers to identify the strategy using information such as the
strategy ID and description. The records will be linked automatically to other records as
you expand the strategy by adding Action records and Risk records and assessing the risk.
Ultimately, the Proposed Strategy record and the records to which it is linked represent
the strategy that you propose the company implement. The Active Strategy record and the
records to which it is linked represent the strategy that the company is currently
implementing.
When you modify an Asset Strategy that is in the Active state, causing its state to change
to Modified, Meridium APM captures your changes in the Proposed Strategy record and
other records to which it is linked. When you later activate the strategy, the Meridium
APM system copies the information from the Proposed Strategy record (and appropriate
linked records) to the Active Strategy record (and appropriate linked records).
The Proposed Strategy record and its linked records are then identical to the Active
Strategy record and its linked records until additional changes are made, which causes the
cycle to continue.
ASM families can also participate in additional relationships with families in the Asset
Criticality Analysis (ACA) data model, if an Asset Criticality Analysis System record is
promoted from ACA to ASM.
Illustration of the ASM Data Model

The following diagram illustrates how families are related to one another within the ASM
data model. In the following image, boxes represent entity families, and arrows represent
relationship families that are configured in the baseline database.
Notice that several revision families exist in the ASM data model. Records are created in
these families automatically when you modify certain information about an Asset
Strategy.
Illustration of the ASM Data Model

Integrated with Asset Criticality
Analysis
A System Strategy can be created automatically when an Asset Criticality Analysis
System record is promoted from Asset Criticality Analysis (ACA) to ASM. The following
illustration shows how the families in the ASM data model are related to the families in
the ACA data model. In this illustration, the boxes represent entity families, and the
arrows represent relationship families. You can determine the cardinality of a relationship
by the direction of the arrow (i.e., the family to which the arrow points is the successor
family).
About Revision Families in the ASM

Data Model
The following revision families exist in the ASM data model:
Strategy Revision
Action Revision
Risk Revision
Risk Assessment Revision
Records are created in these families when you modify certain information about an
Asset Strategy. The following table explains when these records are created.
This action:
Activating an Asset Strategy for the first
time
...Creates this record:

Strategy Revision
Action Revision
Risk Revision
Activating an Asset Strategy after
modifying an Action record
Action Revision

modifying a Risk record
Risk Revision

modifying a Risk Assessment record that is Risk Assessment Revision
linked to an Action record
Strategy Revision
Activating a System Strategy if the
underlying Asset Strategies have never been Action Revision
activated
Risk Revision
1
1. If you activate an Asset Strategy after modifying a Risk Assessment record that is
linked to a Risk record, a Risk Assessment Revision is not created. The Risk Revision
record that is created as a result of the change is updated to contain the new risk rank, so
a Risk Assessment Revision record is not needed.
Asset Strategies
An Asset Strategy is the combination of actions and risks that are associated with a piece
of equipment or location. An Asset Strategy consists of:
Multiple Risk records, which represent ways in which the piece of equipment or
location can fail.
Multiple Action records, which represent the physical actions that you want to
perform to maintain the piece of equipment or location.
Multiple Risk Assessment records, which represent the Risk Rank associated with
a failure.
The first step in building an Asset Strategy is to create an Asset Strategy record. You can
then further define the Asset Strategy by adding Risks and Actions. After your database
contains one or more Asset Strategies, you can build System Strategies. Then, you can
build Unit Strategies.
When reviewing the ASM data model, you will notice that each Asset Strategy record is
linked directly to:
One Active Strategy record.
-and
One Proposed Strategy record.
The Active Strategy record and the records to which it is linked represent the strategy that
you are currently using to maintain the piece of equipment or location. Likewise, the
Proposed Strategy record and the records to which it is linked represent the strategy that
you want to start using to maintain the piece of equipment or location.
In other words, for each Asset Strategy, there is always one Active Strategy and one
Proposed Strategy.
System Strategies
A System Strategy is a collection of Asset Strategies. The first step in building a System
Strategy is to create a System Strategy record. You can then further define the System
Strategy by adding one or more Asset Strategies. Then, you can build Unit Strategies.
Unit Strategies
A Unit Strategy is a collection of System Strategies. The first step in building a Unit
Strategy is to create a Unit Strategy record. You can then further define the Unit Strategy
by adding one or more System Strategies.
Active Strategies and Proposed

Strategies
Note: The information in this topic also applies to Asset Strategy Templates but is limited
to Asset Strategies to simplify the discussion.
When reviewing the ASM data model, you will notice that each Asset Strategy record is
linked directly to:
-and
The Active Strategy record and the records to which it is linked represent the strategy that
you are currently using to maintain the piece of equipment or location. Likewise, the
Proposed Strategy record and the records to which it is linked represent the strategy that
you want to start using to maintain the piece of equipment or location.
In other words, for each Asset Strategy, there is always one Active Strategy and one
Proposed Strategy. Throughout this documentation, we refer to the following types of
Asset Strategies:
Active Strategy: Represents the strategy that you are currently using to maintain
the piece of equipment or location.
Proposed Strategy: Represents the strategy that you want to start using to maintain
the piece of equipment or location.
When you create an Asset Strategy, the Active Strategy and the Proposed Strategy are
created automatically and are identical. As you make changes to the Asset Strategy by
adding Risks and Actions and assessing the risk, those changes are stored in the Proposed
Strategy. When you activate the Proposed Strategy, the contents of the Proposed Strategy
are copied to the Active Strategy. And once again, the Active Strategy and Proposed
strategy are identical.
Consider the following image, which illustrates the Proposed Strategy and Active
Strategy that are created when you create an Asset Strategy.
Now, consider the following image, which illustrates what happens to the Proposed
Strategy when you add an Action, Risk, and Risk Assessment to the Asset Strategy.
You can see from this image that only the Proposed Strategy is affected. The Active
Strategy remains unchanged.
Finally, consider the following image, which illustrates what happens when you activate
the Proposed Strategy.
You can see from this image that the Proposed Strategy and the Active Strategy are now
identical again. The process would begin again if you were to modify the Asset Strategy
in some way. For example, if you were to add a new Action, the following image
illustrates how the Proposed Strategy would be updated, where the new Action is colored
purple.
Asset Strategy Templates

An Asset Strategy Template represents an Asset Strategy that you plan to reuse by
applying it to additional Asset Strategies. The process of creating an Asset Strategy
Template from scratch is almost identical to the process of creating an Asset Strategy.
Additionally, you can create an Asset Strategy Template via the following methods:
From an existing Asset Strategy.
From an existing RCM FMEA Analysis.
When working with Asset Strategy Templates, you can add Action records and Risk
records and manage Risk Assessments.
Risks
A Risk identifies a way in which the piece of equipment or location can fail and the
consequence of the failure. This consequence is presented as a risk rank value, which is
determined from the values that you select in the Risk Assessment interface that appears
when you create a Risk. After you have created an Asset Strategy record, you can begin
adding Risks to the Asset Strategy.
The values you specify in a Risk are stored in a Risk record. Throughout this
documentation, unless it is necessary to refer to the record itself, however, we use the
term Risk.
Actions
An Action identifies the physical ways in which you maintain a piece of equipment or
location. For example, an Action might indicate that you want to perform a visual
inspection of a piece of equipment. After you have created an Asset Strategy record, you
can begin adding Actions to the Asset Strategy.
The values you specify in an Action are stored in an Action record. Throughout this
documentation, however, unless it is necessary to refer to the record itself, we use the
term Action.
About State Configuration in ASM

ASM leverages State Configuration Roles, which you can assign to Security Users to
manage who can transition strategies from one state to another.
In the baseline Meridium APM database, no State Configuration Roles are assigned to
any state in the Asset Strategy State Configuration or the Asset Strategy Template State
Configuration. An administrative user can assign State Configuration Roles to these
states, if desired.
Throughout ASM, some options will be disabled based upon whether the current user is
assigned to the State Configuration Role that is required to perform that action. In other
words, if an action will change the state of the strategy (e.g., adding an Action record)
and the current user does not have permission to change the state, all options that would
cause the state to change will be disabled. For example, consider the following scenario:
An administrative user has specified that only members of the Asset Strategy
Modifier State Configuration Role can transition an Active Strategy to the
Modified state.
Only members of the ASM Analyst Security Group are assigned to the Asset
Strategy Modifier State Configuration Role.
A user is logged in to Meridium APM as a member of only the ASM Reviewer
Security Group.
In this case, when the ASM Reviewer opens on the Asset Strategy Actions page an Asset
Strategy in the Pending Review state, the following options will be disabled on that page:
The Add Action button.

The Remove Action button.
The Undo Action button.
The Assign New Risk button.
The Assign Existing Risk button.
The Action datasheet.
The Risk Assessment datasheet.
If NO State Configuration Roles are specified for State Configuration, as in the baseline
database, all options will be available to all users, and state changes will not be restricted.
To take full advantage of the features in ASM, we recommend that you assign members
of the ASM Security Groups to a corresponding State Configuration Role.
Asset Strategy State Configuration

The following diagram shows the states and operations that exist in the baseline State
Configuration for the Asset Strategy family. You can use this diagram to determine which
operations will appear on the Operations menu when you are viewing an Asset Strategy.
The Operations menu will display any operation to which the current Asset Strategy
record can be transitioned from its current state.
States and Operations
Initial State
The Draft state is the initial state of all new Asset Strategy records.
Datasheet Configuration
By default, states and operations will appear on the datasheet when you are viewing an
Asset Strategy record in the Record Manager.
Reserved States and Operations

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

By default, NO State Configuration Roles are assigned to any state in the Asset Strategy
State Configuration. If desired, you can assign State Configuration Roles to any state.
Asset Strategy Template State

Configuration
The following diagram shows the states and operations that exist in the baseline State
Configuration for the Asset Strategy family. You can use this diagram to determine which
operations will appear on the Operations menu when you are viewing an Asset Strategy.
The Operations menu will display any operation to which the current Asset Strategy
record can be transitioned from its current state.
Initial State
The Draft state is the initial state of all new Asset Strategy Template records.
Asset Strategy Template record in the Record Manager or the Bulk Data Form.
By default, all states and operations displayed in the preceding diagram are reserved. This
means that you cannot remove or modify any of these states or operation. You can,
however, add your own states and operations to the State Configuration.

By default, NO State Configuration Roles are assigned to any state in the Asset Strategy
State Configuration. If desired, you can assign State Configuration Roles to any state.
About the Cancel Operation

The Cancel operation is available on the Operations menu for Asset Strategies that are in
the Modified state. When you use the Cancel operation, the Meridium APM system will:
Change the state from Modified to Active.
-AND
Revert ALL the changes that were made to the strategy since the last time it was
activated.
In other words, all your changes are discarded, and the Asset Strategy is restored to the
state in which it existed prior to making your changes.
For example, suppose you added multiple Actions and Risks to an Asset Strategy and
modified multiple values in existing Actions, and now you realize that those changes
belong to a different Asset Strategy. In this case, you can use the Cancel operation to
automatically undo the changes from the Asset Strategy and restore it to the way it was
before you made the changes.
Managing Records for ASM Families

To ensure data integrity, records that make up strategies in ASM should be created and
managed using only the tools provided in the Asset Strategy Management module.
Therefore, the Meridium APM system prevents you from creating or modifying records
in certain families via the Record Manager and Bulk Data Form.
The following table lists the families that can be managed only within ASM and the page
in ASM to which you will be directed via the link above the Datasheet list when you are
viewing a record in one of these families via the Record Manager.
Family
Page in ASM
Asset Strategy
Strategy Overview
Active Strategy
Strategy Overview
Proposed Strategy
Strategy Overview
Asset Strategy Template
Strategy Overview
System Strategy
System Overview
Unit Strategy
Unit Overview
Action
Actions
Risk
Risks
Strategy Revision
Revision History
Action Revision
Revision History
Risk Revision
Revision History
Revision History
Accessing the ASM - Start Page

To access the ASM - Start Page:
Strategy, and then click Asset Strategy Management.
The ASM - Start Page appears.
Aspects of the ASM - Start Page

The ASM - Start Page serves as the starting point for the tasks that you can perform in
Meridium APM Asset Strategy Management. You can access each task via a link on this
page. Note that the links on this page do not suggest a recommended workflow but rather
allow you to access certain features that you will need to use as part of managing
strategies.
The following links are available:
Create Strategy: Displays the Strategy Type dialog box, where you can select the
type of strategy you want to create: Asset Strategy, System Strategy, or Unit
Strategy. Note that if you do not have Insert privileges to the Asset Strategy
family, Meridium APM will display a message after you click the link, indicating
that your security privileges are insufficient.
Search for Strategy: Displays a strategy search page, where you can search for an
existing Asset Strategy, System Strategy, or Unit Strategy. Note that the search
page that you last viewed will be displayed when you click the Search for
Strategy link. For example, if you last viewed the ASM - Asset Strategy Search
page, this page will appear when you click the Search for Strategy link the next
time.
If you do not have View privileges to the Asset Strategy family, a message appears after
you click the link, indicating that your security privileges are insufficient.
Import Strategy: Displays the Open window, where you can:
-OR
Select a Microsoft Excel file to import to create a new Asset Strategy.
Select an existing Task record to use as the basis for creating or updating
an Asset Strategy.
Note that if you do not have Insert privileges to the Asset Strategy family, a message
appears after you click the link, indicating that your security privileges are insufficient.
Manage Templates: Displays the ASM - Asset Strategy Template Search page,
where you can search for an existing Asset Strategy Template record or create a
new one. Note that if you do not have View privileges to the Asset Strategy
family, a message appears after you click the link, indicating that your security
privileges are insufficient.
Import Strategy Template: Displays the Open window, where you can select a
Microsoft Excel file to import to create a new Asset Strategy Template.
Perform Administrative Tasks: Displays the ASM - Administration page, where
you can define the queries that you want to use for searching for strategies. Note
that only Super Users and members of the MI ASM Administrator Security Group
can see this link.

Deploying and configuring ASM for the first time includes completing multiple steps,
which are outlined in the table in this topic. The steps in this section of the documentation
provide all the information that you need to deploy and configure ASM on top of the
basic Meridium APM system architecture.
Whether a step is required or optional is indicated in the Required/Optional cell. Steps
are marked as Required if you must perform the step to take advantage of ASM
functionality.
The person responsible for completing each task may vary within your organization. We
recommend, however, that the steps be performed in relatively the same order in which
they are listed in the table.
Step Task
1
Required/Optional Notes
This step is necessary
only if you are using
If you are using families outside of the Optional
families outside the
baseline Equipment and Functional
baseline Equipment
Location families, review the ASM
and Functional
Location families to
store equipment and
location data.
data module to determine which

relationship definitions you will need
to modify to include your custom
equipment and location families.
Modify any relationship definitions as
needed via the Configuration Manager
application.
2
Assign Security Users to one or more

of the ASM Security Groups via the
Configuration Manager application.
Required
None
Define sites to associate with strategies

via the Meridium APM Framework
Optional
application.
None
Specify query preferences for the

search queries in ASM via the
Meridium APM Framework
application.
The ASM module is

configured to use the
baseline queries by
default. You need to
perform this task only
if you want to use
custom queries.
Import and export Asset Strategies via

the Meridium APM Framework
Optional
application.
Optional
None
Upgrade Workflow
You can upgrade to V3.6.0.0.0 using the instructions that are provided in this section of
the documentation. To access these instructions, click the starting version from which you
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading ASM from V3.5.1 to

V3.6.0.0.0
ASM will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you upgrade the
components in the basic Meridium APM system architecture. No additional steps are
required.
Upgrading ASM from V3.5.0 SP1 LP to

V3.6.0.0.0
The following table lists the steps that are required to upgrade and configure ASM for
V3.6.0.0.0. These steps assume that you have completed the steps for upgrading the basic
Meridium APM system architecture.
Step Task
Required/Optional
Move to the Asset Strategy family any custom rules that are
defined for the following families and configured to be executed Required
1
during the Asset Strategy activation process:
Action
Risk
Risk Assessment
Risk Rank
Action Revision
Risk Revision
Strategy Revision
Move to the Asset Strategy Template family any custom rules
that are defined for the following families and configured to be
executed when a new Asset Strategy Template is saved after
being created from an existing Asset Strategy Template or Asset
Strategy:
Action
Risk
Risk Assessment
Risk Rank
Has Risk Category
Required
Move to the Asset Strategy or Asset Strategy Template family

(as appropriate) any custom rules that are defined for any other
Required
family and are configured to be executed when an Asset Strategy
or Asset Strategy Template is deleted.

V3.6.0.0.0
The following table lists the step that is required to upgrade and configure ASM for
V3.6.0.0.0. This step assumes that you have completed the steps for upgrading the basic
Step Task
Required/Optional
defined for the following families and configured to be executed Required
1
during the activation process:
Action
Risk
Risk Assessment
Risk Rank
Action Revision
Risk Revision
Strategy Revision

V3.6.0.0.0
The following table lists the step that is required to upgrade and configure ASM for
Step Task
Required/Optional
defined for the following families and configured to be executed
during the activation process:
Action
Risk
Risk Assessment
Risk Rank
Action Revision
Risk Revision
Strategy Revision
Required
ASM Security Groups

The following table contains a list of the family-level permissions that are provided for
each of the baseline ASM Security Groups.
Family
MI ASM
Analyst
MI ASM
Administrator
MI ASM
Reviewer
MI ASM
Viewer
Action
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Action Mapping
View
None
None
Active Strategy
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Analysis Link
View
View
View
View
Asset Criticality Analysis
View
View
View
View

Has System
View
View
View
View

System
View
View
View
View
Asset Strategy
Insert, View,
Update, and View
Delete
View and
Update
View
Calibration Task
View
View
None
Checkpoint Task
Insert, View Insert, View and

and Update Update
Insert, View
and Update
Insert,
View and
Update
Consequence
View
View
View
None
None
Insert, View,
Update, and
Delete
Distribution
Insert, View,
Update, and View
Delete
View
View
Execution Mapping
View
None
None
None
Growth Model
View
View
View
View
Has Action Driver
Insert, View,
Update, and None
Delete
None
None
Has Action Mapping
View
None
None
Has Action Revisions
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Actions
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Active Strategy
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Asset Strategy
Insert, View,
Update, and View
Delete
View
View
Has Associated
Recommendation
Insert, View,
Update, and View
Delete
View
View
Has Associated Strategy
Insert, View,
Update, and View
Delete
View
View
Has Checkpoint
View
None
None
None
Insert, View,
View
View
Has Child Hierarchy Item View
None
Update, and
Delete
Has Child Work
Management Item
View
Has Driving
Recommendation
None
None
None
Insert, View,
Update, and View
Delete
View and
Delete
View
Has Execution Mapping
View
None
None
Has Functional Location
View
View
Has Global Events
Insert, View,
Update, and View
Delete
View
View
Has Health Indicators
Insert, View,
Update, and View
Delete
View
View
Insert, View,
Has Measurement Location
Update, and None
Group
Delete
None
None
Has Mitigated TTF

Distribution
Insert, View,
Update, and View
Delete
View
View
Has Mitigation Revisions
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Planned Resource

Usages
Insert, View,
Update, and View
Delete
View
View
Has Proposed Strategy
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Readings
View
View
View
None
View
Has Recommendations
Insert, View,
Update, and None
Delete
Has Reference Values
View
Insert, View,
Update, and
Delete
None
View
View
Has Resource Usages
Insert, View,
Update, and View
Delete
View
View
Has Risk
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Risk Assessments
Insert, View,
Update, and View
Delete
View
View
Has Risk Category
Insert, View, Insert, View,

Update, and Update, and
Delete
Delete
Insert, View,
Update, and
Delete
View
Has Risk Matrix
View
None
None
Has Risk Revisions
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has Root System
Insert, View,
Update, and View
Delete
View
View
Has Scenarios
Insert, View,
Update, and View
Delete
View
View
Has Site Reference
View
None
None
Has Strategy
Insert, View,
Update, and View
Delete
View
None
View
Has Strategy Revision
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Has System Actions
Insert, View,
Update, and View
Delete
View
View
Has System Elements
Insert, View,
Update, and View
Delete
View
View
Insert, View,
Has System Optimization Update, and View
Delete
View
View
Has System Resources
Insert, View,
Update, and View
Delete
View
View
Has System Results
Insert, View,
Update, and View
Delete
View
View
Has System Risks
Insert, View,
Update, and View
Delete
View
View
Has System Strategy
Insert, View,
Update, and View
Delete
View
View
Has TTF Distribution
Insert, View,
Update, and View
Delete
View
View
Has TTR Distribution
Insert, View,
Update, and View
Delete
View
View
Has Unplanned Resource

Usages
Insert, View,
Update, and View
Delete
View
View
Has Work Management

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

Item Definition
Configuration
View
None
None
Health Indicator
Insert, View,
Update, and None
Delete
View and
Update
View and
Update
Health Indicator Has

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

Source
Insert, View,
Update, and View
Delete
View
View
None
Health Indicator Mapping View
Insert, View,
Update, and
Delete
View
View
Hierarchy Item Child

Definition
View
Insert, View,
Update, and
Delete
View
View
Hierarchy Item Definition View
Insert, View,
Update, and
Delete
View
View
Implementation Package
View and
Insert
None
None
None
Implementation Role
View
View
View
View
Implements Action
Insert, View
None
and Update
None
None
Implements Strategy
View and
Insert
None
None
None
Implements Secondary
Strategy
View
None
None
None
Inspection Task
View
None
View
View
Is Based on RBI
Degradation Mechanism
None
None
View and
Delete
None
Is Based on RCM FMEA

Failure Effect
Insert, View,
Update, and None
Delete
None
None
View and
Update
View
Insert, View,
Is Basis for Asset Strategy
Update, and View
Template
Delete
Is Mitigated
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
KPI
View
View
View
View
KPI Measurement
View
View
View
View
Insert, View,
Master Template Has Asset
Update, and View
Strategy
Delete
View and
Update
View
Measurement Location
View
View
View
View
Group
Insert, View
None
and Update
None
None
Template
View
View
View
Mitigates Risk
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Operator Rounds
Allowable Values
View
View
View
View
Probability
View
Insert, View,
Update, and
Delete
View
View
View
Proposed Strategy
Insert, View,
Update, and View
Delete
View and
Update
View
Protection Level
View
View
View
View
RBI Degradation
Mechanisms
View and
Update
None
None
None
RBI Recommendation
View and
Update
None
None
None
RCM FMEA Asset
Insert, View,
Update, and View
Delete
View
View
Reading
View
View
View
View
Reliability Distribution
View
View
View
View
Reliability Growth
View
View
View
View
Risk Assessment
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
Risk Category
View
Insert, View,
Update, and
Delete
View
View
Risk Matrix
View
Insert, View,
Update, and
Delete
View
View
Risk Rank
Insert, View,
Update, and View
Delete
Insert, View,
Update, and
Delete
View
View
View
Risk Threshold
View
Safety Analysis Has

Equipment
View
Insert, View,
Update, and
Delete
View
Site Reference
View
View
View
View
System Action
Insert, View,
Update, and View
Delete
View
View
System Action Mapping
View
View
View
System Action
Optimization
Insert, View,
Update, and View
Delete
View
View
System Action Result
Insert, View,
Update, and View
Delete
View
View
System Analysis
Insert, View,
Update, and View
Delete
View
View
System Element
Insert, View,
Update, and View
Delete
View
View
System Element Result
Insert, View,
Update, and View
Delete
View
View
System Global Event
Insert, View,
Update, and View
Delete
View
View
System Resource
Insert, View,
Update, and View
Delete
View
View
System Resource Result
Insert, View,
Update, and View
Delete
View
View
View
View
System Resource Usage
Insert, View,
Update, and
Delete
Insert, View, View

Update, and
Delete
System Risk Assessment
Insert, View,
Update, and View
Delete
View
View
System Scenario
Insert, View,
Update, and View
Delete
View
View
System Sensor
Insert, View,
Update, and View
Delete
View
View
System Strategy
Insert, View,
Update, and View
Delete
View and
Update
View
Unit Strategy
Insert, View,
Update, and View
Delete
View and
Update
View
Was Applied to Asset

Strategy
Insert, View,
Update, and View
Delete
View and
Update
View
Was Promoted to ASM

Element
View
None
View
View
Work Management Item

Child Definition
View
None
None
None

Definition
View
None
None
None

Definition Configuration
View
None
None
None
Associating a Strategy with a Specific

Site
Some companies that use the Meridium APM software have facilities at multiple sites, or
locations, around the world. Each site contains unique locations and equipment.
If desired, you can define these sites and associate equipment and locations with the site
to which they belong. When you create an Asset Strategy record and link it to an
Equipment or Functional Location record, the Site Reference field will be populated
automatically with the Record ID of the Site Reference record to which the Equipment or
Functional Location record is linked. To help streamline the strategy-building process, the
Meridium APM system will allow you to add multiple Asset Strategies to System
Strategies only if all the underlying equipment and locations belong to the same site.
Likewise, you can add multiple System Strategies to a Unit Strategy only if all
underlying equipment and locations belong to the same site.
You can also associate risk matrices with specific sites. If a piece of equipment or
location is associated with a site and you build an Asset Strategy for that equipment or
location, when you define risks for the strategy, rather than seeing the default risk matrix,
you will see the risk matrix that is associated with that site.
Accessing the ASM - Administration

Page
To access the ASM - Administration page:
1. On the Meridium APM Framework main menu, click Go To, point to Asset
Strategy, and then click Asset Strategy Management.
The ASM - Start Page appears.
2. Click the Perform Administrative Tasks link.
The ASM - Administration page appears.
Aspects of the ASM - Administration

Page
The ASM - Administration page is divided into the following tabs:
Query Preferences: Provides options that you can use to specify the queries that
you want to use to search for strategies.
Import / Export: Provides options that you can use to import and export
strategies across databases.
The ASM - Administration page contains the following task menus: Search Tasks and
Common Tasks.
Note: In addition to these task menus, the Template Tasks menu also appears. All links on
this menu, however, are disabled.
Search Menu
The Search menu on the ASM - Administration page contains the following links:
Asset Strategies: Displays the ASM - Asset Strategy Search page, where you can
search for an existing Asset Strategy.
System Strategies: Displays the ASM - System Strategy Search page, where you
can search for an existing System Strategy.
Unit Strategies: Displays the ASM - Unit Strategy Search page, where you can
search for an existing Unit Strategy.
Templates: Displays the ASM - Asset Strategy Template Search page, where you
can search for an existing Asset Strategy Template.
Common Tasks Menu
The Common Tasks menu on the ASM - Administration page contains the following
links:
Create Strategy: Displays the ASM - Asset Strategy Definition page, where you
can create a new Asset Strategy record.
Import Strategy: Displays the Open dialog box, where you can select an Excel file
to use for creating a new Asset Strategy.
Delete Strategy: This link is always disabled.
Send To: Displays a submenu with options that let you provide a link to the
current page on your desktop (create shortcut), in an email message, or on a Home
Page.
Help: Displays the context-sensitive Help topic for the ASM - Administration
page.
About Specifying Search Queries

When you click the Search for Strategy link on the ASM - Start Page, one of the
following search pages appear, where you can search for existing strategies. The page
that you viewed last will be displayed by default.
Asset Strategy Search

System Strategy Search
Unit Strategy Search
Asset Strategy Template Search
Each of these pages displays the results of a query that is stored in the Meridium APM
Catalog. Note that throughout this documentation, we refer generally to these queries as
strategy search queries.
As an administrative user, if you want any of the search pages to return the results of a
different query, you will need to create the query, save it to the Meridium APM Catalog,
and then use the options on the Query Preferences tab on the ASM - Administration page
to specify the query that you want to use.
By default, the search pages are configured to return the results of the following strategy
search queries, and the Catalog path to these queries appears by default on the Query
Preferences tab on the ASM - Administration page.
...Is Used
on This
Page
This Query
...Stored in This Catalog Folder
Asset_Strategy_Search
Asset
\Public\Meridium\Modules\Asset Strategy
Strategy
Management\Management\Queries\Asset_Strategy_Search
Search
System
\\Public\Meridium\Modules\Asset Strategy
System_Strategy_Search
Strategy
Management\Management\Queries\System_Strategy_Search
Search
Unit_Strategy_Search
Management\Management\Queries\Unit_Strategy_Search
Unit
Strategy
Search
Template_Search
Management\Management\Queries\Template_Search
Asset
Strategy
Template
Search
Query Preferences Tab

The Query Preferences tab appears on the ASM - Administration page, as shown in the
following image. A red outline has been added to the image to highlight the Query
Preferences tab.
The Query Preferences tab contains the following text boxes:
Asset Strategy Search Query: Identifies the Asset Strategy Search query that will
be used to search for Asset Strategies on the Asset Strategy Search page.
System Strategy Search Query: Identifies the System Strategy Search query that
will be used to search for System Strategies on the System Strategy Search page.
Unit Strategy Search Query: Identifies the Unit Strategy Search query that will be
used to search for Unit Strategies on the Unit Strategy Search page.
Template Search Query: Identifies the Template Search query that will be
used to search for Asset Strategy Templates on the Asset Strategy Template
Search page.
If desired, you can change the selections that Meridium APM provides by default. Each
text box contains an
button, which you can click to display the Query Finder dialog
box, where you can browse to the query that you want to use for each option. You can
also type the desired query path directly in the appropriate text box.
The following buttons are available at the bottom of the Query Preferences tab:
Save: Saves any changes that you have made on the Query Preferences tab.
Exit: If you have not made changes on the Query Preferences tab, the ASM - Start
page appears. If you have made changes on the Query Preferences tab, a prompt
appears, asking if you want to save the changes. If you click the Yes button, the
changes are saved, and then the ASM - Start page appears. If you click the No
button, the changes are not saved, and then the ASM - Start page appears.
Specifying a Strategy Search Query

The following instructions assume that:
The query you want to specify has been saved to the Meridium APM Catalog.
You have View permissions to the Catalog folder that contains the desired query.
To specify a strategy search query:

1. On the ASM - Administration page, on the Query Preferences tab, click the
button in the text box associated with the strategy search query that you want to
specify. For example, if you want to specify the Asset Strategy search query, click
the
button in the Asset Strategy Search Query text box.
The Query Finder window appears. The hierarchy in the left pane represents the
Meridium APM Catalog folder structure. By default, your personal folder is
automatically selected in the hierarchy.
2. In the hierarchy on the left, navigate to and select the folder containing the query
that you want to use as the strategy search query.
The items that exist in the selected folder are displayed in the pane on the right.
3. In the pane on the right, select the query that you want to use as the strategy
search query.
4. Click OK.
The selected text box is populated with the path to the query that you selected. For
example, the following image shows the Asset Strategy Search Query text box, populated
with the path to the Asset_Strategy_Search query.
5. At the bottom of the page, click the Save button.

The selected query will now be used to return results on the corresponding strategy
search page.
About Importing and Exporting

Strategies
The ASM - Administration page provides a feature that lets you import an XML file
containing Asset Strategies that originated in one Meridium APM database to create new
Asset Strategies in another Meridium APM database. This feature also lets you export
Asset Strategies to XML files, which can then be imported into other Meridium APM
databases. Throughout this documentation, this feature is referred to as the import/export
feature.
This feature is useful for transferring Asset Strategies between databases. For example, if
you develop Asset Strategies in a test database and then want to import them into a
production database, this feature will allow you to do so. The advantage of using this
feature over other import features is that this one is configured specifically to use XML
files to create the records and links that make up Asset Strategies.
Keep in mind that when we use the term Asset Strategy, we are referring to the Asset
Strategy record and all the records that are linked to that record, with the exception of the
Equipment or Functional Location record. For more details on the records that make up
the Asset Strategy, refer to the ASM data model image.
The import/export feature is available on the Import/Export tab on the ASM Administration page. To access this page, you must be logged in as a Super User or a
member of the ASM Administrator Security Group.
About the XML File

The import/export feature utilizes XML files to:
Store Asset Strategy data that you export.

Create new Asset Strategies, using the data that you import.
Before you can import Asset Strategy data, you will need to create an XML file by
exporting the Asset Strategies using the import/export feature. When you export Asset
Strategies, the following files are created in the file location that you specify:
The <Export File Name> files folder, where <Export File Name> is the file name
that you specify before exporting the Asset Strategies. Within this folder, multiple
XML files are created, where each file represents a single Asset Strategy that you
exported. These files are named according to the Entity Key of the Asset Strategy
record.
A single XML file that represents ALL the Asset Strategies that you exported.
When you import these Asset Strategies later, this is the file that you will select to
import.
Note: The XML files are automatically encrypted. While you can open this file, you will
not be able to modify its content.
For example,if you export six Asset Strategies and name the file Asset
Strategies_Exported, the Meridium APM system will create the following files, as shown
in Figure 1:
Asset Strategies_Exported.xml file, which is the one that you would select to
import the Asset Strategies into a different database.
Asset Strategies_Exported files folder.
Six XML files (shown in Figure 2).
Figure 1
Figure 2
The Import/Export Tab

The Import / Export tab appears on the ASM - Administration page, as shown in the
following image. A red outline has been added to the image to highlight the Import /
Export tab.
The Import / Export tab on the ASM - Administration page is divided into two tabs:
Import: Contains the Select File box, where you can specify the folder path to the
XML file that you want to import. You can specify the folder path by clicking the
button and navigating to the file. To the right of the Select File box, the
following buttons appear:
Import: Starts the import process. This button is disabled until a value
appears in the Import text box.
View Log: Displays the Asset Strategy Import Log window, which
displays the results of the last import process. The View Log button is
enabled only after an import operation has been executed.
The following image shows the Import tab on the Import / Export tab. A red outline has
been added to the image to highlight the Import tab.
Export: Displays the results of a query that exists in the code, which returns the
list of Asset Strategies in the current database. You can use these results to select
the Asset Strategies that you want to export. If you want to see different results,
you can specify a different export query. Above the results, the following items
appear:
Locate Query box: Lets you specify the Catalog path to the export query
whose results you want to view in the results grid at the bottom of the
page. You can specify the Catalog path by clicking the
navigating to the file.
button and
Run Query button: Runs the export query that is specified in the Locate
Query box or the default query (if a query has not been specified in the
Locate Query text box), and then displays the results at the bottom of the
page.
Save File box: Lets you specify the XML file to which you want to save
the exported strategies. You can specify the XML file by clicking the
button and navigating to the file.
Export button: Starts the export process. The Export button is disabled
until a value appears in the Save File box.
View Log button: Displays the Asset Strategy Export Log window, which
displays the results of the last export process. The View Log button is
enabled only after an export operation has been executed.
The following image shows the Export tab on the Import / Export tab. A red outline has
been added to the image to highlight the Export tab.
Performing the Export Procedure

To export Asset Strategies:
1. On the ASM - Administration page, click the Import/Export tab.
The Import/Export tab appears.
2. On the Import/Export tab, click the Export tab.

The Export tab appears.
The Export tab displays the results the query that exists in the code. If you want to view
different results, you can specify a different query. These instructions assume that you are
viewing the desired results.
3. To the right of the Save File box, click the
The Save As window appears.
button.
4. Navigate to the location where you want to save the exported files, and in the File
Name text box, type a name for the XML file.
5. Click the Save button.
The Save As window closes, and the file path that you specified appears in the Save File
box.
6. In the query results, select the rows containing the Asset Strategies that you want
to export.
Hint: You can select multiple rows by pressing and holding the Ctrl key.
7. Click the Export button.
The export process begins, and the Performing Asset Strategy Export dialog box appears,
displaying the progress of the export process.
When the export is finished, the Asset Strategy Export Log window appears, displaying
the results of the export procedure.
At this point, you can review the results of the export process. If desired, you can save the
results by clicking the Save Log button and navigating to the location where you want to
save the file.
8. When you are finished reviewing the results of the export procedure, click OK.
The Composite Entity Export Log window closes, revealing the Export tab.
Specifying a Different Export Query
If desired, you can change the query whose results are displayed on the Export tab. The
following instructions assume that you have saved the desired query to the Catalog and
that the query is configured to return records in the Asset Strategy family.
To specify a different export query:
1. On the Export tab, in the Locate Query box, click the
button.
The Open Catalog Item window appears.
2. Navigate to the desired query, and then click the Open button.
The Meridium APM system checks the query to see if it is configured to return records in
the Asset Strategy family:
If the query is not configured to return records in the Asset Strategy

family, a message appears, indicating that the query is invalid. You will
need to select a query that is configured accordingly or use the default
query.
If the query is configured to return records in the Asset Strategy family,
the Catalog path to the specified query appears in the Locate Query box.
For example, the following image shows the Locate Query box, populated
with the Catalog path to the Asset_Strategy_Search query.
3. Click the Run Query button.

The results of the specified query appear in the grid. For example, the following image
shows the results of the Asset_Strategy_Search query. Note that in this example, the
query contains a prompt.
About Importing Asset Strategies From

Different Databases
Unlike the Import Strategy option that is available from the ASM - Start page and lets
you create Asset Strategies by importing data from a Microsoft Excel spreadsheet or from
SAP, you can use the import/export feature on the ASM - Administration page to import
Asset Strategies that originated in a different Meridium APM database and are stored in
an XML file.
When you import Asset Strategies from an XML file, the Meridium APM system uses the
values that make up the Asset Strategy in the source database to create NEW records that
make up the Asset Strategy in the target database. The new Asset Strategy will be an
exact copy of the Asset Strategy as it exists in the source database.
Additionally, the import procedure does not update existing Asset Strategies and related
records in the target database. It creates a copy of the imported Asset Strategy in the
target database. In other words, if you import an Asset Strategy that already exists in the
target database, your database will contain two of the same Asset Strategies. For this
reason, we recommend that you not import an Asset Strategy that already exists in the
target database.
This feature assumes that the Site Reference and Risk Matrix records that are associated
with the Asset Strategies from the source database also exist in the target database with
the same Name and configuration. If these records do not exist in the target database, that
Asset Strategy will not be imported, and the import log will contain these details.
Note the following information about imported Asset Strategies:
While the state of the source Asset Strategy is retained, the value in the Date State
Entered field will be set to the date on which the Asset Strategy is imported. In
other words, it will match the date on which the state was changed in the target
database, not the date on which the state was changed in the source database.
The link between the Asset Strategy record and the Equipment or Functional
Location record is not created in the target database. After you import an Asset
Strategy, you will need to link the Asset Strategy record to the desired Equipment
or Functional Location record in the target database. You can do so manually
using ASM, or you can use an update query based on the Asset Name specified in
the Asset Strategy record.
What Happens If the Imported Strategy

Already Exists in the Target Database?
The import procedure only creates new Asset Strategies. It does not update existing ones.
Therefore, if you import an Asset Strategy that already exists in the target database, the
existing Asset Strategy will not be overwritten or updated with information from the
Asset Strategy that you imported. Instead, a NEW Asset Strategy will be created. In other
words, you would see more than one Asset Strategy with the same name. To prevent
duplicate Asset Strategies from appearing in the database, we recommend that you import
only the Asset Strategies that do not already exist in the target database.
If duplicate Asset Strategies do appear in your database after you import them, you can
determine which Asset Strategy existed previously and which one was imported by
comparing the values in the Date State Entered column on the ASM - Asset Strategy
Search page. For the imported Asset Strategy, t value in this column will match the date
on which the Asset Strategy was imported.
Performing the Import Procedure

To import an Asset Strategy that was created in a different database:
1. On the ASM - Administration page, click the Import/Export tab.
The Import/Export tab appears, and the Import tab is displayed by default.
2. On the Import tab, to the right of the Select File box, click the
button.
The Open window appears.
3. Navigate to the XML file containing the Asset Strategies that you want to import,
and then click the Open button.
The Open window closes, and the file path to the file that you selected appears in the
Select File box.
4. Click the Import button.

The Performing Asset Strategy Import dialog box appears, displaying the progress of the
import process.
When the import process is finished, the Asset Strategy Import Log window appears,
displaying the results of the import procedure.
At this point, you can review the results of the import procedure. If desired, you can save
the results by clicking the Save Log button and navigating to the location where you want
to save the file.
5. When you are finished reviewing the results of the import procedure, click OK.
The Composite Entity Export Log window closes, revealing the Import tab.
About the Asset Strategy

<Import/Export> Log Window
The Asset Strategy <Import/Export> Log window displays the results of the most recent
import or export procedure that was executed, where <Import/Export> corresponds to
either the import or export procedure, respectively. The following image shows the Asset
Strategy Export Log window.
After you complete an import or export procedure, this window appears automatically.
Additionally, you can access this window using the View Log button on either the Import
or Export tabs that appear on the Import/Export tab.
You can use this window to view the results of the import or export procedure that was
last executed. This window does not store results for other past import or export
procedures. You can, however, save the results of an import or export procedure via the
Save Log button on the Asset Strategy <Import/Export> Log window.
The Asset Strategy <Import/Export> window contains a grid, where each row displays
the following information for a single Asset Strategy that was imported or exported:
Entry Date: The date and time on which the import or export process was
executed.
Entity ID: The Entity ID of the Asset Strategy that you imported or exported.
Result: A textual indication of whether the import or export was successful or if

errors occurred during the process. If the process was successful, this cell contains
the value Successful. If errors occurred during the process, this cell contains the
value Error, and a corresponding message appears in the Message cell in that row.
Message: An error message that indicates why the import o export process failed.
Below the grid, the following buttons appear:
Save Log: Displays the Save As window, where you can specify the location
where you want to save the log results. When you save log results, it is saved as a
TXT file.
OK: Closes the Asset Strategy <Import/Export> Log window.
Saving the Import/Export Log Results

The following instructions provide details on saving the results of an import or export
procedure. When you save the log results, you are saving the information that is
displayed in the grid on the Asset Strategy <Import/Export> Log window to a TXT file.
For example, the following image shows the Asset Strategy Export Log window, after an
export procedure was completed successfully.
If you were to save these results, the TXT file that is created would look like the
following image.
To save the import/export log:

1. On the Asset Strategy <Import/Export> Log window, below the grid, click the
Save Log button.
The Save As window appears.
2. Navigate to the location where you want to save the log file, and in the File name
text box, type a name for the file.
The file is saved to the specified location.
About the Page Labels

Throughout ASM, except for the ASM - Administration page, all page labels contain the
following components, separated by a dash:
The text ASM.

A brief description of the page you are currently viewing, such as Asset Strategy
Definition.
The ID of the strategy that you are viewing (stored in the Strategy ID field).
For example, consider the following image, where the page label has been outlined in
red.
From this image, you can see from the page label that the Strategy ID is PMP-8131.
Throughout this documentation, in most cases, when we refer to pages, the text ASM and
the Strategy ID component are omitted from the labels to make the documentation easier
to read. So, instead of this:
ASM - Asset Strategy Definition - <Strategy ID> page
...you will see this:
Asset Strategy Definition page
In cases where omitting the text ASM or <Strategy ID> from the page label could cause
confusion in the documentation (e.g., ASM - Start Page), it is included.
Interpreting the Site Map

The Site Map in ASM functions differently than the Site Map in other modules. In other
modules, the Site Map allows you navigate from the current page to a previously
accessed page within the same module. In ASM, the Site Map allows you to navigate
between strategies. You can click any link in the Site Map to access the associated
strategy.
Site Map Displayed for Asset Strategies

If you are viewing an Asset Strategy, the Site Map that appears on all pages contains the
following text:
Asset Strategy Management -> Unit Strategy ID -> System Strategy ID -> Asset Strategy
ID
...where:
Unit Strategy ID is the ID of the Unit Strategy that contains the Asset Strategy.
System Strategy ID is the ID of the System Strategy that contains the Asset
Strategy.
Asset Strategy ID is the ID of the Asset Strategy.
If the Asset Strategy is not linked to a System Strategy, in place of the text System
Strategy ID, you will see the text No System Defined. In addition, if the Asset Strategy is
included in a System Strategy that is not included in a Unit Strategy, in place of the text
Unit Strategy ID, you will see the text No Unit Assigned.
Site Map Displayed for System Strategies

If you are viewing a System Strategy, the Site Map that appears on all pages contains the
following text:
Asset Strategy Management -> Unit Strategy ID -> System Strategy ID
...where:
Unit Strategy ID is the ID of the Unit Strategy that contains the System Strategy.
System Strategy ID is the ID of the System Strategy.
If the System Strategy is not included in a Unit Strategy, in place of the text Unit Strategy
ID, you will see the text No Unit Assigned.
Site Map Displayed for Unit Strategies

If you are viewing a Unit Strategy, the Site Map that appears on all pages contains the
following text:
Asset Strategy Management -> Unit Strategy ID
Where Unit Strategy ID is the ID of the Unit Strategy.
Example
Consider the following Site Map:
From this Site Map, you can see that:
Asset Strategy PMP-4543 is currently displayed.

Asset Strategy PMP-4543 is included in System Strategy FCC-OVH.
System Strategy FCC-OVH is included in Unit Strategy FCC.
Aspects of the Asset Strategy Search

Page
The Asset Strategy Search page is divided into the following areas:
Asset Strategy Search workspace: The area that allows you to search for an Asset
Strategy.
Task menus: Menus that provide specific functionality. The following task menus
are available: Search and Common Tasks.
Asset Strategy Search Workspace

The Asset Strategy Search workspace lets you run the Asset Strategy Search query to
view a list of existing Asset Strategy records that meet your query criteria.
The baseline Asset Strategy Search query, Asset_Strategy_Search, is stored in the
Meridium APM Catalog in the following folder: \\Public\Meridium\Modules\Asset
Strategy Management\Management\Queries. If you want the Asset Strategy Search
workspace to return results of a different query, an administrative user will need to create
the query and configure the Asset Strategy Search page to use it.
The baseline Asset_Strategy_Search query contains two prompts: Asset Type and State.
These prompts appear at the top of the page as drop-down lists that contain various
options.
The Asset Type list contains the following options:
All: Causes the query to return all Asset Strategy records. This is the
default selection.
<Family Caption>, where <Family Caption> is the caption of any family
that is related to the Asset Strategy family through the Has Strategy
relationship. The option that you select will cause the query to return all
Asset Strategy records that are linked to a record in the family with the
selected family caption.
The State list contains the following options:
All: Causes the query to return all Asset Strategy records regardless of
their state. This is the default selection.
<State Name>, where <State Name> is the name of any state that has been
configured in the State Configuration for the Asset Strategy family. The
option that you select will cause the query to return all Asset Strategy
records with the selected state.
Each time you access the Asset Strategy Search workspace, the values that appear by
default in the prompts will be used to filter the list. After you select different criteria, you
can click the Run Query button to run the Asset Strategy Search query and display the
results in a grid at the bottom of the page. The default Asset Strategy Search query is
configured to display the following columns of information:
Strategy ID
Description
Strategy Activation Date
Strategy Evaluation Date
Strategy Notes
Asset Name
Asset Type
State
Hint: If desired, you can customize the column display or filter the results. Note,
however, that you cannot apply a filter to a date column.
You can click any hyperlinked strategy ID to view the Asset Strategy Overview page.
Accessing the Asset Strategy Template

Search Page
To access the Asset Strategy Template Search page:
On the ASM - Start Page, click the Manage Templates link.
The Asset Strategy Template Search page appears.
Aspects of the Asset Strategy Template

Search Page
The Asset Strategy Template Search page is divided into the following areas:
Asset Strategy Template Search workspace: The area that allows you to search for
an Asset Strategy Template.

Workspace
The Asset Strategy Template Search workspace lets you run the Asset Strategy Template
Search query to view a list of existing Asset Strategy Template records that meet your
query criteria.
The baseline Asset Strategy Template Search query, Template_Search, is stored in the
Strategy Management\Management\Queries.
The baseline Template_Search query contains one prompt: State. The prompt appears at
the top of the page as a drop-down list that contains the following options.
All: Causes the query to return all Asset Strategy Template records, regardless of
their state. This is the default selection.
[State Name], where [State Name] is the name of any state that has been
configured in the State Configuration for the Asset Strategy Template family. The
option that you select will cause the query to return all Asset Strategy Template
records with the selected state.
Each time you access the Asset Strategy Template Search workspace, the value that
appears by default in the prompt will be used to filter the list. After you select different
criteria, you can click the Run Query button to run the Asset Strategy Template Search
query and display the results in a grid at the bottom of the page. The default Asset
Strategy Template Search query is configured to display the following columns of
information:
Template ID
Description
Template Activation Date
Template Evaluation Date
Template Notes
Asset Name
Asset Family
State
Date State Entered
State Owner
User ID
Last Updated
Hint: If desired, you can customize the column display.
You can click any hyperlinked template ID to view the Asset Strategy Template
Overview page.
Aspects of the System Strategy Search

Page
The System Strategy Search page is divided into the following areas:
System Strategy Search workspace: The area that allows you to search for a
System Strategy.
System Strategy Search Workspace

The System Strategy Search workspace lets you run the System Strategy Search query to
view a list of all existing System Strategy records that meet your query criteria.
The baseline System Strategy Search query, System_Strategy_Search, is stored in the
Strategy Management\Management\Queries. If you want the System Strategy Search
workspace to display results of a different query, an administrative user will need to
create the query and configure the System Strategy Search page to use it.
The default System Strategy Search query is configured to display the following columns
of information: ID and Description.
You can click any hyperlinked strategy ID to view the System Strategy Overview page.
Aspects of the Unit Strategy Search

Page
The Unit Strategy Search page is divided into the following areas:
Unit Strategy Search workspace: The area that allows you to search for a Unit
Strategy.
Unit Strategy Search Workspace

The Unit Strategy Search workspace lets you run the Unit Strategy Search query to view
a list of all existing Unit Strategy records that meet your query criteria.
The baseline Unit Strategy Search query, Unit_Strategy_Search, is stored in the
Strategy Management\Management\Queries. If you want the Unit Strategy Search
workspace to display results of a different query, an administrative user will need to
create the query and configure the Unit Strategy Search page to use it.
The default Unit Strategy Search query is configured to display the following columns of
information: ID and Description.
You can click any hyperlinked strategy ID to view the Unit Strategy Overview page.
Accessing the Asset Strategy Overview

To access the Asset Strategy overview:
Search for and open the Asset Strategy whose overview you want to view.
The Asset Strategy Overview page appears.
About the Asset Strategy Overview

The Asset Strategy overview contains the following items:
The Risk Profile graph.

The Financial Risk Exposure graph.
The Cost of Actions graph.
The Cost Projection graph.
A grid containing a list of the Actions that belong to the Active Strategy.
The Asset Strategy overview is displayed on the Asset Strategy Overview page.

Overview
To access the Asset Strategy Template overview:
Search for and open the Asset Strategy Template whose overview you want to
view.
The Asset Strategy Template Overview page appears.

-OR
If you are currently working with the Asset Strategy Template whose overview
you want to view, on the Navigation menu, click the Overview link.
About the Asset Strategy Template

Overview
The Asset Strategy Template overview contains the following items:

A grid containing a list of the Actions that belong to the Asset Strategy Template
record.
Note: The hyperlinks in the preceding list display topics that describe these items in terms
of an Asset Strategy. The information provided for these items applies also to Asset
Strategy Templates.
The Asset Strategy Template overview is displayed on the Asset Strategy Template
Overview page.
Accessing the System Strategy Overview

To access the overview of a System Strategy:
Search for and open the System Strategy whose overview you want to view.
The System Strategy Overview page appears.
About the System Strategy Overview

The System Strategy overview contains the following items:

A grid containing a list of the non-Draft Asset Strategies that are included in the
System Strategy.
The System Strategy overview is displayed on the System Strategy Overview page.
Accessing the Unit Strategy Overview

To access the overview of a Unit Strategy:
Search for and open the Unit Strategy whose overview you want to view.
The Unit Strategy Overview page appears.
About the Unit Strategy Overview

The Unit Strategy overview contains the following items:

A grid containing a list of the Active System Strategies that are included in the
Unit Strategy.
The Unit Strategy overview is displayed on the Unit Strategy Overview page.
Accessing the Asset Strategy Definition

Page
These instructions explain how to access the Asset Strategy Definition page from the
ASM - Start Page. You can also access this page from any other page in ASM by clicking
the Strategy Definition link on the Navigation menu while you are viewing an Asset
Strategy.
To access the Asset Strategy Definition page from the start page:
1. On the ASM - Start Page, click the Create Strategy link.
The Strategy Type dialog box appears.

2. If it is not already selected, click Asset Strategy, and then click OK.
The Asset Strategy Definition page appears.
Aspects of the Asset Strategy Definition

Page
The Asset Strategy Definition page is divided into the following areas:
Asset Strategy Definition workspace: The area that allows you to define
properties for an Asset Strategy.
are available: Search, Navigation, Tools, Common Tasks, Template Tasks, and
Associated Pages.
Asset Strategy Definition Workspace

The Asset Strategy Definition workspace displays the Asset Strategy datasheet, where
you can specify properties of the Asset Strategy.
The Asset Strategy datasheet is divided into the following sections, which appear as tabs:
Main
Asset
The Main tab displays the following fields:
Strategy ID: The ID of the Asset Strategy.
Description: A description of the Asset Strategy.
Strategy Owner: The user who created Asset Strategy record. The value in this
field is set by default to the name of the Security User who created the Asset
Strategy record. The value can be modified if desired. If you want to select
another owner, you can select a Security User from the list. The list is populated
with all active Security Users that belong to the MI ASM Analyst Security Group.
Note: You can delete an Asset Strategy only if you are the Security User in the Strategy
Owner field.
Strategy Activation Date: The date that the Asset Strategy state was set to Active
for the first time. This field is disabled, and the field is populated automatically
after the Asset Strategy state changes to Active for the first time.
Strategy Activated By: The user ID of the Security User who first set the Asset
Strategy state to Active.
Strategy Re-Evaluation Date: The date on which you want to reevaluate the Asset
Strategy.
Plan Length: The number of years for which you want to calculate costs. This
value will be used to determine the number of datapoints (bars) on the Cost
Projection graph.
Risk Analysis Type: A value that indicates whether the strategy results (shown in
the graphs) are based on an ASO Analysis or not. The field will contain one of the
following values:
o
o
Simulation: The strategy results are based on an ASO Analysis.

Qualitative: The strategy results are not based on an ASO Analysis. If the
strategy has never been used to create an ASO Analysis, the Risk Analysis
Type field contains the value Qualitative and is disabled.
Note the following about the Risk Analysis Type field:
If the Asset Strategy has never been used to create an ASO Analysis and is
not included in an ASO Analysis, the value will be set to Qualitative, and
the field will be disabled. The value will be changed automatically to
Simulation if you create an ASO Analysis from the Asset Strategy or
include the Asset Strategy in an ASO Analysis by creating an analysis
from a System Strategy or Unit Strategy that includes the Asset Strategy.
If the Asset Strategy was used to create an ASO Analysis, the value will be
set to Simulation, and the field will be enabled. If desired, you can change
the value to Qualitative to update the strategy results so that they are no
longer based on the ASO Analysis. If you change the value to Qualitative,
the ASO Analysis will not be deleted or unlinked from the Asset Strategy.
If the Asset Strategy is included in an ASO Analysis but was not used to
create the analysis, the value will be set to Simulation, and the field will be
disabled. The value will be changed automatically to Qualitative only if
the Risk Analysis Type in the System Strategy or Unit Strategy that
includes the Asset Strategy is set to Qualitative.
Strategy Notes: Any additional information you want to provide about the Asset
Strategy.
The Asset tab displays the following fields:
Asset Name: The Equipment Technical Number of the Equipment record or the
Functional Location ID of the Functional Location record to which the Asset
Strategy record is linked. This text box contains a
button, which you can
click to search for the Equipment or Functional Location record that you want to
link to the Asset Strategy record. This button is enabled only if the Asset Strategy
is in the Draft or Modified state.
Asset Type: The Taxonomy Type Description of the selected Equipment or
Functional Location record. This field is populated automatically after you use the
button in the Asset Name text box to select an Equipment or Functional
Location record.
Site Reference: The Record ID of the Site Reference record that is linked to the
selected Equipment or Functional Location record. This field is populated
automatically after you use the
button in the Asset Name text box to select an
Equipment or Functional Location record. It is disabled after you save the Asset
Strategy record.
Next to the disabled Datasheet list, the datasheet toolbar appears. On the toolbar, the
following options are enabled:
: Saves the current Asset Strategy record.

: Displays the Reference Documents window, where you can manage the
Reference Document records that are linked to the current Asset Strategy record.
: Displays the State Assignments dialog box, where you can manage the
Security Users that are assigned to the states that are defined for the Asset
Strategy family.
About Accessing the Asset Strategy

Template Definition Page
You can access the Asset Strategy Template Definition page when using any of the
following workflows:
When you are creating a new Asset Strategy Template either from scratch.
When you are creating a new Asset Strategy Template from an existing Asset
Strategy.
When you are creating a new Asset Strategy Template from an existing Asset
Strategy Template.
When you are opening the datasheet for an existing Asset Strategy Template.
The following image shows the Asset Strategy Template Definition page as it appears
when you view the datasheet for an existing Asset Strategy Template.
Aspects of the Asset Strategy Template

Definition Page
The Asset Strategy Template Definition page is divided into the following areas:
Asset Strategy Template Definition workspace: The area that allows you to define
properties of the Asset Strategy Template.
are available: Search, Navigation, Common Tasks, and Associated Pages.
The Asset Strategy Template Definition

Workspace
The Asset Strategy Template Definition workspace displays the Asset Strategy Template
datasheet, where you can specify properties of the Asset Strategy Template.
The Asset Strategy Template datasheet contains the following fields:
Template ID: The ID of the Asset Strategy Template.

Description: A description of the Asset Strategy Template.
Template Owner: The user who created the Asset Strategy Template record. The
value in this field is set by default to the name of the Security User who created
the Asset Strategy Template record. The value can be modified if desired. If you
want to select another owner, you can select a Security User from the list. The list
is populated with all active Security Users that belong to the MI ASM Analyst
Security Group.
Note: You can delete an Asset Strategy Template only if you are the Security User in the
Strategy Owner field.
Template Activation Date: The date that the Asset Strategy Template state was set
to Active for the first time. This field is disabled, and the field is populated
automatically after the Asset Strategy Template state changes to Active for the
first time.
Template Evaluation Date: The date on which you want to reevaluate the Asset
Strategy Template.
Risk Matrix: A list that contains the Record IDs of the Risk Matrix records that
exist in the database. This field is disabled after the Asset Strategy Template
record is saved.
Template Notes: Any additional information you want to provide about the Asset
Strategy Template.
To the right of the disabled Datasheet list, the datasheet toolbar appears. On the toolbar,
the following options are enabled:
: Saves the current Asset Strategy Template record.

: Displays the State Assignments dialog box, where you can manage the
Security Users that are assigned to the states that are defined for the Asset
Strategy Template family.
Accessing the System Strategy

Definition Page
These instructions explain how to access the System Strategy Definition page from the
ASM - Start Page. You can also access this page from any other page in ASM by clicking
the System Definition link on the Navigation menu while you are viewing a System
Strategy.
To access the System Strategy Definition page from the start page:
2. If it is not already selected, click System Strategy, and click OK.
The System Strategy Definition page appears.
Aspects of the System Strategy

Definition Page
The System Strategy Definition page is divided into the following areas:
System Strategy Definition workspace: The area that allows you to define
properties for a System Strategy.
are available: Search, Navigation, Tools, Common Tasks, and Associated Pages.
System Strategy Definition Workspace

The System Strategy Definition workspace displays the System Strategy datasheet, where
you can specify properties of the System Strategy. The System Strategy datasheet
contains the following fields:
System ID: The ID of the System Strategy.

Strategy Owner: The name of the Security User who created the System Strategy
record. The value in this field is set by default to the name of the Security User
who created the Asset Strategy record. The value can be modified if desired. Note
that you can delete a System Strategy only if you are the Security User in the
following values:
Qualitative: The strategy results are not based on an ASO Analysis.
If the System Strategy has never been used to create an ASO Analysis and
is not included in an ASO Analysis, the value will be set to Qualitative,
and the field will be disabled. The value will be changed automatically to
Simulation if you create an ASO Analysis from the System Strategy or
include the System Strategy in an ASO Analysis by creating an analysis
from a Unit Strategy that includes the System Strategy.
If the System Strategy was used to create an ASO Analysis, the value will
be set to Simulation, and the field will be enabled. If desired, you can
change the value to Qualitative to update the strategy results so that they
are no longer based on the ASO Analysis. If you change the value to
Qualitative, the ASO Analysis will not be deleted or unlinked from the
System Strategy.
If the System Strategy is included in an ASO Analysis but was not used to
create the analysis, the value will be set to Simulation, and the field will be
disabled. The value will be changed automatically to Qualitative only if
the Risk Analysis Type in the Unit Strategy that includes the System
Strategy is set to Qualitative.
Site Reference: The Record ID of the Site Reference record to which all
underlying Equipment or Functional Location records are linked. You can select a
value from the list, which displays the Record ID of all Site Reference records in
the database. If you do so, you will be able to link this System Strategy record
only to Asset Strategy records that are linked to Equipment or Functional
Location records that are linked to the same Site Reference record.
If you do not select a value in the list, when you link an Asset Strategy record to the
System Strategy record, this field will be populated automatically with the name of the
Site Reference record that is linked to the underlying Equipment or Functional Location
record. If the underlying Equipment or Functional Location record is not linked to a Site
Reference record, the Meridium APM system will continue this process with every
additional Asset Strategy record that you link to the System Strategy record.
After a Site Reference record is located and the field is populated automatically, it is also
disabled. From that point on, you will be able to link this System Strategy record only to
Asset Strategy records that are linked to Equipment or Functional Location records that
are linked to the same Site Reference record.
Description: A description of the System Strategy.
following option is enabled:
: Saves the current System Strategy record.

Reference Document records that are linked to the current System Strategy
record.
Accessing the Unit Strategy Definition

Page
These instructions explain how to access the Unit Strategy Definition page from the ASM
- Start Page. You can also access this page from any other page in ASM by clicking the
Unit Definition link on the Navigation menu while you are viewing a Unit Strategy.
To access the Unit Strategy Definition page from the start page:
2. If it is not already selected, click Unit Strategy, and click OK.
The Unit Strategy Definition page appears.
Aspects of the Unit Strategy Definition

Page
The Unit Strategy Definition page is divided into the following areas:
Unit Strategy Definition workspace: The area that allows you to define properties
for a Unit Strategy.
are available: Search, Navigation, Tools, Common Tasks, and Associated Pages.
Unit Strategy Definition Workspace
The Unit Strategy Definition workspace displays the Unit Strategy datasheet, where you
can specify properties of the Unit Strategy. The Unit Strategy datasheet contains the
following fields:
Unit ID: The ID of the Unit Strategy.

Strategy Owner: The name of the Security User who created the Unit Strategy
record. The value in this field is set by default to the name of the Security User
who created the Asset Strategy record. The value can be modified if desired. Note
that you can delete a Unit Strategy only if you are the Security User in the
following values:
Qualitative: The strategy results are not based on an ASO Analysis.
If the Unit Strategy has never been used to create an ASO Analysis, the
value will be set to Qualitative, and the field will be disabled. The value
will be changed automatically to Simulation if you create an ASO
Analysis from the Unit Strategy.
If the Unit Strategy was used to create an ASO Analysis, the value will be
set to Simulation, and the field will be enabled. If desired, you can change
the value to Qualitative to update the strategy results so that they are no
longer based on the ASO Analysis. If you change the value to Qualitative,
the ASO Analysis will not be deleted or unlinked from the Unit Strategy.
Site Reference: The Record ID of the Site Reference record to which all
underlying Equipment or Functional Location records are linked. You can select a
value from the list, which displays the Record ID of all Site Reference records in
the database. If you do so, you will be able to link this Asset Strategy record only
to System Strategy records whose underlying Equipment or Functional Location
records are linked to the same Site Reference record.
If you do not select a value in the list, when you link a System Strategy record to the Unit
Strategy record, this field will be populated automatically with the name of the Site
Reference record that is linked to the underlying Equipment or Functional Location
record. If the underlying Equipment or Functional Location record is not linked to a Site
Reference record, the Meridium APM system will continue this process with every
additional System Strategy record that you link to the Unit Strategy record.
After a Site Reference record is located and the field is populated automatically, it is also
disabled. From that point on, you will be able to link this Unit Strategy record only to
System Strategy records whose underlying Equipment or Functional Location records are
linked to the same Site Reference record.
Description: A description of the Unit Strategy.
following option is enabled:
: Saves the current Unit Strategy record.

Reference Document records that are linked to the current Unit Strategy record.
Accessing the Asset Strategy Actions

Page
To access the Asset Strategy Actions page:
1. Search for and open an Asset Strategy.
2. On the Navigation menu, click the Actions link.
The Asset Strategy Actions page appears.
A list of Actions that are included in the Asset Strategy is displayed in the Proposed
Strategy section.
Overview of the Asset Strategy Actions

Page
The Asset Strategy Actions page is divided into the following items:
Proposed Strategy section: Contains a grid, which displays a list of Actions that
are included in the Asset Strategy.
Mitigated Risks tab: Contains a grid, which displays a list of Risks that are
associated with the Action that is selected in the Proposed Strategy section.
Health Indicators tab: Contains a grid, which displays a list of Health Indicator
records that are linked to the Action record represented by the Action that is
selected in the Proposed Strategy section.
Proposed Strategy Section

The Proposed Strategy section contains a grid, which displays a list of Actions that are
included in the Asset Strategy. Each row in the grid represents one Action.
By default, the grid contains the following columns:
Flag: An icon indicating the status of the Action.
If the Asset Strategy state is anything other than Active or Draft and the
Action has not been modified since it was created, the Flag column will
contain the icon.
Action has been modified, the Flag column will contain the icon.
Action has been removed from the Asset Strategy (and therefore the
Action record has been unlinked from the Asset Strategy record), the Flag
column will contain the icon.
Name: The name of the action. This column contains a hyperlink that you can
click to access the Action datasheet, where you can modify the Action.
Description: A description of the action.
Action Type: The type of action.
Interval: The interval by which the action should be completed.
Interval Units: The units associated with the interval.
Cost: The cost of performing the action.
Nonrecurring: A check box indicating whether or not the action should be

repeated on a recurring basis.
Number of Recommendations: The number of source Recommendations that were

promoted to create this Action. This column contains a hyperlink that you can
click to access the Manage Recommendations to Action Links page for the current
Asset Strategy.
Below the grid, the following buttons are available:
Add Action: Displays the New Action window, where you can create a new
Action. This button is always enabled.
Copy Action: Creates a copy of the selected Action, where the Record ID of the
new Action record is Copy of <Action Name> n, where <Action Name> is the
value in the Name field in the source Action record and n is a numeric value
indicating the order in which the copy was created, relative to other copies of the
same source Action record. The new Action will contain the same values as the
source Action, with the exception of the following fields:
Action ID
Global ID
Max Unmitigated Risk
ROI
Relevance
Status
This button is disabled if you are logged in as a member of the ASM Viewer Security
Group. You can copy only one Action record at a time. If you select multiple Actions, the
Copy Action button will be disabled.
Remove Action: Causes Meridium APM to delete the Action the next time the
Asset Strategy state is set to Active. This button is enabled only if the Asset
Strategy state is Active. You can select multiple Actions to remove them at one
time.
Undo Action: Reverses the last action that you performed on the Action. For
example, if you created the Action, the Undo Action button will remove the
Action from the grid. If you last clicked the Remove Action button, the Undo
Action button will undo this step, causing the Action to appear in the grid without
the icon. You can select multiple Actions to reverse the last action that you
performed on them. This button is enabled only if the Asset Strategy state is Draft
or Modified.
Note that if you want to collapse the Proposed Strategy section, you can click the
button in the Proposed Strategy section header. To expand the section again, you can
click the
button.
Mitigated Risks Section

The Mitigated Risks tab contains a grid, which displays a list of Risk that are associated
with the Action that is selected in the Proposed Strategy section. Each row in the grid
represents one Risk.
Flag: An icon indicating the status of the Risk Assessment record that is linked to
the Risk record.
If the Asset Strategy state is Modified or Pending Review and the Risk
Assessment record has not been modified since it was created, the Flag
Assessment record has been modified, the Flag column will not contain an
icon.
Assessment record has been removed from the Asset Strategy (and
therefore unlinked from the Asset Strategy record), the Flag column will
contain the icon.
Name: The name of the risk.
Description: A description of the risk.
Unmitigated Risk Rank: The calculated risk rank in the Risk record.
Action Mitigated Risk Rank: The calculated risk rank in the Risk Assessment
record that is linked to the Risk record. This column contains a hyperlink that you
can click to access the risk matrix, where you can modify the mitigated risk value
on any tab.
Strategy Mitigated Risk Rank: The sum of the smallest risk rank values across
ALL risk categories (represented by tabs on the risk matrix) defined for ALL
actions that mitigate the risk.
Assign New Risk: Displays the Create Risk Wizard, where you can create a new
Risk that is associated with the Action. This button is disabled if you are logged in
as a member of the ASM Viewer Security Group.
Assign Existing Risks: Displays the Assign Risks window, where you can select
existing Risks to associate with the Action. This button is disabled if you are
logged in as a member of the ASM Viewer Security Group.
Health Indicators Tab

The Health Indicators tab contains a grid, which displays a list of Health Indicator
records that are linked to the Action record that is selected in the Proposed Strategy
section. Each row in the grid represents one Health Indicator record.
Name: The hyperlinked name of the Health Indicator record. You can click the
hyperlink to display the details of the source record (if the Health Indicator is
linked to a source record) or the Health Indicator datasheet (if the Health Indicator
record is not linked to a source record).
Description: A description of the Health Indicator.
Add Indicator: Displays the Create New Health Indicator dialog box, where you
can create a new Health Indicator record to link to the selected Action record.
Delete Indicator: After asking for confirmation, deletes the selected Health
Indicator record.

Actions Page
To access the Asset Strategy Template Actions page:
1. Search for and open the desired Asset Strategy Template.
The Asset Strategy Template Actions page appears.
A list of the Actions that belong to the Asset Strategy Template is displayed in the
Proposed Strategy section.
Overview of the Asset Strategy Template

Actions Page
The Asset Strategy Template Actions page is divided into the following items:
Proposed Strategy section: Contains a grid, which displays a list of Actions that
belong to the Asset Strategy Template.
Mitigated Risks tab: Contains a gird, which displays a list of Risks that are
associated with the Action that is selected in the Proposed Strategy section.
Health Indicators tab: Contains a grid, which displays a list of Health Indicator
records that are linked to the Action record that is selected in the Proposed
Strategy section.
Proposed Strategy Section

The Proposed Strategy section contains a grid, which displays a list of Actions that are
linked to the Asset Strategy Template record. Each row in the grid represents one Action.
If the Asset Strategy Template state is anything other than Active or Draft
and the Action has not been modified since it was created, the Flag column
will contain the icon.
and the Action has been modified, the Flag column will contain the
icon.
and the Action has been removed from the Asset Strategy Template (and
therefore the Action record has been unlinked from the Asset Strategy
Template record), the Flag column will contain the icon.
Name: The name of the action. This column contains a hyperlink that you can
click to access the Action datasheet, where you can modify the Action.
Cost: The cost of performing the action.
Nonrecurring: A check box indicating whether or not the action should be

repeated on a recurring basis.
Number of Recommendations: The number of source Recommendations that were

promoted to create this Action. This column contains a hyperlink that you can
click to access the Manage Recommendations to Action Links page.
Add Action: Displays the New Action window, where you can create a new
Action. This button is always enabled.
Remove Action: Causes the Meridium APM system to delete the Action the next
time the Asset Strategy Template state is set to Active. This button is enabled only
if the Asset Strategy Template state is Active.
Undo Action: Reverses the last action that you performed on the Action. For
example, if you created the Action, the Undo Action button will remove the
Action from the grid. If you last clicked the Remove Action button, the Undo
Action button will undo this step, causing the Action to appear in the grid without
the icon. This button is enabled only if the Asset Strategy Template state is
Draft or Modified.
Note: The instructions for performing the actions described above are explained in the
context of an Asset Strategy. These instructions can also be used to perform these actions
in the context of an Asset Strategy Template.
If you want to collapse the Proposed Strategy section, you can click the up arrow in the
Proposed Strategy section header. To expand the section again, you can click the down
arrow.
Mitigated Risks Section

The Mitigated Risks tab contains a grid, which displays a list of Risks that are associated
with the Action that is selected in the Proposed Strategy section. Each row in the grid
Flag: An icon indicating the status of the Risk Assessment record that is linked to
the Risk record.
If the Asset Strategy Template state is Modified or Pending Review and

the Risk Assessment record has not been modified since it was created, the
Flag column will contain the icon.

the Risk Assessment record has been modified, the Flag column will not
contain an icon.

the Risk Assessment record has been removed from the Asset Strategy
Template (and therefore unlinked from the Asset Strategy record), the Flag
Name: The name of the risk.
Unmitigated Risk Rank: The calculated risk rank in the Risk record.
Action Mitigated Risk Rank: The calculated risk rank in the Risk Assessment
record that is linked to the Risk record. This column contains a hyperlink that you
can click to access the risk matrix, where you can modify the mitigated risk value
on any tab.
Actions that are associated with the Risk.
Assign New Risk: Displays the Create Risk Wizard, where you can create a new
Risk that is associated with the Action. This button is disabled if you are logged in
Assign Existing Risks: Displays the Assign Risks window, where you can select
existing Risks to associate with the Action. This button is disabled if you are
logged in as a member of the ASM Viewer Security Group.
Health Indicators Tab

The Health Indicators tab contains a grid, which displays a list of Health Indicator
records that are linked to the Action record that is selected in the Proposed Strategy
section. Each row in the grid represents one Health Indicator record.
Name: The hyperlinked name of the Health Indicator record. You can click the
hyperlink to view the Health Indicator datasheet.
Description: A description of the Health Indicator.
Add Indicator: Displays the Create New Health Indicator dialog box, where you
can create a new Health Indicator record to link to the selected Action record.
Delete Indicator: After asking for confirmation, deletes the selected Health
Indicator record.
Accessing the Asset Strategy Risks Page
To access the Asset Strategy Risks page:

1. Search for and open an Asset Strategy.
2. On the Navigation menu, click the Risks link.
The Asset Strategy Risks page appears.
A list of Risks that are included in the Asset Strategy is displayed in the Risks section.
Overview of the Asset Strategy Risks

Page
The Asset Strategy Risks page is divided into the following sections:
Risks: Contains a grid, which displays a list of Risks that are included in the Asset
Strategy.
Mitigating Actions: Contains a grid, which displays a list of Actions that are
associated with the Risk that is selected in the Risks section.
Risks Section
The Risks section contains a grid, which displays a list of Risks that are included in the
Asset Strategy. Each row in the grid represents one Risk.
Flag: An icon indicating the status of the Risk.
If the Asset Strategy state is Modified or Pending Review and the Risk has
not been modified since it was created, the Flag column will contain the
icon.
been modified, the Flag column will contain the
icon.
been removed from the Asset Strategy (and therefore the Risk record has
been unlinked from the Asset Strategy record), the Flag column will
contain the icon.
Name: A short name describing the risk. This column contains a hyperlink that
you can click to access the Risk datasheet, where you can modify the Risk record.
Unmitigated Risk Rank: The calculated risk rank for the risk. This column
contains a hyperlink that you can click to access the risk matrix, where you can
modify the unmitigated risk value on any tab.
actions that mitigate the risk.
Source: A hyperlink that indicates the source of the Risk.
Add Risk: Displays the Create Risk Wizard, where you can create a new Risk.
This button is disabled if you are logged in as a member of the ASM Viewer
Security Group. Otherwise, this button is always enabled.
Copy Risk: Creates a copy of the selected Risk, where the Record ID of the new
Risk record is Copy of <Risk Name> n, where <Risk Name> is the value in the
Name field in the source Risk record and n is a numeric value indicating the order
in which the copy was created, relative to other copies of the same source Risk
record. The new Risk will contain the same values as the source Risk. This button
is disabled if you are logged in as a member of the ASM Viewer Security Group.
Remove Risk: Causes Meridium APM to delete the Risk the next time the Asset
Strategy state is set to Active. You can select multiple Risks to delete them all at
the same time. This button is enabled only if the Asset Strategy state is Active.
Security Group.
Undo Risk: Reverses the last action that you performed on the Risk. For example,
if you created the Risk, the Undo Risk button will remove the Risk from the grid.
If you last clicked the Remove Risk button, the Undo Risk button will undo this
action, causing the Risk to appear in the grid without the icon. You can select
multiple Risks to reverse the last action that you performed on them. This button
is enabled only if the Asset Strategy state is Draft or Modified. This button is
disabled if you are logged in as a member of the ASM Viewer Security Group.
Note that if you want to collapse the Risks section, you can click the
button in the
Risks section header. To expand the section again, you can click the
button.
Mitigating Actions Section

The Mitigating Actions section contains a grid, which displays a list of Actions that are
associated with the Risk that is selected in the Risks section. Each row in the grid
represents one Action.
If the Asset Strategy state is Modified or Pending Review and the Action
has not been modified since it was created, the Flag column will contain
the icon.
If the Asset Strategy state is Modified or Pending Review and the Action
has been modified, the Flag column will contain the icon.
If the Asset Strategy state is anything Modified or Pending Review and the
Action has been removed from the Asset Strategy (and therefore the
Action record has been unlinked from the Asset Strategy record), the Flag
Name: A short name describing the action.
Action Mitigated Financial Risk Rank: The value on the Financial tab of the risk
matrix when it is accessed from the Action.
Action Mitigated Risk Rank: The calculated risk rank for the action. This column
modify the mitigated risk value on any tab.
ROI: The return on investment for the Action.
Assign New Action: Displays the New Action window, where you can create a
new Action that is associated with the Risk. Note that a warning message will
appear if you try to assign an Action to a Risk that is flagged for deletion. This
button is disabled if you are logged in as a member of the ASM Viewer Security
Group.
Assign Existing Actions: Displays the Assign Actions window, where you can
select the existing Actions to associate with the Risk. Note that a warning message
will appear if you try to assign an Action to a Risk that is flagged for deletion.
Security Group.
Note that if you want to collapse the Mitigating Actions section, you can click the
button in the Mitigating Actions section header. To expand the section again, you can
click the
button.
Accessing the ASM - Asset Strategy

Template Risks Page
To access the Asset Strategy Template Risks page:
1. Search for and open the desired Asset Strategy Template.
The Asset Strategy Template Overview page appears,.

The Asset Strategy Template Risks page appears.
A list of the Risks that belong to the Asset Strategy Template is displayed in the Risks
section.
Overview of the Asset Strategy Template

Risks Page
The Asset Strategy Template Risks page is divided into the following sections:
Risks: Contains a grid, which displays a list of Risks that belong to the Asset
Strategy Template.
Mitigating Actions: Contains a grid, which displays a list of Actions that are
associated with the Risk that is selected in the Risks section.
Risks Section
The Risks section contains a grid, which displays a list of Risks that belong to the Asset
Strategy Template. Each row in the grid represents one Risk.
Flag: An icon indicating the status of the Risk.

the Risk has not been modified since it was created, the Flag column will
contain the icon.

the Risk has been modified, the Flag column will contain the
icon.

the Risk has been removed from the Asset Strategy Template (and
therefore the Risk record has been unlinked from the Asset Strategy
Template record), the Flag column will contain the icon.
Name: The name of the risk. This column contains a hyperlink that you can click
to access the Risk datasheet, where you can modify the Risk.
Unmitigated Risk Rank: The calculated risk rank for the risk. This column
modify the unmitigated risk value on any tab.
Actions that are associated with the Risk.
Source: A hyperlink that indicates the source of the Risk.
Add Risk: Displays the Create Risk Wizard, where you can create a new Risk.
This button is always enabled. This button is disabled if you are logged in as a
member of the ASM Viewer Security Group.
Copy Risk: Creates a copy of the selected Risk, where the Record ID of the new
Risk record is Copy of <Risk Name> n, where <Risk Name> is the value in the
Name field in the source Risk record and n is a numeric value indicating the order
in which the copy was created, relative to other copies of the same source Risk
record. The new Risk will contain the same values as the source Risk. This button
Remove Risk: Causes Meridium APM to delete the Risk the next time the Asset
Strategy Template state is set to Active. This button is enabled only if the Asset
Strategy Template state is Active. This button is disabled if you are logged in as a
Undo Risk: Reverses the last action that you performed on the Risk. For example,
if you created the Risk, the Undo Risk button will remove the Risk from the grid.
If you last clicked the Remove Risk button, the Undo Risk button will undo this
action, causing the Risk to appear in the grid without the icon. This button is
enabled only if the Asset Strategy Template state is Draft or Modified. This button
Note that if you want to collapse the Risks section, you can click the up arrow in the
Risks section header. To expand the section again, you can click the down arrow.
Mitigating Actions Section

The Mitigating Actions section contains a grid, which displays a list of Actions that are
associated with the Risk that is selected in the Risks section. Each row in the grid
represents one Action.

the Action has not been modified since it was created, the Flag column

the Action has been modified, the Flag column will contain the icon.
If the Asset Strategy Template state is anything Modified or Pending

Review and the Action has been removed from the Asset Strategy
Template (and therefore the Action record has been unlinked from the
Asset Strategy Template record), the Flag column will contain the icon.
Name: The name of the action.
Action Mitigated Financial Risk Rank: The value on the Financial tab of the risk
matrix when it is accessed from the Action record.
Action Mitigated Risk Rank: The calculated risk rank for the action. This column
modify the mitigated risk value on any tab.
Assign New Action: Displays the New Action window, where you can create a
new Action that is associated with the Risk. Note that a warning message will
appear if you try to assign an Action to a Risk that is flagged for deletion. This
button is disabled if you are logged in as a member of the ASM Viewer Security
Group.
select the existing Actions to associate with the Risk. Note that a warning message
will appear if you try to assign an Action to a Risk that is flagged for deletion.
Security Group.
Note that if you want to collapse the Mitigating Actions section, you can click the up
arrow in the Mitigating Actions section header. To expand the section again, you can
click the down arrow.
About Managing a System Strategy

From the System Strategy Management page, you can view the Asset Strategies that
belong to the System Strategy, and:
Add new Asset Strategies to the System Strategy.
Add existing Asset Strategies to the System Strategy.
Remove an Asset Strategy from the System Strategy.
Accessing the System Strategy

Management Page
To access the System Strategy Management page:
1. Search for and open the System Strategy that you want to manage.
2. On the Navigation menu, click the Manage System link.
The System Strategy Management page appears.
Aspects of the System Strategy

Management Page
The System Strategy Management page contains the Asset Strategies grid, which displays
the list of Asset Strategies that make up the System Strategy. Each row in the grid
represents one Asset Strategy. For each Asset Strategy in the grid, the following
information is displayed by default:
Strategy ID: The value stored in the Strategy ID field in the corresponding Asset
Strategy record. This value appears as a hyperlink, which you can click to view
the Asset Strategy on the Asset Strategy Overview page.
Description: The value stored in the Description field in the corresponding Asset
Strategy record.
Asset Name: The value stored in the Asset Name field in the corresponding Asset
Strategy record.
Asset Type: The value stored in the Asset Type field in the corresponding Asset
Strategy record.
Create New: Displays a new Asset Strategy record on the Asset Strategy
Definition page.
Add Existing: Displays the Find Items window, where you can search for an
existing Asset Strategy to add to the Unit Strategy.
Remove Selected: After displaying a confirmation message, removes the selected
Asset Strategy from the Unit Strategy.
About Managing a Unit Strategy

From the Unit Strategy Management page, you can view the System Strategy records
that belong to the Unit Strategy, and:
Add new System Strategies to the Unit Strategy.

Add existing System Strategies to the Unit Strategy.
Remove System Strategies from the Unit Strategy.
Accessing the Unit Strategy

Management Page
To access the Unit Strategy Management page:
1. Search for and open the Unit Strategy that you want to manage.
2. On the Navigation menu, click the Manage Unit link.
The Unit Strategy Management page appears.
Aspects of the Unit Strategy

Management Page
The Unit Strategy Management page contains the System Strategies grid, which displays
the list of System Strategies that make up the Unit Strategy. Each row in the grid
represents one System Strategy. For each System Strategy in the grid, the following
information is displayed by default:
System ID: The value stored in the System ID field in the corresponding System
Strategy record. This value appears as a hyperlink, which you can click to view
the System Overview page for the corresponding System Strategy.
Description: The values is stored in the Description field in the corresponding

System Strategy record.
Create New: Displays a new System Strategy record on the System Strategy
Definition page.
Add Existing: Displays the Find Items window, where you can search for an
existing System Strategy to add to the Unit Strategy.
Remove Selected: After displaying a confirmation message, removes the selected
System Strategy from the Unit Strategy.
Accessing the Asset Strategy Risk

Analysis
To access the Asset Strategy risk analysis:
1. Search for and open the Asset Strategy whose risk analysis you want to view.
2. On the Navigation menu, click the Risk Analysis link.
The Asset Strategy Risk Analysis page appears.
About the Asset Strategy Risk Analysis

The Asset Strategy risk analysis contains the following items:
Actions section: Contains a grid containing a list of the Actions that are included
in the Proposed Strategy.
Risk and Cost Summary pane: Contains the following graphs:
Note that if you want to collapse the Risk and Cost Summary pane, you can click the
button in the Risk and Cost Summary pane header. To expand the pane again, you
can click the
button.
The Asset Strategy risk analysis is displayed on the Asset Strategy Risk Analysis page.
Actions Section
The Asset Strategy Risk Analysis page contains the Actions section. The Actions section
contains a grid that lists the Actions that are included in the Proposed Strategy.
Each row in the grid represents an Action. You can click a hyperlink in the Name column
to see the Action datasheet for the Action represented by that row. Note, however, that
you cannot modify the Action from this page.
In addition, you can:
Clear the Selected Actions check box in any row. Doing so causes the graphs
below the grid to change, reflecting the potential impact to the Asset Strategy if
you were to decide not to perform that action.
Click the Basis for Revision button to enter text explaining why you have decided
to modify the Asset Strategy.
Click the Show Changes button to see a list of changes that have been made to
any Action that appears in the list. The list will reflect changes between the Action
that is included in the Active Strategy and the Action that is included in the
Proposed Strategy. If no changes have been made to the Action since the Asset
Strategy was last activated, the Show Changes button will be disabled.
Note that you will typically want to review the changes if you are responsible for
reviewing changes waiting for approval.

Risk Analysis
To access the Asset Strategy Template risk analysis:
1. Search for an open the Asset Strategy Template whose risk analysis you want to
view.
The Asset Strategy Template Risk Analysis page appears.
About the Asset Strategy Template Risk

Analysis
The Asset Strategy Template risk analysis appears on the Asset Strategy Template Risk
Analysis page and contains the following items:
Actions section: Contains a grid that contains a list of the Actions that belong to
the Proposed Asset Strategy Template record.
can click the
button.
Strategy Templates.
Actions Section
The Asset Strategy Template Risks page contains the Actions section. The Actions
section contains a grid that lists the Actions that are belong to the Proposed Strategy.
Each row in the grid represents an Action. You can click a hyperlink in the Name column
to see the Action datasheet for the Action represented by that row. Note, however, that
you cannot modify the Action from this page.
This section contains the following options:
Selected Actions check box: Specifies whether or not you want the action to be
performed as part of the Asset Strategy. Clearing the Actions check box indicates
that you do not want that action to be performed. Selecting the Actions check box
indicates that you want that action to be performed. When you modify this check
box, the graphs below the grid will change, reflecting the potential impact to the
Asset Strategy Template.
Basis for Revision button: Displays the Basis For Revision text box, where you
can enter text explaining why you have decided to modify the Asset Strategy
Template.
Show Changes button: Displays a list of changes that have been made to any
Action that appears in the list. The list will reflect changes between the
Action that is belongs to the Active Strategy Template and the Action that
belongs to the Proposed Strategy Template. If no changes have been made to
the Action since the Asset Strategy Template was last activated, the Show
Changes button will be disable. You will typically want to review the changes
if you are responsible for reviewing changes waiting for approval.
Strategy Templates.
Accessing the System Strategy Risk

Analysis
To access the System Strategy risk analysis:
1. Search for and open the System Strategy whose risk analysis you want to view.
The System Strategy Risk Analysis page appears.
About the System Strategy Risk

Analysis
The System Strategy risk analysis contains the following items:
Actions section: Contains a grid containing a list of the Actions that belong to the
underlying Proposed Strategies.
can click the
button.
The System Strategy risk analysis is displayed on the System Strategy Risk Analysis
page.
Actions Section
The System Strategy Risk Analysis page contains the Actions section. The Actions
section contains a grid that lists the Actions that belong to the underlying Proposed
Strategies.
Each row in the grid represents an Action. The following columns contain a hyperlinks:
Name: Displays the Action datasheet for the Action represented by that row.
Strategy ID: Displays the Asset Strategy Risk Analysis page for the Asset Strategy
that contains that Action.
below the grid to change, reflecting the potential impact to the System Strategy if
to modify the System Strategy. Note that entering a basis for revision on a System
Strategy will override the basis for revision on all underlying Asset Strategies.
that belongs to the underlying Proposed Strategy and the Action that belongs to
the underlying Active Strategy. If no changes have been made to the Action since
the underlying Asset Strategy was last activated, the Show Changes button will be
disabled.
The Running Total column contains a value representing the total yearly cost of
performing the action represented by that row and all actions in all rows above it.
Accessing the Unit Strategy Risk

Analysis
To access the Unit Strategy risk analysis:
1. Search for and open the Unit Strategy whose risk analysis you want to view.
The Unit Strategy Risk Analysis page appears.
About the Unit Strategy Risk Analysis

The Unit Strategy risk analysis contains the following items:
Actions section: Contains a grid containing a list of the Actions that belong to the
underlying Proposed Strategies.
can click the
button.
The Unit Strategy risk analysis is displayed on the Unit Strategy Risk Analysis page.
Actions Section
The Unit Strategy Risk Analysis page contains the Actions section. The Actions section
contains a grid that lists the Actions that belong to the underlying Proposed Strategies.
Each row in the grid represents an Action. The following columns contain a hyperlinks:
System ID: Displays the System Strategy Risk Analysis page for the System
Strategy that contains the Asset Strategy that contains that Action.
Strategy ID: Displays the Asset Strategy Risk Analysis page for the Asset Strategy
that contains that Action.
Name: Displays the Action datasheet for the Action represented by that row.
below the grid to change, reflecting the potential impact to the Unit Strategy if
to modify the Unit Strategy.
that belongs to the underlying Proposed Strategy and the Action that belongs to
the underlying Active Strategy. If no changes have been made to the Action since
the underlying Asset Strategy was last activated, the Show Changes button will be
disabled.
The Running Total column contains a value representing the total yearly cost of
performing the action represented by that row and all actions in all rows above it.
Accessing the Review Asset Strategy

Page
To access the Review Asset Strategy page:
1. Search for and open the Asset Strategy that you want to review.
2. On the Navigation menu, click the Review Strategy link.
The Review Asset Strategy page appears.
Accessing the Review Asset Strategy

Template Page
To access the Review Asset Strategy Template page:
1. Search for and open the Asset Strategy Template that you want to review.
The Review Asset Strategy Template -page appears.
Accessing the Review System Strategy

Page
To access the Review System Strategy page:
1. Search for and open the System Strategy that you want to review.
The Review System Strategy page appears.
Accessing the Review Unit Strategy

Page
To access the Review Unit Strategy page:
1. Search for and open the Unit Strategy that you want to review.
The Review Unit Strategy page appears.
Search Menu
The Search menu appears one every page in ASM and contains links that you can use to
navigate to the search pages associated with the link labels. For example, the Unit
Strategies link displays the Unit Strategy Search page, where you can search for an
existing Unit Strategy.
When you are viewing a search page (e.g., Unit Strategy Search), a green arrow appears
to the left of the link that is associated with the current page, indicating the page that you
are viewing. For example, the following image shows the Search menu as it appears on
the Unit Strategy Search page.
The Search menu contains the following links:
Asset Strategies: Displays the Asset Strategy Search page, where you can search
for an existing Asset Strategy.
System Strategies: Displays the System Strategy Search page, where you can
search for an existing System Strategy.
Unit Strategies: Displays the Unit Strategy Search page, where you can search for
an existing Unit Strategy.
Templates: Displays the Asset Strategy Template Search page, where you can
search for an existing Asset Strategy Template.
Navigation Menu
The Navigation menu appears throughout ASM and provides access to features that are
available in the ASM module. When you are viewing an Asset Strategy-specific page in
ASM, the Navigation menu offers quick access to other features within the context of the
Asset Strategy that you are currently viewing. Likewise, if you are viewing a System
Strategy-specific page, the Navigation menu offers quick access to other features within
the context of the System Strategy. The same is true for Unit Strategy-specific pages.
For example, if you access the Unit Strategy Overview page, you can click the Unit
Definition link on the Navigation menu to view the Unit Strategy Definition page for that
same strategy.
Note: The link for the page that you are currently viewing will always be labeled with a
green arrow.
The following table lists the links that are available on the Navigation menu and the
behavior of the link, depending on the type of strategy you are viewing when you click
the link.
Hint: The Site Map can help you determine the type of strategy that you are currently
viewing.
Overview
Health
Indicators
Strategy
Definition
Behavior if clicked
while viewing a
System Strategy
Displays the System
Strategy Overview
page.
Behavior if clicked
while viewing a
Unit Strategy
Displays the Unit
Strategy Overview
page.
Displays the Asset Strategy When you are

Overview page.
viewing a System
Strategy, this link is
labeled System
Overview.
Displays the Asset Health
Manager - <Strategy ID>
page.
This link does not
appear on the
This link is enabled only if
Navigation menu
the Asset Strategy record is
when you are
linked to an Equipment or
viewing a System
Functional Location record
Strategy.
and the Asset Health
Manager module is active.
Displays the System
Strategy Definition
page.
When you are

viewing a Unit
Strategy, the link is
labeled Unit
Overview.
Displays the Asset Strategy When you are

Definition page.
viewing a System
Strategy, this link is
labeled System
Definition.
When you are

viewing a Unit
Strategy, the link is
labeled Unit
Definition.
Behavior if clicked while

viewing an Asset Strategy
Link
This link does not

appear on the
Navigation menu
when you are
viewing a Unit
Strategy.
Displays the Unit
Strategy Definition
page.
Actions
This link does not

appear on the
Displays the Asset Strategy Navigation menu
Actions page.
when you are
viewing a System
Strategy.
This link does not

appear on the
Navigation menu
when you are
viewing a Unit
Strategy.
Risks
This link does not

appear on the
Risks page.
when you are
viewing a System
Strategy.
This link does not

appear on the
Navigation menu
when you are
viewing a Unit
Strategy.
Risk Analysis
Displays the System Displays the Unit

Displays the Asset Strategy
Strategy Risk
Strategy Risk
Risk Analysis page.
Analysis page.
Analysis page.
Review
Strategy
Displays the Review Asset

Strategy page.
Displays the Review Displays the

System Strategy
Review Unit
page.
Strategy page.
This link does not

This link does not
appear on the
appear on the
Revision
Navigation menu
History
Revision History page.
when you are
when you are
viewing a System
viewing a Unit
Strategy.
Strategy.
If the Asset Strategy

Strategy
Displays the
record is not yet linked Displays the
Implementation
Implementation
to an Implementation Implementation
Package List page, Package List page,
Package record,
which displays a list which displays a list
displays a message
of Implementation of Implementation
asking if you want to
link the Asset Strategy Package records that Package records
are linked to any
that are linked to
record to a new
Asset Strategy record any underlying
Implementation
Package record, where that is linked to the Asset Strategy
record.
you can click the Yes System Strategy
record.
button to display the
Implementation
Package Creation page.
If the Asset Strategy

record is linked to an
Implementation
Package record,
displays the Packaging
<Package ID> page,
where <Package ID> is
the ID of the
Implementation
Package record to which
the Asset Strategy
record is linked.
This link does not
This link does not appear on
appear on the
Displays the System
the Navigation menu when
Navigation menu
Manage System
Strategy
you are viewing an Asset
when you are
Management page.
Strategy.
viewing a Unit
Strategy.
This link does not
This link does not appear on
appear on the
Displays the Unit
the Navigation menu when
Manage Unit
Navigation menu
Strategy
you are viewing an Asset
you are viewing a
Management page.
Strategy.
System Strategy.
Displays a submenu of
Displays a submenu
options that let you navigate
with an option that
to the RCM, FMEA, SIS
lets you view the
Management, RBI, or ACA
ACA Analysis from
analysis or view the
which the System
Recommendation records
This link is disabled
Strategy was created.
from which the Asset
when you are
Source Analyses
Strategy was created.
viewing a Unit
If the current System
Strategy.
Strategy was not
If the Asset Strategy was not
created from an ACA
created from an analysis or
Analysis, this link is
from Recommendation
disabled.
records, this link is disabled.
Tools Menu
The Tools menu appears one every page in ASM and contains links that you can use to
create an ASO Analysis from a strategy or run a simulation for an existing ASO Analysis.
The Tools menu contains the following links:
Optimize Strategy: Displays different items, depending upon several factors,

which are described in the following list.
If you are creating an ASO Analysis from the strategy, the Validate
Strategy window appears, which displays Actions and Risks that are
missing values that are needed to run a simulation.
If you are opening an existing ASO Analysis containing one or more

Scenarios whose Actions and Risks do not contain the necessary values to
run a simulation, the Validate Strategy window appears, which displays
Actions and Risks that are missing values that are needed to run a
simulation.
If you are opening an existing ASO Analysis containing Scenarios whose

Actions and Risks do contain the necessary values to run a simulation, if
you are currently viewing an Asset Strategy, the ASO Analysis appears on
one of the following pages:
If the ASO Analysis has been saved with simulation results, the
Asset Strategy Optimization Summary page appears.
If the ASO Analysis has not been saved with simulation results, the
Asset Strategy Optimization Analysis Definition page appears.
If you are opening an existing ASO Analysis containing Scenarios whose

Actions and Risks do contain the necessary values to run a simulation, if
you are currently viewing a System Strategy or Unit Strategy, one of the
following items appears:
If you have already defined which pieces of equipment and

locations cause a shutdown, the Asset Strategy Optimization
Summary page appears.
If you have not already defined which pieces of equipment and
locations cause a shutdown, the Asset Strategy Optimization
Builder appears, displaying the Welcome screen. You will need to

use the builder to define which pieces of equipment and locations
cause a shutdown.
Run Simulation: Runs the simulation and refreshes the current page to display the
updated results. Note that if the Enable Event Log check box is selected on the
Asset Strategy Optimization Analysis Definition page, the Browse For Folder
dialog box appears, where you can choose where you want to save the Event Log
before running the simulation. If you are viewing an existing Asset Strategy to
which changes have not been made since the last time the simulation was run,
however, a message will appear, indicating that the simulation does not need to be
run.
Common Tasks Menu

The Common Tasks menu that appears throughout ASM (except for when you are
working with Asset Strategy Templates) contains the following links:
Create Strategy: Displays the ASM - Asset Strategy Definition page, where you
can create a new Asset Strategy record.
Import Strategy: Displays the Open dialog box, where you can select an Excel file
to use for creating a new Asset Strategy.
Note: The Import Strategy link is available only if you viewing an Asset Strategy. It is not
available if you are viewing a System Strategy or Unit Strategy.
Delete Strategy: After asking for confirmation, deletes the selected Asset Strategy,
including the Asset Strategy record and all records to which it is linked, either
directly or indirectly.
Page.
Help: Displays the context-sensitive Help topic for the current page.
Template Tasks Menu

The Template Tasks appears throughout ASM when you are working with an Asset
Strategy and contains the following links:
Save as Template: Displays the Asset Strategy Template Definition page, where
you can define the Asset Strategy Template that you want to create from the Asset
Strategy that you are currently viewing. This link is disabled if you are logged in
Apply a Template: Displays the Apply Template Builder, which you can use to
apply an Asset Strategy Template to the Asset Strategy that you are currently
viewing. This link is disabled if you are logged in as a member of the ASM
Viewer Security Group.
Go To Master: Displays the Asset Strategy Template page that corresponds to the
Asset Strategy page that you are currently viewing. For example, if you are
viewing the Asset Strategy Definition page, when you click this link, the Asset
Strategy Template Definition page appears. If you are viewing an Asset Strategy
page that has no corresponding page for Asset Strategy Templates, the Asset
Strategy Template Overview page will appear by default. This link is enabled only
if you are viewing an Asset Strategy to which an Asset Strategy Template has
been applied as a Master Template.
Remove From Master: Displays a confirmation message, asking if you are sure
that you want to remove the Asset Strategy from the Master Template, and then
removes the Asset Strategy from the Master Template. This link is enabled only if
you are viewing an Asset Strategy to which an Asset Strategy Template has been
applied as a Master Template.
Note: The Template Tasks menu does not appear when you are working with Asset
Strategy Templates.
Associated Pages Menu

The following table explains the links are displayed on the Associated Pages menu
throughout ASM. If a page is not listed in the table, the Associated Pages menu is not
available on that page.
This page
...Displays links that are defined for this

family
Asset Strategy Definition
Asset Strategy
Asset Strategy Overview
Asset Strategy
Asset Strategy Actions
The Associated Pages menu appears but

does not display any links.
Asset Strategy Risks

Asset Strategy Risk Analysis
Asset Strategy
Review Asset Strategy
Asset Strategy
Asset Strategy Revision History
Asset Strategy
System Strategy Definition
System Strategy
System Strategy Overview
System Strategy
System Strategy Management
System Strategy
System Strategy Risk Analysis
System Strategy
Review System Strategy
System Strategy
Unit Strategy Definition
Unit Strategy
Unit Strategy Overview
Unit Strategy
Unit Strategy Management
Unit Strategy
Unit Strategy Risk Analysis
Unit Strategy
Review Unit Strategy
Unit Strategy
Asset Strategy Template Definition
Asset Strategy Template Overview
Asset Strategy Template Actions

Asset Strategy Template Risks

Asset Strategy Template Risk Analysis
Review Asset Strategy Template
Asset Strategy Template Revision History Asset Strategy Template
Available Task Menus for Asset Strategy

Templates
When you are working with Asset Strategy Templates in ASM, the following task menus
are available:
Search
Navigation
Common Tasks
Associated Pages
The options that are available on these menus may vary, depending on the content that
you are currently viewing.
Navigation Menu
The Navigation menu appears throughout ASM when you are working with Asset
Strategy Templates and contains the following links:
Overview: Displays the Asset Strategy Template Overview page. This link is
enabled only after the Asset Strategy Template record is saved.
Template Definition: Displays the Asset Strategy Template Definition page.
Actions: Displays the Asset Strategy Template Actions page. This link is enabled
only after the Asset Strategy Template record is saved.
Risks: Displays the Asset Strategy Template Risks page. This link is enabled only
after the Asset Strategy Template record is saved.
Risk Analysis: Displays the Asset Strategy Template Risk Analysis page. This link
is enabled only after the Asset Strategy Template record is saved.
Controlled Strategies: Displays the Master Template Management page. This link
is enabled only after the Asset Strategy Template record is saved.
Review Template: Displays the Review Asset Strategy Template page. This link is
enabled only after the Asset Strategy Template record is saved.
Revision History: Displays the Asset Strategy Template Revision History page.
This link is enabled only after the Asset Strategy Template record is saved.
When you navigate to a page using the links on the Navigation menu, a green arrow
appears to the left of the link to indicate the page that you are currently viewing. For
example, when you are viewing the Asset Strategy Template Risk Analysis page, a green
arrow appears to the left of the Risk Analysis link, indicating that you are currently
working with an Asset Strategy Template Risk Analysis.
Common Tasks Menu
The Common Tasks menu appears throughout ASM when you are working with Asset
Strategy Templates and contains the following links:
Create Template: Displays a blank Asset Strategy Template record on the Asset
Strategy Template Definition page. This link is disabled if you are logged in as a
Import Template: Displays the Open dialog box, where you can navigate to the
Microsoft Excel file that you want to import, and then import the file. This link is
disabled if you are logged in as a member of the ASM Viewer Security Group.
Apply Template: Displays the Apply Template Builder, which you can use to
apply an Asset Strategy Template to an Asset Strategy. This link is always
disabled on the Asset Strategy Template Search page. This link is disabled if you
are logged in as a member of the ASM Viewer Security Group.
Copy Template: Creates a copy of the template with which you are currently
working and displays it on the ASM - Asset Strategy Template Definition page.
This link is enabled only if you have create privileges on the Asset Strategy
Template family. This link is disabled, however, if you are logged in as a member
of the ASM Viewer Security Group.
Delete Template: Deletes the selected Asset Strategy Template record and all
records (Action, Proposed Strategy, Active Strategy, etc.) to which it is linked.
This link is disabled if you are logged in as a member of the ASM Viewer
Security Group.
Page.
Help: Displays the help topic for the page that you are currently viewing.
ASM Workflow
The following workflow represents the basic steps that you might use to create Asset
Strategies, System Strategies, and a Unit Strategy, assuming that your database does not
yet contain any of these items. After you have completed this workflow, you will
probably find that you need to repeat certain steps at various times depending on your
company's specific needs, changing conditions, and your role within the organization.
In general, you will need to perform the following tasks to create Asset Strategies that roll
up to System Strategies and System Strategies that roll up to a Unit Strategy:
1. Create an Asset Strategy record.
2. Link the Asset Strategy record to an Equipment or Functional Location record that
is already stored in your database.
3. Add Risks to the Asset Strategy that you created in step 1. Risks represent ways in
which a piece of equipment or location can fail and the consequences of the
failures.
4. Add Actions to the Asset Strategy that you created in step 1. Actions represent
actions that prevent the defined failures or reduce the severity of the
consequences.
5. Propose the Asset Strategy. As a proposed strategy, the strategy will be available
for review by other users.
6. Review the Asset Strategy. As a user who is responsible for reviewing the Asset
Strategy, you will need to accept the proposed strategy or send it back to the
creator for additional work.
7. Modify the Asset Strategy. If the strategy was sent back for additional work, make
any desired changes to the strategy. Otherwise, proceed to step 8.
8. Repeat steps 5 through 7 for each equipment or location for which you want to
create a strategy.
9. Create a System Strategy record.
10. Link Asset Strategy records to the System Strategy record.
11. Review the System Strategy. As a user who is responsible for reviewing the Asset
Strategy, you will need to evaluate the strategy and activate it, which will also
activate all associated Asset Strategies.
12. Create a Unit Strategy record.
13. Link System Strategy records to the Unit Strategy record.
After you have created Asset Strategies, System Strategies, and Unit Strategies, you can
search for and open an existing strategy to make any changes.
About Creating Asset Strategies

Using ASM, you can create Asset Strategies:
From scratch.
By using an Asset Strategy Template, which copies data from an existing Asset
Strategy Template into a new Asset Strategy.
By importing data from an Excel file.
By transferring data from existing Task records.
By transferring data from existing Measurement Location records.
By promoting an ACA System to ASM.
By promoting existing Recommendation records to ASM.
By importing them from a different database.
Creating an Asset Strategy from Scratch

To create an Asset Strategy from scratch:
1. Create an Asset Strategy record.
2. Link the Asset Strategy record to an Equipment or Functional Location record that
is already stored in your database.
3. Add Risks to the Asset Strategy that you created in step 1. Risks represent ways in
which a piece of equipment or location can fail and the consequences of the
failures.
4. Add Actions to the Asset Strategy that you created in step 1. Actions represent
actions that prevent the defined failures or reduce the severity of the
consequences.
Creating an Asset Strategy Record

To create an Asset Strategy record:
1. Access the ASM - Asset Strategy Definition page.
2. Enter values in the fields on the Main tab.
3. If desired, use the Asset tab to link the Asset Strategy record to an Equipment or
Functional Location record.
4. If you want to link the Asset Strategy record to a Reference Document record, on
the datasheet toolbar, click the button, and use the Reference Documents
window to select the desired file.
5. On the toolbar, click the
button.
The Asset Strategy record is saved. If you linked the Asset Strategy record to an
Equipment or Functional Location record that is linked to a Site Reference record, the
Record ID of the Site Reference record is displayed in the Site Reference cell.
About Importing Asset Strategies from

Microsoft Excel
If desired, you can create an Asset Strategy from a Microsoft Excel file. When you do so,
the Meridium APM system will create:
One Asset Strategy record.

One Active Strategy record that is linked to the Asset Strategy record.
One Proposed Strategy record that is linked to the Asset Strategy record.
Multiple Action records, which are linked to the Proposed Strategy record.
Multiple Risk records, which are linked to the Proposed Strategy record.
Multiple Risk Assessment records, which are linked to the Risk records that are
created.
Multiple Risk Rank records, which are linked to the Risk Assessment records that
are created.
During the import process, you can map values in the Microsoft Excel file to fields in the
Meridium APM records that will be created. To make sure that the mappings work
correctly, the Microsoft Excel file must meet the minimum requirements listed in the
following table.
Requirement
Example Used
Throughout This
Documentation
The Microsoft Excel file must contain a worksheet

that lists the equipment and locations for which
Assets worksheet
you are creating Asset Strategies. There are no
restrictions on the tab name.
Notes
Always required
The Assets worksheet must contain a column

whose values you will map to the Strategy ID field Strategy ID column Always required
in the Asset Strategy records.
The Assets worksheet must contain a column that
contains IDs of valid Equipment and Functional
Location records in Meridium APM. Each Asset
Asset ID column
Strategy record that is created will be linked to one
of these Equipment or Functional records after the
import procedure has been completed.
Always required
The Excel file must contain a worksheet that lists

the Actions that you want to include in the Asset
Strategies. There are no restrictions on the tab
name.
Actions worksheet Always required
The Actions worksheet must contain a column

whose values you will map to the Action ID field
in the Action records.
Action ID column Always required
The Actions worksheet must contain a column that

Asset ID column
Location records in Meridium APM. Each ID must
exist in at least one row on the Assets worksheet.
Always required

that lists the Risks that you want to include the
Risk worksheet
Asset Strategies. There are no restrictions on the
tab name.
Required only if
you want the
Asset Strategies
to contain Risks.
The Risks worksheet must contain a column that

Asset ID column
Location records in Meridium APM. Each ID must
exist in at least one row on the Assets worksheet.
Required only if
you want the
Asset Strategies
to contain Risks.

that lists the Risk Assessment and Risk Rank
Mitigations
values that will be associated with the Risks. There worksheet
are no restrictions on the tab name.
Required only if
you want the
Asset Strategies
to contain Risks.
Required only if
The Mitigations worksheet must contain a column
you want the
that contains values that exist in at least one row on Action ID column
Asset Strategies
the Actions worksheet.
to contain Risks.
The Mitigations worksheet must contain a column
that contains values that exists in at least one row Risk ID column
on the Risks worksheet.
Required only if
you want the
Asset Strategies
to contain Risks.
The Asset worksheet must contain a column that

stores the name of the EAM system in which the
technical objects exist.
Required only if
you are using
multiple EAM
systems.
EAM column
Note that if you want to map a value to the Action Type field in an Action record, the
Microsoft Excel file must contain a value that mimics an Action Type as it is stored in the
Meridium APM database, not as it is displayed on the Action datasheet. Use the following
table to determine the Action Types that can be mapped from the Microsoft Excel file to
Action records.
Value in Microsoft Excel File Value that Will Appear on the Action Datasheet
PM
Time-Based Maintenance (Preventive) (PM)
CM
Condition-Based Maintenance (Predictive) (CM)
DSN
Redesign (DSN)
PROC
Procedure (PROC)
TRN
Training (TRN)

The following instructions assume that a Microsoft Excel file that meets the minimum
requirements has been saved to a location that is accessible from your workstation.
Note: You must be a Super User or a member of the MI ASM Analyst Security Group to
perform the following steps.
To import an Asset Strategy:
1. On the ASM - Start Page, click the Import Strategy link.
-OROn any Common Tasks menu in ASM, click the Import Strategy link.
The Asset Strategy Builder appears, displaying the Welcome screen.
2. Click the Next button.

The Select Import Method screen appears.
3. Select the Excel option, and then click the Next button.
The Open dialog box appears.
4. Navigate to the location containing the Microsoft Excel file that you want to use
for importing an Asset Strategy, select the file, and then click the Open button.
The Select Data to Import window appears, displaying the Assets tab by default.
5. In the Required Mappings section, in the Asset Worksheet list, select the Assets
worksheet that is configured in the Microsoft Excel file. This is the spreadsheet
that contains a column whose value you will map to the Strategy ID field in the
Asset Strategy record.
6. In the Strategy ID Column list, select the column whose value you want to map to
the Strategy ID field in the Asset Strategy record.
7. In the Asset ID Column list, select the column whose value contains an ID of a
valid Equipment or Functional Location record in the database.
8. If you want the Asset Strategy record to be linked to an existing Equipment or
Functional Location record:
a. In the Optional Mappings section, in the Meridium Asset Family list,
select the desired family: Equipment or Functional Location.
b. In the Optional Mappings section, in the Meridium Asset ID Field list,
select the ID field of the desired Equipment or Functional Location record.
Meridium APM will use the value that you selected in the Asset ID
Column list to determine the Microsoft Excel file column that contains the
ID of the Equipment or Functional Location record to which you want to
link the Asset Strategy record.
9. To populate other fields in the Asset Strategy record, in the Additional Mappings
section, to the right of each Excel Column cell, select a value in the Meridium
Strategy Field column that represents a field that you want to populate from that
Microsoft Excel file column. For example, if the Microsoft Excel file contains the
column Notes, to the right of the Notes cell, you would probably want to select
Strategy Notes.
10. Click the Actions tab.
11. In the Action Worksheet list, select the Actions worksheet that is configured in the
Microsoft Excel file. This is the worksheet that contains a column whose value
you will map to the Action ID field in the Action record.
12. In the Asset Reference Column list, select the column whose value contains an ID
of a valid Equipment or Functional Location record in the database.
13. In the Action ID list, select the column whose value you want to map to the
Action ID field on the Action datasheet.
14. To populate other fields in the Action records, in the Additional Mappings section,
to the right of each Excel Column cell, select a value in the Meridium Action
Field column that represents a field that you want to populate from that Microsoft
Excel file column. For example, if the Microsoft Excel file contains the column
Type, to the right of the Type cell, you would probably want to select Action
Type.
Note: At this point, you could click OK to create an Asset Strategy that does not contain
Risks. The remaining instructions, however, assume that you want to import Risks from
the Microsoft Excel file to the Asset Strategy.
15. Click the Risks tab.
16. In the Risk Worksheet list, select the Risks worksheet that is configured in the
you will map to the Risk ID field in the Risk record.
17. In the Asset Reference Column list, select the column whose value contains an ID
of a valid Equipment or Functional Location record in the database.
18. In the Risk ID Column list, select the column whose value you will map to the
Risk ID field in the Risk record.
19. In the Meridium Risk Matrix list, select the Risk Matrix that you want the Asset
Strategy to use.
20. To populate other fields in the Risk records, in the Additional Mappings section,
to the right of each Excel Column cell, select a value in the Meridium Risk Field
column that represents a field that you want to populate from that Microsoft Excel
file column.
Note: If the Risk Matrix that you selected in the previous step does not contain a
Financial tab, the Meridium Risk Field lists will not display any financial fields.
21. Click the Mitigations tab.
22. In the Mitigation Worksheet list, select the Mitigations worksheet that is
configured in the Microsoft Excel file.
23. In the Action Reference Column list, select the column that contains the ID of an
Action, as it appears on the Actions worksheet.
24. In the Risk Reference Column list, select the column that contains the ID of a
Risk, as it appears on the Risks worksheet.
25. To populate other fields in the Risk Assessment records, in the Additional
Mappings section, to the right of each Excel Column cell, select a value in the
Meridium Risk Assessment Field column that represents a field that you want to
populate from that Microsoft Excel file column.
26. Click OK.
The Import Existing Strategy page appears, displaying the results of the import
procedure. Each row represents an Asset Strategy that was created successfully, unless
otherwise specified. In some cases, an Asset Strategy may not have been imported. If so,
a message will appear in the Info column, indicating the reason that strategy was skipped.
The Strategy column contains a hyperlink, which you can click to access the Asset
Strategy Actions page.
Note: When you navigate away from the Import Existing Strategy page, you will be
prompted to save the results to a file. If you want to save the result to a text file, click the
Yes button, and provide a name for the file. If you do not want to save the results, click
the No button to proceed with viewing the Asset Strategy.
Saving a Mapping
To save a mapping from a Microsoft Excel file to an Asset Strategy:
1. After you have accessed the Select Data to Import dialog box and configured the
mappings that you want to save, click the Save Mapping button.
The Save Mapping window appears.
2. In the Mapping Name text box, type a new name for the mapping.
3. Click OK.
The mapping is saved, and the Save Mapping window closes. The Pre-Configured
Mapping list above the Assets tab is populated with the mapping name. Other users that
access the Select Data to Import window will now be able to select this mapping and use
it to create a new Asset Strategy.
Microsoft Excel File Structure

Consider the following example, which explains how to create two Asset Strategies,
where one Asset Strategy contains three Action records, and the other Asset Strategy
contains two Action records.
Assets Worksheet
The Microsoft Excel file contains the Assets worksheet, as shown in the following image.
From this worksheet, you can see that two Asset IDs are listed: 19-02600 and 19-04500.
Because an Asset Strategy record can be linked to only one Equipment or Functional
Location record, when you use this Microsoft Excel file to create Asset Strategies, two
Asset Strategy records will be created. One of these records will be linked to the record
with the ID 19-02600, and the other Asset Strategy record will be linked to the record
with the ID 19-04500.
Actions Worksheet
The Microsoft Excel file also contains the Actions worksheet, as shown in the following
image. (The tab is displayed in the following two separate images to make the columns
easier to see.)
In the Microsoft Excel file, the three yellow rows represent actions for equipment 1902600, and the two blue rows represent actions for equipment 19-04500. The ID that is
associated with each action is displayed in the Asset ID column.
In other words, for equipment 19-02600, the following actions should be performed:
Vibration Analysis
Basic Lube Oil Analysis
Complete Lube Oil Analysis
Likewise, for equipment 19-04500, the following actions should be performed:
Performance Test
Internal Inspection
Each action will be used to create a single Action when the import procedure is
performed.
Risks Worksheet
The Microsoft Excel file also contains the Risks worksheet, as shown in the following
image. (The tab is displayed in the following two separate images to make the columns
easier to see.)
In the Microsoft Excel file, the two yellow rows represent risks for equipment 19-02600,
and the blue row represents the risk for equipment 19-04500. The asset ID that is
associated with each risk is displayed in the Asset ID column.
In other words, for equipment 19-02600, the following risks exist:
Bearing Failure
Seal Leak
Likewise, for equipment 19-04500, the following risk exists:
Misalignment
Each risk will be used to create a single Risk when the import procedure is performed.
Mitigations Worksheet
Finally, the Microsoft Excel file contains the Mitigations worksheet, as shown in the
following image.
In the Microsoft Excel file, the yellow row indicates that the action Vibration Analysis
mitigates the risk Bearing Failure. Likewise, the blue row indicates that the action
Performance Test mitigates the risk Misalignment.
Mappings
Based on the example Microsoft Excel file structure, when performing the import
procedure, you could specify the mappings from the Assets worksheet of the Microsoft
Excel file, as shown in the following image.
Note that in the Additional Mappings section, the Asset ID and Strategy ID are not
mapped from the Microsoft Excel file to the Asset Strategy record. In this example, these
fields have already been mapped using the Required Mappings section of this dialog box.
If additional columns were available in the Assets worksheet of the Microsoft Excel file,
they would also be listed in the Additional Mappings section, and you might consider
mapping them to a field in the Asset Strategy record (e.g., Strategy Notes).
Likewise, you could specify the mappings from the Actions worksheet of the Microsoft
Excel file, as shown in the following image.
You could specify the mappings from the Risks worksheet of the Microsoft Excel file, as
shown in the following image.
Finally, you could specify the mappings from the Mitigations tab of the Microsoft Excel
file, as shown in the following image.
Result
Using the example Microsoft Excel file structure and mappings, when the import
procedure is complete, two Asset Strategies would be created, as shown in the following
image.
The Asset Strategy Strategy for 19-04500 would be linked to the Action records shown in
the following image.
The fields in Action: Internal Inspection would be populated as shown in the following
image.
Because the Mandatory column in the Microsoft Excel file contained the value TRUE,
the Mandatory check box is selected, which causes most of the remaining fields to be
disabled.
The Asset Strategy would also contain the Risk record Misalignment, which would be
associated with the Action Action: Performance Test, as shown in the following image.
The mitigated Risk Rank for the Safety category would be 0.05, which appears at the
intersection of the Probability 0.05 and the Consequence 1, as shown in the following
image.
If you remember from the Mitigations worksheet in the Microsoft Excel file, for the
Performance Test, the Mitigated Safety Probability value is 0.05, and the Mitigated
Safety Consequence is 1. These values are highlighted in the following image.
About Importing Asset Strategies from

SAP
If you use SAP to track information about your current strategies, you might want to
transfer that data from your SAP system to your Meridium APM system. Doing so will
allow you to track those strategies in the Meridium APM system using ASM and other
Meridium APM modules.
If desired, you can create an Asset Strategy from data in SAP using the Asset Strategy
Builder. When you do so, for each Equipment or Functional Location record that you
select in the Asset Strategy Builder, the Meridium APM system will create:

Multiple Action records, which are linked to the Proposed Strategy record. Each
Action record represents a separate item from SAP.
One Implementation Package record, which is linked to the Asset Strategy record.
Multiple work item records, where each one represents an SAP item that you
imported. Each work item record will be included in the Implementation Package
that is created automatically.
Using the Asset Strategy Builder, you can import SAP data using several different
scenarios.
Workflow for Importing Asset Strategies

from SAP
Importing Asset Strategies from SAP is just one step in a larger workflow that involves
multiple modules and features. The following table identifies the workflow in which we
suggest that you import Asset Strategies from SAP.
Step Location/Feature Task

1
SAP Interfaces
Extract Equipment and Functional Locations from SAP.
ASM
Create Asset Strategies from existing SAP plans for those pieces
of equipment and locations.
ASM
Perform a risk assessment, including modifying or removing

Actions that were created from SAP, creating new Actions, and
defining risk.
ASI
Create the appropriate work items to reflect the changes that you
made to the Asset Strategy, and then transfer the changes back to
SAP.
ASM
If additional SAP plans are created for the same SAP Equipment
or Functional Locations (e.g., new Notifications are created),
import those new items into the existing Asset Strategies for those
Equipment and Functional Location records.
Import Scenarios
The structure of data in SAP is shown in the following diagram.
In addition, SAP uses Notifications, which are not part of this data hierarchy.
Assuming that your SAP system contains at least one of each item in the preceding image
and a Notification, you could use the Asset Strategy Builder in the following ways:
Import Maintenance Plans and all items below them. If you choose this option, in
the Asset Strategy Builder, you will be prompted to select which items will be
used to create Actions. You can choose to:
Create Actions from the associated Maintenance Items.
Create Actions from the associated Operations.
In either case, one Action will be created for each Maintenance Item or Operation that
you import. In addition, one work item record will be created for each SAP item that you
import. For example, if you import only one Maintenance Plan, only one Maintenance
Plan record will be created.
The appropriate links will also be created between the work item records that are created
automatically. For example, if you import a Maintenance Plan that has two Maintenance
Items, one Maintenance Plan record and two Maintenance Item records will be created,
and the Maintenance Item records will be linked to the Maintenance Plan record through
the Has Maintenance Item relationship.
Import Maintenance Items and all items below them. If you choose this option, in
the Asset Strategy Builder, you will be prompted to select which items will be
used to create Actions. You can choose to:
Create Actions from the selected Maintenance Item.
Create Actions from the associated Operations.
In either case, one Action will be created for each Maintenance Item or Operation that
you import. In addition, one work item record will be created for each SAP item that you
import. For example, if you import only one Maintenance Item, one Maintenance Item
record will be created.
automatically. For example, if you import a Maintenance Item that has two Object Lists,
one Maintenance Item record and two Object List Item records will be created, and the
Object List Item records will be linked to the Maintenance Item record through the Has
Object List Item relationship.
Import Task Lists and all items below them. If you choose this option, one Action
will be created for each Operation that you import. In addition, one work item
record will be created for each SAP item that you import. For example, if you
import only one Task List, one Task List record will be created.
automatically. For example, if you import a Task List that has two Materials, one Task
List record and two Material records will be created, and the Material records will be
linked to the Task List record through the Has Materials relationship.
Import Notifications. If you choose this option, one Action will be created for
each Notification that you import. In addition, one Notification record will be
created for each SAP Notification that you import.
Conditions Required to Create Asset

Strategies from SAP
To import data from SAP to create Asset Strategies, the following pre-requisites must be
met:
The ASI for SAP license must be active.

At least one Site Reference record must exist in your database.
The Site Reference record must be linked to at least one Equipment or Functional
Location record that represents the Equipment or Functional Location whose
items you want to import from SAP. If you followed the suggested workflow and
extracted Equipment and Functional Locations from SAP using the SAP
Interfaces, records in the Equipment and Functional Location families were
created automatically and linked automatically to the appropriate Site Reference
record.
The Equipment and Functional Location families must be related to the Asset
Strategy family through the Has Strategy relationship.
If you are importing items associated with SAP Functional Locations, the Locate
Assets by Site Reference for Import query must be configured to return Site
Reference records that are linked to Functional Location records.
What Happens to Asset Strategies that

are Created from SAP Items?
After you create a new Asset Strategy from SAP items:
The Asset Strategy will be set to the Active state.

The following fields in the Asset Strategy record will be populated automatically:
Strategy ID
Note: The Strategy ID field will be populated with the value in the Equipment Technical
Number field of the Equipment record or the Functional Location ID field of the
1.
Description
Note: The Description will be Strategy imported from existing Work Management Items
on [Current Date and Time], where [Current Date and Time] is the date and time on
which the Asset Strategy record was created.
1.
Strategy Owner
Strategy Activated By
Plan Length
Asset Name
Asset Type
Site Reference
A new work item record will be created for each SAP item that you imported. For
example, suppose you import the following items.
Using this example, the following work item records and links would be created.
A new Action will be created from each Maintenance Item, Operation, Task List,
or Notification that you imported. The data in each Action is copied from the
corresponding work item record using the rules referenced in the Action Mapping
record to which the source work item record is linked.
No Risks will be created. You will need to assign Risks to each Action manually.
The Asset Strategy record will be linked to an Implementation Package record.
The Implementation Package record will be set to the Implemented state and
linked to the work item records that were created from the imported SAP items.
When you perform the import procedure, you can choose whether the
Implementation Package will be a primary or secondary Implementation Package.
If you update an existing Asset Strategy with new SAP items for the same SAP
Equipment or Functional Location for which the Asset Strategy exists:
The Asset Strategy will be set automatically to the Active state.

A new work item record will be created for each SAP item that you imported.
A new Action will be created from each new Maintenance Item, Operation, Task
List, or Notification that you imported. The data in each Action is copied from the
corresponding work item record using the rules referenced in the Action Mapping
record to which the source work item record is linked.
No Risks will be created. You will need to assign Risks to each Action manually.

The Implementation Package record will be set to the Implemented state and
linked to the work item records that were created from the newly imported SAP
items. When you perform the import procedure, you can choose whether the
Implementation Package will be a primary or secondary Implementation Package.
Configuring the Locate Assets by Site

Reference for Import Query
The Locate Assets by Site Reference for Import query, which is located in the Catalog
folder \\Public\Meridium\Modules\Asset Strategy Management\Management\Queries, is
intended to display either Equipment or Functional Location records that are linked to
Site Reference records. When you choose to import SAP items to create Asset Strategies,
the query results are displayed on the Select SAP Object(s) screen of the Asset Strategy
Builder.
By default, the query returns records in the Equipment family. If your Site Reference
records are linked to Functional Location records, however, you will need to modify the
query to return records in the Functional Location family.
To configure the Locate Assets by Site Reference for Import query:
1. In the Catalog, navigate to the folder \\Public\Meridium\Modules\Asset Strategy
Management\Management\Queries.
2. Open the Locate Assets by Site Reference for Import query.
3. On the Query Tasks menu, click the Design View link.

The query design appears, displaying the Equipment, Has Site Reference, and Site
Reference families as the sources.
4. Remove the Equipment family.
Note: Removing the Equipment family will remove the Has Site Reference family
automatically.
5. Add the Functional Location and Has Site Reference families.
6. Add any fields that will help you identify the Functional Location records when
the results are displayed in the Asset Strategy Builder.
7. On the Common Tasks menu, click the Save Query link.
The query is saved.

To import an Asset Strategy from SAP:
-OROn any Common Tasks menu in ASM, click the Import Strategy link.

3. Select the SAP Work Management Item(s) option.
Note: The SAP Work Management Item(s) option appears only if the ASI for SAP license
is active.
The Select Implementation Package to Import Into section appears, which you can use to
select whether to import the Work Management Item(s) into your Asset Strategy as a
Primary or a Secondary Implementation Package.
e
The Select SAP Object(s) screen appears.
5. In the Select Site Reference list, select the Site Reference record that is linked to
the Equipment or Functional Location records representing the SAP Equipment or
Functional Locations whose items you want to import.
The list below the Select Site Reference list is updated to display the Equipment records
or the Functional Location records that are linked to the selected Site Reference record.
Note: The grid displays either the Equipment records or the Functional Location records
that are linked to the selected Site Reference record. It does not display both the
Equipment and Functional Location records that are linked to the selected Site Reference
record. Whether you see Equipment records or Functional Location records depends on
how the Locate Assets by Site Reference for Import query has been configured.
6. In the Select SAP Object Type list, select the items that you want to import from
SAP. You can select one of the following options:
Maintenance Plans
Maintenance Items
Task Lists
Notifications
7. In the grid, select the rows containing the Equipment or Functional Location
records representing the SAP Equipment or Functional Locations whose items
you want to import.

If you selected Maintenance Plans or Maintenance Items in the Select SAP Object Type
list, the Select How Actions Are Created screen appears. In this case, proceed with the
next step of these instructions.
-ORIf you selected Task Lists or Notifications in the Select SAP Object Type list, the Select
SAP Work Management Item(s) screen appears. In this case, proceed to step 11 of these
instructions.
9. On the Select How Actions Are Created screen, select one of the following
options:
Import Maintenance Items as Actions: An Action will be created for each

Maintenance Item that is imported.
Import Operations as Actions: An Action will be created for each

Operation that is imported.

The Select SAP Work Management Item(s) screen appears.
11. On the Select SAP Work Management Item(s) screen, in the grid, select the rows
containing the SAP items that you want to import. The list displays only SAP
items of the type that you selected in the Select SAP Object Type list on the Select
SAP Object(s) screen. The list is also filtered to display only those items for the
Equipment or Functional Locations that you selected in the grid on the Select
SAP Object(s) screen.
For example, if you selected Maintenance Plan in the Select SAP Object Type list and
Equipment 101 in the grid, the Select SAP Work Management Item(s) screen would
display only Maintenance Plans for Equipment 101.
12. Click the Finish button.
procedure. The Strategy column contains a hyperlink, which you can click to access the
Asset Strategy Actions page for the new Asset Strategy.
prompted to save the results to a file. If you want to save the result to a text file, click the
About Creating or Updating Asset

Strategies from Task Records
If desired, you can create an Asset Strategy from existing Task records. When you do so,
Meridium APM will create:

Action record represents a separate Task record.
Before you can create an Asset Strategy from Task records, several conditions must be
met.
If you create an Asset Strategy from a Task record and later modify values in the Task
record, the corresponding Action record in the Asset Strategy will be updated. If the Asset
Strategy was set to the Active state, it will be set to the Modified state when the Action
record is updated.

Strategies from Tasks
Before you can create an Asset Strategy from Task records, the following conditions must
be met:
The Task records must be linked to Equipment or Functional Location records.

The Related Record ID field in the Task records must contain the Record ID of
the Equipment or Functional Location record that is linked to the Task record.
The Equipment and Functional Location must be related to the Asset Strategy
family through the Has Strategy relationship.
In Asset Strategy Implementation (ASI), in the Work Management Item

Definition record that represents the Task records that will be used to create the
Asset Strategy, the Allow Link Existing check box must be selected. For example,
if you want to create an Asset Strategy from Inspection Task records, the Allow
Link Existing check box in the Inspection Task Work Management Item
Definition record must be selected.
The Locate Assets for Import query must be configured to return records in the
appropriate family: Equipment or Functional Location.

are Created from Task Records?
After you create a new Asset Strategy from existing Task records:

The following fields on the Asset Strategy record will be populated automatically:
Strategy ID
1.
Description
1.
Strategy Owner
Plan Length
Asset Name
Asset Type
A new Action is created from each Task record that you selected in the Asset
Strategy Builder. The data in each Action is copied from the source Task record
using the rules referenced in the Action Mapping record that is linked to the Work
Management Item Definition record whose Family ID field contains the value
Inspection Task (if the Asset Strategy is created from an Inspection Task record)
or Calibration Task (if the Asset Strategy is created from a Calibration Task
record).
Note: If the Rejectable field in the Task record is set to True, the Mandatory field will be
set to False in the Action record.
No Risks are created. You will need to assign Risks to each Action manually.
The Implementation Package record will be set to the Implemented state. In
addition, the Implementation Package record will be linked to the work item
record (e.g., Inspection Task) that was used to create the Asset Strategy. When
you perform the import procedure, you can choose whether the Implementation
Package will be a primary or secondary Implementation Package.
About Creating Asset Strategies from

Existing Measurement Location
Records
If desired, you can create an Asset Strategy from existing Measurement Location records.
When you do so, Meridium APM will create:

Action record represents a Measurement Location record that you selected during
the import process.
Multiple Measurement Location Group records, where each Measurement

Location Group record is linked to a separate Measurement Location record that
you selected during the import process. For example, if you select three
Measurement Location records, three Measurement Location Group records will
be created during the import process. Each of those Measurement Location Group
records will be linked to a single Measurement Location record.
Multiple Health Indicator records, which are linked to the Action records. Each
Health Indicator record is linked to a Measurement Location record that you
selected during the import process.
Before you can create an Asset Strategy from Measurement Location records, several
conditions must be met.

Strategies from Measurement Location
Records
Before you can create an Asset Strategy from Measurement Location records, the
following conditions must be met:
The Measurement Location records must be linked to Equipment or Functional

Location records.

Definition record that represents Measurement Location Group records and
Measurement Location records, the Allow Link Existing check box must be
selected.
The Locate Assets for Import query must be configured to return records in the
appropriate family: Equipment or Functional Location.

are Created from Measurement
Location Records?
After you create a new Asset Strategy from existing Measurement Location records:

The following fields on the Asset Strategy record will be populated automatically:
Strategy ID
Description
Strategy Owner
Plan Length
Asset Name
Asset Type
A new Action is created from each Measurement Location record that you
selected in the Asset Strategy Builder. The data in each Action is copied from the
source Measurement Location record using the rules referenced in the Action
Mapping record that is linked to the Work Management Item Definition record
with the value Measurement Location Group in the Family ID field.
A new Health Indicator record is created from each Measurement Location record
that you selected in the Asset Strategy Builder. Each Health Indicator record is
linked to the corresponding Action record that was created during the import
process.
No Risks are created. You will need to assign Risks to each Action manually.

The Implementation Package record will be set to the Implemented state. In
addition, the Implementation Package record will be linked to Measurement
Location Group records. The number of Measurement Location Group records to
which it is linked mimics the number of Measurement Location records that were
selected in the Asset Strategy Builder. Each Measurement Location Group record
will also be linked to a Measurement Location record that was selected during the
import process.
Creating an Asset Strategy from Task or

Measurement Location Records
To create an Asset Strategy from existing Task or Measurement Location records:


3. Select the Meridium Work Management Item(s) option.

The Select Implementation Package to Import Into section appears, which you can use to
select whether to import the Work Management Item(s) into your Asset Strategy as a
Primary or a Secondary Implementation Package.

The Select Asset(s) screen appears.
5. Select the rows containing the Equipment or Functional Location records that are
linked to the Task and Measurement Location records that you want to use for
creating a new Asset Strategy.
The Select Work Management Item(s) screen appears, displaying a list of all Task and
Measurement Location records that are not already linked to an Action record through the
Has Action Driver relationship.
7. Select the rows containing the Task or Measurement Location records that you
want to use for creating a new Asset Strategy.
procedure. Each row represents an Asset Strategy that was created successfully. The
Strategy column contains a hyperlink, which you can click to access the Asset Strategy
Overview page for the new Asset Strategy.
prompted to save the results to a file. If you want to save the result to a Text file, click the
Configuring the Locate Assets for

Import Query
The Locate Assets for Import query, which is located in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Management\Queries, is used
when you create Asset Strategies from Task or Measurement Location records. By
default, the query returns records in the Equipment family. If the Task and Measurement
Location records are linked to Functional Location records, however, you will need to
modify the query to return records in the Functional Location family.
To configure the Locate Assets for Import query so that you can create Asset Strategies
from Task and Measurement Location records:
1. In the Catalog, navigate to \\Public\Meridium\Modules\Asset Strategy
2. Open the Locate Assets for Import query.
The query design appears, displaying the Equipment family as the source.
5. Add the Functional Location family as a source.
the results are displayed in the Asset Strategy Builder, which appears when you
click the Import Strategy link on the ASM - Start Page.
The query is saved.
About Asset Strategies that are Created

by Promoting Recommendation
Records
After you promote a Recommendation record ASM, an Asset Strategy will be created,
and the Action record that is created from the Recommendation record is populated
automatically with values in the Recommendation record.
In addition to the Action record being created, the following records are also created:

If the Recommendation record was created as part of an RCM or FMEA Analysis,

additional records are also created.
Creating an Asset Strategy by

Promoting a Recommendation Record
To create an Asset Strategy by promoting a Recommendation record:
1. On the Recommendation Management page, locate the row containing the
Recommendation record(s) that you want to promote to Action record(s).
2. Promote the Recommendation record to an Action. You can:
Promote a Recommendation record that is linked to an Equipment or

-OR1.
Promote a Recommendation record that is not linked to an Equipment or

The Recommendation record is promoted to a new Action.
About Asset Strategies that are Created

by Promoting RCM FMEA
Recommendation Records
When you promote an RCM FMEA Recommendation record to ASM, the Meridium
APM system will create an Asset Strategy and automatically populate values in the
Action record with values from the RCM FMEA Recommendation record.
More specifically, in addition to the Action record being created, the following records
are also created:

One Risk record, which is linked to the RCM FMEA Failure Effect record to
which the RCM FMEA Recommendation record is linked. Certain fields in the
Risk record will be populated automatically with values in the RCM FMEA
Failure Effect record. Other fields in the Risk record will be populated
automatically with values in the RCM FMEA Failure Mode record to which the
RCM FMEA Failure Effect record is linked.
Note: If a Reference Document record is linked to the RCM FMEA Failure Effect record
to which the RCM FMEA Recommendation record is linked, the Reference Document
record will also be linked to the Risk record that is created and linked to the RCM FMEA
Failure Effect record automatically.
One Risk Assessment record, which is linked to the Proposed Strategy record, the
Action record, and the Risk record that are linked to the Proposed Strategy record.
Certain fields in the Risk Assessment record will be populated automatically with
values in the RCM FMEA Recommendation record that you promoted. Other
fields in the Risk Assessment record will be populated automatically with values
in the RCM FMEA Failure Effect record to which the RCM FMEA
Recommendation record is linked.
Multiple Risk Rank records, which are linked to the Risk record, the Risk
Assessment record, and the Action record. Each Risk Rank records stores a value
that you specified in the Risk Assessment interface when you defined risk values
for the RCM FMEA Failure Effect record that is linked to the RCM FMEA
Recommendation record that you promoted to the Action record.
For example, if you selected the value 100 on the Environment tab when defining the risk
value for the RCM FMEA Failure Effect record, the value in the Consequence field in the
Environment Risk Rank record will be 100.
If you are creating an Asset Strategy by promoting an RCM FMEA Analysis, each of the
scenarios described above will occur for each Recommendation record that is linked to
the RCM FMEA Analysis.
Note: The Meridium APM system uses the Site Reference record that is associated with
the RCM FMEA Analysis to transfer risk assessment information from RCM FMEA to
ASM.
About Creating Asset Strategies by

Promoting RCM FMEA Analyses
When you create an Asset Strategy by promoting an RCM FMEA Analysis, the process is
similar to creating an Asset Strategy by promoting an RCM FMEA Recommendation
record. However, when you promote an Analysis, you are promoting at the level of the
RCM FMEA Asset. In this case, you promote ALL of the Recommendation records that
are linked to that Analysis.
Creating an Asset Strategy by

Promoting an RCM FMEA Analysis
To create an Asset Strategy by promoting an RCM FMEA Analysis:
1. For the RCM FMEA Analysis you want to promote, access the Recommendation
Management page via RCM or FMEA.
2. On the Asset Tasks menu, click the Promote to Strategy link.
Note: If you do not have any RCM FMEA Asset records associated with the RCM FMEA
Analysis, or if you have both physical and "virtual" pieces of equipment or locations
associated with the RCM FMEA Analysis, this link will be disabled.
3. If the State Configuration for the Accepted by ASM state is defined in a way that
does not require a Security User to be assigned, or if the State Configuration for
the Accepted by ASM state already has a Security User assigned, a progress bar
appears, as shown in the following image. In this case, skip Step 4 of these
instructions.
- or If the State Configuration for the Accepted by ASM state is defined in a way that requires
a Security User to be assigned, but a Security User is not currently assigned, the State
Assignee dialog box appears, as shown in the following image. In this case, proceed to
the next step in these instructions.
4.
On the State Assignee dialog box, select the Security User that you want to assign
to the Accepted by ASM state, and click OK.
The progress bar shown above appears.

The new Asset Strategy records appear on the Asset Strategy Actions page.
Values Mapped from RCM FMEA

Failure Effect Fields to Risk Fields
When you promote a Recommendation record to an Action to create a new Asset
Strategy, if the Recommendation record is linked to an RCM FMEA Failure Effect
record, along with a new Action record, a new Risk record is also created. Several values
in the RCM FMEA Failure Effect record are used to populate fields in the Risk record.
The following table describes these field mappings.
RCM FMEA Risk Field

Failure
Effect Field
Notes
Driving Risk
Driving Risk None
Driving Risk
Category
Driving Risk
None
Category
Effect Name
Name
The Name field in the Risk record is populated with a

concatenation of the value in the Failure Mode Name field
in the RCM FMEA Failure Mode and the Effect Name
field in the RCM FMEA Failure Effect record to which it is
linked. For example, if the Failure Mode Name is Failure
Mode 1 and the Effect Name is Failure Effect 1, the Name
in the Risk record will be Failure Mode 1 - Failure Effect
1.
Unmitigated
Risk
Risk Rank
None
Unmitigated
Financial
Financial Risk Risk
Effect Long
Description
None
Description The Description field in the Risk record is populated with a

concatenation of the value in the Failure Mode Long
Description field in the RCM FMEA Failure Mode record
and the Effect Long Description - Modified field in the
RCM FMEA Failure Effect record to which it is linked. For
example, if the Failure Mode Long Description is Failure
Mode Long Description and the Failure Effect Long
Description is Failure Effect Long Description, the

Description in the Risk record will be Failure Mode Long
Description - Failure Effect Long Description.
In an RCM FMEA Failure Effect record, if you modify a value that was used to populate
a Risk record, the updated value will be reflected in the Risk record.
However, in a Risk record, if you change a value that was mapped from an RCM FMEA
Failure Effect field, the updated value is not reflected in the RCM FMEA Failure Effect
field. For example, if you change the value in the Risk Rank field in the Risk record, the
value is not transferred automatically to the Unmitigated Risk field in the RCM FMEA
Failure Effect record.

Failure Effect Fields to Risk Assessment
Fields
record, along with a new Risk record, a new Risk Assessment record is also created.
Several values in the RCM FMEA Failure Effect record are used to populate fields in the
Risk Assessment record. The following table describes these field mappings.
RCM FMEA Risk

Notes
Failure
Assessment
Effect Field Field
Driving Risk
Driving Risk None
Driving Risk
Category
Driving Risk
None
Category
Effect Name
Name
The Name field in the Risk Assessment record is populated

with a concatenation of the value in the Failure Mode
Name field in the RCM FMEA Failure Mode and the
Effect Name field in the RCM FMEA Failure Effect record
to which it is linked. For example, if the Failure Mode

Name is Failure Mode 1 and the Effect Name is Failure
Effect 1, the Name in the Risk Assessment record will be
Failure Mode 1 - Failure Effect 1.
Unmitigated
Risk
Risk Rank
Unmitigated
Financial
Financial Risk Risk
None
None
In an RCM FMEA Failure Effect record, if you modify a value that was used to populate
a Risk Assessment record, the updated value will be reflected in the Risk Assessment
record.
However, in a Risk Assessment record, if you change a value that was mapped from an
RCM FMEA Failure Effect field, the updated value is not reflected in the RCM FMEA
Failure Effect field. For example, if you change the value in the Name field in the Risk
Assessment record, the value is not transferred automatically to the Effect Name field in
the RCM FMEA Failure Effect record.

Failure Mode Fields to Risk Fields
Strategy, a new Risk record is also created. Several values in the associated RCM FMEA
Failure Mode record (the RCM FMEA Failure Mode record that is linked to the RCM
FMEA Failure Effect record to which the RCM FMEA Recommendation record is
linked) are used to populate fields in the Risk record. The following table describes these
field mappings.
RCM FMEA Failure Mode Field Risk Field

PF Interval
PF Interval
PF Interval Units
PF Interval Units
In an RCM FMEA Failure Mode record, if you modify a value that was used to populate
a Risk record, the updated value will be reflected in the Risk.
However, in a Risk record, if you change a value that was mapped from an RCM FMEA
Failure Mode field, the updated value is not reflected in the RCM FMEA Failure Mode
field. For example, if you change the value in the PF Interval field in the Risk record, the
value is not transferred automatically to the PF Interval field in the RCM FMEA Failure
Mode record.

Recommendation Fields to Risk
Assessment Fields
record, along with a new Action record, a new Risk Assessment record is also created.
Several values in the RCM FMEA Recommendation record are used to populate fields in
the Risk Assessment record. The following table describes these field mappings.
RCM FMEA
Recommendation
Field
Risk
Notes
Assessment
Field
None
Name
The Name field in the Risk Assessment record is

populated with a concatenation of the value in the
Failure Mode Name field in the associated RCM
FMEA Failure Mode and the Effect Name field in
the RCM FMEA Failure Effect record to which it is
linked. For example, if the Failure Mode Name is
Failure Mode 1 and the Effect Name is Failure
Effect 1, the Name in the Risk record will be Failure
Mode 1 - Failure Effect 1.
Mitigated Risk
Risk Rank
None
Mitigated Financial
Risk
Financial
Risk
None
In an RCM FMEA Recommendation record, if you modify a value that was used to
populate a Risk Assessment record, the updated value will be reflected in the Risk
Assessment record.
However, in a Risk Assessment record, if you change a value that was mapped from an
RCM FMEA Recommendation field, the updated value is not reflected in the RCM
FMEA Recommendation field. For example, if you change the value in the Risk Rank
field in the Risk Assessment record, the value is not transferred automatically to the
Mitigated Risk field in the RCM FMEA Recommendation record.

Recommendation Fields to Action
Fields
When you promote an RCM FMEA Recommendation record to an Action to create a new
Asset Strategy, values in the Recommendation record are used to populate fields in the
Action record. The following table describes these mappings.
RCM FMEA Recommendation Field
Action Field
Recommendation Headline
Name
Recommendation Description
Description
None. The Action Basis field is

populated automatically with the value Action Basis
RCM/FMEA Recommendation.
Action Type
Action Type
Interval
Interval
Interval Units
Interval Units
Estimated Cost
Cost
Asset Shutdown Required?
Shutdown
Required
Estimated Cost Basis
Cost Basis
Nonrecurring
Nonrecurring
Performance Interval
Performance
Interval
Performance Interval Units
Performance
Interval Units
Recommended Resource
Recommended
Resource
Target Completion Date
Target
Completion Date
In the RCM FMEA Recommendation record, if you update the value in the fields listed in
this table, the updated value will be reflected in the Action record in ASM.
Creating a System Strategy Record

The following instructions provide details on manually creating a System Strategy record.
You can also create a System Strategy record by promoting an ACA System to ASM.
To create a System Strategy record:
1. Access the System Strategy Definition page.
2. Complete the fields as desired.
button.
The System Strategy record is saved.
Creating a Unit Strategy Record

To create a Unit Strategy record:
1. Access the Unit Strategy Definition page.
button.
The Unit Strategy record is saved.
About Opening Strategies

Meridium APM provides the following pages to allow you to open existing strategies:
Asset Strategy Search: Lets you search for and open existing Asset Strategies.
System Strategy Search: Lets you search for and open existing System Strategies.
Unit Strategy Search: Lets you search for and open existing Unit Strategies.
Opening an Existing Strategy

To open an existing strategy:
1. On the ASM - Start Page, click the Search for Strategy link.
-OR-
On any page within Asset Strategy Management, on the Search menu, click the link
corresponding to the type of strategy that you want to find (i.e., to search for an Asset
Strategy, click the Asset Strategies link).
The strategy search page appears.
1.
o
If you clicked the Asset Strategies link on the Search menu, the Asset
Strategy Search page appears.
If you clicked the System Strategies link on the Search menu, the System
If you clicked the Unit Strategies link on the Search menu, the Unit
2. Use the search workspace to open the desired strategy.

1.
o
If you are viewing the Asset Strategy Search page, use the Asset Strategy
Search workspace to open the desired Asset Strategy.
If you are viewing the System Strategy Search page, use the System
Strategy Search workspace to open the desired System Strategy.
If you are viewing the Unit Strategy Search page, use the Unit Strategy
Search workspace to open the desired Unit Strategy.
Linking an Asset Strategy Record to an

Equipment or Functional Location
Record
The following instructions provide details on linking an Asset Strategy record to an
Equipment or Functional Location record. When you do so, if the Equipment or
Functional Location record is already linked to Risk Assessment records from the Asset
Criticality Analysis (ACA) module, those risk ranks will be used in ASM as the
unmitigated risk assessment by default.
To link an Asset Strategy record to an Equipment or Functional Location record:

1. On the Asset Strategy Definition page, click the Asset tab.
2. In the Asset Name text box, click the
button.
The Find Items window appears.

3. In the Search In list, select the family of the record to which you want to link the
Asset Strategy record: Equipment or Functional Location.
4. If desired, in the Look For text box, type a keyword to limit your results to
records containing that word within the Record ID. If you specify a keyword,
your results will contain records that match your family criteria and contain the
keyword that you specified. A keyword can contain any number of characters, any
alphanumeric value, and any special character.
5. Click the Find Now button.
Meridium APM performs the search, and the results appear in the search results section
of the window.
6. Select the row containing the Equipment or Functional Location record to which
you want to link the Asset Strategy record, and click the Open button.
The Asset Strategy Definition page returns to focus, and the Asset Name text box and
Asset Type text box are populated with values stored in the associated Equipment or
If you linked the Asset Strategy record to an Equipment record:
The Asset Name text box is populated automatically with the value stored in the
Equipment Technical Number field in the Equipment record.
Note: If the Equipment Technical Number field is empty in the associated Equipment
record, the Asset Name text box will be populated instead with the Record ID of the
selected record.
The Asset Type text box is populated automatically with the value stored in the
Taxonomy Type Description field in the Equipment record.
If you linked the Asset Strategy record to a Functional Location record:
The Asset Name text box is populated automatically with the value stored in the
Functional Location field in the Functional Location record.
Note: If the Functional Location field is empty in the associated Functional Location
record, the Asset Name text box will be populated instead with the Record ID of the
selected record.
The Asset Type text box is populated automatically with the value stored in the
Taxonomy Type Description field in the Functional Location record.
In addition, if the Equipment or Functional Location record is linked to a Site Reference

record, the Site Reference text box is populated with the name of that Site Reference
record.
button.
The Asset Strategy record is saved and linked to the selected Equipment or Functional
Location record.
Creating Risks from Scratch

To create a Risk from scratch:
1. Search for and open the Asset Strategy to which you want to add a Risk.
3. In the Risks section, click the Add Risk button.
The Create Risk Wizard appears, displaying the Risk Datasheet screen.
4. On the Main tab:

a. In the Name text box, type a name for the risk.
b. In the Description text box, type a description of the risk.
Note that the Risk ID, Risk Rank, and Financial Risk fields are disabled.
1.
o
The Risk ID is set automatically to <Asset Strategy ID> -R00n, where

<Asset Strategy ID> is the ID of the Asset Strategy, and n is a three-digit
numeric value indicating the number of Risks that are already included in
the Asset Strategy.
Note that if you are creating Risk 1 through 9, the three-digit number begins with 00. For
example, if you are adding the first Risk to Pump 101 Asset Strategy, the Risk ID would
be Pump 101 Asset Strategy-R001.
If you are creating Risk 10 through 99, the three-digit number begins with 0. For
example, if you are adding the 15th Risk to Pump 101 Asset Strategy, the Risk ID would
be Pump 101 Asset Strategy-R015.
1.
o
After you save the Risk, in the Risk record, the Risk Rank and Financial
Risk fields will be populated automatically based upon the information
that you supply on the Risk Assessment interface using the remaining
steps.
5. Click the Detail tab, and complete the fields as desired.

The Risks Definition screen appears, displaying the Risk Matrix feature of the Risk
Assessment interface. Note that if the Asset Strategy record is linked to an Equipment or
Functional Location record that is linked to a Site Reference record that is also linked to a
Risk Matrix record, the Risk Matrix that you see is generated using that Risk Matrix
record (and the records to which it is linked).
7. Select the desired values on the Risk Matrix.
Note: If any tab represents a risk category that does not apply to the risk that you are
assessing, you can select the Not Applicable check box on that tab. When you do so, the
tab will be disabled, and the tab label will be updated to contain the text N/A.
8. If you want to link the Risk record to a Reference Document record, on the
datasheet toolbar, click the button, and use the Reference Documents window
to select the desired file.
9. When you are finished making selections, click the Finish button.
The Risk appears in the Risks section.
Creating Risks by Copying Existing

Risks
To create a Risk by copying an existing Risk:
1. Search for and open the Asset Strategy that includes the Risk that you want to use
to create a new Risk.
3. In the Risks section, select the row containing the Risk that you want to use to
create a new Risk.
4. Click the Copy Risk button.
A new Risk appears in the grid with the Name Copy of <Risk Name> n, where <Risk
Name> is the value in the Name field in the source Risk record and n is a numeric value
indicating the order in which the copy was created, relative to other copies of the same
source Risk record. The new Risk contains the same values as the source Risk.
Deleting Risks
If desired, you can remove a Risk from an Asset Strategy after its state has been set to
Active. Removing a Risk deletes the Risk record from the database. Keep in mind that
you can remove multiple Risks at one time.
Note: If you delete a Risk, you will still be able to view a history of changes that were
made to that Risk before it was removed. These changes are stored in Risk Revision
records, which are created automatically when the Asset Strategy state is set to Active.
While removing a Risk from an Asset Strategy will delete the Risk record, the Risk
Revision records will not be deleted.
Note that to completely delete a Risk, the Risk must be flagged for removal, and the
Asset Strategy must be set to Active. The following instructions explain how to flag the
Risk for removal and set the Asset Strategy to Active. In a realistic scenario, the same
Security User will probably not perform both of these tasks. These tasks are presented
together in the following instructions to provide a view of the entire process of deleting a
Risk.
To delete a Risk:
1. Search for and open an Active Strategy whose Risk you want to delete.
3. In the grid in the Risks section, select the row containing the Risk that you want
to delete.
4. Click the Remove Risk button.
In the grid in the Risks section, in the row containing the selected Risk, the icon in the
Flag column changes to . In addition, the Asset Strategy state changes to Modified.
5. Above the Risks section, click the Operations link, and then click Propose on the
submenu that appears.
6. As a Security User with permissions to set an Asset Strategy to Active, above the
Risks section, click the Operations link, and then click Make Active.
A message appears, asking if you are sure you want to make the proposed changes active.
7. Click the Yes button.
A message appears, indicating that the proposed changes are now active.
8. Click OK.
The Asset Strategy state changes to Active, the Risk is removed from the grid, and the
Risk record is deleted from the database.
Undoing a Change to a Risk

If desired, you can reverse changes that you made to a Risk.
If the Asset Strategy record has never been set to Active, selecting to undo
changes to the Risk will delete the Risk.
If the Asset Strategy record has been set to Active, selecting to undo changes to
the Risk will reverse all changes that you have made to the Risk since the last
Asset Strategy activation date.
Note that if you have modified an Action record in any way and you have not yet
activated the Asset Strategy, undoing a Risk will also undo the changes to the associated
Action.
You can undo changes to a Risk only if the Asset Strategy state is Draft or Modified.
Keep in mind that you can select multiple Risks to undo the changes that you made to the
records.
To undo a change to a Risk:
1. In the Risks section, click the Undo Risk button.
A message appears, asking if you are sure you want to revert the Risk back to its original
version (the version that existed before you made any changes).
Any changes that you made the Risk are reversed.
Modifying a Risk's Unmitigated Risk

Rank
To modify the unmitigated risk rank of a Risk:
1. Search for and open an Asset Strategy containing the Risk whose unmitigated risk
rank you want to modify.

3. In the grid in the Risks section, in the Unmitigated Risk Rank cell in the row
containing the Risk with the unmitigated risk rank that you want to modify, click
the hyperlink.
The Unmitigated Risk Assessment window appears, displaying the Risk Matrix feature of
the Risk Assessment interface. Note that:
4.
The Risk Of cell is populated with the value in the Name cell on the Risk
datasheet.
If the Asset Strategy record is linked to an Equipment or Functional

Location record that is linked to a Site Reference record that is also linked
to a Risk Matrix record, the Risk Matrix that you see is generated using
that Risk Matrix record (and the records to which it is linked).

5. When you are finished making selections, click the Save button.
The updated unmitigated risk rank appears in the grid in the Risks section.
Associating a New Action with a Risk

To associate a new Action with a Risk:
1. Search for and open the Asset Strategy that contains a Risk that you want to
associate with a new Action (an Action that does not exist yet).

3. In the Mitigating Actions section, click the Assign New Action button.
The New Action window appears, displaying the Action datasheet of a new Action
record.
4. Complete the fields as desired, and click OK.
The new Action appears in the grid in the Mitigating Actions section.
Associating Existing Actions with a Risk

To associate existing Actions with a Risk:
1. Search for and open the Asset Strategy that contains a Risk record that you want
to associate with existing Action.
3. In the Mitigating Actions section, click the Assign Existing Actions button.
The Assign Actions window appears. The Risk Name cell is populated with the name of
the associated Risk.
4. In the Actions section, in the rows containing the Actions that you want to
associate with the Risk that is specified in the Risk Name cell, select the Selected
check box.
5. Click OK.
The selected Actions appear in the grid in the Mitigating Actions section.
Modifying an Action's Mitigated Risk

Rank
When you associate an Action with a Risk, the mitigated risk rank of that Action is set by
default to the unmitigated risk rank of the associated Risk. To indicate the risk that the
asset failure would present if you were to perform the mitigating action on the piece of
equipment or location, you will need to modify the mitigated risk rank.
To modify the mitigated risk rank for an Action that is associated with a Risk:
1. Search for and open an Asset Strategy that contains an Action record whose
unmitigated risk rank you want to modify.
3. In the grid in the Mitigating Actions section, in the Action Mitigated Risk Rank
cell in the row containing the Action with the mitigated risk rank that you want to
modify, click the hyperlink.
The Risk Mitigation Assessment window appears, displaying the Risk Matrix feature of
4.
The Risk Of cell is populated with the value in the Name cell on the
associated Risk datasheet.
The Mitigated By cell contains the value in the Name field in the Action
record.

Note: The Not Applicable check box is disabled when you are assessing the mitigated
risk of an Action. The Not Applicable check box selection will be inherited from the
associated Risk record's risk assessment.
The updated mitigated risk rank appears in the grid in the Mitigating Actions section.
Creating Actions from Scratch

To create an Action from scratch:
1. Search for and open the Asset Strategy to which you want to add an Action.
3. In the Proposed Strategy section, click the Add Action button.
The New Action window appears, displaying the Action datasheet.

Note that the Action ID is set automatically to <Asset Strategy ID> -An, where <Asset
Strategy ID> is the ID of the Asset Strategy, and n is a two-digit numeric value indicating
the number of Actions that are already included in the Asset Strategy.
Note that if you are creating Action 1 through 9, the two-digit number begins with 0. For
example, if you are adding the first Action to Pump 101 Asset Strategy, the Action ID
would be Pump 101 Asset Strategy-A01. If, however, you are adding the tenth Action, the
Action ID would be Pump 101 Asset Strategy-A10.
5. If this Action represents an action that you want to perform only once instead of
on a recurring basis, select the Nonrecurring check box. The Annual Cost graph
and the Cost Projection graphs will include or exclude the Action based on the
recurrence pattern.
Note: The values in the Performance Interval field and the Performance Interval Units
field are not used in any calculations in ASM. You can use them as reference values, but
Meridium APM does not execute any logic based on the values. All calculations that
require an interval are based on the values in the Interval field and the Interval Units
field.
6. If this Action represents an action that is required, select the Mandatory check
box. Doing so will disable all remaining fields except for the Cost field and the
Mandatory field itself. This means that you can change the mandatory status at
any time by clearing the Mandatory check box, which will re-enable the
remaining fields.
7. If you want to designate the type of work that this action represents, in the
Implementation Role list, select the desired Implementation Role. The list
displays the Role Name of all Implementation Role records that exist in the
database. Note that if you select an Implementation Role, only Security Users that
are assigned to that Implementation Role will be able to create work item records
from the corresponding Action Revision record in ASI.
8. If you want to link the Action record to a Reference Document record, on the
datasheet toolbar, click the button, and use the Reference Documents window
to select the desired file.
9. When you are finished completing the fields, click OK.
The Action appears in the grid in the Proposed Strategy section.
Creating Actions by Copying Existing

Actions
To create an Action by copying an existing Action:
1. Access the Asset Strategy Actions page for the Asset Strategy containing the
Action that you want to use to create a new Action.
2. In the Proposed Strategy grid, select the row containing the Action that you want
to use to create a new Action.
3. Click the Copy Action button.

A new Action appears in the grid with the Name Copy of <Action Name> n, where
<Action Name> is the value in the Name field in the source Action record, and n is a
numeric value indicating the order in which the copy was created, relative to other copies
of the same source Action record. The new Action contains the same values as the source
Action, with the exception of the following fields:
Action ID
Global ID
Max Unmitigated Risk
ROI
Relevance
Status
Creating Actions from Recommendation

Records
These instructions assume that both of the following conditions have been met:
Your database contains an Asset Strategy record that is linked to an Equipment or

The Recommendation record that you want to use for creating an Action is linked
to the same Equipment or Functional Location record.
To create an Action from an existing Recommendation record:

1. Using Recommendation Management:
a. Create or find the Recommendation record that you want to use for
creating an Action.
b. Promote the Recommendation to an Action.
2. The Manage Recommendations to Action Links - <Strategy ID> page appears,

where <Strategy ID> is the ID of the Asset Strategy record that is linked to the
Equipment or Functional Location record to which the Recommendation record is
linked.
3. In the Recommendation section, select the row containing the Recommendation
record that you want to use for creating an Action.
4. On the Recommendation Tasks menu, click the Create New Action link.
The Recommendation record is removed from the Recommendations section. A new
Action appears is in the Actions section, and the Name of the Action is the same as the
Recommendation ID of the Recommendation record. The state of the Recommendation
record also changes to Accepted by ASM.
Modifying Actions
Note: You cannot modify an Action if the Mandatory check box is selected.
To modify an Action:
1. Search for and open an Asset Strategy that contains the Action that you want to
modify.
3. In the grid in the Proposed Strategy section, click the hyperlinked name of the
Action that you want to modify.
The Modify Action - <Action Name> dialog box appears, where <Action Name> is the
name of the selected Action.
4. Modify the values as desired.
5. Click OK.
The changes are saved.
Deleting Actions
If desired, you can remove an Action from an Asset Strategy after its state has been set to
Active. Removing an Action from an Asset Strategy deletes the Action record from the
database. Keep in mind that you can delete multiple Actions at one time.
Note: If you delete an Action, you will still be able to view a history of changes that were
made to that Action before it was removed. These changes are stored in Action Revision
records, which are created automatically when the Asset Strategy state is set to Active.
While removing an Action from an Asset Strategy will delete the Action record, the
Action Revision records will not be deleted.
Note that to completely delete an Action, the Action must be flagged for removal, and the
Asset Strategy must be set to Active. The following instructions explain how to flag the
Action for removal and set the Asset Strategy to Active. In a realistic scenario, the same
Security User will probably not perform both of these tasks. These tasks are presented
together in the following instructions to provide a view of the entire process of deleting
an Action.
Note: You cannot delete an Action if the Mandatory check box is selected.
To delete an Action:
1. Search for and open an Active Strategy whose Action you want to delete.
3. In the grid in the Proposed Strategy section, select the row containing the Action
that you want to delete.
4. Click the Remove Action button.
In the grid in the Proposed Strategy section, in the row containing the selected Action, the
icon in the Flag column changes to . In addition, the Asset Strategy state changes to
Modified.
5. Above the Proposed Strategy section, click the Operations link, and then click
Propose on the submenu that appears.
6. As a Security User with permissions to set an Asset Strategy to Active, above the
Proposed Strategy section, click the Operations link, and then click Make Active.
A message appears, asking if you are sure you want to make the proposed changes active.
A message appears, indicating that the proposed changes are now active.
8. Click OK.
The Asset Strategy state changes to Active, the Action is removed from the grid, and the
Action record is deleted from the database.
Undoing a Change to an Action

If desired, you can reverse changes that you made to an Action.
If the Asset Strategy record has never been set to Active, selecting to undo
changes to the Action will delete the Action record.
If the Asset Strategy record has been set to Active, selecting to undo changes to
the Action will reverse all changes that you have made to the Action since the last
Asset Strategy activation date.
Note that you can undo changes to an Action only if the Asset Strategy state is Draft or
Modified. Keep in mind that you can select multiple Actions to undo the changes you
made to the records.
Note: You cannot undo a change to an Action if the Mandatory check box is selected.
To undo a change to an Action:
1. In the Proposed Strategy section, click the Undo Action button.
A message appears, asking if you are sure you want to revert the Action back to its
original version (the version that existed before you made any changes).

Any changes that you made the Action are reversed.
Modifying an Action's Mitigated Risk

Rank
When you associate a Risk with an Action, the mitigated risk rank of that Action is set by
default to the unmitigated risk rank of the associated Risk. To indicate the risk that the
asset failure would present if you were to perform the mitigating action on the piece of
equipment or location, you will need to modify the mitigated risk rank.
To modify the mitigated risk rank of an Action:
1. Search for and open an Asset Strategy that contains an Action record whose
mitigated risk rank you want to modify.
whose risk rank you want to modify.
4. In the grid in the Mitigated Risks section, select the row representing the Risk that
is mitigated by the Action that is selected in the Proposed Strategy section.
5. In the selected row in the Mitigated Risks section, in the Action Mitigated Risk
Rank cell, click the hyperlink.
The Risk Mitigation Assessment window appears, displaying the Risk Matrix feature of
6.
The Risk Of cell is populated with the value in the Name cell on the
associated Risk datasheet.
The Mitigated By cell contains the value in the Name field in the Action
record.


Note: The Not Applicable check box is disabled when you are assessing the mitigated
risk of an Action. The Not Applicable check box selection will be inherited from the
associated Risk record's risk assessment.
The mitigated risk rank appears in the grid in the Mitigated Risks section.
Associating a New Risk with an Action

To associate a new Risk with an Action:
1. Search for and open the Asset Strategy that contains an Action that you want to
associate with a new Risk (a Risk that does not exist yet).
3. Below the Mitigated Risks tab, click the Assign New Risk button.
The Create Risk Wizard appears, displaying the Risk datasheet of a new Risk record.
4. On the Main tab:
a. In the Name text box, type a name for the risk.
b. In the Description text box, type a description of the risk.
5. Click the Detail tab, and complete the fields as desired.

The Risks Definition screen appears, displaying the Risk Matrix feature of the Risk
Assessment interface.
8. When you are finished making selections, click the Finish button.
The new Risk appears in the grid on the Mitigated Risks tab.
Associating Existing Risks with an

Action
To associate existing Risks with an Action:
1. Search for and open the Asset Strategy that contains the Action that you want to
associate with existing Risk.
3. Below the Mitigated Risks tab, click the Assign Existing Risks button.
The Assign Risks window appears. The Action Name cell is populated with the name of
the associated Action.
4. In the Risks section, in the rows containing the Risks that you want to associate
with the Action that is specified in the Action Name cell, select the Selected check
box.
5. Click OK.
The selected Risks appear in the grid in the Mitigated Risks section.
Excluding Actions
When you are viewing the Risk Analysis for an Asset Strategy, you can see a list of
Actions that are included in the Proposed Strategy. You can also use the graphs to
interpret the effects of performing those actions.
If desired, via the Risk Analysis, you can exclude certain Actions from the Asset Strategy.
Using the graphs, you can see the impact of excluding those Actions. Based upon the data
in the graphs, you can decide if you want to mark the Actions for deletion.
You cannot, however, exclude Actions that were promoted to ASM from certain modules
(e.g., from an RCM Recommendation record). If you try to exclude an Action that was
created in a different module, a message will appear, indicating that you cannot exclude
that Action from the analysis.
Note: You can exclude an Action only if its Mandatory check box is cleared.
To exclude Actions via the Asset Strategy Risk Analysis:
1. On the Asset Strategy Risk Analysis page, in the grid in the Actions section, select
the row containing the Action that you want to exclude.
2. In the selected row, clear the Selected Action check box.
The graphs are updated to reflect the change.
3. If you are satisfied with the results in the graphs and you want to delete the
Action, below the Actions section, click the Apply Selections button.
Note: The Apply Selections button is enabled only if the strategy is Active.
A message appears, indicating that the Actions that you excluded will be deleted, asking
if you are sure that you want to continue.
If the Asset Strategy has not been activated since the selected Action was created or last
updated, the Action is removed from the grid, and the Action record is deleted from the
database.
-ORIf the Asset Strategy was activated after the Action was created or last updated, the
Actions are flagged for deletion but not removed from the grid.
Linking an Action Record to a New

Health Indicator Record
Note: You can link an Action record to a Health Indicator record only if the Asset
Strategy record is linked to an Equipment or Functional Location record.
To link an Action record to a new Health Indicator record:
1. Search for and open the Asset Strategy record that is linked to the Action record
that you want to link to a new Health Indicator record.
3. Click the Health Indicators tab.
record that you want to link to a new Health Indicator record.
5. Below the grid on the Health Indicators tab, click the Add Indicator button.
The Create New Health Indicator dialog box appears.
6. To create a Health Indicator record based on an existing source record (e.g.,
Measurement Location record), which will link the Health Indicator record to the
source record, accept the default selection.
-OR-
To create a Health Indicator record that is not based on an existing source record, select
the Create a Health Indicator without a data source option.
7. Click OK.
If you accepted the default selection, the Health Indicator Builder appears, displaying the
Welcome screen.
-ORIf you selected the Create a Health Indicator without a data source option, the (new
Health Indicator) window appears.
8. If the Health Indicator Builder appears, proceed through the builder, and click the
Finish button when you are ready.
-ORIf the (new Health Indicator) window appears:
1.
1. In the Name cell, type a name for the health indicator.
2. In the Description cell, type a description of the health indicator. If you
use the corresponding Action Revision record to build a Measurement
Location Group record in ASI, the description that you type will be used to
populate the Description field in the Measurement Location record that
will be created when you build the Measurement Location Group record.
3. In the ML Type list, select the type of the Measurement Location record
that you want to create from this Health Indicator record: Character or
Numeric. If you use the corresponding Action Revision record to build a
Measurement Location Group record in ASI, the description that you type
will be used to populate the ML Type field in the Measurement Location
record that will be created when you build the Measurement Location
Group record.
4. Click the Config tab.
5. If you selected Character in the ML Type list on the Main tab, in the
Allowable Values list, select the values that are appropriate for this type of
health indicator. If you use the corresponding Action Revision record to
build a Measurement Location Group record in ASI, the values that you
select will be used to populate the Allowable Values field in the
Measurement Location record that will be created when you build the
Measurement Location Group record.
Note: The Allowable Values list contains all values that exist in the Value field Operator
Rounds Allowable Values records whose Category field contains the value AHI Generic.
By default, Meridium APM provides a certain set of Operator Rounds Allowable Values
records with the value AHI Generic in the Category field. If other Operator Rounds
Allowable Values records have been created with this value, the value in their Value field
will also appear in this list.
1.
6. In the remaining fields on the Config tab, type or select the values that
represent alert conditions for this health indicator. If you use the
corresponding Action Revision record to build a Measurement Location
Group record in ASI, the values that you type will be used to populate the
fields on the limit fields (on the Limit Values tab of the Measurement
Location datasheet) in the Measurement Location record that will be
created when you build the Measurement Location Group record.
6. Click OK.
The new Health Indicator record is created and displayed in the grid on the Health
Indicators tab. The Health Indicator record is linked to the selected Action record, the
Asset Strategy record, and the Equipment or Functional Location record that is linked to
the Asset Strategy record.
Deleting a Health Indicator Record

To delete a Health Indicator record:
1. Search for and open the Asset Strategy record that is linked to the Action record
that is linked to the Health Indicator record that you want to delete.
record that is linked to the Health Indicator record that you want to delete.
5. Below the grid on the Health Indicators tab, select the row containing the Health
Indicator record.
6. Click the Delete Indicator button.
A message appears, asking if you are sure that you want to delete the Health Indicator
record.
The Health Indicator record is deleted and removed from the grid.
Viewing the Details of a Health

Indicator Record's Source Record
To view the details of a Health Indicator record's source record:
1. Search for and open the Asset Strategy record that is linked to the Health Indicator
record whose details you want to view.
4. In the row containing the Health Indicator record whose details you want to view,
click the hyperlink.
The Health Indicator Details window appears. This window displays the same
information that you would see on the Details tab if you were viewing the Asset Health
Manager page.
Note: If the Health Indicator record is based on a source for which no readings exist (e.g.,
the Health Indicator record is linked to a Measurement Location record that is not linked
to any Reading records), only the Source tab will be available on the Health Indicator
Details window. The Trend tab will not be available.
Viewing the Datasheet for a Health

Indicator Record Without a Source
Record
To view the datasheet for a Health Indicator record that is not linked to a source record:
1. Search for and open the Asset Strategy record that is linked to the Health Indicator
record whose datasheet you want to view.
4. In the row containing the Health Indicator record whose datasheet you want to
view, click the hyperlink.
The Modify Health Indicator - <Name> window appears, where <Name> is the name of
the Health Indicator record.
Viewing a List of Recommendation

Records that Were Used to Create an
Action
To view a list of the Recommendation records that were used to create an Action:
1. In the appropriate Asset Strategy, access the list of Actions that were created from
a Recommendation record.
2. In the grid in the Proposed Strategy section, in the row containing the Action
whose associated Recommendation record(s) you want to view, click the
hyperlink in the Number of Recommendations cell.
The Manage Recommendation to Action Links page appears. You can view the
Recommendation records that were used to create this Action in the Source
Recommendation for Selected Action section.
Accessing the Manage

Recommendations to Action Links Page
The Manage Recommendations to Action Links page lets you manage the links that exist
between Recommendation records and Action records.
You can access the Manage Recommendations to Action Links page when you...
View the list of Recommendation records that were used to create an Action.
Create an Action from an existing Recommendation record.
The following image shows the Manage Recommendations to Actions Links page.
Aspects of the Manage

Recommendation to Action Links Page
The Manage Recommendations to Action Links page contains the following sections:
Recommendations: Displays a list of Recommendation records that are linked to

the Equipment or Functional Location record that is associated with the Asset
Strategy from which you accessed the page. For example, if accessed the page
from the PMP-1001 Asset Strategy (assuming that the root Asset Strategy record
is linked to record PMP-1001), the Recommendations section will display a list of
Recommendation records that are linked to record PMP-1001.
Actions: Displays a list of Actions that are included in the Proposed Strategy from
which you accessed the page.
Source Recommendations for Selected Action: Displays a list of
Recommendation records that were used to create the Action that is selected in the
Actions section.
The Manage Recommendations to Action Links page also contains the following
task menus: Recommendation Tasks, Action Tasks, and Common Tasks.
From this page, you can:
Unlink an Action record from a Recommendation record.

Link a newly created Recommendation record to an existing Action record.
Create a new Action from an existing Recommendation record.
Indicate that a Recommendation drives an Action.
Recommendation Tasks Menu

The Recommendation Tasks menu on the Manage Recommendations to Action Links
page contains the following links:
Create New Action: Creates a new Action from the Recommendation record that
is selected in the Recommendations section. Note that if you select multiple
Recommendation records and click Create New Action, one new Action will be
created for each Recommendation record. This link is disabled if the strategy to
which the Action belongs is controlled by a Master Template. This link is disabled
if you are logged in as a member of the ASM Viewer Security Group.
Link to Action: Links the Recommendation record that is selected in the

Recommendations section to the Action record that is selected in the Actions
section. This link is disabled if the strategy to which the Action belongs is
controlled by a Master Template. This link is disabled if you are logged in as a
Show All: Refreshes the list of Recommendation records to display all

Recommendation records that are linked to the Equipment or Functional Location
record. You might want to use this link to be sure that you are seeing any
Recommendation records that were recently written.
Action Tasks
The Action Tasks menu on the Manage Recommendations to Action Links page contains
the following link:
Unlink Recommendations: Unlinks the Recommendation records that are selected

in the Source Recommendations for Selected Action section from the Action
record to which they are linked. Note that this link is disabled if...
No Recommendation records are displayed in the Source

Recommendations for Selected Action section.
The strategy to which the Action belongs is controlled by a Master

Template.
The selected Recommendation record is a driving Recommendation

record.
Common Tasks
The Common Tasks menu on the Manage Recommendations to Action Links page
contains the following links:
Page.
Help: Displays the help topic for the current page.
Unlinking an Action Record from a

Recommendation Record
When a Recommendation is promoted to an Action, the Recommendation record is
linked to the Action record. If desired, you can unlink the two records.
To unlink an Action record from a Recommendation record:
1. In the appropriate Asset Strategy, access the list of Actions.
record that you want to unlink from a Recommendation record(s), click the
hyperlink in the # of Recommendations cell.
Recommendation records that are currently linked to this Action record in the Source
3. In the Source Recommendations for Selected Action section, select the row
containing the Recommendation record that you want to unlink from the Action
record.
4. On the Action Tasks menu, click the Unlink Recommendations link.
The Recommendation record is unlinked from the Action record, and the
Recommendation record appears in the Recommendations section on this page.
Linking a Newly Created

Recommendation Record to an Existing
Action Record
In some cases, after an Action is created from one or more Recommendation records,
additional Recommendation records may be created that you want to link to the Action
record.
To link a newly created Recommendation record to an existing Action record:
1. In the appropriate Asset Strategy, access the list of Actions.
record that you want to link to a new Recommendation record, click the hyperlink
in the # of Recommendations cell.
Recommendation records that are currently linked to this Action record in the Source
3. On the Recommendation Tasks menu, click the Show All link.
Any Recommendation records that are not currently linked to the Action record but that
are linked to the same Equipment or Functional Location record are displayed in the
Recommendations section.
4. In the grid in the Recommendations section, select the row containing the
Recommendation record that you want to link to the existing Action record.
5. On the Recommendation Tasks menu, click the Link to Action link.
The Recommendation record is removed from the Recommendations section and inserted
into the Source Recommendations for Selected Action section, and the Name of the
Action is the same as the Recommendation ID of the Recommendation record. The state
of the Recommendation record also changes to Accepted by ASM.
Creating a New Action from an Existing

Recommendation Record
To create a new Action from an existing Recommendation record:

1. Access the list of Recommendation records that are linked to an existing Action
record.
The Manage Recommendation to Action Links page appears.
2. In the Recommendations section, select the row containing the Recommendation
record that you want to use to create a new Action.
3. On the Recommendations Tasks menu, click the Create New Action link.
The new Action appears in the list in the Actions section, and the Recommendation
record appears in the Source Recommendations for Selected Action section.
Indicating that a Recommendation

Drives an Action
To indicate that a Recommendation record drives an Action:
1. On the Manage Recommendations to Action Links page:
Link a newly created Recommendation record to an existing Action

record.
-or2.
Create a new Action from an existing Recommendation record.
2. After the Recommendation record appears in the Source Recommendations for

Selected Action section, in that section, in the row containing the driving
Recommendation record, select the Drives Action check box.
A message appears, asking if you want to update the Action with information in the
Recommendation record any time that the mapped values in the Recommendation record
changes.
The Recommendation record is set as the driving Recommendation for the selected
Action.
Indicating that a Recommendation No

Longer Drives an Action
To indicate that a Recommendation record no longer drives an Action:
1. On the Manage Recommendations to Action Links page, in the Source
Recommendations for Selected Action section, select the row containing the
driving Recommendation record.
2. Clear the Drives Action check box.
An informational message appears, indicating that the Recommendation record can now
be deleted since it no longer drives the Action.
3. Click OK.
The Recommendation record is removed as the driving Recommendation record for the
selected Action.
Interpreting the Strategy Mitigated Risk

Rank
The Strategy Mitigated Risk Rank is the sum of the smallest risk rank values across all
risk categories (represented by tabs on the risk matrix) defined for all Actions that are
associated with the Risk.
The Strategy Mitigated Risk Rank appears in the following places:
Risks section of the Asset Strategy Risks page.
Mitigated Risks section of the Asset Strategy Actions page.
The Strategy Mitigated Risk Rank is calculated as:

Strategy Mitigated Risk Rank = MSR + MER + MOR + MFR
...where:
MSR = Minimum Safety Risk from All Mitigating Actions
MER = Minimum Environment Risk from All Mitigating Actions
MOR = Minimum Operations Risk from All Mitigating Actions
MFR = Minimum Financial Risk from All Mitigating Actions
To find the minimum risk for all actions, Meridium APM looks at the risk value for each
category and takes the minimum value across all Action.
For example, assuming that you are using the baseline risk matrix, suppose Action 1 and
Action 2 mitigate Risk A, and the risk values for these Actions are as shown in the
following table, where the minimum risk value for the two Actions is shown in bold.
Action Safety Risk Environmental Risk Operational Risk Financial Risk

Action 1 100
200
300
400
Action 2 150
250
90
120
Using this example, the Strategy Mitigated Risk Rank will be calculated as:
Strategy Mitigated Risk Rank = MSR + MER + MOR + MFR
Strategy Mitigated Risk Rank = 100 + 200 + 90 + 120
Strategy Mitigated Risk Rank = 510
Specifying the Reason for Changing the

Asset Strategy
If you modify an Asset Strategy, you can specify a reason for the modifications. This
provides the person responsible for reviewing the changes some insight into the rationale
behind the decisions.
To specify the reason for changing the Asset Strategy:
1. On the Asset Strategy Risk Analysis page, below the grid in the Actions section,
click the Basis for Revision button.
The Basis for Revision dialog box appears.
2. In the text area in the Basis for Revision dialog box, type the reason for the
changes that you have made to the Asset Strategy.
3. Click OK.
The text is saved. When a user reviews changes waiting for approval, the text that you
typed will be available to help them determine whether or not to activate the changes.
Proposing an Asset Strategy

After you have created a Draft Asset Strategy that includes Actions and Risks that you
think represent a valid and manageable plan for a piece of equipment or location, you will
need to propose the Asset Strategy, which will set it to a Pending Review state. A Security
User who is responsible for reviewing the Asset Strategy will then be able to accept it,
making it Active, or send it back for additional work.
Note that when an Asset Strategy is set to the Pending Review state, the Plan Length
field, which is visible on the Asset Strategy Definition page, is disabled.
To propose an Asset Strategy:
1. Search for and open the Asset Strategy that you want to propose. To propose an
Asset Strategy, it will need to be in a state of Draft or Modified.

Note: You can propose an Asset Strategy from other pages, such as the Asset Strategy
Actions page, but these instructions assume that want to review the risk analysis before
proposing the Asset Strategy.
3. Above the Actions section, click the Operations link, and then click Propose on
the submenu.
A message appears, asking if you are sure you want to propose the Asset Strategy.
The Asset Strategy state changes to Pending Review. When the Asset Strategy is in a
Pending Review state, you cannot modify an Action, Risk, or the Risk Rank associated
with an Action or a Risk.
About Reviewing Recent Changes

Awaiting Approval
You can review recent changes that have been made to an Asset Strategy to determine
whether or not you want to:
Approve the changes and activate the Asset Strategy.
-OR
Send the Asset Strategy back for revision.
You can perform this review process from the Review Asset Strategy page.
You can use this page to review the following items:
A detailed view of any changes that have been made between an Action that is
included in the Active Strategy and the corresponding Action that is included in
The reason that changes were made to the Asset Strategy.
If desired, you can also print the Asset Strategy Approval Report for this Asset Strategy
before approving the changes by activating the Asset Strategy or sending it back for
rework.
Viewing a List of Changes Made to an

Action
Note that you can view a list of changes that were made to an Action from the Review
Asset Strategy page or from the Asset Strategy Risk Analysis page.
This documentation assumes that you want to review the changes before you activate a
modified Asset Strategy, which we assume that you will do from the Review Asset
Strategy page.
To view a list of changes that were made to an Action:
1. On the Review Asset Strategy page, click the Details tab.
A grid appears, displaying a list of Actions that are included in the Proposed Strategy.
2. In the grid, select the row containing the Action whose changes you want to view.
3. Below the grid, click the Show Changes button.
Note: The Show Changes button is disabled if you select an Action that has been added or
deleted from the strategy and the changes have not yet been made active. In other words,
if you select an Action whose icon contains a gear symbol or a minus symbol, the Show
Changes button is disabled.
The Changes window appears, displaying a list of differences that exist between the
selected Action and the corresponding Action that is included in the Proposed Strategy.
Viewing the Basis for Revision

When a user makes a change to an Asset Strategy, they can specify a reason for the
change from the Asset Strategy Risk Analysis page. If a user made changes to an Asset
Strategy, specified the reason for the changes, and then proposed the Asset Strategy, you
can review the reason before you activate the Asset Strategy.
Note: If an Asset Strategy is part of a System Strategy or Unit Strategy, if it is modified at
either of those levels, the basis for revision can be entered from the risk analysis of the
System Strategy or Unit Strategy.
To review the basis for revision:
On the Review Asset Strategy page, click the Basis for Revision tab.
Text appears, indicating the reason that the Asset Strategy was last modified.
Undoing ALL Changes Made to An

Asset Strategy
If desired, you can undo ALL the changes that have been made to an Asset Strategy in the
Modified state since it was last activated. When you do so, the Meridium APM system
will:
Change the state from Modified to Active.
-AND
Revert ALL the changes that were made to the strategy since the last time it was
activated.
In other words, all your changes are discarded, and the Asset Strategy is restored to the
state in which it existed prior to making your changes.
The following instructions provide details on undoing all the changes that were made to
an Asset Strategy. These instructions assume that you are viewing a page in ASM where
the Operations menu is available and that the Asset Strategy is in the Modified state.
Note: The Cancel option is not available on the Operations menu when you are working
with an Asset Strategy that was created from an RBI Analysis.
To undo all the changes made to an Asset Strategy:
1. Click the Operations link.
A submenu appears, displaying the options Cancel and Propose.
2. Click Cancel.
The Meridium APM system reverts all the changes that were made to the Asset Strategy
since it was last activated, and the state of the Asset Strategy is changed to Active.
About Restoring Asset Strategy

Revisions to Use in the Current Asset
Strategy
If desired, you can restore a previous Asset Strategy Revision and use its contents in the
current Asset Strategy. For example, if you activate an Asset Strategy after removing
several Actions and Risks and adding different Actions and Risks but later you realize
that this was a mistake, you can restore the content of the previous Asset Strategy (before
you made your changes) and apply it to the current Asset Strategy. You can do so using
the Restore option that appears on the shortcut menu when you right-click an Asset
Strategy Revision in the Revisions pane on the Asset Strategy Revision History page.
Note: The Restore option is not available when you are working with an Asset Strategy
that was created from an RBI Analysis.
When you restore an Asset Strategy Revision, the Meridium APM system will:
Discard any changes that were made to the current Asset Strategy since it was last
activated.
Restore the values stored in the records that make up the current Asset Strategy
with those that exist in the same records that existed in the Asset Strategy
Revision. In other words, the records that exist in both the current Asset Strategy
and the Asset Strategy Revision will be restored using the values stored in the
Asset Strategy Revision records.
Restore the Action, Risk, and Risk Assessment records that existed in the desired
Asset Strategy Revision but do not exist in the current Asset Strategy. In other
words, records that are not part of the current Asset Strategy will be restored using
the values stored in the Asset Strategy Revision records.
Change the state of the Asset Strategy to Modified.
Additionally, when you try to restore an Asset Strategy Revision, the Meridium APM
system will prompt you to specify whether you want to remove or keep the Action, Risk,
and Risk Assessment records that exist in the current Asset Strategy but do not exist in
the Asset Strategy Revision. In other words, you can choose to keep the records that were
created after the selected Asset Strategy Revision was created or to remove them from the
current Asset Strategy. You cannot remove records from an Asset Strategy, however, if it
contains one or more of the following record types:
Mandatory Actions
Actions or Risks that originate from other modules
In this case, the option to remove records from the current Asset
Strategy will be disabled.
Like any other changes that you make to an Asset Strategy, after you restore an Asset
Strategy Revision and activate the Asset Strategy, a new Asset Strategy Revision will be
created for the Asset Strategy. When you restore an Asset Strategy Revision, you are not
removing any Asset Strategy Revisions that existed between the current Asset Strategy
and the restored Asset Strategy Revision.
The Meridium APM system prevents you from restoring an Asset Strategy Revision if
any of the following conditions are met:
The Asset Strategy is in the Pending Review state.

The Asset Strategy is currently a controlled strategy.
The user who is currently logged in does not have the necessary permissions to
change the current state of the Asset Strategy.
Consider another example in which you apply the wrong Asset Strategy Template to an
Asset Strategy as a master and then activate that Asset Strategy. In this case, you would
want to restore the Asset Strategy Revision that was created before the Asset Strategy
Template was applied to the Asset Strategy. Because the Asset Strategy is currently linked
to a Master Asset Strategy Template record, however, you will need to remove the link
between the controlled strategy and its master before you can restore the desired Asset
Strategy Revision.
Hint: If you make changes to the Asset Strategy by mistake and you
have not activated the Asset Strategy after making those changes, you
can use the Cancel operation to undo them.
Restoring Asset Strategy Revisions

The following instructions provide details on restoring an Asset Strategy Revision and
using it in the current Asset Strategy. These instructions assume that:
The Asset Strategy is in a state other than Pending Review.

The Asset Strategy is not currently a controlled strategy.
The user who is currently logged in has the necessary permissions to change the
current state of the Asset Strategy.
To restore an Asset Strategy Revision:

1. Access the Asset Strategy Revision History page for the Asset Strategy whose
Asset Strategy Revision you want to restore.
2. In the Revisions pane, right-click the Asset Strategy Revision that you want to
restore.
The shortcut menu appears and contains the option Restore.
3. Click the Restore link.
The Restore Revision Options dialog box appears, asking you to specify what the
Meridium APM system should do with the items that exist in the current Asset Strategy
but not in the selected Asset Strategy Revision.
You can choose from the following options:
4.
o
Mark these items for removal.
Note: Keep in mind that this option may be disabled if the Asset Strategy contains
mandatory Actions or Action or Risk records that were created in a different module and
promoted to ASM.
4.
o
Keep these items in the Asset Strategy.
5. Select the desired option.

6. Click OK.
The Meridium APM system:
Discards any changes that were made to the current Asset Strategy since it
was last activated.
Replaces the values stored in the records that make up the current Asset
Strategy with those that exist in the same records that existed in the
selected Asset Strategy Revision.
Restores Action, Risk, and Risk Assessment records that existed in the
selected Asset Strategy Revision but do not exist in the current Asset
Strategy.
Removes or keeps the items that exist in the current Asset Strategy but not
in the selected Asset Strategy Revision, based upon your selection on the
Restore Revision Options dialog box.
Changes the state of the Asset Strategy to Modified.
Activating an Asset Strategy

When you set an Asset Strategy state to Active, you indicate that you approve of the plan
and agree with the Actions and Risks. You can set the state to Active if it is currently
Draft or Pending Review.
Note that when an Asset Strategy is set to the Active state, the Plan Length field, which is
visible on the Asset Strategy Definition page, is disabled.
To set an Asset Strategy state to Active from the Draft state:

1. Search for and open the Asset Strategy that you want to activate.
Note: You can activate an Asset Strategy from other pages, such as the Asset Strategy
Actions page, but these instructions assume that want to do so from the Review Asset
Strategy page.
3. Above the area that displays the Basis for Revision tab, click the Operations link,
and then click Baseline on the submenu.
A message appears, asking if you are sure you want to activate the Asset Strategy even
though it has not yet been reviewed.
A message appears, indicating that the Asset Strategy is now Active. In the current
workspace, you can see that the Asset Strategy state is now Active.
To set an Asset Strategy state to Active from the Pending Review state:
1. Search for and open the Asset Strategy that you want to activate.
Strategy page.
and then click Make Active on the submenu.
A message appears, asking if you are sure you want to activate the Asset Strategy.

A message appears, indicating that the Asset Strategy state is now Active. In the current
workspace, you can see that the Asset Strategy state is now Active.
Send an Asset Strategy Back for Rework

If you are reviewing an Asset Strategy that is set to the Pending Approval state and you
do not approve of any part of it, you can send it back for rework.
To send an Asset Strategy back for rework:
1. Search for and open the Asset Strategy that you want to send back for rework.
Strategy page.
and then click Rework on the submenu.
A message appears, asking if you are sure you want to perform the operation.
The Basis for Rework dialog box appears.
5. In the Basis for Rework, type any comments explaining why the Asset Strategy
cannot be activated without additional work.
6. Click OK.
The Asset Strategy state is set to Modified. The comments that you typed in the Basis for
Rework dialog box will be available on the Review Strategy tab on the Review Asset
Strategy page. The next time that you are ready to review the Asset Strategy, you can use
these comments as a reminder about why the Asset Strategy was not ready to be activated
the last time.
Accessing the Revision History

To access the ASM - Asset Strategy Revision History - <Strategy ID> page:
1. Search for and open the Asset Strategy whose revision history you want to review.
2. On the Navigation menu, click the Revision History link.
Note: This link is enabled only if the Asset Strategy has been activated at least once.
The Asset Strategy Revision History page appears.
About the Revision History

The revision history for an Asset Strategy lets you view the Asset Strategy that was
initially created and all changes that have been made to the Asset Strategy since then.
From the Asset Strategy Revision History page, for the initial Asset Strategy and each
Asset Strategy revision, you can view the following information:
Information in the Strategy Revision record.

Information in each Action Revision record.
Information in each Risk Assessment Revision record.
Information in each Risk Revision record.
Overview of the Asset Strategy Revision

History Page
The Asset Strategy Revision History page is divided into the following panes:
Revisions: Displays a list of all revisions that have been made to the Asset
Strategy.
Selected Revision: Displays the details of the revision that is selected in the
Revisions pane.
Datasheet: Displays the datasheet associated with the record that is selected in the
Selected Revision pane.
Revisions Pane
The Revisions pane of the Asset Strategy Revision History page contains a list of all
Strategy Revision records that are linked to the Active Strategy record that is linked to the
currently displayed Asset Strategy record.
Each item in the list represents the Asset Strategy as it existed when its state was set to
Active.
Note: When an Asset Strategy record's state is set to Active, a Strategy Revision record is
created automatically and linked to the Active Strategy record that is linked to that Asset
Strategy record.
In the following image, the list in the Revisions pane contains two items.
The first item in the list contains a zero (0) in parentheses. This item represents the Asset
Strategy as it existed when it was activated for the first time. The date and time represents
the date and time that the Asset Strategy state was set to Active for the first time.
The second item in the list contains a one (1) in parentheses. This item represents the
Asset Strategy as it existed when it was activated for the second time. The date and time
represents the date and time that the Asset Strategy state was set to Active for the second
time.
Each subsequent item in the list contains a number in parentheses, which is one digit
higher than the number in the previous item in the list. For each item, you can see the
date and time that the Asset Strategy was set to Active.
You can select an item in the list and see the details of the associated Asset Strategy in the
Selected Revision pane.
The Revisions pane contains a shortcut menu that contains one option, Restore, which
lets you restore the selected Asset Strategy Revision and use it in the current Asset
Strategy.
To collapse the Revision pane, you can click the
Revision pane and the Selected Revision pane.
button that appears between the
Selected Revision Pane

The Selected Revision pane on the Asset Strategy Revision History page displays details
about the Asset Strategy that is associated with the item that is selected in the Revisions
pane.
The Selected Revision pane displays the Strategy Revision record at the root level of the
tree.
Note: When an Asset Strategy record's state is set to Active, a Strategy Revision record is
created automatically and linked to the Active Strategy record that is linked to that Asset
Strategy record.
Below the Strategy Revision record, you will see the Action Revision records and Risk
Revision records that are linked to the Strategy Revision record. The Action Revision
records are grouped under the Actions folder, and the Risk Revision records are grouped
under the Risks folder.
For example, in the following image, you can see that the Strategy Revision record is
linked to three Action Revision records and one Risk Revision record.
Below each Action Revision record, you can see the Risk Assessment Revision records to
which it is linked. This Risk Assessment Revision records appears below the Mitigates
folder.
For example, in the following image, you can see that the Action Revision record Replace
the dryer is linked to the Risk Assessment Revision record Dryer catches on fire ~ 90~
80.
Below each Risk Revision record, you can see the Risk Assessment Revision record to
which it is linked. The Risk Assessment Revision record appears below the Is Mitigated
folder.
For example, in the following image, you can see that the Risk Revision record Dryer
catches on fire ~ 5500~ 800 is linked to the Risk Assessment Revision record Dryer
catches on fire ~ 90~ 80.
An icon appears next to each Action Revision, Risk Revision, and Risk Assessment
Revision record. The icon indicates the action that you performed on that record. For a
Strategy Revision record with a zero (0) in the title, all icons will have a plus sign (e.g.,
). For any subsequent Strategy Revision record, any record that you modified will
have a gear symbol (e.g.,

(e.g.,
).
), and any record that you deleted will have an X symbol
Note that in some cases, the value in the Strategy Mitigated Risk Rank field changes but
the associated Risk record does not change. In this case, the Selected Revision pane will
display the associated Risk Revision record with the symbol.
The Selected Revisions pane contains a shortcut menu that contains one option, Show
Changes, which appears only if the selected item was modified (which you can identify
from the gear symbol). You can click the Show Changes link to see a list of the changes
that were made to that item.
To collapse the Selected Revision section, you can click the
between the Selected Revision pane and the datasheet pane.
button that appears
Datasheet Pane
The datasheet pane of the Asset Strategy Revision History page displays details about the
record that is selected in the Selected Revision pane.
Note: To view the full datasheet, you can collapse the Revisions pane and the Selected
Revisions pane by clicking the
button to the right of either pane.
Note that all fields on the datasheet are disabled.
Viewing a List of Changes that Were

Made to an Item in the Selected
Revision Section
To view a list of changes that were made to an item in the Selected Revision section:
1. Access the revision history for the Asset Strategy whose changes you want to
view.
2. In the tree in the Selected Revision section, right-click an item with gear icon
(e.g.,
).
A shortcut menu appears, containing the option Show Changes.

3. Click the Show Changes link.
The Changes window appears, displaying a list of changes that were made to the selected
item.
About the Risk Profile Graph

The Risk Profile graph is available on the following pages:

It is also available on the following pages:

The Risk Profile graph that is displayed on the Asset Strategy Overview page and the
Asset Strategy Template Overview page represents data in the Active Strategy only. The
Risk Profile graph that is displayed on the other pages, however, represents data in the
Active and the Proposed Strategy.
Interpreting the Risk Profile Graph in

the Overview
The Risk Profile graph that appears on the Asset Strategy Overview page represents data
in the Active Strategy only.
The following image shows an example of the Risk Profile graph in the Asset Strategy
overview.
The Risk Profile graph displays a profile of the risk rank values for each Risk included in
the Active Strategy. From the example graph in the preceding image, you can determine
from the eight datapoints on the Unmitigated line that the Active Strategy contains eight
Risks. By default, the graph contains a line that represents the unmitigated risk rank of
each Risk. The gray bars represent the Strategy Mitigated Risk Rank for each Risk in the
Active Strategy.
If desired, you can use the values in the Category list to filter the graph to display the risk
rank associated with a specific risk category (excluding Financial risk categories) for
each Risk. For example, consider the following graph, which shows the total unmitigated
risk, 153.3, for the Risk Lubricant Loss across all risk categories.
You would also see this value if you opened the Unmitigated Risk Assessment window
for this Risk.
In addition, you would see this value in the Unmitigated Risk Rank column in the Risks
section on the Asset Strategy Risks page.
If you filter the Risk Profile graph to display only risk values associated with the
Operations risk category, it would look like the graph shown in the following image.
In this image, you can see that the Operations risk of Lubricant Loss is 150. You could
also see this value if you opened the Unmitigated Risk Assessment window for this Risk,
as shown in the following image.
Note: If you filter the graph to show risk rank values for a specific risk category, the
graph will most likely be resorted from left to right. In other words, the Risks will appear
in different places on the x-axis after the filtering is applied.
If you right-click the line and the bars, you can choose to show the datapoint values on
the graph to determine the exact risk rank values. The following image shows the
example graph with labeled datapoint values.
From this graph, you can see that the unmitigated risk rank for the first Risk is 500, and
the Strategy Mitigated Risk Rank is 150.
Note: The callouts in the following graph have been added to the documentation to make
the graph easier to interpret. These callouts are not available in the graph in the ASM
product.
If you were to view the Asset Strategy Risks page, you would see these same values for
this Risk. The unmitigated risk rank is displayed in the Unmitigated Risk Rank column in
the grid in the Risks section. The Strategy Mitigated Risk Rank is displayed in the
Strategy Mitigated Risk Rank column in the same grid.
By default, the unmitigated risk rank values are plotted from highest to lowest on the
graph from left to right. In other words, the line always slopes down to the right in the
default view of the graph. If desired, you can sort the graph from left to right by the
Strategy Mitigated Risk Rank values. To do so, below the x-axis, select the Active option.

the Risk Analysis and on the Review
Page
The Risk Profile graph that appears on the Asset Strategy Risk Analysis page and the
Review Asset Strategy page represents data in the Active Strategy and in the Proposed
Strategy.
Note: The Risk Profile graph does not display Risk records that have been removed from
The following image shows an example of the Risk Profile graph in the Asset Strategy
risk analysis.
The Risk Profile graph displays:
The Strategy Mitigated Risk Rank value for each Risk that belongs to the Active
Strategy. These values are displayed on the line with the circles.
The projected, or proposed, Strategy Mitigated Risk Rank value for each Risk that
belongs to the Proposed Strategy. These values are displayed on the vertical bars.
As you make changes to the Asset Strategy, changing its state to Modified, those
changes are reflected in the bars on the graph.
The unmitigated risk rank value for each Risk that belongs to the Active Strategy.
These values are displayed on the line with the triangles.
From the example graph in the preceding image, you can determine from the eight
datapoints on each line that the Proposed Strategy contains eight Risks.
Note: If a Proposed Strategy contains more Risks than the corresponding Active Strategy,
the additional Risks are displayed on the Risk Profile Graph. For any additional Risk, the
unmitigated risk rank and the active risk rank will be the same until the strategy is
activated.
each Risk. For example, consider the following graph, which shows the total unmitigated
risk, 153.3, for the Risk Lubricant Loss across all risk categories.
You would also see this value if you opened the Unmitigated Risk Assessment window
for this Risk.
In addition, you would see this value in the Unmitigated Risk Rank column in the Risks
section on the Asset Strategy Risks page.
If you filtered the Risk Profile graph to display only risk values associated with the
Operations risk category, it would look like the graph shown in the following image.
In this image, you can see that the Operations risk of Lubricant Loss is 150. You would
also see this value if you opened the Unmitigated Risk Assessment window for this Risk,
Note: If you filter the graph to show risk rank values for a specific risk category, the
the graph to determine the exact risk rank values. The following image displays the
Note that in some cases, displaying the datapoint values might cause the values to
overlap, as shown in this image. If this happens, you can pause on a line or a bar to see
only the datapoint values on that line or bar.
From the example graph, you can see that:
The unmitigated risk rank for the last Risk is 60.

The current Strategy Mitigated Risk Rank for this Risk is 5.
The Asset Strategy has been modified in some way (e.g., an Action's Mitigated
Risk Rank has been reduced, an Action has been removed, etc.) The vertical bar
represents the projected Strategy Mitigated Risk Rank assuming that these
changes are accepted and that the Asset Strategy state becomes Active without the
changes being reversed. In this example, the projected, or proposed, Strategy
Mitigated Risk Rank is 30.
Note: The callouts in the following graph have been added to the documentation to make
the graph easier to interpret. These callouts are not available in the graph in the ASM
product.
If you were to view the Asset Strategy Risks page, you would see these values for this
Risk in the Unmitigated Risk Rank and Strategy Mitigated Risk Rank columns in the
Risks section.
In the preceding image, you can see that the unmitigated risk rank for the first Risk is
650, which is displayed on the Unmitigated line in the graph. You can also see that the
Strategy Mitigated Risk Rank is 50.5, which is displayed on the Proposed bar on the
graph.
If you were to view the Risks section on the Asset Strategy Risks page, you would see the
icon in the Flag column. From this icon, you can determine that the Risk has been
modified.
Note that if you do not want to view all Risk Rank values on the graph, you can filter the
graph to display any combination of values, such as unmitigated risk rank values only or
active Strategy Mitigated Risk Rank values only.
graph from left to right. In other words, the Unmitigated line always slopes down to the
right in the default view of the graph. If desired, you can sort the graph from left to right
by the proposed Strategy Mitigated Risk Rank values or the active Strategy Mitigated
Risk Rank values. To do so, below the x-axis, select the desired option.
About the Financial Risk Graph

The Financial Risk Exposure graph is available on the following pages:


The Financial Risk Exposure graph that is displayed on the Asset Strategy Overview
page and the Asset Strategy Template Overview page represents data in the Active
Strategy. The Financial Risk Exposure graph that is displayed on the other pages,
however, represents data in the Active and Proposed Strategy.
Interpreting the Financial Risk

Exposure Graph in the Overview
The Financial Risk Exposure graph that appears on the Asset Strategy Overview page
represents data in the Active Strategy.
The following image shows an example of the Financial Risk Exposure graph in the
Asset Strategy overview.
The Financial Risk Exposure graph displays the financial risk rank associated with each
Risk that is included in the Active Strategy. For each Risk, you can see the unmitigated
financial risk rank and the mitigated financial risk rank, which is based on all Actions that
are currently included in the Active Strategy.
The graph contains two bars: Unmitigated and Active. Each bar is divided into multiple
sections, where each section represents a Risk that is included in the Active Strategy.
From the legend, you can determine which Risk is associated with which color.
In this example, because each bar contains eight sections, you can determine that the
Active Strategy record contains eight Risks.
Within each bar, each section represents the financial risk associated with that Risk.
Unmitigated Bar
The Unmitigated bar displays the unmitigated financial risk rank associated with each
Risk. You can also view the unmitigated financial risk rank value for a Risk by using the
Risks section of the Asset Strategy Risks page to access the Unmitigated Risk
Assessment window for that Risk. The financial risk rank is displayed on the Financial
tab.
For example, in the following image, you can see that the unmitigated financial risk for
the Risk Bearing Failure is $150,000.
If you were to access the Unmitigated Risk Assessment window for this Risk, you would
see that the value on the Financial tab is also 150,000.
Active Bar
The Active bar in the Financial Risk Exposure graph displays the mitigated financial risk
rank for each Risk. The mitigated financial risk rank value for a Risk equals the lowest
financial risk rank for all Actions that are associated with the Risk.
For example, in the following image, you can see that the active mitigated financial risk
rank for the Risk Bearing Failure is $25,000.
If you were to view all of the Action records that are associated with this Risk, you would
see that the lowest unmitigated financial risk rank for all of the Actions is also 100.

Exposure Graph in the Risk Analysis
and on the Review Page
The Financial Risk Exposure graph that appears on the Asset Strategy Risk Analysis page
and the Review Asset Strategy page represents data in the Active Strategy and the
Proposed Strategy.
Note: The Financial Risk Exposure graph does not display Risk records that have been
removed from the Proposed Strategy.
Asset Strategy risk analysis.
The Financial Risk Exposure graph displays:
The unmitigated financial risk rank for each Risk that belongs to the Active
Strategy. These values are displayed on the Unmitigated bar.
The mitigated financial risk rank for each Risk that belongs to the Active Strategy.
These values are displayed on the Active bar.
The projected, or proposed, mitigated financial risk rank for each Risk assuming
that one or more changes are made to the Asset Strategy. These values are
displayed on the Proposed bar. As you make changes to the Asset Strategy,
changing the state to Modified, those changes are reflected in the Proposed bar.
Each bar is divided into multiple sections, where each section represents a Risk that
belongs to the strategy (either the Active Strategy or the Proposed Strategy, depending on
the bar you are viewing). From the legend, you can determine which Risk is associated
with which color.
In this example, because the Active bar contains eight sections, you can determine that
the Active Strategy contains eight Risks .
Note: If a Proposed Strategy contains more Risks than the corresponding Active Strategy,
the additional Risks are represented on the Financial Risk Exposure Graph. For any
additional Risk, the Unmitigated value and the Active value will be the same until the
strategy is activated.
Within each bar, each section represents the financial risk rank associated with that Risk.
Unmitigated Bar
The Unmitigated bar displays the unmitigated financial risk rank associated with each
Risk. You can also view the unmitigated financial risk rank value for a Risk by using the
Risks section of the Asset Strategy Risks page to access the Unmitigated Risk
Assessment window for that Risk. The financial risk rank is displayed on the Financial
tab.
For example, in the following image, you can see that the unmitigated financial risk rank
for the Risk Bearing Failure is $150,000.
If you were to access the Unmitigated Risk Assessment window for this Risk, you would
see that the value on the Financial tab is also $150,000.
Active Bar
The Active bar in the Financial Risk Exposure graph displays the mitigated financial risk
rank for each Risk. The mitigated financial risk rank value for a Risk equals the lowest
financial risk rank from all Actions (included in the Active Asset Strategy) that are
associated with the Risk.
For example, in the following image, you can see that the mitigated financial risk rank for
the Risk Bearing Failure is $25,000.
Because the example Asset Strategy is currently in a Modified state, the active financial
risk rank is not displayed anywhere else besides the graph.
Proposed Bar
The Proposed bar displays the projected, or proposed, mitigated financial risk rank for
each Risk, assuming that one or more changes are made to the Asset Strategy. As you
make changes to the Asset Strategy, changing the state to Modified, those changes are
reflected in the Proposed bar.
For example, in the following image, the proposed mitigated financial risk rank for the
Risk Bearing Failure is $15,000.
If you were to view this Risk in the grid on the Asset Strategy Risks page, you could see
from the Action Mitigated Financial Risk column in the Mitigating Actions section that
the lowest mitigated financial risk rank across all Actions that are associated with this
Risk is 15,000.
About the Cost of Actions Graph
The Cost of Actions graph is available on the following pages:


The Cost of Actions graph that is displayed on the Asset Strategy Overview page and
Cost of Actions graph that is displayed on the other pages, however, represents data in the
Active and Proposed Strategy.
Keep in mind that if a Strategy is included in an ASO Analysis, the Cost of Actions graph
will display data from the simulation.
Interpreting the Cost of Actions Graph

in the Overview
The Cost of Actions graph that appears on the Asset Strategy Overview page represents
data in the Active Strategy only.
The following image shows an example of the Cost of Actions graph in the Asset
Strategy overview.
The Cost of Actions graph displays the cost per year associated with each Action in the
Active Strategy.
Hint: The cost displayed on the graph is not the Cost value that appears by default in the
grid in the Actions section. The Cost value on the graph actually represents the Annual
Cost for each Action, which is calculated using the Cost, the Interval, and the Interval
Units for each Action. For example, if the Cost is $50.00, the Interval is 6, and the
Interval Units is Months, the Annual Cost will be $100.00 (the Action is performed every
six months, or twice a year, and 50 multiplied by two is 100). You can see the Annual
Cost for each Action by adding it to the grid in the Actions section using the Show
Available Fields option.
By default, the graph contains one bar, Active, which is divided into the following
sections:
PM: Represents the total cost per year for Actions with the Action Type TimeBased Maintenance (Preventive) (PM).
CM: Represents the total cost per year for Actions with the Action Type
Hint: If you view the Action datasheet for any Action record, you can see these options in
the Action Type field.
From the legend, you can determine which action type is associated with which color.
In this example, you can see that the total cost per year for CM Actions that are included
in the Active Asset Strategy is $2,033.00.
If desired, you can modify the graph to display the total cost per year for ALL Actions
that are included in the Active Strategy, regardless of the Action Type. To do so, below
the x-axis, select the Total option. In addition, you can modify the graph to display the
cost per year for each Action that is included in the Active Strategy. To do so, below the
x-axis, select the Each Action option.
Note: If you select the Each Action option and the Asset Strategy contains more than
twelve Actions, the legend will be hidden.

in the Risk Analysis and on the Review
Page
The Cost of Actions graph that appears on the Asset Strategy Risk Analysis page and the
Review Asset Strategy page represents data in the Active Strategy and in the Proposed
Strategy.
The following image shows an example of the Cost of Actions graph in the Asset
Strategy risk analysis.
The Cost of Actions graph displays the cost per year associated with each Action in the
Active Strategy and the Proposed Strategy.
By default, the graph contains two bars: Active and Proposed. Each bar is divided into the
following sections:
PM: Represents the total cost per year for Actions whose Action Type is TimeBased Maintenance (Preventive) (PM).
CM: Represents the total cost per year for Actions whose Action Type is
the Action Type cell.
In this example, you can see that the total cost per year for PM Actions that are included
in the Active Strategy is $4,870.00.
As you make changes to the Asset Strategy, causing its state to change to Modified, any
changes that you make to an Action's cost will be reflected in the Proposed bar.
If desired, you can modify the graph to display the total cost per year for ALL Actions
that are included in the Active Strategy and the Propose Strategy, regardless of the Action
Type. To do so, below the x-axis, select the Total option. In addition, you can modify the
graph to display the cost per year for each Action that is included in the Active Strategy
and the Proposed Strategy. To do so, below the x-axis, select the Each Action option.
About the Cost Projection Graph

The Cost Projection graph is available on the following pages:


The Cost Projection graph that is displayed on the Asset Strategy Overview page and
Cost Projection graph that is displayed on the other pages, however, represents data in the
Active and Proposed Strategy.
Keep in mind that if a Strategy is included in an ASO Analysis, the Cost Projection graph
will display data from the simulation.
Interpreting the Cost Projection Graph

in the Overview
The Cost Projection graph that appears on the Asset Strategy Overview page represents
data in the Active Strategy only.
The number of bars on the graph mimics the value in the Plan Length field on the Asset
Strategy datasheet. For example, if the Plan Length is five years, the graph will contain
five bars.
The following image shows an example of the Cost Projection graph in the Asset Strategy
overview.
You can use the Total, Action Type, and Each Action options to show the yearly cost of
all Actions, the yearly cost of Actions by Action type, or the yearly cost of Actions by
specific Action.
From the legend, you can determine which action type or Action is associated with which
color.
twelve Active Actions, the legend will be hidden.
The costs displayed on the graph are determined from the Cost value and the recurrence
pattern of each Action, which is indicated with the Nonrecurring check box on the Action
datasheet.
For example, if an Action that costs $100.00 is recurring, the Action will cost $100.00
every year for the length of the plan (determined from the Plan Length field on the Asset
Strategy datasheet). Regardless of the plan length, the cost will be incurred every year.
Likewise, if an Action that costs $200.00 is nonrecurring and is set to occur in three years
(the Interval on the Action datasheet is 3 and the Interval Units is Years), the Action will
cost $200.00 three years from today. If the plan length is five years, that $200.00 will not
be incurred again during the plan.
Note the following:
All Actions with yearly intervals will be displayed in the first year of the graph.
If an Action occurs in increments of less than a year (e.g., monthly), that Action
will be represented in the first year of the graph.
If an Action contains no interval, and interval of 0 (zero), or no interval unit, all

the cost for that Action will be represented in the first year in the plan.

in the Risk Analysis and on the Review
Page
The Cost Projection graph that displays the cost per year associated with each Action in
the Asset Strategy. The number of bars on the graph mimics the value in the Plan Length
field on the Asset Strategy datasheet. For example, if the Plan Length is five years, the
graph will contain five bars.
The Cost Projection graph represents data in the Active Strategy and in the Proposed
Strategy.
The following image shows an example of the Cost Projection graph.
You can display the cost of Actions for the Proposed Strategy or for the Active Strategy
by selecting the appropriate option below the graph: Show Proposed or Show Active.
In addition, you can use the Total, Action Type, and Each Action options to show the
yearly cost of all Actions, the yearly cost of Actions by Action type, or the yearly cost of
Actions by specific Action.
From the legend, you can determine which action type or Action is associated with which
color.
twelve Actions, the legend will be hidden.
datasheet.
every year for the length of the plan (determined from the Plan Length field on the Asset
Strategy datasheet). Regardless of the plan length, the cost will be incurred every year.
cost $200.00 three years from today (the fourth year of the plan). If the plan length is five
years, that $200.00 will not be incurred again during the plan.
Note the following:
All Actions with yearly intervals will be displayed in the first year of the graph.
If an Action occurs in increments of less than a year (e.g., monthly), that Action
will be represented in the first year of the graph.
If an Action contains no interval, and interval of 0 (zero), or no interval unit, all

the cost for that Action will be represented in the first year in the plan.
Example of the Cost Projection Graph

in the Risk Analysis
Consider the following image.
In this image, year 1 of the plan shows a cost of $405.00. This cost is incurred each year
because the recurring Actions cost a total of $405.00. In other words, these Actions will
cost the company $405.00 every year for the length of the plan.
The second year shows a cost of $6,935.00. This cost is a combination of the yearly
recurring Action costs and the cost for Actions that occur every two years.
About Updating Asset Strategies from

Task Records
If desired, you can update an Asset Strategy from existing Task records if the Task
records are linked to the same Equipment or Functional Location record that is linked to
the Asset Strategy record. When you do so, Meridium APM will:
Create multiple Actions, which belong to the Proposed Strategy. Each Action
represents a separate Task record.
Update the Implementation Package record that is linked to the Asset Strategy.
Before you can update an Asset Strategy from Task records, several conditions must be
met.
Conditions Required to Update Asset

Strategies from Task Records
Before you can update an Asset Strategy from Task records, the following conditions
must be met:
The Task records must be linked to Equipment or Functional Location records.

The Related Record ID field in the Task records must contain the Record ID of
the Equipment or Functional Location record that is linked to the Task record.

Definition record that represents the Task records that will be used to create the
Asset Strategy, the Allow Link Existing check box must be selected. For example,
if you want to create an Asset Strategy from Inspection Task records, the Allow
Link Existing check box in the Inspection Task Work Management Item
Definition record must be selected.
If the Task records are linked to Functional Location records, the Locate Assets
for Import query must be configured to return records in the Functional Location
family.

are Updated from Task Records?
After you update an Asset Strategy from an existing Task record:
If the Asset Strategy was in the Active state, it will remain in the Active state.
If the Asset Strategy was in the Pending Review state, it will remain in the
Pending Review state.
source Task record using the rules referenced in the Action Mapping record to
which that Task record is linked. The new Action will be represented by the
icon.
Note: If the Rejectable check box is selected in the Task record, the Mandatory check box
will be cleared in the Action.
No new Risks are created. You will need to assign Risks to each new Action
manually.
If the Asset Strategy record is already linked to an Implementation Package
record, the Implementation Package record will remain in its current state. In
addition, the Implementation Package record will be linked to the work item
record (e.g., Inspection Task) that was used to create the Asset Strategy.
About Updating Asset Strategies from

Measurement Location Records
If desired, you can update an Asset Strategy from existing Measurement Location records
if the Measurement Location records are linked to the same Equipment or Functional
Location record that is linked to the Asset Strategy record. When you do so, Meridium
APM will:
Create multiple Actions, which belong to the Proposed Strategy. Each Action
represents a separate Measurement Location record.
Update the Implementation Package record that is linked to the Asset Strategy.
Before you can update an Asset Strategy from Measurement Location records, several
conditions must be met.
Conditions Required to Update Asset

Strategies from Measurement Location
Records
Before you can update an Asset Strategy from Measurement Location records, the
following conditions must be met:
The Measurement Location records must be linked to Equipment or Functional

Location records.
Definition record that represents Measurement Location Group records and
Measurement Location records, the Allow Link Existing check box must be
selected.
If the Measurement Location records are linked to Functional Location records,

the Locate Assets for Import query must be configured to return records in the
Functional Location family.

are updated from Measurement
Location Records?
After you update an Asset Strategy from an existing Measurement Location record:
If the Asset Strategy was in the Active state, it will remain in the Active state.
If the Asset Strategy was in the Pending Review state, it will remain in the
Pending Review state.
source Measurement Location record using the rules referenced in the Action
Mapping record for the Measurement Location Group family. The new Action
will be represented by the icon.
A new Health Indicator record is created from each Measurement Location record
that you selected in the Asset Strategy Builder. Each Health Indicator record is
linked to the appropriate Action record.
No new Risks are created. You will need to assign Risks to each new Action
manually.
If the Asset Strategy record is already linked to an Implementation Package

record, the Implementation Package record will remain in its current state. In
addition, the Implementation Package record will be linked to Measurement
Location Group records. The number of Measurement Location Group records to
which it is linked mimics the number of Measurement Location records that were
selected in the Asset Strategy Builder. Each Measurement Location Group record
will also be linked to a Measurement Location record that was selected during the
import process.
Updating an Asset Strategy from Task

or Measurement Location Records
To update an Asset Strategy from existing Task or Measurement Location records:
The Asset Strategy Builder appears, displaying the Welcome page.
3. Select the Existing Work Management Item(s) option.
The Select Asset(s) screen appears.
5. Select the rows containing the Equipment or Functional Location records that are
linked to the Task and Measurement Location records that you want to use for
updating an existing Asset Strategy.
The Select Work Management Item(s) screen appears.
7. Select the rows containing the Task and Measurement Location records that you
want to use for updating an Asset Strategy.
A series of messages appear. Each message indicates that an existing Asset Strategy
record is already linked to the Equipment or Functional Location record to which the
selected Task and Measurement Location records are linked.
9. Click the Yes button on each message to update the Asset Strategy record that is
linked to the Equipment or Functional Location record to which the specified
Task or Measurement Location record is linked.
-OR-
Click the Yes to All button on the first message to update all Asset Strategy records that
are linked to the Equipment or Functional Location record to which the selected Task and
Measurement Location records are linked.
procedure. Each row represents an Asset Strategy that was updated successfully. The
Strategy column contains a hyperlink, which you can click to access the Asset Strategy
Overview page for that Asset Strategy.
prompted to save the results to a file. If you want to save the result to a Text file, click the
Configuring the Locate Assets for

Import Query
The Locate Assets for Import query, which is located in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Management\Queries, is
intended to display records in the Equipment or Functional Location family. By default,
the query returns records in the Equipment family. If your Task and Measurement
Location records are linked to Functional Locations records, however, you will need to
modify the query to return records in the Functional Location family.
To configure the Locate Assets for Import query so that you can update Asset Strategies
from Task and Measurement Location records:
1. In the Catalog, navigate to \\Public\Meridium\Modules\Asset Strategy
2. Open the Locate Assets for Import query.
The query design appears, displaying the Equipment family as the source.
5. Add the Functional Location family.
the results are displayed in the Asset Strategy Builder, which appears when you
click the Import Strategy link on the ASM - Start Page.
The query is saved.
Accessing the Implementation Package

Associated with an Asset Strategy
If an Asset Strategy record is linked to an Implementation Package record, you can access
that Implementation Package record from the Asset Strategy.
To access an Implementation Package record from an Asset Strategy:
1. Open the Asset Strategy that is linked to the Implementation Package record that
you want to view.
2. On the Navigation menu, click the Strategy Implementation link.
The Packaging <Package ID> page appears, where <Package ID> is the ID of the
Implementation Package record that is linked to the Asset Strategy record.
Creating an Implementation Package

Record from an Asset Strategy
Note: You can link an Implementation Package record to an Asset Strategy record only if
the Asset Strategy record is set to an Active state.
To create a new Implementation Package record that is linked to an Asset Strategy record:
1. Open the Active Asset Strategy that you want to link to a new Implementation
Package record.
A message appears, indicating that an Implementation Package record is not yet linked to
the Asset Strategy record, asking if you want to create one.
The Implementation Package Creation page appears, where you can create the
Note that if the underlying Equipment or Functional Location record is linked to a Site
Reference record that is linked to an SAP System record, the name of that SAP System
record is used to populate the SAP System field in the Implementation Package record.
Also, you will be able to link the Implementation Package record to other Asset Strategy
records only if their underlying Equipment or Functional Location records are linked to
the same Site Reference record.
Note: If the Asset Strategy record state was not Active, an informational message
appears. You can click the Yes button on the message to access the Asset Strategy
Implementation Start Page.
Accessing AHM from an Existing Asset

Strategy
Note: You can access Asset Health Manager (AHM) from an Asset Strategy only if the
Asset Strategy record is linked to an Equipment or Functional Location record.
To access AHM from an existing Asset Strategy:
1. Open the Asset Strategy from which you want to access AHM.
2. On the Navigation menu, click the Health Indicators link.

The ASM - Asset Health Manager page appears. The Equipment or Functional Location
record that is linked to the Asset Strategy record is displayed at the root level of the
Health Indicator Explorer pane. From this page, you can perform any task that you can
perform on the Asset Health Manager page.
About the ASM - Asset Health Manager

Page
The ASM - Asset Health Manager page displays the Asset Health Manager page within
the ASM module. This page functions exactly like it does when it is accessed through the
AHM module. Note that the Equipment or Functional Location record that is linked to
the Asset Strategy record is displayed at the root level of the Health Indicator Explorer
pane.
About the Asset Strategy Approval

Report
The Asset Strategy Approval Report is a comprehensive report that is provided as
baseline ASM content. It provides the following information about a given Asset
Strategy:
A summary of the information that is provided in the graphs in the Risk Analysis.
A summary of the financial benefits and return on investment for the Active
Strategy and the Proposed Strategy. This summary includes a section where you
can write your name, the date, and any comments.
The information in the Asset Strategy record.
A summary of risks, including a list of the actions that mitigate them, the
unmitigated Risk Rank associated with the risk, and the mitigated Risk Rank
associated with the mitigating action.
A list of Actions that are included in the Active Strategy.
The report is meant to be printed to help you decide whether to approve an Asset Strategy
or send it back for rework.
Note: The printed report is easier to view if it is printed using a landscape orientation. To
print it using a landscape orientation, you can use the Page Setup button
on the Report
Viewer toolbar.
You can access the Asset Strategy Approval Report by clicking the Report link on the
Associated Pages menu when you are viewing any of the following pages:

Asset Strategy Revision History
The Asset Strategy Approval Report is stored in the following folder in the Catalog:
\\Public\Meridium\Modules\Asset Strategy Management\Management\Reports.
Note: The report is built from queries that are stored in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Management\Queries. You
should not change the name of the this Catalog folder, the name or content of any queries
within the folder that are referenced by this report, or remove from the folder any query
that is being used by the report. Modifying or moving any of these queries could cause
the report to stop working.
Accessing the Asset Strategy Approval

Report
To access the Asset Strategy Approval report:
1. Open the Asset Strategy whose report you want to view.

2. On the Associated Pages menu, click the Report link.
The Asset Strategy Approval Report appears on the Report Viewer page.
Queries Used by the Asset Strategy

Approval Report
The following table lists queries that are used by the Asset Strategy Approval Report and
the report sections that they generate. Each query is stored in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Management\Queries. For
additional details on the data that is included in each query, you can run the query itself.
Query
Report Section
Asset Strategy Actions Detail
Strategy Cost
Asset Strategy Active Actions Detail
Active Actions
Asset Strategy Active Mitigated Financial

Risks Detail
Financial Risk Mitigation
Asset Strategy Active Mitigated Risks

Detail

Strategy Definition

Active Actions
Strategy Risk Profile
Asset Strategy Financial Risks
Asset Strategy Risk Profile
Strategy Risk Profile
Asset Strategy Risk Summary
Asset Strategy Benefit Summary
Cover Page
The cover page of the Asset Strategy Approval Report displays the Strategy ID and
Description of the Asset Strategy and the date on which the report was generated and the
name of the Security User who generated the report.
The following image illustrates the cover page of a report that was generated:
For an Asset Strategy with the Strategy ID Dryer Strategy and the Description
Strategy for clothes dryer.
On 3/4/2010.
By Amy Duncan.
About the Strategy Risk Profile Section

The Strategy Risk Profile section of the Asset Strategy Approval Report contains the
following items:
Risk Profile graph

Financial Risk Exposure graph
List of Risk records and their risk ranks
The following shows an example of the Strategy Risk Profile section.
Risk Profile Graph

The Risk Profile graph in the Asset Strategy Approval Report shows similar information
to what you would see on the Risk Profile graph in the Risk Analysis. In the report,
however, the graph type is slightly different, and some additional information is
displayed.
Specifically, the Risk Profile graph in the report shows the following information:
Active Bar
The Active bar on the Risk Profile graph shows the following information:
The combined active unmitigated risk rank for all Risks. In other words, this is the
sum of all unmitigated risk rank values that existed when you last activated the
Asset Strategy (assuming that the Asset Strategy is now in a non-Active state). In
the report, this value is displayed in green on the Active bar. This value does not
appear for each Risk on the Risk Profile graph in the Risk Analysis.
The combined Strategy Mitigated Risk Rank value for all Risks. In other words,
this is the sum of all mitigated risk rank values that existed when you last
activated the Asset Strategy (assuming that the Asset Strategy is now in a nonActive state). In the report, this value is displayed in blue on the Active bar. If you
were to view the Risk Profile graph in the Risk Analysis, the Strategy Mitigated
Risk Rank for each Risk record would be displayed as separate datapoints on the
Active line (i.e., the line with the circles).
Proposed Bar
The Proposed bar on the Risk Profile graph shows the following information:
The combined proposed unmitigated risk rank value for all Risks. In other words,
this is the sum of all unmitigated risk rank values that could have changed since
the Asset Strategy was last activated and, therefore, need to be reviewed. In the
report, this value is displayed in tan on the Proposed bar. If you were to view the
Risk Profile graph in the Risk Analysis, the unmitigated risk rank for each Risk
record would be displayed on the Unmitigated line (i.e., the line with the
triangles).
The projected, or proposed, Strategy Mitigated Risk Rank value for all Risks. In
other words, this is the sum of all mitigated risk rank values that could have
changed since the Asset Strategy was last activated and, therefore, need to be
reviewed. In the report, this value is displayed in red on the Proposed bar. If you
were to view the Risk Profile graph in the Risk Analysis, the proposed Strategy
Mitigated Risk Rank for each Risk record would be displayed as separate bars.
The following image shows an example of the Risk Profile graph.
In this image, you can see that:
The combined active unmitigated risk rank for all Risks is 483.6 (on the green
Active bar).
The combined active mitigated risk rank for all Risks is 161.2 (on the blue Active
bar).
The combined proposed unmitigated risk rank for all Risks is 166.3 (on the tan
Proposed bar).
The combined proposed mitigated risk rank for all Risks is 161.2 (on the red
Proposed bar).
Financial Risk Exposure Graph

The Financial Risk Exposure graph in the Asset Strategy Approval Report shows similar
information to what you would see in the Financial Risk Exposure graph in the Risk
Analysis. Specifically, the Financial Risk Exposure graph in the report shows the
following information:
Active Bar
The Active bar on the Financial Risk Exposure graph shows the following information:
The combined unmitigated financial risk rank values for all Risks that are
included in the Active Strategy. In other words, this is the sum of all unmitigated
financial risk rank values that existed when you last activated the Asset Strategy.
In the report, this value is displayed in green on the Active bar. This value does
not appear for each Risk on the Financial Risk Exposure graph in the Risk
Analysis.
The combined mitigated financial risk rank values for all Risks that are included
in the Active Strategy. In other words, this is the sum of all mitigated financial
risk rank values that existed when you last activated the Asset Strategy. In the
report, this value is displayed in yellow on the Active bar. If you were to view the
Financial Risk Exposure graph in the Risk Analysis, the mitigated financial risk
rank value for each Risk record would be displayed on the Active bar.
Proposed Bar
The Proposed bar on the Financial Risk Exposure graph shows the following information:
The combined projected, or proposed, unmitigated financial risk rank values for
all Risks. In other words, this is the sum of all unmitigated financial risk rank
values that could have changed since the Asset Strategy was last activated and,
therefore, need to be reviewed. In the report, this value is displayed in purple on
the Proposed bar. If you were to view the Financial Risk Exposure graph in the
Risk Analysis, the proposed unmitigated financial risk rank value for each Risk
record would be displayed on the Unmitigated bar.
The projected, or proposed, mitigated financial risk values for all Risks. In other
words, this is the sum of all mitigated financial risk rank values that could have
changed since the Asset Strategy was last activated and, therefore, need to be
reviewed. In the report, this value is displayed in blue on the Proposed bar. If you
were to view the Financial Risk Exposure graph in the Risk Analysis, the
proposed mitigated financial risk rank value for each Risk record would be
displayed on the Proposed bar.
The following image shows an example of the Financial Risk Exposure graph.
In this image, you can see that:
The combined active unmitigated financial risk rank for all Risks is $183.00 (on
the green Active bar).
The combined active mitigated financial risk rank for all Risks is $111.00 (on the
blue Active bar).
The combined proposed unmitigated financial risk rank for all Risks is $162.00
(on the tan Proposed bar).
The combined proposed mitigated financial risk rank for all Risks is $64.50 (on
the red Proposed bar).
List of Risk Records and Risk Ranks

The Risk Analysis section of the Asset Strategy Approval Report contains a list of Risks
that are included in the Asset Strategy. For each Risk that is included in the Asset
Strategy, the list contains four rows:
One row displays the unmitigated risk rank associated with the Risk that is
included in the Active Strategy.
One row displays the mitigated risk rank associated with the Risk that is included
in the Active Strategy.
One row displays the unmitigated risk rank associated with the corresponding
Risk that is included in the Proposed Strategy.
One row displays the mitigated risk rank associated with the corresponding Risk
that is included in the Proposed Strategy.
The following columns of information are displayed for each row:
Strategy Type: Displays a value representing the type of Asset Strategy that
includes the Risk.
If the Risk belongs to an Active Strategy, the Strategy Type column

contains the value Active.
If the Risk belongs to a Proposed Strategy, the Strategy Type column
contains the value Proposed.
Name: Displays the value in the Name field in the Risk record.
Risk Type: Displays a value identifying the type of risk. The value in the Risk
Type column is tied closely to the value in the Rank column.
If the value in the Rank column comes from the Risk Rank field in the
Risk record, the value in the Risk Type column is Unmitigated.
If the value in the Rank column comes from the Risk Rank field in the
Risk Assessment record to which the Risk record is linked, the value in the
Risk Type column is Mitigated.
Rank: Displays the risk rank value associated with the type of Risk record
represented by the value in the Risk Type column.
If the value in the Risk Type column is Unmitigated, the value in the Rank
column is the value in the Risk Rank field in the Risk record.
If the value in the Risk Type column is Mitigated, the value in the Rank
column is the value in the Risk Rank field in the Risk Assessment record
to which the Risk record is linked.
The following image shows an example of the list of Risk records.
Strategy Cost Graph

The Strategy Cost section of the Asset Strategy Approval Report shows similar
information to what you would see in the Cost of Actions graph in the Risk Analysis. In
the report, however, for both the Active Strategy and the Proposed Strategy, the graph
shows two side-by-side bars to represent the CM Action records and PM Action records.
The graph in the Risk Analysis, on the other hand, shows one stacked bar for the Active
Strategy and another stacked bar for the Proposed Strategy, where the PM and CM Action
Types are displayed on one bar.
The following image shows an example of the Strategy Cost graph.
The Strategy Cost graph displays the cost per year associated with each Action in the
Active Strategy and in the Proposed Strategy.
Cost for each Action record by adding it to the grid in the Actions section using the Show
By default, the graph contains two bars for the Active Strategy and two bars for the
Proposed Strategy. In each set of bars:
One bar represents the total cost per year for Actions whose Action Type is TimeBased Maintenance (Preventive) (PM).
One bar represents the total cost per year for Actions whose Action Type is
Condition-Based Maintenance (Predictive) (CM).
Hint: If you view the Action datasheet for any Action, you can see these options in the
Action Type list.
From the legend, you can determine which Action Type is associated with which color.
in the Active Strategy is $60.00.
As you make changes to the Asset Strategy, causing its state to change to Modified, any
changes that you make to an Action's cost will be reflected in the Proposed bar for the
Action Type associated with that Action record.
Below the Strategy Cost graph is a grid containing a row for each Action in the Active
Asset Strategy and a separate row for each Action in the Proposed Asset Strategy. In the
grid, you can see various information about each Action, including the Annual Cost.
Strategy Definition
The Strategy Definition section of the Asset Strategy Approval Report contains the
following information from the Asset Strategy record:
Strategy Owner
Description
Strategy Re-Evaluation Date
Site Reference
Notes
This information is also available on the Asset Strategy Definition page. The following
image shows an example of the Strategy Definition section in the Asset Strategy
Approval Report.
Active Actions
The Active Actions section of the Asset Strategy Approval Report contains the following
information from the Actions that are included in the Asset Strategy:
Action ID
Action Name
Action Description
Action Type
Interval
Interval Units
Condition Monitoring Type
The following image shows an example of the Active Actions section in the Asset
Strategy Approval Report.
Creating Templates from Scratch

To create an Asset Strategy Template from scratch:
1. On the ASM - Start Page, click the Manage Templates link.
The Asset Strategy Template Search page appears.
2. On the Common Tasks menu, click the Create Template link.
The Asset Strategy Template Definition page appears.
3. In the Template ID text box, type an ID for the Asset Strategy Template.
4. In the Description text box, type a description of the Asset Strategy Template.
5. If desired, in the Template Owner text box, modify the default value. The value in
the Template Owner text box is set by default to the name of the Security User
who created the Asset Strategy Template record.
Note: The value in the Template Activation Date text box is set by default to the date that
the Asset Strategy Template state was set to Active for the first time. This field is
disabled, and the field is populated automatically after the Asset Strategy Template state
changes to Active for the first time.
6. In the Template Evaluation Date list, select the date on which you want to
reevaluate the Asset Strategy Template.
7. In the Risk Matrix list, select the Risk Matrix that you want to use in this Asset
Strategy Template and all Asset Strategies to which it is applied. Note that you
cannot apply an Asset Strategy Template that uses one Risk Matrix to an Asset
Strategy that is already using a different Risk Matrix.
8. In the Template Notes text box, type any additional information you want to
provide about the Asset Strategy Template.
9. On the datasheet toolbar, click the
button.
The Asset Strategy Template record is saved.

10. Continue building the Asset Strategy Template by adding Action records using the
Asset Strategy Template Actions page.
Note that the Proposed Strategy section and the Risks section on the Asset Strategy
Template Actions page are identical to the Proposed Strategy section and the Risks
section on the Asset Strategy Actions page. You can use the instructions for performing
tasks on that page to determine how to determine the same tasks on the Asset Strategy
Template Actions page.
11. Continue building the Asset Strategy Template by adding Risks using the Asset
Strategy Template Risks page.
Note that the Risks section and the Mitigating Actions section on the Asset Strategy
Template Risks page are identical to the Risks section and the Mitigating Actions section
on the Asset Strategy Risks page. You can use the instructions for performing tasks on
that page to determine how to determine the same tasks on the Asset Strategy Template
Risks page.
12. When you are finished building the Asset Strategy Template, activate the Asset
Strategy Template so that it can be applied to Asset Strategies.
Creating Templates from Existing Asset

Strategies
To create an Asset Strategy Template from an existing Asset Strategy:
1. Search for and open the Active Asset Strategy that you want to use to create an
2. On the Template Tasks menu, click the Save as Template link.
The Asset Strategy Template Definition page appears.
The following text boxes are populated automatically:
Template ID: Set by default to the ID of the source Asset Strategy,

appended by the text - Template. For example, if the ID of the source
Asset Strategy is Piping Circuit Strategy, the ID of the Asset Strategy
Template will be Piping Circuit Strategy - Template.
Description: Set by default to the description of the source Asset Strategy
record.
Template Owner: Set by default to the Security User who created the Asset
Strategy Template record.
Template Evaluation Date: Set by default to the Strategy Re-Evaluation

Date value from the source Asset Strategy record.
Template Notes: Set by default to the Strategy Notes value from the source
Note that unlike the Asset Strategy datasheet, the Asset Strategy Template datasheet does
not contain an Asset tab. You cannot link an Asset Strategy Template record to an
Equipment or Functional Location record.
3. On the datasheet toolbar, click the
button.
The Asset Strategy Template record is saved.

As you view the Actions, Risks, and Risk Assessments for the Asset Strategy Template,
you will see that they are identical to the Actions, Risks, and Risk Assessments for the
source Asset Strategy. You can modify the values in these records if desired.
Note, however, that if the Risks or Actions that are linked to the Asset Strategy originated
from RBI or SIS Management, those items will not be copied.
Creating Templates from Existing

Templates
You can use an existing Asset Strategy Template to create a new Asset Strategy Template
by creating a copy of the existing Asset Strategy Template. The new Asset Strategy
Template will be an exact copy of the source Asset Strategy Template with the exception
of the Template ID value. The Template ID of the new Asset Strategy Template will be
Copy of <Source Template ID> <#>, where:
Source Template ID is the value stored in the Template ID field in the source
Asset Strategy Template record.
# is a number that increments by one each time you create a subsequent copy of
the same source Asset Strategy Template record, beginning with the second copy.
For example, if you create a copy of an Asset Strategy Template with the Template ID
Template - PMP, the Template ID for the new Asset Strategy Template will be Copy of
Template - PMP. If you create a second copy of the same source Asset Strategy Template
record, the Template ID for the new Asset Strategy Template record will be Copy of
Template - PMP 1.
If the source Asset Strategy Template includes items that are marked for deletion, the new
Asset Strategy Template will not include those items (i.e., they will be considered deleted
from the source template).
You can create a copy of an Asset Strategy Template using the Copy Template link on the
Common Tasks menu from any page where you are working with templates, including
the Asset Strategy Template Search page.
To create an Asset Strategy Template from an existing Asset Strategy Template:
1. Open or select the Asset Strategy Template that you want to copy to create a new
2. On the Common Tasks menu, click the Copy Template link.
A new Asset Strategy Template is created and displayed on the Asset Strategy Template
Definition page.
About Creating Templates by Promoting

RCM FMEA Analyses
Like creating an Asset Strategy by promoting an RCM FMEA Recommendation record,
you can promote an RCM FMEA Recommendation record to an Asset Strategy Template.
When you do so, various records will be created as a part of that process. An RCM
FMEA Recommendation record can only be promoted to an Asset Strategy Template if
that RCM FMEA Recommendation record is linked to an RCM FMEA Asset record.
Creating Asset Strategy Templates by

Promoting RCM FMEA Analyses
To create an Asset Strategy Template by promoting an RCM FMEA Analysis:
1. Access the Recommendation Management page from the RCM Analysis whose
recommendations you want to use to create an Asset Strategy Template.
-ORAccess the Recommendation Management page from the FMEA Analysis whose
recommendations you want to use to create an Asset Strategy Template.
2. On the Asset Tasks menu, click the Promote to Template link.
The Meridium APM system checks to see whether the Accepted by ASM state requires a
Security User to be assigned.
3.
o
If the State Configuration for the Accepted by ASM state does not require
a Security User to be assigned, or if the State Configuration for the
Accepted by ASM state already has a Security User assigned, a progress
bar appears, as shown in the following image. After the progress bar
reaches the end, the new Asset Strategy Template record appears on the
Asset Strategy Template Actions page.
-OR
o
If the State Configuration for the Accepted by ASM state requires a

Security User to be assigned but a Security User is not currently assigned,
the State Assignee dialog box appears, as shown in the following image.
3. On the State Assignee dialog box, in the Select assignee for State 'Accepted by
ASM' list, select the Security User that you want to assign to the Accepted by
ASM state, and click OK.
A progress bar appears. After the progress bar reaches the end, the new Asset Strategy
Template record appears on the Asset Strategy Template Actions page.
About Importing Templates from

Microsoft Excel
If desired, you can create an Asset Strategy Template from a Microsoft Excel file. When
you do so, Meridium APM will create:
One Asset Strategy Template record.

One Active Strategy record that is linked to the Asset Strategy Template record.
One Proposed Strategy record that is linked to the Asset Strategy Template record.
Action record represents a separate Action from the Microsoft Excel spreadsheet.
During the import process, you can map values in the Microsoft Excel file to fields in the
Meridium APM records that will be created. To make sure that the mappings work
correctly, the Microsoft Excel file must meet the following minimum requirements:
It must contain a worksheet that lists the Asset Strategy Templates that you want
to create. There are no restrictions on the tab name. Throughout this
documentation, we refer to this tab as the Templates worksheet.
The Templates worksheet must contain a column whose value you will map to the
Template ID field in the Asset Strategy Template record. Throughout this
documentation, we refer to this tab as the Template ID column.
It must contain a worksheet that lists the Actions that you want to include in the
Asset Strategy Template. There are no restrictions on the tab name. Throughout
this documentation, we refer to this tab as the Actions worksheet.
The Actions worksheet must contain a column whose value you will map to the
Action ID field in the Action record.
The Actions worksheet must contain a column that defines the Asset Strategy
Template to which each Action should belong. Each cell in the column must
contain a value that appears in the Template ID column on the Templates
worksheet. Throughout this documentation, we refer to this column as the
Template Reference column.
Note that if you want to map a value to the Action Type field in an Action record, the
Microsoft Excel file must contain a value that mimics an Action Type as it is stored in the
Meridium APM database, not as it is displayed on the Action datasheet. Use the following
list to determine the Action Types that you can be mapped from the Microsoft Excel file
to an Action record:
PM: Will be displayed as Time-Based Maintenance (Preventive) (PM) on the

Action datasheet.
CM: Will be displayed as Condition-Based Maintenance (Predictive) (CM) on the
Action datasheet.
DSN: Will be displayed as Redesign (DSN) on the Action datasheet.
PROC: Will be displayed as Procedure (PROC) on the Action datasheet.
TRN: Will be displayed as Training (TRN) on the Action datasheet.

The following instructions assume that a Microsoft Excel file that meets the minimum
requirements has been saved to a location that is accessible from your workstation.
Note: You must be a Super User or a member of the MI ASM Analyst Security Group to
perform the following steps.
To import an Asset Strategy Template:
1. On the ASM - Start Page, click the Import Strategy Template link.
-OROn any Common Tasks menu in ASM, click the Import Template link.
2. Navigate to the location containing the Microsoft Excel file that you want to use
for importing an Asset Strategy Template, select the file, and then click the Open
button.
The Select Data to Import window appears, displaying the Templates tab by default.
3. In the Required Mappings section, in the Template Worksheet list, select the
Templates worksheet that is configured in the Microsoft Excel file. This is the
worksheet that contains a column whose value you will map to the Template ID
field in the Asset Strategy Template record.
4. In the Template ID Column list, select the column whose value you want to map
to the Template ID field in the Asset Strategy Template record.
5. To populate other fields in the Asset Strategy Template record, in the Additional
Meridium Strategy Template Field column that represents a field that you want to
populate from that Microsoft Excel file column. For example, if the Microsoft
Excel file contains the column Description, to the right of the Description cell,
you would probably want to select Description.
6. Click the Actions tab.
7. In the Action Worksheet list, select the Actions worksheet that is configured in the
you will map to the Action ID field in the Action record.
8. In the Template Reference Column list, select the Template Reference column that
is configured in the Microsoft Excel file.
9. In the Action ID list, select the column whose value you want to map to the
Action ID field on the Action datasheet.
10. To populate other fields in the Action records, in the Additional Mappings section,
to the right of each Excel Column cell, select a value in the Meridium Action
Field column that represents a field that you want to populate from that Microsoft
Excel file column. For example, if the Microsoft Excel file contains the column
Type, to the right of the Type cell, you would probably want to select Action
Type.
Note: At this point, you could click OK to create an Asset Strategy Template that does not
contain Risks. The remaining instructions, however, assume that you want to import
Risks from the Microsoft Excel file to the Asset Strategy Template.
11. Click the Risks tab.
12. In the Risk Worksheet list, select the Risks worksheet that is configured in the
you will map to the Risk ID field in the Risk record.
13. In the Template Reference Column list, select the column whose value contains
the ID of the Asset Strategy Templates that should contain each Risk record.
14. In the Risk ID Column list, select the column whose value you will map to the
Risk ID field in the Risk record.
15. In the Meridium Risk Matrix list, select the Risk Matrix that you want the Asset
Strategy Template to use.
16. To populate other fields in the Risk records, in the Additional Mappings section,
to the right of each Excel Column cell, select a value in the Meridium Risk Field
column that represents a field that you want to populate from that Microsoft Excel
file column.
17. Click the Mitigations tab.
18. In the Mitigation Worksheet list, select the Mitigations worksheet that is
configured in the Microsoft Excel file.
19. In the Action Reference Column list, select the column that contains the ID of an
Action, as it appears on the Actions worksheet.
20. In the Risk Reference Column list, select the column that contains the ID of a
Risk, as it appears on the Risks worksheet.
21. To populate other fields in the Risk Assessment records, in the Additional
Meridium Risk Assessment Field column that represents a field that you want to
populate from that Microsoft Excel file column.
22. Click OK.
The Import Strategy Template page appears, displaying the results of the import
procedure. Each row represents an Asset Strategy Template that was created successfully.
The Strategy column contains a hyperlink, which you can click to access the Asset
Strategy Actions page. In some cases, an Asset Strategy Template may not have been
imported. If so, a message will appear in the Info column, indicating the reason that
strategy was skipped.
Saving a Mapping
To save a mapping from a Microsoft Excel file to an Asset Strategy Template:
1. After you have accessed the Select Data to Import dialog box and configured the
mappings that you want to save, click the Save Mapping button.
The Save Mapping window appears.
2. In the Mapping Name text box, type a new name for the mapping.
3. Click OK.
The mapping is saved, and the Save Mapping window closes. The Pre-Configured
Mapping list above the Assets tab is populated with the mapping name. Other users that
access the Select Data to Import window will now be able to select this mapping and use
it to create a new Asset Strategy Template.
Example of a Microsoft Excel File Used

to Create Asset Strategy Templates
Consider the following example, which explains how to create two Asset Strategy
Templates, where one Asset Strategy Template contains three Action records, and the
other Asset Strategy Template contains two Action records.
Note: This example assumes that you are not importing Risks from the Microsoft Excel
file. To see an example of importing Risks to create an Asset Strategy, click here.
The Microsoft Excel file contains the Templates worksheet, which is shown in the
following image.
From this worksheet, you can see that two Template IDs are listed: Template 1 and
Template 2. When you use this Microsoft Excel file to create Asset Strategy Templates,
two Asset Strategy Template records will be created.
The Microsoft Excel file also contains the Actions worksheet, which is shown in the
following image.
In the Microsoft Excel file, the three green rows represent actions for Template 1, and the
two blue rows represent actions for Template 2. The Template ID associated with each
action is displayed in the Template ID column.
In other words, for Template 1, the following actions should be included:
Vibration Analysis
Basic Lube Oil Analysis
Complete Lube Oil Analysis
Likewise, for Template 2, the following actions should be included:
Performance Test
Internal Inspection
Each action will be used to create a single Action record when the import procedure is
performed.
Based on this Microsoft Excel file, when performing the import procedure, you could
specify the mappings from the Templates worksheet of the Microsoft Excel file to match
the mapping that are shown in the following image.
Note that in the Additional Mappings section, the ID is not mapped from the Microsoft
Excel file to the Asset Strategy Template record. In this example, this field has already
been mapped using the Required Mappings section of this dialog box. If additional
columns were available in the Templates worksheet of the Microsoft Excel file, they
would also be listed in the Additional Mappings section, and you might consider mapping
them to a field in the Asset Strategy Template record (e.g., Notes).
Likewise, you could specify the mappings from the Actions worksheet of the Microsoft
Excel file to match the mappings shown in the following image.
When the import procedure is complete, two Asset Strategy Templates would be created,
The Asset Strategy Template Template 1 would be linked to the Action records shown in
The fields in Action: Basic Lube Oil Analysis would be populated as shown in the
following image.
Likewise, the Asset Strategy Template Template 2 would be linked to the Action records
shown in the following image.
The fields in Action: Internal Inspection would be populated as shown in the following
image.
Opening Asset Strategy Templates

To open an existing Asset Strategy Template:
1. Access the ASM - Asset Strategy Template Search page.
2. In the Asset Strategy Template Search workspace, in the row containing the Asset
Strategy Template that you want to open, click the hyperlinked Template ID.
About Applying Templates to Asset

Strategies
You can apply an Asset Strategy Template to an Asset Strategy in one of two ways:
Apply the template as a copy: This option allows you to manage the Asset
Strategy independently of the template after the template has been applied.
Apply the template as a master: This option causes the Asset Strategy to become
controlled completely by the Asset Strategy Template, meaning that no changes
can be made at the Asset Strategy level. To be able to make changes at the Asset
Strategy level, you will need to remove the Asset Strategy from the template (i.e.,
break the connection between the template and the strategy).
Specifically, you can apply Asset Strategy Templates (i.e., templates) to Asset Strategies
using the following methods:
While viewing an Asset Strategy:
Apply it as a copy.
Apply it as a master.
While viewing the Asset Strategy Template:
Apply it as a copy.
Apply it as a master.
Create a new Asset Strategy as a controlled strategy of a master Asset

Strategy Template.
Create a new Asset Strategy as a copy of the Asset Strategy Template.
If an Asset Strategy Template is configured to use a non-default Risk Matrix (via the Risk
Matrix field in the Asset Strategy Template record), the Asset Strategy Template can be
applied only to:
Existing Asset Strategies that are associated with a site whose Site Reference
record is linked to that Risk Matrix record.
New Asset Strategies where the Equipment or Functional Location record is

linked to a Site Reference record that is linked to that Risk Matrix record.
In addition, after you apply an Asset Strategy Template that is configured to use a nondefault Risk Matrix to an Asset Strategy, the Risk Matrix field in that Asset Strategy
Template record is disabled.
About Applying a Template as a Master

or as a Copy
Regardless of your entry point to the Apply Template Builder, you will need to specify
the method that you want to use to apply a template. More specifically, you can select one
of the following options:
Apply the template as a copy: The Asset Strategy Template will be applied to the
selected Asset Strategies as a copy, and you will be able to manage the Asset
Strategies independently of the master template afterwards. If you select this
option, you will need to select additional settings. These settings are explained in
the instructions for applying a template as a copy.
Apply the template as a master: The Asset Strategy Template will be applied to
the selected Asset Strategies as a master, and all changes to the Asset Strategies
will be driven by changes to the Asset Strategy Template. This option causes the
Asset Strategies to become controlled completely by the Asset Strategy Template,
meaning that no changes can be made at the Asset Strategy level.
If you select this option, the Asset Strategy states will be set to Active (but displayed as
Controlled by Master Template). Note that you cannot apply a template as a master to an
Asset Strategy that contains Mandatory Action records.
You will select one of these options on either of the following screens in the Apply
Template Builder. These screens contain the same options but are titled differently
depending upon your entry point.
Options for Applying the Template screen, which appears when you access the
Apply Template Builder while you are viewing an Asset Strategy.
Template Application Method screen, which appears when you access the Apply
Template Builder while you are viewing a template.
The following image shows what the options look like on these screens. A red outline has
been added to the image to highlight the Apply the template as a copy and Apply the
template as a master options.
Using the Actions or Risks to Include in

Template Application Screen in the
Apply Template Builder
When you apply a template to an Asset Strategy as a copy, you will specify which
portions of the template you want to apply. You can choose from the following options:
Apply both Actions and Risks
-OR
Apply Risks only
The option that you select will determine the content that appears on the Actions or Risks
to Include in Template Application screen. The following image shows what the Actions
or Risks to Include in Template Application screen looks like when you select the Apply
both actions and risks option on the preceding screen in the builder. You can use the
Actions or Risks to Include in Template Application screen to remove actions and risks
that you do not want to add to the Asset Strategy. This step is optional.
This screen can contain the following tabs, depending upon whether you select to apply
both Actions and Risks or only Risks to the Asset Strategy:
Template Risks to Include: Contains two grids:
Template Risks to Include: Contains the list of Risks that are included in
the template. Each row represents one Risk. When you select a row, the
Mitigating Actions grid refreshes and displays the Actions that are
associated with the selected Risk. This grid will always appear.
Mitigating Actions: Contains the list of Actions that are associated with
the Risk that is selected in the Template Risks to Include grid. Each row
represents one Action. This grid will appear only if you select the Apply
both actions and risks option in the Select which portions of the template
to apply section.
Template Actions to Include: Contains two grids:
Template Actions to Include: Contains a list of Actions that are included in

the template. Each row represents one Action. When you select a row, the
Mitigated Risks grid refreshes and displays the Risks that are associated
with the Action.
Mitigated Risks: Contains the list of Risks that are associated with the
Action that is selected in the Template Actions to Include grid. Each row
This tab will appear only if you select the Apply both actions and risks option on the
preceding screen in the builder.
The column on the far left in these grids contains a check box, which is selected by
default. You can clear this check box to specify that the corresponding record should not
be applied to the Asset Strategy. When you clear a check box for:
A Risk, it will not be applied to the Asset Strategy. If the Risk is associated with
Actions, those Actions will not be excluded automatically from the template
application. In order to exclude the Actions that mitigate a risk, you must clear the
check box associated with any Action you want to exclude.
An Action, it will not be applied to the Asset Strategy. If the Action is associated
with Risks, those Risks will not be excluded automatically from the template
application. In order to exclude the Risks from the template application, you must
clear the check box for any Risk you want to exclude.
When you clear a check box associated with an Action or Risk, you are specifying that
the item should not be applied to the Asset Strategy. That item will not be removed from
the template itself.
Applying a Template as a Copy While

Viewing the Asset Strategy
You can apply an Asset Strategy Template to an Asset Strategy only if the Asset Strategy
state is Draft, Modified, or Active. You cannot apply an Asset Strategy Template to an
Asset Strategy if the Asset Strategy state is Pending Review. The following instructions
assume that you are applying a template to an Asset Strategy in a state other than Pending
Review.
Members of the MI ASM Reviewer Security Group will be unable to apply a template to
an Asset Strategy. The Apply a Template link is disabled if you are logged in as a member
of the MI ASM Reviewer Security Group.
To apply a Template as a copy while viewing the Asset Strategy:
1. Open the Asset Strategy to which you want to apply an Asset Strategy Template
as a copy.
2. On the Template Tasks menu, click the Apply a Template link.
The Apply Template Builder appears, displaying the Welcome screen.

The Select a Template screen appears, displaying a list of all Active Asset Strategy
Templates.
4. In the grid, select the row containing the Asset Strategy Template that you want to
apply to the Asset Strategy, and then click the Next button.
The Options for Applying the Template screen appears.
5. In the Select to apply the template as a copy or as a master section, select the
Apply the template as a copy option.
6. In the Select which portions of the template to apply section, select one of the
following options:
1.
Apply both actions and risks: Will cause the Actions, Risks, and all
associated Risk Assessments to be transferred from the Asset Strategy
Template to the new Asset Strategies. This option is selected by default.
Apply risks only: Will cause only the Risks and their unmitigated Risk
Assessments to be transferred from the Asset Strategy Template to the new
Asset Strategies.
7. In the Select how existing items should be handled in existing Asset Strategies
section, select one of the following options:
o
Mark existing items for deletion: Causes the Meridium APM system to
flag any non-Mandatory Actions and associated Risks in the Asset
Strategy as deleted, meaning their flag will contain an X symbol
(Mandatory Actions are not flagged as deleted). This option is selected by
default.
If desired, after the Asset Strategy Template is applied, you can undo this action so that
the Actions and Risks will not be deleted when the Asset Strategy is activated. Note that
if an Action or Risk was added to the Asset Strategy after it was last activated, that record
will be removed from the Asset Strategy when the Asset Strategy Template is applied.
The Asset Strategy will be set to the Modified state.
Append the template items to the existing items: Causes the Meridium
APM system to flag any Action or Risk in the Asset Strategy Template as
new in the Asset Strategy. This option does not flag any Action or Risk in
the Asset Strategy as deleted.
The Asset Strategy state will be set to the Modified state.

The Actions or Risks to Include in Template Application screen appears, displaying in
grids the Actions and Risks that are included in the template.
9. Review the Actions and Risks that are included in the template application, and
clear the check box in the rows containing the items that you do not want to apply
to the Asset Strategy. This step is optional.
The Finish Applying the Template screen appears, displaying a summary of your
selections.
The Asset Strategy Template is applied to the Asset Strategy, and a message appears,
indicating that the Asset Strategy Template was applied successfully.
12. Click OK.
The Asset Strategy returns to focus.
Applying a Template as a Copy While

Viewing the Template
Review.
To apply a Template as a copy while viewing the Asset Strategy Template:

1. Open the Asset Strategy Template that you want to apply as a copy to existing
Asset Strategies.
2. On the Common Tasks menu, click the Apply Template link.

The Template Application Method screen appears.
5. In the Select which portions of the template to apply section, select either of the
following options:
5.
Apply both actions and risks: Transfers the Actions, Risks, and all
associated Risk Assessments from the Asset Strategy Template to the
Asset Strategies. This option is selected by default.
Apply risks only: Transfers only the Risks and their unmitigated Risk
Assessments from the Asset Strategy Template to the Asset Strategies.
Strategies as deleted, meaning their flag will contain an X symbol
default.
If desired, after the Asset Strategy Template is applied to an Asset Strategy, you can undo
this action so that the Actions and Risks will not be deleted when the Asset Strategy is
activated. Note that if an Action or Risk was added to the Asset Strategy after it was last
activated, that record will be removed from the Asset Strategy when the Asset Strategy
Template is applied.
The Asset Strategies will be set to the Modified state.
APM system to flag any Actions or Risks in the Asset Strategy Template
as new in the Asset Strategy. This option does not flag any Actions or
Risks in the Asset Strategy as deleted.

clear the check box in the row containing the items that you do not want to apply
The Select Records screen appears.
10. To apply this Asset Strategy Template to Asset Strategies for specific assets,
accept the default selection, Search by Asset.
-OR-
To apply this Asset Strategy Template to specific Asset Strategies, select the Search by
Asset Strategy option.
7.
o
If you selected the Search by Asset option on the previous screen, the
Search In list displays a list of families that are predecessors in the Has
Strategy relationship.
If you selected the Search by Asset Strategy option on the previous screen,
the Asset Type list displays a list of families that contain a record that is
already linked to an Asset Strategy record.
o
If you selected the Apply the template as a copy option on the

Template Application Method screen, this screen displays the
results of the query Asset_Strategy_Search_Non_Pending.
If you selected the Apply the template as a master option on the
results of the query Strategies Without Master Templates.
12. If you see the Search In list, select the family containing the records that are
linked to Asset Strategy records to which you want to apply this template:
Equipment or Functional Location. The search results will display all records in
that family. If desired, you can also use the options on the Advanced Search tab to
refine the search criteria using an Advanced Search.
-ORIf you see the Asset Type list, select the family containing the records that are linked to
the Asset Strategy records to which you want to apply this template: Equipment or
Functional Location.
If you selected the Apply the template as a copy option on the Template
Application Method screen, the search results display Asset Strategy
records that are linked to an Equipment or Functional Location record in
the selected family and that are not set to the Pending Review state.
If you selected the Apply the template as a master option on the Template
Application Method screen, the search results display:
Non-Pending Review Asset Strategy records that are linked to an

Equipment or Functional Location record in the selected family but
are not linked to an Asset Strategy Template record through the
Master Template Has Asset Strategy relationship.
Non-Pending Review Asset Strategy records that are not linked to
an Equipment or Functional Location record and are not linked to
an Asset Strategy Template record through the Master Template
Has Asset Strategy relationship.
13. Click the Find Now button or the Run Query button, whichever is available.
The results are returned in the grid below the search criteria.
14. Select the rows containing the desired records.
If you select Equipment or Functional Location records, this template will be applied to
the Asset Strategies for those assets.
-ORIf you select Asset Strategy records, this template will be applied to those Asset
Strategies.
selections.
The Asset Strategy Template is applied to the Strategy.
Creating New Asset Strategies as Copies

of a Template
The following instructions provide details on creating one or more Asset Strategies from
an Asset Strategy Template that is applied as a copy. The number of Asset Strategies that
will be created is determined by the number of Equipment and Functional Location

records that you select during the creation process.
To create one or more new Asset Strategies as a copy of an Asset Strategy Template:
1. Search for and open the Active Asset Strategy Template that you want to use to
create new Asset Strategies.
5. In the Select which portions of the template to apply section, select either of the
following options:
Apply both actions and risks: Transfers the Actions, Risks, and all
associated Risk Assessments from the Asset Strategy Template to the
Asset Strategies. This option is selected by default.
Apply risks only: Transfers only the Risks and their unmitigated Risk
Assessments from the Asset Strategy Template to the Asset Strategies.
Strategies as deleted, meaning their flag will contain an X symbol
default.
If desired, after the Asset Strategy Template is applied to an Asset Strategy, you can undo
this action so that the Actions and Risks will not be deleted when the Asset Strategy is
activated. Note that if an Action or Risk was added to the Asset Strategy after it was last
activated, that item will be removed from the Asset Strategy when the Asset Strategy
Template is applied.
APM system to flag any Actions or Risks in the Asset Strategy Template
as new in the Asset Strategy. This option does not flag any Actions or
Risks in the Asset Strategy as deleted.

clear the check box in the row containing the items that you do not want to apply
10. Accept the default selection, Search by Asset, and click the Next button.
The Select Records screen appears. The Search In list displays a list of families that are
predecessors in the Has Strategy relationship.
11. In the Search In list, select the Equipment or Functional Location family
containing the records for which you want to create new Asset Strategies. If
desired, you can also use the options on the Advanced Search tab to refine the
search criteria using an Advanced Search.
This template will be used to create new Asset Strategies for the selected records.
selections.
The Asset Strategy Template is used to create the new Asset Strategies, and the Apply
Asset Strategy Template page appears.
Each row represents an Asset Strategy that was created successfully. The Strategy column
contains a hyperlink, which you can click to access the Asset Strategy Actions page.
Note that in each new Asset Strategy that was created from the template, any Actions or
Risks that exist in the Asset Strategy Template are flagged as new in the Asset Strategy
(their flag will contain a plus symbol). If desired, you can undo this action so that the
Actions and Risks will not be included in the Asset Strategy when the Asset Strategy is
activated.
About Master Templates

A master template is an Asset Strategy Template that has been applied to an Asset
Strategy and controls the Asset Strategy, meaning that no changes can be made at the
Asset Strategy level. All changes that you make to a master template will be applied
automatically to the controlled Asset Strategy when the template is activated.
Note the following characteristics of master templates and the records related to them:
When an Asset Strategy is controlled by a master template, its stored state is

always Active, regardless of the state of the master template. When you are
viewing the Asset Strategy in ASM, however, the state will be displayed as
Controlled by Master Template.
When you activate a master template, a message will appear, identifying the Asset
Strategies to which the changes will be applied.
Health Indicator records that are linked to Action records in a master template will
not be applied to any Asset Strategies that are controlled by the master template.
You cannot delete an Asset Strategy Template that is functioning as a master

template. If a template is applied to an Asset Strategy as a master, you must
remove those Asset Strategies from the master template before you can delete the
You cannot apply a master template to an Asset Strategy that contains Mandatory
Actions.
You cannot apply a master template to an Asset Strategy whose state is set to
Pending Review.
You cannot apply a master template to an Asset Strategy that contains Actions or
Risks that originated in Risk Based Inspection (RBI) or Safety Instrumented
System (SIS) Management.
If an Asset Strategy Template has been applied as a master template to an Asset

Strategy, another Asset Strategy Template cannot be applied to that Asset Strategy.
An Asset Strategy Template can be applied as a master template to some Asset

Strategies and as a standard template to other Asset Strategies.
Applying a Template as a Master While

Viewing the Asset Strategy
Review.
You cannot apply a template as a master to an Asset Strategy that contains Mandatory
Action records.
To apply a template as a master while viewing the Asset Strategy:
1. Open the Asset Strategy to which you want to apply an Asset Strategy Template
as a master.
2. On the Template Tasks menu, click the Apply a Template link.

The Select a Template screen appears, displaying a list of all Active Asset Strategy
Templates.
4. In the grid, select the row containing the Asset Strategy Template that you want to
apply to the Asset Strategy, and then click the Next button.
The Options for Applying the Template screen appears.
Apply the template as a master option.
The remaining options are disabled.

The Finish Applying Template screen appears, displaying a summary of your selections.
A progress bar appears, indicating the progress of the operation. After the Asset Strategy
Template is applied to the Asset Strategy, a message appears, indicating that the Asset
Strategy Template was applied successfully.
8. Click OK.
The Asset Strategy returns to focus.
Applying a Template as a Master via the

Master Template Management Page
After an Asset Strategy Template exists, you can apply it to an existing Asset Strategy by:
Using the Apply Template Builder.

Using the Master Template Management page.
These instructions explain how to add an Asset Strategy to a master template using the
Master Template Management page.
To add existing Asset Strategies to a master template:
1. Open the desired Asset Strategy Template.
2. Access the list of Asset Strategies that the template currently controls.
3. On the Master Template Management page, below the grid, click the Add
Existing button.
The Select Asset Strategies to Add to Master Template window appears, displaying the
4. In the Asset Type list, select the family containing the records whose Asset
Strategies you want to add to the master template: Equipment or Functional
Location.
5. Click the Run Query button.
The results are displayed in the grid. The results display:
Asset Strategy records that are linked to an Equipment or Functional

Location record in the selected family but are not linked to an Asset
Strategy Template record through the Master Template Has Asset Strategy
relationship.
Asset Strategy records that are not linked to an Equipment or Functional
Location record and are not linked to an Asset Strategy Template record
through the Master Template Has Asset Strategy relationship.
6. In the search results, select the rows containing the Asset Strategies that you want
to add to the master template.
7. Click the Add Asset Strategies button.
A progress bar appears, indicating the progress of the operation. When the operation is
complete, the selected Asset Strategies appear in the grid on the Master Template
Management page.
Applying a Template as a Master via the

Apply Template Builder
Review.
You cannot apply a template as a master to an Asset Strategy that contains Mandatory
Action records.
To apply a Template as a master while viewing the Asset Strategy Template:
1. Open the Asset Strategy Template that you want to apply as a master to existing
Asset Strategies.


6. To apply this Asset Strategy Template to Asset Strategies for specific pieces of
equipment or locations, accept the default selection, Search by Asset.
-orTo apply this Asset Strategy Template to specific Asset Strategies, select the Search by
Asset Strategy option.
7.
o
If you selected the Search by Asset option on the previous screen, the
Search In list displays a list of families that are predecessors in the Has
Strategy relationship.
If you selected the Search by Asset Strategy option on the previous screen,
the Asset Type list displays a list of families that contain a record that is
already linked to an Asset Strategy record.
o
If you selected the Apply the template as a copy option on the

results of the query Asset_Strategy_Search_Non_Pending.
If you selected the Apply the template as a master option on the
8. If you see the Search In list, select the family containing the records that are
linked to Asset Strategy records to which you want to apply this template:
Equipment or Functional Location. The search results will display all records in
that family. If desired, you can also use the options on the Advanced Search tab to
refine the search criteria using an Advanced Search.
-orIf you see the Asset Type list, select the family containing the records that are linked to
the Asset Strategy records to which you want to apply this template: Equipment or
If you selected the Apply the template as a copy option on the Template
Application Method screen, the search results display Asset Strategy
records that are linked to an Equipment or Functional Location record in
the selected family and that are not set to the Pending Review state.
If you selected the Apply the template as a master option on the Template
Application Method screen, the search results display:
Non-Pending Review Asset Strategy records that are linked to an

Equipment or Functional Location record in the selected family but
are not linked to an Asset Strategy Template record through the
Master Template Has Asset Strategy relationship.
Non-Pending Review Asset Strategy records that are not linked to
an Equipment or Functional Location record and are not linked to
an Asset Strategy Template record through the Master Template
Has Asset Strategy relationship.
9. Click the Find Now button or the Run Query button, whichever is available.
If you select Equipment or Functional Location records, this template will be applied to
the Asset Strategies for those pieces of equipment or locations.
-orIf you select Asset Strategy records, this template will be applied to those Asset
Strategies.
selections.
The Asset Strategy Template is applied to the Strategy.
Creating New Asset Strategies as

Controlled Strategies of a Master
Template
The following instructions provide details on creating one or more Asset Strategies from
an Asset Strategy Template that is applied as a master. The number of Asset Strategies
that will be created is determined by the number of Equipment and Functional Location
records that you select during the creation process.
To create one or more new Asset Strategies as controlled strategy of a master template:
1. Search for and open the Active Asset Strategy Template that you want to use to
create new Asset Strategies.

6. Accept the default selection, Search by Asset, and click the Next button.
The Select Records screen appears. The Search In list displays a list of families that are
predecessors in the Has Strategy relationship.
7. In the Search In list, select the Equipment or Functional Location family
containing the records for which you want to create new Asset Strategies. If
desired, you can also use the options on the Advanced Search tab to refine the
search criteria using an Advanced Search.

This template will be used to create new Asset Strategies for the selected records.
selections.
The Asset Strategy Template is used to create the new Asset Strategies, and the Apply
Asset Strategy Template page appears.
Each row represents an Asset Strategy that was created successfully. The Strategy column
contains a hyperlink, which you can click to access the Asset Strategy Actions page.
Note that in each new Asset Strategy that was created from the template, any Actions or
Risks that exist in the Asset Strategy Template are flagged as new in the Asset Strategy
(their flag will contain a plus symbol). If desired, you can undo this action so that the
Actions and Risks will not be included in the Asset Strategy when the Asset Strategy is
activated.
Viewing the Master Template that

Controls a Specific Asset Strategy
To open an Asset Strategy's master template while viewing the Asset Strategy:
While viewing the Asset Strategy, on the Template Tasks menu, click the Go To
Master link.
Removing Strategies from a Master

Template
After an Asset Strategy Template has been applied to an Asset Strategy as a master
template, you can remove the connection between the template and the strategy by:
Opening the Asset Strategy to which the template is applied.
Using the Master Template Management page.
After you remove this connection, you will be able to manage the Asset Strategy at the
strategy level.
To remove an Asset Strategy from a master template while viewing the Asset Strategy:
1. While viewing the Asset Strategy, on the Template Tasks menu, click the Remove
from Master link.
A message appears, asking if you are sure that you want to remove the connection.
The Asset Strategy is removed from the master template.
To remove an Asset Strategy from a master template while viewing the Asset Strategy
Template:
1. Open the desired Asset Strategy Template.
2. Access the list of Asset Strategies that the template currently controls.
3. On the Master Template Management page, in the grid, select the rows containing
the Asset Strategies that you want to remove from the template.
4. Below the grid, click the Remove Selected button.
A message appears, asking if you are sure that you want to remove the connection.
The Asset Strategy is removed from the master template.
Viewing a List of Strategies that a

Master Template Controls
To access a list of Asset Strategies that a master Asset Strategy Template controls:
1. Open the Asset Strategy Template that serves as the master of one or more Asset
Strategies.
2. On the Navigation menu, click the Controlled Strategies link.
The Master Template Management page appears.
Aspects of the Master Template

Management Page
The Master Template Management page contains the Controlled Asset Strategies grid,
which displays a list of Asset Strategies that are controlled by the Asset Strategy
Template with which you are currently working.
Each row in the grid represents one Asset Strategy record. The grid contains the
following columns, which displays information about the Asset Strategy:
Strategy ID: The ID of the Asset Strategy.

Description: The description of the Asset Strategy as it appears in the Asset
Strategy record.
Asset Name: The ID of the Asset to which the Asset Strategy is linked.
Asset Type: The name of the family to which the piece of equipment or location
belongs.
Add Existing: Displays the Select Asset Strategies to Add to Master Template
window, where you can search for an existing Asset Strategy record to which you
want to apply the Asset Strategy Template as a master template.
Remove Selected: Displays a confirmation message, asking if you really want to
remove the selected Asset Strategy from the master template, and then removes
the link between the Asset Strategy and the Asset Strategy Template. This button
is enabled only when an Asset Strategy is selected in the grid.
Notes About Health Indicator Records

in Asset Strategy Templates
Note the following about Health Indicator records and Asset Strategy Templates:
When you link a Health Indicator record to an Action record that belongs to an
Asset Strategy Template, you will not be able to link the Health Indicator record
to a source record.
If you create an Asset Strategy Template from an existing Asset Strategy and the
source Asset Strategy contained a Health Indicator record that was linked to a
source record, the Asset Strategy Template will contain a corresponding Health
Indicator record, but it will not be linked to a source record.
Activating Asset Strategy Templates

When you set an Asset Strategy Template state to Active, you indicate that you approve
of the plan and agree with the Actions and Risks. You can set the state to Active if it is
currently Draft or Pending Review. After an Asset Strategy Template state is Active, the
Asset Strategy Template can be applied to Asset Strategies.
To set an Asset Strategy Template state to Active from the Draft state:
1. Search for and open the Asset Strategy Template that you want to activate.

2. On the Navigation menu, click the Review Template link.
The Review Asset Strategy Template page appears.
Note: You can activate an Asset Strategy Template from other pages, such as the Asset
Strategy Template Actions page, but these instructions assume that want to do so from the
Review Asset Strategy Template page.
and then click Baseline on the submenu.
A message appears, asking if you are sure you want to activate the Asset Strategy
Template even though it has not yet been reviewed.
A message appears, indicating that the Asset Strategy Template is now Active. On the
current workspace, you can see that the Asset Strategy Template state is now Active.
-ORIf the Asset Strategy Template has been applied to one or more Asset Strategies as a
master template, the State Management window appears, listing the Asset Strategies to
which the changes will be applied.
5. Click OK to complete the activation process.
A progress bar appears, indicating the progress of the activation process. When the
progress bar disappears, the Review Asset Strategy Template page returns to focus.
To set an Asset Strategy Template state to Active from the Pending Review state:
1. Search for and open the Asset Strategy Template that you want to activate.
2. On the Navigation menu, click the Review Template link.
The Review Asset Strategy Template page appears.
Note: You can activate an Asset Strategy Template from other pages, such as the Asset
Strategy Template Actions page, but these instructions assume that want to do so from the
Review Asset Strategy Template page.
and then click Make Active on the submenu.
A message appears, asking if you are sure you want to activate the Asset Strategy
Template.
A message appears, indicating that the Asset Strategy Template state is now Active. On
the current workspace, you can see that the Asset Strategy Template state is now Active.
-ORIf the Asset Strategy Template has been applied to one or more Asset Strategies as a
master template, the State Management window appears, listing the Asset Strategies to
which the changes will be applied.
5. Click OK to complete the activation process.
A progress bar appears, indicating the progress of the activation process. When the
progress bar disappears, the Review Asset Strategy Template page returns to focus.
About Reviewing Recent Changes

Awaiting Approval
You can review recent changes that have been made to an Asset Strategy Template to
determine whether or not you want to:
Approve the changes and activate the Asset Strategy Template.
-OR
Send the Asset Strategy Template back for revision.
You can perform this review process from the Review Asset Strategy Template page.
You can use this page to review the following items:
A detailed view of any changes that have been made between an Action that
belongs to the Active Strategy Template and the corresponding Action that
belongs to the Proposed Strategy Template.
The reason that changes were made to the Asset Strategy Template.
Strategy Templates.
Graphs
Asset Strategy Template graphs function the same way that Asset Strategy graphs
function. For example, the Risk Profile graph in the Risk Analysis represents data in the
Active Asset Strategy Template and in the Proposed Asset Strategy Template.
Accessing an Asset Strategy from the

To access an Asset Strategy from the System Strategy overview:
1. Access the System Strategy overview for the desired System Strategy.
2. In the Active Asset Strategies section below the graphs, in the row containing the
Asset Strategy that you want to access, click the hyperlinked Strategy ID.
The selected Asset Strategy appears on the Asset Strategy Overview page appears.
Adding New Asset Strategies to a

System Strategy
To add new Asset Strategies to a System Strategy:
1. Access the System Strategy Management page.
2. At the bottom of the page, click the Create New button.
The Asset Strategy Definition page appears.
3. Create the Asset Strategy record for the Asset Strategy that you want to add to the
System Strategy.
4. Continue building the Asset Strategy by:
Creating Risks.
Creating Actions.
The Asset Strategy is added to the System Strategy.

5. On the site map, click the <System Strategy ID> link. For example, if the ID of
the System Strategy is Electrical System Strategy, the link on the site map will be
Electrical System Strategy.
The ASM - System Strategy Overview - <Strategy ID> page appears, where <Strategy
ID> is the ID of the System Strategy that you selected on the site map.
6. To see that the records have been linked, on the Navigation menu, click the
Manage System link.
The newly created Asset Strategy appears in the list.
Adding Existing Asset Strategies to a

System Strategy
Note: The Meridium APM system will allow you to add multiple Asset Strategies to a
System Strategy only if all the underlying pieces of equipment and locations belong to
the same site.
To add existing Asset Strategies to a System Strategy:
2. At the bottom of the page, click the Add Existing button.
The Find Items window appears. The Search In list is populated automatically with Asset
Strategy.
The search results appear in the grid below the search criteria.
4. Select the rows containing the Asset Strategies that you want to add to the System
Strategy.
5. Click the Open button.
The Selected Asset Strategies appear in the list on the System Strategy Management
page.
Removing Asset Strategies from a

System Strategy
To remove Asset Strategies from a System Strategy:
2. In the grid, select the rows containing the Asset Strategies that you want to
remove from the System Strategy.
3. At the bottom of the page, click the Remove Selected button.
A message appears, asking if you are sure you want to remove the selected Asset
Strategies from the System Strategy.
The selected Asset Strategies are removed from the System Strategy.
Excluding Actions Via the Risk Analysis

When you are viewing the Risk Analysis for a System Strategy, you can see a list of
Actions that are included in all underlying Proposed Strategies. You can also use the
graphs to interpret the effects of performing those actions.
If desired, via the Risk Analysis, you can exclude certain Actions from the System
Strategy. Using the graphs, you can see the impact of excluding those Actions. Based on
the data in the graphs, you can decide if you want to mark the Actions for deletion.
Note: You can exclude an Action only if its Mandatory check box is cleared and the
Action does not belong to an Asset Strategy that is controlled by a master template.
To exclude Actions via the System Strategy Risk Analysis:
1. In the grid in the Actions section, in the row containing the Action that you want
to exclude, clear the Selected Action check box.
Hint: To exclude multiple Actions, you can use the CTRL or SHIFT key to select multiple
rows at once. If you then clear the Selected Action check box in any of the selected rows,
the Selected Action check box will be cleared in all remaining selected rows.
Note: If you excluded an Action that belongs to an Asset Strategy whose state is set to
Pending Review, a message appears, indicating that those Actions cannot be excluded
from the System Strategy.
If the associated Asset Strategy has not been activated since the selected Action was
created or last updated, the Action is removed from the grid, and the Action record is
deleted from the database.
-ORIf the associated Asset Strategy was activated after the Action was created or last updated,
the Action records are flagged for deletion but not removed from the grid.

System Strategy
To specify the reason for changing the System Strategy:
1. On the System Strategy Risk Analysis page below the grid in the Actions section,
changes that you have made to the System Strategy.
3. Click OK.
The Apply Revision to Selected Strategies window appears.
In the grid, in the rows containing the Asset Strategies to which you want to apply the
basis for revision, select the Selected check box
4. Click OK.
The text is saved and can be seen when you review the underlying Asset Strategies.

Action
1. On the System Strategy Risk Analysis page, click the Details tab.
A grid appears, displaying a list of Actions that belong to the underlying Proposed Asset
Strategy.
selected Action and the corresponding Action that belongs to the Active Strategy.
Interpreting the Running Total

The Running Total column in the Actions section contains a value representing the total
yearly cost of implementing the Action represented by that row and all selected Actions
in the rows above it.
In other words:
Running Total = Yearly cost of Action in that row + Yearly cost of Selected Actions in
each previous row
For example, suppose the first row contains the following data:
Cost = 100.00
Interval = 1
Interval Units = Years
In this case, the yearly cost of implementing this Action is $100.00.

Suppose the second row contains the following data:
Cost = 200.00
Interval = 6
Interval Units = Months
In this case, because the Action is performed every six months, or twice a year, the yearly
cost of implementing this Action is $400.00 ($200.00 X 2).
Using this example, the Running Total value in the second row would be calculated as:
Running Total = $400.00 + $100.00
Running Total = $500.00
So, the Running Total value displayed in the second row would be 500.00
About Reviewing a System Strategy

You can review a System Strategy to determine whether or not you want to approve the
information and activate the underlying Asset Strategies. You can perform this review
process from the Review System Strategy page.
You can use this page to:
Review the list of non-Active Asset Strategies that are included in the System
Strategy. From this list, you can click a hyperlink to access any of the Asset
Strategies.
Manage the states of the underlying non-Active Asset Strategies.
Review the Risk Profile graph.
Review the Financial Risk Exposure graph.
Review the Cost of Actions graph.
About Managing Asset Strategy States

from a System Strategy
When you are viewing the Review System Strategy page, you can see a list of all
underlying Asset Strategies that are set to a state other than Active. From this page, you
can:
Assign a Security User to an Asset Strategy state. Doing so will set this Security
User as the assignee of that state in ALL underlying Asset Strategies that are
transferred to that state. For example, if you assign John Smith to the Active state
from this page, when you transfer all underlying Asset Strategy to the Active state
from the Review System Strategy page, John Smith will continue to be assigned
to the Active state in those Asset Strategies.
Note that the Security User who changes the states of multiple Asset Strategies using this
page will be set automatically as the assignee of the state from which they were changed.
For example, if Mary Jones is logged in and changes the state of Pending Review Asset
Strategies to the Active state, Mary Jones will become the assignee of the Pending
Review state in those Asset Strategies, even if another Security User was previously
assigned to the Pending Review state of those Asset Strategies.
Any state assignments that you define via the Review System Strategy page do not persist
if you navigate away from this page before you change the state of any underlying Asset
Strategy.
Hint: If State Configuration for the Asset Strategy family is configured as such, a
Security User must also be assigned to the successor state before a Security User can
transition a record to that state.
Change the states of multiple underlying Asset Strategies at one time.
To facilitate this workflow, the Review System Strategy page contains the following
items:
System Level State Management section: Contains the following items:
Assignments button: Displays the State Assignments dialog box, where

you can assign Security Users to any state that exists in the State
Configuration that is defined for the Asset Strategy family.
State list: Displays all current states of the underlying Asset Strategies,
except for Active. For example, if the System Strategy contains Draft,
Pending Review, and Active Asset Strategies, the list contains the values
Draft and Pending Review.
Operations list: Displays the operations that can be used to transition the
Asset Strategies that are set to the predecessor state that appears in the
State list. For example, if the State list contains the value Pending Review,
the list contains the values Make Active and Rework since these are the
only operations that contain the Pending Review predecessor state. The
predecessor state is determined by the Asset Strategy State Configuration.
Apply button: Transitions ALL underlying Asset Strategies that are set to
the selected state to a successor state using the selected operation. The
successor state is determined by the Asset Strategy State Configuration.
Note: Security Users belonging to the MI ASM Viewer Security Group will not see the
System Level State Management section and thus cannot manage Asset Strategy states
from a System Strategy.
Asset Strategies section: Displays a grid containing a list of all non-Active Asset
Strategies that are included in the System Strategy.
The following image shows the sections described in the preceding list.
Assigning a Security User to an Asset

Strategy State
To assign a Security User to a state that is defined in the State Configuration for the Asset
Strategy family:
1. Access the Review System Strategy page for the System Strategy whose
underlying Asset Strategies are set to a state to which you want to assign a
Security User.
2. In the System Level State Management section, click the Assignments button.
The State Assignments window appears.

3. Select the row containing the state to which you want to assign a Security User.
4. In the selected row, in the Assigned User list, select the Security User that you
want to assign to the state.
5. Click OK.
The Security User is assigned to the state. This Security User will now be able to
transition ALL underlying Asset Strategies from the assigned state to a successor state.
Note, however, that this state assignment does not persist if you navigate away from this
page before you transition the Asset Strategies that are set to the assigned state.
transition an Asset Strategy to that state.
Changing the State of Multiple

Underlying Asset Strategies
Note: If you do not belong to the State Configuration Role that is assigned to a state, the
Operations list will be empty when that state is selected in the States list. State
Configuration Roles are assigned to states via the Configuration Manager. For example,
suppose the MI ASM Administrator State Configuration Role is assigned to the Pending
Review state. If you are not a member of this State Configuration Role, the Make Active
operation will not appear in the Operations list when the Pending Review state is selected
in the States list.
To select the state of the Asset Strategies whose state you want to change:
1. Access the Review System Strategy page for the System Strategy containing the
Asset Strategies whose state you want to change.
2. In the System Level State Management section, in the State list, select the state of
the Asset Strategies that you want to transition to a different state. For example, if
you want to change all underlying Draft Asset Strategies to Active, select Draft.
3. In the Operations list, select the operation that you want to perform on the Asset
Strategies that are set to the state that appears in the State list. For example, if you
want to change all underlying Draft Asset Strategies to Active using the Baseline
operation, select Baseline.
4. Click the Apply button.
A message appears, indicating the number of Asset Strategies on which the selected
operation will be performed and asking if you want to continue with the operation.
The State Transition dialog box appears, indicating the progress of the operation. When
the operation is complete, the Asset Strategies that were set to the selected state are set to
a new state using the selected operation.

The Risk Profile graph is available on the following pages:
System Strategy Overview: Represents data in only the Active Strategies that are
included in the System Strategy.
System Strategy Risk Analysis: Represents data in the Asset Strategies that are
anything other than Active.
Review System Strategy: Represents data in all Asset Strategies that are included
in the System Strategy.

the Overview
The Risk Profile graph that appears on the System Strategy Overview page represents
data in the Active Strategies that are included in the System Strategy.
The following image shows an example of the Risk Profile graph in the System Strategy
overview.
The Risk Profile graph displays a profile of the risk rank values for all Risks that belong
to each Active Strategy. The graph contains a line that represents the highest unmitigated
risk rank of all Risks that belong to each Active Strategy. The gray bar represents the
highest Strategy Mitigated Risk Rank for all Risks that belong to each Active Strategy.
From the example graph in the preceding image, you can determine from the six
datapoints on the Unmitigated line that the System Strategy contains six Active
Strategies.
each Active Asset Strategy. For example, consider the following graph, which shows the
highest unmitigated risk across all risk categories, 500.1, for the Asset Strategy PMP4543.
You would see this value in the Unmitigated Risk Rank column in the Risks section on
the Asset Strategy Risks - PMP-4543 page, as shown in the following image. (A black
arrow has been added to call out the value.)
Environment risk category, it would look like the graph in the following image.
In this image, you can see that the highest Environment risk included in Asset Strategy
PMP-4543 is 3.
Note: If you filter the graph to show risk ranks values for a specific risk category, the
From this graph, you can see that the highest unmitigated risk rank across all Risks for
the last Active Strategy is 500. Likewise, the highest Strategy Mitigated Risk Rank across
all Risk records for this Active Strategy is 150.
If you were to view the Asset Strategy Risks page for the first Active Strategy, you would
see these same values in the Unmitigated Risk Rank and Strategy Mitigated Risk Rank
columns in the Risks section.
Strategy Mitigated Risk Rank values. To do so, below the x-axis, select the Active option.
Note that you can also click any datapoint on the graph to open the Asset Strategy
Overview page for the Asset Strategy that is represented by the clicked datapoint.

the Risk Analysis
The Risk Profile graph that appears on the System Strategy Risk Analysis page represents
data in all Asset Strategies that are included in the System Strategy.
The following image shows an example of the Risk Profile graph in the System Strategy
overview.
The highest Strategy Mitigated Risk Rank value across all Risks that belong to the
Active Strategy. These values are displayed on the line with the circles.
The highest projected, or proposed, Strategy Mitigated Risk Rank value across all
Risks that belong to the Proposed Strategy. These values are displayed on the
vertical bars. As you make changes to the Asset Strategies, changing their state to
Modified, those changes are reflected in the bars on the graph.
The highest unmitigated risk rank value across all Risks that belong to the Active
Strategy record. These values are displayed on the line with the triangles.
From the example graph in the preceding image, you can determine from the six
datapoints on each line that the System Strategy contains six Asset Strategies.
each Asset Strategy. For example, consider the following graph, which shows the highest
unmitigated risk across all risk categories, 500.1, for the Asset Strategy PMP-4543.
You would see this value in the Unmitigated Risk Rank column in the Risks section on
the Asset Strategy Risks - PMP-4543 page, as shown in the following image. (A black
arrow has been added to call out the value.)
Environment risk category, it would look like the graph shown in the following image.
In this image, you can see that the highest Environment risk included in Asset Strategy
PMP-4543 is 3.
Note: If you filter the graph to show risk ranks values for a specific risk category, the
From this graph, you can see that the highest unmitigated risk rank across all Risks for
the fourth Asset Strategy is 500.1 (rounded to 500 in the label on the graph). Likewise,
the highest Strategy Mitigated Risk Rank across all Risk records for this Asset Strategy is
150.1 (rounded to 150 in the label on the graph).
If you were to view the Asset Strategy Risks page for the fourth Asset Strategy, you
would see these same values in the Unmitigated Risk Rank and Strategy Mitigated Risk
Rank columns in the Risks section, as shown in the following image.
proposed or active Strategy Mitigated Risk Rank values. To do so, below the x-axis,
select the Proposed or Active option.
Note that you can also click any datapoint on the graph to open the Asset Strategy Risk
Analysis page for the Asset Strategy that is represented by the clicked datapoint.
Interpreting the Risk Profile Graph on

the Review Page
The Risk Profile graph that appears on the Review System Strategy page represents data
in all included Asset Strategies in any state except Active.
The following image shows an example of the Review System Strategy page.
The highest Strategy Mitigated Risk Rank value across all Risks that belong to
each Asset Strategy. These values are displayed on the line with the circles.
The highest projected, or proposed, Strategy Mitigated Risk Rank value across all
Risks that belong to each Proposed Strategy. These values are displayed on the
vertical bars. As you make changes to an Asset Strategy, changing its state to
Modified, those changes are reflected in the bars on the graph.
The highest unmitigated risk rank value across all Risks that belong to each
Active Strategy. These values are displayed on the line with the triangles.
From the example graph in the preceding image, you can determine from the two
datapoints on each line that the System Strategy contains two Asset Strategies.
the graph to determine the exact risk rank values. The following image shows the
Note that in some cases, displaying the datapoint values might cause the values to
overlap. If this happens, you can pause on a line or a bar to see only the datapoint values
on that line or bar.
From the example graph, you can see that:
The highest unmitigated risk rank across all Risks in the first Asset Strategy is
2500.
Currently, the highest Strategy Mitigated Risk Rank across all Risks in the first
Asset Strategy is 301.
The Asset Strategy has been modified in some way (e.g., an Action's Mitigated
Risk Rank has been reduced, an Action has been removed, etc.) The vertical bar
represents the highest projected Strategy Mitigated Risk Rank assuming that these
changes are accepted and the Asset Strategy state becomes Active without the
changes being reversed. In this example, the highest projected, or proposed,
Strategy Mitigated Risk Rank is 31.
If you were to view the Asset Strategy Risks page for the first Asset Strategy, you would
see these values for the Risks records in the Unmitigated Risk Rank and Strategy
Mitigated Risk Rank columns in the Risks section.
In the preceding image, you can see that the highest unmitigated risk rank is 2500, which
is displayed on the Unmitigated line in the graph. You can also see that the highest
Strategy Mitigated Risk Rank is 30.6, which is rounded and displayed as 31 on the
Proposed bar on the graph.
graph from left to right. In other words, the Unmitigated line always slopes down to the
right in the default view of the graph.
Note that you can also click any datapoint on the graph to open the Review Asset
Strategy page for the Asset Strategy that is represented by the clicked datapoint.
About the Financial Risk Exposure

Graph
The Financial Risk Exposure graph is available on the following pages:

The Financial Risk Exposure graph that is displayed on the System Strategy Overview
page represents data in only the Active Strategies that are included in the System
Strategy. The Financial Risk Exposure graph that is displayed on the Review System
Strategy page, however, represents data in the Asset Strategies that are anything other
than Active.

Exposure Graph in the Overview
The Financial Risk Exposure graph that appears on the System Strategy Overview page
represents data in only the Active Strategies that are included in the System Strategy.
System Strategy overview.
The Financial Risk Exposure graph displays the financial risk rank associated with all
Risks that belong to each Active Strategy that is included in the System Strategy. For
each Asset Strategy, you can see the unmitigated financial risk rank and the mitigated
financial risk rank, which is based on all Actions that are currently included in that Asset
Strategy.
The graph contains two bars, Unmitigated and Active. Each bar is divided into multiple
sections, where each section represents an Active Strategy that is included in the System
Strategy. From the legend, you can determine which Asset Strategy is associated with
which color.
In this example, because each bar contains two sections, you can determine that the
System Strategy contains two Active Strategies.
Within each bar, each section represents the financial risk rank associated with that Asset
Strategy.
Unmitigated Bar
The Unmitigated bar displays the total unmitigated financial risk rank associated with
each Asset Strategy. You can view the individual unmitigated financial risk rank values
for each Risk in the Asset Strategy by using the Risks section of the Asset Strategy Risks
page to access the Unmitigated Risk Assessment window for that Risk. The financial risk
rank is displayed on the Financial tab.
For example, in the following image, you can see that the total unmitigated financial risk
rank for the Asset Strategy Stove Strategy is 160.
If you were to access the Unmitigated Risk Assessment window for each Risk that is
included in the Stove Strategy, you would see that the sum of the values on the Financial
tabs equals 160.
The unmitigated financial risk rank for the first Risk is 60.
The unmitigated financial risk rank for the second Risk is 100.
In this case, the sum of values equals 160, which is reflected on the Financial Risk
Exposure graph.
Active Bar
The Active bar in the Financial Risk Exposure graph displays the sum of the lowest
mitigated financial risk ranks across all Risks that belong to each Active Strategy.
If you were to view all of the Actions for each Risk that belongs to the Active Strategy,
you would see in the Action Mitigated Financial Risk column of the Mitigating Actions
section that the lowest unmitigated financial risk rank across all Actions that are
associated with the first Risk is 5.
The lowest unmitigated financial risk rank across all Actions that are associated with the
second Risk is 2.5, which is rounded to 3 for graphing purposes.
If you add these numbers together, the total value is 8, which is reflected in the Financial
Risk Exposure graph.
Note that you can also click any datapoint on the graph to open the Asset Strategy
Overview page for the Asset Strategy that is represented by the clicked datapoint.

Exposure Graph on the Review Page
The Financial Risk Exposure graph that appears on the Review System Strategy page
represents data in all included Asset Strategies in any state except Active.
The following image shows an example of the Financial Risk Exposure graph on the
Review System Strategy page.
The Financial Risk Exposure graph displays:
The total unmitigated financial risk rank across all Risks that belong to each
Active Strategy. These values are displayed on the Unmitigated bar.
Currently, the sum of the lowest mitigated financial risk ranks across all Risks that
belong to each Active Strategy. These values are displayed on the Active bar.
The sum of the lowest projected, or proposed, mitigated financial risk ranks
across all Risks that belong to each Proposed Strategy, assuming that one or more
changes are made to the Asset Strategies. These values are displayed on the
Proposed bar. As you make changes to the Asset Strategy, changing the state to
Modified, those changes are reflected in the Proposed bar.
Each bar is divided into multiple sections, where each section represents an Asset
Strategy that is included in the System Strategy. From the legend, you can determine
which Asset Strategy is associated with which color.
In this example, because each bar contains two sections, you can determine that the
System Strategy contains two Asset Strategies.
Within each bar, each section represents the financial risk rank associated with that Asset
Strategy.
Unmitigated Bar
The Unmitigated bar displays the total unmitigated financial risk rank associated across
all Risks that belong to the Active Strategy. You can also view the individual unmitigated
financial risk rank value for each Risk by using the Risks section of the Asset Strategy
Risks page to access the Unmitigated Risk Assessment window for that Risk. The
financial risk is displayed on the Financial tab.
For example, in the following image, you can see that the total unmitigated financial risk
If you were to access the Unmitigated Risk Assessment window for each Risk that is
included in the Stove Strategy, you would see that the sum of the values on the Financial
tabs equals 160.
The unmitigated financial risk rank for the first Risk is 60.
The unmitigated financial risk rank for the second Risk is 100.
In this case, the sum of values equals 160, which is reflected on the Financial Risk
Exposure graph.
Active Bar
The Active bar in the Financial Risk Exposure graph displays the sum of the lowest
mitigated financial risk ranks across all Risks that belong to each Active Strategy.
If you were to view all of the Actions for each Risk that is included in the Asset Strategy,
you would see that the lowest unmitigated financial risk rank across all Actions that are
associated with the first Risk is 5.
The lowest unmitigated financial risk rank across all Actions that are associated with the
second Risk is 2.5, which is rounded to 3 for graphing purposes.
If you add these numbers together, the total value is 8, which is reflected in the Financial
Risk Exposure graph.
Proposed Bar
The Proposed bar displays the sum of the lowest projected, or proposed, mitigated
financial risk rank across all Risks for each Asset Strategy, assuming that one or more
changes are made to the Asset Strategy. As you make changes to the Asset Strategy,
changing the state to Modified, those changes are reflected in the Proposed bar.
For example, in the following image, the proposed mitigated financial risk rank for the
Asset Strategy Stove Strategy is 13.
If you were to view this Asset Strategy on the Asset Strategy Risks page, you could see
that the sum of the lowest mitigated financial risk rank across all Risks is 13.
The lowest mitigated financial risk rank for the first Risk in the Stove Strategy is 7.5,
which rounded to 8 for graphing purposes. The lowest mitigated financial risk rank for
the second Risk is 5.
The sum of these numbers, 5 and 8 (rounded from 7.5), is 13, which is reflected in the
graph on the Proposed bar.
Note that you can also click any datapoint on the graph to open the Review Asset
Strategy page for the Asset Strategy that is represented by the clicked datapoint.
The Cost of Actions graph is available on the following pages:

The Cost of Actions graph that is displayed on the System Strategy Overview page
represents data in only the Active Strategies that are included in the System Strategy. The
Cost of Actions graph that is displayed on the Review System Strategy page, however,
represents data in the Asset Strategies that are anything other than Active.

in the Overview
The Cost of Actions graph that appears on the System Strategy Overview page represents
data in only the Active Strategies that are included in the System Strategy.
The following image shows an example of the Cost of Actions graph in the System
Strategy overview.
The Cost of Actions graph displays the cost per year associated with all Actions in all
Active Strategies that belong to the System Strategy.
By default, the graph contains one bar, Active, which is divided into the following
sections:
PM: Represents the total cost per year for Actions with the Action Type TimeBased Maintenance (Preventive) (PM).
CM: Represents the total cost per year for Actions with the Action Type
the Action Type field.
in both Active Strategies is $9,740.00.
If desired, you can modify the graph to display:
The total cost per year for ALL Actions, regardless of their Action Type, that are
included in all Active Strategies that in included in the System Strategy. To do so,
below the x-axis, select the Total option. Selecting this option causes the Active
bar on the graph to contain only one section, where that section represents the
sum of all Actions in all Active Strategies that are included in the System
Strategy.
The total cost per year for all Actions that are included in each Active Strategy,
where the Active bar is divided into sections, where each section represents an
Active Strategy. To do so, below the x-axis, select the Each Strategy option.
Note: If you select the Each Strategy option and the System Strategy contains more than
twelve Asset Strategies, the legend will be hidden.

on the Review Page
The Cost of Actions graph that appears on the Review System Strategy page represents
data in included Asset Strategies in any state except Active.
The following image shows an example of the Cost of Actions graph on the Review
System Strategy page.
The Cost of Actions graph displays the cost per year associated with all Actions in all
non-Active Asset Strategies that are included in the System Strategy.
By default, the graph contains two bars: Active and Proposed. Each bar is divided into the
following sections:
PM: Represents the total cost per year for Actions whose Action Type is TimeBased Maintenance (Preventive) (PM).
CM: Represents the total cost per year for Actions whose Action Type is
Hint: If you view the Action datasheet for any Action, you can see these options in the
Action Type cell.
Active Bar
The Active bar is divided into two sections, where each section represents, for a specific
action type (PM or CM), the total cost per year for all Actions that are included in the
Active version of all Asset Strategies that are included in the System Strategy.
In this example, you can see that the total cost per year for CM Actions that are included
in the Active version of all Asset Strategies that are included in the System Strategy is
$1,141.00.
Hint: The color of the bars has been modified in this image to make the labels easier to
see.
Proposed Bar
As you make changes to an Asset Strategy, causing its state to change to Modified, any
changes that you make to an Action's cost will be reflected in the Proposed bar.
In the following image, you can see that the proposed total cost per year for all Actions in
all Asset Strategies that are included in the System Strategy is $595.00.

The Cost Projection graph is available on the following pages:

System Strategy Risk Analysis
The Cost Projection graph that is displayed on the System Strategy Overview page
represents data in the Active Strategy only. The Cost Projection graph that is displayed on
the other two pages, however, represents data in the Active Strategy and in the Proposed
Strategy.

in the Overview
The Cost Projection graph that appears on the System Strategy Overview page represents
data in only the Active Strategies that are included in the System Strategy.
The following image shows an example of the Cost Projection graph in the System
Strategy Overview.
The Cost Projection graph displays the cost per year of all Actions that are included in all
underlying Active Strategies and that fall within the planning period. The planning period
is the shortest plan length across all underlying Active Strategies.
Note: If none of the underlying Active Strategies have a plan length, the Cost Projection
graph will use a plan length of one year.
For example, if the System Strategy contains three Active Strategies with Plan Lengths of
five years, seven years, and ten years, the Cost Projection graph in the System Strategy
will represent the five-year plan length. In other words, the graph will contain five bars.
You can use the Total, Action Type, and Each Strategy options to show the yearly cost of
all Actions, the yearly cost of Actions by Action type, or the yearly cost of Actions by
Asset Strategy.
From the legend, you can determine which Action type or Asset Strategy is associated
with which color.
Note: If you select the Each Strategy option and the System Strategy contains more than
twelve Active Strategies, the legend will be hidden.
datasheet.
every year for the length of the plan (determined from the shortest plan length of all
underlying Asset Strategies). Regardless of the plan length, the cost will be incurred
every year.
cost $200.00 three years from today (the fourth year of the plan). If the plan length is five
years, that $200.00 will not be incurred again during the plan.

The Cost Projection graph represents data in all Asset Strategies that are included in the
System Strategy.
The following image shows an example of the Cost Projection graph.
The Cost Projection graph displays the cost per year of all Actions that are included in the
underlying Asset Strategies and that fall within the planning period. The planning period
is the shortest plan length across all underlying Asset Strategies.
Note: If none of the underlying Asset Strategies have a plan length, the Cost Projection
graph will use a plan length of one year.
For example, if the System Strategy contains three Asset Strategies with Plan Lengths of
five years, seven years, and ten years, the Cost Projection graph in the System Strategy
will represent the five-year plan length. In other words, the graph will contain five bars.
You can display the cost of Actions for all Proposed Asset Strategies or for all Active
Asset Strategies by selecting the appropriate option below the graph: Show Proposed or
Show Active.
datasheet.
every year for the length of the plan (determined from the shortest plan length of all
underlying Asset Strategies). Regardless of the plan length, the cost will be incurred
every year.
cost $200.00 three years from today. If the plan length is five years, that $200.00 will not
be incurred again during the plan.
Example of the Cost Projection Graph

in the Risk Analysis
Consider the following Asset Strategies.
Strategy A (Plan Length = 5 years)
Action Cost ($) Interval Interval Units Recurring?
Action 1 200
Years
No
Action 2 100
Years
Yes
Strategy B (Plan Length = 7 years)

Action Cost ($) Interval Interval Units Recurring?
Action 1 50
Years
Yes
Action 2 75
Years
No
If these Asset Strategies are included in a System Strategy, the plan length used in the
System Strategy would be five years, since this is the shortest plan length between the
two Asset Strategies.
The Cost Projection graph would look like the graph shown in the following image.
Year 1
Year 1 of the plan shows a cost of $150.00. which is a combination of the cost of all
Actions that occur that year. Based on the preceding tables, you can see that the following
Actions occur in year 1:
Action 2 from Asset Strategy A
Action 1 from Asset Strategy B
Remember that the total cost for year 1 is calculated as:

Cost for Year 1 = Combined cost of all Actions that occur that year
...so:
Cost for Year 1 = Cost of Action 2 from Asset Strategy A + Cost of Action 1 from Asset
Strategy B
Given the following values:
Cost of Action 2 from Asset Strategy A = $100.00
Cost of Action 1 from Asset Strategy B = $50.00
...the total cost for year 1 is calculated as follows:
Cost for Year 1 = $100.00 + $50.00
Cost for Year 1 = $150.00
Year 2
Year 2 of the plan shows a cost of $225.00, which is a combination of the cost of all


...so:
Strategy B + Cost of Action 2 from Asset Strategy B

Cost for Year 2 = $100.00 + $50.00 + $75.00
Year 3

...so:
Strategy B + Cost of Action 1 from Asset Strategy A

Cost for Year 3 = $100.00 + $50.00 + $200.00
Year 4


...so:
Strategy B + Cost of Action 2 from Asset Strategy B

Cost for Year 2 = $100.00 + $50.00 + $75.00
Year 5
Year 5 of the plan shows a cost of $150.00. which is a combination of the cost of all

...so:
Strategy B
Cost for Year 5 = $100.00 + $50.00

Accessing Implementation Packages

Associated with Any Underlying Asset
Strategy
If a System Strategy is linked to an Asset Strategy record that is linked to an
Implementation Package record, you can access that Implementation Package record
from the System Strategy.
To access an Implementation Package record from a System Strategy:
1. Open the System Strategy that is linked to the Asset Strategy whose linked
Implementation Package record you want to view.
The Implementation Package List page appears, displaying a list of Implementation
Package records that are linked to any Asset Strategy record that is linked to the System
Strategy record.
Adding a New System Strategy to a Unit

Strategy
To add a new Asset Strategy to a System Strategy:
1. Access the Unit Strategy Management page.
2. At the bottom of the page, click the Create New button.
The System Strategy Definition page appears.
3. Create the System Strategy record for the System Strategy that you want to add to
the Unit Strategy.
4. On the site map, click the <Unit Strategy ID> link. For example, if the ID of the
Unit Strategy is Unit A Strategy, the link on the site map will be Unit A.
The System Strategy is added to the Unit Strategy, and the Unit Strategy Overview <Strategy ID> page appears, where <Strategy ID> is the ID of the Unit Strategy that you
selected on the site map.
5. To see that the System Strategy has been added, on the Navigation menu, click the
Manage Unit link.
The newly created System Strategy appears in the list.
Adding Existing System Strategies to a

Unit Strategy
Note: The Meridium APM system will allow you to add multiple System Strategies to a
Unit Strategy only if all the underlying pieces of equipment and locations belong to the
same site.
To add existing System Strategies to a Unit Strategy:
2. At the bottom of the page, click the Add Existing button.
The Find Items window appears. The Search In list is populated automatically with
System Strategy.
The search results appear in the grid below the search criteria.
4. Select the rows containing the System Strategies that you want to add to the Unit
Strategy record.
The selected System Strategies appear in the list on the Unit Strategy Management page.
Removing System Strategies from a Unit

Strategy
To remove a System Strategy from a Unit Strategy:
2. In the grid, select the rows containing the System Strategies that you want to
remove from the Unit Strategy.
3. At the bottom of the page, click the Remove Selected button.
A message appears, asking if you are sure you want to remove the selected System
Strategies from the Unit Strategy.
The selected System Strategies are removed from the Unit Strategy record.
Excluding Actions Via the Risk Analysis

When you are viewing the Risk Analysis for a Unit Strategy, you can see a list of Actions
that are included in all underlying Proposed Strategies. You can also use the graphs to
interpret the effects of performing those actions.
If desired, via the Risk Analysis, you can exclude certain Actions from the Unit Strategy.
Using the graphs, you can see the impact of excluding those Actions. Based on the data in
the graphs, you can decide if you want to mark the Actions for deletion.
Note: You can exclude an Action only if its Mandatory check box is cleared and the
Action does not belong to an Asset Strategy that is controlled by a master template.
To exclude Actions via the Unit Strategy Risk Analysis:
1. In the grid in the Actions section, in the row containing the Action that you want
to exclude, clear the Selected Action check box.
Hint: To exclude multiple Actions, you can use the CTRL or SHIFT key to select multiple
rows at once. If you then clear the Selected Action check box in any of the selected rows,
the Selected Action check box will be cleared in all remaining selected rows.
Note: If you excluded an Action that belongs to an Asset Strategy whose state is set to
Pending Review, a message appears, indicating that those Actions cannot be excluded
from the Unit Strategy.
If the associated Asset Strategy has not been activated since the selected Action was
created or last updated, the Action is removed from the grid, and the Action record is
-ORIf the associated Asset Strategy was activated after the Action was created or last updated,
the Action records are flagged for deletion but not removed from the grid.

Unit Strategy
To specify the reason for changing the Unit Strategy:
1. On the Unit Strategy Risk Analysis page, below the grid in the Actions section,
changes that you have made to the System Strategy.
3. Click OK.
The Apply Revision to Selected Strategies window appears.
In the grid, in the rows containing the Asset Strategies to which you want to apply the
basis for revision, select the Selected check box
4. Click OK.
The text is saved and can be seen when you review the underlying Asset Strategies.

Action
1. On the Unit Strategy Risk Analysis page, click the Details tab.
A grid appears, displaying a list of Actions that belong to the underlying Proposed Asset
Strategy.
selected Action and the corresponding Action that belongs to the Active Strategy.
About Reviewing a Unit Strategy

You can review a Unit Strategy from the Review Unit Strategy page.
You can use this page to:
Review the list of System Strategies whose Asset Strategies are in a state other
than Active. The list of System Strategies is displayed on the System Strategies
tab. From this list, you can click any hyperlink to access the System Strategy.
Review the list of all underlying Asset Strategies. The list of Asset Strategies is
displayed on the Asset Strategies tab. From the list, you can click any hyperlink to
access the Asset Strategy.
Manage the states of the underlying non-Active Asset Strategies.
Review the Risk Profile graph.
Review the Financial Risk Exposure graph.
Review the Cost of Actions graph.
About Managing Asset Strategy States

from a Unit Strategy
When you are viewing the Review Unit Strategy page, you can see a list of all underlying
Asset Strategies that are set to a state other than Active. From this page, you can:
Assign a Security User to an Asset Strategy state. Doing so will allow this
Security User to transition ALL underlying Asset Strategies from the assigned
state to a successor state. Note, however, that this state assignment does not
persist if you navigate away from this page before you transition the Asset
Strategies that are set to the assigned state.
Hint: If the State Configuration for the Asset Strategy family is configured as such, a
transition a record to that state.
Change the states of multiple underlying Asset Strategies at one time.
To facilitate this workflow, the Review Unit Strategy page contains the following items:
Unit Level State Management section: Contains the following items:
Assignments button: Displays the State Assignments dialog box, where

you can assign Security Users to any state that exists in the State
Configuration that is defined for the Asset Strategy family.
State list: Displays all current states of the underlying Asset Strategies,
except for Active. For example, if the Unit Strategy contains Draft,
Pending Review, and Active Asset Strategies, the list contains the values
Draft and Pending Review.
Operations list: Displays the operations that can be used to transition the
Asset Strategies that are set to the predecessor state that appears in the
State list. For example, if the State list contains the value Pending Review,
the list contains the values Make Active and Rework since these are the
only operations that contain the Pending Review predecessor state. The
predecessor state is determined by the Asset Strategy State Configuration.
Apply button: Transitions ALL underlying Asset Strategies that are set to
the selected state to a successor state using the selected operation. The
successor state is determined by the Asset Strategy State Configuration.
Note: Security Users belonging to the MI ASM Viewer Security Group will not see the
Unit Level State Management section and thus cannot manage Asset Strategy states from
a Unit Strategy.
Asset Strategies section: Displays a grid containing a list of all underlying System
Strategies that contain non-Active Asset Strategies.
These sections are displayed in the following image.
Assigning a Security User to an Asset

Strategy State
To assign a Security User to a state that is defined in the State Configuration for the Asset
Strategy family:
1. Access the Review Unit Strategy page for the Unit Strategy whose underlying
Asset Strategies are set to a state to which you want to assign a Security User.
2. In the Unit Level State Management section, click the Assignments button.
The State Assignments window appears.
3. Select the row containing the state to which you want to assign a Security User.
4. In the selected row, in the Assigned User list, select the Security User that you
want to assign to the state.
5. Click OK.
The Security User is assigned to the state. This Security User will now be able to
transition ALL underlying Asset Strategies from the assigned state to a successor state.
Note, however, that this state assignment does not persist if you navigate away from this
page before you transition the Asset Strategies that are set to the assigned state.
transition an Asset Strategy to that state.
Changing the State of Multiple

Underlying Asset Strategies
Note: Security Uses belonging to the MI ASM Analyst Security Group cannot set Asset
Strategies to the Active state from the Pending Review state using the Unit Level State
Management features. This means that if you are logged in as a member of this Security
Group and see the Pending Review state in the State list, the Make Active operation will
not appear in the Operations list.
To select the state of the Asset Strategies whose state you want to change:
1. Access the Review Unit Strategy page for the Unit Strategy containing the Asset
Strategies whose state you want to change.
2. In the Unit Level State Management section, in the State list, select the state of
the Asset Strategies that you want to transition to a different state. For example, if
you want to change all underlying Draft Asset Strategies to Active, select Draft.
3. In the Operations list, select the operation that you want to perform on the Asset
Strategies that are set to the state that appears in the State list. For example, if you
want to change all underlying Draft Asset Strategies to Active using the Baseline
operation, select Baseline.
4. Click the Apply button.
A message appears, indicating the number of Asset Strategies on which the selected
operation will be performed and asking if you want to continue with the operation.
The State Transition dialog box appears, indicating the progress of the operation. When
the operation is complete, the Asset Strategies that were set to the selected state are set to
a new state using the selected operation.

The Risk Profile graph that is displayed when you are viewing a Unit Strategy is similar
to the Risk Profile graph that is displayed when you are viewing a System Strategy.
While the graphs for a System Strategy display data based on the underlying Asset
Strategies, the graphs for a Unit Strategy display data based on the underlying System
Strategies.
Use the information in this documentation about interpreting the Risk Profile graph for
System Strategies to gain an understanding of the type of data that the graph displays.
Then, use this information to interpret the Risk Profile graph for Unit Strategies.
About the Financial Risk Exposure

Graph
The Financial Risk Exposure graph that is displayed when you are viewing a Unit
Strategy is similar to the Financial Risk Exposure graph that is displayed when you are
viewing a System Strategy. While the graphs for a System Strategy display data based on
the underlying Asset Strategies, the graphs for a Unit Strategy display data based on the
underlying System Strategies.
Use the information in this documentation about interpreting the Financial Risk Exposure
graph for System Strategies to gain an understanding of the type of data that the graph
displays. Then, use this information to interpret the Financial Risk Exposure graph for
Unit Strategies.
The Cost of Actions graph that is displayed when you are viewing a Unit Strategy is
similar to the Cost of Actions graph that is displayed when you are viewing a System
Strategy. While the graphs for a System Strategy display data based on the underlying
Asset Strategies, the graphs for a Unit Strategy display data based on the underlying
System Strategies.
Use the information in this documentation about interpreting the Cost of Actions graph
for System Strategies to gain an understanding of the type of data that the graph displays.
Then, use this information to interpret the Cost of Actions graph for Unit Strategies.

The Cost Projection graph that is displayed when you are viewing a Unit Strategy is
similar to the Cost Projection graph that is displayed when you are viewing a System
Strategy. While the graphs for a System Strategy display data based on the underlying
Asset Strategies, the graphs for a Unit Strategy display data based on the underlying
System Strategies.
Use the information in this documentation about interpreting the Cost Projection graph
for System Strategies to gain an understanding of the type of data that the graph displays.
Then, use this information to interpret the Cost Projection graph for Unit Strategies.
Accessing Implementation Packages

Associated with Any Underlying Asset
Strategy
If a Unit Strategy's underling Asset Strategy record is linked to an Implementation
Package record, you can access that Implementation Package record from the Unit
Strategy.
To access an Implementation Package record from a Unit Strategy:
1. Open the Unit Strategy whose underlying Asset Strategy record is to the
Implementation Package record that you want to view.
The Implementation Package List page appears, displaying a list of Implementation
Package records that are linked to any underlying Asset Strategy record.
About Saving Strategies

When you are viewing a strategy on any page other than a strategy definition page, you
will notice that a Save link is not available on the Common Tasks menu. In ASM,
changes that you make on pages other than a strategy definition page are saved
automatically.
When you are working with an Asset Strategy, your changes are saved automatically to
either:
The Proposed Strategy record or a record to which it is linked.
-OR
The Active Strategy record or a record to which it is linked.
For example, if you are working with a new Asset Strategy that has never been activated
and you add an Action, the information is saved automatically to the Action record that is
linked to the Proposed Strategy record.
When you are working with a System Strategy or a Unit Strategy, any changes that you
make to an underlying Asset Strategy (e.g., on the System Strategy Risk Analysis page,
you clear the Selected Actions check box for an Action) are saved automatically to the
underlying Proposed Strategy record. The same is true when you are working with a Unit
Strategy.
To determine the records that will store your changes, refer to the overview of the ASM
data structure and illustration of the ASM data model.
Deleting Strategies
When you are finished with a strategy, you can delete it using the Delete link on the
Common Tasks menu on any page within ASM where you are working with that strategy.
Likewise, you can delete multiple strategies at one time using the Delete link on the
Common Tasks menu on the following pages:
Asset Strategy Search

System Strategy Search
Unit Strategy Search
The following instructions provide details on deleting one or multiple strategies via any
of the search pages in the previous list.
To delete a single strategy or multiple strategies:
1. Access the search page for the type of strategies that you want to delete.
2. In the search results, select the rows containing those strategies you want to
delete.
3. On the Common Tasks menu, click the Delete Strategy link (if you are viewing a
list of strategies) or the Delete Template link (if you are viewing a list of Asset
Strategy Templates).
The Meridium APM system checks to see if the strategy can be deleted, and then displays
a confirmation message, asking if you are sure want to delete the record. If, however, one
or more of the strategies cannot be deleted (e.g., it is a master template with controlled
strategies), a dialog box appears, displaying the list of strategies that could not be deleted
and indicates why it could not be deleted. You can click OK to close this message.
4. On the delete confirmation message, click the Yes button.
The selected strategies are deleted.
About ASM and ASO

The Meridium APM Asset Strategy Optimization (ASO) module extends the analytical
capabilities of the Asset Strategy Management (ASM) module by providing features,
which allow you to perform the following additional steps:
Define planned and unplanned correction costs for each Risk.

Define Resources, such as spare parts and human resources, that are needed to
perform actions.
Define Time to Failure (TTF) and Time to Repair (TTR) information based on
Monte Carlo simulation results.
Integrate with the Meridium APM Reliability Analytics module.
Use a diagramming tool that allows you to represent the physical structure of your
equipment and locations.
Define Global Events.
While ASO is its own separate module, it is intended to extend the capabilities available
in ASM by providing a more detailed analysis. You will, therefore, access ASO directly
from an existing Asset Strategy, System Strategy, or Unit Strategy. You can use the
additional features in ASO to perform the steps in the preceding list to determine the most
optimal strategy, which can then be reflected in ASM.
In other words, ASO and ASM work together to provide a more comprehensive view of
your equipment and locations to help you determine the best way to manage them to
reduce cost and risk.
In ASM, the Tools menu provides options that let you create or open an ASO Analysis
and run a simulation after an analysis exists.
If you run a simulation from ASM, while the simulation is running, you can continue
working in other areas of the Meridium APM Framework by:
-or-
Clicking anywhere on the Meridium APM Framework main window outside the
Run Simulation dialog box. When you do so, the simulation will continue to run
in the background, and the dialog box will be hidden behind the Meridium APM
Framework window. When the simulation finishes, the dialog box will be returned
to focus automatically.
Clicking either the minimize or the close button on the Run Simulation dialog
box. When you do so, the simulation will continue to run in the background, and
the minimized dialog box will appear on your Windows taskbar. When the
simulation finishes, the dialog box will be maximized and returned to focus
automatically.
Note: While a simulation is running, you cannot modify the Asset Strategy. If you try to
do so, an error message will appear, indicating the action cannot be completed until the
simulation is complete.
Running Simulations from ASM

To run a simulation from ASM:
1. While viewing the Risk Analysis for an Asset Strategy, System Strategy, or Unit
Strategy, on the Tools menu, click the Run Simulation link.
The Browse For Folder window appears, where you can select or create a folder in which
to store the Event Logs. If you are viewing an Asset Strategy to which changes have not
been made since the last time the simulation was run, however, a message appears,
indicating that the simulation does not need to be run. These instructions assume that the
simulation needs to be run.
Hint: If the Enable Event Log check box is cleared on the Asset Strategy Optimization
Analysis Definition page, the Browse For Folder dialog box will not appear.
2. Navigate to the location where you want to save the Event Logs.
3. Click OK.
Note: If there are already Event Logs files in the folder that you select, a warning
message will appear, stating that any existing Event Log files may be overwritten.
The Run Simulation dialog box appears and displays the progress of the simulation.
After the progress bar reaches the end, the Go to Strategy and Close buttons become
enabled. If you do not want to view the results, you can click the Close button to close
the Run Simulation dialog box. These instructions assume that you want to view the
results.
4. Click the Go to Strategy button.

Associated Pages
The following Associated Page is configured by default for the Asset Strategy family:
Report: Launches the Asset Strategy Approval Report for the Asset Strategy that
you are currently viewing.
Note: To see the underlying URL for this Associated Page, you can use the URL Manager
application.
About the ASM Catalog Folder

Structure
The main ASM Catalog folder is \\Public\Meridium\Modules\Asset Strategy
Management\Management. This folder contains a subfolder, Queries, which contains
baseline queries that are used by default in ASM.
If desired, you can store additional items in the main ASM Catalog folder or in the
Queries subfolder. In addition, you can create new subfolders to store additional items.
Note: All Public folders exist by default. Any baseline item in the Baseline folder is also
available in the corresponding Public folder. Throughout this documentation, however,
we refer to items in the Public folder.
Files in the Queries Folder

The queries listed in the following table are provided in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Management\Queries. In this
table, the values listed in the Query column refer to the query names. The baseline
captions are the same as the names.
Query
Behavior and Usage
Active_Template_Search
Returns a list of all Asset Strategy Template

records that are currently in the Active state.
When you choose to apply an Asset Strategy
Template to an existing Asset Strategy while
viewing the Asset Strategy, you will see the Apply
Template Builder. Meridium APM runs this query
when you access the Select a Template screen of
this builder.
Asset_Strategy_Search
After prompting you to select a family and a state,

returns a list of all Asset Strategy records that are
linked to a record in the selected family and that
are currently in the selected state. Meridium APM
runs this query when you click the Search for
Strategy link on the ASM - Start Page and are
directed to the Asset Strategy Search page.
Meridium APM also runs this query when you
click the Asset Strategies link on any Search menu
in ASM.
After prompting you to select a family, returns a

list of all Asset Strategy records that are linked to
a record in the selected family. When you choose
to apply an Asset Strategy Template to an existing
Asset Strategy while viewing the Asset Strategy
Asset_Strategy_Search_Non_Pending Template, you will see the Apply Template
Builder. If you choose to apply the template to
existing Asset Strategies on the Options for
Applying the Template screen, Meridium APM
runs this query when you access the Select
Records screen.
Locate Assets for Import
Returns a list of Equipment records. Meridium

APM runs this query when you select the Existing
Work Management Item(s) option on the Select
Import Method screen when you are importing an

Asset Strategy. Note that if you plan to import
Task records or Measurement Location records
that are linked to Functional Location record, you
should configure this query to return records in
the Functional Location family.
After prompting you to select a family, returns a
list of:
Strategies Without Master Templates
Asset Strategy records that are linked to a

record in the selected family but are not
linked to an Asset Strategy Template
record through the Master Template Has
Asset Strategy relationship.
Asset Strategy records that are not linked
to a record and are not linked to an Asset
Strategy Template record through the
Master Template Has Asset Strategy
relationship.
Meridium APM runs this query when you click

the Add Existing button on the Master Template
Management page or when you choose to apply
an Asset Strategy Template as a master in the
Apply Template Builder.
System_Strategy_Search
Returns a list of all System Strategy records.

the Search for Strategy link on the ASM - Start
Page and are directed to the System Strategy
Search page. Meridium APM also runs this query
when you click the System Strategies link on any
Search menu in ASM.
Template_Search
After prompting you to select an Asset Strategy

Template state, returns a list of all Asset Strategy
Template records that are currently in the selected
state. Meridium APM runs this query when you
click the Manage Templates link on the ASM Start Page and are directed to the ASM - Asset
Strategy Template Search page. Meridium APM
also runs this query when you click the Templates
link on any Search menu in ASM.
Unit_Strategy_Search
Returns a list of all Unit Strategy records.

the Search for Strategy link on the ASM - Start
Page and are directed to the Unit Strategy Search
page. Meridium APM also runs this query when
you click the Unit Strategies link on any Search
menu in ASM.
ROI Calculation
On the Asset Strategy Risks page, the ROI column appears in the Mitigating Actions
section, as shown in the following image. A red outline has been added to this image to
highlight this column.
For each Action displayed in the grid, ROI is calculated as:

ROI = ([Unmitigated Financial Risk - Mitigated Financial Risk] Annual Action Cost) /
Annual Action Cost
If an Action mitigates only one Risk, the unmitigated financial risk and mitigated
financial risk apply only to that Risk. If, however, an Action mitigates multiple Risks, the
ROI calculation uses the sum of the differences between the unmitigated and mitigated
financial risks for each Risk that the Action mitigates.
Because this case is more difficult to understand, the remaining example in this
documentation uses an Action that mitigates multiple Risks.
Consider the following image of the Action Cleaning the pump, where the Action is
displayed in the Proposed Strategy section on the Asset Strategy Actions page.
Note: The grid has been modified to include additional columns beyond those that are
included in the baseline grid.
You can see that the cost of performing the action is $8,500.00 every two years.
Remember that the ROI calculation uses an annual action cost, so in this example, the
value 8,500 is divided by two to determine the annual cost: $4,250.
So far, for this example, we have determined two parts of the ROI equation, shown in
blue in the following equation:
Annual Action Cost
ROI = ([Unmitigated Financial Risk - Mitigated Financial Risk] 4,250) / 4,250
To determine the unmitigated financial risk and the mitigated financial risk, we need to
look at the individual Risks that the Action mitigates. From the example image, you can
see that the Action mitigates the following Risks:
Bearing Failure
Sealing Failure
Oil Leaks
In the following image, the unmitigated financial risk and mitigated financial risk is
outlined for each individual Risk.
Because the Action mitigates multiple Risks, the ROI calculation uses the differences
between the unmitigated and mitigated financial risk for each Risk. Using the example
values in the grid, the ROI calculation would use the following individual differences:
Bearing Failure: 120,000 - 36,000 = 84,000

Sealing Failure: 451,000 - 135,300 = 315,700
Oil Leaks: 225,600 - 75,200 = 150,400
...where the individual differences are added together to determine the total difference:
550,100 (84,000 + 315,700 + 150,400).
Now, for this example, we have determined the remaining part of the ROI equation,
shown in green in the following equation:
Annual Action Cost
ROI = (550,100 4,250) / 4,250

Therefore, the final ROI equation would look like this:
Annual Action Cost
ROI = (550,100 4,250) / 4,250
ROI = 545,850 / 4,250
ROI = 128.43
If you remember from the first image in this example, for the Action Cleaning the pump,
the value displayed in the ROI column in the Mitigating Actions section is 128 (where
128.43 has been rounded down).
System Code Tables Used by ASM

The following table provides a list of the System Code Tables that are used by ASM.
Table ID
MI_ACTION_TYPE
MI_PERFORMANCE_INTERVAL_UNITS
MI_TIME_UNITS
Table
Description
Function
Action Type
Used to populate the

Action Type list in Action
records.
Performance
Interval Units

Units list in Action
records.
Time Units

Interval Units list in
Action records.
SC_RECOM_RESOURCE
Recommended
Resource

list in Action records.
Parameters for the Asset Strategy

Management URL
There is one root URL associated with Asset Strategy Management (ASM):
meridium://ASM/Management. A link constructed from the path alone will open the
ASM - Start Page. In addition, you can use any of the parameters described in the
following table. Click here for examples of using these parameters to customize the ASM
URL.
Parameter
Name
EntyKey
Mode
Description
Accepted Value(s)
Specifies the Entity

The Entity Key(s) of the
Key of the Asset
desired Asset Strategy,
Strategy, System
System Strategy, Unit
Strategy, or Unit
Strategy, or Asset
Strategy record
Strategy Template
whose data you want
record.
to display.
Specifies that the
page will display
Template
information
associated with an
Asset Strategy
Template record.
Notes
None
The Mode parameter can

be used if any the following
values are specified for the
Page parameter:
Definition
Overview
Actions
FailureRisks
Page
Specifies the page

that you want to
display.
SearchAsset
Definition
RiskAnalysis
Approval
History
Use the following links to
view notes about each
value that is accepted by
the Page parameter.
Overview
SearchAsset
Actions
Definition
FailureRisks
Overview
RiskAnalysis
Actions
Approval
FailureRisks
History
RiskAnalysis
SearchSystem
Approval
SysDefinition
History
SysOverview
SearchSystem
SysAssets
SysDefinition
SysReview
SysOverview
SearchUnit
SysAssets
UnitDefinition
SysReview
UnitOverview
SearchUnit
UnitSystems
UnitDefinition
UnitReview
UnitOverview
Import
UnitSystems
SearchTemplate
UnitReview
Import
SearchTemplate
Admin
Admin
HealthIndicators
HealthIndicators
To see examples of URLs
that include these
parameter values, see the
topic Examples of ASM
URLs.
Examples of ASM URLs
meridium://ASM/Management
Displays the ASM - Start Page.
meridium://ASM/Management?Page=SearchAsset
Displays the Asset Strategy Search page.
meridium://ASM/Management?Page=Definition&EntyKey=0
Displays a blank Asset Strategy Definition page, where you can create a new Asset
Strategy record.
meridium://ASM/Management?Page=Definition&EntyKey=0&Mode=Template
Displays a blank Asset Strategy Template Definition page, where you can create a new
Asset Strategy Template record.
meridium://ASM/Management?
Page=Definition&EntyKey=1234567&Mode=Template
Displays the Asset Strategy Template Definition - <Template ID> page, where <Template
ID> is the ID of the Asset Strategy Template record with the Entity Key 1234567.
meridium://ASM/Management?Page=Overview&EntyKey=1234567
Displays the Asset Strategy Overview - <Strategy ID> page, where <Strategy ID> is the
ID of the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=Actions&EntyKey=1234567
Displays the Asset Strategy Actions - <Strategy ID> page, where <Strategy ID> is the ID
of the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=FailureRisks&EntyKey=1234567
Displays the Asset Strategy Risks - <Strategy ID> page, where <Strategy ID> is the ID of
the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=RiskAnalysis&EntyKey=1234567
Displays the Asset Strategy Risk Analysis - <Strategy ID> page, where <Strategy ID> is
the ID of the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=Approval&EntyKey=1234567
Displays the Review Asset Strategy - <Strategy ID> page, where <Strategy ID> is the ID
of the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=History&EntyKey=1234567
Displays the Asset Strategy Revision History - <Strategy ID> page, where <Strategy ID>
is the ID of the Asset Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=SearchSystem
Displays the System Strategy Search page.
meridium://ASM/Management?Page=SysDefinition&EntyKey=0
Displays a blank System Strategy Definition page, where you can create a new System
Strategy record.
meridium://ASM/Management?Page=SysDefinition&EntyKey=1234567
Displays the System Strategy Definition - <Strategy ID> page, where <Strategy ID> is
the ID of the System Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=SysOverview&EntyKey=1234567
Displays the System Strategy Overview - <Strategy ID> page, where <Strategy ID> is
the ID of the System Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=SysAssets&EntyKey=1234567
Displays the Manage System Strategy - <Strategy ID> page, where <Strategy ID> is the
ID of the System Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=SysReview&EntyKey=1234567
Displays the Review System Strategy - <Strategy ID> page, where <Strategy ID> is the
ID of the System Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=SearchUnit
Displays the Unit Strategy Search page.
meridium://ASM/Management?Page=UnitDefinition&EntyKey=0
Displays a blank Unit Strategy Definition page, where you can create a new Unit Strategy
record.
meridium://ASM/Management?Page=UnitDefinition&EntyKey=1234567
Displays the Unit Strategy Definition - <Strategy ID> page, where <Strategy ID> is the
ID of the Unit Strategy record with the Entity Key 1234567.
meridium://ASM/Management?Page=UnitOverview&EntyKey=1234567
Displays the Unit Strategy Overview - <Strategy ID> page, where <Strategy ID> is the
ID of the Unit Strategy record with the Entity Key 1234567
meridium://ASM/Management?Page=UnitSystems&EntyKey=1234567
Displays the Manage Unit Strategy - <Strategy ID> page, where <Strategy ID> is the ID
of the Unit Strategy record with the Entity Key 1234567
meridium://ASM/Management?Page=UnitReview&EntyKey=1234567
Displays the Review Unit Strategy - <Strategy ID> page, where <Strategy ID> is the ID
of the Unit Strategy record with the Entity Key 1234567
meridium://ASM/Management?Page=Import
Displays the Open window, where you can select a Microsoft Excel file, existing Task
records, or existing Measurement Location record to use for creating or updating an
existing Asset Strategy.
meridium://ASM/Management?Page=SearchTemplate
Displays the Asset Strategy Template Search page.
Page=Overview&Mode=Template&EntyKey=1234567
Displays the Asset Strategy Template Overview - <Template ID> page, where <Template
Page=Actions&Mode=Template&EntyKey=1234567
Displays the Asset Strategy Template Actions - <Template ID> page, where <Template
Page=FailureRisks&Mode=Template&EntyKey=1234567
Displays the Asset Strategy Template Risks - <Template ID> page, where <Template ID>
is the ID of the Asset Strategy Template record with the Entity Key 1234567.
Page=RiskAnalysis&Mode=Template&EntyKey=1234567
Displays the Asset Strategy Template Risk Analysis - <Template ID> page, where
<Template ID> is the ID of the Asset Strategy Template record with the Entity Key
1234567.
Page=Approval&Mode=Template&EntyKey=64251748617
Displays the Review Asset Strategy Template - <Template ID> page, where <Template
Page=History&Mode=Template&EntyKey=1234567
Displays the Asset Strategy Template Revision History - <Template ID> page, where
<Template ID> is the ID of the Asset Strategy Template record with the Entity Key
1234567.
meridium://ASM/Management?Page=Admin
Displays the ASM - Administration page.
Action
Identifies the physical ways in which you maintain a piece of equipment or location. For
example, an Action might indicate that you want to perform a visual inspection of a piece
of equipment. After you have created an Asset Strategy record, you can begin adding
Actions to the Asset Strategy.
The values you specify in an Action are stored in an Action record. Throughout this
documentation, however, unless it is necessary to refer to the record itself, we use the
term Action.
Asset Strategy
The combination of actions and risks that are associated with a piece of equipment or
location and represent a plan to optimize performance to achieve business benefits.
Risk
The way in which the piece of equipment or location can fail and the consequence of the
failure. This consequence is presented as a risk rank value, which is determined from the
values that you select in the Risk Assessment interface that appears when you create a
Risk.
Strategy Mitigated Risk Rank

The sum of the smallest risk rank values across all risk categories (represented by tabs on
the risk matrix) defined for all Actions that are associated with the Risk.
System Strategy
A collection of Asset Strategies.
Unit Strategy
A collection of System Strategies.

Implementation
The Meridium APM Asset Strategy Implementation (ASI) module lets you build
Implementation Packages, which are containers of records that dictate the work that you
want to perform and the Asset Strategies that contain the original work requests (Action
Revision records). Using ASI, you can determine where you want to track the physical
work that needs to be performed: your Meridium APM system or an external SAP
system. Then, by implementing these Implementation Packages, you can create those
physical work items (Meridium APM records or SAP items).
For example, if you want to track work items in Meridium APM, you can create
Measurement Location records or Meridium APM Task records. If, however, you want to
track work against items in your SAP system, you can also use ASI to create items such
as Maintenance Plans, Maintenance Items, and Task Lists.
Note that if you choose to track your work using SAP items, you must activate the ASI
for SAP license, which allows for integration between Meridium APM and an external
SAP System.
Keep in mind that although ASI is highly configurable, the focus of this documentation is
to explain how to perform tasks using the baseline ASI implementation. D
ASI System Requirements

The following licenses are required to take full advantage of ASI functionality:
ASM and ASI

ASI for SAP
In addition, your system must contain the basic Meridium APM system architecture and
the following additional components:
The Asset Strategy Management (ASM) module. ASI allows you to build
Implementation Packages, which are containers of records that dictate the work
that you want to perform and the Asset Strategies that contain the original work
requests (Action Revision records). Asset Strategies are created in ASM. This
documentation assumes that you have deployed and configured the ASM module.
An SAP System. This component is required only if you want to create items such
as Maintenance Plans, Maintenance Items, and Task Lists from ASI. To take full
advantage of the ASI module, we recommend that you integrate ASI with SAP, so
this documentation provides details on performing the steps required to integrate
ASI with SAP.
Note: For all ASI workflows, the Meridium APM system does not support integration
with SAP through SAP PI.
perform some configuration tasks specifically for the ASI module.
ASI Data Model

Like all Meridium APM modules, Meridium APM Asset Strategy Implementation
consists of entity families, relationship families, and business rules. The Packaging
<Package ID> page in ASI provides you with a custom view of ASI records that exist in
the database. This page also helps facilitate the creation of new records.
When attempting to understand and make use of the Meridium APM ASI functionality, it
can be helpful to visualize the ASI data model. Because you should already be familiar
with the concept of records and viewing records in the Meridium APM Record Manager,
as you attempt to get your bearings in ASI, it may be useful to remember that ASI is
simply a customized view of individual records that work together to make up an
Implementation Package.
All ASI implementation packages begin with an Implementation Package record. Each
Implementation Package record will be linked to:
Zero or one SAP System records through the Has SAP System relationship.
At least one Asset Strategy record through the Implements Strategy relationship.
Zero or more Asset Strategy records through the Implements Secondary Strategy
relationship.
One or more Action records through the Implements Actions relationship.
One or more other records through the Has Work Management Item relationship.
These records store the details of work items that you want to implement, either in
Meridium APM or in an external SAP management system.
The following diagram illustrates how families are related to one another within the ASI
data model. The boxes represent entity families, and the arrows represent relationship
families. You can determine the predecessor and successor in each relationship by the
direction of the arrow head. The box to which the arrow is pointing is the successor in the
relationship.
Note that the following relationships are used only if you transfer Action records from
one Implementation Package to another Implementation Package:
Implements Secondary Strategy: Links the Asset Strategy record to which the
transferred Action record is linked to the secondary Implementation Package
record.
Implements Action: Links the transferred Action record to the secondary
What is an Implementation Package?

An Implementation Package is a collection of records that define the work that you want
to perform and the Asset Strategies that contain the original work requests (i.e., Action
records). An Implementation Package consists of the following records:
One Implementation Package record that defines basic information about the
purpose and content of the Implementation Package.
One or more Asset Strategy records that contain the original work requests (i.e.,
Actions).
One or more Actions representing the original work requests.
Note: Although you are technically seeing the Action Revision records in ASI, for
simplicity sake, unless the distinction is essential to the discussion, the ASI
documentation refers to these items simply as Actions.
Multiple records that represent work that you want to perform. These records are
linked either directly or indirectly to the root Implementation Package record and
can belong to different families, such as the Calibration Task family or the
Maintenance Item family. Because they can belong to different families and we
cannot predict the families that you might use, throughout the Meridium APM
documentation, we refer to them generically as work item records.
Some work item records will represent work that you want to track using Meridium APM
(e.g., Inspection Task records), and other work item records will represent work that you
want to track using SAP (e.g., Maintenance Item records).
About Primary and Secondary

Implementation Packages
When you add an Asset Strategy to an Implementation Package, all Actions that belong to
that Asset Strategy become available for implementation in that Implementation Package.
In some cases, however, depending upon your business processes and personal
workflows, you might not want to implement all of those Actions in the same
Implementation Package. Instead, you might want to transfer one or more Actions from
that Implementation Package to another Implementation Package.
Throughout the ASI product and this documentation, the following terminology is used to
describe Implementation Packages:
Primary Implementation Package: The Implementation Package to which the

Asset Strategy and its Actions are originally added.
Secondary Implementation Package: Any Implementation Package to which an
Action is transferred.
Except for transferring Actions back to their original primary Implementation Package,
which is available only for secondary Implementation Packages, all features and
functionality of primary Implementation Packages are also available for secondary
Implementation Packages. This means that the ability to transfer Actions to other
secondary Implementation Packages is available for both primary and secondary
Implementation Packages.
Note that an Implementation Package can be both a primary Implementation Package and
a secondary Implementation Package. For instance, consider the following image, where
Package 1, outlined in red, is:
A primary Implementation Package for the Vibration Analysis Actions from Asset
Strategy 1, Asset Strategy 2, and Asset Strategy 3.
A secondary Implementation Package for the Vibration Analysis Action from
Asset Strategy 4.
Throughout this documentation, wherever functionality is available for both types of

Implementation Packages and the distinction is irrelevant to the explanation, we simply
use the term Implementation Package.
Example: Primary and Secondary

Suppose that an Asset Strategy Template contains the following Actions that apply to all
pumps:
Vibration Analysis
Thermography
Lubrication
Overhaul
As illustrated in the following image, you could apply this template to three specific
pumps (Pump 101, Pump 102, and Pump 103), which would create three distinct Asset
Strategies that all inherit Actions from the template.
After these Asset Strategies exist, you could create a single Implementation Package from
them. As illustrated in the following image, all Actions would become available in that
Implementation Package, labeled Primary Package 1. In the image, all Actions of the
same name are grouped together and shaded a common color. For example, you can see
three Vibration Analysis Actions shaded in yellow, where each one is for a different pump
(101, 102, or 103).
After the Actions exist in the Implementation Package, you could build a single SAP
Maintenance Plan from them. For the purpose of this example, however, we assume that
your company requires different users to complete different routes, where each route
involves performing only one type of action (only vibration analyses, only thermography
analyses, and so on).
Based upon this assumption, you would not want to create a single Maintenance Plan
from all of these Actions. Instead, you would want to transfer the common Actions to
other Implementation Packages, where each of those Implementation Packages represents
an individual route that should be performed by one person.
In the following image, you can see that each group of common Actions is transferred to
a secondary Implementation Package, labeled according to the type of action. For
example, all Vibration Analysis Actions have been transferred to the Vibration Route
Suppose that later, you apply the original Asset Strategy Template to another pump
(Pump 104), creating Asset Strategy 4, and you add that Asset Strategy to another
primary Implementation Package, Primary Package 2.
Suppose that Pump 104 exists in a different building than Pump 101, 102, and 103.
Regardless of the building in which pumps exists, overhauls are performed on all pumps
by the same person. Other actions, however, are divided among operators according to
the building in which those pumps exist. In other words, the operators performing actions
on Pump 101, 102, and 103 are not going to perform those actions on Pump 104.
In this case, you decide to transfer:
The Overhaul Action to the existing secondary Implementation Package Overhaul

Package.
The Vibration Analysis, Thermography, and Lubrication Actions to new

secondary Implementation Packages.
The final image depicts all of the Actions in their appropriate Implementation Packages.
Note: For the Actions in Primary Package 2, the image illustrates the transfer of only the
Vibration Analysis Action to a separate secondary Implementation Package. The other
Actions shaded in gray would also be transferred to other secondary Implementation
Packages.
About Work Item Records
Work item records represent the work that should be completed when the Implementation
Package is implemented. Throughout the documentation, we refer to them as work item
records because they can belong to any family. Before you can create work item records
in a particular family, the corresponding Work Management Item Definition records and
Work Management Item Child Definition records must exist. Each Work Management
Item Definition record contains a family ID, which identifies a family to which work item
records can belong.
Meridium APM delivers a baseline set of Work Management Item Definition and Work
Management Item Child Definition records to allow you to create work item records in
certain baseline families. For example, Meridium APM delivers a Work Management
Item Definition record whose family ID is Maintenance Item, which allows you to add
Maintenance Item records to an Implementation Package. You can also create your own
Work Management Item Definition records so that you can create work item records in
other families.
After you add a work item record to an Implementation Package, the work item record is
linked either directly or indirectly to the root Implementation Package record. Work item
records can also be linked to one another and arranged hierarchically in the tree on the
Packaging <Package ID> page according to these relationships. Beyond defining the
family of the work item records that you want to create, you will, therefore, need to
define where in this hierarchy they can exist. To do so, you will need to:
Configure the appropriate relationship definitions via the Configuration Manager.
-and
Create the appropriate Work Management Item Definition and Work Management
Item Child Definition records via the Meridium APM Framework.
On the Packaging <Package ID> page, the options that appear in the tree and on the
Packaging Tasks menu are dynamic, meaning that they change based upon the current
selection in the tree. The options that are available are based upon the way in which you
have configured the hierarchy.
Throughout this documentation, we describe the hierarchy that appears on the Packaging
<Package ID> page using the terms predecessor record and successor record. In this
context:
A predecessor record is any work item record to which another work item record
can be linked.
A successor record is any work item record that is linked to a predecessor work
item record.
How Does Meridium APM Determine

the Predecessor Records to Which I
Can Link a New Successor Record?
Each Work Management Item Definition record contains a Parent Family ID field, which
contains a value that identifies the predecessor family whose existing work item records
can be linked to a new successor work item record identified by the value in the Family
ID field. For example, in the baseline Maintenance Item Work Management Item
Definition record, the Parent Family ID is Maintenance Plan. This means that from a
predecessor Maintenance Plan record, you can create a new Maintenance Item record to
link to it.
How Does Meridium APM Determine

the Successor Records That I Can Link
to a Predecessor Record?
Each Work Management Item Definition record can be linked to one or more Work
Management Item Child Definition records, which contain a Child Family ID field. The
Child Family ID field contains a value that identifies the family in which new successor
records can be created and linked to an existing predecessor record identified by the
family ID in the Work Management Item Definition record to which it is linked.
For example, the baseline Maintenance Item Work Management Item Definition record is
linked to a Work Management Item Child Definition record whose Child Family ID is
Task List. This means that from a predecessor Maintenance Item record, you can create a
successor Task List record. The Task List record will be linked to the Maintenance Item
record and the Implementation Package record.
How Are Work Item Records Arranged

in the Tree?
Any work item record that can be added to an Implementation Package can be added
directly under the root Implementation Package node. This one-dimensional organization,
however, is not always desired or representative of how the work item records are linked
to one another. In addition, if the work item records represent work that will be
performed in SAP, this one-dimensional level of organization does not reflect how the
items are arranged in the SAP hierarchy.
For example, in the baseline Meridium APM database, you could create Maintenance
Item, Maintenance Plan, and Task List records on the root level of the tree on the
Packaging <Package ID> page, as shown in the following image.
These records will be linked to the root Implementation Package record because they are
positioned directly under the Implementation Package node. The links can be created
because all three families are related to the Implementation Package family through the
Has Work Management Item relationship.
Rather than arranging the records in this way, however, you will probably want to arrange
them hierarchically, as shown in the following image, to mimic the hierarchy structure
that is used by SAP and to allow the records to be appropriately linked to one another.
Structuring the records in this way demonstrates how the records are linked to one
another. In other words:
The Implementation Package record is linked to the Maintenance Plan record

through the Has Work Management Item relationship.
The Maintenance Plan record is linked to the Maintenance Item record through
The Maintenance Item record is linked to the Task List record through the Has
Task List relationship.
It is possible to arrange the records in a tree structure like this because the appropriate
relationship definitions, Work Management Item Definition records, and Work
Management Item Child Definition records exist.
A Complete Example
On the Packaging <Package ID> page, the options that you see in the tree and on the
Packaging Tasks menu are determined based on the following items:
The relationship definitions that have been configured in the Configuration

Manager.
The Work Management Item Definition records and Work Management Item
Child Definition records that have been configured in the Meridium APM
Framework.
The following information explains which relationship definitions, Work Management

Item Definition records, and Work Management Item Child Definition records work
together to allow you to create the following structure on the Packaging <Package ID>
page.
Maintenance Plan Record

The Maintenance Plan record can be created and added to the Implementation Package
because a Work Management Item Definition record contains the value Maintenance Plan
in the Family ID field, as shown in the following image.
The Maintenance Plan record can be added to the root level of the tree because the
Maintenance Plan family is related to the Implementation Package family through the
Has Work Management Item relationship.
Maintenance Item Record

The Maintenance Item record can be created and added to the Implementation Package
because a Work Management Item Definition record contains the value Maintenance Item
in the Family ID field, as shown in the following image.
The Maintenance Item record can be created as a successor of the Maintenance Plan
record because the Maintenance Item Work Management Item Definition record contains
the value Maintenance Plan in the Parent family ID field.
In addition, the Maintenance Item record can be linked to the Maintenance Plan record
because the Maintenance Plan family is related to the Maintenance Item family through
The result is that the Create a new Maintenance Item... option is available when you
right-click a Maintenance Plan node, as shown in the following image.
Task List Record

The Task List record can be created and added to the Implementation Package because a
Work Management Item Definition record contains the value Task List in the Family ID
field, as shown in the following image.
The Task List record can be created from the predecessor Maintenance Item record
because of three things:
The Task List Work Management Item Definition record contains the value
Maintenance Item in the Parent Family ID field.
-AND
The Maintenance Item Work Management Item Definition record is linked to a

Work Management Item Child Definition record that contains the value Task List
in the Child Family ID field.
-AND
The Maintenance Item family is related to the Task List family through the Has
Task List relationship.
The result is that the following option is available when you right-click a Maintenance
Item node, as shown in the following image.
Keep in mind that these Work Management Item Definition and Work Management Item
Child Definition records are provided in the baseline Meridium APM database, meaning
that by default, you can create Maintenance Plan, Maintenance Item, and Task List
records in the preceding hierarchy.
If however, you create new families whose records you want to add to an Implementation
Package, you will need to know how to configure the appropriate relationship definitions
in the Configuration Manager, create Work Management Item Definition records, and
create Work Management Item Child Definition records.
About Implementation Roles

An Implementation Role identifies a type of work that is performed by people within
your organization. In ASI, you can create Implementation Role records to categorize
these work types. For instance, you might create the following Implementation Role
records: Electrical and Mechanical. Using this example, you can assume that some users
in the organization perform electrical work (e.g., repair transformers) while other users
perform mechanical work (e.g., repair pumps). As part of creating an Implementation
Role record, you will need to assign it to Security Users or Security Groups to indicate
the users who perform that type of work.
After you create Implementation Role records, when an ASM user creates an Action, he
or she can use the Implementation Role field to indicate the type of work that the Action
represents. For example, if a user creates the Action Install light fixtures, he would want
to select the Implementation Role Electrical.
If an Action has a designated Implementation Role, only Security Users who are assigned
to that Implementation Role will be able to create work item records from that Action in
ASI. In addition, when the Action is used to create a work item record, the work item
record will be organized in the tree according to the Implementation Role to which it
belongs. Security Users who are assigned the Implementation Role that is associated with
the Action can filter the tree to display only work item records representing work that
they are responsible for performing.
To illustrate this workflow, consider the following example:
The following Implementation Role records exist.
Role Name Assigned To
Electrical John Smith
Mechanical Mary Jones
In addition, the following Actions exist.
Action Name
Associated With
Install light fixtures Electrical

Replace filter
Mechanical
If both Actions are used to create Inspection Task records in ASI, the tree will look like
the one shown in the following image.
John Smith could log in and filter the tree to display only the Electrical Inspection Task:
Install light fixtures. Likewise, Mary Jones could log in and filter the tree to display only
the Mechanical Inspection Task: Replace filter.
About the PRT Functionality

In SAP, an Operation defines specific maintenance work that needs to be performed. To
each Operation, you can assign a production resource/tool (PRT) to define items that help
the operator perform the work. In SAP, there are four main types of PRTs:
Material
Equipment
Document
PRT Master
Using ASI, you can use the PRT Builder to create a PRT record in Meridium APM that
will be used to create a document PRT (i.e., an SAP PRT of the type Document) in SAP
when the Implementation Package is implemented. In SAP, a document PRT allows you
to reference an external file, such as a Word document, that contains information needed
to perform maintenance work. When an operator is ready to perform the work, he can use
the information in the file to guide his work. For example, suppose an Operation indicates
that you need to perform maintenance on your vehicle. While the Operation defines the
expected work duration and the type of activity (e.g., change oil filter), a document PRT
might reference a Word document including images and detailed instructions (i.e., an
explanation of how to change the oil filter).
Note: You can also create PRT records outside of the PRT Builder and associate them
with existing PRTs in SAP. When you do so, you can choose any type of PRT to associate
with the PRT record.
Because you will probably create many PRT records as you build Implementation
Packages, ASI allows you to create PRT Template records, where each one references a
file that stores the basic structure of the files that you can reference from PRT records.
When you create a PRT record in ASI, you must select which PRT template file you want
to use to build the file that will be referenced from that PRT record. Values will be passed
in to the PRT template file from the records to which the PRT record is linked to generate
a PRT file with specific values.
The following terms are used throughout this documentation when referring to PRT
functionality.
Term
Definition
A Meridium APM
entity that is stored in
PRT Template record the PRT Template
family and references
a PRT template file.
PRT template file
PRT record
PRT file
Example
Notes
The baseline record

with the ID Simple
PRT Template that is
stored in the PRT
Template family.
You can create PRT

Template records on
the Implementation
Administration page.
A file that contains

information about
vehicle maintenance
procedures, including
the type of vehicle to
A file that is
which the procedures
referenced from a
apply, the interval at
PRT Template record
which the
and can be used as
maintenance should
the basis for creating
be performed, and a
new PRT files, which
place for the operator
are referenced from
to sign and date each
PRT records.
maintenance action,
such as changing the
oil filter, rotating the
tires, or checking
fluid levels.
A Meridium APM
entity that is part of
an Implementation
Package.
When you create a

PRT template file,
data is actually
inserted into the
binary field Template,
which is defined in
the PRT Template
family. The file does
not exist as an
external file but is
stored in the
Meridium APM
database and
referenced by the
value in this binary
field.
Each PRT record is

linked to an
A record with the ID Operation record.
Oil Filter Change that Each Operation
is stored in the PRT record is linked to a
family.
Task List record and
one or more Action
Revision records.
A file that is
A file that contains
referenced from a
images and step-byPRT record and based step instructions for
on a PRT template
changing an oil filter.
file.
When a file is
associated with a PRT
record, data is
actually inserted into
the binary field
Document Binary,
which is defined in
the PRT family. The

file does not exist as
an external file but is
stored instead in the
Meridium APM
database and
referenced by the
value in this binary
field.
In other words, PRT Template records contain references to PRT template files. The
following image illustrates this association.
PRT records contain references to PRT files, which are files that were created using a
PRT template file. The following image illustrates this association.
Implementation Package State

Configuration
This topic describes attributes of the State Configuration that is defined for the
Implementation Package family in the baseline Meridium APM database.

The following State Configuration is defined for the Implementation Package family.
Note that in this image, a box represents a state, and an arrow represents an operation.
The state to which an arrow points represents a successor state.
Initial State
The Draft state is the initial state of all new Implementation Package records.
Implementation Package record in the Record Manager.

The following table lists the baseline states and operations and indicates which of these
states and operations are reserved. You cannot remove or modify reserved states or
operation. You can, however, add your own states and operations to the State
Configuration.
States
State
Is Reserved?
Draft
No
Implemented
Yes
Modified
Yes
Packaged
Yes
Partially Implemented
No
Pending Implementation
Yes
Operations
Operation
Is Reserved?
Complete Implementation
Yes
Implement
Yes
Package
No
Partially Implement
Yes
Revert
No
Revise
Yes
Update
Yes
By default, the MI ASI User State Configuration Role is assigned to all states in the
Implementation Package State Configuration. If desired, you can assign other State
Configuration Roles to any state. In addition, for each state, the Require a specific user
to be assigned to a state check box is selected.
About Assigning Users to States in ASI

By default, all the Implementation Package record states require a Security User to be
assigned to the successor state before the record can be transitioned to the successor state.
In ASI, however, if you try to transition the Implementation Package to a state that does
not have an assigned user, the Meridium APM system will assign the current Security
User to the successor state automatically, with the exception of the Packaged and
Modified states. You must assign a Security User manually to the Packaged and Modified
states.
In addition, if the Security User who is currently logged in is not assigned to the current
state of the Implementation Package record, links on the State Configuration Tasks
menu will be disabled if the corresponding action would cause the state of the
Implementation Package record to change.
Accessing the Asset Strategy

Implementation Start Page
To access the Asset Strategy Implementation Start Page:
Strategy, and then click Asset Strategy Implementation.
The Asset Strategy Implementation Start Page appears.
Aspects of the Asset Strategy

The Asset Strategy Implementation Start Page serves as the starting point for the tasks
that you can perform in Meridium APM Asset Strategy Implementation. You can access
each task via a link on the start page. Note that the links on this page do not suggest a
recommended workflow but rather allow you to access certain features that you will need
to use as part of building and implementing Implementation Packages.
The following links are available:
Create Package: Displays the Implementation Package Creation page, where you
can create an Implementation Package record.
Search for Package: Displays the Implementation Package List page, where you
can open an Implementation Package record.
Administration: Displays the Implementation Administration page, where you can
perform various ASI administrative tasks.

Deploying and configuring ASI for the first time includes completing multiple steps,
provide all the information that you need to deploy and configure the ASI module on top
of the basic Meridium APM system architecture.
Steps are marked as Required in the Required/Optional column if you must perform the
steps to take advantage of ASI functionality. This documentation assumes that in addition
to implementing the basic ASI functionality that you also want to implement integration
with SAP. Steps necessary for SAP integration are also designated as Required in the
following table.
recommend that the steps be performed in relatively the same order in which they are
listed in the table.
Step Task
Install the ASI for SAP ABAP addon on your SAP System.
Review the ASI data model to

determine which relationship
definitions you will need to modify
to include your custom equipment
Optional
and location families. Modify any
relationship definitions as needed via
the Configuration Manager
application.
This task is necessary only

if you store equipment and
location information in
families other than the
baseline Equipment and
Functional Location
families.
Assign Security Users to one or more

of the ASI Security Groups via the Required
Users will need

permissions to the ASI
families in order to use
ASI.
Required
None
Configure SAP for external

numbering in your SAP System.
4
Required
None
Required
None
Define sites to associate with

Implementation Packages via the
application.
Optional
This is required only if you

want to import data from
SAP into ASM.
Configure secured Maintenance

Plants in your SAP System.
Optional
None
Configure SAP permissions.

5
Configure Work Management Item

Definition records via the Meridium Optional
APM Framework application.

if you want to use Work
Management Item
Definition records beyond
those provided with the
baseline database.
Define Implementation Roles via the

Optional
application.
None
10
Define the SAP connection that will

be used when SAP items are created
from records that represent work
Required
items. You can do so via the
application.
None
11
Build PRT Templates via the

application.
Optional

if you want to use the PRT
functionality.
12
Define the packaging query via the

application.
Optional

if you want to use a query
other than the baseline
query.
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading ASI from V3.5.1 to V3.6.0.0.0
The following table lists the step that is required to upgrade and configure ASI for
Step Task
Required/Optional
Required
Upgrade the ASI for SAP ABAP add-on in your SAP System.
Upgrading ASI from V3.5.0 SP1 LP to

V3.6.0.0.0
Step Task
Required/Optional
Required

Step Task
Required/Optional
Required

Step Task
Required/Optional
Required
What is the ASI for SAP ABAP Add-on?

Meridium APM ASI for SAP extends the basic functionality of Asset Strategy
Implementation (ASI) by offering integration with SAP. Deploying ASI for SAP requires
two steps:
Activating the ASI for SAP license in the Meridium APM database. This
documentation assumes that you activated the license when you completed the
steps for creating or upgrading your Meridium APM database.
Deploying the ASI for SAP ABAP add-on, which is package that must be
deployed on your SAP system to allow for integration between your Meridium
APM system and your SAP system.
The files necessary to deploy ASI for SAP are provided on the ASI for SAP ABAP Addon DVD, which is not included in the standard Meridium APM distribution but can be
obtained from Meridium, Inc. upon request.
The ASI for SAP ABAP Add-on DVD contains installation files, upgrade files, and
exchange files. In this documentation, we provide details on using the installation and
upgrade files. You will need to use the exchange files if you upgrade an SAP system on
which the ASI for SAP ABAP Add-on package has been installed. In that case, the SAP
upgrade procedure will prompt you for the exchange files for ASI for SAP. You can find
the files in the Exchange Upgrade Files folder on the ASI for SAP ABAP Add-on DVD.
Within the Exchange Upgrade Files folder, you will see subfolders representing the
version of SAP to which you are upgrading. When prompted for an ASI for SAP
exchange file, use the files in these subfolders. This documentation does not provide
specific instructions for using these files during an SAP upgrade.
For information about what is included in the ASI ABAP Add-on, see the file
SAP_ASI_<version>_ObjectList.pdf, which is located on the ASI for SAP ABAP Add-on
installation DVD in the root folder.
What is Included in the ASI ABAP AddOn?

For information about what is included in the ASI ABAP Add-on, see the file
SAP_ASI_<version>_ObjectList.pdf, which is located on the ASI for SAP ABAP Add-on
installation DVD in the root folder.
Installing the ASI ABAP Add-On on the

SAP System
Note: You do not need to perform the following procedure if you are upgrading from a
previous version of Meridium APM and you installed ASI for SAP in that version. To
complete the following instructions successfully, you must use SAP client 000.
To install the ASI ABAP add-on package on the SAP system:
1. On a machine from which you can access the SAP Server, insert the ASI for SAP
ABAP Add-on installation DVD.
2. Navigate to the folder Installation Files.
3. Navigate to the subfolder ECC6, and copy the .PAT file.
4. On the SAP Server, paste the copied file into the folder usr\sap\trans\eps\in.
5. Log in to the SAP system as a user with:
SCTSIMPSGL and S_CTS_ADMIN authorizations.
-or3.
SAP_ALL authorization.
6. Run the SAINT transaction.

The Add-On Installation Tool screen appears.
7. On the Installation Package menu, point to Load Packages, and then click
From application server.
A message appears, asking if you want to upload OCS packages from the ECS inbox.
The SAINT: Uploading Packages from the File System screen appears.
9. Select the .PAT file that you copied in step 3 of these instructions. The message
column should read Uploaded successfully.
10. Click the
button.
The Add-On Installation Tool screen appears again.

11. Click the Start button.
A new grid appears. MIAPM appears in the list of add-on packages that can be installed.
12. Select the row containing the text MIAPM in the first column, and click the
Continue button.
The Support Package selection tab appears.
13. Click the Continue button.
14. Click the Continue button again.
Note: During the installation, the Add Modification Adjustment Transports to the Queue
dialog box might appear. If it does, click the No button.
An indicator appears at the bottom of the screen to indicate the installation progress.
15. When the progress indicator disappears, a message appears, indicating that the
add-on package will be installed.
16. Click the
button.
The status is updated to indicate that the add-on package will now be imported, and the
installation process continues.
When the installation process is complete, the status is updated to indicate that the add-on
package was imported successfully.
The MIAPM add-on package appears in the list of installed add-on packages on the
Add-On Installation Tool screen.
After you have installed the ASI ABAP add-on package, you will need to perform various
configuration steps to ensure the proper functioning of ASI for SAP.
Upgrading the ASI ABAP Add-On on

the SAP System
Note: You should perform the following procedure only if you are upgrading from a
previous version of Meridium APM and you installed ASI for SAP in that version.
To upgrade the ASI ABAP Add-on on the SAP System:
1. On a machine from which you can access the SAP Server, insert the ASI for SAP
ABAP Add-on installation DVD.
2. Navigate to the folder Upgrade Files.
3. Navigate to the subfolder ECC6, and copy the .PAT file.
4. On the SAP Server, paste the copied file into the folder usr\sap\trans\eps\in.
5. Log in to the SAP system as a user with S_CTS_IMPSGL and S_CTS_ADMIN
authorization.
6. Run the SAINT transaction.
The Add-On Installation Tool screen appears.
7. On the Installation Package menu, point to Load packages, and then click
From Application Server.
A message appears, asking if you want to upload OCS packages from the ECS inbox.
The SAINT: Uploading Packages from the File System screen appears.
9. Select the .PAT file that you copied during step 3 of these instructions. The
message column should read Uploaded successfully.
10. Click the
button.
The Add-On Installation Tool screen appears again.

11. Click the Start button.
A new grid appears. MIAPMINT appears in the list of add-on packages that can be
installed.
12. Select the row containing the value MIAPMINT in the first column, and click the
Continue button.
The Support Package selection tab appears.
13. Click the Continue button.
14. Click the Continue button again.
Note: During the installation, the Add Modification Adjustment Transports to the Queue
dialog box might appear. If it does, click the No button.
An indicator appears at the bottom of the screen to indicate the installation progress.
15. When the progress indicator disappears, a message appears, indicating that the
add-on package will be installed.
16. Click the
button.
The status is updated to indicate that the add-on package will now be imported, and the
installation process continues.
When the installation process is complete, the status is updated to indicate that the add-on
package was imported successfully.
ASI Security Groups

The baseline Meridium APM database contains two Security Groups specifically for
Asset Strategy Implementation:
MI ASI Administrator
MI ASI User
The following table lists the baseline family-level privileges that exist for these Security
Groups.
Family
MI ASI Administrator 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

Delete
Consequence
None
View
Equipment

Delete
View, Update, Insert
Execution Mapping

Delete
View
Functional Location

Delete
Health Indicator
None
View
Health Indicator Mapping
None
View
Hierarchy Item Child Definition
None
View
Hierarchy Item Definition
None
View
Implementation Authorization

Delete
View
None

Delete
Implementation Role

Delete
View
Inspection Task
None

Delete
KPI
None
View
KPI Measurement
None
View
Maintenance Item
None

Delete
Maintenance Package
None

Delete
Maintenance Plan
None

Delete
Material
None

Delete
None

Delete
Measurement Location Group
None

Delete
Measurement Location Template

Delete
Notification
None

Delete
Object List Item
None

Delete
Operation
None

Delete
Operator Rounds Allowable Values
None
View
Probability
None
View
Proposed Strategy
None
View
Protection Level
None
View
PRT
None

Delete
PRT Template

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

Delete
View
Site Reference
View
View
System Strategy
None
View
Task List
None

Delete
Task Types
None
View
Thickness Monitoring Task
None

Delete
Unit Strategy
None
View
Work Management Item Child Definition

Delete
View
Work Management Item Definition

Delete
View

Configuration

Delete
View
Authorized to Implement

Delete
View
Documents Action

Delete

Delete
Has Actions
None
View
Relationship Families
Has Action Mapping

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

Delete
View
Has Driving Recommendation
None
View
Has Execution Mapping

Delete
View
Has Health Indicators

Delete

Delete
Has KPI Measurement
None
View
Has Maintenance Item
None

Delete
Has Maintenance Package
None

Delete
Has Material
None

Delete
Has Measurement Location Group
None

Delete
Has Mitigation Revisions
None
View
Has Object List Item
None
Delete
Has Operation
None

Delete
Has Proposed Strategy
None
View
Has PRT
None

Delete
None
View
Has Risk
None
View
Has Risk Category
None
View
Has Risk Revisions
None
View
Has SAP System
None

Delete
Has Strategy
None
View
Has Strategy Revision
None
View
Has System Strategy
None
View
Has Tasks
None

Delete
Has Task List
None

Delete
Has Task Revision
None

Delete
Has Work Management Item
None

Delete
Has Work Management Item Definition

Configuration

Delete
View
Health Indicator Has Mapping
None
Health Indicator Has Source
None

Delete
Implements Action
None

Delete
Implements Strategy
None

Delete
Implements Secondary Strategy
None

Delete
Is Mitigated
None
View
Master Template Has Asset Strategy
None
View
Mitigates Risk
None
View
Was Applied to Asset Strategy

Delete

Delete
Was Applied to PRT

Delete

Delete
Configuring SAP for External

Numbering
When you implement an Implementation Package in ASI, Meridium APM generates
unique numbers for SAP Maintenance Plans, Maintenance Items, and General
Maintenance Task Lists. In order for Meridium APM to assign these external numbers,
your SAP system must be configured to allow External Numbering.
Consult the documentation for your SAP system to define the following External Number
Ranges.
Object Type
From Number
To Number
Maintenance Plan
M00000000001
M99999999999
Maintenance Item
M000000000000001
M999999999999999
General Maintenance Task

List
M0000001
M9999999
Configuring SAP Permissions

If you will be sending data to SAP using ASI Implementation Packages, you must have
the following security permissions:
Access to execute RFCs as described in SAP note 460089.

Access to execute the functions contained in the /MIAPM/ASM function group.
Authorizations defined in the SAP_PM_DATATRANSFER role.
For details on configuring SAP security, see the documentation for your SAP system.
About Secured Maintenance Plants

Using your SAP system, you can configure ASI to let you see and work with data (e.g.,
Task Lists) that is specific only to certain Maintenance Plants in that SAP system.
Throughout the ASI documentation, these Maintenance Plants are referred to as secured
Maintenance Plants.
To specify that a Maintenance Plant is secured, using your SAP system, you will need to
add the Maintenance Plant to the /MIAPM/PLANT_CFG table. After you add the desired
Maintenance Plants to the table, they will appear in the grid on the Secured Maintenance
Plants tab on the Implementation Administration page. Then, when you create an
Implementation Package record that is linked to an SAP System record that references
that SAP system, actions that you can perform and SAP values that you can work with
within that Implementation Package will be limited to actions and values that apply only
to those Maintenance Plants.
Note: If the /MIAPM/PLANT_CFG table is empty, no Maintenance Plants will be

secured, meaning that ASI users can see and manage data for ALL Maintenance Plants in
that SAP system.
For example, suppose that the following Maintenance Plants exist in SAP System A:
3000
0001
4000
1000
If you wanted users to be able to create and manage data for only Maintenance Plant
3000, in SAP System A, you could add Maintenance Plant 3000 to the table in SAP. As a
result, the grid on the Secured Maintenance Plants tab would look like the following
image.
Then, you could create an Implementation Package record that is linked to the SAP
System record that references SAP System A.
As a result, actions that you can perform in this Implementation Package would be
limited to actions that apply only to Maintenance Plant 3000. For example, if you tried to
search for a Maintenance Plant from the Plant field in a Task List record, the search
results would contain only Maintenance Plant 3000, as shown in the following image.
Adding a Maintenance Plant to the

/MIAPM/PLANT_CFG Table
To add a Maintenance Plant to the /MIAPM/PLANT_CFG table:
1. On the SAP system, run the following transaction: se16
The Data Browser: Initial Screen appears.
2. In the Table Name text box, type: /MIAPM/PLANT_CFG
3. Click the
button.
The Table /MIAPM/PLANT_CFG Insert screen appears.

4. In the SWERK text box, type the Maintenance Plant that you want to secure.
5. Click the
button.
The entry is saved, and the specified Maintenance Plant is secured.

Note: If desired, you can remove a Maintenance Plant from the /MIAPM/PLANT_CFG
table, which will cause that Maintenance Plant to no longer be secured. For details on
removing entries from tables, see the SAP Help.
Accessing the Implementation

Administration Page
Note: You can access the Implementation Administration page only if you are a member
of the MI ASI Administrator Security Group.
To access the Implementation Administration page:
On the Asset Strategy Implementation Start Page, click the Administration

link.
The Implementation Administration page appears.
Overview of the Implementation

Administration Page
The Implementation Administration page is divided into the following areas:
Administrative Settings workspace: The area that allows you to manage

administrative tasks. This area is divided into the following items:
Work Management Item Definitions tab
Implementation Roles tab
SAP System Definitions tab
PRT Templates tab
Secured Maintenance Plants tab
Implementation Location Preferences section
Paste Options section
are available:
Administration Tasks menu
Common Tasks menu
Work Management Item Definitions Tab

The Work Management Item Definitions tab on the Implementation Administration page
contains a grid that displays a list of the Work Management Item Definition records that
exist in the database. Each row in the grid represents one Work Management Item
Definition record.
Keep in mind from the illustration of the ASI data model that each Work Management
Item Definition record can be linked to one record in each of the following families:
Action Mapping
Execution Mapping
Work Management Item Definition Configuration
The grid in the Work Management Item Definitions section contains the following
columns:
Work Management Item: Contains the hyperlinked family ID of the Work

Management Item Definition record. When you use the scroll bar to view
subsequent columns in the grid, the Work Management Item column remains
frozen in the first position so that you can see the Work Management Item
Definition record represented by that row.
Action Mapping: Contains the hyperlinked name of the Action Mapping record to
which the Work Management Item Definition record is linked. If no Action
Mapping records are linked to the Work Management Item Definition record, the
hyperlink text will be Create Action Mapping, which you can click to create a
new Action Mapping record that is linked to the Work Management Item
Definition record.
An Action Mapping record identifies the mapping that will be invoked when you create a
Meridium APM record, such as an Inspection Task record or a Maintenance Item record,
from an Action.
Execution Mapping: Contains the hyperlinked name of the Execution Mapping

record to which the Work Management Item Definition record is linked. If no
Execution Mapping records are linked to the Work Management Item Definition
record, the hyperlink text will be Create Execution Mapping, which you can click
to create a new Execution Mapping record that is linked to the Work Management
Item Definition record.
An Execution Mapping record identifies the rule that will be invoked when you
implement the Implementation Package. This rule is responsible for creating physical
items in the SAP database.
Definition Configuration: Contains the hyperlinked name of the Work

Management Item Definition Configuration record to which the Work
Management Item Definition record is linked. If no Work Management Item
Definition Configuration records are linked to the Work Management Item
Definition record, the hyperlinked text will be Create Definition Configuration,
which you can click to create a new Work Management Item Definition
Configuration record that is linked to the Work Management Item Definition
record.
A Work Management Item Definition Configuration record identifies the rule that will be
invoked when you right-click a work item node in the tree. The Work Management Item
Definition Configuration records in the baseline Meridium APM database identify rules
that cause additional options to be available on the shortcut menu in the tree. The
following table describes the functionality that is associated with the Work Management
Item Definition Configuration records that are linked to Work Management Item
Definition records in the baseline Meridium APM database.
Work Management
Item Definition
Record

Definition Configuration
Record
Associated Functionality
Allows you to:
Maintenance Plan
Maintenance Plan
Configuration
Copy and paste Maintenance

Plan nodes in the tree.
-AND-
View the Maintenance Plan

Tasks menu.
Allows you to:
Notification
Notification Configuration
Copy and paste Notification

nodes in the tree.
View the Notification Tasks

menu.
Allows you to...
Maintenance Item
Maintenance Item
Configuration
-AND
Object List Item
Object List Item

Configuration
View the Maintenance Item

Tasks menu.
Allows you to copy and paste Object

List Item records in the tree to create
new ones.
Allows you to...
Task List
Copy and paste Task List nodes

in the tree.
Copy and paste Task List nodes

in the tree.
Task List Configuration

-ANDView the Task List Tasks menu.
Allows you to:
Operation
Operation Configuration
Copy and paste Operation
nodes in the tree.
View the Operation Tasks

menu.
Material
Material Configuration
Allows you to copy and paste Material

nodes in the tree.
PRT
PRT Configuration
Allows you to copy and paste PRT

nodes in the tree.
Maintenance Package
Allows you to copy and paste
Configuration
Maintenance Package nodes in the tree.
Unchanged Image: Contains an icon that you can click to see the image that is
used when a record belonging to the family identified in the Work Management
Item column contains the value Unchanged in the Status field. The image will
appear in the tree when the associated work item record is unchanged. If desired,
you can assign a new image to a Work Management Item Definition record to
represent the Unchanged status.
Maintenance Package
Added Image: Contains an icon that you can click to see the image that is used
when a record belonging to the family identified in the Work Management Item
column contains the value Added in the Status field. This icon is used to indicate
that the record is not yet implemented in SAP, with the exception of the following
families for which updates in SAP are not supported. The image will appear in the
tree after the associated work item is added to the tree.
Calibration Task
Inspection Task
If desired, you can assign a new image to a Work management Item Definition record to
represent the Added status.
Modified Image: Contains an icon that you can click to see the image that is used
column contains the value Modified in the Status field. This icon is used to
indicate that the record has been modified and the changes are not yet
implemented in SAP, with the exception of the following families for which
updates in SAP are not supported. The image will appear in the tree after the
associated work item is modified.
Calibration Task
Inspection Task
represent the Modified status.
Deleted Image: Contains an icon that you can click to see the image that is used
column contains the value Deleted in the Status field. This icon is used to indicate
that the record has been deleted in Meridium APM but this change has not yet
been implemented in SAP, with the exception of the following families for which
updates in SAP are not supported. The image will appear in the tree after the
associated work item is marked for deletion.
Calibration Task
Inspection Task
represent the Deleted status.
Implementation Roles Tab

The Implementation Roles tab on the Implementation Administration page contains a grid
that displays a list of Implementation Role records that exist in the database. Meridium
APM does not provide any Implementation Role records, so in the baseline database, this
grid will be empty.
The grid on the Implementation Roles tab contains the following columns:
Image: Contains an icon that you can click to see the image that is defined
for the Implementation Role record. The image will appear in the tree after a
Security User that is assigned to the Implementation Role adds a work item
to the tree on the Packaging <Package ID> page. If desired, you can assign a
new image to an Implementation Role record.
Role Name: Contains the hyperlinked Role Name of the Implementation Role
record. You can click the hyperlink to the view the Implementation Role
datasheet, which displays the Role Name and the Implementation Authorization
records to which the Implementation Role record is linked.
SAP System Definitions Tab

The SAP System Definitions tab on the Implementation Administration page contains a
grid that displays a list of SAP System records that exist in the database. Meridium APM
does not provide any SAP System records, so in the baseline database, this grid will be
empty.
The grid on the SAP System Definitions tab contains the following columns:
SAP System: The hyperlinked name of the SAP System record.

Connection Type: The type of connection that will be used to connect to the SAP
system. The default value is RFC.
Password: A hyperlink that allows you set or modify the password to the SAP
system. If a password has not yet been specified, the hyperlink text is Set
Password, which you can click to display the Enter SAP System Password dialog
box, where you can type the desired password. After you have defined the
password, the hyperlink text is Change Password, which you can click to display
the Enter SAP System Password dialog box, where you can type a new password.
Test Connection: A hyperlink that allows you to test the SAP connection. After
you click the hyperlink, if the connection information is valid, a confirmation
message will appear.
The following image illustrates the SAP System Definitions tab containing one row.
PRT Templates Tab

The PRT Templates tab on the Implementation Administration page contains a grid that
displays a list of PRT Template records that exist in the database. Meridium APM
provides the PRT Template record Simple PRT Template, so in the baseline database, this
grid will contain one row.
The grid on the PRT Templates tab contains the following columns:
Template ID: The hyperlinked ID of the PRT Template record. You can click any
hyperlink to access the datasheet for that PRT Template record.
Template: A hyperlink that allows you modify the document template. After you
create a new PRT Template record, the hyperlink text is Edit Template, which you
can click to display the Document Template window, where you can modify the
document template.
Secured Maintenance Plants Tab

The Secured Maintenance Plants tab on the Implementation Administration page contains
the following items:
SAP System list: Contains the value in the Name field in all SAP System records
that exist in the database. The baseline Meridium APM database does not contain
any SAP System records, so in the baseline database, this list will be empty. If
you have created at least one SAP System record that is set as the default SAP
System, that record will be selected in the list by default. If no SAP System
records are set as the default, nothing will be selected in the list by default, and
you will need to click the

button to select a value.
Grid: Displays a list of secured Maintenance Plants belonging to the SAP system
that is identified by the value in the SAP System list.
Unlike the other tabs on the Implementation Administration page, you cannot add rows to
the grid on the Secured Maintenance Plans tab through the ASI interface. Instead, the grid
displays a list of secured Maintenance Plants that have been added to the
/MIAPM/PLANT_CFG table via the SAP system.
The following image illustrates the Secured Maintenance Plants tab containing multiple
rows.
Note: The Secured Maintenance Plants tab appears only if the ASI for SAP license has
been activated.
Implementation Location Preferences

Section
The Implementation Location Preferences section on the Implementation Administration
page displays a series of text boxes that allow you to manage various administrative
settings.
The Implementation Location Preferences section contains the following text boxes:
Query to locate package for Packaging: Contains the Catalog path to the query
that you want to use to return results on the Implementation Package List page
that you can access via the Packaging link on the Asset Strategy Implementation
Start Page. This text box is populated with the following value in the baseline
database: Public\Meridium\Modules\Asset Strategy

Management\Implementation\Queries\Locate_Packages.
To configure Meridium APM to use a different query, you can click the Browse button to
the right of the text box and browse to the location of the desired query.
Package Builder Project Path: Contains the path to the Rules Library project that
you want to use for determining how the Implementation Packaging Builder
should function. This text box is populated with the following value in the
baseline database: Rules Library\Meridium\Asset Strategy
Management\Implementation\PackageBuilder.
Package Builder Class Name: Contains the name of the class, which exists within
the Rules Library project that is referenced in the Package Builder Project Path
text box, that you want to use for determining how the Implementation Packaging
Builder should function. This text is populated with the value Builder in the
baseline database.
After you make a change to any of the values, you can click the Save button to save the
changes.
Paste Options Section

The Paste Options section on the Implementation Administration page contains the
Display Asset and Action Assignment dialog during paste operations check box, which
you can clear to hide the Asset and Action Assignment window from users who copy and
paste nodes to create new records on the Packaging <Package ID> page.
In the baseline database, the check box is selected.
Administration Tasks Menu
The Administration Tasks menu on the Implementation Administration page contains the
following links:
New Work Management Item: Displays the <empty> (new Work Management
Item Definition) window, where you can create a new Work Management Item
Definition record.
New SAP System: Displays the <empty> (new SAP System) window, where you
can create a new SAP System record.
New Implementation Role: Displays the <empty> (new Implementation Role)

window, where you can create a new Implementation Role record.
New PRT Template: Displays the <empty> (new PRT Template) window, where
you can create a new PRT Template record.
Common Tasks Menu
The Common Tasks menu on the Implementation Administration page contains the
following links:
Page.
Help: Displays the context-sensitive Help topic for the Implementation
Associating an Implementation Package

with a Specific Site
Some companies that use the SAP software have multiple sites, or locations, around the
world. Each site might use its own SAP system.
If desired, you can define these sites and associate each SAP system with the site that
uses it. After you create an Implementation Package and reference an SAP system using
the SAP System field, the Meridium APM system will allow you to add Asset Strategies
to that Implementation Package only if all the underlying equipment or locations belong
to the site that uses that SAP system.
For example, suppose you have the following sites and SAP systems.
Site SAP System
A 100
B
200
You can see that Site A uses SAP System 100 and Site B uses SAP System 200. You
could, therefore, create an Implementation Package record that references SAP System
100 (in the SAP System field), which indirectly references Site A.
In ASM, you might have the following sites, equipment, and Asset Strategies.
Site Equipment Asset Strategy
A Pump 1
Pump Strategy
Tank Strategy
Tank 1
You can see that Site A contains the equipment Pump 1 and Site B contains the
equipment Tank 1. In this case, you could add Pump Strategy to the Implementation
Package because its equipment belongs to the same site (site A) that uses SAP System
100.
You could not, however, add Tank Strategy to the Implementation Package because its
equipment belongs to a different site (site B) than the site that uses SAP System 100 (site
A).
Hiding the Asset and Action Assignment

Window
The Asset and Action Assignment window appears when you copy and paste nodes in the
tree on the Packaging <Package ID> page (if the records represented by the copied nodes
meet certain conditions).
To hide the Asset and Action Assignment window:
On the Implementation Administration page, in the Paste Options section, clear

the Display Asset and Action Assignment dialog during paste operations check
box. When you are finished, the setting should look like the one shown in the
following image.
Baseline Work Management Item

Definition Records
The baseline Meridium APM database contains the following Work Management Item
Definition records, which means that by default, you can add records that belong to these
families to an Implementation Package:
Calibration Task
Inspection Task
Maintenance Item
Maintenance Package
Maintenance Plan
Material
Notification
Object List Item
Operation
PRT
Task List
Thickness Monitoring Task
All baseline Work Management Item Definition records have assigned images, but you
can assign a different image to any existing Work Management Item Definition record. If
you create a new Work Management Item Definition record, in the tree on the Packaging
<Package ID> page, nodes representing records that belong to the corresponding family
will have the default image .
Hint: If you create a new Work Management Item Definition record, you should change
the default image to something more applicable.
Creating a Work Management Item

Definition Record
Note: The following information contain a combination of instructions and examples.
Because the process of creating a Work Management Item Definition record can be
complex, the examples help clarify the steps. To see the examples, within the instructions,
click the text Click here for an example. The examples will be displayed as drop-down
text.
To create a Work Management Item Definition record:

1. On the Implementation Administration page, on the Administration Tasks
menu, click the New Work Management Item link.
The <empty> (new Work Management Item Definition) window appears.
2. In the Family ID list, select the family representing the type of work item record
that you want to add to an Implementation Package. The list displays all families
that are related to the Implementation Package family through the Has Work
Management Item relationship. This field is required.
Click here for an example.
3. In the Group Name list, select the Packaging Tasks shortcut menu to which you
want to add a link that allows you to create work item records in this family. The
list displays the description of all System Codes in the
MI_WKMGMTDF_GROUP System Code Table.
4. If you want to be able to link existing work item records in this family to records
in its predecessor family, accept the default selection in the Allow Link Existing
check box. This will allow you to add existing work item records in the family
that you selected in the Family ID list to records in its predecessor family using
the shortcut menu in the tree on the Packaging <Package ID> page.
-ORIf you do not want to link existing work item records in this family to records in its
successor family, clear the Allow Link Existing check box.
5. If work item records in this family can be linked to a predecessor record in a
family other than the Implementation Package family, click the Parent Family tab.
-ORIf work item records in this family will be created and linked only to the Implementation
Package record, save the record.
6. If you clicked the Parent Family tab in step 5, in the Parent Family ID list, select
the family whose records will be predecessors to work item records that belong to
the family that you selected in the Family ID list. The list displays all families that
are related to the Implementation Package family through the Has Work
Management Item relationship.
Note: Any family that exists in the Parent Family ID field should also exist in the Family
ID field in a separate Work Management Item Definition record. In addition, that Work
Management Item Definition record should be linked to a Work Management Item Child
Definition record whose Child Family ID field contains the appropriate successor family.
Using the preceding example, the value Task Grouping would need to exist in the Family
ID field in a separate Work Management Item Definition record. That Work Management
Item Definition record would also need to be linked to a Work Management Item Child
Definition record whose Child Family ID field contains the value Preventative
Maintenance Task.
7. If you selected a Parent Family ID in step 6, in the Parent Family Relationship ID
list, select the relationship family that relates the family that you selected in the
Family ID list to the family that you selected in the Parent Family ID list.
8. Save the record.
After you have saved the Work Management Item Definition record, you will need to
complete the following steps:
If the family that you selected in the Family ID list is related to a successor family
whose records you want to add to an Implementation Package, create the
appropriate Work Management Item Child Definition record.
If you selected a family in the Parent Family ID list, make sure that the database
contains a separate Work Management Item Definition record that contains that
family in the Family ID field.
Assign an image to the Work Management Item Definition record.
Creating a Work Management Item

Child Definition Record
To create a Work Management Item Child Definition record:
1. Access the Implementation Administration page.

2. On the Work Management Item Definitions tab, in the row containing the
predecessor family to which you want to link new successor records, click the
hyperlink in the Work Management Item cell.
For example, if you want to be able to link new Preventative Maintenance Task records to
Task Grouping records, click the Task Grouping link.
The <Family> (Work Management Item Definition) window appears, displaying a
master/detail datasheet, where the Work Management Item Definition record is the master
record, and the Work Management Item Child Definition record is the detail record.
For example, if you clicked the Task Grouping hyperlink, the Task Grouping (Work
Management Item Definition) window appears.
3. In the Work Management Item Child Definition section below the master record,
in the Child Family ID list, select the successor family whose records you want to
link to records belonging to the family that appears in the Family ID cell. The list
displays all families that are related to the Implementation Package family
through the Has Work Management Item relationship.
For example, if you want to link new Preventative Maintenance Task record to Task
Grouping records, in the Child Family ID list, select Preventative Maintenance Task.
4. In the Child Family Relationship ID list, select the relationship family that relates
the family that appears in the Family ID cell to the family that you selected in the
Child Family ID list.
5. Save the master Work Management Item Definition record.
After you have saved the Work Management Item Definition record, you will need to:
Make sure that the database contains a separate Work Management Item
Definition record whose family ID field contains the family that you selected in
the Child Family ID list in the Work Management Item Child Definition record
that you just created.
Make sure that the Parent family ID field in the separate Work Management Item
Definition record contains the appropriate predecessor family (i.e., the family that
exists in the family ID field in the Work Management Item Definition record that
is linked to the Work Management Item Child Definition record that you just
created).
Assigning an Image to a Work

Management Item Definition Record
To assign an image to a Work Management Item Definition record:
2. On the Work Management Item Definitions tab, locate the column containing the
type of image that you want to change. For example, if you want to change the
image that appears when a Notification record is modified, locate the Modified
Image column.
3. Click anywhere inside the cell of the row containing the Work Management Item
Definition record to which you want to assign a new image.
The image appears in a drop-down window.
4. Right-click the image, and click Load.
5. Navigate to the location of the desired image, select the image, and click the Open
button.
The selected image appears in the drop-down window.
6. Click OK.
The new image is saved and will now be displayed in the tree where applicable.
Creating an Implementation Role

Record
To create an Implementation Role record:
1. On the Implementation Administration page, on the Administration Tasks
menu, click the New Implementation Role link.
The <empty> (new Implementation Role) window appears.

2. In the Role Name text box, type a name for the Implementation Role. Keep in
mind that the name you type will be displayed throughout the interface to identify
the Implementation Role, so be sure to specify a name that will make sense to
your users.
3. Click OK.
The Implementation Role record is saved.
Assigning Implementation Roles to

Individual Security Users
To assign an Implementation Role to individual Security Users:
1. On the Implementation Administration page, on the Implementation Roles tab,
click the hyperlinked Role Name of the Implementation Role record that you want
to use to assign an Implementation Role to individual Security Users.
The <Role Name> (Implementation Role) window appears, where <Role Name> is the
Role Name of the selected Implementation Role record.
2. In the grid in the Implementation Authorization section, in the Authorization Type
list in the first row, select Security User.
3. In the same row, in the Authorized User(s) list, select the Security User to which
you want to assign the Implementation Role.
4. Click OK.
The Implementation Role is assigned to the selected Security User.
Assigning Implementation Roles to All

Users in a Security Group
To assign an Implementation Role to all Security Users that belong to a Security Group:
1. On the Implementation Administration page, on the Implementation Roles tab,
click the hyperlinked Role Name of the Implementation Role record that you want
to use to assign an Implementation Role to all Security Users that belong to a
given Security Group.
The <Role Name> (Implementation Role) window appears, where <Role Name> is the
Role Name of the selected Implementation Role record.
2. In the grid in the Implementation Authorization section, in the Authorization Type
list in the first row, select Security Group.
3. In the same row, in the Authorized User(s) list, select the Security Group to which
you want to assign the Implementation Role.
4. Click OK.
The Implementation Role is assigned to all Security Users that belong to the selected
Security Group.
Assigning an Image to an
Implementation Role Record
After you assign an image to an Implementation Role record, that image will appear in
the tree on the Packaging <Package ID> page when a Security User that is assigned to the
Implementation Role adds a work item to the tree.
To assign an image to an Implementation Role record:
2. On the Implementation Roles tab, in the Image cell of the row containing the
Implementation Role record to which you want to assign a new image, click the
button.
A drop-down window appears.
3. Right-click anywhere inside the drop-down window, and click Load.
4. Navigate to the location of the desired image, select the image, and click the Open
button.
The selected image appears in the drop-down window.
5. Click OK.
The new image is saved and will now be displayed in the tree to group work items that
were created by Security Users with the same Implementation Role.
Creating a New SAP System Record

To create a new SAP System record:
1. On the Implementation Administration page, on the Administration Tasks menu,
click the New SAP System link.
The <empty> (new SAP System) window appears, displaying the SAP System datasheet
for a new SAP System record.
2. In the Name text box, type a name for the SAP System record.
We recommend that you use the format <SYSID>-<CLIENT>, where <SYSID> is the
System ID of the SAP system and <CLIENT> is the Client number. By doing so, the
value in the Name field will match the value that will be populated automatically in the
System ID field when you test the connection to the SAP system.
Note: You do not need to select the Default SAP System? check box. When you create
SAP work items from Action Revision records, Meridium APM uses the SAP system that
is defined in the SAP System record that is linked to the Implementation Package record.
3. In the User ID text box, type a valid User ID that you can use to log in to the SAP
system.
4. In the Password text box, click the
button.
The Enter SAP System Password dialog box appears.

5. In the Enter Password text box, type the password that is associated with the
specified user ID.
6. In the Confirm Password text box, retype the password that you typed in the Enter
Password text box.
7. Click OK.
The password is saved. If needed, you can change the password later.
8. In the Connection String text box:
1. Replace the text SAP_SERVER_IP with the IP address of the SAP Server.
2. Replace the text SAP_System_Number with the SAP System number.
3. Replace the text SAP_CLIENT_NUMBER with the SAP Client number.
4. Delete all angle brackets.
9. In the ITS URL text box:
1. Replace the text its_or_integrated_its_server_url with the ITS Server
information. To locate the ITS Server information:
i.
In SAP, run the following transaction: SE80
Note: If you do not have access to this transaction, contact your SAP
BASIS team for assistance.
ii.
On the toolbar, click Utilities, and then click Settings.
iii.
On the upper-right corner of the screen, click

several times
until the Internet Transaction Server tab appears.
iv.
Click the Internet Transaction Server tab.
The ITS Server information that you must type in the ITS URL text
box in Meridium APM is <Log><Path>, where <Log> is the text in
the Log section and <Path> is the text in the Path section.
2. Delete the angle brackets.

3. At the end of the URL, type: webgui/!
For example, the ITS URL that corresponds with the values in the image above is http://
DOCROAECC6.meridium.com:8000/sap/bc/gui/sap/its/webgui/!
10. Click OK.
The SAP System record is saved. When you create an Implementation Package record,
you can specify that you want to use this SAP System record by selecting it using the
SAP Connection tab.
Changing the Password that You

Specified
To change the password that you specified to an SAP system:
1. On the SAP System Definitions tab, in the row representing the SAP system
whose password you want to specify, click the Change Password link.
The Enter SAP System Password dialog box appears.
2. In the Enter Password text box, type the password that is associated with the user
ID that is defined in the SAP System record.
3. In the Confirm Password text box, type the password that you typed in the Enter
Password text box.
4. Click OK.
The password is saved.
Testing the Connection to an SAP

System
After you have created an SAP System record, you can test the connection information
that you provided in the Connection String field.
To test the connection to an SAP system:
On the SAP System Definitions tab, in the row representing the SAP system
whose connection you want to test, click the Test Connection link.
The connection information that you provided is tested, and a message appears indicating
whether or not the test was successful. In addition, in the SAP System record, the System
ID field is populated automatically with the name of the SAP system, using the format
<SYSID>-<CLIENT>, where <SYSID> is the System ID of the SAP system and
<CLIENT> is the Client number.
The PRT Workflow

The following table lists the steps that are involved in the PRT workflow.
Step Action
Notes
The PRT Template record references a PRT template
file automatically, but the content of the PRT
template file is empty by default.
Create a PRT Template

record.
You can build the content of a template file by

Build the content of the PRT clicking the Edit Template link in the row
template file.
containing the desired PRT Template record on the
Implementation Administration page.
Build an Implementation
You can do so on the Packaging <Package ID> page
Package that includes a Task using the Packaging Tasks menu, the shortcut menu
List record.
in the tree, or the Implementation Package Builder.
Values from the Task List record will be passed in to
the PRT file wherever there is a merge field
referencing a field from the Task List family.
From the Task List record,

build a PRT record.
Likewise, values from the Maintenance Item record

and Maintenance Plan record to which the Task List
record is linked (directly or indirectly) will be
passed in to the PRT file wherever there is a merge
field referencing a field from that family.
Select the Operation record Values from the Operation record will be passed in
to which the PRT record
to the PRT file wherever there is a merge field
should be linked.
referencing a field from the Operation family.
You can associate a file with a PRT record using the
PRT Builder, and you can later view the PRT
document by navigating through the PRT Builder
and selecting to regenerate the PRT document.
Select the PRT template file
on which to base the PRT
file, which will be
The PRT file will contain values from the records to
referenced automatically
which the PRT record is linked. For example, if the
from the PRT record.
Action Revision record Change Oil Filter is linked
to an Operation record, a PRT record that is created
from that Operation record will reference a PRT file
that contains values from that Action Revision
record.
Values from the Action Revision records will be

Select the Action Revision
passed in to the PRT file wherever there is a merge
records whose values should
field referencing a field from the Action Revision
be inserted into the PRT file.
family.
Based on the State Configuration that is defined for

Package the Implementation the Implementation Package family, this step is
Package.
required before you can implement the
Implement the
The PRT record is transferred to the SAP system as

a PRT, and the PRT file is transferred to the SAP
system as a Microsoft Word document that is
referenced from the PRT.
Creating a PRT Template Record

To create a new PRT Template record:
1. On the Implementation Administration page, on the Administration Tasks menu,
click the New PRT Template link.
The <empty> (new PRT Template) window appears, displaying the PRT Template
datasheet for a new PRT Template record.
2. In the ID text box, type an identifying name for the PRT Template record.
3. Click OK.
The PRT Template record is saved.
Building a PRT Template File

After you create a PRT Template record, you can build a PRT template file that will be
referenced from the PRT Template record. You can use the following instructions to build
the PRT template file for the first time or modify one after it has already been built.
To create a PRT template file:
2. Click the PRT Templates tab.
3. In the row containing the PRT Template record that you want to associated with a
new PRT template file, click the Edit Template link.
The Document Template window appears.
4. Use the Document Template window to create the PRT template file.
5. When you are finished creating the PRT template file, click OK.
Aspects of the Document Template

Window
The Document Template window appears when you choose to build a PRT template file.
The following image shows the Document Template window that appears when you
choose to modify the PRT template file that is referenced from the baseline record Simple
PRT Template.
The Document Template window contains the following items:
Toolbar: Contains items that let you format the content of the file and insert merge
blocks and merge fields. The Add Merge Block and Add Merge Field buttons are
explained in this documentation. The remaining options function the same way
that they function in Microsoft Word and are not explained in this documentation.
For details on using these options, see the Microsoft Word documentation.
Horizontal ruler: A ruler that measures the width of the page. The horizontal ruler
functions the same way that it functions in Microsoft Word and is not explained in
this documentation. For details on using the horizontal ruler, see the Microsoft
Word documentation.
Vertical ruler: A ruler that measures the length of the page. The vertical ruler
functions the same way that it functions in Microsoft Word and is not explained in
this documentation. For details on using the vertical ruler, see the Microsoft Word
documentation.
Page: The workspace where you can insert text, merge blocks, merge fields,
tables, images, and other content. The page contains standard copy, cut, and paste
functions and other functions that are supported within the body of a Microsoft
Word document.
OK button: Saves any changes that you have made to the file.
Cancel button: Discards any changes that you have made to the file and returns
you to the Implementation Administration page.
About the Content of the PRT Template

File
A PRT template file contains content that will be used as the basis for creating a PRT file.
When you create a new PRT Template record, it will be associated with a PRT template
file automatically. The file will not, however, contain any content. The organization and
structure of the content is up to you. Because PRT template files are used to build PRT
files that are transferred to your SAP system, you will need to build the content according
to any company standards and guidelines for these files. For example, you might want to
add your company logo, copyright information, and so on.
While the Meridium APM system does not enforce any guidelines regarding the content
of the file, at a minimum, a PRT template file should contain at least one merge field and
one merge block. Most likely, the PRT template files that you build will contain many
merge fields and merge blocks. Beyond merge fields and merge blocks, PRT template
files can include any other content (text, images, or tables) that you want to include in the
Microsoft Word documents that will be generated from them.
What is a Merge Field?

A merge field is a reference from a PRT template file to any field within any of the
following families:
Maintenance Plan
Maintenance Item
Task List
Operation
Action Revision
You will want to insert merge fields into PRT template files to create placeholders for the
actual data that will be inserted into the PRT files that are built from them. In the end, a
PRT file will contain a specific field value whereas the PRT template file contains only a
reference to the field whose value should be inserted.
More specifically, PRT files are referenced from PRT records, which are linked to other
records in the ASI data model. When you build a PRT file, the Meridium APM system
locates the records to which the PRT record is linked. It then replaces each merge field in
the source PRT template file with the actual value that is stored in that field in the
associated record.
When you add a merge field to a PRT template file, the following text appears in the file:
<<(<Family Caption>) - <Field Caption>>>
...where:
<Family Caption> is the caption of the family that contains the field.
<Field Caption> is the caption of the selected field.
For example, the PRT template file that is referenced from the baseline PRT Template
record contains the merge field Description from the Action Revision family. The
following line of text appears in the file where this merge field exists:
<<(Action Revision) - Description>>
This merge field is outlined in red in the following image.
Suppose you create a PRT record that is linked (indirectly) to an Action Revision record
with the following value in the Description field:
Perform full spectrum vibration monitoring. Establish baseline and action levels. Trend
results.
If you build the PRT file from the baseline PRT template file, the PRT file will look like
Note that where the PRT template file contains the text <<(Action Revision) Description>>, the PRT file contains the actual value that is stored in the Description
field in the Action Revision record.
What is a Merge Block?

A merge block is a group of merge fields that reference fields in the same family. Each
merge field in a PRT template file must exist within a merge block.
When a PRT file is built from a PRT template file, values do not replace merge blocks
like they replace merge fields. The merge blocks are required in order for the Meridium
APM system to generate the PRT file accurately without error. Beyond supporting the
Meridium APM code, merge blocks do not serve any functional purpose.
When you add a merge block to a file, the merge block is represented by opening and
closing symbols. For example, consider the following image, where the red arrows
point to the two merge block symbols before and after the Maintenance Item merge
fields.
These merge fields exist within a single merge block, and that merge block is defined by
the opening and closing merge block symbols.
For guidelines on adding merge blocks, see the Tips for Adding Merge Fields and Merge
Blocks in this documentation.
Adding a Merge Field

Note: Before adding merge fields to a PRT template file, see the Tips for Adding Merge
Fields and Merge Blocks in this documentation.
To add a merge field to a PRT template file:
1. Place your cursor in the workspace in the Document Template window.
2. On the toolbar, click the Add Merge Field button.
The Insert Field dialog box appears.
3. In the Name list, select the field to which you want to add a reference. Each value
in the list appears using the format (<Family Caption> - <Field Caption>), where
<Family Caption> is the caption of the family to which the field belongs, and
<Field Caption> is the caption of the field. For example, the Category field in the
Maintenance Plan family is listed as (Maintenance Plan) - Category.
4. Click OK.
The merge field is added to the file.
Adding a Merge Block

Note: Before adding merge blocks to a PRT template file, see the Tips for Adding Merge
Fields and Merge Blocks in this documentation.
To add a merge block to a PRT template file:
1. In the Document Template window, place the cursor before the first merge field
that you want to add to the merge block (including the empty space before the
merge field), and drag the cursor to select all the merge fields that you want to add
to the merge block (including the empty space after the merge field).
2. On the toolbar, click the Add Merge Block button.
The Insert Block dialog box appears.
3. In the Name list, select the family of the selected merge fields. For example, if
you selected merge fields from the Operation family, you would select Operation.
4. Click OK.
The merge block is added to the file.
Tips for Adding Merge Fields and

Merge Blocks
Note the following guidelines about adding content to a PRT template file:
Each merge field must exist within a merge block.

Before you add a merge block, you must add all the merge fields that will belong
to that merge block.
Each merge block can contain merge fields from only one family.
To add a merge block, the file must contain at least one empty space before the
first merge field and one empty space after the last merge field, where neither
empty space is part of the merge field itself. To determine if an empty space is
part of a merge field, you can type any character in the space. If the character is
highlighted in grey, the space is still considered part of the merge field.
To prevent problems, before adding merge fields that will belong to the same merge
block, press the Enter key several times in the file to create the rows on which these
merge fields will reside. The number of times you should press the Enter key should
exceed the number of merge fields that you plan to add by at least two. This will ensure
that one empty space exists before the first merge field and one exists after the last merge
field.
For example, if you want to add three merge fields from the Action Revision family:
1.
1. Before adding the first one, place the cursor on an empty line, and press
the Enter key five times.
2. Place the cursor on the second line that you added, and add the first merge
field.
3. Add the second and third merge fields on the second and third lines that
you added.
4. After you have added the third merge field, place the cursor on the next
row and type any character. If the character is not highlighted in grey, you
can delete the character and include that empty space when you add the
merge block.
Merge fields and merge blocks cannot be removed or modified after they are
added.
Specifying the Packaging Query

The packaging query is used on the Implementation Package List page that appears when
you click the Package link on the Asset Strategy Implementation Start Page. By default,
this page returns the results of the following query: \\Public\Meridium\Modules\Asset
Strategy Management\Implementation\Queries\Locate_Packages.
If desired, you can specify that you want to see the results of a different query when you
click the Package link on the start page.
The query that you want to specify has been saved to the Meridium APM Catalog.
You have View permissions to the Catalog in which the desired query is located.
To specify the packaging query:

2. In the Implementation Location Preferences section, to the right of the Query to
locate package for Packaging text box, click the Browse button.
The Save As dialog box appears.
3. Navigate to the folder containing the query that you want to use as the packaging
query, select the query, and click the Open button.
The Query to locate package for Packaging text box is populated with the path to the
query that you selected.
The selected query will now be used.
ASI Workflow
Depending on the type of records that you want to create from an Action, the workflow
that you follow in ASI will vary. The following workflow describes the basis tasks that
you can perform within ASI and provides a general order in which you should perform
them. This workflow assumes that all installation, upgrade, and configuration tasks have
already been completed.
In general, you will need to perform the following tasks in ASI:
1. Create an Implementation Package record.
2. Add Asset Strategies to the Implementation Package.
3. Add work item records to the Implementation Package.
4. Package the Implementation Package.
5. Implement the Implementation Package.
About Starting an Implementation

Package
An Implementation Package record stores details about an Implementation Package and
connection information to the SAP system in which the Implementation Package will be
implemented. The Implementation Package record is the root record of the
Implementation Package. All other records that make up the Implementation Package will
be linked to the Implementation Package record.
You can create an Implementation Package record via the following pages:
Asset Strategy Implementation Start Page
Implementation Package List
Using either of these methods, you will define the Implementation Package record on the
Implementation Package Creation page.

Creation Page
To access the Implementation Package Creation page:
On the Asset Strategy Implementation Start Page, click the Create Package link.
On the Implementation Package List page, on the Common Tasks menu, click the
Create Package link.
-or-
The Implementation Package Creation page appears, displaying a new blank

Implementation Package record in the Implementation Package Details section.
Aspects of the Implementation Package

Creation Page
The Implementation Package Creation page appears after you:
Click the Create Package link on the Asset Strategy Implementation Start Page.
Click the Create Package link on the Common Tasks menu on the Implementation
Package List page.
The Implementation Package Creation page contains the following items:
Implementation Package Details section: Displays the datasheet for the

Implementation Package record. In the baseline database, the datasheet contains
two tabs: Package Details and SAP Connection.
Asset Strategies for Package section: Contains a grid that displays the Asset
Strategy records that are linked to the Implementation Package record. Each row
in the grid represents one Asset Strategy record. The buttons in this section are
disabled until you save the Implementation Package record, in which case the
page is relabeled Implementation Package Update.
Task menus pane: Contains the Common Tasks menu.
After you save the Implementation Package record, the page will be refreshed and
renamed the Implementation Package Update page.
Common Tasks Menu

The Common Tasks menu on the Implementation Package Creation page contains the
following links:
View Package: This link is always disabled on this page.

Save: Saves the Implementation Package record.
Send To: This link is always disabled on this page.
Help: Displays the context-sensitive Help topic for the Implementation Package
Creation page.
Creating Implementation Package

Records from the Asset Strategy
To create an Implementation Package record from the Asset Strategy Implementation
Start Page:
1. Access the Implementation Package Creation page.
2. In the ID text box, type an ID for the Implementation Package record.
3. In the Description text box, type a description for the Implementation Package.
4. If you want to create SAP work items when the Implementation Package is
implemented, click the SAP Connection tab.
Note: If you do not want to create SAP work items when the Implementation Package is
implemented, continue to step 8.
The SAP Connection tab appears.
5. In the SAP System text box, click the
button.
The Find Items window appears. The Search In list contains the value SAP System. You
cannot select another value.
6. Perform a search for the SAP System record representing the SAP system in
which you want to create SAP work items when the Implementation Package is
implemented.
The results appear in the search results section of the window.
7. Select the row containing the SAP System record to which you want to link the
Implementation Package record, and click the Open button.
The Implementation Package Creation page returns to focus, and the SAP System text
box is populated with the Record ID of the selected record.
8. On the Common Tasks menu, click the Save link.
The Implementation Package record is saved and linked to the selected SAP System
record. In addition, the page is refreshed and renamed the Implementation Package
Update page. At this point, you can add Asset Strategies to the Implementation Package.

List Page
The Implementation Package List page provides tools that you can use to search for an
existing Implementation Package record and then open that record from the search
results.
To access the Implementation Package List page:
1. Access the Asset Strategy Implementation Start Page.
2. Click the Search for Package link.
The Implementation Package List page appears.

List Page
The Implementation Package List page contains the results of the query that is specified
in the Query to locate Implementation Package text box on the Implementation
Administration page. This documentation assumes that you are using the baseline
Locate_Packages query, which contains the following prompts that appear as lists at the
top of the Implementation Package List page:
State: Contains a list of record states that have been configured for the
Implementation Package family. You can choose from the following baseline
states:
All: Displays all the existing Implementation Package records that are in
any state.
Draft: Displays the Implementation Package records that are in the Draft
state.
Implemented: Displays the Implementation Package records that are in the

Implemented state.
Modified: Displays the Implementation Package records that are in the

Modified state.
Packaged: Displays the Implementation Package records that are in the

Packaged state.
Partially Implemented: Displays the Implementation Package records that

are in the Partially Implemented state.
Implementation Role: Contains the value All and the list of Implementation Roles
representing the Implementation Role records that exist in the database.
This query is run automatically using the default prompt value in both prompts: All. If
you select different criteria, you can click the Run Query button to run the query and
display the results in the grid at the bottom of the page. The query results will include
hyperlinked Record IDs, which you can use to open the Implementation Package records
on the Packaging <Package ID> page, where <Package ID> is the ID of the selected
Below the query results are options that you can use to navigate the results.
The Implementation Package List page contains one task menu, Common Tasks.
Note: If you access the Implementation Package List page from an ASM - System
Strategy Overview page or an ASM - Unit Strategy Overview page, the query that is run
will differ from the one described here and return results based on the System Strategy or
Unit Strategy you are viewing.
Common Tasks Menu

The Common Tasks menu on the Implementation Package List page contains the
following links:
Create Package: Displays a new blank Implementation Package record on the

Implementation Package Creation page.
Delete Package: Displays a confirmation message, and then deletes the selected
records. Under some circumstances, the Implementation Package record cannot
be deleted.
Sent To: Displays a submenu with options that let you provide a link to the current
page on your desktop (create shortcut), in an email message, or on a Home Page.
Help: Displays the context-sensitive help topic for the Implementation Package
List page.
Opening an Existing Implementation

Package
To open an existing Implementation Package:
1. Access the Implementation Package List page.
2. Locate the row containing the Implementation Package that you want to open.
Hint: You can use the State and Implementation Role lists above the grid to filter the
Implementation Packages that are returned in the results.
3. In the grid, click the hyperlinked ID of the Implementation Package.
The Implementation Package appears on the Packaging <Package ID> page, where
<Package ID> is the ID of the selected Implementation Package.
Aspects of the Packaging Page

The Packaging <Package ID> page, where <Package ID> is the ID of the Implementation
Package record, is divided into the following areas:
Task Menus pane: Displays the following task menus:
State Configuration Tasks
Packaging Tasks
Maintenance Plan Tasks
Note: This menu appears only when a Maintenance Plan node is selected in the tree.
Task List Tasks
Note: This menu appears only when a Task List node is selected in the tree.
Maintenance Item Tasks
Note: This menu appears only when a Maintenance Item node is selected in the tree.
Operation Tasks
Note: This menu appears only when an Operation node is selected in the tree.
Notification Tasks
Note: This menu appears only when a Notification node is selected in the tree.
Asset Strategy Tasks
Action Tasks
Common Tasks
Associated Pages
The left pane, which contains a tree containing nodes representing records.
The datasheet for the record that is currently selected in the tree.
The Unpackaged Actions tab.
The Packaged Actions tab.
The Externally Packaged Actions tab.
Note: Throughout the rest of this documentation, we refer to this page as the Packaging
page.
State Configuration Tasks Menu

The State Configuration Tasks menu on the Packaging page displays links that allow you
to change the state of the Implementation Package record. The links that are available
depend upon the State Configuration that is defined for the Implementation Package
family and the current state of the selected Implementation Package records.
In addition, if the Security User who is currently logged in is not assigned to the current
state of the Implementation Package record, links on the State Configuration Tasks menu
will be disabled if the corresponding action would cause the state of the Implementation
Package record to change.
Packaging Tasks Menu

The Packaging Tasks menu on the Packaging page contains the following links:
Operator Rounds: Displays a submenu from which you can choose to create a
Measurement Location Group record or a Measurement Location record. After
you create the record, it will be represented by a new node in the tree.
Tasks: Displays a submenu from which you can choose to create a Calibration
Task record, Inspection Task record, or Thickness Monitoring Task record. After
you create the record, it will be represented by a new node in the tree.
SAP: Displays a submenu from which you can choose to create any of the
following records:
Maintenance Plan
Maintenance Item
Object List Item
Task List
Operation
Material
PRT
Maintenance Package
After you create the record, it will be represented by a new node in the tree.
Maintenance Plan Tasks Menu

The Maintenance Plan Tasks menu appears on the Packaging page only when a
Maintenance Plan node is selected in the tree.
This menu contains one link, Append Standard Text, which displays the Select Standard
Text window, where you can search in SAP for the standard text value that you want to
append to the value in the Long Text field in the Maintenance Plan record.
Task List Tasks Menu

The Tasks List Tasks menu appears on the Packaging page only when a Task List node is
selected in the tree. The Task List Tasks menu contains the following links:
Manage Package Assignments: Displays the Assign Maintenance Packages for

Task List window, where you can view and manage the Maintenance Package
records that are linked to the Operation records that are linked to the selected Task
List record. This link is enabled only if the following conditions are met:
In the tree, you have selected a Task List node representing a Task List
record whose Maintenance Strategy field contains a value.
-AND
o
An SAP system is associated with the Implementation Package.
Build PRT: Displays the PRT Builder, which you can use to create PRT records.
This link is enabled only if the Implementation Package is in a state other than
Implemented.
Append Standard Text: Displays the Select Standard Text window, where you can
search in SAP for the standard text value that you want to append to the value in
the Long Text field in the Task List record.
Maintenance Item Tasks Menu

The Maintenance Item Task menu appears on the Packaging page only when a
Maintenance Item node is selected in the tree. This menu contains the following links:
Maintain Object List: You can use this link to manage the Object List records that
are linked to the Maintenance Item record represented by the selected node.
Append Standard Text: Displays the Select Standard Text window, where you can
search in SAP for the standard text value that you want to append to the value in
the Long Text field in the Maintenance Item record.
Locate Task List: Displays the Locate Task List window, where you can search for
the SAP Task List that you want to use to create a new Task List record.
Note: The Locate Task List link is enabled only if the Maintenance Item record
represented by the selected node is not already linked to a Task List record. Also, the
Implementation Package record must be in a state that allows it to be modified (e.g.,
Draft).
Synchronize Reference Object: Copies the value in the Equipment or Functional

Location field in the Maintenance Item record to the Equipment or Functional
Location field in the Task List record to which it is linked.
Note: This link is enabled only if the Maintenance Item record is linked to a Task List
record that does not represent a Reference Task List.
Operation Tasks Menu
The Operation Tasks menu appears on the Packaging page only when an Operation node
is selected in the tree.
append to the value in the Long Text field in the Operation record.
Notification Tasks Menu

The Notification Tasks menu appears on the Packaging page only when a Notification
node is selected in the tree.
append to the value in the Description field in the Notification record.
Asset Strategy Tasks Menu

The Asset Strategy Tasks menu on the Packaging page contains the following link:
Navigate: Displays the Select Package for Navigation window, which displays the
results of the Catalog query Locate Packages for Navigation. By default, the
query is configured to display all Implementation Packages (except for the current
Implementation Package) that contain one or more of the Asset Strategies that
belong to the current Implementation Package. You can use the query results to
select the Implementation Package to which you want to navigate.
This link is enabled only if the current Implementation Package contains at least one
Asset Strategy that belongs to at least one other Implementation Package.
Action Tasks Menu

The Action Tasks menu on the Packaging page contains the following links:
Build: Displays a submenu with options that let you create work item records
from the selected Actions. This link is enabled only if you have selected an Action
on the Unpackaged Actions tab.
Apply Updates: Updates the work item record represented by the selected node
with the updated values in the associated Action. This button is enabled only if
you have selected a node that is associated with an Action to which a change has
been made (causing a new Action Revision record to be created).
Link Action: Associates the selected Action with the work item represented by the
selected node. This link is enabled only if you have selected an Action on the
Unpackaged Actions tab and a work item node in the tree.
Unlink Action: Removes the association between the selected Action and the
work item represented by the selected node. This link is enabled only if you have
selected an Action on the Packaged Actions tab and the associated work item node
in the tree.
Move To: Displays a submenu with the following options:
Primary Package: Transfers the selected Action back to its original

primary Implementation Package. This option is enabled only if you are
viewing a secondary Implementation Package.
New Secondary Package: Displays the New Secondary Package
(Implementation Package) window, where you can define the ID and
description of the new Implementation Package to which you want to
transfer the selected Action.
Existing Secondary Package: Displays the Existing Secondary Package

window, where you can select the existing Implementation Package to
which you want to transfer the selected Action.
The Move To link is enabled only if you have selected an Action on the Unpackaged
Actions tab.
Note: All functionality that is available from the Action Tasks menu is also available
from the shortcut menu in the grids on the Unpackaged Actions and Packaged Actions
tabs, as appropriate. For example, to associate an Action with an existing work item
record, you can select the Action on the Unpackaged Actions tab and click the Link
Action link on the Actions Tasks menu, or you can select the Action in the grid, rightclick the grid, and then click Link Action on the shortcut menu. The instructions in this
documentation explain how to use the Actions Tasks menu. If you prefer to use the
shortcut menu, however, the labels on the shortcut menu are the same as those on the
Action Tasks menu.
Common Tasks Menu

The Common Tasks menu on the Packaging page contains the following links:
Save <Package ID>: Saves any changes that you have made to the currently
displayed datasheet. This link is enabled only if the Implementation Package
record is in the Draft or Modified state.
Strategy Links: Displays the Implementation Package Update page, where you
can add Asset Strategies to the Implementation Package or remove Asset
Strategies from the Implementation Package.
Page.
Help: Displays the context-sensitive Help topic for the Packaging page.
About the Tree

The tree on the Packaging page displays various nodes, where each node in the tree
represents a Meridium APM record. The root node of the tree always represents the
Implementation Package record. Each node that represents an SAP item (e.g.,
Maintenance Item) has an icon that indicates the status of the corresponding SAP item.
You can select a node in the tree to see the datasheet for that record to the right of the
tree. In addition, as you select nodes in the tree, the rows in the grid on the Packaged
Actions tab change. The grid on the Packaged Actions tab displays only those Actions
that were used to create a work item record.
If an Action was used to create a work item record, to remove the association (i.e., unlink
the Action Revision record from the work item record), you can select the node that
represents that record and click the Unlink Action link on the Action Tasks menu. For
example, if an Action was used to create an Inspection Task record, you can select the
Inspection Task node in the tree, then select the row containing the associated Action on
the Packaged Action tab, and then click the Unlink Action link.
To re-associate an Action with a record that represents a work item, you can select the
node that represents that record and then click the Link Action link on the Action Tasks
menu.
When you select any node other than the Implementation Package node, a new tab
appears at the bottom of the tree, displaying the ID of the selected node as it appears in
the tree. When you click this tab, that node appears at the root level in its own tree with
nodes that represent the records that are linked to the record represented by the root-level
node. Within this documentation, we refer to this feature as the zoomed tree view.
You can also use the shortcut menu in the tree to work with the records in the tree.
Below the tree, you will see a list that allows you to filter the nodes in the tree according
to the Implementation Role with which they are associated. The list contains the
following options:
Show all Work Management Items: Displays all nodes in the tree.
Filter Package by Implementation Roles: Displays only the nodes that are
associated with the Implementation Role that is assigned to the Security User who
is currently logged in.
Note: If a Super User is logged in, ALL nodes will be displayed even if the Super User
selects Filter Package by Implementation Roles.
Zoomed Tree Tab

When you are viewing the tree on the Packaging page, you can select any node in the tree
to work with that record and its linked records within its own tree. When you select any
node other than the Implementation Package record (i.e., the root node when you open
the Packaging page), a new tab will appear at the bottom of the tree, displaying the ID of
the currently selected node, as shown in the following image. A red outline has been
added to the following image to highlight this tab.
When you select this tab, the Meridium APM system will zoom to that location in the
tree, displaying the selected node at the root level in its own tree. Only the selected node
and its associated nodes will appear in the tree in the zoomed tree view, as shown in the
following image.
This view offers the same functions as the tree that appears by default when you open the
Packaging page, where the Implementation Package node is displayed at the root level.
Images Displayed for SAP Items

On the Packaging page, the tree contains nodes representing items that you want to
implement. All nodes representing SAP items contain an image representing the status of
the Meridium APM record relative to its SAP counterpart.
If the Meridium APM record has never been sent to SAP (i.e., an SAP counterpart does
not exist for that record), the tree will display an image with a green plus sign in the
lower right corner. For example, if a Maintenance Item record has never been used to
create an SAP Maintenance Item, the tree will display the
image.
If, however, a Meridium APM record has been modified or deleted since it was last sent
to SAP, the image will contain either a blue gear or a red X, where:
A blue gear indicates that the record has been modified. For example, if a
Maintenance Item record has been modified since it was sent to SAP to create a
new Maintenance Item, you would see the
image.
A red X indicates that the record has been flagged for deletion. For example, if the
Maintenance Item record has been flagged for deletion since it was last sent to
SAP (but the Maintenance Item has not yet been deleted in SAP), you would see
the
image.
Finally, if the Meridium APM record has remained unchanged since it was last sent to
SAP, the tree will display the standard image without any overlaying icons. For example,
if a Maintenance Item record has not changed since it was last sent to SAP, you would see
the image.
The following table lists the baseline images that are associated with the statuses of
Meridium APM records relative to their SAP counterparts.
Meridium APM Record New Modified Deleted Unchanged

Maintenance Plan
Maintenance Item
Notification
Object List Item
Operation
Material
PRT
Maintenance Package
Unpackaged Actions Tab

The Unpackaged Actions tab displays a list of Actions that:
Belong to the underlying Asset Strategies and that are not yet associated with a
work item record. After you select one of these Actions on the Unpackaged
Actions tab, you can:
Create a new work item record from it.
Associate it with an existing work item record.
-or-
Are already associated a work item record, but the Action has been modified in
ASM, creating an Action Revision record. After you select one of these Actions
on the Unpackaged Actions tab, you can update the work item record with which
it is associated to reflect the latest changes in ASM. You will know that an Action
has been modified since being associated with a work item if the Revision
Operation column contains the
icon.
Note: An Action Revision record is created only when you activate the Asset Strategy
containing the modified Action. Modifying an Action without activating the Asset
Strategy does not result in an Action Revision record, meaning that the updates will not
be reflected on the Unpackaged Actions tab.
The following image shows an example of the Unpackaged Actions tab.
The Unpackaged Actions tab contains a grid, grouped by Asset Strategy, where each row
in the grid represents an Action that belongs to an underlying Asset Strategy. Specifically,
the grid displays Action Revision records, and the following columns are displayed:
Revision Operation: An icon indicating the status of the Action Revision record.
These icons are identical to the icons that are displayed in ASM for Actions and
Risks.
Name: The value (formatted as a hyperlink) in the Name field in the Action
Revision record. You can click any hyperlink in this column to display the
datasheet for the Action Revision record.
Interval: The value in the Interval field in the Action Revision record.
Interval Units: The value in the Interval Units field in the Action Revision record.
Mandatory: A check box reflecting the value in the Mandatory field in the Action
Revision record. If the value in the field is set to True, the check box is selected.
If the value in the field is set to False, the check box is cleared.
Nonrecurring: A check box reflecting the value in the Nonrecurring field in the
Action Revision record. If the value in the field is set to True, the check box is
selected. If the value in the field is set to False, the check box is cleared.
Implementation Role: The value in the Implementation Role field in the Action
Revision record.
Work Management Item ID: The Record ID (formatted as a hyperlink) of the

work item record that is associated with the Action Revision record. This column
contains a value only if a new Action Revision record has been created since the
associated work item record was last updated. You can click any hyperlink in this
column to navigate in the tree directly to the node that is associated with the
Action Revision record.
Packaged Actions Tab

The Packaged Actions tab on the Packaging page displays a list of Actions that belong to
the underlying Asset Strategies and that are already associated with a work item record. If
you select a node in the tree and its successor nodes are associated with an Action, that
Action will appear on the Packaged Actions tab when you select either the predecessor or
the successor node in the tree.
For example, suppose an Action is used to create an Operation record. If the Operation
record is linked to a Task List record, the Action will appear on the Packaged Actions tab
when you select either the Task List node or the Operation node in the tree.
The following image shows an example of the Packaged Actions tab.
The Packaged Actions tab contains a grid, grouped by Asset Strategy, where each row in
the grid represents an Action that is associated with a work item record. Specifically, the
grid displays Action Revision records, and the following columns are displayed:
Risks.
Implementation Role: The value in the Implementation Role field in the Action
Revision record.
Work Management Item ID: The Record ID (formatted as a hyperlink) of the

work item record that is associated with the Action Revision record. This column
contains a value only if a new Action Revision record has been created since the
associated work item record was last updated. You can click any hyperlink in this
column to navigate in the tree directly to the node that is associated with the
Action Revision record.
Externally Packaged Actions Tab
The Externally Packaged Actions tab on the Packaging page displays a list of Actions that
have been transferred from the current primary Implementation Package to another
Implementation Package. The following image shows an example of the Externally
Packaged Actions tab.
The Externally Packaged Actions tab contains a grid, grouped by Asset Strategy, where
each row in the grid represents an Action that has been transferred from the current
primary Implementation Package to another Implementation Package. Specifically, the
grid displays Action Revision records, and the following columns are displayed:
Risks.
Implementation Package: The value (formatted as a hyperlink) in the Name field

in the Implementation Package to which the Action was transferred. You can click
any hyperlink in this column to navigate to that Implementation Package.
About Adding Asset Strategies to

After you create an Implementation Package record, you can add one or more Asset
Strategies to the Implementation Package for the purpose of creating work item records
from the Actions that belong to those Asset Strategies. If an Implementation Package is
associated with a specific site, you can add Asset Strategies to it only if their underlying
equipment or locations are associated with that site or are not associated with any site.
You can add an Asset Strategy to an Implementation Package via the Implementation
Package Update page.

Update Page
You can use the Implementation Package Update page to add Asset Strategies to an
Implementation Package. You can access the Implementation Package Update page via
the following methods:
Saving a new Implementation Package record.

Clicking the Strategy Links link on the Common Tasks menu on the Packaging
page.
The following instructions provide details on accessing the Implementation Package

Update page using the Strategy Links link on the Common Tasks menu on the Packaging
page.
To access the Implementation Package Update page via the Strategy Links link on the
Common Tasks menu on the Packaging page:
1. Open the Implementation Package to which you want to add additional Asset
Strategies.
The Packaging page appears.
2. On the Common Tasks menu, click the Strategy Links link.
The Implementation Package Update page appears.

Update Page
The Implementation Package Update page provides options that you can use to add Asset
Strategies to the Implementation Package. The Implementation Package Update page
contains the following sections:
Implementation Package Details: Contains the datasheet for the Implementation

Package record representing the current Implementation Package.
Asset Strategies for Package: Contains a grid that displays the Asset Strategy
records that are linked to the Implementation Package record. Each row in the
grid represents one Asset Strategy record. For each Asset Strategy record that
appears in the grid, the following information is displayed:
Strategy ID: The value stored in the Asset ID field in the Asset Strategy
record. This value appears as a hyperlink, which you can click to view the
Asset Strategy in ASM.
Asset Name: The value stored in the Asset Name field in the Asset
Strategy record.
Description: The value stored in the Description field in the Asset Strategy
record.
Add Asset Strategies: Displays the Select Asset Strategies to Add to

Package window, from which you can select the Asset Strategies that you
want to add to the Implementation Package. The Select Asset Strategies to
Add to Package window displays results of the Locate Strategies to
Package query by default. This query is stored in the Meridium APM
Catalog folder \\Public\Meridium\Modules\Asset Strategy
Management\Implementation\Queries.
Remove Asset Strategy: Deletes the link between the selected Asset
Strategy record and the Implementation Package record. This button is
enabled only when Asset Strategies appear in the Asset Strategies for
Package grid.
The Implementation Package Update page contains one task menu, Common Tasks.
Common Tasks Menu

The Common Tasks menu on the Implementation Package Update page contains the
following links:
View Package: Displays the Packaging page for the current Implementation
Package.
Save: Saves the Implementation Package.
Delete: Displays a confirmation message and then deletes the Implementation

Package record. Under some circumstances, the Implementation Package record
cannot be deleted.
Page.
Help: Displays the context-sensitive Help topic for the Implementation Package
Update page.
Adding Asset Strategies to an

When you add Asset Strategies to an Implementation Package, you are linking the Asset
Strategy records to the Implementation Package record. Keep in mind that if the
Implementation Package is associated with a specific site, you can add Asset Strategies to
it only if their underlying equipment or locations are associated with that site or are not
associated with any site.
In addition, when you try to add an Asset Strategy to the Implementation Package record,
the Meridium APM system checks the SAP system that is associated with the Asset
Strategy to see if it matches the SAP system that is associated with the Implementation
Package. Only Asset Strategies whose associated SAP system matches the SAP system
that is associated with the Implementation Package will be added to the Implementation
Package.
To add Asset Strategies to an Implementation Package:
1. Access the Implementation Package Update page.
2. At the bottom of the page, click the Add Asset Strategies button.
The Select Asset Strategies to Add to Package dialog box appears, displaying a list of all
Active Asset Strategies that do not currently belong to an Implementation Package.
3. In the grid, select the rows containing the Asset Strategies that you want to add to
the Implementation Package, and click the Add to Package button.
The selected Asset Strategies appear in the grid in the Asset Strategies for Package
section.
The Implementation Package record is linked to the selected Asset Strategy records.
Removing Asset Strategies from an

You can remove an Asset Strategy from an Implementation Package only if none of the
Actions that belong to that Asset Strategy are currently associated with a work item
record. If you try to do so, a message will appear, indicating that the Asset Strategy could
not be removed from the Implementation Package.
To remove an Asset Strategy from an Implementation Package:

1. Open the Implementation Package from which you want to remove from an Asset
Strategy.
2. On the Common Tasks menu, click the Strategy Links link.
The Implementation Package Update page appears, displaying the Implementation
Package datasheet and a list of Asset Strategies that currently belong to the
3. In the grid in the Asset Strategies for Package section, select the row containing
the Asset Strategy that you want to remove from the Implementation Package.
4. At the bottom of the page, click the Remove Asset Strategy button.
The Asset Strategies are removed from the grid, and the Asset Strategy records are
unlinked from the Implementation Package record.
About Adding Work Item Records to

On the Packaging page, you can create work item records and add them to an
Implementation Package, where the new records are represented by nodes in the tree.
When creating records, you can use any of the methods in the following table.
Regardless of how you create new records, they will be linked to the Implementation
Package record through the Has Work Management Item relationship.
Method
Notes
Using the
Packaging
Tasks menu.
You will need to populate manually all fields that are not calculated and
that are not populated automatically by a Meridium APM rule.
Using the
You will need to populate manually all fields that are not calculated and
shortcut menu
that are not populated automatically by a Meridium APM rule.
in the tree.
This option is available for the following types of records:
Mapping
values from an
existing Action.
Records that represent Meridium APM work items (e.g.,

Measurement Location records).
Records that represent SAP work items (e.g., Maintenance

Items).
If you use this method, certain values in the Action will be used to
populate fields in the new record. This method can save you a significant
amount of time. When using Actions as the basis for creating new
records, you have two options:
Use the Build link and select the individual type of records that
you want to create.
Use the Build link and select the Implementation Package option,
which will allow you to use the Implementation Packaging
Builder to create the records. If you are creating records that
represent SAP work items, the Implementation Packaging Builder
will also create the records in the appropriate SAP hierarchy
using the Rules Library project and class that is specified on the
This option is available for records in the following families:
Copying an
existing record.
Notification
Object List Item
Operation
Material
PRT
Maintenance Package
Creating Records Using the Packaging

Tasks Menu
To create a record from scratch using the Packaging Tasks menu:
1. Open the Implementation Package to which you want to add a new record that
represents a work item.
2. On the Packaging Tasks menu, click the desired link.
A submenu appears.
3. On the submenu, click the link associated with the type of record that you want to
create.
A new window appears, displaying the datasheet for the family of the selected record
type. For example, if you clicked Inspection Task in step 2, the <empty> (new Inspection
Task) window appears, displaying the Inspection Task datasheet.
The record is created, and the tree is updated to display a new node representing this
record. The node is grouped in the tree under a folder labeled according to the type of
record that you created. For example, if you created an Inspection Tasks record, a node is
added to the tree under the Inspection Task folder.
In addition, the new node is highlighted in the tree, and the datasheet area to the right of
the tree displays the datasheet of the new record.
Hint: The image that appears in the tree for the new node is configured on the
Creating a Record Using the Shortcut

Menu in the Tree
To create a record from scratch using the shortcut menu in the tree:
1. Open the Implementation Package to which you want to add a new work item
record.
2. In the tree, right-click the node under which you want to create a new node. Note
that the new record will be linked to the record represented by the node that you
right-click.
A shortcut menu appears.
3. On the shortcut menu, click the desired option.
A new window appears, displaying the datasheet for the family of the selected record
type.
The record is created, and the tree is updated to display a new node representing this
record. The node is grouped in the tree under a folder labeled according to the type of
record that you created. For example, if you created an Inspection Tasks record, a node is
added to the tree under the Inspection Task folder.
In addition, the new node is highlighted in the tree, and the datasheet area to the right of
the tree displays the datasheet of the new record.
Hint: The image that appears in the tree for the new node is configured on the
Adding Existing Records to an

If your database already contains a record that you want to add to an Implementation
Package, you can do so via the Packaging page. By default, you can add the following
types of existing records to an Implementation Package:
Calibration Task
Inspection Task
Note: You can add records in these families to an Implementation Package because the
corresponding Work Management Item Definition record contains a selected Allow link
existing check box. If this check box is cleared in a Work Management Item Definition
record, you will not be able to add existing records in that family to an Implementation
Package.
To add an existing record to an Implementation Package:
1. Open the Implementation Package to which you want to add an existing record.
2. In the tree, right-click the Implementation Package node.
3. On the shortcut menu, click Link Existing.
A submenu appears.
4. On the submenu, click Find an existing <Family Caption> to link to <Package
ID>, where <Family Caption> is the family to which the desired record belongs
and <Package ID> is the ID of the selected Implementation Package record.
For example, to add an existing Inspection Task record to Implementation Package A,
you would click Find an existing Inspection Task to link to Implementation Package A.
The Select <Family Caption> to Add to Package dialog box appears, where <Family
Caption> is the family of the desired record.
5. In the grid that appears, select the rows containing the records that you want to
add to the Implementation Package, and click OK.
The tree is updated to display nodes representing the selected records. In addition, the
selected records are linked to Implementation Package record.
About Copying and Pasting Nodes in the

Tree
Using the shortcut menu in the tree, you can create new records in certain families by
copying the node representing an existing record and pasting it to the desired location in
the tree. You can choose to copy only the selected node or the selected node and all of its
successor nodes. When you paste a copied node, a new node appears in the tree, and a
new record is created in the corresponding family and populated automatically with the
values in the corresponding fields in the source record (with some exceptions).
To copy a node, in the tree, you will need to select the node and then click the Copy
option on the shortcut menu. You can paste a copied node only to a node that represents a
family that is related to the family representing the copied node. You will know if it is
valid to paste a node in a given location if the Paste option is enabled on the shortcut
menu.
When you paste one or more nodes, the Asset and Action Assignment window appears (if
certain conditions have been met). You can use this window to select the following items:
The SAP Equipment or Functional Locations that you want to assign to the new
nodes.
The Actions that you want to assign to the new nodes.
After you copy a node, you can paste a copy of it more than once, without copying the
source node again. Each time you paste a copied node, a new node appears representing a
new record that is a copy of the source record.
Fields Mapped from Copied Nodes

The following table provides details on each node you can copy and the fields in the
source record that are mapped to the target record.
Node
Mapped Fields
All fields are mapped,
Maintenance with the following
Item
Notes
When you try to paste a Maintenance Item node
to a Maintenance Plan node, the Meridium APM
system will check to see if the value stored in the
exceptions:
Date Imported
Maintenance
Item (i.e., ID
field)
Maintenance Strategy field in the target

Maintenance Plan record matches the value
stored in the Maintenance Strategy field in the
source Maintenance Item record:
If the values match, the copied

Maintenance Item node will be pasted to
that Maintenance Plan node.
If the values do not match, the copied
Maintenance Item node will not be pasted
to that Maintenance Plan node.
If you paste a Maintenance Item node and

implement the Implementation Package in SAP, a
new Maintenance Item will be created in SAP for
the new node.
Maintenance All fields are mapped.
Package
Maintenance with the following
exceptions:
Plan
Material
Notification
Date Imported
ID
Object List
Item
If you paste a child node to a parent Maintenance

Plan node, the Maintenance Strategy value from
parent Maintenance Plan record will be copied to
the Maintenance Strategy field in the child
record.
All fields are mapped.

with the following
exceptions:
Notification
Number
Import Status
Date Imported
If you paste a Maintenance Plan node and

implement the Implementation Package in SAP, a
new Maintenance Plan will be created in SAP for
the new node.
Operation
PRT

except for the
Document Binary field.
with the following
exceptions:
Task List
Date Imported
Group
Group Counter
If you paste a PRT node and implement the

Implementation Package in SAP, a new PRT will
be created in SAP for the new node.
When you try to paste a Task List node to a
Maintenance Item node, the Meridium APM
system will check to see if the value stored in the
Maintenance Strategy field in the Maintenance
Item record matches the value stored in the
Maintenance Strategy field in the Task List
record:
If the values match, the Task List node

will be pasted to that Maintenance Item
node.
If the values do not match, the Task List
node will not be pasted to that
Maintenance Item node.
If you paste a Task List node and implement the

Implementation Package in SAP, a new Task List
will be created in SAP for the new node.
Copying Nodes
You can copy nodes only in certain families. You will know if you can copy a node if the
Copy option is enabled on the shortcut menu.
To copy a node in the tree:
1. Open the desired Implementation Package.
2. In the tree, right-click the node that you want to use as a source node to create a
new node.
The shortcut menu appears.

3. On the shortcut menu, click Copy.
If you copied a node with child nodes, a message appears, asking if you want to also copy
the successor nodes.
4. If you want to copy the successor nodes, click the Yes button.
-orIf you do not want to copy the successor nodes, click the No button.
The selected node is copied. If you clicked the Yes button on the message, its successor
nodes are also copied.
Pasting Nodes
The following instructions assume that you are viewing an Implementation Package and
that you have already copied the nodes that you want to paste.
To paste a copied node in the tree:
1. Right-click the node below which you want to paste the copied nodes.
The shortcut menu appears.
2. On the shortcut menu, click Paste.
If the required conditions have been met, the Asset and Action Assignment window
appears.
-orIf the required conditions have not been met, a new node(s) appears in the selected
location.
3. If you want to change the SAP Equipment and Functional Location assignment
for the new nodes, assign different SAP Equipment items and Functional
Locations to the new nodes.
4. Assign Actions to the new nodes.
5. Click OK.
The Asset and Action Assignment window closes, the Packaging page returns to focus,
and the tree is updated to contain new nodes that are copies of the source nodes.
Conditions Required to Display the

Asset and Action Assignment Window
When you paste one or more copied nodes, the Asset and Action Assignment window
will be displayed if the following conditions have been met:
The Display Asset and Action Assignment dialog during paste operations check
box is selected on the Implementation Administration page.
-and
At least one of the following conditions has been met:
At least one of the copied nodes contains a field that allows you to select
an SAP Equipment or Functional Location.
The Unpackaged Actions tab contains at least one Action.
For example, consider the scenarios in the following table.
In this scenario...
The
window
is...
The Display Asset and Action

Assignment dialog during
Not
paste operations check box is displayed
cleared.
Because...
The Meridium APM system looks first at the

check box. If it is cleared, no further
evaluation of the copied nodes occurs.

paste operations check box is
selected.
-and-
The Maintenance Item record contains fields

Displayed that allow you to select an SAP Equipment or
You copy a Maintenance

Item node.
selected.
Although the Operation record does not
contain fields that allow you to select an SAP
Displayed Equipment or Functional Location, the
You copy an Operation node.
Unpackaged Actions tab contains at least one
Action.
-and-and-
The Unpackaged Actions tab

contains two Actions.
selected.
-andNot
You copy an Operation node. displayed
-and-
The Operation record does not contain fields

that allow you to select an SAP Equipment or
Functional Location, and the Unpackaged
Actions tab does not contain at least one
Action.
The Unpackaged Actions tab

contains no records.
Aspects of the Asset and Action

Assignment Window
If the required conditions have been met, the Asset and Action Assignment window
appears when you paste one or more copied nodes.
The Asset and Action Assignment window contains the following items:
Tree: Contains a hierarchical list of the nodes that will be created when you
complete the paste operation.
Grid: Contains rows representing the SAP Equipment, SAP Functional Locations,
and Actions that you can assign to the records that will be created when you
complete the paste operation. Each row in the grid corresponds to the node that
exists at that level in the tree on the left. For example, in the following image, the
row for the Maintenance Item 6 Month Oil analysis PdM Route is highlighted in
red.
In each row, the following cells are available:

1.
Equipment: Lets you assign an SAP Equipment item to the node in that
row. When you complete the paste operation, this value will be stored in
the appropriate equipment field (e.g., the Equipment Number field in
Object List Item records) in the record represented by that node.
Equipment Label: Displays the label of the selected SAP Equipment item.
When you complete the paste operation, this value will be stored in the
Equipment Description field in the record represented by that node.
Functional Location: Lets you assign an SAP Functional Location to the

node in that row. When you complete the paste operation, this value will
be stored in the appropriate functional location field (e.g., the Functional
Location ID field in Object List Item records) in the record represented by
that node.
Functional Location Label: Displays the label of the selected SAP

Functional Location. When you complete the paste operation, this value
will be stored in the Functional Location Label field in the record
represented by that node.
Assigned Actions: Lets you assign Actions to the node in that row. When
you complete the paste operation, the corresponding Action Revision
records will be linked to the work item record represented by that node.
The Actions are displayed in the following format:
<Strategy ID> - <Action Revision Name>

...where:
1.
1.
<Strategy ID> is the value in the Strategy ID field in the Asset

Strategy containing the Action.
<Action Revision Name> is the value in the Name field in the

corresponding Action Revision record.
For example, in the following image, the first Action in the list is PMP-4543 Operational Check, where PMP-4543 is the value in the Strategy ID field in the Asset
Strategy record, and Operational Check is the value in the Name field in the
corresponding Action Revision record.
In any enabled cell, you can select the appropriate value. Except for the Assigned Actions
cell, which does not represent a field, the other cells behave the same way that they do on
the datasheets based upon rules that are defined for those fields. For example, the
Equipment Label cell is disabled and populated automatically after you select a value in
the Equipment cell in that row. In addition, you can click the
representing a field to select an item from SAP.
button in any cell
Note: Standard grid functionality is intentionally unavailable.
OK button: Completes the paste operation, which applies your selections.

Cancel button: Discards your changes and closes the window, cancelling the paste
operation.
Help button: Displays the context-sensitive Help topic for the Asset and Action
Assignment window.
Typical Workflow Using the Asset and

Action Assignment Window
If you apply Asset Strategy Templates to different Asset Strategies for similar equipment
and add all of those Asset Strategies to the same Implementation Package, you can create
nodes from Actions from one of those Asset Strategies and then copy those nodes to
create new nodes, where the new nodes are assigned to the Equipment and Actions from
the other Asset Strategies, as appropriate. During the paste operation, if your
administrative setting is configured to display the Asset and Action Assignment window,
you can quickly and easily assign the appropriate SAP Equipment and Actions to the new
nodes.
Consider the following workflow:
1. You create an Asset Strategy Template for one type of equipment, such as electric
pump motors. The template contains five Actions:
o Thermography
o
Vibration Analysis
Seal Replacement
Efficiency Testing
Lubrication Analysis
2. You apply the template as a master to an Asset Strategy for a specific electric
pump motor. The Asset Strategy, therefore, inherits the Actions from the template.
We will refer to this Asset Strategy as N051.
3. You build an Implementation Package for the Asset Strategy and use the Actions
to create various work item records representing SAP work items. You also
implement the Implementation Package.
4. You apply the same Asset Strategy Template to a different Asset Strategy for a
different electric pump motor. The Asset Strategy, therefore, inherits the Actions
from the template. We will refer to this Asset Strategy as N052.
5. You add Asset Strategy N052 to the existing Implementation Package. The
Actions from this Asset Strategy appear on the Unpackaged Actions tab.
6. You want to add these new Actions to the existing Maintenance Plan (created
using the Actions from Asset Strategy N051), where the new Actions are
represented by different Maintenance Items, Task Lists, and Operations. To do so,
you copy the existing Maintenance Item and all of its children.
7. You paste the Maintenance Item and its children to the existing Maintenance
Package. When you do so, the Asset and Action Assignment window appears.
8. For the new Maintenance Item, you assign the piece of equipment associated with
the strategy N052.
9. For the new Operations, you assign the appropriate Actions from the strategy
N052. For example, for the Operation 0010 Perform Efficiency Testing, you
assign the corresponding Action...
...and for the Operation 0020 Perform Lubrication Oil Analysis, you assign the
corresponding Action.
10. You complete the paste operation. The new records that were created during the
paste operation are:
o Linked to the Action Revision records from Asset Strategy N052.
o
Populated with the selected Equipment and Functional Location values

(e.g., the new Maintenance Item record contains the value M-3000-N052
in the Equipment field).
Assigning SAP Equipment Items and

Functional Locations to Nodes
The following instructions assume that you have already pasted nodes, causing the Asset
and Action Assignment window to appear.
To assign SAP Equipment items and Functional Locations to nodes using the Asset and
Action Assignment window:
1. On the Asset and Action Assignment window, in the row containing the node to
which you want to assign an SAP Equipment item or Functional Location, in the
appropriate cell (e.g., Equipment), click the
button.
The Select a <Field Caption> window appears, where <Field Caption> is the caption of
the field from which you accessed the window. In the image below, you can see that the
window label is Select an Equipment because it was accessed from the Equipment cell.
2. Type the desired criteria in the available cells. To return all values, you can select
the default selection, which is the asterisk (*) symbol.
3. Click the Search button.
The Search Results tab appears, displaying the search results.
4. On the Search Results tab, select the row containing the value that you want to
use for populating the field and corresponding cell on the Asset and Action
Assignment window, and click OK.
The selected value appears in the appropriated cell in the grid. In the following image,
you can see that the selected SAP Equipment is M-3000-N058.
Assigning Actions to Nodes

You have already pasted nodes, causing the Asset and Action Assignment window
to appear.
-and
Actions exist on the Unpackaged Actions tab on the Packaging page.
To assign Actions to nodes using the Asset and Action Assignment window:
On the Asset and Action Assignment window, in the row containing the node to
which you want to assign an Action, in the Assigned Actions list, select the check
boxes for the Actions that you want to assign to that node.
For example, in the following image, you can see that the Action PMP-4543 - Lube Oil
Analysis has been assigned to the node.
Note: Actions that have already been assigned to another node will not appear in the list.
About Creating Records from Actions

For any Action that is included in an Asset Strategy that belongs to an Implementation
Package, you can use that Action to create a work item record. You can create work item
records representing:
-or-
Meridium APM work items (e.g., Inspection Task records).
SAP work items (e.g., SAP Notifications).
Creating Records that Represent

Meridium APM Work Items
Using values in an Action, you can create the following records to represent Meridium
APM work items:

Calibration Task
Inspection Task
To create records that represent Meridium APM work items:

1. Open the Implementation Package to which you want to add a record that
represents a Meridium APM work item.
2. In the tree, if it is not already selected, select the root node, which represents the
3. In the grid on the Unpackaged Action tab, select the rows containing the Actions
that you want to use to create new records that represent Meridium APM work
items.
4. On the Action Tasks menu, click the Build link.
A submenu appears.
5. On the submenu, click the item that represents the type of record that you want to
create from the Actions that are selected in the grid. One record will be created for
each Action that is selected in the grid. For example, if four Actions are selected
in the grid and you click Inspection Task on the submenu, four Inspection Task
records will be created, and each of these Inspection Task records will contain
data from one of the Actions.
The records are created, and the tree is updated to display a new node representing each
record. The nodes are grouped in the tree under a folder labeled according to the type of
records that you created. For example, if you created four Inspection Task records, four
nodes are added to the tree under the Inspection Task folder.
In addition, note that the first new node is highlighted in the tree. To see the datasheet of
each new record that you created, you can select the appropriate node in the tree and view
the datasheet area to the right of the tree.
Hint: The image that appears in the tree for the new nodes is configured on the
Notes About Creating Measurement

Location Group Records
If you create a Measurement Location Group record from an Action, the Meridium APM
system checks to see if the Action record is linked to a Health Indicator record. The
Meridium APM system accounts for the following scenarios:
The Action record is not linked to a Health Indicator record. In this case, the
Measurement Location Group record is linked to a Measurement Location record,
which contains data from the Action. This Measurement Location records is
linked to the Equipment or Functional Location record that is linked to the
associated Asset Strategy record.
The Action record is linked to a Health Indicator record that IS linked to a
Measurement Location source record. In this case, the Measurement Location
Group record is linked to the source Measurement Location record. The
Measurement Location record contains data from the Health Indicator record,
which was copied to the Measurement Location record when it was created from
the Health Indicator record. The Measurement Location records is linked to the
Equipment or Functional Location record that is linked to the associated Asset
Strategy record.
The Action record is linked to a Health Indicator record that is not linked to a
Measurement Location source record. In this case, the Measurement Location
Group record is linked to a Measurement Location record, which contains data
from the Action. This Measurement Location record is linked to the Equipment or
Functional Location record that is linked to the associated Asset Strategy record.
Values Mapped to Inspection Task

Records
The following table lists the fields that are populated in an Inspection Task record when
you create it from an Action. The table describes:
The Inspection Task fields that reflect values in the Action.

The Inspection Task fields that are populated with default values that do not
reflect values in the Action.
Inspection
Task Field
Action
Field
Notes
Task ID
Name
None
Task
Description
Description None
Last Date
None
Set by default to the current date.
Desired
Interval
Interval
None
Desired
None
Interval UOM
Set by default to MON, regardless of the value in the Interval

Units field in the Action Revision record.
Next Date
None
Set by default to n days after the Last Date, where n is the

value in the Desired Interval field.
Coverage
None
Set by default to zero (0).
Reoccurring
None
Selected by default.
Modifiable
None
Rejectable
None
Min Interval
Interval
None
Min Interval
UOM
None

Min Date
None

Max Interval
Interval
None
Max Interval
UOM
None

Max Date
None

Source Type
None
Set by default to Manual.
Task State
None
Set by default to Scheduled without change.
Related Entity
None
ID
Reason
Action
Basis
Set by default to the record ID of the Equipment or

Functional Location record that is linked to the Asset
Strategy record for the Asset Strategy containing the Action.
The Reason field does not appear on the Inspection Task
datasheet that is provided in the baseline Meridium APM
database. You can, however, see that this field contains the
value from the Action Basis field by building a query on the
Inspection Task family and including the Reason field.
Values Mapped to Calibration Task

Records
The following table lists the fields that are populated in a Calibration Task record when
The Calibration Task fields that reflect values in the Action.

The Calibration Task fields that are populated with default values that do not
Calibration
Task Field
Action Field Notes
Task ID
Name
None
Task
Description
Description None
Last Date
None
Desired Interval Interval
None
Desired Interval
None
UOM
Set by default to DAYS, regardless of the value in the

Interval Units field in the Action Revision record.
Next Date
None

Coverage
None
Reoccurring
None
Modifiable
None
Rejectable
None
Min Interval
Interval
None.
Min Interval
UOM
None

Min Date
None

Max Interval
Interval
None.
Max Interval
UOM
None

Max Date
None

Source Type
None
Set by default to Calibration.
Task State
None
Related Entity
None
ID
Reason
Set by default to Scheduled without change.

Set by default to the Record ID of the Equipment or
Strategy record for the Asset Strategy containing the
Action.
The Reason field does not appear on the Calibration Task

datasheet that is provided in the baseline Meridium APM
Action Basis database. You can, however, see that this field contains the
value from the Action Basis field by building a query on
the Calibration Task family and including the Reason field.
Values Mapped to Thickness Monitoring

Task Records
The following table lists the fields that are populated in a Thickness Monitoring Task
record when you create it from an Action Revision record. The table describes:
The Thickness Monitoring Task fields that reflect values in the Action.
The Thickness Monitoring Task fields that are populated with default values that
do not reflect values in the Action.
Thickness
Monitoring Task
Field
Action
Revision
Field
Notes
Task ID
Name
None
Task Description
Description
None
Last Date
None
Desired Interval
Interval
None
Desired Interval
UOM
Interval Units None
Next Date
None
Set by default to n days after the Last Date, where n

is the value in the Desired Interval field.
Coverage
None
Reoccurring
None
Modifiable
None
Rejectable
None
Min Interval
Interval
None
Min Interval UOM Interval Units None

Min Date
None

Max Interval
Interval
None
Max Interval UOM Interval Units None

Max Date
None

Source Type
None
Set by default to Manual.
Task State
None
Set by default to Proposed.
Related Entity ID
None

Action.
Reason
Action Basis None
Values Mapped to Measurement

Location Group Records
When you create a Measurement Location Group record from an Action, the
Measurement Location Group ID field is populated with <Action Revision Name>
Group, where <Action Revision Name> is the value in the Name field in the Action
Revision record.
For example, if the name in the Action Revision record is Replace Motor, the
Measurement Location Group ID would be Replace Motor Group.
Values Mapped to Measurement

Location Records
The following table lists the fields that are populated in a Measurement Location record
when you create it from an Action. The table describes:
The Measurement Location fields that reflect values in the Action.

The Measurement Location fields that are populated with default values that do
not reflect values in the Action.
Measurement
Location Field
Action Field Notes

Set by default to the Equipment Technical Number of
the Equipment record or the Functional Location ID of
the Functional Location record that is linked to the Asset
Action. If the Equipment Technical Number field in the
Equipment record or the Functional Location field in the
Functional Location record is empty, this field will be
populated instead with the Record ID of the Equipment
or Functional Location record.
Asset ID
None
Description
Description None
ML Type
None
Set by default to Numeric.
Status
None
Set by default to Active.
Determined based on the current date and time, the

Action Revision Interval, and the Action Revision
Interval Units value.
For example, suppose the following is true:
Schedule
Interval and
Interval
Units
Current date and time = 05/05/2008 4:30 PM.

Action Revision Interval = 10
Action Revision Interval Units = Years
In this case, the Schedule would be Due January 1 of

every 10 years effective 5/5/2008 4:30 PM.
Next Date
None
Determined based on the value in the Schedule field.
Values Mapped to Checkpoint Task

Records
When you create a Measurement Location or Measurement Location Group record from
an Action, a Checkpoint Task record is created automatically and linked to the created
Measurement Location record(s). Checkpoint Task records store the schedule that is
associated with the checkpoint.
The following table lists the fields that are populated in a Checkpoint Task record. The
table describes:
The Checkpoint Task fields that reflect values in the Action.

The Checkpoint Task fields that are populated with default values that do not
Measurement
Location Field
Task ID
Action
Field
Notes
None
Generated automatically by the Meridium APM system

and set by default to CP-<n>, where <n> is a number
representing the number of Checkpoint Task records that
have been initiated (even if they were not actually saved).
Determined based on the current date and time, the

Interval value, and the Interval Units value.
For example, suppose the following is true:
Schedule
Interval
and
Interval
Units
Current date and time = 05/05/2008 4:30 PM.

Action Revision Interval = 10
Action Revision Interval Units = Years
In this case, the Schedule would be Due January 1 of

every 10 years effective 5/5/2008 4:30 PM.
Note that if the Action Revision record does not have a
value in the Interval or Interval Unit field, the Schedule
field will display the text There is no more future
occurrence. The checkpoint is configured to occur one
time only on the current date and time.
Next Date
None
Calculated using the schedule and the current date and

time.

Builder
To access the Implementation Package Builder:
1. Open the Implementation Package to which you want to add a new record that
represents an SAP work item.
2. In the tree, if it is not already selected, select the root node, which represents the
3. In the grid on the Unpackaged Action tab, select the rows containing the Actions
that you want to use to create new records representing SAP items.
4. On the Action Tasks menu, click the Build button.
A submenu appears.
5. On the submenu, click Implementation Package.

The Implementation Package Builder appears, displaying the Welcome screen.
Using the Implementation Package

Builder
Using the Implementation Package Builder, you can create the following records to
represent SAP work items:
Maintenance Plan
Maintenance Item
Object List Item
Task List
Operation
Material
PRT
Maintenance Package
Note: You can create records that represent SAP work items only if the ASI for SAP
license is active.
To use the Implementation Package Builder to create records that represent SAP work
items:
1. Access the Implementation Package Builder.
2. On the Welcome screen, click the Next button.
The Select Work Management System screen appears.
3. Accept the default selection, SAP, and click the Next button.
The Select SAP Template Path screen appears.
4. Select either of the following options:
Actions are Items: This option will create a Maintenance Plan record for
each unique interval associated with the Actions that belong to the
underlying Asset Strategies. This option will also create one Maintenance
Item record for each Action, and each Maintenance Item will be grouped
under the appropriate Maintenance Plan (i.e., each Maintenance Item
record will be linked to the appropriate Maintenance Plan record through
the Has Maintenance Items relationship).
8.
Actions are Operations: This option will create a Maintenance Plan record,
Maintenance Item record, and Task List record for each unique
combination of equipment or location and intervals for the Actions that
belong to the underlying Asset Strategies. This option will also create an
Operation record for each Action, and each Operation will be grouped
under the appropriate Task List (i.e., each Operation record will be linked
to the appropriate Task List record through the Has Operation
relationship).

The appropriate records are created, and new nodes representing each record appear in
the tree.
Example: Selecting Actions are Items

Suppose an Implementation Package includes two Asset Strategies: Dryer Strategy and
Stove Strategy.
Suppose that the Actions for the Dryer Strategy contain the following values.
Name
Interval
Replace the dryer 8 years

Clean the lint trap 1 week
In addition, assume that the Actions for the Stove Strategy contain the following values.
Name
Interval
Replace the stove 8 years

Clean the eyes
1 month
In this case, between the two Asset Strategies, there are three unique intervals: 8 years, 1
week, and 1 month. If you select all of the Actions, choose to build an Implementation
Package, and select Actions are Items, three Maintenance Plan records will be created to
represent each unique interval, as shown in the following image.
Below each Maintenance Plan node, a Maintenance Item node will appear to represent
each Action that contains that interval. Using the Action names and intervals listed above,
the Maintenance Item nodes shown in the following image would appear below each
Maintenance Plan node.
Example: Selecting Actions are

Operations
Suppose an Implementation Package includes two Asset Strategies: Dryer Strategy and
Stove Strategy.
Suppose that the Actions for the Dryer Strategy contain the following values.
Name
Interval
Replace the dryer 8 years

Clean the lint trap 1 week
In addition, assume that the Actions for the Stove Strategy contain the following values.
Name
Interval
Replace the stove 8 years

Clean the eyes
1 month
In this case, between the two Asset Strategies, there are three unique intervals: 8 years, 1
week, and 1 month. If you select all of the Actions, choose to build an Implementation
Package, and select Actions are Operations, three Maintenance Plan records will be
created to represent each unique interval, as shown in the following image.
Below each Maintenance Plan node, a Maintenance Item node will appear to represent
each Action that contains that interval. Using the Action names and intervals listed above,
this would mean that the Maintenance Item nodes shown in the following image would
appear below each Maintenance Plan node.
Below each Maintenance Item node, a Task List node will appear to represent the
Equipment or Functional Location record for each Action, as shown in the following
image.
Below each Task List node, an Operation node will appear to represent the action that
you want to perform, as shown in the following image.
Values Mapped to Notification Records

The following table lists the fields that are populated in a Notification record when you
create it from an Action. The table describes:
The Notification fields that reflect values in the Action.

The Notification fields that are populated with default values that do not reflect
values in the Action.
Notification
Field
Action Notes
Field
Notification
Type
None
Set by default to M1.
Short Text
Name
None.
Set by default to the Record ID of the Equipment or Functional
Location record that is linked to the associated Asset Strategy
record.
None
Note that Meridium APM determines whether to populate the

Functional Location field or the Equipment field based on the
results of the queries Get SAP ID for Equipment and Get SAP
ID for Functional Location.
None
Set by default to 3 - Medium
Functional
Location
-OREquipment
Priority
Values Mapped to Maintenance Item

Records
The following table lists the fields that are populated in a Maintenance Item record when
The Maintenance Item fields that reflect values in the Action.

The Maintenance Item fields that are populated with default values that do not
Maintenance
Item Field
Action
Field
Notes
Item Description Description None

Category
None
Set by default to PM - Maintenance Order
Priority
None
Set by default to 3 - Medium

Functional Location record that is linked to the associated
None
Note that Meridium APM determines whether to populate

the Functional Location field or the Equipment field based
on the results of the queries Get SAP ID for Equipment
and Get SAP ID for Functional Location.
Functional
Location
-OREquipment
Values Mapped to Operation Records

When you create an Operation record from an Action, the Description field is populated
with the value in the Description field in the Action Revision record.
Options for Creating Maintenance

Package Records
To create a Maintenance Package record, you can use the:
Assign Maintenance Packages for Task List window. You should use this option if
you want to create multiple Maintenance Package records at one time, based upon
a specific maintenance strategy, and link them to the Operation records that are
linked to a specific Task List record.
Packaging Tasks menu.
Shortcut menu in the tree.
Implementation Package Builder.
Accessing the Assign Maintenance

Packages for Task List Window
You manage the Maintenance Packages for a Task List using the Assign Maintenance
Packages for Task List window only if all the following conditions are met:
The Implementation Package record is linked to an SAP System record with a

valid connection.
The Maintenance Strategy field in the Task List record contains a value.
The Task List record is linked to at least one Operation record.
To access the Assign Maintenance Packages for Task List window:

1. Open the Implementation Package whose Maintenance Packages you want to
manage.
2. In the tree, select the Task List node representing the Task List whose
Maintenance Packages you want to manage.
3. On the Task List Tasks menu, click the Manage Package Assignments link.
The Assign Maintenance Packages for Task List window appears.
Using the Assign Maintenance Packages

for Task List Window
You can use the Assign Maintenance Packages for Task List window to manage
Maintenance Packages for the Task List represented by the Task List node that is selected
in the tree. If you remember from the ASI data model, Maintenance Package records are
linked to Operation records, which are linked to Task List records. The following image
illustrates how records in these families are linked to one another in the Meridium APM
database.
For each Task List record that is linked to one or more Operation records, you can use the
Assign Maintenance Packages for Task List window to create and delete the Maintenance
Package records that are linked to the Operation records
The Assign Maintenance Packages for Task List window contains the Assign
Maintenance Packages grid, which displays:
The Operation records that are linked to the Task List record represented by the
selected Task List node.
-and
Maintenance Package records that are linked to each Operation record in the grid.
The following image shows an example of what the Assign Packages for Task List
window looks like. Shading and callouts have been added to the image to distinguish
these items.
Each row in the orange highlighted area represents one Operation record. The following
columns are included the grid in this area and contain values that are stored in
corresponding fields in the Operation record:
Operation
Sub Operation
Description
Each column in the green highlighted area corresponds to one cycle that is defined for the
maintenance strategy that is specified in the Maintenance Strategy field in the Task List
record. Keep in mind that maintenance strategies come from your SAP system (i.e., the
SAP system that is defined in the SAP System record to which the Implementation
Package record is linked). Likewise, a cycle is a value that is stored in the Maintenance
Package record and comes from your SAP system. Each maintenance strategy will be
associated with one or more cycles.
The columns that are included in the Maintenance Package records area will vary
depending upon the cycles that are defined in your SAP system. Each cell in a cycle
column contains a check box, which you can use to create and delete Maintenance
Package records. Specifically, you can:
Select a cycle check box to create a Maintenance Package record with the
corresponding cycle and link it to the Operation record in that row. In other
words, each selected check box represents one Maintenance Package record.
Clear a cycle check box to delete the Maintenance Package record with the cycle
in that column and remove the link between that record and the Operation record
in that row. In other words, you can clear a check box to delete the Maintenance
Package record it represents.
Consider the image of the Assign Maintenance Packages for Task List window shown
above. In this image, you can see that:
Maintenance Package records will be created and linked to the following

Operation records:
Sand Blast
Scrape
The following cycles are defined for the maintenance strategy specified in the
Task List:
3M
1M
1Y
The Sand Blast Operation record is linked to two Maintenance Package records:
One with the Cycle 1M.
One with the Cycle 1Y.
The Scrape Operation record is linked to a Maintenance Package record with the
Cycle 3M.
The following image shows what these records look like in the tree, where they are
represented by nodes. Shading has been added to this image in these records:
Orange shading highlights the Operation records.

Green shading highlights the Maintenance Package records that are linked to the
Operation records.
You can manage Maintenance Package records in this way only if the Implementation
Package record is in Draft or Modified state. If the Implementation Package record is in a
state other than Draft or Modified, the Assign Maintenance Packages grid is disabled.
Creating Maintenance Package Records

To create Maintenance Package records using the Assign Maintenance Packages for Task
List window:
1. Access the Assign Maintenance Packages for Task List window.
2. Locate the row containing the Operation record to which you want to link the new
Maintenance Package records.
3. In the Maintenance Package record area, for each Maintenance Package record
that you want to create, select the check box in the cell that corresponds to the
desired cycle for the Maintenance Package. For example, if you want to create
one Maintenance Package record with the cycle 1M and one Maintenance
Package record with the cycle 1Y, you would select the check boxes in the 1M
and 1Y columns, as shown in the following image.
4. Click OK.
The Maintenance Package records are created and linked to the corresponding Operation
records. Continuing with the previous example, the following image shows what the new
Maintenance Package nodes would look like in the tree. A red outline has been added to
this image to highlight the Maintenance Package nodes.
Deleting Maintenance Package Records

To delete Maintenance Package records using the Assign Maintenance Packages for Task
List window:
1. Access the Assign Maintenance Packages for Task List window.
2. Locate the row containing the Operation record that is linked to the Maintenance
Package records that you want to delete.
3. In the Maintenance Package records area, for each Maintenance Package record
that you want to delete, clear the check box in the cell that represents that
Maintenance Package. For example, if you want to delete the Maintenance
Package record with the cycle 3M, you would clear the check box in the 3M
column, as shown in the following image.
4. Click OK.
The Maintenance Package records are deleted. Continuing with the previous example, the
following image shows what the Maintenance Package nodes would look like in the tree
now that the Maintenance Package record 3M has been deleted. A red outline has been
added to this image to highlight the Maintenance Package records.
Options for Creating PRT Records

To create a PRT record, you can use the:
PRT Builder.
Packaging Tasks menu.
Shortcut menu in the tree.
Implementation Package Builder.
Accessing the PRT Builder

To access the PRT Builder:
1. In the tree, select the Task List node representing the Task List record to which
you want to link new PRT records.
2. On the Task List Tasks menu, click the Build PRT link.
The PRT Builder appears.
About the PRT Builder

Using the PRT Builder, you can:
Create a new PRT record and associate it with a new PRT file.
Modify an existing PRT file that is already associated with a PRT record.
After you use the PRT Builder to associate a PRT file with a PRT record, when you
implement the Implementation Package, the PRT record will be transferred to the SAP
system as a PRT, and the PRT file will be transferred to the SAP system as a Word
document that is referenced from the PRT.
Creating a New PRT Record Using the

PRT Builder
To use the PRT Builder to create a new PRT record:
1. Access the PRT Builder.
The welcome screen appears.
The Select Builder Path screen appears.
3. Accept the default selection, Build new PRT Document, and click the Next
button.
The Define SAP Operation Details screen appears.
4. Use the Select an Operation from the list to select the Operation record to which
you want to link the new PRT record.
To link the PRT record to an existing Operation record, click the

button, and select the desired Operation record. The list contains all
Operation records that are linked to the Task List record from which you
accessed the PRT Builder.
-or4.
If you want to link the PRT record to a new Operation record, accept the
default selection, New Operation, and complete the fields on the Operation
datasheet.

Note: If you type a value in the Sub Operation text box, you will not be able to click the
Next button because SAP does not support linking a PRT to a Sub Operation. If you have
typed a value in the Sub Operation text box, to enable the Next button, delete the value
that you typed and navigate to another field on the same screen.
The Define SAP Maintenance Package Details screen appears.
6. If you want to link a Maintenance Package record to the selected Operation

record:
a. Accept the default selection, Define Maintenance Package for SAP
Operation.
b. In the Select a Maintenance Package from the list, accept the default
selection, New Maintenance Package.
c. Complete the fields on the Maintenance Package datasheet.
-orIf you do not want to link a Maintenance Package record to the selected Operation record,
clear the Define Maintenance Package for SAP Operation check box.
The Define SAP PRT Details screen appears.
8. In the Select a PRT from the list, accept the default selection, New PRT, and
complete the fields on the PRT datasheet. Note that you should not populate the
Document, Document Part, or Document Version fields. These fields will be
populated automatically when the Implementation Package is implemented.
The Select the Actions you would like to include in the PRT Document screen appears,
displaying a list of all Actions that have not yet been used to create a work item record
(i.e., they appear on the Unpacked Action tab on the Packaging <Package ID> page) and
all Actions that were used to create the Operation record that you selected on the Define
SAP Operation Details screen.
10. In the grid, in the rows containing the Actions that you want to use to build the
PRT file that will be referenced from the new PRT record, select the Include With
PRT check box.
The Select the PRT Template screen appears.
12. In the Select a PRT Template from the list, click the
button, and select the
PRT template file on which you want to base the PRT file that will be referenced
from the new PRT record. The content in the workspace below your selection
changes based on the selected PRT template file.
13. If desired, modify the formatting or add additional content to the PRT file. You
can add text, images, and tables, but you cannot add merge fields or merge blocks.
14. When you are finished formatting the PRT file, click the Finish button.
15. The Packaging page returns to focus. In addition:
The new PRT node appears in the tree below the Operation node
representing the Operation record that you selected on the Define SAP
Operation Details screen.
If you chose to link a Maintenance Package record to the Operation record

that you selected on the Define SAP Operation Details screen, the
Maintenance Package node appears in the tree below that Operation node.
The Actions that you selected on the Select the Actions you would like to
include in the PRT Document screen appear on the Packaged Actions stab.
Modifying an Existing PRT File
To use the PRT Builder to modify a PRT file that is associated with an existing PRT
record:
1. In the tree on the Packaging page, select the Task List record that is linked to the
PRT record whose PRT file you want to modify.
2. Access the PRT Builder.
The welcome screen appears.
The Select Builder Path screen appears.
4. Select the Regenerate existing PRT Document option, and click the Next button.
The Define SAP Operation Details screen appears.
5. In the Select an Operation from the list, accept the default selection. The list
contains the Operation record that is associated with the PRT record.
The Define SAP Maintenance Package Details screen appears.
7. If you want to link a Maintenance Package record to the selected Operation

record:
a. Accept the default selection, Define Maintenance Package for SAP
Operation.
b. In the Select a Maintenance Package from the list, accept the default
selection, New Maintenance Package.
c. Complete the fields on the Maintenance Package datasheet.
-orIf you do not want to link a Maintenance Package record to the selected Operation record,
clear the Define Maintenance Package for SAP Operation check box.

The Define SAP PRT Details screen appears.
9. In the Select a PRT from the list, click the

whose PRT file you want to modify.
button, and select the PRT record
The Select the Actions you would like to include in the PRT Document screen appears,
displaying a list of all Actions that have not yet been used to create a work item record
(i.e., they appear on the Unpacked Action tab on the Packaging <Package ID> page) and
all Actions that were used to create the Operation record that was selected on the Define
SAP Operation Details screen. The Include With PRT check box is selected for any
Action that is currently associated with this Operation record.
11. In the grid, in the rows containing the Actions that you want to use to build the
PRT file that will be referenced from the new PRT record, select the Include With
PRT check box. If you want to remove any Actions from the PRT file, you can
clear the Include With PRT check box in those rows.
The Select the PRT Template screen appears.
On the New Document tab, the Select a PRT Template from the list displays the PRT
template file that was last used to build the PRT file. The Previous Document Version tab
displays the current PRT file.
13. To select a different PRT template file to use as the basis for this PRT file, on the
New Document tab, in the Select a PRT Template from the list, click the
button, and select the desired PRT template file.
A message appears, indicating that any changes you have made to the content on the New
Document tab will be lost.
14. Click OK.
The content in the workspace below your selection changes based on the selected PRT
template file.
15. If desired, modify the formatting or add additional content to the PRT file. You
can add text, images, and tables, but you cannot add merge fields or merge blocks.
16. When you are finished formatting the PRT file, click the Finish button.
17. The Packaging page returns to focus. In addition:
13.
If you chose to link a Maintenance Package record to the Operation record

that was selected on the Define SAP Operation Details screen, the
Maintenance Package node appears in the tree below that Operation node.
The Actions that you selected on the Select the Actions you would like to
include in the PRT Document screen appear on the Packaged Actions tab.
Options for Creating Object List Item

Records
To create an Object List Item record, on the Packaging page, you can:
Click the Maintain Object List link on the Maintenance Item Tasks menu, which
will cause the Meridium APM system to create it automatically. You can use this
option only if your Implementation Package contains Asset Strategy records that
are linked to records in the baseline Equipment or Functional Location family.
Create them manually using the Packaging Tasks menu or the shortcut menu in
the tree.
How the Maintain Object List Link

Works
When you select a Maintenance Item record in the tree, the Maintenance Item Tasks
menu appears, displaying the Maintain Object List link.
When you click the Maintain Object List link, the Meridium APM system searches the
Actions that are associated with the selected Maintenance Item record and any Operation
record to which it is linked. If those Actions belong to an underlying Asset Strategy that
is linked to an Equipment record, one Object List Item record will be created for each of
those underlying Equipment records.
This feature ensures that your Object List Item records are always in sync with the
actions that are currently part of the Implementation Package. In general, you should use
this feature before packaging any Implementation Package.
For example, suppose an Implementation Package contains the following Asset Strategies
with the following Actions.
Asset Strategy 1 - Equipment 100

Action 1 Overhaul every 5 years
Action 2 Inspect every 1 month
If you were to associate all of these Actions with a Maintenance Item record, when you
selected that Maintenance Item record and clicked the Maintain Object List link, the
following Object List Item records would be created automatically:
Equipment 100
Equipment 200
Equipment 300
In other words, one Object list Item record is created for each unique underlying
Equipment record.
Note that when you click the Maintain Object List link, the Meridium APM system not
only creates Object List Item records but also deletes Object List Item records when
appropriate (e.g., an Action has been disassociated from a Maintenance Item record since
the Object List Item record was last created).
Options for Creating Task List Records

To create a Task List record, on the Packaging page, you can:
Create it automatically from an existing Task List in SAP. If you choose to create
a Task List record from an existing SAP Task List, you can use either of the
following options:
Create the Task List record as a reference to the existing SAP Task List.
Task List records that are created as references to existing SAP Task Lists
cannot be modified in the Meridium APM system. When the
Implementation Package is implemented, the new SAP Maintenance Item
that is created from the associated Meridium APM Maintenance Item
record will be associated automatically with the existing SAP Task List
from which you created the Task List record.
Create the Task List record as a copy of the existing SAP Task List. Task
List records that are created as copies of existing SAP Task Lists can be
modified in the Meridium APM system. When the Implementation
Package is implemented, the new SAP Maintenance Item that is created
from the associated Meridium APM Maintenance Item record will be
associated automatically with a new SAP Task List.
-or
Create them manually using the Packaging Tasks menu or the shortcut menu in
the tree.
Creating a Task List Record from an

Existing SAP Task List
Note: You can create a Task List record from an SAP Task List only if the Maintenance
Item record to which the new Task List record will be linked is not already linked to a
Task List record. Also, the Implementation Package record must be in a state that allows
it to be modified (e.g., Draft).
To create a Task List record from an existing SAP Task List:
1. Open the Implementation Package to which you want to add a new Task List
record.
2. In the tree, select the Maintenance Item node under which you want to create a
new Task List node.
3. On the Maintenance Item Tasks menu, click the Locate Task List link.
The Locate Task List window appears, displaying the Search Criteria tab.
4. In the Task List Type list, select the type of Task List that you want to use to
create a new Task List record.
5. In the remaining text boxes, type values to limit the Task Lists that will be
returned by the search. To return Task Lists with ANY value in a given field,
accept the default selection: *
Note: The Maintenance Strategy text box is disabled and displays the value in the
Maintenance Strategy field of the Maintenance Item record to which the Task List record
will be linked. This ensures that your search results will return Task Lists from the
appropriate category.
6. When you are finished defining the search criteria, click the Search button.
The Search Results tab appears, displaying the Task Lists that the specified criteria.
7. On the Search Results tab, select the row containing the Task List that you want to
use to create a new Task List record, and click OK.
A message appears, asking if you want to create the Task List record as a reference to the
selected Task List or as a copy of the selected Task List.
8. If you want to create the Task List record as a reference to the selected Task List,
click the Yes button. Task List records that are created as a reference to an SAP
Task List cannot be modified in the Meridium APM system.
-ORIf you want to create the Task List record as a copy of the selected Task List, click the No
button. Task List records that are created as a copy of an SAP Task List can be modified
in the Meridium APM system.
A new Task List record is created and linked to the selected Maintenance Item record. In
addition, if the SAP Task List contains Operations and PRTs, new Operation and PRT
records are also created. The tree is also updated to reflect the new records.
If you created the Task List record as a reference to the SAP Task List, the fields on the
Task List record and any successor Operation records are disabled. If you created the
Task List record as a copy of the SAP Task List, the fields are enabled.
Associating an Action with an Existing

Work Item
To associate an Action with an existing work item:
1. Open the Implementation Package that contains the work item that you want to
associate with an Action.
2. In the tree, select the node that you want to associate with an Action.
3. On the Unpackaged Action tab, select the row containing the Action that you want
to associate with the selected node.
4. On the Action Tasks menu, click the Link Action link.
The Action is removed from the grid on the Unpackaged Actions tab and added to the
grid on the Packaged Actions tab. In addition, the Action Revision record is linked to the
record that is represented by the selected node.
Removing the Association Between an

Action and a Work Item
After you have associated an Action with a work item, you might decide that you no
longer want that Action to be associated with that work item.
To remove the association between an Action and a work item:
1. Open the Implementation Package that contains the work item that you want to
disassociate from an Action.
2. In the tree, select the node that you want to disassociate from an Action.
3. Click the Packaged Actions tab.
4. On the Packaged Actions tab, select the row containing the Action that you want
to disassociate from the selected node.
5. On the Action Tasks menu, click the Unlink Action link.
The Action is removed from the grid on the Packaged Actions tab and added to the grid
on the Unpackaged Actions tab. In addition, the corresponding Action Revision record is
unlinked from the record that is represented by the selected node.
About Updating Work Item Records

with Changes to Actions
If someone makes a change to an Action in an Asset Strategy, a new Action Revision
record is created to capture the updated values. If you have created one or more records
from that Action, you will need to update those records so that they reflect the values in
the most recent Action Revision record.
For example, consider the Asset Strategy Dryer Strategy with an Action of Clean the lint
trap, where the interval is 1 week. The first time this Action is created, an Action record
and an Action Revision record are created to store the Action values. Suppose that you
create an Inspection Task record from this Action via ASI.
If someone later modifies the Action via ASM to change the interval to 2 weeks, a new
Action Revision record will be created to store the updated value. You will then want to
update the Inspection Task record to reflect the new interval, too.
In a scenario like this:
The Unpackaged Actions tab will contain a row for the Action, where the values
in the grid reflect the updated Action values.
The Packaged Actions tab will contain a row for the Action, where the values in
the grid reflect the previous Action values.
Only changes to values in the following fields will trigger an Action to appear on the
Unpackaged Action tab:
Action Basis
Name
Description
Action Type
Condition Monitoring Type
Interval
Interval Units
Performance Interval Units
Nonrecurring
Existing Plan
Mandatory
Shutdown Required
Updating a Work Item Record After an

Action is Changed
To update a work item record after an Action is changed:
1. Open the Implementation Package that contains the work item record that you
want to update.
2. In the tree, if it is not already selected, select the root Implementation Package
node.
3. In the grid on the Unpackaged Actions tab, in the row that contains the
the Work Management Item ID column, click the hyperlink.
The node representing the associated work item record is highlighted in the tree.
4. In the grid, select the same row in which you clicked the hyperlink.
5. On the Action Tasks menu, click the Apply Updates button.
The work item record is updated. The Action is removed from the grid on the
Unpackaged Actions tab and added to the grid on the Packaged Actions tab.
About Transferring Actions to Other

For any Action that appears on the Unpackaged Actions tab, you can:
Transfer it to another existing Implementation Package.

Create a new Implementation Package to which it will be transferred
automatically.
icon, in
Transfer it back to its original primary Implementation Package.
Transferring an Action to an Existing

To transfer an Action to an existing Implementation Package:
1. On the Packaging page, select the Unpackaged Actions tab.
2. In the row containing the Action that you want to transfer to an existing
Implementation Package, right-click the row, point to Move To, and click Existing
Secondary Package.
The Existing Secondary Package window appears, displaying the results of the Catalog
query Move to Existing Secondary Package. By default, the query is configured to
display all existing Implementation Packages, except for the Implementation Package
that you are currently viewing on the Packaging page, where those Implementation
Packages are associated with the same SAP system as the current Implementation
Package.
3. In the SAP System list, accept the default selection.

Note: If you want to transfer the Action to an Implementation Package that is associated
with a different SAP system than the current Implementation Package, you can select the
appropriate SAP system in the SAP System list. The Meridium APM Best Practice for
ASI, however, assumes that you want to transfer the Action to an Implementation
Package that is associated with the same SAP system as the current Implementation
Package.
4. In the grid, select the row containing the existing Implementation Package to
which you want to transfer the Action, and click OK.
The Action is transferred to the selected Implementation Package, and the Unpackaged
Actions tab returns to focus, where the transferred Action is removed from the grid. In
addition, if you transferred the Action from a primary Implementation Package, you can
click the Externally Packaged Actions tab to see the Action.
Transferring an Action to a New

To transfer an Action to a new Implementation Package:
2. In the row containing the Action that you want to transfer to a new
Implementation Package, right-click the row, point to Move To, and click New
Secondary Package.
The New Secondary package (Implementation Package) window appears. By default, the
value in the ID text box is New Secondary Package.
3. In the ID text box, replace the default ID with a new ID that accurately describes
the new Implementation Package.
4. In the Description text box, type a description of the new Implementation
Package.
Note: The new Implementation Package inherits the SAP system from the
Implementation Packaging containing the selected Action. While you can select a
different SAP system using the ellipsis button on the SAP Connection tab, the Meridium
APM Best Practice for ASI assumes that you want the new Implementation Package to
inherit the SAP system from the current Implementation Package.
5. Click OK.
The Implementation Package record is saved and linked to the selected SAP System
record. In addition, the Packaging page returns to focus, and the transferred Action is
removed from the Unpackaged Actions tab. In addition, if you transferred the Action
from a primary Implementation Package, you can click the Externally Packaged Actions
tab to see the Action.
Transferring an Action Back to Its

Primary Implementation Package
To transfer an Action back to its original primary Implementation Package:
2. In the row containing the Action that you want to transfer to its original primary
Implementation Package, right-click the row, point to Move To, and click Primary
Package.
The Action is transferred to its primary Implementation Package, and the Unpackaged
Actions tab returns to focus, where the transferred Action is removed from the grid.
Navigating Between Packages

Containing Common Asset Strategies
When you are viewing an Implementation Package, you can use the following
instructions to navigate to another Implementation Package containing one or more of the
Asset Strategies that belong to the current Implementation Package. For example, if you
are viewing an Implementation Package containing the Asset Strategies Pump 101
Strategy, Pump 102 Strategy, and Pump 103 Strategy, you can navigate from that
Implementation Package to any other Implementation Package containing one or more of
those Asset Strategies.
To navigate between Implementation Packages:
1. On the Packaging page, on the Asset Strategy Tasks menu, click the Navigate
link.
The Select Package for Navigation window appears, displaying the results of the Catalog
query Locate Packages for Navigation. By default, the query is configured to display all
Implementation Packages (except for the current Implementation Package) that contain
one or more of the Asset Strategies that belong to the current Implementation Package.
2. In the grid, select the row containing the Implementation Package to which you
want to navigate, and click the Navigate button.
The selected Implementation Package appears on the Packaging page.
Navigating From a Primary Package to

a Secondary Package
If you are viewing a primary Implementation Package, you can navigate to any secondary
Implementation Package to which you have transferred an Action from the current
primary Implementation Package.
To navigate from a primary Implementation Package to a secondary Implementation
Package:
1. Open the primary Implementation Package.

2. On the Packaging page, click the Externally Packaged Actions tab.
3. In the grid, select the row containing the Action belonging to the secondary
Implementation Package to which you want to navigate.
4. In the selected row, in the Implementation Package column, click the hyperlink.
The secondary Implementation Package appears on the Packaging page.
Populating Records with Standard Text

from SAP
Using the Select Standard Text window, you can search in SAP for the standard text that
you want to copy to a Work Item record. You can access the Select Standard Text window
using the Append Standard Text link, which appears on the context-sensitive task menu
for specific Work Item families. The following table lists the Work Item families for
which you can obtain standard text from SAP and the task menu from which you can
access the Select Standard Text window.
Work Item Family
Task Menu
Maintenance Plan
Maintenance Plan Tasks
Maintenance Item
Maintenance Item Tasks
Task List
Task List Tasks
Operation
Operation Tasks
Notification
Notification Tasks
The task menus listed in the table appear only when you select in the tree a node
representing a record in the corresponding family. For example, to the see the Task List
Tasks menu, you will need to select a Task List node in the tree.
When you append standard text from SAP to a Work Item record, the Meridium APM
system will import the standard text from SAP and automatically copy it to the Long Text
field in the current record, with the exception of Notification records. Standard Text is
copied to the Description field in Notification records. If the Long Text or Description
field (for Notification records) already contains a value, the Standard Text will be
appended to the existing value.
The following instructions provide details on performing this procedure. These
instructions assume that you are viewing an Implementation Package on the Packaging
page.
To append standard text from SAP to a Work Item record:
1. In the tree, select the node representing the record to which you want to append
standard text from SAP.
The context-sensitive task menu for that family appears in the task menu pane.
2. On the context-sensitive task menu for that family (e.g., Task List Tasks), click
the Append Standard Text link.
The Select Standard Text window appears, and the Search Criteria tab is selected by
default.
3. In the Text ID cell, accept the default value ST.

4. In the Text Name cell, you can:
o
Accept the default value*, which will return ALL the standard text values
from SAP.
-OR3.
o
Enter the name associated with the desired standard text in SAP.
5. In the Text Title cell, you can:

5.
o
-OR5.
Accept the default value*, which will return ALL the standard text values
from SAP.
Enter the title associated with the desired standard text in SAP.
6. Click the Search button.

The Search Results tab appears, displaying the results for the search criteria you entered
on the Search Criteria tab.
7. In the search results, select the row containing the standard text that you want to
copy to the current record.
8. Click OK.
The selected standard text is copied to the Long Text field or Description (for
Notification records) field in the record represented by the currently selected node.
Searching for SAP Data from a

Meridium APM Datasheet
After you create a record that represents an SAP work item, some fields in that record
will need to be populated manually. Because the fields should store SAP values that will
be transferred to the SAP database when you implement the Implementation Package,
Meridium APM provides a way for you to use the datasheet to query the SAP database
for a list of valid values that the SAP database will accept.
To search for SAP data from a Meridium APM datasheet:
1. Open the desired Implementation Package record.
2. In the tree, select a node that represents an SAP work item (e.g., a Maintenance
Plan node).
3. In the datasheet section to the right of the tree, in the field that you want to
populate with a valid value from the SAP database, click the
button.
Hint: Meridium APM text fields also use an

the Text Editor.
button to indicate that you can access
The Select a <Field Caption> window appears, where <Field Caption> is the caption of
the field from which you accessed the window.
4. If a Search Criteria tab appears:
...type the desired criteria in the available cells. To return all values, you can select the
default selection, which is the asterisk (*) symbol.
-ORIf a Search Criteria tab does not appear, proceed to step 5 of these instructions.
5. On the Search Results tab, select the row containing the value that you want to
use for populating the field, and click OK.
The selected value appears in the field.
Populating the Equipment or Functional

Location Field in a Task List Record
Automatically
If a Maintenance Item record contains a value in either the Functional Location or
Equipment field, after you create a Task List record that is linked to that Maintenance
Item record, you can use the following instructions to copy that value to the Task List
record.
To populate the Equipment or Functional Location field in a Task List record
automatically:
1. Open the desired Implementation Package record.

2. In the tree, select the Maintenance Item node representing the record that is linked
to the Task List record whose Equipment or Functional Location field you want to
populate automatically.
3. On the Maintenance Item Tasks menu, click the Synchronize Reference Object
link.
If the Maintenance Item record contains a value in the Functional Location field, the
value is copied to the Functional Location field in the Task List record. Likewise, if the
Maintenance Item record contains a value in the Equipment field, the value is copied to
the Equipment field in the Task List record. In addition, the field in the Task List record
to which the value was copied is disabled, ensuring that the two values will never be
different.
Note: If you later decide to create a general Task List from this Task List record, you can
remove the value from the Equipment or Functional Location field in the Maintenance
Item record, which will cause it to be removed automatically from the Task List record.
Saving Values in a Work Item Record

As you create new records that represent work items and the records are linked to the
Implementation Package record, the Meridium APM system saves the records and the
links automatically. If, however, you modify a value on any of the datasheets, you will
need to save those changes manually.
To save modified values in a record that represents a work item:
After you have modified a value in a datasheet to the right of the tree, on the
Common Tasks menu, click the Save <Entity ID> link, where <Entity ID> is the
Record ID of the selected record.
The updated values are saved to the Meridium APM database.
Packaging an Implementation Package

After you are finished creating work items records, you can package the Implementation
Package. Doing so makes all records that are linked to the Implementation Package readonly. A reviewer can then evaluate the Implementation Package and decide to implement
it, which will create the appropriate items in the SAP system, or revert it to a modifiable
state for additional work.
To package an Implementation Package:
1. Open the Implementation Package whose state you want to set to Packaged.
2. On the State Configuration Tasks menu, click the Package link.
The state of the Implementation Package record changes from Draft to Packaged. In
addition, in the tree, the label next to the root node changes to reflect the updated state.
Implementing an Implementation
Package
To set the state of an Implementation Package record to Implemented:
1. Open the Implementation Package whose state you want to change to
Implemented.
2. On the State Configuration Tasks menu, click the Implement or Update link,
whichever is available.
Note: The Implement link will be available if the Implementation Package record state
has never been set to Implemented. The Update link will be available if the
Implementation Package record state has been set to Implemented and then Modified
(through the Revise operation).
The Processing Implementation Package <Package ID> window appears, where
<Package ID> is the ID of the selected Implementation Package. This window displays
the results of the implementation process. Specifically, it indicates whether or not the
items were created successfully. If an item was not created, you will see a warning
message indicating the cause of the problem.
Note: If you used to Action to create a record representing a Meridium APM work item,
such as an Inspection Task record, this window will display a warning message for that
item. The warning message will indicate that the item was not implemented because no
Execution Mapping is defined. You can disregard this message for any record that
represents a Meridium APM work item.
4. When you are finished reviewing the status, click the Close button.
A message appears, asking if you want to save the results to an external file. If you do not
want to save the results, you can click the No button, and the Implementation Package
record state will change to Implemented. The remaining instructions assume, however,
that you want to save the results to a file.
5. On the message, click the Yes button.
The Save As dialog box appears.
6. Navigate to the location in which you want to save the file, type a name for the
file, and click the Save button when you are finished.
The results of the implementation process are saved to the specified Text file, and the
Implementation Package record state changes to Implemented. In addition, in the tree, the
label next to the root node changes to reflect the updated state.
Field Values That are Disabled After

Implementation
The following table lists the Meridium APM fields that are disabled automatically after
you implement an Implementation Package.
Family
Field
Maintenance Plan ID
Maintenance Item Maintenance Item
Maintenance Item Category
Maintenance Item Work Center
Maintenance Item Work Center Plant
Task List
Equipment
Task List
Functional Location
Task List
Group
Task List
Planning Plant
Task List
Key Date
Task List
Plant
Material
Material Number
Notification
Notification Type
Reverting an Implementation Package

to the Draft State
After an Implementation Package is packaged, you cannot:
Add additional records to the Implementation Package.

Remove work items from the Implementation Package.
Create new work item records from Actions.
Remove the association between a work item record and an Action.
After an Implementation Package is packaged, however, you might decide that you want
to make additional changes. To make these changes, you will need to change the state
back to Draft.
To revert the state of an Implementation Package back to Draft:
1. Open the Packaged Implementation Package whose state you want to revert to
Draft.
2. On the State Configuration Tasks menu, click the Revert link.
The state of the Implementation Package record changes from Packaged to Draft. In
addition, in the tree, the label next to the root node changes to reflect the updated state.
Setting an Implemented Implementation

Package to a Modifiable State
After an Implementation Package record is implemented, you cannot:
Add additional records to the Implementation Package.

Remove work item records from the Implementation Package.
Create new work item records from Actions.
Remove the association between a work item record and an Action.
To set the state of an Implemented Implementation Package record to a state where it can
be modified:
1. Open the implemented Implementation Package whose state you want to change.
2. On the State Configuration Tasks menu, click the Revise link.
The state of the Implementation Package record changes from Implemented to Modified.
In addition, in the tree, the label next to the root node changes to reflect the updated state.
You can now make the desired changes and reimplement the Implementation Package
when you are finished making changes.
Viewing Items in SAP After an

Implementation Package Has Been
Implemented
After an Implementation Package has been implemented, you can access the SAP system
from Meridium APM to see any SAP item that was created from a Meridium APM
record.
Note that you can access only Maintenance Plans, Maintenance Items, and Task Lists
directly from the associated Meridium APM record. You cannot access Operations, PRTs,
Materials, or Object List Items directly from the associated Meridium APM record.
To view an item in SAP after the Implementation Package has been implemented:
1. Open the implemented Implementation Package that contains a record that was
used to create an item in the SAP system.
2. In the tree, select the node associated with the SAP item that you want to view.
3. In the datasheet section to the right of the tree, locate the cell that contains a
hyperlink, and click the hyperlink.
The SAP Login screen appears.
4. Log into the SAP system using a valid user name and password.
The SAP system appears, displaying the item that is associated with the node that you
selected in the tree.
About Updating Items in SAP With

Changes in ASI
After an Implementation Package has been implemented, if any of the following records
that belong to it are modified or deleted, or the links between the records are removed,
when you reimplement the Implementation Package (via the Update operation), the
corresponding SAP items will be updated, deleted, or disassociated accordingly:
Maintenance Item
Maintenance Plan
Task List
Object List Item
Operation
Material
Maintenance Package
PRT
Notification
Note: This update functionality will work correctly only if the version of your SAP
system supports it (i.e., SAP systems running ECC 6 EhP 5 and higher). Otherwise,
when you implement the Implementation Package, a message will appear, indicating that
the updates are not allowed.
To facilitate the SAP updates, each of the records listed above contains the
Implementation Status field, where the value determines whether or not SAP updates are
needed upon implementation of the Implementation Package. The Implementation Status
field can contain any of the following values:
Added: The record is new and has not yet been sent to SAP. In this case, when the
Implementation Package is implemented, the corresponding SAP item will be
created.
Modified: One or more values in the record have changed since it was last sent to
SAP. In this case, when the Implementation Package is reimplemented, the
corresponding SAP item will be updated accordingly.
Deleted: The record has been flagged for deletion since it was last sent to SAP. In
this case, when the Implementation Package is reimplemented, the corresponding
SAP item will be deleted.
Unchanged: The record has not changed since it was last sent to SAP. In this case,
when the Implementation Package is reimplemented, the corresponding SAP item
will remain untouched.
The Implementation Status field is not available on any baseline datasheets. Instead, the
value is used to determine the image that is displayed next to the node name in the tree on
the Packaging page.
Note: Some fields in Meridium APM records are disabled automatically after the
Implementation Package is implemented.
About Deleting Implementation Package

Records
When you delete an Implementation Package record, the records that are linked to it as
successors will not be deleted (e.g., Inspection Task records) from the Meridium APM
database. Only the Implementation Package record and the links between the
Implementation Package record and the successor records will be deleted.
You cannot delete an Implementation Package record that is linked to any work item
records that were created from Actions. If an Implementation Package contains records
that were created from Actions, you will need to delete those links before you can delete
the Implementation Package record. To determine if an Implementation Package fits this
description, you can look at the Packaged Actions tab on the Packaging page for that
package. If it contains any items, you cannot delete the Implementation Package record.
In addition, you cannot delete an Implementation Package containing work item records
that cannot be deleted (i.e., they are already flagged for deletion, they represent reference
Task Lists, or their corresponding Work Management Item Definition Configuration
record points to rules indicating that deletion is not allowed).
You can delete a single Implementation Package record from the Implementation
Package Update page, or you can delete multiple Implementation Package records at one
time via the Implementation Package List page.
Deleting Implementation Package

Records via the Implementation
Package Update Page
The following instructions provide details on deleting a single Implementation Package
record via the Implementation Package Update page. You can delete multiple
Implementation Package records at one time using the Implementation Package List
page.
To delete an Implementation Package record via the Implementation Package Update
page:
1. On the Implementation Package Update page, open the Implementation Package

record that you want to delete.
2. On the Common Tasks menu, click the Delete link.

The Implementation Package record is deleted, and the Implementation Package List
page appears.
Deleting Work Item Records

Representing Meridium APM Items
To delete records that represent Meridium APM work items (e.g., Task records):
1. Open the Implementation Package that contains the work item record that you
want to delete.
2. In the tree, right-click the node that represents the record that you want to delete.
3. On the shortcut menu, point to Delete, and then click one of the following
options:
Delete <Record Description>, where <Record Description> is the

description of the corresponding record. This option will delete only the
record represented by the node that you right-clicked.
-or4.
Delete <Record Description> and all Child Work Management Items,

where <Record Description> is the description of the corresponding
record. This option will delete the record represented by the node that you
right-clicked and the records represented by all successor nodes of that

node.
If the node you selected does not have any successor nodes, the node is removed from the
tree, and the corresponding record is deleted from the database.
-orIf the node you selected has successor nodes and you selected to delete the successors,
the selected node and its successor nodes are removed from the tree, and the
corresponding records are deleted from the database.
Deleting Work Item Records

Representing SAP Items
When you delete a work item record representing an SAP item (e.g., Maintenance Item)
that has already been sent to SAP through the Implement or Update operation, the record
is flagged for deletion but not actually deleted from the database. In addition, the
corresponding node remains in the tree with an updated image to indicate that it has been
flagged for deletion. When you reimplement the Implementation Package, any records
that are flagged for deletion are deleted from the Meridium APM database, and their SAP
counterparts are then deleted or unlinked from corresponding items, as appropriate.
If a Task List record was created from an existing SAP Task List, when you delete that
Task List record or any successor Operation records to which it is linked, the records are
deleted immediately from the Meridium APM system instead of being flagged for
deletion.
Note: Some SAP items cannot be deleted due to SAP restrictions. In these cases, when
you send to SAP a record that has been flagged for deletion in the Meridium APM
system, a message appears, indicating that the SAP item was not actually deleted.
To delete records that represent SAP work items:
1. Open the Implementation Package that contains the record that you want to
delete.
2. In the tree, right-click the node that represents the record that you want to delete.
3. On the shortcut menu, point to Delete, and then click one of the following
options:
Delete <Record Description>, where <Record Description> is the

description of the corresponding record. This option will delete only the
record represented by the node that you right-clicked.
-or4.
Delete <Record Description> and all Child Work Management Items,

where <Record Description> is the description of the corresponding
record. This option will delete the record represented by the node that you
right-clicked and the records represented by all successor nodes of that
node.
If the node you selected does not have any successor nodes, the image next to the node
changes to one indicating that the SAP counterpart will be deleted the next time the
-orIf the node you selected has successor nodes and you selected to delete the successors,
the image next to the selected node and all of its successors changes to one indicating that
the SAP counterpart will be deleted the next time the Implementation Package is
implemented.
Note: If the deleted node is a child of a parent node (e.g., the deleted node is an Operation
that belongs to a parent Task List node), the image next to the parent node changes to
indicate that it has been modified.
Undoing the Deletion for Work Items

Representing SAP Items
To undo the deletion of records that represent SAP work items:

1. Open the Implementation Package that contains the record for which you want to
undo the deletion.
2. In the tree, right-click the node that represents the deleted record for which you
want to undo the deletion.
3. On the shortcut menu, point to Delete, and then click Undo Delete of <Record
Description>, where <Record Description> is the description of the corresponding
record.
The deletion is undone, and the red X is removed from the node's image.
ASI Associated Pages

The Associated Pages menu appears on the Packaging page and will display the
Associated Pages that have been defined for the family of the record whose node is
currently selected in the tree. There are no baseline Associated Pages defined for the ASI
families.
About the ASI Catalog Folder Structure

The main ASI Catalog folder is \\Public\Meridium\Modules\Asset Strategy
Management\Implementation. This folder contains a subfolder, Queries, which contains
baseline queries that are used by default in ASI.
If desired, you can store additional items in the main ASI Catalog folder or in the Queries
subfolder. In addition, you can create new subfolders to store additional items.
Note: All Public folders exist by default. Any baseline item in the Baseline folder is also
available in the corresponding Public folder. Throughout this documentation, however,
we refer to items in the Public folder.
Queries Folder
The queries listed in the following table are provided in the Catalog folder
\\Public\Meridium\Modules\Asset Strategy Management\Implementation\Queries. In this
table, the values listed in the Query column refer to the query names. The baseline
captions are the same as the names.
IMPORTANT: With the exception of the Get SAP ID for Equipment and Get SAP ID for
Functional Location queries, you should not modify these queries in any way or move
them to another Catalog folder. Also, while modifying the design of the Get SAP ID for
Equipment and Get SAP ID for Functional Location queries is allowed, if you are using
the baseline Equipment and Functional Location families, it is not necessary.
Query
Behavior and Usage
Asset Is Equipment
This query is not used by ASI.

Returns the Equipment record that contains the
ID corresponding to the value supplied for the
SAP Equipment ID prompt and is linked to the
SAP System record identified by the value
supplied for the SAP System prompt. In the
baseline Meridium APM database, the query
returns records in the Equipment family.
Get Equipment for SAP ID
This query is not meant to be run on its own.

Instead, the Meridium APM system runs this
query automatically to determine which
Equipment record to link to the new Asset
Strategy record when you create an Asset
Strategy by importing Maintenance Items,
Notifications, or Operations from SAP. When
the Meridium APM system runs this query, it
performs several actions automatically:
It passes the Equipment ID of the
imported SAP item to the SAP

Equipment ID prompt in the query.
It locates the Site Reference record that

you selected on the Select SAP Object(s)
screen of the Asset Strategy Builder and
locates the SAP System record that is
linked to that Site Reference record. It
then passes the value in the Name field in
that SAP System record to the SAP
System prompt in the query.
If the query returns a record using the provided

values, the Meridium APM system links that
record to the new Asset Strategy record. If the
query does not return a record using that value,
the Meridium APM system runs the Get
Functional Location for SAP ID query.
Get Functional Location for SAP ID
Note: Because the documentation for importing

SAP items to create Asset Strategies assumes
that you began the workflow by importing
Equipment and Functional Location records
using the SAP Interfaces, this documentation
assumes that you will link your Asset Strategy
records to either an Equipment or Functional
Location record. You will not, therefore, need to
modify the baseline Get Equipment for SAP ID
query to include a family other than the baseline
Equipment family.
Returns the Functional Location record that
contains the ID corresponding to the value
supplied for the SAP Functional Location ID
prompt and is linked to the SAP System record
identified by the value supplied for the SAP
System prompt. In the baseline Meridium APM
database, the query returns records in the
Functional Location family. This query is not
meant to be run on its own. Instead, the
Meridium APM system runs this query
automatically to determine which Functional
Location record to link to the new Asset Strategy
record when you create an Asset Strategy by
importing Maintenance Items, Notifications, or
Operations from SAP. When the Meridium APM
system runs this query, it performs several

actions automatically:
It passes the Functional Location of the

imported SAP item to the SAP
Functional Location ID prompt in the
query.
It locates the Site Reference record that

you selected on the Select SAP Object(s)
screen of the Asset Strategy Builder and
locates the SAP System record that is
linked to that Site Reference record. It
then passes the value in the Name field in
that SAP System record to the SAP
System prompt in the query.
If the query returns a record using the provided

values, the Meridium APM system links that
record to the new Asset Strategy record.
Note: Because the documentation for importing
SAP items to create Asset Strategies assumes
that you began the workflow by importing
Equipment and Functional Location records
using the SAP Interfaces, this documentation
assumes that you will link your Asset Strategy
records to either an Equipment or Functional
Location record. You will not, therefore, need to
modify the baseline Get Functional Location for
SAP ID query to include a family other than the
baseline Functional Location family.
Get SAP ID for Equipment
Get SAP ID for Functional Location
After providing a prompt for an Entity Key,

returns the record with the provided Entity Key.
In the baseline Meridium APM database, the
query returns records in the Equipment family.
This query is not meant to be run on its own.
Instead, Meridium APM runs this query
automatically to determine whether to populate
the Equipment or Functional Location field
when you build Notification or Maintenance
Item records from Actions.
After providing a prompt for an Entity Key,
returns the record with the provided Entity Key.
In the baseline Meridium APM database, the

query returns records in the Functional Location
family. This query is not meant to be run on its
own. Instead, it is run automatically to determine
whether to populate the Equipment or Functional
Location field when you build Notification or
Maintenance Item records from Actions.
Locate Packages for Navigation
Returns all existing the Implementation

Packages that contain one or more of the Asset
Strategies that belong to the current
Implementation Package. This query is not
meant to be run on its own. Instead, it is run
automatically when you click the Navigate link
on the Packaging page.
Locate Strategies to Package
Returns a list of Active Asset Strategy records

that are not linked to an Implementation Package
record. This results of this query are displayed
on the Select Asset Strategy to Add to Package
window, which you can access via the
Implementation Package Update page. You can
add criteria to this query, but you should not
remove any criteria from the query.
Locate_Packages
After providing a prompt for State and

Implementation Role, returns a list of all
Implementation Package records that meet the
specified criteria. This query is run when you
click the Packaging link on the Asset Strategy
Implementation Start Page.
Locate_Packages_for_Execution
This query is not used by ASI.
Returns a list of all Implementation Package

records that are linked to the Asset Strategy
record to which a given System Strategy record
Locate_Packages_for_System_Strategy
is linked. This query is run when you click the
Strategy Implementation link on the Navigation
menu when you are viewing a System Strategy.
Locate_Packages_for_Unit_Strategy
Returns a list of all Implementation Package

records that are linked to the Asset Strategy
record that is linked to the System Strategy
record to which a given Unit Strategy record is
linked. This query is run when you click the

Strategy Implementation link on the Navigation
menu when you are viewing a Unit Strategy.
Move to Existing Secondary Package
After providing a prompt for an SAP system,

returns all existing Implementation Packages
associated with the selected SAP system, except
for the current Implementation Package. This
query is not meant to be run on its own. Instead,
it is run automatically when you send an Action
to a new or existing Implementation Package.
About the Get SAP ID for <Equipment

or Functional Location> Query
After providing a prompt for an Entity Key, the query Get SAP ID for Equipment returns
the record with the provided Entity Key. In the baseline Meridium APM database, the
query returns records in the Equipment family. This query is not meant to be run on its
own. Instead, Meridium APM runs this query automatically to determine whether to
populate the Equipment or Functional Location field when you build Notification or
Maintenance Item records from Actions.
When Meridium APM runs the query, Meridium APM provides the prompt with the
Entity Key of the predecessor record that is linked to the underlying Asset Strategy
record:
If the Entity Key identifies a record that belongs to the query's source family, the
Equipment field in the Notification and Maintenance Item records will be
populated automatically with the ID of that record. Meridium APM uses the value
that is returned by the query as the ID. In the baseline query, the query returns the
Equipment ID.
If the Entity Key does not identify a record that belongs to the query's source
family, Meridium APM runs the query Get SAP ID for Functional Location. If the
Entity Key identifies a record that belongs to that query source's family (which is
the Functional Location family if you have not modified the query), the
Functional Location field in the Notification and Maintenance Item records will
be populated automatically with the ID of that record.
For example, suppose an Asset Strategy record is linked to the Equipment record HX112. If you build a Notification record from an Action that belongs to this Asset Strategy,
Meridium APM will:
Identify the Entity Key of the Equipment record HX-112.

Supply this Entity Key to the prompt in the Get SAP ID for Equipment query.
Identify the Equipment ID returned by the query: HX-112.
Populate the Equipment field in the Notification record with HX-112.
You will not need to modify the baseline query if your Asset Strategy records are linked
to records in the baseline Equipment or Functional Location family.
Action Mapping
The following table provides an alphabetical list and description of the fields that exist
for the Action Mapping family. The information in this table reflects the baseline state
and behavior of these fields.
Field
Caption
Data
Type
Description
Behavior and Usage
Class Name Character The rule class that will be

You will need to type the name
invoked when you use an Action of the class.
to create a Meridium APM
record, such as an Inspection Task
record or a Maintenance Item
record.
Description Text
Name
A description of the mapping.
Character The name of the mapping.
You can type any description

you choose.
The value in this field is
displayed in the Action
Mapping column on the Work
Management Item Definitions
tab of the Implementation
Project Path Character The path to the Rules Library rule You will need to type the path
project that stores the rule that
to the rule project.
will be invoked when you use an
Action to create a Meridium APM
record, such as an Inspection Task
record or a Maintenance Item
record.
Execution Mapping
for the Execution Mapping family. The information in this table reflects the baseline state
and behavior of these fields.
Field
Caption
Data
Type
Description
Behavior and Usage

You will need to type the name of
invoked when you implement the class.
the Implementation Package.
Description Text
Name
A description of the mapping. You can type any description you

choose.
Character The name of the mapping.
The value in this field is displayed

in the Execution Mapping column
on the Work Management Item
Definitions tab of the
Implementation Administration
page.
Project Path Character The path to the Rules Library You will need to type the path to
rule project that stores the rule the rule project.
that will be invoked when you
implement the Implementation
Package.
Implementation Authorization
for the Implementation Authorization family. The information in this table reflects the
baseline state and behavior of these fields.
Field Caption
Data
Type
Description
Behavior and Usage
On the datasheet, you can select

Authorization Character A value that indicates whether one of the following values
from a list:
Type
the Implementation Role
(identified by the
Implementation Role record to
Security Group
which the Implementation
Authorization record is linked)
Security User
is assigned to a Security User
or Security Group.
On the datasheet, you can select
Authorization Character Identifies the Security User or a value from the list.
User(s)
Security Group to which the
Implementation Role
If the Authorization
(identified by the
Type field contains the
Implementation Role record to
value Security Group,
which the Implementation
the Authorized User(s)
Authorization record is linked)
list will contain all
is assigned.
active Security Groups
that exist in the database.
If the Authorization
Type field contains the
value Security User, the
Authorized User(s) list
will contain all active
Security Users that exist
in the database.
Implementation Role
for the Implementation Role family. The information in this table reflects the baseline
state and behavior of these fields.
Field
Data
Caption Type
Description
Behavior and Usage
Stores code identifying the

image. This value is used
internally by the Meridium
APM system.
The image will appear in the tree on

the Packaging page after a Security
User that is assigned to the
Implementation Role adds a work item
to the tree.
Image
Binary
Name
Character A name for the

Implementation Role.
The name will be displayed throughout

the interface to identify the
Implementation Role, so be sure to
specify a name that will make sense to
your users.
PRT Template
for the PRT Template family. The information in this table reflects the baseline state and
behavior of these fields.
Field
Caption
Data
Type
ID
Character An identifying name for the You can type any name that you
PRT Template record.
choose.
Template Binary
Description
Stores code identifying the

PRT template file. This
value is used internally by
the Meridium APM system.
Behavior and Usage
The value in this field is created when

you build the PRT template file (using
the Edit Template link on the
Implementation Administration page).
Work Management Item Child

Definition
for the Work Management Item Child Definition family. The information in this table
reflects the baseline state and behavior of these fields.
Field Caption
Data
Type
Description
Behavior and Usage
On the datasheet, you can select a

Child Family Character The successor family whose family from a list containing all
ID
records you want to link to families that are related to the
Implementation Package family
records belonging to the
through the Has Work
family that appears in the
Family ID cell in the Work Management Item relationship.
Management Item
Definition record to which For example, suppose you want to
this Work Management Item be able to link Preventative
Child Definition record is Maintenance Task records to Task
linked.
Grouping records. If the Family ID
field in the predecessor Work
Management Item Definition
record contains the value Task
Grouping, in the Child Family ID
list, you would select Preventative
Maintenance Task.
Child Family Character The relationship family that On the datasheet, you can select
Relationship
relates the family that
the appropriate relationship family
ID
appears in the Family ID
from the list.
cell in the predecessor Work
Management Item
Definition record to the
family that is stored in the
Child Family ID field in this
Child Definition record.

for the Work Management Item Definition family. The information in this table reflects
the baseline state and behavior of these fields.
Field Caption
Data
Type
Added Icon Binary
Description
Behavior and Usage
This icon is used to indicate that the

Stores code identifying record is not yet implemented in SAP,
the image that is used with the exception of the following
when a record belonging families for which updates in SAP are
to the family identified not supported. The image will appear in
in the Family ID field the tree after the associated work item
record is created.
contains the value
Added in the Status
field. This value is used
internally by the
Meridium APM system.
Calibration Task
Inspection Task
On the datasheet, you can select or
clear the check box.
Allow Link Logical

Existing
Deleted Icon Binary
A value that indicates

whether or not you are
allowed to add existing
records in the family
that is stored in the
Family ID field to
records in its
predecessor family
using the shortcut menu
in the tree on the
Packaging page.
For example, if you selected

Preventative Maintenance Task in the
Family ID list, its successor family is
the Implementation Package family,
and the Allow Link Existing check box
is selected, when you right-click the
Implementation Package node in the
tree, the Find an existing Preventative
Maintenance Task to link to <Root
Implementation Package Name>
Implementation Package option will
appear.
Stores code identifying record has been deleted from the
the image that is used Meridium APM system but this change
when a record belonging has not yet been implemented in SAP,
to the family identified with the exception of the following
in the Family ID field families for which updates in SAP are
not supported. The image will appear in
contains the value
the tree after the associated work item

record is marked for deletion.
Deleted in the Status
internally by the
Calibration Task
Inspection Task
On the datasheet, the list displays all
families that are related to the
Family ID Character The family ID of the
family representing the Implementation Package family
type of work item record through the Has Work Management
that you want to add to Item relationship. This field is required.
an Implementation
Package.
For example, if you want to be able to
add Preventative Maintenance Task
records to an Implementation Package,
you would select Preventative
Maintenance Task in the Family ID list.
This would allow you to add
Preventative Maintenance Task records
to an Implementation Package using
the shortcut menu when you right-click
the Implementation Package node in
the tree on the Packaging page.
On the datasheet, the list displays the
description of all System Codes in the
Group Name Character The Packaging Tasks
shortcut menu to which MI_WKMGMTDF_GROUP System
you want to add a link Code Table.
that allows you to create
work item records in
For example, suppose you selected
this family.
Family ID list. If you select Tasks in
the Group Name list, when you click
the Tasks link on the Packaging Tasks
menu, the shortcut menu will contain
the Preventative Maintenance Task
link.
Icon
Binary Stores code identifying record has not been modified in the
the image that is used Meridium APM system since it was
when a record belonging sent to SAP, with the exception of the
to the family identified following families for which updates in
in the Family ID field SAP are not supported. The image will
appear in the tree if the associated work
contains the value
item record is unchanged.

Unchanged in the Status
internally by the

Calibration Task
Inspection Task
Stores code identifying record has been modified in the
the image that is used Meridium APM system and the
when a record belonging changes are not yet implemented in
to the family identified SAP, with the exception of the
in the Family ID field following families for which updates in
SAP are not supported. The image will
contains the value
Modified in the Status appear in the tree after the associated
field. This value is used work item record is modified.
internally by the
Modified
Icon
Binary
Inspection Task
families that are related to the
Character The family ID of the
Implementation Package family
family whose records
will be predecessors to through the Has Work Management
records that belong to Item relationship.
the family that is stored
in the Family ID field. For example, if you selected
Family ID list and you want to be able
to link Preventative Maintenance Task
records to predecessor Task Grouping
records, you would select Task
Grouping in the Parent Family ID list.
This will cause the Create a new
Preventative Maintenance Task to link
to 'Task Grouping' option to be
available on the shortcut menu when
you right-click a Task Grouping record
in the tree.
Character The relationship family relationship families that exist in the
that relates the family
Parent
Family ID
Parent
Family
Calibration Task
database.
Relationship
ID
Sequence
that is stored in the

Family ID field to the
family that is stored in
the Parent Family ID
field.
For example, suppose you selected

Family ID list and Task Grouping in
the Parent Family ID list. If the Task
Grouping family is related to the
Preventative Maintenance Task family
through the Has Tasks relationship, you
would select Has Tasks in the Parent
Family Relationship ID list.
Number A number that

You can type any number beginning
determines the order in with 0.
which the family
identified by the value
in the Family ID field
will appear on the
Packaging Tasks
submenu, the shortcut
menu in the tree, and the
Definitions grid on the
Implementation

Configuration
for the Work Management Item Definition Configuration family. The information in this
table reflects the baseline state and behavior of these fields.
Field
Caption
Data
Type
Description

invoked when you rightclick a work item node in
Behavior and Usage

You will need to type the name of the
class.
the tree on the Packaging

page.
Description Text
Name
A description of the
configuration.
Character The name of the

configuration.
You can type any description you

choose.
The value in this field is displayed in
the Definition Configuration column
on the Work Management Item
Definitions tab of the
Project Path Character The path to the rule that will You will need to type the path to the
be invoked when you right- rule project.
click a work item node in
the tree on the Packaging
page.
for the Implementation Package family. The information in this table reflects the baseline
state and behavior of these fields.
Field
Caption
Data
Type
Description Text
ID
Description
Behavior and Usage
You an type any description you choose.

A description of the
Implementation Package. This field is disabled if the
Implementation Package record is set tot
he Packaged or Implemented state.
Character The ID of the

You can type any ID you choose.
SAP
System
Character The name of the SAP

system to which you will On the datasheet, you can click the
transfer the items in the button to display the Find Items
Implementation Package. window, where you can search for the
SAP System record representing the
SAP system to which you want to
transfer items in the Implementation
Package.
About These Descriptions

Throughout most of the Meridium APM documentation, family field descriptions are
provided in a table format, where the table describes the purpose and behavior of all
fields that are defined for a specific family.
In ASI, however, most of the fields that are defined for families representing SAP items
(e.g., Maintenance Plan) correspond directly to an SAP field. We assume that you are
familiar with your SAP data structure and fields, so we do not provide descriptions of the
values that these fields are meant to store. In other words, because they store the same
values that their corresponding SAP counterpart fields store, we assume that you
understand what to type or select in the fields in the Meridium APM system.
We do, however, provide information about the behavior of some fields on the datasheet
if that behavior cannot be inferred based upon prior knowledge of SAP functionality. For
example, if a field is required in the Meridium APM system in order to save a record, we
note the requirement. Likewise, if a field is populated automatically in the Meridium
APM system as a result of selecting a value in another field, this is also noted.
Note that for all families, all fields are disabled after the Implementation Package is
implemented.
Maintenance Item
Note the following information about specific Maintenance Item fields:
Equipment: The Equipment field is disabled if the Maintenance Item record is

linked to a Task List record and the associated Task List has been implemented in
SAP or if the Task List record contains a value in the Equipment field.

Item record, you can use the Synchronize Reference Object link on the Maintenance Item
Tasks menu to copy that value to the Task List record.
Functional Location: The Functional Location field is disabled if the Maintenance

Item record is linked to a Task List record and the associated Task List has been
implemented in SAP or if the Task List record contains a value in the Functional
Location field.

Item record, you can use the Synchronize Reference Object link on the Maintenance Item
Tasks menu to copy that value to the Task List record.
Implementation Status: This field can contain any of the following values:
Added: The record is new and has not yet been sent to SAP. In this case,
when the Implementation Package is implemented, the corresponding SAP
item will be created.
Modified: One or more values in the record have changed since it was last
sent to SAP. In this case, when the Implementation Package is
reimplemented, the corresponding SAP item will be updated accordingly.
Deleted: The record has been flagged for deletion since it was last sent to
corresponding SAP item will be deleted.
Unchanged: The record has not changed since it was last sent to SAP. In
this case, when the Implementation Package is reimplemented, the
corresponding SAP item will remain untouched.
the Packaging page.
Item Description: This field is required.

Maintenance Item: After the Implementation Package is implemented, this field is
populated automatically with a hyperlink that you can click to open the ITS
System Information screen in Internet Explorer, where you can log in to the SAP
system to view the Maintenance Item.
Maintenance Package
Note the following information about specific Maintenance Package fields:
the Packaging page.
Maintenance Plan
Note the following information about specific Maintenance Plan fields:
Description: This field is required.

Factory Calendar: This field is disabled if the value in the Scheduling Indicator
field is empty. If the Scheduling Indicator field is cleared after a value already
exists in the Factory Calendar field, the Factory Calendar field will be cleared
automatically.
the Packaging page.
ID: After the Implementation Package is implemented, this field is populated

automatically with a hyperlink that you can click to open the ITS System
Information screen in Internet Explorer, where you can log in to the SAP system
to view the Maintenance Plan.
Interval: This field is required.
Interval Unit: This field is required.
Maintenance Strategy: If you modify the value stored in the Maintenance Strategy
field in a predecessor Maintenance Plan record, that value will be automatically
copied to the Maintenance Strategy field in the successor records, with one
exception. If you modify the value stored in the Maintenance Strategy field in a
Maintenance Plan record that is linked to predecessor Maintenance Package
records, the Maintenance Package records will be deleted automatically.
Likewise, if you modify the value stored in the Maintenance Strategy field in a successor
record, that value will be automatically copied to the Maintenance Strategy field in the
predecessor records.
Material
Note the following information about specific Material fields:
the Packaging page.
Notification
Note the following information about specific Notification fields:
the Packaging page.
Notification Number: After the Implementation Package is implemented, this field

is populated automatically with a hyperlink that you can click to open the ITS
System Information screen in Internet Explorer, where you can log in to the SAP
system to view the Notification.
Notification Type: This field is required.
Short Text: This field is required.
Object List Item

Note the following information about specific Object List Item fields:
Equipment Description: This field is populated automatically after the Equipment

Number field is populated.
Equipment Number: If the Functional Location ID field is empty, this field is
required.
Functional Location ID: If the Equipment Number field is empty, this field is
required.
Functional Location Label: This field is populated automatically after the

Functional Location ID field is populated.
the Packaging page.
Operation
Note the following information about specific Operation fields:
Calc: Depending upon what you select in the Calc list, other fields will be enabled
or disabled. This behaviors are described in the following list:
If you select Calculate Duration, the Normal Duration and Normal

Duration Unit fields will be disabled.
If you select Calculate Work, the Work and Work Unit fields will be
disabled.
If you select Calculate Number of Capacities, the Number of Resources

field will be disabled.
If you select Calculate Manually or leave this field blank, all the fields are
enabled.
the Packaging page.
Plant: This field is populated automatically after the Work Center field is
populated.
StdTxt: When you populate the StdTxt field in an Operation record, a message
appears, asking if you want to overwrite the value in the Description field or
append the value in the Long Text field with the selected value.
If you choose to overwrite the value in the Description field, the

Description field becomes disabled.
If you choose to append the value in the Long Text field, the StdTxt field
is cleared after the value in the Long Text field is appended with the
standard text value.
PRT
Note the following information about specific PRT fields:
Document: This field is populated automatically when the Implementation

Package is implemented.
Document Part: This field is populated automatically when the Implementation
Package is implemented.
Document Version: This field is populated automatically when the

the Packaging page.
Task List
Note the following information about specific Task List fields:
Description: This field is required.

Equipment: If the Equipment field contains a value, an Equipment Task List will
be created in SAP. If the Functional Location field contains a value, a Functional
Location Task List will be created in SAP. If neither field contains a value, a
general Task List will be created in SAP.
Equipment Description: This field is populated automatically after the Equipment

field is populated.
Functional Location: If the Equipment field contains a value, an Equipment Task

List will be created in SAP. If the Functional Location field contains a value, a
Functional Location Task List will be created in SAP. If neither field contains a
value, a general Task List will be created in SAP.
Functional Location Label: This field is populated automatically after the

Functional Location field is populated.
Group: After the Implementation Package is implemented, this field is populated

automatically with a hyperlink, which displays the ITS System Information
window in Internet Explorer, where you can log in to the SAP System to view the
SAP Task List.
the Packaging page.
Key Date: The value in this field is set by default to the current date and time.
Maintenance Strategy: This field is disabled if the associated Task List has been
implemented in SAP.
Status: The value in this field is set by default to 4.
System Code Tables Used by ASI

The following table provides a list of the System Code Tables that are used by ASI.
Table ID
Table Description Function

Used to populate the:
MI_WKMGMTDF_GROUP
MI_OPERTION_CALC
Work
Management Item
Definition Groups
Operation Calc
Group Name list on the Work

Management Item Definition
datasheet.
Packaging Tasks menu on the
Implementation Packaging page
in the Meridium APM
Framework application.
Used to populate the Calc list on the

Operation datasheet.
Maintenance Plan Used to populate the Scheduling

MI_MAINTPLN_INDICATOR Scheduling
Indicator list on the Maintenance
Indicator
Plan datasheet.
URL Paths for ASI Features

The following table lists and describes the paths for the Meridium APM Asset Strategy
Implementation (ASI) features. Note that to construct a valid URL, you must prepend
meridium:// to the path. In some cases, you must define parameters following the path.
Feature
URL Path
Asset Strategy ASM/Implementation

Implementation
Description
Displays the Asset Strategy
Implementation Start Page. This
Start Page
path does not accept parameters.
Implementation
Administration ASM/Implementation/Admin
Page
Displays the Implementation

Administration page. This path
does not accept parameters.
Displays the PRT Builder, which
lets you build a new PRT file or
modify an existing PRT file.
This path requires one
parameter: EntyKey.
PRT Builder
ASM/Implementation/BuildPRT
Implementation
Package
ASM/Implementation/Create
Creation Page
The PRT file that you create

using the PRT Builder will be
associated with the PRT record
that is linked to the Operation
record that you select in the PRT
Builder. This Operation record
will be linked to the Task List
record with the specified Entity
Key.
Package Creation page.
Note that this path accepts one
parameter, Key, but providing
this parameter will launch the
Implementation Package Update
page, which is considered a
separate feature of ASI and is
explained in a separate row of
this table.
If you want to access the

Creation page, where you can
create a new Implementation
Package record, you should use
the ASM/Implementation/Create
URL path without the Key
parameter.
Implementation
Package
ASM/Implementation/Create
Update Page
ASM/Implementation/Execution
-ORImplementation
ASM/Implementation/Packaging
Package List
page
Packaging
<Package ID> -ORPage

page, this path requires one
parameter: Key. From the
page, you can manage links
between the Implementation
Package record with the
specified Entity Key and Asset
Strategy records.
Package List page appears,
which displays a list of all
records.
Note that this URL accepts one

parameter, Key, but providing
this parameter will display the
Packaging page, which is
considered a separate feature of
ASI and is explained in a
separate row of this table.

Implementation Package List
page, where you can view a list
of Implementation Package
records, you should use the
or
URL path without the Key
parameter.
Packaging page, these paths
require one parameter, Key.
Both URLs will then display the
Packaging page for the
Implementation Package record
with the specified Entity Key.
Maintain
Object List
Tells the Meridium APM system

to search the Action Revision
records that are linked to the
selected Maintenance Item
record and any Operation record
to which it is linked. If those
Action Revision records are
associated with an underlying
Asset Strategy record that is
linked to an Equipment record,
one Object List Item record will
ASM/Implementation/Maintain_Object_List be created for each of those
underlying Equipment records.
This path requires one

parameter: EntyKey, where the
EntyKey is the Entity Key of the
Maintenance Item record whose
Object List Items you want to
maintain.
Examples of ASI URLs
meridium://ASM/Implementation
Displays the Asset Strategy Implementation Start Page.
meridium://ASM/Implementation/ADMIN
Displays the Implementation Administration page.
meridium://ASM/Implementation/BuildPRT?Key=123456
Displays the PRT Builder, where you can create or modify a PRT file. The PRT file will
be associated with the PRT record that is linked to the Operation record that you select in
the PRT Builder. This Operation record will be linked to the Task List record with the
Entity Key 123456.
meridium://ASM/Implementation/CREATE
Displays the Implementation Package Creation page, where you can create a new
meridium://ASM/Implementation/EXECUTION
Displays the Implementation Package List page.
meridium://ASM/Implementation/PACKAGING
Displays the Implementation Package List page.
meridium://ASM/Implementation/CREATE?KEY=1234567
Displays the Implementation Package Update page, where you can manage links between
the Implementation Package record with the Entity Key 1234567 and Asset Strategy
records.
meridium://ASM/Implementation/EXECUTION?KEY=1234567
Displays the Packaging page for the Implementation Package record with the entity key
1234567.
meridium://ASM/Implementation/PACKAGING?KEY=1234567
Displays the Packaging page for the Implementation Package record with the entity key
1234567.
meridium://ASM/Implementation/Maintain_Object_List/EntyKey=1234567
Tells the Meridium APM system to maintain the Object List for the Maintenance Item
record with the Entity Key 1234567.
Values Mapped to SAP Maintenance

Plans
The following table explains the Maintenance Plan fields that are used to populate SAP
Maintenance Plan fields when you implement an Implementation Package.
Meridium APM Field

Caption
SAP Field ID
SAP Field Caption
ID
WARPL
Maintenance Plan
Category
MPTYP
Maintenance Plan Category
Maintenance Strategy
WSTRA
Interval
ZYKL1
Maintenance Cycle
Interval Unit
ZEIEH
Unit for the Performance of Maintenance Tasks
Counter
POINT
Measuring Point
Offset
OFFS1
Maintenance Package Offset
Interval Description
PAK_TEXT
Text for Maintenance Package/Cycle

(Time/Performance)
Description
WPTXT
Maintenance Plan Text
Sort Field
PLAN_SORT
Sort Field for Maintenance Plans
Authorization Group
BEGRU
Technical Object Authorization Group
Shift Factor for Late

Completion
VSPOS
Shift Factor for Late Completion
Shift Factor for Early

Completion
VSNEG
Shift Factor for Early Completion
Tolerance for Late

Completion
TOPOS
Tolerance for Late Completion (%)
Tolerance for Early

Completion
TONEG
Tolerance for Early Completion (%)
Cycle Modification Factor
SFAKT
IBIP: Cycle Modification Factor
Scheduling Indicator
STICH
Scheduling Indicator
Factory Calendar
FABKL
Factory Calendar Key
Scheduling Period
ABRHO
Scheduling Period
Scheduling Unit
HUNIT
Unit in Scheduling Interval
Call Horizon
HORIZ
Call Horizon for Maintenance Plan Calls
Call Confirm
CALL_CONFIRM
Only Create New Call Object After Completing

Predecessor
Start Date
STADT
Start Date
Start Counter
SZAEH
Start Counter Reading

Items
The following table explains the Maintenance Item fields that are used to populate SAP
Maintenance Item fields when you implement an Implementation Package.
Meridium APM Field

Caption
SAP Field
ID
SAP Field Caption
Maintenance Item
WAPOS
Maintenance Item
Category
MPTYP
Maintenance Plan Category
WSTRA
Item Description
PSTXT
Item Short Text
Functional Location
TPLNR
Functional Location
Equipment
EQUNR
Equipment Number
Assembly
BAUTL
Assembly
Planning Plant
IWERK
Maintenance Planning Plant
Maintenance Planner Group
WPGRP
Planner Group for Customer Service and Plant

Maintenance
Order Type
AUART
Order Type
Activity Type
ILART
Maintenance Activity Type
Work Center
GEWERK
Main Work Center for Maintenance Tasks
Work Center Plant
WERGW
Plant Associated with Main Work Center
Business Area
GSBER
Business Area
Group
PLNNR
Key for Task List Group
Group Counter
PLNAL
Group Counter
System Condition
ANLZU
Overall Condition of Technical System
Notification Type
QMART
Notification Type
Priority
PRIOK
Priority

Items
The following table explains the Object List Item fields that are used to populate SAP
Object List Item fields when you implement an Implementation Package.
Meridium APM Field Caption SAP Field ID SAP Field Caption

Sort Field
SORTF
Object List Sort Field
Equipment Number
EQUNR
Equipment Number
Functional Location ID
TPLNR
Functional Location
Functional Location Label
STRNO
Functional location Label
Values Mapped to SAP Task Lists

The following table explains the Task List fields that are used to populate SAP Task List
fields when you implement an Implementation Package.

Equipment
EQUNR
Equipment Number
Functional Location
TPLNR
Functional Location
Group
PLNNR
Key for Task List Group
Description
KTEXT
Work Center Description
Work Center
ARBPL
Work Center
Planning Plant
WERKS
Maintenance Planning Plant
Usage
VERWE
Use by User or System
Planner Group
VAGRP
Responsible Planner Group/Department
Status
STATU
Status
STRAT
System Condition
ANLZU
Overall Condition of Technical System
Assembly
ISTRU
Assembly
Key Date
STTAG
Key Date
Plant
AWERK
Plant
Values Mapped to SAP Operations

The following table explains the Operation fields that are used to populate SAP Operation

Operation
VORNR
Operation/Activity Number
Sub Operation
UVORN
Suboperation
Work Center
ARBPL
Work Center
Control Key
STEUS
Control Key
Plant
WERKS
Plant
StdTxt
KTSCH
Standard Text Key
Description
LTXA1
Operation Short Text
Currency
WAERS
Currency Key
Cost Element
SAKTO
Cost Element
Purchasing Organization
EKORG
Purchasing Organization
Purchasing Group
EKGRP
Purchasing Group for External

Processing
Material Group
MATKL
Material Group
Normal Duration
DAUNO
IBIP: Normal Operation Duration
Normal Duration Unit
DAUNE
Normal Duration/Unit
Work
ARBEI
IBIP: Operation Labor
Work Unit
ARBEH
Unit for Work
Number of Resources
ANZZL
IBIP: Char. - No. of Required Capacity
User Field Key Word ID
SLWID
Key Word ID for User-defined Fields
User Field 0
USR00
User Field with 20 Characters
User Field 1
USR01
User Field 2
USR02
User Field 3
USR03
User Field 4
USR04
IBIP: User Field for Quantity (Length 10,3)
User Field 4 Units
USE04
User field: Unit for Quantity Fields
User Field 5
USR05
IBIP: User Field for Quantity (Length 10,3)
User Field 5 Units
USE05
User Field 6
USR06
IBIP: User Field for Values (Length 10,3)
User Field 6 Units
USE06
User Field 7
USR07
IBIP: User Field for Values (Length 10,3)
User Field 7 Units
USE07
User Field 8
USR08
User field for Date
User Field 9
USR09
User field for Date
User Field 10
USR10
User-defined Field: Indicator for Reports
User Field 11
USR11
User-defined Field: Indicator for Reports
Calc
INDET
Key for Calculation
Activity Type
LARNT
Activity Type
Order Quantity
BMEIH
Operation Order Quantity Unit
Order Quantity Unit
BMVRG
IBIP: Purchase Order Quantity Operation
Execution Factor
AUFKT
Execution Factor
System Condition
ANLZU
System Condition
Values Mapped to SAP Materials

The following table explains the Material fields that are used to populate SAP Material

Material Number
IDNRK
Material Number
Quantity
MENGE
Quantity
Values Mapped to SAP PRTs

The following table explains the PRT fields that are used to populate SAP PRT fields
when you implement an Implementation Package.
Meridium APM Field Caption
SAP Field SAP Field Caption

ID
None. The value in the FHMAR field is

FHMAR
always set to D.
Production Resources/Tools Category
Control Key
STEUF
Control Key for Management of Production

Resources/Tools
Document
DOKNR
Document Number
Document Part
DOKTL
Document Part
Document Type
DOKAR
Document Type
Document Version
DOKVR
Document Version
Item Number
PSNFH
Item Number for Production Resource/Tool
Quantity
MGVGW
Standard Value for PRT Quantity
Quantity Unit
MGEINH
Quantity Unit of Production Resource/Tool

Packages
The following table explains the Maintenance Package fields that are used to populate
SAP Maintenance Package fields when you implement an Implementation Package.
Meridium
APM Field
Caption
SAP Field ID
SAP Field Caption
KTEXTZYK<#>
Note:
Cycle
<#> is a number between one (1) and 32 that is
determined by the sequence of the Operations on the
associated Task List, regardless of the Operation
number.
Short Text for the

Maintenance Cycle
(Time/Performance)
Values Mapped to SAP Notifications

The following table explains the Notification fields that are used to populate SAP
Notification fields when you implement an Implementation Package.
Meridium APM Field Caption
SAP Field ID SAP Field

Caption
Notification Type
NOTIF_TYPE
Notification
Type
Equipment
EQUIPMENT
Equipment
Number
Functional Location
FUNCT_LOC
Functional
Location
Short Text
SHORT_TEXT
Short Text
Priority
PRIORITY
Required Start Date
Priority
Required Start
DESSTDATE Date
-AND-
-AND-
Required Start
Time
Required End
DESENDDAT
Date
DESSTTIME
Required End Date
-AND-
-AND-
DESENDDATE
Required End
Time
None. The value in the NOTIF_DATE field is populated

automatically with the date and time that the Notification
was created.
NOTIF_DATE
Date of
Notification
None. The value in the NOTIFTIME field is populated
NOTIFTIME
Notification
automatically with the date and time that the Notification

was created.
Time
A collection of records that define the work that you want to perform and the Asset
Strategies that contain the original work requests (i.e., Action records).
Implementation Role
A type of work that is performed by people within your organization. In ASI, you can
create Implementation Role records to categorize these work types.
Primary Implementation Package

The Implementation Package to which the Asset Strategy and its Actions are originally
added.
Secondary Implementation Package

Any Implementation Package to which an Action is transferred.
Work Item Record

Records that represent the work that should be completed when the Implementation
Package is implemented. Throughout the documentation, we refer to them as work item
records because they can belong to any family.

Optimization
The Meridium APM Asset Strategy Optimization (ASO) module extends the analytical
capabilities of the Asset Strategy Management (ASM) module by providing the
additional ability to:
Define planned and unplanned correction costs for each Risk.

Define Resources, such as spare parts and human resources, that are needed to
perform actions.
Define Time to Failure (TTF) and Time to Repair (TTR) information based on
Monte Carlo simulation results.
Integrate with the Meridium APM Reliability Analytics module.
Use a diagramming tool that allows you to represent the physical structure of
pieces of equipment and locations.
Define Global Events.
While ASO is its own separate module, it is intended to extend the capabilities available
in ASM by providing a more detailed analysis of a particular strategy. You will, therefore,
access ASO directly from an existing Asset Strategy, System Strategy, or Unit Strategy. In
ASO, you can use the additional features in the preceding list to determine the most
optimal strategy for a piece of equipment or location, which can then be viewed and
managed further in ASM.
In other words, ASO and ASM work together to provide a more comprehensive view of
your equipment and locations to help you determine the best way to manage them to
reduce cost and risk.
Many of the features in ASO work similarly to or exactly the way they work in System
Reliability Analysis. Throughout the ASO documentation, where applicable, links are
provided to the System Reliability Analysis documentation to direct you to more details.
D
Note: You can access ASO only if the ASM module is active.
ASO System Requirements

The following licenses must be active to take advantage of ASO:

ASM and ASI
The ASM and ASI license activates the ASM module. This documentation assumes that
you have deployed ASM. In addition, your system must contain the basic Meridium APM
system architecture.
perform some configuration tasks specifically for the ASO module.
A Note About ASM Terms Used in the

ASO Documentation
Many of the concepts in ASO build upon concepts in Asset Strategy Management (ASM),
such as:
Active Strategy
Proposed Strategy
Mitigated Risk
Unmitigated Risk
Throughout the ASO documentation, we use terms that are introduced and described in
more detail in the ASM documentation. We assume that you are familiar with these terms
and with the ASM functionality in general. Where applicable, the ASO documentation
contains links to the ASM documentation to direct you to more details.
ASO Data Model

The following diagram shows the entity and relationship families that are used in an ASO
Analysis. Throughout this documentation, we use the term ASO Analysis to mean the
combination of the root System Analysis record and all records that are linked to it. Note
that in the following image:
Gray arrows and boxes represent entity families, relationship families, and
associated relationship definitions that exist in the ASO data model but are not
currently used in any ASO workflows.
Black arrows and boxes represent entity families, relationship families, and
associated relationship definitions that are configured in the baseline database and
do not require customization for the baseline functionality to work.
Gray arrows and boxes represent entity families, relationship families, and
associated relationship definitions that may require customization.
While interpreting the image, note that:
While only one System Scenario box appears in the image, each ASO Analysis
will contain multiple System Scenario records.
The image contains two System SubSystem boxes because in an ASO Analysis,
System SubSystem records serve two purposes:
They identify the Diagram. Each ASO Analysis contains only one
Diagram, but per Scenario, the database contains two separate System
SubSystem records to represent this Diagram. In other words, for each
Scenario that exists in the analysis, the set of System SubSystem records
that represent the Diagram is duplicated. So, for an analysis that contains
only an Active Scenario and Proposed Scenario, four identical System
Subsystem records will exist. Two of the records will be linked to the
Active Scenario record, and two of them will be linked to the Proposed
Scenario record. Whenever a change is made to the properties of the
Diagram itself, the Meridium APM system updates all System SubSystem
records that represent the Diagram so that they are always identical.
Note: The Meridium APM system creates two identical System SubSystem records to
represent the Diagram because the ASO and System Reliability Analysis modules share
code and in System Reliability Analysis, each analysis can have multiple Diagrams.
They identify subsystems within the Diagram. In an ASO Analysis, the

Diagram can contain multiple subsystems. Per Scenario, the database
contains two separate System SubSystem records to represent a single
subsystem in the Diagram. In other words, for each Scenario that exists in
the analysis, the set of System SubSystem records that represent a
subsystem within the Diagram is duplicated. So, for an analysis that
contains only an Active Scenario and a Proposed Scenario, if the Diagram
contains only one subsystem, four identical System Subsystem records
will exist to represent this subsystem. Two of the records will be linked to
the Active Scenario record, and two of them will be linked to the Proposed
Scenario record. Whenever a change is made to the properties of the
subsystem element via the Diagram, the Meridium APM system updates
all System Subsystem records that represent that subsystem so that they
are always identical.
In other words, because each ASO Analysis must have an Active Scenario and a Proposed
Scenario at all times, each ASO Analysis will contain at least four System SubSystem
records, where these System SubSystem records represent the Diagram. Two of these
records will be linked to the Active Scenario record, and two of them will be linked to the
Proposed Scenario record. As additional Scenarios are created, other identical sets of
System SubSystem records are created and linked to those Scenario records to represent
the Diagram. In addition, if the Diagram includes subsystems, per Scenario, the ASO
Analysis will contain two additional System SubSystem records to represent those
subsystems.
The System SubSystem family is related to the System SubSystem family through
the Has System Elements relationship. In the image, the System SubSystem box
that contains the text Diagram in parentheses represents the Diagram. The System
SubSystem box that contains the text Subsystem in parentheses represents
subsystems within the Diagram. This distinction is made so that you can see that
the System Global Event record is linked to the System SubSystem records that
represents the Diagram.
Note: In ASO Analyses, all System SubSystem records are linked to the successor System
Element records. The boxes are separated in the image only to clarify the Has Global
Events relationship.
Components in an ASO Analysis

An ASO Analysis is made up of records and links as defined by the ASO data model.
Specifically, an ASO Analysis is a collection of Scenarios, Resources, and simulation
results. An ASO Analysis is represented by a System Analysis record, which stores
identifying information about the analysis and is linked to other records that make up the
analysis. Beyond understanding an ASO Analysis at the entity level, it is helpful to
visualize it at a conceptual level, where groups of records and links make up the main
elements of the analysis. These elements are described in the following list:
Diagram: A logical, visual representation of the physical structure of equipment

and locations, including the connections between them. Each ASO Analysis
contains one Diagram.
Note: If you create an ASO Analysis from an Asset Strategy, a Diagram will exist, but it
will contain only an Asset element.
A Diagram is represented by a System Subsystem record, which can be linked to System
Subsystem, System Sensor, System Buffer, System Link, System Asset, and System
Switch records. The items that these records represent are referred to as elements, which
are simply the components that make up the Diagram itself.
Scenario: A representation of one possibility for managing the risk and cost for a
given piece of equipment or location. A Scenario is represented by a System
Scenario record, which contains all the identifying information for the Scenario
and is linked to other records that help define the Scenario. Each ASO Analysis
contains multiple Scenarios and will always contain at least the following
Scenarios:
Active Scenario
Proposed Scenario
Unmitigated Scenario
Note: The Unmitigated Scenario cannot be manipulated in ASO. It represents the

unmitigated strategy, or the strategy as it exists with only Risks and no Actions. The
simulation results will include results for the Unmitigated Scenario, but you cannot
modify the Unmitigated Scenario in ASO.
An ASO Analysis can contain additional Scenarios if you choose to create them. Except
for the Unmitigated Scenario, each Scenario can contain the following components:
Risk: A component that identifies a specific way that a piece of equipment

or location can fail, specifies the consequences of the failure, and includes
Time to Failure (TTF) and Time to Repair (TTR) distribution data. A Risk
is represented by a System Risk record, which contains all of the
identifying information for the risk.
Action: A component that identifies a specific operation that can be

performed against a piece of equipment or location. Actions include
condition-based maintenance, procedures, redesigns, time-based
maintenance, and training and may or may not mitigate Risks. Actions are
represented by records in the System Condition Monitor, System
Inspection, System Preventive Maintenance, or System Special Action
families, which contain all the identifying information for the action.
Global Event: A component that groups together actions that require a

shutdown. Scheduling a Global Event can make a system more efficient
by providing more time in which to run while still allowing maintenance
and other actions to take place. A Global Event is represented by a System
Global Event record, which contains all the identifying information for the
Global Event.
Resource: A component of an ASO Analysis that associates a cost with an

occurrence of an action or risk. Resources are represented by a System Resource
record.
Simulation Results: The outcome of running a simulation against all Scenarios

included in a given ASO Analysis. Simulation results are stored in System
Element Result, System Action Result, or System Resource Result records, which
are linked to the root System Analysis record.
Visual Representation of ASO Analysis

Components
The following image illustrates the components that make up an ASO Analysis. In the
image, you can see that the analysis contains one Diagram and four Scenarios:
Unmitigated Scenario: Contains only Risks.

Active Scenario: Contains the same Risks as the Unmitigated Scenario, plus
Actions and a Global Event.
Proposed Scenario: Contains only two of the Risks and two of the Actions from
the Active Scenario.
Other Scenario: Contains two of the Risks and all three Actions from the Active
Scenario, plus an additional Action.
In addition, the analysis contains Resources and Simulation Results.
ASO Workflow
The following steps represent a complete workflow for using ASO:
1. Open the Asset Strategy, System Strategy, or Unit Strategy from which you want
to create an ASO Analysis.
2. Create an ASO Analysis from the strategy. When you do so, two Scenarios will be
created automatically:
An Active Scenario that represents the Active Strategy.
A Proposed Scenario that represents the Proposed Strategy.
3. Review the default simulation parameters, and modify them if needed.

4. Review the Diagram that was created automatically from the information in ASM,
and modify it if needed.
5. In the Scenario that represents the Active Strategy:
Provide values that will be used to yield accurate simulation results.
Optimize Action intervals, define Resources, and define Global Events.
Run a simulation.
Evaluate the simulation results.
2. In the Scenario that represents the Proposed Strategy:
Provide values that will be used to yield accurate simulation results.
Optimize Action intervals, define Resources, and define Global Events.
Add, modify, or remove Actions and Risks.
Run a simulation.
Evaluate the simulation results.
3. If the simulation results indicate that neither the Active Scenario nor the Proposed
Scenario represents an acceptable strategy, suggest a new strategy. To do so, you
can:
1.
Modify the Proposed Scenario until it represents the suggested strategy.
-OR1.
Create a new Scenario to represent the suggested strategy. You can create
the new Scenario in either of the following ways:
Create it from scratch.
Create it by copying the existing Active or Proposed Scenario.
8. In the Scenario that represents the suggested strategy:

1. Provide values that will be used to yield accurate simulation results.
2. Optimize Action intervals, define Resources, and define Global Events.
3. Add, modify, or remove Actions and Risks.
4. Run a simulation.
5. Evaluate the simulation results.
9. If you are not satisfied with the simulation results from the Scenario, continue
suggesting new strategies (by modifying the Proposed Scenario or creating new
Scenarios), running simulations, and evaluating the simulation results until you
are satisfied with them.
10. When you have determined which Scenario represents the most acceptable
strategy, if it is not already the Proposed Scenario, set it as the Proposed Scenario.
11. Navigate back to ASM to continue managing the strategy as needed.
Overview of the ASO Analysis Example

To make the ASO documentation easier to follow and to help explain how ASO Analyses
can be created and used, we provide an example of an ASO Analysis. We will refer to this
example as necessary throughout the ASO documentation.
Our ASO Analysis Example involves a water bottling facility, which contains equipment
that performs the following steps in the water bottling process:
1. Collect water from a source via a pump.
2. Pump the collected water into a holding tank.
3. Extract water from the holding tank into a filling machine, which fills bottles.
4. Attach caps to the bottles.
5. Attach labels to the bottles.
Note: In this example, we assume that the bottles, labels, and caps are produced at a
separate facility and used in this process.
In this example, the water bottling facility is a unit, which we refer to as the Water
Bottling Unit. This unit contains two systems: Water Collection System and Bottling
System. Each system contains equipment that work together to complete a single process.
The Water Collection System contains the following equipment:
Water Pump
Water Tank
The Bottling System contains the following equipment:
Filling Machine
Capping Machine
Labeling Machine
The unit, systems, and equipment and the process in which they are involved are
illustrated in the following image.
Remember that an ASO Analysis begins with an Asset Strategy, System Strategy, or Unit
Strategy. Therefore, our ASO Analysis Example includes the following strategies, where
the indentation of the bullets indicates the structure of the strategies:
Water Bottling Strategy (Unit Strategy)
Water Collection Strategy (System Strategy)
Water Pump Strategy (Asset Strategy)
Water Tank Strategy (Asset Strategy)
Bottling Strategy (System Strategy)
Filling Machine Strategy (Asset Strategy)
Capping Machine Strategy (Asset Strategy)
Labeling Machine Strategy (Asset Strategy)
Note: In our ASO Example, each Asset Strategy has an Active Strategy and a Proposed
Strategy that are different from one another.
In our ASO Analysis Example, we will create an ASO Analysis from the Water Bottling
Strategy (the Unit Strategy). Where we explain features that are specific to equipment,
such as managing Risks and Actions, we focus on the equipment Water Pump.
ASM Records and Links in Our

Example
Remember that in our ASO Analysis Example, the following strategies exist:
The following image shows the records and links that are used to create the association
between the Unit Strategy, one of its System Strategies, one of its Asset Strategies (Water
Pump Strategy), and that Asset Strategy's Action and Risk records. Keep in mind that for
each Asset Strategy in the previous list, a similar set of records and links exists. This
image is meant to provide a visual indication of only the records and links that exist for
the Water Pump Strategy.
Remember that throughout this documentation, although we explain how to create an
ASO Analysis from the Unit Strategy, the majority of the focus is at the Water Pump
level.
ASO Records and Links in Our

Example
Remember that in our ASO Analysis Example, we create an ASO Analysis from the Unit
Strategy Water Bottling Strategy, which includes the Asset Strategy Water Pump
Strategy. This Asset Strategy includes the following Action and Risk records:
Risk records: Impeller Failure, Bearing Failure, Seal Failure
Action records: Redesign Impellers, Vibration Analysis, Replace Seals
Using this example, the following image illustrates the records and links that would exist
in ASO after the ASO Analysis is created. The colors in the image have the following
meanings:
Orange: Identifies two separate Water Bottling Strategy System Subsystem

records, which represent the Diagram in the ASO Analysis. Note that although
two physical records exist in the database, ASO allows you to have only one
Diagram per analysis. Therefore, whenever a change is made to the properties of
the Water Bottling Strategy element via the Diagram, the Meridium APM code
updates both System Subsystem records so that they are always identical.
Yellow: Identifies two separate Water Collection Strategy System Subsystem
records, which represent the Water Collection Strategy System Strategy. Note that
these records are used to build the Diagram for the ASO Analysis. Although two
physical records exist in the database, ASO allows you to have only one Diagram
per analysis. Therefore, whenever a change is made to the properties of the Water
Collection Strategy element via the Diagram, the Meridium APM code updates
both System Subsystem records so that they are always identical.
Green: Identifies two separate Water Pump Strategy System Asset records, which
represent the Water Pump Strategy Asset Strategy. Note that these records are
used to build the Diagram for the ASO Analysis. Although two physical records
exist in the database, ASO allows you to have only one Diagram per analysis.
Therefore, whenever a change is made to the properties of the Water Pump
Strategy element via the Diagram, the Meridium APM code updates both System
Asset records so that they are always identical.
Gray: Identifies System Asset records that are part of the ASO Analysis but not
the focus of this documentation. The image is meant to provide a visual indication
of only the records and links that exist for the Water Pump System Asset record.
Remember that throughout this documentation, although we explain how to create
an ASO Analysis from the Unit Strategy, the majority of the focus is at the Water
Pump level.
You can see that the Water Pump System Asset record is linked to three System Risk
records. From the name of each System Risk record, you can infer the Risk record in
ASM from which it was created. In addition, the Water Pump System Asset record is also
linked to records in the following families through the Has System Actions relationship:
System Special Action

System Inspection
System Preventive Maintenance
If you remember from the ASO data model, these families are all subfamilies of the
System Action family. While the subfamily to which these records belong differs, the
three records were all created from an Action record in ASM. From the name of the
record (e.g., Redesign Impellers), you can infer the Action record from which it was
created.
Note: The subfamilies to which the records belong is determined by the System Action
Mapping records that have been configured.
Asset Data
In our ASO Analysis Example, the Equipment record Water Pump contains the following
values:
Name: Water Pump

Production Contribution: 100
Fixed Cost: 5000
Variable Cost: 50
Variable Cost Units: Per Hour
Lost Production Cost: 0
Lost Production Cost Units: Per Day
Asset Strategy Data

In our ASO Analysis Example, the Asset Strategy record that is linked to the Equipment
record Water Pump contains the following values:
Strategy ID: Water Pump Strategy

Description: Asset Strategy for the Water Pump
Plan Length: 5
Asset Name: Water Pump
Asset Family: Equipment
Action Data
The following table shows the example data stored in the Action records that are linked to
the Active Strategy record with the ID Water Pump Strategy.
Action
Values
Name: Redesign Impellers
Redesign Impellers
Action Type: Redesign (DSM)
Interval: 2
Interval Units: Years
Nonrecurring: Yes
Cost: 1,600
Shutdown Required: Yes
Name: Replace Seals
Replace Seals
Action Type: Time-Based Maintenance (Preventive) (PM)
Interval: 2
Nonrecurring: No
Cost: 2,000
Name: Vibration Analysis
Vibration Analysis
Action Type: Condition-Based Maintenance (Predictive) (CM)
Interval: 3
Interval Units: Weeks
Nonrecurring: No
Cost: 0
Shutdown Required: No
Risk Data
The following table shows the example data stored in the Risk records (and the
corresponding Risk Assessment records) that are linked to the Active Strategy record with
the ID Water Pump Strategy. It also shows which Action records represent actions that
mitigate the risk.
Risk
Risk Values
Mitigating Action Values
Name: Seal Failure

Seal Failure
Unmitigated Risk Rank: 150.6
Name: Replace Seals

Mitigated Risk Rank: 3.6
Name: Bearing Failure
Mitigated Financial Risk:

$230.00
Unmitigated Risk Rank: 306
Unmitigated Financial Risk:

$1,080.00
Name: Impeller Failure

$360.00
Name: Replace Seals
Unmitigated Financial Risk: $690.00
Bearing Failure
Impeller
Failure
Unmitigated Financial Risk: $165.00 Mitigated Financial Risk: $55.00
Action Data
The following table shows the example data stored in the Action records that are linked to
the Proposed Strategy record with the ID Water Pump Strategy.
Note: Values that differ from the values in the corresponding Action record that is linked
to the Active Strategy record are colored red.
Action
Values
Action Type: Redesign (DSM)
Interval: 3
Redesign Impellers

Nonrecurring: Yes
Cost: 1,800
Name: Replace Seals

Action Type: Time-Based Maintenance (Preventive) (PM)
Interval: 2
Replace Seals
Nonrecurring: No
Cost: 1,500
Action Type: Condition-Based Maintenance (Predictive) (CM)
Condition Monitoring Type: Periodic
Interval: 4
Vibration Analysis

Nonrecurring: No
Cost: 0
Risk Data
The following table shows the example data stored in the Risk records (and the
corresponding Risk Assessment records) that are linked to the Proposed Strategy record
with the ID Water Pump Strategy. It also shows which Action records represent actions
that help mitigate the risk.
Note: Values that differ from the values in the corresponding Risk record that is linked to
the Active Strategy record are colored red.
Risk
Risk Values
Mitigating Action Values
Name: Seal Failure

Seal Failure
Unmitigated Risk Rank: 150.6
Name: Replace Seals


$225.00
Unmitigated Financial Risk:

$1,080.00

$360.00
Name: Replace Seals
Unmitigated Financial Risk: $690.00
Bearing Failure
Impeller
Failure
Unmitigated Financial Risk: $165.00 Mitigated Financial Risk: $55.00
Action Data
The following table shows the example data that is used in the Actions that are defined
for the Water Pump Strategy and belong to the Active Scenario. Because the Active
Scenario always reflects data that was mapped from ASM and these values cannot be
changed, this table includes only the values that are specific to ASO and were not mapped
from ASM. For a list of values that exist in the corresponding Action records in the
Active Strategy with the ID Water Pump Strategy, click here.
Note: The Source column identifies the family name of the record in which the associated
data is stored. The data from ALL source records is combined to create comprehensive
Action data.
Action
Mitigated
Risk
Redesign
Impellers
Impeller
Failure
Source
Values
Duration: 2

Duration Units: Weeks
Replace Failure Consequence:
Yes
Replace TTF Distribution: Yes

System Risk Assessment
Mitigated Unplanned Correction

Cost: 1000
Name: New TTF Distribution
1
Distribution Type: Weibull

Time Unit: Months
Weibull
Beta: 4
Eta: 48
Gamma: 0
Duration: 1
Replace Seals Seal Failure
System Preventive
Maintenance
Vibration
Analysis
System Inspection
Bearing
Failure
Duration Units: Days

Duration: 1
Duration Units: Hours
Detection Probability (%): 90
1.
When you click a hyperlinked Action name, the Mitigated Unplanned Correction
Cost field appears on the Mitigated Risks tab and is labeled Fixed Unplanned
Correction Cost.
Risk Data
The following table shows the example data that is used in the Risks that are defined for
the Water Pump Strategy and belong to the Active Scenario. Note that this table includes
only the values that are specific to ASO and were not mapped from ASM. For a list of
values that exist in the corresponding Risk records in the Active Strategy with the ID
Water Pump Strategy, click here.
Risk data.
Risk
Mitigating
Action
Source
Values
Last Failure: 1/1/1999 12:00:00 AM
Fixed Unplanned Correction Cost: 1500
Variable Unplanned Correction Cost: 1000
Variable Unplanned Correction Cost Units:
Per Day
Planned Correction Cost: 1000
Planned Correction Duration: 12
Planned Correction Duration Units: Hours
Seal Failure
Replace Seals
System
Risk
Is Active: Yes
Is Latent: No
Failure Without Replacement: No
Number of Subcomponents: 1
PF Interval: 30
PF Interval Units: Days
Repair Immediately: Yes
Percentage of PF Interval to Wait (%): 0
Name: TTF Distribution
Time Unit: Years
Weibull
Beta: 4
Eta: 3
Gamma: 0
Enable Distribution Association: No
Name: TTR Distribution

Distribution Type: SingleValue
Normal
Time Unit: Hours

Value: 12
Last Failure: 1/1/1999 12:00:00 AM
Per Day
Bearing
Failure
Vibration
Analysis
System
Risk
Is Active: Yes
Is Latent: No
PF Interval: 6
PF Interval Units: Weeks
Exponential
Distribution Type: Exponential
Time Unit: Months
Value: 60
Exponential
Time Unit: Hours

MTTR: 8
Last Failure: 1/1/1999 12:00:00 AM
Per Day
Impeller
Failure
Redesign
Impellers
System
Risk
Is Active: Yes
Is Latent: No
PF Interval: 0
Exponential

Time Unit: Months
Value: 24
Normal
Time Unit: Hours

Value: 12
Action Data
The following table shows the example data that is used in the Actions that are defined
for the Water Pump Strategy and belong to the Proposed Scenario. Because you can
change the values that were originally mapped from ASM to a Proposed Scenario, this
table includes the values that are specific to ASO and those that were mapped from ASM.
In our example, however, we have not changed these values from their original ASM
values. To distinguish between the two types of values, values that were mapped from
ASM are colored gray in the table.
Note that values that differ from the values in the corresponding Action in the Active
Scenario are colored red.
Action data.
Action
Mitigated
Risk
Source
Values
Redesign
Impellers
Impeller
Failure
System Special
Action
Action Type: Redesign (DSN)

Action Cost: 1600
Interval: 2
Duration: 1.5
Duration Units: Weeks
One Time Action: Yes
Replace Failure Consequence: Yes
Replace TTF Distribution: Yes
System Risk
Assessment
Mitigated Unplanned Correction Cost:

1000
Name: New TTF Distribution
1

Time Unit: Months
Weibull
Beta: 4
Eta: 48
Gamma: 0
Name: Replace Seals
Replace Seals Seal Failure System Preventive

Maintenance
Action Type: Time-Based

Maintenance (Preventive) (PM)
Action Cost: 2000
Interval: 2
Duration: .5
Duration Units: Days
One Time Action: No
Action Type: Condition-Based
Maintenance (Predictive) (CM)
Condition Monitoring Type:
Periodic
Action Cost: 0
Interval: 3
Vibration
Analysis
Bearing
Failure
System Inspection

Duration: 1
Duration Units: Hours
One Time Action: No
Detection Probability (%): 100
1.
When you click a hyperlinked Action name, the Mitigated Unplanned Correction
Cost field appears on the Mitigated Risks tab and is labeled Fixed Unplanned
Correction Cost.
Risk Data
The following table shows the example data that is used in the Risks that are defined for
the Water Pump Strategy and belong to the Proposed Scenario. Because you can change
the values that were originally mapped from ASM to a Proposed Scenario, this table
includes the values that are specific to ASO and those that were mapped from ASM. In
our example, however, we have not changed these values from their original ASM values.
To distinguish between the two types of values, values that were mapped from ASM are
colored gray in the table.
Note that values that differ from the values in the corresponding Risk in the Active
Scenario are colored red.
Risk data.
Risk
Mitigating
Action
Source
Values
Name: Seal Failure
Seal Failure
Replace Seals
System
Risk
Last Failure: 1/1/1999 12:00:00 AM

Per Day
Is Active: Yes
Is Latent: No
PF Interval: 30

Time Unit: Years
Weibull
Beta: 4
Eta: 3
Gamma: 0
Normal
Time Unit: Hours

Value: 12
Bearing
Failure
Vibration
Analysis
System
Risk
Last Failure: 1/1/1999 12:00:00 AM

Per Day
Is Active: Yes
Is Latent: No
PF Interval: 6
PF Interval Units: Weeks
Exponential
Time Unit: Months

Value: 60
Exponential
Time Unit: Hours

MTTR: 8
Impeller
Failure
Redesign
Impellers
System
Risk
Last Failure: 1/1/1999 12:00:00 AM

Per Day

Is Active: Yes
Is Latent: No
PF Interval: 0
Exponential
Time Unit: Months

Value: 24
Normal
Time Unit: Hours

Value: 12
About Accessing ASO

ASO must be accessed from within the context of an Asset Strategy, System Strategy, or
Unit Strategy. You can access ASO by:
Creating a new ASO Analysis for an existing strategy.
-OR
Opening an existing ASO Analysis for an existing strategy.
Each time you access ASO, the Meridium APM system validates the strategy to
determine if it contains sufficient information to run a simulation. To run a simulation, the
Meridium APM system needs certain information from the Action and Risk records that
belong to the strategy. All of the required information is stored in fields in Action and
Risk records, but not all of the fields are displayed on the baseline Action and Risk
datasheets. Therefore, assuming that you are using the baseline datasheets, some of this
information might already exist in your Action and Risk records, and other information
can be provided only after you initiate the action of creating or opening an ASO Analysis.
Therefore, when you choose to create a new ASO Analysis or open an existing ASO
Analysis that is missing some information, the Validate Strategy window appears,
prompting you to provide the information that is missing.
For values that are missing and can be provided using the baseline Action and
Risk datasheets, you must type or select the desired values in this window or close
the window and provide the values using the datasheets. You cannot proceed with
creating or opening the ASO Analysis until the values are provided. In the
Validate Strategy window, these values are grouped together under the Error
heading.
For values that are missing but cannot be provided using the baseline Action and
Risk datasheets, you can type or select the desired values in the window or
proceed without providing any values. If you proceed without providing any
values, the Meridium APM system will assume certain default values. In the
Validate Strategy window, these values are grouped together under the Warning
heading.
If you are creating a new ASO Analysis, after you provide the missing information, the
Asset Strategy Optimization Builder will appear. You can use this builder to provide
additional information about the analysis that you are creating and specify whether or not
you want the Meridium APM system to run a simulation before displaying the analysis.
When you complete the steps in the builder, depending upon whether you chose the
Advanced option in the builder, the ASO Analysis will appear on the ASO - Asset
Strategy Optimization Summary - <Analysis Name> page or the ASO - Asset Strategy
Optimization Analysis Definition - <Analysis Name> page, where <Analysis Name> is

the name of the ASO Analysis.
A Note About Your Point of Access

An ASO Analysis can be created or opened from an Asset Strategy, System Strategy, or
Unit Strategy. Remember that in our ASO Analysis Example, the following collection of
strategies exists, where the indentation of the bullets indicates the structure of the
strategies:
Water Source Strategy (Asset Strategy)
The strategy level from which you create the ASO Analysis determines which elements
the Diagram and Scenarios contain.
If you create an ASO Analysis from the highest level, the Unit Strategy, one ASO
Analysis will exist to represent data in ALL of the strategies below it in the collection. If,
however, an ASO Analysis does not yet exist for the Unit Strategy and you create an ASO
Analysis from one of the System Strategies, one ASO Analysis will exist to represent data
in that System Strategy and any Asset Strategies that it contains. Likewise, if an ASO
Analysis does not yet exist for the Unit Strategy or its System Strategies and you create
an ASO Analysis from one of the Asset Strategies, one ASO Analysis will exist to
represent data in that Asset Strategy.
In other words, when you create an ASO Analysis, the Meridium APM system creates the
analysis from the current strategy and any strategies that it contains. After an ASO
Analysis exists for a strategy that contains other strategies, if you access ASO from a
lower-level strategy that it contains, a new ASO Analysis will not be created for that
lower-level strategy. Instead, the ASO Analysis for the higher-level strategy will be
displayed.
The System Analysis record in the ASO Analysis will always be linked to only the Asset
Strategy, System Strategy, or Unit Strategy record from which the ASO Analysis was
originally created.
Throughout this documentation, we use the phrase included in an ASO Analysis to refer
to any Unit Strategy, System Strategy, or Asset Strategy whose values are used in the
ASO Analysis simulation, regardless of which strategy was used to create the analysis.
Aspects of the Validate Strategy

Window
The Validate Strategy window appears when you choose to create a new ASO Analysis or
open an existing ASO Analysis.
The window contains a grid, where each row represents a field that is used to yield
simulation results but is missing a value. Each row represents a field in an Action record
or a Risk record.
Note: You can infer whether the field belongs to an Action or Risk record from the value
in the Object column, which comes from the Name field in the record. For example, in
the preceding image, in the first row, you can infer that the Planned Correction Duration
field belongs to the Risk record Impeller Failure because the phrase Failure suggests a
risk. There is no other visual indicator to identify the type of record to which the field in
each row belongs.
For each row, the following columns appear:
Object: Displays the name of the Action or Risk record that is missing a value.
Field: Displays the caption of the field that is missing a value.
Value: Contains an empty cell where you can type or select the desired value.
The rows are grouped by multiple levels, where:
The first (highest) level indicates one of the following conditions:
Error: Indicates that the field value is missing and can be provided using
the baseline Action and Risk datasheets. For these rows, you must type or
select the desired values in the Value cell or close the window and provide
the values using the datasheets. You cannot proceed with creating or
opening the ASO Analysis until the values are provided.
Warning: Indicates that the field value is missing but cannot be provided
using the baseline Action and Risk datasheets. For these rows, you can
type or select the desired values in the Value cell or proceed without
providing any values. If you proceed without providing any values, the
Meridium APM system will assume certain default values.
The second level always contains the text Error, even if the first level indicates a
warning condition.
The third level indicates the strategy that contains the Action or Risk record that is
missing a value. The group header contains the following text:
Path -> <Unit Strategy> -> <System Strategy> -> <Asset Strategy> -> <Strategy
Type>
...where:
<Unit Strategy> is the name of the Unit Strategy containing the Asset
Strategy with the Action or Risk record that is missing a value.
<System Strategy> is the name of the System Strategy containing the

Asset Strategy with the Action or Risk record that is missing a value.
<Asset Strategy> is the name of the Asset Strategy with the Action or Risk
record that is missing a value.
<Strategy Type> is the type of Asset Strategy: Active or Proposed.
The level of the strategy from which you access the window determines which values
appear in this path. For instance, if you access the window from a Unit Strategy, all
values appear in the path. If you access it from a System Strategy, the <Unit Strategy>
value is omitted from the path. Likewise, if you access the window from an Asset
Strategy, the <Unit Strategy> and <System Strategy> values are omitted from the path.
Consider the following example, where the window was accessed from the Unit Strategy
with the ID Water Bottling Strategy.
OK: Closes the Validate Strategy window. If you are creating a new ASO
Analysis, after you click OK, the Asset Strategy Optimization Builder appears,
where you will need to provide additional information about the ASO Analysis
that you are creating. If you are opening an existing ASO Analysis, after you click
OK, the ASO Analysis appears.
Note: The OK button is disabled until you have provided values for all fields that are
grouped under the Error heading.
Revalidate: Revalidates the information in the strategy to determine if any values

that are used to yield simulation results are missing.
Copy Details: Copies the information that appears in the window so that you can
paste it to an external file (e.g., a Microsoft Word document). If a significant
number of fields are missing values, you might want to copy the information,
paste it into an external file, and use the file as a guide for entering values in the
Action or Risk datasheets before you try to access ASO again from that strategy.
Cancel: Closes the window and disregards any values that you have entered in the
Value column.
Help: Displays the context-sensitive Help topic for the Validate Strategy window.
Deploying and configuring ASO for the first time includes completing multiple steps,
provide all the information that you need to deploy and configure ASO on top of the basic
Whether a step is required or option is indicated in the Required/Optional cell. Steps are
marked as Required if you must perform the step to take advantage of ASO functionality.
Step Task
Required/Optional
Required
Assign Security Users to ASO Security Groups via the

Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading ASO from V3.5.1 to

V3.6.0.0.0
ASO will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you upgrade the
components in the basic Meridium APM system architecture.
Upgrading ASO from V3.5.0 SP1 LP to

V3.6.0.0.0
ASO will be upgraded from V3.5.0 SP1 LP to V3.6.0.0.0 automatically when you
upgrade the components in the basic Meridium APM system architecture.

V3.6.0.0.0

V3.6.0.0.0
Configuring Security for ASO

The Meridium Asset Strategy Optimization module leverages the baseline Meridium
Asset Strategy Management Security Groups. To use ASO, a user must be a member of
one of the following Security Groups:
MI ASM Administrator
MI ASM Analyst
MI ASM Reviewer
MI ASM Viewer
About Navigating ASO Features

From ASM, you can open an existing ASO Analysis or create a new one. When you do
so:
If you are creating a new analysis (and you selected the Advanced option in the
builder) or opening an existing analysis for which the simulation has not yet been
run, the Asset Strategy Optimization Analysis Definition page will be displayed.
If you are creating a new analysis (and you selected the Run Simulation option in
the builder) or opening an existing analysis for which the simulation has been run,
the Asset Strategy Optimization Summary page will be displayed.
You can use either of these pages to perform tasks and access additional pages related to
the analysis.
Note: Each page title is prefixed with the text ASO and appended with the name of the
ASO Analysis. For example, if you are viewing the Water Bottling Strategy Optimization
analysis on the Asset Strategy Optimization Summary page, the page title will be ASO Asset Strategy Optimization Summary - Water Bottling Strategy Optimization.
Throughout the documentation, we refer to the page names without the text ASO or the
analysis name. Continuing with the example, we would refer to the ASO - Asset Strategy
Optimization Summary - Water Bottling Strategy Optimization page simply as the Asset
Strategy Optimization Summary page.

Optimization Summary Page
The Asset Strategy Optimization Summary page displays a summary of the simulation
results that currently exist for an ASO Analysis.
The Asset Strategy Optimization Summary page contains the following features:
Task menus: Displays the task menus that are common to most pages in ASO:
Tools menu, Navigation menu, and Common Tasks menu.
Asset Strategy Optimization Summary workspace: Displays the simulation results
on the following tabs:
Total Cost: Displays the Total Cost graph that exists for the ASO Analysis.
Total Cost Trend: Displays the Total Cost Trend graph that exists for the
ASO Analysis.
Risk: Displays the Risk graph that exists for the ASO Analysis.
Risk Trend: Displays the Risk Trend graph that exists for the ASO
Analysis.
Annual Action Cost: Displays the Annual Action Cost graph that exists for
the ASO Analysis.
Action Cost Trend: Displays the Action Cost Trend graph that exists for
the ASO Analysis.
Resource Occurrence: Displays the Resource Occurrence graph that exists

for the ASO Analysis.
Resource Time: Displays the Resource Time graph that exists for the ASO
Analysis.
Resource Cost: Displays the Resource Cost graph that exists for the ASO
Analysis.
You can right-click a graph to display a submenu of options that you can use to customize
the graph.
Note: If values that will affect the simulation results have been modified since the
simulation was last run, a message will be displayed at the top of the page indicating that
the simulation must be rerun. Whenever this message appears, we recommend that you
rerun the simulation to ensure that valid results are displayed.

Optimization Analysis Definition Page
The Asset Strategy Optimization Analysis Definition page contains features that allow
you to define basic properties of an ASO Analysis.
The Asset Strategy Optimization Analysis Definition page is divided into the following
areas:
Analysis Parameters section: Displays fields that you can use to define the
properties of an ASO Analysis. The content of this pane is controlled by the
default datasheet that is defined for the System Analysis family.

Optimization Analysis Definition Diagram Page
The Asset Strategy Optimization Analysis Definition - Diagram page displays the
Diagram for an ASO Analysis.
The Asset Strategy Optimization Analysis Definition - Diagram page contains the
following features:
Asset Strategy Optimization Analysis Definition - Diagram workspace: Serves as
the main display area and contains the following features:
Diagram Hierarchy pane: Provides a hierarchical view of the elements that

are included in the Diagram.
Diagram Canvas: Serves as an interactive drawing interface where you can

build a Diagram. You can drag elements from the Diagram Palette pane to
the Diagram Canvas to display the elements within the Diagram. You can
then rearrange the elements by dragging them to different locations on the
Diagram Canvas.
Diagram Palette pane: Displays the available Diagram elements that you
can drag onto the Diagram Canvas to include in the Diagram.
Properties pane: Displays the information associated either with the entire
Diagram or a selected element.

Optimization Analysis Definition - Grid
Page
The Asset Strategy Optimization Analysis Definition - Grid page displays a grid view of
the Diagram. The grid view facilitates a global view of the entire Diagram and its
properties.
Note: The Asset Strategy Optimization Analysis Definition - Grid page displays Asset,
Buffer, Distribution, Link, Risk, Subsystem, and Switch elements. Sensor elements can
be viewed only on the Asset Strategy Optimization Analysis Definition - Diagram page.
The Asset Strategy Optimization Analysis Definition - Grid page contains the following
features:
Asset Strategy Optimization Analysis Definition - Grid workspace: Serves as the
main display area and contains the following features:
Filter list: Contains a list of Diagram elements. You can select any option
in the list to view a specialized grid view of the Diagram that focuses on
the selected element and detailed information related to the selected
element. You can select any of the following elements:
Asset
Buffer
Link
Subsystem
Switch
Grid: Provides a grid view of the Diagram.

Optimization Scenarios Page
The Asset Strategy Optimization Scenarios page contains a grid and buttons that you can
use to manage the Scenarios associated with an ASO Analysis.
The grid displays the following columns of information, which display values from the
corresponding fields in System Scenario records:
Flag
Name
Description
Below the Scenarios grid, the following buttons appear:
Add Scenario: Displays the Add New Scenario dialog box, where you can create a
new System Scenario record to link to the current System Analysis record. This
link is enabled only if you are logged in as a Super User or member of the MI
ASM Analyst Security Group.
Edit Scenario: Displays a dialog box where you can modify the properties of the
System Scenario record that is currently selected in the Scenarios grid. This link
is enabled only if you are logged in as a Super User or member of the MI ASM
Analyst Security Group.
Copy Scenario: Creates a copy of the Scenario that is currently selected in the
Scenarios grid. The copy includes the System Scenario record itself and the
System Subsystem records that are linked to it. This link is enabled only if you
are logged in as a Super User or member of the MI ASM Analyst Security Group.
Delete Scenario: After asking for confirmation, deletes the Scenario that is
currently selected in the Scenarios grid. This link is enabled only if you are
logged in as a Super User or member of the MI ASM Analyst Security Group.
Set As Proposed: Sets the currently selected Scenario to the Proposed Scenario,
which causes the icon to appear in the Flag column for that Scenario. This link

Optimization Scenarios - Actions Page
The Asset Strategy Optimization Scenarios - Actions page lets you view and manage the
Actions that exist for a given Scenario in an ASO Analysis.
The Asset Strategy Optimization Scenarios - Actions page contains the following
features:
Asset Strategy Optimization Scenarios - Actions workspace: Displays the
following sections:
Scenario list: Contains the names of the System Scenario records that are
associated with the current ASO Analysis. You can select any name in the
list to view the Actions that are associated with that Scenario.
Diagram Hierarchy pane: Displays the Diagram elements that can have
Actions associated with them.
Actions pane: Displays a grid that you can use to view Actions that are
associated with the selected element in the Diagram Hierarchy pane and
buttons that you can use to perform various operations against those
Actions.
Mitigated Risks pane: Displays a grid that you can use to view Risks that
have been mitigated by the selected Action in the Actions pane and
buttons that you can use to perform various operations against those Risks.

Optimization Scenarios - Risks Page
The Asset Strategy Optimization Scenarios - Risks page lets you view and manage the
Risks that exist for a given Scenario in an ASO Analysis.
The Asset Strategy Optimization Scenarios - Risks page contains the following features:
Asset Strategy Optimization Scenarios - Risks workspace: Displays the following
sections:
list to view the Risks that are associated with that Scenario.
Diagram Hierarchy pane: Displays the Diagram elements that can have
Risks associated with them.
Risks pane: Displays a grid that you can use to view Risks that are
associated with the selected element in the Diagram Hierarchy pane and
buttons that you can use to perform various operations against those Risks.
Mitigating Actions pane: Displays a grid that you can use to view Actions
that will mitigate the Risk selected in the Risks pane and buttons that you
can use to perform various operations against those Actions.

Optimization Scenarios - Global Events
Page
The Asset Strategy Optimization Scenarios - Global Events page lets you view and
manage the Global Events that exist for a given Scenario in an ASO Analysis.
The Asset Strategy Optimization Scenarios - Global Events page contains the following
features:
Asset Strategy Optimization Scenarios - Global Events workspace: Displays the
following sections:
list to view the Global Events that are associated with that Scenario.
Global Events pane: Displays a grid that you can use to view Global
Events that are associated with the selected Scenario and buttons that you
can use to perform actions related to Global Events.
Actions to Align pane: Displays a grid that you can use to view Actions to
align with the Global Event and buttons that you can use to perform
various operations against those Actions.

Optimization Scenarios - Grid Page
The Asset Strategy Optimization Scenarios - Grid page displays an editable grid view of
the Actions, Distributions, and Risks that belong to a given Scenario. The grid view
facilitates a global view of the entire Scenario and the properties of its items. You can use
the Scenario grid view to quickly type or select values for the Actions, Distributions, and
Risks that belong to a Scenario.
If desired, you can alternatively enter values in Actions using the Asset Strategy
Optimization Scenarios - Actions page. Likewise, you can enter values in Risks
(including Distribution data) using the Asset Strategy Optimization Scenarios - Risks
page. This documentation does not assume which approach you will use. It instead
explains how to use both approaches so that you can decide which interface to use based
upon your specific workflow.
The Asset Strategy Optimization Scenarios - Grid page contains the following features:
Asset Strategy Optimization Scenarios - Grid workspace: Serves as the main
display area and contains the following features:
Scenario list: Contains a list of Scenarios that exist for the current ASO
Analysis. You can select any Scenario in the list to view an editable grid
view of the Actions, Distributions, and Risks that belong to that Scenario.
Filter list: Contains a list of types of Scenario elements. You can select any
element type in the list to view an editable grid view of the elements of
that type that belong to the Scenario that is selected in the Scenario list.
You can select any of the following element types:
Action
Distribution
Risk
Grid: Provides a grid view of the Actions, Distributions, or Risks that

belong to the Scenario that is selected in the Scenario list, based upon the
element type that is selected in the Filter list.

Optimization Simulation Results Page
The Asset Strategy Optimization Simulation Results page displays the simulation results
that currently exist for an ASO Analysis.
The Asset Strategy Optimization Simulation Results page contains the following features:
Tabbed grid: Appears at the top of the Asset Strategy Optimization Simulation
Results workspace and contains detailed simulation results on three tabs:
Elements tab: Displays detailed simulation results for the components in

the ASO Analysis.
Actions tab: Displays detailed simulation results for the Actions that are
associated with the ASO Analysis.
Resources tab: Displays detailed simulation results for the Resources that
are associated with the ASO Analysis.
Plots area: Displays graphs that display data for the Scenario that is currently
selected in the grid at the top of the workspace. As you select different cells in the
grid, the graphs will be updated to display information that is specific to that
element. The following graphs are displayed:
Histogram Plot graph: Provides a visual representation of the frequency

distribution of the result that appear in the grid.
Trend Plot graph: Provides the average value for each analysis time
interval, as defined by the value in the Time Analysis Type field in the root
System Analysis record, of the result that appears in the grid.
Impact Plot graph: Provides the average values that are combined to make
up the average value of the result that appears in the grid.
Note: If values that will affect the simulation results have been modified since the
simulation was last run, a message will be displayed at the top of the page indicating that
the simulation must be rerun. Whenever this message appears, we recommend that you
rerun the simulation to ensure that valid results are displayed.
Tools Menu
The Tools menu contains the following links:
Validate Diagrams: Evaluates the Diagram in the ASO Analysis and provides
feedback on whether or not the Diagram is valid. If the Diagram is invalid,
detailed results will be displayed on the Diagram Validation Results dialog box.
This link is enabled only if you are logged in as a Super User or member of the
MI ASM Analyst Security Group.
Run Simulation: Validates the Diagram in the ASO Analysis and, if the model is
valid, shows the progress of the simulation and then displays the results on the
Asset Strategy Optimization Summary page. If the Diagram is invalid, detailed
results will be displayed on the Diagram Validation Results dialog box and the
simulation cannot run. This link is enabled only if you are logged in as a Super
User or member of the MI ASM Analyst Security Group.
Optimize Actions: Displays the Multiple Action Interval Optimization window,

where you can run a simulation to find the optimal interval to perform Actions
that have been assigned to a Scenario.
Resources: Displays the Resources window, where you can define Resources for
the ASO Analysis.
Refresh Distributions: After prompting you for confirmation, refreshes all the
distribution data associated with the ASO Analysis by replacing the current TTF
and TTR distributions with the most recently saved TTF and TTR distributions
from the source distribution. This link is enabled only if you are logged in as a
Super User or member of the MI ASM Analyst Security Group.
Navigation Menu
The Navigation menu contains links that allow you to navigate throughout the various
views and elements of an ASO Analysis.
The Navigation menu contains the following links:
Summary: Displays the Asset Strategy Optimization Summary page.

Analysis Definition: Displays the Asset Strategy Optimization Analysis Definition
page.
Grid View: Displays the Asset Strategy Optimization Analysis Definition Grid page.
Scenario Management: Displays the Asset Strategy Optimization Scenarios page.
Diagram: Displays the Asset Strategy Optimization Analysis Definition Diagram page.
Actions: Displays the Asset Strategy Optimization Scenarios - Actions

page.
Risks: Displays the Asset Strategy Optimization Scenarios - Risks page.
Global Events: Displays the Asset Strategy Optimization Scenarios Global Events page.
Grid View: Displays the Asset Strategy Optimization Scenarios - Grid

page.
Simulation Results: Displays the Asset Strategy Optimization Simulation Results

page.
Note: As you navigate through pages that are accessible from the Navigation menu, keep
in mind that clicking the Back button will take you to the page you were on immediately
before you accessed the current ASO Analysis. For example, if you open an ASO
Analysis from an Asset Strategy, causing the Asset Strategy Optimization Summary page
to be displayed, if you then navigate to the Asset Strategy Optimization Analysis
Definition page and then click the Back button, the Asset Strategy will be displayed, not
the Asset Strategy Optimization Summary page.
Common Tasks Menu
The Common Tasks menu contains the following links:
Save Analysis: Saves all changes that you have made to the current ASO Analysis.
This link is enabled only if the following conditions are met:
The analysis contains unsaved changed.

You are logged in as a Super User or a member of the MI ASM Analyst
Security Group.
Delete Analysis: After asking for confirmation, deletes the current analysis and
then displays the Overview page for the strategy from which you created the ASO
Analysis. This link is enabled only if you are logged in as a Super User or
member of the MI ASM Analyst Security Group.
Page.
Help: Displays the context-sensitive Help topic for the current page.
About Saving an ASO Analysis

An ASO Analysis consists of multiple records that are linked together to make up the
entire analysis. As you navigate through the pages in ASO, you will add and modify
records belonging to the analysis. Rather than saving these records individually, you will
need to save the entire analysis in order to retain the changes that you have made to
individual records.
You can save an ASO Analysis by clicking the Save Analysis link on the Common Tasks
menu on any page in ASO. Clicking this link will save the root System Analysis record
and all records that are linked to it, either directly or indirectly. In other words, when you
save an ASO Analysis, the following analysis components will also be saved:
Diagram
Scenarios
Resources
Risks
Actions
Global Events
Simulation results
If you make changes to any of the elements in this list and do not save the analysis, your
changes will be discarded. You will know that the analysis contains unsaved changes if
the Save Analysis link is enabled on the Common Tasks menu. Additionally, when you
navigate away from ASO, if the analysis contains unsaved changes, you will be prompted
to save those changes.
Creating an ASO Analysis

To create an ASO Analysis, you must be logged in as a Super User or member of the MI
ASM Analyst Security Group. The following instructions assume that you have the
privileges that are required to perform the task.
To create a new ASO Analysis:
1. Open the existing Asset Strategy, System Strategy, or Unit Strategy for which you
want to create an ASO Analysis.
2. On the Tools menu, click the Optimize Strategy link.
The Validate Strategy window appears.
3. In the Value column, type or select values that are missing.
4. When you are finished providing the missing values, click the Revalidate button.
If any values are still missing, a row appears for each field that is missing a value.
6. When you are finished providing the missing values, click OK.
The Asset Strategy Optimization Builder appears, displaying the Welcome screen.

The Simulation Options screen appears.
8. If you want to run the simulation before opening the ASO Analysis, accept the
default selection Run Simulation.
-orIf you want to open the ASO Analysis without running the simulation so that you can
define additional parameters before running the simulation manually, select the Advanced
option.
If you selected the Advanced option, the ASO - Asset Strategy Optimization Analysis
Definition - <Analysis Name> page appears, where <Analysis Name> is the default name
of the ASO Analysis.
-orIf you accepted the default selection, the Run Simulation dialog box appears, indicating
the progress of the simulation.
After the progress bar reaches the end, the Go to Analysis and Discard and Close
buttons become enabled. If you do not want to view the results, you can click the Discard
and Close button to close the Run Simulation dialog box. These instructions assume
that you want to view the results.
10. Click the Go to Analysis button.
The ASO - Asset Strategy Optimization Summary - <Analysis Name> page appears,
where <Analysis Name> is the default name of the ASO Analysis.
ASO Analysis Records That Are Created

Automatically
When you create an ASO Analysis, the following items are created automatically:
One System Analysis record. The System Analysis record is linked automatically
to the Asset Strategy, System Strategy, or Unit Strategy record from which the
ASO Analysis was created.
Multiple System Scenario records:
Active Scenario: Represents the Active Strategy. Note that if you create an
ASO Analysis from a System Strategy or Unit Strategy, the Active
Scenario includes the Actions and Risks that belong to all Active
Strategies that belong to that System Strategy or Unit Strategy. If you
create an ASO Analysis from an Asset Strategy that has never been
activated (or from a System Strategy or Unit Strategy containing only
Asset Strategies that have never been activated), the Active Scenario will
still be created, but it will not contain any Actions or Risks.
Proposed Scenario: Represents the Proposed Strategy. Note that if you
create an ASO Analysis from a System Strategy or Unit Strategy, the
Proposed Scenario includes the Actions and Risks that belong to all
Proposed Strategies that belong to that System Strategy or Unit Strategy.
Multiple System SubSystem records:
Two System SubSystem records will be created to represent the one

Diagram. These System SubSystem records are identical to each other and
will always share the same values.
One additional System SubSystem record will be created to represent each

additional System Strategy that is included in the ASO Analysis. This
means that if you create an ASO Analysis from an Asset Strategy that does
not belong to a System Strategy, there will be only two System Subsystem
records that represent the Diagram.
Likewise, if you create an ASO Analysis from a System Strategy or Unit Strategy, the
Meridium APM system will evaluate the strategy collection and create System
SubSystem records from any System Strategies that it finds in the collection.
Multiple System Asset records, where each System Asset record represents an
Equipment or Functional Location record that is linked to an Asset Strategy
record that is included in the ASO Analysis. If you create an ASO Analysis from
an Asset Strategy that does not belong to a System Strategy, only one System
Asset record will be created to represent the Equipment or Functional Location
record to which that Asset Strategy record is linked. If, however, you create an
ASO Analysis from an Asset Strategy that belongs to a System Strategy
containing other Asset Strategies, multiple System Asset records will be created to
represent the Equipment or Functional Location records to which those Asset
Strategy records are linked.
Likewise, if you create an ASO Analysis from a System Strategy or Unit Strategy, the
Meridium APM system will evaluate the strategy collection and create System Asset
records from any Asset Strategies that it finds in the collection.
Note that the Meridium APM system creates two copies of each System Asset record.
One of the System Asset records is linked to the Proposed Scenario record, and the other
System Asset record is linked to the Active Scenario record.
Multiple System Risk records:
For each Risk record that belongs to an Active Strategy that is included in
the ASO Analysis, one System Risk record will be created and linked to
the Active Scenario record.
For each Risk record that belongs to a Proposed Strategy that is included
in the ASO Analysis, one System Risk record will be created and linked to
the Proposed Scenario record.
Multiple TTF Distribution records:
For each System Risk record that is included in the Active Scenario, one
TTF Distribution record will be created and linked to the System Risk
record.
For each System Risk record that is included in the Proposed Scenario,
one TTF Distribution record will be created and linked to the System Risk
record.
Multiple TTR Distribution records:
For each Action record that belongs to an Active Strategy that is included
in the ASO Analysis, one System Action record will be created and
included in the Active Scenario.
For each Action record that belongs to a Proposed Strategy that is included
in the ASO Analysis, one System Action record will be created and
included in the Proposed Scenario.
Multiple System Action Optimization records:
For each System Risk record that is included in the Proposed Scenario,
one TTR Distribution record will be created and linked to the System Risk
record.
Multiple System Action records:
For each System Risk record that is included in the Active Scenario, one
TTR Distribution record will be created and linked to the System Risk
record.
For each System Action record that is included in the Active Scenario, one
System Action Optimization record will be created and linked to the
System Action record.
For each System Action record that is included in the Proposed Scenario,
one System Action Optimization record will be created and linked to the
Multiple System Risk Assessment records:
For each System Action record that is included in the Active Scenario, one
System Risk Assessment record will be created and linked to the System
Action record.
For each System Action record that is included in the Proposed Scenario,
one System Risk Assessment record will be created and linked to the
Opening Existing ASO Analyses

After an ASO Analysis exists for a strategy, you can access it by clicking the Optimize
Strategy link on the Tools menu in ASM. When you click this link, the Meridium APM
system runs the simulation and displays the results on the ASO - Asset Strategy
Optimization Summary - <Analysis Name> page, where <Analysis Name> is the name of
the ASO Analysis.
To open an existing ASO Analysis:
1. Open the existing Asset Strategy, System Strategy, or Unit Strategy whose ASO
Analysis you want to open.
2. On the Tools menu, click the Optimize Strategy link.
If the Meridium system finds a value in all fields that are required in order to run the
simulation, the ASO - Asset Strategy Optimization Summary - <Analysis Name> page
appears, where <Analysis Name> is the name of the ASO Analysis. In this case, you can
begin working with the existing ASO Analysis.
-ORIf the Meridium system does not find a value in all fields that are required in order to run
the simulation, the Validate Strategy window appears. In this case, proceed to step 3 of
these instructions.
3. In the Value column, type or select values that are missing for each field in the
list.
4. When you are finished providing the missing values, click the Revalidate button.
If any values are still missing, a row appears for each field that is missing a value.
6. When you are finished providing the missing values, click OK.
The ASO - Asset Strategy Optimization Summary - <Analysis Name> page appears,
where <Analysis Name> is the name of the ASO Analysis.
Defining Analysis Parameters

The parameters of an ASO Analysis are defined in a System Analysis record, which is the
root record in the analysis. The values that you define for the analysis parameters will
serve as inputs to the simulation and will affect the simulation results. You can modify
the analysis parameters and rerun the simulation to see the effect that they have on the
results.
To define analysis properties, you must be logged in as a Super User or member of the
MI ASM Analyst Security Group. The following instructions assume that you have the
To define the analysis properties:
On the Asset Strategy Optimization Analysis Definition page, in the Analysis

Parameters section, specify the desired values for the available fields.
After you have defined the desired parameters, you can save your changes or run the
simulation to see the effect of the changes you made.
About Building Diagrams

A Diagram represents the physical layout and construction of pieces of equipment and
locations. A Diagram consists of a root System Subsystem record, which is linked to one
or more System Subsystem, System Sensor, System Buffer, System Link, System Asset,
and System Switch records that together make up the Diagram.
When you create an ASO Analysis, the Diagram is created automatically using the
strategy (and any strategies it contains) from which you created the analysis. Therefore,
after you have created an ASO Analysis, there is no manual step required for creating a
Diagram. You simply can build out the Diagram further by adding the necessary elements
and connections.
You can view and build a Diagram on the Asset Strategy Optimization Analysis
Definition- Diagram page.
Elements of a Diagram
The following table lists the elements that are available in a Diagram and the associated
records that are created automatically in the Meridium APM database when you add each
element to the Diagram. Click the hyperlinked element in the table to view the properties
associated with that element.
Icon
Element
Record
Description
None
Represents the starting point for all paths in the

Diagram. This element is created by default when
the Diagram is created. There is no record associated
with this element, so any data that you enter for this
element in the Properties grid will not be saved.
End
None
Represents the ending point for all paths in the

Diagram. This element is created by default when
the Diagram is created. There is no record associated
with this element, so any data that you enter for this
element in the Properties grid will not be saved.
Asset
Represents a piece of equipment or location. An

Asset element can either be imported from an Asset
System Asset
Strategy that exists within the Meridium APM
database, or it can be created from scratch.
Buffer
System Buffer
Link
System Link Connects other elements that work together to
Start
Represents an intermediate storage container

between two other elements.
produce output.
Sensor
Switch
System
Sensor
System
Switch
Detects the failure of a piece of equipment and

location and notifies Switches of the failure. A
Sensor cannot be connected to any other elements in
the Diagram. Its purpose is to monitor other
elements for failures. If an Asset element in the
Diagram fails, the Sensor that is monitoring that
element will activate designated Switches to start
elements running and deactivate other Switches to
put other elements in standby.
Represents a component that is activated or
deactivated by a Sensor when a failure occurs.
Switches allow you to connect or disconnect an
entire branch of the Diagram when failures are
detected.
Represents a collection of equipment and locations.
In the Diagram Hierarchy pane:
-and-
System
Subsystem
Subsystem
The root Subsystem, like Water Bottling

Strategy in our ASO Analysis Example, is
represented by this icon:
Other Subsystem elements, like Bottling
Strategy and Water Collection Strategy in our
ASO Analysis Example, are represented by
this icon:
After the Diagram is created automatically,

additional System Subsystem elements can be
created by importing System Strategies into the
Diagram.
Accessing the Diagram

To access the Diagram:
On the Navigation menu, under the Analysis Definition link, click the Diagram
link.
The Asset Strategy Optimization Analysis Definition - Diagram page appears.
Diagram Canvas
The Diagram Canvas on the Asset Strategy Optimization Analysis Definition - Diagram
page is the main area that you will use for building a Diagram. When the Diagram is
complete, the Diagram Canvas will contain a visual representation of equipment,
locations, and the connections between them. The Diagram is interactive and can be
modified using tools that are available on the Diagram Canvas itself, including the
following features.
Note: The tasks that you can perform in the Diagram will vary, depending on your
security privileges. Some options may be disabled based on these privileges. This
documentation assumes that you are logged in as a Super User or member of the MI ASM
Drag-and-Drop
You can click any element on the Diagram Canvas to make a green box appear around it,
then hold your mouse button down, and drag the element to the desired location.
Shortcut Menus
Diagram Canvas Shortcut Menu
You can right-click any blank area on the Diagram Canvas to see the menu shown in the
following image.
The shortcut menu contains the following options:
Import <Strategy>: Displays the Search Strategies window, which you can use to
search for a System Strategy or Asset Strategy to import into the Diagram. Note
that if you right-click the Diagram from the level that represents a Unit Strategy,
the label is Import System Strategy. Likewise, if you right-click the Diagram from
the level that represents a System Strategy, the label is Import Asset Strategy.
Zoom In: Zooms in on the Diagram by 10 percent of the current zoom level.
Zoom Out: Zooms out from the Diagram by 10 percent of the current zoom level.
Fit: Fits the entire Diagram within the space available on the Diagram Canvas.
Original: Returns the Diagram to the original zoom level, which is the zoom level
that is shown when you first access the Asset Strategy Optimization Analysis
Definition - Diagram page.
Show Overview: Opens the Overview window.
Hide Grid: Removes the grid lines from the Diagram Canvas. This option appears
on the menu only when the grid lines are displayed.
Note: When the grid lines are hidden, the Hide Grid option is replaced by the Show Grid
option. This option will display the grid lines on the Diagram Canvas.
Snap to Grid: Allows you to position elements only at intersections. In other

words, you will not be able to position elements between lines. This option
appears on the menu only when the grid lines are displayed.
Paste: Pastes the element that was last copied. This option appears on the menu
only when an element has been copied.
Element Shortcut Menu

You can also right-click any element on the Diagram Canvas to see options that are
available for that element, which are shown in the following image.
The shortcut menu contains the following options:
Refresh Distributions: Refreshes the distribution data for the selected element by
importing the most current information from the associated Asset Strategy. This
menu option appears only when you right-click an Asset element.
View Datasheet: Displays the datasheet associated with the currently selected
record. This menu option appears only when you right-click an Asset element.
View Strategy: Displays the Overview page for the strategy that was used to
create that Diagram element.
Copy (CTRL+C): Creates a copy of the selected element. This menu option does
not appear if you select an Asset element that was created from an Asset Strategy
that does not belong to a System Strategy.
Paste (CTRL+V): Pastes the element that was last copied. This menu option does
not appear if you select an Asset element that was created from an Asset Strategy
that does not belong to a System Strategy.
Delete (DELETE): Deletes the selected element from the Diagram. This menu
option does not appear if you select an Asset element that was created from an
Asset Strategy that does not belong to a System Strategy.
Note: When you select a connection, Delete is the only available option. When you select
the Start or End element, NO options will appear on the shortcut menu.
Diagram Hierarchy Pane

The Diagram Hierarchy pane on the Asset Strategy Optimization Analysis Definition Diagram page provides a hierarchical view of the elements in a Diagram.
Consider our ASO Analysis Example. In this case, the Diagram Hierarchy pane would
look like the following image.
You can click any element in the Diagram Hierarchy pane to display that element on the
Diagram Canvas. For example, if you clicked Bottling Strategy, the element that
represents the Bottling Strategy would be displayed on the Diagram Canvas as shown in
Because the Bottling Strategy element was created from a System Strategy that contains
three Asset Strategies, the Diagram Canvas displays an Asset element for each Asset
Strategy that belongs to the Bottling Strategy.
Note: The Diagram Hierarchy pane does not appear if you are viewing an ASO Analysis
that was created from an Asset Strategy that does not belong to a System Strategy.
Diagram Palette Pane
On the Asset Strategy Optimization Analysis Definition - Diagram page, the Diagram
Palette pane contains icons that represent the physical elements of the Diagram. You can
select an element from the palette and drag it onto the Diagram Canvas to define its
properties and include it in the Diagram. The following icons are available:
Asset
Buffer
Link
Switch
Sensor
Note: The Diagram Palette pane does not appear if you are viewing an ASO Analysis that
was created from an Asset Strategy that does not belong to a System Strategy.
Properties Pane
The Properties pane on the Asset Strategy Optimization Analysis Definition - Diagram
page lets you view and modify the properties of the element that is currently selected in
the Diagram. The header text of the Properties pane will indicate which element is
selected by showing <Name>'s Properties, where <Name> is the value from the Name
field of the selected element. For instance, in the following image, the value in the Name
field is Asset, so the Properties pane is titled Asset's Properties. Throughout this
documentation, we refer to this area of the screen generically as the Properties pane.
Note: The tasks that you can perform in the Properties pane will vary, depending on your
security privileges. Some options may be disabled based on these privileges. The
documentation assumes that you are logged in as a Super User or member of the MI ASM
Most of the cells in the Properties pane represent fields in the record that corresponds to
the selected element. You can click the
button to view fields in the Properties pane in
the categorized view. The categorized view displays properties in sections that can be
collapsed by clicking the minus sign (-) or expanded by clicking the plus sign (+).
You can also click the

button to view the Properties pane in the alphabetical view. The
alphabetical view displays properties in alphabetical order according to the text box label,
The Properties pane works much like a standard datasheet, where you can place your
cursor in a cell and then modify the value for the associated field. If a value already exists
in a field, it will be displayed in the appropriate cell. At the bottom of the Properties pane,
any help text defined for the selected field will be displayed. For example, in the
preceding image, the help text defined for the Description field is Description of the
currently selected element.
Displaying an Overview of the Diagram
If the Diagram you are currently viewing exceeds the size of the Diagram Canvas on the
Asset Strategy Optimization Analysis Definition - Diagram page, you can use the
overview feature to display a more compact view of the Diagram.
To display an overview of a Diagram:
1. Right-click any blank space on the Diagram Canvas.
2. Click Show Overview.
The Overview window appears, displaying a blue locator box that highlights the section
of the Diagram that is currently shown on the Diagram Canvas.
You can click another location within the Overview window to move the locator box to
that location. As you do so, the view on the Diagram Canvas will change to reflect your
location within the Diagram on the Overview window.
Hiding and Displaying Panes

If you are working with a large Diagram, you may want to increase the display area of the
Diagram Canvas. You can do so by hiding the Diagram Hierarchy, Diagram Palette, and
Properties panes.
To hide a pane:
In the upper, right corner of the pane header, click the button.
The pane closes and is identified by a tab that appears in the pane's original position. For
example, the following image shows the Diagram Hierarchy pane after it has been
hidden. Note the Diagram Hierarchy tab that appears on the left side of the screen.
To display a hidden pane:
Point to the tab that identifies the pane you want to display.
The pane reappears. If you move your pointer off the pane, the pane will disappear again.
You can lock the pane back into the display position by clicking the button again.
About Adding Elements
When an ASO Analysis is created, the Diagram is built by default from the Unit Strategy,
System Strategies, and Asset Strategies that are included in the analysis. If desired, you
can build the Diagram further by adding elements and connections. You have two options
for adding elements to the Diagram:
You can create new elements from scratch by using the Diagram Palette pane.
When you add an element in this way, the Meridium APM system will create a
new record to store information for that element. The new record will be linked to
the System Subsystem record that represents the Diagram.
You can create new elements by importing records that already exist in the
Meridium APM database. When you add an element in this way, the Meridium
APM system will use the information in the existing record to populate
information in a new record to represent the appropriate Diagram element. The
original record will continue to exist in the Meridium APM database. The new
record will be linked to the System Subsystem that represents the Diagram.
After you add elements to the Diagram, you can create connections between them to
indicate their relationship to one another and their physical arrangement.
Adding Elements from the Diagram

Palette Pane
To add an element to the Diagram, you must be logged in as a Super User or member of
the MI ASM Analyst Security Group. The following instructions assume that you have
the privileges that are required to perform the task.
To add a new element to the Diagram from the Diagram Palette pane:
1. Click the desired element in the Diagram Palette pane.
2. Hold your mouse button down, drag the element to the Diagram Canvas, and then
release your mouse button to drop it in the desired location.
The element appears on the Diagram Canvas. It is selected automatically, so the
Properties pane displays the properties of the new element. When you save the ASO
Analysis, the appropriate record will be created in the Meridium APM database to store
information for that element.
About Importing Elements into the

Diagram
In an ASO Analysis, you can import the following elements into the Diagram:
System Strategy: If the Diagram contains at least one SubSystem element that was
created from a System Strategy, you can import another System Strategy into the
Diagram. The option to import a System Strategy is available only when the
Diagram Canvas currently displays a SubSystem element. Consider the following
image from our ASO Analysis Example, where the Diagram Canvas displays the
elements that were created from the System Strategies Bottling Strategy and
Water Collection Strategy.
In this example, if you right-clicked the Diagram Canvas, the Import System Strategy
option would appear on the shortcut menu.
When you import a System Strategy into the Diagram, the System Strategy is added to
the Unit Strategy containing the System Strategy(s) that are represented by the currently
displayed SubSystem element(s). This means that if you were to open the Unit Strategy
in ASM, you would see the imported System Strategy in the list of System Strategies that
it contains.
Note that when a System Strategy is imported, two copies of the same System Subsystem
record are created, where each System SubSystem record represents the System Strategy
record of the imported System Strategy. Note that one of the System SubSystem records
is linked to the Proposed Scenario record, and the other System SubSystem record is
linked to the Active Scenario record.
Asset Strategy: Asset Strategies can be imported into any Diagram. The option to
import an Asset Strategy is available, however, only when the Diagram Canvas
currently displays an Asset element(s). Consider the following image from our
ASO Analysis Example, where the Diagram Canvas displays the Asset elements
that were created from the Asset Strategies Labeling Machine Strategy, Filling
Machine Strategy, and Capping Machine Strategy.
In this example, if you right-clicked the Diagram Canvas, the Import Asset Strategy
option would appear on the shortcut menu.
When you import an Asset Strategy into the Diagram, the Asset Strategy is added to the
System Strategy containing the Asset Strategy(s) that are represented by the currently
displayed Asset element(s). This means that if you were to open the System Strategy in
ASM, you would see the imported Asset Strategy in the list of Asset Strategies that it
contains.
Note that when an Asset Strategy is imported, two copies of the same System Asset
record are created, where each System Asset record represents the Equipment or
Functional Location record that is linked to the Asset Strategy record of the imported
Asset Strategy. One of the System Asset records is linked to the Proposed Scenario
record, and the other System Asset record is linked to the Active Scenario record.
When you import a System Strategy or Asset Strategy into the Diagram, the Meridium
APM system validates the Asset Strategies to make sure they contain the necessary data
to run a simulation. The Validate Strategy window appears, indicating which fields, if
any, are missing values. You will need to provide the missing information before you can
proceed with importing the strategy.
Importing System Strategies into the

Diagram
To import a System Strategy into the Diagram, you must be logged in as a Super User or
member of the MI ASM Analyst Security Group. The following instructions assume that
you have the privileges that are required to perform the task.
To import a System Strategy into the Diagram:
1. Make sure that the Diagram Canvas currently displays a SubSystem element.
2. Right-click the Diagram Canvas, and click Import System Strategy.
The Search Strategies window appears.
The Search Strategies window contains a grid, where each row represents a System
Strategy that is available for import.
Note: System Strategies that already belong to a Unit Strategy are not displayed in the
grid.
3. In the grid, select the row containing the System Strategy that you want to import
into the Diagram.
4. Click OK.
The Validate Strategy window appears, displaying a row for each field in an underlying
Asset Strategy that is missing a value.
Note: If no fields are missing values, the window is blank.
5. If any fields are missing values, type or select the desired values.
6. Click OK.
The selected System Strategy is added to the Diagram and the Diagram Hierarchy pane as
Subsystem elements. When you save the ASO Analysis, the appropriate records will be
created in the Meridium APM database to store information for the new elements.
Importing Asset Strategies into the

Diagram
To import an Asset Strategy into the Diagram, you must be logged in as a Super User or
To import an Asset Strategy into the Diagram:
1. Make sure that the Diagram Canvas currently displays an Asset element.
2. Right-click the Diagram Canvas, and click Import Asset Strategy.
The Search Strategies window appears.
The Search Strategies window contains a grid, where each row represents an Asset
Strategy that is available for import.
Note: Asset Strategies that already belong to a System Strategy are not displayed in the
grid.
3. In the grid, select the rows containing the Asset Strategies that you want to import
into the Diagram.
4. Click OK.
The Validate Strategy window appears, displaying a row for each field in a selected Asset
Strategy that is missing a value.
Note: If no fields are missing values, the window is blank.
5. If any fields are missing values, type or select the desired values.
6. Click OK.
The Asset Strategies are added to the Diagram and the Diagram Hierarchy pane as Asset
elements. When you save the ASO Analysis, the appropriate records will be created in the
Meridium APM database to store information for the new elements.
Connecting Elements in the Diagram

To connect Elements in the Diagram, you must be logged in as a Super User or member
of the MI ASM Analyst Security Group. The following instructions assume that you have
To connect two elements in the Diagram:
1. For the desired element, point to the black circle on the side from which you want
to start the connection.
2. Click the port and drag the pointer in the direction that you want to create the
connection.
An arrow will be drawn automatically in the direction that you drag your mouse.
3. Continue dragging your mouse until the arrow reaches the desired destination
(i.e., the circle on the element that will serve as the end of the connection). The
connection will be completed automatically.
4. Release your mouse button to set the connection.
Deleting Elements from the Diagram

If desired, you can delete any element from the Diagram. You cannot, however, delete the
Start or the End node. To delete an Element from the Diagram, you must be logged in as
a Super User or member of the MI ASM Analyst Security Group. The following
instructions assume that you have the privileges that are required to perform the task.
To delete an element from the Diagram:
1. Right-click the element that you want to delete, and then click Delete.
-orSelect the element that you want to delete, and press the Delete key on your keyboard.
A confirmation message appears, asking if you really want to delete the element.
The element is deleted from the Diagram.
Deleting Connections Between Elements

To delete a connection between Elements in the Diagram, you must be logged in as a
Super User or member of the MI ASM Analyst Security Group. The following
instructions assume that you have the privileges that are required to perform the task.
To delete a connection between two elements in the Diagram:

1. Click the connector to select it.
Note: This image shows the Canvas Diagram with Hide Grid option selected.
2. Right-click the connection, and then click Delete.
-ORPress the Delete key on your keyboard.
A confirmation message appears, asking if you really want to delete the connection.
The connection is deleted from the Diagram.
Performing Validation
For the Meridium APM system to run simulations, the elements within the Diagram must
be connected correctly. Isolated elements, broken connections, and circular connections
will cause a Diagram to fail validation. When you perform a validation, the Meridium
APM system will validate the Diagram in the ASO Analysis.
The validation process evaluates the Diagram in both directions:
From the Start element to the End element.
From the End element to the Start element.
If an error is found along either path, it will be reported in the validation results. An error
that is found along both paths will be reported twice.
To validate the Diagram:
While viewing an ASO Analysis on any page, on the Tools menu, click the
Validate Diagrams link.
If the Diagram is valid, the Diagram Validation Results dialog box will
display a message stating that the Diagram is valid.
1.
If the Diagram is invalid, the Diagram Validation Results dialog box will
be displayed, where you can view the results of the validation.
About the Diagram Validation Results

Dialog Box
The Diagram Validation Results dialog box displays all the errors that exist in the
Diagram in an ASO Analysis.
The Diagram Validation Results dialog box displays the Error grid, which displays error
information, organized first by Scenario and then by error type.
Below the Error grid, the following buttons appear:
OK: Closes the Diagram Validation Results dialog box.

Copy Details: Copies the content of the Error grid so that you can paste the error
information into another application or file, such as a Microsoft Word or
Microsoft Excel document. You can use this method to view the Diagram Canvas
and error information simultaneously while you correct the errors.
Help: Displays the context-sensitive Help topic for the Diagram Validation
Results dialog box.
Interpreting Diagram Validation Results

If you validate an ASO Analysis Diagram and the Meridium APM system indicates that it
is invalid, the Diagram Validation Results dialog box will be displayed, where you can
view the results of the validation.
The Diagram Validation Results dialog box can display any of the following error
messages, depending upon the conditions that are found within the Diagram:
Not Reach End Error: The End element cannot be reached from the Start element
by following connections in the Diagram. The Diagram must be connected such
that a path exists from the Start element to the End element. If this path does not
exist, the simulation will not run. You must correct this error before you can run
the simulation.
The following images show a broken connection error and the corresponding error
message in the Diagram Validation Results dialog box.
Note: This broken connection did not produce a Not Reach Start error because there is a
complete connection from the End element to the Start element.
Not Reach Start Error: The Start element cannot be reached from the End element
by following connections in the Diagram. The Diagram must be connected such
that a path exists from the End element to the Start element. If this path does not
exist, the simulation will not run. You must correct this error before you can run
the simulation.
The following images show a broken connection error and the corresponding error
Note: This broken connection produced both a Not Reach End error and a Not Reach
Start error because there is not a complete connection anywhere in the Diagram.
Isolated Element(s) Error: An element is not connected to any other element on

the Diagram Canvas. This type of error will not prevent the simulation from
running, but the isolated element will be ignored by the simulation.
The following images show an isolated element error and the corresponding error
Circular Error: An element in the series has a connection to an earlier element in

the series. This will prevent the Simulation from running and you must repair the
connection so that it starts at the Start element and ends at the End element.
The following images show a circular error and its error message in the Diagram
Validation Results dialog box.
Workflow for Developing a Scenario

To develop a Scenario, you must complete the following steps:
1. Create a System Scenario record.
2. Add Risks, Actions, and Global Events to the Scenario, as desired.
Types of Scenarios
Each ASO Analysis will contain the following Scenarios:
Active Scenario: Represents the current strategy for the equipment and locations
that appear on the Diagram. When you create an ASO Analysis, the Active
Scenario is created automatically. You cannot set another Scenario as the Active
Scenario or delete the Active Scenario. Each analysis can contain only one Active
Scenario. The Active Scenario always reflects data in the Active Strategies that
are included in the ASO Analysis. In the Active Scenario, you cannot:
Create or delete Risks.
Create or delete Actions.
Modify the association between Actions and Risks.
Create new associations between Actions and Risks.
You can, however, define Resources, Global Events, and TTF and TTR Distributions.
In the grid on the Asset Strategy Optimization Scenarios page, the row representing the
Active Scenario contains the icon. By default, the Active Scenario is represented by the
System Scenario record with the value Active in the Name field. If desired, you can
change the value in the Name field.
Proposed Scenario: Represents a proposed strategy for the equipment and

locations that appear on the Diagram. When you create an ASO Analysis, the
Proposed Scenario is created automatically. You can keep the default Proposed
Scenario, or you can set another customer-defined Scenario as the Proposed
Scenario. When you do so, the values in that customer-defined Scenario will be
transferred to the Proposed Strategies that are included in the ASO Analysis. Each
ASO Analysis must contain a Proposed Scenario at all times, and each analysis
can contain only one Proposed Scenario. The Proposed Scenario always reflects
data in the Proposed Strategies that are included in the ASO Analysis. In the
Proposed Scenario, you can:
Define Resources, Global Events, and TTF and TTR Distributions.
In the grid on the Asset Strategy Optimization Scenarios page, the row representing the
Proposed Scenario contains the icon. By default, the Proposed Scenario is represented
by the System Scenario record with the value Proposed in the Name field. If desired, you
can change the value in the Name field.
Unmitigated Scenario: Represents the unmitigated strategy, or the strategy as it

exists with only Risks and no Actions, for the equipment and locations that are
represented on the Diagram. The simulation results will include results for the
Unmitigated Scenario, but you cannot modify the Unmitigated Scenario in ASO.
Each ASO Analysis contains only one Unmitigated Scenario. Because there is no System
Scenario record to represent the Unmitigated Scenario, the Unmitigated Scenario does
not appear in the grid on the Asset Strategy Optimization Scenarios page.
Customer-defined Scenario: Represents a suggested strategy for the equipment

and locations that appear on the Diagram. Customer-defined Scenarios do not
reflect data in ASM. In a customer-defined Scenario, you can:
Define Resources, Global Events, and TTF and TTR Distributions.
Each ASO Analysis can contain multiple customer-defined Scenarios. Each customerdefined Scenario is represented by a System Scenario record without an icon. If desired,
you can set a customer-defined Scenario as the Proposed Scenario. When you do so, the
values in that customer-defined Scenario will be transferred to the Proposed Strategies
that are included in the ASO Analysis.
Creating System Scenario Records

Creating a System Scenario record is the first step in the process of developing a
Scenario. To create a System Scenario record, you must be logged in as a Super User or
member of the MI ASM Analyst Security Group
Note: When you create a new ASO Analysis, two System Scenario records will be created
automatically and identified by the values Active and Proposed in the Name field. You
can modify either Scenario, or you can copy the Proposed Scenario to create a new
Scenario, which you can then set as the Proposed Scenario. Each ASO Analysis must
contain at least one Active Scenario and one Proposed Scenario.
To create a new System Scenario record:
1. Access the Asset Strategy Optimization Scenarios page for the ASO Analysis for
which you want to create a new Scenario.
2. In the Scenarios section, below the grid, click the Add Scenario button.
The Add New Scenario dialog box appears.
The content of the Add New Scenario dialog box is controlled by the default datasheet
defined for the System Scenario family.
3. Define the properties of the System Scenario record as desired.
4. Click OK.
The System Scenario record is created, and the Asset Strategy Optimization Scenarios Actions page appears so that you can begin adding Actions to the Scenario. Note that any
Actions or Risks that exist in the Active Scenario are flagged as deleted by default so that
you can see how the new Scenario differs from the Active Scenario.
Creating Copies of System Scenario

Records
To create a copy of a System Scenario record, you must be logged in as a Super User or
To copy a Scenario:
1. Access the Asset Strategy Optimization Scenarios page for the ASO Analysis
containing a Scenario that you want to copy.
2. In the grid within the Scenarios section, select the row containing the System
Scenario record that you want to copy.
3. Below the grid, click the Copy Scenario button.
The Scenario is copied and appears in the grid in the Scenarios section with the value
Copy of <Scenario Name> in the Name column, where <Scenario Name> is the name of
the System Scenario record that you copied.
Modifying System Scenario Records

To modify a System Scenario record, you must be logged in as a Super User or member
of the ASM Analyst Security Group. The following instructions assume that you have the
To modify a System Scenario record:
containing a Scenario that you want to modify.
2. In the grid within the Scenarios section, select the row containing the System
Scenario record that you want to modify.
3. Click the Edit Scenario button.
The <Scenario Name> dialog box appears, where <Scenario Name> is the value in the
Name field of the System Scenario record that you selected. The content of this dialog
box is controlled by the default datasheet defined for the System Scenario family.
4. Modify the properties of the System Scenario record as desired.

5. Click OK.
Your changes are applied.
Deleting System Scenario Records

To delete a Scenario, you must be logged in as a Super User or member of the MI ASM
Analyst Security Group. The following instructions assume that you have the privileges
that are required to perform the task.
To delete a Scenario from an ASO Analysis:
containing a Scenario that you want to delete.
2. In the grid within the Scenarios section, select the row containing the scenario that
you want to delete.
3. Below the grid, click the Delete Scenario button.
A confirmation message appears, asking if you really want to delete the Scenario.
The Scenario is removed from the grid in the Scenarios section.
About Risks
In ASO, a Risk identifies one way in which a piece of equipment or location can fail. If
the risk occurs, then the piece of equipment or location will fail. In ASO Analyses, Risks
are represented by System Risk records, which are linked to System Asset and System
Switch records. When you create an ASO Analysis from a strategy, each Risk record in
ASM is used to create a System Risk record in ASO. In addition, the System Risk record
is linked automatically to the System Asset record that is created automatically from the
Equipment or Functional Location record to which the Asset Strategy is linked.
A piece of equipment or location may have multiple Risks to represent multiple ways in
which it can fail. As such, System Asset and System Switch records can be linked to
multiple System Risk records.
Each risk has a characteristic pattern of causing a piece of equipment or location to fail as
defined by its TTF distribution data or maximum operating time. Risks also have TTR
distribution data, which characterizes the time required to correct the failure that occurs
as the result of the Risk and get the system running again. This distribution data is stored
in Distribution records, which are linked to Risk records.

The Diagram Hierarchy pane on the Asset Strategy Optimization Scenarios - Risks page
displays the elements that you have defined on the Asset Strategy Optimization Analysis
Definition - Diagram page. In the following image, the Diagram Hierarchy pane is
outlined in red.
When you select an element in the Diagram Hierarchy pane, the associated Risks for that
element are displayed in the Risks pane. For example, in this image, the selected
G0006A-071 Asset element has six associated Risks:
Impeller Wear
Lubricant Loss
Lubricant Degradation
Misalignment
Seal Leak
Bearing Failure
Risks Pane
The Risks pane is displayed on the Asset Strategy Optimization Scenarios - Risks page
and on the Risks Editor window. It displays the Risks that are associated with the element
that is selected in the Diagram Hierarchy pane. In the following image, the Risks pane is
outlined in red.
Note: For the purposes of this image, the Diagram Hierarchy pane has been hidden.
The grid in the Risks pane displays the following columns of information:
Flag: Contains an icon indicating the status of the System Risk record relative to
the corresponding System Risk record that belongs to the Active Scenario.
If you are viewing System Risk records that belongs to the Active
Scenario (i.e., the Scenario list above the grid contains the value Active),
the Flag column will not contain an icon.
If you are viewing System Risk records that belongs to a non-Active

Scenario (i.e., the Scenario list above the grid does not contain the value
Active) and the System Risk record is identical to the corresponding
System Risk record in the Active Scenario, the Flag column will not
contain an icon.

Active) and the System Risk record does not have a corresponding System
Risk record in the Active Scenario, the Flag column will contain the
icon.

Active) and the System Risk record is different from the corresponding
System Risk record in the Active Scenario, the Flag column will contain
the icon.

Active) whose System Scenario record was created from scratch (i.e., the
System Scenario was not copied from another System Scenario record),
the Flag column will contain the
icon.
Name: Displays the value in the Name field in the System Risk record.
Description: Displays the value in the Description field in the System Risk record.
TTF: Displays the TTF Distribution link. You can click this link to open the TTF
Distribution window, where you can view the Time to Failure (TTF) distribution
data for the associated System Risk record.
TTR: Displays the TTR Distribution link. You can click this link to open the TTR
Distribution window, where you can view the Time to Repair (TTR) distribution
data for the associated System Risk record.
Planned Resource Usages: Displays the Planned Resource Usages link, which you
can click to open the Planned Resource Usages window and view any planned
Resources that have been assigned to the Risk.
Unplanned Resource Usages: Displays the Unplanned Resource Usages link,

which you can click to open the Unplanned Resource Usages window and view
any unplanned Resources that have been assigned to the Risk.
Qualitative Consequence: Displays a hyperlinked numeric value, which you can

click to open the Qualitative Consequence Editor window.
Risks to Reset: Displays a number representing the number of additional Risks

that will be reset following a planned or unplanned correction of the Risk in that
row. This number appears as a hyperlink, which you can click to access the Risks
to Reset dialog box, where you can manage the additional Risks that will be reset
in the simulation following a planned or unplanned correction of the source Risk.
When you right-click any cell in the grid in the Risks pane, a shortcut menu appears and
contains options that you can use to manage the Risks that you want to reset following a
planned or unplanned correction of the Risk in that row.
Below the grid in the Risks pane, the following buttons appear:
Add Risk: Displays the Add New Risk window, where you create a new System
Risk record to link to the currently selected System Asset or System Switch
record. This link is enabled only if you are logged in as a Super User or member
of the MI ASM Analyst Security Group.
Associate Distribution: Displays the Find Items window, where you can search for
a Reliability Distribution or Reliability Growth Analysis to associate with the
selected Risk. This link is enabled only if you are logged in as a Super User or
Open Analysis: Displays the Reliability Distribution Summary page or the

Reliability Growth Analysis page for the Reliability Distribution Analysis or
Reliability Growth Analysis that is associated with the selected Risk. This button
is enabled only when the selected Risk is associated with a Reliability
Distribution Analysis or a Reliability Growth Analysis.
Refresh Distribution: Refreshes the associated distributions by importing the TTF

and TTR distribution information with the most current information from the
associated Reliability Distribution Analysis or Reliability Growth Analysis. This
link is enabled only when the selected Risk is associated with a Reliability
Distribution Analysis or a Reliability Growth Analysis. This link is enabled only
if you are logged in as a Super User or member of the MI ASM Analyst Security
Group.
Delete Risk: After asking for confirmation, deletes the System Risk record that is
currently selected in the Risks pane. This button is always disabled if you are
viewing Risks that belong to the Active Scenario. This link is enabled only if you
are logged in as a Super User or member of the MI ASM Analyst Security Group.
Undo Risk: Causes the System Risk record to be updated so that its values are
identical to the values in the corresponding System Risk record in the Active
Scenario. Before you click the Undo Risk button, you might want to click the
Show Changes button so that you can see how the System Risk record in this
Scenario differs from the one in the Active Scenario. This button is always
disabled if you are viewing Risks that belong to the Active Scenario. If you are
viewing Risks that belong to any other Scenario, this button is enabled only if an
Asset element is selected in the Diagram Hierarchy pane and the selected Risk is
somehow different from the corresponding Risk in the Active Scenario. This link
Show Changes: Displays the Changes for <Risk> window, where <Risk> is the
value in the Name field in the selected System Risk record. You can use this
window to see the differences that exist between values in this System Risk record
and values in the corresponding System Risk record in the Active Scenario. This
button is always disabled if you are viewing Risks that belong to the Active
Scenario. If you are viewing Risks that belong to any other Scenario, this button is
enabled only if an Asset element is selected in the Diagram Hierarchy pane and
the Risk is somehow different from the corresponding Risk in the Active
Scenario.
Mitigating Actions Pane

The Mitigating Actions pane is displayed on the Asset Strategy Optimization Scenarios Risks page and on the Risks Editor window. It displays the Actions that are associated
with the Risk that is selected in the Risks pane. In the following image, the Mitigating
Actions pane is outlined in red.
When you select a Risk in the Risks pane, the associated Actions for that Risk are
displayed in the Mitigating Actions pane. For example, in this image, the Seal Leak Risk
has two associated Actions: Operator Check and Internal Inspection.
The grid in the Mitigating Actions pane displays the following columns of information:
Flag: Contains an icon indicating the status of the System Action record relative
to the corresponding System Action record that belongs to the Active Scenario.
If you are viewing System Action records that belongs to the Active
If you are viewing System Action records that belongs to a non-Active

Active) and the System Action record is identical to the corresponding
System Action record in the Active Scenario, the Flag column will not
contain an icon.

Active) and the System Action record does not have a corresponding
System Action record in the Active Scenario, the Flag column will contain
the icon.

Active) and the System Action record is different from the corresponding
the icon.

the Flag column will contain the icon.
Name: Displays the value in the Name field in the System Action record.
Description: Displays the value in the Description field in the System Action
record.
Resource Usages: Displays the Resources Usages link, which you can click to
open the Resource Usages window to manage the Resources that have been
assigned to the Action.
Below the grid in the Actions pane, the following buttons appear:
Assign New Action: Displays the Select Action Type dialog box, where you can
create a new System Action record to link to the currently selected System Asset
or System Switch record. When you create a new Action by using the Assign New
Action button, the Action will be assigned to mitigate the Risk currently selected
in the Risks pane. This link is enabled only if you are logged in as a Super User or
assign an existing Action to mitigate the Risk currently selected in the Risks pane
or remove an existing Action from mitigating the Risk currently selected in the
Risks pane. This link is enabled only if you are logged in as a Super User or
Creating Risks on the Risks Page

To create a Risk, you must be logged in as a Super User or member of the MI ASM
Note: You can add Risks only to non-Active Scenarios.
The following instructions provide details on creating Risk records and simultaneously
assigning them to Actions via the Asset Strategy Optimization Scenarios - Risks page.
You can also create Risk records and simultaneously assign them to Actions using the
Asset Strategy Optimization Scenarios - Actions page.
To add a Risk to an Asset or Switch element in a Scenario:
1. While viewing the desired non-Active Scenario on the Asset Strategy

Optimization Scenarios - Risks page, in the Diagram Hierarchy pane, select the
element to which you want to add a Risk.
2. Below the grid in the Risks pane, click the Add Risk button.
The Add New Risk window appears, displaying the default datasheet for the System Risk
family.
3. In the fields in the Add New Risk window, define the properties of the System
Risk record as desired.
4. Click OK.
The new Risk appears in the Risks grid with the
icon in the Flag column.
Creating Risks on the Actions Page

To assign a new Risk to an Action, you must be logged in as a Super User or member of
Note: You can create new Risks and assign them to Actions only in non-Active Scenarios.
The following instructions provide details on creating a Risk record and simultaneously
assigning it to an Action using the Asset Strategy Optimization Scenarios - Actions page.
You can also create Risk records and simultaneously assign them to Actions using the
Asset Strategy Optimization Scenarios - Risks page.
To assign a new Risk to an Action:
Optimization Scenarios - Actions page, in the Diagram Hierarchy pane, select the
element that contains the Action to which you want to assign a Risk.
2. In the grid in the Actions pane, select the Action to which you want to assign a
Risk.
3. Below the grid in the Mitigated Risks pane, click the Assign New Risk button.
The New Risk window appears, displaying the default datasheet for the System Risk
family.
4. In the fields on the New Risk window, define the properties of the System Risk
record as desired.
5. Click OK.
The new Risk is created, linked to the selected element, and assigned to the Action, and it
appears in the grid in the Mitigated Risks pane.
Assigning Existing Risks to Actions
To assign existing Risks to an Action, you must be logged in as a Super User or member
Note: You can assign existing Risks to Actions only for Scenarios in a state other than
Active.
To assign existing Risks to an Action:
1. While viewing the desired Scenario on the Asset Strategy Optimization Scenarios
- Actions page, select the Action to which you want to assign a Risk.
2. In the grid in the Actions pane, select the Action to which you want to assign a
Risk.
3. Below the grid in the Mitigated Risks pane, click the Assign Existing Risks
button.
The Assign Risk window appears, which shows the Risks that exist in the Scenario to
which the Action belongs.
4. In the Assign Risks window, in the Is Selected column of the grid, select the
check box for the Risk(s) that you want to assign to the Action.
Hint: You can clear the Is Selected check box to remove from the Action any Risk that is
currently assigned.
5. Click OK.
The Risk(s) are assigned to the selected Action in the Actions pane and appear in the grid
in the Mitigated Risks pane.
Options for Modifying Risks

You can modify the values in a System Risk record using either of the following options:
Asset Strategy Optimization Scenarios - Risks page.

Asset Strategy Optimization Scenarios - Grid page.
Modifying Risks Using the Risks Page

To modify a Risk, you must be logged in as a Super User or member of the MI ASM
To modify a Risk using the Asset Strategy Optimization Scenarios - Risks page:
- Risks page, in the Diagram Hierarchy pane, select the row that contains the Risk
that you want to modify.
2. In the Risks pane, in the Name column, click the hyperlinked name of the Risk
that you want to modify.
The <Risk Name> dialog box appears, where <Risk Name> is the name of the System
Risk record that you selected.
3. Modify the properties of the System Risk record as desired.
4. Click OK.
Your changes are saved.
Modifying Risks Using the Grid Page

To modify a Risk, you must be logged in as a Super User or member of the MI ASM
To modify a Risk using the Asset Strategy Optimization Scenarios - Grid page:
- Grid page, in the Filter list, select Risk.
The grid is updated to display only the Risks that belong to that Scenario.
2. In the grid, in any cell containing a value that you want to modify, delete the
current value, and type or select the desired value.
3. On the Common Tasks menu, click the Save Analysis link.
About Resources for Risks

After Resources exist for an ASO Analysis, you can assign them to Risks. When you do
so, you associate the cost of that Resource with each failure that occurs as a result of that
Risk. This allows you to assign a realistic, financial cost to the consequences of the Risk
that can be included in the simulation results.
When you assign a Resource to a Risk, a System Resource Usage record will be created
and will store information that specifies how the Resource will be used (e.g., the quantity
and duration). There are two ways to assign Resources to Risks:
Planned Resource Usage: Used for a planned correction, or when a potential

failure is detected by a condition-based maintenance Action and triggers repairs
that mitigate the failure before it can occur. This is a proactive approach that
keeps the piece of equipment or location running.
Unplanned Resource Usage: Used for an unplanned correction, or repairs for a
piece of equipment or location that has failed unexpectedly due to a Risk. This is
a reactive approach with focuses on getting the piece of equipment or location
running again after it has failed.
Assigning Resources to Risks

To assign a Resource to a Risk, you must be logged in as a Super User or member of the
To assign a Resource to a Risk:
- Risks page, in the Diagram Hierarchy pane, select the element that contains the
Risk to which you want to assign a Resource.
2. In the grid in the Risks pane, in the row containing the Risk to which you want to
assign a Resource, click the Planned Resource Usages link.
-ORIn the grid in the Risks pane, in the row containing the Risk to which you want to assign a
Resource, click the Unplanned Resource Usages link.
The <Resource Usages> - <Risk> window appears, where <Resource Usages> is the type
of Resource Usage that you selected and <Risk> is the name of the Risk that you
selected.
In this image, the Planned Resource Usages - Bearing Failure window displays the
Resources that are assigned to the current Risk.
3. Click the Add Existing button. This button will be enabled only if one or more
Resources already exist for the analysis.
A new row appears in the grid.
Hint: Alternatively, you can click the Add New button to create a Resource from scratch
and assign it to a Risk. After you have created the Resource, you can skip to step 5.
4. In the Resource cell of the first row, click the
button, and select the Resource
that you want to assign to the Risk.
5. Type the desired values in the Quantity, Duration, and Duration Units cells. These
values will be used to populate the corresponding fields in the System Resource
Usage record.
Note: The Total Fixed Cost and Total Variable Cost columns display the actual value that
will be incurred when the System Resource Usage is added to the Simulation Results.
Since this value is a product of the values you enter on the Resource dialog box and
Resource Usage window, the cells are disabled and you cannot type values in these cells.
6. Click the Close button.
The <Resource Usages> - <Risk> window closes and your selections are applied.
Modifying Resources Assigned To Risks

When you modify a Resource that is assigned to a Risk, you modify the System Resource
Usage record. The actual System Resource record is not changed.
To modify a Resource, you must be logged in as a Super User or member of the MI ASM
To modify a Resource that is assigned to a Risk:
- Risks page, in the Diagram Hierarchy pane, select the element whose Risk has
Resources that you want to modify.
2. In the grid in the Risks pane, in the row containing the Risk whose Resources you
want to modify, click the Planned Resource Usages link.
-ORIn the grid in the Risks pane, in the row containing the Risk whose Resources you want to
modify, click the Unplanned Resource Usages link.
selected.
3. In the Resource Usages grid, modify the properties of the Resource Usage record
as desired.
Removing Resources from Risks

When you remove a Resource from a Risk, you delete the System Resource Usage record
so that the Resource is no longer used by the selected Risk. The actual System Resource
record is still available for the ASO Analysis and can be used if needed.
To remove a Resource from a Risk, you must be logged in as a Super User or member of
To remove a Resource from a Risk:
- Risks page, in the Diagram Hierarchy pane, select the Risk whose Resource you
want to remove.
2. In the grid in the Risks pane, in the row containing the Risk whose Resources you
want to remove, click the Planned Resource Usages link.
-ORIn the grid in the Risks pane, in the row containing the Risk whose Resources you want to
remove, click the Unplanned Resource Usages link.
selected.
3. In the Resource Usages grid, select the Resource that you want to remove.
4. Click the Delete button.
A confirmation message appears, asking if you really want to delete the selected item(s).
The Resource Usage is removed from the Risk.
About Defining Distribution Data for

Risks
You have two options for defining distribution data for Risks. You can:
Enter distribution data manually.

Associate distribution data from existing Reliability Distribution Analyses and
Reliability Growth Analyses.
Options for Modifying Distribution Data

Manually
You can modify the values in a Distribution record using either of the following options:
Using the Asset Strategy Optimization Scenarios - Risks page.

Using the Asset Strategy Optimization Scenarios - Grid page.
Defining Distribution Data Manually

Using the Risks Page
To define distribution data, you must be logged in as a Super User or member of the MI
To define TTF or TTR distribution data manually using the Asset Strategy Optimization
Scenarios - Risks page:
- Risks page, in the Diagram Hierarchy pane, select the element whose Risk
distribution you want to define.
2. In the grid in the Risks pane, in the row containing the Risk whose distribution
data you want to define...
In the TTF column, click the TTF Distribution link.
In the TTR column, click the TTR Distribution link.
-or-
The TTR Distribution or TTR Distribution window appears, depending on which link
you clicked.
3. Define the properties of the Distribution record as desired.

4. Click OK.
Your new distribution data is saved.
Defining Distribution Data Manually

Using the Grid Page
To define distribution data, you must be logged in as a Super User or member of the MI
To define TTF or TTR distribution data manually using the Asset Strategy Optimization
Scenarios - Grid page:
- Grid page, in the Filter list, select Distribution.
The grid is updated to display only the Distributions that belong to the Risks in that
Scenario.
About Associating Existing Distribution

Data with Risks
As an alternative to entering distribution data manually for Risks, you can associate Risks
with distribution data from existing Reliability Growth Analyses and Reliability
Distribution Analyses. When you enter data manually, you can choose any values that
you desire for your distribution data, but when you associate existing distribution data
with Risks, you use data stored in actual Reliability Growth or Reliability Distribution
Analyses.
After existing distribution data has been associated with a Risk, you can update the
information periodically. When you associate the distribution data, the Entity Key and
Family Key of the Reliability Distribution and Reliability Growth Analysis are stored in
the System Risk record, thereby establishing a connection between the two records that
allows for future updates. This way your ASO Analysis uses the most current information
available to calculate the simulation results.
Associating Existing Distribution Data

with Risks
To associate existing distribution data with Risks, you must be logged in as a Super User
or member of the MI ASM Analyst Security Group. The following instructions assume
that you have the privileges that are required to perform the task.
To associate an existing Reliability Distribution Analysis or Reliability Growth Analysis

with a Risk:
Risk with which you want to associate distribution data.
2. In the grid in the Risks pane, select the Risk with which you want to associate a
distribution data.
3. Below the grid in the Risks pane, click the Associate Distribution button.
The Find Items window appears, where you can search for a Reliability Growth Analysis
or Reliability Distribution Analysis whose distribution data you want to associate with a
Risk.
4. In the Find Items window, perform a search to locate your desired analysis.
The search results appear at the bottom of the window.
5. In the search results, select the desired record.
The distribution data from the selected record is imported, and a connection is established
between the Risk and the selected Reliability Growth Analysis or Reliability Distribution
Analysis.
Refreshing Distribution Data

To refresh the distribution data associated with a Risk:
Risk whose distribution data you want to refresh.
2. In the grid in the Risks pane, select the Risk whose distribution data you want to
refresh.
3. Below the grid in the Risks pane, click the Refresh Distribution button.
A confirmation message appears, asking if you really want to refresh all distribution data
for this Risk.
4. Click OK.
The distribution data is refreshed.
Opening Associated Analyses

You can open the Reliability Growth or Reliability Distribution Analysis that is
associated with the Risk selected in the Diagram Hierarchy pane. To open a Reliability
Growth or Reliability Distribution Analysis, you must be logged in as a Super User or a
member of the ASM Analyst Security Group.
To open an associated analysis:
Risk whose associated Reliability Growth or Reliability Distribution Analysis you
want to view.
2. In the grid in the Risks pane, select the Risk whose associated Reliability Growth
or Reliability Distribution Analysis you want to view.
3. Below the grid in the Risks pane, click the Open Analysis button.
Note: If your ASO Analysis has any unsaved changes, you will be prompted to save
them.
The ASO Analysis is closed, and the Reliability Growth or Reliability Distribution
Analysis is opened.
Removing the Association Between a

Risk and a Growth or Distribution
Analysis
To remove the association between a Risk and a Reliability Growth or Reliability
Distribution Analysis, you must be logged in as a Super User or member of the MI ASM
To remove the association between a Risk and a Reliability Growth or Reliability
Distribution Analysis:
Risk for which you want to remove an analysis association.
2. In the grid in the Risks pane, select the hyperlink that represents the analysis
association that you want to remove.
The <Distribution> window appears, where <Distribution> is the TTF or TTR
distribution that you selected.
3. In the bottom of the <Distribution> window, clear the Enable Distribution

Association check box.
The fields in the TTF Distribution window are enabled.
Note: You can keep the last values that have been imported from the associated analysis
or you can enter new distribution data manually.
4. Click OK.
About Resetting Risks

When a simulation is run, the occurrence of the Risks that are defined for a piece of
equipment, location, or switch are simulated, based upon the TTF Distribution associated
with that Risk. When a Risk with a failure type of Failure With Replacement occurs or
after actions are performed that mitigate the occurrence of that Risk in the simulation,
that Risk will be reset automatically. This means that the time in service for the
component associated with the Risk will be changed to zero (0), indicating that the
component was replaced (or repaired to as good as new).
When a Risk will be reset automatically is determined by the failure type of that Risk. A
Risk whose failure type is Failure With Replacement will be reset automatically when
any of the following scenarios occur:
An unplanned correction takes place following the occurrence of a Risk.

A planned correction takes place to mitigate the occurrence of a Risk.
Preventive Maintenance is performed against a piece of equipment or location to

mitigate the occurrence of a Risk.
A Special Action with a TTF replacement is performed against a piece of

equipment or location to mitigate the occurrence of a Risk.
A Risk whose failure type is Failure Without Replacement will be reset automatically
when any of the following scenarios occur:
Preventive Maintenance is performed against a piece of equipment or location to

mitigated the occurrence of a Risk.
A Special Action with TTF replacement is performed against an asset to mitigate

the occurrence of a Risk.
For example, suppose that the following Risks with a failure type of Failure With
Replacement are defined in your simulation for a Water Pump asset:
Bearing failure
Impeller failure
Seal failure
In the simulation, after unplanned correction is completed following the occurrence of the
Bearing failure Risk, the time in-service for the Bearing will be reset automatically to
zero (0) to indicate that you will replace the Bearing after it fails so that the Bearing
failure Risk will not occur again until the defined TTF Distribution is reached.
In addition to Risks being reset automatically as described above, you can specify that
additional Risks be reset following the planned or unplanned correction of a given Risk.
In other words, you can specify a Risk as a source Risk, whose planned or unplanned
correction triggers additional Risks to be reset at that time. This means that the time inservice for the components associated with the additional Risks will be changed to zero
(0), indicating that the additional components were also replaced (or repaired to as good
as new) following the planned or unplanned correction of the source Risk.
Throughout the documentation we will use the term source Risk to refer to a Risk whose
planned or unplanned correction triggers the resetting of additional Risks. We will use the
term additional Risk to refer to Risks that are reset by the occurrent or mitigation of a
source Risk.
You can specify that additional Risk should be reset only when:
An unplanned correction takes place following the occurrence of a given Risk.
A planned correction takes place to mitigate the occurrence of a given Risk.
-or-
It is important to note that source Risks that are mitigated as a result of Special Action
with a TTF replacement or Preventive Maintenance will not trigger any additional Risks
to be reset.
Continuing with our previous example, suppose that:
You will replace the Seal in addition to the Bearing when the Bearing failure Risk
occurs.
-or
The planned correction that you perform to mitigate the effect of the Bearing
failure Risk will also mitigate the occurrence of the Seal failure Risk.
In this case, you want to indicate in your simulation that the Bearing failure Risk (i.e., the
source Risk) should reset the Seal failure Risk (i.e., an additional Risk). In other words,
the time that the Seal has been in-service will also be changed to zero (0) to reflect that
the Seal was replaced (or repaired to as good as new) when the Bearing failure Risk
occurs or is mitigated as a result of planned correction.
You can manage the additional Risks that you should be reset by a source Risk via the
Risk to Reset dialog box or the shortcut menu in the Risks pane on the Asset Strategy
Optimization Scenarios- Risks page. You can specify any Risk that is defined for an asset
as a source Risk or an additional Risk, with a few exceptions.
Rules for Resetting Risks

When you set up a simulation to include source and additional Risks, it is important to
keep in mind the following rules:
You can specify a Risk as a source Risk if the failure type for that Risk is:
Failure With Replacement

-or-
Failure Without Replacement
You can specify a Risk as an additional Risk only if the failure type for that Risk
is Failure With Replacement.
Keep in mind that in the simulation, only Risks whose failure type is Failure With
Replacement are reset following a planned or unplanned correction. Risks whose failure
type is Failure Without Replacement are not be reset following a planned or unplanned
correction because the components associated with these Risks are not replaced (or
repaired to as good as new). Specifically, this means that a Risk whose failure type is
Failure Without Replacement:
Can be specified as a source Risk. In other words, the planned or unplanned

correction of these Risks can trigger additional Risks to be reset, if the failure type
of the additional Risks is Failure With Replacement.
Cannot be specified as additional Risks. In the Risks to Reset grid on the Risks to
Reset dialog box, rows containing Risks whose failure type is Failure Without
Replacement are disabled.
For example, suppose that the following Risks with the following failure types are
defined for a Shell and Tube Heat Exchanger asset:
A Tube Bundle Failure Risk whose failure type is Failure Without Replacement.
A Shell Head Failure Risk whose failure type is Failure With Replacement.
A Seals (gaskets) Failure Risk whose failure type is Failure With Replacement.
Now suppose that when you complete planed or unplanned correction for the Tube
Bundle Failure Risk, though you will not replace (or repair to as good as new) the Tube
Bundle, you will replace (or repair to as good as new) the Seals (gaskets). In this case,
you want to indicate in your simulation that the Tube Bundle Failure Risk is a source
Risk that should trigger the resetting of the Seals (gaskets) Failure Risk (i.e., an
additional Risk). In other words, the time that the Seal (gasket) has been in service will be
changed to zero (0) to reflect that the Seal (gasket) will be replaced (or repaired to as
good as new) following the planned or unplanned correction of the Tube Bundle Failure
Risk.
Interpreting Simulation Results That

Include Source and Additional Risks
The results for a simulation will appear differently depending upon whether or not the
simulation includes source and additional Risks. It is important that you understand how
to interpret simulation results that include source and additional Risks. When you set up a
simulation to include source and additional Risks, you should keep in mind the
information listed in this topic. This documentation assumes that you are familiar with
System Risk records and their role in an ASO Analysis.
If an unplanned correction causes a source Risk and any additional Risk to be

reset, in the simulation results, the Failure associated with the unplanned
correction of the source Risk will be attributed only to the source Risk.
If a planned correction of a source Risk triggers additional Risks to be reset, in the

simulation results, the following values will be attributed to each individual Risk:
Planned correction cost
Planned resource usages
Downtime
Downtime for each Risk will be calculated based upon the planned correction duration
for that Risk.
If an unplanned correction of a source Risk, triggers additional Risk to be reset, in

the simulation results, the following values will be attributed to each individual
Risk:
Fixed unplanned correction cost
Variable unplanned correction cost
Unplanned resource usage
Downtime
Variable unplanned correction cost and downtime for each Risk will be calculated based
upon the TTR distribution for that Risk.
If planned or unplanned correction of a source Risk triggers additional Risks to be

reset, in the simulation results, the System Asset record to which the System Risk
records are linked will be populated with the largest downtime value of all the
Risks (i.e., source and additional). For example, suppose the following Risks are
defined for a Water pump asset:
A Bearing failure Risk that is a source Risk, and whose downtime value is
1 day.
A Seal Failure Risk that is an additional Risk, and whose downtime value
is 2 days.
In this case, after the Bearing failure Risk resets the Seal Failure Risk will be reset, and in
the simulation results, a downtime value of 2 days will be attributed to the Water pump
asset.
If planned or unplanned correction has started for an additional Risk, and then
planned or unplanned correction starts for the source Risk that resets that
additional Risk, the additional Risk will be reset only once as a result of its own
planned or unplanned correction. The additional Risk will not be reset two times
as a result of its own planned or unplanned correction and the planned or
unplanned correction of the source Risk. This will be reflected in the simulation
results.
Overview of the Risks to Reset Dialog

Box
Using the Risks to Reset dialog box, you can specify per source Risk the additional Risks
that should be reset following the planned or unplanned correction of that Risk.
The Risks to Reset for <Asset ID> dialog box contains the Risks to Reset <Risk ID> grid,
where:
<Asset ID> is the Entity ID of the System Asset record represented by the Asset
element and to which the System Risk record is linked.
<Risk ID> is the value stored in the Name field in the System Risk record of the
source Risk for which you are specifying additional Risks to be reset.
Throughout this documentation, we refer to the Risks to Reset for <Asset ID> dialog box
as the Risks to Reset dialog box, and we refer to the Risks to Reset for <Risk ID> grid as
the Risks to Reset grid.
Consider the following image, which shows an example of what the Risks to Reset dialog
box looks like when you access it from a Bearing failure Risk that is defined for the Asset
element G0006-071.
In this image, you can see that the Risks to Reset grid displays the Risks that are defined
for the Asset element G0006-071. You can select these Risks to specify that the Bearing
failure Risk (i.e., the source Risk) should reset additional Risks in the simulation.
Using the Risks to Reset Dialog Box

You can use the Risks to Reset dialog box to select the additional Risks that a source Risk
should reset. You can access the Risks to Reset dialog box by clicking the hyperlinked
number in the Risks to Reset cells in the:
Risks pane on the Asset Strategy Optimization Scenarios - Risks page.

Mitigated Risks pane on the Asset Strategy Optimization Scenarios - Actions
page.
You can modify selections on the Risks to Reset dialog box only when it is accessed via
the Asset Strategy Optimization Scenarios - Risk page. If you access the Risks to Reset
dialog box via the Asset Strategy Optimization Scenarios - Actions page, all the options
will be disabled. The following image shows the Risks to Reset dialog box as it appears
when you access it from the Asset Strategy Optimization Scenarios - Risks page.
The Risks to Reset dialog box contains the Risks to Reset grid, which displays all the
Risks that are defined for the selected Asset element, except for the currently selected
Risk, whose ID appears in the title above the grid. This is the source Risk.
Each row in the grid represents one Risk. For each Risk that is displayed in the grid, the
following columns appear and contain values from the underlying System Risk record:
Name: Displays the value stored in the Name field in the System Risk record.
Failure Without Replacement: Displays one of the following read-only selections
that is stored in the Failure Without Replacement field in the System Risk record:
No: Indicates that the failure type for the Risk in that row is Failure With
Replacement. Risks with this failure type can be selected as an additional
Risk to be reset.
Yes: Indicates that the failure type for the Risk in that row is Failure
Without Replacement. Risks with this failure type cannot be selected as an
additional Risk to be reset, and rows in the grid for these Risks will be
disabled.
An additional, unlabeled column containing a check box appears to the left of the Name
column and lets you select the Risks that should be reset by the source Risk.
Below the grid, the Select All check box appears, which you can use to:
Select all the Risks that are defined for the piece of equipment or location.
Clear all the currently selected Risks.
-or-
If one or more check boxes are selected in the grid (but not all), the Select All check box
will be selected and colored gray. For example, the following image shows how the
Select All check box appears in this case. A red outline has been added to the image to
highlight this check box. You can clear the gray Select All check box to clear all the
currently selected check boxes.
In addition, the following buttons are available on the Risks to Reset dialog box:
OK: Saves your changes and closes the Risks to Reset dialog box.
Cancel: Closes the Risks to Reset dialog box and discards your changes.
The Shortcut Menu in the Risk Pane

When you right-click any cell in the Risks pane on the Asset Strategy Optimization
Scenarios - Risks page, a shortcut menu appears, as shown in the following image. This
menu contains options that you can use to manage the Risks that you want to be reset by
a source Risk. The source Risk is determined by the row from which you access the
shortcut menu.
The shortcut menu in the Risks pane contains the following options:
Select All Risks to Reset for Current Risk: Specifies that ALL the Risks defined
for the equipment should be reset by the selected source Risk.
Unselect All Risks to Reset for Current Risk: Specifies that none of the Risks
defined for the equipment should be reset by the selected source Risk.
Select All Risks to Reset for Asset: Specifies that ANY Risk defined for the
equipment should reset ALL the remaining Risks defined for the equipment.
Unselect All Risks to Reset for Asset: Specifies that none of the Risks defined for
the equipment should be reset by any other Risk defined for the equipment.
Specifying Risks to Reset

The following instructions provide details on specifying which additional Risks should be
reset by a source Risk, using the Risks to Reset dialog box. When you specify that a Risk
should be reset, the time in-service for the component associated with the Risk will be
changed to zero (0) in the simulation, following the planned or unplanned correction of
the source Risk.
These instructions assume that you are viewing the desired ASO Analysis on the Asset
Strategy Optimization Scenarios - Risks page. Additionally, if you are viewing a System
or Unit Strategy, these instructions assume that the desired Asset element is selected in
the Diagram Hierarchy pane.
To specify Risks to reset:
1. In the Risks pane, locate the row containing the desired source Risk.
2. In the Risks to Reset cell, click the hyperlinked number.
The Risks to Reset dialog box appears.
3. In the Risks to Reset grid, select the check box in the row containing each
additional Risk that you want to be reset by the source Risk.
In the following image, you can see that the Lubricant Degradation and Seal Leak Risks
are selected to be reset by the Lubricant Loss Risk.
Hint: You can use the Select All check box to select all the Risks defined for the piece of
equipment or location.
4. Click OK.
The Risks to Reset dialog box closes, and the hyperlinked in the Risks to Reset cell for
the source Risk changes to reflect the number of additional Risks you selected. When you
run the simulation, the time in-service for the components associated with the additional
Risks will be changed to zero (0), following the planned or unplanned correction of the
source Risk.
In the following image, you can see that the hyperlinked number in the Risks to Reset
cell for the Lubricant Loss Risk is 2, indicating that the Lubricant Loss Risk resets two
additional Risks. The Risks to Reset cell has been outlined in red to highlight this value.
In the example used in these instructions, when you run the simulation, the time that the
Lubricant and the Seal has been in service will be changed to zero (0), following the
planned or unplanned correction of the Lubricant Loss Risk to reflect that the Seal and
the Lubricant were replaced (or repaired to as good as new).
Updating Risks to Reflect the Active

Scenario
If a Scenario contains a System Risk record whose values are different from the
corresponding System Risk record in the Active Scenario, you can update the System
Risk record in the non-Active Scenario so that its values are identical to the values in the
corresponding System Risk record in the Active Scenario. You can update a System Risk
record only if an Asset element is selected in the Diagram Hierarchy pane and the
selected System Risk record is somehow different from the corresponding System Risk
record.
You will know that a System Risk record is somehow different from the corresponding
System Risk record in the Active Scenario if the row in which it appears contains the
icon or the
icon.
Note: Before you update a System Risk record, you might want to click the Show
Changes button so that you can see how the System Risk record in this Scenario differs
from the one in the Active Scenario.
To update a Risk record, you must be logged in as Super User or a member of the MI
To update a System Risk record so that its values match the values in the corresponding
System Risk record in the Active Scenario:
Asset element whose System Risk record you want to update.
2. In the grid in the Risks pane, select the System Risk record that you want to
update.
3. Below the grid in the Risks pane, click the Undo Risk button.
The System Risk record is updated so that its values are identical to the values in the
corresponding System Risk record in the Active Scenario.
About Viewing Differences Between

Proposed Risks and Active Risks
If a non-Active Scenario contains a System Risk record whose values or values in related
records are different from the corresponding records in the Active Scenario, you can view
the differences between those records. You will know that a System Risk record or a
related record is somehow different in the Active Scenario if the row in which it appears
contains the icon or the
icon. You can view the differences, however, only if the
row contains the icon.
You can view these differences on the Changes for <Risk> dialog box, where <Risk> is
the value stored in the Name field in the corresponding System Risk record. You can
access this dialog box from the Show Changes button in the Risks pane on the Asset
Strategy Optimization Scenarios - Risks page, when a Risk is selected in the grid. The
Changes for <Risk> dialog box contains a grid that contains the following information:
Field: The field whose value differs from the value in the same field in the
corresponding record in the Active Scenario.
Old Value: The value in the Active Scenario, with the exception of the following
fields:
Planned Resource Usages
Unplanned Resource Usages
Related Risks
Instead, these cells indicate that changes were made to the data in these areas for the
Risk. To see the specific changes, you will need to open the corresponding records.
New Value: The value in the non-Active Scenario, with the exception of the
following fields:
Related Risks
Risk. To see the specific changes, you will need to open the corresponding records.
The rows in the grid are grouped by family name, and then by record ID.
The following image shows what the Changes for <Risk> dialog box looks like when you
are viewing changes for a Bearing Failure Risk.
Accessing the Changes for <Risk Name>

Dialog Box
If a non-Active Scenario contains a System Risk record whose values or values in related
records are different from the Active Scenario, you can view the differences between
those records using these instructions. After you review the differences, if desired, you
can update the System Risk record in the current Scenario so that its values will match
the values in the Active Scenario.
To access the Changes for <Risk name> window:

Asset element whose System Risk records you want to view.
2. In the Risks pane, select the row containing the Risk whose differences you want
to view.
The Changes for <Risk> dialog box appears.
Deleting Risks
To delete a Risk, you must be logged in as a Super User or member of the MI ASM
Note: You can delete a Risk only in a non-Active Scenario.
To delete a Risk:
element whose Risk you want to delete.
2. In the grid in the Risks pane, select the Risk that you want to delete.
3. Below the grid in the Risks pane, click the Delete Risk button.
A confirmation message appears, asking if you really want to delete the Risk.
The Risk is removed from the grid on the Asset Strategy Optimization Scenarios - Risks
page.
About Actions
In an ASO Analysis, an Action represents an operation that can be performed against a
piece of equipment or location. Actions can represent inspections, general maintenance,
or specific events that mitigate Risks. Using an action to mitigate a risk can help to
improve reliability and efficiency by minimizing downtime and lost production costs.
Actions can be unique events that happen only once during a simulation period, or they
can be repeated at certain times during the simulation period. You can optionally assign
resources to actions to associate a specific cost with the action. When you assign
resources to actions, a System Resource Usage record will be created.
Actions in ASO Analyses are stored in the following records:
System Condition Monitor Records: Store information about continuous,

condition-based maintenance Actions.
System Inspection Records: Store information about periodic, condition-based
maintenance Actions.
System Preventive Maintenance Records: Store information about time-based

maintenance Actions.
System Special Action Records: Store information about procedural, redesign, or

training Actions.

The Diagram Hierarchy pane on the Asset Strategy Optimization Scenarios - Actions
page displays the elements in the Diagram that can have Actions associated with them. In
the following image, the Diagram Hierarchy pane is outlined in red.
When you select an element in the Diagram Hierarchy pane, the Actions that are
currently defined for that element are displayed in the Actions pane. For example, in this
image, the selected G0005-098 asset has seven associated Actions:
Change Lubricant
Check Lubrication
Internal Inspection
Vibration Inspection
Lube Oil Analysis
Motor Test
Operational Check
Actions Pane
The Actions pane is displayed on the Asset Strategy Optimization Scenarios - Actions
page and on the Actions Editor window. It displays the Actions that are associated with
the element that is selected in the Diagram Hierarchy pane. In the following image, the
Actions pane is outlined in red.
The grid in the Actions pane displays the following columns of information:
Flag: Contains an icon indicating the status of the System Action record relative
to the corresponding System Action record that belongs to the Active Scenario.
If you are viewing System Action records that belongs to the Active
Active) and the System Action record is identical to the corresponding
System Action record in the Active Scenario, the Flag column will not
contain an icon.

Active) and the System Action record does not have a corresponding
the icon.

Active) and the System Action record is different from the corresponding
the icon.

the Flag column will contain the icon.
Name: Displays the value that exists in the Name field in the System Action
record.
Description: Displays the value that exists in the Description field in the System
Action record.
Resource Usages: Displays the Resource Usages link, which provides access to
any Resources that have been assigned to the Action.
Below the grid in the Actions pane, the following buttons appear:
Add Action: Displays the Select Action Type dialog box, where you can create a
new System Action record to link to the current System Asset or System Switch
record. This button is always disabled if you are viewing Actions that belong to
the Active Scenario. To add Actions, you must be logged in as a Super User or
member of the MI ASM Analyst Security Group. The documentation assumes that
Delete Action: After asking for confirmation, deletes the System Action record
that is currently selected in the Actions pane. To delete Actions, you must be
logged in as a Super User or member of the MI ASM Analyst Security Group. The
documentation assumes that you have the privileges that are required to perform
the task.
Undo Action: Causes the System Action record to be updated so that its values are
identical to the values in the corresponding System Action record in the Active
Scenario. Before you click the Undo Risk button, you might want to click the
Show Changes button so that you can see how the System Action record in this
Scenario differs from the one in the Active Scenario. This button is always
disabled if you are viewing Actions that belong to the Active Scenario. If you are
viewing Actions that belong to any other Scenario, this button is enabled only if
an Asset element is selected in the Diagram Hierarchy pane and the Action is
somehow different from the corresponding Action in the Active Scenario. This
option is enabled only if you are logged in as a Super User or member of the MI
Show Changes: Displays the Changes for <Action> window, where <Action> is
the value in the Name field in the selected System Action record. You can use this
window to see the differences that exist between values in this System Action
record and values in the corresponding System Action record in the Active
Scenario. This button is always disabled if you are viewing Actions that belong to
the Active Scenario. If you are viewing Actions that belong to any other Scenario,
this button is enabled only if an Asset element is selected in the Diagram
Hierarchy pane and the Action is somehow different from the corresponding
Action in the Active Scenario.
Optimize: Displays the Action Interval Optimization window, where you can find
the optimal interval at which to implement an Action.
Mitigated Risks Pane

The Mitigated Risks pane is displayed on the Asset Strategy Optimization Scenarios Actions page and on the Actions Editor window. It displays the Risks that are mitigated
by the Action that is selected in the Actions pane. In the following image, the Mitigated
Risks pane is outlined in red.
The Mitigated Risks pane displays the following columns of information:
Flag: Contains an icon indicating the status of the System Risk record relative to
the corresponding System Risk Assessment record that belongs to the Active
Scenario.
If you are viewing System Risk records that belongs to the Active

Active) and the System Risk record is identical to the corresponding
System Risk Assessment record in the Active Scenario, the Flag column
will not contain an icon.

Active) and the System Risk record does not have a corresponding System
Risk Assessment record in the Active Scenario, the Flag column will
contain the icon.

Active) and the System Risk record is different from the corresponding
System Risk Assessment record in the Active Scenario, the Flag column

the Flag column will contain the
icon.
Name: Displays the value that exists in the Name field in the System Risk record.
This value appears as a hyperlink that you can click to open the datasheet for that
System Risk record.
Description: Displays the value that exists in the Description field in the System
Risk record.
TTF: Displays the TTF Distribution link. You can click this link to open the TTF
Distribution window, where you can view and modify the Time to Failure (TTF)
distribution data for the associated System Risk record.
TTR: Displays the TTR Distribution link. You can click this link to open the TTR
Distribution window, where you can view and modify the Time to Repair (TTR)
distribution data for the associated System Risk record.
Planned Resource Usages: Displays the Planned Resource Usages link, which you
can click to open the Planned Resource Usages window and view any planned
Resources that have been assigned to the Risk.
Unplanned Resource Usages: Displays the Unplanned Resource Usages link,

which you can click to open the Unplanned Resource Usages window and view
any unplanned Resources that have been assigned to the Risk.
Qualitative Consequence: Displays a hyperlinked numeric value, which you can

click to open the Qualitative Consequence Editor window.
Risks to Reset: Displays a number representing the number of additional Risks

that will be reset in the simulation following the planned or unplanned correction
of the Risk in that row. This number appears as a hyperlink, which you can click
to access the Risks to Reset dialog box, where you can view the additional Risks
that will be reset in the simulation following the planned or unplanned correction
of the source Risk. For details on managing Risks to reset, see the section of this
documentation on managing Risks to reset.
Below the Mitigated Risks grid, the following buttons appear:
Assign New Risk: Displays the New Risk window, where you can create a new
Risk that will be mitigated by the Action that is currently selected in the Actions
pane. This option is enabled only if you are logged in as a Super User or member
of the MI ASM Analyst Security Group.
Assign Existing Risks: Displays the Assign Risks window, where you can assign
an existing Risk to be mitigated by the Action that is currently selected in the
Actions pane or remove an existing Risk from being mitigated by the Action that
is currently selected in the Actions pane. This option is enabled only if you are
About Creating System Action Records

When you create an Action in an ASO Analysis, a record is created in a subfamily of the
System Action family. The Meridium APM system determines the specific family in
which to create the record based upon:
Your selections in the Action Type and Condition Monitoring Type lists on the
Select Action Type dialog box.
-AND
The values that exist in System Action Mapping records.
After you select values on the Select Action Type dialog box, the Meridium APM system
searches all System Action Mapping records for a record with identical values in the
Action Type and Condition Monitoring fields, respectively. When it finds a record with
matching values, the Meridium APM system creates a System Action record in the family
whose caption appears in the ASO Action Type field in that System Action Mapping
record.
About the Select Action Type Dialog Box

The Select Action Type dialog box lets you specify the type of Action that you want to
create using the combination of values that you select in the Action Type and Condition
Monitoring Type lists.
Before you can create an Action, however, you will need to access the Select Action Type
dialog box. You can do so via the following methods:
If you want to create a new Action and assign it to an element without assigning it
to a Risk, on the Asset Strategy Optimization Scenarios - Actions page, in the
Diagram Hierarchy pane, select the element to which you want to add an Action,
and then click the Add Action button, which appears below the grid on the
Actions pane.
-OR
If you want to create a new Action and assign it to an element and a Risk, on the
Asset Strategy Optimization Scenarios - Risks page, in the Diagram Hierarchy
pane, select the element that contains the Risk to which you want to assign an
Action, and then click the Assign New Action button, which appears below the
grid in the Mitigated Actions pane.
The following table shows the values that you can select in the Action Type and
Condition Monitoring Type lists and the record in the System Action subfamily that will
be created, based up on the combination of values that you specify.
Note: The Condition Monitoring Type list appears only if you select Condition-Based
Maintenance (Predictive) (CM) in the Action Type list.
Selecting this Action Type ...and this Condition

Value:
Monitoring Type Value:
...Creates this record:
Condition-Based
Maintenance (Predictive)
(CM)
Periodic
System Inspection
Condition-Based
(CM)
Continuous
System Condition Monitor
Procedure (PROC)
n/a*
Redesign (DSN)
n/a*
Time-Based Maintenance
(Preventive) (PM)
n/a*
System Preventive
Maintenance
Training (TRN)
n/a*
For example, if you create an Action by selecting Condition-Based Maintenance

(Predictive) (CM) in the Action Type list and Continuous in the Condition Monitoring
Type list, a System Condition Monitor record will be created.
Creating System Condition Monitor

Records
To create a new System Condition Monitor record:
1. Using the desired method, access the Select Action Type dialog box.
The Select Action Type dialog box appears.
2. In the Action Type list, select Condition-Based Maintenance (Predictive) (CM).

3. In the Condition Monitoring Type list, select Continuous.
4. Click OK.
The New Condition Monitor window appears.
5. In the fields on the New Condition Monitor window, define the values of the
System Condition Monitor record as desired.
6. Click OK.
The System Condition Monitor record is saved, and the new Action appears in the
Actions grid.
Hint: If desired, in the grid in the Actions pane, you can click the Resource Usages
hyperlink to assign Resources to the Action.
Creating System Inspection Records

To create a new System Inspection record:
2. In the Action Type list, select Condition-Based Maintenance (Predictive) (CM).

3. In the Condition Monitoring Type list, select Periodic.
4. Click OK.
The New Inspection window appears.
5. In the fields on the New Inspection window, define the values of the System
Inspection record as desired.
6. Click OK.
The System Inspection record is saved, and the new Action appears in the Actions grid.
Creating System Preventive

Maintenance Records
To create a new System Preventive Maintenance record:

2. In the Action Type list, select Time-Based Maintenance (Preventive)(PM).

The Condition Monitoring Type list is hidden.
3. Click OK.
The New Preventive Maintenance window appears.
4. In the fields on the New Preventative Maintenance window, define the values of
the System Preventative Maintenance records as desired.
5. Click OK.
The System Preventive Maintenance record is saved, and the new Action appears in the
Actions grid.
Creating System Special Action Records

To create a new System Special Action record:
2. In the Action Type list, select one of the following values:

Procedure (PROC)
Redesign (DSN)
Training (TRN)
The Condition Monitoring Type list is hidden.

3. Click OK.
The New Special Action window appears.
4. In the fields on the Action Properties tab, define the values of the New Special
Action record as desired.
The System Special Action record is saved, and the new Action appears in the Actions
grid.
Assigning Existing Actions to Risks
To assign Actions to a Risk, you must be logged in as a Super User or member of the MI
Note: You can assign existing Actions to Risks for Scenarios in a state other than Active.
To assign one or more existing Actions to a Risk:
- Risks page, select the Risk to which you want to assign an existing Action.
2. Below the grid in the Mitigating Actions pane, click the Assign Existing Actions
button.
The Assign Actions window appears.
3. In the Is Selected column of the grid, select the check box for the Action(s) that
you want to assign.
Note: You can remove any Action that is currently assigned to the Risk by clearing the Is
Selected check box.
4. Click OK.
The Action(s) are assigned and appear in the grid in the Mitigating Actions pane.
Overview of the <Special Action>

Window
When you view an existing System Special Action record, it appears in the <Special
Action> window, where <Special Action> is the name of the Action as it appears in the
Name field in the System Special Action record.
Using the <Special Action> window, you can:
View and modify the System Special Action record.
View a list of System Risk Assessment records that are linked to the System
Special Action record.
Additionally, for each System Risk Assessment record, you can specify the failure
consequence and TTF Distribution values that you want to use in the simulation.
The <Special Action> window contains the following tabs:
Action Properties: Displays the System Special Action datasheet.

Mitigated Risks: Displays the list of System Risk Assessment records that are
linked to the Action and provides options that you can use to specify the failure
consequence and TTF Distribution values that you want to be used in the
simulation when a Special Action is completed to mitigate the occurrence of a
given Risk.
The Mitigated Risks Tab

You can use the Mitigated Risks tab on the <Special Action> window to specify for each
Mitigated Risk that is associated with the Special Action the Failure Consequence and
TTF Distribution values that you want to be used in the simulation when the Special
Action is completed to mitigate the occurrence of the given Risk.
To the left, the Mitigated Risks tab displays the list of Mitigated Risks that are associated
with the Special Action. Each Mitigated Risk represents one System Risk Assessment
record that is linked to the System Special Action record. For each Mitigated Risk that
appears in the list to the left, the following items are displayed to the right:
New Failure Consequence tab: Contains the following items:
Replace Failure Consequence check box: Indicates that, for the selected
Mitigated Risk, you want the simulation to use the Fixed Unplanned
Correction Cost value and the Qualitative Consequence values that you
specify below.
Fixed Unplanned Correction Cost text box: Stores the values that you
want the simulation to use in place of the one that currently exists in the
Fixed Unplanned Correction Cost field in the selected System Risk
Assessment record. This text box is enabled only if the Replace Failure
Consequence check box is selected.
Total Qualitative Consequence: Stores the value that you want the
simulation to use in place of the Total Qualitative Consequence value that
currently exists for the selected Mitigated Risk. This field is disabled and
populated automatically with the sum of the individual values that appear
in the table below the Total Qualitative Consequence text box. To modify
this value, modify the individual values in the Qualitative Consequence
cells in the table. The cells in the Qualitative Consequence column are
enabled only when the Replace Failure Consequence check box is
selected.
The following image shows an example of the New Failure Consequence tab. A
red outline has been added to this image to highlight the tab.
New TTF Distribution tab: Contains the following items:
Replace TTF Distribution check box: Indicates that, for the selected
Mitigated Risk, you want the simulation to use the values that you specify
in the Distribution fields below.
Distribution datasheet: Contains the fields that appear in the Distribution

record that is linked to the System Risk Assessment record. The fields on
the datasheet are enabled only if the Replace TTF Distribution check box
is selected. You can use these fields to store the values that you want to
use when you run the simulation, in place of the values specified on the
TTF Distrubution dialog box for the System Risk record.
The following image shows an example of the New TTF Distribution tab. A red
outline has been added to this image to highlight the tab.
Specifying Failure Consequence Values

for the Simulation
If desired, you can use the <Special Action> window to specify for each Mitigated Risk
that is associated with the Special Action the Failure Consequence values that you want
to be used in the simulation when the Special Action is completed to mitigate the
occurrence of the given Risk.
To specify Failure Consequence values for the simulation:
1. On the ASO - Asset Strategy Optimization Scenarios - Actions page, in the
Actions pane, locate the row containing the desired Special Action.
2. In the Name cell, click the hyperlinked name of the Special Action.
The <Special Action> window appears, where <Special Action> is the value that appears
in the Name field in the System Special Action record.
3. Click the Mitigated Risks tab.

The Mitigated Risks tab appears.
4. In the list to the left, select the Mitigated Risk whose Failure Consequence values
you want to specify for the simulation.
5. On the New Failure Consequence tab, select the Replace Failure Consequence
check box.
The remaining fields are enabled.
6. In the remaining fields, modify the values as desired.
7. Repeat these steps for each Mitigated Risks whose failure consequence values
you want to specify for the simulation, and then click the Close button.
Your changes are saved, and the values that you specified will be used the next time that
the simulation is run.
Specifying TTF Distribution Values for

the Simulation
If desired, you can use the <Special Action> window to specify for each Mitigated Risk
that is associated with the Special Action the TTF Distribution values that you want to be
used in the simulation when the Special Action is completed to mitigate the occurrence of
the given Risk.
To specify TTF Distribution values for the simulation:
1. On the ASO - Asset Strategy Optimization Scenarios - Actions page, in the
Actions pane, locate the row containing the desired Special Action.
2. In the Name cell, click the hyperlinked name of the Special Action.
The <Special Action> window appears, where <Special Action> is the value that appears
in the Name field in the System Special Action record.
3. Click the Mitigated Risks tab.

The Mitigated Risks tab appears.
4. To the right, click the New TTF Distribution tab.

The New TTF Distribution tab appears.
5. In the list to the left, select the Mitigated Risk whose TTF Distribution values you
want to specify for the simulation.
6. On the New TTF Distribution tab, select the Replace TTF Distribution check box.
The fields in the Distribution datasheet section are enabled.
7. In the remaining fields, modify the values as desired.
8. Repeat these steps for each Mitigated Risk whose TTF Distribution values you
want to specify for the simulation, and then click the Close button.
Your changes are saved, and the values that you specified will be used the next time that
the simulation is run.
Options for Modifying Actions

You can modify the values in a System Action record using either of the following pages:
Asset Strategy Optimization Scenarios - Actions page.

Asset Strategy Optimization Scenarios - Grid page.
Modifying Actions Using the Actions

Page
To modify Actions, you must be logged in as a Super User or member of the MI ASM
To modify an existing Action using the Asset Strategy Optimization Scenarios - Actions
page:
- Actions page, in the Diagram Hierarchy pane, select the element that contains
the Action that you want to modify.
2. In the grid in the Actions pane, click the hyperlinked name of the Action that you
want to modify.
The <Action Name> window appears, where <Action Name> is the name of the Action
that you selected.
The content of the Vibration Analysis window is controlled by the default datasheet for
the System Inspection family.
3. Modify the fields in the System Action record as desired.
4. Click OK.
Modifying Actions Using the Grid Page
To modify Actions, you must be logged in as a Super User or member of the MI ASM
To modify an Action using the Asset Strategy Optimization Scenarios - Grid page:
- Grid page, in the Filter list, select Action.
The grid is updated to display only the Actions that belong to that Scenario.
About Resources for Actions

After Resources exist for an ASO Analysis, you can assign them to Actions. When you do
so, you associate the cost of that resource with each occurrence of the action. This allows
you to assign a realistic cost to the action that can be included in the simulation results.
When you assign a Resource to an Action, a System Resource Usage record will be
created and will store information that specifies how the Resource will be used (e.g., the
quantity and duration).
Assigning Resources to Actions

To assign Resources to Actions, you must be logged in as a Super User or member of the
To assign a Resource to an Action:
1. While viewing the desired Active Scenario on the Asset Strategy Optimization
Scenarios - Actions page, in the Diagram Hierarchy pane, select the element that
contains the Action to which you want to assign a Resource.
2. In the grid in the Actions pane, in the row containing the Action to which you
want to assign a Resource, click the Resources Usages link.
The Resource Usages - <Action> window appears, where <Action> is the name of the
Action that you selected, displaying any Resources that are assigned to the Action.
In this image, the Resource Usages - Vibration Analysis window displays the Resources
that are assigned to the Vibration Analysis Action.
3. Click the Add Existing button. This button will be enabled only if one or more
Resources already exist for the analysis.
A new row appears in the grid.
Note: You can click the Add New button to create a Resource from scratch and assign it
to an Action. After you have created the Resource, you can skip to step 5.
4. In the Resource cell of the first row, click the
button, and select the Resource
you want to assign to the Action.
5. Type the desired values in the Quantity, Duration, and Duration Units cells. These
values will be used to populate the corresponding fields in the System Resource
Usage record.
Note: The Total Fixed Cost and Total Variable Cost columns display the actual value that
will be incurred when the System Resource Usage is added to the Simulation Results.
Since this value is a product of the values you enter on into the Resource dialog box and
Resource Usage window, the cells are disabled and you cannot type values in these cells.
The Resource Usages - <Action> window closes, and the selected Resources are assigned
to the Action.
Modifying Resource Assigned to Actions

When you modify a Resource assignment, you are modifying the System Resource Usage
record. The actual System Resource record is not changed. To modify a Resource
assignment, you must be logged in as a Super User or member of the MI ASM Analyst
Security Group. The following instructions assume that you have the privileges that are
required to perform the task.
To modify a Resource assigned to an Action:
- Actions page, in the Diagram Hierarchy pane, select the element whose Action
has Resources that you want to modify.
2. In the grid in the Actions pane, in the row containing the Action whose Resources
you want to modify, click the Resource Usages link.
Action that you selected.
3. In the Resource Usages grid, modify the properties of the Resource Usage record
as desired.
Removing Resources from Actions

When you remove a Resource from an Action, you delete the System Resource Usage
record so that the Resource is not used by the selected Action. The actual System
Resource record is still available for the ASO Analysis and can be used again if needed.
To remove a Resources from an Action, you must be logged in as a Super User or
To remove a Resource from an Action:

- Actions page, in the Diagram Hierarchy pane, select the Action whose Resource
assignment you want to remove.
2. In the grid in the Actions pane, in the row containing the Action whose Resource
assignments you want to remove, click the Resource Usages link.
Action that you selected.
3. In the Resource Usages grid, select the Resource Usage record that you want to
delete.
A confirmation message appears, asking if you really want to delete the selected item(s).
The Resource Usage is removed from the grid, and the System Resource Usage record is
The Resource Usages - <Action> window closes.
About Optimizing Actions

In an ASO Analysis, you can optimize Actions to determine the most efficient interval at
which to perform inspection or preventive maintenance Actions. The optimal interval
balances the cost of the Actions and reliability.
You have two options for optimizing Actions:
You can optimize a single Action.
You can optimize multiple Actions across multiple Scenarios.
After an optimal interval has been calculated, you can apply it to your analysis by
replacing the current interval value with the optimal interval value.
Optimizing a Single Action

To optimize an Action, you must be logged in as a Super User or member of the MI ASM
To optimize a single Action:
- Actions page, in the Diagram Hierarchy pane, select the element whose Action
you want to optimize.
2. In the grid in the Actions pane, select the Action that you want to optimize.
3. Below the grid in the Actions pane, click the Optimize button.
The Action Interval Optimization window appears.
In this image, the Action Interval Optimization window displays the data necessary to
optimize the Replace Seals Action.
4. In the Min Interval text box, type the desired minimum interval.
5. In the Max Interval text box, type the desired maximum interval.
6. In the Increment text box, type the desired increment.
Note: If desired, you can change the value in the Current Interval text box, which
represents the current interval at which the current Action is performed. This text box is
populated with the value in the Current Interval field in the System Action record.
Modifying the value in the Action Interval Optimization window will cause the value in
the System Action record to be updated with the same value.
7. Click the Run Simulation button.
The Optimization Progress window appears, displaying the progress of the optimization
process.
The Optimization Progress window closes, and the Action Interval Optimization window
displays the Cost chart and an updated value in Optimal Interval text box.
Optimizing Multiple Actions

To optimize Actions, you must be logged in as a Super User or member of the MI ASM
To optimize multiple Actions within an ASO Analysis:
1. While viewing the desired ASO Analysis on any page, on the Tools menu, click
the Optimize Actions link.
The Multiple Action Interval Optimization window appears.
In this image, the Multiple Action Interval Optimization window displays Actions in an
ASO Analysis that can be optimized.
2. In the grid in the Actions pane, select the Optimize? check box for the Actions
that you want to optimize.
3. In the row containing the first Action you want to optimize, in the Min Interval
text box, type the desired minimum interval.
4. In the row containing the first Action you want to optimize, in the Max Interval
text box, type the desired maximum interval.
5. In the row containing the first Action you want to optimize, in the Increment text
box, type the desired increment.
6. Repeat steps 3 through 5 for other Actions you want to optimize.
Note: If desired, you can change the data in the Current Interval text box, which
represents the current interval at which the current Action is performed. This text box is
populated with the value in the Current Interval field in the System Action record.
Modifying the value in the Multiple Action Interval Optimization window will cause the
value in the System Action record to be updated with the same value.
7. Below the grid in the Actions pane, click the Run Simulation button.
The Optimization Progress window appears, displaying the progress of the optimization
process.
The Optimization Progress window closes, and the Action Interval Optimization window
displays the Cost chart and an updated value in Optimal Interval text box.
About Applying Optimal Action

Intervals
When you optimize Actions, you can determine the most efficient interval in which to
perform inspection or preventive maintenance Actions. After you have found the optimal
interval for an Action you can apply it to that Action. When you do so, the value in the
Current Interval text box in the Actions pane and the value in the Interval field in the
System Action record will be overwritten with the value that exists in the Optimal
Interval text box.
After you apply the optimal interval, you will need to rerun the simulation for the ASO
Analysis to update the result based upon the new action interval.
Applying Optimal Intervals to Actions

To apply optimal intervals to Actions, you must be logged in as a Super User or member
Applying the Optimal Value to a Single Action:

To apply the optimal interval to a Single Action:
1. Find the optimal Action interval value for the Action you want to optimize.
2. On the Action Interval Optimization window, in the Settings section, click the
Apply Optimal Value button.
Note: The Apply Optimal Value button is enabled only after you have optimized an
Action. If you close the Action Interval Optimization window, you will have to optimize
the Action again for the Apply Optimal Value button to become enabled.
The value in the Optimal Interval text box replaces the value in the Current Interval text
box in the Settings section and in the Interval field in the associated System Action
record.
Applying Optimal Intervals to Multiple Actions:

To apply optimal intervals to multiple Actions:
1. Find the optimal Action intervals for the Actions you want to optimize.
2. In the grid in the Actions pane, in the Apply? column, select the check box for the
Actions whose current interval you want to replace with the optimal interval.
3. Below the grid in the Actions pane, click the Apply Optimal Values button.
The values in the Optimal Interval text boxes replace the values in the respective Current
Interval text boxes in the grid in the Actions pane and in the Interval field in the
associated System Action records.
About Viewing Differences Between

Proposed Actions and Active Actions
If a non-Active Scenario contains a System Action record whose values or values in
related records are different from the corresponding records in the Active Scenario, you
can view the differences between those records. You will know that a System Action
record or a related record is somehow different in the Active Scenario if the row in which
it appears contains the icon or the icon. You can view the differences, however, only
if the row contains the icon.
You can view these differences on the Changes for <Action> dialog box, where <Action>
is the value stored in the Name field in the corresponding System Action record. You can
access this dialog box from the Show Changes button in the Actions pane on the Asset
Strategy Optimization Scenarios - Actions page, when an Action is selected in the grid.
The Changes for <Action> dialog box contains a grid that contains the following
information:
corresponding record in the Active Scenario.
Old Value: The value in the Active Scenario, with the exception of the following
fields:
Action. To see the specific changes, you will need to open the corresponding records.
New Value: The value in the non-Active Scenario, with the exception of the
following fields:
Action. To see the specific changes, you will need to open the corresponding records.
The following image shows what the Changes for <Action> dialog box looks like when
you are viewing changes for an Internal Inspection Action.
Accessing the Changes for <Action>

Dialog Box
If a non-Active Scenario contains a System Action record whose values or values in
related records are different from the corresponding records in the Active Scenario, you
can view the differences between the records using the following instructions. After you
review the differences, if desired, you can update the System Action record in the current
Scenario so that its values will match the values in the Active Scenario.
To access the Changes for <Action> dialog box:
Asset element whose System Action record whose differences you want to view.
2. In the grid in the Actions pane, select the System Action record whose differences
you want to view.
3. Below the grid in the Actions pane, click the Show Changes button.
The Changes for <Action> dialog box appears, where <Action> is the value in the Name
field in the selected System Action record.
Updating Actions to Reflect the Active

Scenario
If a Scenario contains a System Action record whose values are different from the
corresponding System Action record in the Active Scenario, you can update the System
Action record in the non-Active Scenario so that its values are identical to the values in
the corresponding System Action record in the Active Scenario. You can update a System
Action record only if an Asset element is selected in the Diagram Hierarchy pane and the
selected System Action record is somehow different from the corresponding System
Action record.
You will know that a System Action record is somehow different from the corresponding
System Action record in the Active Scenario if the row in which it appears contains the
icon or the icon.
Note: Before you update a System Action record, you might want to click the Show
Changes button so that you can see how the System Action record in this Scenario differs
from the one in the Active Scenario.
To update Actions, you must be logged in as a Super User or member of the MI ASM
To update a System Action record so that its values match the values in the corresponding
System Action record in the Active Scenario:
Asset element whose System Action record you want to update.
2. In the grid in the Actions pane, select the System Action record that you want to
update.
3. Below the grid in the Actions pane, click the Undo Action button.
The System Action record is updated so that its values are identical to the values in the
corresponding System Action record in the Active Scenario.
Deleting Actions
To delete and Action, you must be logged in as a Super User or member of the MI ASM
Note: You can delete an Action only from a non-Active Scenario.
To delete an Action:
element whose Action you want to delete.
2. In the grid in the Actions pane, select the Action that you want to delete.
3. Under the grid in the Actions pane, click the Delete Action button.
A confirmation message appears, asking if you really want to delete the Action.
The Action is removed from the grid in the Asset Strategy Optimization Scenarios Actions page.
About Global Events

A Global Event is an optional component of a Scenario that groups together Actions
requiring a shutdown so that they will be performed at the same time, thereby
maximizing availability. The information for a Global Event is stored in a System Global
Event record.
For instance, consider our ASO Analysis Example, where the Proposed Scenario contains
two Actions that require a shutdown: Redesign Impellers and Replace Seals. The
Redesign Impellers Action has a duration of one week, and the Replace Seals Action has
a duration of one day. Performed independently of one another, they would result in a
shutdown lasting eight days total.
Now, assume that you group the two Actions together using a Global Event, which
specifies that the two Actions would be performed together during the same shutdown.
Managing the Actions in this way would result in a shutdown lasting the longest of the
two durations, or seven days. This approach is preferable, as it would save one day of
cost associated with the shutdown.
ASO Analyses support the use of two types of Global Events:
Date-driven: A Global Event that starts on a certain date.

Action-driven: A Global Event that starts based upon a driving Action.
When you create a Global Event, any Actions that are selected to be assigned and that fall
into a certain time period are performed simultaneously. The execution of the group of
Actions together is the Global Event. The qualifying time period is defined by the values
in the Max Delay and Max Advance Durations fields in the System Global Event record.
Note: While Global Events help limit downtime, the effects of Global Events are not
presented explicitly anywhere in the simulation results. The effects of the Global Events
are exhibited as less downtime, which means lower lost production costs.
Global Events Pane

The Global Events pane appears on the Asset Strategy Optimization Scenarios - Global
Events page and displays the Global Events that are associated with the Scenario that you
are currently viewing. In the following image, the Global Events pane is outlined in red.
The grid in the Global Events pane contains the following columns:
Flag: Contains an icon indicating the status of the System Global Event record
relative to the corresponding System Global Event record that belongs to the
Active Scenario.
If you are viewing System Global Event records that belongs to the Active
If you are viewing System Global Event records that belongs to a nonActive Scenario (i.e., the Scenario list above the grid does not contain the
value Active) and the System Global Event record is identical to the
corresponding System Global Event record in the Active Scenario, the
Flag column will not contain an icon.
value Active) and the System Global Event record does not have a
Flag column will contain the
icon.
value Active) and the System Global Event record is different from the
Flag column will contain the
icon.
value Active) whose System Scenario record was created from scratch
(i.e., the System Scenario was not copied from another System Scenario
record), the Flag column will contain the
icon.
Name: Displays the value stored in the Name field of the System Global Event
record.
Description: Displays the value stored in the Description field of the System
Global Event record.
Driver Type: Displays the value stored in the Driver Type field of the System
Global Event record.
Below the grid in the Global Events pane, the following buttons appear:
Add Global Event: Displays the New Global Event window, where you can create
a new System Global Event record. This link is enabled only if you are logged in
as a Super User or member of the MI ASM Analyst Security Group.
Delete Global Event: After asking for confirmation, deletes the System Global
Event record that is currently selected in the grid in the Global Event pane. This
link is enabled only if you are logged in as a Super User or member of the MI
Undo Global Event: Causes the System Global Event record to be updated so that
its values are identical to the values in the corresponding System Global Event
record in the Active Scenario. Before you click the Undo Global Event button,
you might want to click the Show Changes button so that you can see how the
System Global Event record in this Scenario differs from the one in the Active
Scenario. This button is always disabled if you are viewing Global Events that
belong to the Active Scenario. If you are viewing Global Events that belong to
any other Scenario, this button is enabled only if the Global Event is somehow
different from the corresponding Global Event in the Active Scenario. This link is
enabled only if you are logged in as a Super User or member of the MI ASM
Show Changes: Displays the Changes for <Global Event> window, where
<Global Event> is the value in the Name field in the selected System Global
Event record. You can use this window to see the differences that exist between
values in this System Global Event record and values in the corresponding System
Global Event record in the Active Scenario. This button is always disabled if you
are viewing Global Events that belong to the Active Scenario. If you are viewing
Global Events that belong to any other Scenario, this button is enabled only if the
Global Event is somehow different from the corresponding Global Event in the
Active Scenario.
Actions to Align Pane

The Actions to Align pane appears on the Asset Strategy Optimization Scenarios - Global
Events page and displays the Actions that are currently assigned to the Global Event that
is selected in the Global Events pane. In the following image, the Actions to Align pane is
outlined in red.
The grid in the Actions to Align pane displays the following columns:
Name: Displays a hierarchy that displays the Actions, organized by Diagram

element, that can be aligned by a Global Event. For example, the preceding image
displays the Replace Seals and Redesign Impellers Actions, which are assigned to
the Water Pump Strategy element. In addition, you can see that the Water Pump
Strategy element belongs to the Water Collection Strategy element, which belongs
to the Water Bottling Strategy element.
Is Driver: Displays check boxes that allow you to identify driving Action(s) for
Action-driven Global Events.
Below the grid in the Actions to Align pane, the following button appears:
Assign Action: Displays the Assign Actions window, where you can select
Actions to assign to the current Global Event. This link is enabled only if you are
About Creating Global Events

To create a Global Event, you must complete two steps:
1. Create a System Global Event record.
2. Assign Actions to the Global Event.
Creating System Global Event Records

To create a System Global Event record, you must be logged in as a Super User or
To create a System Global Event record:
- Global Events page, below the grid in the Global Events pane, click the Add
Global Event button.
The New Global Event window appears, where you can create a new Global Event.
The content of the New Global Event window is controlled by the default datasheet that
is defined for the System Global Event family.
2. Define the properties of the System Global Event record as desired.
3. Click OK.
The System Global Event record is created and appears in the grid in the Global Events
pane.
About Assigning Actions to Global

Events
When you assign Actions to a Global Event, you select the Actions that will be executed
at the same time, as defined by the Global Event. Any Actions that should be performed
during the qualifying time period, as defined by the values in the Max Delay Duration
and Max Advance Duration fields, will be executed together.
Assigning Actions to Global Events

To assign Actions to Global Events, you must be logged in as a Super User or member of
To assign an Action to a Global Event:
- Global Events page, in the grid in the Global Events pane, in the Name column,
select the Global Event to which you want to assign Actions.
2. Below the grid in the Actions to Align pane, click the Assign Actions button.
The Assign Actions window appears, showing all of the Actions that exist for the
Scenario.
3. In the Is Selected column, select the check box for the Actions that you want to
assign to the selected Global Event.
4. If the Global Event is driven by Actions, in the Is Driver column, select the check
box for the Actions that you want to drive the selected Global Event.
Note:This column is disabled for date-driven Global Events.
5. Click OK.
Your selections are saved and appear in the Actions to Align pane.
Hint: If you want to select the Is Driver check box for an Action, you must first select the
Is Selected check box.
Removing Actions from Global Events

When you remove an Action from a Global Event, it will no longer be delayed or
advanced in time to be executed with the other grouped Actions in the Global Event.
To remove Actions from Global Events, you must be logged in as a Super User or
To remove an Action from a Global Event:
- Global Events page, in the grid in the Global Events pane, in the Name column,
select the Global Event that contains the Actions that you want to remove.
2. Below the grid in the Actions to Align pane, click the Assign Actions button.
The Assign Actions window appears.
3. In the Is Selected column, clear the check box for any Actions that you want to
remove from the Global Event.
4. Click OK.
Your changes are saved, and the Actions to Align pane is updated to reflect those
changes.
Modifying System Global Event

Records
To modify a System Global Event record, you must be logged in as a Super User or
To modify a System Global Event record:
- Global Events page, in the grid in the Global Events pane, click the hyperlinked
name of the System Global Event record that you want to modify.
The <Global Event> window appears, where <Global Event> is the name of the Global
Event that you selected.
2. Modify the properties of the System Global Event record as desired.

3. Click OK.
Viewing Differences Between the

Current Scenario's Global Events and
the Active Scenario's Global Events
If a non-Active Scenario contains a System Global Event record whose values are
different from the corresponding System Global Event record in the Active Scenario, you
can view the differences between the System Global Event records using the following
instructions. After you review the differences, if desired, you can update the System
Global Event record in the current Scenario so that its values will match the values in the
Active Scenario.
You will know that a System Global Event record is somehow different from the
corresponding System Global Event record in the Active Scenario if the row in which it
appears contains the
icon or the
only if the row contains the
icon. You can view the differences, however,
icon.
To view differences between a System Global Event record in the current Scenario and
the corresponding System Global Event record in the Active Scenario:
name of the System Global Event record whose differences you want to view.
2. Below the grid in the Global Events pane, click the Show Changes button.
The Changes for <Global Event> dialog box appears, where <Global Event> is the value
in the Name field in the selected System Global Event record.
The Changes for <Global Event> dialog box contains a grid that displays the following
columns:
corresponding System Global Event record in the Active Scenario. For
example, in the preceding image, you can see that the value in the Max
Advance Duration field is different between the System Global Event
record in the current Scenario and the Active Scenario.
Old Value: The value in the System Global Event record in the Active
Scenario
New Value: The value in the System Global Event record in the current
Scenario.
Updating Global Events to Reflect the

Active Scenario
If a Scenario contains a System Global Event record whose values are different from the
corresponding System Global Event record in the Active Scenario, you can update the
System Global Event record in the non-Active Scenario so that its values are identical to
the values in the corresponding System Global Event record in the Active Scenario. You
can update a System Global Event record only if the selected System Global Event record
is somehow different from the corresponding System Global Event record.
You will know that a System Global Event record is somehow different from the
corresponding System Global Event record in the Active Scenario if the row in which it
appears contains the
icon or the
icon.
Note: Before you update a System Global Event record, you might want to click the
Show Changes button so that you can see how the System Global Event record in this
Scenario differs from the one in the Active Scenario.
To update a Global Event, you must be logged in as a Super User or member of the MI
To update a System Global Event record so that its values match the values in the
corresponding System Global Event record in the Active Scenario:
name of the System Global Event record that you want to update.
2. Below the grid in the Global Events pane, click the Undo Global Event button.
The System Global Event record is updated so that its values are identical to the values in
the corresponding System Global Event record in the Active Scenario.
Deleting Global Events

To delete a Global Event, you must be logged in as a Super User or member of the MI
To delete a Global Event:
- Global Events page, in the grid in the Global Events pane, select the Global
Event that you want to delete.
2. Below the grid in the Global Events pane, click the Delete Global Event button.
A confirmation message appears, asking if you really want to delete the selected Global
Event.
The Global Event is removed from the grid in the Global Events pane and the System
Global Event record is deleted from the database.
About Resources
Resources are optional components in an ASO Analysis that represent physical parts or
materials, such as spare bearings or seals, or human resources, such as mechanics or
technicians, that you may want to use within the analysis. You can create a Resource by
defining its properties via the Resources window, which is shown in the following
image.
The properties of a Resource are stored in a System Resource record, which is created
when you save a new Resource.
After Resources exist for an ASO Analysis, you can assign them to Actions and Risks to
tie the resource and its cost with an occurrence of the associated event. For example, if
you planned to create an Action that would perform certain maintenance actions, you
might create a Mechanic Resource and assign the Mechanic to the Action.
Associating a Resource with an Action or a Risk will create a System Resource Usage
Record, which is linked to the appropriate System Action or System Risk record, which
will store information that specifics how the resource will be used (e.g., the quantity and
duration).
About Adding Resources to Analyses

You have two options for adding Resources to an ASO Analysis. You can:
Create new Resources from scratch.

Import Resources that already exist in other ASO Analyses.
Note: Resources can also be created within the context of Actions and Risks. Doing so
will cause those Resources to be available at the analysis level so that they can be
assigned to other Actions and Risks.
Accessing the Resources Window

To access the Resources window:
While viewing the desired ASO Analysis on any page, on the Tools menu, click
the Resources link.
The Resources window appears.
Aspects of the Resources Window

The Resources window appears when you click the Resources link on the Tools menu in
ASO.
The Resources window contains a grid, where each row displays a separate System
Resource record. The following columns of information are displayed in the grid by
default:
Name
Description
Fixed Cost
Variable Cost
Variable Cost Units
You can click the hyperlinked value in the Name cell to view the Resource datasheet for
that resource.
Add New: Displays the Add New Resource window, where you can create a new
System Resource record from scratch. This link is enabled only if you are logged
in as a Super User or member of the MI ASM Analyst Security Group.
Import: Displays the Resource Finder window, where you can select the System
Resource record that you want to import. This link is enabled only if you are
Delete: After asking for confirmation, removes the selected row from the grid.
The System Resource record will be deleted from the database when you save
your changes to the ASO Analysis. This link is enabled only if you are logged in
as a Super User or member of the MI ASM Analyst Security Group.
Help: Displays the context-sensitive Help topic for the Resources window.
Close: Closes the Resources window.
Creating Resources from Scratch

To create a Resource for ASO, you must be logged in as a Super User or member of the
To create a new Resource for an ASO Analysis:
1. Access the Resources window.
The Resource window appears.
2. On the Resources window, click the Add New button.
The Add New Resource window appears.
The Add New Resources window displays the default datasheet that has been defined for
the System Resource family.
3. Define the properties of the System Resource record as desired.
4. Click OK.
The Resource is created and appears in the grid on the Resources window.
Importing Existing Resources
When you import a Resource from one ASO Analysis into another ASO Analysis, the
Meridium APM system creates a copy of the existing System Resource and links the new
record to the root System Analysis record of the target analysis.
To import an existing Resource, you must be logged in as a Super User or member of the
To import a Resource from one analysis into another:
1. Open the ASO Analysis into which you want to import the Resource.
2. Access the Resources window.
3. Click the Import button.
The Resource Finder window appears, which displays the Resources that are available to
be imported.
4. Select the row containing the Resource that you want to import.
5. Click OK.
A copy of the System Resource record is created, and the imported Resource appears on
the Resources window.
Modifying Resources
To modify a Resource, you must be logged in as a Super User or member of the MI ASM
To modify an existing Resource:
the Resources link.
The Resources window appears.

2. Click the hyperlinked name of the Resource that you want to modify.
The <Resource Name> dialog box appears, where <Resource Name> is the name of the
System Resource record that you selected.
The <Resource Name> window displays the default datasheet that has been defined for
the System Resource family. This image displays the Vibration Technician window,
which defines the properties for the Vibration Technician System Resource record.
3. Modify the fields in the System Resource record as desired.
4. Click OK.
Deleting Resources
To delete a Resource, you must be logged in as a Super User or member of the MI ASM
To delete a Resource:
the Resources link.
2. Select the row containing the System Resource record that you want to delete.
A confirmation message appears, asking if you really want to delete the Resource.
The Resource is removed from the grid in the Resources window. The System Resource
record will be deleted from the database when you save your changes to the ASO
Analysis.
About Running Simulations

When you run a simulation, you start the process of running Monte Carlo iterations for
each Scenario in an ASO Analysis and viewing the results calculated from those
simulations.
You will want to run the simulation after the ASO Analysis is created for the first time
and if you make changes to the ASO Analysis that would affect the simulation results,
such as changing the simulation parameters or modifying a Scenario. When you run the
simulation, the Diagram is validated. If the Diagram is valid or contains only Isolated
Element errors, then:
If changes have been made to the analysis parameters, all Scenarios will be
included in the simulation run.
If no changes have been made to any of the analysis parameters, only the
Scenarios that have been modified since the last simulation was run will be
included in the new simulation run.
If no changes have been made to the analysis parameters or any of the Scenarios,
a message appears, indicating that no changes have been made.
Note: If no changes have been made to the analysis parameters or any of the Scenarios,
but the Random Seed or Event Log check box is selected, then the simulation will include
every Scenario in the new simulation run.
Keep in mind that it will take time to run simulations. Various factors influence the speed
of the simulation process, including:
The number of iterations defined.

The complexity of the Scenarios (i.e., the number of pieces of equipment or
locations, Risks, Actions, and Subsystems).
The frequency at which actions occur.
The frequency at which failures occur.
To shorten the run time of your simulation, you can reduce the number of iterations or the
complexity of the analysis.
You can run only one simulation at a time. While a simulation is running, however, you
can continue working in other areas of the Meridium APM Framework by:
Clicking anywhere on the Meridium APM Framework main window outside the
Run Simulation dialog box. When you do so, the simulation will continue to run
in the background, and the dialog box will be hidden behind the Meridium APM
Framework window. When the simulation finishes, the dialog box will be returned
to focus automatically.
Clicking either the minimize or the close button on the Run Simulation dialog
box. When you do so, the simulation will continue to run in the background, and
the minimized dialog box will appear on your Windows taskbar. When the
simulation finishes, the dialog box will be maximized and returned to focus
automatically.
-or-
Note: While a simulation is running, you cannot access or modify the associated Asset
Strategy. If you try to do so, an error message will appear, indicating the action cannot be
completed until the simulation is complete.
Options for Running Simulations

You have two options for running simulations:
Run the simulation from ASO.
Run the simulation from ASM.
-or-
The simulation results will be the same regardless of the starting point.
Running Simulations from ASO

To run a simulation, you must be logged in as a Super User or member of the MI ASM
To run a simulation from ASO:
1. On any page in ASO, on the Tools menu, click the Run Simulation link.
The Browse For Folder window appears, where you can select or create a folder in which
to store the Event Logs.
Note: If the Enable Event Log check box is cleared on the Asset Strategy Optimization
Analysis Definition page, the Browse For Folder dialog box will not appear.
2. Navigate to the location where you want to save the Event Logs.
3. Click OK.
Note: If there are already Event Logs files in the folder that you select, a warning
message will appear, stating that any existing Event Log files may be overwritten.
The Simulation Progress dialog box appears and displays the progress of the simulation.
The Asset Strategy Optimization Summary page appears.
About Event Logs

The Event Log is a diagnostic tool that lets you see what happens when you run
simulations for an ASO Analysis. When the value in the Enable Event Log field in the
root System Analysis record is set to True, when you run the simulation, one text file will
be produced for every iteration of every Scenario in the ASO Analysis that records every
event that happens in the iteration. Each file is named <Scenario Name>-<Iteration
Number>.txt where:
<Scenario Name> is the name of the Scenario in the ASO Analysis.

<Iteration number> is the number of the iteration that is detailed in the file.
The Event Log files can be saved to any desired location when you run a simulation. The
Event Log files are produced as text files, but can be opened in Microsoft Excel, where
you will see the following columns of information:
Time: The start time, in days, of the event.

Name: The name of the Action, Risk, or element, as defined in its record, that is
detailed in the row.
Event: The event that is detailed in the row. The possible events that can be listed
are:
Alert: A condition monitoring Action identifies a potential failure.
Complete: An Action is complete.
Complete Unplanned Correction: A planned correction has finished repairs

to an element that has failed.
Failed: An element has failed. It will have to be replaced or repaired

before it can run again.
Running: The element is running.
Schedule next <Action> in <Number> Days: A Global Event has changed

the schedule of an Action, where <Action> is the name of the Action that
has been rescheduled and <Number> is the number of days until the next
occurrence of the Action.
Shutdown: An element is stopped because an Action has turned it off.
Simulation Ends: The simulation is complete.
Standby: A Switch element is turned off.
Start: An Action starts.
Start Unplanned Correction: An unplanned correction has started repairs

to an element that has failed.
Stopped: The element is stopped.
Path: The location in the Diagram of the item associated with the event.
Understanding the Content of the Event

Log
The Event Log in ASO works exactly like the Event Log in System Reliability.
Refreshing Multiple Distributions

Using the Refresh Distributions link on the Tools menu refreshes all the distribution data
that was associated with Risks in the ASO Analysis. To refresh Distributions, you must be
logged in as a Super User or member of the MI ASM Analyst Security Group. The
following instructions assume that you have the privileges that are required to perform
the task.
To refresh multiple Distributions:
the Refresh Distributions link.
A confirmation message appears, asking if you really want to refresh all distributions
having associated distributions.
2. Click OK.
The distribution data is refreshed.
Setting a Scenario as the Proposed

Scenario
When you create an ASO Analysis, the Proposed Scenario is created by default. You can
keep this Scenario as the Proposed Scenario, or you can set another customer-defined
Scenario as the Proposed Scenario. When you do so, the values in that customer-defined
Scenario will be transferred to the Proposed Strategies that are included in the ASO
Analysis.
To set a Scenario as the Proposed Scenario, you must be logged in as a Super User or
To set a Scenario as the Proposed Scenario:
containing a Scenario that you want to set as the Proposed Scenario.
2. In the grid within the Scenarios section, select the row containing the Scenario
that you want to set as the Proposed Scenario.
3. Below the grid, click the Set As Proposed button.
The selected Scenario is set as the Proposed Scenario and flagged with the icon in the
grid. In addition, the values in that Scenario are transferred to the Proposed Strategies that
are included in the ASO Analysis.
Managing Strategies that are Included

in an ASO Analysis
After a strategy has been included in an ASO Analysis, you can manage the strategy
using ASM. You will know that a strategy has been included in an ASO Analysis if the
value in the Risk Analysis Type list on the Strategy Definition page is Simulation. When
an ASO Analysis includes a strategy, each time you navigate to the strategy (assuming
that you have not changed the value in the Risk Analysis Type field manually to
Qualitative), the results will reflect the information in ASO.
Some restrictions will apply to how you can manage strategies that are included in an
ASO Analysis. The following subsections indicate which actions are always allowed,
which are always restricted, and which are restricted depending upon certain conditions.
Always Allowed
The following actions are always allowed for strategies that are included in ASO
Analysis:
Creating new Actions or Risks.

Modifying values in Actions or Risks.
Copying Risks.
Undoing Actions or Risks.
Removing Actions or Risks.
Assigning new or existing Actions to Risks.
Assigning new or existing Risks to Actions.
Defining the unmitigated risk rank (non-financial and financial) for any new
Risks that are created after the analysis was last accessed.
Applying an Asset Strategy Template as a non-master template to the Asset

Strategy.
Always Restricted
The following actions are always restricted for Asset Strategies that are included in ASO
Analysis:
Modifying the unmitigated risk rank (non-financial or financial) for any Risk that
existed when the analysis was last accessed.
Note: The unmitigated risk rank and unmitigated financial risk rank are still displayed in
the Risks pane on the Asset Strategy Risks page, but the values are not hyperlinks. This
means that you cannot access the Risk Matrix to view the risk ranks.
Modifying the mitigated risk rank (non-financial or financial) for any Action that
existed when the analysis was last accessed or defining the mitigated risk rank for
any new Actions that are created after the analysis was last accessed.
Note: By default, the mitigated risk rank and mitigated financial risk ranks are not
displayed in the Mitigating Actions pane on the Asset Strategy Risks page. This means
that you cannot access the Risk Matrix to view the mitigated risk ranks.
In the Risk Analysis, viewing the Actions pane.
Applying an Asset Strategy Template as a master template to the Asset Strategy.
Conditionally Restricted
Managing Asset Strategy states. Note the conditions:
If an ASO Analysis includes a System Strategy or Unit Strategy, you

cannot transition the state of individual Asset Strategies that belong to the
System or Unit Strategy.
If an Asset Strategy is included in an ASO Analysis and you change a
value that causes the simulation results to become invalid (i.e., the
simulation needs to be rerun), you cannot change the state of the Asset
Strategy.
About Additional ASM Graphs

After a strategy is included in an ASO Analysis, when you open that strategy, you will see
the following additional graphs in the Risk Analysis and on the Review Strategy page:
Risk Trend
Total Cost
Total Cost Trend
Risk Trend Graph

After a strategy is included in an ASO Analysis, when you view the Risk Analysis or the
Strategy Review page for that strategy, you will see the Risk Trend graph. The following
image shows an example of the Risk Trend graph in ASM.
Note: The labels have been added to the graph in the image. In the baseline graph, the
labels do not appear.
The Risk Trend graph in ASM displays the average (across all iterations) total risk of
each Scenario for each analysis year or month, as defined by the value in the Time
Analysis Type field in the root System Analysis record. If the Time Analysis Type field is
set to:
Yearly, the Risk Trend graph will display the risk for each year included in the
simulation period.
Monthly, the Risk Trend graph will display the risk for each month included in
the simulation period.
The numbers that you see on the Risk Trend graph in ASM can also be seen in the
simulation results in the ASO Analysis. Consider the following example, where the Risk
Trend graph in ASM shows that for this Asset Strategy (Water Pump Strategy), the active
risk for the first year is 183.73:
If you were to view the simulation results in the ASO Analysis that includes the Water
Pump Strategy, you would see this same information. Specifically, you could view the
Risk Trend Plot for the Active Scenario and the Water Pump Strategy element. The risk
for the first year would be the same: 183.73.
If desired, while viewing the Risk Trend graph, you can modify the graph to display the
risk for each risk category that is included in the selected Scenario (i.e., Unmitigated,
Proposed, or Active). To do so, below the x-axis, select the Risk Category option.
Additionally, you can modify the graph to display the risk for each Risk that is included
in the selected Scenario. To do so, below the x-axis, select the Each Risk option.
Total Cost Graph

Strategy Review page for that strategy, you will see the Total Cost graph. The following
image shows an example of the Total Cost graph in ASM.
The Total Cost graph in ASM displays the average (across all iterations) total cost of each
Scenario for the entire simulation period.
The numbers that you see on the Total Cost graph in ASM can also be seen in the
simulation results in the ASO Analysis. Consider the following example, where the Total
Cost graph in ASM shows that for this Asset Strategy (Water Pump Strategy), the active
cost for the simulation period is $754,071.63.
Pump Strategy, you would see this same information. Specifically, in the Elements grid,
you could view the value in the Cost (USD) column for the Active Scenario and the
Water Pump Strategy element. The cost would be the same: $754,072. You can see this
value highlighted in blue in the following image.
Note: The cost is rounded to the nearest dollar in the Elements grid.
If desired, while viewing the Total Cost graph, you can modify the graph to display the
cost for each cost type that is included in the selected Scenario (i.e., Unmitigated,
Proposed, or Active). To do so, below the x-axis, select the Cost Type option.
Additionally, you can modify the graph to display the cost for each Risk that is included
in the selected Scenario. To do so, below the x-axis, select the Each Risk option.
Total Cost Trend Graph

Strategy Review page for that strategy, you will see the Total Cost Trend graph. The
following image shows an example of the Total Cost Trend graph in ASM.
The Total Cost Trend graph in ASM displays the average (across all iterations) total cost
of each Scenario for each analysis year or month, as defined by the value in the Time
Analysis Type field in the root System Analysis record. If the Time Analysis Type field is
set to:
Yearly, the Total Cost Trend graph will display the cost trend for each year
included in the simulation period.
Monthly, the Total Cost Trend graph will display the cost trend for each month
included in the simulation period.
The numbers that you see on the Total Cost Trend graph in ASM can also be seen in the
simulation results in the ASO Analysis. Consider the following example, where the Total
Cost Trend graph in ASM shows that for this Asset Strategy (Water Pump Strategy), the
active cost for the first year is $105,401.25.
Pump Strategy, you would see this same information. Specifically, you could view the
Cost Trend Plot for the Active Scenario and the Water Pump Strategy element. The cost
for the first year would be the same: $105,401.
If desired, while viewing the Total Cost Trend graph, you can modify the graph to display
the cost trend for each cost type that is included in the selected Scenario (i.e.,
Unmitigated, Proposed, or Active). To do so, below the x-axis, select the Cost Type
option. Additionally, you can modify the graph to display the cost trend for each Risk that
is included in the selected Scenario. To do so, below the x-axis, select the Each Risk
option.
Understanding the Analysis Results

When you run a Monte Carlo simulation, the Meridium APM system analyzes statistics
about cost, performance, and reliability from the iterations of the Scenarios to calculate
the simulation results. The data is presented in the Asset Strategy Optimization Summary
page and the Asset Strategy Optimization Simulation Results page.
The Asset Strategy Optimization Summary page provides an overview of the costs and
Resource statistics for the simulation using the following graphs:
Annual Action Cost

Action Cost Trend
Total Cost
Total Cost Trend
Risk
Risk Trend
Resource Occurrence
Resource Time
Resource Cost
The simulation results are also presented in more detail on the Asset Strategy
Optimization Simulation Results page. The following tabs are used to organize the data
on the System Reliability Simulation Results page:
Elements
Actions
Resources
By clicking a cell in any of these three grids, you can view more detailed information in
the following plots:
Histogram Plot graph

Trend Plot graph
Impact Plot graph
Total Cost Graph

The Total Cost graph on the Asset Strategy Optimization Simulation Results page works
exactly like the Cost graph in System Reliability.
Note: In ASO, the Total Cost graph contains information for the Unmitigated, Active, and
Proposed Scenario and information for any customer-defined Scenario. In System
Reliability, there is no Unmitigated, Active, or Proposed Scenario, so the Cost graph
contains only information for customer-defined Scenarios. Keep this distinction in mind
when viewing the System Reliability Analysis example of the Cost graph.
Total Cost Trend Graph

The Total Cost Trend graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Cost Trend graph in System Reliability.
Note: In ASO, the Total Cost Trend graph contains information for the Unmitigated,
Active, and Proposed Scenario and information for any customer-defined Scenario. In
System Reliability, there is no Unmitigated, Active, or Proposed Scenario, so the Cost
Trend graph contains only information for customer-defined Scenarios. Keep this
distinction in mind when viewing the System Reliability Analysis example of the Cost
Trend graph.
Risk Graph
The Risk graph on the Asset Strategy Optimization Summary page displays the average
total risk of each Scenario across all iterations, broken down into Operations,
Environment, and Safety risk categories.
Each Risk has three separate risk ranks that fall into the following risk categories:
Operations, Environment, and Safety. In other words, each Risk has an Operations risk
rank, an Environment risk rank, and a Safety risk rank. In this section of the
documentation, these risk ranks are referred to as risk category risk ranks.
Each bar on the graph represents a separate Scenario, and each bar is divided into
sections that represent the three separate risk categories for the Risks in that Scenario. Per
Scenario, the value for each risk category is calculated as the sum of the calculated risk
ranks (not the risk category risk ranks) for ALL Risks in the Scenario that fall into that
category.
The calculated risk rank for a Risk is determined using the following equation:
Calculated Risk Rank = # Failures x Risk Category Risk Rank
...where:
# Failures is the calculated number of failures for that Risk. This value is
calculated automatically when you run the simulation and is displayed on the
Element tab on the Asset Strategy Optimization Simulation Results page.
Consider the following image, where the number of failures for the Lubricant
Loss Risk is highlighted in blue.
Risk Category Risk Rank is the Operation, Environment, or Safety risk rank for
that Risk (which can be accessed by clicking the hyperlinked Qualitative
Consequence value on the Asset Strategy Optimization Scenarios - Risks page).
Consider the following image, where the Safety risk rank is 100.
This explanation is best understood through an example. Consider the following table,
which shows for a Proposed Scenario the Risks, number of failures per Risk, Safety risk
ranks per Risk, and calculated risk ranks per Risk.
Calculated Risk Rank
Risk
Number of
Safety Risk
Failures
Rank
(# Failures x Safety Risk

Rank)
Seal Leak
1.49
100
149
Casing Leak
1.52
1.52
Motor (Driver) Failure
1.49
1.49
Sub-component
Failure
1.51
1.51
Lubricant Loss
1.51
10
15.1
Misalignment
1.48
1.48
Lubricant Degradation
5.01
5.01
Bearing Failure
1.51
1.51
Impeller Wear
1.51
1.51
You can see that the calculated safety risk rank for each Risk is the number of failures
multiplied by the safety risk rank for that Risk. If you were to add all of the calculated
risk ranks together, the result would be 178.13. The graph, therefore, would display a
value close to 178.13 as the Safety risk rank for the Proposed Scenario, as shown in the
following image, where the value is 178.28
Note: The value on the graph will not be the exact sum of the calculated risk ranks due to
rounding. The number of failures that appears in the simulation results is rounded, but the
values used to generate the graph are not rounded.
Note: If you prefer to see the various risk rank values for ALL risk categories added
together and presented in a single column for each Scenario, select the Show Total check
box in the upper right corner of the plot.
Risk Trend Graph

The Risk Trend graph on the Asset Strategy Optimization Summary page displays the
average (across all iterations) total risk of each Scenario for each analysis year or month,
as defined by the value in the Time Analysis Type field in the root System Analysis
record. If the Time Analysis Type field is set to:
Yearly, the Risk Trend graph will display the risk for each year included in the
simulation period.
Monthly, the Risk Trend graph will display the risk for each month included in
the simulation period.
This image shows an example of the Risk Trend graph and presents the average total risk
for all categories for each year in the analysis period. Note the following details about
this example:
The years 2012 and 2017 represent partial years, so the results from those two
years do not represent a full 12 months.
2012 represents almost 10 months, from 2/6/2012 (the date the simulation
was run) to 12/31/2012 (the last day of the year in which the simulation
was run).
2017 represents a little over 1 month, from 1/1/2017 (the first day of the
year in which the simulation period ends) to 2/5/2017 (the current day, n
years from the day the simulation was run, where n is the simulation
period).
The risk for the Unmitigated Scenario is the highest in 2014 and the lowest in
2017.
The risk for the Active Scenario is the highest in 2015 and the lowest in 2017.
The risk for the Proposed Scenario is the highest in 2015 and the lowest in 2017.
The numbers that appear on the Risk Trend graph in the analysis summary also appear on
the Trend Plot graph in the simulation results. For example, consider the following Risk
Trend graph, which appears in the analysis summary. You can see that for the Active
Scenario, the Risk in 2012 is 1,476.44.
If you were to view the Trend Plot graph for the Active Scenario in the simulation results,
you would see a screen like this, where the Trend Plot graph shows that the Risk in 2012
for the Active Scenario is 1,476.44. A red outline has been added to the following image
to highlight the Trend Plot graph.
Resource Occurrence Graph

The Resource Occurrence graph on the Asset Strategy Optimization Simulation Results
page works exactly like the Resource Occurrence graph in System Reliability.
Note: In ASO, the Resource Occurrence graph contains information for the Unmitigated,
System Reliability, there is no Unmitigated, Active, or Proposed Scenario, so the
Resource Occurrence graph contains only information for customer-defined Scenarios.
Keep this distinction in mind when viewing the System Reliability Analysis example of
the Resource Occurrence graph.
Resource Time Graph

The Resource Time graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Resource Time graph in System Reliability.
Note: In ASO, the Resource Time graph contains information for the Unmitigated,
System Reliability, there is no Unmitigated, Active, or Proposed Scenario, so the
Resource Time graph contains only information for customer-defined Scenarios. Keep
this distinction in mind when viewing the System Reliability Analysis example of the
Resource Time graph.
Resource Cost Graph

The Resource Cost graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Resource Cost graph in System Reliability.
Note: In ASO, the Resource Cost graph contains information for the Unmitigated, Active,
and Proposed Scenario and information for any customer-defined Scenario. In System
Reliability, there is no Unmitigated, Active, or Proposed Scenario, so the Resource Cost
graph contains only information for customer-defined Scenarios. Keep this distinction in
mind when viewing the System Reliability Analysis example of the Resource Cost graph.
Annual Action Cost Graph

The Annual Action Cost graph on the Asset Strategy Optimization Simulation Results
page works exactly like the Cost of Actions graph in Asset Strategy Management (ASM).
with one exception. The Cost of Actions graph in ASM includes an additional option,
Show Cost By, that does not appear on the Annual Action Cost graph in ASO.
Action Cost Trend Graph

The Action Cost Trend graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Cost Projection graph in Asset Strategy Management (ASM). with
one exception. The Cost Projection graph in ASM includes an additional option, Show
Cost By, that does not appear on the Action Cost Trend graph in ASO.
Elements Tab
The Elements tab on the Asset Strategy Optimization Simulation Results page works
exactly like the Elements tab in System Reliability.
Actions Tab
The Actions tab on the Asset Strategy Optimization Simulation Results page works
exactly like the Actions tab in System Reliability.
Resources Tab
The Resources tab on the Asset Strategy Optimization Simulation Results page works
exactly like the Resources tab in System Reliability.
Histogram Plot Graph

The Histogram Plot graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Histogram Plot graph in System Reliability.
Trend Plot Graph
The Trend Plot graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Trend Plot graph in System Reliability.
Impact Plot Graph

The Impact Plot graph on the Asset Strategy Optimization Simulation Results page
works exactly like the Impact Plot graph in System Reliability.

System Condition Monitor records store details about continuous, condition-based
maintenance Actions. The following table provides an alphabetical list and description of
the fields that exist for the System Condition Monitor family. The information in the table
Field
Data
Type
Description
Behavior and Usage
A number that specifies the

cost associated with any
materials or personnel needed
On the System Condition Monitor
to complete the Action. For
datasheet, this field appears as a
Action Cost Number
text box. You can remove the
records, this value represents a
default value and type a number
one-time expense that is
directly in the Action Cost cell.
incurred when the Action is
started. This field contains the
value 0 by default.
Action Type Character The category into which the This field is disabled on the
Action can be classified. By System Condition Monitor
default, this field contains the datasheet.
value Condition-Based
(CM) .
Indicates whether the Action
Condition
occurs continuously or
This field is disabled on the
Monitoring Character periodically, at regular
Type
intervals. By default, this field datasheet.
contains the value Continuous.
On the System Condition Monitor
Description Text
text box with a

button. You
Additional information about
can enter you own value directly
the action.
in the Description cell or click the
button to view the Text
Editor.
On the datasheet, this field
appears as a text box labeled
Detection Probability (%). You
remove the default value and type
a number directly in the cell.
A number representing the

probability that the action will
Detection
identify a potential failure
Number
Probability
resulting from any Risk
assigned to that Action and
correct the potential failure.
GUID
For an Action with no assigned

Risks, any value stored in this
field will be ignored.
For example, a System Condition
Monitor record with the
Detection Probability value 50
has a 50% chance of identifying a
potential failure resulting from a
Risk. In other words, the action
will detect one out of two
potential failures resulting from
any Risks assigned to the Action.
By default, this field contains the
value 100.
Character A value that uniquely

This field is disabled and not
identifies the record within an included on the datasheet by
ASO Analysis. The value that default.
exists in this field is generated
automatically by the Meridium
APM system and should not

be modified as it is required
for the proper functioning of
ASO.
Mandatory Logical This field is not used in ASO. N/A
On the datasheet, this field
appears as a text box. You can
enter your own value directly in
the Name cell.
Name
Character The name of the action.
This value is used to identify

Actions in ASO Analyses. For
instance, the Name column
appears by default in the grid in
the Actions pane on the Asset
Strategy Optimization Scenarios Actions page and displays values
that exist in the Name field to
identify the System Action
records that are displayed in the
grid.
System Inspection
System Inspection records store details about periodic, condition-baed maintenance
Actions. The following table provides an alphabetical list and description of the fields
that exist for the System Inspection family. The information in the table reflects the
baseline state and behavior of these fields. This list is not comprehensive.
Field
Data
Type
Description
Action Cost Number A number that specifies the

to complete the action. For
System Inspection records,
this value represents an
Behavior and Usage
On the System Inspection

expense that is incurred every

time the action occurs. This
field contains the value 0 by
default.
The category into which the
Character action can be classified. By
default, this field contains the This field is disabled on the
Action Type
value Condition-Based
System Inspection datasheet.
(CM).
Indicates whether the action
Condition
occurs continuously or
Monitoring Character periodically, at regular
System Inspection datasheet.
Type
intervals. By default, this field
contains the value Periodic.
Description Text
text box with a

button. You
Additional information about
can enter you own value directly
the action.
in the Description cell or click the
button to view the Text

Editor.
A number representing the
Detection Number probability that the action will datasheet, this field appears as a
identify a potential failure
text box labeled Detection
Probability
resulting from any Risk and Probability (%). You remove the
correct that failure before it
occurs. For an Action with no directly in the cell.
assigned Risks, any value
stored in this field will be
An action can detect a potential
ignored.
failure only when the action
occurs during a Risk's PF Interval,
as defined by the value in the PF
Interval and PF Interval Units
fields in the System Risk record.
If the action does not occur during
the PF Interval, the action cannot
identify the potential failure, and
the value in the Detection
Probability field will be ignored.
To make the action occur during

the PF Interval of a Risk, you can
manually modify the values in the
PF Interval and PF Interval Units
fields of the System Risk record,
or you can optimize the Action.
For example, setting the
Detection Probability to 50 would
indicate that the Action has a 50%
chance of identifying a potential
failure resulting from any risk if
the action occurs during the PF
Interval of the Risks. In other
words, the action will detect one
out of two potential failures
resulting from any Risks assigned
to the Action when the action
occurs during the PF Interval of
the Risks.
Duration
A number that, combined with

the value in the Duration Units
field, identifies the total time
required to complete the
action. For example, if the
value in the Duration field is 4 text box. You can remove the
and the value in the Duration default value and enter your own
Number
Units field is Hours, then the value directly in the Duration cell.
action will take four hours to
complete.
This field contains the value 0
by default.
Duration
Units
GUID

The time units associated with
list with a blank caption and
the value in the Duration field.
Character
contains the following units:
By default, this field contains
Minutes, Hours, Days, Weeks,
the value Days.
Months, or Years. You can select
a value from this list.
Character A value that uniquely
identifies the record within an included on the datasheet by
ASO Analysis. The value that default.
Interval

automatically by the
Meridium APM system and
should not be modified as it is
required for the proper
functioning of ASO.
the value in the Interval Units
field, indicates how often the
action will occur. For
example, if the value in the
Interval field is 4 and the
value in the Interval Units
Number field is Months, then the
action will occur every four
months during the simulation
period.

default value and enter your own
value directly in the Interval cell.
This field contains the value 1

by default.
Interval
Units

The time units associated with datasheet, this field appears as list
the value in the Interval field. with a blank caption and contains
Character
By default, this field contains the following units: Minutes,
the value Days.
Hours, Days, Weeks, Months, or
Years.
Name

text box. You can enter your own
value directly in the Name cell.
This value is used to identify
Actions in the ASO Analyses. For
instance, the Name column
appears by default in the grid in
the Actions pane on the Asset
Strategy Optimization Scenarios Actions page and displays values
that exist in the Name field to
identify the System Action
records that are displayed in the
grid.

check box labeled One Time
Action. This check box is clear by
default, indicating that the action
will occur more than once. You
can select this check box to
indicate that an action will occur
one time.
One Time
Action
Shutdown
Required

For example, an action to inspect
will occur one time or will be
the vibration level of a pump
repeated more than once.
Logical
might occur several times a year.
In this case, the One Time Action
check box in the corresponding
System Inspection record would
be clear. An action to inspect a
newly installed pump for any
installation errors might occur
only once, however, in which case
the One Time Action check box in
the corresponding System
Inspection record would be
selected.
Indicates whether the action On the System Inspection
Logical requires the piece of
equipment or location to be
check box labeled Shutdown
shut down in order for the
Required. This check box is clear
action to be completed or can by default, indicating that the
be completed while the piece piece of equipment or location
of equipment or location is
does not need to be shut down for
running.
the action to be completed. You
select this check box to indicate
that the piece of equipment or
location must be shut down for
the action to be completed.
could be completed while the
pump is running, so the Shutdown
Required check box would be
clear. An action to inspect the
internal components of a pump
would be completed while the
pump is not running, so the
Shutdown Required check box

would be selected.

System Preventive Maintenance records store information about time-based maintenance
that exist for the System Preventive Maintenance family. The information in the table
Field
Data
Type
Description

to complete the action. For
Action Cost Number System Preventive
Maintenance records, this
value represents an expense
that is incurred every time the
action occurs.
Behavior and Usage
On the System Preventive

Maintenance datasheet, this field
remove the default value and type
a number directly in the Action
Cost cell.

action can be classified. By
default, this field contains the
Action Type Character
value Time-Based
datasheet.
Maintenance (Preventive)
(PM).
Condition
This field is not used for
Monitoring Character System Preventive
Type
Maintenance records.
Description Text

datasheet.
Additional information about On the System Preventive

the action.
appears as a text box with a
button. You can enter you own
value directly in the Description

cell or click the
button to
view the Text Editor.
Duration

the value in the Duration Units
field, identifies the total time
value in the Duration field is 4 Maintenance datasheet, this field
and the value in the Duration appears as a text box. You can
Number
Units field is Hours, then the remove the default value and
action will take four hours to enter your own value directly in
complete.
the Duration cell.
the value 0.
Duration
Units
GUID
Interval

The time units associated with appears as a list with a blank
Character
the value in the Duration field. caption and contains the
following units: Minutes, Hours,
Days, Weeks, Months, or Years.
A value that uniquely
identifies the record within an
ASO Analysis. The value that
Character automatically by the
Meridium APM system and
should not be modified as it is
required for the proper
functioning of ASO.
Number the value in the Interval Units
field, indicates how often the
action will occur. For
example, if the value in the
Interval field is 4 and the
value in the Interval Units
field is Months, then the
action will occur every four
months during the simulation

included on the datasheet by
default.

remove the default value and
the Interval cell.
period.
the value 1.
Interval
Units

The time units associated with appears as list with a blank
Character
the value in the Interval field. caption and contains the
following units: Minutes, Hours,
Name
One Time
Action

the Name cell. This value is used
to identify Actions in the ASO
Character
Analyses. For instance, the Name
The name of the action.
column appears by default in the
grid in the Actions pane on the
Scenarios - Actions page and
displays values that exist in the
Name field to identify the System
Action records that are displayed
in the grid.
Indicates whether the action On the System Preventive
Logical will occur one time or will be Maintenance datasheet, this field
repeated more than once.
appears as a check box labeled
One Time Action. This check box
is clear by default, indicating that
the action will occur more than
once. You can select this check
box to indicate that an action will
occur one time.
might occur several times a year.
In this case, the One Time Action
check box in the corresponding
System Inspection record would
be clear. An action to inspect a
Shutdown
Required
newly installed pump for any

installation errors might occur
only once, however, in which case
the One Time Action check box in
the corresponding System
Inspection record would be
selected.
appears as a check box labeled
Shutdown Required. This check
box is clear by default, indicating
that the piece of equipment or
location does not need to be shut
down for the action to be
completed. You select this check
box to indicate that the piece of
equipment or location must be
shut down for the action to be
completed.

requires the piece of
equipment or location to be
shut down in order for the
Logical
action to be completed or can
be completed while the piece For example, an action to inspect
of equipment or location is
running.
could be completed while the
pump is running, so the Shutdown
Required check box would be
clear. An action to inspect the
internal components of a pump
would be completed while the
pump is not running, so the
Shutdown Required check box
would be selected.

System Special Action records store information about procedural, redesign, or training
that exist for the System Special Action records. The information in the table reflects the
baseline state and behavior of these fields.
Field
Data
Type
Description

materials or personnel
needed to complete the
Action Cost Number action. For System Special
Action records, this value
represents an expense that is
incurred every time the
action occurs.
Behavior and Usage
On the System Special Action

datasheet, this field appears a list
labeled Action Type and contains
the following values:
Action Type Character

action can be classified.
Procedures (PROC)
Redesign (DSN)
Training (TRN)
You can select the desired value in

this field when you create the
System Special Action record. After
you make your selection, this field
will be disabled so that the value
cannot be modified.
Condition
This field is not used for
Monitoring Character System Special Action
Type
records.
This field is disabled on the System

Special Action datasheet.
Description Text
Additional information
about the action.
text box with a

button. You can
enter you own value directly in the
Description cell or click the
button to view the Text Editor.
Duration
A number that, combined

Number with the value in the
Duration Units field,
identifies the total time


value in the Duration field is
4 and the value in the
Duration Units field is
default value and enter your own
Hours, then the action will
value directly in the Duration cell.
take four hours to complete.
By default, this field
contains the value 0.
Duration
Units
GUID
Interval
The time units associated

Character with the value in the
Duration field.

datasheet, this field appears as a list
with a blank caption and contains
the following units: Minutes, Hours,
A value that uniquely

identifies the record within
an ASO Analysis. The value
that exists in this field is
Character generated automatically by included on the datasheet by
the Meridium APM system default.
and should not be modified
as it is required for the
proper functioning of ASO.
A number that, combined
with the value in the Interval
Units field, indicates how
often the action will occur.
For example, if the value in
the Interval field is 4 and the On the System Special action
value in the Interval Units datasheet, this field appears as a
Number field is Months, then the
action will occur every four default value and enter your own
months during the
value directly in the Interval cell.
simulation period.
By default, this field
contains the value 1.
Interval
Units

The time units associated
datasheet, this field appears as list
Character with the value in the Interval with a blank caption and contains
field.
the following units: Minutes, Hours,
Mandatory Logical
Name
One Time
Action
Shutdown
Required
This field is not used in

ASO.
N/A
text box. You can enter your own
value directly in the Name cell. This
value is used to identify Actions in
ASO Analyses. For instance, the
Name column appears by default in
the grid in the Actions pane on the
Scenarios - Actions page and
displays values that exist in the
Name field to identify the System
Action records that are displayed in
the grid.
check box labeled One Time
Action. This check box is selected
by default, indicating that the action
will occur once. You can clear this
check box to indicate that an action
will occur more than once.

Indicates whether the action the vibration level of a pump might
Logical will occur one time or will occur several times a year. In this
be repeated more than once. case, the One Time Action check
box in the corresponding System
Inspection record would be clear.
An action to inspect a newly
installed pump for any installation
errors might occur only once,
however, in which case the One
Time Action check box in the
corresponding System Inspection
record would be selected.
Logical Indicates whether the action datasheet, this field appears as a
check box labeled Shutdown
requires the piece of
equipment or location to be Required. This check box is
shut down in order for the selected by default, indicating that
the piece of equipment or location
action to be completed or
must be shut down for the action to

be completed. You clear this check
box to indicate that the piece of
equipment or location does not need
to be shut down for the action to be
completed.
can be completed while the
the vibration level of a pump could
piece of equipment or
be completed while the pump is
location is running.
running, so the Shutdown Required
check box would be clear. An
action to inspect the internal
components of a pump would be
completed while the pump is not
running, so the Shutdown Required
check box would be selected.
Parameters for the Asset Strategy

Optimization URL
The URL for displaying ASO Analyses, meridium://ASM/Optimization, requires both
parameters described in the following table. For examples of these parameters, click here.
Parameter
Name
Description
Accepted Value(s)
Notes
Specifies which ASO

The Entity Key of the desired
AnalysisKey Analysis that you
None
System Analysis record.
want to view.
Page
Identifies the page

that you want to
display.
Analysis
When the analysis

appears, the Asset
Strategy Optimization
Summary page is
displayed by default.
Examples of ASO URLs
meridium://ASM/Optimization?Page=Analysis&AnalysisKey=1234567
Opens the ASO Analysis containing the System Analysis record with the Entity Key
1234567.
Action
An operation that can be performed against a piece of equipment or location. Actions can
represent inspections, general maintenance, or specific events that mitigate Risks.
Diagram
A representation of the physical layout and construction of pieces of equipment and
locations. A Diagram consists of a root System Subsystem record, which is linked to one
or more System Subsystem, System Sensor, System Buffer, System Link, System Asset,
and System Switch records that together make up the Diagram.
Global Event
An optional component of a Scenario that groups together Actions requiring a shutdown
so that they will be performed at the same time, thereby maximizing availability.
Resource
An optional component in an ASO Analysis that represents physical parts or materials,
such as spare bearings or seals, or human resources, such as mechanics or technicians,
that you may want to use within the analysis.
Risk
One way in which a piece of equipment or location can fail. If the risk occurs, then the
piece of equipment or location will fail. In ASO Analyses, Risks are represented by
System Risk records, which are linked to System Asset and System Switch records.
Scenario
A representation of a strategy in an ASO Analysis. Each ASO Analysis will contain an
Active Scenario, a Proposed Scenario, an Unmitigated Scenario, and a Customer-defined
Scenario.
Simulation
The process of running Monte Carlo iterations for each Scenario in a System Reliability
Analysis and viewing the results calculated from those simulations.
Overview of Reliability Centered

Maintenance
Reliability Centered Maintenance (RCM) is a methodology for identifying equipment and
location strategies for maintainability and reliability. The RCM method stresses the value
of maintaining equipment and location to preserve the function of the system rather than
for the purpose of preserving the physical equipment and locations themselves. In other
words, as long as the function is preserved, a complete failure of a piece of equipment or
location or a component within that system may be acceptable. RCM provides a means
for determining optimal maintenance and operational strategies based on the probability
and consequence of the analyzed failure modes.
The Meridium APM RCM implementation utilizes the following seven basic questions
that are outlined in SAE Standard JA1011, "Evaluation Criteria for Reliability-Centered
Maintenance (RCM) Processes":
1. What are the functions and desired performance of the (asset/system) in its
present operating context (Functions)?
2. In what ways can it fail to fulfill its functions (Functional Failures)?
3. What causes each functional failure (Failure Modes)?
4. What happens when each failure occurs (Failure Effect)?
5. In what way does each failure matter (Failure Consequences)?
6. What should be done to predict or prevent each failure (Recommendations)?
7. What should be done if a suitable RCM task cannot be found (Default Actions)?
D
RCM System Requirements
The RCM and FMEA license is required to take advantage of RCM functionality. In
addition, your system must contain the basic Meridium APM system architecture.
After you have installed and configured the basic architecture, you will need to perform
some configuration tasks specifically for the RCM module.
When the RCM module is active, the Failure Modes and Effects Analysis (FMEA)
modules is also active. You will also need to perform some configuration tasks
specifically for FMEA.
Function
To prevent failures within a given system, the functions of the system must first be
defined. In an RCM Analysis, a function defines what the owner of the system wants it to
do. A system can have one or more functions, each of which is defined in a separate
record. To define all the possible functions of a system, it can be helpful to think through
the functions of each individual piece of equipment and location defined for a given
system. For example, a function for a cooling tower may be defined with the following
statement:
Provide 500 gallons per minute of water at a maximum of 90 degrees Fahrenheit under
all ambient conditions.
The analysis team should also define whether each function is evident or hidden. Evident
functions are those in which, under normal circumstances, an operating crew would
notice a failure. Hidden functions are those in which a failure may not be noticed.
The SAE Standard JA1011, "Evaluation Criteria for Reliability-Centered Maintenance
(RCM) Processes," specifies the following requirements for functions:
The operating context of the asset shall be defined.

All the functions of the asset/system shall be identified (all primary and secondary
functions, including the functions of all protective devices).
All function statements shall contain a verb, an object, and a performance

standard (quantified in every case where this can be done).
Performance standards incorporated in function statements shall be the level of

performance desired by the owner or user of the asset/system in its operating
context.
Functional Failure
After a systems functions have been defined, the next step is to define all the ways in
which each function can fail, each of which is defined as a functional failure. For each
function, the analysis team should consider each reasonable way in which a function
could fail. The following example shows one possible function and a related functional
failure for a cooling tower:
Function: Provide 500 gallons per minute of water at a maximum of 90 degrees

Fahrenheit under all ambient conditions.
Functional Failure: Unable to produce 500 gallons per minute of water due to
failure of one supply pump.
The following item is defined as a requirement for failures according to the SAE
Standard JA1011, "Evaluation Criteria for Reliability-Centered Maintenance (RCM)
Processes":
All the failed states associated with each Function shall be identified.
Failure Mode
After all the functional failures have been defined, one or more failure modes can be
defined for each failure. The analysis team should determine which failure modes are
reasonably likely to occur. If the RCM Analysis is being conducted on a system that does
not yet exist physically, the mode(s) will be theoretical, unless other similar types of
systems currently exist and historical data for these systems is available. Note that the
SAE Standard JA1011, "Evaluation Criteria for Reliability-Centered Maintenance (RCM)
Processes," specification recommends that an RCM team review all modes in which
deterioration, design defects, and human error could cause the failure.
Failure modes are often closely related to individual pieces of equipment or components
of the defined piece of equipment. Values stored at the equipment level allow the team to
link a mode to a location, the equipment to that location, and a component to that
equipment. Maintenance and reliability statistics for failure modes can be stored at the
equipment or component level and can be analyzed and updated using the Meridium
APM RCM module.
(RCM) Processes," defines the following requirements for failure modes:
All Failure Modes reasonably likely to cause each Functional Failure shall be
identified.
The method used to decide what constitutes a "reasonably likely" Failure Mode
shall be acceptable to the owner or user of the asset.
Lists of Failure Modes shall include Failure Modes that have happened before,
Failure Modes that are currently being prevented by existing maintenance
programs, and Failure Modes that have not yet happened but that are thought to
be reasonably likely (credible) in the operating context.
Lists of Failure Modes should include any event or process that is likely to cause
a Functional Failure, including deterioration, design defects, and human error
whether caused by operators or maintainers (unless human error is being actively
addressed by analytical processes apart from RCM).
Failure Effect
After all the failure modes have been defined, one or more failure effects can be defined
for each mode. A failure effect documents the consequence a failure occurring. Most
RCM methodologies use failure effects to capture the safety, environmental, and
economic (or production) impact associated with a failure.
(RCM) Processes," defines the following requirements for failure effects:
Failure effects shall describe what would happen if no specific task is done to
anticipate, prevent, or detect the failure.
Failure effects shall include all the information needed to support the evaluation
of the consequences of the failure, including the following data:
The evidence (if any) that the failure has occurred (in the case of hidden
functions, what would happen if a multiple failure occurred).
What the failure does (if anything) to kill or injure someone, or to have an
adverse effect on the environment.
What the failure does (if anything) to have an adverse effect on production
or operations.
What physical damage (if any) is caused by the failure.
What (if anything) must be done to restore the function of the system after
the failure.
Recommendation
For each failure effect, one or more recommended actions can be defined. Generally, for
the equipment or location and system owner, recommended actions should be designed to
reduce to an acceptable level the probability and consequence of the related failure.
Recommendations are the result of the Failure Mode and Risk Matrix Analysis. Each
Failure Mode will have one or many recommendations for how the failure can be avoided
in the future.
After the RCM Analysis team has fully analyzed the system and while the information is
still readily available, the team should define the criteria for reevaluation of the
recommendation. For example, the analysis team can define whether a Recommendation
record should be reevaluated based on time, a condition, a defined date, a system process
change, or a change in the design code.
(RCM) Processes," specifies the following requirements for Recommendation records:
All scheduled tasks shall comply with the following criteria:
In the case of an evident Failure Mode that has safety or environmental

consequences, the task shall reduce the probability of the Failure Mode to
a level that is tolerable to the owner or user of the asset.
In the case of a hidden Failure Mode where the associated multiple failure
has safety or environmental consequences, the task shall reduce the
probability of the hidden Failure Mode to an extent which reduces the
probability of the associated multiple failure to a level that is tolerable to
the owner or user of the asset.
In the case of an evident Failure Mode that does not have safety or
environmental consequences, the direct and indirect costs of doing the task
shall be less than the direct and indirect costs of the Failure Mode when
measured over comparable periods of time.
In the case of a hidden Failure Mode where the associated multiple failure
does not have safety or environmental consequences, the direct and
indirect costs of doing the task shall be less than the direct and indirect
costs of the multiple failure plus the cost of repairing the hidden Failure
Mode when measured over comparable periods of time.
On-Condition Tasks: Any on-condition task (or predictive or condition-based or

condition monitoring task) that is selected shall satisfy the following additional
criteria:
There shall exist an identifiable P-F interval (or failure development

period).
The task interval shall be less than the shortest likely P-F interval.
It shall be physically possible to do the task at intervals less than the P-F
interval.
The shortest time between the discovery of a potential failure and the
occurrence of the Functional Failure (the P-F interval minus the task
interval) shall be long enough for predetermined action to be taken to
avoid, eliminate, or minimize the consequences of the Failure Mode.
Schedule Discard Task: Any scheduled discard task that is selected shall satisfy
the following criteria:
There shall exist a clearly defined potential failure.
There shall be a clearly defined (preferably a demonstrable) age at which

there is an increase in the conditional probability of the Failure Mode
under consideration.
A sufficiently large proportion of the occurrences of this Failure Mode
shall occur after this age to reduce the probability of premature failure to a
level that is tolerable to the owner or user of the asset.
Scheduled Restoration Tasks: Any scheduled restoration task that is selected shall
satisfy the following additional criteria:
There shall be a clearly defined (preferably a demonstrable) age at which

there is an increase in the conditional probability of the Failure Mode
under consideration.
A sufficiently large proportion of the occurrences of this Failure Mode

shall occur after this age to reduce the probability of premature failure to a
level that is tolerable to the owner or user of the asset.
The task shall restore the resistance to failure (condition) of the

component to a level that is tolerable to the owner or user of the asset.
Failure Finding Task: Any failure-finding task that is selected shall satisfy the
following additional criteria (failure-finding does not apply to evident Failure
Modes):
The basis upon which the task interval is selected shall take into account
the need to reduce the probability of the multiple failure of the associated
protected system to a level that is tolerable to the owner or user of the
asset.
The task shall confirm that all components covered by the Failure Mode
description are functional.
The failure-finding task and associated interval selection process should

take into account any probability that the task itself might leave the hidden
function in a failed state.
It shall be physically possible to do the task at the specified intervals.
Overview of the RCM Data Structure

The Meridium APM RCM module uses families to represent the various components of
an RCM Analysis, as defined by the standard, accepted RCM methodology. The
Meridium APM system leverages its fundamental entity and relationship family
infrastructure to store data related to an RCM Analysis.
Each RCM Analysis is represented at the root level by an RCM FMEA Analysis record.
FMEA Analyses use the same root analysis family. RCM Analyses are distinguished from
FMEA Analyses via the Analysis Type field in the RCM FMEA Analysis record. The
analysis type can be either RCM or FMEA. For an RCM FMEA Analysis that will be
used for an RCM Analysis, the analysis type is RCM.
Note: Because both RCM and FMEA Analysis records belong to the same family, a
query on the RCM FMEA Analysis family will return results that include all analyses of
any type. To limit your results to include only one analysis type, you will need to include
the Analysis Type field in your query and define criteria to filter on either RCM or
FMEA.
For an RCM Analysis (a record in which the analysis type is RCM), the RCM FMEA
Analysis record can be linked to RCM Function records through the Has RCM Function
relationship. RCM Function records can be, in turn, linked to RCM Functional Failure
records through the Has RCM Functional Failures relationship, and so on, for all
components of the analysis. Together, the root RCM FMEA Analysis record and all the
records that are linked to it, either directly or indirectly, make up the RCM Analysis.
Overview of the RCM Data Model

The following table provides a summary of the entity families and relationship families
that are used to develop an RCM Analysis.
Records in this entity family:
...Through a relationship
...Can be linked to records in
definition on this relationship
this entity family:
family:
RCM FMEA Analysis
RCM Function
Has RCM Function
RCM Function
RCM Functional Failure
Has RCM Functional Failure
RCM FMEA Failure Mode
Has RCM FMEA Failure

Mode
RCM FMEA Failure Effect

Effect
RCM FMEA
Recommendation
Has RCM FMEA

Recommendation
In addition, the following families and relationship are used by RCM but not within the
analysis tree itself.
...Can be
linked to
records in
this entity
family:
...Through
this
Purpose
relationship:
RCM FMEA
Analysis
Human
Resource
Facilitates the construction of the RCM

Has RCM
Analysis Team Members list. Through this
FMEA Team relationship, Human Resource records are
Member
linked directly to the RCM FMEA
Analysis record.
RCM FMEA
Analysis

equipment list. In this way, the RCM
FMEA Asset records are linked directly to
RCM FMEA Has RCM
the RCM FMEA Analysis record. Note,
Asset
FMEA Asset
however, that RCM FMEA Asset records
do not appear in the analysis tree of an
RCM Analysis.
RCM FMEA
Analysis
Allows Task records generated from

Recommendation records to be linked to
the RCM FMEA Analysis record for
which the recommendation was created.
Note that in the current version of
Meridium APM, RCM FMEA Task
records cannot be created from RCM
FMEA Recommendation records. Instead,
RCM FMEA Recommendation records
can be used to create Action records in
ASM. This relationship still exists,
however, to support legacy RCM FMEA
Task records.
Records in this
entity family:
RCM FMEA
Has Tasks
Task
RCM FMEA
RCM FMEA Has Tasks
Recommendation Task
Allows RCM FMEA Recommendation

records to be linked to RCM FMEA Task
records that are generated from those
recommendations. Note that in the current
version of Meridium APM, RCM FMEA
Task records cannot be created from RCM

Task records.
RCM FMEA
Asset
Asset
Strategy
Facilitates the promotion of RCM FMEA

Asset records to Asset Strategy records
via Recommendation Management. This
link is established when an RCM FMEA
Has Strategy
Analysis is linked to a physical or
"virtual" piece of equipment or location
for which you have defined
Recommendation records.
Asset records to Asset Strategy Template
records via Recommendation
Management. This link is established
Has Strategy
when an RCM FMEA Analysis is linked
to a "virtual" piece of equipment or
location for which you have defined
Allows RCM FMEA Asset records to be
linked to RCM FMEA Task records. This
link is established only when a Task
record is generated from a
recommendation where the related RCM
FMEA Asset record (i.e., the RCM FMEA
Asset record that is linked to the RCM
FMEA Analysis record) is not linked to an
RCM FMEA
Asset
Asset
Strategy
Template
RCM FMEA
Asset
RCM FMEA
Has Tasks
Task
RCM FMEA
Asset
Task History Has Task

History

Task records.
Facilitates the rejection of RCM FMEA
Task records that are linked to RCM
FMEA Asset records. When you reject an
RCM FMEA Task record, a Task History

record is created and linked to the RCM
FMEA Asset record through the Has Task
History relationship.
RCM FMEA
Analysis
Has
Templates
RCM FMEA Facilitates the creation of RCM

Template
Templates.
RCM FMEA
Asset
Has
Templates

Template
Templates.
RCM Function
Has
Templates

Template
Templates.
RCM Functional Has

Failure
Templates

Template
Templates.
RCM FMEA
Failure Mode
Has
Templates

Template
Templates.
RCM FMEA
Failure Effect
Has
Templates

Template
Templates.
RCM FMEA
Has
Recommendation Templates

Template
Templates.
RCM FMEA
Mitigates
Recommendation Risk
Risk
Assessment
Allows you to determine how a

recommendation mitigates a risk.
Note also that the following families are related to the RCM FMEA Template family
through the Has Templates relationship to facilitate the creation of RCM Templates:
RCM FMEA Analysis

RCM FMEA Asset
RCM Function
When RCM FMEA Asset Records Are

NOT Linked to Equipment or
Functional Location Records
Each RCM FMEA Analysis record can optionally be linked to one or more RCM FMEA
Asset records to create the equipment and location list for the analysis. The equipment
and location list helps define what is being evaluated through the RCM Analysis. Each
RCM FMEA Asset record can be linked to an Equipment or Functional Location record.
Alternatively, RCM FMEA Asset records can stand alone and not be linked to Equipment
or Functional Location records to represent "virtual" equipment and locations. A given
RCM Analysis can contain both linked and unlinked RCM FMEA Asset records.
The following image provides a diagram of the relationships that will be created when an
RCM FMEA Asset record is not linked to an Equipment or Functional Location record.
Note: While Human Resource records are not depicted in this diagram, they can be linked
to the RCM FMEA Analysis record through the Has RCM FMEA Team Member
relationship.
Note the following about the preceding image:
The RCM FMEA Asset box in the diagram represents a single RCM FMEA Asset
record within an analysis. The RCM FMEA Analysis record can be linked to
multiple RCM FMEA Asset records, each of which can optionally be linked to an
In this scenario, where the RCM FMEA Asset record is not linked to an
Equipment or Functional Location record:
When an RCM FMEA Recommendation record is created for the analysis,

the Recommendation record is linked to the RCM FMEA Asset record
selected in the related failure mode.
When an RCM FMEA Recommendation record is promoted to an Action

record, the Action record will be linked to a Proposed Strategy record and
associated with the RCM FMEA Asset record. For details, see the ASM
Help.
Note: For any linking to occur, the Asset ID of the desired RCM FMEA Asset record
must be selected manually in the RCM FMEA Failure Mode record.
If you promote an RCM FMEA Recommendation record to an Action record to

create a new Asset Strategy, along with a new Action record, a new Risk record is
also created and linked to the RCM FMEA Failure Effect record to which the
RCM FMEA Recommendation record is linked. Certain fields in the Risk record
will be populated automatically with values in the RCM FMEA Failure Effect
record.
In addition to the families included in the preceding image, the following families are
used by the Decision Logic Builder in RCM:
Decision Tree Consequence

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

Linked to Equipment or Functional
Location Records
The following image provides a diagram of the links that will be created when an RCM
FMEA Asset record is linked to an Equipment or Functional Location record.
Note: All relationships depicted in the image are part of the Meridium APM baseline
database.
relationship.
The Equipment or Functional Location box represents the Equipment and
Functional Location families for which the Is RCM FMEA Asset and Has
Recommendations relationships have been defined between that family and the
specified predecessor or successor.
In this scenario, where the RCM FMEA Asset record is linked to an Equipment or

the Recommendation record is linked to the Equipment or Functional
Location record to which the RCM FMEA Asset record is linked.

associated with the Equipment or Functional Location record.
Note: For any linking to occur, the Asset ID of the desired RCM FMEA Asset record
must be selected manually in the RCM FMEA Failure Mode record.
If you promote an RCM FMEA Recommendation record to an Action record to

create a new Asset Strategy, along with a new Action record:
A new Risk record is also created and linked to the RCM FMEA Failure
Effect record to which the RCM FMEA Recommendation record is linked.
Certain fields in the Risk record will be populated automatically with
values in the RCM FMEA Failure Effect record.
A new Risk Assessment record is also created and linked to the Action
record. Certain fields in the Risk Assessment record will be populated
automatically with values in the RCM FMEA Recommendation record.
used by the Decision Logic Builder in RCM:

Illustration of the RCM Data Model

Analysis
RCM Analyses can be created automatically when an Asset Criticality Analysis System
record is promoted from Asset Criticality Analysis (ACA) to RCM. The following
illustration shows how the families in the RCM data model are related to the families in
family).
RCM FMEA Analysis State

Configuration
By default, the following baseline State Configuration exists for the RCM FMEA
Analysis family.
Initial State
The Draft state is the initial state of all new RCM FMEA Analysis records.
RCM FMEA Analysis record in RCM, FMEA, the Record Manager, or the Bulk Data
Form.

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

By default, the MI RCM User State Configuration Role is assigned to all states in the
RCM FMEA Analysis State Configuration. If desired, you can assign other State
About RCM Recommendations

You can manage RCM FMEA Recommendation records in an RCM Analysis using the
following methods:
On the RCM Explorer page

Via the Recommendation Management feature
Both methods use standard State Configuration functionality to control the available
states and the operations that can be used to transition recommendations from one state to
the next.
Via the RCM Explorer page, you will have access only to non-reserved states and
operations. The available operations will be displayed on the Operations submenu, which
appears in the upper, right corner of the datasheet just as in the Record Manager. The
following diagram shows the non-reserved baseline states that will be available on the
RCM Explorer page.
Note: This image shows the non-reserved states that are included in the State
Configuration for the RCM FMEA Recommendation family in the baseline RCM
product. If custom non-reserved states have been added to your system, they will also be
available from the Operations menu.
If you manage RCM FMEA Recommendations via Recommendation Management,
however, you will have access to both reserved and non-reserved states.
RCM and the Record Manager
To ensure data integrity, records that make up analyses and templates in RCM should be
created and managed using only the tools provided in the RCM module. Therefore, the
Meridium APM system prevents you from creating or modifying certain records in the
Record Manager.
While you view records in these families via the Record Manager, the datasheet will be
disabled and a link will be displayed above the Datasheet list, which you can click to
view in RCM the corresponding analysis or template that includes that record. When you
do so, that record will be selected in the explorer automatically. The text that appears for
this link will vary for each record and is displayed in the format <Record ID> (<Family
Caption>), where <Record ID> is the ID for the record and <Family Caption> is the
family caption of the family to which the record belongs. For example, the following
image shows the link that appears above the Datasheet list in the Record Manager when
you are viewing an RCM FMEA Failure Mode record.
The following list contains the families whose datasheet is disabled in the Record
Manager:
RCM FMEA Analysis

RCM FMEA Asset
RCM Function
RCM Funcational Failure
RCM FMEA Template
Accessing the RCM Start Page
The RCM Start Page serves as the starting point for all tasks related to RCM. The
following instructions provide details on accessing the RCM Start Page.
To access the RCM Start Page:
Strategy, and then click Reliability Centered Maintenance.
The RCM Start Page appears.
Aspects of the RCM Start Page

The RCM Start Page displays the following links, which you can use to access various
features in RCM:
View Analysis List: Opens the RCM Analysis List page, from which you can open
an existing RCM Analysis on the RCM Explorer page.
Manage Templates: Displays the RCM Templates page, where you can view a list
of RCM Templates and use any template to create a new RCM Analysis.
Run Reports: Displays the RCM Reports page, which displays the reports that
have been associated with all RCM Analyses.
View Recently Used Analyses: Displays the RCM Recently Used Analyses page,
where you can open an RCM Analysis that you accessed recently.
Create a New Analysis: Launches the RCM Explorer page, where you can create
an RCM Analysis.
Manage Tasks: Displays the RCM Manage Tasks page, which displays a list of
RCM Analyses that have one or more Task records associated with them.
Note: This link appears only if the Show Manage Tasks on the Start Page option is
enabled on the RCM Administration page.
Perform Administrative Tasks: Displays the RCM Administration page, where

you can define various administrative settings for RCM.
Note: This link appears only if you are a Super User or a member of the MI RCM
Administrator Security Group.

Deploying and configuring RCM for the first time includes completing multiple steps,
provide all the information that you need to deploy and configure RCM on top of the
are marked as Required if you must perform the step to take advantage of RCM
functionality.
The person responsible for performing each task may vary within your organization. We
Step Task
Review the RCM data

model to determine which
relationship definitions
you will need to modify to
include your custom
Optional
equipment and location
families. Modify any
relationship definitions as
needed.
This task is
necessary only if
you store
equipment and
location
information in
families other than
the baseline
Equipment and
Functional
Location families.
Define sites to associate

with RCM Analyses.
Optional
None
Required
None
Assign Security Users to

one or more of the RCM
Security Groups via the
Configuration Manager
application.
Create the Evaluation

Security User via the
application.
Optional
None
Create a scheduled item

for executing RCM eventOptional
based and date-based
evaluations.
None
Define the Evaluation

query.
None
Optional
Define the
Recommendation Review Optional
query.
This task is
necessary only if
you do not want to
use the baseline
query that is
defined by default.
Define the Template query. Optional
This task is
necessary only if
you do not want to
use the baseline
query that is
defined by default.
Define the Analysis List

query.
This task is
necessary only if
you do not want to
use the baseline
query.
Optional
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading RCM from V3.5.1 to

V3.6.0.0.0
RCM will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you upgrade the
required.
Upgrading RCM from V3.5.0 SP1 LP to

V3.6.0.0.0
RCM will be upgraded from V3.5.0 SP1 LP to V3.6.0.0.0 automatically when you
upgrade the components in the basic Meridium APM system architecture. No additional
steps are required.

V3.6.0.0.0
RCM will be upgraded from V3.5.0 to V3.6.0.0.0 automatically when you upgrade the
required.

V3.6.0.0.0
The following table lists the steps that are required to upgrade and configure RCM for
Step Task
Assign Security
Users to the MI
RCM Viewer
Security Group.
Add values to the

Recommended
Required
Resource System
Code Table.
Required
None
This System Code Table is

used to populate the
field in RCM FMEA
Recommendation records
Associating RCM Analyses with a

Specific Site
locations, where each site contains unique equipment and locations. If desired, you can
define the sites in your organization and associate equipment and locations with the site
to which they belong. When you create RCM Analyses for those pieces of equipment and
locations, you will need to select the appropriate site on the Analysis datasheet of the
RCM Analysis.
To help streamline the analysis-creation process, after you select a site on the Analysis
datasheet, the Meridium APM system will allow you to add Equipment and Functional
Location records to the RCM Analysis only if those pieces of equipment and locations
belong to that site.
You can also associate Risk Matrices with specific sites. If a Risk Matrix is associated
with a site and an RCM Analysis is associated with the same site, when you define the
unmitigated risk for a failure effect, rather than seeing the default Risk Matrix, you will
see the Risk Matrix that is associated with that site.
About the RCM Administration Page

Note: To access administrative features in RCM, you must be a Super User or a member
of the MI RCM Administrator Security Group.
Via the RCM Administration page, you can:
Define the Evaluation query.
Define the Recommendation Review query.
Define the Template query.
Define the Analysis List query.
These queries must be defined before users can perform evaluations and approvals for
RCM Analyses and before they can view RCM Templates.
Additionally, via the RCM Administration page, you can choose whether or not the
Manage Tasks link will appear on the RCM Start Page.
RCM Security Groups

The RCM module uses the following baseline Security Groups:
MI RCM Administrator: The MI RCM Administrator Security Group has no

family-level privileges configured for it in the baseline Meridium APM database.
Users who are members of this group will see the Administration link on the
RCM Start Page in the Meridium APM Framework application and will,
therefore, have access to administrative functions in RCM. Users who do not
belong to this Security Group will not see this link and, therefore, will not be able
to access the administrative functions.
Because the MI RCM Administrator Security Group has no family-level privileges

assigned to it by default, to access features and functions in RCM, members of the MI
RCM Administrator Security Group will also need to be assigned to the MI RCM User or
MI RCM Viewer Security Group.
MI RCM User: The MI RCM User Security Group has access to all features in
RCM.
MI RCM Viewer: The MI RCM Viewer Security Group has view-only access to
RCM. Users belonging to the MI RCM Viewer Security Group will not have
access to features that result in the creation, update, or deletion of records or links
between records.
The following table shows the family-level privileges assigned to the MI RCM User and
RCM Viewer Security Groups.
MI RCM User
MI RCM
Viewer
Action
View
View
Asset Criticality Analysis System
View
None
Consequence Definition
View
View
View
View
View
View
Family Caption
Entity families
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
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
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,
View
Insert, Delete
Risk Category
View
View
Risk Matrix
View
View
Risk Rank
View, Update,
Insert, Delete
View
Risk Threshold
View
View
Site Reference
Task History
View
View
View, Update,
Insert, Delete
View
View
View
Has Consolidated Recommendations
View
View
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
View, Update,
Insert, Delete
View
Has RCM FMEA Failure Mode
View, Update,
Insert, Delete
View
Note: The Task History relationship family is inactive in

the baseline Meridium APM database.
Relationship families
Has RCM FMEA Failure Effect
View, Update,
Insert, Delete
View
Has RCM FMEA Recommendation
View, Update,
Insert, Delete
View
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

Has Task History
View
View
View, Update,
Note: The Has Task History relationship family is inactive
Insert, Delete
in the baseline Meridium APM database.
View
Has Tasks
View, Update,
Insert, Delete
View
Has Templates
View, Update,
Insert, Delete
View
Is Based on RCM FMEA Failure Effect
View
View
Is RCM FMEA Asset
View, Update,
Insert, Delete
View
With these privileges, any user who is a member of the MI RCM User Security Group
will have access to ALL records involved in RCM Analyses. In addition to these baseline
privileges, which you can grant by assigning users to the MI RCM User Security Group,
you will need to grant RCM users permission to the Equipment or Functional Location
family if it is related to the RCM FMEA Asset family through the Is RCM FMEA Asset
relationship.
Note: You may also want to grant some users permission to modify the items in the
following Catalog folders: \\Public\Meridium\Modules\RCM.
About Virtual and Physical Equipment

and Locations
When you define RCM FMEA Asset records for your RCM Analyses, you have the
following options:
You can create standalone RCM FMEA Asset records that represent virtual
equipment and locations (i.e., equipment and locations that do not physically exist
and are not represented by Equipment and Functional Location records).
You can create RCM FMEA Asset records that are linked to Equipment or
Functional Location records in your database. This option allows you to make
your RCM FMEA Asset records representative of the actual equipment and
locations in your system. This allows certain values from the related Equipment or
Functional Location record to be passed to other records in the analysis, such as
the Failure Effect and Recommendation.
The baseline RCM implementation includes default rules that will map the certain values
from the Equipment or Functional Location record to the fields of the related RCM
FMEA Asset record. In this way, the RCM FMEA Asset record will store identifying
information about its related Equipment or Functional Location record. In addition, the
values stored in the Asset ID field will be available for selection when you create Failure
Mode and Recommendation records. You can modify the rules that are delivered with the
baseline RCM implementation to map additional fields from the Equipment or Functional
Location record to the RCM FMEA Asset record.
In addition, the Meridium APM baseline database is configured with the Has
Recommendations and Has Strategy relationships, so the Meridium APM system will link
Equipment or Functional Location records to RCM FMEA Recommendation records and
to Asset Strategy records.
Has Recommendations Relationship

The Has Recommendations relationship allows Equipment or Functional Location
records that have been linked to RCM FMEA Asset records to be linked to RCM FMEA
Recommendation records. In the Meridium APM baseline database, the following
families are related to the RCM FMEA Recommendation family through the Has
Recommendations family to facilitate this workflow:
Equipment
Functional Location
RCM FMEA Asset
Therefore, any RCM FMEA Asset record that is linked to an Equipment or Functional
Location record is also linked to the RCM FMEA Recommendation record. If you are
following the Meridium APM Best Practice, you will not have to define the Has
Recommendations relationship for the equipment and locations that you have defined for
RCM or FMEA. However, if you want to define RCM FMEA Assets from any family
other than the baseline Equipment or Functional Location families, you will have to
create a relationship definition to link records in those families to RCM FMEA
Recommendation records through the Has Recommendations relationship family.
Note: If you define the Has Recommendations relationship for any family other than the
baseline Equipment and Functional Location families, be sure to use the Has
Recommendations family and not the Has RCM FMEA Recommendations family, which
is reserved for linking RCM FMEA Failure Effect records to RCM FMEA
Recommendation records within RCM Analyses.
When you create an RCM FMEA Failure Mode record for an RCM Analysis, the value in
the Related Asset ID field will indicate the ID of the related RCM FMEA Asset record.
For RCM Analyses, the Related Asset ID must be selected manually. If the RCM FMEA
Asset record is linked to an Equipment or Functional Location record, the Asset ID
comes from the Equipment or Functional Location record.
When you create RCM FMEA Failure Effect records for that Failure Mode and then
create RCM FMEA Recommendation records for those Failure Effects, the Meridium
APM system will pass to the Recommendations the Related Asset ID from the associated
RCM FMEA Failure Mode record.
If the RCM FMEA Asset record is not linked to an Equipment or Functional

Location record, the RCM FMEA Recommendation record will be linked to the
RCM FMEA Asset record.
If the RCM FMEA Asset record is linked to an Equipment or Functional Location
record, the RCM FMEA Recommendation record will be linked to the Equipment
Creating the Evaluation Security User

When you set up an evaluation for an RCM Recommendation, the Meridium APM
system will create a scheduled item for that evaluation and store it in the Meridium APM
Schedule Manager. The scheduled item will be executed according to the schedule that is
set up for the evaluation. As with other actions that you perform in the Meridium APM
system, the execution of the scheduled item requires user authentication. Therefore, to
execute scheduled evaluations, you must set up a Security User for that purpose.
When the scheduled item for an evaluation is executed, three things happen:
If it is an event-based evaluation, the Meridium APM system runs the Evaluation

Query. Therefore, the Evaluation User must have whatever privileges are
necessary to execute the Evaluation Query that you create. The specific privileges
that are required will vary, depending on which families are queried by the
Evaluation Query.
The Meridium APM system updates the associated Recommendation record with
the execution date. Therefore, the Evaluation User must have View and Update
privileges on the RCM FMEA Recommendation family.
The Meridium APM system sends the evaluation email message to the appropriate
email address. This action requires no special privileges.
Therefore, to set up evaluations, you must set up a Meridium APM Security User that has
the privileges described above.
Creating a Scheduled Item for

Evaluations
In RCM, you can define criteria for evaluating the whole analysis or parts of the analysis
in the future. The evaluation feature allows you to be notified or to notify someone else
when certain conditions are met.
To enable this functionality, you will need to create a scheduled item in the Meridium
APM Schedule Manager using the following instructions. When the scheduled item is
run, it will evaluate any date-based criteria and run the Evaluation query that is used by
any event-based criteria to determine whether or not the criteria have been met. When the
scheduled item is executed:
For any date-based evaluations that have been configured, an email message will
be sent for each item whose dates indicates that it is due for evaluation.
For any event-based evaluations that have been configured, an email message will
be sent only if the count and cost returned by the Evaluation query are greater
than the count and cost defined in the event-based evaluation criteria.
To create a scheduled item for Evaluations:

1. Launch the Meridium APM Schedule Manager application and log in.
2. At the bottom of the Meridium APM Scheduler - Scheduled Items window, click
the Add New link.
The Choose a Meridium Assembly dialog box appears.
3. Open the Meridium.RCM.dll file.
The Choose an Object Type dialog box appears.
4. Select the object type Meridium.RCM.Client.RCMEvaluation, and click OK.

The Schedule RCM Evaluation window appears, and the Task tab is displayed by default.
5. On the Task tab, define a schedule that will execute the scheduled item on a
recurring basis. The frequency by which you want to execute the scheduled item
is up to you.
6. Click the User tab.
The User tab appears.
7.
In the User ID and Password text boxes, enter the Meridium APM username and
password for a user who has at least:
The privileges that are necessary to execute the Evaluation Query. The
specific privileges that are required will vary, depending on which families
are included in the Evaluation Query.
View and Update privileges to the RCM FMEA Recommendation family.
View and Update privileges to the RCM FMEA Asset family.
View and Update privileges to the RCM FMEA Analysis family.
8. Click OK.
The scheduled item is created and a new row appears in the Scheduled Items grid.
About Queries Used by RCM

RCM relies upon queries to perform certain functions. For example, when you access the
RCM Analysis List page, the Meridium APM system runs the Analysis List query and
returns a list of analyses that meet the query criteria. From the list of analyses, you can
open an analysis in the RCM Explorer.
Except in the case of the Evaluation query, which you must create manually, when a
query is required to enable certain functionality, the baseline RCM product contains a
default query for you to use. The default query will be used automatically unless you
choose to use a different query.
You can use the default query exactly as it is shipped, or you can modify it to meet your
specific needs. As long as you do not rename the query or move it to a different location
in the Catalog, it will be used automatically in RCM. If you do change the name of the
query or move it to a different location, you will need to modify the appropriate
Administrative setting to point to your custom query.
The following table provides a list and description of the queries that are provided for use
within RCM. Each of these queries is stored in the folder
\\Public\Meridium\Modules\RCM in the Catalog. In addition to the queries listed in the
table, RCM also uses the Evaluation query, which must be created manually and then
selected on the RCM Administration page.
Query
Description
Name of Default
Query in the Catalog
Recommendation
Review query
Used for reviewing recommendations and Review

promoting them to actions.
recommendations
Template query
Used for generating the list of available

templates when you load templates for
creating new analyses or analysis nodes.
Analysis List query
Used for generating the list of analyses that Enterprise Analysis

appears on the RCM Analysis List page. List
Template List
Note that a copy of each baseline query is also stored in the folder
\\Baseline\Meridium\Modules\RCM. The items in the Baseline folder cannot be
modified, so this folder serves as a permanent record of the content that is delivered with
the baseline Meridium APM product. While a copy of each query is stored in the Baseline
folder, the Meridium APM system reads the query from the folder
\\Public\Meridium\Modules\RCM, so you can customize the baseline functionality by
modifying the query in the folder \\Public\Meridium\Modules\RCM.
The Baseline folder will be updated with any changes made to the baseline content in
future releases. If you modify an item in the folder \\Public\Meridium\Modules\RCM and
later decide that you want to revert to the baseline functionality, you can recover the
baseline query from the folder \\Baseline\Meridium\Modules\RCM.
Accessing the RCM Administration

Page
Note: To access administrative features in RCM, you must be a Super User or a member
To access the RCM Administration page:
On the RCM Start Page, click the Perform Administrative Tasks link.
The RCM Administration page appears.
The RCM Administration page displays all the administrative settings that must be
defined for RCM to work properly. A read-only value in the field associated with a setting
indicates that the setting is defined. For new installations the Template Query and
Analysis List Query are defined automatically. The other settings must be defined
manually. In addition, you can modify the value for any setting that is already defined,
including the ones that are defined automatically in the baseline RCM product.
Use the following links to access help for defining each setting:
Recommendation Review query

Evaluation query
Template query
Analysis List query
Note: The RCM Administration page also contains the Show Manage Tasks on the Start
Page check box. You should not select this check box. If you do, the Manage Tasks link
will appear on the RCM Start Page. This link provides access to a feature that does not
work properly.
About the Evaluation Query

For each RCM Analysis, you can configure date-based and event-based evaluations. A
date-based evaluation relies entirely upon the date and time to determine when an
evaluation email message should be sent. An event-based evaluation, on the other hand,
relies upon failure data to determine when an evaluation email message should be sent.
When you set up an event-based evaluation, you will use the Event-Based Evaluation
dialog box to define criteria for sending the evaluation message.
Note that you can set up the evaluation to be based on failure count, failure cost, and date.
This means that to configure effective event-based evaluations, you must define an
Evaluation query that determines the following for a given piece of equipment or
location:
The number of failures that have occurred for the piece of equipment or location
since a given date.
The total cost of the failures that have occurred for the piece of equipment or
location since a given date.
Each day after the specified start date, the Meridium APM system will run the Evaluation
query for the associated Equipment or Functional Location record. When the record
meets the failure count and/or cost criteria, the Meridium APM system will send an
evaluation message to the email address specified in the Notify field.
Creating the Evaluation Query

The specific families included in your Evaluation query will vary, depending on your data
model. Regardless of your data structure, however, your query must follow the guidelines
provided here.
It must contain two columns of output:
Count, which returns a numeric value representing the total number of failures for
a given piece of equipment or location. The alias for this column must be exactly
Count.
Cost, which returns a numeric value representing the total cost of failures for a
given piece of equipment or location and failure mode. The alias for this column
must be exactly Cost.
The query must contain three prompts in the following order:
ID: Accepts the Record ID (i.e., the value in the ENTY_ID field) of the record
representing the piece of equipment or location. Note that the record can be either
an RCM FMEA Asset record itself or a related Equipment or Functional Location
record, depending on whether or not the RCM FMEA Asset record has been
linked to an Equipment or Functional Location record.
Note: In the baseline RCM implementation, the value in the ENTY_ID field from the
RCM FMEA Asset or an Equipment or Functional Location record is passed to the RCM
FMEA Failure Mode record and to subsequent RCM FMEA Recommendation records. If
you are setting up an event-based evaluation at the recommendation level and you have
modified your business rules to pass a different value to the RCM FMEA Failure Mode
record and the Recommendation record, then you will need to set up the Evaluation query
appropriately.
Failure Mode: Accepts the value in the Failure Mode Name field in the Failure
Mode record that is linked to either the Recommendation record (if you are
setting an evaluation at the recommendation level) or the RCM FMEA Asset
record (if you are setting up an evaluation at the equipment or location level).
When the Meridium APM system runs the Evaluation query, it will extract the
value from the Failure Mode Name field in the Failure Mode record and pass it in
as the value for this prompt.
Note: The Failure Mode parameter expression should include the operator like instead of
is equal to (=).
Date: Accepts the date defined in the evaluation item. When you create an eventbased evaluation, you specify a date after which you want to start counting
failures and failure cost. For example, you might specify to be notified when a
given piece of equipment has five failures, beginning 1/1/2005. In this case, the
date 1/1/2005 will be passed to the Evaluation query. If the specified piece of
equipment has had five failures since that date, then the evaluation email message
will be sent.
Note: The Asset ID, Failure Mode, and Date fields should not be included in the output.
The specific tables that you query will vary, depending on your data model. For example,
you might query the Equipment family to retrieve the Asset ID and the Work Order
family to retrieve the failure data, where the Equipment and Work Order families are
related through the Asset Has Maintenance relationship.
Whatever families you query, be sure that the table from which you retrieve the failure
mode should contain the same values that will be stored in the Failure Mode Name field
in RCM FMEA Failure Mode records. In the baseline RCM implementation, the Failure
Mode Name field in RCM FMEA Failure Mode records is simply a character field that
will accept any character string. Because values will be passed from this field to the
Evaluation query, however, it is important that the values stored in the Failure Mode
Name field match the failure modes that are stored in the records that are queried by the
Evaluation query. How you choose to do this is up to you.
For example, you might modify the Failure Mode Name field in the RCM FMEA Failure
Mode family to provide a restricted list of values or to use System Codes. Then, you
might apply the same rules to the Failure Mode field of the family that is used by the
Evaluation query. Just keep in mind that whatever is stored in the RCM FMEA Failure
Mode Name field will be passed to the Failure Mode prompt in the Evaluation query. If
the values passed to the Evaluation query are different from the values stored in failure
data table used by the query, the query will not return the data need to trigger an eventbased evaluation.
Example of an Evaluation Query

Note: The following example is meant to serve as a guideline for creating an Evaluation
query. The specific families that you query and fields that you include will vary,
depending on your data model.
Suppose that you want to create event-based evaluations for equipment that belongs to an
RCM Analysis. The following image shows the design grid for an example of an
Evaluation query.
When you run the query manually, the Enter parameter values dialog box will look like
This means that when the Meridium APM system runs the query automatically according
to the schedule set up in the Schedule Manager, the following values will be passed in for
the prompts:
The Record ID of the Equipment record.

The value in the Failure Mode Name field in the Failure Mode record that is
linked to the RCM FMEA Asset record to which the Equipment record is linked.
The date specified as the Starting from date in the evaluation criteria.
After the appropriate values have been passed in for the prompts, the query will return
results similar to those shown in the following image.
In this particular case, the results show the failure count and failure cost:
For failures of the specified type, as determined by the specified failure mode.
That occurred for the piece of equipment or location identified by the specified
Record ID.
Since the date specified by the Starting from date in the evaluation criteria.
These results will be examined by the Meridium APM system and compared to the failure
count and cost thresholds defined for the evaluation. If the necessary criteria have been
met (i.e., if the failure count and/or cost returned by the query exceed the values defined
for the evaluation), the Meridium APM system will send an evaluation email message to
the appropriate person. If the criteria have not been met, the email message will not be
sent.
Selecting the Evaluation Query

After you have created the Evaluation query and saved it in the Catalog, you must define
that query in the RCM administrative settings.
To define the Evaluation query:
1. Access the RCM Administration page.
2. To the right of the Evaluation Query text box, click the Browse button.
The Evaluation Query dialog box appears.
The hierarchy in the left pane represents the Catalog folder structure.
that you want to use as the Evaluation query.
4. In the pane on the right, select the query that you want to use as the Evaluation
query.
5. Click OK.
The Evaluation Query text box is populated with the path to the query that you selected.
Defining the Recommendation Review

Query
The Recommendation Review query is used for building the list of recommendations that
appears in the pane on the left of the RCM Review Recommendations page. The
Recommendation Review query should retrieve a list of RCM FMEA Recommendation
records that are linked to a given RCM Analysis.
The baseline RCM product contains a default Recommendation Review query called
Review Recommendations, which is stored in the folder
\\Public\Meridium\Modules\RCM. This query will be used automatically by RCM. If you
prefer to create your own query and use it instead, you will need to select that query via
the RCM administrative settings.
Note: If necessary, you can customize the default query without having to modify the
administrative settings. As long as you do not change the query name or location, the
Meridium APM system will use the default query automatically even if you change the
content.
The following instructions provide details on selecting the RCM Review
Recommendations query. Note that you need to perform this procedure only if you
choose to use a query other than the one that is delivered.
To define the Recommendation Review query:
2. To the right of the Recommendation Review Query text box, click the Browse
button.
The Recommendation Review Query dialog box appears.
that you want to use as the Recommendation Review query.
4. In the pane on the right, select the query that you want to use as the
Recommendation Review query.
5. Click OK.
The Recommendation Review Query text box is populated with the path to the query that
you selected.
Defining the Template Query

The Template query is used by RCM to load RCM Analysis Templates. The baseline
RCM product contains a default query called Template List, which is stored in the
folder \\Public\Meridium\Modules\RCM. This query is run automatically when you
access the RCM Templates page.
The Template List query uses a parameter that displays results based on Template Type.
The Template Type that the query uses will depend on how you access the RCM
Templates page. For instance, when you access the RCM Templates page from the RCM
Start Page, the default parameter is Analysis. However, if you access the RCM Templates
page via the RCM Template Explorer page, the root node in the tree determines which
Template Type the query uses as the parameter. For example, if you are working with an
RCM Template with the Template Type Function, when you access the RCM Templates
page, the query will search and return results for all RCM templates created at the
Function level.
If you prefer to create your own query and use it instead, you will need to select that
query via the RCM administrative settings.
administrative settings. As long as you do not change the query name or location, RCM
will use the default query automatically even if you change the content.
The following instructions provide details on selecting the Template query. Note that you
need to perform this procedure only if you choose to use a query other than the one that is
delivered.
To define the Template query:
2. To the right of the Template Query text box, click the Browse button.
The Template Query dialog box appears.
that you want to use as the Template query.
4. In the pane on the right, select the query that you want to use as the Template
query.
5. Click OK.
The Template Query text box is populated with the path to the query that you selected.
Defining the Analysis List Query

The Analysis List query is used by RCM to generate a list of analyses that appears on the
RCM Analysis List page. The baseline RCM product contains a default query called
Enterprise Analysis List, which is stored in the folder \\Public\Meridium\Modules\RCM.
This query will be used automatically by RCM. If you prefer to create your own query
and use it instead, you will need to select that query via the RCM administrative settings.
administrative settings. As long as you do not change the query name or location, RCM
The following instructions provide details on selecting the RCM Analysis List query.
Note that you need to perform this procedure only if you choose to use a query other than
the one that is delivered.
To select the Analysis List query:
2. To the right of the Analysis List Query text box, click the Browse button.
The Analysis List Query dialog box appears.
that you want to use as the Analysis List query.
4. In the pane on the right, select the query that you want to use as the Analysis List
query.
5. Click OK.
The Analysis List Query text box is populated with the path to the query that you
selected.
Clearing the Current Query Selection

After you have selected the Evaluation, Recommendation Review, Template, or Analysis
List query, the query path appears in the text box on the RCM Administration page. The
text is read-only, so to modify the query selection, you must use the procedure that you
used to select the original query. If, on the other hand, you want to delete the current
query selection so that NO query is selected, use the following instructions.
To delete the current RCM query selection:
2. To the right of the text box for the query that you want to clear, click the Browse
button.
The appropriate query selection dialog box appears, depending on which Browse button
you clicked.
3. In the Catalog hierarchy on the left, select any folder.
The pane on the right will display any queries that are stored in that folder. Do not select
a query.
4. Click OK.
The query path that was previously displayed in the text box is deleted.
Using the RCM Site Map

The Site Map in RCM allows you navigate from the current page to the RCM Start Page
by clicking the RCM link in the Site Map. The Site Map appears at the top of the
workspace on every page within RCM. The page that you are currently viewing appears
as a hyperlink in the Site Map after the delimiter >.
The following image shows an example of the Site Map in RCM as it appears on the
RCM Analysis List page. A red outline has been added to the image to highlight the Site
Map.
Navigating RCM as a Member of the MI

RCM Viewer Security Group
Unlike members of the MI RCM User Security Group, who have access to ALL features
in the RCM modules, members of the MI RCM Viewer Security Group will have viewonly access to RCM. In other words, members of the MI RCM Viewer Security Group
cannot create, modify, or delete records or links between records. These users can,
however, view the contents of analyses.
When you are logged in as a member of this Security Group, options that would result in
the creation, update, or deletion of records or links between records will be disabled,
including datasheets. In other words, if you do not have privileges to perform the action,
the associated option will be disabled.
For example, when you are viewing an analysis on the RCM Explorer page, the RCM
FMEA Analysis datasheet will be disabled. In addition, links like the New Function link
on the Common Tasks menu will be disabled. While links like the Set Up Assets link on
the Analysis Tasks menu will remain enabled and provide access to the RCM Asset List
page.
Throughout this documentation, we assume that you are familiar with the privileges
associated with the Security Group to which you belong. The documentation does not
specify how options in the RCM module behave based upon your security privileges.
Options for Opening an RCM Analysis

You have several options for opening existing RCM Analyses. Your choice of where and
how to open an analysis will depend primarily on your personal preference. You can open
an analysis from:
The RCM Analysis List page, which displays a list of RCM Analyses retrieved by
the query that has been set up for the purpose of generating the analysis list.
The RCM Recently Used Analyses page, which displays a list of the four analyses
that you last accessed.
Accessing the RCM Analysis List

From the RCM Analysis List page, you can run the query that has been set up for the
purpose of retrieving a list of existing RCM Analyses and then, from the list of analyses,
open an analysis.
To access the RCM Analysis List page:
On the RCM Start Page, click the View Analysis List link.
The RCM Analysis List page appears.
Aspects of the RCM Analysis List Page

The main display area of the RCM Analysis List page contains a grid that displays a list
of analyses retrieved by the Analysis List query. If the Analysis List query contains one
or more prompts, those prompts will appear in fields above the grid, along with a Run
Query button. You can select a value for each prompt and then click the Run Query
button to retrieve results based on your selections. For more information on this feature,
click here.
Note: The default Enterprise Analysis List query does not contain any prompts. Prompts
will appear above the grid only if a custom query has been configured by an
administrative user.
The specific columns that appear in the results grid will vary, depending on how the
query has been configured. If the query has been properly configured, the grid will
display the Analysis Short Description column, which will contain a hyperlinked
description of the analysis. You can click any link to open the associated analysis.
The RCM Analysis List page contains the following task menus: Analysis Tasks and
Common Tasks.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Analysis List page contains the following links:
Create Analysis: Opens the RCM Explorer page, displaying a new RCM
Analysis.
Open in Explorer: Opens the selected RCM Analysis on the RCM Explorer page.
This link is disabled if more than one RCM Analysis record is selected in the grid.
Delete Analysis: After asking for confirmation, deletes the analysis that is
currently selected. Note that deleting an analysis from the RCM Analysis List
page will delete the RCM FMEA Analysis record and all the records to which it is
linked (i.e., all the analysis elements).
Common Tasks Menu
The Common Tasks menu on the RCM Analysis List page contains the following links:
Print: Displays the Preview window, from which you can select various print
options and print the list of analyses.
Page.
Help: Displays the context-sensitive Help topic for the RCM Analysis List page.
Opening an Analysis from the Analysis

List
To open an analysis:
In the Analysis Short Description column, click the link for the analysis that you
want to open.
-orSelect the row containing the analysis that you want to open, and on the Analysis Tasks
menu, click the Open in Explorer link.
-orRight-click any analysis in the list, and then click Open in explorer.
The selected analysis appears on the RCM Explorer page.
Deleting RCM Analyses
The following instructions provide details on deleting an RCM Analysis record via the
RCM Analysis List page. You can also delete an RCM Analysis record, however, using
the shortcut menu in the RCM Explorer pane.
When you delete an RCM Analysis record, you are also deleting all the records that are
linked to that record that make up the RCM Analysis.
To delete an RCM Analysis record:
1. Access the RCM Analysis List page.
2. Select the row(s) containing the RCM Analysis record(s) that you want to delete.
3. On the Analysis Tasks menu, click the Delete Analysis link.
A confirmation message appears, asking if you really want to delete the selected analysis
or analyses (if you selected multiple rows).
4. Click OK.
The selected record(s) is deleted.
Accessing the RCM Recently Used

Analyses Page
To view a list of recently accessed analyses:
On the RCM Start Page, click the View Recently Used Analyses link.
The RCM Recently Used Analyses page appears, displaying a list of RCM Analyses that
you have viewed most recently.
Aspects of the RCM Recently Used

Analyses Page
The RCM Recently Used Analyses page displays a list of the last four analyses that you
have opened. By default, the grid contains the following columns:
Id: The value stored in the Analysis ID field in the corresponding record. This
value appears as a hyperlink, which you can click to open the analysis.
Description: The value stored in the Analysis Short Description field in the
corresponding record.
Last Updated On: The date on which the corresponding record was last updated.
Last Updated By: The user name of the user who was logged in when the record
was last updated.
You can customize the default grid display, if desired. If you have not yet viewed any
analyses, the There are no recently viewed links available link will appear in place of the
grid. You can click the link to return to the RCM Start Page.
The RCM Recently Used Analyses page contains two task menus: Analysis Tasks and
Common Tasks.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Recently Used Analyses page contains the
following links:
Analysis.
Open in Explorer: Opens the selected RCM Analysis on the RCM Explorer page.
This link is disabled if more than one RCM Analysis record is selected in the grid.
Delete Analysis: After asking for confirmation, deletes the analysis that is
currently selected. Note that deleting an analysis from the RCM Recently Used
Analyses page will delete the RCM FMEA Analysis record and all the records to
which it is linked (i.e., all the analysis elements).
View Analysis List: Displays the RCM Analysis List page, which displays a list of
all the RCM analyses that exist.
Common Tasks Menu

The Common Tasks menu on the RCM Recently Used Analyses page contains the
following links:
Print: Displays the Preview window, from which you can select various print
options and print the list of analyses.
Page.
Help: Displays the context-sensitive Help topic for the RCM Recently Used
Analyses page.
Opening a Recently Used Analysis

To open an analysis:
In the Id column, click the hyperlinked ID of the analysis that you want to open.
-orSelect the row containing the analysis that you want to open, and on the Analysis Tasks
-orRight-click any analysis in the list, and then click Load selected analysis into explorer.
The selected analysis appears on the RCM Explorer page.
Workflow for Creating an RCM

Analysis
The following list represents the basic steps that should be completed in an RCM
Analysis. Note that none of the steps are required, but the more steps you complete, the
more thorough your analysis will be. In addition, note that the RCM data model dictates
that certain elements be defined before certain other elements can be defined.
1. Create the root-level RCM Analysis record.
2. Create the analysis team.
3. Define the equipment and location list, which helps define the RCM system. Note
that each RCM FMEA Asset record can optionally be linked to an Equipment or
4. Define the functions of the system.
5. Define functional failures for each system function.
6. Define failure modes for each functional failure.
7. Define the failure effects for each failure mode.
8. Define recommendations for each failure effect.
9. Define conditions for evaluation of the recommended actions.
10. Create Task records based on the recommendations.
11. Schedule tasks in Task Management and perform the associated work.
12. Update the analysis based on evaluation email received for recommendations.
Meridium APM provides various tools that you can use to accomplish these tasks. The
tools that you use will depend on your personal preference and your workflow.
Starting a New RCM Analysis

The following instructions provide details on creating a new analysis from scratch. Note
that you can also create a new RCM analysis using the following methods:
Load an RCM Template.

Promote an Asset Criticality Analysis System record from Asset Criticality
Analysis (ACA) to RCM.
The following instructions provide details on creating a new RCM Analysis from the
RCM Start Page. You can also create a new RCM Analysis using the Create Analysis link
that appears on the Analysis Tasks menus throughout RCM.
To create a new analysis from scratch:
1. On the RCM Start Page, click the Create a New Analysis link.
The RCM Explorer page appears, displaying a new analysis.
2. In the Analysis datasheet, enter the desired analysis information. Note that the
default Analysis datasheet contains two tabs:
o Analysis Identification: Stores identifying information, such as the
analysis ID and description. Note that the Analysis ID and Analysis Type
cells are populated automatically and cannot be modified. The Analysis
Short Description cell is also populated with a default value but can be
modified if needed.
o
System Definition: Stores general information about the system that is

being analyzed, including information about the system boundaries. The
System Definition tab also contains the Site Reference field, where you
can select the site to which this analysis belongs. The list contains the
Record ID of all Site Reference records that exist in the database.
Note: After an RCM Analysis contains an Equipment or Functional Location record that
is linked to a Site Reference record, the Site Reference field is disabled.
3. Click the Save button
, which appears above the datasheet.
The new RCM FMEA Analysis record is saved to the database in the Draft state. After
you have saved the analysis, the task menu options become enabled so that you can
perform additional tasks associated with the analysis. The next step in setting up the new
analysis is to define the asset list, set up the analysis team, or create the first Function
record.
Note that if you selected a value in the Site Reference field:
When you define the equipment and location list, you will be able to link
RCM FMEA Asset records to Equipment or Functional Location records
that are linked to that Site Reference record.
When you define the unmitigated risk rank associated with a failure effect,
you will see the Risk Matrix that is built using the Risk Matrix record that
is linked to that Site Reference record.
About the RCM Explorer Page

The RCM Explorer page is the page that you will use to work with RCM Analyses. The
layout of the RCM Explorer page is similar to that of the Record Manager, where it is
divided into three main areas:
The following task menus:
Analysis Tasks menu
Common Tasks menu
Template Tasks menu
Associated Pages menu
Analysis Reports menu
The RCM Explorer pane, which displays the RCM Analysis in a hierarchical view
so that you can view the RCM FMEA Analysis record itself along with all the
related records, which, together, make up the analysis.
The datasheet area, which displays the information stored in the record for the
selected node.
Note that throughout our discussion of the RCM Explorer page, we assume that you are
familiar with the basic concepts and navigational features of the Record Manager. We
limit our discussion primarily to features that are specific to the RCM Explorer page and
that deviate from the standard functionality of the Record Manager.
About Accessing the RCM Explorer

Page
You can access the RCM Explorer page in various ways, depending on the task that you
want to perform:
You can access it to create a new RCM Analysis from scratch.

You can open an existing analysis from the RCM Analysis List page.
You can open an existing analysis from the RCM Recently Used Analyses page.
You can access it and then load an analysis template that you will use to create a
new analysis.
About the RCM Explorer Pane

When you open an RCM Analysis on the RCM Analysis page, the RCM Analysis family
appears at the root level in the RCM Explorer pane. Below the root record, arranged in a
hierarchical view, the RCM Explorer pane displays the other components of the analysis.
When you first open an RCM Analysis, only Function nodes will be displayed in the
RCM Explorer pane, provided that one or more RCM Function records have been linked
to the root RCM FMEA Analysis record. The following image displays an example of the
RCM Explorer pane.
You can click the plus sign (+) to the left of any Function node to expand it and view the
associated functional failure records. You can expand any Functional Failure node to
view the associated Failure Mode records. You can continue expanding the tree to view
all the components involved in the analysis. Components are linked to one another
according to the relationships defined in the RCM data model. The following image
shows an example of a fully expanded branch of the tree. Notice that each analysis node
has its own icon to help you identify it in the tree.
Hint: You can also right-click any branch of the tree and then click Hide Children or
Show Children, as appropriate, to expand or collapse that branch.
Selecting a node in the tree will cause the datasheet for that record to appear in the
datasheet area of the RCM Explorer page.
Note that unlike the standard Record Explorer pane, which displays all the records in the
record hierarchy that are linked to the root record through any relationship, the RCM
Explorer pane displays only the records belonging to the families that make up the RCM
Analysis components, according to the RCM data model. Therefore, you will see only the
records that make up a given RCM Analysis.
The Shortcut Menu in the RCM

Explorer Pane
If you right-click a node in the RCM Explorer pane, a shortcut menu will appear,
displaying options associated with the RCM Analysis and its components. The specific
options that are available on the menu will vary, depending which analysis node you
select. The following image shows the options that appear on the shortcut menu when
you right-click a Function node.
The following options are available on the shortcut menu in the RCM Explorer pane:
Save: Saves any changes that you have made to the currently selected record (i.e.,
the record whose datasheet is displayed on the right side of the page).
Save as Template: Displays the <Node ID> (new RCM FMEA Template) window,
where <Node ID> is the ID of the node that is currently selected in the tree. This
window facilitates the creation of a new RCM FMEA Template at the level of the
currently selected node.
Load Template: Facilitates the creation of a new RCM Analysis node as a
successor of the currently selected node by applying an existing RCM Template.
If you are applying a Function node, Functional Failure node, or Failure

Mode node, this link will launch the Apply Template Builder, which
guides you step-by-step through the process of applying a template to the
new analysis node in the current RCM Analysis. The Apply Template
Builder allows you to replace any RCM FMEA Asset record associated
with the template you want to apply with RCM FMEA Asset records that
are linked to the current analysis.
Note: If you are applying a Failure Mode node, the Apply Template Builder will also give
you an option to load into the current RCM Analysis an FMEA Asset Template.
If you are applying a Failure Effect node or a Recommendation node, this

link will open the Templates window, which displays a list of templates
that you can use for adding a new node to the selected Analysis node. The
list of templates displayed in the Templates window is appropriate to the
type of node that is currently selected.
Cut: Copies the currently selected node and all its nodes and then deletes the
records from the database. A temporary copy of the records is saved so that you
can link them to a different record using the Paste function. For example, you can
cut an RCM Functional Failure record from one Function record and then paste it
to a different Function record.
Copy: Copies the selected record but does not remove it from the analysis tree.
After you have copied a record, the Paste option will appear on the shortcut menu
so that you can paste the record in a different location in the analysis. Note that if
the selected analysis component has children, a prompt appears, asking if you
want to copy just the selected record or the selected record and all its child
records.
Paste: Links the copied record to the record that you select in the RCM Explorer
pane. Note that this menu option appears only after you have copied a record and
only if you select a record to which it is possible to link the copied record,
according to the relationship definitions that exist.
Delete: Deletes the selected record from the analysis and from the database. When
you use this option, a prompt appears, asking if you want to delete the selected
component only or the selected component and all its subcomponents.
If you choose to delete the selected component and all its children, the
Meridium APM system will delete all the records from the analysis and
from the database.
If you choose to delete the selected component and not the children, the
Meridium APM system will delete the selected record from the database
and will remove any subcomponents from the analysis. The children will
not, however, be deleted from the database.
New [Node]: Creates a new record and links it to the selected record. The type of
record that is created will depend on which record you select when you access the
shortcut menu. For example, if you select a Function record, this option will read
New Failure and will result in the creation of a new Functional Failure record.
Reference Documents: Displays the Reference Documents window, where you

can manage the Reference Documents associated with the record.
[Node] Reports: Displays a submenu, containing a list of reports that are

associated with the selected component. For example, when you select an RCM
Function record, this option will be labeled Function Reports. This menu option
appears only if reports exist for the currently selected node.
Show Children: For a given node of the analysis tree, expands the hierarchy to
display the immediate children of that node. This option appears only when you
select a collapsed node that has children.
Hide Children: For a given node of the analysis tree, collapses the hierarchy to
hide the children of that node. This option appears only when you select a node
that has children and that is currently expanded.
Show All: Completely expands the currently selected node.
Help: Displays the context-sensitive Help topic for the RCM Explorer page.
About the Datasheet Area

The datasheet area, which appears on the right side of the RCM Explorer page, displays
the datasheet for the record that is currently selected in the RCM Explorer pane. For
example, when you select an RCM Failure Effect record in the RCM Explorer pane, the
datasheet area displays the Failure Effect datasheet, which is populated with the values
that exist in the Failure Effect record, outlined in red in the following image.
In the datasheet area, you can view the information that currently exists for the selected
record and modify the information if needed. After you make changes to the record
information, you can click the Save link on the Common Tasks menu to save your
changes. If you make changes to a record via the datasheet and then select a different
node in the RCM Explorer pane, you will be prompted to save your changes before
displaying the datasheet for the newly selected node.
The other features of the datasheet area, such as the buttons that appear above the
datasheet itself, are the same as those that are available in the Record Manager.
Note: The New button above the datasheet creates a new record in the same family as
the selected record. For example, if you are viewing an RCM FMEA Recommendation
record and you click the New button above the datasheet, a new RCM FMEA
Recommendation record would appear in the datasheet area. Because the RCM Explorer
page can display only one analysis at a time, the New button is disabled when you are
viewing the RCM FMEA Analysis record.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Explorer page contains the following links:
Manage Team: Displays the RCM Team Members page, where you can set up
your RCM Analysis Team.
Set Up Assets: Displays the RCM Asset List page, where you can set up the
equipment and location list for the current analysis.
Review Recommendations: Displays the Recommendation Management page,

where you can review and manage the Recommendation records associated with
the current analysis. This link is enabled only if one or more RCM FMEA
Recommendation records exist for the current analysis.
View Master Recommendation: If the selected Recommendation record was

consolidated with one or more other Recommendation records, this link opens the
master consolidated Recommendation record in a stand-alone window. This link
is enabled only if the selected Recommendation record is in the Consolidated
state.
Set Up Evaluation: Displays the Set Up <Node> Evaluation dialog box, where
<Node> is the type of node that is selected in the RCM Explorer pane. You can
use this dialog box to define criteria for sending evaluation email. This link is
enabled only an Analysis or Recommendation node is selected in the tree.
Risk Assessment: Displays the Risk Assessment feature.
If a Failure Effect node is selected in the analysis tree, the Unmitigated

Risk Assessment window appears.
If a Recommendation node is selected in the analysis tree and a value has

been selected for at least one Category in the corresponding unmitigated
Risk Assessment, the Risk Mitigation Assessment window appears.
Run Decision Logic: Launches the Decision Logic Builder. This link is enabled
only if a Failure Effect node is selected in the tree.
View Analysis List: Displays the RCM Analysis List page, from which you can
open an existing RCM Analysis.
Analysis.
Common Tasks Menu

The Common Tasks menu on the RCM Explorer page contains the following links:
New [Node]: Creates a new record, whose type is indicated by the [Node] name
and links it to the selected record. The name of this link changes, depending on
which node you select. For example, when you select a Function node in the
RCM Explorer pane, this link reads New Failure and lets you create an RCM
Functional Failure record and link it to the selected function.
Note: This link is disabled when you select a Recommendation node since
Recommendation records represent the lowest level in the RCM Analysis hierarchy. In
other words, you cannot add a record to the analysis when a Recommendation node is
selected.
Save: Saves the currently selected record. For example, if you select a Function
node in the RCM Explorer pane, when you click this link, the Meridium APM
system will save any changes that you have made to that Function record.
Delete: Deletes the selected record from the analysis and from the database. When
you use this option, a prompt appears, asking if you want to delete the selected
component only or the selected component and all its subcomponents.
If you choose to delete the selected component and all its children, the
Meridium APM system will delete all the records from the analysis and
from the database.
If you choose to delete the selected component and not the children, the
Meridium APM system will delete the selected record from the database
and will remove any subcomponents from the analysis. The children will
not, however, be deleted from the database.
Cut: Copies the currently selected node and all its nodes and then deletes the
records from the database. A temporary copy of the records is saved so that you
can then link them to a different record using the Paste function. For example, you
can cut an RCM Functional Failure record from one Function record and then
paste it to a different Function record.
Copy: Copies the selected record but does not remove it from the analysis tree.
After you have copied a record, the Paste option will appear on the shortcut menu
so that you can paste the record in a different location in the analysis. Note that if
the selected analysis component has children, a prompt appears, asking if you
want to copy just the selected record or the selected record and all its subrecords.
Note: If you cut or copy and analysis node, when you paste the node, the Meridium APM
system will generate for the pasted node a new ID that is appropriate to where you paste
it.
Paste: Links the copied record to the record that you select in the RCM Explorer
pane. Note that this menu option appears only after you have copied a record and
only if you select a record to which it is possible to link the copied record,
according to the relationship definitions that exist.
Print: Displays the Preview window, which shows a preview of how the current
datasheet will be printed. From the Preview window, you can select print options
and print the record.

Page.
Help: Displays the context-sensitive Help topic for the RCM Explorer page.
Template Tasks Menu

The Template Tasks menu on the RCM Explorer page contains the following links:
Save as Template: Displays the [Record ID](New RCM FMEA Template)

window, where [Record ID] is the record ID of the selected analysis node. You
can use this window to save the current analysis or analysis node as an RCM
Template.
Load Template: Displays the Templates window, which displays a list of RCM
Templates that you can use for adding a new node to the selected Analysis node.
The list of RCM Templates displayed in the window is appropriate to the type of
node that is currently selected.
Reports Menu
The Reports menu on the RCM Explorer page displays the captions of the reports that are
associated with the node currently selected in the RCM Explorer pane. The name of the
menu will change as appropriate, depending on which node you select. For example,
when you select the root-level analysis node, the menu is labeled Analysis Reports and
displays a list of reports associated with the Analysis node.
Each analysis node has a related folder in the Catalog that is used to determine which
reports to display for which analysis component. This menu appears only if reports exist
in the Catalog folder associated with the selected node.

The Associated Pages menu on the RCM Explorer page displays Associated Pages that
have been configured via the URL Manager for the family of the analysis node that is
currently selected in the RCM Explorer pane.
Note: The Associated Pages menu will not be filtered based on the type of analysis that
you are viewing. Any Associated Page that you configured for a family that is used by
both RCM and FMEA Analyses will appear when you are viewing an RCM Analysis and
when you are viewing an FMEA Analysis.
What is the RCM Analysis Team?

The RCM Analysis Team defines which users will participate in the RCM Analysis. The
RCM Analysis Team actually consists of Human Resource records that are linked to the
RCM FMEA Analysis record. The FMEA Team Members page simply provides a
customized view for working with Human Resource records that are linked to the RCM
FMEA Analysis record. To add people to the RCM Analysis Team, you can either select a
Human Resource record that currently exists in the Meridium APM database, or you can
create a new Human Resource record.
You can set up the RCM Analysis Team on the RCM Team Members page, which is
accessible from the RCM Explorer after you have created a new analysis or opened an
existing analysis.
Accessing the RCM Team Members

Page
To access the RCM Team Members page:
On the RCM Explorer page, on the Analysis Tasks menu, click the Manage Team
link.
The RCM Team Members page appears.
Aspects of the RCM Team Members

Page
The RCM Team Members page for RCM Templates has similar features to the RCM
Team Members page that is configured for RCM Analyses. The RCM Team Members
page contains a grid that displays a list of all the Human Resource records that are linked
to the RCM Template. The grid is divided into two columns:
Record ID: The Record ID of the Human Resource record.

Last Name: The value in the Last Name field in the Human Resource record.
The RCM Team Members page also contains three task menus, which let you perform
tasks specific to the RCM Analysis Team: Analysis Tasks, Team Members Tasks, and
Common Tasks.
From the RCM Team Members page, you can:
Add team members using existing Human Resource records.

Add team members by creating new Human Resource records.
Modify information about a team member by modifying the corresponding

Human Resource record.
Remove team members from the RCM Analysis Team.
Analysis Tasks Menu
The Analysis Tasks menu on the RCM Team Members page contains the following links:
View in Explorer: Opens the current analysis on the RCM Explorer page.
Set Up Assets: Displays the RCM Asset List page, where you can manage the
equipment and location list for the analysis.
Analysis.
Team Members Tasks Menu

The Team Members Tasks menu on the RCM Team Members page contains the following
links:
Create New: Displays the Create New Team Member dialog box, where you can
create a new Human Resource record and add that person to the RCM Analysis
Team.
Add Existing: Displays the Find a Human Resource dialog box, where you can
search for existing Human Resource records to add to the RCM Analysis Team.
Edit: Displays the Edit Team Member dialog box, where you can modify the
information stored in the selected Human Resource record.
Remove: After asking for confirmation, removes the selected Human Resource
record from the RCM Analysis Team. Note that this does not delete the Human
Resource record from the database.
Common Tasks Menu
The Common Tasks menu on the RCM Team Members page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the RCM Team Members
page.
Adding an Existing User to the RCM

Analysis Team
To add a team member to the RCM Analysis Team using an existing Human Resource
record:
1. On the RCM Team Members page, on the Team Member Tasks menu, click the
Add Existing link.
The Find a Human Resource window appears.
2. Specify search criteria to find the desired Human Resource record. Note that the
Human Resource family is selected in the Search In list by default. You cannot
select a different family, but you can define additional criteria if desired.
The Human Resource records that match your search criteria appear in a list at the bottom
of the window.
4. In the list of results, select the record that you want to add to the RCM Analysis
Team.
5. Click the Select button.
The Human Resource record that you selected appears in the list on the RCM Team
Members page.
Creating a New User to Add to the RCM

Analysis Team
To add a team member to the RCM Analysis Team by creating a new Human Resource
record:
1. On the RCM Team Members page, on the Team Member Tasks menu, click the
Create New link.
The Create New Team Member dialog box appears.
2. On the datasheet, complete the desired fields to identify the new Human
Resource. Note that a Last Name is required.
The new Human Resource record is created and added to the RCM Analysis Team.
Modifying Information about a Team

Member
To modify the Human Resource record for an RCM Analysis Team member:
1. On the RCM Team Members page, in the list of team members, click the
hyperlinked Record ID of the Human Resource record that you want to modify.
The Edit Team Member dialog box appears.
2. Make the desired changes.
Your changes are saved to the database.
Removing Team Members from the

RCM Analysis Team
Note: Removing a team member from the RCM Analysis Team simply breaks the link
between the Human Resource record and the RCM FMEA Analysis record. It does not
delete the Human Resource record from the database.
To remove a Human Resource record from the RCM Analysis Team:
1. On the RCM Team Members page, in the list of team members, select the row
containing the Human Resource record that you want to remove from the RCM
Analysis Team.
2. On the Team Members Task menu, click the Remove link.
A message appears, asking if you really want to remove the Human Resource record from
the RCM Analysis Team.
The Human Resource record is removed from the RCM Analysis Team.
Accessing the RCM Asset List Page

An RCM system includes a set of equipment and locations, their functions, and their
boundaries. One of the most important steps in defining the system is to set up the
equipment and location list. After you have opened an existing analysis or created a new
analysis, you can access the RCM Asset List page to set up the equipment and location
list that will help define the analysis system.
To access the RCM Asset List page and set up the equipment and location list for an
analysis:
With the analysis open on the RCM Explorer page, on the Analysis Tasks menu,
click the Set Up Assets link.
The RCM Asset List page appears.
Note: You can also access the RCM Asset List page from the RCM Team Members page.
Aspects of the RCM Asset List Page

The RCM Asset List page contains a grid that displays a list of all the RCM FMEA Asset
records involved in the analysis. The grid is divided into two columns:
Record ID: The Record ID of the RCM FMEA Asset record.

Description: The value from the Description field in the RCM FMEA Asset
record.
The RCM Asset List page also contains three task menus, which let you perform tasks
specific to the equipment and location list: Analysis Tasks, Asset Tasks, and Common
Tasks.
From the RCM Asset List page, you can:
Add RCM FMEA Asset records to the system.

Modify RCM FMEA Asset records.
Link RCM FMEA Asset records to Equipment or Functional Location records.
Delete RCM FMEA Asset records.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Asset List page contains the following links:
View in Explorer: Displays the current analysis on the RCM Explorer page.
Manage Team: Opens the RCM Team Members page, where you can set up the
analysis team for the current analysis.
Set Up Evaluation: Displays the Set Up Asset Evaluation dialog box, where you
can define criteria for sending evaluation email for the piece of equipment or
location that appears in the selected row (either an RCM FMEA Asset record or
an Equipment or Functional Location record that is linked to an RCM FMEA
Asset record).
Analysis.
Assets Tasks Menu

The Assets Tasks menu on the RCM Asset List page contains the following links:
Create New: Displays the Create New Asset Record dialog box, where you can
enter the information for a new RCM FMEA Asset record and add it to the
analysis.
Copy Existing: Displays the Find Asset Records dialog box, where you can search
for an existing RCM FMEA Asset record and create a copy of it to link to the
analysis.
Link to Asset: Displays the Find Asset dialog box, where you can search for an
Equipment or Functional Location record to link to the selected RCM FMEA
Asset record. This link is enabled only when the selected RCM FMEA Asset
record has not yet been linked to an Equipment or Functional Location record. If
no families are related to the RCM FMEA Asset family using the Is RCM FMEA
Asset relationship, the No Relationships Defined error message appears.
Open Linked Asset: Opens in Record Manager the Equipment or Functional

Location record that is currently linked to the selected RCM FMEA Asset record.
This link is enabled only when the selected RCM FMEA Asset record is linked to
an Equipment or Functional Location record.
Edit: Displays the Edit Asset Record dialog box, where you can modify the
content of the selected RCM FMEA Asset record.
Delete: After asking for confirmation, deletes the selected RCM FMEA Asset
record from the database. Note that if the RCM FMEA Asset record is linked to an
Equipment or Functional Location record, the link will also be deleted.
Common Tasks Menu

The Common Tasks menu on the RCM Asset List page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the RCM Asset List page.
Creating a New RCM FMEA Asset

Record to Add to the List
To create a new RCM FMEA Asset record and add it to the equipment and location list:
1. On the RCM Asset List page, on the Assets Tasks menu, click the Create New
link.
The Create New Asset Record dialog box appears.
2. In the fields provided, enter the information for the new RCM FMEA Asset
record.
3. Click OK.
The new RCM FMEA Asset record is created and appears in the list on the RCM Asset
List page.
Copying an Existing RCM FMEA Asset

Record
If an RCM FMEA Asset record already exists that is appropriate for the piece of
equipment or location that you want to add to the system, you can create a copy of the
existing record.
To create a copy of an existing RCM FMEA Asset record:
1. On the RCM Asset List page, on the Assets Tasks menu, click the Copy Existing
link.
The Find Asset Records dialog box appears.
2. Enter the search criteria necessary to find the desired RCM FMEA Asset.
A list of records that match your search criteria appears in the lower portion of the screen.
4. In the list of results, select the row containing the record that you want to copy.
A copy of the selected RCM FMEA Asset record is created. The ID and Description are
regenerated automatically to make them appropriate for the current analysis. The copy
that was created appears in the grid on the RCM Asset List page.
Modifying an RCM FMEA Asset Record

To modify an RCM FMEA Asset record:
1. On the RCM Asset List page, in the list of Asset records, click the hyperlinked
Record ID of the RCM FMEA Asset record that you want to modify.
The Edit Asset Record dialog box appears.
2. Modify the record data, as desired.
3. Click OK.
Linking an RCM FMEA Asset Record

to an Equipment or Functional
Location Record
If your system has been properly configured, you will have the option of linking RCM
FMEA Asset records to Equipment or Functional Location records in your database. This
gives you the ability to use an RCM Analysis to analyze both "virtual" equipment and
locations (which are not represented by existing Equipment and Functional Location
records) and physical equipment and locations (which are represented by Equipment and
Functional Location records).
When RCM FMEA Asset records are linked to Equipment or Functional Location
records, information from the Equipment or Functional Location record will be passed to
various elements in the analysis. In addition, the Equipment or Functional Location
record will then be linked to any Recommendation records or Task records that are
created for the piece of equipment or location.
The first step in linking RCM FMEA Asset records to Equipment or Functional Location
records is to add the RCM FMEA Asset to the equipment and location list of a given
analysis. You can do this either by copying an existing RCM FMEA Asset record or by
creating a new RCM FMEA Asset record. After the RCM FMEA Asset record exists on
the equipment and location list, you can link it to an Equipment or Functional Location
record.
Note that if the System Definition tab of the Analysis datasheet contains a value in the
Site Reference field, you will be able to link RCM FMEA Asset records only to
Equipment or Functional Location records that are linked to that Site Reference record.
Likewise, if the System Definition tab does not yet contain a value in the Site Reference
field, when you add a piece of equipment or location to the RCM Analysis, the Site
Reference field will be updated automatically to display the ID of the Site Reference
record that is linked to the Equipment or Functional Location record representing the
piece of equipment or location. You will then be able to link RCM FMEA Asset records
only to Equipment or Functional Location records that are linked to that Site Reference
record.
To link an RCM FMEA Asset record to an Equipment or Functional Location record:
1. On the RCM Asset List page, in the list of RCM FMEA Asset records, select the
row containing record that you want to link to an Equipment or Functional
Location record.
2. On the Assets Tasks menu, click the Link to Asset link.
Note: This link is enabled only when you select a row containing an RCM FMEA Asset
record that is not already linked to an Equipment or Functional Location record.
The Find Asset window appears.
3. In the Search In list, select the family on which to search.
Note: The Search In list contains the families that are related to the RCM FMEA Asset
family through the Is RCM FMEA Asset relationship.
4. Specify any additional, desired search criteria, and click the Find Now button.
The records that match your search criteria appear in the list at the bottom of the page.
5. Select the row representing the record that you want to link to the RCM FMEA
Asset record.
The list on the RCM Asset List page displays an updated list of RCM FMEA Asset
records. The ID of the record that you just linked is updated to reflect the ID of the
related record. If your system has been configured to do so, additional fields may also be
mapped from the Equipment or Functional Location record to the RCM FMEA Asset
record. If desired, you can open the linked record in Record Manager.
Viewing the Equipment or Functional

Location Record that is Linked to an
RCM FMEA Asset Record
When an RCM FMEA Asset record is linked to an Equipment or Functional Location
record, you can view the associated Equipment or Functional Location record from the
RCM Asset List page. After you open the Equipment or Functional Location record in the
Record Manager, all the standard Record Manager features will be available to you.
To view the Equipment or Functional Location record that is linked to the RCM FMEA
Asset record:
1. On the RCM Asset List page, in the list of existing RCM FMEA Asset records,
select the row representing the RCM FMEA Asset record whose related record
you want to view.
2. On the Assets Tasks menu, click the Open Linked Asset link.
The Record Manager appears, displaying the linked record.
Unlinking an RCM FMEA Asset Record

from the Related Equipment or
Functional Location Record
The RCM Asset List page provides no direct method for unlinking an RCM FMEA Asset
record from its related Equipment or Functional Location record. If you need to unlink an
RCM FMEA Asset record from an Equipment or Functional Location record, either to
create a virtual piece of equipment or location or to relink the RCM FMEA Asset record
to a different record, use one of the following procedures:
On the RCM Asset List page, copy the RCM FMEA Asset record. The new RCM
FMEA Asset record will not be linked to an Equipment or Functional Location
record. You can then delete the original, linked RCM FMEA Asset record.
Open the RCM FMEA Asset record in Record Manager and remove the link
between the RCM FMEA Asset record and the Equipment or Functional Location
record.
Note: If you link an RCM FMEA Asset record to the wrong record, you will need to
unlink the two records using one of the preceding options and then relink the RCM
FMEA Asset record to the desired record. You cannot modify an existing link in a single
step.
You should unlink RCM FMEA Asset records from Equipment or Functional Location
records only if no RCM FMEA Recommendation or RCM FMEA Task records have been
created and linked to the RCM FMEA Asset record. Unlinking records may result in
RCM FMEA Recommendations and RCM FMEA Task records that are linked to record
no longer involved in the Analysis. If you unlink an RCM FMEA Asset record from an
Equipment or Functional Location record and then relink the RCM FMEA Asset records
to a different one, if the original record had been linked to one or more RCM FMEA
Recommendation records, the existing links will be updated automatically so that the
Recommendations are linked to the new record. Links between existing RCM FMEA
Task records and Equipment or Functional Location records will, however, not be
modified.
Deleting an RCM FMEA Asset Record

You can delete RCM FMEA Asset records via the RCM Asset List page. Deleting RCM
FMEA Asset records in this way will delete the RCM FMEA Asset record both from the
analysis system and from the database. If the RCM FMEA Asset record is linked to an
Equipment or Functional Location record, the link between the RCM FMEA Asset record
and the Equipment or Functional Locatin record will be broken, but the Equipment or
Functional Location record will not be deleted from the database.
To delete an RCM FMEA Asset record:
1. On the RCM Asset List page, in the list of RCM FMEA Asset records, select the
row containing the record that you want to delete.
2. On the Assets Tasks menu, click the Delete link.
A confirmation message appears, asking if you really want to delete the record.
The RCM FMEA Asset record is deleted from the database. If the record was linked to an
Equipment or Functional Location record, that link is broken.
Defining Functions
The first step in conducting an RCM analysis is to define all the functions of the system.
The following instructions provide details on creating a Function node. You can repeat
these steps to create as many Function nodes as are necessary in your analysis.
To add an RCM Function record to an RCM Analysis:
1. With the analysis open on the RCM Explorer page, select the analysis node in the
RCM Explorer pane.
2. On the Common Tasks menu, click the New Function link.
-orRight-click the analysis node, and then click New Function.
A new Function node is added to the tree in the RCM Explorer pane.
The RCM Function datasheet is displayed in the datasheet area on the right side of the
page.
3. In the RCM Function datasheet, enter the information for the new RCM Function
record. Note that the Function ID is generated automatically by the system and
cannot be modified. The Function Name is also generated automatically. This can
be modified but is required.
4. When you are finished entering the function information, on the Common Tasks
menu, click the Save link.
The information that you entered for the RCM Function record is saved to the database.
At this point, you can:
Select the analysis node in the RCM Explorer pane to create another RCM
Function record.
Define an RCM Functional Failure record for the RCM Function record
that you just created.
Defining Functional Failures

For each function that you define for an RCM analysis, you can define one or more
functional failures. A functional failure describes a way in which a given function can
fail.
To add an RCM Functional Failure record to an RCM Analysis:
1. With the analysis open on the RCM Explorer page, in the RCM Explorer pane,
select the Function node of the RCM Function record to which you want to link
the new RCM Functional Failure record.
2. On the Common Tasks menu, click the New Failure link.
-orRight-click the Function node, and then click New Failure.
A new Failure node is added to the tree in the RCM Explorer pane.
The RCM Function Failure datasheet is displayed in the datasheet area on the right side
of the page.
3. On the RCM Function Failure datasheet, enter the information for the new RCM
Functional Failure record. Note that the Functional Failure ID is generated
automatically by the system and cannot be modified. The Functional Failure
Name is also generated automatically. This can be modified but is required.
4. When you are finished entering the functional failure information, on the
Common Tasks menu, click the Save link.
The information that you entered for the RCM Functional Failure record is saved to the
database. At this point, you can:
Select a Function node to create another RCM Functional Failure record.
Create a new failure mode for the RCM Functional Failure record that you
just created.
Defining Failure Modes

A failure mode defines how a functional failure is likely to occur. Failure modes are
often, but not always, related to specific equipment or locations or to components within
equipment and locations. Both RCM and FMEA analyses can have multiple failure
modes defined for them.
To add an RCM Failure Mode record to an RCM analysis:
select the Functional Failure node of the RCM Functional Failure record to which
you want to link the new RCM FMEA Failure Mode record.
2. On the Common Tasks menu, click the New Mode link.
-orRight-click the Failure node, and then click New Mode.
A new Failure Mode node is added to the tree in the RCM Explorer pane.
The RCM Failure Mode datasheet is displayed in the datasheet area on the right side of
the page.
3. On the RCM Failure Mode datasheet, enter the information for the new RCM
FMEA Failure Mode record. Note that:
The Failure Mode ID value is generated automatically by the system and

cannot be modified.
The Failure Mode Name value is also generated automatically. This can be
modified but is required.
The Related Asset ID field contains a list of IDs from the RCM FMEA
Asset records that are linked to the RCM FMEA Analysis record. You can
select any ID from the list. Your selection will determine whether the
RCM FMEA Asset record or the Equipment or Functional Location record
is linked to subsequent Recommendation records. If you select an RCM

FMEA Asset record where the Asset Type field contains a value, that value
will be used to populate the Related Asset Type field in the associated
RCM FMEA Failure Mode record and the RCM FMEA Recommendation
record.
Note: If you modify the value in the Related Asset ID field of an existing Failure Mode
record, the links to any recommendations will also be updated. Note, however, that if
RCM FMEA Task records have been linked to the Recommendation record, changing the
Related Asset ID in the Failure Mode record will not update the link to the Task record.
The RCM FMEA Task record will continue to be linked to the RCM FMEA Asset or
Asset record to which the Recommendation record was linked when the Task record was
originally created.
4. When you are finished entering the failure mode information, on the Common
Tasks menu, click the Save link.
The information that you entered for the RCM FMEA Failure Mode record is saved to the
database. At this point, you can:
Select a Functional Failure node and create another RCM FMEA Failure
Mode record.
Create a new failure effect for the RCM FMEA Failure Mode record that
you just created.
Defining Failure Effects

A failure effect defines what would happen if a given failure mode occurred. Failure
effects can be used to define the environmental, safety, and economic consequences of
failure modes.
To add an RCM Failure Effect record to an RCM Analysis:
select the Failure Mode node of the RCM FMEA Failure Mode record to which
you want to link the new RCM FMEA Failure Effect record.
2. On the Common Tasks menu, click the New Effect link.
-orRight-click the Failure Mode node, and then click New Effect.
A new Failure Effect node is added to the tree in the RCM Explorer pane.
The RCM Failure Effect datasheet is displayed in the datasheet area on the right side of
the page.
3. On the RCM Failure Effect datasheet, enter the information for the new RCM
FMEA Failure Effect record. Note that the Effect ID is generated automatically
and cannot be modified. The Effect Name is also generated automatically. This
can be modified but is required.
4. On the Analysis Tasks menu, click the Risk Assessment link.
The Unmitigated Risk Assessment window appears.
5. Using the Risk Matrix provided, define the unmitigated risk rank associated with
the failure effect, and click the Save button.
Note the following:
6.
o
If the Site Reference field on the Analysis datasheet contains a value, you
will see the Risk Matrix that is built using the Risk Matrix record that is
linked to that Site Reference record.
If any tab represents a risk category that does not apply to the failure effect
that you are assessing, you can select the Not Applicable check box on that
tab. When you do so, the tab will be disabled, and the tab label will be
updated to contain the text N/A.
The unmitigated risk rank that you selected in the Risk Assessment feature
appears in the Unmitigated Risk field on the RCM Failure Effect
datasheet.
The Financial Risk Rank that you selected in the Risk Assessment feature
appears in the Unmitigated Financial Risk field on the RCM Failure Effect
datasheet.
The highest unmitigated risk rank that you select on any non-financial tab
appears in the Driving Risk Rank field on the RCM Failure Effect
datasheet.
The tab that contains the highest non-financial unmitigated risk rank
appears in the Driving Risk Category field on the RCM Failure Effect
datasheet.
The Risk Of cell contains the value in the Effect Name field in the RCM
FMEA Failure Effect record.
The text that you type in the Basis for Assessment dialog box is saved in
the RCM FMEA Failure Effect record.
7. On the Analysis Tasks menu, click the Run Decision Logic link.
The Decision Logic Builder appears, displaying the Welcome screen.
8. Use the Decision Logic Builder to identify actions that will mitigate the
associated failure effect.
After you complete the Decision Logic Builder, the responses that you provided to the
questions and the recommended action will be recorded on the Logic Builder tab on the
RCM Failure Effect datasheet.
9. When you are finished entering the failure effect information, on the Common
The information that you entered for the RCM FMEA Failure Effect record is saved to
the database. At this point, you can:
Create another RCM FMEA Failure Effect record.

Define a recommendation for the RCM FMEA Failure Effect record that
you just created.
The Decision Logic Builder

The Decision Logic Builder guides you step-by-step through answering questions that
will result in suggestions for mitigating a given failure effect. After you use the Decision
Logic Builder to determine which actions should be taken to mitigate the effects of the
failure, you can create recommendations that are based upon the recommended actions.
When you go through the Decision Logic Builder, you will be presented with a series of
questions. You will respond Yes or No to each of the questions. When you have reached
the end of the Decision Logic Builder, you will be presented with a recommended action
that is based upon the responses to the questions that were presented. Your responses to
the questions and the recommended action will be recorded in text fields in the RCM
FMEA Failure Effect record. After you complete the Decision Logic Builder, you can
view a summary of your responses on the Logic Builder tab of the RCM Failure Effect
datasheet.
The Decision Logic Builder is based upon the concepts and decision diagrams in SAE
Standard JA1012, "A Guide to the Reliability-Centered Maintenance (RCM) Standard."
The process and terminology used in the Decision Logic Builder are described in more
detail in this standards document. To use the Decision Logic Builder effectively, you will
need to be familiar with this standard.
To use the Decision Logic Builder:
1. Open an RCM Analysis.
2. In the RCM Explorer pane, select a Failure Effect node.
3. On the Analysis Tasks menu, click the Run Decision Logic link.
The Decision Logic Builder appears, displaying the Welcome screen.
The Logic Selection screen appears.
5. Click the Yes button to respond Yes to the question.
-orClick the No button to respond No to the question.
The next question is displayed immediately after you click the Yes or No button.
6. Continue clicking the Yes or No button in response to each question that is
displayed. The number of questions that are presented will depend upon your
responses.
When you have responded to all the questions, a suggested action will be displayed.
The Decision Logic Builder closes. You can click the Logic Builder tab on the RCM
Failure Effect datasheet to view a summary of your responses and the suggested action.
Hint: If you want to modify your responses, click the Run Decision Logic link on the
Analysis Tasks menu and proceed through the Decision Logic Builder again. The
information on the Logic Builder tab will be updated after you complete the builder. If
you close the Decision Logic Builder before responding to all questions and clicking the
Finish button, the information on the Logic Builder tab will not be updated.
Defining Recommendations
Hint: For help with defining Recommendation records, on the RCM Explorer page, you
can click the Decision Tree link on the Recommendation Tasks menu to access the
Decision Tree document that has been configured for use with RCM.
To add an RCM FMEA Recommendation record to an RCM Analysis:
select the Failure Effect node of the RCM FMEA Failure Effect record to which
you want to link the new RCM FMEA Recommendation record.
2. On the Common Tasks menu, click the New Recommendation link.
-orRight-click the Failure Effect node, and then click New Recommendation.
A new Recommendation node is added to the tree in the RCM Explorer pane. The RCM
Recommendation datasheet is displayed in the datasheet area on the right side of the
page.
3. On the RCM Recommendation datasheet, enter the information for the new RCM
FMEA Recommendation record. Note that:
The Recommendation ID is generated automatically and cannot be
modified.
The Recommendation Headline is also generated automatically. This can

be modified but is required.
The Asset ID cell is populated automatically with the value in the Related
Asset ID cell in the related Failure Mode. You can modify this field, if
desired. We recommend, however, that you accept the default value. If you
modify this value, recommendation evaluation email may not be generated
properly. In addition, the Meridium APM system relies upon this value to
relate any Task records generated from the recommendation to the
associated RCM FMEA Asset record or Equipment or Functional Location
record.
If you select Failure Finding (FF) in the Action Type list, the cells below
the ***Failure Finding Activity*** section become enabled. The value in
the FFI cell is calculated using the values in the MMF, MTIVE, MTED,
and n cells.
Note that if you want the calculated FFI value to appear in the Interval field,
select the Use Calculated FFI Results check box. In addition, if you want to see
the FFI value in a different unit (e.g., Months), select the desired interval in the
Display FFI Units As list. The value in the Interval cell will be updated to reflect
the selected unit.
Note: Changes that you make to the values in existing RCM FMEA Recommendation
records will not have any effect on the RCM FMEA Task records to which they are
already linked.
4. On the Analysis Tasks menu, click the Risk Assessment link.
The Risk Mitigation Assessment window appears.
5. Using the Risk Matrix provided, define the mitigated risk rank associated with the
recommendation, and click the Save button. Note that:
The Risk Of cell contains the value in the Effect Name field in the RCM
FMEA Failure Effect record to which the RCM FMEA Recommendation
record is linked.
The Mitigated By cell contains the value in the Recommendation Headline

field in the RCM FMEA Recommendation record.
The Not Applicable check box is disabled when you are assessing the
mitigated risk of a Recommendation record. The Not Applicable check
box selection will be inherited from the associated Failure Effect's risk
assessment.
The text that you type in the Basis for Assessment dialog box is saved in
the RCM FMEA Failure Effect record to which the RCM FMEA
Recommendation record is linked.
The mitigated risk rank that you selected in the Risk Assessment feature appears in the
Mitigated Risk field on the RCM Recommendation datasheet. The financial risk rank that
you selected in the Risk Assessment feature appears in the Mitigated Financial Risk field
on the RCM Recommendation datasheet.
6. When you are finished entering the recommendation information, on the Common
The information that you entered for the RCM Recommendation record is saved to the
database.
About Copying, Cutting, and Pasting

Analysis Elements
To help streamline the analysis-development process, RCM lets you cut, copy, and paste
analysis elements. You can use these options to cut or copy individual analysis nodes and
then paste them to another location within the same analysis. Note the following about
using the cut, copy, and paste functions:
The Cut function creates a copy of the cut elements and then deletes the records
from the database. When you paste the cut elements, the Meridium APM system
will create new records. Note also that the Cut function automatically copies all
nodes of the selected node.
When you paste copied analysis elements, the IDs are generated automatically in
the same way as they are when you create a new analysis element. The Meridium
APM system looks at the other nodes on the level where you are pasting, finds the
highest numeric value of all the current IDs, adds one (1) to the highest value, and
assigns that as the ID value for the newly pasted node. The ID helps uniquely
identify each element with respect to its location in the analysis.
When you paste copied analysis elements, the names are not regenerated.
When you copy or cut and then paste an analysis node that is linked to one or
more Reference Document records, the Reference Document records will also be
copied or cut and then pasted.
Using the Cut Function
To cut an analysis node and paste it to another location within the same analysis:
1. In the RCM Explorer pane, select the node that you want to cut.
2. Press Ctrl+X on your keyboard.
-orOn the Common Tasks menu, click the Cut link.
-orClick the right mouse button, and then click Cut.
If the node that you selected has successor nodes, a message appears, asking if you want
to copy all the child elements.
3. Click OK.
The selected node and all its nodes are copied and then deleted from the database.
Note: If you want to paste the node that you cut, you must do so immediately before
copying or cutting another node; otherwise the cut node and its nodes will be lost
permanently. You will be able to paste the cut node only once.
Using the Copy Function

To make a copy of an analysis node to paste in an additional location within the same
analysis:
1. In the RCM Explorer pane, select the node that you want to copy.
2. Press Ctrl+C on your keyboard.
-orOn the Common Tasks menu, click the Copy link.
-or-
Click the right mouse button, and then click Copy.

If the node that you selected has successor nodes, a message appears, asking if you want
to copy all the child elements.
3. Click the Yes button to copy all the child elements of the selected element.
-orClick the No button to copy only the selected node.
Note: If you want to paste the node that you copied to a different location, do not delete
the copied node. The copied node will not be available for pasting after you delete it.
Using the Paste Function

After you copy a node or cut a node, you can paste the copied element(s) to another node.
The Paste function will automatically paste the copied node and any nodes that were
copied along with it.
Note: A cut node can be pasted only once. A copied node can be pasted multiple times but
cannot be pasted after the copied node is deleted from the database.
To paste the copied element(s) to another location:
1. Select the node on which you want to paste the copied elements.
Note: The node that you select as the target for the Paste operation must be appropriate
for the node that was copied. For example, if you copy a Recommendation node, you
must select a Failure Effect node in order paste the copied elements. The Paste function
will be enabled only after you select an appropriate node.
2. Press Ctrl+V on your keyboard.
-orOn the Common Tasks menu, click the Paste link.
-or-
Click the right mouse button, and then click Paste.

The element is pasted to the selected location.
Modifying an Analysis Node in the RCM

Explorer Pane
You can use the following instructions to modify any node in an RCM Analysis,
including the root-level analysis node.
To modify the information associated with an analysis element in the RCM Explorer
pane:
expand the analysis tree to locate the node representing the record that you want
to modify.
2. Select the node.
The datasheet associated with that record appears in the datasheet area on the right side of
the page.
3. In the datasheet, modify the values in any editable field.
Deleting an Analysis or Analysis Node in

the RCM Explorer Pane
In the RCM Explorer pane, you can delete any analysis element, or you can delete the
root-level analysis node to delete the entire analysis. Note that if you choose to delete an
element that contains elements, all elements will also be deleted. Note also that deleting a
Recommendation record will also delete any related scheduled item that exists for that
recommendation in Schedule Manager.
To delete an analysis or analysis element from the RCM Explorer pane:
1. In the RCM Explorer pane, expand the tree, and select the node representing the
element that you want to delete.
Hint: To delete the entire analysis, select the root-level analysis node.
2. On the Common Tasks menu, click the Delete link.
A message appears, asking if you really want to delete the selected element and all its
children.
3. Click OK.
The selected node and its nodes are deleted from the database.
If you deleted the element of an analysis, the next highest node is selected
in the analysis tree in the RCM Explorer pane.
If you deleted the root-level analysis node, you are directed to the RCM
Start Page.
About RCM Templates

An RCM Template is a copy of an entire RCM Analysis or one or more RCM Analysis
nodes (e.g., Failure Effects) that can be used to create a new RCM Analysis or append
nodes to an existing RCM Analysis. RCM Template records belong to the RCM FMEA
Template family. Together, the RCM FMEA Template record and all the records that are
related to it make up the RCM Template.
You can use RCM Templates to streamline the analysis-development process by reducing
the amount of time spent entering data that is already used in a similar analysis.
You can work with RCM Templates via the locations in the following list. Where you
work with RCM Templates will determine the tasks that you can perform on that RCM
Template. You can use the following lists as a guide for determining which method to use
when working with RCM Templates:
On the RCM Explorer page, you can perform the following tasks:
Create RCM Templates from an existing analysis.
Create new analysis elements from an RCM Template.
Manage analysis elements.
On the RCM Template Explorer page, you can perform the following tasks:
Create new RCM Templates from scratch.
Create new template elements from an existing RCM Template.
Manage template elements in RCM Templates, similar to how you manage

analysis elements in RCM Analyses using the RCM Explorer pane.
On the RCM Templates page, you can perform the following tasks:
Create RCM Analyses from an existing RCM Template.
Create RCM Templates from scratch.
Modify RCM Templates.
Delete RCM Templates.
Accessing the RCM Templates Page

To access the RCM Templates page:
On the RCM Start Page, click the Manage Templates link.
-orOn the RCM Template Explorer page, on the Analysis Tasks menu, click the Manage
Templates link.
The RCM Templates page appears.
Aspects of the RCM Templates Page

The RCM Templates page displays the results of the query that is defined for the
Template Query setting on the RCM Administration page. By default, this page displays
the results of the Template List query, which is stored in the
\\Public\Meridium\Modules\RCM folder in the Meridium APM Catalog. This query
contains one prompt, Template Type, which appears as a list at the top of the RCM
Templates page. The Template Type list contains the following values, which you can use
to filter the query results that appear at the bottom of the page:
Analysis: Displays the RCM Templates that were created at the analysis level.
This value is selected by default when you access the RCM Templates page from
the RCM Start Page. If you access the RCM Templates page from the RCM
Template Explorer page, however, the query will use the prompt value that
corresponds to the type of template that you are working with when you access
the RCM Templates page.
Asset: This value is not used for RCM Templates.
Failure Effect: Displays the RCM Templates that were created at the failure effect
level.
Failure Mode: Displays the RCM Templates that were created at the failure mode
level.
Function: Displays the RCM Templates that were created at the function level.
Function Failure: Displays the RCM Templates that were created at the function
failure level.
Recommendation: Displays the RCM Templates that were created at the

recommendation level.
You can select any value from the Template Type list, and then click the Run Query
button to view the corresponding query results. Note that each of the values in the
preceding list corresponds to a value that can be stored in the Template Type field in the
corresponding RCM FMEA Template record.
Note: Throughout this documentation, our descriptions of the RCM Templates
functionality assume that you are using the default Template List query. If you have
modified the default query or if you are using a different query, the RCM Template
functionality for your implementation may vary slightly from our descriptions.
The query results section contains the following columns:
Template ID: The Record ID of the RCM FMEA Template record.

Template Type: The type of template. This value is determined by the family of
the root node in the template. For example, if the root node in the template is a
Failure Mode, the Template Type cell will contain the value Failure Mode.
Description: The description of the template that is stored in the Description field
in the RCM FMEA Template record.
Analysis Type: The type of analysis to which the template applies (i.e., RCM or
FMEA). By default, the query results on this page will contain only RCM FMEA
Template records whose Analysis Type field contains the value RCM.
The RCM Templates page contains the following task menus: Template Tasks and
Common Tasks.
Template Tasks Menu

The Template Tasks menu on the RCM Templates page contains the following links:
Create Analysis: Creates a new RCM Analysis based upon the RCM Template
that is currently selected in the results grid.
If the template that you want to use to create a new analysis is linked to at
least one RCM FMEA Asset record, this link will display the Apply
Template Builder, which you can use to specify whether you want to keep
or replace the RCM FMEA Asset record(s) and then apply the template
accordingly.
If the template that you want to use to create a new analysis is not linked
to any RCM FMEA Asset records, this link will create the analysis from
the template and open it on the RCM Explorer page.
This link is enabled only when the results displayed on the RCM Templates page contains
records whose Template Type is Analysis. This link is disabled if more than one RCM
FMEA Template record is selected in the grid.
Create Template: Displays the Template Builder, which guides you step-by-step
through the process of creating an RCM Template from scratch.
Edit Template: Displays the selected RCM Template record on the RCM Template
Explorer page, where you can modify the record and save your changes. This link
is enabled only when at least one record appears in the results grid. This link is
disabled if more than one RCM FMEA Template is selected in the grid.
Delete Template: After asking for confirmation, deletes the selected RCM FMEA
Template record from the database. This link is enabled only when at least one
record appears in the grid. You can select multiple records to delete.
Common Tasks Menu

The Common Tasks menu on the RCM Templates page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the RCM Templates page.
Accessing the Template Builder

You can use the Template Builder to create a new RCM Template from scratch. To access
the Template Builder:
On the RCM Templates page, on the Template Tasks menu, click the Create
Template link.
-orOn the RCM Template Explorer page, on the Analysis Tasks menu, click the Create
Template link.
The Template Builder appears, displaying the Welcome screen.
Using the Template Builder to Create a

New RCM Template from Scratch
The following instructions provide details on creating a new RCM Template using the
Template Builder.
To create a new RCM Template from scratch:
1. Access the Template Builder.
The Select Template Type screen appears.
3. Select the Template Type for which you want to create an RCM template, and
then click the Next button.
The Define Root Node screen appears, displaying the datasheet for the family that
corresponds to the template type that you selected on the previous screen. For example, if
you selected the Analysis option, you will create an RCM Template whose root node will
represent an RCM FMEA Analysis record. In this case, the Analysis datasheet for the
RCM FMEA Analysis family will appear on the Define Root Node screen, as shown in
4. Provide values in the fields as needed, and then click the Next button.
The Define Template screen appears, displaying the RCM FMEA Template datasheet.
The following fields contain values by default:
The Type cell is disabled and populated automatically with the template
type value, which indicates the family of the record from which the
template was created.
The Analysis Type cell is disabled and populated automatically wit RCM.
The Author cell is disabled and populated automatically.
The Created On cells is disabled and populated automatically.
6. Provide values in the fields on the datasheet, as needed.

The RCM Template is created and appears on the RCM Template Explorer page, where
the root node in the RCM Template Explorer pane corresponds to the template type value
that you selected.
Creating an RCM Template from an

Existing RCM Analysis
When you use an RCM Template to create a new analysis or to create new nodes in an
existing analysis, ALL the nodes that are included in the RCM Template will be applied
to the target analysis. From the RCM Explorer page, you can create a new RCM
Template from an RCM Analysis or any analysis element.
When you create an RCM Template from the root RCM Analysis node, the RCM
Template will include:
The RCM Analysis node.

Any related RCM FMEA Asset records that make up the RCM Asset list.
Note: If the analysis includes RCM FMEA Asset records that are linked to Equipment or
Functional Location records, the links will not be maintained when the RCM Template is
created. In this way, the RCM FMEA Asset records that are linked to the RCM Template
will become virtual equipment and locations. When you create a new analysis from the
RCM Template in this case, you will be given the option to keep or replace virtual
equipment and locations with Equipment or Functional Location records.
Any related Human Resource records that make up the Team Member list.
Any Function, Functional Failure, Failure Mode, Failure Effect, and
Recommendation nodes included in the analysis.
Any related Risk Assessments.
Any Reference Documents that are linked to the analysis elements.
When you create an RCM Template from an analysis element other than the Analysis
node (i.e., a node that appears below the root Analysis node), the RCM Template will
include the selected node and all of its successor nodes. The root node in the RCM
Template determines the nodes to which the template can be applied in a target RCM
Analysis, with respect to the record hierarchy. For example, an RCM Template whose
root node is a Failure Mode can be applied only to a Functional Failure node.
To create a new RCM Template from an existing RCM Analysis:
1. Open the desired analysis on the RCM Explorer page.
2. In the RCM Explorer pane, select the node that you want to use as the root node
in the RCM Template.
3. On the Template Tasks menu, click the Save as Template link.

A new RCM FMEA Template record appears in a new window.
On the RCM FMEA Template datasheet, the following fields contain values by default:
The Type cell is disabled and populated automatically with the template
type value, which indicates the family of the record from which the
template was created.
The Analysis Type cell is disabled and populated automatically with

RCM.
The Author cell is disabled and populated automatically.
The Created On cell is disabled and populated automatically.
4. Provide values in the fields on the datasheet, as needed.

5. Click OK.
The new template is created and appears on the RCM Template Explorer page, where you
view and modify its contents. At this point you can use the template to create or modify
RCM Analyses.
About Creating New RCM Analyses

from RCM Templates
You can create a new RCM Analysis from any RCM Template whose root node is the
RCM Analysis node. Depending upon whether the RCM Template is associated with
RCM Asset records or not, the steps that you perform to create the new analysis will vary.
If you are applying an RCM Template that is not associated with any RCM FMEA
Asset records, you will follow a one-step template application process via the
RCM Templates page.
If you are applying an RCM Template that is associated with at least one RCM
FMEA Asset record, you will use the Apply Template Builder, which provides
an option for you to keep the virtual equipment and locations associated with the
template or replace them with Equipment and Functional Location records in the
Meridium APM database.
Creating a New Analysis from an RCM

Template without RCM FMEA Asset
Records
The following instructions provide details on creating a new RCM Analysis from an
RCM Template that is not linked to any RCM FMEA Asset records. These instructions
assume that the Analysis node is the root node of the RCM Template you are using to
create a new RCM Analysis.
To create a new RCM Analysis from an RCM Template:
1. Access the RCM Templates page.
2. In the results grid, select the row containing the RCM Template that you want to
use to create a new RCM Analysis.
3. On the Template Tasks menu, click the Create Analysis link.
The RCM Analysis is created and displayed on the RCM Explorer page where you can
view and modify its contents.
Accessing the Apply Template Builder

The following instructions provide details on accessing the Apply Template Builder,
which you can use to create a new RCM Analysis from a template and specify whether
you want to keep or replace the RCM FMEA Asset record(s) that are associated with the
template.
These instructions assume that the RCM Template that you are using to create a new
RCM Analysis is associated with at least one RCM FMEA Asset record.
To access the Apply Template Builder:
2. In the results grid, select the row containing the RCM Template that you want to
use to create a new RCM Analysis.
3. On the Template Tasks menu, click the Create Analysis link.
Using the Apply Template Builder to

Create a New RCM Analysis
Using the Apply Template Builder, you can choose to keep or replace any RCM FMEA
Asset record that is associated with the template that you are using to create a new RCM
Analysis. These instructions assume that the template is associated with at least one RCM
FMEA Asset record.
To create a new RCM Analysis using the Apply Template Builder:
1. Access the Apply Template Builder.
The Review Template Assets screen appears, displaying the list of RCM FMEA Asset
records that are associated with the RCM Template. Below the grid, the Keep these assets
option is selected by default.
3. If you want to apply to the new RCM Analysis all the RCM FMEA Asset records
that are associated with the template, accept the default option and click the
Finish button.
Note: If you choose the Keep these assets option, the new RCM Analysis will not be
linked to any Equipment or Functional Location records (i.e., physical equipment and
locations).
-orIf you want to replace the RCM FMEA Asset records that are associated with the
template, select the Replace these assets with new selections option, and then click the
Next button.
The Select Asset Replacements screen appears.
4. On the Select Asset Replacements screen, click the Select Replacements button.
Note: The Search In list contains only families that are related to the RCM FMEA Asset
family through the Is RCM FMEA Asset relationship.
5. In the Search In list, select the family whose records you want to link to the RCM
Analysis, and then click the Find Now button.
The results appear in the grid.
6. Select the records that you want to use as replacements for the RCM FMEA Asset
records that are currently linked to the RCM Template, and then click the Select
button.
The system checks to see if the selected equipment and locations can be added to the
analysis.
1.
o
7.
If any cannot be added to the analysis, those records are displayed in a

separate window with a message indicating why the record cannot be
added.
The records that can be added to the RCM Analysis are displayed in the
grid on the Select Asset Replacements screen. The records are grouped by
Asset Class.
7. You can continue adding Equipment and Functional Location records in this way.
When you are finished, click the Next button.
The Review/Replace Template Assets screen appears.
This screen contains two columns:

1.
o
Template Asset: Contains the RCM FMEA Asset records that are currently
associated with the RCM Template.
Asset: Contains a list that you can use to specify what you want to do with
the RCM FMEA Asset record in that row. The Asset list contains the
following values:
o
(Keep Template Asset): Indicates that you want to add the RCM
FMEA Asset record to the RCM Analysis without linking it to an
Equipment or Functional Location record. This option is selected
by default.
(Discard Template Asset): Indicates that you do not want to add the
RCM FMEA Asset record to the RCM Analysis. Note that this
option does not delete the RCM FMEA Asset from the RCM
Template.
<Selected Assets>: The Equipment and Functional Location

records that you selected in the previous steps.
9. For each RCM FMEA Asset record in the Template Asset column, select the
option in the Asset column that corresponds to the action that you want to take.
The Review/Replace Template Asset Assignments screen appears, where the Failure
Mode records that are associated with the template appear in rows, as shown in the
following image.
This screen contains the following items:

11.
o
Failure Mode: Contains the names of the Failure Mode that are linked to
the RCM Template. Each Failure Mode appears in a separate row. This
row serves as a grouping for the values that appear in the Template Asset
Assignment and Asset Assignment columns.
Template Asset Assignment: Contains the ID of the RCM FMEA Asset

records that are linked to the Failure Modes in the template. If the Failure
Mode is not linked to one of these records, this cell will be blank.
Asset Assignment: Contains options that you can use to specify the
Equipment or Functional Location record, if any, you want to link to the
Failure Mode in the same row. The values that appears in this list by
default are determined based upon your selection in the previous step. This
list contains the following options:
o
(No Asset Assignment): Indicates that you do not want to link an

Equipment or Functional Location record to the Failure Mode.
<Selected Asset>: The Equipment, Functional Location, and RCM
FMEA Asset records that you selected on previous screens.
12. For each Failure Mode in the Template Asset Assignment column, select the
option in the Asset Assignment list that corresponds to the action that you want to
take.
The new RCM Analysis is created and appears on the RCM Explorer page, where you
can view and modify its contents.
Creating New Nodes Using an RCM

Template
The following instructions provide details on adding nodes to an existing RCM Analysis
using an RCM Template whose root node is a node other than the Analysis node (e.g.,
Failure Mode).
To create new analysis nodes using an RCM Template:
1. Open in the RCM Analysis to which you want to add nodes using a template.
2. In the RCM Explorer pane, select the node below which you want to add the new
nodes. For example, if you want to add a new Failure Mode node below a
Functional Failure node, select the Functional Failure node.
3. On the Template Tasks menu, click the Load Templates link.
If you are applying a Function node, Functional Failure node, or Failure Mode node, the
Apply Template Builder appears, which gives you the option to keep or replace any RCM
FMEA Asset record that is associated with the template. In this case, see the section of
the documentation for applying a Function, Functional Failure, or Failure Mode node to a
current RCM Analysis.
-orIf you are applying a Failure Effect node or a Recommendation node, the Templates
window appears, displaying a list of templates that you can use to add new nodes to the
current RCM Analysis.
This list contains only the templates whose root nodes can be added as a successor to the
node that is currently selected in the RCM Analysis. For example, if an RCM Failure
Mode node is selected, the Templates window will display all the RCM FMEA Templates
whose root node is a Failure Effect node. Because RCM FMEA Template records can be
used in both RCM and FMEA Analyses, you may see both RCM Templates and FMEA
Templates in this list.
4. Select the row containing the RCM FMEA Template record whose nodes you
want to add to the RCM Analysis, and then click OK.
The nodes in the RCM Template are added to the RCM Analysis as successors to the
currently selected node.
Accessing the Apply Template Builder to

Apply an RCM Analysis Node
You can use the Apply Template Builder to apply to an existing RCM Analysis a template
whose root node is a Function, Functional Failure, or Failure Mode. When you apply a
template in this way, you will have the option to replace the RCM FMEA Asset records
from the template with Equipment or Functional Location records in the analysis.
To access the Apply Template Builder to apply a Function, Functional Failure, or Failure
Mode node and its successors:
1. In the RCM Explorer pane, select the node to which you want to add successor
nodes. For example, if you want to add an RCM Function node, you must select
the RCM Analysis node in the tree.
2. On the Template Tasks menu, click the Load Template link.

Add Function, Functional Failure, or
Failure Mode Nodes to an Analysis
The following instructions provide details on using the Apply Template Builder to add
nodes to an existing analysis using a template whose root node is a Function, Functional
Failure, or Failure Mode. Failure Mode nodes can be applied via an RCM or FMEA
template.
Note: You can also use these instructions to create new template elements in an RCM
Template.
To use the Apply Template Builder to create a new RCM Analysis node:
1. Access the Apply Template Builder.

If you are applying a Function or Functional Failure node, the Select Template screen
appears.
If this screen appears, skip step 3, and proceed to step 4.

-orIf you are adding a Failure Mode node, the Select Type screen appears. In this case, you
can select to apply either an RCM FMEA Failure Mode Template or an FMEA Asset
Template to the current analysis.
3. Select the option that represents the type of template you want to apply, and then
click the Next button. You can choose from the following options:
RCM FMEA Failure Mode template
FMEA Asset template
The Select Template screen appears, as shown in the image following step 2. The
workspace will be titled according to the template type that you selected on the previous
screen (i.e., either RCM FMEA Failure Mode or FMEA Asset).
4. On the Select Template screen, select the row containing the template that you
want to apply to the current analysis, and then click the Next button.
The Review/Replace Template Asset Assignments screen appears.
This screen displays a grid with the following items:

5.
o
Failure Mode: Contains the names of the Failure Modes that are linked to
the RCM Template. Each Failure Mode appears in a separate row. This
row serves as a grouping for the values that appear in the Template Asset
Assignment and Asset Assignment columns.
o
Template Asset Assignment: The ID of the RCM FMEA Asset records that
are linked to the Failure Modes in the template. If the Failure Mode is not
linked to one of these records, this cell will be blank.
Asset Assignment: A list that contains the following values, which you can
use to specify what action you want to take with the Equipment,
Functional Location, or RCM FMEA Asset record in that row:
o
(Add to Analysis): Indicates that you want to add the RCM FMEA
Asset record to the target analysis and maintain the link between
the Failure Mode record as it exists in the template. This option is
selected by default in a row where an ID appears in the Template
Asset Assignment cell in that row but does not already appear in
the list of equipment and locations that exist for the target analysis.
(No Asset Assignment): Indicates that you do not want to create a

link between the Failure Mode record and a record representing a
piece of equipment or location. This option is selected by default in
a row where the Template Asset Assignment cell is empty for a
Failure Mode. You can select this option in a row where a record
ID appears in the Template Asset Assignment cell to indicate that
you do not want to maintain in the target analysis the link between
the Failure Mode and the record representing the piece of
equipment or location as it exists in the template.
<Asset IDs>: IDs of the existing records representing equipment

and locations that are already part of the target analysis. You can
select one of these options to indicate that you want to create a link
between the Failure Mode and the record with that ID in the target
analysis. This option is selected by default if a record with the
same ID already exists in the list of equipment and locations for
the target analysis.
6. For each Equipment or Functional Location record that appears in the Template
Asset Assignment column, select the option in the Asset Assignment list that
corresponds to the action that you want to take with that record in the analysis.
The RCM Explorer page returns to focus and the new analysis node has been added to the
tree.
Modifying Existing RCM Templates

To modify an existing RCM Template:
2. Use the query to locate the RCM Template that you want to modify.
3. In the grid, click the hyperlinked ID of the RCM Template that you want to
modify.
The RCM Templates Explorer page appears, displaying the selected RCM FMEA
Template record.
4. Modify the template as needed.

Deleting RCM Templates

The following instructions provide details on deleting an RCM Template via the RCM
Templates page. You can also delete an RCM Template via the RCM Template Explorer
page.
To delete an RCM Template:
2. In the grid, select the row containing the RCM Template that you want to delete.
3. On the Template Tasks menu, click the Delete Template link.
A confirmation message appears, asking if you really want to delete the selected RCM
Template.
The selected RCM FMEA Template record is deleted from the database and is removed
from the query results on the RCM Templates page.
About the RCM Template Explorer

Page
The RCM Template Explorer page is the page that you will use to work with RCM
templates. The layout of the RCM Template Explorer page is similar to that of the Record
Manager, where it is divided into three main areas:
The task menu pane, which contains the following task menus:
Analysis Tasks
Common Tasks
Template Tasks
Reports
Associated Pages
RCM Template Explorer pane.
The datasheet area, which displays the information stored in the record for the
selected node.
Throughout our discussion of the RCM Template Explorer page, we assume that you are
familiar with the basic concepts and navigational features of the Record Manager. We
limit our discussion primarily to features that are specific to the RCM Template Explorer
page or that deviate from the standard functionality of the Record Manager.
Accessing the RCM Template Explorer

Page
You can access the RCM Template Explorer page by performing the following tasks:
Modifying an existing RCM Template.

Creating a new RCM Template from scratch.
Creating an RCM Template from an existing RCM Analysis.
The following image shows what the RCM Template Explorer page looks when you
access it from an existing RCM Template.
About the RCM Template Explorer

Pane
When you open an RCM FMEA Template record on the RCM Template Explorer page,
in the RCM Template Explorer pane, the root node corresponds to the node from which
the template was created. Below the root record, the RCM Template Explorer pane
displays the other components of the template arranged in a hierarchy.
When you first open an RCM Template, only the root node and the nodes that represent
direct successor records of that root node appear in the RCM Template Explorer pane.
You can click the plus sign (+) to the left of any node to expand it and view the next
successor record that exists in the tree.
The RCM Template components are linked to one another through relationships that are
defined in the RCM data model. The following image shows an example of a fully
expanded branch of the tree. Notice that each template node is represented by an icon,
which distinguishes that analysis element in the tree.
Hint: You can also right-click any branch of the tree and then click Hide Children, Show
Children, or Show All as appropriate, to expand or collapse that branch.
When you select a node in the tree, the datasheet for that record is displayed in the
datasheet area on the RCM Template Explorer page.
Note that unlike the standard Record Explorer pane, which displays all the records in the
record hierarchy that are linked to the root record through any relationship, the RCM
Template Explorer pane displays only the records belonging to the families that make up
the RCM Template analysis, according to the RCM data model.
The Shortcut Menu in the RCM

Template Explorer Pane
The RCM Template Explorer pane contains a shortcut menu that appears when you rightclick any node in the tree. The shortcut menu contains the options that you can use to
work with the RCM Template and its components. The specific options that are available
on the menu will vary, depending on the node that is selected when you access the
shortcut menu. For example, the following image shows the options that appear on the
shortcut menu when you right-click a Function node.
The following options are available on the shortcut menu in the RCM Template Explorer
pane:
Save: Saves any changes that you have made to the record that is currently
selected.
Save as Template: Displays a new RCM FMEA Template record in a new
window, from which you can create a new RCM Template using the currently
selected node as the root node.
Load Template: Facilitates the creation of a new analysis elements by applying an
existing RCM Template to the currently selected node.
Cut: Removes the currently selected node and all its successor nodes from the tree
so that you can paste them in a different location. After you have cut a node, the
Paste option will appear on the shortcut menu so that you can paste the node in a
different location in the tree.
Copy: Copies the selected node. After you have copied a node, the Paste option
will appear on the shortcut menu so that you can paste a copy of that node in a
different location in the tree. If the selected template element has successor nodes,
a prompt appears, asking if you want to copy only the selected node or the
selected node and all its successor nodes.
Paste: Pastes the cut or copied nodes in the selected location. Note that this menu
option appears only after you have copied or cut a node and if you select a
predecessor node that participates in a relationship with the node that you want to
paste.
Delete: Deletes the selected node and all its subnodes from the template and from
the database.
New <Node>: Where <Node> is the analysis element that you want to create. The
name of this link will change depending upon the predecessor node that is
selected in the tree. This link creates a new record in the family indicated by the
<Node> value and links it to the selected predecessor record. For example, if you
select a Function node, this link will be labeled New Failure and will result in the
creation of a new Functional Failure record that is linked to the Function record
that is represented by the selected Function node.

<Node> Reports: Where <Node> is the analysis element whose reports you want
to view. When you point to this link, a submenu appears and contains a list of
reports that are associated with the selected component. For example, when you
select an RCM Function node, this option will be labeled Function Reports. This
menu option appears only if reports exist for the family that is represented by the
selected node.
Show Children: Expands the hierarchy to display the successor nodes that appear
directly below a given node. This option appears only when you select a collapsed
predecessor node.
Hide Children: Collapses the hierarchy to hide the successor nodes that appear
directly below a given node. This option appears only when you select an
expanded predecessor node.
Show All: Expands ALL successor nodes that exist below the selected node.
Help: Displays the context-sensitive Help topic for the RCM Template Explorer
page.
About the Datasheet Area

The datasheet area appears to the right side on the RCM Template Explorer page and
displays the datasheet for the node that is currently selected in the RCM Template
Explorer pane. For example, when you select an RCM Failure Effect node in the RCM
Template Explorer pane, the datasheet area displays the Failure Effect record. The
following image shows an example of the datasheet area on the RCM Template Explorer
page. A red outline has been added to the image to highlight this area.
The features of the datasheet area, such as the buttons that appear above the datasheet
itself, are the same as those that are available in the Record Manager.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Template Explorer page contains links that you
can use to work with the analysis elements in the RCM Template Explorer pane. The
links on this menu are hidden or disabled based upon the node that is selected in the tree.
The Analysis Tasks menu on the RCM Template Explorer page contains the following
links:
Template Definition: Displays the datasheet for the current RCM FMEA Template
record. This link is available for all template types.
Manage Team: Displays the RCM Team Members page, where you can create and
manage Human Resource records for an RCM Analysis Template. This link
appears only when you are working with a template whose root node is an
Analysis node.
Set Up Assets: Displays the Manage Asset List page. This link appears only when
you are working with a template whose root node is an Analysis node.
Risk Assessment: Displays the Risk Assessment feature. This link is enabled only
when:
A Failure Effect node is selected in the tree.

A Recommendation node is selected in the tree and a value has been
selected for at least one Category in the corresponding unmitigated Risk
Assessment.
This link does not appear when you are working with a template whose root node is an
RCM Recommendation node.
Run Decision Logic: Displays the Decision Logic Builder. This link is enabled
only when you select a Failure Effect node in the tree. This link does not appear
when you are working with a template whose root node is an RCM
Recommendation node.
Manage Templates: Displays the RCM Templates page. By default, the value in
the Template Type query prompt is set to the Template Type of the template you
were previously viewing.
Create Template: Displays the Template Builder, which you can use to create a
new RCM Template from scratch.
Common Tasks Menu

The Common Tasks menu on the RCM Template Explorer page contains links that you
can use to work with the analysis elements in the RCM Template Explorer pane. These
links are hidden or disabled based on the node that is selected in the tree.
The Common Tasks menu on the RCM Template Explorer page contains the following
links:
New <Node>: Where <Node> is the analysis element that you want to create. The
name of this link will change depending upon the predecessor node that is
selected in the tree. This link creates a new record in the family indicated by the
<Node> value and links it to the selected predecessor record. For example, if you
select a Function node, this link will be labeled New Failure and will result in the
creation of a new Functional Failure record that is linked to the Function record
that is represented by the selected Function node.
Save: Saves the selected record.
Delete: Deletes the selected record and all its subnodes from the template and
from the database.
Cut: Removes the currently selected node and all its successor nodes from the tree
so that you can paste them in a different location. After you have cut a node, the
Paste option will appear on the shortcut menu so that you can paste the node in a
different location in the tree.
Copy: Copies the selected node. After you have copied a node, the Paste option
will appear on the shortcut menu so that you can paste a copy of that node in a
different location in the tree. If the selected template element has successor nodes,
a prompt appears, asking if you want to copy only the selected node or the
selected node and all its successor nodes.
Paste: Pastes the cut or copied nodes in the selected location. Note that this menu
option appears only after you have copied or cut a node and if you select a
predecessor node that participates in a relationship with the node that you want to
paste.
Print: Displays the Preview window. From the Preview window, you can select
print options and print the record.

can manage the Reference Documents associated with the selected record.
Page. This link is enabled only when you are viewing a saved analysis.
Help: Displays the context-sensitive Help topic for the RCM Template Explorer
page.
Template Tasks Menu

The Template Tasks menu on the RCM Template Explorer page contains the following
links:
Save as Template: Displays a new RCM FMEA Template record in a new

window, from which you can create a new RCM Template using the currently
selected node as the root node.
Load Template: Facilitates the creation of a new RCM Template node by applying
an existing RCM Template.
If you are applying a Function node, Functional Failure node, or Failure

Mode node, this link will display the Apply Template Builder.
If you are applying a Failure Effect node or a Recommendation node, this
link will open the Templates window, which displays a list of templates
that you can use for adding a new node to the selected node.
<Node> Reports Menu

The <Node> Reports menu on the RCM Template Explorer page displays the reports
associated with the node currently selected in the RCM Template Explorer pane. The
name of the menu will change as appropriate, depending on which node you select. For
example, when you select the root-level analysis node, the menu is labeled Analysis
Reports and displays a list of reports associated with the Analysis node, as shown in the
preceding image.
Each template node has a related folder in the Catalog that is used to determine which
reports to display for which template component. This menu appears only if reports exist
in the Catalog folder associated with the selected node.

The Associated Pages menu on the RCM Template Explorer page displays Associated
Pages that have been configured via the URL Manager for the family of the node that is
currently selected in the RCM Template Explorer pane.
Note: The Associated Pages menu will not be filtered based on the type of template that
you are viewing. Any Associated Page that you configured for a family that is used by
both RCM and FMEA Templates will appear when you are viewing an RCM Template
and when you are viewing an FMEA Template.
Accessing the RCM Asset List Page for

RCM Templates
To access the RCM Asset List page for an RCM Template:
While viewing an RCM Template on the RCM Template Explorer page, on the
Analysis Tasks menu, click the Set up Assets link.
-orOn the RCM Team Members page, on the Analysis Tasks menu, click the Set Up Assets
link.
The RCM Asset List page appears, displaying the RCM FMEA Asset records that are
linked to the current RCM Template.
About the RCM Asset List Page for

RCM Templates
The RCM Asset List page for RCM Templates contains similar features to the RCM
Asset List page that is configured for RCM Analyses. The RCM Asset List page contains
a grid that displays the list of RCM FMEA Asset records that are associated with the
template. Each row in the grid represents one RCM FMEA Asset record. For each RCM
FMEA Asset record, the following information is displayed:
Record ID: The Record ID of the RCM FMEA Asset record.

Description: The value stored in the Description field in the RCM FMEA Asset
record.
The RCM Asset List page also contains the following task menus, which let you perform
tasks specific to the equipment and location list: Analysis Tasks menu, Asset Tasks menu,
and Common Tasks menu.
From the RCM Asset List page, you can:
Add RCM FMEA Asset records to the current template.

Modify RCM FMEA Asset records that belong to the current template.
Delete RCM FMEA Asset records that belong to the current template.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Asset List page contains the following links:
Template Definition: Displays the RCM FMEA Template record for the associated
RCM Template.
View in Explorer: Displays the associated RCM Template on the RCM Template
Explorer page.
Manage Team: Opens the RCM Team Members page for RCM Templates, where
you can set up the team for the current template.
Asset Tasks Menu

The Assets Tasks menu on the RCM Asset List page contains the following links:
Create New: Displays a new RCM FMEA Asset record in a new window, where
you can define the new RCM FMEA Asset record and link it to the template.
Copy Existing: Displays the Find Asset Records dialog box, where you can search
for an existing RCM FMEA Asset record to create a copy of it and link it to the
analysis.
Edit: Displays the Edit Asset Record dialog box, where you can modify the
contents of the selected RCM FMEA Asset record.
Delete: After asking for confirmation, deletes the selected RCM FMEA Asset
record from the database.
Common Tasks Menu

The Common Tasks menu on the RCM Asset List page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the RCM Asset List page for
RCM Templates.
Accessing the RCM Team Members

Page for an RCM Template
To access the RCM Team Members Page for an RCM Template:
While viewing an RCM Template on the RCM Template Explorer page, on the
Analysis Tasks menu, click the Manage Team link.
-orWhile working with an RCM Template on the RCM Asset List page, on the Analysis
Tasks menu, click the Manage Team link.
The RCM Team Members page appears, displaying a list of Human Resource records that
have been defined for the associated RCM Template.
About the RCM Team Members Page

for RCM Templates
The RCM Team Members page for RCM Templates contains a grid that displays the list
of Human Resource records that make up the RCM Analysis Team. Each row in the grid
represents one Human Resource record. For each Human Resource record in the grid, the
following information is displayed:
Record ID: The Record ID of the Human Resource record.

Last Name: The value in the Last Name field in the Human Resource record.
The RCM Team Members page also contains three task menus, which let you perform
tasks specific to the RCM Analysis Team: Analysis Tasks, Team Members Tasks, and
Common Tasks.
From the RCM Team Members page, you can:
Add team members using existing Human Resource records.

Add team members by creating new Human Resource records.
Modify information about a team member by modifying the corresponding

Human Resource record.
Remove team members from the RCM Analysis Team.
Analysis Tasks Menu

The Analysis Tasks menu on the RCM Team Members page contains the following links:
Template Definition: Displays the RCM FMEA Template record for the associated
RCM Template.
View in Explorer: Opens the current RCM Template on the RCM Template
Explorer page.
Set Up Assets: Displays the RCM Asset List page for RCM Templates, where you
can manage the equipment and location list for the template.
Team Member Tasks Menu

The Team Members Tasks menu on the RCM Team Members page contains the following
links:
Create New: Displays the Create New Team Member dialog box, where you can
create a new Human Resource record and add that person to the RCM Analysis
Team.
Add Existing: Displays the Find a Human Resource dialog box, where you can
search for existing Human Resource records to add to the RCM Analysis Team.
Edit: Displays the Edit Team Member dialog box, where you can modify the
information stored in the selected Human Resource record.
Remove: After asking for confirmation, removes the selected Human Resource
record from the RCM Analysis Team. Note that this does not delete the Human
Resource record from the database.
Common Tasks Menu

The Common Tasks menu on the RCM Team Members page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the RCM Team Members page
for RCM Templates.
Introduction to RCM Reports

Meridium APM supports two types of reports in RCM:
Reports that are generic and apply to any analysis.
Reports that apply to a specific analysis or analysis node.
RCM relies upon the Catalog folder structure to determine which reports appear where
throughout the RCM interface. Each analysis element has a corresponding Catalog folder.
When you are viewing that analysis element, the reports stored in the associated Catalog
folder will be available.
For example, when you are viewing an RCM Analysis on the RCM Explorer page and
you select a Function node, the Function Reports menu will display a list of reports stored
in the following Catalog folder: \\Public\Meridium\Modules\RCM\Function. In addition,
the Catalog contains a generic folder for storing reports that appear on the RCM Reports
page and will apply to any analysis.
When you view an RCM report, the Meridium APM system will run the report and open
it on the Report Viewer page, where all the standard report functionality will be available
to you.
About Running Reports in RCM

The baseline RCM product contains a set of pre-configured RCM reports that you can run
when you are viewing an RCM Analysis on the RCM Explorer page. In addition, by
creating your own custom reports and storing them in the appropriate folder in the
Catalog, you will be able to access and view reports associated with given analysis node.
In addition, the baseline RCM product contains a Catalog folder for storing generic RCM
reports, which can be accessed easily from the RCM Start Page.
When you view an RCM report, the Meridium APM system will run the report and open
it on the Report Viewer page, where all the standard report functionality will be available
to you.
Accessing the RCM Reports Page

The RCM Reports page displays a list of generic reports that have been configured for
use with RCM. Generic RCM reports should be stored in the following Catalog
folder: \\Public\Meridium\Modules\RCM. The RCM Reports page will display any report
stored in that folder.
The RCM Reports page displays the caption of the report as it exists in the Catalog.
Therefore, when saving reports to the folder \\Public\Meridium\Modules\RCM, you will
want to make sure that you use captions that are descriptive enough to identify the
purpose of the report to other users.
Note: The baseline RCM implementation does not include any reports that will appear on
the RCM Reports page. By default, the baseline RCM product contains one baseline
report in the folder \\Public\Meridium\Modules\RCM: RCM AnalysisTeamSubReport.
Because this report is a sub-report of the RCM Analysis Description report, it is
automatically filtered out of the reports list and not displayed on the RCM Reports page.
Any other report that you store in the folder \\Public\Meridium\Modules\RCM will,
however, appear on this page.
To access the RCM Reports page:
On the RCM Start Page, click the Run Reports link.
The RCM Reports page appears.
Opening a Report
The RCM Reports page displays a list of reports that are stored in the following Catalog
folder: \\Public\Meridium\Modules\RCM. Each report caption appears as a hyperlink.
To run a report that is displayed in the list on the RCM Reports page:
Click any hyperlinked report caption.
The results of the report appear on the Report Viewer page.
Running Reports Specific to an Analysis

or Analysis Element
Reports that have been defined for the root-level analysis node or for a specific analysis
element and stored in the correct folder in the Catalog will appear when you are viewing
an analysis or analysis element on the RCM Explorer page.
For example, when you are viewing an RCM Analysis on the RCM Explorer page and
you select a Function node, the Function Reports menu will display a list of reports that
are stored in the following Catalog folder: \\Public\Meridium\Modules\RCM\Function. In
addition, you can right-click any analysis node in the RCM Explorer pane and access a
shortcut menu which will also display a list of reports that have been configured for that
node.
To run an RCM report:
From any of these menus, click the name of the desired report.
The results of the report appear on the Report Viewer page.
About Managing RCM

Recommendations
You can access Recommendation Management and work with RCM FMEA
Recommendation records via the Analysis Tasks menu on the RCM Explorer page.
When you access Recommendation Management via RCM, additional options are
available for working with RCM FMEA Recommendation records.
Accessing Recommendation
Management from the RCM Explorer
Page
To review RCM recommendations and manage them in Recommendation Management:
1. Access the RCM Explorer page.
2. On the Analysis Tasks menu, click the Review Recommendations link.
The Recommendation Management page appears, displaying a list of RCM FMEA
Recommendation records that exist for the current analysis.
Features of the Recommendation

Management Page when Accessed from
RCM
When you access Recommendation Management from an RCM Analysis, the
Recommendation Management page contains features in addition to those that are
available when you access the Recommendation Management page directly.
This page is divided in the following sections:
Recommendation Management workspace: Contains a grid that displays the

Recommendation records that are linked to the equipment and locations that are
associated with the current RCM Analysis.
Task menus: The following task menus are available: Recommendation Tasks
menu, Asset Tasks menu, Common Tasks menu, and Associated Pages menu.
Additionally, when you access the Recommendation Management page from RCM, a site
map appears at the top of the page and allows you to navigate back to the source analysis.
The following image shows an example of the Recommendation Management page when
accessed from RCM.
Asset Tasks Menu

The Asset Tasks menu is available when you access Recommendation Management from
RCM or FMEA.
The RCM FMEA Asset Tasks menu on the Recommendation Management page contains
the following links:
Promote to Strategy: Promotes to an Asset Strategy all the RCM FMEA Asset,
Equipment, or Functional Location records that are linked to the RCM FMEA
Recommendation records in the grid. This link is enabled only if the RCM FMEA
Recommendation records are linked to a record representing a piece of equipment
or location.
Promote to Template: Promotes to an Asset Strategy Template the RCM FMEA

Asset record that is linked to the selected RCM FMEA Recommendation record.
This link is enabled only if the selected RCM FMEA Recommendation record is
linked to an RCM FMEA Asset record.
Viewing Master Recommendations from

Consolidated Recommendations
If you have consolidated RCM Recommendation records to create a master RCM
Recommendation record, while you are viewing one of those consolidated
Recommendation records on the RCM Explorer page, you can access the master
Recommendation.
The following instructions assume that you are already viewing a consolidated RCM
Recommendation record on the RCM Explorer page (i.e., the state of the
Recommendation record is Consolidated).
You can determine the current state of the selected Recommendation record from the
visual indicator above the datasheet toolbar, as outlined in red in the following image.
To view a master Recommendation record from a consolidated Recommendation record:
On the RCM Explorer page, on the Analysis Tasks menu, click the View Master
Recommendation link.
The View Master Recommendation window appears, displaying the datasheet of the
master Recommendation record.
About Evaluations
After you create an RCM Analysis, you can define criteria for evaluating the whole
analysis or parts of the analysis in the future. Specifically, you can define criteria for
evaluating:
The entire analysis.

Any equipment or locations that are included in the analysis.
Any recommendations that are included in the analysis.
The evaluation feature allows you to be notified, or to notify someone else, when certain
conditions are met. You can create two types of evaluations:
A date-based evaluation, where email messages are sent on a one-time or

recurring basis and are triggered when the current date and time match the date
and time specified in the evaluation criteria.
An event-based evaluation, where email messages are sent when a piece of

equipment or location meets the failure cost and/or count criteria specified for the
evaluation.
If you want to evaluate an entire analysis, you can configure only a date-based
evaluation.
If you want to evaluate equipment, locations, or recommendations that are included in an
analysis, you can configure a date-based evaluation, an event-based evaluation, or both
types of evaluations for each piece of equipment, location, or recommendation.
After evaluation criteria exists and the RCM/FMEA Evaluation scheduled item is created
via the Meridium APM Schedule Manager, the scheduled item will be executed on the
Next Evaluation Date that is specified in the scheduled item. When it is executed, the
Meridium APM system will determine whether or not an email message should be sent
based on the existing evaluation criteria.
Note that evaluation criteria defined is stored in the associated record itself. For example,
if you define evaluation criteria for an analysis, the criteria is stored in the RCM FMEA
Analysis record. The facility for defining date-based evaluation criteria is essentially a
user interface that will guide you in populating fields in the associated record. Note that
the values that appear on the datasheet can be modified via the datasheet itself, provided
that you have the appropriate permissions. To ensure that you enter all the values
necessary for setting up valid evaluations, however, we recommend that you use the
evaluation interface instead of the datasheet.
About Analysis Evaluations

After you create an RCM Analysis, you can define criteria for evaluating the analysis in
the future to determine:
How valid the original analysis was.
Whether the analysis needs to be modified.
For each analysis, you can create a date-based evaluation, where email messages are sent
on a one-time or recurring basis and are triggered when the current date and time match
the date and time specified in the evaluation criteria.
When an email message is sent, it will contain the following information:
The description of the RCM Analysis for which the evaluation was configured, as
it is stored in the Analysis Short Description field in the RCM FMEA Analysis
record.
A statement indicating that the specified analysis needs to be reviewed.
A hyperlink that will open on the RCM Explorer page the RCM Analysis that
needs to be reviewed.
About Equipment/Location Evaluations

After you add equipment and locations to an RCM Analysis, you can define criteria for
evaluating each piece of equipment or location in the future to determine the status of the
piece of equipment or location and its failures. Note that the piece of equipment or
location can be represented by either an RCM FMEA Asset record itself or a related
Equipment or Functional Location record, depending on whether or not the RCM FMEA
Asset record has been linked to an Equipment or Functional Location record.
Two types of evaluations can be created for each piece of equipment or location:

An event-based evaluation, where email message are sent when the piece of
equipment or location meets the failure cost and/or count criteria specified for the
evaluation.
Note: Configuring an event-based evaluation at an equipment/location level results in the

same functionality as configuring an event-based evaluation at the recommendation level
for the piece of equipment or location that is related to that recommendation. Both
options will use the Evaluation Query to evaluate failures for that piece of equipment or
location. The only difference you will see is in the text of the email message that is sent.
If you set it up at the equipment/location level, the message will indicate that the piece of
equipment or location needs to be reviewed. If you set up the evaluation at the
recommendation level, the message will indicate that the recommendation needs to be
reviewed. It is up to you to determine if you want to create the event-based evaluation at
the equipment/location level or the recommendation level. Your decision will probably
depend on whether you want the email recipients to evaluate the entire piece of
equipment or location or the specific recommendation.
The ID of the RCM FMEA Asset record that identifies the piece of equipment or
location for which the evaluation was configured.
A statement indicating that the specified piece of equipment or location needs to
be reviewed.
A hyperlink that will open on the RCM Explorer page the RCM Analysis to which
the specified piece of equipment or location belongs.
Note that the content for date-based and event-based evaluation email is the same and
cannot be customized.
About Recommendation Evaluations

After you create Recommendation records for an RCM Analysis, you can define criteria
for evaluating each recommendation in the future to determine:
How valid the original recommendation was.

Whether the recommendation needs to be modified.
Whether additional recommendations should be created based on the validity of a

given recommendation.
Two types of evaluations can be created for each recommendation:

An event-based evaluation, where email messages are sent when the piece of
equipment or location related to the recommendation meets the failure cost and/or
count criteria specified for the evaluation.
Note: Configuring an event-based evaluation at a recommendation level results in the

same functionality as configuring an event-based evaluation at the equipment/location
level for the piece of equipment or location that is related to that recommendation. Both
options will use the Evaluation Query to evaluate failures for that piece of equipment or
location. The only difference you will see is in the text of the email message that is sent.
If you set up the evaluation at the recommendation level, the message will indicate that
the recommendation needs to be reviewed. If you set it up at the equipment/location
level, the message will indicate that the piece of equipment or location needs to be
reviewed. It is up to you to determine if you want to create the event-based evaluation at
the recommendation level or the equipment/location level. Your decision will probably
depend on whether you want the email recipients to evaluate the specific
recommendation or the entire piece of equipment or location.
The ID of the RCM FMEA Recommendation record for which the evaluation was
configured.
A statement indicating that the specified recommendation needs to be reviewed.
A hyperlink that will open on the RCM Explorer page the RCM Analysis to which
the specified Recommendation record belongs.
Note that the content for date-based and event-based evaluation email is the same and
cannot be customized.
About Date-Based Evaluations

A date-based evaluation is an evaluation that triggers an email message to be sent one
time or on a recurring basis, according to the schedule that you define. With date-based
evaluations, the only criteria that must be defined are date and time. Therefore, you can
set up date-based evaluations if you want to review an analysis, equipment or location, or
recommendation on a specific date or on a specific schedule.
When you create a date-based evaluations, you define a Next Evaluation Date. When the
RCM/FMEA Evaluation scheduled item is executed, an email message will be generated
for every item whose date-based criteria indicates that it is due for evaluation.
If you set up date-based evaluation criteria to generate a one-time evaluation email, after
the message has been sent, no additional messages will be sent. For example, suppose
you configure a one-time date-based evaluation for an RCM Analysis and enter a Next
Evaluation Date of 5/15/2010. If the RCM/FMEA Evaluation scheduled item is executed
on 5/14/2010, a message will not be sent. If, however, the scheduled item is executed on
5/15/2010, a message will be sent. If the scheduled item is executed again a day later on
5/16/2010, another message will not be sent.
Note: After a message for a one-time date-based evaluation is sent, the evaluation criteria
will continue to be stored in the record, but no additional messages will be sent. To reenable the evaluation and send a new message, you must modify the evaluation criteria in
some way.
You can also specify that you want to evaluate an analysis, the piece of equipment or
location, or recommendation on a recurring schedule. For recurring, date-based
evaluations, after the scheduled item is executed the first time, the Next Evaluation Date
is updated in both the record (e.g., RCM FMEA Analysis record) and in the scheduled
item, according to the interval that you define. The scheduled item is then executed on the
next evaluation date, after which the Next Evaluation Date is updated again, and so on,
indefinitely or until you disable evaluations.
For example, you may want to implement a policy such that all recommendations should
be reviewed six months after they are created. In this case, a one-time, date-based
evaluation would be appropriate. Or you may want recommendations to be reviewed
once every year, in which case you would use a recurring, date-based evaluation.
Regardless of the desired schedule, as long as date and time are the only criteria that must
be met, you can set up a date-based evaluation.
Setting up a Date-Based Evaluation

A date-based evaluation is an evaluation that will be sent one time or on a recurring basis,
according to the schedule that you define. In date-based evaluations, the only criteria that
must be met are date and time. Therefore, you can set up date-based evaluations if you
want to review an analysis, piece of equipment or location, or recommendation on a
specific date or on a specific schedule. For example, you may want to implement a policy
that all recommendations should be reviewed six months after they are created. Or you
may want recommendations to be reviewed once every year. Regardless of the desired
schedule, as long as date and time are the only criteria that must be met, you can set up a
date-based evaluation.
To set up a date-based evaluation:
1. Open the desired analysis.
2. Expand the analysis hierarchy until you find the node for which you want to set
up evaluation criteria.
3. Select the node, and then on the Analysis Tasks menu, click the Set Up Evaluation
link.
The Set Up <Node> Evaluation dialog box appears, where <Node> is the type of node
that is currently selected in the RCM Explorer pane.
4. Select the Date-based evaluation check box.

The Date-Based Evaluation dialog box appears.
5. In the Next evaluation date text box, type the next date for the evaluation to occur.
Note that:
If you are defining criteria for a one-time, date-based evaluation, the Next
evaluation date represents the one-and-only date and time that the
evaluation email message will be sent.
If you are defining criteria for a recurring evaluation, the Next evaluation
date represents the first date and time that the evaluation email message
will be sent. Subsequent messages will be sent at intervals defined in the
Every fields. Each time an evaluation message is sent, the Next evaluation
date will be incremented according to the specified interval. The updated

value can be viewed on the Evaluation tab of the FMEA Recommendation
datasheet and on the Date-based Evaluation dialog box. The time,
however, will always be the same as what you first set in the Next
evaluation date field.
6. If you want the evaluation to be performed on a recurring basis:
a. Select the Perform this evaluation on a recurring basis check box. Doing
so will enable the Every fields.
b. In the Every text box, type a value representing the interval on which the
re-evaluation should occur.
c. In the list to the right of the text box, select a unit of time (Days, Weeks,
Months, or Years) to define the specified interval.
For example, if you type 6 and select Months, the evaluation email will be sent first on
the Next evaluation date and then every six months after that.
7. In the Notify text box, type the email address to which the evaluation email
should be sent. You must supply a valid email address in order to set up a
functional evaluations.
Note: If you are defining both date-based and event-based evaluation criteria, the email
address for both must be the same. This is because the record contains one email address
field that is used by both evaluation types. For this same reason, if you have already
defined event-based evaluation criteria for an item, the email address that you specified
for the event-based evaluation will appear in the Notify field on the Date-based
evaluation dialog box.
8. Click OK.
The evaluation criteria are saved, and the Date-based Evaluation dialog box closes. Note
that the Date-based evaluation check box is selected on the Set Up Recommendation
dialog box, indicating that date-based criteria have been defined.
9. Click OK to close the Set Up <Node> Evaluation dialog box.
-orSelect the Event-based evaluation check box to define event-based evaluation criteria.
About Event-Based Evaluations

If your RCM system has been properly configured and your RCM Analysis contains all
the necessary components, it will contain RCM FMEA Asset nodes that are linked to
Equipment or Functional Location records, and each RCM FMEA Recommendation
record will be associated with a specific piece of equipment or location. By setting up
event-based evaluation criteria, you can configure the Meridium APM system to send
evaluation email messages based on the failure data that is associated with that piece of
equipment or location. Specifically, event-based evaluations let you specify that when a
given piece of equipment or location exceeds a certain number of failures or a certain
failure cost, an email message should be sent to the specified person.
Event-based evaluation scheduled items are executed for the first time on the Starting
from date, which you define when you set up the event-based evaluation. After that, they
will be executed daily, at the time specified in the Starting from field. Each time the
Meridium APM system runs an event-based evaluation scheduled item, it executes the
Evaluation query and sends an email message only if the Count and Cost returned by the
query are greater than the count and cost defined in the event-based evaluation criteria.
Setting Up an Event-Based Evaluation

If your RCM system has been properly configured and your RCM Analysis contains all
the necessary components, it will contain RCM FMEA Asset records (which can be
linked to Equipment or Functional Location records), and each RCM FMEA
Recommendation record will be associated with a specific piece of equipment or
location. By setting up event-based evaluation criteria, you can configure the Meridium
APM system to send evaluation email messages based on the failure data that is
associated with a piece of equipment or location. Specifically, event-based evaluations let
you specify that when a given piece of equipment or location exceeds a certain number of
failures or a certain failure cost, and email should be sent to the specified person.
Note: For event-based evaluations to work properly, the Evaluation query must first be
created and defined. These instructions assume that the Evaluation query has already
been set up.
To defined event-based evaluation criteria:

2. Expand the analysis hierarchy until you find the RCM FMEA Asset node or the
Recommendation node for which you want to set up evaluation criteria.
3. Select the desired node, and then on the Analysis Tasks menu, click the Set Up
Evaluation link.
4. Select the Event-based evaluation check box.
The Event-Based Evaluation dialog appears.
5. If you want to send evaluation email messages based on the number of failures
that occur for a given piece of equipment or location, select the Failure count
greater than check box, and in the text box, type the number of failures that must
occur before an evaluation email message will be sent to the email address
specified in the Notify field.
Hint: Accept the default value of 0 (zero) if you want the first failure to trigger a
evaluation message.
6. If you want to send evaluation email messages based on the total failure cost
associated with a piece of equipment or location, select the Failure cost greater
than check box, and in the text box, type a value representing the failure cost that
must be exceeded before an evaluation email message will be sent.
Hint: Accept the default value of 0 (zero) if you want any failure cost to trigger an
evaluation message.
7. In the Starting from box, type the date after which you want to start counting
failures and adding up failure costs. When the RCM/FMEA Evaluation scheduled
item is run, it will take into consideration only the failures that occurred on this
date and later.
Note: Unlike date-based evaluations, which are executed according to a schedule that you
define and will result in the generation of a message each time they are run, event-based
evaluations are run for the first time on the Starting from date. After that, they will be
executed daily, at the time specified in the Starting from field. Each time the
RCM/FMEA Evaluation scheduled item is run, it executes the Evaluation query and
sends a message only if the count and cost returned by the query are greater than the
count and cost defined in the event-based evaluation criteria.
8. In the Notify text box, type the email address to which the evaluation email
should be sent. While Meridium APM performs no validation on this field, you
must supply a valid email address in order to set up a functional evaluation.
Note: If you are defining both date- and event-based evaluation criteria, the email address
for both has to be the same. This is because the records contain one email address field
that is used by both evaluation types. For this same reason, if you have already defined
date-based evaluation criteria for a record, the email address that you specified for the
date-based evaluation will appear in the Notify field on the Event-based evaluation dialog
box.
9. Click OK.
The evaluation criteria are saved, and the Event-based Evaluation dialog box closes. Note
that the Event-based evaluation check box is selected on the Set Up <Node> Evaluation
dialog box, indicating that event-based criteria have been defined.
10. Click OK to close the Set Up <Node> Evaluation dialog box.
-orSelect the Date-based evaluation check box to define date-based evaluation criteria.
Modifying Evaluation Criteria

You can use the following instructions to modify the date- or event-based evaluation
criteria that you have already defined.
To modify existing evaluation criteria:
2. Expand the analysis hierarchy until you find the node for which you want to set
up evaluation criteria.
3. Select the desired node, and on the appropriate Analysis Tasks menu, click the Set
Up Evaluation link.
4. Click the Set Up button to the right of the criteria that you want to modify.
5. The Date-based Evaluation or Event-based Evaluation dialog box appears, as
appropriate.
6. Modify the criteria, as desired.
Note: Keep in mind that if both types of criteria are set, modifying the email address for
one will also modify the email address for the other. Note also that modifying the email
address may re-trigger one-time, date-based evaluations that have already been executed.
7. When you are finished modifying the criteria, click OK to save your changes.
Disabling Recurring Evaluations

After you define evaluation criteria for a analysis, piece of equipment or location, or
recommendation, the criteria will continue to be stored in the corresponding record until
you clear the values manually. The criteria will continue to trigger evaluation email only
as long as the evaluations are enabled. To disable evaluations, simply clear the check
boxes on the Set Up <Node> Evaluation dialog box appears, where <Node> is the type of
node that is currently selected in the RCM Explorer pane.
While this will not clear the evaluation criteria, it will discontinue the evaluation email.
About the Catalog Folder Structure for

RCM Reports
RCM uses the Catalog folder structure to determine which reports to display where
throughout the RCM interface. You will need to understand how the folder structure is
used in order to interpret the reports that appear when you are viewing an analysis and to
know where to store custom reports, depending on where you want them to be available.
The following table provides a list and description of the RCM folders that exist by
default in the Catalog.
Folder
\\Public\Meridium\Modules\RCM
\\Public\Meridium\Modules\RCM\Analysis
Behavior and Usage

Used to store generic reports related
to RCM Analyses. The reports
stored in this folder will appear on
the RCM Reports page.
Used to store reports related to the
RCM Analysis node, which is the
root-level node in an RCM Analysis.
These reports appear on the
Analysis Reports menu when you
select the Analysis node in the RCM
Explorer pane.
Several baseline reports are
provided in this folder.
\\Public\Meridium\Modules\RCM\Effect

RCM FMEA Failure Effect records
in an RCM Analysis. These reports
appear on the Effect Reports menu
when you select the Failure Effect
node in the RCM Explorer pane.
\\Public\Meridium\Modules\RCM\Equipment List

RCM FMEA Asset records in an
RCM Analysis.
\\Public\Meridium\Modules\RCM\Failure

RCM Functional Failure records in
an RCM Analysis. These reports
appear on the Failure Reports menu
when you select the Functional
Failure node in the RCM Explorer
pane.
\\Public\Meridium\Modules\RCM\Function

RCM Function records in an RCM
Analysis. These reports appear on
the Function Reports menu when
you select the Function node in the
RCM Explorer pane.
\\Public\Meridium\Modules\RCM\Mode
RCM FMEA Failure Mode records

in an RCM Analysis. These reports
appear on the Mode Reports menu
when you select the Failure Mode
node in the RCM Explorer pane.
\\Public\Meridium\Modules\RCM\Recommendation Used to store reports related to the
records in an RCM Analysis. These
reports appear on the
Recommendation Reports menu
when you select the
Recommendation node in the RCM
Explorer pane.
\\Public\Meridium\Modules\RCM\SSRS
Used to store reports that were used

in a previous release. This Catalog
folder and its contents are not used
by the Meridium APM product.
Baseline RCM Reports

By default, the baseline RCM product contains a set of pre-configured reports for use
with RCM. If desired, you can customize these reports or use them as the basis for
creating your own reports. The following table contains a list and description of the
baseline RCM reports that are delivered with the baseline RCM product. Note that the
Stored In column contains an abbreviated Catalog path, where each of the folders is a
subfolder within the Catalog folder \\Public\Meridium\Modules.
In this table, the values listed in the Report column refer to the report names. The
baseline captions are the same as the names.
Note that the Catalog folder \\Baseline\Meridium\Modules contains subfolders that match
the folders listed in the table. These folders contain copies of the reports that are
delivered as baseline RCM content. The items in the \\Baseline folder cannot be modified
and serve as a historical record of the items that were delivered with the baseline product.
The Meridium APM system reads from the subfolders in the \\Public folder, so the
reports in the Baseline folder are not actually used. The \\Baseline folder will be updated
with any changes made to the baseline content in future releases.
Note: Because these reports provide a formatted view of the information stored in your
analyses, for them to work properly, your analyses must contain accurate, complete data.
In addition, note that for complex analyses, the reports may span multiple pages.
Report
Stored In
Behavior and Usage

Provides an overview of the analysis,
including the analysis name, analysis
description, and a list of the team members
and equipment and locations associated with
the analysis.
This report contains three sections of

information:
RCM Analysis Description RCM\Analysis
RCM
AnalysisTeamSubReport
RCM
The report header, which contains

identifying information about the
analysis.
The Associated Assets section, which
contains a list of all the equipment and
location associated with the Analysis,
grouped by equipment or location type.
The Team Member section, which
contains a list of analysis team members
that is generated by the report RCM
AnalysisTeamSubReport, sorted by last
name, first name, and then middle
initial.
Used by the report RCM Analysis

Description to insert a list of team members
involved in the analysis. Note that although
this report is stored in the folder
\\Public\Meridium\Modules\RCM, the
Meridium APM system is hard coded not to
display this report on the RCM Reports
page.
Provides details of the functions, functional

RCM
RCM\Analysis failures, failure modes, and failure effects
FailureModeEffectsAnalysis
associated with a given RCM Analysis.
RCM Recommendations
Provides details about each recommendation

for all the failure modes in the analysis.
Additional, related information such as
RCM\Analysis
Consequence and calculated Ranking are
also included in the report to provide context
for reviewing recommendations.
Failure Finding Activity

When you define an RCM recommendation and specify the Action Type as Failure
Finding, you can use the Failure Finding Activity cells, shown in the following image, to
calculate the failure finding task interval (FFI).
The following equation is used to calculate FFI:

FFI = MTIVE x [(n + 1)(MTED)/MMF]
1/n
Note that the information used for the FFI calculation is based upon the concepts in SAE
Standard JA1012, "A Guide to the Reliability-Centered Maintenance (RCM) Standard."
The process and terminology used in the FFI calculation are described in more detail in
this standards document. To use the Failure Finding Activity cells effectively, you will
need to be familiar with this standard.
In addition, the FFI calculation is based upon information in the book "ReliabilityCentered Maintenance" by John Moubray.
The following table describes the Failure Finding Activity cells in the Meridium APM
Framework.
Cell
Description
Stores the mean time between multiple failures.
MMF
For example, a 1 in 1,000,000 probability of a multiple failure in one year
implies a mean time between failures of 1,000,000 years.
The probability of multiple failures occurring in any one year is 1/MMF.
MTIVE Stores the mean time between failures of the protective device.
Stores the mean time between failures of the protected function.
MTED
For example, if the demand rate of the protected function is once in 200 years,
this equals a probability of failure for the protected function of 1 in 200 in any
one year, or a mean time between failures of the protected function of 200 years.
The probability of failure of the protected function in any one year is 1/MTED.
n
The number of protective devices.
System Code Tables Used by RCM

The following System Code Tables are used by RCM.
Table ID
MI_FUNCTION_SUB_TYPE Function Sub

Types
Used to populate the Sub Function list

in RCM Function records.
MI_FUNCTION_TYPE
Function Type
Used to populate the Function Type list

in RCM Function records.
SC_RECOM_RESOURCE
Recommended
Resource
Used to populate the Recommended

Resource list in RCM FMEA
URL Paths for RCM Features
The following table lists and describes the paths for accessing features in RCM. Note that
to construct a valid URL, you must prepend meridium:// to the paths listed in the
following table. In some cases, you must define parameters after the path in order to
create a functional link.
Note that there is one root address only for each RCM or FMEA feature, and the root
address accepts parameters that let you determine whether the feature will be specific to
RCM or FMEA. If you do not specify a parameter where a parameter is accepted, the root
address will launch the feature for RCM and not FMEA. To launch the feature for FMEA,
you must expand the root address by adding parameters.
Feature
Start Page
URL Path
Description
RCM
Displays the RCM Start Page.
Administration
RCM/Admin
Page
Displays the RCM Administration page.
Manage Tasks
Page
RCM/Approver Displays the RCM Manage Tasks.
Analysis List
RCM/Find
Recent Analyses RCM/Recent
Templates
Reports
Displays the RCM Recently Used Analyses page,

from which you can open an existing analysis.
Displays the RCM Templates page, where you

can use templates to create a new analysis or
RCM/Templates analysis node. In addition to the Type parameter,
this path accepts parameters that let you
customize the URL.
RCM/Report
Team Member
RCM/List
and Asset Lists
Explorer
Displays the RCM Analysis List page, from

which you can open an existing analysis.
Displays the RCM Reports page, where you can

view a list of reports that have been configured
for RCM.
Displays the RCM Team Members or RCM Asset
List page.
Serves as the path for accessing the RCM

Explorer page. In addition to the Type parameter,
RCM/Explorer
the path requires parameters which allow you to
create a new analysis or load an existing analysis.
Parameters for the Start Page URL

The URL for accessing the RCM Start Page is meridium://RCM. A link constructed from
this path with no parameters will display the RCM Start Page.
Note: This path accepts one parameter that lets you modify the URL to access the FMEA
Start Page.
Examples of the Start Page URL
meridium://RCM
Displays the RCM Start Page.
Parameters for the Administration Page

URL
The URL for accessing the RCM Administration page is meridium://RCM/Admin. A link
constructed from this path with no parameters will display the RCM Administration page.
Examples of the Administration Page

URL
meridium://RCM/Admin
Displays the RCM Administration page.
Parameters for the Manage Tasks URL

The base URL for the RCM Manage Tasks page is meridium://RCM/Approver. A link
constructed from the base URL with no parameters will display the RCM Manage Tasks
page.
Manage Tasks page.
Examples of the Manage Tasks URL
meridium://RCM/Approver
Opens the RCM Manage Tasks page, which displays a list of RCM Analyses that have
associated Task records.
Parameters for the Analysis List URL
The URL for accessing the RCM Analysis List page is meridium://RCM/Find. A link
constructed from this path with no parameters will display the RCM Analysis List page.
Analysis List page.
Examples of the Analysis List URL
meridium://RCM/Find
Displays the RCM Analysis List page, from which you can open an existing RCM
Analysis in the RCM Explorer.
Parameters for the Recently Used

Analyses URL
The URL for accessing the RCM Recently Used Analyses page is
meridium://RCM/Recent. A link constructed from this path with no parameters will
display the RCM Recently Used Analyses page.
Recently Used Analyses page.
Examples of the Recently Used Analyses

URL
meridium://RCM/Recent
Displays the RCM Recently Used Analyses page, where you can open an existing
analysis in the RCM Explorer.
Parameters for the Templates URL

The URL for accessing the RCM Templates page is meridium://RCM/Templates. A link
constructed from this path with no parameters will display the RCM Templates page. The
path accepts the following additional parameters.
Note: This path also accepts the Type parameter that lets you modify the URL to access
the FMEA Templates page.
Parameter
Name
Accepted
Notes
Value(s)
This parameter is required whenever you
want to use a Template to create a new
The Entity Key of
analysis node. Whenever you specify the
the analysis to
A numeric SelectedKey parameter, you must also
which the entity
Entity
use the AnalysisKey parameter, even if
identified by the
Key.
the AnalysisKey and the SelectedKey
AnalysisKey SelectedKey value
are the same value (i.e., if you are
is linked.
loading templates to link to the analysis
node).
Description
This parameter is required whenever you

The Entity Key of
A numeric want to use a Template to create a new
the entity to which
SelectedKey
Entity
analysis node. Whenever you specify the
you want to link a
Key.
SelectedKey parameter, you must also use
new analysis node.
the AnalysisKey parameter.
Examples of the Templates URL
meridium://RCM/Templates
Displays the RCM Templates page. Note that accessing the RCM Templates page in this
way is like accessing it from the RCM Start Page, where you can find analysis templates
and use them to create a new RCM Analysis. Note that because the Context parameter
has been omitted, clicking a hyperlinked Template ID will load the analysis template on
the RCM Explorer page.
meridium://RCM/Templates?SelectedKey=1234567&AnalysisKey=2345678
Opens the RCM Templates page, where you can search for templates that can be linked to
the record identified by the key 1234567. For example, if entity 1234567 is a Failure
Mode record, you would want to find Failure Effect templates. From the list of templates,
you can click a hyperlinked Template ID to open analysis 2345678 on the RCM Explorer
page, where a new analysis node, based on the selected template, will be linked to entity
1234567.
Parameters for the Reports URL

The URL for accessing the RCM Reports page is meridium://RCM/Report. A link
constructed from this path with no parameters will display the RCM Reports page.
Reports page.
Examples of the Reports URL
meridium://RCM/Report
Displays the RCM Reports page, where you can view a list of reports that have been
configured for RCM Analyses and are stored in the Public\Meridium\Modules\RCM
folder in the Catalog.
Parameters for the Team Members and

Asset List URL
The base URL for accessing the RCM Team Members or RCM Asset List pages is
meridium://RCM/List. This URL accepts the parameters described in the following table.
Note that a URL constructed from the path with NO parameters is invalid.
Parameter
Name
Description
Accepted
Value(s)
Analysis
Specifies the analysis for

which you want to open
the team member or
list.
The Entity Key This parameter must be used

of the desired in conjunction with the
analysis.
ListType parameters.
ListType
Equipment
Lets you specify what you
want to set up for a given
Team
analysis.
Notes
This parameter should be used

in conjunction with the
Analysis parameter. These
parameter values are case
sensitive.
Examples of the Team Members and

Asset List URL
meridium://RCM/List?Analysis=64251517623&ListType=Team
Opens the RCM Team Members, where you can set up the Analysis Team for the analysis
with the Entity Key 64251517623.
meridium://RCM/List?Analysis=64251517623&ListType=Equipment
Opens the RCM Asset List page, where you can set up the equipment and location list for
the RCM Analysis with the Entity Key 64251517623.
Parameters for the Explorer URL

The URL for accessing the RCM Explorer page is meridium://RCM/Explorer. Note that
the URL path alone is not a valid URL. Use the information in the following table to
choose parameters that will allow you to construct a functional link.
Note: This path also accepts the Type parameter that lets you modify the URL to access
the FMEA Explorer page.
Parameter
Name
Description
Accepted
Value(s)
Notes
The Datasheet ID must correspond

to a datasheet that has been defined
The Datasheet
for the specified family. If you omit
Specifies the
ID of the desired
this parameter, the default datasheet
datasheet that
datasheet.
will be used. This parameter is
DatasheetID should be displayed
optional.
on the RCM
Explorer page.
EntityKey
FamilyKey
Specifies the Entity

Key of the record
that you want to
open on the RCM
Explorer page.
The numeric
Entity Key of
the entity that
you want to
open.
Specifies the Family

Key for record(s)
The numeric
that you want to
Family Key of
open on the RCM any family
This parameter value should

correspond to an entity belonging to
the family identified by the
FamilyKey parameter. This
parameter is required whenever you
are loading an existing analysis.
This parameter specifies the Family
Key of each root record. The
Family Key that you specify should
correspond to the EntityKey
Explorer page.
involved in an
RCM Analysis.
Mode
Used for creating a

Create
new analysis.
parameter value. This parameter is

required whenever you are loading
an existing analysis.
This parameter is required

whenever you want to load a new
analysis on the RCM Explorer page.
Examples of the Explorer URL
meridium://RCM/Explorer?Mode=Create
Opens a new RCM Analysis on the RCM Explorer page.
meridium://RCM/Explorer?EntityKey=1234567&FamilyKey=2345678
Opens the analysis with the Entity Key 1234567, which belongs to the family with the
Family Key 2345678.
Failure Effect
In an RCM Analysis, the consequence of a failure occurring. Most RCM methodologies
use failure effects to capture the safety, environmental, and economic (or production)
impact associated with a failure.
Failure Mode
In an RCM Analysis, the cause of a functional failure.
Function
In an RCM Analysis, the definition of what the owner of the system wants to do. A
system can have one or more functions, each of which is defined in a separate record.
Functional Failure
In an RCM Analysis, a way in which a function can fail.
RCM Analysis
A means for determining optimal maintenance and operational strategies based on the
probability and consequence of the analyzed failure modes. A Meridium APM RCM
Analysis consists of the following components:
Function
Functional Failure
Failure Mode
Failure Effect
Recommendation
Recommendation
In an RCM Analysis, the recommended action to take for a failure effect. Generally, for
the equipment or location and system owner, recommended actions should be designed to
reduce to an acceptable level the probability and consequence of the related failure.
SAE Standards
Technical standards and recommended practices for the aerospace, automotive, and
commercial-vehicle industries published by SAE International.
Overview of Failure Modes and Effects

Analysis
Whereas an RCM Analysis evaluates a system with respect to its function for the purpose
of determining how to avoid functional failures, a Failure Modes and Effects Analysis
(FMEA) Analysis focuses on the equipment and locations themselves and analyzes how
each piece of equipment or location can fail and the effect of each failure. In other words,
an RCM Analysis is conducted for the purpose of maintaining the function of a system.
An FMEA Analysis is conducted for the purpose of maintaining the system itself.
Specifically, FMEA is a method of identifying the potential failures of equipment and
locations, describing the possible effect of each failure, and making recommendations for
actions that can be taken to prevent the failures from occurring. In Meridium APM, an
FMEA Analysis consists of the following components:
Asset: After you create the root-level FMEA Analysis record, which serves as the
base record to which all analysis nodes are linked, you can define equipment and
locations, which define what is being analyzed by the FMEA Analysis. Each
FMEA Analysis can have one or more pieces of equipment or locations, which are
stored as RCM FMEA Asset records.
An FMEA Analysis can contain "virtual" equipment and locations, which are RCM
FMEA Asset records that are not linked to Equipment or Functional Location records,
and actual equipment and locations, which are RCM FMEA Asset records that are linked
to Equipment or Functional Location records.
Failure Modes: After you have defined the equipment and locations for an FMEA
Analysis, you can define one or more failure modes for each piece of equipment
and location. Failure modes describe the ways in which each piece of equipment
and location failure is likely to occur and are stored in RCM FMEA Failure Mode
records.
Failure Effects: For each failure mode, you can then define failure effects, which
describe the consequences of a failure occurring. Failure effects might describe
the safety, environmental, and economic (or production) impact associated with a
failure. In Meridium APM, you can define a Risk Matrix that will be available in
the analysis and can help you define the effects of each failure mode.
Recommendations: For each failure effect, one or more recommended actions can
be defined and stored in an RCM FMEA Recommendation record. A
Recommendation record defines what should be done to avoid the risk defined by
the Failure Modes and failure effects. Recommendations can be determined, in
part, using the Decision Tree document that has been set up for use with FMEA
Analyses.
In addition, for each FMEA Analysis, you can define an FMEA team, which is a list of
people who are involved in the analysis.
FMEA System Requirements

The RCM and FMEA license is required to take advantage of FMEA functionality. In
addition, your system must contain the basic Meridium APM system architecture.
perform some configuration tasks specifically for the FMEA module.
When the FMEA module is active, the Reliability Centered Maintenance (RCM) modules
is also active. You will also need to perform some configuration tasks specifically for
RCM.
Overview of the FMEA Data Structure

Within the FMEA module uses families to represent the various components of an FMEA
Analysis. Meridium APM leverages its fundamental entity and relationship family
infrastructure to store data related to an FMEA Analysis.
Each FMEA Analysis is represented at the root level by an RCM FMEA Analysis family
record. RCM Analyses use the same root analysis family. FMEA Analyses are
distinguished from RCM Analyses via the Analysis Type field in the RCM FMEA
Analysis record. The Analysis Type can be either RCM or FMEA. For an RCM FMEA
Analysis that will be used for an FMEA Analysis, the Analysis Type is FMEA.
Note: Because both RCM and FMEA Analysis records belong to the same family, a query
on the RCM FMEA Analysis family will return results that include all analyses of any
type. To limit your results to include only one analysis type, you will need to include the
Analysis Type field in your query and define criteria to filter on either RCM or FMEA.
For an FMEA Analysis (a record in which the Analysis Type is FMEA), the RCM FMEA
Analysis record can be linked to RCM FMEA Asset records through the Has RCM
FMEA Asset relationship. RCM FMEA Asset records can, in turn, be linked to RCM
FMEA Failure Mode records through the Has RCM FMEA Failure Mode relationship,
and so on, for all components of the analysis. Together, the root RCM FMEA Analysis
record and all the records that are linked to it, either directly or indirectly, make up the
FMEA Analysis.
Overview of the FMEA Data Model

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

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

Mode

Effect
Has RCM FMEA

Recommendation
The following families and relationship are also used by FMEA but not within the
analysis itself.
Records in this
entity family:
RCM FMEA
Analysis
RCM FMEA
Analysis
...Can be
linked to
records in
this entity
family:
...Through
this
Purpose
relationship:
Human
Resource

Has RCM
Analysis Team Members list. Through
FMEA Team this relationship, Human Resource
Member
records are linked directly to the RCM
FMEA Analysis record.
RCM FMEA
Has Tasks
Task
RCM FMEA
RCM FMEA Has Tasks
Recommendation Task
Allows Task records generated from

Recommendation records to be linked to
the RCM FMEA Analysis record for
which the recommendation was created.
Task records.
Allows RCM FMEA Recommendation
records to be linked to RCM FMEA Task
records that are generated from those
recommendations. Note that in the current

version of Meridium APM, RCM FMEA
Task records cannot be created from RCM
Task records.
RCM FMEA
Asset
RCM FMEA
Asset
RCM FMEA
Asset
Asset
Strategy

Asset records to Asset Strategy records
via Recommendation Management. This
link is established when an RCM FMEA
Has Strategy
Analysis is linked to a physical or
"virtual" piece of equipment or location
for which you have defined

Asset records to Asset Strategy Template
records via Recommendation
Asset
Management. This link is established
Strategy
Has Strategy
when an RCM FMEA Analysis is linked
Template
to a "virtual" piece of equipment or
location for which you have defined
Allows RCM FMEA Asset records to be
linked to RCM FMEA Task records. This
RCM FMEA Has Tasks
link is established only when a Task
Task
record is generated from a
recommendation where the related RCM
FMEA Asset record (i.e., the RCM FMEA
Asset record that is linked to the RCM
FMEA Analysis record) is not linked to an
Task records.
Facilitates the rejection of RCM FMEA
Task records that are linked to RCM
FMEA Asset records. When you reject an
RCM FMEA Task record, a Task History
record is created and linked to the RCM
FMEA Asset record through the Has Task
History relationship.
RCM FMEA
Asset
Task History
Has Task
History
RCM FMEA
Analysis
Has
Templates

Template
Templates.
RCM FMEA
Asset
Has
Templates

Template
Templates.
RCM FMEA
Failure Mode
Has
Templates

Template
Templates.
RCM FMEA
Failure Effect
Has
Templates

Template
Templates.
RCM FMEA
Has
Recommendation Templates

Template
Templates.
RCM FMEA
Mitigates
Recommendation Risk
Risk
Assessment
Allows you to determine how a

recommendation mitigates a risk.
Note also that the following families are related to the RCM FMEA Template family
through the Has Templates relationship to facilitate the creation of FMEA Templates:
RCM FMEA Analysis

RCM FMEA Asset

NOT Linked to Equipment or
Functional Location Records
In an FMEA Analysis, the root-level Analysis node (i.e., the RCM FMEA Analysis
record) can be linked to one or more RCM FMEA Asset records. Each RCM FMEA Asset
record can be linked to an Equipment or Functional Location record. Alternatively, RCM
FMEA Asset records can stand alone and not be linked to Equipment or Functional
Location records to represent "virtual" equipment and locations. A given FMEA Analysis
can contain both linked and unlinked RCM FMEA Asset records.
The following image provides a diagram of the relationships that will be created in an
FMEA Analysis when an RCM FMEA Asset record is not linked to an Equipment or
Note: While Human Resource records are not depicted in this diagram, they can be
linked to the RCM FMEA Analysis record through the Has RCM FMEA Team Member
relationship.
In this scenario, where the RCM FMEA Asset record is not linked to an
Equipment or Functional Location record, when an RCM FMEA
Recommendation record is:
Created for the analysis, the Recommendation record is linked to the RCM
FMEA Asset record.
Promoted to an Action record, the Action record will be linked to a
Proposed Strategy record and associated with the RCM FMEA Asset
record.
used by the Decision Logic Builder in FMEA.


Linked to Equipment or Functional
Location Records
The following image provides a diagram of the links that will be created for an FMEA
Analysis when an RCM FMEA Asset record is linked to an Equipment or Functional
Location record.
Note: All relationships depicted in the image are part of the Meridium APM baseline
database.
relationship.
The Equipment or Functional Location box represents the Equipment or
Functional Location family for which the Is RCM FMEA Asset, Has
Recommendations, and Has Tasks have been defined between that family and the
specified predecessor or successor.
In this scenario, where the RCM FMEA Asset record is linked to an Equipment or

the Recommendation record is linked to the Equipment or Functional
Location record to which the RCM FMEA Asset record is linked.
associated with the Equipment or Functional Location record. For details,
see the ASM Help.
used by the Decision Logic Builder in FMEA:

Illustration of the FMEA Data Model

Analysis
FMEA Analyses can be created automatically when an Asset Criticality Analysis System
record is promoted from Asset Criticality Analysis (ACA) to FMEA. The following
illustration shows how the families in the FMEA data model are related to the families in
family).
RCM FMEA Analysis State

Configuration
By default, the following baseline State Configuration exists for the RCM FMEA
Analysis family.
Initial State
The Draft state is the initial state of all new RCM FMEA Analysis records.
RCM FMEA Analysis record in RCM, FMEA, the Record Manager, or the Bulk Data
Form.

By default, NO states or operations displayed in the preceding diagram are reserved. This
means that you can remove or modify any of these states or operation. You can also add
your own states and operations to the State Configuration.
By default, the MI RCM User State Configuration Role is assigned to all states in the
RCM FMEA Analysis State Configuration. If desired, you can assign other State
About FMEA Recommendations

You can manage RCM FMEA Recommendation records in an FMEA Analysis using the
following methods:
On the FMEA Explorer page

Via the Recommendation Management feature
Both methods use standard State Configuration functionality to control the available
states and the operations that can be used to transition recommendations from one state to
the next.
Via the FMEA Explorer page, you will have access only to non-reserved states and
operations. The available operations will be displayed on the Operations submenu, which
appears in the upper, right corner of the datasheet just as in the Record Manager. The
following diagram shows the non-reserved baseline states that will be available on the
FMEA Explorer page.
Note: This image shows the non-reserved states that are included in the State
Configuration for the RCM FMEA Recommendation family in the baseline FMEA
product. If custom non-reserved states have been added to your system, they too will be
available from the Operations menu.
If you manage recommendations via Recommendation Management, however, you will
have access to both reserved and non-reserved states.
FMEA and the Record Manager
To ensure data integrity, records that make up analyses and templates in FMEA should be
created and managed using only the tools provided in the FMEA module. Therefore, the
Meridium APM system prevents you from creating or modifying certain records in the
Record Manager.
While you view records in these families via the Record Manager, the datasheet will be
disabled and a link will be displayed above the Datasheet list, which you can click to
view in FMEA the corresponding analysis or template that includes that record. When
you do so, that record will be selected in the explorer automatically. The text that appears
for this link will vary for each record and is displayed in the format <Record ID>
(<Family Caption>), where <Record ID> is the ID for the record and <Family Caption>
is the family caption of the family to which the record belongs. For example, the
following image shows the link that appears above the Datasheet list in the Record
Manager when you are viewing an RCM FMEA Failure Mode record.
The following list contains the families whose datasheet is disabled in the Record
Manager:
RCM FMEA Analysis

RCM FMEA Asset
RCM FMEA Template
Accessing the FMEA Start Page

The FMEA Start Page serves as the starting point for all tasks related to FMEA. The
following instructions provide details on accessing the FMEA Start Page.
To access the FMEA Start Page:
Strategy, and then click Failure Modes and Effects Analysis.
The FMEA Start Page appears.
Aspects of the FMEA Start Page

The FMEA Start Page displays the following links, which you can use to access various
features in FMEA:
View Analysis List: Opens the FMEA Analysis List page, from which you can
open an existing FMEA Analysis on the FMEA Explorer page.
Manage Templates: Displays the FMEA Templates page, where you can view a
list of FMEA Templates and use any of the templates to create a new FMEA
Analysis.
Run Reports: Displays the FMEA Reports page, which displays the reports that
have been associated with all FMEA Analyses.
View Recently Used Analyses: Displays the FMEA Recently Used Analyses page,
where you can open an FMEA Analysis that you accessed recently.
Create a New Analysis: Launches the FMEA Explorer page, where you can
create an FMEA Analysis.
Manage Tasks: Displays the FMEA Manage Tasks page, which displays a list of
FMEA Analyses that have one or more associated Task records.
Note: This link appears only if the Show Manage Tasks on the Start Page option is
enabled on the FMEA Administration page.
Perform Administrative Tasks: Displays the FMEA Administration page, where

you can configure administrative settings for FMEA.
Note: This link appears only if you are a Super User or a member of the MI RCM
Administrator Security Group.

Deploying and configuring FMEA for the first time includes completing multiple steps,
provide all the information that you need to deploy and configure FMEA on top of the
are marked as Required if you must perform the step to take advantage of FMEA
functionality.
Step Task
Review the FMEA data

model to determine
which relationship
definitions you will need Optional
to modify to include your
custom equipment and
location families.
This task is
necessary only if
you store equipment
and location
information in
families other than
the baseline
Equipment and
Functional Location
families.
Define sites to associate

Optional
with FMEA Analyses.
None
Assign Security Users to

one or more of the FMEA
Security Groups via the Required
application.
None

Security User via the
Optional
None
application.
Create a scheduled item

for executing RCM
Optional
event-based and datebased evaluations.
None
Define the Evaluation

query.
None
Optional
Define the
Recommendation Review Optional
query.
This task is
necessary only if
you do not want to
use the baseline
query that is defined
by default.
Define the Template

query.
This task is
necessary only if
you do not want to
use the baseline
query that is defined
by default.
Optional

Optional
query.
This task is
necessary only if
you do not want to
use the baseline
query.
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading FMEA from V3.5.1 to

V3.6.0.0.0
FMEA will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you upgrade the
required.
Upgrading FMEA from V3.5.0 SP1

LP to V3.6.0.0.0
FMEA will be upgraded from V3.5.0 SP1 LP to V3.6.0.0.0 automatically when you
upgrade the components in the basic Meridium APM system architecture. No additional
steps are required.

V3.6.0.0.0
FMEA will be upgraded from V3.5.0 to V3.6.0.0.0 automatically when you upgrade the
required.

V3.6.0.0.0
The following table lists the steps that are required to upgrade and configure FMEA for
Step Task
Assign Security
Users to the MI
RCM Viewer
Required
Security Group via
the Configuration
Manager application.
None
Add values to the

Recommended
Resource System
Required
Code Table via the
Configuration
Manager application.
This System Code Table

is used to populate the
field in RCM FMEA
Recommendation
records
FMEA Configuration Tasks

The following table lists the configuration tasks that an administrative user will need to
perform before other users can begin using the Failure Modes and Effects Analysis
module.
Task
Review the FMEA data
Required/Optional? Notes
Optional
This task is necessary only if you store
model to determine which

relationship definitions you
will need to modify to
include your custom
families.
Assign Security Users to one
or more of the FMEA
Security Groups.
equipment and location information in

families other than the baseline
Equipment and Functional Location
families.
Required
Define sites to associate with

Optional
FMEA Analyses.
Optional
Map additional fields to the
Users will need permissions to the

FMEA families in order to use the
FMEA module.
None
You need to complete this task only if
you store equipment and location
information in families other than the
Location families or if you use the
Location families but want to map
fields in addition to those that are
already mapped in the baseline
product.

Security User.
Required
None
Create a scheduled item for

executing FMEA eventbased and date-based
evaluations.
Required
None
Define the Evaluation query. Required
None
Optional
Define the Recommendation
Review query.
Optional
Define the Template query.
This task is necessary only if you do

not want to use the baseline query that
is defined by default.
This task is necessary only if you do
not want to use the baseline query that
is defined by default.
Required
The queries in this list must be defined
query.
before users can perform evaluations

and approvals for FMEA Analyses and
before they can view FMEA
Templates.
Associating FMEA Analyses with a

Specific Site
locations, where each site contains unique equipment and locations. If desired, you can
define the sites in your organization and associate equipment and locations with the site
to which they belong. When you create FMEA Analyses for those pieces of equipment
and locations, you will need to select the appropriate site on the Analysis datasheet of the
FMEA Analysis.
To help streamline the analysis-creation process, after you select a site on the Analysis
datasheet, the Meridium APM system will allow you to add Equipment and Functional
Location records to the FMEA Analysis only if the pieces of equipment and locations
belong to that site.
You can also associate Risk Matrices with specific sites. If a Risk Matrix is associated
with a site and an FMEA Analysis is associated with the same site, when you define the
unmitigated risk for a failure effect, rather than seeing the default Risk Matrix, you will
see the Risk Matrix that is associated with that site.
FMEA Security Groups

The FMEA module uses the following baseline Security Groups:
MI RCM Administrator: The MI RCM Administrator Security Group has no

family-level privileges configured for it in the baseline Meridium APM database.
Users who are members of this group will see the Administration link on the
RCM Start Page in the Meridium APM Framework application and will,
therefore, have access to administrative functions in FMEA. Users who do not
belong to this Security Group will not see this link and, therefore, will not be able
to access the administrative functions.
Because the MI RCM Administrator Security Group has no family-level privileges

assigned to it by default, to access features and functions in FMEA, members of the MI
RCM Administrator Security Group will also need to be assigned to the MI RCM User or
MI RCM Viewer Security Group.
MI RCM User: The MI RCM User Security Group has access to all features in
FMEA.
MI RCM Viewer: The MI RCM Viewer Security Group has view-only access to
FMEA. Users belonging to the MI RCM Viewer Security Group will not have
access to features that result in the creation, update, or deletion of records or links
between records.
The following table shows the family-level privileges assigned to the MI RCM User and
RCM Viewer Security Groups.
MI RCM User
MI RCM
Viewer
Action
View
View
Asset Criticality Analysis System
View
None
Consequence Definition
View
View
View
View
View
View
View
View
Human Resource
View, Update,
Insert, Delete
View
Family Caption
Entity families
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
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
RCM FMEA Template
View, Update,
Insert, Delete
View
RCM FMEA Task
View, Update,
Insert, Delete
View
Reference Documents
View, Update,
Insert, Delete
View
Risk Assessment
View, Update,
Insert, Delete
View
Risk Category
View
View
Risk Matrix
View
View
Risk Rank
View, Update,
Insert, Delete
View
Risk Threshold
View
View
Site Reference
Task History
View
View
View, Update,
Insert, Delete
View
View
View
Has Consolidated Recommendations
View
View
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
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
Note: The Task History relationship family is inactive in

the baseline Meridium APM database.
Relationship families
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

Has Task History
View
View
View, Update,
Note: The Has Task History relationship family is inactive
Insert, Delete
in the baseline Meridium APM database.
View
Has Tasks
View, Update,
Insert, Delete
View
Has Templates
View, Update,
Insert, Delete
View
Is Based on RCM FMEA Failure Effect
View
View
Is RCM FMEA Asset
View, Update,
Insert, Delete
View
With these privileges, any user who is a member of the MI RCM User Security Group
will have access to ALL records involved in FMEA Analyses. In addition to these
baseline privileges, which you can grant by assigning users to the MI RCM User Security
Group, you will need to grant FMEA users permission to the Equipment or Functional
Location family if it is related to the RCM FMEA Asset family through the Is RCM
FMEA Asset relationship.
Note: You may also want to grant some users permission to modify the items in the
following Catalog folders: \\Public\Meridium\Modules\RCM.
About Virtual and Physical Equipment

and Locations
When you define RCM FMEA Asset records for your FMEA Analyses, you have the
following options:
You can create standalone RCM FMEA Asset records that represent "virtual"
equipment and locations (i.e., equipment and locations that do not physically exist
and are not represented by Equipment and Functional Location records).
You can create RCM FMEA Asset records that are linked to Equipment or
Functional Location records in your database. This option allows you to make
your RCM FMEA Asset records representative of the actual equipment and
locations in your system. This allows certain values from the related Equipment or
Functional Location record to be passed to other records in the analysis, such as
the Failure Effect and Recommendation.
The baseline FMEA implementation includes default rules that will map the certain
values from the Equipment or Functional Location record to the fields of the related
RCM FMEA Asset record. In this way, the RCM FMEA Asset record will store
identifying information about its related Equipment or Functional Location record. In
addition, the values stored in the Asset ID field will be available for selection when you
create Failure Mode and Recommendation records. If desired, you can modify the rules
that are delivered with the baseline FMEA implementation to map additional fields from
the Equipment or Functional Location record to the RCM FMEA Asset record.
In addition, the Meridium APM baseline database is configured with the Has
Recommendations and Has Strategy relationships, so the Meridium APM system will link
Equipment or Functional Location records to RCM FMEA Recommendation records and
to Asset Strategy records.
Has Recommendations Relationship

The Has Recommendations relationship allows Equipment or Functional Location
records that have been linked to RCM FMEA Asset records to be linked to RCM FMEA
Recommendation records. In the Meridium APM baseline database, the following

families are related to the RCM FMEA Recommendation family through the Has
Recommendations family to facilitate this workflow:
Equipment
Functional Location
RCM FMEA Asset
Therefore, any RCM FMEA Asset record that is linked to an Equipment or Functional
Location record is also linked to the RCM FMEA Recommendation record. If you are
following the Meridium APM Best Practice, you will not have to define the Has
Recommendations relationship for the equipment and locations that you have defined for
RCM or FMEA. However, if you want to define RCM FMEA Assets from any family
other than the baseline Equipment or Functional Location families, you will have to
create a relationship definition to link those records to RCM FMEA Recommendation
records through the Has Recommendations relationship family.
Note: If you define the Has Recommendations relationship for any families other than
the baseline Equipment and Functional Location families, be sure to use the Has
Recommendations family and not the Has RCM FMEA Recommendations family, which
is reserved for linking RCM FMEA Failure Effect records to RCM FMEA
Recommendation records within FMEA Analyses.
When you create an RCM FMEA Failure Mode record for an RCM Analysis, the value in
the Related Asset ID field will indicate the ID of the related RCM FMEA Asset record.
For RCM Analyses, the Related Asset ID must be selected manually. If the RCM FMEA
Asset record is linked to an Equipment or Functional Location record, the Asset ID
comes from the Equipment or Functional Location record.
When you create RCM FMEA Failure Effect records for that Failure Mode and then
create RCM FMEA Recommendation records for those Failure Effects, the Meridium
APM system will pass to the Recommendations the Related Asset ID from the associated
RCM FMEA Failure Mode record.
If the RCM FMEA Asset record is not linked to an Equipment or Functional

Location record, the RCM FMEA Recommendation record will be linked to the
If the RCM FMEA Asset record IS linked to an Equipment or Functional Location
record, the RCM FMEA Recommendation record will be linked to the Equipment
Creating the Evaluation Security User

When you set up an evaluation for an FMEA Recommendation, the Meridium APM
system will create a scheduled item for that evaluation and store it in the Meridium APM
Schedule Manager. The scheduled item will be executed according to the schedule that is
set up for the evaluation. As with other actions that you perform in the Meridium APM
system, the execution of the scheduled item requires user authentication. Therefore, to
execute scheduled evaluations, you must set up a Security User for that purpose.
When the scheduled item for an evaluation is executed, three things happen:
If it is an event-based evaluation, the Meridium APM system runs the Evaluation

Query. Therefore, the Evaluation User must have whatever privileges are
necessary to execute the Evaluation Query that you create. The specific privileges
that are required will vary, depending on which families are queried by the
Evaluation Query.
The Meridium APM system updates the associated Recommendation record with
the execution date. Therefore, the Evaluation User must have View and Update
privileges on the RCM FMEA Recommendation family.
The Meridium APM system sends the evaluation email message to the appropriate
email address. This action requires no special privileges.
Therefore, to set up evaluations, you must set up a Meridium APM Security User that has
the privileges described above.
Creating a Scheduled Item for

Evaluations
In FMEA, you can define criteria for evaluating the whole analysis or parts of the
analysis in the future. The evaluation feature allows you to be notified, or to notify
someone else, when certain conditions are met.
To enable this functionality, you will need to create a scheduled item in the Meridium
APM Schedule Manager to evaluate any date-based criteria and run the Evaluation query
that is used by any event-based criteria to determine whether or not the criteria have been
met. When the scheduled item is executed:
For any date-based evaluations that have been configured, an email message will
be sent for each item whose dates indicates that it is due for evaluation.
For any event-based evaluations that have been configured, an email message will
be sent only if the count and cost returned by the Evaluation query are greater
than the count and cost defined in the event-based evaluation criteria.
To create a scheduled item for Evaluations:

1. Launch the Meridium APM Schedule Manager application and log in.
2. At the bottom of the Meridium APM Scheduler - Scheduled Items window, click
the Add New link.
The Choose a Meridium Assembly dialog box appears.
3. Open the Meridium.RCM.dll file.
The Choose an Object Type dialog box appears.
4. Select the object type Meridium.RCM.Client.RCMEvaluation, and click OK.

The Schedule RCM Evaluation window appears, and the Task tab is displayed by default.
5. On the Task tab, define a schedule that will execute the scheduled item on a
recurring basis. The frequency by which you want to execute the scheduled item
is up to you.
6. Click the User tab.
The User tab appears.
7.
In the User ID and Password text boxes, enter the Meridium APM username and
password for a user who has at least:
The privileges that are necessary to execute the Evaluation Query. The
specific privileges that are required will vary, depending on which families
are included in the Evaluation Query.
View and Update privileges to the RCM FMEA Recommendation family.
View and Update privileges to the RCM FMEA Asset family.
View and Update privileges to the RCM FMEA Analysis family.
8. Click OK.
The scheduled item is created and a new row appears in the Scheduled Items grid.
About Queries Used by FMEA

FMEA relies on queries to perform certain functions. For example, when you access the
FMEA Analysis List page, the Meridium APM system runs the Analysis List query and
returns a list of analyses that meet the query criteria. From the list of analyses, you can
open an analysis in the FMEA Explorer.
Except in the case of the Evaluation query, which you must create manually, when a
query is required to enable certain functionality, the baseline FMEA product contains a
default query for you to use. The default query will be used automatically unless you
choose to use a different query.
You can use the default query exactly as it is shipped, or you can modify it to meet your
specific needs. As long as you do not rename the query or move it to a different location
in the Catalog, it will be used automatically in FMEA. If you do change the name of the
query or move it to a different location, you will need to modify the appropriate
Administrative setting to point to your custom query.
The following table provides a list and description of the queries that are provided for use
within FMEA. Each of these queries is stored in the folder
\\Public\Meridium\Modules\FMEA in the Catalog. In addition to the queries listed in the
table, FMEA also uses the Evaluation query, which must be created manually and then
selected on the FMEA Administration page.
Query
Description
Name of Default
Query in the Catalog
Recommendation
Review query
Used for reviewing recommendations and Review

promoting them to actions.
Recommendations
Template query
Used for generating the list of available

templates when you load templates for
creating new analyses or analysis nodes.
Used for generating the list of analyses

Analysis List query that appears on the FMEA Analysis List
page.
Template List
Enterprise Analysis
List
Note that a copy of each baseline query is also stored in the folder
\\Baseline\Meridium\Modules\FMEA. The items in the Baseline folder cannot be
modified, so this folder serves as a permanent record of the content that is delivered with
the baseline Meridium APM product. While a copy of each query is stored in the Baseline
folder, the Meridium APM system reads the query from the folder
\\Public\Meridium\Modules\FMEA, so you can customize the baseline functionality by
modifying the query in the folder \\Public\Meridium\Modules\FMEA.
The Baseline folder will be updated with any changes made to the baseline content in
future releases. If you modify an item in the folder \\Public\Meridium\Modules\FMEA
and later decide that you want to revert to the baseline functionality, you can recover the
baseline query from the folder \\Baseline\Meridium\Modules\FMEA.
Accessing the FMEA Administration

Page
Note: To access administrative features in FMEA, you must be a Super User or a member
To access the FMEA Administration page:
On the FMEA Start Page, click the Perform Administrative Tasks link.
The FMEA Administration page appears.
The FMEA Administration page displays all the administrative settings that must be
defined for FMEA to work properly. A read-only value in the field associated with a
setting indicates that the setting is already defined. For new installations the Template
Query and Analysis List Query are defined automatically. The other settings must be
defined manually. In addition, you can modify the value for any setting that is already
defined, including the ones that are defined automatically in the baseline FMEA product.
Use the following links to access help for defining each setting:
Evaluation query
Recommendation Review query
Template query
Analysis List query
Note: The FMEA Administration page also contains the Show Manage Tasks on the Start
Page check box. You should not select this check box. If you do, the Manage Tasks link
will appear on the FMEA Start Page. This link provides access to a feature that does not
work properly.
About the Evaluation Query

For each FMEA Analysis, you can configure date-based and event-based evaluations. A
date-based evaluation relies entirely upon the date and time to determine when an
evaluation email message should be sent. An event-based evaluation, on the other hand,
relies upon failure data to determine when an evaluation email message should be sent.
When you set up an event-based evaluation, you will use the Event-Based Evaluation
dialog box to define criteria for sending the evaluation email message.
Note that you can set up the evaluation to be based on failure count, failure cost, and date.
This means that to configure effective event-based evaluations, you must define an
Evaluation query that determines the following for a given piece of equipment or
location:
The number of failures that have occurred for the piece of equipment or location
since a given date.
The total cost of the failures that have occurred for the piece of equipment or
location since a given date.
Each day after the specified start date, the Meridium APM system will run the Evaluation
query for the associated Equipment or Functional Location record. When the record
meets the failure count and/or cost criteria, the Meridium APM system will send an
evaluation email message to the email address specified in the Notify field.
Creating the Evaluation Query

The specific families included in your Evaluation query will vary, depending on your data
model. Regardless of your data structure, however, your query must follow the guidelines
provided here.
It must contain two columns of output:
Count, which returns a numeric value representing the total number of failures for
a given piece of equipment or location. The alias for this column must be exactly
Count.
Cost, which returns a numeric value representing the total cost of failures for a
given piece of equipment or location and failure mode. The alias for this column
must be exactly Cost.
The query must contain three prompts in the following order:
ID: Accepts the Record ID (i.e., the value in the ENTY_ID field) of the record
representing the piece of equipment or location. Note that the record can be either
an RCM FMEA Asset record itself or a related Equipment or Functional Location
record, depending on whether or not the RCM FMEA Asset record has been
linked to an Equipment or Functional Location record.
Note: In the baseline FMEA implementation, the value in the ENTY_ID field from the
RCM FMEA Asset or an Equipment or Functional Location record is passed to the RCM
FMEA Failure Mode record and to subsequent RCM FMEA Recommendation records. If
you are setting up an event-based evaluation at the recommendation level and you have
modified your business rules to pass a different value to the RCM FMEA Failure Mode
record and the Recommendation record, then you will need to set up the Evaluation query
appropriately.
Failure Mode: Accepts the value in the Failure Mode Name field in the Failure
Mode record that is linked to either the Recommendation record (if you are
setting an evaluation at the recommendation level) or the RCM FMEA Asset
record (if you are setting up an evaluation at the equipment/location level). When
the Meridium APM system runs the Evaluation query, it will extract the value
from the Failure Mode Name field in the Failure Mode record and pass it in as the
value for this prompt.
Note: The Failure Mode parameter expression should include the operator like instead of
is equal to (=).
Date: Accepts the date defined in the evaluation item. When you create an eventbased evaluation, you specify a date after which you want to start counting
failures and failure cost. For example, you might specify to be notified when a
given piece of equipment has five failures, beginning 1/1/2005. In this case, the
date 1/1/2005 will be passed to the Evaluation query. If the specified piece of
equipment has had five failures since that date, then the evaluation email message
will be sent.
Note: The Asset ID, Failure Mode, and Date fields should not be included in the output.
The specific tables that you query will vary, depending on your data model. For example,
you might query the Equipment family to retrieve the Asset ID and the Work Order
family to retrieve the failure data, where the Equipment and Work Order families are
related through the Asset Has Maintenance relationship.
Whatever families you query, be sure that the table from which you retrieve the failure
mode should contain the same values that will be stored in the Failure Mode Name field
in RCM FMEA Failure Mode records. In the baseline FMEA implementation, the Failure
Mode Name field in RCM FMEA Failure Mode records is simply a character field that
will accept any character string. Because values will be passed from this field to the
Evaluation query, however, it is important that the values stored in the Failure Mode
Name field match the failure modes that are stored in the records that are queried by the
Evaluation query. How you choose to do this is up to you.
For example, you might modify the Failure Mode Name field in the RCM FMEA Failure
Mode family to provide a restricted list of values or to use System Codes. Then, you
might apply the same rules to the Failure Mode field of the family that is used by the
Evaluation query. Just keep in mind that whatever is stored in the RCM FMEA Failure
Mode Name field will be passed to the Failure Mode prompt in the Evaluation query. If
the values passed to the Evaluation query are different from the values stored in failure
data table used by the query, the query will not return the data need to trigger an eventbased evaluation.
Example of an Evaluation Query

Note: The following example is meant to serve as a guideline for creating an Evaluation
query. The specific families that you query and fields that you include will vary,
depending on your data model.
Suppose that you want to create event-based evaluations for equipment that belongs to an
FMEA Analysis. The following image shows the design grid for an example of an
Evaluation query.
When you run the query manually, the Enter parameter values dialog box will look like
This means that when the Meridium APM system runs the query automatically according
to the schedule set up in the Schedule Manager, the following values will be passed in for
the prompts:
The Record ID of the Equipment record.

The value in the Failure Mode Name field in the Failure Mode record that is
linked to the RCM FMEA Asset record to which the Equipment record is linked.
The date specified as the Starting from date in the evaluation criteria.
After the appropriate values have been passed in for the prompts, the query would return
results similar to those shown in the following image.
In this particular case, the results show the failure count and failure cost:
For failures of the specified type, as determined by the specified failure mode.
That occurred for the piece of equipment or location identified by the specified
Record ID.
Since the date specified by the Starting from date in the evaluation criteria.
These results will be examined by the Meridium APM system and compared to the failure
count and cost thresholds defined for the evaluation. If the necessary criteria have been
met (i.e., if the failure count and/or cost returned by the query exceed the values defined
for the evaluation), the Meridium APM system will send an evaluation email message to
the appropriate person. If the criteria have not been met, the email message will not be
sent.
Selecting the Evaluation Query

After you have created the Evaluation query and saved it in the Catalog, you must define
that query in the FMEA Administrative settings.
To define the Evaluation query:
1. Access the FMEA Administration page.
2. To the right of the Evaluation Query text box, click the Browse button.
The Evaluation Query dialog box appears.
that you want to use as the Evaluation query.
4. In the pane on the right, select the query that you want to use as the Evaluation
query.
5. Click OK.
The Evaluation Query text box is populated with the path to the query that you selected.
Defining the Recommendation Review

Query
The Recommendation Review query is used for building the list of recommendations that
appears in the pane on the left of the FMEA Review Recommendations page. The
Recommendation Review query should retrieve a list of FMEA FMEA Recommendation
records that are linked to a given FMEA Analysis.
The baseline FMEA product contains a default Recommendation Review query called
Review Recommendations, which is stored in the folder
\\Public\Meridium\Modules\FMEA. This query will be used automatically by FMEA. If
you prefer to create your own query and use it instead, you will need to select that query
via the FMEA administrative settings.
administrative settings. As long as you do not change the query name or location, the
Meridium APM system will use the default query automatically even if you change the
content.
The following instructions provide details on selecting the FMEA Review
Recommendations query. Note that you need to perform this procedure only if you
choose to use a query other than the one that is delivered.
To define the Recommendation Review query:
2. To the right of the Recommendation Review query text box, click the Browse
button.
The Recommendation Review Query dialog box appears.
that you want to use as the Recommendation Review query.
4. In the pane on the right, select the query that you want to use as the
Recommendation Review query.
5. Click OK.
The Recommendation Review query text box is populated with the path to the query that
you selected.
Defining the Template Query

The Template query is used by FMEA to load FMEA Analysis Templates. The baseline
FMEA product contains a default Template query called Template List, which is stored in
the folder \\Public\Meridium\Modules\FMEA. This query is run automatically when you
access the FMEA Templates page.
The Template List query uses a parameter that displays results based on Template Type.
The Template Type that the query uses will depend on how you access the FMEA
Templates page. For instance, when you access the FMEA Templates page from the
FMEA Start Page, the default parameter is Analysis. However, if you access the FMEA
Templates page via the FMEA Template Explorer page, the root node in the tree
determines which Template Type the query uses as the parameter. For example, if you are
working with an FMEA Template with the Template Type Function, when you access the
FMEA Templates page, the query will search and results for all FMEA templates created
at the Function level.
If you prefer to create your own query and use it instead, you will need to select that
query via the FMEA administrative settings.
administrative settings. As long as you do not change the query name or location, FMEA
The following instructions provide details on selecting the Template query. Note that you
need to perform this procedure only if you choose to use a query other than the one that is
delivered.
To define the Template query:
2. To the right of the Template Query text box, click the Browse button.
The Template Query dialog box appears.
that you want to use as the Template query.
4. In the pane on the right, select the query that you want to use as the Template
query.
5. Click OK.
The Template Query text box is populated with the path to the query that you selected.
Defining the Analysis List Query

The Analysis List query is used by the system to generate a list of analyses that appears
on the FMEA Analysis List page. The baseline FMEA product contains a default Analysis
List query called Enterprise Analysis List, which is stored in the folder
\\Public\Meridium\Modules\FMEA. This query will be used automatically by FMEA. If
you prefer to create your own query and use it instead, you will need to select that query
via the FMEA administrative settings.
administrative settings. As long as you do not change the query name or location, FMEA
The following instructions provide details on selecting the FMEA Analysis List query.
Note that you need to perform this procedure only if you choose to use a query other than
the one that is delivered.
To define the Analysis List query:
2. To the right of the Analysis List Query text box, click the Browse button.
The Analysis List Query dialog box appears.
that you want to use as the Analysis List query.
4. In the pane on the right, select the query that you want to use as the Analysis List
query.
5. Click OK.
The Analysis List Query text box is populated with the path to the query that you
selected.
Clearing the Current Query Selection

After you have selected the Evaluation, Recommendation Review, Template, or Analysis
List query, the query path appears in the text box on the FMEA Administration page. The
text is read-only, so to modify the query selection, you must use the procedure that you
used to select the original query. If, on the other hand, you want to delete the current
query selection so that NO query is selected, use the following instructions.
To delete the current FMEA query selection:
2. To the right of the text box for the query that you want to clear, click the Browse
button.
The appropriate query selection dialog box appears, depending on which Browse button
you clicked.
3. In the Catalog hierarchy on the left, select any folder.
The pane on the right will display any queries that are stored in that folder. Do not select
a query.
4. Click OK.
The query path that was previously displayed in the text box is deleted.
Using the FMEA Site Map

The Site Map in FMEA allows you navigate from the current page to the FMEA Start
Page by clicking the FMEA link in the Site Map. The Site Map appears at the top of the
workspace on every page within FMEA. The page that you are currently viewing appears
as a hyperlink in the Site Map after the delimiter >.
The following image shows an example of the Site Map in RCM as it appears on the
FMEA Recently Used Analyses page. A red outline has been added to the image to
highlight the Site Map.
Navigating FMEA as a Member of the

MI RCM Viewer Security Group
Unlink members of the RCM User Security Group, who have access to ALL features in
the FMEA module, members of the MI RCM Viewer Security Group will have view-only
access to FMEA. In other words, members of the MI RCM Viewer Security Group
cannot create, modify, or delete records or links between records. These users can,
however, view the contents of analyses.
When you are logged in as a member of this Security Group, options that would result in
the creation, update, or deletion of records or links between records will be disabled,
including datasheets. In other words, if you do not have privileges to perform the action,
the associated option will be disabled.
For example, when you are viewing an analysis on the FMEA Explorer page, the RCM
FMEA Analysis datasheet will be disabled. In addition, links like the Link to Asset link
on the Common Tasks menu will be disabled. While links like the Manage Team link on
the Analysis Tasks menu will remain enabled and provide access to the FMEA Team
Members page.
Throughout this documentation, we assume that you are familiar with the privileges
associated with the Security Group to which you belong. The documentation does not
specify how options in the FMEA module behave based upon your security privileges.
Workflow for Creating an FMEA

Analysis
In Meridium APM, conducting an FMEA Analysis consists of:

1. Creating the root-level analysis record, which stores identifying information about
the analysis itself.
2. Creating the analysis team.
3. Linking RCM FMEA Assets to the analysis record to define what is being
analyzed.
4. For each piece of equipment or location, identifying the potential failure modes.
5. For each failure mode, identifying the possible failure effects.
6. For each failure effect, defining one or more recommendations.
Starting a New FMEA Analysis

The following instructions provide details on creating a new analysis from scratch. Note
that you can also create a new RCM analysis using the following methods:
Load an FMEA Template.

Promote an Asset Criticality Analysis System record from Asset Criticality
Analysis (ACA) to FMEA.
The following instructions provide details on creating a new FMEA Analysis from the
FMEA Start Page. You can also create a new FMEA Analysis using the Create Analysis
link that appears on the Analysis Tasks menus throughout FMEA.
To create a new analysis from scratch:
1. On the FMEA Start Page, click the Create a New Analysis link.
The FMEA Explorer page appears, displaying a new analysis.
2. In the Analysis datasheet, enter the desired analysis information. Note that the
default Analysis datasheet contains two tabs:
o Analysis Identification: Stores identifying information, such as the
analysis ID and description. Note that the Analysis ID and Analysis Type
cells are populated automatically and cannot be modified. The Analysis
Short Description cell is also populated with a default value but can be
modified if needed.
o
System Information: Stores information about the system that is being

analyzed. The System Definition tab also contains the Site Reference field,
where you can select the site to which this analysis belongs. The list
contains the Record ID of all Site Reference records that exist in the
database.
Note: After an FMEA Analysis contains an Equipment or Functional Location record that
is linked to a Site Reference record, the Site Reference field is disabled.
Click the Save button
, which appears above the datasheet.
The new RCM FMEA Analysis record is saved to the database in the Draft state.
After you have saved the analysis, the task menu options become enabled so that
you can perform additional tasks associated with the analysis.
Options for Opening an FMEA

Analysis
You have several options for opening existing FMEA Analyses. Your choice of
where and how to open an analysis will depend primarily on your personal
preference. You can open an analysis from:
The FMEA Analysis List page.
The FMEA Recently Used Analyses page.
Accessing the FMEA Analysis

List Page
From the FMEA Analysis List page, you can run the query that has been
set up for the purpose of retrieving a list of existing FMEA Analyses and
then, from the list of analyses, open an analysis.
To access the FMEA Analysis List page:
On the FMEA Start Page, click the View Analysis List link.
The FMEA Analysis List page appears.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights

reserved.
Aspects of the FMEA

Analysis List Page
The main display area of the FMEA Analysis List page contains a
grid that displays a list of analyses retrieved by the Analysis List
query. If the Analysis List query contains one or more prompts,
those prompts will appear in fields above the grid, along with a
Run Query button. You can select a value for each prompt and then
click the Run Query button to retrieve results based on your
selections. For more information on this feature, click here.
Note: The default Enterprise Analysis List query does not contain
any prompts. Prompts will appear above the grid only if a custom
query has been configured by an administrative user.
The specific columns that appear in the grid will vary, depending
on how the query has been configured. If the query has been
properly configured, the grid will display the Analysis Short
Description column, which will contain a hyperlinked description
of the analysis. You can click any link to open the associated
analysis.
The FMEA Analysis List page contains the following task menus:
Analysis Tasks and Common Tasks.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights

reserved.
Analysis Tasks Menu

The Analysis Tasks menu on the FMEA Analysis List page
Create Analysis: Opens the FMEA Explorer page,
displaying a new FMEA Analysis.
Open in Explorer: Opens the selected FMEA Analysis
on the FMEA Explorer page. This link is disabled if more
than one FMEA Analysis record is selected in the grid.
Delete Analysis: After asking for confirmation, deletes
the analysis that is currently selected. Note that deleting an
analysis from the FMEA Analysis List page will delete the
RCM FMEA Analysis record and all the records to which it
is linked (i.e., all the analysis elements).
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All

rights reserved.
Common Tasks Menu

The Common Tasks menu on the FMEA Analysis List page
Print: Displays the Preview window, from
which you can select various print options and print
the list of analyses.
Send To: Displays a submenu with options that

let you provide a link to the current page on your
desktop (create shortcut), in an email message, or
on a Home Page.
Help: Displays the context-sensitive Help topic
for the FMEA Analysis List page.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc.

All rights reserved.
Opening an Analysis
from the FMEA
Analysis List
To open an analysis from the Analysis List:
In the Analysis Short Description
column, click the link for the analysis that
you want to open.
-orSelect the row containing the analysis that
you want to open, and on the Analysis Tasks
-orRight-click any analysis in the list, and then
click Open in explorer.
The selected analysis appears on the FMEA
Explorer page.
V3.6.0.0.0 - Copyright 1993-2014

Meridium, Inc. All rights reserved.
Accessing the
FMEA Recently
Used Analyses Page
To access the FMEA Recently Used
Analyses page:
On the FMEA Start Page, click
the View Recently Used Analyses
link.
The FMEA Recently Used Analyses
page appears, displaying a list of
FMEA Analyses that you have
viewed most recently.
V3.6.0.0.0 - Copyright 1993-2014

Meridium, Inc. All rights reserved.
Aspects of the
FMEA Recently
Used Analyses
Page
The FMEA Recently Used Analyses
page displays a list of the last four
analyses that you accessed. By
default, the grid contains the
following columns:
Id: The value stored in
the Analysis ID field in the
corresponding record. This
value appears as a hyperlink,
which you can click to open

the analysis.
Description: The value
stored in the Analysis Short
Description field in the
corresponding record.
Last Updated Date: The
date on which the
corresponding record was last
updated.
Last Updated By: The
user name of the user who
was logged in when the
record was last updated.
You can customize the
default grid display, if
desired. If you have not yet
viewed any analyses, a There
are no recently viewed links
available link will appear in
place of the grid. You can
click the link to return to the
FMEA Start Page.
The FMEA Recently Used
Analyses page contains two
task menus: Analysis Tasks
and Common Tasks.
V3.6.0.0.0 - Copyright
1993-2014 Meridium, Inc.
Analysis
Tasks Menu
The Analysis Tasks menu on

the FMEA Recently Used
Analyses page contains the
following links:
Create Analysis:
Opens the FMEA
Explorer page,
displaying a new
FMEA Analysis.
Open in Explorer:
Opens the selected
FMEA Analysis on
the FMEA Explorer
page. This link is
disabled if more than
one FMEA Analysis
record is selected in
the grid.
Delete Analysis:
After asking for
confirmation, deletes
the analysis that is
currently selected.
Note that deleting an
analysis from the
FMEA Recently Used
Analyses page will
delete the RCM
FMEA Analysis
record and all the
records to which it is
linked (i.e., all the
analysis elements).
View Analysis
List: Displays the
FMEA Analysis List
page, which displays
a list of all the FMEA
Analyses that exist.
V3.6.0.0.0 Copyright 19932014 Meridium, Inc.

Commo
n Tasks
Menu
The Common Tasks
menu on the FMEA
Recently Used
Analyses page
contains the following
links:
Print:
Displays the
Preview
window, from
which you can
select various
print options
and print the
list of
analyses.
Send To:
Displays a
submenu with
options that let
you provide a
link to the
current page
on your
desktop
(create
shortcut), in
an email
message, or on
a Home Page.
Help:
Displays the
contextsensitive Help
topic for the
FMEA
Recently Used
Analyses
page.
V3.6.0.0.0 Copyright
1993-2014
Meridium,
Inc. All rights
reserved.
Open
ing a
Recent
ly
Used
FMEA
Analys
is
To open an
analysis on the
FMEA
Explorer page:
In
the Id
column
, click
the
hyperli
nked
ID of
the
analysi
s that
you
want to
open.
-orSelect
the
row
contain
ing the
analysi
s that
you
want to
open,
and on
the
Analys
is
Tasks
menu,
click
the
Open
in
Explor
er link.
-orRightclick
any
analysi
s in the
list,
and
then
click
Load
selecte
d
analys
is into
eplore
r.
The
selecte
d
analysi
s
appear
s on
the
FMEA
Explor
er
page.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
D
elet
ing
F
M
EA
An
aly
ses
The
followi
ng
instruct
ions
provid
e
details
on
deletin
g an
RCM
Analys
is
record
via the
FMEA
Analys
is List
page.
You
can
also
delete
an
RCM
Analys
is
record,
howev
er,
using
the
shortcu
t menu
in the
FMEA
Explor
er
pane.
When
you
delete
an
FMEA
Analys
is
record,
you are
also
deletin
g all
the
records
that are
linked
to that
record
that
make
up the
FMEA
Analys
is.
To
delete
an
FMEA
Analys
is
record:
Access
the
FMEA
Analys
is List
page.

Select
the
row(s)
contain
ing the
RCM
Analys
is
record(
s) that
you
want to
delete.
On
the
Analys
is
Tasks
menu,
click
the
Delete
Analys
is link.
A
confir
mation
messag
e
appear
s,
asking
if you
really
want to
delete
the
selecte
d
analysi
s or
analyse
s (if
you
selecte
d
multipl
e
rows).
C
l
i
c
k
O
K
.
T
h
e
s
e
l
e
c
t
e
d
r
e
c
o
r
d
(
s
)
i
s
d
e
l
e
t
e
d
.
V
3
.
6
.
0
.
0
.
0
C
o
p
y
r
i
g
h
t
1
9
9
3
2
0
1
4
M
e
r
i
d
i
u
m
,
I
n
c
.
A
l
l
r
i
g
h
t
s
r
e
s
e
r
v
e
d
.
A
b
o
u
t
t
h
e
F
M
E
A
E
x
p
l
o
r
e
r
P
a
g
e
A
n
F
M
E
A
A
n
a
l
y
s
i
s
c
a
n
i
n
c
l
u
d
e
R
C
M
F
M
E
A
A
s
s
e
t
,
F
a
i
l
u
r
e
M
o
d
e
,
F
a
i
l
u
r
e
E
f
f
e
c
t
,
a
n
d
R
e
c
o
m
m
e
n
d
a
t
i
o
n
r
e
c
o
r
d
s
.
I
n
M
e
r
i
d
i
u
m
A
P
M
,
e
a
c
h
F
M
E
A
A
n
a
l
y
s
i
s
i
s
d
e
f
i
n
e
d
a
t
t
h
e
r
o
o
t
l
e
v
e
l
i
n
a
r
e
c
o
r
d
t
h
a
t
b
e
l
o
n
g
s
t
o
t
h
e
R
C
M
F
M
E
A
A
n
a
l
y
s
i
s
f
a
m
i
l
y
.
O
t
h
e
r
c
o
m
p
o
n
e
n
t
s
o
f
t
h
e
a
n
a
l
y
s
i
s
,
s
u
c
h
a
s
f
a
i
l
u
r
e
m
o
d
e
s
a
n
d
f
a
i
l
u
r
e
e
f
f
e
c
t
s
,
a
r
e
d
e
f
i
n
e
d
i
n
r
e
c
o
r
d
s
t
h
a
t
a
r
e
l
i
n
k
e
d
e
i
t
h
e
r
d
i
r
e
c
t
l
y
o
r
i
n
d
i
r
e
c
t
l
y
t
o
t
h
e
r
o
o
t
R
C
M
F
M
E
A
A
n
a
l
y
s
i
s
r
e
c
o
r
d
,
a
c
c
o
r
d
i
n
g
t
o
t
h
e
f
a
m
i
l
i
e
s
a
n
d
r
e
l
a
t
i
o
n
s
h
i
p
s
d
e
f
i
n
i
t
i
o
n
s
o
u
t
l
i
n
e
d
i
n
t
h
e
F
M
E
A
d
a
t
a
m
o
d
e
l
.
B
e
c
a
u
s
e
e
a
c
h
F
M
E
A
A
n
a
l
y
s
i
s
i
s
r
e
p
r
e
s
e
n
t
e
d
b
y
m
u
l
t
i
p
l
e
,
l
i
n
k
e
d
r
e
c
o
r
d
s
,
m
a
n
a
g
i
n
g
F
M
E
A
A
n
a
l
y
s
e
s
i
n
v
o
l
v
e
s
m
a
n
a
g
i
n
g
t
h
e
s
e
v
a
r
i
o
u
s
r
e
c
o
r
d
s
,
b
o
t
h
a
s
a
g
r
o
u
p
a
n
d
i
n
d
i
v
i
d
u
a
l
l
y
.
M
e
r
i
d
i
u
m
A
P
M
p
r
o
v
i
d
e
s
t
h
e
F
M
E
A
E
x
p
l
o
r
e
r
p
a
g
e
t
o
f
a
c
i
l
i
t
a
t
e
w
o
r
k
i
n
g
w
i
t
h
t
h
e
s
e
l
i
n
k
e
d
r
e
c
o
r
d
s
.
T
h
e
l
a
y
o
u
t
o
f
t
h
e
F
M
E
A
E
x
p
l
o
r
e
r
p
a
g
e
i
s
s
i
m
i
l
a
r
t
o
t
h
a
t
o
f
t
h
e
R
e
c
o
r
d
M
a
n
a
g
e
r
,
w
h
e
r
e
i
t
i
s
d
i
v
i
d
e
d
i
n
t
o
t
h
r
e
e
m
a
i
n
a
r
e
a
s
:
The
followi
ng task
menus:

Analysis Tasks
Common
Tasks
Template
Tasks
Reports
Associated
Pages
The FMEA
Explorer pane,
which displays
the hierarchy
of records
involved in the
FMEA
Analysis.
The
datasheet area,
which displays
the
information
stored in the
record for the
selected node.
Note that
throughout our
discussion of
the FMEA
Explorer page,
we assume that
you are
familiar with
the basic
concepts and
navigational
features of the
Record
Manager. We
limit our
discussion
primarily to
features that
are specific to
the FMEA
Explorer page
and that
deviate from
the standard
functionality
of the Record
Manager.
Note: We
recommend
that you not
work with
FMEA
Analyses in
the Record
Manager,
except to view
Equipment or
Functional
Location
records that are
linked to RCM
FMEA Asset
records.
Instead, you
should work
with RCM
Analyses on
the FMEA
Explorer
page.
1993-2014
Meridium, Inc.
All rights
reserved.
Abou
t
Access
ing the
FMEA
Explor
er
Page
You can access
the FMEA
Explorer page
in various
ways,
depending on
the task that
you want to
perform:
You can access

to create a new FM
Analysis from scrat
You can open a

existing analysis fro
the FMEA Analysis
List page.
You can open a

existing analysis fro
the FMEA Recently
Used Analyses pag
You can access

and load an analysi
template to use to
create a new analys
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
About
the FME
Explorer
Pane
When you open an

FMEA Analysis on
FMEA Explorer pa
the RCM FMEA
Analysis family
appears at the root
level in the FMEA
Explorer pane. Belo
the root record,
arranged in a
hierarchical view, t
FMEA Explorer pa
displays the other
components of the
analysis. When you
first open an FMEA
Analysis, only Asse
nodes will be
displayed in the
FMEA Explorer pa
provided that one o
more RCM FMEA
Asset records have
been linked to the r
RCM FMEA Analy
record. The followi
image displays an
example of the RCM
Explorer pane.
You can click the p

sign (+) to the left o
the any RCM FME
Asset node to expan
it and view the
associated Failure
Mode records. You
can expand any
Failure Mode node
view the associated
Failure Effect recor
You can continue
expanding the tree
view all the
components involv
in the analysis.
Components are
linked to one anoth
according to the
relationships define
in the FMEA data
model. The followi
image shows an
example of a fully
expanded branch of
the tree. Notice tha
each analysis node
its own icon to help
you identify it in th
tree.
Hint: You can also

right-click any bran
of the tree and then
click Hide Children
Show Children, as
appropriate, to expa
or collapse that
branch.
Selecting a node in
tree will cause the
datasheet for that
record to appear in
datasheet area of th
FMEA Explorer pa
Note that unlike the

standard Record
Explorer pane, whi
displays all the reco
in the record hierar
that are linked to th
root record through
any relationship, th
FMEA Explorer pa
displays only the
records belonging t
the families that ma
up the FMEA Analy
components,
according to the
FMEA data model.
Therefore, you will
see only the records
that make up a give
FMEA Analysis.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
Using
the
Shortcut
Menu in
the FME
Explorer
Pane
If you right-click a
node in the FMEA
Explorer pane, a
shortcut menu will
appear, displaying
options associated
with the FMEA
Analysis and its
components. The
specific options tha
are available on the
menu will vary,
depending on whic
analysis node you
select. The followin
image shows the
options that appear
the shortcut menu
when you right-clic
Failure Mode node
The following optio

shortcut menu in th
FMEA Explorer pa
Save: Saves any

changes that you ha
made to the current
selected record (i.e.
the record whose
datasheet is display
on the right side of

page).
Save as Templa
Displays the <Node
ID> (new RCM
FMEA Template)
window, where <N
ID> is the ID of the
node that is current
selected in the tree,
where you can save
the current analysis
node(s) as an analy
template.
Load Template:
Displays the
Templates window,
which displays a lis
of Templates that y
can use for adding
new node to the
selected Analysis
node. The list of
Templates displaye
in the window is
appropriate to the ty
of node that is
currently selected.
Cut: Copies the

currently selected
node and all its nod
and then deletes the
records from the
database. A tempor
copy of the records
saved so that you li
them to a different
record using the Pa
function. For exam
you can cut a Failu
Mode node from on
RCM FMEA Asset
node and then paste
to a different RCM
FMEA Asset node.
Copy: Copies th
selected record but
does not remove it
from the analysis tr
After you have cop
a record, the Paste
option will appear o
the shortcut menu s
that you can paste t
record in a differen
location in the
analysis. Note that
the selected analysi
component has
children, a prompt
appears, asking if y
want to copy just th
selected record or t
selected record and
its child records.
Delete: Deletes
selected record from
the analysis and fro
the database. When
you use this option,
prompt appears,
asking if you want
delete the selected
component only or
selected componen
and all its
subcomponents.
If you choo
to delete the selecte
component and all
children, the
Meridium APM
system will delete a
the records from th
analysis and from t
database.
If you choose to
delete the selected
component and not
children, the
Meridium APM
system will delete t
the database and wi
remove any
subcomponents fro
the analysis. The
children will not,
however, be deleted
from the database.
Paste: Links the

copied record to the
record that you sele
in the FMEA Explo
pane. Note that this
menu option appea
only after you have
copied a record and
only if you select a
record to which it i
possible to link the
copied record,
according to the
relationship
definitions that exis
New [Analysis
Component]: Creat
a new record and li
it to the selected
record. The type of
record that is create
will depend on whi
record you select
when you access th
shortcut menu. For
example, if you sel
a Failure Mode nod
this option will read
New Effect and wil
result in the creatio
of a new Failure
Effect record.
Reference
Documents: Displa
the Reference
Documents window
where you can man
the Reference
Documents associa
with the record.
[Component]
Reports: Displays a
submenu, containin
list of reports that a
associated with the
selected componen
For example, when
you select an Failur
Mode node, this
option will be label
Mode Reports.
Show Children:
For a given node of
the analysis tree,
expands the hierarc
to display the
immediate children
that node. This opti
appears only when
you select a collaps
node that has childr
Hint: To expand a
node entirely (i.e., t
expand its children
children's children,
and so on), use the
Expand Node optio
Hide Children:
a given node of the
analysis tree, collap
the hierarchy to hid
the children of that

node. This option
appears only when
you select a node th
has children and tha
is currently expand
Show All:
Completely expand
the currently select
node.
Help: Displays
context-sensitive H
topic for the FMEA
Explorer page.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
About
the
Datashee
Area
The datasheet area,

which appears on th
right side of the
FMEA Explorer pa
displays the datashe
for the record that i
currently selected i
the FMEA Explore
pane. For example,
when you select a
Failure Effect node
the FMEA Explore
pane, the datasheet

area displays the
FMEA Failure Effe
datasheet, which is
populated with the
values that exist in
RCM FMEA Failur
Effect record, outlin
in red in the follow
image.
In the datasheet are

you can view the
information that
currently exists for
selected record and
modify the
information if need
After you make
changes to the reco
information, you ca
click the Save link
the Common Tasks
menu to save your
changes. If you ma
changes to a record
via the datasheet an
then select a differe
node in the FMEA
Explorer pane, you
will be prompted to
save your changes
before displaying th
datasheet for the
newly selected nod
The other features o

the datasheet area,
such as the buttons
that appear above th
datasheet itself, are
same as those that a
available in the
Record Manager.
Note: The New but

above the datash
creates a new recor
in the same family
the selected record.
For example, if you
are viewing an RCM
FMEA
Recommendation
record and you clic
the New button abo
the datasheet, a new
RCM FMEA
Recommendation
record would appea
in the datasheet are
Because the FMEA
Explorer page can
display only one
analysis at a time, t
New button is disab
when you are viewi
the RCM FMEA
Analysis record.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
Analysi
Tasks
Menu
The Analysis Tasks

menu on the FMEA
Explorer page
contains the follow

links:
Manage Team:
Displays the FMEA
Team Members pag
where you can set u
your FMEA Analys
Team.
Review
Recommendations:
Displays the
Recommendation
Management page,
where you can revi
and manage the
Recommendation
records that are
associated with the
current analysis. Th
link is enabled only
one or more RCM
FMEA
Recommendation
records exist for the
current analysis.
View Master
Recommendation: I
the selected
Recommendation
record was
consolidated with o
or more other
Recommendation
records, this link
opens the master
consolidated
Recommendation
record in a stand-al
window. This link i
enabled only if the
selected
Recommendation
record is in the
Consolidated state.
Set Up Evaluati
Displays the Set Up
<Node> Evaluation
dialog box, where
<Node> is the type
the node that is
the FMEA Explore
pane. You can use t
dialog box to define
criteria for sending
evaluation email. T
link is enabled only
an Analysis, RCM
FMEA Asset, or
Recommendation
node is selected in
tree.
Risk Assessmen
Displays the Risk
Assessment feature
If a Failure
node is selected in
analysis tree, the U
Risk window appea
If a Recommen
node is selected in
analysis tree and a
been selected for at
Category in the cor
unmitigated Risk A
the Risk Mitigation
Assessment window
Run Decision L
Launches the Decis
Builder. This link i
only if a Failure Ef
is selected in the tre
View Analysis L
Displays the FMEA
List page, from wh
can open an existin
Analysis.
Create Analysis
the FMEA Explore
displaying a new FM
Analysis.
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
rights reserved.
Commo
Tasks Me
The Common Task

the FMEA Explore
contains the follow
New [Node]: C
new record, whose
indicated by the [N
and links it to the se
record. The name o
changes, depending
mode you select. Fo
example, when you
RCM FMEA Asset
the FMEA Explore
link reads New Mo
you create an RCM
Failure Mode recor
it to the selected RC
Asset node.
Note: This link doe

appear when you se
Recommendation n
Recommendation r
represent the lowes
the FMEA Analysis
Link to Asset: O
Find Items window
you can search for
Equipment or Func
Location record and
the selected RCM F
Asset record. This l
enabled only when
an RCM FMEA As
that is not currently
an Equipment or Fu
Location Asset reco
Open Linked A
Opens in the Recor
the Equipment or F
Location record tha
to the currently sele
FMEA Asset record
is enabled only whe
select an RCM FM
record that is curren
to an Equipment or
Functional Location
Save: Saves the

selected record. For
if a Failure Mode n
selected in the FME
Explorer pane, whe
click this link, the M
APM system will s
changes that you ha
to that Failure Mod
Delete: Deletes
analysis and from t
database. When you
option, a prompt ap
asking if you want
the selected compo
or the selected com

all its subcomponen
If you choo
the selected compo
all its children, the
APM system will d
the records from th
and from the databa
If you choose to
selected componen
the children, the M
APM system will d
database and will re
subcomponents fro
analysis. The childr
not, however, be de
the database.
Cut: Copies the

selected node and a
and then deletes the
from the database. A
temporary copy of
is saved so that you
link them to a diffe
using the Paste func
example, you can c
Failure Mode node
Asset node and then
to a different Asset
Copy: Copies th
record but does not
from the analysis tr
you have copied a r
Paste option will ap
the shortcut menu s
can paste the record
different location in
analysis. Note that
selected analysis co
has children, a prom
appears, asking if y
copy just the select

or the selected reco
its child records.
Note: If you cut or

analysis node, when
the node, the Merid
system will generat
pasted node a new
appropriate to wher
paste it.
Paste: Links the

copied record to the
that you select in th
Explorer pane. Not
menu option appea
after you have copi
and only if you sele
to which it is possib
the copied record, a
to the relationship d
that exist.
Print: Displays
Preview window, w
shows a preview of
current datasheet w
printed. From the P
window, you can se
options and print th
Send To: Displa

submenu with optio
you provide a link t
current page on you
(create shortcut), in
message, or on a H
Help: Displays
context-sensitive H
for the FMEA Expl
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
rights reserved.
Templa
Tasks Me
The Template Task

the FMEA Explore
contains the follow
Save as Templa
[Record ID](New R
Template) window,
ID] is the record ID
analysis node. You
window to save the
or analysis node as
Template.
Load Template:
Templates window,
list FMEA Templat
use for adding a ne
selected Analysis n
FMEA Templates d
window is appropri
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Reports
The Reports menu

Explorer page displ
of the reports that a
the node currently s
FMEA Explorer pa
the menu will chan
depending on whic
For example, when
root-level analysis
labeled Analysis Re
displays a list of rep
with the Analysis n
Each analysis node

folder in the Catalo
determine which re
for which analysis n
appears only if repo
Catalog folder asso
selected node.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Associa
Pages Me
The Associated Pag

FMEA Explorer pa
Associated Pages th
configured via the U
the family of the an
Explorer pane.
Note: The Associa

will not be filtered
type of analysis th
viewing. Any Asso
you configured for
used by both RCM
Analyses will appe
viewing an RCM A
when you are view
Analysis.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
What is
FMEA A
Team?
The FMEA Analysi

which users will pa
FMEA Analysis. Th
Team actually cons
Resource records th
the RCM FMEA An
The FMEA Team M
simply provides a c
for working with H
records that are link
FMEA Analysis rec
people to the FMEA
you can either selec
Resource record tha
in the Meridium AP
you can create a ne
Resource record.
You can configure

Analysis Team on t
Members page, wh
from the FMEA Ex
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Accessin
FMEA Te
Members
To access the FME

page from the FME
On the FMEA E
Analysis Tasks men
Team link.
The FMEA Team M
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Aspects
FMEA Te
Members
The FMEA Team M

grid that displays a
Resource records th
Analysis Team. The
columns:
Record ID: The

Resource record.
Last Name: The

field of the Human
The FMEA Team M

contains three task
perform tasks speci
Team: Analysis Tas

Tasks, and Commo
From the FMEA Te

can:
Add team mem

Human Resource re
Add team mem

Human Resource re
Modify informa
member.
Remove team m
Analysis Team.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Analysi
Menu
The Analysis Tasks

Team Members pag
link:
View in Explor
Analysis on the FM
Create Analysis
page, displaying a n
V3.6.0.0.0 - Copyri
Team M
Menu
The Team Member

Members page con
Create New: Di
dialog box, where y
record and add that
Add Existing: D
dialog box, where y
Resource records to
Edit: Displays t
you can modify the
Human Resource re
Remove: After
selected Human Re
Team. Note that thi
record from the dat
V3.6.0.0.0 - Copyri
rights reserved.
Commo
The Common Task

page contains the fo
Send To: Displa

a link to the current
email message, or o
Help: Displays
Team Members pag
V3.6.0.0.0 - Copyri
reserved.
Adding
the FME
To add a team mem

existing Human Re
On the FMEA T
Tasks menu, click t
The Find a Human
Specify search
Note that the Huma
default. You cannot
criteria if desired.
Click the Find N
The Human Resour

list at the bottom of
In the list of res
Click the Select
The Human Resour

Team Members pag
V3.6.0.0.0 - Copyri
Creatin
FMEA A
To add a team mem

Resource record:
On the FMEA T
the Create New link
The Create New Te
On the datashee
Note that a Last Na
Click the Save b
The new Human Re
V3.6.0.0.0 - Copyri
Modifyi
Member
To modify the Hum
On the FMEA T
Record ID of the H
The Edit Team Mem
Make the desire
Click the Save b
Your changes are sa
V3.6.0.0.0 - Copyri
Removi
Analysis
Note: Removing a t
the Human Resourc
Resource record fro
To remove a Huma
On the FMEA T
Human Resource re
On the Team M
A message appears
FMEA Analysis Te
Click the Yes b
The Human Resour
V3.6.0.0.0 - Copyri
Adding
Analysis
To add an RCM FM
With the analys

pane.
On the Commo
-or-
Right-click the ana
A new RCM FMEA
Select the new R

of the page.
On the FMEA A
generated automati
be modified but is r
When you are f
The information tha
Re-select th
Add a Failure M
V3.6.0.0.0 - Copyri
Linking
Function
If your system has

Location records in
(which are not repr
represented by exis
When RCM FMEA

Location record wi
linked to any Recom
The first step in lin

FMEA Analysis. Af
Equipment or Func
Note that if the Sys

FMEA Asset record
Definition tab does
the Site Reference f
Functional Location
are linked to that Si
To link an RCM FM
On the FMEA E
On the Commo
Note: This link is e

Location record.
The Find Asset win
In the Search In
Note: The Search In
Specify any add
The records that ma
Select the row r
Click the Select
The Find Items win

the selected record.
additional fields ma
in Record Manager
V3.6.0.0.0 - Copyri
Viewing
RCM FM
When an RCM FM
After you open the
To view the Equipm
On the FMEA E
On the Commo
The Record Manag
V3.6.0.0.0 - Copyri
Unlinki
Records
The FMEA Explore

unlink an RCM FM
Asset record to a di
In the FMEA E
linked to an Equipm
Open the RCM
Note: If you link an

record using one of
You should unlink

created and linked t
to records no longe
a different one, if th
Recommendation r
modified.
V3.6.0.0.0 - Copyri
Defining
To add an RCM FM
With the analys

RCM FMEA Failur
On the Commo
-or-
Right-click the Ass
A new Failure Mod
The FMEA Failure
In the FMEA Fa
The Failure Mo
The Failure Mo
The Related As
Type field, that valu
When you are f
The information tha
Select an As
Add a failure ef
V3.6.0.0.0 - Copyri
Defining
To add an FMEA F
With the analys

record.
On the Commo
-or-
Right-click the Fail
A new Failure Effe
The FMEA Failure
In the FMEA Fa
generated automati
On the Analysis
The Unmitigated R
eate recommendations that are based upon the recommended actions.
pon the responses to the questions that were presented. Your responses to the questions and the
cribed in more detail in this standards document. To use the Decision Logic Builder effectively, you will need
. If you close the Decision Logic Builder before responding to all questions and clicking the Finish button,
ify this value, recommendation evaluation email may not be generated properly. In addition, the Meridium
n cells.
al in the Display FFI Units As list. The value in the Interval cell will be updated to reflect the selected unit.
fect's risk assessment.
sessment feature appears in the Mitigated Financial Risk field on the FMEA Recommendation datasheet.
ecord for the analysis.
another location within the same analysis. Note the following about using the cut, copy, and paste functions:
ote also that the Cut function automatically copies all nodes of the selected node.
e other nodes on the level where you are pasting, finds the highest numeric value of all the current IDs, adds
d.
u will be able to paste the cut node only once.
copied along with it.
ust select a Failure Effect node in order paste the copied elements. The Paste function will be enabled only
modify.
set record and the Equipment or Functional Location record will be broken. The Asset record will not,
create a new FMEA Analysis or append nodes to an existing FMEA Analysis. FMEA Template records
he FMEA Template.
ready used in a similar analysis.
ks that you can perform on that FMEA Template. You can use the following lists as a guide for determining
EA Explorer pane.
ation page. By default, this page displays the Template List query, which is stored in the
ppears as a list at the top of the FMEA Templates page. The Template Type list contains the following
you access the FMEA Templates page from the FMEA Template Explorer page, the query uses as the
rer page.
g query results. Note that each of the values listed above corresponds to a value that can be stored in the
ing the default Template List query. If you have modified the default query or if you are using a different
late. For example, if the root node in the template is a Failure Mode, the Template Type cell will contain the
CM FMEA Template record.
query results on this page will contain only RCM FMEA Template records whose Analysis Type is FMEA.
d in the results grid.
MEA Asset record, this link will display the Apply Template Builder, which you can use to specify whether
.
set records, this link will create the analysis from the template and open it on the FMEA Explorer page.
whose Template Type is Analysis. This link is disabled if more than one RCM FMEA Template record is
ess of creating an FMEA Template from scratch.
rer page, where you can modify the record and save your changes. This link is enabled only when at least
Template is selected in the grid.
d from the database. This link is enabled only when at least one record appears in the grid. You can select
on your desktop (create shortcut), in an email message, or on a Home Page.
e Template Builder:
plate link.
Template link.
New FMEA Template from Scratch
e Template Builder.
mplate, and click the Next button.
Template Type that you selected in the previous step. For example, if you are creating an FMEA Template
tasheet for an RCM FMEA Analysis record will appear on the Define Root Node screen, as shown in the
ystem and can not be modified. If you are creating an FMEA Template at the analysis level, the Analysis
in the preceding image.
xt button.
A Template datasheet.
ith the template type value, which indicates the family of the record from which the template was created.
ally with FMEA.
y.
he FMEA Template Explorer page, where the Template Type that you defined is the root node in the FMEA
e new template record appears in the datasheet area.
Inc. All rights reserved.
emplate from an Existing FMEA Analysis
w analysis or to create new nodes in an existing analysis, all the nodes that are included in the FMEA
rom the FMEA Explorer page, you can create a new FMEA Template from an FMEA Analysis or any
oot FMEA Analysis node, the FMEA Template will include:
that make up the Team Member list.
ect, and Recommendation nodes included in the analysis.
nked to the analysis elements.
hat includes RCM FMEA Asset records that are linked to Equipment or Functional Location records, the
MEA Template is created. In this way, the RCM FMEA Asset records that are linked to the FMEA Template
ons. When you create a new analysis from the FMEA Template, you will be given the choice to keep or
with Equipment or Functional Location records.
m an analysis element other than the Analysis node (i.e., a node that appears below the Analysis node), the
node and all of its successor nodes. The root node in the FMEA Template determines the nodes to which the
EA Analysis, with respect to the record hierarchy. For example, an FMEA Template whose root node is a
ilure Mode node.
n existing FMEA Analysis:
EA Explorer page.
e node that you want to use as the root node in the FMEA Template.
click the Save as Template link.
ord appears in a new window.
asheet, the following fields contain values by default:
ell is disabled and populated automatically with the template type value, which indicates the family of the
the template was created.
Type cell is disabled and populated automatically with FMEA.
l is disabled and populated automatically.
n cell is disabled and populated automatically.
ete the details of the datasheet as needed.
OK.
mplate is created and appears on the FMEA Template Explorer page, where you can view and modify its
you created the FMEA Template at the Analysis node level, you will be able to use the FMEA Template for
w FMEA Analyses. Otherwise, you can apply the FMEA Template to an existing analysis to create new
des based on the ones in the template.
- Copyright 1993-2014 Meridium, Inc. All rights reserved.
out Creating New FMEA Analyses from FMEA

plates
eate a new FMEA Analysis from any FMEA Template whose root node is an Analysis node. Depending upon
e template is associated with RCM FMEA Asset records or not, the steps that you perform to create the new
ll vary.
If you are applying an FMEA Template that is not associated with any RCM FMEA Asset records, you will
ow a one-step template application process via the FMEA Templates page.
If you are applying an FMEA Template that is associated with at least one RCM FMEA Asset record, you
use the Apply Template Builder, which provides an option for you to replace the virtual equipment and
ations with Equipment or Functional Location records.
6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.
Creating a New Analysis from an FMEA Template

Without RCM FMEA Asset Records
following instructions provide details on creating a new FMEA Analysis by applying an FMEA Template.
se instructions assume that the Analysis node is the root node in the FMEA Template that you are using to
ate a new FMEA Analysis and that the template is not associated with any RCM FMEA Asset records.
create a new FMEA Analysis from an FMEA Template:
Access the FMEA Templates page.

In the grid, select the row containing the FMEA Template that you want to use to create a new
FMEA Analysis.
On the Template Tasks menu, click the Create Analysis link.
The FMEA Analysis is created and displayed on the FMEA Explorer page, where you can view and
modify its contents.
Accessing the Apply Template Builder

The following instructions provide details on accessing the Apply Template Builder, which you can use
to create a new FMEA Analysis from a template and specify whether you want to keep or replace the
RCM FMEA Asset record(s) that are associated with the template.
These instructions assume that the FMEA Template that you are using to create a new FMEA Analysis is
associated with at least one RCM FMEA Asset record.
To access the Apply Template Builder:
Access the FMEA Templates page.
In the results grid, select the row containing the FMEA Template that you want to use to
create a new FMEA Analysis.
On the Template Tasks menu, click the Create Analysis link.

Create a New FMEA Analysis
Using the Apply Template Builder, you can choose to keep or exchange any RCM FMEA
Asset record that is associated with the template that you are applying to a new FMEA
Analysis. These instructions assume that the template with which you are creating a new
FMEA Analysis is associated with at least one RCM FMEA Asset record.
To create a new FMEA Analysis using the Apply Template Builder:
Access the Apply Template Builder.
On the Welcome screen, click the Next button.
The Review Template Assets screen appears, displaying a list of RCM FMEA
Assets that are associated with the selected FMEA Template. Below the grid, the
Keep these assets option is selected by default.
If you want to apply to the analysis all the RCM FMEA Asset records
that are associated with the template, click the Finish button.
Note: If you choose the Keep these assets option, the new FMEA Analysis
will not be linked to any Equipment or Functional Location records (i.e.,
physical equipment and locations).
-orIf you want to replace the RCM FMEA Asset records that are associated
with the template, select the Replace these assets with new selections
option, and then click the Next button.
The Select Asset Replacements screen appears.
On the Select Asset Replacements screen, click the Select

Replacements button.

Note: The Search In list will contain only families that are related
to the RCM FMEA Asset family through the Is RCM FMEA Asset
relationship.
In the Search In list, select the family from which you
will apply equipment and location records to the analysis,
and then click the Find Now button.
The results appear in a grid.
Select the records that you want to use as
replacements for the RCM FMEA Asset records that
are currently linked to the FMEA Template, and
then click the Select button.
The system checks to see if the selected equipment
and locations can be added to the analysis:
If any cannot be added to the analysis, those
records are displayed in a separate window with a
message indicating why the record cannot be added.
The RCM FMEA Asset records can be added are
successfully linked to the FMEA Analysis.
You can continue adding Equipment and
Functional Location records in this way.
When you are finished, click the Next
button.
The Review/Replace Template Assets screen
appears.
This screen contains two columns:

Template Asset: Contains the RCM
FMEA Asset records that are currently
associated with the FMEA Template.
Asset: Contains a list that you can use to
specify what you want to do with the RCM
FMEA Asset record in that row. The Asset

list contains the following values:
(Keep Template Asset):
Indicates that you want to add the
RCM FMEA Asset record to the
FMEA Analysis without linking it to
an Equipment or Functional Location
record. This option is selected by
default.
(Discard Template Asset):
Indicates that you do not want to add
the RCM FMEA Asset record or any
of its subnodes to the FMEA
Analysis. Note that this option does
not delete the RCM FMEA Asset
from the FMEA Template.
<Selected Assets>: Indicates that
you want to replace the RCM FMEA
Asset record that is linked the FMEA
Template with the Equipment and
Functional Location records that you
selected in the previous steps.
For each RCM FMEA
Asset record in the Template
Asset column, select the
option in the Asset
Assignment list that
corresponds to the action that
you want to take.
Click the Finish
button.
The new FMEA
Analysis is created
and displayed on the
FMEA Explorer page,
where you can view
and modify its
contents.
V3.6.0.0.0 Copyright 19932014 Meridium, Inc.

Creating
New
FMEA
Analysis
Nodes
from an
FMEA
Template
While working with
an existing FMEA
Analysis, you can
create new nodes
(e.g., Failure Effects)
by applying an FMEA
Template.
Note: You can also
uses these instructions
to create new template
elements from an
FMEA Template.
To create new analysis
nodes from an FMEA
Template:
Open on the
FMEA Explorer page
the FMEA Analysis to
which you want to

apply Analysis nodes.
In the FMEA
Explorer pane, locate
the node below which
you want to add new
analysis nodes. For
example, if you want
to link new Failure
Effect records to a
Failure Mode record,
select the Failure
Mode node.
On the Template
Tasks menu, click the
Load Template link.
The Templates
window appears.
The Templates
window displays a list
of all the RCM FMEA
Template records that
can be used to create a
successor node for the
selected node. For
example, if you
selected a Failure
Mode node, the
Templates window
will display all the
Failure Effect
Templates that can be
used to create a
Failure Effect node.
Because RCM FMEA
Template records can
be shared across RCM
and FMEA analyses,
this list will contain
both RCM Templates

and FMEA Templates.
Select the
row containing
the RCM
FMEA
Template
record that you
want to use to
create the new
node, and then
click OK.
The FMEA
Template is
applied to the
FMEA
Analysis, and
then the node
that
corresponds to
the root node
from the
template is
selected by
default in the
FMEA
Explorer pane.
1993-2014
Meridium, Inc.
All rights
reserved.
Modi
fying
Existin
g
FMEA
Templ
ates
To modify an
existing
FMEA
Template:
Access the
FMEA
Templates
page.
In the
query results
grid, click the
hyperlinked
ID of the
FMEA
Template that
you want to
modify.
The FMEA
Template
Explorer page
appears,
displaying the
RCM FMEA
Template
record that you
selected.
Modify
the
templat
e as
needed
.
Click
the
Save
button.
Your
change
s are
saved
to the
databas
e.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
D
elet
ing
F
M
EA
Te
mp
lat
es
The
followi
ng
instruct
ions
provide
details
on
deletin
g an
FMEA
Templa
te via
the
FMEA
Templa
tes
page.
You
can
also
delete
an
FMEA
Templa
te via
the
FMEA
Templa
te
Explor
er
page.
To
delete
an
FMEA
Templa
te:
Access
the
FMEA
Templa
tes
page.
In
the
grid,
select
the row
contain
ing the
FMEA
Templa
te that
you
want to
delete.
On
the
Templa
te
Tasks
menu,
click
the
Delete
Templa
te link.
A
confir
mation
messag
e
appears
,
asking
if you
really
want to
delete
the
selecte
d
FMEA
Templa
te.
C
l
i
c
k
t
h
e
Y
e
s
b
u
t
t
o
n
.
T
h
e
F
M
E
A
T
e
m
p
l
a
t
e
s
p
a
g
e
r
e
f
r
e
s
h
e
s
,
a
n
d
t
h
e
R
C
M
F
M
E
A
T
e
m
p
l
a
t
e
r
e
c
o
r
d
i
s
d
e
l
e
t
e
d
f
r
o
m
t
h
e
d
a
t
a
b
a
s
e
.
V
3
.
6
.
0
.
0
.
0
C
o
p
y
r
i
g
h
t
1
9
9
3
2
0
1
4
M
e
r
i
d
i
u
m
,
I
n
c
.
A
l
l
r
i
g
h
t
s
r
e
s
e
r
v
e
d
.
A
b
o
u
t
t
h
e
F
M
E
A
T
e
m
p
l
a
t
e
E
x
p
l
o
r
e
r
P
a
g
e
T
h
e
F
M
E
A
T
e
m
p
l
a
t
e
E
x
p
l
o
r
e
r
p
a
g
e
i
s
t
h
e
p
a
g
e
t
h
a
t
y
o
u
w
i
l
l
u
s
e
t
o
w
o
r
k
w
i
t
h
F
M
E
A
t
e
m
p
l
a
t
e
s
.
I
t
d
i
s
p
l
a
y
s
a
n
F
M
E
A
T
e
m
p
l
a
t
e
i
n
a
h
i
e
r
a
r
c
h
i
c
a
l
v
i
e
w
s
o
t
h
a
t
y
o
u
c
a
n
v
i
e
w
t
h
e
R
C
M
F
M
E
A
T
e
m
p
l
a
t
e
r
e
c
o
r
d
i
t
s
e
l
f
a
l
o
n
g
w
i
t
h
a
l
l
t
h
e
r
e
l
a
t
e
d
r
e
c
o
r
d
s
.
T
h
e
l
a
y
o
u
t
o
f
t
h
e
F
M
E
A
T
e
m
p
l
a
t
e
E
x
p
l
o
r
e
r
p
a
g
e
i
s
s
i
m
i
l
a
r
t
o
t
h
a
t
o
f
t
h
e
R
e
c
o
r
d
M
a
n
a
g
e
r
,
w
h
e
r
e
i
t
i
s
d
i
v
i
d
e
d
i
n
t
o
t
h
r
e
e
m
a
i
n
a
r
e
a
s
:
The
task
menu
pane,
which
contain
s the
followi
ng task
menus:

Analysis Tasks
Common
Tasks
Template
Tasks
Reports
Associated
Pages
FMEA
Template
Explorer pane
The
datasheet area,
which displays
the
information
stored in the
record for the
selected node.
Note that
throughout our
discussion of
the FMEA
Template
Explorer page,
we assume that
you are
familiar with
the basic
concepts and
navigational
features of the
Record
Manager. We
limit our
discussion
primarily to
features that
are specific to
the FMEA
Template
Explorer page
and that
deviate from
the standard
functionality
of the Record
Manager.
1993-2014
Meridium, Inc.
All rights
reserved.
Acce
ssing
the
FMEA
Templ
ate
Explor
er
Page
You can access
the FMEA
Template
Explorer page
by performing
the following
tasks:
Modifying an
existing FMEA
Template.
Creating a new
FMEA Template fro
scratch.
Creating an
FMEA Template fro
an existing FMEA
Analysis.
The following imag

shows what the
FMEA Template
Explorer page look
like when you acce
it from an existing
FMEA Template.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
About
the FME
Template
Explorer
Pane
When you open an

FMEA Template on
the FMEA Templat
Explorer page, in th
FMEA Template
Explorer pane, the
root node correspon
to the node from
which the FMEA
Template was creat
Below the root reco
the FMEA Templat
Explorer pane
displays the other
components of the
template arranged i
hierarchy.
When you first ope

an FMEA Template
only the root node a
the nodes that
represent direct
successor records o
that root node appe
in the FMEA
Template Explorer
pane. You can click
the plus sign (+) to
left of any node to
expand it and view
next record that exi
in the tree. You can
continue expanding
the tree to view all
components involv
in the FMEA
Template.
Components within
the FMEA Templat
Explorer pane are
linked to one anoth
according to the
relationships define
in the FMEA data
model. The followi
image shows an
example of a fully
expanded branch of
the tree. Notice tha
each template node
represented by an
icon, which
distinguishes that
analysis element in
the tree.
Hint: You can also

right-click any bran
of the tree and then
click Hide Children
Show Children, or
Show All, as
appropriate, to expa
or collapse that
branch.
Selecting a node in
tree will cause the
datasheet for that
record to appear in
datasheet area of th
FMEA Template
Explorer page.
Note that unlike the

standard Record
Explorer pane, whi
displays all the
records in the recor
hierarchy that are
linked to the root
record through any
relationship, the
FMEA Template
Explorer pane
displays only the
records belonging t
the families that ma
up the FMEA
Template compone
according to the
FMEA data model.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
The
Shortcut
Menu in
the FME
Template
Explorer
Pane
If you right-click a
node in the FMEA
Template Explorer
pane, a shortcut me
will appear, display
options associated
with the FMEA
Template and its
components. The
specific options tha
menu will vary,
depending which n
you select. The
following image
shows the options t
appear on the short
menu when you rig
click a Failure Mod
node.
The following optio

shortcut menu in th
FMEA Template
Explorer pane:
Save: Saves any

changes that you ha
made to the record
that is currently
selected.
Save as Templa
Displays a new RC
FMEA Template
record in a new
window, from whic

you can create a ne
FMEA Template us
node as the root no
Load Template:
Facilitates the creat
of a new FMEA
Template node by
applying an existin
FMEA Template to
node.
Cut: Removes t
currently selected
node and all its
successor nodes fro
the tree so that you
can paste them in a
different location.
After you have cut
node, the Paste opti
will appear on the
shortcut menu so th
you can paste the n
in a different locati
in the tree.
Copy: Copies th
selected node. Afte
you have copied a
node, the Paste opti
will appear on the
shortcut menu so th
you can paste a cop
of that node in a
different location in
the tree. If the selec
template element h
successor nodes, a
prompt appears,
asking if you want
copy only the selec
node or the selected
node and all its

successor nodes.
Paste: Pastes th
cut or copied nodes
the selected locatio
Note that this menu
option appears only
after you have copi
or cut a node and if
you select a
predecessor node th
participates in a
relationship with th
node that you want
paste.
Delete: Deletes
selected node and a
its subnodes from t
template and from t
database.
New <Node>:
Where <Node> is t
analysis element th
you want to create.
The name of this lin
will change depend
upon the predecess
node that is selected
the tree. This link
creates a new recor
in the family indica
by the <Node> valu
and links it to the
selected predecesso
record. For exampl
if you select a Failu
Mode node, this lin
will be labeled New
Effect and will resu
in the creation of a
new Failure Effect
record that is linked
the Failure Mode
record that is
represented by the
selected Failure Mo
node.
Reference
Documents: Displa
the Reference
Documents window
where you can
manage the Referen
Documents associa
with the record.
<Node> Report
Where <Node> is t
analysis element
whose reports you
want to view. When
you point to this lin
a submenu appears
and contains a list o
reports that are
associated with the
selected componen
For example, when
you select an RCM
Function node, this
option will be label
Function Reports.
This menu option
appears only if repo
exist for the family
that is represented b
the selected node.
Show Children:
Expands the hierarc
to display the
successor nodes tha
appear directly belo
a given node. This
option appears only
when you select a
collapsed predecess
node.
Hide Children:
Collapses the
hierarchy to hide th
successor nodes tha
appear directly belo
a given node. This
option appears only
when you select an
expanded predecess
node.
Show All:
Expands all succes
nodes that exist bel
the selected node.
Help: Displays
context-sensitive H
topic for the FMEA
Template Explorer
page.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
About
the
Datashee
Area
The datasheet area,

which appears on th
right side of the
FMEA Template
Explorer page,
displays the datashe
for the record that i
the FMEA Templat
Explorer pane. For
example, when you
select an FMEA
in the FMEA
Template Explorer
pane, the datasheet
area displays the
Failure Effect
datasheet, which is
populated with the
values that exist in
The following imag
shows an example o
the datasheet area o
the FMEA Templat
Explorer page. A re
outline has been
added to the image
highlight this area.
The features of the

datasheet area, such
the buttons that app
above the datasheet
itself, are the same
those that are
available in the
Record Manager.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
Analysi
Tasks
Menu
The Analysis Tasks

menu on the FMEA
Template Explorer
page contains links
that you can use to
work with the analy
elements in the FM
Template Explorer
pane. The links on
menu are hidden or
disabled based upo
the node that is
The following list

describes the links
that have been defin
for the Analysis Ta
menu:
Template
Definition: Display
the datasheet for th
current RCM FME
Template record. T
link is available for
ALL template types
Manage Team:
Displays the FMEA
Team Members pag
where you can crea
and manage Human
Resource records fo
an FMEA Analysis
Template.
Note: This link

appears only when
you are working wi
a template whose ro
node is an Analysis
node.
Risk Assessmen
Displays the Risk
Assessment feature
This link is enabled
only when:
If a Failure
If a Recommen
selected in the tree
been selected for at
Category in the cor
unmitigated Risk A
This link does not a

are working with a
root node is a Reco
node.
Run Decision L
Decision Logic Bui
enabled only when
Failure Effect node
link does not appea
working with a tem
node is a Recomme
Manage Templa
FMEA Templates p
the value in the Tem
prompt is set to the
the template you w
viewing.
Create Templat
Template Builder, w
to create a new FM
from scratch.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Commo
Menu
The Common Task

FMEA Template Ex
contains links that y
work with the analy
the FMEA Templat
These links are hidd
based on the node t
the tree.
The Common Task

FMEA Template Ex
contains the follow
New <Node>: W
the analysis elemen
create. The name of
change depending u
predecessor node th
the tree. This link c
record, whose type
the <Node> name a
selected predecesso
example, when you
node in the FMEA
pane, this link read
lets you create an R
Failure Mode recor
selected Asset node
Save: Saves the

record.
Delete: Deletes
record and all its su
from the template a
database.
Cut: Removes t
selected node and a
nodes from the tree
paste them in a diff
After you have cut
option will appear o
menu so that you ca
in a different locati
Copy: Copies th
After you have cop
Paste option will ap
shortcut menu so th
copy of that node in
location in the tree.
template element h
nodes, a prompt ap
you want to copy o
node or the selected
successor nodes.
Paste: Pastes th
nodes in the selecte
that this menu optio
after you have copi
and if you select a p
that participates in
the node that you w
Print: Displays
window. From the P
you can select print
the record.
Send To: Displa

with options that le
link to the current p
desktop (create sho
message, or on a H
Help: Displays
sensitive Help topic
Template Explorer
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Templa
Menu
The Template Task

FMEA Template Ex
contains the follow
Save as Templa
FMEA Template re
from which you can
Template using the
as the root node. Th
creation of a new R
Load Template:
window, which disp
Templates that you
new node to the sel
node. The list of FM
in the window is ap
V3.6.0.0.0 - Copyri
Meridium, Inc. All
<Node>
Menu
The <Node> Repor

Template Explorer
associated with the
in the FMEA Temp
name of the menu w
appropriate, depend
select. For example
root-level analysis
Analysis Reports an
reports associated w
shown in the preced
Each template node

the Catalog that is u
reports to display fo
component. This m
reports exist in the
with the selected no
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Associa
Menu
The Associated Pag

Template Explorer
Pages that have bee
Manager for the fam
that is currently sel
Template Explorer
Note: The Associa

be filtered based o
that you are viewi
that you configure
used by both RCM
will appear when y
RCM Template an
an FMEA Templa
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Accessin
FMEA Te
Members
an FMEA
To access the FME

for an FMEA Temp
Open an existin
FMEA Template Ex
On the Analysi
Manage Team link.
The FMEA Team M

displaying a list of
that have been defin
FMEA Template.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
About t
Team Me
for FMEA
The FMEA Team M

Templates contains
of all the Human R
up the FMEA Analy
the grid represents
record. For each rec
following informati
Record ID: The

Resource record.
Last Name: The

Name field in the H
The FMEA Team M

contains the follow
Tasks, Team Memb
Tasks.
From the FMEA Te

can:
Add team mem

Human Resource re
Add team mem

Human Resource re
Modify informa
member.
Remove team m
Analysis Team.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Analysi
Menu
The Analysis Tasks

Team Members pag
links:
Template Defin
Template record ass
Template.
View in Explor
Template on the FM
Create Templat
which you can use
from scratch.
V3.6.0.0.0 - Copyri
Team M
Menu
The Team Member

Team Members pag
Create New: Di
dialog box, where y
record and add that
Add Existing: D
dialog box, where y
Resource records to
Edit: Displays t
you can modify the
Human Resource re
Remove: After
selected Human Re
Team. Note that thi

record from the dat
V3.6.0.0.0 - Copyri
rights reserved.
Commo
The Common Task

page contains the fo
Send To: Displa

a link to the current
email message, or o
Help: Displays
Team Members pag
V3.6.0.0.0 - Copyri
reserved.
Introdu
Reports
Meridium APM sup
Reports that are
Reports that app
FMEA relies upon

appear where throu
corresponding Cata
the reports stored in
For example, when

Explorer page and y
menu will display a
folder: \\Public\Me
In addition, the Cat

appear on the FME
V3.6.0.0.0 - Copyri
About R
FMEA
The baseline FMEA

reports that you can
FMEA Explorer pa
and storing them in
to access and view
addition, the baselin
generic FMEA repo
Page.
When you view an

report and open it o
functionality will b
V3.6.0.0.0 - Copyri
Accessin
Page
The FMEA Reports

configured for use w
the following Catal
FMEA Reports pag
The FMEA Reports

the Catalog. Theref
\\Public\Meridium\
use captions that ar
report to other user
Note: The baseline

that will appear on
FMEA product con
\\Public\Meridium\
Because this report
report, it is automat
on the FMEA Repo
folder \\Public\Mer
page.
To access the FME
On the FMEA S
The FMEA Reports
V3.6.0.0.0 - Copyri
Opening
The FMEA Reports

Catalog folder: \\Pu
as a hyperlink.
To run a report that
Click any hyper
The results of the re
V3.6.0.0.0 - Copyri
Runnin
or Analys
Reports that have b

element and stored
an analysis or analy
For example, when

you select a Failure
are stored in the fol
addition, you can ri
shortcut menu whic
node.
To run an FMEA re
From any of the
The results of the re
V3.6.0.0.0 - Copyri
About M
You can access Rec

records via the Ana
When you access R

working with RCM
V3.6.0.0.0 - Copyri
Accessin
from the
To review FMEA R
Access the FME
On the Analysis
The Recommendati
records that exist fo
V3.6.0.0.0 - Copyri
Feature
Page whe
When you access R

Management page
Recommendation M
This page is divided
Recommendatio
are linked to the eq
Task menus: Th
Common Tasks me
Additionally, when
top of the page and
The following imag
V3.6.0.0.0 - Copyri
Asset Ta
The Asset Tasks me
The Asset Tasks me
Promote to Str
Location records th
only if the RCM FM
location.
Promote to Tem
the selected RCM F
Recommendation r
V3.6.0.0.0 - Copyri
Viewing
Consolida
If you have consoli

while you are view
access the master R
The following instr

on the FMEA Explo
You can determine

datasheet toolbar, a
To view a master R
On the FMEA E
The View Master R
V3.6.0.0.0 - Copyri
About E
After you create an

the future. Specific
The entire analy
Any equipment
Any recommen
The evaluation feat

create two types of
A date-based ev
current date and tim
An event-based
cost and/or count cr
If you want to evalu
If you want to evalu

date-based evaluati
or recommendation
After evaluation cri

Schedule Manager,
item. When it is exe
based on the existin
Note that evaluatio

criteria for an analy
evaluation criteria i
that the values that
appropriate permiss
recommend that yo
V3.6.0.0.0 - Copyri
About A
After you create an
How valid the o
Whether the an
For each analysis, y

basis and are trigge
When an email mes
The description
Description field in
A statement ind
A hyperlink tha
V3.6.0.0.0 - Copyri
About E
After you add equip

equipment or locati
that the piece of eq
Equipment or Func
to an Equipment or
Two types of evalu
A date-based ev
An event-based
failure cost and/or c
Note: Configuring
configuring an even
to that recommenda
location. The only d
equipment/location
set up the evaluatio
reviewed. It is up to
the recommendatio
entire piece of equi
When a message is
The ID of the R
was configured.
A statement ind
A hyperlink tha
equipment or locati
Note that the conten
V3.6.0.0.0 - Copyri
About R
After you create Re

recommendation in
How valid the o
Whether the rec
Whether additio
Two types of evalu
A date-based ev
An event-based
recommendation m
Note: Configuring
an event-based eva
recommendation. B
location. The only d
the recommendatio
the equipment/loca
is up to you to dete
equipment/location
specific recommend
When a message is
The ID of the R
A statement ind
A hyperlink tha
record belongs.
Note that the conten
V3.6.0.0.0 - Copyri
About D
A date-based evalu
according to the sch
and time. Therefore
location, or recomm
When you create a

scheduled item is e
is due for evaluatio
If you set up date-b

sent, no additional
FMEA Analysis an
executed on 5/14/2
will be sent. If the s
Note: After a messa

the record, but no a
modify the evaluati
You can also specif

recurring schedule.
Evaluation Date is
to the interval that y
Evaluation Date is
For example, you m

they are created. In
recommendations t
Regardless of the d
based evaluation.
V3.6.0.0.0 - Copyri
Setting
A date-based evalu
you define. In datedate-based evaluati
specific date or on
should be reviewed
year. Regardless of
date-based evaluati
To set up a date-ba
Open the desire
Expand the ana
Select the node
The Set Up <Node>

Explorer pane.
Select the Date-
The Date-Based Ev
In the Next eva
If you are d
evaluation email m
If you are defin

sent. Subsequent em
will be incremental
datasheet and on th
If you want the
Select the Perfo
In the Every tex
In the list to the
For example, if you
In the Notify te
evaluations.
Note: If you are def

address field that is
specified for the ev
Click OK.
The evaluation crite

dialog box, indicati
Click OK to clo
-or-
Select the Event-ba
V3.6.0.0.0 - Copyri
About E
If your FMEA syste

or Functional Loca
configure the Merid
you specify that wh
Event-based evalua
executed daily, at th
sends an email mes
V3.6.0.0.0 - Copyri
Setting
If your FMEA syste

Equipment and Fun
criteria, you can co
evaluations let you
person.
Note: For event-bas
To defined event-b
Open the desire
Expand the ana
Select the desir
The Set Up <Node>
Select the Even
The Event-Based E
If you want to s
number of failures
Hint: Accept the de
If you want to s
failure cost that mu
Hint: Accept the de
In the Starting f
that occurred on thi
Note: Unlike date-b

on the Starting from
email message only
In the Notify te
evaluation.
Note: If you are def

reason, if you have
Click OK.
The evaluation crite

defined.
Click OK to clo
o disable evaluations, simply clear the check boxes on the Set Up <Node> Evaluation dialog box appears,
-or-
Select the Date-bas
V3.6.0.0.0 - Copyri
Modifyi
You can use the fol

To modify existing
ending on where you want them to be available.
he baseline FMEA product. Note that the Stored In column contains an abbreviated Catalog path, where each
ms that were delivered with the baseline product. The Meridium APM system reads from the subfolders in
ailure Finding Activity cells effectively, you will need to be familiar with this standard.
Cell
Description
Stores the mean time between multiple failures.
MMF
For example, a 1 in 1,000,000 probability of a multiple failure in one year
implies a mean time between failures of 1,000,000 years.
The probability of multiple failures occurring in any one year is 1/MMF.
MTIVE Stores the mean time between failures of the protective device.
Stores the mean time between failures of the protected function.

MTED
For example, if the demand rate of the protected function is once in 200 years,
this equals a probability of failure for the protected function of 1 in 200 in any
one year, or a mean time between failures of the protected function of 200 years.
The probability of failure of the protected function in any one year is 1/MTED.
n
The number of protective devices.
Table ID
SC_RECOM_RESOURCE Recommended
Resource
Use to populate the Recommended

Resource list in RCM FMEA
M and not FMEA. To launch the feature for FMEA, you must expand the root address by adding parameters.
e FMEA Recently Used Analyses page.
ates page and modify the behavior of the URL.
er is required whenever you want to use a Template to create a new analysis node. Whenever you specify
ey parameter, you must also use the AnalysisKey parameter, even if the AnalysisKey and the SelectedKey
value (i.e., if you are loading templates to link to the analysis node).
is required whenever you want to use a Template to create a new analysis node. Whenever you specify the
arameter, you must also use the AnalysisKey parameter.
een omitted, clicking a hyperlinked Template ID will load the analysis template on the FMEA Explorer page.
s, you can click a hyperlinked Template ID to open analysis 2345678 on the FMEA Explorer page, where a
orrespond to a datasheet that has been defined for the specified family. If you omit this parameter, the default
his parameter is optional.
uld correspond to an entity belonging to the family identified by the FamilyKey parameter. This parameter
u are loading an existing analysis.
the Family Key of each root record. The Family Key that you specify should correspond to the EntityKey
rameter is required whenever you are loading an existing analysis.
whenever you want to load a new analysis on the FMEA Explorer page.
whenever you want to create a new FMEA Analysis on the FMEA Explorer page, as specified by the
n omit this parameter whenever you specify the EntityKey and FamilyKey parameters.
alysis consists of the following components:
nalyses.

ASWP

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ASWP

Hochgeladen von

Copyright:

Verfügbare Formate

About the Asset Strategy Work Process

Evaluate asset risk

Identify and qualify unmitigated risks.

Identify gaps in mitigation.

Define regulatory actions.

Document areas that need improving.

Document your decision process.

Review the impact of the new strategy on risk and cost,

The updated strategy profile.

Why the updated strategy was selected.

The return on investment value.

The risk reduction numbers.

Recommendations that were identified.

Document the decision-making process behind the new

A process for obtaining and communicating feedback

Ensure the work is being documented.

Review work history to maintain and ensure regulation

Asset Strategy Management (ASM)

Asset Strategy Optimization (ASO)

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Asset Strategy System Requirements

Asset Strategy Management (ASM)

Asset Strategy Optimization (ASO)

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

First-Time Deployment Workflow

Configure the Asset Strategy Management module.

Configure the Asset Strategy Implementation

Configure the Asset Strategy Optimization module.

Configure one of the following modules:

Reliability Centered Maintenance

Failure Modes and Effects Analysis

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Asset Strategy Management

Asset Strategy Optimization

Reliability Centered Maintenance

Failure Modes and Effects Analysis

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Asset Strategy User Instructions

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Accessing the Asset Strategy Dashboard

The Dashboard page appears, displaying the Asset Strategy dashboard.

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Aspects of the Asset Strategy Dashboard

The Asset Strategy dashboard contains the following sections:

Content Filter section

Evaluate Risk and Performance section

Mitigate Risk & Optimize Action Plan section

Communicate, Implement, and Execute Plan section

Criticality Distribution section

Asset Strategy Workflows section

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

The Content Filter section contains the following lists:

Total Unplanned Maintenance Costs

Evaluate Risk and Performance

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Total Unplanned Maintenance Costs

For example, suppose that:

You select the value Roanoke in the Site list.

The Functional Location record Roanoke is linked to a Work History record

Event Start Date: 7/17/2013

Event Type: Repair

Maintenance Cost: 100

Event Start Date: 7/15/2013

Event Type: Repair